Vehicle-mounted host computer data storage scheduling method and vehicle

Abstract

The application provides a vehicle-mounted host storage data scheduling method and a vehicle. The method obtains a priority score or a priority level of stored file data, deletes internal data to be deleted determined based on the priority score or the priority level in the case that the remaining storage space is insufficient, intelligently selects low-priority data and guides a user to delete the low-priority data when the space is insufficient, divides the data to be stored into data of different levels, and stores the data according to corresponding data sub-partitions, so that the scheduling method can store new data into corresponding sub-partitions according to importance, thereby maintaining the health state of the storage space and improving user experience.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and more particularly to a method for scheduling data stored in an onboard host and a vehicle. Background Technology

[0002] As vehicles are used for extended periods, the built-in storage space of the vehicle's infotainment system becomes limited. With prolonged use, cached data from various applications, downloaded files, recorded videos, and other data will gradually fill up the storage space. When upgrades or the installation of large applications are needed, the process often fails due to insufficient remaining space.

[0003] Traditional solutions to insufficient remaining storage space include providing a "clear cache" button. However, this only deletes temporary cache and cannot clean up large files downloaded or generated by the user. Furthermore, the deletion entry points for different applications are scattered, making the process cumbersome. Users find it difficult to properly delete data within built-in storage devices, resulting in data that cannot be stored correctly. Summary of the Invention

[0004] The main objective of this invention is to provide a method for scheduling data stored in an in-vehicle host and a vehicle, aiming to solve the technical problem that users have difficulty in reasonably deleting data in the built-in storage devices, resulting in the inability to store data properly.

[0005] To achieve the above objectives, this invention proposes a method for scheduling data storage in a vehicle-mounted host, which is applied to a vehicle-mounted host. The built-in storage device in the vehicle-mounted host includes multiple storage partitions, and each storage partition includes an auxiliary data sub-partition, a normal data sub-partition, an important data sub-partition, and a core data sub-partition. The method for scheduling data stored in the vehicle host includes: Obtain the priority score or priority level of the file data stored in each data sub-partition; Upon receiving data to be stored, obtain the remaining storage space of the storage partition; If the remaining storage space is less than the required storage space for the data to be stored, the internal data to be deleted in each of the data sub-partitions is determined based on the priority score or priority level, and the internal data to be deleted is sent to the user. Upon receiving a deletion command from a user, the internal data to be deleted is deleted, and the data to be stored is divided into auxiliary data, ordinary data, important data, and core data. The auxiliary data, the ordinary data, the important data, and the core data are stored in their respective data sub-partitions.

[0006] Optionally, obtaining the priority score or priority level of the file data stored in each data sub-partition includes: Retrieve the set of data tags for the file data stored in each data sub-partition; Obtain the label weights and current label scores for each data label within the data label set; The priority score or priority level of the file data is calculated based on the tag weight and the tag score.

[0007] Optionally, after obtaining the label weights corresponding to each data label in the data label set and the label scores at the current time, the method further includes: Obtain the vehicle's current driving status; Adjust the current time-based label score of the scene data labels in the data label set according to the current driving state; The priority score or priority level of the file data is calculated based on the weight of each label, the adjusted label score of the scene data label, and the label scores of other labels.

[0008] Optionally, the on-board host storage data scheduling method further includes: Get the user-set data cleanup cycle, the previous data cleanup time, and the current time; If the time interval between the previous data cleanup time and the current time reaches the data cleanup cycle, the space health of the storage device is detected; If the space health is less than the preset health, the internal data to be deleted in the storage partition is determined based on the priority score or priority level, and the internal data to be deleted is sent to the user. Upon receiving a deletion command from the user, the internal data to be deleted is deleted.

[0009] Optionally, the built-in storage device is divided into a temporary storage partition and multiple non-temporary storage partitions, and the vehicle host is also connected to an external storage device; The on-board host storage data scheduling method further includes: Upon receiving data to be stored, the remaining temporary storage space of the temporary storage partition is checked; If the remaining temporary storage space is less than the required storage space for the data to be stored, detect the remaining non-temporary storage space of the non-temporary storage partition; If the remaining non-temporary storage space is less than the required storage space for the data to be stored, the data type of the data to be stored is detected. When the data type is the first data type, the non-temporary data to be transferred in the non-temporary storage partition and the external storage space required for the non-temporary data to be transferred are determined based on the priority score or priority level. Detect the first remaining external storage space of the external storage device; If the first remaining external storage space is less than the external storage space required for the non-temporary data to be transferred, the external data to be deleted in the external storage device is determined based on the priority score or priority level of the file data in the external storage device. Delete the data to be deleted externally, transfer the non-temporary data to be transferred to the external storage device, and store the data to be stored in the non-temporary storage partition.

[0010] Optionally, the on-board host storage data scheduling method further includes: When the data type is the second data type, the second remaining external storage space of the external storage device is detected; the priority of the second data type is lower than the priority of the first data type. If the second remaining external storage space is less than the external storage space required for the data to be stored, the external data to be deleted in the external storage device is determined. Delete the data to be deleted externally, and store the data to be stored in the external storage device.

[0011] Optionally, the on-board host storage data scheduling method further includes: If the remaining temporary storage space is not less than the required storage space for the data to be stored, the data to be stored will be stored in the temporary storage partition. Detect the remaining non-temporary storage space of the non-temporary storage partition storing the data to be stored; If the remaining non-temporary storage space is not greater than the storage space of the temporary storage partition, the data to be transferred in the non-temporary storage partition and the external storage space required for the data to be transferred are determined based on the priority score or priority level. Detect the first remaining external storage space of the external storage device; If the first remaining external storage space is less than the external storage space required for the data to be transferred, the external data to be deleted in the external storage device is determined based on the priority score or priority level of the file data in the external storage device. The data to be deleted externally is deleted, and the data to be transferred is transferred to the external storage device. The file data in the temporary storage partition is stored through the non-temporary storage partition.

[0012] Optionally, the step of storing the data to be stored in the temporary storage partition when the remaining temporary storage space is not less than the required storage space for the data to be stored includes: If the remaining temporary storage space is not less than the required storage space for the data to be stored, the data type of the data to be stored is detected. If the data type is a first data type, the step of storing the data to be stored in the temporary storage partition is performed; If the data type is the second data type, the step of detecting the second remaining external storage space of the external storage device is performed.

[0013] Optionally, when the remaining temporary storage space is not less than the required storage space for the data to be stored, detecting the data type of the data to be stored includes: If the remaining temporary storage space is not less than the required storage space for the data to be stored, detect the current operating status of the vehicle; When the current running state is non-dormant state, the step of detecting the data type of the data to be stored is executed; When the current operating state is a near-hibernation state between receiving a hibernation command and entering a hibernation state, hibernation storage data is determined based on the priority score or priority level of the file data in the temporary storage partition and the priority score or priority level of the file data in the external storage device. The hibernation storage data is transferred to the non-temporary storage partition.

[0014] Furthermore, to achieve the above objectives, the present invention also provides a vehicle, the vehicle comprising: a controller and an on-board host, wherein the built-in storage device within the on-board host is divided into a temporary storage partition and multiple non-temporary storage partitions, each storage partition including: an auxiliary data sub-partition, a normal data sub-partition, an important data sub-partition, and a core data sub-partition; the on-board host is connected to an external storage device; The controller is used to execute the vehicle host storage data scheduling method described in any of the above-mentioned methods.

