Vehicle data uploading methods, devices, vehicles, and storage media

Abstract

This application provides a vehicle data uploading method, apparatus, vehicle, and storage medium. The method includes: in response to a vehicle start command, acquiring the vehicle's current mileage, a target mileage difference, and historical mileage previously uploaded to a cloud platform, wherein the target mileage difference represents the minimum mileage difference required to update the mileage uploaded to the cloud platform; determining a mileage jump risk value for the current mileage based on the target mileage difference and the historical mileage, wherein the mileage jump risk value indicates whether there is a risk of mileage jump on the cloud platform if the current mileage is uploaded; and determining the target mileage value to be uploaded to the cloud platform by the vehicle after this start based on the current mileage, the mileage jump risk value, and the historical mileage. This method can prevent mileage jumps from occurring after the vehicle starts up and the mileage uploaded to the cloud platform changes.

Description

Technical Field

[0001] This application relates to the field of vehicles, and more specifically, to a method, apparatus, vehicle, and storage medium for uploading vehicle data in the field of vehicles. Background Technology

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

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

[0004] Therefore, how to prevent the mileage values ​​uploaded by vehicles to the cloud platform from changing abruptly is a technical problem that needs to be solved. Summary of the Invention

[0005] This application provides a vehicle data uploading method, device, vehicle, and storage medium. When the wake-up command of the vehicle host is detected, the method determines the target mileage value to be uploaded to the cloud platform based on the vehicle's current mileage value, mileage jump risk value, and historical mileage value, thereby avoiding mileage jumps when uploaded to the cloud platform.

[0006] Firstly, a method for uploading vehicle data is provided, the method comprising:

[0007] In response to the vehicle's start command, the system obtains the vehicle's current mileage, target mileage difference, and historical mileage previously uploaded to the cloud platform. The target mileage difference represents the minimum mileage difference required to update the mileage uploaded to the cloud platform.

[0008] Based on the target mileage difference and historical mileage values, the mileage jump risk value of the current mileage value is determined. The mileage jump risk value is used to indicate whether there is a risk of mileage jump on the cloud platform 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 the embodiments of this application, in response to a vehicle start command, the vehicle's current mileage, target mileage difference, and historical mileage last uploaded to the cloud platform are obtained. A mileage jump risk value for the current mileage is determined, and a target mileage is determined based on the current mileage, historical mileage, and mileage jump risk value. Because this application can determine the mileage jump risk value based on the target mileage difference and historical mileage, it can determine whether there is a mileage jump risk in the cloud platform after the current mileage is uploaded. Furthermore, based on the current mileage, mileage jump risk value, and historical mileage, a corresponding target mileage is determined; that is, the determined target mileage is different when the current mileage jump risk value is different. Compared to the prior art where the vehicle's host uploads the vehicle's actual mileage after wake-up, this solution can determine the target mileage based on the current mileage, mileage jump risk value, and historical mileage, instead of directly uploading the current mileage; therefore, it can avoid mileage jumps in the cloud platform caused by directly uploading the current mileage.

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

[0012] If the mileage jump risk value indicates that uploading the current mileage value to the cloud platform poses a risk of mileage jump, the historical mileage value will be 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 risk of mileage jump on the cloud platform, then the current mileage value will be determined as the target mileage value.

[0014] In the embodiments of this application, when the mileage jump risk value indicates that the current mileage value should be uploaded to the cloud platform, and the mileage value on the cloud platform is at risk of jumping, a historical mileage value is determined as the target mileage value to avoid the mileage value on the cloud platform jumping. Since the historical mileage value is the mileage value previously uploaded to the cloud platform, determining the historical mileage value as the target mileage value ensures that the target mileage value uploaded to the cloud platform is consistent with the historical mileage value before the engine was turned off, thereby avoiding the mileage value uploaded to the cloud platform jumping. If the mileage jump risk value indicates that the current mileage value should be uploaded to the cloud platform, and the mileage value on the cloud platform is not at risk of jumping, the current mileage value is determined as the target mileage value, ensuring that different target mileage values ​​can be determined when the mileage jump risk value is different, thereby avoiding the mileage value uploaded to the cloud platform jumping.

[0015] In conjunction with the first aspect and the above implementation methods, some implementation methods of the first aspect also include:

[0016] Obtain the data display format for the target mileage value on the cloud platform;

[0017] Based on the data display format, a target threshold is determined, 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 historical mileage values, determine the mileage jump risk value for the current mileage value, including:

[0019] Determine the first difference between the target threshold and the target mileage;

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

[0021] Based on the first difference and the first value, determine the mileage jump risk value of the current mileage value.

[0022] In the embodiments of this application, a target threshold is determined according to the data display format of the target mileage value. The target threshold is the minimum value that would cause the mileage value displayed on the cloud platform to change. A mileage jump risk value for the current mileage value is determined based on a first difference between the target threshold and the target mileage difference, and a first numerical value. Since a larger first numerical value with a preset number of digits in the historical mileage values ​​indicates a higher probability of mileage jumps, a first difference between the target threshold and the target mileage difference is determined. This first difference is used to determine the critical value at which the mileage value on the cloud platform has a jump risk, thereby ensuring that the mileage jump risk value for the current mileage value can be determined based on the first difference and the first numerical value.

[0023] Combining the first aspect and the above implementation methods, in some implementation methods of the first aspect, the mileage jump risk value of the current mileage value is determined based on the first difference and the first value, including:

[0024] When the first value is greater than the first difference, a mileage jump risk value is determined, indicating that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform is at risk of jumping.

[0025] 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, the mileage value on the cloud platform will not have a jump risk.

[0026] In the embodiments of this application, a first difference between the target threshold and the target mileage difference is determined. The first value and the first difference are compared to determine whether there is a risk of mileage jumps in the mileage value uploaded to the cloud platform after the vehicle starts. Since a larger first value with a preset number of digits in the historical mileage values ​​indicates a higher probability of mileage jumps, and the first difference represents a threshold value indicating a risk of mileage jumps in the cloud platform. When the first value is greater than the first difference, it indicates that the vehicle's mileage value has reached the threshold value indicating a risk of mileage jumps, meaning that there is a risk of mileage jumps in the cloud platform when the current mileage value is uploaded. When the first value is less than or equal to the first difference, it indicates that the vehicle's mileage value has not reached the threshold value indicating a risk of mileage jumps, meaning that there is no risk of mileage jumps in the cloud platform when the current mileage value is uploaded. By comparing the first value and the first difference, a mileage jump risk value is determined, ensuring that the presence of a mileage jump risk in the cloud platform can be determined based on the first value and the threshold value (first difference), thus ensuring that a mileage jump risk value can be obtained.

