Vehicle machine cache management method and related device

Abstract

The application discloses a car machine cache management method and related equipment, and relates to the field of vehicle electronics and control, and mainly aims to solve the problem that the existing car machine cache cleaning method is poor in adaptability and needs manual intervention. The method comprises the following steps: detecting the current driving scene of the target vehicle and the cache occupancy rate of the car machine, wherein different driving scene states correspond to different cache cleaning strategies; in the case that the cache occupancy rate is greater than a trigger threshold, determining a low-priority cache file based on the cache cleaning strategy corresponding to the current driving scene, wherein the low-priority cache file is marked to a pre-release pool; in the case that the cache occupancy rate is greater than an execution threshold, deleting the low-priority cache file from the pre-release pool, wherein the execution threshold is greater than the trigger threshold.

Description

Technical Field

[0001] This invention relates to the field of vehicle electronics and control, and in particular to a vehicle infotainment system cache management method and related equipment. Background Technology

[0002] With the development of intelligent connected vehicles, the functions of in-vehicle systems are becoming increasingly complex, and the amount of cached data generated during operation is surging, posing a challenge to the management of the limited storage space of the in-vehicle system. Existing mainstream in-vehicle system cache management methods mainly suffer from two representative shortcomings: First, there is the threshold-triggered automatic cleanup mechanism, which allocates a fixed cache space to applications and clears old caches in order of file creation time when the occupied space exceeds a preset threshold. Second, there is the manual identification cleanup mechanism, which does not have an automatic cleanup function but instead displays the cache size through application icons, requiring users to manually operate by long-pressing the icon. In summary, existing in-vehicle system cache management technologies, limited by their fixed cleanup strategies or reliance on manual operation, are unable to meet the core needs of intelligent vehicles for scene perception and automated management. Summary of the Invention

[0003] In view of the above problems, the present invention provides a vehicle infotainment system cache management method and related equipment, the main purpose of which is to solve the problems of poor adaptability and the need for manual intervention in existing vehicle infotainment system cache clearing methods.

[0004] To address at least one of the aforementioned technical problems, in a first aspect, the present invention provides a vehicle infotainment system cache management method, the method comprising: The current driving scenario of the target vehicle and the cache usage rate of the vehicle system are detected, wherein different driving scenario states correspond to different cache clearing strategies; If the cache occupancy rate is greater than the trigger threshold, low-priority cache files are determined based on the cache cleanup strategy corresponding to the current driving scenario, wherein the low-priority cache files are marked to the pre-release pool; If the cache occupancy rate is greater than the execution threshold, the low-priority cache file is deleted from the pre-release pool, wherein the execution threshold is greater than the trigger threshold.

[0005] Optionally, detecting the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle's infotainment system includes: The driving status, navigation application status, and entertainment application status of the target vehicle are detected. The driving status is determined based on the current vehicle speed and changes in GPS latitude and longitude data, and the entertainment application status is determined based on changes in the data usage of the entertainment program. The current driving scenario of the target vehicle is determined based on the driving status, the navigation application status, and the entertainment application status.

[0006] Optionally, determining the current driving scenario of the target vehicle based on the driving state, the navigation application state, and the entertainment application state includes: When navigation is in use and entertainment is not in use, the current driving scenario of the target vehicle is determined to be the navigation scenario; When entertainment is enabled and navigation is disabled, the current driving scenario of the target vehicle is determined to be an entertainment scenario. When navigation and entertainment are both not in use, the current driving scenario of the target vehicle is determined to be an idle scenario; With both navigation and entertainment applications active, the current driving scenario of the target vehicle is determined based on the driving status, including: When the target vehicle is in the driving state, the current driving scenario of the target vehicle is determined to be a navigation-priority coexistence scenario; If the target vehicle is not in the driving state, the current driving scenario of the target vehicle is determined to be an entertainment-priority coexistence scenario.

[0007] Optionally, detecting the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle's infotainment system includes: Obtain the total cache space capacity and used cache amount of the vehicle's infotainment system; The cache utilization rate is determined based on the total cache space capacity and the amount of cache already used.

[0008] Optionally, when the cache occupancy rate is greater than the trigger threshold, determining low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario includes: If the current driving scenario is either the navigation scenario or the navigation priority coexistence scenario, the non-navigation cache file is determined to be a low-priority cache file; If the current driving scenario is the entertainment scenario or the entertainment-first coexistence scenario, the non-entertainment cache file is determined to be a low-priority cache file; If the current driving scenario is an idle scenario, all cached files are determined to be low-priority cached files.

[0009] Optionally, determining all cached files as low-priority cached files when the current driving scenario is an idle scenario includes: If all cached files are low-priority cached files, then all cached files are sorted based on file type and file creation time; Based on the sorting results, all cached files are deleted sequentially until the cache occupancy rate is less than the trigger threshold.

