Mileage data recovery method and device and storage medium

Abstract

The invention discloses a mileage data recovery method and device and a storage medium, and belongs to the technical field of vehicle control. The method comprises the steps that after a vehicle is powered on, a first backup mileage and a first VIN stored in a TBOX are obtained; in response to the fact that the stored second VIN is inconsistent with the first VIN and information for starting the VIN write-in operation is received, the VIN write-in operation is executed, and the stored second VIN is updated into the first VIN in the VIN write-in operation; obtaining an execution detection result of the VIN write-in operation; in response to the fact that a detection result indicating successful execution of the VIN write-in operation is obtained and the stored second backup mileage is smaller than the first backup mileage, updating the stored second backup mileage to the first backup mileage; and displaying the first backup mileage. While the accuracy of the mileage data is ensured, the mileage data of the vehicle is recovered, and the integrity of the mileage data is ensured.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle control technology, and in particular to a method, device and storage medium for recovering mileage data. Background Art

[0002] Mileage data is an important record of vehicle driving conditions and is very important for vehicle maintenance, insurance claims, used car evaluation, etc. During vehicle use, if the instrument is damaged or replaced, resulting in the loss of vehicle mileage data, it will affect the driver's grasp of the vehicle's operating status. In related technologies, the vehicle's mileage data is recorded by another execution recording device.

[0003] In the related art, the mileage data of the execution recording device must be manually written into the instrument cluster through a diagnostic instrument, and the mileage data is subject to the risk of being tampered with. Therefore, how to restore the mileage data of the vehicle while ensuring the accuracy of the mileage data is a problem that needs to be solved. Summary of the invention

[0004] The embodiment of the present application provides a mileage data recovery method, device and storage medium, which can prevent mileage data errors when recovering the mileage data of a vehicle. The technical solution is as follows:

[0005] On the one hand, an embodiment of the present application provides a method for recovering mileage data, the method comprising:

[0006] After the vehicle is powered on, the first backup mileage and the first VIN (Vehicle Identification Number) stored in the TBOX (Telematics BOX) are obtained;

[0007] In response to the second VIN being stored being inconsistent with the first VIN and receiving information for starting a VIN write operation, performing a VIN write operation, wherein the VIN write operation is to update the second VIN stored to the first VIN;

[0008] Acquire an execution detection result of a VIN write operation, wherein the execution detection result of the VIN write operation is used to indicate whether the VIN write operation is successfully executed;

[0009] In response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage, updating the stored second backup mileage to the first backup mileage;

[0010] The first backup mileage is displayed.

[0011] On the other hand, a device for recovering mileage data is provided, the device comprising:

[0012] A first acquisition module, used to acquire a first backup mileage and a first vehicle identification code VIN stored in the remote communication terminal TBOX after the vehicle is powered on;

[0013] an execution module, configured to execute a VIN write operation in response to the stored second VIN being inconsistent with the first VIN and receiving information for starting a VIN write operation, wherein the VIN write operation is to update the stored second VIN to the first VIN;

[0014] A second acquisition module, used for acquiring an execution detection result of the VIN write operation, wherein the execution detection result of the VIN write operation is used for indicating whether the VIN write operation is successfully executed;

[0015] an updating module, configured to update the stored second backup mileage to the first backup mileage in response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage;

[0016] A display module is used to display the first backup mileage.

[0017] On the other hand, a non-temporary computer-readable storage medium is also provided, characterized in that a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to implement any of the mileage data recovery methods described above.

[0018] On the other hand, a computer program product is also provided, the computer program product comprising computer instructions, and when the computer instructions are executed by a processor, the steps of any of the above-mentioned mileage data recovery methods are implemented.

[0019] The technical solution provided by this application brings at least the following beneficial effects:

[0020] The present application obtains the first backup mileage and the first VIN stored in the TBOX after the vehicle is powered on, and performs a VIN write operation when the stored second VIN is inconsistent with the first VIN and information for starting the VIN write operation is received, thereby ensuring the accurate correspondence between the mileage data and the vehicle VIN; then obtains the execution detection result of the VIN write operation, and when the detection result indicating that the VIN write operation is successfully executed is obtained and the stored second backup mileage is less than the first backup mileage, the stored second backup mileage is updated to the first backup mileage and the first backup mileage is displayed, thereby restoring the vehicle's mileage data while ensuring the accuracy of the mileage data, thereby ensuring the integrity of the mileage data. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0022] Figure 1 It is a schematic diagram of an implementation environment provided by an embodiment of the present application;