[0027] In conjunction with the first aspect and the above implementation methods, in some implementation methods of the first aspect, after detecting the wake-up command from the vehicle host, the method further includes:

[0028] Perform anomaly detection on the vehicle's infotainment system and obtain anomaly detection results;

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

[0030] In the embodiments of this application, anomaly detection is performed on the vehicle's infotainment system to obtain anomaly detection results. The target mileage difference for the vehicle is determined based on the anomaly detection results; that is, the target mileage difference for the vehicle differs depending on the anomaly detection results of the infotainment system. This ensures that the target mileage difference for the vehicle can be obtained based on the anomaly detection results of the infotainment system.

[0031] Combining the first aspect and the above implementation methods, in some implementation methods of the first aspect, the target mileage difference of the vehicle is determined based on the anomaly detection results, including:

[0032] If the anomaly detection result indicates that there is an anomaly in the vehicle's infotainment system, determine the anomaly level corresponding to the anomaly;

[0033] The target mileage difference is determined based on the anomaly level; the target mileage difference is positively correlated with the anomaly level.

[0034] If the anomaly detection result indicates that there is no anomaly in the vehicle's infotainment system, the preset mileage difference will be set as the target mileage difference value.

[0035] In the embodiments of this application, if the anomaly detection result indicates an anomaly in the vehicle system, a target mileage difference is determined based on the anomaly level. If the anomaly detection result indicates that the vehicle system is not faulty, a preset mileage difference is determined as the target mileage difference. When the target mileage difference is configured to a small value, the risk of mileage jumps is low, but the performance requirements of the vehicle system (e.g., software refresh frequency and memory) are high. When the vehicle system is not faulty, the preset mileage difference is determined as the target mileage difference to ensure a high refresh frequency of the mileage value uploaded to the cloud platform, thereby reducing the probability of mileage jumps. When the vehicle system is faulty, the vehicle system cannot update the total mileage uploaded to the cloud platform at a high update frequency. In this case, the target mileage difference is determined based on the anomaly level. This ensures that the target mileage difference can be adapted according to the anomaly level.

[0036] In conjunction with the first aspect and the above implementation methods, some implementation methods of the first aspect also include:

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

[0038] In the embodiments of this application, since the target parameters of the vehicle's infotainment system may change during vehicle operation, such as the system's memory, software refresh rate, and response time, the current system may be unable to 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 system's target parameters to prevent the system from freezing and thus avoid failures in the process of uploading mileage values ​​to the cloud platform.

[0039] Secondly, a vehicle data uploading device is provided, the device comprising:

[0040] The acquisition module is used to respond to the vehicle's start command to acquire the vehicle's current mileage value, target mileage difference, and historical mileage value previously uploaded to the cloud platform, where the target mileage difference is used to represent the minimum mileage difference required to update the mileage uploaded to the cloud platform;

[0041] The first determination module is used to determine the mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value. The mileage jump risk value is used to indicate whether there is a jump risk in the mileage value on the cloud platform 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 will upload 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 conjunction with the second aspect, in some implementations of the second aspect, the second determining module is specifically used to: determine the historical mileage value as the target mileage value if the current mileage value is uploaded to the cloud platform and there is a risk of mileage jump on the cloud platform; and determine the current mileage value as the target mileage value if the current mileage value is uploaded to the cloud platform and there is no risk of mileage jump on the cloud platform.

[0044] In conjunction with the second aspect and the above implementation methods, in some implementation methods of the second aspect, the acquisition module is further used to: acquire the data display format of the mileage value on the cloud platform; the first determination module is used to: 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; determine 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; and determine the mileage jump risk value of the current mileage value based on the first difference and the first value.

[0045] In conjunction with the second aspect and the above implementation methods, in some implementation methods of the second aspect, the first determining module is specifically used to: determine the mileage jump risk value indicating that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform has a jump risk when the first value is greater than the first difference; and determine the mileage jump risk value indicating that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform does not have a jump risk when the first value is less than or equal to the first difference.

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

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

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

[0049] Thirdly, a vehicle is provided, including a memory and a processor, the memory for storing executable program code, and the processor for calling and running the executable program code from the memory, causing the vehicle to perform the methods of the first aspect or any possible implementation thereof.

[0050] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0051] Fifthly, a computer-readable storage medium is provided that stores instructions which, when executed on a vehicle, cause the vehicle to perform the method described in the first aspect or any possible implementation thereof. Attached Figure Description

[0052] Figure 1 This is a schematic diagram of a scenario provided in an embodiment of this application;

[0053] Figure 2 This is a schematic diagram illustrating a vehicle mileage value display provided in an embodiment of this application;

[0054] Figure 3 This is a schematic flowchart illustrating a vehicle data uploading method provided in an embodiment of this application;

[0055] Figure 4 This is a schematic flowchart illustrating another vehicle data uploading method provided in an embodiment of this application;

[0056] Figure 5 This is a schematic diagram of the structure of a vehicle data uploading device provided in an embodiment of this application;

[0057] Figure 6 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

[0058] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0059] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting 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 that feature.

[0060] Currently, vehicle mileage not only needs to be displayed on the vehicle's dashboard but also needs to be uploaded to the national regulatory backend via a cloud platform. The mileage displayed on the dashboard can be in integer format, while the data uploaded to the cloud platform can have one decimal place. For example... Figure 1 The scenario diagram shown in scenario 100 includes vehicle 110 and cloud platform 120. During the journey, the vehicle uploads its mileage value to the cloud platform.

[0061] As described in the background section, the mileage value uploaded to the cloud platform may change abruptly. For example, if the actual mileage is 3000.5 km when the engine is off, the instrument panel displays 3000 km, and the cloud platform uploads 3000.5 km. The mileage does not change during the vehicle's shutdown process, and the data uploaded to the cloud platform should still be 3000.5 km when the vehicle is restarted. However, during testing, it was found that the mileage uploaded to the cloud platform after the vehicle restarted was 3000.6 km. That is, without any actual mileage accumulation, the mileage value uploaded to the cloud platform changed by 0.1 km (=3000.6 km - 3000.5 km). In this application, this phenomenon is referred to as a "jump".

