Vehicle mileage data management method

Abstract

The vehicle mileage data management method comprises the following steps: S10, after a vehicle is powered on, updating the value of a local backup total mileage as the value of the total mileage of an instrument every time the total mileage of the instrument is increased by a set increment; s20, judging whether the connection authentication between the vehicle-mounted communication module and the cloud operation platform is successful or not, and if yes, entering S30; s30, adding 1 to the non-updated reporting times, and reporting the non-updated reporting times and the local backup total mileage to the cloud operation platform; s40, after the cloud operation platform receives the reported local backup total mileage and the non-updated reporting times, judging whether a quotient obtained by dividing a difference value between the received local backup total mileage and the cloud backup total mileage by a set increment is consistent with the received non-updated reporting times or not; if yes, the value of the cloud backup total mileage is updated to be the value of the local backup total mileage, an updating success signal is sent to the vehicle, and the vehicle resets the number of reporting times which are not updated after receiving the updating success signal. Therefore, the original data can be reserved after the total mileage of the vehicle stored on the vehicle is lost or tampered.

Description

Technical Field

[0001] The present invention relates to a data management method, in particular to a method for managing vehicle mileage data. Background Art

[0002] Vehicle mileage is a key indicator of a car's condition and value, and serves as a reference for drivers' regular maintenance. Currently, to prevent mileage loss, the instrument cluster's mileage is backed up using other vehicle controllers. However, if both the backup controller and the instrument cluster's mileage are lost or tampered with, the original mileage cannot be restored. Summary of the Invention

[0003] The object of the present invention is to provide a method for managing vehicle mileage data, which can retain the original vehicle mileage after the vehicle mileage of a backup controller and an instrument are lost or tampered with.

[0004] The present invention provides a method for managing vehicle mileage data. The vehicle includes an instrument and an on-board communication module. The instrument stores the total mileage. The total mileage is calculated in real time based on the vehicle's operating conditions. The on-board communication module stores a local backup of the total mileage and the number of unupdated reports. A cloud-based operations platform stores the cloud-based backup of the total mileage. The management method includes the following steps: S10: after the vehicle is powered on, the value of the local backup total mileage is updated to the value of the instrument total mileage every time the instrument total mileage increases by a set increment, and then enters S20; S20: determines whether the connection authentication between the on-board communication module and the cloud operation platform is successful. If the judgment result is yes, enters S30; S30: adds 1 to the number of unupdated reports and reports them to the cloud operation platform together with the local backup total mileage, and then enters S40; and S40: after the cloud operation platform receives the reported local backup total mileage and the number of unupdated reports, determines whether the quotient of the difference between the received local backup total mileage and the cloud backup total mileage divided by the set increment is consistent with the received number of unupdated reports. If the judgment result is yes, the value of the cloud backup total mileage is updated to the value of the local backup total mileage, and an update success signal is sent to the vehicle. After the vehicle receives the update success signal, the number of unupdated reports is cleared.

[0005] This vehicle mileage data management method can back up the original vehicle mileage on a cloud-based operations platform as a cloud-based backup mileage. The original vehicle mileage refers to the vehicle mileage before the mileage recorded on the vehicle's communication module and meter was lost or tampered with. This ensures that even if the mileage recorded on the vehicle's communication module and meter is lost or tampered with, the original mileage remains on the cloud-based operations platform, facilitating data recovery and verification.

[0006] In another exemplary implementation of the vehicle mileage data management method, after the vehicle is powered on, the process enters S20 .

[0007] In another exemplary embodiment of the vehicle mileage data management method, S10 includes: S11: after the vehicle is powered on, cyclically determine whether the vehicle is driving normally. If the determination result is yes, enter S12; S12: determine whether the difference between the value of the total mileage of the instrument and the value of the local backup total mileage reaches a set increment. If the determination result is yes, enter S13; and S13: update the value of the local backup total mileage to the value of the total mileage of the instrument, and then enter S20.