[0023] Figure 2 is a flow chart of a method for recovering mileage data provided in an embodiment of the present application;

[0024] Figure 3 This is a logic flow chart for restoring mileage data provided by an embodiment of the present application;

[0025] Figure 4 It is a structural schematic diagram of a mileage data recovery device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0027] This application embodiment provides a method for recovering mileage data. Please refer to Figure 1 , which shows a schematic diagram of the implementation environment of the method provided in the embodiment of the present application. The implementation environment may include: a combination meter 11, an ECU (Electronic Control Unit) 12, a TBOX 13, an OBD (On-Board Diagnostics Tool) 14, a mileage sensor 15, a display screen 16 of a center console, and an audio system 17.

[0028] Optionally, the ECU 12 is used to obtain the power-on and power-off status of the vehicle and send it to the instrument cluster 11. The TBOX 13 is used to send the stored first backup mileage and the first VIN to the instrument cluster 11, and update the backup mileage after the instrument cluster 11 is updated. The OBD 14 is used to start the VIN write operation and write the first VIN stored in the TBOX 13 to the instrument cluster 11. The mileage sensor 15 is used to obtain the vehicle's mileage in real time and send it to the instrument cluster 11, so that the instrument cluster 11 updates the stored backup mileage.

[0029] Exemplarily, the display screen 16 of the center console is used to prompt for VIN inconsistency, display the execution detection result of the VIN write operation, and prompt for abnormal update of the backup mileage. Similarly, the audio 17 is also used to prompt for VIN inconsistency. The display screen of the instrument cluster 11 is used to display the backup mileage stored in the instrument cluster 11. In a possible implementation, the instrument cluster 11, ECU 12, TBOX 13, OBD 14, mileage sensor 15, the display screen 16 of the center console and the audio 17 establish a communication connection through a wired or wireless network.

[0030] Based on the above Figure 1 In the implementation environment shown, the present application embodiment provides a method for recovering mileage data as follows Figure 2 As shown, taking the method applied to a combination instrument as an example, the method includes steps 201 to 205.

[0031] In step 201 , after the vehicle is powered on, the instrument cluster obtains the first backup mileage and the first VIN stored in the TBOX.

[0032] In a possible implementation, the instrument cluster can obtain the power-on and power-off status of the vehicle through the ECU, wherein the power-on and power-off status of the vehicle includes the vehicle being powered on and the vehicle being powered off. Exemplarily, after determining that the power-on and power-off status of the vehicle is the vehicle being powered on, the instrument cluster obtains the first backup mileage and the first VIN stored in the TBOX, including: the instrument cluster obtains the first backup mileage and the first VIN stored in the TBOX through the CAN (Controller Area Network) bus. The first backup mileage is the total mileage of the vehicle stored in the TBOX, and the first VIN is the identification code of the vehicle stored in the TBOX.

[0033] In step 202 , in response to the second VIN stored being inconsistent with the first VIN and receiving information for starting a VIN write operation, the combination meter performs a VIN write operation, wherein the VIN write operation updates the second VIN stored to the first VIN.

[0034] In a possible implementation, after acquiring the first backup mileage and the first VIN stored in the TBOX, the instrument cluster compares the stored second VIN with the first VIN stored in the TBOX to determine whether the stored second VIN is consistent with the first VIN stored in the TBOX. In response to the stored second VIN being inconsistent with the first VIN, a prompt is given for the VIN inconsistency.

[0035] Optionally, if the comparison result is that the second VIN stored in the instrument cluster is inconsistent with the first VIN stored in the TBOX, the method of prompting the VIN inconsistency includes but is not limited to: displaying a text message of "VIN is inconsistent, please start the VIN write operation" on the display screen of the vehicle's center console; broadcasting a voice message of "VIN is inconsistent, please start the VIN write operation" through the audio system on the vehicle.

[0036] Exemplarily, after determining that the stored second VIN is inconsistent with the first VIN, the instrument cluster determines whether information for starting a VIN write operation is received. Optionally, after seeing the information indicating that the VIN is inconsistent, the maintenance personnel can start a VIN write operation through OBD to write the first VIN stored in the TBOX into the instrument cluster.

