Vehicle data uploading method and device, vehicle and storage medium

Abstract

The invention provides a vehicle data uploading method and device, a vehicle and a storage medium, and the method comprises the steps: obtaining a current mileage value and a target mileage difference value of the vehicle and a historical mileage value which is uploaded to a cloud platform last time in response to a starting instruction of the vehicle, wherein the target mileage difference value is used for representing a minimum mileage difference value for updating the mileage uploaded to the cloud platform; based on the target mileage difference value and the historical mileage value, determining a mileage jump risk value of the current mileage value, the mileage jump risk value being used for indicating whether the mileage value on the cloud platform has a jump risk if the current mileage value is uploaded to the cloud platform; and based on the current mileage value, the mileage jump risk value and the historical mileage value, determining a target mileage value uploaded to the cloud platform after the vehicle is started this time. The method can avoid jumping of the mileage value uploaded to the cloud platform after the vehicle is started.

Description

Technical Field

[0001] The present application relates to the field of vehicles, and more specifically, to a method, device, vehicle and storage medium for uploading vehicle data in the field of vehicles. Background Art

[0002] The vehicle's mileage value not only needs to be displayed on the vehicle instrument, but also needs to be uploaded to the national regulatory backend through the cloud platform.

[0003] Since the vehicle cannot be driven after being turned off, the mileage value of the vehicle will not change during the process of being turned off. However, due to various reasons, it was found in the test process that after the vehicle was started, the mileage value uploaded to the cloud platform may jump without any actual mileage accumulation.

[0004] Therefore, how to avoid sudden changes in the mileage value uploaded by the vehicle to the cloud platform is a technical problem that needs to be solved at present. Summary of the invention

[0005] The present application provides a vehicle data uploading method, device, vehicle and storage medium. When the method detects a wake-up command from a vehicle host, it determines a target mileage value to be uploaded to a cloud platform based on the vehicle's current mileage value, mileage jump risk value and historical mileage value, thereby avoiding jumps in the mileage value uploaded to the cloud platform.

[0006] In a first aspect, a method for uploading vehicle data is provided, the method comprising:

[0007] In response to a vehicle start command, the current mileage value, the target mileage difference value, and the historical mileage value previously uploaded to the cloud platform of the vehicle are obtained, wherein the target mileage difference value is used to indicate the minimum mileage difference value for updating the mileage uploaded to the cloud platform;

[0008] Based on the target mileage difference and the historical mileage value, determine the mileage jump risk value of the current mileage value, where the mileage jump risk value is used to indicate whether the mileage value on the cloud platform has a jump risk if the current mileage value is uploaded to the cloud platform;

[0009] Based on the current mileage value, mileage jump risk value and historical mileage value, determine the target mileage value that the vehicle will upload to the cloud platform after this startup.

[0010] In an embodiment of the present application, in response to a vehicle startup command, the current mileage value, target mileage difference value and the historical mileage value uploaded to the cloud platform last time are obtained. The mileage jump risk value of the current mileage value is determined, and the target mileage value is determined based on the current mileage value, the historical mileage value and the mileage jump risk value. Since the present application can determine the mileage jump risk value based on the target mileage difference value and the historical mileage value, it is determined whether the mileage value in the cloud platform has a jump risk after uploading the current mileage value to the cloud platform. And based on the current mileage value, the mileage jump risk value and the historical mileage value, the corresponding target mileage value is determined, that is, when the current mileage jump risk value is different, the determined target mileage value is also different. Compared with the prior art in which the real mileage value of the vehicle is uploaded after the vehicle host is awakened, the present solution can determine the uploaded target mileage value based on the current mileage value, the mileage jump risk value and the historical mileage value, instead of directly uploading the current mileage value; therefore, it is possible to avoid the mileage value in the cloud platform from jumping due to the direct upload of the current mileage value.

[0011] In conjunction with the first aspect, in certain implementations of the first aspect, determining the target mileage value based on the current mileage value, the mileage jump risk value, and the historical mileage value includes:

[0012] If the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform and the mileage value on the cloud platform has a jump risk, the historical mileage value is determined as the target mileage value;

[0013] If the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform and there is no jump risk in the mileage value on the cloud platform, the current mileage value is determined as the target mileage value.

[0014] In an embodiment of the present application, when the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform, and there is a risk of a jump in the mileage value on the cloud platform, in order to avoid a jump in the mileage value on the cloud platform, the historical mileage value is determined as the target mileage value. Since the historical mileage value is the mileage value last uploaded to the cloud platform, the historical mileage value is determined as the target mileage value to ensure that the target mileage value uploaded to the cloud platform is consistent with the historical mileage value before the engine is turned off, thereby avoiding a jump in the mileage value uploaded to the cloud platform. If the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform, and there is no risk of a jump in the mileage value on the cloud platform, the current mileage value is determined as the target mileage value to ensure that different target mileage values ​​can be determined when the mileage jump risk values ​​are different, thereby avoiding a jump in the mileage value uploaded to the cloud platform.

[0015] In combination with the first aspect and the above implementations, in some implementations of the first aspect, the following further includes:

[0016] Get the data display format of the target mileage value on the cloud platform;

[0017] Determine a target threshold based on the data display format, where the target threshold is the minimum value that causes the mileage value displayed on the cloud platform to change;

[0018] Based on the target mileage difference and the historical mileage value, the mileage jump risk value of the current mileage value is determined, including:

[0019] Determining a first difference between a target threshold and a target mileage difference;

[0020] Determine a first value of a preset number of digits in the historical mileage value;

[0021] A mileage jump risk value of the current mileage value is determined based on the first difference and the first value.

[0022] In an embodiment of the present application, a target threshold is determined according to the data display format of the target mileage value, and the target threshold is the minimum value that causes the mileage value displayed in the cloud platform to change. The mileage jump risk value of the current mileage value is determined based on the first difference and the first numerical value between the target threshold and the target mileage difference. Since the larger the first numerical value of the preset digits in the historical mileage value, the greater the probability of a mileage jump in the vehicle. Therefore, the first difference between the target threshold and the target mileage difference is determined, and the critical value of the mileage value in the cloud platform that has a jump risk is determined by the first difference, thereby ensuring that the mileage jump risk value of the current mileage value can be determined based on the first difference and the first numerical value.

[0023] In combination with the first aspect and the foregoing implementations, in some implementations of the first aspect, determining the mileage jump risk value of the current mileage value based on the first difference and the first value includes:

[0024] When the first value is greater than the first difference, determining the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform has a jump risk;

[0025] When the first value is less than or equal to the first difference, it is determined that the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, there is no jump risk in the mileage value on the cloud platform.

[0026] In an embodiment of the present application, a first difference between a target threshold and a target mileage difference is determined. The first value and the first difference are compared to determine whether the mileage value uploaded to the cloud platform after the vehicle is started has a risk of jump. Since the larger the first value of the preset digit in the historical mileage value, the greater the probability of a mileage jump in the vehicle, and the first difference is used to indicate the critical value of the mileage value in the cloud platform having a risk of jump. When the first value is greater than the first difference, it indicates that the mileage value of the vehicle has reached the critical value of the risk of jump, that is, when the current mileage value is uploaded to the cloud platform, the mileage value in the cloud platform has a risk of jump. When the first value is less than or equal to the first difference, it indicates that the mileage value of the vehicle has not reached the critical value of the risk of jump, that is, when the current mileage value is uploaded to the cloud platform, the mileage value in the cloud platform does not have a risk of jump. By comparing the first value and the first difference, the mileage jump risk value is determined, ensuring that it is possible to determine whether the mileage value in the cloud platform has a risk of jump based on the first value and the critical value (first difference) of the risk of jump, that is, ensuring that the mileage jump risk value can be obtained.

[0027] In combination with the first aspect and the above implementations, in some implementations of the first aspect, after detecting a wake-up instruction from a vehicle host, the method further includes:

[0028] Perform abnormality detection on the vehicle's onboard system and obtain abnormality detection results;

[0029] Based on the anomaly detection results, the target mileage difference of the vehicle is determined.