[0015] This invention provides a method for scheduling data storage in a vehicle-mounted host and a vehicle. The method includes obtaining a priority score or priority level of file data stored in each data sub-partition; upon receiving data to be stored, obtaining the remaining storage space of the storage partition; if the remaining storage space is less than the required storage space for the data to be stored, determining the internal data to be deleted in each data sub-partition based on the priority score or priority level, and sending the internal data to be deleted to the user; upon receiving a deletion instruction from the user, deleting the internal data to be deleted, and dividing the data to be stored into auxiliary data, ordinary data, important data, and core data; and storing the auxiliary data, ordinary data, important data, and core data into their respective data sub-partitions. This invention obtains the priority score or priority level of the stored file data and deletes the internal data to be deleted based on the priority score or priority level when the remaining storage space is insufficient. It can intelligently filter low-priority data and guide users to delete it when space is insufficient. Furthermore, after dividing the data to be stored into different levels, it stores the data according to the corresponding data sub-partitions. This scheduling method can classify and store new data into the corresponding sub-partitions according to their importance, thereby maintaining the health of the storage space and improving the user experience. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0017] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the first embodiment of the vehicle-mounted host data scheduling method of the present invention; Figure 2 This is a schematic diagram of the built-in storage device of the vehicle-mounted host proposed in this invention; Figure 3 This is a schematic diagram of the first process of the second embodiment of the vehicle host storage data scheduling method of the present invention; Figure 4 This is a schematic diagram of the second process of the second embodiment of the vehicle host storage data scheduling method of the present invention; Figure 5 This is a schematic diagram of the third process of the second embodiment of the vehicle host storage data scheduling method of the present invention; Figure 6This is a schematic diagram of the first process of the third embodiment of the vehicle host storage data scheduling method of the present invention; Figure 7 This is a schematic diagram of the second process of the third embodiment of the vehicle host storage data scheduling method of the present invention; Figure 8 This is a schematic diagram of the third process of the third embodiment of the vehicle host storage data scheduling method of the present invention; Figure 9 This is a schematic diagram of the fourth process of the third embodiment of the vehicle host storage data scheduling method of the present invention; Figure 10 This is a fifth flowchart illustrating the third embodiment of the vehicle-mounted host data scheduling method of the present invention.

[0019] The objectives, features, and advantages of this invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of the present invention and are not intended to limit the present invention.

[0021] To better understand the technical solution of the present invention, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0022] Reference Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle-mounted host data scheduling method of the present invention. Based on Figure 1 The first embodiment of the vehicle-mounted host storage data scheduling method of the present invention is presented.

[0023] In this embodiment, the vehicle-mounted host storage data scheduling method is applied to the vehicle-mounted host, referring to... Figure 2 , Figure 2 This is a schematic diagram of the built-in storage device of the vehicle-mounted host proposed in this invention. The built-in storage device in the vehicle-mounted host includes multiple storage partitions, each of which includes: an auxiliary data sub-partition, a general data sub-partition, an important data sub-partition, and a core data sub-partition.

[0024] It's important to note that built-in storage devices are hardware devices within the vehicle's head unit used for persistent data storage. Built-in storage devices are typically divided into multiple logical partitions for storing system files, user data, etc. A storage partition is a logical area within the built-in storage device divided according to function or purpose. Each storage partition is further divided into multiple sub-partitions for storing data of different importance levels. The auxiliary data sub-partition is a sub-area within the storage partition used to store application auxiliary data. Auxiliary data refers to data that, once deleted, does not affect normal functionality and can be regenerated, such as temporary images during interface rendering or runtime debugging information. The ordinary data sub-partition is a sub-area within the storage partition used to store ordinary application data. Ordinary data refers to data that, once deleted, will affect functional smoothness but will not cause the application to malfunction, such as POI cache, map tile cache, and lyrics cache. The important data sub-partition is a sub-area within the storage partition used to store important application data. Important data refers to data that depends on user operations for generation and whose deletion will affect the user's personalized experience and application efficiency, such as user-favorited playlists, playback history, and custom settings. The core data sub-partition is a sub-area within the storage partition used to store core application data. Core data refers to data that, if deleted, would severely limit functionality or render the device unusable, and that users cannot easily regenerate. Examples include user account information, login credentials, license activation files, and offline map data.

[0025] The method for scheduling data stored in the vehicle host includes: Step S10: Obtain the priority score or priority level of the file data stored in each data sub-partition; It should be understood that in this embodiment and the following embodiments, the controller inside the vehicle can be used as the execution subject, and the controller can be connected to the vehicle host and the data receiving end.

[0026] It's important to note that the priority score is a comprehensive score used to quantify the importance of file data and its deletion priority. The priority level is a comprehensive ranking used to quantify the importance of file data and its deletion priority. File data priority levels can include: core data level, important data level, ordinary data level, and auxiliary data level. A lower priority score or priority level indicates less important data, which can be deleted first when storage space is insufficient. Similarly, a higher priority score or priority level indicates more important data; even when storage space is insufficient, data with higher priority scores or higher priority levels, such as core data or important data, is usually not deleted.

[0027] In practice, the controller can obtain the priority score or priority level of all file data stored in each data sub-partition. The priority score or priority level can be calculated and maintained periodically by the controller in the background. For example, the priority score can be determined daily or weekly based on attributes such as the file data's generation scenario, file type, and access frequency; the priority level can be determined based on the sub-partition where the file data is stored. The priority score and priority level can be recorded in the metadata of each file data.

[0028] Step S20: Upon receiving the data to be stored, obtain the remaining storage space of the storage partition; It should be noted that the data to be stored can be a new data file that is about to be written to the built-in storage, such as an upgrade package, application installation package, or videos or documents downloaded by the user. The data to be stored has a specific data type and a required storage space size. The remaining storage space can be the amount of unused available space in the current storage partition. In specific implementations, when the controller receives the data to be stored, it can immediately query the remaining storage space size of the current storage partition through the file system interface.

[0029] Step S30: If the remaining storage space is less than the required storage space for the data to be stored, determine the internal data to be deleted in each of the data sub-partitions based on the priority score or priority level, and send the internal data to be deleted to the user; It should be noted that the internal data to be deleted can be low-priority files recommended for deletion by the user based on priority scores or priority levels. This internal data may come from different data sub-partitions, and the system will aggregate its type and size for the user to view.

[0030] In practice, the controller compares the remaining storage space with the required storage space for the data to be stored. If the remaining storage space is greater than or equal to the required storage space, there is no need to delete the already stored file data, and the process proceeds directly to the next storage step. If the remaining storage space is less than the required storage space, the controller, based on a pre-calculated priority score or priority level, selects the file data with the lowest score from each data sub-partition, compiles this list into internal data to be deleted, and then displays the list of internal data to be deleted to the user in a pop-up window, prompting the user that there is insufficient space and suggesting that these low-priority data be deleted to free up space. The internal data to be deleted can be formed into a data table, which is displayed to the user. This data table can include information such as the name, type, sub-partition, size, and priority score or priority level of each file.

[0031] Step S40: Upon receiving a deletion instruction from the user, delete the internal data to be deleted, and divide the data to be stored into auxiliary data, ordinary data, important data, and core data; It should be noted that the delete command can be a confirmation action by the user in response to a system pop-up prompt, indicating agreement to delete the listed internal data to be deleted. The delete command can be issued by clicking the confirm delete button in the pop-up window or by using voice commands.

[0032] In practice, after sending the data to be deleted to the user, the controller waits for user feedback. If the user cancels the deletion, the deletion operation is not performed, and the storage request may fail or prompt the user to manage it manually. If the user confirms the deletion or ignores the pop-up window, indicating that the deletion instruction has been received, the deletion operation is executed immediately, completely removing the data to be deleted from the corresponding data sub-partition. After the data to be deleted is deleted, the controller classifies and identifies the data to be stored. Based on the source, purpose, and importance of the data to be stored, the controller divides it into four categories: auxiliary data, ordinary data, important data, and core data. For example, upgrade files within an upgrade package can be classified as core data, the size of the upgrade package can be classified as important data, the file format of the upgrade package can be classified as ordinary data, and the download time of the upgrade package can be classified as auxiliary data.

