Vehicle-mounted application management method, system, equipment and medium

Abstract

The invention relates to the field of vehicles, in particular to a vehicle-mounted application management method, system, device and medium, and the method comprises the steps: starting a vehicle-mounted control unit after a vehicle power supply system is activated; obtaining the use frequency of each vehicle-mounted application; according to the use frequency of each vehicle-mounted application and a preset static priority, calculating a dynamic starting priority of the vehicle-mounted application; starting each vehicle-mounted application to a corresponding application starting state according to the dynamic starting priority and the static priority; wherein the application starting state comprises a preliminary loading state and an active state; and in response to a starting request for any vehicle-mounted application, judging whether the vehicle-mounted application is in an active state, and if not, starting the vehicle-mounted application to be in the active state. According to the method, the defects of an existing static starting mode are effectively overcome, the performance of the vehicle-mounted system and the user experience are improved, and the method has remarkable technical advantages and practical application value.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a management method, system, device and medium for vehicle-mounted applications. Background Art

[0002] With the development of automobile intelligence, in-vehicle applications have become an important part of modern automobiles. In-vehicle applications refer to software applications that run in the vehicle environment, providing drivers and passengers with various information services and entertainment functions, including navigation, music playback, phone answering, voice assistants, etc. The startup sequence of in-vehicle applications refers to the process of loading and initializing these applications in a certain order when the vehicle is started. It is very important to pay attention to the startup sequence of in-vehicle applications, because a reasonable startup sequence can improve the response speed of the system, optimize resource allocation, and improve user experience. If the startup sequence is unreasonable, it may cause the system startup time to be too long, waste resources, and even cause problems such as application freeze or crash, affecting driving safety and user satisfaction. Therefore, optimizing the startup sequence of in-vehicle applications is of great significance to improving the overall performance and user satisfaction of the in-vehicle system.

[0003] At present, the startup order of in-vehicle applications usually adopts a preset static method. In this method, system developers predefine a fixed startup order based on the importance and dependencies of the applications. When the system starts, the applications are started in this preset order. However, this static startup method has some limitations, and the preset startup order cannot meet the needs of different users in different situations, thus affecting the user experience. Summary of the invention

[0004] To solve the above problems, the present invention provides a method, system, device and medium for managing vehicle-mounted applications.

[0005] A first aspect of the present invention discloses a method for managing vehicle-mounted applications, comprising:

[0006] After the vehicle power system is activated, the on-board control unit is started;

[0007] Get the usage frequency of each in-vehicle application;

[0008] Calculating the dynamic startup priority of the in-vehicle application according to the usage frequency of each in-vehicle application and the preset static priority; wherein the static priority includes: a first static priority, a second static priority, a third static priority and a fourth static priority;

[0009] According to the dynamic startup priority and the static priority, each of the vehicle-mounted applications is started to its corresponding application startup state; wherein the application startup state includes a preliminary loading state and an active state;

[0010] In response to a start request for any vehicle-mounted application, it is determined whether the vehicle-mounted application is in an active state, and if not, the vehicle-mounted application is started in an active state.

[0011] Furthermore, the step of calculating the dynamic startup priority of the in-vehicle application according to the usage frequency and the preset static priority of each in-vehicle application includes:

[0012] The dynamic startup priority of the vehicle application is calculated according to the following formula:

[0013] P(A i )=α·I(A i )+β·F(A i );

[0014] Among them, P(A i ) represents the vehicle-mounted application A i Dynamic startup priority, I(A i ) represents the vehicle-mounted application A i The static priority of the system, α represents the weight of the preset static priority, F(A i ) represents the vehicle-mounted application A i The usage frequency of the algorithm is β, and β represents the weight of the preset usage frequency.

[0015] Furthermore, the step of obtaining the usage frequency of each in-vehicle application includes:

[0016] Determine the time period corresponding to the current time point in the historical statistical data to obtain the current time period;

[0017] The usage frequency of each in-vehicle application by the current user in the current time period is obtained from the historical statistical data.

[0018] Furthermore, according to the dynamic startup priority and the static priority, the step of starting each of the vehicle-mounted applications to its corresponding application startup state includes:

[0019] sorting all the vehicle-mounted applications from high to low according to the dynamic startup priority;

[0020] According to the static priority, the sorted in-vehicle applications are started in sequence to their preset application start states.

[0021] Furthermore, according to the static priority, the step of sequentially starting the sorted in-vehicle applications to their preset application start states includes:

[0022] Traverse the sorted in-vehicle applications, and for each in-vehicle application, determine the corresponding static priority:

[0023] If it is the first static priority, start it as active;

[0024] If it is the second static priority level or the third static priority level, start it as a preliminary loading state;

[0025] If it is the fourth static priority, it will not be started.

[0026] Further, after the vehicle power system is activated, the step of starting the vehicle control unit includes:

[0027] After the vehicle power system is activated, the on-board control unit is started;

[0028] Play the startup animation.

[0029] Furthermore, the in-vehicle application management method further includes:

[0030] Monitor vehicle applications for cleaning;

[0031] Determine the corresponding static priority:

[0032] If it is the first static priority, clear its application startup state to active state;

[0033] If it is the second static priority or the third static priority, clearing its application startup state to the initial loading state;

[0034] If it is the fourth static priority, the in-vehicle application is cleared.

[0035] A second aspect of the present invention discloses a management system for vehicle-mounted applications, the system comprising:

[0036] A first starting module, used to start the vehicle control unit after the vehicle power system is activated;

[0037] An acquisition module, used to acquire the usage frequency of each vehicle-mounted application;

[0038] A calculation module, configured to calculate the dynamic startup priority of the in-vehicle application according to the usage frequency of each in-vehicle application and a preset static priority; wherein the static priority includes: a first static priority, a second static priority, a third static priority and a fourth static priority;

[0039] A second startup module, configured to start each of the vehicle-mounted applications to its corresponding application startup state according to the dynamic startup priority and the static priority; wherein the application startup state includes a preliminary loading state and an active state;

[0040] The response module is used to respond to a start-up request for any vehicle-mounted application, determine whether the vehicle-mounted application is in an active state, and if not, start the vehicle-mounted application in an active state.

[0041] The third aspect of the present invention discloses an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The device is characterized in that when the processor executes the computer program, it implements the steps of any vehicle-mounted application management method disclosed in the first aspect of the present invention.

[0042] A fourth aspect of the present invention discloses a storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any one of the vehicle-mounted application management methods disclosed in the first aspect of the present invention.

[0043] The present invention provides a method for managing vehicle-mounted applications, which dynamically adjusts the startup priority of applications by calculating the usage frequency of applications in real time and combining preset static priorities. Compared with the static startup sequence, the method can optimize the startup sequence according to the actual usage of the user, ensure that frequently used applications can be started faster and reach an active state, and improve the response speed of the system and user experience. At the same time, by introducing dynamic priorities, the method can adapt to changes in the frequency of application use and adjust the startup sequence in time, thereby improving the adaptability and flexibility of the system. In addition, the present invention also introduces the concept of application startup state, divides the application startup process into two stages: initial loading and active, and judges the current state of the application when receiving a startup request, avoiding unnecessary repeated startups and further optimizing the utilization efficiency of system resources. In short, the management method of vehicle-mounted applications provided by the present invention effectively solves the shortcomings of the existing static startup method through dynamic priority and startup state management, improves the performance and user experience of the vehicle-mounted system, and has significant technical advantages and practical application value. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0045] Figure 1 It is a flowchart of a method for managing vehicle-mounted applications disclosed in an embodiment of the present invention;

[0046] Figure 2 It is a structural schematic diagram of a management system for vehicle-mounted applications disclosed in an embodiment of the present invention;

[0047] Figure 3 It is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0049] The terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, device, or product end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units inherent to these processes, methods, devices, or product ends.

[0050] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0051] See also Figure 1 As shown, Figure 1 FIG. 1 is a flow chart of a method for managing vehicle-mounted applications disclosed in an embodiment of the present invention. Figure 1 As shown, the management method of the vehicle-mounted application may include the following operations:

[0052] S101, after the vehicle power system is activated, starting the vehicle control unit;

[0053] In an optional embodiment, after the vehicle power system is activated, the step of starting the vehicle control unit includes:

[0054] After the vehicle power system is activated, the on-board control unit is started;

[0055] Play the startup animation.

[0056] In this optional embodiment, the vehicle power system is the core part of the vehicle electrical system, responsible for powering various electrical and electronic equipment on the vehicle. It is usually composed of components such as batteries, generators (AC generators), voltage regulators, and power control modules. The battery stores electrical energy, the generator generates electrical energy and charges the battery when the engine is running, the voltage regulator ensures that the generator outputs a stable voltage, and the power control module manages the operation of the entire system, such as controlling the output of the generator, monitoring the battery status, etc. The reliability of the vehicle power system directly affects the normal operation of the vehicle.

[0057] The vehicle control unit, also known as the vehicle controller or vehicle computer, is the core component responsible for controlling and coordinating various electronic systems in modern vehicles. It is essentially an embedded computer system that collects vehicle operation data through sensors, runs preset control programs, and then controls various components of the vehicle through actuators (such as motors, valves, etc.). Different vehicle control units are responsible for different functions, such as engine control, transmission control, brake control, body stability control, etc. These units communicate with each other through the in-vehicle network to jointly achieve intelligent control of the vehicle.

[0058] Boot animation refers to a short video or animation played on the display screen when the vehicle control unit is started. Boot animation usually displays the brand logo and visually shows that the system is starting up. Boot animation is not just a decoration, it can also cover up the time it takes for the system to start up, give users instant feedback, and improve user experience. At the same time, a well-designed boot animation is also a way to showcase the brand image and improve brand recognition.

[0059] S102, obtaining the usage frequency of each vehicle-mounted application;

[0060] In this optional embodiment, the vehicle application refers to a software program running on the vehicle control unit to provide users with various functions. Common vehicle applications include navigation software, multimedia players, Bluetooth phones, vehicle settings interfaces, etc. These applications interact with users through the vehicle display, audio system, steering wheel control buttons, etc., greatly enriching the driving experience. The development of vehicle applications needs to consider the particularities of the in-vehicle environment, such as safety, reliability, ease of use, etc.

[0061] In an optional embodiment, the step of obtaining the usage frequency of each in-vehicle application includes:

[0062] Determine the time period corresponding to the current time point in the historical statistical data to obtain the current time period;

[0063] The usage frequency of each in-vehicle application by the current user in the current time period is obtained from the historical statistical data.

[0064] In this optional embodiment, the current time point can be obtained by a clock built into the vehicle control unit or a GPS system connected to the vehicle. An example of determining the time period of the current time point is given: Assuming that the current time is 8:30 a.m., the 24 hours of a day are divided into multiple time periods in historical statistical data, such as morning (6:00-9:00), morning (9:00-12:00), afternoon (12:00-18:00), evening (18:00-24:00) and late night (0:00-6:00). According to the current time point of 8:30, it can be determined that the current time period is "morning". The division of this time period can be adjusted according to specific application scenarios and user habits, for example, it can also be distinguished by weekdays and weekends, and the embodiment of the present invention does not limit it.

[0065] Historical statistics refer to the data that the system has recorded over a long period of time on the use of in-vehicle applications by users, including the frequency of use of each application in different time periods. This data can be stored in the memory of the in-vehicle control unit or uploaded to a cloud server for analysis. By analyzing historical statistics, the system can understand the user's habits of using different applications at different time periods. For example, a user may use a navigation application more frequently in the morning, but prefer to use a multimedia playback application in the evening.

[0066] It can be seen that this optional embodiment can accurately predict the applications that the user is most likely to use at the current time point by analyzing the historical data of the user's use of in-vehicle applications in different time periods, and assign a higher startup priority to these applications. In this way, when the user enters the vehicle, the application that the user is most likely to use has been started to the application startup state, providing a smoother user experience and improving the usability and efficiency of the in-vehicle system. Moreover, the application startup strategy based on historical data realizes the adaptation of the in-vehicle system to user habits. Different users may have different usage preferences at different times. The system can dynamically adjust according to the actual usage of each user to provide personalized services. This intelligent management method represents the development trend of in-vehicle electronic systems and can significantly improve the intelligence level of vehicles and user satisfaction.