[0030] In an embodiment of the present application, an abnormality detection is performed on the vehicle's vehicle-mounted system to obtain an abnormality detection result. The target mileage difference of the vehicle is determined based on the abnormality detection result, that is, when the abnormality detection result of the vehicle-mounted system is different, the target mileage difference of the corresponding vehicle is also different. It is ensured that the target mileage difference of the vehicle can be obtained based on the abnormality detection result of the vehicle-mounted system.

[0031] In combination with the first aspect and the above implementations, in some implementations of the first aspect, determining the target mileage difference of the vehicle based on the abnormality detection result includes:

[0032] If the abnormality detection result indicates that the vehicle's onboard system has an abnormality, determine the abnormality level corresponding to the abnormality;

[0033] Based on the abnormality level, a target mileage difference is determined; wherein the target mileage difference is positively correlated with the abnormality level;

[0034] If the abnormality detection result indicates that there is no abnormality in the vehicle's on-board system, the preset mileage difference is determined as the target mileage difference.

[0035] In an embodiment of the present application, if the abnormality detection result indicates that there is an abnormality in the vehicle-machine system, the target mileage difference is determined according to the abnormality level. If the abnormality detection result indicates that there is no fault in the vehicle-machine system, the preset mileage difference is determined as the target mileage difference. When the target mileage difference is configured to a smaller value, the risk of vehicle mileage jump is smaller, but the performance requirements of the vehicle-machine system (for example, software refresh frequency and memory) are higher. When there is no abnormality in the vehicle-machine system, the preset mileage difference is determined as the target mileage difference to ensure that the refresh frequency of the mileage value uploaded to the cloud platform is high, thereby reducing the probability of jump risk. When there is an abnormality in the vehicle-machine system, the vehicle-machine system cannot update the total mileage uploaded to the cloud platform at a higher update frequency. At this time, the target mileage difference is determined according to the abnormality level. Ensure that the corresponding target mileage difference can be adapted according to the abnormality level.

[0036] In combination with the first aspect and the above implementations, in some implementations of the first aspect, the following further includes:

[0037] During vehicle driving, the target mileage difference of the vehicle is adjusted based on the target parameters of the vehicle computer system, where the target parameters include the software refresh rate, memory and response time of the vehicle computer system.

[0038] In the embodiment of the present application, since the target parameters of the vehicle system may change during the driving of the vehicle, such as the memory, software refresh frequency and response time of the vehicle system, the current vehicle system cannot update the mileage value uploaded to the cloud according to the target mileage difference. Therefore, the target mileage difference of the vehicle is adjusted based on the target parameters of the vehicle system to avoid the vehicle system from getting stuck, thereby avoiding failures in the process of uploading the mileage value to the cloud platform.

[0039] In a second aspect, a vehicle data uploading device is provided, the device comprising:

[0040] an acquisition module, for acquiring the current mileage value, the target mileage difference value and the historical mileage value uploaded to the cloud platform last time of the vehicle in response to the vehicle start command, wherein the target mileage difference value is used to indicate the minimum mileage difference value for updating the mileage uploaded to the cloud platform;

[0041] A first determination module is used to determine a mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value, wherein the mileage jump risk value is used to indicate whether the mileage value on the cloud platform has a jump risk if the current mileage value is uploaded to the cloud platform;

[0042] The second determination module is used to determine the target mileage value that the vehicle uploads to the cloud platform after this startup based on the current mileage value, the mileage jump risk value and the historical mileage value.

[0043] In combination with the second aspect, in certain implementations of the second aspect, the second determination module is specifically used to: determine the historical mileage value as the target mileage value when the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, there is a risk of jump in the mileage value on the cloud platform; determine the current mileage value as the target mileage value when the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, there is no risk of jump in the mileage value on the cloud platform.

[0044] In combination with the second aspect and the above-mentioned implementation methods, in some implementation methods of the second aspect, the acquisition module is also used to: obtain the data display format of the mileage value on the cloud platform; the first determination module is used to: determine the target threshold based on the data display format; wherein the target threshold is the minimum value that causes the mileage value displayed on the cloud platform to change; determine the first difference between the target threshold and the target mileage difference; determine the first numerical value of a preset number of digits in the historical mileage value; and determine the mileage jump risk value of the current mileage value based on the first difference and the first numerical value.

[0045] In combination with the second aspect and the above-mentioned implementation methods, in certain implementation methods of the second aspect, the first determination module is specifically used to: when the first numerical value is greater than the first difference, determine the mileage jump risk value to indicate that if the current mileage value is uploaded to the cloud platform, there is a risk of jump in the mileage value on the cloud platform; when the first numerical value is less than or equal to the first difference, determine the mileage jump risk value to indicate that if the current mileage value is uploaded to the cloud platform, there is no risk of jump in the mileage value on the cloud platform.

[0046] In combination with the second aspect and the above-mentioned implementation methods, in some implementation methods of the second aspect, a detection module and a third determination module are also included. The detection module is used to: perform abnormality detection on the vehicle's vehicle-mounted system to obtain abnormality detection results; the third determination module is used to: determine the vehicle's target mileage difference based on the abnormality detection results.

[0047] In combination with the second aspect and the above-mentioned implementation methods, in some implementation methods of the second aspect, the third determination module is specifically used to: if the abnormality detection result indicates that there is an abnormality in the vehicle's vehicle-computer system, determine the abnormality level corresponding to the abnormality; based on the abnormality level, determine the target mileage difference, wherein the target mileage difference is positively correlated with the abnormality level; if the abnormality detection result indicates that there is no abnormality in the vehicle's vehicle-computer system, determine the preset mileage difference as the target mileage difference.

[0048] In combination with the second aspect and the above-mentioned implementation methods, in some implementation methods of the second aspect, an adjustment module is also included, and the adjustment module is used to: during vehicle driving, adjust the target mileage difference of the vehicle based on the target parameters of the vehicle system, wherein the target parameters include the software refresh rate, memory and response time of the vehicle system.

[0049] In a third aspect, a vehicle is provided, comprising a memory and a processor, wherein the memory is used to store executable program code, and the processor is used to call and run the executable program code from the memory, so that the vehicle executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0050] In a fourth aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the method in the first aspect or any possible implementation of the first aspect.

[0051] In a fifth aspect, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed on a vehicle, the vehicle executes the method in the above-mentioned first aspect or any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 This is a schematic diagram of a scenario provided by an embodiment of the present application;

[0053] Figure 2 This is a data display diagram of a vehicle mileage value provided by an embodiment of the present application;

[0054] Figure 3 is a schematic flow chart of a vehicle data uploading method provided in an embodiment of the present application;

[0055] Figure 4 is a schematic flow chart of another vehicle data uploading method provided in an embodiment of the present application;

[0056] Figure 5 It is a structural diagram of a vehicle data uploading device provided in an embodiment of the present application;

[0057] Figure 6 It is a structural schematic diagram of a vehicle provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The technical solution in the present application will be described clearly and in detail below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B: "and / or" in the text is only a description of the association relationship of 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. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0059] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features.

[0060] At present, the mileage value of a vehicle needs to be displayed not only on the vehicle instrument, but also uploaded to the national regulatory backend through the cloud platform. The mileage displayed on the instrument can be an integer, and the data format uploaded to the cloud platform can have 1 decimal place. Figure 1 As shown in the schematic diagram of the scene, the scene 100 includes a vehicle 110 and a cloud platform 120. During the driving process, the vehicle uploads the mileage value of the vehicle to the cloud platform.

[0061] As described in the background technology section, the mileage value uploaded to the cloud platform may jump. For example, the actual mileage is 3000.5km when the engine is turned off, the instrument shows 3000km, and the value uploaded to the cloud platform is 3000.5km. The process of turning off the engine will not cause the mileage to change. When the vehicle is restarted, the data uploaded to the cloud platform should still be 3000.5km. However, during the test, it was found that the mileage uploaded to the cloud platform after the vehicle was started was 3000.6km. In other words, without any actual mileage accumulation, the mileage value uploaded to the cloud platform changes by 0.1km (=3000.6km-3000.5km). In this application, this phenomenon is called "jump".