[0062] It should be noted that the update strategy for vehicle mileage uploaded to the cloud platform is typically based on a predetermined mileage change (e.g., 10m) as the minimum upload unit. The following description uses 10m as the minimum upload unit as an example. It should be understood that 10m is merely an example, and this application is not limited to this. For example, the minimum upload unit could also be 20m, 30m, or 40m, etc. If the change in mileage before the vehicle is turned off (this change represents the difference between the last mileage uploaded to the cloud platform before the vehicle was turned off and the actual mileage at the time the vehicle was turned off) contains a portion less than 10m, this portion of mileage will not be uploaded to the cloud platform. After the vehicle's host is woken up, if the vehicle uploads the latest mileage value (including the portion less than 10m), there may be an interval equal to this portion between the two uploads. This interval may cause a jump in the mileage value displayed on the cloud platform; that is, the mileage value displayed on the cloud platform may jump by 0.1km.

[0063] For example, if the vehicle's last uploaded mileage to the cloud platform before being turned off was 195m, and it then travels another 7 meters, resulting in a true mileage of 202m, the actual mileage will not be uploaded to the cloud platform when the vehicle is turned off. Since the mileage change since the last upload is 7m (202m - 195m), which is less than the minimum upload unit of 10m, the actual mileage of 202m will not be uploaded to the cloud platform. The uploaded mileage on the cloud platform will still be 0.1km (mileage is in km, and the data format on the cloud platform retains one decimal place; therefore, the mileage of 195m, or 0.195km, will be displayed as 0.1km on the cloud platform). If the vehicle's main unit is activated again after the vehicle is turned off, the vehicle will upload the current actual mileage of 202m to the cloud platform. In this case, the uploaded mileage on the cloud platform will become 0.2km (mileage is in km, and the data format on the cloud platform retains one decimal place; therefore, the mileage of 202m, or 0.202km, will be displayed as 0.2km on the cloud platform). In this situation, even if the vehicle has no mileage accumulation, the mileage value uploaded to the cloud platform will jump from 0.1km to 0.2km.

[0064] It's important to note that after a vehicle uploads its mileage to the cloud platform, the platform transmits the data to the national regulatory backend via a secure communication protocol for vehicle monitoring. If the mileage value uploaded to the cloud platform changes without any actual mileage accumulation (i.e., the cloud platform's mileage value jumps), it could lead to monitoring failure and misjudgments of driving behavior, making it impossible to accurately determine the vehicle's usage and driving mode. For example, between the time the vehicle is turned off and restarted, it is actually stationary (the vehicle's actual mileage value does not change). If the cloud platform's mileage value changes, it might be mistakenly interpreted as the vehicle being in motion.

[0065] Therefore, how to prevent the mileage values ​​uploaded by vehicles to the cloud platform from changing abruptly is a technical problem that needs to be solved.

[0066] In view of this, this application provides a vehicle data uploading method, apparatus, vehicle, and storage medium. Through embodiments of this application, upon detecting a wake-up command from the vehicle's main unit, a target mileage value to be uploaded to the cloud platform is determined based on the vehicle's current mileage, mileage jump risk value, and historical mileage values. This avoids mileage value jumps when uploaded to the cloud platform.

[0067] Figure 2 This is a schematic diagram showing a vehicle mileage value provided in an embodiment of this application.

[0068] For example, a vehicle's odometer reading is typically displayed in kilometers, and the maximum odometer reading is usually 999,999 km. If converted to meters (m), the maximum odometer reading would be 999,999,000 m. Figure 2 As shown, each box represents a digit, through... Figure 2 The boxes in the diagram represent the number of digits in the vehicle's odometer reading after conversion. Box 200 represents the odometer reading after converting kilometers to meters, box 210 represents the first 7 digits of the odometer reading after converting kilometers to meters, and box 220 represents the last 2 digits of the odometer reading after converting kilometers to meters.

[0069] For example, if the vehicle's actual mileage is 100001.898 km, expressed in meters, this actual mileage can be represented as 100001898 m. Therefore, box 210 contains 1000018, and box 220 contains 98. Since the vehicle's odometer reading can be an integer and can be in kilometers, the odometer reading displayed on the vehicle's instrument panel is 100001 km (an integer). Because the mileage data uploaded to the cloud platform can have one decimal place and can be in kilometers, the mileage value uploaded to the cloud platform is 100001.8 km (one decimal place, the last two digits omitted).

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

[0071] For example, if a vehicle had a mileage value of 3 meters that was not uploaded to the cloud platform before it was turned off, and the last actual mileage value uploaded to the cloud platform before the engine was turned off was 100001898 meters (mileage unit is km, and the mileage value displayed on the cloud platform is rounded to one decimal place, i.e., 100001.8 km), the last two digits would be 98. When the vehicle is started, the current actual mileage value uploaded is 100001898 + 3 = 100001901. Therefore, the mileage value after adding the 3 meters that was not uploaded to the cloud platform is 100001901 meters (mileage unit is km, and the mileage value displayed on the cloud platform is rounded to one decimal place, i.e., 100001.9 km). It can be seen that when the last two digits are 98, the mileage value uploaded to the cloud platform jumps from 100001.8 km to 100001.9 km. When the total mileage before the engine is turned off is 100001801m (mileage unit is km, the mileage value displayed on the cloud platform is rounded to one decimal place, i.e., 100001.8km), the last two digits are 01. After the vehicle is started, the current actual mileage is uploaded, and the 3m mileage value not uploaded to the cloud platform is added, resulting in 100001804m (mileage unit is km, the mileage value displayed on the cloud platform is rounded to one decimal place, i.e., 100001.8km). Therefore, when the last two digits are 01, the mileage value uploaded to the cloud platform will not change. Thus, the larger the last two digits, the greater the likelihood that the mileage value uploaded to the cloud platform will change.

[0072] The method for uploading vehicle data provided in this application will be described in detail below with reference to the method flowchart provided in the embodiments of this application.

[0073] Figure 3 This is a schematic flowchart illustrating a vehicle data uploading method provided in an embodiment of this application.

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

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

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

[0077] For example, a vehicle start command is used to activate the vehicle's engine or electric motor, causing the vehicle to transition from a stationary state to a drivable state. Methods for triggering the vehicle start command include, but are not limited to, triggering the vehicle start command via a key signal from a remote key, or triggering the vehicle start command via an ignition switch signal from turning the ignition switch. This application does not limit the method of triggering the vehicle start command.

[0078] The target mileage difference represents the minimum mileage difference required to update the mileage uploaded to the cloud platform. For example, a target mileage difference of 10m means that the vehicle's mileage is uploaded to the cloud platform every 10m. In other words, when the vehicle's mileage difference is greater than 10m, the mileage uploaded to the cloud platform is updated.

