Task operation method and device of vehicle, electronic equipment and storage medium

Abstract

The invention discloses a task operation method and device of a vehicle, electronic equipment and a storage medium. The method comprises the steps that a to-be-operated target task in a cabin system of the vehicle is determined; based on the type of the target task, an operation unit matched with the cabin system is allocated to the target task, and a target operation unit is obtained; the power consumption mode of the target operation unit is determined, and the power consumption mode is used for representing the mode that the target operation unit consumes power when the cockpit system adopts the target operation unit to operate the target task; in the cabin system, according to the power consumption mode and the initial sequence information of the target task, the target operation unit is adopted to operate the target task, and the initial sequence information is used for representing the initial sequence of executing the target task. The technical problem that the task operation efficiency of the vehicle is low is solved.

Description

Technical Field

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

[0002] Currently, for the various types of tasks to be run in a vehicle's cockpit system, a static binding strategy is often used to assign fixed computing units to each task.

[0003] However, this static allocation method has drawbacks, such as high-priority tasks may consume redundant computing power, and sudden emergency tasks may experience response delays due to insufficient resources, resulting in low task operation efficiency of the vehicle.

[0004] There is currently no effective solution to the technical problem of low operational efficiency of the aforementioned vehicles. Summary of the Invention

[0005] This application provides a vehicle task operation method, apparatus, electronic device, and storage medium to at least solve the technical problem of low task operation efficiency of vehicles.

[0006] According to one aspect of the embodiments of this application, a vehicle task operation method is provided. The method includes: determining a target task to be run in the vehicle's cockpit system; assigning an operation unit matching the cockpit system to the target task based on the type of the target task, thereby obtaining a target operation unit; determining a power consumption mode of the target operation unit, wherein the power consumption mode is used to represent the power consumption mode of the target operation unit when the cockpit system uses the target operation unit to run the target task; and running the target task in the cockpit system according to the power consumption mode and the initial sequence information of the target task, wherein the initial sequence information is used to represent the initial order of execution of the target task.

[0007] Furthermore, based on the type of the target task, an operating unit matching the cockpit system is assigned to the target task to obtain the target operating unit, including: determining the type relationship between the type and the preset type; and assigning an operating unit to the target task based on the type relationship to obtain the target operating unit.

[0008] Furthermore, the target task includes at least one target subtask, wherein determining the type relationship between the type and the preset type includes: determining the type relationship between the type of the target subtask and the preset type.

[0009] Furthermore, the target task includes at least one target subtask, wherein, based on type relationships, a running unit is assigned to the target task to obtain a target running unit, which includes: based on the type relationship between the type of the target subtask and a preset type, a running unit is assigned to the target subtask to obtain a target running unit.

[0010] Furthermore, the preset types include: preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. The operating units include: a central operating unit, a graphics operating unit, a network operating unit, and a signal processing unit. The central operating unit includes: a first sub-operating unit, a second sub-operating unit, and a third sub-operating unit. The first, second, and third sub-operating units are different sub-operating units deployed within the central operating unit. Based on the type relationship between the type of the target sub-task and the preset types, operating units are assigned to the target sub-task to obtain the target operating unit. This includes: responding to the type relationship that the type of the target sub-task is the same as the preset driving type, assigning the first sub-operating unit, the graphics operating unit, and the network operating unit from the central operating unit to the target sub-task. The system operates as follows: A target operating unit is obtained; in response to the type relationship being the same as the preset auxiliary type, the second sub-operating unit, graphics operating unit, network operating unit, and signal processing unit in the central operating unit are assigned to the target sub-task, thus obtaining the target operating unit; in response to the type relationship being the same as the preset interaction type, a second sub-operating unit is assigned to the target sub-task, thus obtaining the target operating unit; in response to the type relationship being the same as the preset entertainment type, a third sub-operating unit, graphics operating unit, and signal processing unit in the central operating unit are assigned to the target sub-task, thus obtaining the target operating unit; in response to the type relationship being the same as the preset background type, a third sub-operating unit is assigned to the target sub-task, thus obtaining the target operating unit.

[0011] Further, determining the power consumption mode of the target operating unit includes: in response to the target task including a target sub-task of preset entertainment type, a target sub-task of preset driving type, and a target sub-task of preset auxiliary type, determining the power consumption mode as a first power consumption mode, wherein the first power consumption mode is used to represent the mode in which the target operating unit consumes power when the cockpit system uses the target operating unit to run the target task at the upper limit frequency of the target operating unit; in response to the target task including a target sub-task of preset driving type, a target sub-task of preset entertainment type, and a target sub-task of preset background type, determining the power consumption mode as a second power consumption mode, wherein the second power consumption mode is used to represent the mode in which the target operating unit consumes power when the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit. The power consumption mode of the operating unit; in response to the target task including a target sub-task of preset interactive type and a target sub-task of preset entertainment type, the power consumption mode is determined as a third power consumption mode, wherein the third power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the redundant operating units are turned off to run the target task, and the redundant operating units are the operating units other than the target operating unit; in response to the target task including a target sub-task of preset background type, the power consumption mode is determined as a fourth power consumption mode, wherein the fourth power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the wake-up unit to run the target task, and the wake-up unit is the unit used to wake up the vehicle's sensing devices.

[0012] Furthermore, the target task includes at least one target sub-task, wherein, in the cockpit system, the target task is run using a target operation unit according to the power consumption mode and the initial sequence information of the target task, including: adjusting the initial sequence information to obtain target sequence information, wherein the target sequence information is used to represent the target order of executing the target task; and in the cockpit system, the target sub-task is run using a target operation unit according to the power consumption mode and the target sequence information.

[0013] According to another aspect of the embodiments of this application, a vehicle task operation device is also provided. The device includes: a first determining unit, configured to determine a target task to be run in the vehicle's cockpit system; an allocation unit, configured to allocate an operation unit matching the cockpit system to the target task based on the type of the target task, thereby obtaining a target operation unit; a second determining unit, configured to determine the power consumption mode of the target operation unit, wherein the power consumption mode is used to represent the mode in which the target operation unit consumes power when the cockpit system uses the target operation unit to run the target task; and an operation unit, configured to run the target task in the cockpit system according to the power consumption mode and the initial sequence information of the target task, wherein the initial sequence information is used to represent the initial order of executing the target task.

[0014] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0015] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0016] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0018] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0019] In this embodiment, when running a vehicle task, the target task to be run in the vehicle's cockpit system is determined; based on the type of the target task, a running unit matching the cockpit system is assigned to the target task, thus obtaining a target running unit; the power consumption mode of the target running unit is determined; and in the cockpit system, the target task is run using the target running unit according to the power consumption mode and the initial sequence information of the target task. Since this embodiment, based on determining the target task to be run in the cockpit system, assigns a running unit to the target task according to its type, thus obtaining a target running unit, and further determines the power consumption mode of the assigned target running unit when it runs the target task in the cockpit system, and combines the determined power consumption mode and the initial sequence information of the target task to run the target task in the cockpit system, the assigned target running unit is used to run the target task. This achieves the goal of avoiding response delays due to insufficient resources for sudden emergency tasks, thereby solving the technical problem of low vehicle task operation efficiency and ultimately improving the technical effect of vehicle task operation efficiency. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0021] Figure 1(a) is a schematic diagram of an application scenario of a vehicle task operation method according to an embodiment of this application;