[0067] S103, calculating the dynamic startup priority of the in-vehicle application according to the usage frequency of each in-vehicle application and the preset static priority; wherein the static priority includes: a first static priority, a second static priority, a third static priority and a fourth static priority;

[0068] In an optional embodiment, the step of calculating the dynamic startup priority of the in-vehicle application according to the usage frequency and the preset static priority of each in-vehicle application includes:

[0069] The dynamic startup priority of the vehicle application is calculated according to the following formula:

[0070] P(A i )=α·I(A i )+β·F(A i );

[0071] Among them, P(A i ) represents the vehicle-mounted application A i Dynamic startup priority, I(A i ) represents the vehicle-mounted application A i The static priority of the system, α represents the weight of the preset static priority, F(A i ) represents the vehicle-mounted application A i The usage frequency of the algorithm is β, and β represents the weight of the preset usage frequency.

[0072] In this optional embodiment, the static priority represents the intrinsic importance of the application. Some key system applications or applications closely related to driving safety, such as navigation, vehicle diagnosis, etc., can be assigned a higher static priority, which ensures that these applications can obtain a higher startup priority regardless of the actual frequency of use, thereby ensuring the stability and security of the system. The frequency of use reflects the user's actual usage preferences for different in-vehicle applications. Incorporating the frequency of use into the priority calculation allows the system to dynamically adapt to the user's habits. The user's frequently used applications will automatically obtain a higher startup priority, thereby improving the user experience; infrequently used applications will receive a lower priority accordingly, which can avoid unnecessary waste of resources.

[0073] The weight coefficients α and β in the above formula provide flexibility to adjust the static priority and the influence of usage frequency. These two coefficients can be set according to the specific system design and user needs. For example, for a system that does not require high entertainment functions, a larger α value can be set to emphasize the importance of key in-vehicle applications; while for a system that focuses on entertainment functions, a larger β value can be set to adapt to the personalized needs of users.

[0074] It can be seen that this optional embodiment linearly combines static priority and dynamic usage frequency, which can dynamically adapt to the user's actual usage habits while ensuring system stability and security. This adaptive resource management method can significantly improve the startup efficiency of in-vehicle applications, reduce unnecessary resource usage, and provide a more personalized user experience.

[0075] S104, starting each of the vehicle-mounted applications to its corresponding application startup state according to the dynamic startup priority and the static priority; wherein the application startup state includes a preliminary loading state and an active state;

[0076] In an optional embodiment, according to the dynamic startup priority and the static priority, the step of starting each of the in-vehicle applications to its corresponding application startup state includes:

[0077] sorting all the vehicle-mounted applications from high to low according to the dynamic startup priority;

[0078] According to the static priority, the sorted in-vehicle applications are started in sequence to their preset application start states.

[0079] In this optional embodiment, algorithms such as bubble sort, selection sort, insertion sort, quick sort, merge sort, heap sort, etc. can be used to sort all the vehicle-mounted applications from high to low according to the dynamic startup priority, and the embodiment of the present invention is not limited thereto.

[0080] The initial loading state means that the basic operating environment of the in-vehicle application is ready, but the main interface (i.e., Activity) of the in-vehicle application has not yet been started. Specifically, the application process has been created and the Application object of the in-vehicle application has been initialized, but the main interface of the application has not yet been created and displayed, and the user cannot interact with the in-vehicle application.

[0081] The active state is the state after the initial loading state during the process of fully starting the in-vehicle application. In this state, the main interface of the in-vehicle application has been created and rendered.

[0082] In an optional embodiment, the step of starting the sorted in-vehicle applications in sequence to their preset application start states according to the static priorities includes:

[0083] Traverse the sorted in-vehicle applications, and for each in-vehicle application, determine the corresponding static priority:

[0084] If it is the first static priority, start it as active;

[0085] If it is the second static priority level or the third static priority level, start it as a preliminary loading state;

[0086] If it is the fourth static priority, it will not be started.

[0087] In this optional embodiment, the first static priority refers to the launcher application of the vehicle system. The launcher application is responsible for presenting the main interface of the vehicle system, providing the launch entry of the vehicle application, and managing the running status of the vehicle application. It is the core component of the vehicle system and directly affects the user's first impression of the system and the overall experience. The first static priority is, for example, the main interface application of the vehicle system, the application launcher, the task manager, etc.