[0033] Step S50: Store the auxiliary data, the ordinary data, the important data, and the core data into their respective data sub-partitions.

[0034] Understandably, when the controller determines the auxiliary data, ordinary data, important data, and core data within the data to be stored, it can store the categorized data into corresponding data sub-partitions. Auxiliary data is stored in the auxiliary data sub-partition, ordinary data in the ordinary data sub-partition, important data in the important data sub-partition, and core data in the core data sub-partition. For example, the userdata partition of a vehicle's onboard host currently has 1.2GB of remaining space. At this time, a user remotely sends an FOTA upgrade package of 2.5GB via mobile phone. After receiving the data to be stored, the controller finds that the remaining space of 1.2GB is less than the required space of 2.5GB, and therefore retrieves files with lower priority scores or the lowest priority levels from each data sub-partition. After priority score comparison or priority level confirmation, the following 1.8GB of data, totaling 1.8GB, were selected as internal data to be deleted: old map tile cache from the navigation application (500MB, score 15), lyrics cache from online music (200MB, score 10), regular dashcam recordings from one month ago (800MB, score 8), and some application auxiliary data (300MB, score 5). The controller displayed a pop-up window stating, "Insufficient space. We recommend deleting the old map tile cache from the navigation application, lyrics cache from online music, regular dashcam recordings from one month ago, and some application auxiliary data to free up 1.8GB of space: Confirm deletion?" Whether the user clicks the "Confirm Delete" button or not, the controller can directly delete these files, freeing up 1.8GB of space and leaving 3.0GB of remaining storage space in the storage partition, meeting the 2.5GB requirement. Finally, the FOTA upgrade package was identified as core data and stored in the core data sub-partition. Simultaneously, temporary decompressed files generated during the upgrade process were identified as auxiliary data and stored in the auxiliary data sub-partition.

[0035] This embodiment provides a method for scheduling data storage in a vehicle-mounted host. The method includes obtaining priority scores or priority levels of file data stored in each data sub-partition; upon receiving data to be stored, obtaining the remaining storage space of the storage partition; if the remaining storage space is less than the required storage space for the data to be stored, determining the internal data to be deleted in each data sub-partition based on the priority scores or priority levels, and sending the internal data to be deleted to the user; upon receiving a deletion instruction from the user, deleting the internal data to be deleted, and dividing the data to be stored into auxiliary data, ordinary data, important data, and core data; and storing the auxiliary data, ordinary data, important data, and core data into their respective data sub-partitions. This invention obtains the priority score or priority level of the stored file data and deletes the internal data to be deleted based on the priority score or priority level when the remaining storage space is insufficient. It can intelligently filter low-priority data and guide users to delete it when space is insufficient. Furthermore, after dividing the data to be stored into different levels, it stores the data according to the corresponding data sub-partitions. This scheduling method can classify and store new data into the corresponding sub-partitions according to their importance, thereby maintaining the health of the storage space and improving the user experience.

[0036] Based on the first embodiment of the vehicle-mounted host storage data scheduling method of the present invention, a second embodiment of the vehicle-mounted host storage data scheduling method of the present invention is proposed. (Refer to...) Figure 3 , Figure 3 This is a schematic diagram of the first process of the second embodiment of the vehicle-mounted host data scheduling method of the present invention.

[0037] In this embodiment, step S10 includes: Step S11: Obtain the set of data tags for the file data stored in each data sub-partition.

[0038] It should be understood that the files stored in the vehicle's infotainment system are diverse in type and vary greatly in importance. Judging whether to delete files based on a single dimension could easily lead to the accidental deletion of critical data, resulting in impaired application functionality. Therefore, a multi-dimensional tagging system is needed to quantitatively score each file from multiple perspectives, and then obtain a comprehensive priority score through weighted summation to accurately assess the importance of each file at any given moment. Alternatively, the system can determine the sub-region where the file is stored based on its data tags, thereby determining the file's priority level and the importance of each file.

[0039] It should be noted that a data tag set is a collection of tags used to describe various attributes of file data. A data tag set typically contains multiple independent tags, each reflecting the characteristics of the data from a different dimension. For example, a data tag set may include tags such as storage time, data generation context, scenario score, access frequency, data acquisition method, regulatory relevance, associated file type, and the number of associated files.

[0040] In practice, when obtaining the priority score or priority level of file data stored in each data sub-partition, the controller can traverse each file and retrieve the data tag set corresponding to that file. The data tag set is typically stored along with the file data in the form of metadata, or maintained in a database table outside the file system, recording the tag information for each file. The controller reads the current state of each data tag for each file from this database table.

[0041] Step S12: Obtain the label weights and current label scores for each data label in the data label set.

[0042] It's important to note that a data tag is a single tag item within a set of data tags, and each data tag corresponds to a specific evaluation dimension. For example, the storage time tag measures how long file data remains on the storage device; the access frequency tag measures how many times file data has been accessed recently. Tag weight is the proportion of each data tag's weight in calculating the priority score. The sum of the tag weights is 1, and the weight of different tags reflects the degree of influence that dimension has on the importance of the data. For example, the regulatory relevance tag has a weight of 30%, indicating that regulatory-related data is extremely important; the scenario score tag has a weight of 20%, indicating that the data is relatively important in the current driving scenario; while the storage time tag has a weight of 10%, indicating that the influence of the time dimension is relatively small.

[0043] It's important to note that tag scores are quantified scores obtained by file data under a specific data tag according to preset rules. Tag scores typically reflect the specific importance of the file data within that tag dimension. For example, the scoring rules for the storage time tag are as follows: if the storage time is greater than 30 days, the storage time tag score is 1 point; if the storage time is greater than 7 days but less than 30 days, the storage time tag score is 3 points; and if the storage time is less than 7 days, the storage time tag score is 5 points. Furthermore, the tag score for the scenario scoring tag can be set based on the specific vehicle status and the importance level of the file data. For example, the tag score for a scenario using auxiliary data is 1 point, the tag score for a scenario using ordinary data is 5 points, the tag score for a scenario using important data is 10 points, and the tag score for a scenario using core data is 100 points. For example, when the vehicle is driving at high speed, the scene score of the online navigation data at the lane level and the map tile cache in the navigation system is set to 100 points, regardless of the importance level at which they are stored. Similarly, when the vehicle is in autonomous driving mode, the scene score of the sensor data and vehicle control data in the autonomous driving control process is set to 100 points, regardless of the importance level at which they are stored.

[0044] In practical implementation, the controller can directly obtain tag weights through extraction. Tag weights are pre-set fixed values ​​stored in the controller's non-volatile memory. For example, the tag weight for regulatory relevance is 20%, the weight for scenario score C is 20%, the weight for storage time A is 10%, the weight for data generation background B is 10%, the weight for access frequency D is 10%, the weight for data acquisition method E is 10%, the weight for associated file type G is 5%, and the weight for the number of associated files H is 5%. Tag scores, on the other hand, need to be dynamically calculated based on the current state of the file data. For example, for the storage time tag, the controller reads the file's creation time, calculates the difference in days between the current time and the creation time, and then determines the score according to the scoring rules. For the scenario score tag, the controller needs to combine the current vehicle driving status (such as vehicle speed, driving time, whether autonomous driving is enabled, etc.) and the application type to which the file belongs, and look up the scenario score at the current moment from the scenario score mapping table. For the regulatory relevance tag, the controller checks whether the file data involves regulatory requirements to determine its relevance.