[0079] The historical mileage value before engine shutdown represents the last mileage value uploaded to the cloud platform before the vehicle start command was detected, i.e., before the vehicle was shut down. The current mileage value is the actual mileage value of the vehicle. For example, if the last mileage value uploaded to the cloud platform before the vehicle was shut down was 195m, and the vehicle shut down when it reached a mileage value of 202m, when the vehicle is started this time, the historical mileage value before engine shutdown will be 195m, and the current mileage value will be 202m.

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

[0081] The method for determining the target mileage difference for a vehicle is described below.

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

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

[0084] To further explain the above-mentioned test items, slow software updates in the vehicle may cause delays in mileage data collection and processing, thus affecting mileage data upload. Insufficient vehicle memory may cause the vehicle's infotainment system to malfunction or result in lost mileage data. Network connectivity issues with the infotainment system may prevent timely upload of mileage data to the cloud or result in data loss. Power problems in the vehicle, such as a sudden power outage or unstable power supply, may lead to mileage data loss during the upload process.

[0085] It should be noted that when the target mileage difference is small, the performance requirements of the vehicle's infotainment system are relatively high (e.g., software refresh rate and memory). When the infotainment system's anomaly detection results indicate the aforementioned anomaly, the vehicle cannot update the target mileage value uploaded to the cloud platform at a high refresh rate. Therefore, it is necessary to adapt the target mileage difference to the anomaly level (i.e., the severity of the anomaly) of the infotainment system.

[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 100m and the target mileage difference is 10m, it means the target mileage value is refreshed every 10m, meaning it may have been refreshed 10 times within 100m. If the target mileage difference is 20m, it means the target mileage value is refreshed every 20m, meaning it may have been refreshed 5 times within 100m.

[0087] In the embodiments of this application, anomaly detection is performed on the vehicle's infotainment system to obtain anomaly detection results. The target mileage difference for the vehicle is determined based on the anomaly detection results; that is, different anomaly detection results for the infotainment system correspond to different target mileage differences for the vehicle, ensuring that the target mileage difference for the vehicle can be obtained based on the anomaly detection results of the infotainment system.

[0088] In one implementation, determining the target mileage difference for the vehicle based on the anomaly detection result includes: if the anomaly detection result indicates that the vehicle's infotainment system has an anomaly, determining the anomaly level corresponding to the anomaly; determining the target mileage difference based on the anomaly level; wherein the target mileage difference is positively correlated with the anomaly level; if the anomaly detection result indicates that the vehicle's infotainment system does not have an anomaly, determining a preset mileage difference as the target mileage difference, wherein the preset mileage difference is a unit distance.

[0089] For example, based on the severity of the anomalies in the vehicle's infotainment system, the anomaly levels are divided into three categories: Level 1 (minor anomaly), Level 2 (severe anomaly), and Level 3 (major anomaly). A target mileage difference is determined based on the anomaly level indicated by the anomaly detection results. A higher anomaly level indicates a more severe anomaly, and the corresponding target mileage difference is larger. This allows the vehicle to update the mileage value in the cloud platform at a lower refresh frequency, thereby mitigating anomalies such as lag and slow response in the vehicle's infotainment system.

[0090] For example, if the anomaly detection result indicates that the vehicle's infotainment system has a level 3 anomaly, the target mileage difference is set at 30m (when the mileage change reaches 30m, the vehicle's current mileage is uploaded to the cloud platform). If the anomaly detection result indicates that the vehicle's infotainment system has a level 2 anomaly, the target mileage difference is set at 20m (when the mileage change reaches 20m, the vehicle's current mileage is uploaded to the cloud platform). If the anomaly detection result indicates that the vehicle's infotainment system has a level 1 anomaly, the target mileage difference is set at 10m (when the mileage change reaches 10m, the vehicle's current mileage is uploaded to the cloud platform). If the anomaly detection result indicates that the vehicle's infotainment system has no anomaly, the target mileage difference is set at 1m (when the mileage change reaches 1m, the vehicle's current mileage is uploaded to the cloud platform).

[0091] In one implementation, a range of target mileage differences is determined based on the anomaly level, and the corresponding target mileage difference is automatically applied within that range. For example, when the anomaly level is Level 1, the corresponding target mileage difference is greater than or equal to 10m and less than 20m. When the anomaly level is Level 2, the corresponding target mileage difference is greater than or equal to 20m and less than 30m. When the anomaly level is Level 3, the corresponding target mileage difference is greater than or equal to 30m.

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

[0093] In the embodiments of this application, if the anomaly detection result indicates an anomaly in the vehicle infotainment system, a target mileage difference is determined based on the anomaly level. If the anomaly detection result indicates that the vehicle infotainment system is not faulty, a preset mileage difference is determined as the target mileage difference. Since the risk of mileage jumps is low when the target mileage difference is small, but the performance requirements of the vehicle infotainment system (including software refresh frequency and memory) are high, when the vehicle infotainment system is not faulty, the target mileage difference is determined per unit distance to ensure a high refresh frequency of the mileage value uploaded to the cloud platform, thereby reducing the probability of mileage jumps. However, when the vehicle infotainment system is faulty, it cannot update the total mileage uploaded to the cloud platform at a high refresh frequency. Therefore, the target mileage difference is determined based on the anomaly level of the vehicle infotainment system to ensure that the target mileage difference can be adapted to the anomaly level of the vehicle infotainment system.

[0094] S320 determines the mileage jump risk value of the current mileage value based on the target mileage difference and historical mileage values.

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

[0096] In one implementation, the data display format for mileage values ​​on the cloud platform is obtained;

[0097] Based on the data display format, a target threshold is determined; whereby the target threshold is the minimum value that causes the mileage value displayed on the cloud platform to change.

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

[0099] For example, based on the data display format of the mileage value on the cloud platform, a target threshold for changes in the mileage value displayed on the cloud platform is determined. For instance, if the target mileage value is displayed in a one-decimal-place format in km, the minimum change in the mileage value displayed on the cloud platform is 0.1 km (converted to m, i.e., 100 m). Therefore, when the target mileage value is displayed in a one-decimal-place format, a change in mileage of 100 m will cause a change in the mileage value displayed on the cloud platform. If the target mileage value is displayed in a two-decimal-place format in km, the minimum change in the mileage value displayed on the cloud platform is 0.01 km (converted to m, i.e., 10 m). Therefore, when the target mileage value is displayed in a two-decimal-place format, a change in mileage of 10 m will cause a change in the mileage value displayed on the cloud platform.