[0022] Figure 1(b) is a flowchart of a vehicle task operation method according to an embodiment of this application;

[0023] Figure 2 This is a structural block diagram of a vehicle task operation device according to an embodiment of this application;

[0024] Figure 3 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] According to an embodiment of this application, an embodiment of a vehicle task operation method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Also, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0028] As an optional implementation, the above-described vehicle task operation method can be applied to, but is not limited to, the application scenario shown in Figure 1(a). Figure 1(a) is a schematic diagram of an application scenario of a vehicle task operation method according to an embodiment of this application. As shown in Figure 1(a), in the application scenario, the terminal device 10 can, but is not limited to, communicate with the server 13 through the network 11. The server 13 can, but is not limited to, perform operations on the database, such as writing data or reading data. The terminal device 10 can, but is not limited to, a human-machine interaction screen, a processor, and a memory. The human-machine interaction screen can, but is not limited to, display a virtual machine on the mobile terminal 10. The vehicle 12 can, but is not limited to, respond to the above-described human-machine interaction operation, execute the corresponding operation, or generate the corresponding instruction and send the generated instruction to the server 13.

[0029] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be executed in a different order than that shown here. Specifically, the vehicle task operation method of this application may include: step S102, determining the target task to be run in the vehicle's cockpit system; step S104, assigning a running unit matching the cockpit system to the target task based on the type of the target task, obtaining the target running unit; step S106, determining the power consumption mode of the target running unit; and step S108, in the cockpit system, running the target task using the target running unit according to the power consumption mode and the initial sequence information of the target task.

[0030] It should be noted that all information and data involved in this application are authorized by the user or fully authorized by all parties, and the collection, use and processing of such data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0031] Figure 1(b) is a flowchart of a vehicle task operation method according to an embodiment of this application. As shown in Figure 1(b), the method may include the following steps:

[0032] Step S112: Determine the target task to be executed in the vehicle's cockpit system.

[0033] In the technical solution provided in step S112 of this application, the target task may include a single type of target subtask, or the target task may include multiple types of target subtasks. For example, the single type of target subtask may be any of the following types of target subtasks: a preset driving type target subtask, a preset assistance type target subtask, a preset interaction type target subtask, a preset entertainment type target subtask, and a preset background type target subtask, etc. The multiple types of target subtasks may be any combination of the following types of target subtasks: a preset driving type target subtask, a preset assistance type target subtask, a preset interaction type target subtask, a preset entertainment type target subtask, and a preset background type target subtask. This is only an example and is not specifically limited.

[0034] In this embodiment, the cockpit system described above can be an intelligent cockpit system in different types of vehicles.

[0035] In this embodiment, a target task to be executed in the vehicle's cockpit system is determined. Optionally, this embodiment performs task detection on the vehicle's cockpit system to obtain detection results, which can be used to indicate whether a target task to be executed exists in the cockpit system. Based on the obtained detection results, the target task to be executed in the cockpit system can be determined.

[0036] Optionally, based on the obtained detection results, the target task to be executed in the cockpit system can be determined. If the detection results indicate that a target task exists in the cockpit system, task identification is performed on the detection results to obtain the target task. If the detection results indicate that no target task exists in the cockpit system, task detection continues until the detection results indicate that a target task exists in the cockpit system.

[0037] Step S114: Based on the type of the target mission, assign an operating unit that matches the cockpit system to the target mission to obtain the target operating unit.

[0038] In the technical solution provided in step S114 of this application, the type of the target task can also be simply referred to as the task type. The task type can be any one or any combination of the following types: driving type, assistance type, interaction type, entertainment type, and background type, etc.

[0039] In this embodiment, the aforementioned operating unit can be one of the following computing units: a central processing unit (CPU), a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processing unit (ISP), and a digital signal processing unit (DSP).

[0040] In this embodiment, the target operating unit can be any one or any combination of the following computing units: CPU, GPU, NPU, ISP, and DSP.

[0041] In this embodiment, after determining the target task to be run in the vehicle's cockpit system, an operating unit matching the cockpit system is assigned to the target task based on its type, thus obtaining the target operating unit. This embodiment, by identifying the type of the target task after determining it, and then assigning an operating unit matching the cockpit system based on the type relationship between the target task's type and a preset type, confirms the assigned operating unit as the target operating unit, thereby achieving the goal of assigning a target operating unit to the target task.

[0042] Optionally, if the type relationship indicates that the type of the target task is the same as the preset type, then the target task can be assigned a running unit corresponding to the preset type, and the assigned running unit can be identified as the target running unit. If the type relationship indicates that the type of the target task is different from the preset type, then the target task is recorded as an abnormal task, and an abnormal prompt message is output. The abnormal prompt message can be used to indicate that there is an abnormal task to be run in the cockpit system.

[0043] Step S116: Determine the power consumption mode of the target operating unit, wherein the power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target mission.

[0044] In the technical solution provided in step S116 of this application, the power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task. For example, the power consumption mode can be any of the following modes: a first power consumption mode, a second power consumption mode, a third power consumption mode, and a fourth power consumption mode. The first power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task at the upper limit frequency of the target operating unit. The second power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit. The third power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and disables redundant operating units to run the target task. The fourth power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the wake-up unit to run the target task.

[0045] In this embodiment, based on the type of the target task, an operating unit matching the cockpit system is assigned to the target task. After obtaining the target operating unit, the power consumption mode of the target operating unit is determined. Optionally, after determining the target task to be run, this embodiment determines the cockpit usage scenario in which the target task is located. Based on the cockpit usage scenario, the power consumption mode of the target operating unit can be determined to be a first power consumption mode, a second power consumption mode, a third power consumption mode, or a fourth power consumption mode. This achieves the purpose of determining the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task.

[0046] It should be noted that the above method for determining the power consumption mode of the target operating unit is merely an illustrative example and is not intended to impose specific limitations. Any method that can determine the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target mission, based on the determination of the target operating unit, is within the protection scope of the embodiments of this application, and will not be described in detail here.

[0047] Step S118: In the cockpit system, the target task is run by the target running unit according to the power consumption mode and the initial sequence information of the target task, wherein the initial sequence information is used to indicate the initial order of execution of the target task.

[0048] In the technical solution provided by step S118 of this application, the initial sequence information can be used to represent the initial order of executing the target task. For example, the initial sequence information can be represented by a priority, and the priority is a dynamically adjustable priority.

[0049] In this embodiment, after determining the power consumption mode of the target operating unit, the target task is run in the cockpit system according to the power consumption mode and the initial sequence information of the target task. Optionally, based on the determined power consumption mode, this embodiment, in the cockpit system, uses the target operating unit to run the target task according to the determined power consumption mode and the initial sequence information of the target task. For example, if the target task includes a preset entertainment type target sub-task, a preset driving type target sub-task, and a preset assistance type target sub-task, then in the cockpit system, according to the initial sequence information of the target task, the CPU, DSP, and DSP power consumption modes are used to run the preset entertainment type target sub-task, the CPU, GPU, and NPU to run the preset driving type target sub-task, and the CPU, GPU, NPU, and ISP to run the preset assistance type target sub-task.

