Task management method and device of operating system and vehicle
By receiving user requests to display and update the task list of dual operating systems, and using RPC communication module to collaborate management, the problem of inefficient task management in dual operating systems is solved, achieving more efficient task management and user experience improvement.
Patent Information
- Application Number
- CN202510372592.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-25
- Publication Date
- 2025-08-19
AI Technical Summary
The existing multi-task management methods cannot effectively manage tasks in dual-operating system vehicles, resulting in inefficient management and poor user experience.
By receiving a user-triggered task list display request, displaying the operation task information associated with the first operating system and/or the second operating system, and updating the task list according to user operation instructions, the RPC communication module is used to realize communication and collaborative management between the two operating systems.
It improves the efficiency of multi-operating system devices when managing multi-tasks, makes the devices more intelligent and convenient, and improves the user experience.
Smart Images

Figure CN120508357A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of operating system technology, and specifically relates to an operating system task management method, device and vehicle, as well as electronic equipment, vehicle-mounted systems, computer-readable storage media and computer program products. Background Art
[0002] As vehicles become more intelligent, the in-vehicle operating system has become an indispensable part of the vehicle. As users' demands for the performance of the vehicle's intelligent cockpit increase, vehicles are no longer limited to being configured with a single operating system, but are gradually increasing to being configured with two operating systems. How to manage tasks between these dual operating systems is a technical problem that needs to be solved. Summary of the Invention
[0003] This application aims to solve at least one of the technical problems existing in the prior art. To this end, this application proposes an operating system task management method, device, and vehicle, as well as an electronic device, a vehicle-mounted system, a computer-readable storage medium, and a computer program product, which can effectively improve the efficiency of multi-operating system devices in managing multiple tasks, thereby making the device more intelligent and convenient, and thus improving the user experience.
[0004] In a first aspect, an embodiment of the present application provides a task management method for an operating system, comprising:
[0005] Receive user-triggered task list display requests;
[0006] The running task list is displayed based on the task list display request, where the running task list includes running task information associated with application programs of the first operating system and / or the second operating system.
[0007] In some embodiments, it further includes:
[0008] receiving an application operation instruction triggered by a user, where the application operation instruction is used to operate an application program of the first operating system and / or the second operating system;
[0009] Update the running task list based on the application operation instructions.
[0010] In some embodiments, the receiving of the user-triggered application operation instruction includes at least one of the following:
[0011] receiving an application operation instruction triggered by a first preset operation of an application icon of the first operating system and / or the second operating system displayed on the application center interface by a user;
[0012] receiving an application operation instruction triggered by a second preset operation performed by a user on the application display interface;
[0013] An application operation instruction triggered by a third preset operation of the user on the running task information in the running task list is received.
[0014] In some embodiments, the application operation instruction includes at least one of a start operation instruction, a put foreground instruction, a put background instruction, and a restart operation instruction.
[0015] In some embodiments, updating the running task list based on the application operation instruction includes:
[0016] Generate a task operation request based on the application operation instruction;
[0017] updating the task queue of the first operating system and / or the second operating system based on the task operation request;
[0018] The running task list is updated based on the updated task queue.
[0019] In some embodiments, the task operation request includes a first task operation request executed locally by the first operating system;
[0020] Updating a task queue of the first operating system based on the task operation request includes:
[0021] A first task operation request is executed in the first operating system to process a running task associated with the application program and update a first task queue of the first operating system.
[0022] In some embodiments, updating the running task list based on the updated task queue includes:
[0023] The first operating system updates the running task list based on the first task queue
[0024] In some embodiments, the task operation request includes a second task operation request executed by the second operating system, and updating the second task queue of the second operating system based on the task operation request includes:
[0025] The first operating system sends the second task operation request to the second operating system, and the second operating system executes the second task operation request to process the running task associated with the application program and updates the second task queue of the second operating system.
[0026] In some embodiments, further comprising:
[0027] The first operating system receives running task update information sent by the second operating system, where the running task update information is generated based on the updated second task queue;
[0028] The first operating system updates the running task list based on the running task update information.
[0029] In some embodiments, further comprising:
[0030] The first operating system sends a task queue monitoring request to the second operating system, so that the second operating system generates running task update information when monitoring that the task queue is updated.
[0031] In some embodiments, further comprising:
[0032] The first operating system receives initial information of a running task sent by the second operating system, where the initial information of the running task is generated by the second operating system based on an initial task queue of the second operating system;
[0033] The first operating system generates an initial running task list according to the initial task queue of the first operating system and the initial running task information.
[0034] In some embodiments, further comprising:
[0035] Get the application icon information from the application management module;
[0036] An initial running task list is generated or the running task list is updated based on the icon information of the application.
[0037] In some embodiments, the running task information in the above-mentioned running task list is arranged according to task activity.
[0038] In some embodiments, the first operating system and the second operating system communicate with each other via an RPC communication module.
[0039] In some embodiments, the first operating system includes at least one of an Android operating system and a Linux operating system, and the second operating system includes at least one of an Android operating system and a Linux operating system.
[0040] In a second aspect, an embodiment of the present application provides an electronic device comprising: a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the task management method of the operating system as described in the first aspect are implemented.
[0041] In a third aspect, an embodiment of the present application provides a vehicle system, on which a first operating system and a second operating system run, and the vehicle system includes the electronic device of the second aspect.
[0042] In a fourth aspect, an embodiment of the present application provides a vehicle, comprising the vehicle-mounted system described in the third aspect.
[0043] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the task management method of the operating system as described in the first aspect are implemented.
[0044] In a sixth aspect, an embodiment of the present application provides a computer program product, which, when executed by a processor of a vehicle, implements the steps of the task management method of the operating system as described in the first aspect.
[0045] The technical solution provided by this application receives a task list display request triggered by a user and displays a running task list based on the task list display request. The running task list includes running task information associated with applications in the first operating system and / or the second operating system. Since the above technical solution can manage running tasks in multiple operating systems in the same task list, it can conveniently and quickly manage running tasks in multiple operating systems and effectively improve the efficiency of multi-operating system devices in managing multiple tasks, thereby making the device more intelligent and convenient, and thus improving the user experience.
[0046] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become obvious from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:
[0048] Figure 1 This is a flowchart of a task management method for a dual operating system in an embodiment of the present application;
[0049] Figure 2 This is a flowchart of updating a running task list according to an embodiment of the present application;
[0050] Figure 3 This is another flowchart of updating the running task list in an embodiment of the present application;
[0051] Figure 4 This is a schematic diagram of an updated running task list in an embodiment of the present application;
[0052] Figure 5 A flowchart of generating or updating a running task list according to an embodiment of the present application is provided;
[0053] Figure 6 This is an overall framework diagram of a task management system of an operating system that can be used in embodiments of the present application;
[0054] Figure 7 This is a schematic diagram of a process for synchronizing task information in an embodiment of the present application;
[0055] Figure 8 This is a schematic diagram of a process for actively synchronizing task information in an embodiment of the present application;
[0056] Figure 9 This is a flow chart of a passive synchronization operation task information in an embodiment of the present application;
[0057] Figure 10 This is a schematic diagram of a task management structure in an embodiment of the present application;
[0058] Figure 11 This is a schematic structural diagram of an electronic device according to an embodiment of the present application;
[0059] Figure 12 This is a structural diagram of a vehicle system in an embodiment of the present application;
[0060] Figure 13 This is a structural diagram of a vehicle in an embodiment of the present application. DETAILED DESCRIPTION
[0061] The following describes embodiments of the present application in more detail with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are for illustrative purposes only and are not intended to limit the scope of protection of the present application.
[0062] It should be understood that the various steps described in the method embodiments of the present application can be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.
[0063] As described in the background technology, existing vehicles are gradually being equipped with two operating systems, but the existing multi-tasking management method can still only manage the tasks of a single system in the vehicle and cannot perform multi-tasking management in the dual operating systems. As a result, the efficiency of managing tasks in the dual systems of vehicles with dual operating systems is low, resulting in a poor user experience.
[0064] Therefore, this application provides a technical solution for a task management method of an operating system. Figure 1 A flowchart of a task management method for an operating system provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the following steps are included:
[0065] Step 101: Receive a task list display request triggered by a user;
[0066] The task list in the technical solution provided in the embodiment of the present application includes various tasks that need to be executed by the system or processed by the user, as well as corresponding task information. These tasks and task information may come from different operating systems and applications, and are usually displayed in the form of a list so that the user can understand which tasks currently need to be processed and how to process the above tasks; the task list display request refers to an instruction issued by the user to the system in some way, such as clicking a button, triggering an event, and executing a specific command, etc., to request the system to display the current task list on the interface, for example, displaying the current task list on the user interface.
[0067] Step 102: Display a running task list based on the task list display request, where the running task list includes running task information associated with application programs of the first operating system and / or the second operating system.
[0068] On the basis of step 101, the running task list can be displayed according to the received task list display request. Specifically, when a task list display request triggered by the user is received, the system will display the current task list on the interface according to the above request, for example, display the running task list on the user interface. The above running task list refers to a group of tasks that the current system is executing or will execute, and a task list formed by the task information of the above tasks, which includes running task information associated with the application of at least one of the first operating system and the second operating system. The above running task information refers to the relevant information of each running task in the task list, such as task name, task status, task execution time, task description, and task object, wherein the task object includes icon information of the application corresponding to the task.
[0069] As described above, managing multiple tasks in multiple operating systems through the above-mentioned operating system task management method can effectively improve the efficiency of multi-operating system devices in managing multiple tasks, thereby making the device more intelligent and convenient, thereby improving the user experience.
[0070] Typically, as user needs change, the tasks that the system needs to perform will change. These changes may come from new instructions from the user, updates to application status, adjustments to system resources, or triggering of external events. Therefore, in order to maintain the responsiveness and accuracy of the system, the task list needs to be continuously updated. By dynamically managing the task list, the system can allocate resources more efficiently and ensure that tasks are executed in the order and efficiency expected by the user. Therefore, in an embodiment of the present application, the current task list can be updated according to the instructions triggered by the user, specifically, Figure 2 As shown, the following steps are included:
[0071] Step 201: Receive an application operation instruction triggered by a user, where the application operation instruction is used to operate an application program of the first operating system and / or the second operating system;
[0072] This step is to receive the above application operation instructions after the user triggers the application operation instructions through some interactive method. For example, the user triggers the application operation instructions of a certain application in the application center interface through physical buttons, touch screen control, voice control, etc. The above application operation instructions are used to operate the corresponding application, such as opening the corresponding application, closing the corresponding application, and executing specific functions in the corresponding application. In this application, the above application operation instructions can be used to operate the application in the first operating system, or the application in the second operating system, or the application in both of the above operating systems.
[0073] In an embodiment of the present application, the above-mentioned application operation instructions include various types of instructions, such as start operation instructions, put foreground instructions, put background instructions, and restart operation instructions. The start operation instruction is used to activate and run the corresponding application, such as starting WeChat; the put foreground instruction is used to switch the interface of the application currently in the background from the background to the foreground so that the user can interact with it directly; the put background instruction is used to switch the current application interface from the foreground to the background to temporarily hide the application interface so that the user can handle other tasks without closing the application; the restart operation instruction is used to restart the application to solve possible operating problems or update the application status. The diversity of these instructions ensures that the system can meet the user's application management needs in different scenarios to improve the user's application management experience.
[0074] Step 202: Update the running task list based on the application operation instruction.
[0075] On the basis of step 201, task information associated with the application in the corresponding operating system is further formed according to the received application operation instructions, and the current task list is updated accordingly. The above-mentioned task information includes the task identifier, operation type and task execution time, etc., wherein the task identifier is used to distinguish different tasks in the task list; the operation type is used to describe the specific operation type of the task, such as opening the application, closing the application, executing specific functions such as sending messages, starting services, loading data, etc. within the application; the execution time includes the task start time, end time and execution duration, etc. The above-mentioned updating of the running task list refers to operations such as adding, deleting and modifying the running task list, for example, adding a new task of the first operating system to the running task list.
[0076] In the embodiment of the present application, the system can receive a variety of user-triggered application operation instructions to achieve control and management of system functions and services, including the following:
[0077] The first is to receive an application operation instruction triggered by the user's first preset operation on the application icon of the first operating system and / or the second operating system displayed on the application center interface. Specifically, when the user performs the first preset operation on the application center interface for the application icon corresponding to the first operating system, or the second operating system, or the application of the above two operating systems, the system will receive the application operation instruction triggered thereby. For example, the user can start the application by clicking the application icon of an application on the application center interface. At this time, the system will receive a start operation instruction. The above-mentioned first preset operation refers to the operation of completing a specific function in a preset manner when the user interacts with the interface. For example, the operation of starting the application can be set to be completed by "clicking".
[0078] The second method involves receiving application operation instructions triggered by a second preset user action on the application display interface. For example, if a user clicks a specific function button on the application display interface, the system will receive the instruction triggered by this click and subsequently perform the corresponding function operation accordingly. The aforementioned second preset operation refers to the operation of completing a specific function in a pre-set manner when the user interacts with the interface. For example, a user can close a running application on the application display interface by clicking a button, swiping the screen, or other specified interactive actions.
[0079] The third type is receiving an application operation command triggered by a user performing a third preset operation on a running task in the running task list. For example, when a user views the running task list and taps a task item, swipes to change the order of task execution, or long-presses to access more operation options, the system will receive the application operation command triggered by the above operation. The above third preset operation is the same as the first preset operation command or the second preset operation command.
[0080] In some embodiments, if the system detects a fault or abnormal situation, in order to ensure the continuity of the user experience, the system will not only immediately initiate a fault detection and processing mechanism, but also automatically generate corresponding application operation instructions based on preset strategies or algorithms to quickly respond to the fault, such as closing the application, adjusting the system configuration, or performing application data recovery operations to ensure the integrity and security of the application data, thereby reducing the impact on the user.
[0081] In some embodiments, Figure 3 for Figure 2 The specific execution flow diagram of step 202 is shown in FIG. Figure 3 As shown, the following steps are included:
[0082] Step 301: Generate a task operation request based on the application operation instruction;
[0083] In step 201, after the system receives the application operation instruction triggered by the user, it generates a corresponding task operation request based on the specific content of the above application operation instruction. Specifically, the system will form a task operation request based on information such as the type of application operation instruction, the target object, and the required parameters to ensure that the user's desired operation can be accurately completed subsequently. For example, if the user triggers an application operation instruction to close the currently running application by clicking a button, the system will generate an operation request to close the task and include detailed information about the above application so that the closing operation can be performed subsequently. The above task operation request refers to a set of instructions generated by the system based on the application operation instruction triggered by the user to guide the system to perform a specific task or operation. It includes all necessary information required to perform the task, such as the task type, target object, operation parameters, etc., to ensure that the system can accurately understand and execute the user's intention.
[0084] Step 302: updating the task queue of the first operating system and / or the second operating system based on the task operation request;
[0085] On the basis of step 301, according to the generated task operation request, the task queue of at least one of the first operating system and the second operating system is updated. Specifically, after receiving the task operation request, the system will analyze the content of the above request and perform corresponding operations on the task queue, for example, removing, pausing, or continuing to execute a task from the task queue, thereby updating the above task queue. The above task queue is used to manage and schedule a list of tasks that are waiting to be executed or are about to be executed. Each task queue usually contains a series of unsorted task items and task information of the task items. These task items represent various operations or functions that the system needs to complete. The various task items in the task queue are executed in sequence according to the order of their generation time. For example, the task items generated first will be executed by the system first.
[0086] Step 303: Update the running task list based on the updated task queue.
[0087] After the task queue is updated in step 302, the above-mentioned task queue can be further used to update the running task list. Specifically, the system will traverse the above-mentioned task queue, check the task items therein, and add, delete, modify, etc. to the running task list based on the number of task items in the task queue, status and other information to achieve its update. In this way, the running task list can reflect the execution progress and status of tasks in each operating system in real time, so that users can grasp the task dynamics at any time, which greatly improves the user's task management experience. For example, when updating the running task list based on the updated task queues of two types of operating systems, the content of the task queue of the first operating system and the content of the task queue of the second operating system can be fused through a related fusion algorithm to obtain a fused running task list, that is, the running task list is updated and a unified view is formed in the system. At this time, the updated running task list is as follows: Figure 4 In this way, we can avoid displaying redundant task information while retaining the complete context information of the task.
[0088] In some embodiments, the above-mentioned task operation request may include a first task operation request executed locally by the first operating system, which refers to an operation request generated in the first operating system and required to be executed to complete the task in the first operating system. Therefore, when the system updates the task queue of the first operating system according to the received task operation request, it will perform corresponding operations in the first operating system according to the content of the above-mentioned request to process the running tasks associated with the application in the first operating system. In the process of performing these operations, the system will also synchronously update the task queue in the first operating system, that is, perform real-time maintenance on the first task queue. In this way, the user can clearly understand which task items are running or will be running in the system so as to manage them. The above-mentioned first task queue refers to the task queue of the first operating system.
[0089] In an embodiment of the present application, after the first task queue is updated according to the first task operation request, the running task list can be further updated using the above-mentioned first task queue to ensure that the above-mentioned running task list is the latest running task list, which is convenient for users to manage tasks. Specifically, the first operating system performs corresponding operations on the running task list based on the number, status and other information of the task items in the first task queue, for example, adding task items to the running task list, deleting completed or canceled task items, and modifying the status or priority of the executing task, thereby updating the running task list.
[0090] In some embodiments, the above-mentioned task operation request may also include a second task request executed by the second operating system, which refers to an operation request generated in the first operating system and required to be executed in the second operating system to complete the task. Therefore, like the operation on the first operating system side, when it is determined that the task operation request is a second task operation request that needs to be executed on the second operating system side, and the task queue of the second operating system, that is, the second task queue, can be updated according to the above-mentioned second task operation request, the first operating system will send the above-mentioned second task operation request to the second operating system. After the second operating system receives the above-mentioned request, it will perform corresponding operations on the system side according to the content of the second task request to process the running tasks associated with the application in the second operating system, and in the process of executing these operations, the system will also synchronously update the task queue in the second operating system, that is, perform real-time maintenance on the second task queue. The above-mentioned second task queue refers to the task queue of the second operating system.
[0091] In an embodiment of the present application, after updating the second task queue on the second operating system side according to the second task operation request, the relevant information can also be sent to the first operating system so that the first operating system can update the running task list accordingly, thereby maintaining the synchronization of task information between the two operating systems. Specifically, after the second operating system updates the second task queue, running task update information will be formed, and then the second operating system will send the above-mentioned running task update information to the first operating system. After the system receives the above-mentioned running task update information, it can further update the running task list based on the information to ensure that the task management information between the two systems remains consistent and real-time. The above-mentioned running task update information includes information such as the number of task items, the status, progress, results and priority of the task.
[0092] In some embodiments, the first operating system can also send a task queue monitoring request to the second operating system so that the second operating system generates corresponding running task update information after monitoring the task queue update. Specifically, the first operating system sends a task monitoring request to the second operating system. After receiving the above request, the second operating system uses the task monitoring unit within the system to monitor the second task queue. When changes are detected in the above task queue, such as the addition of a new task, the change of the status of an existing task, the adjustment of the task priority, etc., the running task update information is generated and then sent to the first operating system for updating the running task list. If the second task queue still changes after sending the running task update information, the task monitoring unit will continue to monitor these changes and repeat the above information generation and sending process. If the task queue does not change, the task monitoring unit remains silent and continues to monitor to wait for possible updates. The above task queue monitoring request is a signal or instruction used to inform the second operating system that the first operating system wishes to monitor updates to its task queue. The task monitoring unit is a component or module used to monitor the task list, which is used to monitor the task queue of the second operating system so as to respond promptly when information such as the number of task items, task status, activity and priority changes.
[0093] In an embodiment of the present application, before monitoring the second task queue of the second operating system through the task monitoring unit, a corresponding operation can also be performed to start the task monitoring unit. Specifically, the first operating system can send a registration task monitoring request to the task monitoring unit to trigger the startup of the task monitoring unit. For example, the system sends the registration task monitoring request to the task monitoring unit through communication mechanisms such as inter-process communication and network requests. After receiving the above request, the task monitoring unit will register the listener, configure the monitoring parameters, and other processing, and then start monitoring the task queue for the second operating system. The above-mentioned registration task monitoring request is used to register with the task monitoring unit, that is, to inform the task monitoring unit that there is a need to monitor tasks and which tasks to monitor.
[0094] In the embodiment of the present application, an initial running task list may be generated according to the task queue of the operating system, specifically including the following situations:
[0095] In the first case, when generating an initial running task list based on the task queue of the first operating system, specifically, after the device is started, the running task information of the task items in the initial task queue of the first operating system can be sorted to generate the initial running task list. In this case, the initial running task list only includes the task running information of the first operating system. The aforementioned initial task queue refers to the collection of task items on the first operating system side when the device is started; the initial running task list refers to the running task list actively generated after sorting the task items in the initial task queue when the device is started.
[0096] In the second case, when generating an initial task running list based on the initial task queue of the second operating system, specifically, initial running task information is first generated based on the initial task queue of the second operating system. This information is then sent to the first operating system, and an initial running task list is generated based on the initial running task information. In this case, the initial running task list only includes the task running information of the second operating system. The initial running task information includes information such as the number of task items in the task queue of the second operating system, task status, result, and priority.
[0097] In the third case, an initial running task list is jointly generated based on the initial task queues of the first operating system and the second operating system. Specifically, the initial running task list is jointly generated based on the initial task queue of the first operating system and the initial running task information generated based on the initial task queue of the second operating system. At this time, the initial running task list includes the task running information of the first operating system and the second operating system.
[0098] In some embodiments, the initial running task list can also be generated based on the relevant information of the application, such as the icon information of the application. Figure 5As shown, the following steps are included:
[0099] Step 501: Obtain application icon information from the application management module;
[0100] This step is to obtain the icon information of the application from the application management module configured by the operating system. Specifically, the icon information of the application can be obtained from the application management module through the task management module. For example, the task management module of the first operating system obtains the icon information of the application of the first operating system from the application management module; the task management module of the second operating system obtains the icon information of the application of the second operating system from the application management module. The above-mentioned application management module is used for relevant information of the applications of the first operating system and the second operating system, such as the icon information of the application, version update instructions, new function introduction, and the icon and version of the new application; icon information refers to the collection of images and related attributes displayed by the application in the user interface, and its data volume is large, including information such as image files, resolution, size, file format, and interactive behavior. This information can not only help users quickly identify and start the required application, but also provide some basic visual features about the application.
[0101] Step 502: Generate an initial running task list or update the running task list based on the icon information of the application.
[0102] Based on step 501, an initial running task list can be generated based on the icon information of each application obtained, or the current running task list can be updated based on the above icon information to form a new running task list. Specifically, the initial running task list can be generated or the running task list can be updated based on the changes in the icon information of each application and the arrangement order of the icons of these applications in the system interface. That is, if the running task list has not been generated in the system, the initial running task list is generated; otherwise, the current running task list is updated using the icon information.
[0103] In some embodiments, when the running task information in the running task list can be sorted according to its activity, the following methods can be used to complete the sorting:
[0104] The first method: In the first operating system, the order of the tasks of the first operating system and the running task information of the second operating system is first disrupted. Then, the running task information of all tasks is reordered according to the task activity. The above activity is a comprehensive indicator, which can be determined based on factors such as task priority, task execution frequency, task execution time, and actual user needs. For example, if a user needs to activate the vehicle navigation function while driving a vehicle, the activation of the vehicle navigation task has a high activity and will be placed at the front of the fusion task list.
[0105] The second method: in the first operating system, first keep the order of the running task information in the running task list of the first operating system unchanged, and determine the activity of the corresponding tasks, and then insert the running task information received in the second operating system into the above-mentioned task list in sequence according to the task activity to complete the sorting of the running task information in the running task list. For example, for the 3 tasks in the first operating system, the activity of task 1b is 2, the activity of task 2b is 3, and the activity of task 3b is 5. For the 3 tasks synchronized by the second operating system, the activity of task 1a is 1, the activity of task 2a is 4, and the activity of task 3a is 6. After sorting the above tasks according to the task activity, the order of the running task information in the running task list is: running task information 1a, running task information 1b, running task information 2b, running task information 2a, running task information 3b and running task information 3a.
[0106] In an embodiment of the present application, the communication between the first operating system and the second operating system can be achieved through the RPC communication module, that is, the first operating system and the second operating system establish a two-way connection based on the RPC communication module, and based on the above-mentioned two-way connection, the first operating system sends information to the second operating system, or the second operating system sends information to the first operating system. For example, the second operating system sends the running task update information to the first operating system through the RPC communication module; the first operating system sends the second task operation request to the second operating system through the RPC communication module. This two-way communication capability not only greatly enhances the interactivity and synergy between the two operating systems, but also greatly improves the overall performance and flexibility of the system, bringing users a smoother and more convenient multi-tasking experience. The above-mentioned RPC communication module, that is, the Remote Procedure Call (RPC) communication module, is used to achieve communication between different operating systems.
[0107] In an embodiment of the present application, the task queues, running task update information, and obtained application icon information of the above-mentioned first operating system and second operating system can all be stored in a database, wherein various types of information of the first operating system can be stored in the database of the first operating system and can also be synchronously stored in the database of the second operating system. In this way, not only the integrity and consistency of the data are ensured, but also data sharing and interaction are allowed between different operating systems, providing strong support for cross-system task scheduling, resource allocation, and collaborative work of applications.
[0108] In an embodiment of the present application, a system performance recovery program is also provided in the above-mentioned operating system, which can automatically adjust system resource allocation based on information monitoring data such as the task queue or running task list of each operating system and the temperature of the device CPU. For example, when the server CPU temperature of the first operating system is too high, the current running task list will be analyzed, and tasks that do not need to be executed in a short time will be removed first, and the corresponding applications will be closed to reduce the temperature and load of the CPU.
[0109] In an embodiment of the present application, when a task in the running task list is unexpectedly terminated due to some factors, such as high CPU temperature, or other factors, the task management module in the operating system can quickly restore and restart the corresponding application based on the running task list, running task information, and other information to complete the corresponding task, thereby better maintaining the stability and continuity of the operating system. The above-mentioned task management module is used to start and terminate tasks, monitor task status, clear the multi-task list, and monitor its changes.
[0110] In some embodiments, the first operating system includes at least one of an Android operating system and a Linux operating system, and the second operating system includes at least one of an Android operating system and a Linux operating system. The Android operating system is a free and open source mobile operating system based on the Linux kernel; the Linux operating system is open source, stable, and flexible, and is widely used in multiple fields such as servers, embedded systems, and desktop environments. In this application, the first operating system and the second operating system can be a combination of different operating systems, such as one being Android and the other being Linux, or they can be the same operating system. The specific operating system can be determined based on the needs of the user and the application scenario.
[0111] In some embodiments, if the first operating system and the second operating system are respectively an Android operating system and a Linux operating system, then the system can be operated by Figure 6 The task management system of the operating system shown completes the task management of the operating system. Figure 6 The overall framework diagram of a task management system of an operating system includes an Android operating system 1 and a Linux operating system 2, wherein the Android operating system includes a task database module 11, a system service module 12, a task management module 13, a PRC communication module 14 and a refresh rate module 15, the task database module 11 is used to store task information of the Android operating system to ensure the persistence of information data; the system service module 12 is used to provide underlying support for the system and applications to ensure that the device can run efficiently and safely, which includes package management services, activity management services and activity task management services, etc. The package management service (PackageManagerService, abbreviated as: PMS) is mainly responsible for managing and maintaining application packages installed on the device, namely APK files; the activity management service (ActivityManagerService, abbreviated as: AMS) is mainly responsible for managing the life cycle, tasks, back-off stack and application process management of activities in the application, for example, it is responsible for starting, pausing, resuming and destroying activities; the activity task management service (Activity Task Manager Service, abbreviated as: ATMS) is Android The newly added system service class 10 takes on some of the work of AMS, mainly responsible for managing activities and their containers, such as tasks, stacks, and displays. It is used to manage and control the application's life cycle, task stack, window, and display. The above-mentioned system service module can work in conjunction with the task management module 13 through the inter-process communication (IPC) mechanism to ensure cross-process synchronization of application status. The task management module 13 interacts with the Android operating system through IPC and is used to start and terminate tasks, monitor task status, clear the multi-task list, and monitor its changes. The RPC communication module 14, also known as the Remote Procedure Call (RPC) communication module, is used to achieve efficient communication between the Android system and the Linux system, synchronize complete task information, and perform remote control. The refresh rate module 15 is used to dynamically adjust the screen refresh rate based on the content displayed on the screen.
[0112] The Linux operating system 2 includes a task database module 21, a task management module 22, an application management module 23 and an RPC communication module 24, wherein the task database module 21 is used to store task information of the Linux operating system to ensure the persistence of information data; the task management module 22 is used to view and control the running processes in the system, monitor the system resource usage and manage system performance, for example, for the control, information collection and process supervision of tasks on the Linux operating system side, and the synchronization, acquisition and control of tasks on the Android operating system side; the application management module 23 is used to manage and maintain the application presentation in the system to ensure the stable operation of the system, the reasonable allocation of resources and the efficient use of software, for example, the installation, update and uninstallation of software; the RPC communication module 24 is used to achieve efficient communication between the Android system and the Linux system, synchronize complete task information and perform remote control, etc.
[0113] Therefore, in an embodiment of the present application, a running task list can be generated or updated based on the task queue of the first operating system and the task queue of the second operating system on the basis of the task management system of the above-mentioned operating system. At this time, a two-way connection can be established between the first operating system and the second operating system. Once the connection is established, the task management module of the first operating system will actively send a running task information synchronization request to the task management module of the second operating system, so that the first operating system receives the running task update information of the second operating system sent by the task management module. After receiving the above-mentioned running task information synchronization request, the second operating system will generate the running task update information through the task queue and feed it back to the first operating system. Then, in the first operating system, based on the above-mentioned running task update information and the task queue of the first operating system, a running task list is generated, or the current running task list is updated. In this way, the running task information between the two systems can be ensured to maintain consistency and synchronization. The above-mentioned running task information synchronization request is a signal or instruction used to inform the task management module of the second operating system that the first operating system wishes to obtain its current initial running task information.
[0114] In an embodiment of the present application, while synchronizing the running task information of the two operating systems through the above embodiment to generate or update the running task queue, the task management module of the first operating system will also determine whether the application in the application management module within the system has completed synchronization, for example, synchronizing the icon information of the application. Specifically, while the running task information of the second operating system is synchronized to the first operating system, the first operating system will also check the application management module, that is, its task management module will send an application synchronization status request to the application management module, and the application management module will respond to the above request and feedback the application synchronization status information. If the synchronization status information of the application is completed synchronization status information, the task management module can determine that the synchronization of the application in the application management module is completed; if the synchronization status information of the application is in progress status information, the synchronization will continue, and the task management module will subsequently send an application synchronization status request to the application management module again until the synchronization of the application in the application management module is completed. The above application synchronization status request is a signal or instruction used to inform the application management module that the task management module wants to obtain the synchronization status information of the application; the application synchronization status information includes field information such as completed and in progress. For example, if application 1 is closed in the second operating system to reduce CPU temperature, the status information of application 1 will also be synchronized to the first operating system, and the status information of application 1 will be updated to ensure information consistency. In this way, synchronizing application information at the same time as task information not only ensures that the application icon information stored in the first operating system is the latest information, but also significantly reduces the amount of data between the two operating systems in subsequent operations, thereby improving system efficiency.
[0115] In an embodiment of the present application, when the device is a vehicle with dual operating systems, and the first operating system is an Android system and the second operating system is a Linux system, the task management and running task information synchronization between the two operating systems can be achieved through active synchronization and passive synchronization to generate a running task list or update the running task list. Specifically, the task information synchronization of the above two methods can be achieved through the Linux application management module, the Linux task management module, the Android task management module and the Android system service module, wherein the Linux application management module is used to manage the information of the application programs of the dual operating systems, for example, the icon information of the application programs in the synchronization task; the Linux task management module is responsible for the tasks, management scheduling and information monitoring of the Linux domain, and realizes cross-system interaction of task management with the Android system through the RPC communication module; the Android task management module is responsible for task management on the Android side, interacts with the Android system through IPC, and communicates with the Linux system through the RPC communication module to realize two-way synchronization of running task information; the Android system service module is responsible for receiving IPC calls for task management on the Android side to ensure that the Android task information is synchronized to the task management system on the Android side. For example, when synchronizing the running task information of the Android system to the Linux system, such as Figure 7 As shown, the following steps are included:
[0116] Step 701: Send a registration task monitoring request to the Android system;
[0117] After the vehicle is started and the Android system successfully establishes a connection with the Linux system, the Linux task management module will send a registration task monitoring request to the Android system.
[0118] Step 702: Android system registers task monitoring;
[0119] Based on step 701, the Android task management module notifies the process in the Android system service module to register a task monitor.
[0120] Step 703: The Linux application management module actively sends a task information synchronization request to the Android system;
[0121] After completing the above monitoring settings, when the synchronization of running task information is achieved through active synchronization, the Linux application management module sends a running task information synchronization request to the Android task management module of the Android system through the RPC communication module to inform the Android task management module to perform the running task information synchronization operation.
[0122] Step 704: The Android task management module sends a request to obtain running task information to the Android task service module;
[0123] Based on the received running task information synchronization request in step 703, the Android task management module sends a request to the Android task service module to obtain the current running task information of the Android system. The above-mentioned current running task information refers to the running task information that already exists in the Android system when the Android task management module receives the task information synchronization request.
[0124] Step 705: The Android task service module returns the running task information to the Android task management module;
[0125] On the basis of step 704, the Android task service module immediately responds to the request for obtaining the running task information after receiving the request, and sends the current running task information to the Android task management module.
[0126] Step 706: The Android system transmits the running task information to the Linux task management module of the Linux system;
[0127] In step 705, after the Android task management module obtains its running task information, it sends the above running task information to the Linux task management module again through the RPC communication module and stores it in the task database of the Linux system.
[0128] Step 707: The Linux task management module sends an application synchronization status request to the Linux application management module;
[0129] While executing steps 703 to 706 , in the Linux system, the Linux task management module sends an application synchronization status request to the Linux application management module to determine whether the application information in the system has been synchronized.
[0130] Step 708: The Linux application management module returns the application synchronization status information to the Linux task management module;
[0131] Based on step 707, after the Linux application management module receives the application synchronization status request, it sends the synchronization status information of the current application to the Linux application management module. If the synchronization status information of the application is completed synchronization status information, the Linux task management module can determine that the synchronization of the application in the application management module is completed; if the synchronization status information of the application is in progress status information, the synchronization will continue, and the Linux task management module will subsequently send the application synchronization status request to the application management module again until the synchronization of the application in the application management module is completed.
[0132] Step 709: The Linux task management module sends an instruction to control the Android task to the Android task management module;
[0133] By executing the above steps, the synchronization of running task information between operating systems can be achieved through active synchronization. At the same time, the synchronization of the above task information can also be completed through passive synchronization. At this time, the Linux task management module sends control Android task instructions to the Android task management module through the RPC communication module. The above instructions are used to specify which tasks the Android system performs.
[0134] Step 710: The Android task management module sends an application operation instruction to the Android task service module;
[0135] On the basis of step 709, the Android task management module sends application operation instructions such as start, restart and put in the foreground to the Android task service module according to the received control Android task instruction, so that it performs the above operations.
[0136] Step 711: The Android task service module monitors changes in the task queue and updates the task queue;
[0137] When executing step 710, the monitoring unit of the Android system monitors the changes of the task queue in real time, updates the task queue, and obtains the final task queue after executing the application operation instruction, and generates the running task update information of the task queue.
[0138] Step 712: The Android task service module returns the running task update information to the Android task management module;
[0139] Based on step 711, the Android task service module sends the running task update information to the Android task management module.
[0140] Step 713: The Android task management module sends running task update information to the Linux task management module. Subsequently, the running task queue is updated according to the above information and the task queue of the Linux system.
[0141] Step 714: The Linux task management module sends a request to the application management module to obtain application icon information;
[0142] While executing steps 709 to 713 , the Linux task management module sends a request to the application management module to obtain application icon information.
[0143] Step 715: The Linux application management module returns the application icon information to the Linux task management module.
[0144] Based on step 714, the Linux application management module sends the application icon information to the Linux task management module according to the received request.
[0145] In the embodiment of the present application, when the device is a vehicle with dual operating systems, and the first operating system is an Android system and the second operating system is a Linux system, and active synchronization is used to synchronize the running task information between the two systems to update the running task list, specifically, Figure 8 As shown, the following steps are included:
[0146] Step 801: Vehicle starts;
[0147] Start the vehicle and establish a connection between the Android system and the Linux system through the RPC communication module.
[0148] Step 802: Start Task Manager 2;
[0149] On the basis of step 801, the task manager 2 of the Linux system is started.
[0150] Step 803: Determine whether the task status is normal;
[0151] Whether the task status in the currently running task list on the Linux system side is normal, if normal, execute step 805, otherwise execute step 804. Determining whether the task status is normal means determining whether a system failure occurs.
[0152] Step 804: Read the task information in the task database and restore it to its original state;
[0153] In the above step 803, after determining that the task status is abnormal, the task database set by the Linux system is read to obtain relevant information of the abnormal task, and the task is restored to a normal state according to the information.
[0154] Step 805: Send a request for synchronization of running task information to the Android system;
[0155] In the above step 803, after determining that the task status is normal, the task management module of the Linux system sends a running task information synchronization request to the task management module of the Android system through the RPC communication module.
[0156] Step 806: Start Task Manager 1;
[0157] While executing step 802 , the task manager 1 of the Android system is started.
[0158] Step 807: The Android system returns the running task update information;
[0159] Based on steps 805 and 806, after receiving the running task information synchronization request, the task management module of the Android system requests the Android system service through IPC to obtain the latest running task information. After obtaining the running task update information, it sends it to the task management module of the Linux system through the RPC communication module to complete the synchronization of the running task information and update the running task list.
[0160] Step 808: Send an application status synchronization request to the application management module of the Linux system;
[0161] While executing step 805 and step 807, the Linux system will also check its application management module, ie, send application synchronization status information to it to determine whether the application management service has completed the synchronization of all application information.
[0162] Step 809: The application manager returns application synchronization status information;
[0163] On the basis of step 808 , after receiving the application state synchronization request, the application management module sends the application state synchronization information to the task manager 1 .
[0164] Step 810: Execute the task operation according to the task processing request.
[0165] Based on step 809, the task management service module on the Linux side has completed the synchronization of the latest running task information of the dual operating systems, obtained the latest running task list, and provided application operation-related services to the outside world, that is, executing startup, restart, and foreground operations according to the synchronized running task information.
[0166] In the embodiment of the present application, when the device is a vehicle with dual operating systems, and the first operating system is an Android system and the second operating system is a Linux system, and the task information synchronization between the above two systems is achieved by passive synchronization, specifically, Figure 9 As shown, the following steps are included:
[0167] Step 901: The monitoring unit monitors the task queue;
[0168] On the Linux system side, the internal monitoring unit is used to monitor changes in the Linux system task queue.
[0169] Step 902: Obtain a task operation request;
[0170] Based on step 901 , the task management module on the Linux system side obtains a task operation request, which includes a task operation request on the Linux system side, ie, a local task operation request, and a task operation request on the Android system side.
[0171] Step 903: Determine in which operating system the task is executed;
[0172] According to the type of the task operation request obtained in step 902 , it is determined in which operating system the task is executed. If the task operation request is a local task operation request, step 904 is executed; otherwise, step 905 is executed.
[0173] Step 904: Execute the task in the Linux system;
[0174] In the above step 903, after determining that the task operation request is a local task operation request, the task is executed in the Linux system.
[0175] Step 905: Execute the task in the Android system;
[0176] In the above step 903, after determining that the task operation request is an Android system side task operation request, the task is executed in the Android system.
[0177] Step 906: Execute the task operation according to the task operation request;
[0178] On the basis of step 904, specific operations are performed on the Linux system side according to the acquired local task operation request.
[0179] Step 907: Determine whether to feedback the task operation result across operating systems;
[0180] After executing step 906, the task operation result is obtained. Based on the result content, it is determined whether the task operation result needs to be fed back across operating systems. The task operation result includes task operation success information or task operation execution identification information. If the task operation is successful, step 920 is executed; otherwise, step 908 is executed.
[0181] Step 908: Update the database and notify the process that has registered to monitor Linux task queue changes;
[0182] After determining that the task operation fails in step 909, the corresponding information in the database of the Linux system is updated, and all processes registered to monitor changes in the Linux task queue are notified.
[0183] Step 909: The monitoring unit monitors the task queue;
[0184] While executing step 901 , on the Android system side, an internal monitoring unit is used to monitor changes in Android system task information, such as changes in task queues.
[0185] Step 910: Obtain a task operation request;
[0186] Based on step 909 , the task management module on the Android system side obtains a task operation request, which includes a task operation request on the Android system side, ie, a local task operation request, and a task operation request on the Linux system side.
[0187] Step 911: Determine in which operating system the task is executed;
[0188] According to the type of the task operation request obtained in step 910 , it is determined in which operating system the task is executed. If the task operation request is a local task operation request, step 912 is executed; otherwise, step 913 is executed.
[0189] Step 912: Execute the task in the Android system;
[0190] In the above step 911 , after determining that the task operation request is a local task operation request, the task is executed in the Android system.
[0191] Step 913: Execute the task in the Linux system;
[0192] In the above step 903, after determining that the task operation request is an Android system side task operation request, the task is executed in the Android system, that is, the above request is repackaged according to a specific protocol and sent to the task management service of the Linux system, requesting the service to perform the corresponding operation.
[0193] Step 914: Execute the task operation according to the task operation request;
[0194] On the basis of step 913 , specific operations are performed on the Android system side according to the acquired local task operation request.
[0195] Step 915: Determine whether the task is successfully executed;
[0196] After the task operation is completed in step 914, it is determined whether the above operation is successful and a task operation result is generated. If the task operation result is that the task operation is successfully executed, step 917 is executed; otherwise, step 916 is executed.
[0197] Step 916: Determine whether to feedback the task operation result across operating systems;
[0198] After determining in step 915 that the task operation has failed, it is further determined whether it is necessary to feedback the task operation result across operating systems.
[0199] Step 917: The monitoring unit detects a change in the task queue;
[0200] If it is determined in step 915 that the task operation is successful, the monitoring unit on the Android system side will detect the change in the task queue and generate running task update information.
[0201] Step 918: The Linux system receives the task feedback result from the Android system.
[0202] In the above step 916, after determining that the task operation result needs to be fed back across the operating systems, the Android system sends the task feedback result to the Linux system through the RPC communication system, and the Linux system will not wait for the task management module on the Android system side to obtain the running task update information, but will return directly and continue to listen and process task-related operation requests from the Linux system or the Android system in the working thread of the Linux system until the task management module in the Android system monitors the changes in the task queue of the Android system and notifies the generated running task update information to the task management service of the Linux system according to a specific protocol. The service will then perform the next step according to the corresponding task operation result and the received running task update information.
[0203] Step 919: Update the task database and notify the process that has registered to monitor the Android task list queue;
[0204] Based on the above step 918, the corresponding information of the task database in the Android system is updated, and all processes registered to monitor changes in the Android task queue are notified.
[0205] Step 920: Continue to monitor the task queue through the monitoring unit.
[0206] After executing the above steps, the task queues of both operating systems continue to be monitored through the monitoring units.
[0207] In the embodiment of the present application, when the device is a vehicle with dual operating systems, it can use the CS architecture to complete the task management of the dual operating systems, that is, when the Linux system controls the tasks of the Android system, Linux is the client and Android is the server; conversely, Android is the client and Linux is the server. Specifically, its structural diagram is as follows Figure 10 As shown, when the Linux system controls the tasks of the Android system: the Linux system uses a specific protocol to package the request data according to business needs, and then sends the above request data to the task management module on the Android system side through the RPC communication module. After parsing the request data sent by the Linux system, the task management module on the Android system side executes the Android task operation, such as starting, pinning or restarting. The above task operations will cause the task queue on the Android system side to change. After monitoring the changes in the task queue, the monitoring unit on the Android side synchronizes the generated running task update information to the task management service module on the Linux system side to update the running task list. The task management service module on the Linux system side stores this data in the database and notifies all applications or processes that have registered to monitor the Android task queue, thereby completing the task management of the dual operating systems.
[0208] When the Android system controls the tasks on the Linux system side: the Android system uses a specific protocol to encapsulate the request data according to business needs, and then transmits the above request data to the task management service module on the Linux system side through the RPC communication module. After the task management service module on the Linux system side parses the above request data, it performs corresponding operations on the tasks on the Linux system side, such as starting, stopping, and putting them in the foreground, and updates the database accordingly based on the results of the task operation execution, and notifies all applications or processes that have registered to listen to the Linux task queue, thereby completing the task management of the dual operating systems.
[0209] The present application also provides an electronic device, such as Figure 11 As shown, the electronic device includes: a processor 31 and a memory 32, the memory 32 stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the following is achieved: Figures 1-10 The steps of the task management method of the operating system.
[0210] This application also provides a vehicle system, such as Figure 12 As shown, the vehicle system can run the first operating system 41 and the second operating system 42 at the same time, and the vehicle system also includes Figure 11 The electronic device 43 shown has a first operating system including at least one of Android and Linux; and a second operating system including at least one of Android and Linux. For example, the first operating system is Android and the second operating system is Linux. By implementing operating system task management through the above-mentioned vehicle-mounted system, users can enjoy a diverse application experience and convenient operation.
[0211] The present application also provides a vehicle, such as Figure 13 As shown, the vehicle includes Figure 12 The vehicle-mounted system 51 described above enables the vehicle to operate on a dual operating system, thereby better managing multiple tasks within the operating system and ensuring smooth execution and efficient coordination of various functions. This not only enhances the vehicle's flexibility and compatibility, but also allows users to enjoy a more personalized and diversified driving experience.
[0212] The present application also provides a computer-readable storage medium, wherein a program or instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a processor, the following is realized: Figures 1-10 The steps of the task management method of the operating system.
[0213] The present application also provides a computer program product, which, when executed by a vehicle processor, implements the following Figures 1-10 The steps of the task management method of the operating system.
[0214] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0215] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.
[0216] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.
Claims
1. A task management method for an operating system, characterized in that: include: Receive user-triggered task list display requests; The running task list is displayed based on the task list display request, where the running task list includes running task information associated with application programs of the first operating system and / or the second operating system.
2. The method according to claim 1, characterized in that Also includes: receiving an application operation instruction triggered by a user, wherein the application operation instruction is used to operate an application program of the first operating system and / or the second operating system; The running task list is updated based on the application operation instruction.
3. The method according to claim 2, characterized in that The receiving of the application operation instruction triggered by the user includes at least one of the following: receiving an application operation instruction triggered by a first preset operation by a user on an application icon of the first operating system and / or the second operating system displayed on an application center interface; receiving an application operation instruction triggered by a second preset operation performed by a user on the application display interface; An application operation instruction triggered by a third preset operation of the user on the running task information in the running task list is received.
4. The method according to claim 2, characterized in that The application operation instruction includes at least one of a start operation instruction, a put in foreground instruction, a put in background instruction, and a restart operation instruction.
5. The method according to claim 2, characterized in that The updating of the running task list based on the application operation instruction includes: generating a task operation request based on the application operation instruction; updating the task queue of the first operating system and / or the second operating system based on the task operation request; The running task list is updated based on the updated task queue.
6. The method according to claim 5, characterized in that The task operation request includes a first task operation request to be executed locally by the first operating system; The updating of the task queue of the first operating system based on the task operation request includes: The first task operation request is executed in the first operating system to process the running task associated with the application program and update the first task queue of the first operating system.
7. The method according to claim 6, characterized in that The updating of the running task list based on the updated task queue includes: The first operating system updates the running task list based on the first task queue.
8. The method according to claim 5, characterized in that The task operation request includes a second task operation request executed by a second operating system, and updating a second task queue of the second operating system based on the task operation request includes: The first operating system sends the second task operation request to the second operating system, and the second operating system executes the second task operation request to process the running task associated with the application and updates the second task queue of the second operating system.
9. The method according to claim 8, characterized in that Also includes: The first operating system receives running task update information sent by the second operating system, where the running task update information is generated based on the updated second task queue; The first operating system updates the running task list based on the running task update information.
10. The method according to claim 9, characterized in that Also includes: The first operating system sends a task queue monitoring request to the second operating system, so that the second operating system generates the running task update information when monitoring that the task queue is updated.
11. The method according to any one of claims 1 to 10, characterized in that: Also includes: The first operating system receives initial information of a running task sent by the second operating system, where the initial information of the running task is generated by the second operating system based on an initial task queue of the second operating system; The first operating system generates an initial running task list according to the initial task queue of the first operating system and the initial running task information.
12. The method according to claim 11, characterized in that Also includes: Get the application icon information from the application management module; The initial running task list is generated or the running task list is updated based on the icon information of the application.
13. The method according to claim 1, wherein The running task information in the running task list is arranged according to the task activity.
14. The method according to claim 1, wherein The first operating system and the second operating system communicate with each other through an RPC communication module.
15. The method according to claim 1, wherein The first operating system includes at least one of an Android operating system and a Linux operating system, and the second operating system includes at least one of an Android operating system and a Linux operating system.
16. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the task management method of the operating system according to any one of claims 1 to 15 are implemented.
17. A vehicle computer system, characterized in that: The first operating system and the second operating system run on the vehicle system, and the vehicle system includes the electronic device according to claim 16.
18. A vehicle, characterized in that: Including the vehicle system according to claim 17.
19. A computer-readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the task management method of the operating system according to any one of claims 1 to 15 are implemented.
20. A computer program product, characterized in that The program product implements the steps of the task management method of the operating system according to any one of claims 1 to 15 when executed by a processor of an electronic device.