[0010] Optionally, deleting the low-priority cache file from the pre-release pool when the cache occupancy rate exceeds the execution threshold includes: If the cache occupancy rate is greater than the execution threshold, the real-time driving scenario of the target vehicle at the current moment is obtained as the final driving scenario. Low-priority cache files are determined based on the cache cleanup strategy corresponding to the final driving scenario; The low-priority cached files are removed from the pre-release pool.

[0011] Secondly, embodiments of the present invention also provide a vehicle infotainment system cache management device, comprising: The detection unit is used to detect the current driving scenario of the target vehicle and the cache usage rate of the vehicle system, wherein different driving scenario states correspond to different cache clearing strategies; The determining unit is configured to determine low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario when the cache occupancy rate is greater than the trigger threshold, wherein the low-priority cache files are marked to the pre-release pool; The deletion unit is used to delete the low-priority cache file from the pre-release pool when the cache occupancy rate is greater than the execution threshold, wherein the execution threshold is greater than the trigger threshold.

[0012] To achieve the above objectives, according to a third aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium comprising a stored program, wherein the steps of the above-described vehicle system cache management method are implemented when the program is executed by a processor.

[0013] To achieve the above objectives, according to a fourth aspect of the present invention, an electronic device is provided, including at least one processor and at least one memory connected to the processor; wherein the processor is configured to invoke program instructions in the memory to execute the steps of the above-described vehicle cache management method.

[0014] By employing the above technical solution, the vehicle-mounted system cache management method and related equipment provided by this invention address the problems of poor adaptability and the need for manual intervention in existing vehicle-mounted system cache clearing methods. This invention detects the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle-mounted system. Different driving scenario states correspond to different cache clearing strategies. When the cache occupancy rate exceeds a trigger threshold, low-priority cache files are determined based on the cache clearing strategy corresponding to the current driving scenario. These low-priority cache files are marked in a pre-release pool. When the cache occupancy rate exceeds an execution threshold, the low-priority cache files are deleted from the pre-release pool. The execution threshold is greater than the trigger threshold. In this solution, the correlation between the cache clearing strategy and the driving scenario is first established, enabling adaptive adjustments based on different situations such as navigation, entertainment, or other states. Furthermore, a dual-threshold triggering process, including a trigger threshold and an execution threshold, is designed, and the cache clearing process is clearly separated into two stages: decision-making and execution. When cache usage exceeds a low trigger threshold, the system determines which cache files are low-priority based solely on the strategy defined for the current driving scenario. These files are then marked into a pre-release pool, completing the intelligent filtering and preparation of cleanup targets without actually releasing space. Only when cache usage continues to grow to a higher execution threshold is the final physical deletion operation performed. This pre-decision, post-execution mechanism separates resource-intensive analysis and filtering work from execution moments when resources may already be strained, reducing the risk of performance fluctuations caused by the need to instantly complete complex decisions and deletion operations. The entire process automatically completes scenario detection, decision-making, and execution without manual user intervention, thus automating cache management and reducing the security risks and inconvenience of manual operation.

[0015] Correspondingly, the vehicle-mounted cache management device, equipment, and computer-readable storage medium provided in the embodiments of the present invention also have the above-mentioned technical effects.

[0016] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0017] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1A flowchart illustrating a vehicle infotainment system cache management method provided in an embodiment of the present invention is shown. Figure 2 This diagram illustrates the composition of a vehicle infotainment system cache management device according to an embodiment of the present invention. Figure 3 This diagram illustrates the composition of an electronic device for managing vehicle-mounted caches, as provided in an embodiment of the present invention. Detailed Implementation

[0018] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0019] To address the issues of poor adaptability and the need for manual intervention in existing in-vehicle infotainment system cache clearing methods, this invention provides an in-vehicle infotainment system cache management method, such as... Figure 1 As shown, the method includes: S101. Detect the current driving scenario of the target vehicle and the cache usage rate of the vehicle system, wherein different driving scenario states correspond to different cache clearing strategies; For example, after identifying different specific driving scenarios for the target vehicle, such as long-distance highway navigation, urban traffic congestion, or in-car entertainment, a specific cache management operation plan is matched and executed for each identified scenario. These operation plans differ in terms of the cached data objects to be cleared, the triggering time of the clearing operation, and the level of aggressiveness in execution, to adapt to the performance requirements of the vehicle's infotainment system and the user's experience needs in specific scenarios. Through this correspondence, cache management is no longer a single or fixed operation, but can adaptively adjust according to the dynamic changes in the driving scenario, thereby improving the rationality of vehicle resource scheduling and overall operational efficiency.

[0020] In one embodiment, detecting the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle's infotainment system includes: The driving status, navigation application status, and entertainment application status of the target vehicle are detected. The driving status is determined based on the current vehicle speed and changes in GPS latitude and longitude data, and the entertainment application status is determined based on changes in the data usage of the entertainment program. The current driving scenario of the target vehicle is determined based on the driving status, the navigation application status, and the entertainment application status.

