Vehicle function pre-sales inspection and verification method and device and electronic equipment

Abstract

The embodiment of the invention provides a vehicle function pre-sales inspection and verification method and device and electronic equipment, and relates to the technical field of vehicle detection, and the method comprises the steps: obtaining detection data actively uploaded by a vehicle in a pre-sales detection execution process, carrying out the dynamic storage based on time, calling the detection data in real time for state early warning and result calculation, and comparing the obtained manual detection information with a calculation result based on vehicle data, efficiently and conveniently finding out abnormal problems such as improper execution and low efficiency of pre-sales detection through the difference between the manual detection information and the calculation result, and generating a verification report according to the abnormal problems so as to comprehensively and accurately grasp the pre-sales detection condition. Detection personnel are supervised, urged and guided to correctly and efficiently carry out vehicle pre-sales detection according to a set process standard. According to the invention, cloud full-link automatic monitoring and verification of vehicle function pre-sales detection execution conditions are realized, so that dealers are effectively controlled to carry out pre-sales detection work, and the detection and supervision efficiency is improved while the cost is saved.

Description

[Technical field]

[0001] The embodiments of the present application relate to the field of vehicle detection technology, and in particular to a method, device and electronic equipment for pre-sale inspection and verification of vehicle functions. [Background technology]

[0002] Before a car is sold, it needs to be inspected by inspectors at the dealership for a pre-sale inspection (PDI: Pre Delivery Inspection). However, there are currently situations where the PDI inspection is not thorough enough or the inspection is not in place, which not only leads to the risk of vehicle functions not being able to be used normally, but also affects the brand reputation of the car company that produces the vehicle. At present, car companies do not have effective, reliable, and efficient technical means to verify whether the PDI inspection is performed manually according to the process, so they cannot ensure that the functions of the delivered vehicles can be used normally. [Summary of the invention]

[0003] The embodiments of the present application propose a method, device and electronic equipment for pre-sale inspection and verification of vehicle functions, which relate to the field of vehicle detection technology and can verify the comprehensiveness and accuracy of pre-sale inspection tasks of major vehicle functions by automated technical means, thereby saving costs and improving the effectiveness of inspection and supervision.

[0004] In a first aspect, an embodiment of the present application provides a method for pre-sale inspection and verification of vehicle functions, the method comprising:

[0005] While manually executing the vehicle function pre-sale inspection process, receiving the pre-sale inspection data of the current tested function actively fed back by the vehicle;

[0006] After parsing the pre-sale inspection data, the data is stored in a plurality of partitions having the same time unit;

[0007] Based on the stored pre-sale inspection data, a real-time warning of the vehicle function inspection status is provided, and a real-time calculation and judgment is made on whether the pre-sale inspection of the current tested function has been completed according to the warning record; wherein the real-time warning is used to record and monitor the status change of the current tested function;

[0008] Obtaining the input information of the execution result of the manual pre-sales inspection and comparing it with the calculated execution result of the pre-sales inspection;

[0009] Generate a pre-sale inspection monitoring report based on the comparison results.

[0010] In this embodiment, during the execution of pre-sale inspection, the inspection data actively uploaded by the vehicle is obtained and dynamically stored based on time, and the inspection data is called in real time for status warning and result calculation. The obtained manual inspection information is then compared with the calculation results based on the vehicle data. Through the difference between the two, abnormal problems such as inadequate execution and low efficiency of pre-sale inspection can be efficiently and conveniently discovered, and a verification report is generated accordingly, so as to comprehensively and accurately grasp the pre-sale inspection situation, urge and guide the inspection personnel to correctly and efficiently carry out vehicle pre-sale inspection in accordance with the established process standards. This application realizes full-link automated monitoring and verification of the execution of vehicle function pre-sale inspection in the cloud, thereby effectively controlling the dealers to carry out pre-sale inspection work, while saving costs and improving the efficiency of inspection and supervision.

[0011] In at least one possible implementation, the real-time warning vehicle function check status includes:

[0012] Obtain the operating status of the function under test and the time of status acquisition in real time;

[0013] According to the changes in the operating status of the function under test, the warning content is determined and recorded, and the warning occurrence time is determined based on the corresponding status collection time.