[0045] Step S13: Calculate the priority score or priority level of the file data based on the tag weight and the tag score.

[0046] Understandably, the controller can calculate the priority score of the file data based on the acquired tag weights and corresponding tag scores, using a preset weighted summation. The formula for calculating the priority score is: Priority Score = WA SA+WB SB+……+WG SG+WH SH, where W represents the tag weight and S represents the tag score. The higher the calculated priority score, the more important the file data is and the less likely it is to be deleted; the lower the score, the less important the file data is and the more suitable it is to be deleted or moved.

[0047] For example, the file data is the historical search records of a navigation application, stored for 20 days. The tag score for data generated from user-generated videos or images is 4 points; the tag score for the vehicle currently traveling at high speed is 100 points; the tag score for accessing the data twice within 30 days is 2 points; the tag score for data acquired through application operation is 1 point; the tag score for data unrelated to regulations is 1 point; the tag score for associated file types being the same is 3 points; and the tag score for associated files being 1 is 1 point. The controller obtains the following tag weights: A=0.1, B=0.1, C=0.2, D=0.1, E=0.1, F=0.3, G=0.05, H=0.05. Tag scores: SA=3 points, SB=4 points, SC=100 points, SD=2 points, SE=1 point, SF=1 point, SG=3 points, SH=1 point. The calculated priority score is 31.6. If another file is a lyrics cache for online music, its priority score, calculated using the same method, is 2.8. Given the priority score for each file, its priority level can be determined by combining the score with the sub-partition where it's stored. For example, a file with a low priority score (e.g., ordinary data) but stored in a core data sub-partition can be considered important data.

[0048] Reference Figure 4 , Figure 4 This is a schematic diagram of the second process of a second embodiment of the vehicle-mounted host data scheduling method of the present invention. In this embodiment, after step S12, the method further includes: Step S14: Obtain the current driving status of the vehicle; It should be understood that the importance of file data is not static. For example, the scene data tags in the tag dataset change dynamically with the vehicle's driving status. For instance, when driving at high speeds, navigation map data and dashcam recordings are crucial, while online music cache and lyrics files are relatively less important. However, when the vehicle is idling or charging, the importance of entertainment data increases significantly, while the importance of navigation data decreases. Using a fixed tag score across all states would lead to inaccurate priority score calculations for file data. Therefore, it is necessary to adjust the tag scores of scene data tags in real time based on the vehicle's current driving status, making the priority assessment more aligned with the actual needs at hand, thus enabling precise choices when freeing up space. The criteria for judging the tag scores of other data tags in the tag dataset are relatively fixed and precise, and do not change with the vehicle's status.

[0049] It should be noted that the current driving status refers to the vehicle's current operating mode or condition. The current driving status is typically determined by a combination of signals including vehicle speed, driving time, ignition status, charging status, and autonomous driving activation status. For example, the current driving status may include: highway driving at speeds exceeding 30 km / h; long-distance travel exceeding one hour; autonomous driving mode; idling with the vehicle ignited and speed below 10 km / h for less than 5 minutes; camping mode with the vehicle ignited and speed below 10 km / h for more than 10 minutes; and charging status.

[0050] In practice, after obtaining the label weights corresponding to each data label and the label score at the current moment, the controller can further obtain the vehicle's current driving status. The controller obtains relevant signals from the vehicle speed sensor, ignition switch, charging status signal, navigation system, and autonomous driving controller through the vehicle bus to comprehensively determine the current driving status.

[0051] Step S15: Adjust the current time tag score of the scene data tags in the data tag set according to the current driving state; It should be noted that scenario data tags are labels within a data tag set used to reflect the importance of file data in the current driving scenario. Scenario data tags are a key dimension in priority score calculation, and their weight is usually high. The score of scenario data tags is dynamically adjusted according to the vehicle's driving status to reflect the changing importance of various application data in different scenarios.

[0052] In practical implementation, the controller can adjust the current-moment tag score of the scene data tags in the data tag set based on the current driving state. The core basis for adjustment is the scene score adjustment for various application data under different driving states. The adjusted scene score is determined based on the current driving state and the application type of the file data. For example, when the current driving state is high-speed driving, the scene score for all data from applications such as dashcams and navigation is adjusted to 100 points; while the scene score for all data from applications such as online music, online video, mini-programs, and remote conferencing is adjusted to 5 points. As another example, when the current driving state is long-term low-speed driving, the scene score for entertainment applications such as online music, online video, Bluetooth music, in-vehicle conferencing, and mini-programs is adjusted to 100 points; while the scene score for navigation data is adjusted to 10 points. Yet another example, when the current driving state is charging, the scene score for applications such as FOTA upgrades, upgrade center, and sentry mode is adjusted to 100 points; while the scene score for data such as online music, Bluetooth music, in-vehicle conferencing, mini-programs, and voice commands is adjusted to 1 point.

[0053] Step S16: Calculate the priority score or priority level of the file data based on the weight of each label, the adjusted label score of the scene data label, and the label scores of other labels.

[0054] It should be understood that after adjusting the scene data label scores, the controller uses the adjusted scene scores, combined with the current scores of other labels and their respective label weights, to recalculate the priority score of each file data according to the weighted summation formula, and then determines the priority level of each file data based on the priority scores and the sub-partitions where the file data is stored.

[0055] Reference Figure 5 , Figure 5 This is a schematic diagram of the third process of a second embodiment of the vehicle-mounted host storage data scheduling method of the present invention. In this embodiment, after step S10, the vehicle-mounted host storage data scheduling method further includes: Step S101: Obtain the user-set data cleanup cycle, the previous data cleanup time, and the current time.

[0056] It should be understood that the storage space of the vehicle's host is gradually occupied. If cleanup is only triggered when space is insufficient, users often face the problem of needing to delete data temporarily when they urgently need space. Furthermore, deleting a large amount of data at once may affect the user experience.

[0057] It's important to note that the data cleanup cycle is the time interval between two automatic cleanup operations set by the user through the vehicle settings interface. The data cleanup cycle can be set daily, weekly, or monthly, allowing users to choose based on their usage habits and storage space growth rate. For example, users who frequently download large files can choose weekly, while those with lower usage frequency can choose monthly. The previous data cleanup time can be the system timestamp recorded when the last scheduled cleanup operation was performed. After each scheduled cleanup, the controller records the current time as the previous data cleanup time in non-volatile memory for comparison with the current time.

[0058] In practice, the controller can obtain the data cleanup cycle set by the user through the vehicle settings interface, read the data cleanup time before the last periodic cleanup operation from the non-volatile memory, and obtain the current system time.

[0059] Step S102: If the time interval between the previous data cleanup time and the current time reaches the data cleanup cycle, detect the space health of the storage device.

[0060] It should be noted that space health is an inverse indicator of the proportion of used space to total space in the current storage device, usually expressed as a percentage of remaining space. For example, space health can be defined as: remaining space / total space × 100%, with a higher health rating indicating more abundant remaining space.

[0061] In practice, the controller can calculate the time interval between the previous data cleanup time and the current time. If the time interval has not yet reached the data cleanup cycle, the controller skips the current cleanup and waits for the next inspection. If the time interval has reached or exceeded the data cleanup cycle, the controller obtains the total and remaining space of the storage partition through the file system interface and calculates its health status.

[0062] Step S103: If the space health is less than the preset health, determine the internal data to be deleted in the storage partition based on the priority score or priority level, and send the internal data to be deleted to the user.