[0021] For example, the steps in detecting the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle's infotainment system involve detecting the driving status, navigation application status, and entertainment application status. Here, the driving status is characterized by the vehicle's movement through the current vehicle speed and changes in latitude and longitude data in GPS data. The current vehicle speed indicates the instantaneous speed of the vehicle, and changes in latitude and longitude data in GPS data provide location and trajectory information. The navigation application status describes whether the navigation software is in operation. The entertainment application status reflects the activity level of the entertainment program based on changes in its data traffic.

[0022] This embodiment acquires the target vehicle's driving status, navigation application status, and entertainment application status in real time, and determines the current driving scenario based on the combination of these statuses. The driving status is determined by the current vehicle speed and changes in latitude and longitude data in the GPS data, such as stable high-speed driving or low-speed congested driving; the navigation application status indicates whether the navigation function is enabled; the entertainment application status is determined by monitoring changes in the data flow of the entertainment program to determine whether it is running in the background or foreground. Subsequently, these statuses are comprehensively analyzed. For example, if the driving status shows a high vehicle speed and changes in latitude and longitude data in the GPS data within a preset time (e.g., 5 minutes), the navigation application status is active, and the entertainment application status shows low data flow changes, then it is identified as a long-distance highway navigation scenario; if the driving status shows a vehicle speed of 0 and no changes in latitude and longitude data in the GPS data within a preset time (e.g., 5 minutes), the navigation application status is inactive, and the entertainment application status shows high data flow changes, then it is identified as an urban parking entertainment scenario.

[0023] By employing the aforementioned technical solutions, real-time information from vehicle driving, navigation, and entertainment can be integrated, thereby enhancing the accuracy and breadth of driving scenario recognition. By providing the basis for vehicle movement through driving status, revealing route guidance needs through navigation application status, and reflecting in-vehicle entertainment activities through entertainment application status, this multi-dimensional detection makes the determination of driving scenarios more comprehensive and reliable. This provides a more realistic basis for managing the cache utilization of the vehicle's infotainment system, supporting more rational resource scheduling and improving the smoothness of the infotainment system's operation and user experience.

[0024] In one embodiment, determining the current driving scenario of the target vehicle based on the driving state, the navigation application state, and the entertainment application state includes: When navigation is in use and entertainment is not in use, the current driving scenario of the target vehicle is determined to be the navigation scenario; When entertainment is enabled and navigation is disabled, the current driving scenario of the target vehicle is determined to be an entertainment scenario. When navigation and entertainment are both not in use, the current driving scenario of the target vehicle is determined to be an idle scenario; With both navigation and entertainment applications active, the current driving scenario of the target vehicle is determined based on the driving status, including: When the target vehicle is in the driving state, the current driving scenario of the target vehicle is determined to be a navigation-priority coexistence scenario; If the target vehicle is not in the driving state, the current driving scenario of the target vehicle is determined to be an entertainment-priority coexistence scenario.

[0025] For example, the above-described determination of the target vehicle's current driving scenario based on driving status, navigation application status, and entertainment application status distinguishes different driving scenario types through a series of conditional judgments. When navigation is in use and entertainment is not in use, the current driving scenario is determined to be a navigation scenario; when entertainment is in use and navigation is not in use, the current driving scenario is determined to be an entertainment scenario; when both navigation and entertainment are not in use, the current driving scenario is determined to be an idle scenario. In the case where both navigation and entertainment are in use, the system further subdivides based on driving status: if the target vehicle is in use, the current driving scenario is determined to be a navigation-priority coexistence scenario; if the target vehicle is not in use, the current driving scenario is determined to be an entertainment-priority coexistence scenario.

[0026] In this embodiment, real-time data on the navigation application status, entertainment application status, and driving status are continuously acquired, and the corresponding driving scenarios are output using the aforementioned logical conditions. For example, while the vehicle is in motion, if the driver uses both navigation guidance and music playback functions simultaneously, both the navigation application status and the entertainment application status are considered application statuses. The system checks the driving status to distinguish between coexisting scenarios. If the vehicle is moving, it is determined to be a navigation-priority coexisting scenario, in which case the navigation function is considered the primary requirement. If the vehicle is stationary, such as in a parked state, it is determined to be an entertainment-priority coexisting scenario, in which case the entertainment function is considered the primary requirement. This approach ensures that various user operation scenarios, from single-application to multi-application coexistence, can be accurately categorized, forming a complete and comprehensive scenario recognition coverage.