[0100] For example, a first value with a preset number of digits is determined from the historical mileage value, where the first value is a numerical value composed of digits with a preset number of digits in the historical mileage value. For instance, if the actual mileage value corresponding to the historical mileage value previously uploaded to the cloud platform is 1098m (displayed in the cloud platform in km, with one decimal place, the mileage value displayed on the cloud platform is 1.0km), and the preset number of digits is the last two digits, then the first value is 98. If the actual mileage value corresponding to the historical mileage value previously uploaded to the cloud platform is 8960m (displayed in the cloud platform in km, with one decimal place, the mileage value displayed on the cloud platform is 8.9km), and the preset number of digits is the last two digits, then the first value is 60.

[0101] Optionally, based on the target threshold, a preset number of digits is determined in the historical mileage values, where the preset number of digits is one digit less than the target threshold. For example, when the target threshold is 100m, the target threshold has three digits, and the determined preset number of digits is the last two digits. When the target threshold is 10m, the target threshold has two digits, and the determined preset number of digits is the last digit.

[0102] In the embodiments of this application, a target threshold is determined according to the data display format of the target mileage value. The target threshold is the minimum value at which the data display of the target mileage value changes. A mileage jump risk value for the current mileage value is determined based on a first difference and a first value between the target threshold and the target mileage difference. Since a larger first value with a preset number of digits in the historical mileage values ​​indicates a higher probability of mileage jumps, a first difference between the target threshold and the target mileage difference is determined. This first difference is used to determine the critical value at which mileage jumps occur in the cloud platform, thereby ensuring that the mileage jump risk value for the current mileage value can be determined based on the first difference and the first value.

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

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

[0105] For example, if the target mileage difference is 10m and the target threshold is 100m (meaning that the mileage value displayed on the cloud platform changes when the mileage change reaches 100m), then the first difference is determined to be 90m (=100m-90m). The first value of a preset number of digits in the historical mileage values ​​is determined (for example, the first value is the last two digits of the corresponding historical mileage value), and the first difference is compared with the first value of the preset number of digits in the historical mileage values. If there was 5m of mileage not uploaded to the cloud platform before the engine was turned off, and the first value is 98m, when the vehicle is started, the first value and the mileage not uploaded to the cloud platform before the engine was turned off will accumulate and reach the target threshold (98m+5m=103m), causing the mileage value displayed on the cloud platform to jump, meaning there is a risk of jumping when uploading the current mileage value. However, when the first value is less than or equal to the first difference, for example, 20m... In this situation, even if there are mileage values ​​that were not uploaded to the cloud platform before the engine was turned off, reaching the maximum value (approaching 10m), the first value and the mileage values ​​that were not uploaded to the cloud platform before the engine was turned off will not reach the target threshold after accumulation. Therefore, the mileage value displayed on the cloud platform will not change, meaning there is no risk of the vehicle uploading the current mileage value changing.

[0106] In the embodiments of this application, a first difference between the target threshold and the target mileage difference is determined; the first value and the first difference are compared to determine whether there is a risk of mileage jumps in the mileage value uploaded to the cloud platform after the vehicle starts. Since the larger the first value with a preset number of digits in the historical mileage value, the greater the probability of mileage jumps, and the first difference is used to represent the threshold value for mileage jump risks in the cloud platform. When the first value is greater than the first difference, it indicates that the vehicle's mileage value has reached the threshold value for jump risks, meaning that there is a risk of mileage jumps in the cloud platform when the current mileage value is uploaded. When the first value is less than the first difference, it indicates that the vehicle's mileage value has not reached the threshold value for jump risks, meaning that there is no risk of mileage jumps in the cloud platform when the current mileage value is uploaded. By comparing the first value and the first difference, a mileage jump risk value is determined, ensuring that it is possible to determine whether there is a risk of mileage jumps in the cloud platform based on the first value and the threshold value for jump risks (the first difference), thus ensuring that the mileage jump risk value can be obtained.

[0107] It's important to note that if the first value is greater than the first difference, it indicates a possibility of a jump in the vehicle's uploaded mileage value. However, this does not mean that the mileage value in the cloud platform will necessarily change after the vehicle uploads its current mileage. For example, if the first value is 95, and the mileage value not uploaded to the cloud platform before the engine is turned off (i.e., the mileage value updated but not uploaded before the engine is turned off) is 7m, the first value and the mileage value not uploaded to the cloud platform, when accumulated, reach the target threshold (95 + 7 > 100), causing a change in the mileage value in the cloud platform. In other words, if the current mileage value is uploaded to the cloud platform after the vehicle is started, the mileage value in the cloud platform will change. If the value updated but not uploaded before the engine is turned off is 3m, then the first value and the mileage value not uploaded to the cloud platform, when accumulated, do not reach the target threshold (95 + 3 < 100), and the mileage value in the cloud platform will not change. In other words, if the current mileage value is uploaded to the cloud platform after the vehicle is started, the mileage value in the cloud platform will not change. Therefore, the aforementioned "mileage jump risk" indicates the possibility that the mileage value on the cloud platform might change if the current mileage value is uploaded. If there is a possibility that the mileage value on the cloud platform might change after uploading the current mileage value, then a mileage jump risk exists. If there is no possibility that the mileage value on the cloud platform might change after uploading the current mileage value, then there is no mileage jump risk.

[0108] Optionally, the system obtains the historical mileage value last uploaded to the cloud platform before the vehicle was turned off, and the first mileage value updated before the vehicle was turned off but not uploaded to the cloud platform; determines a first value with a preset number of digits for the historical mileage value, and sums the first value and the first mileage value to obtain a sum. The sum is compared with a target threshold. If the sum is greater than the target threshold, a mileage jump risk value is determined, indicating that the current mileage value has a jump risk; if the sum is less than the target threshold, a mileage jump risk value is determined, indicating that the current mileage value does not have a jump risk.