[0050] In steps S112 to S118 of this application, when running a vehicle task, the target task to be run in the vehicle's cockpit system is determined; based on the type of the target task, a running unit matching the cockpit system is assigned to the target task to obtain the target running unit; the power consumption mode of the target running unit is determined; and in the cockpit system, the target task is run using the target running unit according to the power consumption mode and the initial sequence information of the target task. Since this application, based on determining the target task to be run in the cockpit system, assigns a running unit to the target task according to the type of the target task to obtain the target running unit, and then determines the power consumption mode of the target running unit when the cockpit system uses the assigned target running unit to run the target task, and combines the determined power consumption mode and the initial sequence information of the target task in the cockpit system to run the target task, the assigned target running unit is used to run the target task. This achieves the goal of avoiding response delays due to insufficient resources in sudden emergency tasks, thereby solving the technical problem of low vehicle task operation efficiency and ultimately achieving the technical effect of improving vehicle task operation efficiency.

[0051] The following description further explains the steps of assigning a target operating unit to the target task based on the type of the target task, and obtaining the target operating unit.

[0052] As an optional embodiment, step S114, based on the type of the target task, assigns an operating unit that matches the cockpit system to the target task to obtain the target operating unit, including: determining the type relationship between the type and the preset type; and assigning an operating unit to the target task based on the type relationship to obtain the target operating unit.

[0053] In this embodiment, the above-mentioned type relationship can be that the type of the target task is the same as the preset type, or the above-mentioned type relationship can be that the type of the target task is different from the preset type.

[0054] In this embodiment, after determining the target task to be executed in the vehicle's cockpit system, the type relationship between the type and a preset type is determined. Optionally, based on the determined target task, this embodiment performs type identification on the target task to obtain its type. By comparing the type of the target task with a preset type, the type relationship between the two types can be obtained.

[0055] In this embodiment, after determining the type relationship between the type and the preset type, an operating unit is allocated to the target task based on the type relationship, thus obtaining the target operating unit. Optionally, based on the determined type relationship, this embodiment can allocate an operating unit that matches the cockpit system to the target task and determine the allocated operating unit as the target operating unit, thereby achieving the purpose of allocating a target operating unit to the target task and thus realizing the technical effect of improving the utilization rate of the operating unit.

[0056] Optionally, if the type relationship is that the type of the target task is the same as the preset type, then the target task can be assigned a running unit corresponding to the preset type, and the assigned running unit can be identified as the target running unit. If the type relationship is that the type of the target task is different from the preset type, then the target task is recorded as an abnormal task, and an abnormal prompt message is output.

[0057] The steps for determining the type relationship between the type and the preset type in this embodiment will be further explained below.

[0058] As an optional embodiment, the target task includes at least one target subtask, wherein determining the type relationship between the type and the preset type includes: determining the type relationship between the type of the target subtask and the preset type.

[0059] In this embodiment, the target task may include at least one target subtask. That is, the target task may include one or more target subtasks.

[0060] In this embodiment, after determining the target task to be executed in the vehicle's cockpit system, the type relationship between the type of the target subtask and a preset type is determined. Optionally, if the target task includes one target subtask, the type of the target subtask is compared with the preset type to obtain the type relationship between the target subtask type and the preset type. If the target task includes multiple target subtasks, the types of each target subtask are compared with the preset type to obtain the type relationships between the types of multiple target subtasks and the preset type. That is, multiple type relationships can be obtained, thereby achieving the purpose of determining the type relationship and realizing the technical effect of improving the accuracy of the type relationship.

[0061] The following description further explains the steps of allocating running units to the target task based on type relationships in this embodiment to obtain the target running units.

[0062] As an optional embodiment, the target task includes at least one target subtask, wherein, based on type relationships, a running unit is assigned to the target task to obtain a target running unit, which includes: assigning a running unit to the target subtask based on the type relationship between the type of the target subtask and a preset type to obtain a target running unit.

[0063] In this embodiment, the target task may include at least one target subtask. That is, the target task may include one or more target subtasks.

[0064] In this embodiment, after determining the type relationship between the type of the target subtask and the preset type, a running unit is allocated to the target subtask based on the type relationship between the type of the target subtask and the preset type, thus obtaining the target running unit.

[0065] Optionally, based on the determined type relationship, if the type relationship is a single type relationship, then an operating unit matching the cockpit system can be assigned to the target sub-task, and the assigned operating unit can be designated as a target operating unit. If the type relationship is multiple type relationships, then operating units matching the cockpit system can be assigned to multiple target sub-tasks respectively, and the assigned multiple operating units can be designated as target operating units. This achieves the goal of assigning target operating units to target tasks, thereby realizing the technical effect of improving the utilization rate of operating units.

[0066] The following description further explains the steps of allocating running units to target subtasks and obtaining target running units based on the type relationship between the type of target subtask and the preset type in this embodiment.

[0067] As an optional embodiment, the preset types include: preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. The operating unit includes: a central operating unit, a graphics operating unit, a network operating unit, and a signal processing unit. The central operating unit includes: a first sub-operating unit, a second sub-operating unit, and a third sub-operating unit. The first sub-operating unit, the second sub-operating unit, and the third sub-operating unit are different sub-operating units deployed in the central operating unit. Based on the type relationship between the type of the target sub-task and the preset types, an operating unit is assigned to the target sub-task to obtain the target operating unit. This includes: in response to the type relationship indicating that the type of the target sub-task is the same as the preset driving type, assigning the first sub-operating unit, the graphics operating unit, and the third sub-operating unit from the central operating unit to the target sub-task. The system first establishes a network operation unit to obtain the target operation unit. Then, in response to the type relationship where the type of the target subtask is the same as the preset auxiliary type, it allocates the second sub-operation unit, graphics operation unit, network operation unit, and signal processing unit from the central operation unit to the target subtask, thus obtaining the target operation unit. Finally, in response to the type relationship where the type of the target subtask is the same as the preset interaction type, it allocates the second sub-operation unit to the target subtask, thus obtaining the target operation unit. Similarly, in response to the type relationship where the type of the target subtask is the same as the preset entertainment type, it allocates the third sub-operation unit, graphics operation unit, and signal processing unit from the central operation unit to the target subtask, thus obtaining the target operation unit. Finally, in response to the type relationship where the type of the target subtask is the same as the preset background type, it allocates the third sub-operation unit to the target subtask, thus obtaining the target operation unit.

[0068] In this embodiment, the preset types may include: preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. For example, the preset driving type can be described by the safety critical class P0, the preset interaction type can be described by the core experience class P1, the preset entertainment type can be described by the entertainment service class P3, and the preset background type can be described by the background support class P4.

[0069] In this embodiment, the aforementioned operating unit may include: a central operating unit, a graphics operating unit, a network operating unit, and a signal processing unit. For example, the central operating unit may be a CPU, the graphics operating unit may be a GPU, the network operating unit may be an NPU, and the signal processing unit may include: an ISP and a DSP.

[0070] In this embodiment, the central operating unit may include a first sub-operating unit, a second sub-operating unit, and a third sub-operating unit, which may be different sub-operating units deployed within the central operating unit. For example, the first sub-operating unit may be a large CPU core, the second sub-operating unit may be a medium CPU core, and the third sub-operating unit may be a small CPU core.