[0062] It should be noted that the update strategy of the mileage value uploaded by the vehicle to the cloud platform is usually based on the predetermined mileage change (for example, 10m) as the minimum upload unit. The following will be described as an example of uploading with 10m as the minimum upload unit. It should be understood that 10m is only exemplary and the present application is not limited thereto. For example, the minimum upload unit can also be 20m, 30m or 40m, etc. If the change in the mileage value before the vehicle is turned off (the change represents the difference between the mileage value uploaded to the cloud platform for the last time before the vehicle is turned off and the actual mileage value when the vehicle is turned off) has a part less than 10m, the part of the mileage less than 10m will not be uploaded to the cloud platform, and after the vehicle host is awakened, if the vehicle uploads the current latest mileage value (including the part less than 10m), there may be an interval between the two uploaded data with a distance equal to this part, and this part of the interval may cause the mileage value in the cloud platform to jump, that is, the mileage value displayed in the cloud platform may jump by 0.1km.

[0063] For example, the mileage value uploaded to the cloud platform for the last time before the vehicle is turned off is 195m, and then after driving 7 meters, the actual mileage value of the vehicle is 202m. Since the mileage change from the last upload to the cloud platform is 7m (=202m-195m), which is less than the minimum upload unit of 10m, when the vehicle is turned off, its actual mileage value of 202m will not be uploaded to the cloud platform, and the uploaded mileage value on the cloud platform is still 0.1km (the mileage unit is km, and the data format on the cloud platform is to retain 1 decimal place, so the mileage value of 195m, that is, the mileage value of 0.195km is displayed as 0.1km on the cloud platform). If the wake-up command of the vehicle host is detected again after the vehicle is turned off, the vehicle uploads the current actual mileage value of 202m to the cloud platform, and the uploaded mileage value on the cloud platform will become 0.2km (the mileage unit is km, and the data format on the cloud platform is to retain 1 decimal place, so the mileage value of 202m, that is, the mileage value of 0.202km is displayed as 0.2km on the cloud platform). In this case, even if the vehicle has no accumulated mileage, the mileage value uploaded to the cloud platform will jump from 0.1km to 0.2km.

[0064] It should be noted that after the vehicle uploads the mileage value to the cloud platform, the cloud platform transmits the data to the national supervision background through a secure communication protocol and supervises the vehicle. If the mileage value uploaded to the cloud platform changes without any actual mileage accumulation (that is, the mileage value of the cloud platform jumps), it may lead to failure of supervision and misjudgment of driving behavior, making it impossible to accurately judge the usage and driving mode of the vehicle. For example, during the period from when the vehicle is turned off to when it is restarted, the vehicle is actually stationary (the actual mileage value of the vehicle will not change). If the mileage value of the cloud platform changes, the mileage value in the cloud platform may be misjudged as the vehicle is in driving state.

[0065] Therefore, how to avoid sudden changes in the mileage value uploaded by the vehicle to the cloud platform is a technical problem that needs to be solved at present.

[0066] In view of this, the present application provides a vehicle data uploading method, device, vehicle and storage medium. Through the embodiments of the present application, when a wake-up command of a vehicle host is detected, the target mileage value uploaded to the cloud platform is determined according to the current mileage value, mileage jump risk value and historical mileage value of the vehicle. The mileage value uploaded to the cloud platform is prevented from jumping.

[0067] Figure 2 This is a data display diagram of a vehicle mileage value provided in an embodiment of the present application.

[0068] For example, the vehicle's instrument mileage is usually displayed in kilometers, and the maximum value of the vehicle's instrument mileage is usually 999999km. If converted to meters (m), the maximum value of the vehicle's instrument mileage after conversion is 999999000m. Figure 2 As shown, each box represents a digit, through Figure 2 The boxes in the figure represent the number of digits of the vehicle's instrument mileage after conversion, wherein box 200 represents the vehicle's instrument mileage after converting kilometers to meters, box 210 represents the first 7 digits of the vehicle's instrument mileage after converting kilometers to meters, and box 220 represents the last 2 digits of the vehicle's instrument mileage after converting kilometers to meters.

[0069] For example, if the actual mileage of the vehicle is 100001.898km, if it is expressed in meters, the actual mileage can be expressed as 100001898m, then the value in box 210 is 1000018, and the value in box 220 is 98. Since the vehicle's instrument mileage can be an integer, and the instrument mileage can be in kilometers, the instrument mileage displayed in the vehicle's instrument is 100001km (integer). Since the data format of the mileage uploaded to the cloud platform can have one decimal place, and the mileage value uploaded to the cloud platform can be in kilometers, the mileage value uploaded to the cloud platform is 100001.8km (keep one decimal place, and omit the last two values).

[0070] It should be understood that when the value in box 220 (the last two digits) is larger, if there is a mileage value that has not been uploaded to the cloud platform before the vehicle is turned off, the probability of the mileage jumping by 0.1 km after the vehicle is started is higher.

[0071] For example, if the mileage value that has not been uploaded to the cloud platform before the vehicle is turned off is 3m, when the real mileage value uploaded to the cloud platform for the last time before the vehicle is turned off is 100001898 meters (the mileage unit is km, and the mileage value displayed in the cloud platform retains 1 decimal place, that is, the mileage value displayed in the cloud platform is 100001.8km), the last two digits are 98. When the vehicle is started, the current real mileage value 100001898+3=100001901 is uploaded, so the mileage value after adding the mileage value of 3m that has not been uploaded to the cloud platform is 100001901m (the mileage unit is km, and the mileage value displayed in the cloud platform retains 1 decimal place, and the mileage value displayed in the cloud platform is 100001.9km). It can be seen that when the last two digits are 98, the mileage value uploaded to the cloud platform jumps from 100001.8km to 100001.9km. When the total mileage before shutdown is 100001801m (the mileage unit is km, and the mileage value displayed in the cloud platform retains one decimal place, that is, the mileage value displayed in the cloud platform is 100001.8km), the value of the last two digits is 01. When the vehicle is started, the current real mileage value is uploaded, and the mileage value of 3m that has not been uploaded to the cloud platform is superimposed to 100001804m (the mileage unit is km, and the mileage value displayed in the cloud platform retains one decimal place, that is, the mileage value displayed in the cloud platform is 100001.8km). It can be seen that when the value of the last two digits is 01, the mileage value uploaded to the cloud platform will not jump. Therefore, the larger the value of the last two digits, the greater the possibility of a jump in the mileage value uploaded to the cloud platform.

[0072] The vehicle data uploading method provided in the present application is described in detail below in conjunction with the method flow chart provided in the embodiment of the present application.

[0073] Figure 3 It is a schematic flow chart of a vehicle data uploading method provided in an embodiment of the present application.

[0074] For example, Figure 3 The method 300 shown may be executed by the vehicle, or may be executed by a vehicle system; or may be executed by a processor or chip in the vehicle.

[0075] like Figure 3 As shown, the vehicle data uploading method 300 includes S310 to S330, and S310 to S330 are described in detail below.

[0076] S310, in response to a vehicle start command, obtaining the vehicle's current mileage value, target mileage difference value, and historical mileage value previously uploaded to the cloud platform.

[0077] Exemplarily, the vehicle start command is used to activate the vehicle engine or motor, so that the vehicle changes from a stationary state to a drivable state. The way to trigger the vehicle start command includes but is not limited to: triggering the vehicle start command through a key signal of a remote control key, or triggering the vehicle start command through an ignition switch signal by turning an ignition switch. The present application does not limit the way to trigger the vehicle start command.

[0078] The target mileage difference is used to indicate the minimum mileage difference for updating the mileage uploaded to the cloud platform. For example, if the target mileage difference is 10m, it means that the mileage value of the vehicle is uploaded to the cloud platform every 10m, that is, when the mileage difference of the vehicle is greater than 10m, the mileage value uploaded to the cloud platform is updated.

[0079] The historical mileage value before the vehicle is turned off is used to indicate the mileage value uploaded to the cloud platform for the last time before the vehicle start command is detected, that is, before the vehicle is turned off. The current mileage value of the vehicle is the actual mileage value of the vehicle. For example, the mileage value uploaded to the cloud platform for the last time before the vehicle is turned off is 195m. If the vehicle turns off when the mileage value reaches 202m, when the vehicle is started this time, the historical mileage value before the vehicle is turned off is 195m, and the current mileage value of the vehicle is 202m.

[0080] Exemplarily, the current mileage value of the vehicle can be determined based on the odometer (ODO) data of the vehicle, and the historical mileage value of the vehicle can be determined based on the mileage value uploaded to the cloud platform; this solution does not limit the method for obtaining the current mileage value and the historical mileage value.