[0109] For example, the first value with a preset number of digits in the historical mileage values ​​is summed with the first mileage value to obtain a sum. This sum is then compared with a target threshold to determine whether the sum will cause a jump in the vehicle's mileage. Since the target threshold is the minimum value that would cause a change in the mileage value in the cloud platform, if the sum is greater than the target threshold, it means that the sum of the first value and the first mileage value will cause a change in the mileage value displayed in the cloud platform. Therefore, the current mileage value uploaded after the vehicle starts and the previously uploaded historical mileage value are displayed differently in the cloud platform. That is, when the current mileage value is uploaded to the cloud platform after the vehicle starts, there is a risk of a jump in the mileage value in the cloud platform. If the sum is less than or equal to the target threshold, it means that the sum of the first value and the first mileage value will not change the mileage value displayed in the cloud platform. Therefore, the current mileage value uploaded after the vehicle starts and the previously uploaded historical mileage value are displayed as the same mileage value in the cloud platform. That is, when the current mileage value is uploaded to the cloud platform after the vehicle starts, there is no risk of a jump in the mileage value in the cloud platform.

[0110] For example, if the last uploaded historical mileage value before the engine was turned off was 100001898m (displayed on the cloud platform in km, rounded to one decimal place, i.e., 100001.8km), the first value is determined to be 98, and the target threshold is 100. If the first mileage value not uploaded to the cloud platform before the engine was turned off was 3m, the first value and the first mileage value are summed, resulting in a sum of 101 (=98+3). Since the sum is greater than the target threshold, it is determined whether there is a risk of mileage abrupt changes on the cloud platform if the vehicle is started and the current mileage value is uploaded. Therefore, by comparing the sum with the target threshold, it is possible to accurately determine whether there is a risk of mileage abrupt changes in the mileage value uploaded to the cloud platform.

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

[0112] In one implementation, based on the current mileage value, the mileage jump risk value, and historical mileage values, the target mileage value that the vehicle will upload to the cloud platform after this startup is determined, including:

[0113] If the mileage jump risk value indicates that uploading the current mileage value to the cloud platform would pose a risk of mileage jump, then the historical mileage value will be determined as the target mileage value; if the mileage jump risk value indicates that uploading the current mileage value to the cloud platform would not pose a risk of mileage jump, then the current mileage value will be determined as the target mileage value.

[0114] For example, when the mileage jump risk value indicates that the current mileage value should be uploaded to the cloud platform, and the mileage value on the cloud platform is at risk of jumping, the historical mileage value is determined as the target mileage value to avoid the mileage value on the cloud platform jumping. Since the historical mileage value is the total mileage before the vehicle is turned off, determining the historical mileage value as the target mileage value ensures that the target mileage value uploaded to the cloud platform is consistent with the historical mileage value before the vehicle is turned off, thereby preventing the total mileage of the vehicle from jumping. If the mileage jump risk value indicates that the current mileage value should be uploaded to the cloud platform, and the mileage value on the cloud platform is not at risk of jumping, the current mileage value is determined as the target mileage value. This ensures that when the mileage jump risk value is different, the corresponding target mileage value can be determined to avoid the mileage value uploaded to the cloud platform jumping.

[0115] In one possible implementation, the target mileage difference is determined based on the anomaly level of the vehicle system, and the target mileage value to be uploaded is determined based on the target mileage difference and the first value of the last two digits of the historical mileage value.

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

[0117] Taking a Level 1 anomaly as an example, the following is a detailed explanation: When the anomaly level is Level 1, 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, the current mileage value is not allowed to be sent after the vehicle starts, but the historical mileage value before the engine is turned off is sent instead; when the first value is less than 80, the current mileage value is sent directly after the vehicle starts.

[0118] When the target mileage difference is 10 meters, 10 meters is the lower limit for uploading. If the last two digits of the historical mileage value exceed 90 meters, there is a risk of a jump exceeding 100 meters (0.1 km). 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, uploading the current mileage value should be prohibited after the vehicle starts; otherwise, the uploaded current mileage value will differ from the historical mileage value on the cloud platform. When the target mileage difference is 20 meters, 20 meters is the lower limit for uploading. If the last two digits of the historical mileage value exceed 80 meters, there is a risk of a jump exceeding 100 meters (0.1 km). Therefore, 80 meters needs to be determined as the second limit. Using these two thresholds, a minimum threshold of 80 meters is determined for the risk of a jump. When the last two digits of the historical mileage value are less than or equal to the minimum threshold, it means that uploading the current mileage value will not change the mileage value displayed on the cloud platform, i.e., there is no risk of a jump in the mileage value on the cloud platform. If the last two digits of the historical mileage value are greater than the minimum threshold, it means that uploading the current mileage value will cause the mileage value displayed on the cloud platform to change, i.e., there is a risk of the mileage value in the cloud platform changing.

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

[0120] It should be noted that the above is a detailed explanation of determining the target mileage value when the anomaly level is Level 1. For Level 2 or Level 3 anomalies, please refer to the above description; it will not be repeated here.

[0121] In one possible implementation, after uploading the target mileage value to the cloud platform, the vehicle's current mileage value 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, if the target mileage difference is 10m and the target mileage is 195m, after the vehicle uploads the target mileage to the cloud platform, the platform obtains the vehicle's current mileage in real time. When the change in the current mileage reaches the target mileage difference, the uploaded target mileage is updated. For example, when the vehicle's current mileage is 205m, the target mileage is updated and uploaded as 205m; when the vehicle's current mileage is 215m, the target mileage is updated again and uploaded as 215m.

[0123] In the embodiments of this application, the current mileage of the vehicle is acquired in real time, and the target mileage value is updated when the change in the current mileage reaches the target mileage difference. This ensures that after the target mileage value is uploaded to the cloud platform, it is updated promptly based on the change in the current mileage value.

[0124] In one implementation, the method further includes: adjusting the target mileage difference of the vehicle based on the target parameters of the vehicle system during vehicle operation, 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, and a lag is detected in the vehicle's infotainment system based on its target parameters (including software refresh frequency, memory, and response time), the target mileage difference will be adjusted to a larger difference, such as 30. This is achieved by changing the mileage update interval in the cloud platform from 10 minutes to 30 minutes, thus mitigating the lag in the vehicle's infotainment system.

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

[0127] In the embodiments of this application, since the target parameters of the vehicle's infotainment system may change during vehicle operation, such as the system's memory, software refresh rate, and response time, the current infotainment system may be unable to 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 infotainment system to avoid system lag and thus prevent failures in the process of uploading mileage values ​​to the cloud platform.