[0014] In at least one possible implementation, the real-time calculation and determination of whether the pre-sale inspection of the current function under test has been completed includes: obtaining a record of successful inspection of the current function under test based on the warning content, and combining the corresponding warning occurrence time, vehicle sales and dealer collection time information, to calculate and determine whether the vehicle has completed the pre-sale inspection process of the current function under test.

[0015] In this embodiment, real-time warning is provided for the real-time CAN data actively uploaded by the vehicle during the inspection process, and the successful record of the tested function is obtained in real time, thereby automatically triggering real-time calculation to determine whether the PDI detection of the current tested function is completed, thereby achieving the purpose of efficient and automated verification.

[0016] In at least one possible implementation manner, the pre-sale inspection data includes: real-time data and historical data, wherein the historical data is data that is not uploaded in real time during the same inspection process.

[0017] The real-time data actively uploaded by the vehicle and the automatically reissued historical data provide a true and complete data source for the OEM to verify the PDI test results of the dealer's tested functions, and provide a reliable data basis for both the real-time and offline calculations involved in this application.

[0018] In at least one possible implementation, the verification method further includes a non-real-time processing method:

[0019] Extracting the historical data within a predetermined time range from the stored data at a preset frequency;

[0020] Based on the time sequence of the extracted historical data, determine the power-on and power-off time of the vehicle, and calculate and record the corresponding detection status label in combination with the change of the operating status of the tested function;

[0021] Use the inspection status label to determine whether the pre-sale inspection has been completed.

[0022] The offline calculation proposed in this embodiment can completely and accurately calculate the status label of the function under test, make up for the deficiency that the real-time warning calculation results may be inaccurate, and provide data guarantee for the accuracy of the PDI verification report.

[0023] In at least one possible implementation, the verification method further includes:

[0024] If the comparison results are inconsistent, a prompt message to re-perform the pre-sales inspection will be automatically pushed;

[0025] If the comparison results are consistent, the execution reminder information of the pre-sales inspection will be automatically pushed according to the established cycle.

[0026] In this embodiment, the abnormal problem of manual execution of PDI is not determined through inconsistency comparison, and it is further proposed that even if the comparison is consistent, PDI detection supervision information needs to be sent to the manual end at regular intervals to ensure the timeliness of PDI execution.

[0027] In at least one possible implementation manner, the storing in several partitions having the same time unit includes: determining a corresponding date according to the time when the data is received, and storing in a corresponding partition set in units of a predetermined time duration.

[0028] In this embodiment, the data is stored in a predetermined time unit according to the date of data reception, which is beneficial for storing vehicle inspection data and also for quickly extracting data for the aforementioned offline processing process.

[0029] In a second aspect, an embodiment of the present application provides a vehicle function pre-sale inspection and verification device, the device comprising:

[0030] A vehicle inspection data receiving module is used to receive the pre-sale inspection data of the current tested function actively fed back by the vehicle while the vehicle function pre-sale inspection process is manually performed;

[0031] An inspection data storage module, used to parse the pre-sale inspection data and store them in a plurality of partitions with the same time unit;

[0032] An inspection status calculation module is used to warn the vehicle function inspection status in real time based on the stored pre-sale inspection data, and to calculate and determine in real time whether the pre-sale inspection of the current tested function has been completed according to the warning record; wherein the real-time warning is used to record and monitor the status change of the current tested function;

[0033] The pre-sale inspection data verification module is used to obtain the input information of the execution result of the manual pre-sale inspection and compare it with the calculated pre-sale inspection execution result;

[0034] The supervision report generation module is used to generate a pre-sale inspection monitoring report based on the comparison results.

[0035] In a third aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors, a memory, and one or more computer programs, wherein the memory may adopt a non-volatile storage medium, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, and when the instructions are executed by the device, the electronic device performs the method as described in the first aspect or any possible implementation manner of the first aspect.

[0036] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer-readable storage medium is run on a computer, the computer executes the method as described in the first aspect or any possible implementation of the first aspect.

[0037] It should be understood that the second to fourth aspects of the embodiments of the present application are consistent with the technical solutions of the first aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here.