[0008] In another exemplary embodiment of the vehicle mileage data management method, in S11 , it is determined whether the vehicle is running normally based on the vehicle speed and / or gear position.

[0009] In another exemplary embodiment of the vehicle mileage data management method, the on-board communication module also stores an update flag. The value of the update flag is 0 or 1. S10 also includes: setting the value of the update flag to 0 while updating the value of the local backup total mileage. S40 also includes: setting the value of the update flag to 1 after the vehicle receives the update success signal. The instrument stores the instrument VIN. The on-board communication module stores the vehicle VIN. An instrument mileage recovery interaction module is provided on the vehicle for users to submit instrument mileage recovery requests. The management method also includes the following steps: S60: After the user submits the instrument mileage recovery request through the instrument mileage recovery interaction module, determine whether the vehicle VIN is consistent with the instrument VIN. If the judgment result is yes, enter S70; S70: determine whether the value of the update flag is 1. If the judgment result is yes, enter S80; and S80: update the value of the instrument total mileage to the value of the local backup total mileage and prompt that the instrument mileage recovery is successful.

[0010] In another exemplary implementation of the vehicle mileage data management method, each time the vehicle is powered on, the value of the update flag is set to 0.

[0011] In another exemplary embodiment of the vehicle mileage data management method, S40 further includes: after the cloud operation platform receives the reported local backup total mileage and the number of unupdated reports, it sends a report success signal to the vehicle. In S70, if the judgment result is no, then enter S20 and S90: judge whether the vehicle has received the report success signal and the update success signal. If the report success signal and the update success signal are not received, it prompts that the instrument mileage recovery failed and the failure reason is the vehicle network abnormality. If the report success signal is received and the update success signal is not received, it prompts that the instrument mileage recovery failed and the failure reason is the local backup total mileage abnormality. If the report success signal and the update success signal are received, the instrument total mileage value is updated to the local backup total mileage value and prompts that the instrument mileage recovery is successful.

[0012] In another exemplary embodiment of the vehicle mileage data management method, in S60, if the judgment result is no, then proceed to S100: prompting that the meter mileage recovery failed and the failure reason is that the vehicle VIN is inconsistent with the meter VIN.

[0013] In another exemplary implementation of the vehicle mileage data management method, in S20 , if the judgment result is no, S20 is repeatedly executed.

[0014] In another exemplary implementation of the vehicle mileage data management method, in S40 , if the judgment result is no, it is prompted that the local backup total mileage is abnormal. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The following drawings are only used to schematically illustrate and explain the present invention and are not intended to limit the scope of the present invention.

[0016] Figure 1 The present invention is a flowchart of an exemplary embodiment of a method for managing vehicle mileage data.

[0017] Figure 2 For illustration Figure 1 The carrier of vehicle mileage data in the management method shown.

[0018] Figure 3 for Figure 1 The specific flow chart of S10 of the management method is shown.

[0019] Figure 4 A flowchart of another exemplary embodiment of a method for managing vehicle mileage data.

[0020] Description of labels 10 vehicles 11 Instruments 12 Vehicle Communication Module 20 Cloud operation platform. DETAILED DESCRIPTION

[0021] In order to have a clearer understanding of the technical features, purposes and effects of the invention, the specific embodiments of the present invention are now described with reference to the accompanying drawings. The same reference numerals in the drawings represent components with the same structure or similar structures but the same functions.

[0022] In this document, “illustrative” means “serving as an example, instance or illustration”, and any diagram or implementation described in this document as “illustrative” should not be interpreted as a more preferred or more advantageous technical solution.

[0023] To simplify the drawings, each figure schematically shows only the parts related to the present invention, which do not represent the actual structure of the product.