[0128] In the above embodiments, in response to the vehicle's start command, the vehicle's current mileage, target mileage difference, and historical mileage last uploaded to the cloud platform are obtained. A mileage jump risk value for the current mileage is determined, and a target mileage is determined based on the current mileage, historical mileage, and mileage jump risk value. Because this application can determine the mileage jump risk value based on the target mileage difference and historical mileage, it can determine whether there is a mileage jump risk in the cloud platform after the current mileage is uploaded. Furthermore, based on the current mileage, mileage jump risk value, and historical mileage, a corresponding target mileage is determined; that is, the determined target mileage is different when the current mileage jump risk value is different. Compared to the prior art where the vehicle's host uploads the vehicle's actual mileage after wake-up, this solution can determine the uploaded target mileage based on the current mileage, mileage jump risk value, and historical mileage, instead of directly uploading the current mileage; therefore, it can avoid mileage jumps in the cloud platform caused by directly uploading the current mileage.

[0129] Figure 4 This is a schematic flowchart illustrating another vehicle data uploading method provided in this application embodiment.

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

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

[0132] S401, in response to the vehicle's start command, performs anomaly detection on the vehicle's infotainment system.

[0133] For example, a vehicle start command is used to activate the car's engine or electric motor, enabling the vehicle to transition from a stationary state to a drivable state. Methods for triggering the vehicle start command include, but are not limited to, triggering the vehicle start command via a key signal from a remote key, or triggering the vehicle start command via an ignition switch signal from turning the ignition switch. In response to the vehicle start command, the vehicle's main unit is awakened and performs anomaly detection on the vehicle's infotainment system.

[0134] For example, when performing anomaly detection on the vehicle infotainment system, the detection items are those that affect the uploaded vehicle mileage value. These items include, but are not limited to, the vehicle's software refresh rate, the vehicle infotainment system's memory, the vehicle infotainment system's network connection, and power supply issues.

[0135] S402, based on the detection results of anomaly detection, determines the target mileage difference for the vehicle.

[0136] For example, if the detection result indicates an anomaly in the vehicle's infotainment system, the corresponding anomaly level is determined. Based on the anomaly level, a target mileage difference is determined, where the target mileage difference is positively correlated with the anomaly level; that is, the higher the anomaly level of the infotainment system, the larger the determined target mileage difference. If the anomaly detection result indicates that the vehicle's infotainment system does not have an anomaly, a preset mileage difference is determined as the target mileage difference, where the preset mileage difference is a unit distance.

[0137] Alternatively, the implementation methods of S401 and S402 can be found in [reference needed]. Figure 3 The relevant description of S310 will not be repeated here.

[0138] S403 retrieves the vehicle's current mileage and the historical mileage value previously uploaded to the cloud platform.

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

[0140] Alternatively, the implementation of S403 can be found in [reference needed]. Figure 3 The relevant descriptions in S301 will not be repeated here.

[0141] S404, based on the data display format of mileage values ​​on the cloud platform, determines the target threshold.

[0142] For example, based on the data display format of the mileage value on the cloud platform, a target threshold for causing a change in the mileage value displayed on the cloud platform is determined; for instance, if the target mileage value is displayed in a format with one decimal place and the unit is km, then the minimum change in the data display of the target mileage value is 0.1 km, i.e., the target threshold is 100 m. If the target mileage value is displayed in a format with two decimal places and the unit is km, then the minimum change in the data display of the target mileage value is 0.01 km, i.e., the target threshold is 10 m.

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

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

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

[0146] For example, a first value with a preset number of digits is determined from the historical mileage value, where the first value is a numerical value composed of digits with a 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] Alternatively, the implementation methods of S403 to S406 can be found in [reference needed]. Figure 3 The implementation method of S320 will not be elaborated here.

[0148] S407, Is the first value greater than the first difference? If yes, proceed to S408; if no, proceed to S410.

[0149] For example, the larger the first value with a preset number of digits in the historical mileage values, the greater the probability of a mileage jump, and the first difference is used to represent the threshold at which the vehicle's mileage value indicates a risk of a jump. Therefore, by comparing the first value and the first difference, it is possible to accurately determine whether there is a risk of a jump in the mileage value in the cloud platform after the current mileage value is uploaded to the cloud platform.

[0150] For S408, if the current mileage value is uploaded to the cloud platform, there is a risk that the mileage value on the cloud platform may change.

[0151] For example, when the first value is greater than the first difference, it means that the mileage value displayed on the cloud platform has reached the threshold where there is a risk of mileage jump. That is, if the current mileage value is uploaded to the cloud platform, there is a risk of mileage jump on the cloud platform.

[0152] S409 sets 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 the mileage value on the cloud platform changing, the historical mileage value is determined as the target mileage value. This ensures that the target mileage value uploaded to the cloud platform is consistent with the historical mileage value uploaded before the engine is turned off, thereby avoiding changes in the mileage value displayed on the cloud platform.

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

[0155] For example, when the first value is less than or equal to the first difference, it means that the mileage value displayed on the cloud platform has not reached the threshold of risk of jump, that is, if the current mileage value is uploaded to the cloud platform, there is no risk of jump in the total mileage on the cloud platform.

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

[0157] Alternatively, the implementation methods of S408 to S411 can be found in [reference needed]. Figure 3 The implementation method of S330 will not be elaborated here.

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

[0159] S413 updates the target mileage value when the change in the vehicle's current mileage value reaches the target mileage difference.

[0160] For example, after uploading the target mileage value to the cloud platform, the vehicle's current mileage value 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. This ensures that the target mileage value uploaded to the cloud platform is updated promptly whenever the vehicle's current mileage value changes.

[0161] In the embodiments of this application, a first value and a first difference are compared to determine whether there is a risk of mileage jumps in the mileage value on the cloud platform when the current mileage value is uploaded to the cloud platform. If there is a risk of mileage jumps in the mileage value on the cloud platform, the historical mileage value previously uploaded to the cloud platform is determined as the target mileage value, thereby avoiding inconsistencies between the mileage value on the cloud platform before vehicle startup and the mileage value on the cloud platform after vehicle startup, thus preventing mileage jumps in the cloud platform.

[0162] The above text combined Figures 1 to 4 The vehicle data uploading method provided in the embodiments of this application is described in detail below; the following will be combined with Figure 5 and Figure 6 The apparatus embodiments of this application are described in detail below. It should be understood that the apparatus in the embodiments of this application can perform the various methods described in the foregoing embodiments of this application, that is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0163] Figure 5 This is a schematic diagram of the structure of a vehicle data uploading device provided in an embodiment of this application.

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

[0165] The acquisition module 510 is used to acquire the vehicle's current mileage value, target mileage difference, and historical mileage value previously uploaded to the cloud platform in response to the vehicle's start command. The target mileage difference is used to represent the minimum mileage difference required to update the mileage uploaded to the cloud platform.