[0088] The second static priority corresponds to the status bar applications and some core function applications of the vehicle system. Status bar applications are usually displayed at the top or bottom of the main interface, providing system status information and quick control entrances. Core function applications provide basic functions of the vehicle system, such as application lists, air conditioning control, navigation services, etc. These applications are crucial to the usability and functionality of the vehicle system and need to be started first when the system starts to ensure that basic functions are available at any time.

[0089] The third static priority refers to other important applications in the vehicle system. These applications provide some advanced functions or enhanced functions. Although they are not used as frequently as core function applications, they still have an important impact on the user experience. These applications need to be started relatively first when the system is started to ensure that they can quickly respond to user requests, such as system settings, driving recorder applications, etc.

[0090] The fourth static priority refers to other common applications, which provide some auxiliary functions or entertainment functions. Although they can enrich the user experience, they are not essential components of the vehicle system. These applications can be delayed when the system starts, or dynamically started according to the actual frequency of use to save system resources, such as game applications, weather forecasts, etc.

[0091] It can be seen that this optional embodiment can determine which in-vehicle applications are most likely to be used by the user in the current situation by sorting all in-vehicle applications according to the dynamic startup priority. This sorting process takes into account the actual frequency of use and the preset importance of each in-vehicle application, and can dynamically adapt to the user's usage habits. The in-vehicle applications ranked in the front will obtain a higher startup priority, so that the user's needs can be responded to more quickly. Secondly, after sorting, different in-vehicle applications are started to different states according to the static priority of the in-vehicle application. This hierarchical startup strategy can further optimize the utilization of system resources. For some key system applications or safety-related in-vehicle applications, even if they are not at the front in the dynamic priority sorting, they will be started to the active state because of their high static priority to ensure the stability and reliability of the system. For some minor in-vehicle applications, even if they are at the front in the sorting, they may only be started to the preliminary loading state to save resources. This startup state allocation strategy not only improves the user experience, but also takes into account the overall performance of the system.

[0092] In general, by combining dynamic priority sorting and static priority hierarchical startup, this embodiment provides an intelligent in-vehicle application management method. It can dynamically adjust resource allocation according to the actual usage of users, while also taking into account the inherent needs of the system. This can not only speed up the startup of commonly used applications and improve user satisfaction, but also ensure the reliable operation of key applications and ensure the stability of the system.

[0093] S105 . Respond to a request to start any vehicle-mounted application, determine whether the vehicle-mounted application is in an active state, and if not, start the vehicle-mounted application in an active state.

[0094] In an optional embodiment, the in-vehicle application management method further includes:

[0095] Monitor vehicle applications for cleaning;

[0096] Determine the corresponding static priority:

[0097] If it is the first static priority, clear its application startup state to active state;

[0098] If it is the second static priority or the third static priority, clearing its application startup state to the initial loading state;

[0099] If it is the fourth static priority, the in-vehicle application is cleared.

[0100] In this optional embodiment, the in-vehicle applications to be cleaned up refer to in-vehicle applications that are marked by the system as needing to be cleaned up due to some reasons (such as memory leaks, long-term non-use, etc.). These in-vehicle applications often occupy too many system resources, or have entered an unstable state, which may affect the overall performance and stability of the system.

[0101] It can be seen that this optional embodiment adopts different cleaning methods for vehicle-mounted applications of different importance according to the static priority of the vehicle-mounted applications. For the most important vehicle-mounted applications of the first static priority, they are reset to the active state to ensure that the system main interface and core functions are not affected; for vehicle-mounted applications of the second static priority or the third static priority, they are cleaned to the initial loading state to provide fast recovery capabilities while recycling resources; for ordinary vehicle-mounted applications, they are directly cleaned to maximize resource recovery. This intelligent resource management mode can significantly improve the overall performance and user experience of the vehicle-mounted electronic system, reduce the risk of system instability, and is of great significance for optimizing the reliability and efficiency of the vehicle-mounted electronic system.