[0081] The following describes a method for determining a target mileage difference for a vehicle.

[0082] In one implementation, after detecting a wake-up command from a vehicle host, an abnormality detection is performed on the vehicle's system to obtain an abnormality detection result; based on the abnormality detection result, a target mileage difference of the vehicle is determined.

[0083] Among them, the detection items of abnormal detection are the detection items that affect the uploaded vehicle mileage value. The detection items of abnormal detection include but are not limited to: the vehicle's software refresh frequency, the memory of the vehicle system, the network connection and power supply problems of the vehicle system, etc.

[0084] Further explanation of the above detection items: When the vehicle's software refreshes slowly, it may cause delays in the collection and processing of mileage values, thereby affecting the upload of mileage values. When the vehicle's memory is insufficient, the vehicle system may not operate normally or the mileage value may be lost. When the vehicle system has an abnormal number of network connections, the mileage value may not be uploaded to the cloud in time or the mileage value may be lost. When the vehicle has a power problem, such as a sudden power outage or unstable power supply in the vehicle system, the mileage value may be lost during the mileage upload process.

[0085] It should be noted that when the target mileage difference is small, the performance requirements of the vehicle's on-board system are high (for example, software refresh rate and memory, etc.). When the abnormality detection result of the on-board system indicates that the on-board system has the above-mentioned abnormality, the vehicle cannot update the target mileage value uploaded to the cloud platform at a higher refresh frequency. Therefore, it is necessary to adapt the target mileage difference corresponding to the abnormality level according to the abnormality level of the on-board system (that is, the severity of the abnormality).

[0086] It should be understood that the higher the refresh frequency of the vehicle's target mileage value, the smaller the target mileage difference; for example, if the vehicle travels 100 meters, if the target mileage difference is 10 meters, it means that the target mileage value is refreshed every 10 meters, that is, within 100 meters, the target mileage value may be refreshed 10 times. If the target mileage difference is 20 meters, it means that the target mileage value is refreshed every 20 meters, that is, within 100 meters, the target mileage value may be refreshed 5 times.

[0087] In an embodiment of the present application, an abnormality detection is performed on the vehicle's on-board system to obtain an abnormality detection result. The target mileage difference of the vehicle is determined according to the abnormality detection result, that is, when the abnormality detection result of the on-board system is different, the target mileage difference of the corresponding vehicle is also different, ensuring that the target mileage difference of the vehicle can be obtained according to the abnormality detection result of the on-board system.

[0088] In one implementation, based on the abnormality detection result, a target mileage difference of the vehicle is determined, including: if the abnormality detection result indicates that there is an abnormality in the vehicle's in-vehicle system, determining the abnormality level corresponding to the abnormality; based on the abnormality level, determining the target mileage difference; wherein the target mileage difference and the abnormality level are positively correlated; if the abnormality detection result indicates that there is no abnormality in the vehicle's in-vehicle system, determining a preset mileage difference as the target mileage difference, wherein the preset mileage difference is a unit distance.

[0089] Exemplarily, according to the severity of the abnormality of the vehicle system, the abnormality level is divided into three levels, including level one abnormality (relatively minor abnormality), level two abnormality (relatively serious abnormality) and level three abnormality (serious abnormality). According to the abnormality level indicated by the abnormality detection result, the target mileage difference is determined. The higher the abnormality level, the more serious the abnormality, and the larger the target mileage difference corresponding to the determined abnormality level, so that the vehicle updates the distance value in the cloud platform at a lower refresh frequency, thereby alleviating abnormalities such as stagnation and slow response of the vehicle system.

[0090] For example, when the detection result of the abnormality detection indicates that the abnormality level of the vehicle system is the third level abnormality, the target mileage difference is determined to be 30m (when the mileage change reaches 30m, the current mileage value of the vehicle is uploaded to the cloud platform). If the detection result of the abnormality detection indicates that the abnormality level of the vehicle system is the second level abnormality, the target mileage difference is determined to be 20m (when the mileage change reaches 20m, the current mileage value of the vehicle is uploaded to the cloud platform). If the detection result of the abnormality detection indicates that the abnormality level of the vehicle system is the first level abnormality, the target mileage difference is determined to be 10m (when the mileage change reaches 10m, the current mileage value of the vehicle is uploaded to the cloud platform). If the detection result of the abnormality detection indicates that there is no abnormality in the vehicle system, the target mileage difference is determined to be 1m (when the mileage change reaches 1m, the current mileage value of the vehicle is uploaded to the cloud platform).

[0091] In one implementation, the interval of the target mileage difference is determined according to the abnormality level, and the corresponding target mileage difference is automatically adapted within the interval. For example, when the abnormality level is level one, the corresponding target mileage difference is greater than or equal to 10m and less than 20m. When the abnormality level is level two, the corresponding target mileage difference is greater than or equal to 20m and less than 30m. When the abnormality level is level three, the corresponding target mileage difference is greater than or equal to 30m.

[0092] It should be noted that the above is an example of the correspondence between the abnormal level of the vehicle system and the target mileage difference, and this application does not limit this.

[0093] In an embodiment of the present application, if the abnormality detection result indicates that there is an abnormality in the vehicle-machine system, the target mileage difference is determined according to the abnormality level; if the abnormality detection result indicates that there is no fault in the vehicle-machine system, the preset mileage difference is determined as the target mileage difference. When the target mileage difference is small, the risk of vehicle mileage jump is small, but the requirements for the performance of the vehicle-machine system (including software refresh frequency and memory, etc.) are high; when there is no abnormality in the vehicle-machine system, the unit distance is determined as the target mileage difference to ensure that the refresh frequency of the mileage value uploaded to the cloud platform is high, thereby reducing the probability of jump risk. When there is an abnormality in the vehicle-machine system, the vehicle-machine system cannot update the total mileage uploaded to the cloud platform at a higher refresh frequency. Therefore, the target mileage difference is determined according to the abnormality level of the vehicle-machine system to ensure that the corresponding target mileage difference can be adapted according to the abnormality level of the vehicle-machine system.

[0094] S320, determining a mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value.

[0095] Among them, the mileage jump risk value is used to indicate whether there is a jump risk of the mileage value on the cloud platform if the current mileage value is uploaded to the cloud platform.

[0096] In one implementation, obtaining a data display format of the mileage value on the cloud platform;

[0097] Determine a target threshold based on the data display format; wherein the target threshold is the minimum value that causes the mileage value displayed on the cloud platform to change;

[0098] Determine a first difference between a target threshold and a target mileage difference; determine a first numerical value of a preset digit in the historical mileage value; and determine a mileage jump risk value of the current mileage value based on the first difference and the first numerical value.

[0099] Exemplarily, based on the data display format of the mileage value on the cloud platform, determine the target threshold value for the change in the mileage value displayed on the cloud platform. For example, if the data display format of the target mileage value is 1 decimal place and the unit is km, the minimum value of the change in the mileage value displayed on the cloud platform is 0.1km (converted to m, that is, 100m). It can be seen that when the data display format of the target mileage value is 1 decimal place, the mileage value displayed on the cloud platform will change when the mileage change reaches 100m. If the data display format of the target mileage value is to display two decimal places and the unit is km, the minimum value of the change in the mileage value displayed on the cloud platform is 0.01km (converted to m, that is, 10m). It can be seen that when the data display format of the target mileage value is 2 decimal places, the mileage change reaches 10m, which will cause the mileage value displayed on the cloud platform to change.

[0100] Exemplarily, the first value of the preset digits in the historical mileage value is determined, wherein the first value is a value composed of the digits of the preset digits in the historical mileage value. For example, the actual mileage value corresponding to the historical mileage value uploaded to the cloud platform last time is 1098m (displayed in the cloud platform in km, retaining 1 decimal place, the mileage value displayed in the cloud platform is 1.0km), if the preset digits are the last two digits, the first value is 98. The actual mileage value corresponding to the historical mileage value uploaded to the cloud platform last time is 8960m (displayed in the cloud platform in km, retaining 1 decimal place, the mileage value displayed in the cloud platform is 8.9km), if the preset digits are the last two digits, the first value is 60.