[0037] In one possible implementation, in response to the second VIN stored being inconsistent with the first VIN and receiving information to start the VIN write operation, the instrument cluster performs a VIN write operation, wherein the VIN write operation is to update the second VIN stored to the first VIN. Optionally, if the second VIN stored is inconsistent with the first VIN and the information to start the VIN write operation is received, the instrument cluster performs a VIN write operation, including: the instrument cluster writes the first VIN to the instrument cluster via the OBD, replacing the second VIN as the VIN stored in the instrument cluster. The OBD may be connected to the vehicle via the OBD-II port of the vehicle.

[0038] Exemplarily, in response to the stored second VIN being consistent with the first VIN, the instrument cluster keeps the stored second backup mileage unchanged. In a possible implementation, if the comparison result is that the second VIN stored in the instrument cluster is consistent with the first VIN stored in the TBOX, the instrument cluster keeps the currently stored second backup mileage unchanged, confirming that the currently stored second backup mileage is the latest total mileage of the vehicle.

[0039] In step 203 , the instrument cluster obtains an execution detection result of the VIN write operation, where the execution detection result of the VIN write operation is used to indicate whether the VIN write operation is successfully executed.

[0040] Exemplarily, after the VIN write operation starts to be executed for a first time period, the instrument cluster obtains an execution detection result of the VIN write operation, wherein the execution detection result of the VIN write operation is used to indicate whether the VIN write operation is successfully executed.

[0041] In one possible implementation, the instrument cluster obtains an execution detection result of the VIN write operation, including: the instrument cluster compares whether the currently stored VIN is consistent with the first VIN; if the currently stored VIN is consistent with the first VIN, the instrument cluster obtains a detection result indicating that the VIN write operation is successfully executed; if the currently stored VIN is inconsistent with the first VIN, the instrument cluster obtains a detection result indicating that the VIN write operation is not successfully executed.

[0042] Optionally, the execution detection result of the VIN write operation can be displayed in text form through the display screen of the vehicle center console. In a possible implementation, the first duration can be set to the longest duration required to normally complete the VIN write operation.

[0043] In step 204 , in response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage, the combination meter updates the stored second backup mileage to the first backup mileage.

[0044] Optionally, after obtaining the detection result indicating that the VIN write operation is successfully performed, the instrument cluster compares the stored second backup mileage with the first backup mileage stored in the TBOX to determine whether the stored second backup mileage is equal to the first backup mileage stored in the TBOX.

[0045] In a possible implementation, in response to obtaining a test result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage, the combination meter updates the stored second backup mileage to the first backup mileage. Exemplarily, if the test result indicating that the VIN write operation is successfully performed is obtained and the stored second backup mileage is less than the first backup mileage, the combination meter updates the stored second backup mileage to the first backup mileage, including: the combination meter stores the first backup mileage, replacing the second backup mileage as the latest total mileage of the vehicle.

[0046] In another possible implementation, in response to obtaining a test result indicating that the VIN write operation is successfully performed and the stored second backup mileage is greater than or equal to the first backup mileage, the stored second backup mileage is kept unchanged. Alternatively, if a test result indicating that the VIN write operation is successfully performed is obtained and the stored second backup mileage is greater than or equal to the first backup mileage, the instrument cluster keeps the stored second backup mileage unchanged and confirms that the currently stored second backup mileage is the latest total mileage of the vehicle.

[0047] Exemplarily, after the instrument cluster performs a VIN write operation, in response to obtaining at least one of a detection result indicating that the VIN write operation was not successfully performed or the vehicle is powered off, a prompt is given that the backup mileage update is abnormal. In a possible implementation, if a detection result indicating that the VIN write operation was not successfully performed is obtained, or it is identified that the power-on / off state of the vehicle is switched to the vehicle being powered off, a prompt is given that the backup mileage update is abnormal. The prompt method includes, but is not limited to: displaying a text message "the backup mileage update is abnormal" on the display screen of the vehicle center console.

[0048] In step 205 , the instrument cluster displays the first backup mileage.

[0049] In a possible implementation, after the instrument cluster completes updating the stored backup mileage, the instrument cluster displays the first backup mileage, including: the instrument cluster displays the first backup mileage in text form on a display screen of the instrument cluster.

[0050] Optionally, as the subsequent vehicle continues to travel, the stored second backup mileage is updated based on the mileage of the vehicle to obtain an updated backup mileage; in response to the updated backup mileage being greater than the first backup mileage, the TBOX is controlled to update the stored first backup mileage to the updated backup mileage. Exemplarily, the instrument cluster obtains the vehicle's mileage in real time according to the mileage sensor, and then updates the stored second backup mileage based on the vehicle's mileage to obtain an updated backup mileage.