[0063] It's important to note that the preset health level is a threshold value corresponding to the difference between 1 and the proportion of currently used space. This preset health level can be set by the user or the system. When the actual health level falls below this threshold, a data cleanup operation is triggered. The preset health level can be adjusted by the user in the settings, for example, choosing 30%, 20%, or 10%. For instance, if the user sets the preset health level to 30%, it means that cleanup will be triggered when the remaining space is less than 30% of the total space, i.e., when the used space exceeds 70%.

[0064] In practice, the controller compares the calculated space health score with the user-defined preset health score. If the space health score is less than or equal to the preset health score, it indicates excessive space usage, requiring file data cleanup. If the space health score is greater than the preset health score, no file data cleanup is needed, and the controller records the inspection results and exits. If file data cleanup is determined to be necessary, the controller can filter out the lowest-scoring files from each data sub-partition based on their priority score or priority level, or filter out the lowest-priority files from each data sub-partition based on their priority level. This data is then compiled into a list of files to be deleted and sent to the user, prompting them that the current storage space usage is high and suggesting the deletion of the following low-priority data to free up space. The user is then asked to confirm the deletion.

[0065] Step S104: Upon receiving a deletion instruction from the user, delete the internal data to be deleted.

[0066] It should be understood that after sending the internal data to be deleted to the user, the controller can continuously monitor user feedback. If the user chooses to cancel deletion, the deletion operation will not be performed. If the user selects to confirm deletion or ignore the pop-up window, i.e., the deletion instruction has been received from the user, all files in the internal data list to be deleted will be completely removed from the corresponding data sub-partitions. After deletion is completed, the controller records the current time as the previous data cleanup time for use in the next inspection. For example, if the user sets the data cleanup cycle to weekly and the preset health level to 30%, and the last cleanup time was Saturday at 10:00 AM, then at 10:00 AM the following Saturday, the controller detects that the time interval is exactly 7 days, and begins to check the space health of the storage devices. If the space health level is below 30%, the controller selects the files with the lowest priority score or the lowest priority level from each data sub-partition, and after user confirmation, immediately deletes these files to increase the remaining storage space and improve the health level.

[0067] Based on the first or second embodiment of the vehicle-mounted host storage data scheduling method proposed in this invention, a third embodiment of the vehicle-mounted host storage data scheduling method of this invention is proposed. (Refer to...) Figure 6 , Figure 6 This is a schematic diagram of the first process of the third embodiment of the vehicle-mounted host data scheduling method of the present invention.

[0068] In this embodiment, the built-in storage device is divided into a temporary storage partition and multiple non-temporary storage partitions, and the vehicle host is also connected to an external storage device.

[0069] It should be understood that the built-in storage space of the vehicle's infotainment system is limited. When large files need to be stored, even deleting low-priority data may not meet the space requirements. Indiscriminately deleting user data may affect important functions.

[0070] The on-board host storage data scheduling method further includes: Step S21: Upon receiving data to be stored, detect the remaining temporary storage space of the temporary storage partition; It's important to note that the temporary storage partition is a special area within the built-in storage device used to temporarily store new data generated during the current vehicle usage scenario. The size of the temporary storage partition can be set as a percentage of the total built-in storage capacity. Before the vehicle goes into sleep mode, the data in the temporary storage partition will be re-evaluated based on priority scores or priority levels. Important data will be moved to non-temporary storage partitions, while low-priority data will be moved to external storage or deleted. The remaining temporary storage space represents the amount of remaining storage space within the temporary storage partition that can still store file data.

[0071] In practice, when the controller receives data to be stored, it first checks the remaining temporary storage space in the temporary storage partition. If the remaining temporary storage space is greater than or equal to the required storage space for the data to be stored, the data to be stored is directly stored in the temporary storage partition for initial storage.

[0072] Step S22: If the remaining temporary storage space is less than the required storage space for the data to be stored, detect the remaining non-temporary storage space of the non-temporary storage partition; It should be noted that a non-temporary storage partition can be a regular storage area within an internal storage device, excluding temporary storage partitions, used for long-term storage of user data. A non-temporary storage partition contains four sub-partitions: auxiliary data, general data, important data, and core data. The remaining non-temporary storage space represents the amount of remaining storage space within the non-temporary storage partition that can still store file data. If the remaining temporary storage space in the temporary storage partition is insufficient, data to be stored can also be stored in the non-temporary storage partition.

[0073] In practice, if the remaining temporary storage space is less than the required storage space, the controller further checks the remaining non-temporary storage space in the non-temporary storage partition. If the remaining non-temporary storage space is greater than or equal to the required storage space, the data to be stored is directly stored in the non-temporary storage partition.

[0074] Step S23: If the remaining non-temporary storage space is less than the required storage space for the data to be stored, detect the data type of the data to be stored; It should be noted that the data type to be stored can include: a first data type that cannot be stored in external storage devices and a second data type that can be stored in external storage devices. The first data type includes secure file data that requires fast retrieval, etc.

[0075] It should be understood that the remaining non-temporary storage space in the non-temporary storage partition may also be insufficient to accommodate the data to be stored. In this case, it is necessary to determine the data type of the data to be stored, and then determine whether the data can be stored in an external storage device. In specific implementations, the data type of the data to be stored can be determined based on the urgency of the data to be executed or the importance of the data. For example, if the data to be stored is a repair kit for a vehicle, then the data to be stored is the first type of data that needs to be executed immediately and should be stored in the internal storage device.

[0076] Step S24: If the data type is the first data type, determine the non-temporary data to be transferred in the non-temporary storage partition and the external storage space required for the non-temporary data to be transferred based on the priority score or priority level.

[0077] It should be noted that the first data type can be a classification of the data to be stored, indicating that the data should be preferentially stored in the non-temporary storage partition of the built-in storage. The first data type typically includes data with high read / write speed requirements or requiring immediate access, such as FOTA upgrade packages, currently used navigation map data, and documents being edited by the user. The non-temporary data to be transferred refers to low-priority file data in the non-temporary storage partition, selected based on priority scores or priority levels, that needs to be moved to external storage devices to free up space. The non-temporary data to be transferred typically includes data with low access frequency, low timeliness requirements, but is not suitable for direct deletion. The external storage space required for the non-temporary data to be transferred refers to the storage space required when the non-temporary data is transferred to an external storage device.

[0078] In practice, if the remaining non-temporary storage space is also less than the required storage space, the controller detects the data type of the data to be stored. If the data type is the primary data type, which needs to be stored in the built-in storage device first, the controller filters out the non-temporary data to be transferred from low to high based on the priority score or priority level of each file data in the non-temporary storage partition, and calculates the external storage space required for this non-temporary data to be transferred.

[0079] Step S25: Detect the first remaining external storage space of the external storage device; It should be noted that external storage devices are pluggable external storage devices, such as SD cards, USB flash drives, or portable hard drives. External storage devices connect to the vehicle's head unit via interfaces such as SD card slots or USB ports to expand available storage space. The read and write speeds of external storage devices are typically lower than those of internal storage, making them suitable for storing data with infrequent access. The first remaining external storage space refers to the amount of remaining available storage space on the external storage device when data to be transferred needs to be moved from the non-temporary storage partition.

[0080] In practice, the controller detects the remaining external storage space of the external storage device. If the remaining external storage space is greater than or equal to the external storage space required for the non-temporary data to be transferred, the non-temporary data to be transferred is directly moved from the non-temporary storage partition to the external storage device, and then the data to be stored is stored in the non-temporary storage partition.

[0081] Step S26: If the first remaining external storage space is less than the external storage space required for the non-temporary data to be transferred, determine the external data to be deleted in the external storage device based on the priority score or priority level of the file data in the external storage device. It should be noted that the external data to be deleted can be low-priority file data in external storage devices that are filtered based on priority scores or priority levels and need to be deleted to make room for transferred data from internal storage.