Brief Description of the Drawings

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1 A flowchart of a method for pre-sale inspection and verification of vehicle functions provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of offline calculation of parking status tags provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of the structure of a vehicle function pre-sale inspection and verification device provided in an embodiment of the present application. [Specific implementation method]

[0042] In order to better understand the technical solution of this specification, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0043] It should be clear that the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0044] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit this specification. The singular forms of "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0045] At present, OEMs verify dealers’ vehicle PDI test data only through manual regular spot checks, which not only consumes a lot of time and manpower costs, but is also extremely inefficient.

[0046] This application utilizes the execution data of the vehicle's PDI function test uploaded to the cloud to propose a reliable PDI test feedback and supervision execution monitoring solution, which can verify the execution of PDI tests, such as comprehensiveness and accuracy, by automated technical means, thereby effectively controlling the PDI test situation, saving costs while improving detection and supervision efficiency.

[0047] The technical solution protected by the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0048] See also Figure 1 , is a flow chart of a vehicle function pre-sale inspection and verification method provided in an embodiment of the present application. The flow of the method is described as follows:

[0049] Step 101: while manually executing the vehicle function pre-sale inspection process, receiving the pre-sale inspection data of the current tested function actively fed back by the vehicle.

[0050] To expand on this, taking parking PDI detection as an example, the inspection process can be performed according to the following standards:

[0051] (1) Time requirement: before the vehicle is delivered to the user;

[0052] (2) Inspection steps:

[0053] Start the vehicle and drive it to the vicinity of the parking position;

[0054] Start the automatic parking function through the car computer, key or mobile phone APP;

[0055] The vehicle searches for the parking garage → selects a parking location → triggers the start of parking → parking succeeds / takes over / failures.

[0056] (3) Evaluation: The parking function is turned on and used normally, and the parking PDI test is passed.

[0057] (4) Input the parking PDI detection into the system to complete.

[0058] The vehicle can collect the vehicle's hexadecimal message information through the intelligent vehicle terminal (T-BOX) and upload the vehicle message to the platform's cloud service. For example, when the PDI inspector performs PDI inspection on the parking function, the vehicle will actively send the parking function-related CAN message information to the OEM's platform, which can specifically include real-time CAN data messages and historical CAN messages.

[0059] Among them, the real-time CAN message is to ensure that the monitoring mechanism can grasp the PDI detection status of the vehicle in real time. If the vehicle cannot send the aforementioned real-time CAN message in time due to poor signal environment, the T-BOX can resend the CAN message in idle time after the signal is restored. This message is called a historical CAN message. Its main purpose is to ensure the integrity of the PDI detection data received by the cloud.

[0060] The T-BOX automatically uploads real-time CAN data and automatically reissues historical CAN data strategies, providing OEMs with a true and complete data source for verifying dealer parking PDI test results, and providing a data basis for real-time warning calculations and offline calculations.

[0061] Step 102: After parsing the pre-sale inspection data, the data is stored in a plurality of partitions having the same time unit.

[0062] Specifically, the platform's cloud server can decrypt and parse the PDI inspection message uploaded by the vehicle into plain text, and then store it securely in a large database. What can be further proposed in this link is that in order to improve the storage writing efficiency and the subsequent quick query of the corresponding data, the corresponding date (datetime, dt) of the time when the cloud service receives the CAN message data, that is, the corresponding date is determined according to the CAN message data time received by the cloud CAN data parsing and storage module. It can be pointed out that storing in a given time unit according to the data reception date dt is conducive to storing CAN data and quickly extracting data for offline calculations mentioned later. For example, PDI data is partitioned and stored in units of days: the pre-sales inspection data CAN message sent by a vehicle on the day of dt can be stored in the first dt partition; and the historical CAN message reissued by the vehicle can be stored in the second dt partition, that is, there can be different partitions to store CAN messages uploaded at different times.

[0063] Step 103: Based on the stored pre-sale inspection data, a real-time warning of the vehicle function inspection status is issued, and according to the warning record, it is calculated and determined whether the pre-sale inspection of the current tested function has been completed.