[0051] Optionally, a mileage sensor can be installed on the vehicle's gearbox or axle to monitor the number of tire rotations in real time, and then calculate the vehicle's mileage based on the number of tire rotations and the circumference of the tire.

[0052] Illustratively, after acquiring the updated backup mileage, the instrument cluster compares the updated backup mileage with the first backup mileage. If the updated backup mileage is greater than the first backup mileage, the instrument cluster controls TBOX to update the stored first backup mileage to the updated backup mileage.

[0053] In summary, Figure 3The mileage data recovery logic flow chart shown in the figure is used as an example for illustration. Among them, the execution subject can be the instrument cluster. Step 301, TBOX sends the first backup mileage and the first VIN to the instrument cluster. Step 302, determine whether the stored second VIN is consistent with the first VIN stored in TBOX. If the stored second VIN is consistent with the first VIN stored in TBOX, go to step 303; if the stored second VIN is inconsistent with the first VIN stored in TBOX, go to step 304. Step 303, keep the currently stored second backup mileage unchanged. Step 304, prompt VIN inconsistency. After step 304, go to step 305.

[0054] Optionally, in step 305, it is determined whether information for starting the VIN write operation is received and successfully executed. If information for starting the VIN write operation is received and successfully executed, the process proceeds to step 306; if at least one of information for starting the VIN write operation is not received or unsuccessfully executed, the process proceeds to step 307. In step 306, it is determined whether the stored second backup mileage is equal to the first backup mileage stored in the TBOX. In step 307, the currently stored second backup mileage is kept unchanged.

[0055] In a possible implementation, after step 306, if the stored second backup mileage is equal to the first backup mileage stored in the TBOX, proceed to step 308; if the stored second backup mileage is not equal to the first backup mileage stored in the TBOX, proceed to step 309. In step 308, the stored second backup mileage is updated to the first backup mileage. In step 309, the currently stored second backup mileage is kept unchanged.

[0056] The embodiment of the present application obtains the first backup mileage and the first VIN stored in the TBOX after the vehicle is powered on, and performs a VIN write operation when the stored second VIN is inconsistent with the first VIN and information for starting the VIN write operation is received, thereby ensuring accurate correspondence between the mileage data and the vehicle VIN; then obtains the execution detection result of the VIN write operation, and when a detection result indicating that the VIN write operation is successfully executed is obtained and the stored second backup mileage is less than the first backup mileage, the stored second backup mileage is updated to the first backup mileage and the first backup mileage is displayed, thereby restoring the vehicle's mileage data while ensuring the accuracy of the mileage data, thereby ensuring the integrity of the mileage data.

[0057] See also Figure 4 , an embodiment of the present application provides a mileage data recovery device, the device comprising:

[0058] The first acquisition module 401 is used to acquire the first backup mileage and the first vehicle identification code VIN stored in the remote communication terminal TBOX after the vehicle is powered on;

[0059] An execution module 402 is configured to execute a VIN write operation in response to the stored second VIN being inconsistent with the first VIN and receiving information for starting a VIN write operation, wherein the VIN write operation is to update the stored second VIN to the first VIN;

[0060] A second acquisition module 403 is used to acquire an execution detection result of the VIN write operation, where the execution detection result of the VIN write operation is used to indicate whether the VIN write operation is successfully performed;

[0061] An updating module 404, configured to update the stored second backup mileage to the first backup mileage in response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage;

[0062] The display module 405 is used to display the first backup mileage.

[0063] In one possible implementation, the update module 404 is further used to update the stored second backup mileage based on the vehicle's mileage to obtain an updated backup mileage; in response to the updated backup mileage being greater than the first backup mileage, control TBOX to update the stored first backup mileage to the updated backup mileage.

[0064] In a possible implementation, the device further includes: a prompt module, configured to prompt that the VINs are inconsistent in response to the stored second VIN being inconsistent with the first VIN.

[0065] In a possible implementation, the first acquisition module 401 is further configured to keep the stored second backup mileage unchanged in response to the stored second VIN being consistent with the first VIN.

[0066] In a possible implementation, the second acquisition module 403 is further configured to keep the stored second backup mileage unchanged in response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is greater than or equal to the first backup mileage.

[0067] In a possible implementation, the device further includes: a prompt module for prompting that an abnormality occurs in the update of the backup mileage in response to obtaining at least one of a detection result indicating that the VIN write operation is not successfully performed or the vehicle is powered off.