[0071] In this embodiment, after determining the type relationship between the type of the target subtask and the preset type, in response to the type relationship indicating that the type of the target subtask is the same as the preset driving type, the first sub-operating unit, the graphics operating unit, and the network operating unit in the central operating unit are allocated to the target subtask to obtain the target operating unit. Optionally, this embodiment compares the type of the target subtask with the preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. If the comparison shows that the type of the target subtask is the same as the preset driving type, the first sub-operating unit, the graphics operating unit, and the network operating unit in the central operating unit are allocated to the target subtask, and the allocated first sub-operating unit, the graphics operating unit, and the network operating unit are determined as the target operating unit. This achieves the purpose of allocating a target operating unit to the target task, thereby realizing the technical effect of improving the utilization rate of the operating unit.

[0072] In this embodiment, after determining the type relationship between the type of the target subtask and a preset type, in response to the type relationship indicating that the type of the target subtask is the same as the preset auxiliary type, the target subtask is assigned a second sub-operating unit, a graphics operating unit, a network operating unit, and a signal processing unit within the central operating unit, thus obtaining the target operating unit. Optionally, this embodiment compares the type of the target subtask with preset driving types, preset auxiliary types, preset interaction types, preset entertainment types, and preset background types. If the comparison shows that the type of the target subtask is the same as the preset auxiliary type, the target subtask is assigned a second sub-operating unit, a graphics operating unit, a network operating unit, and an ISP within the signal processing unit within the central operating unit. The assigned second sub-operating unit, graphics operating unit, network operating unit, and signal processing unit ISP is then determined as the target operating unit. This achieves the goal of assigning a target operating unit to the target task, thereby improving the utilization rate of the operating unit.

[0073] In this embodiment, after determining the type relationship between the type of the target subtask and a preset type, in response to the type relationship indicating that the type of the target subtask is the same as the preset interaction type, a second sub-running unit is assigned to the target subtask, thus obtaining the target running unit. Optionally, this embodiment compares the type of the target subtask with preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. If the comparison shows that the type relationship indicates that the type of the target subtask is the same as the preset interaction type, a second sub-running unit in the central running unit is assigned to the target subtask, and the assigned second sub-running unit is determined as the target running unit. This achieves the goal of assigning a target running unit to the target task, thereby realizing the technical effect of improving the utilization rate of the running unit.

[0074] In this embodiment, after determining the type relationship between the type of the target subtask and the preset type, in response to the type relationship indicating that the type of the target subtask is the same as the preset entertainment type, a third sub-operating unit, a graphics operating unit, and a signal processing unit in the central operating unit are allocated to the target subtask to obtain the target operating unit. Optionally, this embodiment compares the type of the target subtask with preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. If the comparison shows that the type of the target subtask is the same as the preset entertainment type, then a third sub-operating unit, a graphics operating unit, and a DSP in the signal processing unit in the central operating unit are allocated to the target subtask, and the allocated third sub-operating unit, graphics operating unit, and signal processing unit are determined as the target operating unit. This achieves the purpose of allocating a target operating unit to the target task, thereby realizing the technical effect of improving the utilization rate of the operating unit.

[0075] In this embodiment, after determining the type relationship between the type of the target subtask and a preset type, in response to the type relationship indicating that the type of the target subtask is the same as the preset background type, a third sub-running unit is allocated to the target subtask to obtain the target running unit. Optionally, this embodiment compares the type of the target subtask with preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. If the comparison shows that the type relationship indicates that the type of the target subtask is the same as the preset background type, a third sub-running unit in the central running unit is allocated to the target subtask, and the allocated third sub-running unit is determined as the target running unit. This achieves the purpose of allocating a target running unit to the target task, thereby realizing the technical effect of improving the utilization rate of the running unit.

[0076] The steps for determining the power consumption mode of the target operating unit in this embodiment will be further explained below.

[0077] As an optional embodiment, step S116, determining the power consumption mode of the target operating unit, includes: in response to the target task including a preset entertainment type target sub-task, a preset driving type target sub-task, and a preset auxiliary type target sub-task, determining the power consumption mode as a first power consumption mode, wherein the first power consumption mode is used to represent the mode in which the target operating unit consumes power when the cockpit system uses the target operating unit to run the target task at the upper limit frequency of the target operating unit; in response to the target task including a preset driving type target sub-task, a preset entertainment type target sub-task, and a preset background type target sub-task, determining the power consumption mode as a second power consumption mode, wherein the second power consumption mode is used to represent the mode in which the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit. When a target task is selected, the power consumption mode of the target operating unit is determined. In response to the target task including a target sub-task of a preset interactive type and a target sub-task of a preset entertainment type, the power consumption mode is determined as a third power consumption mode. The third power consumption mode represents the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and disables redundant operating units to run the target task. Redundant operating units are operating units other than the target operating unit. In response to the target task including a target sub-task of a preset background type, the power consumption mode is determined as a fourth power consumption mode. The fourth power consumption mode represents the power consumption mode of the target operating unit when the cockpit system uses both the target operating unit and a wake-up unit to run the target task. The wake-up unit is a unit used to wake up the vehicle's sensing devices.

[0078] In this embodiment, the first power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target mission at the upper limit frequency of the target operating unit. For example, the first power consumption mode can also be called a high-performance mode.

[0079] In this embodiment, based on the type of the target task, an operating unit matching the cockpit system is assigned to the target task. After obtaining the target operating unit, in response to the target task including a target sub-task of preset entertainment type, a target sub-task of preset driving type, and a target sub-task of preset auxiliary type, the power consumption mode is determined to be the first power consumption mode.

[0080] Optionally, after determining the target task to be run, this embodiment determines the cockpit usage scenario in which the target task is located. If the cockpit usage scenario is a "multi-screen 4K playback + navigation + voice" scenario, then the target task can be determined to include a target sub-task of the preset entertainment type, a target sub-task of the preset driving type, and a target sub-task of the preset assistance type. When the target task includes a target sub-task of the preset entertainment type, a target sub-task of the preset driving type, and a target sub-task of the preset assistance type, the power consumption mode is determined as the first power consumption mode. This achieves the purpose of determining the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task at the upper limit frequency of the target operating unit, thereby achieving the technical effect of saving the energy consumption of the target operating unit.

[0081] In this embodiment, the second power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit. For example, the second power consumption mode can also be called a balanced mode.

[0082] In this embodiment, based on the type of the target task, an operating unit matching the cockpit system is assigned to the target task. After obtaining the target operating unit, in response to the target task including a target sub-task of a preset driving type, a target sub-task of a preset entertainment type, and a target sub-task of a preset background type, the power consumption mode is determined to be the second power consumption mode.

[0083] Optionally, after determining the target task to be run, this embodiment determines the cockpit usage scenario in which the target task is located. If the cockpit usage scenario is a "navigation + music + background monitoring" scenario, then the target task can be determined to include a target sub-task of a preset driving type, a target sub-task of a preset entertainment type, and a target sub-task of a preset background type. When the target task includes a target sub-task of a preset driving type, a target sub-task of a preset entertainment type, and a target sub-task of a preset background type, the power consumption mode is determined as the second power consumption mode. This achieves the purpose of determining the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit, thereby achieving the technical effect of saving the energy consumption of the target operating unit.