[0101] Optionally, based on the target threshold, the preset number of digits in the historical mileage value is determined, and the preset number of digits is 1 digit less than the number of digits of the target threshold. For example, when the target threshold is 100m, the target threshold is 3 digits, and the determined preset number of digits is the last 2 digits. When the target threshold is 10m, the target threshold is 2 digits, and the determined preset number of digits is the last 1 digit.

[0102] In an embodiment of the present application, a target threshold is determined according to the data display format of the target mileage value, and the target threshold is the minimum value at which the data display of the target mileage value changes. The mileage jump risk value of the current mileage value is determined based on the first difference and the first numerical value between the target threshold and the target mileage difference. Since the larger the first numerical value of the preset digits in the historical mileage value, the greater the probability of a mileage jump in the vehicle. Therefore, the first difference between the target threshold and the target mileage difference is determined, and the critical value of the mileage value in the cloud platform that has a jump risk is determined by the first difference, thereby ensuring that the mileage jump risk value of the current mileage value can be determined based on the first difference and the first numerical value.

[0103] In one implementation, determining the mileage jump risk value of the current mileage value based on the first difference and the first value includes:

[0104] When the first value is greater than the first difference, the mileage jump risk value is determined to indicate that if the current mileage value is uploaded to the cloud platform, there is a risk of jump in the mileage value on the cloud platform; when the first value is less than or equal to the first difference, the mileage jump risk value is determined to indicate that if the current mileage value is uploaded to the cloud platform, there is no risk of jump in the mileage value on the cloud platform.

[0105] For example, if the target mileage difference is 10m and the target threshold is 100m (indicating that when the mileage change reaches 100m, the mileage value displayed in the cloud platform changes), the first difference is determined to be 90m (=100m-90m). Determine the first numerical value of the preset digit in the historical mileage value (for example, the first numerical value is the last 2 digits of the mileage value corresponding to the historical mileage value), and compare the first difference with the first numerical value of the preset digit in the historical mileage value. If there is a mileage value of 5m that has not been uploaded to the cloud platform before the engine is turned off, when the first numerical value is 98, after the vehicle is started, the first numerical value and the mileage value that has not been uploaded to the cloud platform before the engine is turned off are accumulated to reach the target threshold (98m+5m=103m), which will cause the mileage value displayed in the cloud platform to jump, that is, there is a risk of jumping when uploading the current mileage value. When the first numerical value is less than or equal to the first difference, for example, 20m. In this case, even if there is a mileage value that has not been uploaded to the cloud platform before the engine is turned off and it reaches the maximum value (close to 10m), the accumulation of the first value and the mileage value that has not been uploaded to the cloud platform before the engine is turned off will not reach the target threshold. Therefore, the mileage value displayed on the cloud platform will not jump, that is, there is no risk of jump when the vehicle uploads the current mileage value.

[0106] In an embodiment of the present application, a first difference between a target threshold and a target mileage difference is determined; the first value and the first difference are compared to determine whether the mileage value uploaded to the cloud platform after the vehicle is started has a risk of jump. Since the larger the first value of the preset digit in the historical mileage value, the greater the probability of a mileage jump in the vehicle, and the first difference is used to indicate the critical value of the mileage value in the cloud platform having a risk of jump. When the first value is greater than the first difference, it indicates that the mileage value of the vehicle has reached the critical value of the risk of jump, that is, when the current mileage value is uploaded to the cloud platform, the mileage value in the cloud platform has a risk of jump. When the first value is less than the first difference, it indicates that the mileage value of the vehicle has not reached the critical value of the risk of jump, that is, when the current mileage value is uploaded to the cloud platform, the mileage value in the cloud platform does not have a risk of jump. By comparing the first value and the first difference, the mileage jump risk value is determined, ensuring that it is possible to determine whether the mileage value in the cloud platform has a risk of jump based on the first value and the critical value (first difference) of the risk of jump, that is, ensuring that the mileage jump risk value can be obtained.

[0107] It should be noted that if the first value is greater than the first difference, it means that the mileage value uploaded by the vehicle may jump, which does not mean that the mileage in the cloud platform will definitely jump after the vehicle uploads the current mileage value to the cloud platform. For example, when the first value is 95, and the mileage value not uploaded to the cloud platform before the engine is turned off (that is, the mileage value updated before the engine is turned off but not uploaded) is 7m, the first value and the mileage value not uploaded to the cloud platform will reach the target threshold (95+7>100) after accumulation, which will cause the mileage value in the cloud platform to change. That is, when the vehicle is started, if the current mileage value is uploaded to the cloud platform, the mileage value in the cloud platform will jump. If the value updated before the engine is turned off but not uploaded is 3m, the first value and the mileage value not uploaded to the cloud platform will not reach the target threshold (95+3<100) after accumulation, which will not cause the mileage value in the cloud platform to change. That is, when the vehicle is started, if the current mileage value is uploaded to the cloud platform, the mileage value in the cloud platform will not jump. Therefore, the above-mentioned jump risk is used to indicate the possibility that the mileage value on the cloud platform will jump if the current mileage value is uploaded to the cloud platform. If the current mileage value is uploaded to the cloud platform, there is a possibility that the mileage value on the cloud platform will jump, then it is determined that there is a jump risk. If the current mileage value is uploaded to the cloud platform, there is no possibility that the mileage value on the cloud platform will jump, then it is determined that there is no jump risk.

[0108] Optionally, obtain the historical mileage value uploaded to the cloud platform for the last time before the vehicle is turned off, and the first mileage value updated before the vehicle is turned off but not uploaded to the cloud platform; determine the first numerical value of the preset digits of the historical mileage value, sum the first numerical value and the first mileage value to obtain the sum value. Compare the sum value with the target threshold value, if the sum value is greater than the target threshold value, determine that the mileage jump risk value indicates that the current mileage value has a jump risk; if the sum value is less than the target threshold value, determine that the mileage jump risk value indicates that the current mileage value does not have a jump risk.

[0109] Exemplarily, the first numerical value of the preset digits in the historical mileage value and the first mileage value are summed to obtain the sum value, and the sum value is compared with the target threshold value to determine whether the sum value will cause the mileage of the vehicle to change. Since the target threshold value is the minimum value that causes the mileage value in the cloud platform to change, if the sum value is greater than the target threshold value, it means that after the first numerical value is superimposed on the first mileage value, the mileage value displayed in the cloud platform will change. Therefore, there is a difference between the current mileage value uploaded after the vehicle is started and the historical mileage value uploaded last time displayed in the cloud platform, that is, after the vehicle is started, when the current mileage value is uploaded to the cloud platform, there is a risk of a jump in the mileage value in the cloud platform. If the sum value is less than or equal to the target threshold value, it means that after the first numerical value is superimposed on the first mileage value, the mileage value displayed in the cloud platform will not change. Therefore, the current mileage value uploaded after the vehicle is started and the historical mileage value uploaded last time displayed in the cloud platform are the same mileage value, that is, after the vehicle is started, when the current mileage value is uploaded to the cloud platform, there is no risk of a jump in the mileage value in the cloud platform.

[0110] For example, if the last historical mileage value uploaded before shutdown is 100001898m (displayed on the cloud platform in km, and retaining 1 decimal place, that is, 100001.8km). According to the historical mileage value, the first numerical value is determined to be 98, and the target threshold is 100. If the first mileage value that has not been uploaded to the cloud platform before shutdown is 3m, the first numerical value and the first mileage value are summed to obtain a sum of 101 (=98+3), and the sum is greater than the target threshold. Then, it is determined whether the mileage value on the cloud platform has a risk of jumping if the current mileage value is uploaded to the cloud platform after the vehicle is started. It can be seen that by comparing the sum and the target threshold, it is possible to accurately determine whether the mileage value uploaded to the cloud platform has a risk of jumping.

[0111] S330, based on the current mileage value, the mileage jump risk value and the historical mileage value, determine the target mileage value that the vehicle uploads to the cloud platform after this startup.

[0112] In one implementation, based on the current mileage value, the mileage jump risk value and the historical mileage value, a target mileage value to be uploaded to the cloud platform after the vehicle is started is determined, including:

[0113] If the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform and there is a risk of jump in the mileage value on the cloud platform, the historical mileage value will be determined as the target mileage value; if the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform and there is no risk of jump in the mileage value on the cloud platform, the current mileage value will be determined as the target mileage value.