[0166] The first determining module 520 is used to determine the mileage jump risk value of the current mileage value based on the target mileage difference and the historical mileage value. The mileage jump risk value is used to indicate whether there is a jump risk in the mileage value on the cloud platform if the current mileage value is uploaded to the cloud platform.

[0167] The second determining module 530 is used to determine the target mileage value that the vehicle will upload 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 determining module 530 is specifically used to: determine the historical mileage value as the target mileage value if the mileage value on the cloud platform is at risk of being changed if the current mileage value is uploaded to the cloud platform.

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

[0170] Optionally, as an embodiment, the acquisition module 510 is further configured to: acquire the data display format of the mileage value on the cloud platform; the first determination module 520 is configured to: 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; determine 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; and determine the mileage jump risk value of the current mileage value based on the first difference and the first value.

[0171] Optionally, as an embodiment, the first determining module 520 is specifically used to: when the first value is greater than the first difference, determine the mileage jump risk value of the current mileage value indicating that if the vehicle uploads the current mileage value to the cloud platform, the mileage value on the cloud platform has a jump risk; when the first value is less than or equal to the first difference, determine the mileage jump risk value indicating that if the current mileage value is uploaded to the cloud platform, the mileage value on the cloud platform does not have a jump risk.

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

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

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

[0175] It should be noted that the aforementioned vehicle data uploading device is implemented in the form of a functional unit. The term "module" here can be implemented in software and / or hardware, without specific limitations.

[0176] For example, a "module" can be a software program, hardware circuit, or a combination of both that implements the above functions. Hardware circuits may include application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memory for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functions.

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

[0178] Figure 6 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application.

[0179] For example, vehicle 600 includes processor 610, memory 620 and executable program code 630.

[0180] For example, vehicle 600 includes one or more processors 610, which can support vehicle 600 in implementing 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] For example, processor 610 can be used to control vehicle 600, execute software programs, and process data from the software programs. Vehicle 600 may also include a communication unit for receiving and transmitting signals.

[0182] For example, 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 run by the processor 610 to generate instructions, causing the processor 610 to execute the vehicle data uploading method described in the above method embodiments according to the instructions.

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

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

[0185] For example, the memory 620 can be used to store related programs of the vehicle data uploading method provided in the embodiments of this 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 embodiments of this application; for example, in response to the vehicle's start command, the current mileage value, the target mileage difference, and the historical mileage value previously uploaded to the cloud platform are obtained, wherein the target mileage difference is used to represent the minimum mileage difference for updating the mileage uploaded to the cloud platform; based on the target mileage difference 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 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, the target mileage value to be uploaded to the cloud platform by the vehicle after this start is determined.

[0186] This 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 foregoing embodiments.

[0187] The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, Digital Video Discs (DVDs), Compact Disc Read-Only Memory (CD-ROM), microdrives, and magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), dynamic random access memory (DRAM), 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] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement a vehicle data uploading method as described in the above embodiments.

[0189] In addition, the vehicle provided in the embodiments of this application may specifically be a chip, component or module. The vehicle may include a connected processor and a memory. The memory is used to store instructions. When the vehicle is running, the processor may call and execute the instructions to make the chip execute a vehicle data uploading method in the above embodiments.

[0190] 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 be referred to the beneficial effects of the corresponding vehicle data uploading method provided above, and will not be repeated here.

[0191] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above 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 this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0193] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for uploading vehicle data, characterized in that, The method includes: In response to the vehicle's start command, the system acquires the vehicle's current mileage value, target mileage difference, historical mileage value previously uploaded to the cloud platform, and the data display format of the mileage value on the cloud platform, wherein the target mileage difference is used to represent the minimum mileage difference required to update the mileage uploaded to the cloud platform; Based on the data display format, a target threshold is determined, wherein the target threshold is the minimum value that causes the mileage value displayed on the cloud platform to change; Determine a first difference between the target threshold and the target mileage difference; Determine the first value of the historical mileage value with a preset number of digits; Based on the first difference and the first value, a mileage jump risk value for the current mileage is determined; wherein the mileage jump risk value is used to indicate whether there is a risk of mileage jump on the cloud platform if the current mileage is uploaded to the cloud platform. If the mileage jump risk value indicates that uploading the current mileage value to the cloud platform would result in a mileage jump risk on the cloud platform, the historical mileage value will be 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.

2. The method according to claim 1, characterized in that, The step of determining the mileage jump risk value of the current mileage value based on the first difference and the first value includes: 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, the mileage value on the cloud platform has the risk of jump. 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, the mileage value on the cloud platform does not have the jump risk.

3. The method according to any one of claims 1 or 2, characterized in that, Also includes: Anomaly detection is performed on the vehicle's infotainment system, and anomaly detection results are obtained; Based on the anomaly detection results, the target mileage difference of the vehicle is determined.

4. The method according to claim 3, characterized in that, The step of determining the target mileage difference of the vehicle based on the anomaly detection results includes: If the anomaly detection result indicates that there is an anomaly in the vehicle's infotainment system, determine the anomaly level corresponding to the anomaly; Based on the anomaly level, the target mileage difference is determined, wherein the target mileage difference is positively correlated with the anomaly level; If the anomaly detection result indicates that there is no anomaly in the vehicle's infotainment system, the preset mileage difference is determined as the target mileage difference value.

5. The method according to any one of claims 1 or 2, characterized in that, Also includes: During the vehicle's operation, the target mileage difference of the vehicle is adjusted based on the target parameters of the vehicle's infotainment system, including the software refresh rate, memory, and response time of the infotainment system.

6. A vehicle data uploading device, characterized in that, The device includes: The acquisition module is used to acquire the vehicle's current mileage value, target mileage difference, historical mileage value previously uploaded to the cloud platform, and the data display format of the mileage value on the cloud platform in response to the vehicle's start command, wherein the target mileage difference is used to represent the minimum mileage difference for updating the mileage uploaded to the cloud platform; The first determining module is configured to: 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; determine 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; and determine a mileage jump risk value of the current mileage value based on the first difference and the first value, wherein the mileage jump risk value is used to indicate whether there is a jump risk in the mileage value on the cloud platform if the current mileage value is uploaded to the cloud platform. The second determining module is 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, the mileage value on the cloud platform will have the risk of jump; and to 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, the mileage value on the cloud platform will not have the risk of jump.

7. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a vehicle, cause the vehicle to perform the method as described in any one of claims 1 to 5.

Images