[0084] In this embodiment, the aforementioned third power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and disables redundant operating units to run the target task. Here, the redundant operating units refer to the operating units other than the target operating unit. For example, the aforementioned third power consumption mode can also be called a low-power mode.

[0085] In this embodiment, based on the type of the target task, an operating unit matching the cockpit system is assigned to the target task. After obtaining the target operating unit, in response to the target task including a target sub-task of a preset interactive type and a target sub-task of a preset entertainment type, the power consumption mode is determined to be the third power consumption mode.

[0086] Optionally, after determining the target task to be run, this embodiment determines the cockpit usage scenario in which the target task is located. If the cockpit usage scenario is a "music playback only + screen always on" scenario, then the target task can be determined to include a target sub-task of a preset interactive type and a target sub-task of a preset entertainment type. In the case that the target task includes a target sub-task of a preset interactive type and a target sub-task of a preset entertainment type, the power consumption mode is determined as the third power consumption mode. This achieves the purpose of determining the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and turns off the redundant operating units to run the target task, thereby achieving the technical effect of saving the energy consumption of the target operating unit.

[0087] In this embodiment, the aforementioned fourth power consumption mode can be used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the wake-up unit to run the target task. The wake-up unit can be a unit used to wake up the vehicle's sensing devices. For example, the aforementioned fourth power consumption mode can also be called a sleep mode, and the wake-up unit can be a sensor wake-up unit.

[0088] In this embodiment, based on the type of the target task, an operating unit matching the cockpit system is assigned to the target task. After obtaining the target operating unit, in response to the target task including a target sub-task of a preset background type, the power consumption mode is determined to be the fourth power consumption mode.

[0089] Optionally, after determining the target task to be run, this embodiment determines the cockpit usage scenario in which the target task is located. If the cockpit usage scenario is a "remote monitoring after vehicle shutdown" scenario, it can be determined that the target task includes a target sub-task of a preset background type. In the case that the target task includes a target sub-task of a preset background type, the power consumption mode is determined as the fourth power consumption mode. This achieves the purpose of determining the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the wake-up unit to run the target task, thereby achieving the technical effect of saving the energy consumption of the target operating unit.

[0090] The following description further explains the steps of running the target task using the target operation unit in the cockpit system according to the power consumption mode and the initial sequence information of the target task in the above embodiment.

[0091] As an optional embodiment, the target task includes at least one target sub-task, wherein step S118, in the cockpit system, the target task is run using a target running unit according to the power consumption mode and the initial sequence information of the target task, including: adjusting the initial sequence information to obtain target sequence information, wherein the target sequence information is used to represent the target order of executing the target task; and in the cockpit system, the target sub-task is run using a target running unit according to the power consumption mode and the target sequence information.

[0092] In this embodiment, the target order information can be used to represent the target order in which the target tasks are performed.

[0093] In this embodiment, after determining the power consumption mode of the target operating unit, the initial sequence information is adjusted to obtain the target sequence information; in the cockpit system, the target operating unit is used to run the target sub-task according to the power consumption mode and the target sequence information.

[0094] Optionally, this embodiment adjusts the initial sequence information according to the input / output frequency, interrupt response count, and user interaction intensity of the target task to obtain target sequence information. Then, in the cockpit system, the target task is run by the target operating unit according to the adjusted target sequence information and the determined power consumption mode. This achieves the goal of avoiding response delays due to insufficient resources in sudden emergency tasks, thereby improving the technical effect of improving the vehicle's task operation efficiency.

[0095] In this embodiment, when running a vehicle task, the target task to be run in the vehicle's cockpit system is determined; based on the type of the target task, a running unit matching the cockpit system is assigned to the target task, thus obtaining a target running unit; the power consumption mode of the target running unit is determined; and in the cockpit system, the target task is run using the target running unit according to the power consumption mode and the initial sequence information of the target task. Since this embodiment, based on determining the target task to be run in the cockpit system, assigns a running unit to the target task according to its type, thus obtaining a target running unit, and further determines the power consumption mode of the assigned target running unit when it runs the target task in the cockpit system, and combines the determined power consumption mode and the initial sequence information of the target task to run the target task in the cockpit system, the assigned target running unit is used to run the target task. This achieves the goal of avoiding response delays due to insufficient resources for sudden emergency tasks, thereby solving the technical problem of low vehicle task operation efficiency and ultimately improving the technical effect of vehicle task operation efficiency.

[0096] The technical solutions of the embodiments of this application will be illustrated below with reference to preferred embodiments.

[0097] Currently, for the various tasks to be run in a vehicle's cockpit system, a static binding strategy is often used to allocate fixed computing units to each task. However, this static allocation method has drawbacks, such as high-priority tasks potentially consuming redundant computing power, and sudden emergency tasks experiencing response delays due to insufficient resources, resulting in low task operation efficiency for the vehicle.

[0098] However, this application proposes a vehicle task operation method. Based on determining the target task to be run in the cockpit system, an operation unit is allocated to the target task according to the type of the target task, thereby obtaining the target operation unit. Then, the power consumption mode of the target operation unit is determined when the cockpit system uses the allocated target operation unit to run the target task. In the cockpit system, the allocated target operation unit is used to run the target task in combination with the determined power consumption mode and the initial sequence information of the target task. This achieves the purpose of avoiding response delays due to insufficient resources in sudden emergency tasks, thereby solving the technical problem of low vehicle task operation efficiency and achieving the technical effect of improving vehicle task operation efficiency.

[0099] In this embodiment, a dynamic scheduling mechanism based on task type and real-time requirements adjusts the computing power allocation of computing units. This dynamic scheduling mechanism can rely on the heterogeneous computing architecture of the Qualcomm 8397 cockpit platform, achieving precise allocation of computing resources through a three-level scheduling logic. This heterogeneous computing architecture can include CPU clusters, GPUs, NPUs, and dedicated ISPs.

[0100] In this embodiment, task type and priority modeling is performed. Based on the hardware acceleration capabilities of Qualcomm 8397, cockpit tasks are divided into 5 types of tasks as shown in Table 1 below, and each type of task is bound to a computing unit as shown in Table 1 below. At the same time, each type of task is assigned a dynamic priority as shown in Table 1 below.

[0101] Table 1 Task List

[0102]

[0103] Optionally, the dynamic adjustment rules for the priority of the above tasks are as follows: The task feature extraction module monitors the input / output (I / O) frequency, interrupt response count, and user interaction intensity of the task in real time, and automatically adjusts the priority accordingly. For example, when a P1-level navigation task detects a high-speed scene, its priority is temporarily increased by 10%. The high-speed scene can be, but is not limited to, scenes where the speed detected by the Global Positioning System (GPS) is greater than 60 km / h. When a P3-level video task has no user operation for 5 consecutive minutes, it is automatically downgraded to P4 level.