[0114] Exemplarily, when the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform, and there is a risk of a jump in the mileage value on the cloud platform, in order to avoid a jump in the mileage value on the cloud platform, the historical mileage value is determined as the target mileage value. Since the historical mileage value is the total mileage before the vehicle is turned off, the historical mileage value is determined as the target mileage value to ensure that the target mileage value uploaded to the cloud platform is consistent with the historical mileage value before the vehicle is turned off, thereby avoiding a jump in the total mileage of the vehicle. If the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform, and there is no risk of a jump in the mileage value on the cloud platform, the current mileage value is determined as the target mileage value to ensure that the corresponding target mileage value can be determined when the mileage jump risk value is different, so as to avoid a jump in the mileage value uploaded to the cloud platform.

[0115] In a possible implementation, the target mileage difference is determined according to the abnormality level of the vehicle system, and the uploaded target mileage value is determined according to the target mileage difference and the first value of the last two digits of the historical mileage value.

[0116] For example, when the abnormality level is level 1, the corresponding target mileage difference is greater than or equal to 10m and less than 20m. When the abnormality level is level 2, the corresponding target mileage difference is greater than or equal to 20m and less than 30m. When the abnormality level is level 3, the corresponding target mileage difference is greater than or equal to 30m.

[0117] Taking the abnormality level of level one as an example for detailed explanation, when the abnormality level is level one, the target mileage difference is greater than or equal to 10m and less than 20m; when the first value is greater than 80 and less than or equal to 99, it is prohibited to send the current mileage value after the vehicle is started, but the historical mileage value before shutdown is sent; when the first value is less than 80, the current mileage value is sent directly after the vehicle is started.

[0118] Since the target mileage difference is 10m, 10 meters is the lower limit critical value for upload. When the last two digits of the historical mileage value exceed 90 meters, there is a risk of jumping more than 100 meters (ie 0.1km). Therefore, 90 meters needs to be determined as the minimum limit. If the last two digits of the historical mileage value are between 90 and 99, it is necessary to prohibit uploading the current mileage value after the vehicle is started, otherwise the value of the current mileage value after uploading is different from the historical mileage value on the cloud platform. Since the target mileage difference is 20m, 20 meters is the lower limit critical value for upload. When the last two digits of the historical mileage value exceed 80 meters, there is a risk of jumping more than 100 meters (ie 0.1km). Therefore, 80 meters needs to be determined as the second limit. Through two critical values, the minimum critical value of 80 with a risk of jumping is determined. When the last two digits of the historical mileage value are less than or equal to the minimum critical value, it means that after uploading the current mileage value, the mileage value displayed in the cloud platform will not change, that is, there is no risk of jumping in the mileage value in the cloud platform. When the last two digits of the historical mileage value are greater than the minimum critical value, it means that uploading the current mileage value will cause the mileage value displayed on the cloud platform to change, that is, there is a risk of a jump in the mileage value on the cloud platform.

[0119] It should be understood that when the first value is between 80 and 90, there may be a risk of jump or there may not be a risk of jump. However, after the vehicle is started, if it is necessary to calculate the sum of the difference between the first value and the target mileage separately to determine whether there is a risk of jump, it may increase the time for the vehicle system to upload the mileage value to the cloud platform, resulting in delay. Therefore, in order to avoid delays in uploading mileage values, the historical mileage value before the engine is turned off is directly sent.

[0120] It should be noted that the above is a detailed description of determining the target mileage value when the abnormality level is level 1. When the abnormality level is level 2 or level 3, please refer to the above description and will not be repeated here.

[0121] In one possible implementation, after uploading the target mileage value to the cloud platform, the current mileage value of the vehicle is obtained in real time; when the change in the current mileage value reaches the target mileage difference, the target mileage value is updated based on the current mileage value.

[0122] For example, the target mileage difference is 10m, and the target mileage value is 195m. After the vehicle uploads the target mileage value to the cloud platform, the current mileage value of the vehicle is obtained in real time. When the change in the current mileage value reaches the target mileage difference, the uploaded target mileage value is updated. For example, when the current mileage value of the vehicle is 205m, the target mileage value is updated and the target mileage value of 205m is uploaded. When the current mileage value of the vehicle is 215m, the target mileage value is updated again and the target mileage value of 215m is uploaded.

[0123] In the embodiment of the present application, the current mileage value of the vehicle is obtained in real time, and the target mileage value is updated when the change in the current mileage reaches the target mileage difference. It is ensured that after uploading the target mileage value to the cloud platform, the target mileage value uploaded to the cloud platform is updated in a timely manner according to the change in the current mileage value.

[0124] In one implementation, it also includes: during vehicle driving, adjusting the target mileage difference of the vehicle based on the target parameters of the vehicle system, wherein the target parameters include the software refresh rate, memory and response time of the vehicle system.

[0125] For example, if the current target mileage difference is 10, when the vehicle system is detected to be stuck based on the target parameters of the vehicle system (including the software refresh frequency, memory and response time of the vehicle system, etc.), the target mileage difference is adjusted to a larger mileage difference, such as 30. By adjusting the mileage value in the cloud platform to be updated every 30 meters instead of every 10 meters, the stuck of the vehicle system can be alleviated.

[0126] It should be noted that the above is an example of the target mileage difference; this application does not limit this.

[0127] In the embodiment of the present application, since the target parameters of the vehicle system may change during the driving process of the vehicle, such as the memory, software refresh frequency and response time of the vehicle system, the current vehicle system cannot update the mileage value uploaded to the cloud according to the current target mileage difference. Therefore, the target mileage difference of the vehicle is adjusted based on the target parameters of the vehicle system to avoid the vehicle system from getting stuck, thereby avoiding failures in the process of uploading mileage values ​​to the cloud platform.

[0128] In the above embodiment, in response to the vehicle's start-up command, the vehicle's current mileage value, target mileage difference value, and the historical mileage value last uploaded to the cloud platform are obtained. The mileage jump risk value of the current mileage value is determined, and the target mileage value is determined based on the current mileage value, the historical mileage value, and the mileage jump risk value. Since the present application can determine the mileage jump risk value based on the target mileage difference value and the historical mileage value, it is determined whether the mileage value in the cloud platform has a jump risk after uploading the current mileage value to the cloud platform. And based on the current mileage value, the mileage jump risk value, and the historical mileage value, the corresponding target mileage value is determined, that is, when the current mileage jump risk value is different, the determined target mileage value is also different. Compared with the prior art in which the vehicle host uploads the real mileage value of the vehicle after waking up, the present solution can determine the uploaded target mileage value based on the current mileage value, the mileage jump risk value, and the historical mileage value, instead of directly uploading the current mileage value; therefore, it can avoid the mileage value in the cloud platform from jumping due to the direct upload of the current mileage value.

[0129] Figure 4 It is a schematic flowchart of another vehicle data uploading method provided in an embodiment of the present application.

[0130] Figure 4 The method 400 shown may be executed by the vehicle, or may be executed by a vehicle system; or may be executed by a processor or chip in the vehicle.

[0131] like Figure 4 As shown, the vehicle data uploading method 400 includes S401 to S413, and S401 to S413 are described in detail below.

[0132] S401, in response to a vehicle startup instruction, performing abnormality detection on a vehicle computer system.

[0133] Exemplarily, the vehicle start command is used to activate the vehicle engine or motor, so that the vehicle changes from a stationary state to a drivable state. The way to trigger the vehicle start command includes but is not limited to: triggering the vehicle start command through a key signal of a remote control key, or triggering the vehicle start command through an ignition switch signal by turning an ignition switch. In response to the vehicle start command, the vehicle host is awakened, and the vehicle system is detected for abnormalities.

[0134] Exemplarily, when performing abnormality detection on the vehicle system, the detection items of the abnormality detection are detection items that affect the uploaded vehicle mileage value, and the detection items include but are not limited to: the vehicle's software refresh frequency, the vehicle system's memory, the vehicle system's network connection, power supply problems, etc.

[0135] S402, determining a target mileage difference of the vehicle based on the detection result of the abnormality detection.