[0082] In practice, if the first remaining external storage space is less than the external storage space required for the non-temporary data to be transferred, the controller further evaluates the priority of the file data in the external storage device and filters out the external data to be deleted from low to high based on the priority score or priority level.

[0083] Step S27: Delete the data to be deleted externally, transfer the non-temporary data to be transferred to the external storage device, and store the data to be stored in the non-temporary storage partition.

[0084] It should be understood that when the controller determines that external data to be deleted, it can directly delete this external data to free up space on the external storage device. After deletion, it checks again whether the first remaining external storage space is sufficient. If it is sufficient, the non-temporary data to be transferred is moved to the external storage device, and then the data to be stored is stored in the non-temporary storage partition.

[0085] In this embodiment, the built-in storage is divided into temporary storage partitions and non-temporary storage partitions. When the non-temporary storage partition is insufficient, low-priority data is transferred to external storage devices instead of being directly deleted. If the external storage devices are also full, even lower-priority data is further deleted from the external storage. This satisfies the need for temporary large-capacity storage while maximizing the retention of user data.

[0086] Reference Figure 7 , Figure 7 This is a schematic diagram of the second process of the third embodiment of the vehicle-mounted host data scheduling method of the present invention.

[0087] In this embodiment, after step S23, the method further includes: Step S28: If the data type is the second data type, detect the second remaining external storage space of the external storage device; the priority of the second data type is lower than the priority of the first data type.

[0088] It should be understood that not all data to be stored needs to be prioritized for storage in the fast internal storage. Some data does not require high access speed, such as downloaded offline music files, cached videos that have been watched, and application installation package backups. These can be stored in external storage devices to avoid running out of storage space when the internal storage device is insufficient.

[0089] It should be noted that the second data type refers to data types that can be directly stored on external storage devices without occupying internal storage space. The second data type has lower priority than the first data type and typically includes data with low read / write speed requirements, low access frequency, or acceptable slower response times. Examples include offline music files downloaded from the public network, cached online videos already watched, backups of historical application installation packages, and user manual PDF files. The second remaining external storage space refers to the amount of remaining available storage space on the external storage device when it needs to directly store the data to be stored.

[0090] In practical implementation, considering that the external storage device may already contain a large amount of file data, leading to insufficient second remaining external storage space, this embodiment also requires detection of the second remaining external storage space of the external storage device. The controller can determine the data type of the data to be stored after receiving it. If the data type is the second data type, the second remaining external storage space of the external storage device is detected, i.e., the available space size of the external storage device is queried through the file system interface. If the second remaining external storage space is greater than or equal to the required storage space of the data to be stored, the controller directly writes the data to be stored into the external storage device for storage.

[0091] Step S29: If the second remaining external storage space is less than the external storage space required by the data to be stored, determine the external data to be deleted in the external storage device.

[0092] It should be understood that if the second remaining external storage space is less than the required storage space for the data to be stored, the controller needs to free up space in the external storage device. The controller obtains the priority score or priority level of all file data in the external storage device. Subsequently, the controller filters the external data to be deleted from low to high based on the priority score or priority level until the total size of the filtered files is greater than or equal to the space gap required for the data to be stored.

[0093] Step S210: Delete the data to be deleted externally and store the data to be stored in the external storage device.

[0094] It should be understood that, upon determining that data needs to be deleted externally, the controller can completely remove the selected data from the external storage device. After deletion, the controller re-checks the remaining external storage space to confirm that it meets the storage requirements of the data to be stored. Finally, the data to be stored is written to the external storage device.

[0095] In this way, the second data type directly utilizes external storage space, avoiding both the use of internal storage resources and the complex data migration operations within internal storage. Furthermore, when external storage space is insufficient, low-priority data is deleted to meet the demand. This avoids consuming valuable internal storage resources, simplifies the processing flow, and improves storage efficiency.

[0096] Reference Figure 8 , Figure 8 This is a schematic diagram of the third process of the third embodiment of the vehicle-mounted host data scheduling method of the present invention.

[0097] In this embodiment, after step S21, the method further includes: Step S211: If the remaining temporary storage space is not less than the required storage space for the data to be stored, store the data to be stored in the temporary storage partition; It should be noted that if the remaining temporary storage space is not less than the required storage space for the data to be stored, it means that the temporary storage partition can directly store the data to be stored, and the data to be stored can be directly sent to the temporary storage partition for storage.

[0098] In practice, after receiving the data to be stored, the controller can check the remaining temporary storage space in the temporary storage partition. If the remaining temporary storage space is not less than the required storage space for the data to be stored, the controller will directly write the data to be stored into the temporary storage partition for temporary storage.

[0099] Step S212: Detect the remaining non-temporary storage space of the non-temporary storage partition storing the data to be stored.

[0100] It should be understood that temporary storage partitions are used to temporarily store newly generated data during vehicle operation, but this data ultimately needs to be migrated to non-temporary storage partitions for long-term storage before the vehicle goes into hibernation. If the non-temporary storage partitions do not have enough remaining space, they cannot receive data from the temporary storage partitions, causing data to accumulate in the temporary partitions and affecting the writing of subsequent new data.

[0101] Therefore, in this embodiment, it is also necessary to promptly assess the space status of the non-temporary partition after storing the data to be stored in the temporary partition. If the remaining space in the non-temporary partition is insufficient to accommodate the data in the temporary partition, the low-priority data in the non-temporary partition is transferred to external storage in advance, thereby freeing up space for the non-temporary partition, ensuring that the data in the temporary partition can be migrated smoothly, and maintaining the smooth flow of the entire storage system.

[0102] In practice, the controller can detect the remaining non-temporary storage space in the non-temporary storage partition. The controller compares the remaining non-temporary storage space with the total storage space of the temporary storage partition. If the remaining non-temporary storage space is greater than the storage space of the temporary storage partition, it means that the non-temporary partition has enough space to accommodate the data in the temporary partition, and no additional processing is required. The data can then be migrated normally before the vehicle goes into sleep mode.

[0103] Step S213: If the remaining non-temporary storage space is not greater than the storage space of the temporary storage partition, determine the data to be transferred in the non-temporary storage partition and the external storage space required for the data to be transferred based on the priority score or priority level. It should be noted that the data to be transferred refers to low-priority files in the non-temporary storage partition that have been selected based on priority scores or priority levels and need to be moved to external storage devices to free up space. The term "data to be transferred" has the same meaning as "non-temporary data to be transferred"—data that needs to be moved to make room for data in the temporary storage partition.

[0104] In practice, if the remaining non-temporary storage space is no greater than the storage space of the temporary storage partition, the controller needs to allocate space for the non-temporary partition in advance. Based on the priority score or priority level of each file data in the non-temporary storage partition, the controller filters out the data to be transferred from low to high and calculates the external storage space required for this data to be transferred.

[0105] Step S214: Detect the first remaining external storage space of the external storage device; It should be understood that, in order to ensure that the data to be transferred can be successfully transmitted to the external storage device for storage, that is, the remaining storage space of the external storage device can accommodate the data to be transferred, in this embodiment, the controller can also detect the first remaining external storage space of the external storage device. If the first remaining external storage space is greater than or equal to the external storage space required by the data to be transferred, the data to be transferred is directly moved from the non-temporary storage partition to the external storage device, thereby freeing up the space in the non-temporary partition.