[0064] This step mainly includes two parts: real-time warning and real-time calculation. The real-time warning is mainly used to record and monitor the changes in the execution status of the current tested function of the vehicle; while the real-time calculation is mainly based on the warning records of the tested function to determine whether the PDI detection of the current tested function is completed in a statistical way.

[0065] The following uses the PDI of the parking function as an example to specifically introduce the real-time calculation process of the above status warning and judgment:

[0066] (1) The real-time warning rule processing steps are as follows:

[0067] a) After CAN data is parsed and stored, CAN message data is pushed in real time, including at least three pieces of information: vehicle identification number (VIN), collection time (CollectTime), and parking operation status (IPAOperSts, Intelligent Parking Assistance Operation Status). The true value meaning corresponding to IPAOperSts is shown in Table 1.

[0068] Table 1 IPAOperSts truth value mapping table

[0069] IPAOperSts True Value Truth value meaning 0 Closed state 1 Not Ready 2 Ready state 3 Looking for parking space 4 Find a parking space 5 Parking in progress 6 Parking successful 7 Parking takeover 8 Parking failure

[0070] b) Parking success warning: When the IPAOperSts=4 changes to IPAOperSts=5 of a certain vehicle, the warning rule is triggered, and the CollectTime corresponding to the message IPAOperSts=4 is the warning occurrence time. At this time, real-time monitoring of the warning begins, and the actual date corresponding to the warning occurrence date=CollectTime and the warning occurrence time=CollectTime, VIN are synchronously recorded; subsequently, when the IPAOperSts=5 changes to IPAOperSts=6, it means that the parking is successful, the warning exits and records the parking success time=(CollectTime corresponding to the message IPAOperSts=6).

[0071] c) Parking takeover warning: When a vehicle's IPAOperSts=4 changes to IPAOperSts=5, the warning rule is triggered, and the CollectTime corresponding to the message IPAOperSts=4 is the warning occurrence time. At this time, real-time monitoring of the warning begins, and the warning occurrence date = the actual date corresponding to CollectTime, and the warning occurrence time = CollectTime, VIN are recorded; subsequent monitoring to IPAOperSts=5 changing to IPAOperSts=7 indicates that parking is taken over, the warning is exited, and the parking takeover time = (CollectTime corresponding to the message IPAOperSts=7) is recorded.

[0072] d) Parking failure warning: When a vehicle's IPAOperSts=4 changes to IPAOperSts=5, the warning rule is triggered, and the CollectTime corresponding to the message IPAOperSts=4 is the warning occurrence time. At this time, real-time monitoring of the warning begins, and the warning occurrence date = the actual date corresponding to CollectTime and the warning occurrence time = CollectTime, VIN are recorded; subsequent monitoring to IPAOperSts=5 changing to IPAOperSts=8 indicates parking failure, the warning is exited, and the parking failure time = (the CollectTime corresponding to the message IPAOperSts=8) is recorded.

[0073] (2) Real-time statistical calculation:

[0074] After each real-time warning is exited, the warning occurrence time in the result data of the successful parking warning of the vehicle on that day is automatically extracted and compared with the dealer's car collection date and sales date according to the following rules to determine whether the PDI detection is completed:

[0075] 1) If the vehicle has not been sold (the sales date is empty), the warning occurrence date ≥ the dealer's vehicle collection date, and the parking PDI detection is completed, otherwise it is determined that the PDI is not completed;

[0076] 2) If the vehicle has been sold (the sales date is not empty), the sales date ≥ the warning occurrence date ≥ the dealer's vehicle collection date, and the parking PDI detection is completed, otherwise it is determined that the PDI is not completed;

[0077] 3) If the vehicle has no warning record of successful parking, it is determined that PDI is not completed.

[0078] Real-time warning is given to the real-time CAN data uploaded by T-BOX, and the parking success record is obtained in real time, so as to automatically trigger real-time calculation to determine whether the PDI detection of the current function under test is completed, so as to achieve the purpose of efficient and automated verification.