[0136] Exemplarily, if the detection result indicates that the vehicle's vehicle-mounted system has an abnormality, the abnormality level corresponding to the abnormality is determined. According to the abnormality level, the target mileage difference is determined, wherein the target mileage difference is positively correlated with the abnormality level, that is, the higher the abnormality level of the vehicle-mounted system, the larger the determined target mileage difference. If the abnormality detection result indicates that the vehicle's vehicle-mounted system has no abnormality, the preset mileage difference is determined as the target mileage difference, wherein the preset mileage difference is a unit distance.

[0137] Optionally, the implementation of S401 and S402 can refer to Figure 3 The relevant description of S310 is not repeated here.

[0138] S403, obtaining the current mileage value of the vehicle and the historical mileage value previously uploaded to the cloud platform.

[0139] For example, the current mileage value of the vehicle is the actual mileage value of the vehicle. The historical mileage value is the mileage value of the vehicle last uploaded to the cloud platform, that is, the mileage value last uploaded to the cloud platform before the vehicle was turned off.

[0140] Optionally, the implementation of S403 can refer to Figure 3 The relevant description in S301 will not be repeated here.

[0141] S404, determining a target threshold based on the data display format of the mileage value on the cloud platform.

[0142] Exemplarily, based on the data display format of the mileage value on the cloud platform, the target threshold value that causes the mileage value displayed on the cloud platform to change is determined; for example, if the data display format of the target mileage value is 1 decimal place and the unit is km, the minimum value for the target mileage value data to change is 0.1km, that is, the target threshold value is 100m. If the data display format of the target mileage value is to display 2 decimal places and the unit is km, the minimum value for the target mileage value data to change is 0.01km, that is, the target threshold value is 10m.

[0143] S405, determining a first difference between the target threshold and the target mileage difference.

[0144] The first difference is used to indicate a critical value at which the mileage value uploaded to the cloud platform has a risk of jumping.

[0145] S406, determining a first value of a preset number of digits in the historical mileage value.

[0146] Exemplarily, a first value of a preset number of digits in the historical mileage value is determined, wherein the first value is a value composed of digits of the preset number of digits in the historical mileage value. For example, the preset number of digits is the last two digits; when the historical mileage value is 1098m, the first value is 98m. When the historical mileage value is 8960m, the first value is 60m.

[0147] Optionally, the implementation of S403 to S406 can refer to Figure 3 The implementation method of S320 in FIG. 1 is not described in detail here.

[0148] S407, whether the first value is greater than the first difference; if so, execute S408; if not, execute S410.

[0149] For example, since the larger the first value of the preset digits in the historical mileage value is, the greater the probability of the vehicle's mileage jumping, and the first difference is used to indicate the critical value of the vehicle's mileage value indicating the risk of jumping. Therefore, by comparing the first value and the first difference, it is possible to accurately determine whether the mileage value in the cloud platform has a risk of jumping after uploading the current mileage value to the cloud platform.

[0150] S408: If the current mileage value is uploaded to the cloud platform, there is a risk of a jump in the mileage value on the cloud platform.

[0151] Exemplarily, when the first numerical value is greater than the first difference, it indicates that the mileage value displayed on the cloud platform has reached a critical value at which there is a risk of a jump, that is, if the current mileage value is uploaded to the cloud platform, there is a risk of a jump in the mileage value on the cloud platform.

[0152] S409: Determine the historical mileage value as the target mileage value.

[0153] For example, when the current mileage value is uploaded to the cloud platform and there is a risk of a jump in the mileage value on the cloud platform, the historical mileage value is determined as the target mileage value to ensure that the target mileage value uploaded to the cloud platform is consistent with the historical mileage value uploaded before shutdown, thereby avoiding a jump in the mileage value displayed on the cloud platform.

[0154] S410, if the current mileage value is uploaded to the cloud platform, there is no risk of jump in the mileage value on the cloud platform.

[0155] Exemplarily, when the first numerical value is less than or equal to the first difference, it indicates that the mileage value displayed on the cloud platform has not reached the critical value for which there is a risk of a jump, that is, if the current mileage value is uploaded to the cloud platform, there is no risk of a jump in the total mileage on the cloud platform.

[0156] S411, determining the current mileage value as the target mileage value.

[0157] Optionally, the implementation of S408 to S411 can refer to Figure 3 The implementation method of S330 will not be repeated here.

[0158] S412, upload the target mileage value to the cloud platform.

[0159] S413, when the change in the current mileage value of the vehicle reaches the target mileage difference, the target mileage value is updated.

[0160] For example, after uploading the target mileage value to the cloud platform, the current mileage value of the vehicle is obtained in real time. When the change in the current mileage value reaches the target mileage difference, the target mileage value is updated based on the current mileage value. Ensure that the target mileage value uploaded to the cloud platform can be updated in time when the current mileage value of the vehicle changes.

[0161] In the embodiment of the present application, by comparing the first value and the first difference, it is determined whether the mileage value on the cloud platform has a risk of mileage jump when uploading the current mileage value to the cloud platform. If the mileage value on the cloud platform has a risk of mileage jump, the historical mileage value uploaded to the cloud platform last time is determined as the target mileage value, thereby avoiding the inconsistency between the mileage value on the cloud platform before the vehicle starts and the mileage value on the cloud platform after the vehicle starts, thereby avoiding the mileage value on the cloud platform from jumping.

[0162] Combination of the above Figures 1 to 4 The vehicle data uploading method provided by the embodiment of the present application is described in detail; Figure 5 and Figure 6 The device embodiments of the present application are described in detail. It should be understood that the device in the embodiments of the present application can execute the various methods of the aforementioned embodiments of the present application, that is, the specific working processes of the following various products can refer to the corresponding processes in the aforementioned method embodiments.

[0163] Figure 5 It is a structural diagram of a vehicle data uploading device provided in an embodiment of the present application.

[0164] For example, Figure 5 As shown, the vehicle data uploading device 500 includes:

[0165] An acquisition module 510 is used to obtain the current mileage value, the target mileage difference value and the historical mileage value uploaded to the cloud platform last time of the vehicle in response to the vehicle start command, wherein the target mileage difference value is used to indicate the minimum mileage difference value for updating the mileage uploaded to the cloud platform;

[0166] A first determination module 520 is used to determine a mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value, wherein the mileage jump risk value is used to indicate whether the mileage value on the cloud platform has a jump risk if the current mileage value is uploaded to the cloud platform;

[0167] The second determination module 530 is used to determine the target mileage value that the vehicle uploads to the cloud platform after this startup based on the current mileage value, the mileage jump risk value and the historical mileage value.

[0168] Optionally, as an embodiment, the second determination module 530 is specifically configured to: determine the historical mileage value as the target mileage value when the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform has a jump risk;

[0169] If the mileage jump risk value indicates that the current mileage value is uploaded to the cloud platform and there is no jump risk in the mileage value on the cloud platform, the current mileage value is determined as the target mileage value.

[0170] Optionally, as an embodiment, the acquisition module 510 is also used to: obtain the data display format of the mileage value on the cloud platform; the first determination module 520 is used to: determine the target threshold based on the data display format, wherein the target threshold is the minimum value that causes the mileage value displayed on the cloud platform to change; determine the first difference between the target threshold and the target mileage difference; determine the first numerical value of a preset number of digits in the historical mileage value; and determine the mileage jump risk value of the current mileage value based on the first difference and the first numerical value.

[0171] Optionally, as an embodiment, the first determination module 520 is specifically used to: when the first numerical value is greater than the first difference, determine the mileage jump risk value of the current mileage value to indicate that if the vehicle uploads the current mileage value to the cloud platform, there is a risk of a jump in the mileage value on the cloud platform; when the first numerical value is less than or equal to the first difference, determine the mileage jump risk value to indicate that if the current mileage value is uploaded to the cloud platform, there is no risk of a jump in the mileage value on the cloud platform.

[0172] Optionally, as an embodiment, it also includes a detection module and a third determination module, the detection module is used to: perform abnormality detection on the vehicle's on-board system to obtain abnormality detection results; the third determination module is used to: determine the vehicle's target mileage difference based on the abnormality detection results.