[0024] The present invention provides a method for managing vehicle mileage data. Figure 1 The present invention is a flowchart of an exemplary embodiment of a method for managing vehicle mileage data. Figure 2 For illustration Figure 1 The carrier of vehicle mileage data in the management method shown. Figure 2 As shown, the vehicle 10 includes an instrument 11 and an on-board communication module 12. The instrument 11 stores the total mileage of the instrument and can display the value of the total mileage of the instrument after the vehicle is powered on. The total mileage of the instrument is calculated in real time according to the operation of the vehicle. Specifically, the total mileage of the instrument is calculated in real time according to the rotation of the wheels, for example, but not limited to this. The on-board communication module 12 stores the local backup total mileage and the number of unupdated reports. The cloud operation platform 20 stores the cloud backup total mileage. The factory values of the total mileage of the instrument, the local backup total mileage, the number of unupdated reports and the cloud backup total mileage are, for example, all 0. The vehicle 10 can, for example, establish a signal connection with the cloud operation platform 20 through the on-board communication module 12. The signal connection is, for example, a wireless connection.

[0025] like Figure 1 As shown, the vehicle mileage data management method includes the following S10 to S40.

[0026] S10: After the vehicle is powered on, the local backup total mileage value is updated to the total mileage value of the instrument each time the total mileage increases by a set increment, and then the process proceeds to S20. The set increment can be set as needed, for example, 10 km.

[0027] Specifically, if Figure 3 As shown, S10 specifically includes the following S11 to S13, for example.

[0028] S11: After the vehicle is powered on, a loop is performed to determine whether the vehicle is operating normally. If the determination is yes, the process proceeds to S12. Specifically, the determination is made based on the vehicle speed and / or gear position. More specifically, the determination is made if the vehicle speed is greater than 0 and the gear position is not P, but this is not limited to this. This loop is repeated, for example, every time a set duration is passed. The set duration can be set as needed.

[0029] S12: Determine whether the difference between the total mileage value of the meter and the value of the local backup total mileage reaches a set increment. If the determination result is yes, proceed to S13.

[0030] S13: Update the local backup total mileage value to the instrument total mileage value, and then enter S20.

[0031] S20: Determine whether the vehicle-mounted communication module has successfully connected and authenticated with the cloud-based operating platform. If so, proceed to S30. If not, repeat S20. Connection authentication is used, for example, to verify the identity of the vehicle-mounted communication module, thereby determining whether it is permitted to access specific data on the cloud-based operating platform. The cloud-based operating platform, for example, maintains a dedicated database for each registered vehicle-mounted communication module. This dedicated database, for example, stores the total mileage backed up in the cloud. Only registered vehicle-mounted communication modules can successfully connect and authenticate. After successful connection authentication, the vehicle-mounted communication module can access its corresponding dedicated database on the cloud-based operating platform.

[0032] S30: The number of unupdated reports is increased by 1 and reported together with the local backup total mileage to the cloud operation platform, and then enters S40.

[0033] S40: After receiving the reported local backup total mileage and the number of unupdated reports, the cloud operations platform determines whether the quotient of the difference between the received local backup total mileage and the cloud backup total mileage divided by the set increment is consistent with the received number of unupdated reports. If so, the cloud backup total mileage is updated to the local backup total mileage, and an update success signal is sent to the vehicle. Upon receiving the update success signal, the vehicle resets the number of unupdated reports to zero.

[0034] This vehicle mileage data management method can back up the original vehicle mileage on a cloud-based operations platform as a cloud-based backup mileage. The original vehicle mileage refers to the vehicle mileage before the mileage recorded on the vehicle's communication module and meter was lost or tampered with. This ensures that even if the mileage recorded on the vehicle's communication module and meter is lost or tampered with, the original mileage remains on the cloud-based operations platform, facilitating data recovery and verification.

[0035] like Figure 1 As shown, in an exemplary embodiment, after the vehicle is powered on, it enters S20 to enable timely data backup.

[0036] like Figure 1 As shown, in the exemplary embodiment, in S40, if the judgment result is no, the user is prompted that the local backup total mileage is abnormal, thereby facilitating the user to perform subsequent processing.

[0037] Figure 4 FIG. 1 is a flow chart of another exemplary embodiment of a method for managing vehicle mileage data. Figure 1 The management method shown in the figure further adds the steps of meter mileage recovery, which is consistent with Figure 1 The same or similar aspects of the management methods shown are not described in detail here, and the differences are described as follows.