[0104] In this embodiment, demand quantification indicators are obtained. These indicators are computing power requirement thresholds set for each type of task, and can be adjusted based on the hardware parameters of the Qualcomm 8397. For example, the demand quantification indicators for P0-level autonomous driving vision fusion tasks are: NPU computing power ≥ 15 trillion operations per second (TOPS), and CPU large core utilization ≤ 30% (to avoid affecting interrupt response); the demand quantification indicators for P1-level augmented reality (AR) navigation are: GPU graphics core utilization maintained at 40%-60% (to ensure 60fps rendering), and memory bandwidth ≥ 20GB / s; the demand quantification indicators for P3-level 4K video are: GPU video decoding unit utilization ≤ 25%, and small core cluster load ≤ 50%.

[0105] In this embodiment, the computing power allocation value of a task can be determined through a dynamic mapping mechanism. The scheduler collects the load of each computing unit every 20ms (sampling accuracy is 1ms), and the computing power allocation value can be calculated in real time using the following formula: Target allocation rate = Computing power demand threshold × (1 + priority weight) × Load fluctuation coefficient. It should be noted that the above load fluctuation coefficient can be calculated based on the average load fluctuation over the past 10 sampling periods, and the range of the load fluctuation coefficient is 0.8-1.2.

[0106] In this embodiment, the scheduling and execution of heterogeneous computing resources can be carried out as follows.

[0107] Optionally, for CPU scheduling, using the Qualcomm 8397, computing resources are allocated through the following strategy to achieve CPU scheduling: P0 task is allocated 1 large core, P1 task is allocated 1 medium core, the main frequency is locked at 2.8GHz, and preemptive scheduling is adopted, where the response latency is ≤5ms; P2 task is allocated 1 medium core, P3 task is allocated 1 small core, the main frequency is dynamically adjusted to within 1.2GHz-2.0GHz, and time slice rotation is used, where the slice length is 10ms); P4 task is restricted to the small core cluster, and the main frequency is ≤1.0GHz, and P4 task is only activated when the load of large core / medium core is <60%.

[0108] Optionally, GPU scheduling is implemented through a frame scheduler: a dedicated rendering queue (highest priority) is reserved for P1-level AR navigation to ensure that the rendering time of each frame is ≤16ms; when P3-level video and P2-level touch tasks compete for GPU resources, computing units are allocated in a 7:3 ratio, and the texture fill rate of the video task is limited (from 48Gpixel / s to 24Gpixel / s).

[0109] Optionally, when the neural network is running, model sharding technology is used to achieve NPU scheduling: when P0-level visual fusion and P1-level speech recognition are running simultaneously, the NPU computing power is split in a 6:4 ratio, with the target detection model (accounting for 60%) and the speech feature extraction model (accounting for 40%) loaded respectively.

[0110] In this embodiment, by combining the Dynamic Voltage and Frequency Scaling (DVFS) and Cluster power domain design of the Qualcomm 8397, energy efficiency optimization is achieved from both hardware and software perspectives.

[0111] Optionally, according to Table 2 below, the power consumption of the computing unit can be adaptively adjusted based on the load and scenario.

[0112] Table 2. Mode and power consumption in different scenarios

[0113]

[0114] In this embodiment, refined DVFS curves are designed for the Qualcomm 8397's CPU / GPU / NPU. Specifically, for the CPU, the frequencies of the large cores (e.g., 1.8GHz~2.8GHz) and small cores (e.g., 0.8GHz~1.6GHz) are dynamically adjusted based on the task's single-core performance requirements. For the GPU, the Adreno Power Management (APM) module monitors the rendering load (e.g., number of triangles per frame) in real time. When the load is ≤50%, the frequency is automatically reduced (e.g., from 840MHz to 585MHz), and the core voltage is lowered (from 0.9V to 0.7V). For the NPU, an on-demand computing power activation method is adopted. When speech recognition is needed, all NPU cores are activated (frequency 1.2GHz), while only one core (frequency 0.4GHz) is retained for listening only, with the voltage reduced from 0.8V to 0.5V.

[0115] In this embodiment, the power domain isolation feature of the Qualcomm 8397 enables cross-unit coordinated sleep and wake-up. For example, when there is no image rendering task, some shader cores of the GPU are automatically shut down, reserving 20% ​​of the cores for standby; during multi-tasking intervals (e.g., 5 minutes of user inactivity), a "light sleep" is triggered: the large CPU cores are shut down, only the small cores maintain a low frequency, the NPU / GPU enters a clock self-refresh state, retains memory data, and the wake-up latency is ≤50ms; the corresponding computing unit is quickly activated by sensor interrupts (e.g., user touch of the screen, voice wake-up word trigger), and the switching time from sleep state to operation is ≤200ms.

[0116] In this embodiment, by deploying an energy efficiency monitoring module, the "computing power output / power consumption" ratio (TOPS / W) can be calculated in real time. When the energy efficiency ratio of any computing unit (e.g., GPU) is lower than a threshold (e.g., energy efficiency ratio < 2.5 TOPS / W), frequency reduction or task migration is automatically triggered. For example, some rendering tasks are offloaded to the CPU integration or GPU cores. Long-term statistical analysis of energy efficiency data under different scenarios allows for dynamic optimization of the DVFS curve and task allocation strategy through OTA updates. For example, in low-temperature winter environments, the performance degradation of the voltage compensation chip is appropriately increased, thereby avoiding energy efficiency degradation caused by frequent frequency reduction.

[0117] In this embodiment, when running a vehicle task, the target task to be run in the vehicle's cockpit system is determined; based on the type of the target task, a running unit matching the cockpit system is assigned to the target task, thus obtaining a target running unit; the power consumption mode of the target running unit is determined; and in the cockpit system, the target task is run using the target running unit according to the power consumption mode and the initial sequence information of the target task. Since this embodiment, based on determining the target task to be run in the cockpit system, assigns a running unit to the target task according to its type, thus obtaining a target running unit, and further determines the power consumption mode of the assigned target running unit when the cockpit system runs the target task, and combines the determined power consumption mode and the initial sequence information of the target task to run the target task, the assigned target running unit is used to run the target task. This achieves the goal of avoiding response delays due to insufficient resources for sudden emergency tasks, thereby solving the technical problem of low vehicle task operation efficiency and ultimately improving the technical effect of improving vehicle task operation efficiency.

[0118] According to another aspect of the embodiments of this application, corresponding to the embodiments of the above-described vehicle task operation method, the embodiments of this application also provide a vehicle task operation device. Figure 2 This is a structural block diagram of a vehicle task operation device according to an embodiment of this application, such as... Figure 2 As shown, the vehicle's task operation device 200 may include: a first determining unit 202, an allocation unit 204, a second determining unit 206, and an operation unit 208.

[0119] The first determining unit 202 is used to determine the target task to be executed in the vehicle's cockpit system.

[0120] The allocation unit 204 is used to allocate a running unit that matches the cockpit system to the target mission based on the type of the target mission, thereby obtaining the target running unit.

[0121] The second determining unit 206 is used to determine the power consumption mode of the target operating unit, wherein the power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target mission.

[0122] The operation unit 208 is used in the cockpit system to run the target task using the target operation unit according to the power consumption mode and the initial sequence information of the target task, wherein the initial sequence information is used to indicate the initial order of execution of the target task.