[0106] Step S215: If the first remaining external storage space is less than the external storage space required for the data to be transferred, determine the external data to be deleted in the external storage device based on the priority score or priority level of the file data in the external storage device. It should be understood that if the initial remaining external storage space is less than the external storage space required for the data to be transferred, it indicates that the remaining external storage space of the external storage device is insufficient to store the data to be transferred. Further priority evaluation of the file data in the external storage device is needed. Based on priority scores or priority levels, data to be deleted is selected from low to high and then deleted to free up space. After deletion, the initial remaining external storage space is checked again to see if it is sufficient. If it is sufficient, the data to be transferred is moved to the external storage device.

[0107] Step S216: Delete the data to be deleted externally, transfer the data to be transferred to the external storage device, and store the file data in the temporary storage partition through the non-temporary storage partition.

[0108] Understandably, when deleting data to be externally deleted, the data to be transferred within the non-temporary storage partition can be moved to an external storage device, thus expanding the remaining space in the non-temporary storage partition. The controller can migrate file data from the temporary storage partition, including recently added data to be stored and other temporary data, to the non-temporary storage partition, storing it according to its data type into corresponding auxiliary data, ordinary data, important data, or core data sub-partitions. At this point, the temporary storage partition is cleared and can continue to receive new data.

[0109] Reference Figure 9 , Figure 9 This is a schematic diagram of the fourth process of the third embodiment of the vehicle-mounted host data scheduling method of the present invention.

[0110] In this embodiment, step S211 includes: Step S2111: If the remaining temporary storage space is not less than the required storage space for the data to be stored, detect the data type of the data to be stored; It should be understood that temporary storage partitions are used to temporarily store newly generated data during vehicle operation, but not all new data should be stored in the temporary partition. Data of the primary data type, which has high read / write speed requirements, should be preferentially stored in the internal storage, while data of the secondary data type, which has lower speed requirements, is more suitable for direct storage in external storage. Storing all data indiscriminately in the temporary partition may cause it to fill up prematurely, affecting the writing of subsequent important data and increasing the burden of data preparation before hibernation.

[0111] In practice, after determining that the remaining temporary storage space is not less than the required storage space for the data to be stored, the controller first detects the data type of the data to be stored. The controller determines whether the data belongs to a primary or secondary data type based on information such as its source, file attributes, or user tags. For example, FOTA upgrade packages, currently used navigation map data, and documents being edited by the user can be classified as primary data types; offline music files downloaded by the user from the public network, cached videos that have been viewed, and backups of historical application installation packages can be classified as secondary data types.

[0112] Therefore, even when there is sufficient temporary storage space, it is necessary to first determine the data type of the data to be stored and then decide the storage path based on the type: the first data type is stored in the temporary partition, and the second data type is directly stored in the external storage device, thereby achieving a reasonable allocation of storage resources.

[0113] Step S2112: If the data type is the first data type, perform the step of storing the data to be stored to the temporary storage partition.

[0114] Understandably, if the data to be stored is of type 1, the controller will store the data to a temporary storage partition. For example, it will write file data to a free area of ​​the temporary storage partition and record the file's metadata information, such as its source, timestamp, and data type. Then, it will perform the steps to transfer the file data from the temporary storage partition to a non-temporary storage partition. The controller will...

[0115] Step S2113: If the data type is the second data type, perform the step of detecting the second remaining external storage space of the external storage device.

[0116] Understandably, if the data to be stored is of the second data type, the controller will not store the data in the temporary storage partition. Instead, it will check the second remaining external storage space of the external storage device. If the second remaining external storage space is sufficient, the data to be stored will be directly stored in the external storage device. If the second remaining external storage space is insufficient, the controller can delete the file data with the lower priority score in the external storage space, release the external storage device, and store the data to be stored in the external storage device after the space is released.

[0117] This categorized storage strategy allows data of the first type to leverage the high-speed read / write capabilities of the built-in storage, ensuring the responsiveness of critical applications. Data of the second type is directly offloaded to external storage, saving valuable space in the built-in storage and reducing the workload of data preparation before hibernation.

[0118] Reference Figure 10 , Figure 10 This is a schematic diagram of the fifth process of the third embodiment of the vehicle-mounted host storage data scheduling method of the present invention. In this embodiment, step S2111 includes: Step S201: If the remaining temporary storage space is not less than the required storage space for the data to be stored, detect the current operating status of the vehicle.

[0119] It should be understood that during vehicle operation, the temporary storage partition continuously receives newly generated data, but not all of this data needs to be permanently stored in the internal storage. Before the vehicle enters sleep mode, the system has a relatively idle time window, which is the best time to conduct a comprehensive priority assessment and reorganization of the data in the temporary storage partition and external storage devices. By migrating high-priority data to a non-temporary storage partition for permanent storage, and keeping low-priority data in external storage devices or deleting it, the storage layout can be effectively optimized. This ensures that critical data remains in the faster internal storage, while preventing data accumulation in the temporary partition from affecting subsequent use.

[0120] It should be noted that the current operating state can include hibernation, near-hibernation, and non-hibernation. A non-hibernation state means the vehicle is running or ready to run, such as while driving, idling, charging, or in autonomous driving mode. In a non-hibernation state, system resources are primarily used for current driving and entertainment functions, and large-scale data processing is not suitable; therefore, only simple data type checks and storage operations are performed. A near-hibernation state is the state before the vehicle is powered off or enters a low-power mode, typically corresponding to the stage where the vehicle is turned off, the doors are locked, and the system is preparing to hibernate. The near-hibernation state provides a relatively idle time window, suitable for performing background tasks such as data processing, migration, and priority reassessment. A hibernation state is the state where the vehicle has already been powered off or entered a low-power mode, typically corresponding to the stage where the vehicle is turned off, the doors are locked, and the system is in hibernation mode.

[0121] During the specific testing process, the controller can obtain signals such as the vehicle's ignition status, speed, gear position, and charging status through the vehicle bus to comprehensively determine whether the vehicle is currently in a non-dormant state or a dormant state.

[0122] Step S202: When the current running state is non-dormant state, perform the step of detecting the data type of the data to be stored.

[0123] It should be understood that if the current operating state is non-dormant, such as when the vehicle is in motion or idling, the controller will perform the step of detecting the data type of the data to be stored, that is, determining whether the data to be stored belongs to the first data type or the second data type, and storing it according to the corresponding storage path, that is, the first data type is stored in the temporary storage partition, and the second data type is stored in the external storage device.

[0124] Step S203: When the current running state is a near-hibernation state before receiving a hibernation command but entering hibernation state, determine hibernation storage data based on the priority score or priority level of the file data in the temporary storage partition and the priority score or priority level of the file data in the external storage device.

[0125] It should be noted that hibernation storage data can be data that, nearing hibernation, is selected based on the priority score or priority level of all files in the temporary storage partition and external storage devices, and needs to be migrated to a non-temporary storage partition for permanent storage. Hibernation storage data typically includes files with high priority scores or priority levels, such as important video recordings generated during the current driving process, important data actively downloaded by the user, and core application data.

[0126] In practice, if the current operating state is nearing hibernation, the controller does not perform data type judgment but instead initiates the data preparation process before hibernation. First, it obtains the priority scores or priority levels of all file data in the temporary storage partition and the external storage device. Then, based on these priority scores or priority levels, it filters out data with higher scores or those at the core data level or important data level—that is, data that needs to be permanently retained—to form the hibernation storage data. The filtering rules can be: data with a priority score higher than a preset threshold (e.g., 50 points), or data with a priority level belonging to the core data level or important data level.

[0127] Step S204: Transfer the hibernation storage data to the non-temporary storage partition.