[0027] By employing the aforementioned technical solution, driving scenarios can be differentiated in a multi-layered and targeted manner based on the actual activation status of navigation and entertainment applications and whether the vehicle is in motion. By further subdividing the coexistence of navigation and entertainment into navigation-first and entertainment-first categories, scenario recognition can better reflect the user's different priorities and usage intentions when the vehicle is moving or stationary. This refined scenario determination lays an accurate foundation for subsequent adaptation of differentiated cache clearing strategies, enabling the vehicle's infotainment system to more appropriately allocate cache resources according to scenario characteristics, optimize operating efficiency and user interaction experience, and reduce improper resource allocation or operational delays that may be caused by scenario misjudgment or coarse-grained segmentation.

[0028] In one embodiment, detecting the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle's infotainment system includes: Obtain the total cache space capacity and used cache amount of the vehicle's infotainment system; The cache utilization rate is determined based on the total cache space capacity and the amount of cache already used.

[0029] For example, the steps in detecting the current driving scenario of the target vehicle and the cache occupancy rate of the vehicle's infotainment system involve obtaining the total cache space capacity and the amount of cache already used. Here, the total cache space capacity refers to the total size of the vehicle's infotainment system's cache storage area, and the amount of cache already used refers to the size of the portion of that storage area currently occupied by data.

[0030] This embodiment obtains the total cache space capacity and used cache amount of the target vehicle's infotainment system through the vehicle's storage management interface or cache monitoring service, and then determines the cache utilization rate based on these two values. The total cache space capacity, a fixed or configurable value, is read from the storage management unit of the vehicle's hardware or operating system. Simultaneously, the used cache amount is obtained in real time by scanning cache areas or summarizing cache usage data from various applications and processes. Then, the used cache amount is compared with the total cache space capacity, and the cache utilization rate is calculated by determining the ratio of the used cache amount to the total cache space capacity.

[0031] For example, during normal operation of the vehicle's infotainment system, the cache management module periodically calls system functions to obtain the total cache space capacity and collects the total amount of cache data occupied by all running applications and background services as the used cache amount. Then, it calculates the current cache occupancy rate based on the ratio between the two, thereby reflecting the cache usage status in numerical form.

[0032] The aforementioned technical solution enables real-time and accurate assessment of the actual usage level of in-vehicle infotainment system cache resources, providing crucial data support for subsequent differentiated cache management tailored to driving scenarios. By directly obtaining the total cache space capacity and the amount of cache used, and determining the cache occupancy rate, the progress and trend of cache consumption can be continuously monitored. This ensures that cache management decisions are based on objective quantitative indicators rather than subjective estimates, thereby enhancing the rationality and timeliness of resource scheduling. This monitoring mechanism based on actual cache usage helps to identify resource stress in advance when cache occupancy is high, triggering appropriate cache cleanup strategies, promoting the maintenance of smooth and stable operation of the in-vehicle infotainment system, and optimizing the user experience.

[0033] S102. When the cache occupancy rate is greater than the trigger threshold, a low-priority cache file is determined based on the cache cleanup strategy corresponding to the current driving scenario, wherein the low-priority cache file is marked to the pre-release pool. For example, the above steps of determining low-priority cache files and marking them to the pre-release pool based on the cache cleanup strategy corresponding to the current driving scenario when the cache occupancy rate exceeds the trigger threshold involve multiple parameters. The trigger threshold is a preset critical value used to determine whether the cache occupancy rate has reached a level requiring cleanup operations; low-priority cache files refer to cache data files that are determined to be of lower importance and can be cleaned up first according to specific rules; the pre-release pool is a logical collection or list used to temporarily store or record cache files marked as low-priority for subsequent unified processing. As mentioned above, the current driving scenario and cache cleanup strategy refer to the specific scenario type in which the vehicle is located and the cleanup rules pre-configured for that scenario, respectively.

[0034] This embodiment continuously monitors cache usage during vehicle system operation. When the cache usage exceeds a preset trigger threshold, it indicates that cache space is strained and a cleanup process needs to be initiated. At this point, based on the determined current driving scenario, the cache cleanup strategy corresponding to that scenario is retrieved from the policy configuration. This strategy defines priority rules for various cache files under different scenarios. The system scans the cache files in the vehicle system according to these rules, identifying those that meet the low-priority criteria. For example, in a scenario where entertainment is prioritized alongside other driving scenarios, the corresponding cache cleanup strategy might specify that the offline map cache for the navigation application is low-priority, while the cache for the currently playing media file is high-priority. Therefore, the system will identify the offline map cache for navigation as a low-priority cache file. Subsequently, these identified low-priority cache files are added or marked to a pre-release pool. The pre-release pool acts as an intermediate temporary storage area, recording all cache file entries to be cleaned, but not immediately performing deletion operations, to facilitate unified management or confirmation in subsequent steps.

[0035] By employing the above technical solution, when cache occupancy is too high, low-priority cache files with minimal impact on the current user experience can be intelligently selected as candidate cleanup targets based on the specific needs of the current driving scenario. By introducing a pre-release pool to pre-mark and centrally manage low-priority cache files, a clear and orderly set of targets is provided for cache cleanup, making the cleanup operation more targeted and controllable. This helps avoid system performance fluctuations or important data loss that may result from blindly or uniformly cleaning all caches. Thus, while freeing up cache space to alleviate resource pressure, it better ensures the caching needs of core functions related to the current driving scenario, improving the rationality and stability of vehicle system resource scheduling.