[0102] See also Figure 2 As shown, Figure 2 FIG. 1 is a schematic diagram of a management system for vehicle-mounted applications disclosed in an embodiment of the present invention. Figure 2 As shown, the system comprises:

[0103] A first starting module 201, used to start the vehicle control unit after the vehicle power system is activated;

[0104] An acquisition module 202 is used to acquire the usage frequency of each vehicle-mounted application;

[0105] The calculation module 203 is used to calculate the dynamic startup priority of the vehicle-mounted application according to the usage frequency of each vehicle-mounted application and the preset static priority; wherein the static priority includes: a first static priority, a second static priority, a third static priority and a fourth static priority;

[0106] The second startup module 204 is used to start each of the vehicle-mounted applications to its corresponding application startup state according to the dynamic startup priority and the static priority; wherein the application startup state includes a preliminary loading state and an active state;

[0107] The response module 205 is used to respond to a start request for any vehicle-mounted application, determine whether the vehicle-mounted application is in an active state, and if not, start the vehicle-mounted application in an active state.

[0108] For the specific definition of the management system of vehicle-mounted applications, please refer to the definition of the management method of vehicle-mounted applications in the above text, which will not be repeated here. Each module in the above-mentioned management system of vehicle-mounted applications can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the electronic device in hardware format, or can be stored in the memory of the electronic device in software format, so that the processor can call the operations corresponding to the above modules.

[0109] It should be noted that, in order to highlight the innovative part of the present invention, the present embodiment does not introduce modules that are not closely related to solving the technical problem proposed by the present invention, but this does not mean that there are no other modules in the present embodiment.

[0110] like Figure 3 As shown, the electronic device 1 provided by the present invention may include a memory 12, a processor 13 and a bus, and may also include a computer program stored in the memory 12 and executable on the processor 13, such as a management program for vehicle-mounted applications.

[0111] The memory 12 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a mobile hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a magnetic memory, a disk, an optical disk, etc. The memory 12 may be an internal storage unit of the electronic device 1 in some embodiments, such as a mobile hard disk of the electronic device 1. The memory 12 may also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device 1. Further, the memory 12 may also include both an internal storage unit and an external storage device of the electronic device 1. The memory 12 may not only be used to store application software and various types of data installed in the electronic device 1, such as the management code of the vehicle-mounted application, etc., but may also be used to temporarily store data that has been output or is to be output.

[0112] In some embodiments, the processor 13 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips. The processor 13 is the control core (Control Unit) of the electronic device 1, and uses various interfaces and lines to connect various components of the entire electronic device 1, and executes or executes programs or modules (such as management programs for vehicle-mounted applications, etc.) stored in the memory 12, and calls data stored in the memory 12 to execute various functions of the electronic device 1 and process data.

[0113] The processor 13 executes the operating system and various installed application programs of the electronic device 1. The processor 13 executes the application programs to implement the steps in the above-mentioned vehicle-mounted application management method.

[0114] Exemplarily, the computer program may be divided into one or more modules, which are stored in the memory 12 and executed by the processor 13 to complete the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program in the electronic device 1. For example, the computer program may be divided into a first startup module 201, an acquisition module 202, a calculation module 203, a second startup module 204, and a response module 205.

[0115] The above-mentioned integrated unit implemented in the form of a software function module can be stored in a computer-readable storage medium, and the storage medium can be non-volatile or volatile. The above-mentioned software function module is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, a computer device, or a network device, etc.) or a processor to perform part of the functions of the management method of the vehicle-mounted application described in each embodiment of the present application.

[0116] In summary, the present invention discloses a method, system, device and medium for managing in-vehicle applications, which can optimize the startup sequence according to the actual usage of the user, ensure that frequently used applications can be started faster and reach an active state, and improve the response speed of the system and the user experience. At the same time, by introducing dynamic priorities, the method can adapt to changes in the frequency of application use and adjust the startup sequence in a timely manner, thereby improving the adaptability and flexibility of the system. In addition, the present invention also introduces the concept of application startup state, divides the application startup process into two stages: initial loading and active, and judges the current state of the application when a startup request is received, avoiding unnecessary repeated startups and further optimizing the utilization efficiency of system resources. Therefore, the present invention effectively overcomes the various shortcomings of the prior art and has a high industrial utilization value.