[0128] Understandably, the controller will transfer the selected hibernation storage data from the temporary storage partition and external storage devices to the corresponding sub-partitions of the non-temporary storage partition. For example, core data will be stored in the core data sub-partition, and important data will be stored in the important data sub-partition. After the transfer is complete, the controller can clear the temporary storage partition to prepare for the next vehicle operation. Meanwhile, low-priority data that was not selected in the external storage devices can remain in the external storage or be deleted depending on space availability. Once these steps are completed, the vehicle can officially enter hibernation mode. Through this near-dormant state cleanup mechanism, the system can automatically archive and optimize data without affecting normal user operation, ensuring that the built-in storage space always remains in a healthy state.

[0129] It should be noted that the above examples are only for understanding the present invention and do not constitute a limitation on the vehicle host storage data scheduling method of the present invention. Any simple modifications based on this technical concept are within the protection scope of the present invention.

[0130] In addition, to achieve the above objectives, the present invention also provides a vehicle, a controller, and an in-vehicle host. The built-in storage device in the in-vehicle host is divided into a temporary storage partition and multiple non-temporary storage partitions. Each storage partition includes: an auxiliary data sub-partition, a normal data sub-partition, an important data sub-partition, and a core data sub-partition. The in-vehicle host is connected to an external storage device. The controller is used to execute the vehicle host storage data scheduling method described in any of the above embodiments.

[0131] The above description is only a part of the embodiments of the present invention and does not limit the patent scope of the present invention. All equivalent structural transformations made under the technical concept of the present invention using the contents of the present invention specification and drawings, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.

Claims

1. A method for scheduling data stored in a vehicle-mounted host, characterized in that, The device is applied to an in-vehicle host, and the built-in storage device in the in-vehicle host includes: multiple storage partitions, each of which includes: an auxiliary data sub-partition, a normal data sub-partition, an important data sub-partition, and a core data sub-partition; The method for scheduling data stored in the vehicle host includes: Obtain the priority score or priority level of the file data stored in each data sub-partition; Upon receiving data to be stored, obtain the remaining storage space of the storage partition; If the remaining storage space is less than the required storage space for the data to be stored, the internal data to be deleted in each of the data sub-partitions is determined based on the priority score or priority level, and the internal data to be deleted is sent to the user. Upon receiving a deletion command from a user, the internal data to be deleted is deleted, and the data to be stored is divided into auxiliary data, ordinary data, important data, and core data. The auxiliary data, the ordinary data, the important data, and the core data are stored in their respective data sub-partitions.

2. The vehicle-mounted host storage data scheduling method as described in claim 1, characterized in that, The process of obtaining the priority score or priority level of the file data stored in each data sub-partition includes: Retrieve the set of data tags for the file data stored in each data sub-partition; Obtain the label weights and current label scores for each data label within the data label set; The priority score or priority level of the file data is calculated based on the tag weight and the tag score.

3. The vehicle-mounted host data scheduling method as described in claim 2, characterized in that, After obtaining the label weights corresponding to each data label in the data label set and the label scores at the current time, the method further includes: Obtain the vehicle's current driving status; Adjust the current time-based label score of the scene data labels in the data label set according to the current driving state; The priority score or priority level of the file data is calculated based on the weight of each label, the adjusted label score of the scene data label, and the label scores of other labels.

4. The vehicle-mounted host data scheduling method as described in claim 3, characterized in that, The on-board host storage data scheduling method further includes: Get the user-set data cleanup cycle, the previous data cleanup time, and the current time; If the time interval between the previous data cleanup time and the current time reaches the data cleanup cycle, the space health of the storage device is detected; If the space health is less than the preset health, the internal data to be deleted in the storage partition is determined based on the priority score or priority level, and the internal data to be deleted is sent to the user. Upon receiving a deletion command from the user, the internal data to be deleted is deleted.

5. The vehicle-mounted host data scheduling method as described in any one of claims 1 to 4, characterized in that, The built-in storage device is divided into a temporary storage partition and multiple non-temporary storage partitions, and the vehicle host is also connected to an external storage device. The on-board host storage data scheduling method further includes: Upon receiving data to be stored, the remaining temporary storage space of the temporary storage partition is checked; If the remaining temporary storage space is less than the required storage space for the data to be stored, detect the remaining non-temporary storage space of the non-temporary storage partition; If the remaining non-temporary storage space is less than the required storage space for the data to be stored, the data type of the data to be stored is detected. When the data type is the first data type, the non-temporary data to be transferred in the non-temporary storage partition and the external storage space required for the non-temporary data to be transferred are determined based on the priority score or priority level. Detect the first remaining external storage space of the external storage device; If the remaining external storage space is less than the external storage space required for the non-temporary data to be transferred, the external data to be deleted in the external storage device is determined based on the priority score or priority level of the file data in the external storage device. Delete the data to be deleted externally, transfer the non-temporary data to be transferred to the external storage device, and store the data to be stored in the non-temporary storage partition.

6. The vehicle-mounted host storage data scheduling method as described in claim 5, characterized in that, The on-board host storage data scheduling method further includes: When the data type is the second data type, the second remaining external storage space of the external storage device is detected; the priority of the second data type is lower than the priority of the first data type. If the second remaining external storage space is less than the external storage space required for the data to be stored, the external data to be deleted in the external storage device is determined. Delete the data to be deleted externally, and store the data to be stored in the external storage device.

7. The vehicle-mounted host storage data scheduling method as described in claim 6, characterized in that, The on-board host storage data scheduling method further includes: If the remaining temporary storage space is not less than the required storage space for the data to be stored, the data to be stored will be stored in the temporary storage partition. Detect the remaining non-temporary storage space of the non-temporary storage partition storing the data to be stored; If the remaining non-temporary storage space is not greater than the storage space of the temporary storage partition, the data to be transferred in the non-temporary storage partition and the external storage space required for the data to be transferred are determined based on the priority score or priority level. Detect the first remaining external storage space of the external storage device; If the first remaining external storage space is less than the external storage space required for the data to be transferred, the external data to be deleted in the external storage device is determined based on the priority score or priority level of the file data in the external storage device. The data to be deleted externally is deleted, and the data to be transferred is transferred to the external storage device. The file data in the temporary storage partition is stored through the non-temporary storage partition.

8. The vehicle-mounted host storage data scheduling method as described in claim 7, characterized in that, The step of storing the data to be stored in the temporary storage partition when the remaining temporary storage space is not less than the required storage space for the data to be stored includes: If the remaining temporary storage space is not less than the required storage space for the data to be stored, the data type of the data to be stored is detected. If the data type is a first data type, the step of storing the data to be stored in the temporary storage partition is performed; If the data type is the second data type, the step of detecting the second remaining external storage space of the external storage device is performed.

9. The vehicle-mounted host storage data scheduling method as described in claim 8, characterized in that, When the remaining temporary storage space is not less than the required storage space for the data to be stored, detecting the data type of the data to be stored includes: If the remaining temporary storage space is not less than the required storage space for the data to be stored, detect the current operating status of the vehicle; When the current running state is non-dormant state, the step of detecting the data type of the data to be stored is executed; When the current operating state is a near-hibernation state between receiving a hibernation command and entering a hibernation state, hibernation storage data is determined based on the priority score or priority level of the file data in the temporary storage partition and the priority score or priority level of the file data in the external storage device. The hibernation storage data is transferred to the non-temporary storage partition.

10. A vehicle, characterized in that, The vehicle includes a controller and an on-board host. The built-in storage device in the on-board host is divided into a temporary storage partition and multiple non-temporary storage partitions. Each storage partition includes an auxiliary data sub-partition, a normal data sub-partition, an important data sub-partition, and a core data sub-partition. The on-board host is connected to an external storage device. The controller is used to execute the vehicle host storage data scheduling method according to any one of claims 1 to 9.

Images