[0036] In one embodiment, determining low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario when the cache occupancy rate is greater than the trigger threshold includes: If the current driving scenario is either the navigation scenario or the navigation priority coexistence scenario, the non-navigation cache file is determined to be a low-priority cache file; If the current driving scenario is the entertainment scenario or the entertainment-first coexistence scenario, the non-entertainment cache file is determined to be a low-priority cache file; If the current driving scenario is an idle scenario, all cached files are determined to be low-priority cached files.

[0037] For example, the step described above, which determines low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario when the cache occupancy rate exceeds the trigger threshold, directly associates the driving scenario type with the category of cache files to be cleaned through specific rules. When the current driving scenario is identified as a navigation scenario or a navigation-first coexistence scenario, non-navigation cache files are determined to be low-priority cache files; when the current driving scenario is identified as an entertainment scenario or an entertainment-first coexistence scenario, non-entertainment cache files are determined to be low-priority cache files; when the current driving scenario is identified as an idle scenario, all cache files are determined to be low-priority cache files. Here, non-navigation cache files refer to all cache files other than those generated by the navigation application or directly related to the navigation function, and non-entertainment cache files refer to all cache files other than those generated by the entertainment application or directly related to the entertainment function.

[0038] When the cache occupancy rate exceeds the trigger threshold and the cleanup process is initiated, this application directly applies the aforementioned rules to determine the specific range of low-priority cache files based on the precisely determined current driving scenario. For example, if the vehicle is determined to be in a navigation scenario where it is traveling long distances on highways and the navigation function is active, then according to the rule of "determining non-navigation cache files as low-priority cache files," files unrelated to navigation, such as music player song cache and video application preview image cache, will be identified as low-priority, while navigation application route calculation cache and real-time traffic cache will be protected. Conversely, if the vehicle is parked and the user is watching video, in an entertainment scenario, then according to the rule of "determining non-entertainment cache files as low-priority cache files," the system will determine navigation application historical search record cache and system log cache as low-priority, while the buffered data of the currently playing video will remain high-priority. In idle scenarios, since there is no dominant application, all cache files are considered objects that can be prioritized for cleanup. This determination method directly and explicitly translates scenario semantics into specific file filtering instructions.

[0039] Understandably, when both navigation and entertainment are active, the system doesn't directly determine the current driving scenario type based on the driving status. Instead, it first assesses the vehicle's cache space. If the cache space is sufficient, meaning the cache occupancy rate doesn't exceed the threshold requiring a cleanup operation, the system maintains the coexistence of navigation and entertainment applications without prioritizing them or initiating subsequent cache cleanup. Only when insufficient cache space is detected, i.e., the cache occupancy rate exceeds a relevant threshold, does the system further differentiate the specific coexistence scenario type based on the driving status: if the target vehicle is in motion, the current driving scenario is determined to be a navigation-priority coexistence scenario; if the target vehicle is not in motion, the current driving scenario is determined to be an entertainment-priority coexistence scenario. This process ensures that prioritization is only based on vehicle movement status when resources are scarce and trade-offs must be made, thus prioritizing the user experience of all active applications when resources are sufficient.

[0040] By employing the aforementioned technical solution, abstract driving scenario classifications can be transformed into specific, actionable cache file cleanup priority commands. By pre-setting clear and differentiated file filtering rules for navigation-dominated scenarios, entertainment-dominated scenarios, and idle scenarios, the determination process for low-priority cache files becomes highly scenario-based and purposeful, ensuring that the cleanup operation closely aligns with the user's core functional needs in the current scenario. Protecting navigation cache in navigation-related scenarios, protecting entertainment cache in entertainment-related scenarios, and comprehensively preparing for cleanup in idle scenarios—this targeted protection mechanism helps to maximize the preservation of cache data crucial to user experience while freeing up cache space. This reduces the risk of improper cleanup interfering with main functions, improving the accuracy of vehicle system resource management and the consistency of user experience.

[0041] In one embodiment, determining all cached files as low-priority cached files when the current driving scenario is an idle scenario includes: If all cached files are low-priority cached files, then all cached files are sorted based on file type and file creation time; Based on the sorting results, all cached files are deleted sequentially until the cache occupancy rate is less than the trigger threshold.

[0042] For example, the above steps involve file type and file creation time. File type refers to the data format or application category of the cached file, such as image cache, log file, temporary data, etc.; file creation time refers to the point in time when the cached file is generated or recorded in the vehicle's storage system.