[0068] After the vehicle is powered on, the device obtains the first backup mileage and the first VIN stored in the TBOX, and when the stored second VIN is inconsistent with the first VIN and information for starting the VIN write operation is received, the device performs a VIN write operation to ensure accurate correspondence between the mileage data and the vehicle VIN; then obtains the execution detection result of the VIN write operation, and when the detection result indicating that the VIN write operation is successfully executed is obtained and the stored second backup mileage is less than the first backup mileage, the stored second backup mileage is updated to the first backup mileage and the first backup mileage is displayed, thereby restoring the vehicle's mileage data while ensuring the accuracy of the mileage data, thereby ensuring the integrity of the mileage data.

[0069] It should be noted that the device provided in the above embodiment only uses the division of the above functional modules as an example to implement its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and their specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0070] In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor of a computer device to enable the computer to implement any of the above-mentioned mileage data recovery methods.

[0071] In one possible implementation, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0072] In an exemplary embodiment, a computer program product or a computer program is also provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs any of the above-mentioned methods for recovering mileage data.

[0073] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, the first VIN, the second VIN, the first backup mileage and the second backup mileage involved in this application are all obtained with full authorization.

[0074] It should be understood that the "plurality" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0075] It should be noted that the terms "first", "second", etc. (if any) in the specification and claims of the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0076] The above description is only an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for recovering mileage data, characterized in that: The method comprises: After the vehicle is powered on, the first backup mileage and the first vehicle identification code VIN stored in the remote communication terminal TBOX are obtained; In response to the second VIN being stored being inconsistent with the first VIN and receiving information for starting a VIN write operation, performing a VIN write operation, wherein the VIN write operation is to update the second VIN stored to the first VIN; Acquire an execution detection result of a VIN write operation, wherein the execution detection result of the VIN write operation is used to indicate whether the VIN write operation is successfully executed; In response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage, updating the stored second backup mileage to the first backup mileage; The first backup mileage is displayed.

2. The method according to claim 1, characterized in that: After the stored second backup mileage is updated to the first backup mileage, the method further includes: Updating the stored second backup mileage based on the mileage of the vehicle to obtain an updated backup mileage; In response to the updated backup mileage being greater than the first backup mileage, the TBOX is controlled to update the stored first backup mileage to the updated backup mileage.

3. The method according to claim 1, characterized in that The method further comprises: In response to the stored second VIN being inconsistent with the first VIN, a prompt is given that the VINs are inconsistent.

4. The method according to claim 1, characterized in that After obtaining the first backup mileage and the first VIN stored in the TBOX, the method includes: In response to the stored second VIN being consistent with the first VIN, the stored second backup mileage is maintained unchanged.

5. The method according to claim 1, characterized in that: After obtaining the execution detection result of the VIN write operation, the method further includes: In response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is greater than or equal to the first backup mileage, the stored second backup mileage is maintained unchanged.

6. The method according to claim 1, characterized in that The method further comprises: In response to obtaining at least one of a detection result indicating that the VIN write operation was not successfully performed or the vehicle being powered off, a prompt is given that an abnormality occurs in updating the backup mileage.

7. A mileage data recovery device, characterized in that: The device comprises: A first acquisition module, used to acquire a first backup mileage and a first vehicle identification code VIN stored in the remote communication terminal TBOX after the vehicle is powered on; an execution module, configured to execute a VIN write operation in response to the stored second VIN being inconsistent with the first VIN and receiving information for starting a VIN write operation, wherein the VIN write operation is to update the stored second VIN to the first VIN; A second acquisition module, used for acquiring an execution detection result of the VIN write operation, wherein the execution detection result of the VIN write operation is used for indicating whether the VIN write operation is successfully executed; an updating module, configured to update the stored second backup mileage to the first backup mileage in response to obtaining a detection result indicating that the VIN write operation is successfully performed and the stored second backup mileage is less than the first backup mileage; A display module is used to display the first backup mileage.

8. The device according to claim 7, characterized in that The update module is further used to update the stored second backup mileage based on the mileage of the vehicle to obtain an updated backup mileage; in response to the updated backup mileage being greater than the first backup mileage, control the TBOX to update the stored first backup mileage to the updated backup mileage.

9. A computer program product, comprising computer instructions, which, when executed by a processor, implement the steps of the mileage data recovery method according to any one of claims 1 to 6.

10. A non-transitory computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is loaded and executed by a processor to implement the mileage data recovery method according to any one of claims 1 to 6.

Images