[0079] It is worth noting that the real-time warning and judgment calculation involved in the above-mentioned links are mainly used to parse the warning data of the day and count the usage detection of the vehicle's tested functions to meet the purpose of real-time monitoring. However, in some special scenarios, if part of the vehicle's CAN data message fails to be uploaded to the platform during the test of a certain function, regardless of whether the data is completed in the CAN data message received by the cloud platform on the same day, during the above-mentioned warning and calculation process, some of the CAN data at the beginning, middle, and result of the test of a certain function process is lost. At this time, the warning start time and warning end time of the tested function may not correspond to the same tested function process record, and even cause the warning to fail to trigger. Based on this special situation analysis, the present application proposes in other preferred embodiments that the shortcomings of this scenario can be compensated by offline calculation.

[0080] The overall idea is to first extract several CAN data messages uploaded and parsed by the vehicle in the most recent time; then, determine the power-on and power-off time of the vehicle in ascending time order, and obtain and record the corresponding detection status label in combination with the operating status information of the function under test; then use the detection status label to determine whether the pre-sales inspection has been completed, thereby effectively making up for the shortcomings of real-time calculation and ensuring the accuracy and integrity of the data results.

[0081] This application designs offline calculations, mainly for the PDI process data that is subsequently reissued to the cloud. Since the aforementioned real-time warning and calculation cannot monitor the reissued data, the results of real-time calculations may not be able to ensure data integrity. Therefore, offline calculations can completely and accurately calculate the status labels of the functions under test, making up for the inaccurate calculation results of real-time warnings, and providing data guarantees for the accuracy of PDI test reports.

[0082] Combined with the previous example, the offline processing process is explained as follows:

[0083] (1) First, determine the data range for offline processing: Assuming that there is a 7-day CAN data reissue mechanism, the PDI data of the vehicle on that day may be stored in multiple dt messages. In order to ensure the integrity of the data, during offline calculation, the CAN messages of the first 7 dt are extracted each time to calculate the parking function status label. Here is an example of determining the date range. If the offline calculation date is T, the CAN messages corresponding to T-1 to T-7 are extracted; if the offline calculation date is T+1, the CAN messages corresponding to T to T-6 are extracted;

[0084] (2) Secondly, determine the frequency of offline processing. For example, in the above example, the CAN data of the first 7 dt is extracted for calculation each time. In this example, the frequency of offline calculation of parking detection status tags can be set to once a day.

[0085] (3) Combining the above Table 1 and Figure 2 As shown, the steps of calculating the parking tag offline may include:

[0086] a) Extract the following CAN data from the previous 7 days: VIN, CollectTime, IPAOperSts, and Vehicle Ready Status (VehRdySts), and sort each VIN in ascending order by CollectTime;

[0087] b) Find the VehRdySts corresponding to each VIN in chronological order. When VehRdySts=0 changes to VehRdySts=1, the corresponding CollectTime is determined as the power-on time, and the corresponding date is the power-on date; when VehRdySts=1 changes to VehRdySts=0, the corresponding CollectTime is the power-off time;

[0088] c) During the period from power-on time to power-off time, find the first CAN message with IPAOperSts=3, and the corresponding CollectTime is the start time of searching for a parking space;

[0089] d) After the start time of searching for a parking space, if a CAN message is found in which IPAOperSts=3 changes to IPAOperSts=4, the corresponding CollectTime is the time when the parking space is found;

[0090] e) After finding the parking space time, if a CAN message is found where IPAOperSts=4 changes to IPAOperSts=5, the corresponding CollectTime is the parking start time;

[0091] f) Therefore, as mentioned above, after the parking start time, if a CAN message is found in which IPAOperSts=5 changes to IPAOperSts=6 or 7 or 8, the corresponding CollectTime is the time of parking success / takeover / failure;

[0092] g) Record parking detection status tags in the database, such as: VIN, power-on date, power-on time, power-off time, parking space search start time, parking space search time, parking start time, parking success time, parking takeover time, parking failure time, etc., and can overwrite the tag data repeated in the previous power-on date.

[0093] h) After the 7-day parking inspection status tag is recorded, the tag data of the corresponding vehicle is extracted from the database, and statistics are collected to determine whether the PDI inspection has been completed. Here, referring to the previous text, the power-on date tag is combined with the sales date and the dealer's receipt date to provide an example:

[0094] 1) If the vehicle has not been sold (the sales date is empty), the power-on date ≥ the dealer's vehicle collection date, and there is a parking success time tag (it can be understood that the parking success tag is not empty), then the parking PDI detection is determined to be completed, otherwise it is indicated to be incomplete;

[0095] 2) If the vehicle has been sold (the sales date is not empty), the sales date ≥ the power-on date ≥ the dealer's vehicle collection date, and there is a parking success time tag, then the parking PDI detection is considered to be completed, otherwise it is considered to be incomplete;

[0096] 3) If the corresponding vehicle does not have a parking success time tag, the PDI detection of the vehicle is not completed.

[0097] Continuing from the above, step 104: obtaining the input information of the execution result of the manual pre-sale inspection, and comparing it with the calculated execution result of the pre-sale inspection.

[0098] In actual operation, the vehicles for which the PDI inspection has not been completed as mentioned above, which are calculated and determined in the cloud, can be extracted at regular intervals and compared with the PDI inspection results of the corresponding vehicles in the PDI report entered by the dealer side through a call such as an HTTPS interface.

[0099] Step 105: Generate a pre-sale inspection monitoring report based on the comparison results.

[0100] For example, but not limited to, the use of visual analysis tools can be used to visualize the PDI monitoring result data and automatically output reports, which may include: the number of vehicles inspected for a certain function, the PDI completion rate of the function, the number of vehicles not inspected by PDI, the number of vehicles with abnormal PDI inspections, the number of vehicles that have completed PDI inspections, a detailed list of vehicles that have not undergone PDI inspections and have abnormal PDI inspections, etc. Efficient and intuitive viewing tools can reduce the verification workload and improve work efficiency.

[0101] Finally, it can be added that the purpose of comparing the cloud-based calculation results with the test data manually entered by the dealer is to verify whether the test personnel have correctly and truly performed the PDI test in accordance with the standard process. Therefore, if the calculation results are inconsistent with the manual results, it means that the PDI test has not been reliably performed on the dealer side. At this time, not only can the verification report be output, but the information can also be automatically pushed to the dealer side through the aforementioned interface, so that it can conduct self-inspection and re-conduct PDI testing as needed. Of course, even if the comparison results indicate that the two are consistent, the dealer can be urged to perform PDI testing regularly through the interface according to the established cycle, and it can also replace the manual screening of abnormal vehicles and incomplete vehicle lists.

[0102] See also Figure 3 Based on the same inventive concept, the embodiment of the present application also provides a vehicle function pre-sale inspection and verification device, the device comprising:

[0103] The vehicle inspection data receiving module 301 is used to receive the pre-sale inspection data of the current tested function actively fed back by the vehicle while the vehicle function pre-sale inspection process is manually executed;

[0104] An inspection data storage module 302 is used to parse the pre-sale inspection data and store it in a plurality of partitions with the same time unit;

[0105] The inspection status calculation module 303 is used to warn the vehicle function inspection status in real time based on the stored pre-sale inspection data, and to calculate and determine in real time whether the pre-sale inspection of the current tested function has been completed according to the warning record; wherein the real-time warning is used to record and monitor the status change of the current tested function;

[0106] The pre-sale inspection data verification module 304 is used to obtain the input information of the execution result of the manual pre-sale inspection and compare it with the calculated pre-sale inspection execution result;

[0107] The supervision report generating module 305 is used to generate a pre-sale inspection monitoring report based on the comparison result.

[0108] Based on the same inventive concept, an embodiment of the present application also provides an electronic device, including at least one processor, which is used to execute a computer program stored in a memory to implement the flow chart steps of the above-mentioned vehicle function pre-sale inspection and verification method provided in the embodiment of the present application.

[0109] Optionally, the processor may specifically be a central processing unit, a specific ASIC, or one or more integrated circuits for controlling program execution.

[0110] Optionally, the electronic device may further include a memory connected to at least one processor, and the memory may include ROM, RAM, and disk storage. The memory is used to store data required by the processor when it is running, that is, it stores instructions that can be executed by at least one processor, and at least one processor executes the methods mentioned in the above embodiments by executing the instructions stored in the memory. Among them, the number of memories is one or more. Among them, the number of memories is one or more.