[0043] In this embodiment, after the current driving scenario is determined to be an idle scenario and all cached files are marked as low priority, a refined cleanup process is initiated. First, all low-priority cached files are sorted according to predefined rules, primarily based on file type and file creation time. For example, the system may prioritize cleaning temporary data type files before cleaning log files; within the same file type, files with earlier creation times (i.e., older files) are prioritized. Based on this sorting rule, a file order list from highest to lowest priority is generated. Subsequently, these cached files are deleted from the storage space sequentially according to this list. After deleting one or a batch of files, the system recalculates the current cache occupancy rate and compares it with a trigger threshold. This deletion process continues until the system detects that the cache occupancy rate has dropped below the pre-set trigger threshold, thus ensuring that cache space is restored to a sufficient level.

[0044] By employing the aforementioned technical solution, an orderly and controllable cleanup mechanism is introduced when cleaning up all cached files in idle scenarios. By sorting all cached files according to file type and creation time, the system can release space in order of minimizing impact on system operation and prioritizing data with lower value. For example, older temporary files are cleaned up first, rather than newer application data. This sequential deletion approach, stopping once the target is reached, ensures that the cleanup operation has clear objectives and limits, avoiding system instability caused by excessive or disordered cleanup. It effectively reduces cache occupancy while maintaining predictability and a moderate impact on system resources, thus achieving a balance between releasing necessary space and maintaining the integrity of basic system data.

[0045] S103. If the cache occupancy rate is greater than the execution threshold, the low-priority cache file is deleted from the pre-release pool, wherein the execution threshold is greater than the trigger threshold.

[0046] In one embodiment, deleting the low-priority cache file from the pre-release pool when the cache occupancy rate exceeds the execution threshold includes: If the cache occupancy rate is greater than the execution threshold, the real-time driving scenario of the target vehicle at the current moment is obtained as the final driving scenario. Low-priority cache files are determined based on the cache cleanup strategy corresponding to the final driving scenario; The low-priority cached files are removed from the pre-release pool.

[0047] For example, the above steps involve an execution threshold and a final driving scenario. The execution threshold is a preset cache occupancy threshold used to trigger the deletion operation; the final driving scenario refers to the real-time driving scenario determined by detecting the target vehicle's driving status, navigation application status, and entertainment application status at the current moment. The meanings of cache occupancy, low-priority cache files, pre-release pool, and cache cleanup strategy are as described above.

[0048] In this application, during the continuous monitoring of cache utilization in the vehicle's infotainment system, when the cache utilization rate is determined to exceed an execution threshold, the system first acquires the real-time driving scenario of the target vehicle at the current moment as the final driving scenario. This acquisition process is achieved by real-time detection of changes in current vehicle speed, GPS latitude and longitude data, and traffic changes in navigation and entertainment application status. Based on these statuses, the specific driving scenario type, such as navigation scenario or entertainment scenario, is determined. Subsequently, based on the cache cleanup strategy corresponding to this final driving scenario, the specific range of low-priority cache files is redefined. For example, if the final driving scenario is a navigation-priority coexistence scenario, non-navigation cache files are determined as low-priority cache files according to the corresponding strategy. Finally, the system deletes these redefined low-priority cache files from the pre-release pool, that is, removes the records of these files from the pre-release pool logical set or directly clears their stored data, thereby completing the cache release operation.

[0049] Understandably, S102's process of determining low-priority cache files and marking them to the pre-release pool based on the cache cleanup strategy corresponding to the current driving scenario is a pre-screening and preparation process performed when the cache occupancy rate first exceeds the trigger threshold. Its purpose is to identify potential cleanupable objects in advance based on the current driving scenario and manage them centrally, thus providing a pre-planned target set for subsequent possible cleanup operations. This helps reduce the number of files that need to be calculated and screened in real-time and the processing latency when the cache occupancy rate further increases to the execution threshold. In this step, determining low-priority cache files based on the cache cleanup strategy corresponding to the final driving scenario and deleting them from the pre-release pool is the final operation performed when the cache occupancy rate exceeds a higher execution threshold. Re-acquiring the final driving scenario and redetermining low-priority cache files based on it ensures that the actual deletion operation matches the latest real-time state of the vehicle, as the driving scenario may have changed, for example, from a navigation scenario to an entertainment scenario. Therefore, S102's pre-marking provides a buffer and preparation for the system, while this redetering step ensures the real-time nature and accuracy of the deletion. The two work together in terms of timing and function to achieve progressive and adaptive optimization of cache management.

[0050] By employing the above technical solution, when the cache occupancy rate reaches a level requiring deletion, the cleanup strategy can be ensured to match the latest vehicle status by acquiring the final driving scenario in real time. Low-priority cache files are re-determined based on the final driving scenario, making the deletion operation more reflective of current user needs and system resource status, thus improving the targeting and adaptability of the cleanup. Deleting these files from the pre-release pool achieves centralized and orderly management of cache cleanup objects, helping to reduce interference with cached data required for core functions in the current driving scenario while reducing cache occupancy, thereby improving the real-time performance of vehicle system resource scheduling and the consistency of user experience.