[0123] Optionally, the allocation unit 204 may include: a first determining module, used to determine the type relationship between the type and the preset type; and an allocation module, used to allocate a running unit to the target task based on the type relationship, thereby obtaining the target running unit.

[0124] Optionally, the target task includes at least one target subtask, wherein the first determining module may include: a first determining submodule, used to determine the type relationship between the type of the target subtask and a preset type.

[0125] Optionally, the target task includes at least one target subtask, wherein the allocation module may include: an allocation submodule, used to allocate a running unit to the target subtask based on the type relationship between the type of the target subtask and a preset type, thereby obtaining the target running unit.

[0126] Optionally, the preset types include: preset driving type, preset assistance type, preset interaction type, preset entertainment type, and preset background type. The operating units include: a central operating unit, a graphics operating unit, a network operating unit, and a signal processing unit. The central operating unit includes: a first sub-operating unit, a second sub-operating unit, and a third sub-operating unit. The first sub-operating unit, the second sub-operating unit, and the third sub-operating unit are different sub-operating units deployed in the central operating unit. The allocation submodule can allocate operating units to the target sub-task based on the type relationship between the type of the target sub-task and the preset types by performing the following steps to obtain the target operating unit: In response to the type relationship that the type of the target sub-task is the same as the preset driving type, the first sub-operating unit, the graphics operating unit, the network operating unit, and the signal processing unit in the central operating unit are allocated to the target sub-task. The system first establishes a line unit and a network operation unit to obtain the target operation unit. Then, in response to the type relationship where the type of the target subtask is the same as the preset auxiliary type, it allocates the second sub-operation unit, graphics operation unit, network operation unit, and signal processing unit from the central operation unit to the target subtask, thus obtaining the target operation unit. Finally, in response to the type relationship where the type of the target subtask is the same as the preset interaction type, it allocates the second sub-operation unit to the target subtask, thus obtaining the target operation unit. Similarly, in response to the type relationship where the type of the target subtask is the same as the preset entertainment type, it allocates the third sub-operation unit, graphics operation unit, and signal processing unit from the central operation unit to the target subtask, thus obtaining the target operation unit. Finally, in response to the type relationship where the type of the target subtask is the same as the preset background type, it allocates the third sub-operation unit to the target subtask, thus obtaining the target operation unit.

[0127] Optionally, the second determining unit 206 may include: a second determining module, configured to, in response to the target task including a target sub-task of a preset entertainment type, a target sub-task of a preset driving type, and a target sub-task of a preset auxiliary type, determine the power consumption mode as a first power consumption mode, wherein the first power consumption mode is used to represent the mode in which the target operating unit consumes power when the cockpit system uses the target operating unit to run the target task at the upper limit frequency of the target operating unit; and a third determining module, configured to, in response to the target task including a target sub-task of a preset driving type, a target sub-task of a preset entertainment type, and a target sub-task of a preset background type, determine the power consumption mode as a second power consumption mode, wherein the second power consumption mode is used to represent the mode in which the target operating unit consumes power when the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit. The power consumption mode of the unit; the fourth determining module, used to determine the power consumption mode as the third power consumption mode in response to the target task including the target sub-task of the preset interactive type and the target sub-task of the preset entertainment type, wherein the third power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the redundant operating units are turned off to run the target task, and the redundant operating units are the operating units other than the target operating unit; the fifth determining module, used to determine the power consumption mode as the fourth power consumption mode in response to the target task including the target sub-task of the preset background type, wherein the fourth power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and the wake-up unit to run the target task, and the wake-up unit is the unit used to wake up the vehicle's sensing devices.

[0128] Optionally, the running unit 208 may include: an adjustment module for adjusting the initial sequence information to obtain target sequence information, wherein the target sequence information is used to represent the target order for executing the target task; and a running module for running the target sub-task in the cockpit system according to the power consumption mode and the target sequence information, using the target running unit.

[0129] In this embodiment, the vehicle's task operation device includes the following units: a first determining unit for determining the target task to be run in the vehicle's cockpit system; an allocation unit for allocating a running unit matching the cockpit system to the target task based on the type of the target task, thereby obtaining the target running unit; a second determining unit for determining the power consumption mode of the target running unit, wherein the power consumption mode represents the power consumption mode of the target running unit when the cockpit system uses the target running unit to run the target task; and an operation unit for running the target task in the cockpit system according to the power consumption mode and the initial sequence information of the target task, wherein the initial sequence information represents the initial order of executing the target task. This achieves the goal of avoiding response delays due to insufficient resources in sudden emergency tasks, thereby solving the technical problem of low vehicle task operation efficiency and achieving the technical effect of improving vehicle task operation efficiency.

[0130] Embodiments of this application also provide an electronic device, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0131] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0132] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0133] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0134] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of this application.

[0135] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0136] According to an embodiment of this application, an electronic device is also provided. Figure 3 This is a schematic diagram of an electronic device according to an embodiment of this application, such as... Figure 3As shown, the electronic device 300 may include a memory 310 and a processor 320. The memory 310 is used to store an executable program; the processor 320 is used to run the program stored in the memory 310. When the program runs, it executes the vehicle task operation method of this application.

[0137] In this application, "multiple" refers to two or more.

[0138] In this application, unless otherwise expressly defined, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0139] The terms “first,” “second,” “third,” “fourth,” etc., in this application (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0140] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0141] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided. This computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method described in the embodiments.

[0142] Computer-readable storage media, also known as computer storage media, may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. These propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable storage media can transmit, propagate, or transfer programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0143] The program code contained in a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, radio frequency, or any suitable combination thereof.

[0144] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: determining the target task to be run in the vehicle's cockpit system; assigning a running unit matching the cockpit system to the target task based on the type of the target task, thereby obtaining the target running unit; determining the power consumption mode of the target running unit, wherein the power consumption mode is used to represent the power consumption mode of the target running unit when the cockpit system uses the target running unit to run the target task; and running the target task in the cockpit system according to the power consumption mode and the initial sequence information of the target task, wherein the initial sequence information is used to represent the initial order of execution of the target task.

[0145] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: determining the type relationship between the type and the preset type; and based on the type relationship, allocating a running unit to the target task to obtain the target running unit.

[0146] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: determining the type relationship between the type of the target subtask and the preset type.

[0147] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: based on the type relationship between the type of the target subtask and the preset type, allocates a running unit to the target subtask to obtain the target running unit.

[0148] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: In response to the type relationship being the same as the preset driving type, a first sub-running unit, a graphics running unit, and a network running unit in the central running unit are allocated to the target sub-task to obtain a target running unit; In response to the type relationship being the same as the preset auxiliary type, a second sub-running unit, a graphics running unit, a network running unit, and a signal processing unit in the central running unit are allocated to the target sub-task to obtain a target running unit; In response to the type relationship being the same as the preset interaction type, a second sub-running unit is allocated to the target sub-task to obtain a target running unit; In response to the type relationship being the same as the preset entertainment type, a third sub-running unit, a graphics running unit, and a signal processing unit in the central running unit are allocated to the target sub-task to obtain a target running unit; In response to the type relationship being the same as the preset background type, a third sub-running unit is allocated to the target sub-task to obtain a target running unit.