[0038] In this illustrative embodiment, the on-board communication module also stores an update flag. The value of the update flag is 0 or 1. The factory value of the update flag is, for example, 0. S10 also includes: setting the value of the update flag to 0 while updating the value of the local backup total mileage. S40 also includes: setting the value of the update flag to 1 after the vehicle receives the update success signal. The instrument stores the instrument VIN. The on-board communication module stores the vehicle VIN. When the vehicle leaves the factory, the instrument VIN is consistent with the vehicle VIN. An instrument mileage recovery interaction module is provided on the vehicle for the user to submit an instrument mileage recovery request. The instrument mileage recovery interaction module is, for example, a physical button or a virtual button. As Figure 4 As shown, the management method further includes the following S60 to S80.

[0039] S60: After the user submits the meter mileage recovery request through the meter mileage recovery interactive module, it is determined whether the vehicle VIN is consistent with the meter VIN. If the determination result is yes, the process proceeds to S70.

[0040] S70: Determine whether the value of the update flag is 1. If yes, proceed to S80.

[0041] S80: The total mileage value of the meter is updated to the value of the local backup total mileage, and the user is prompted that the meter mileage is restored successfully, so that the user can understand the meter mileage restoration status.

[0042] In an exemplary embodiment, S40 further includes: after the cloud operation platform receives the reported local backup total mileage and the number of unupdated reports, it sends a reporting success signal to the vehicle. If the judgment result in S70 is negative, the process proceeds to S20 and S90. S90 performs different processing based on the execution result after entering S20. Specifically, S90 determines whether the vehicle has received the reporting success signal and the update success signal. If neither the reporting success signal nor the update success signal is received, the user is notified that the meter mileage restoration failed and the failure was caused by a vehicle network anomaly. This allows the user to understand the reason for the meter mileage restoration failure and facilitates subsequent processing. If the reporting success signal is received but the update success signal is not received, the user is notified that the meter mileage restoration failed and the failure was caused by an anomaly in the local backup total mileage. This allows the user to understand the reason for the meter mileage restoration failure and facilitates subsequent processing. If the reporting success signal and the update success signal are received, the meter total mileage value is updated to the local backup total mileage value, and the user is notified that the meter mileage restoration was successful. This allows the user to understand the meter mileage restoration status.

[0043] In an exemplary embodiment, each time the vehicle is powered on, the update flag is set to 0. This prevents the local backup total mileage of the onboard communication module from being tampered with while the vehicle is powered off, which would cause the instrument mileage to be restored using the tampered local backup total mileage.

[0044] like Figure 4 As shown, in the exemplary embodiment, if the result of the determination in S60 is negative, the process proceeds to S100: the user is notified that the meter mileage restoration failed and the reason for the failure is that the vehicle VIN is inconsistent with the meter VIN. This allows the user to understand the reason for the meter mileage restoration failure and facilitates subsequent processing.

[0045] In an exemplary embodiment, the above prompt is implemented, for example, through a display screen or a speaker provided in the vehicle, but is not limited thereto.

[0046] It should be understood that although this specification is described according to various embodiments, not every embodiment contains only one independent technical solution. This narrative method of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment can also be appropriately combined to form other implementation methods that can be understood by those skilled in the art.

[0047] The series of detailed descriptions listed above are only specific descriptions of feasible embodiments of the present invention. They are not intended to limit the scope of protection of the present invention. Any equivalent implementation scheme or changes that do not deviate from the technical spirit of the present invention, such as the combination, division or repetition of features, should be included in the scope of protection of the present invention.

Claims