[0051] In summary, this application continuously monitors the target vehicle's driving status, such as current speed and changes in GPS latitude and longitude data, as well as the status of navigation applications and entertainment applications, such as changes in traffic to entertainment programs, to determine driving scenarios in real time. These scenarios may include navigation, entertainment, idle, or a combination of navigation-first and entertainment-first scenarios. When the cache occupancy rate exceeds a trigger threshold, specific rules are applied based on the scenario type to filter low-priority cache files. For example, in navigation-related scenarios, non-navigation cache files are marked; in entertainment-related scenarios, non-entertainment cache files are marked; and in idle scenarios, all cache files are marked, sorted, and deleted sequentially until the cache occupancy rate decreases. When the cache occupancy rate exceeds an execution threshold, the system re-acquires the final driving scenario and, based on its strategy, re-determines low-priority cache files and deletes them from the pre-release pool, ensuring that the cleanup operation matches the vehicle's latest status. It can adaptively adjust the cache management strategy according to the real-time driving scenario of the vehicle. Through a dual threshold mechanism, it separates the cleanup decision from the execution. When the cache space is tight, it prioritizes the screening and preparation of cache data that has little impact on the current scenario, and performs deletion when necessary. This reduces the interference with the cache data of core functions during the automated management process, improves the accuracy and timeliness of vehicle system resource scheduling, and enhances the consistency of user experience and the stability of system operation.

[0052] The key to reducing lag in this solution lies in its pre-release pool mechanism, which separates the resource-intensive analysis and decision-making phase of cache cleanup from the final physical deletion execution phase, and selects different trigger times. When the cache occupancy rate exceeds the trigger threshold, the system begins to analyze the current driving scenario and determine which cache files are low-priority, marking them to the pre-release pool. This analysis and decision-making process involves scanning cache files and matching rules, requiring certain computing resources. However, at this point, the cache occupancy rate has not yet reached its limit, system resources are relatively abundant, and the vehicle may be in a low-load driving scenario (such as a parked state). Therefore, this preparatory work can be completed smoothly without causing a perceptible system response delay for the user. When the cache occupancy rate further increases to a higher execution threshold, and the system faces resource constraints and needs to release space immediately, since the low-priority cache files to be deleted are already ready in the pre-release pool, there is no need for another time-consuming analysis and decision-making process; the physical deletion operation can be performed directly. This deletion action mainly involves storage I / O operations, and its resource consumption and required time are far less than the entire "analysis + decision + deletion" process. This allows the system to quickly release space with minimal additional burden when resources are nearing saturation, thus avoiding resource contention and operational delays caused by simultaneously executing a complex full cleanup process during periods of high system load. Therefore, by shifting the heavy analysis work to a relatively idle period and ensuring that only lightweight deletion operations are performed during execution, this solution effectively reduces the risk of increased load due to cache cleanup during periods of high system resource scarcity, thereby reducing the occurrence of stuttering.

[0053] Furthermore, as a response to the above Figure 1 In addition to the implementation of the method shown, this embodiment of the invention also provides a vehicle infotainment system cache management device for managing the aforementioned... Figure 1 The method shown is implemented accordingly. This device embodiment corresponds to the foregoing method embodiment. For ease of reading, this device embodiment will not repeat the details of the foregoing method embodiment, but it should be clear that the device in this embodiment can implement all the contents of the foregoing method embodiment. Figure 2 As shown, the device includes: a detection unit 21, a determination unit 22, and a deletion unit 23, wherein... The detection unit 21 is used to detect the current driving scenario of the target vehicle and the cache usage rate of the vehicle system, wherein different driving scenario states correspond to different cache clearing strategies; The determining unit 22 is used to determine low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario when the cache occupancy rate is greater than the trigger threshold, wherein the low-priority cache files are marked to the pre-release pool; The deletion unit 23 is used to delete the low-priority cache file from the pre-release pool when the cache occupancy rate is greater than the execution threshold, wherein the execution threshold is greater than the trigger threshold.

[0054] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters can implement a vehicle infotainment system cache management method that addresses the problems of poor adaptability and the need for manual intervention in existing vehicle infotainment system cache clearing methods.

[0055] This invention provides a computer-readable storage medium, which includes a stored program that, when executed by a processor, implements the vehicle system cache management method.

[0056] This invention provides a processor for running a program, wherein the program executes the vehicle system cache management method during runtime.

[0057] This invention provides an electronic device, which includes at least one processor and at least one memory connected to the processor; wherein the processor is used to call program instructions in the memory to execute the vehicle infotainment system cache management method described above. This invention provides an electronic device 30, such as... Figure 3 As shown, the electronic device includes at least one processor 301, and at least one memory 302 and bus 303 connected to the processor; wherein, the processor 301 and the memory 302 communicate with each other through the bus 303; the processor 301 is used to call program instructions in the memory to execute the above-mentioned vehicle cache management method.