[0111] An embodiment of the present application also provides a computer storage medium, wherein the computer storage medium stores computer instructions. When the computer instructions are executed on a computer, the computer executes the methods mentioned in the above embodiments.

[0112] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for pre-sale inspection and verification of vehicle functions, characterized in that: The method comprises: While manually executing the vehicle function pre-sale inspection process, receiving the pre-sale inspection data of the current tested function actively fed back by the vehicle; After parsing the pre-sale inspection data, the data is stored in a plurality of partitions having the same time unit; Based on the stored pre-sale inspection data, a real-time warning of the vehicle function inspection status is provided, and a real-time calculation and judgment is made on whether the pre-sale inspection of the current tested function has been completed according to the warning record; wherein the real-time warning is used to record and monitor the status change of the current tested function; Obtaining the input information of the execution result of the manual pre-sales inspection and comparing it with the calculated execution result of the pre-sales inspection; Generate a pre-sale inspection monitoring report based on the comparison results.

2. The vehicle function pre-sale inspection and verification method according to claim 1, characterized in that: The real-time warning vehicle function inspection status includes: Obtain the operating status of the function under test and the time of status acquisition in real time; According to the changes in the operating status of the function under test, the warning content is determined and recorded, and the warning occurrence time is determined based on the corresponding status collection time.

3. The vehicle function pre-sale inspection and verification method according to claim 2, characterized in that: The real-time calculation and determination of whether the pre-sale inspection of the current tested function has been completed includes: obtaining a record of a successful inspection of the current tested function according to the warning content, and calculating and determining whether the vehicle has completed the pre-sale inspection process of the current tested function in combination with the corresponding warning occurrence time, vehicle sales, and dealer collection time information.

4. The vehicle function pre-sale inspection and verification method according to claim 1, characterized in that: The pre-sale inspection data includes: real-time data and historical data, wherein the historical data is data that is not uploaded in real time during the same inspection process.

5. The vehicle function pre-sale inspection and verification method according to claim 4, characterized in that: The verification method also includes a non-real-time processing method: Extracting the historical data within a predetermined time range from the stored data at a preset frequency; Based on the time sequence of the extracted historical data, determine the power-on and power-off time of the vehicle, and calculate and record the corresponding detection status label in combination with the change of the operating status of the tested function; Use the inspection status label to determine whether the pre-sale inspection has been completed.

6. The vehicle function pre-sale inspection and verification method according to claim 1, characterized in that: The verification method further comprises: If the comparison results are inconsistent, a prompt message to re-perform the pre-sales inspection will be automatically pushed; If the comparison results are consistent, the execution reminder information of the pre-sales inspection will be automatically pushed according to the established cycle.

7. The vehicle function pre-sale inspection and verification method according to any one of claims 1 to 6, characterized in that: The storing in several partitions with the same time unit includes: determining the corresponding date according to the time when the data is received, and storing in the corresponding partition set in the unit of a predetermined time length.

8. A vehicle function pre-sale inspection and verification device, characterized in that: The device comprises: A vehicle inspection data receiving module is used to receive the pre-sale inspection data of the current tested function actively fed back by the vehicle while the vehicle function pre-sale inspection process is manually performed; An inspection data storage module, used to parse the pre-sale inspection data and store them in a plurality of partitions with the same time unit; An inspection status calculation module is used to warn the vehicle function inspection status in real time based on the stored pre-sale inspection data, and to calculate and determine in real time whether the pre-sale inspection of the current tested function has been completed according to the warning record; wherein the real-time warning is used to record and monitor the status change of the current tested function; The pre-sale inspection data verification module is used to obtain the input information of the execution result of the manual pre-sale inspection and compare it with the calculated pre-sale inspection execution result; The supervision report generation module is used to generate a pre-sale inspection monitoring report based on the comparison results.

9. An electronic device, characterized in that: include: One or more processors, a memory and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, which, when executed by the electronic device, enable the electronic device to execute the vehicle function pre-sale inspection and verification method as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the vehicle function pre-sale inspection and verification method according to any one of claims 1 to 7 is implemented.

Images