1. A method for managing vehicle mileage data, characterized in that: The vehicle includes an instrument and an on-board communication module. The instrument stores the total mileage of the instrument, which is calculated in real time based on the vehicle's operating conditions. The on-board communication module stores the local backup total mileage and the number of unupdated reports. The cloud operation platform stores the cloud backup total mileage. The management method includes the following steps: S10: After the vehicle is powered on, each time the total mileage of the instrument increases by a set increment, the local backup total mileage value is updated to the total mileage of the instrument, and then the process goes to S20; S20: Determine whether the vehicle communication module and the cloud operation platform are successfully connected and authenticated. If the judgment result is yes, proceed to S30; S30: The number of unupdated reports is increased by 1 and reported together with the local backup total mileage to the cloud operation platform, and then the process proceeds to S40; and S40: After the cloud operation platform receives the reported local backup total mileage and the number of unupdated reports, it determines whether the quotient of the difference between the received local backup total mileage and the cloud backup total mileage divided by the set increment is consistent with the received number of unupdated reports. If the judgment result is yes, the value of the cloud backup total mileage is updated to the value of the local backup total mileage, and an update success signal is sent to the vehicle. After the vehicle receives the update success signal, the number of unupdated reports is cleared.

2. The vehicle mileage data management method according to claim 1, characterized in that: After the vehicle is powered on, it enters S20.

3. The vehicle mileage data management method according to claim 1, characterized in that: The S10 includes: S11: After the vehicle is powered on, it is cyclically determined whether the vehicle is running normally. If the determination result is yes, it proceeds to S12; S12: Determine whether the difference between the total mileage value of the meter and the total mileage value of the local backup reaches the set increment. If the determination result is yes, proceed to S13; and S13: Update the local backup total mileage value to the instrument total mileage value, and then enter S20.

4. The vehicle mileage data management method according to claim 3, characterized in that: In S11 , it is determined whether the vehicle is running normally based on the vehicle speed and / or gear position.

5. The vehicle mileage data management method according to claim 1, characterized in that: The on-board communication module further stores an update flag, the value of which is 0 or 1. S10 further includes: setting the value of the update flag to 0 while updating the local backup total mileage value. S40 further includes: setting the value of the update flag to 1 after the vehicle receives the update success signal. The instrument stores the instrument VIN, and the on-board communication module stores the vehicle VIN. The vehicle is provided with an instrument mileage recovery interactive module for a user to submit an instrument mileage recovery request. The management method further includes the following steps: S60: After the user submits a meter mileage recovery request through the meter mileage recovery interactive module, it is determined whether the vehicle VIN is consistent with the meter VIN. If the determination result is yes, the process proceeds to S70; S70: Determine whether the value of the update flag is 1. If yes, proceed to S80; and S80: The total mileage value of the instrument is updated to the value of the local backup total mileage and a prompt is given indicating that the instrument mileage recovery is successful.

6. The vehicle mileage data management method according to claim 5, characterized in that: Each time the vehicle is powered on, the value of the update flag is set to 0.

7. The vehicle mileage data management method according to claim 5, characterized in that: S40 also includes: after the cloud operation platform receives the reported local backup total mileage and the number of unupdated reports, it sends a reporting success signal to the vehicle. In S70, if the judgment result is no, it enters S20 and S90: judge whether the vehicle receives the reporting success signal and the updating success signal. If the reporting success signal and the updating success signal are not received, it prompts that the instrument mileage recovery failed and the failure reason is the vehicle network abnormality. If the reporting success signal is received and the updating success signal is not received, it prompts that the instrument mileage recovery failed and the failure reason is the local backup total mileage abnormality. If the reporting success signal and the updating success signal are received, the value of the instrument total mileage is updated to the value of the local backup total mileage and the instrument mileage recovery is successful.

8. The vehicle mileage data management method according to claim 5, characterized in that: If the result of the determination in S60 is no, the process proceeds to S100 : prompting that the meter mileage restoration has failed and the reason for the failure is that the vehicle VIN is inconsistent with the meter VIN.

9. The vehicle mileage data management method according to claim 1, characterized in that: In S20, if the judgment result is no, S20 is repeatedly executed.

10. The vehicle mileage data management method according to claim 1, characterized in that: In S40 , if the judgment result is no, it is prompted that the local backup total mileage is abnormal.

Images