[0058] The smart electronic devices mentioned in this article can be PCs, tablets, mobile phones, etc.

[0059] This application also provides a computer program product that, when executed on a process management electronic device, is suitable for executing a program that initializes the above-described vehicle cache management method steps.

[0060] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0061] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0062] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0063] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0064] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0065] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to perform actions such as... Figure 1 The control flow of the memory in the corresponding embodiment.

[0066] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0067] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0068] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of 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 system, 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, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0069] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0070] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0071] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0072] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A vehicle infotainment system cache management method, characterized in that, include: The current driving scenario of the target vehicle and the cache usage rate of the vehicle system are detected, wherein different driving scenario states correspond to different cache clearing strategies; If the cache occupancy rate is greater than the trigger threshold, low-priority cache files are determined based on the cache cleanup strategy corresponding to the current driving scenario, wherein the low-priority cache files are marked to the pre-release pool; If the cache occupancy rate is greater than the execution threshold, the low-priority cache file is deleted from the pre-release pool, wherein the execution threshold is greater than the trigger threshold.

2. The method according to claim 1, characterized in that, The detection of the current driving scenario of the target vehicle and the cache usage rate of the vehicle's infotainment system includes: The driving status, navigation application status, and entertainment application status of the target vehicle are detected. The driving status is determined based on the current vehicle speed and changes in GPS latitude and longitude data, and the entertainment application status is determined based on changes in the data usage of the entertainment program. The current driving scenario of the target vehicle is determined based on the driving status, the navigation application status, and the entertainment application status.

3. The method according to claim 2, characterized in that, Determining the current driving scenario of the target vehicle based on the driving state, the navigation application state, and the entertainment application state includes: When navigation is in use and entertainment is not in use, the current driving scenario of the target vehicle is determined to be the navigation scenario; When entertainment is enabled and navigation is disabled, the current driving scenario of the target vehicle is determined to be an entertainment scenario. When navigation and entertainment are both not in use, the current driving scenario of the target vehicle is determined to be an idle scenario; With both navigation and entertainment applications active, the current driving scenario of the target vehicle is determined based on the driving status, including: When the target vehicle is in the driving state, the current driving scenario of the target vehicle is determined to be a navigation-priority coexistence scenario; If the target vehicle is not in the driving state, the current driving scenario of the target vehicle is determined to be an entertainment-priority coexistence scenario.

4. The method according to claim 1, characterized in that, The detection of the current driving scenario of the target vehicle and the cache usage rate of the vehicle's infotainment system includes: Obtain the total cache space capacity and used cache amount of the vehicle's infotainment system; The cache utilization rate is determined based on the total cache space capacity and the amount of cache already used.

5. The method according to claim 3, characterized in that, When the cache occupancy rate exceeds the trigger threshold, the step of determining low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario includes: If the current driving scenario is either the navigation scenario or the navigation priority coexistence scenario, the non-navigation cache file is determined to be a low-priority cache file; If the current driving scenario is the entertainment scenario or the entertainment-first coexistence scenario, the non-entertainment cache file is determined to be a low-priority cache file; If the current driving scenario is an idle scenario, all cached files are determined to be low-priority cached files.

6. The method according to claim 5, characterized in that, The step of determining all cached files as low-priority cached files when the current driving scenario is an idle scenario includes: If all cached files are low-priority cached files, then all cached files are sorted based on file type and file creation time; Based on the sorting results, all cached files are deleted sequentially until the cache occupancy rate is less than the trigger threshold.

7. The method according to claim 1, characterized in that, The step of deleting the low-priority cache file from the pre-release pool when the cache occupancy rate exceeds the execution threshold includes: If the cache occupancy rate is greater than the execution threshold, the real-time driving scenario of the target vehicle at the current moment is obtained as the final driving scenario. Low-priority cache files are determined based on the cache cleanup strategy corresponding to the final driving scenario; The low-priority cached files are removed from the pre-release pool.

8. A vehicle infotainment system cache management device, characterized in that, Also includes: The detection unit is used to detect the current driving scenario of the target vehicle and the cache usage rate of the vehicle system, wherein different driving scenario states correspond to different cache clearing strategies; The determining unit is configured to determine low-priority cache files based on the cache cleanup strategy corresponding to the current driving scenario when the cache occupancy rate is greater than the trigger threshold, wherein the low-priority cache files are marked to the pre-release pool; The deletion unit is used to delete the low-priority cache file from the pre-release pool when the cache occupancy rate is greater than the execution threshold, wherein the execution threshold is greater than the trigger threshold.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed by a processor, it implements the steps of the vehicle system cache management method as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, The electronic device includes at least one processor and at least one memory connected to the processor; wherein the processor is used to call program instructions in the memory to execute the steps of the vehicle system cache management method as described in any one of claims 1 to 7.

Images