[0173] Optionally, as an embodiment, the third determination module is specifically used to: if the abnormality detection result indicates that there is an abnormality in the vehicle's vehicle-mounted system, determine the abnormality level corresponding to the abnormality; based on the abnormality level, determine the target mileage difference, wherein the target mileage difference is positively correlated with the abnormality level; if the abnormality detection result indicates that there is no abnormality in the vehicle's vehicle-mounted system, determine the preset mileage difference as the target mileage difference.

[0174] Optionally, as an embodiment, it also includes an adjustment module, which is used to: during vehicle driving, adjust the target mileage difference of the vehicle based on the target parameters of the vehicle system, wherein the target parameters include the software refresh rate, memory and response time of the vehicle system.

[0175] It should be noted that the above-mentioned vehicle data uploading device is embodied in the form of a functional unit. The term "module" here can be implemented in the form of software and / or hardware, and is not specifically limited to this.

[0176] For example, a "module" may be a software program, a hardware circuit, or a combination of the two that implements the above functions. The hardware circuit may include an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor, or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit, and / or other suitable components that support the described functions.

[0177] Therefore, the units of each example described in the embodiments of the present application can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

[0178] Figure 6 It is a structural schematic diagram of a vehicle provided in an embodiment of the present application.

[0179] Exemplarily, vehicle 600 includes: a processor 610 , a memory 620 , and executable program code 630 .

[0180] Exemplarily, the vehicle 600 includes one or more processors 610, which can support the vehicle 600 to implement the vehicle data uploading method in the method embodiment. The processor 610 can be a general-purpose processor or a special-purpose processor. For example, the processor 610 can be a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, such as discrete gates, transistor logic devices, or discrete hardware components.

[0181] Exemplarily, the processor 610 may be used to control the vehicle 600, execute software programs, and process data of the software programs. The vehicle 600 may also include a communication unit to implement input (reception) and output (transmission) of signals.

[0182] Exemplarily, the vehicle 600 may include one or more memories 620 on which executable program code 630 is stored. The executable program code 630 can be executed by the processor 610 to generate instructions so that the processor 610 executes the vehicle data uploading method described in the above method embodiment according to the instructions.

[0183] Optionally, data may be stored in the memory 620. Optionally, the processor 610 may read data stored in the memory 620, which may be stored at the same storage address as the executable program code 630, or may be stored at a different storage address from the executable program code 630.

[0184] Exemplarily, the processor 610 and the memory 620 may be provided separately or integrated together, for example, integrated on a system on chip (SOC) of the terminal device.

[0185] Exemplarily, the memory 620 can be used to store relevant programs of the vehicle data uploading method provided in the embodiment of the present application, and the processor 620 can be used to call the executable program code 630 stored in the memory 620 when controlling the vehicle to execute the vehicle data uploading method of the embodiment of the present application; for example, in response to the vehicle startup command, the current mileage value, target mileage difference value and historical mileage value last uploaded to the cloud platform of the vehicle are obtained, wherein the target mileage difference value is used to represent the minimum mileage difference value for updating the mileage uploaded to the cloud platform; based on the target mileage difference value and the historical mileage value, the mileage jump risk value of the current mileage value is determined, wherein the mileage jump risk value is used to indicate whether there is a jump risk of the mileage value on the cloud platform if the current mileage value is uploaded to the cloud platform; based on the current mileage value, the mileage jump risk value and the historical mileage value, the target mileage value uploaded by the vehicle to the cloud platform after this startup is determined.

[0186] The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the vehicle data uploading method of any of the aforementioned embodiments.

[0187] Among them, computer-readable storage media may include but are not limited to any type of disk, including floppy disks, optical disks, digital versatile disks (Digital Video Disc, DVD), compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), microdrives and magneto-optical disks, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read only memory (Electrically Erasable Programmable read only memory, EEPROM), dynamic random access memory (Dynamic Random Access Memory, DRAM), video random access memory (Video Random Access Memory, VRAM), flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.

[0188] The present application also provides a computer program product. When the computer program product runs on a computer, the computer executes the above-mentioned related steps to implement a vehicle data uploading method in the above-mentioned embodiment.

[0189] In addition, the vehicle provided in the embodiments of the present application may specifically be a chip, component or module, and the vehicle may include a connected processor and memory; wherein the memory is used to store instructions, and when the vehicle is running, the processor may call and execute instructions so that the chip executes a vehicle data uploading method in the above-mentioned embodiments.

[0190] Among them, the vehicle, computer-readable storage medium, computer program product or chip provided in this application are all used to execute the corresponding vehicle data uploading method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding vehicle data uploading method provided above, and will not be repeated here.

[0191] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

[0193] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A vehicle data uploading method, characterized in that: The method comprises: In response to a vehicle start command, obtaining a current mileage value, a target mileage difference value, and a historical mileage value previously uploaded to a cloud platform of the vehicle, wherein the target mileage difference value is used to represent a minimum mileage difference value for updating the mileage uploaded to the cloud platform; Determine a mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value, wherein the mileage jump risk value is used to indicate whether there is a risk of a jump in the mileage value on the cloud platform if the current mileage value is uploaded to the cloud platform; Based on the current mileage value, the mileage jump risk value and the historical mileage value, a target mileage value of the vehicle to be uploaded to the cloud platform after this startup is determined.

2. The method according to claim 1, characterized in that The determining, based on the current mileage value, the mileage jump risk value and the historical mileage value, a target mileage value to be uploaded by the vehicle to the cloud platform after the current startup includes: If the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform and the mileage value on the cloud platform has the jump risk, the historical mileage value is determined as the target mileage value; If the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform and the mileage value on the cloud platform does not have the jump risk, the current mileage value is determined as the target mileage value.

3. The method according to claim 1, characterized in that: Also includes: Obtain the data display format of the mileage value on the cloud platform; Determining a target threshold based on the data display format, wherein the target threshold is a minimum value that causes a change in the mileage value displayed on the cloud platform; The determining the mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value includes: Determining a first difference between the target threshold and the target mileage difference; Determine a first value of a preset number of digits in the historical mileage value; A mileage jump risk value of the current mileage value is determined based on the first difference and the first value.

4. The method according to claim 3, characterized in that: The determining, based on the first difference and the first value, the mileage jump risk value of the current mileage value includes: When the first value is greater than the first difference, determining the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform has the jump risk; When the first value is less than or equal to the first difference, determining the mileage jump risk value indicates that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform does not have the jump risk.

5. The method according to any one of claims 1 to 4, characterized in that Also includes: Performing an abnormality detection on the vehicle computer system of the vehicle to obtain an abnormality detection result; Based on the abnormality detection result, a target mileage difference of the vehicle is determined.

6. The method according to claim 5, characterized in that The determining the target mileage difference of the vehicle based on the abnormality detection result includes: If the abnormality detection result indicates that the vehicle system has an abnormality, determining an abnormality level corresponding to the abnormality; Based on the abnormality level, determining the target mileage difference, wherein the target mileage difference is positively correlated with the abnormality level; If the abnormality detection result indicates that there is no abnormality in the vehicle computer system of the vehicle, the preset mileage difference is determined as the target mileage difference.

7. The method according to any one of claims 1 to 4, characterized in that Also includes: During the driving of the vehicle, the target mileage difference of the vehicle is adjusted based on the target parameters of the vehicle system, wherein the target parameters include the software refresh rate, memory and response time of the vehicle system.

8. A vehicle data uploading device, characterized in that: The device comprises: an acquisition module, configured to acquire, in response to a vehicle startup instruction, a current mileage value, a target mileage difference value, and a historical mileage value previously uploaded to the cloud platform of the vehicle, wherein the target mileage difference value is used to represent a minimum mileage difference value for updating the mileage uploaded to the cloud platform; A first determination module is used to determine a mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value, wherein the mileage jump risk value is used to indicate whether there is a risk of a jump in the mileage value on the cloud platform if the current mileage value is uploaded to the cloud platform; The second determination module is used to determine the target mileage value uploaded by the vehicle to the cloud platform after this startup based on the current mileage value, the mileage jump risk value and the historical mileage value.

9. A vehicle, characterized in that: The vehicle comprises: A memory for storing executable program codes; A processor is used to call and run the executable program code from the memory so that the vehicle executes the method as claimed in any one of claims 1 to 7.

10. A computer storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a vehicle, the vehicle is caused to perform the method according to any one of claims 1 to 7.

Images