[0117] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A method for managing vehicle-mounted applications, characterized in that: The method comprises: After the vehicle power system is activated, the on-board control unit is started; Get the usage frequency of each in-vehicle application; Calculating the dynamic startup priority of the in-vehicle application according to the usage frequency of each in-vehicle application and the preset static priority; wherein the static priority includes: a first static priority, a second static priority, a third static priority and a fourth static priority; According to the dynamic startup priority and the static priority, each of the vehicle-mounted applications is started to its corresponding application startup state; wherein the application startup state includes a preliminary loading state and an active state; In response to a start request for any vehicle-mounted application, it is determined whether the vehicle-mounted application is in an active state, and if not, the vehicle-mounted application is started in an active state.

2. A method for managing vehicle-mounted applications according to claim 1, characterized in that: The step of calculating the dynamic startup priority of the in-vehicle application according to the usage frequency and the preset static priority of each in-vehicle application comprises: The dynamic startup priority of the vehicle application is calculated according to the following formula: P(A i )=α·I(A i )+β·F(A i ); Among them, P(A i ) represents the vehicle-mounted application A i Dynamic startup priority, I(A i ) represents the vehicle-mounted application A i The static priority of the system, α represents the weight of the preset static priority, F(A i ) represents the vehicle-mounted application A i The usage frequency of the algorithm is β, and β represents the weight of the preset usage frequency.

3. A method for managing vehicle-mounted applications according to claim 1, characterized in that: The step of obtaining the usage frequency of each vehicle-mounted application includes: Determine the time period corresponding to the current time point in the historical statistical data to obtain the current time period; The usage frequency of each in-vehicle application by the current user in the current time period is obtained from the historical statistical data.

4. A method for managing vehicle-mounted applications according to claim 3, characterized in that: The step of starting each of the vehicle-mounted applications to its corresponding application startup state according to the dynamic startup priority and the static priority includes: sorting all the vehicle-mounted applications from high to low according to the dynamic startup priority; According to the static priority, the sorted in-vehicle applications are started in sequence to their preset application start states.

5. A method for managing vehicle-mounted applications according to claim 4, characterized in that: The step of sequentially starting the sorted in-vehicle applications to their preset application startup states according to the static priorities includes: Traverse the sorted in-vehicle applications, and for each in-vehicle application, determine the corresponding static priority: If it is the first static priority, start it as active; If it is the second static priority level or the third static priority level, start it as a preliminary loading state; If it is the fourth static priority, it will not be started.

6. A method for managing vehicle-mounted applications according to any one of claims 1 to 5, characterized in that: After the vehicle power system is activated, the steps to start the on-board control unit include: After the vehicle power system is activated, the on-board control unit is started; Play the startup animation.

7. A method for managing vehicle-mounted applications according to any one of claims 1 to 5, characterized in that: The in-vehicle application management method further includes: Monitor vehicle applications for cleaning; Determine the corresponding static priority: If it is the first static priority, clear its application startup state to active state; If it is the second static priority or the third static priority, clearing its application startup state to the initial loading state; If it is the fourth static priority, the in-vehicle application is cleared.

8. A management system for vehicle-mounted applications, characterized in that: The system comprises: A first starting module, used to start the vehicle control unit after the vehicle power system is activated; An acquisition module, used to acquire the usage frequency of each vehicle-mounted application; A calculation module, configured to calculate the dynamic startup priority of the in-vehicle application according to the usage frequency of each in-vehicle application and a preset static priority; wherein the static priority includes: a first static priority, a second static priority, a third static priority and a fourth static priority; A second startup module, configured to start each of the vehicle-mounted applications to its corresponding application startup state according to the dynamic startup priority and the static priority; wherein the application startup state includes a preliminary loading state and an active state; The response module is used to respond to a start-up request for any vehicle-mounted application, determine whether the vehicle-mounted application is in an active state, and if not, start the vehicle-mounted application in an active state.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method for managing in-vehicle applications according to any one of claims 1 to 7 are implemented.

10. A storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method for managing in-vehicle applications according to any one of claims 1 to 7 are implemented.

Images