[0149] Optionally, when the above-mentioned computer program is executed by the processor, the program code implements the following steps: In response to the target task including a preset entertainment type target subtask, a preset driving type target subtask, and a preset auxiliary type target subtask, the power consumption mode is determined to be a first power consumption mode, wherein the first power consumption mode is used to represent the power consumption mode of the target operating unit when the cockpit system uses the target operating unit to run the target task at the upper limit frequency of the target operating unit; In response to the target task including a preset driving type target subtask, a preset entertainment type target subtask, and a preset background type target subtask, the power consumption mode is determined to be a second power consumption mode, wherein the second power consumption mode is used to represent the power consumption mode when the cockpit system uses the target operating unit to run the target task at the lower limit frequency of the target operating unit. The power consumption mode of the target operating unit is determined as follows: In response to the target task including a target sub-task of a preset interactive type and a target sub-task of a preset entertainment type, the power consumption mode is determined as a third power consumption mode. The third power consumption mode represents the power consumption mode of the target operating unit when the cockpit system uses the target operating unit and disables redundant operating units to run the target task. Redundant operating units are operating units other than the target operating unit. In response to the target task including a target sub-task of a preset background type, the power consumption mode is determined as a fourth power consumption mode. The fourth power consumption mode represents the power consumption mode of the target operating unit when the cockpit system uses both the target operating unit and a wake-up unit to run the target task. The wake-up unit is a unit used to wake up the vehicle's sensing devices.

[0150] Optionally, when the above computer program is executed by the processor, the program code implements the following steps: adjusting the initial sequence information to obtain target sequence information, wherein the target sequence information is used to represent the target order of executing the target task; in the cockpit system, according to the power consumption mode and the target sequence information, the target running unit is used to run the target sub-task.

[0151] In the embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

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

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

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

[0155] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A mission run method of a vehicle, characterized by, The method comprises the following steps: determining a target task to be executed in a cabin system of a vehicle; allocating a running unit matched with the cabin system to the target task based on a type of the target task, to obtain a target running unit; determining a power consumption mode of the target running unit, wherein the power consumption mode is used to represent a mode of power consumption of the target running unit when the cabin system executes the target task by using the target running unit; executing the target task in the cabin system by using the target running unit according to the power consumption mode and initial sequence information of the target task, wherein the initial sequence information is used to represent an initial sequence of executing the target task.

2. The method of claim 1, wherein, The method comprises the following steps: determining a type relationship between the type and a preset type; allocating the running unit to the target task based on the type relationship, to obtain the target running unit.

3. The method of claim 2, wherein, The target task comprises at least one target sub-task, and the method of determining the type relationship between the type and the preset type comprises the following steps: determining a type relationship between the type of the target sub-task and the preset type.

4. The method of claim 2, wherein, The target task comprises at least one target sub-task, and the method of allocating the running unit to the target task based on the type relationship, to obtain the target running unit, comprises the following steps: allocating the running unit to the target sub-task based on the type relationship between the type of the target sub-task and the preset type, to obtain the target running unit.

5. The method of claim 4, wherein, The preset type comprises a preset driving type, a preset auxiliary type, a preset interaction type, a preset entertainment type and a preset background type, the running unit comprises a central running unit, a graphics running unit, a network running unit and a signal processing unit, the central running unit comprises a first sub-running unit, a second sub-running unit and a third sub-running unit, the first sub-running unit, the second sub-running unit and the third sub-running unit are different sub-running units arranged in the central running unit, and the method of allocating the running unit to the target sub-task based on the type relationship between the type of the target sub-task and the preset type, to obtain the target running unit, comprises the following steps: in response to the type relationship being that the type of the target sub-task is the same as the preset driving type, allocating the first sub-running unit in the central running unit, the graphics running unit and the network running unit to the target sub-task, to obtain the target running unit; in response to the type relationship being that the type of the target sub-task is the same as the preset auxiliary type, allocating the second sub-running unit in the central running unit, the graphics running unit, the network running unit and the signal processing unit to the target sub-task, to obtain the target running unit; in response to the type relationship being that the type of the target sub-task is the same as the preset interaction type, allocating the second sub-running unit to the target sub-task, to obtain the target running unit; In response to the type relationship being that the type of the target sub-task is the same as the preset entertainment type, the third sub-running unit, the graphic running unit and the signal processing unit in the central running unit are allocated to the target sub-task, to obtain the target running unit; In response to the type relationship being that the type of the target sub-task is the same as the preset background type, the third sub-running unit is allocated to the target sub-task, to obtain the target running unit.

6. The method of claim 1, wherein, The power consumption mode of the target running unit is determined, including: In response to the target task including a target sub-task of a preset entertainment type, a target sub-task of a preset driving type and a target sub-task of a preset auxiliary type, the power consumption mode is determined as a first power consumption mode, where the first power consumption mode is used to represent a mode of power consumption of the target running unit when the target running unit is used by the cabin system to run the target task at an upper limit frequency of the target running unit; In response to the target task including a target sub-task of a preset driving type, a target sub-task of a preset entertainment type and a target sub-task of a preset background type, the power consumption mode is determined as a second power consumption mode, where the second power consumption mode is used to represent a mode of power consumption of the target running unit when the target running unit is used by the cabin system to run the target task at a lower limit frequency of the target running unit; In response to the target task including a target sub-task of a preset interaction type and a target sub-task of a preset entertainment type, the power consumption mode is determined as a third power consumption mode, where the third power consumption mode is used to represent a mode of power consumption of the target running unit when the target running unit is used by the cabin system and a redundant running unit is turned off to run the target task, the redundant running unit being the running unit other than the target running unit in the running unit; In response to the target task including a target sub-task of a preset background type, the power consumption mode is determined as a fourth power consumption mode, where the fourth power consumption mode is used to represent a mode of power consumption of the target running unit when the target running unit is used by the cabin system and a wake-up unit to run the target task, the wake-up unit being a unit for waking up a sensing device of the vehicle.

7. The method according to any one of claims 1 to 6, characterized in that, The target task includes at least one target sub-task, and in the cabin system, the target task is run by using the target running unit according to the power consumption mode and initial order information of the target task, including: The initial order information is adjusted to obtain target order information, where the target order information is used to represent a target order of executing the target task; In the cabin system, the target sub-task is run by using the target running unit according to the power consumption mode and the target order information.

8. A mission running apparatus of a vehicle characterized by comprising: including: A first determination unit is configured to determine a target task to be run in a cabin system of a vehicle; An allocation unit is configured to allocate, based on a type of the target task, a running unit matched with the cabin system to the target task, to obtain a target running unit; A second determining unit is configured to determine a power consumption mode of the target running unit, wherein the power consumption mode is used to represent a mode of power consumption of the target running unit when the cabin system adopts the target running unit to run the target task. A running unit is configured to run the target task in the cabin system by adopting the target running unit according to the power consumption mode and initial sequence information of the target task, wherein the initial sequence information is used to represent an initial sequence of executing the target task.

9. An electronic device, comprising: The method comprises the following steps: A memory is configured to store an executable program; A processor is configured to run the program, wherein the program is configured to execute the method in any one of claims 1 to 7 when the program is running.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises a stored executable program, wherein the executable program is configured to control a device where the storage medium is located to execute the method in any one of claims 1 to 7 when the executable program is running.

Images