Vehicle control task execution method and device, vehicle terminal, mobile terminal and medium

Abstract

This application provides a method, apparatus, vehicle-mounted terminal, mobile terminal, and medium for executing vehicle control tasks. In this method, the vehicle-mounted terminal determines the execution device for each vehicle control task based on task data in a directed acyclic graph (DAG) of acquired task dependencies. Then, the vehicle control task executed by the mobile terminal, along with its task data, is sent to the mobile terminal. Upon receiving input data for the vehicle control task, both the mobile terminal and the vehicle-mounted terminal execute the task according to the input data, obtaining output data. Then, based on the task data, the output data can be retained as input data, sent as input data to the other party, or used as data to be integrated. Finally, the vehicle-mounted terminal integrates all the data to be integrated and outputs it. This solution determines the execution device for each vehicle control task through the task data, enabling both the vehicle-mounted terminal and the mobile terminal to execute the assigned vehicle control task, thus improving task execution efficiency.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method, apparatus, vehicle terminal, mobile terminal and medium for performing vehicle control tasks. Background Technology

[0002] With the continuous development of technology, vehicles are becoming increasingly functional, and the tasks they require for vehicle control are also increasing. The vehicle's onboard terminal can generate control tasks by parsing user-inputted voice or text, and it can also receive control tasks generated by other devices or itself.

[0003] In existing technologies, in order to reduce the computing power pressure on vehicle terminals, the execution of vehicle control tasks is usually carried out by the vehicle terminal randomly sending some control tasks to other devices for execution, while the vehicle terminal itself executes some control tasks.

[0004] However, some vehicle control tasks can only be executed on the in-vehicle terminal, which can lead to problems such as the inability to execute vehicle control tasks or low execution efficiency. Summary of the Invention

[0005] The vehicle control task execution method, apparatus, vehicle terminal, mobile terminal and medium provided in the embodiments of this application are used to solve the problem in the prior art that the vehicle terminal randomly sends some control tasks to other devices for execution, resulting in the vehicle control task being unable to be executed or having low execution efficiency.

[0006] In a first aspect, embodiments of this application provide a method for executing vehicle control tasks, applied to an in-vehicle terminal, the method comprising:

[0007] Based on the task data of each vehicle control task in the obtained directed acyclic graph of task dependencies, the execution device of each vehicle control task is determined, wherein the execution device is an in-vehicle terminal or a mobile terminal.

[0008] Send the vehicle control task and its data for each execution device (mobile terminal) to the mobile terminal.

[0009] Receive input data or data to be integrated sent by the mobile terminal;

[0010] For each vehicle control task executed by an in-vehicle terminal, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is either sent by the mobile terminal or retained by the in-vehicle terminal.

[0011] Based on the task data of the vehicle control task, the output data may be retained as input data, sent to the mobile terminal as input data, or retained as data to be integrated.

[0012] After obtaining the target number of data to be integrated, all the data to be integrated are integrated and output. The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of the task dependency relationship.

[0013] In one possible implementation, determining the execution device for each vehicle control task based on the task data of each vehicle control task in the acquired directed acyclic graph of task dependencies includes:

[0014] For each vehicle control task, if the actuator in the task data of the vehicle control task belongs to a preset list of vehicle terminal devices, then the execution device of the vehicle control task is determined to be a vehicle terminal.

[0015] In one possible implementation, the method further includes:

[0016] For each vehicle control task, the following processing is performed:

[0017] If the actuator in the task data of the vehicle control task does not belong to the preset list of vehicle terminal devices, then based on the obtained device data of the mobile terminal and the task data of the vehicle control task, it is determined whether the preset conditions are met.

[0018] If each preset condition is met, then the device executing the vehicle control task is determined to be a mobile terminal;

[0019] If any preset conditions are not met, then the device executing the vehicle control task is determined to be an in-vehicle terminal.

[0020] In one possible implementation, the device data of the mobile terminal includes: remaining battery power, temperature, available computing power, and packet loss rate in communication between the mobile terminal and the vehicle terminal.

[0021] All preset conditions include at least one of the following: the computational load required for the task in the vehicle control task data is greater than a preset first computational load threshold; the duration required for the task in the vehicle control task data is greater than a preset duration threshold; the remaining battery power of the mobile terminal is greater than a preset battery power threshold; the temperature of the mobile terminal is less than a preset temperature threshold; the available computational load of the mobile terminal is greater than a preset second computational load threshold; and the packet loss rate of the communication between the mobile terminal and the vehicle terminal is less than a preset packet loss rate threshold.

[0022] In one possible implementation, the step of retaining the output data as input data, sending it to the mobile terminal as input data, or retaining it as data to be integrated, based on the task data of the vehicle control task, includes:

[0023] If the output data destination data in the task data of the vehicle control task represents data integration, then the output data will be retained as data to be integrated.

[0024] If the output data destination data in the task data of the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, then the output data is retained as input data.

[0025] If the output data destination data in the task data of the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is a mobile terminal, then the output data is sent to the mobile terminal as input data.

[0026] Secondly, embodiments of this application provide a method for executing vehicle control tasks, applied to a mobile terminal, the method comprising:

[0027] Receive vehicle control tasks and task data for each vehicle control task sent by the vehicle terminal;

[0028] For each vehicle control task, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is sent by the vehicle terminal or retained by the mobile terminal.

[0029] Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the vehicle terminal as input data, or sent to the vehicle terminal as data to be integrated.

[0030] In one possible implementation, the step of retaining the output data as input data, sending it to the vehicle terminal as input data, or sending it to the vehicle terminal as data to be integrated, based on the task data of the vehicle control task, includes:

[0031] If the output data destination data in the task data of the vehicle control task represents data integration, then the output data is sent to the vehicle terminal as data to be integrated.

[0032] If the output data destination data in the task data of the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, then the output data is sent to the vehicle terminal as input data.

[0033] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is a mobile terminal, then the output data will be retained as input data.

[0034] Thirdly, embodiments of this application provide a device for executing vehicle control tasks, comprising:

[0035] The processing module is used to determine the execution device for each vehicle control task based on the obtained directed acyclic graph of task dependencies and the task data of each vehicle control task in the directed acyclic graph of task dependencies. The execution device is an in-vehicle terminal or a mobile terminal.

[0036] The sending module is used to send the vehicle control task and its task data of each execution device to the mobile terminal.

[0037] A receiving module is used to receive input data or data to be integrated sent by the mobile terminal;

[0038] The processing module is further configured to:

[0039] For each vehicle control task executed by an in-vehicle terminal, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is either sent by the mobile terminal or retained by the in-vehicle terminal.

[0040] Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the mobile terminal as input data through the sending module, or retained as data to be integrated.

[0041] After obtaining the target number of data to be integrated, all the data to be integrated are integrated and output. The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of the task dependency relationship.

[0042] Fourthly, embodiments of this application provide a device for executing vehicle control tasks, comprising:

[0043] The receiving module is used to receive vehicle control tasks and task data for each vehicle control task sent by the vehicle terminal.

[0044] Processing module, used for:

[0045] For each vehicle control task, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is sent by the vehicle terminal or stored by the mobile terminal.

[0046] Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the vehicle terminal as input data through the sending module, or sent to the vehicle terminal as data to be integrated through the sending module.

[0047] Fifthly, embodiments of this application provide a vehicle-mounted terminal, including:

[0048] Processor, memory, communication interface;

[0049] The memory is used to store the executable instructions of the processor;

[0050] The processor is configured to execute the method for performing the vehicle control task as described in any of the first aspects by executing the executable instructions.

[0051] Sixthly, embodiments of this application provide a mobile terminal, including:

[0052] Processor, memory, communication interface;

[0053] The memory is used to store the executable instructions of the processor;

[0054] The processor is configured to execute the method for performing the vehicle control task as described in any of the second aspects by executing the executable instructions.

[0055] In a seventh aspect, embodiments of this application provide a readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method for executing the vehicle control task as described in either the first or second aspect.

[0056] Eighthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, is used to implement the method for executing the vehicle control task as described in either the first or second aspect.

[0057] The vehicle control task execution method, apparatus, vehicle-mounted terminal, mobile terminal, and medium provided in this application embodiment determine the execution device for each vehicle control task based on the task data of each vehicle control task in the acquired directed acyclic graph of task dependencies. Then, the vehicle control task executed by the mobile terminal and its task data are sent to the mobile terminal. When the mobile terminal and vehicle-mounted terminal receive the input data for the vehicle control task, they execute the vehicle control task according to the input data, obtaining output data. The mobile terminal, based on the task data, retains the output data as input data, sends it to the vehicle-mounted terminal as input data, or sends it to the vehicle-mounted terminal as data to be integrated. The vehicle-mounted terminal, based on the task data, retains the output data as input data, sends it to the mobile terminal as input data, or retains it as data to be integrated. Finally, the vehicle-mounted terminal integrates all the data to be integrated and outputs it. This solution determines the execution device for each vehicle control task based on the task data of each vehicle control task in the directed acyclic graph of task dependencies, enabling both the vehicle-mounted terminal and the mobile terminal to execute the assigned vehicle control task, thus improving task execution efficiency. Attached Figure Description

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

[0059] Figure 1a A flowchart illustrating an embodiment of the vehicle control task execution method provided in this application;

[0060] Figure 1b Example graph of the directed acyclic graph of task dependencies provided in this application;

[0061] Figure 2 A flowchart illustrating Embodiment 2 of the vehicle control task execution method provided in this application;

[0062] Figure 3 A schematic diagram of the structure of the vehicle control task execution device according to Embodiment 1 provided in this application;

[0063] Figure 4 A schematic diagram of the structure of the vehicle control task execution device according to Embodiment 2 provided in this application;

[0064] Figure 5 This application provides a structural schematic diagram of an in-vehicle terminal;

[0065] Figure 6 This is a schematic diagram of the structure of a mobile terminal provided in this application.

[0066] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0067] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0068] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular 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 a 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.

[0069] With the continuous development of technology, vehicles are becoming increasingly functional, and the tasks they require for vehicle control are also increasing. The vehicle's onboard terminal can generate control tasks by parsing user-inputted voice or text, and it can also receive control tasks generated by other devices or itself.

[0070] In existing technologies, to reduce the computational burden on in-vehicle terminals, the execution of vehicle control tasks typically involves the in-vehicle terminal randomly sending some control tasks to other devices for execution, while the in-vehicle terminal itself performs some control tasks. However, some vehicle control tasks can only be executed on the in-vehicle terminal, leading to problems such as tasks failing to execute or having low execution efficiency.

[0071] To address the problems existing in the prior art, the inventors, during their research on vehicle control task execution methods, discovered that, in order for every possible vehicle control task to be executed, the vehicle-mounted terminal can determine the execution device for each vehicle control task based on the task data of each vehicle control task in a directed acyclic graph of task dependencies. The vehicle control task with the mobile terminal as the execution device, along with its task data, is sent to the mobile terminal. Upon receiving the input data for the vehicle control task, both the mobile terminal and the vehicle-mounted terminal execute the vehicle control task according to the input data, obtaining output data. Then, based on the task data, the output data can be retained as input data, sent as input data to the other party, or used as data to be integrated. Finally, the vehicle-mounted terminal integrates all the data to be integrated and outputs it. Based on the above inventive concept, the vehicle control task execution scheme of this application was designed.

[0072] The following provides an example illustrating the application scenarios of the vehicle control task execution method provided in this application.

[0073] For example, in this application scenario, a user drives a vehicle and speaks to the in-vehicle terminal to control the vehicle.

[0074] The vehicle terminal uses a large language model to process the vehicle control voice, obtain the original task, and then decomposes the original task to obtain a directed acyclic graph of task dependencies, as well as the task data of each vehicle control task in the directed acyclic graph of task dependencies.

[0075] Then, based on the task data of each vehicle control task, the execution device for each vehicle control task is determined. The vehicle control task and its task data for each execution device (a mobile terminal) are then sent to the mobile terminal.

[0076] When the mobile terminal receives input data for the vehicle control task, it executes the vehicle control task based on the input data and obtains the output data of the vehicle control task. Then, based on the task data of the vehicle control task, it retains the output data as input data, sends it to the vehicle terminal as input data, or sends it to the vehicle terminal as data to be integrated.

[0077] When the vehicle terminal receives the input data for the vehicle control task, it executes the vehicle control task based on the input data and obtains the output data of the vehicle control task. Then, based on the task data of the vehicle control task, it retains the output data as input data, sends it to the mobile terminal as input data, or retains it as data to be integrated.

[0078] After receiving the target number of data points to be integrated, the vehicle-mounted terminal integrates all the data and outputs the results. The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of task dependencies.

[0079] It should be noted that the above scenario is only an example of an application scenario provided by the embodiments of this application. The embodiments of this application do not limit the actual form of the various devices included in the scenario, nor do they limit the interaction method between devices. In the specific application of the solution, it can be set according to actual needs.

[0080] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0081] Figure 1a This is a flowchart illustrating an embodiment of the vehicle control task execution method provided in this application. This embodiment describes how, based on the task data of each vehicle control task in a directed acyclic graph with task dependencies, the vehicle terminal determines the execution device for each vehicle control task. Then, the vehicle control task whose execution device is a mobile terminal is sent to the mobile terminal for execution, thus enabling the vehicle control task whose device is the vehicle terminal to execute itself. The method in this embodiment can be implemented through software, hardware, or a combination of both. For example... Figure 1a As shown, the specific steps for executing this vehicle control task include:

[0082] S101: The vehicle terminal determines the execution device for each vehicle control task based on the task data of each vehicle control task in the acquired directed acyclic graph of task dependencies.

[0083] In this step, after the vehicle terminal obtains the task data of each vehicle control task in the directed acyclic graph of task dependencies, in order to improve the execution efficiency of the vehicle control tasks, it is necessary to determine the execution device of each vehicle control task based on the task data of each vehicle control task in the obtained directed acyclic graph of task dependencies. The execution device is either the vehicle terminal or the mobile terminal.

[0084] Specifically, for each vehicle control task, if the actuator in the task data of the vehicle control task belongs to the preset list of vehicle terminal devices, it means that the vehicle control task can only be executed by the vehicle terminal, and the execution device of the vehicle control task is determined to be the vehicle terminal.

[0085] For example, in the task data of a vehicle control task, the actuator is the air conditioner, which belongs to the preset list of vehicle terminal devices. The mobile terminal cannot control the air conditioner; only the vehicle terminal can control it. Therefore, the execution device for this vehicle control task is the vehicle terminal.

[0086] If the actuator in the task data of the vehicle control task is not in the preset list of vehicle terminal devices, the execution device is determined based on the device data of the mobile terminal and the task data of the vehicle control task.

[0087] It's important to note that isolated vertices exist in a directed acyclic graph (DAG) of task dependencies, meaning there are vehicle control tasks with both out-degree and in-degree of 0. In a DAG, vertices represent vehicle control tasks, and directed edges between two vertices represent dependencies. If vehicle control task A points to vehicle control task B in the DAG, it means that vehicle control task B depends on vehicle control task A, and the output data of vehicle control task A is the input data of vehicle control task B.

[0088] For example, Figure 1b Example graph of the directed acyclic graph of task dependencies provided in this application, such as Figure 1b As shown, in the directed acyclic graph of task dependencies, the points represent vehicle control tasks, and the directed edges between two points represent dependencies.

[0089] It should be noted that the vehicle terminal can be a smart cockpit host, a vehicle controller, or a comprehensive control terminal connected to the vehicle control domain, etc. This application does not limit the vehicle terminal, and it can be determined according to the actual situation.

[0090] It should be noted that the vehicle terminal can obtain the task data of each vehicle control task in the directed acyclic graph of task dependencies in the following ways: after receiving the original task sent from voice interaction, touch screen operation, underlying system or other devices, the original task is split and processed by a large language model to obtain the directed acyclic graph of task dependencies, and the task data of each vehicle control task in the directed acyclic graph of task dependencies.

[0091] Alternatively, after obtaining the original task, the original task is split using a preset task splitting template to obtain a directed acyclic graph of task dependencies, and task data for each vehicle control task in the directed acyclic graph of task dependencies.

[0092] It can also be: receiving a directed acyclic graph of task dependencies sent by other devices, and task data for each vehicle control task in the directed acyclic graph of task dependencies.

[0093] This application does not limit the method of obtaining task data for each vehicle control task in the directed acyclic graph of task dependencies; it can be determined according to the actual situation.

[0094] S102: The vehicle terminal sends the vehicle control task and its task data of each execution device to the mobile terminal.

[0095] In this step, after the vehicle terminal determines the execution device for each vehicle control task, it sends the vehicle control task and its data for each execution device (which is a mobile terminal) to the mobile terminal so that the mobile terminal can subsequently execute the vehicle control task.

[0096] It should be noted that the vehicle terminal can also send the task identifier and execution device of each vehicle control task to the mobile terminal.

[0097] For example, the vehicle control task performed by the mobile terminal may be a weather query task, a data calculation task, an image recognition task, a route planning task, etc. This application embodiment does not limit the vehicle control task performed by the mobile terminal, and it can be determined according to the actual situation.

[0098] It should be noted that the mobile terminal can be a smartphone, tablet, or other portable computing device. This application does not limit the mobile terminal, and it can be determined according to the actual situation.

[0099] It should be noted that the communication connection between the vehicle terminal and the mobile terminal can be wired or wireless. Wireless connection can be Wireless Fidelity (WiFi), Bluetooth, etc. This application does not limit the communication connection method between the vehicle terminal and the mobile terminal; it can be determined according to the actual situation.

[0100] S103: After the mobile terminal receives the vehicle control task and the task data of each vehicle control task sent by the vehicle terminal, for each vehicle control task, when the input data of the vehicle control task is obtained, the mobile terminal executes the vehicle control task according to the input data and obtains the output data of the vehicle control task.

[0101] In this step, after the vehicle terminal sends the vehicle control task and its task data of each execution device to the mobile terminal, the mobile terminal can receive the data. Then, for each vehicle control task, when the input data of the vehicle control task is obtained, the vehicle control task is executed according to the input data to obtain the output data of the vehicle control task. The input data is sent by the vehicle terminal or stored by the mobile terminal.

[0102] Specifically, if the in-degree of the vehicle control task in the directed acyclic graph of task dependencies is 0, then the task data in the vehicle control task includes the input data of the task, so it can be obtained, and then the vehicle control task can be executed according to the input data to obtain the output data of the vehicle control task.

[0103] If the in-degree of the vehicle control task in the directed acyclic graph of task dependencies is not 0, it means that the output data of other vehicle control tasks is the input data of this vehicle control task.

[0104] The mobile terminal will determine the processing method of the output data of the vehicle control task of the mobile terminal for each execution device. When the mobile terminal determines that the output data is to be retained as input data, the input data will carry a task identifier. If the task identifier carried includes the task identifier of the task, the mobile terminal can obtain the input data of the vehicle control task, and then execute the vehicle control task according to the input data to obtain the output data of the vehicle control task.

[0105] The vehicle terminal will determine the processing method of the output data of the vehicle control task of each execution device. When the vehicle terminal determines that the output data is sent to the mobile terminal as input data, the input data carries a task identifier. If the task identifier carried includes the task identifier of the task, the mobile terminal can obtain the input data of the vehicle control task, and then execute the vehicle control task according to the input data to obtain the output data of the vehicle control task.

[0106] S104: The mobile terminal, based on the task data of the vehicle control task, retains the output data as input data, sends it to the vehicle terminal as input data, or sends it to the vehicle terminal as data to be integrated.

[0107] In this step, after the mobile terminal obtains the output data of the vehicle control task, it retains the output data as input data, sends it to the vehicle terminal as input data, or sends it to the vehicle terminal as data to be integrated, based on the task data of the vehicle control task.

[0108] Specifically, if the output data destination data in the vehicle control task represents data integration, it indicates that the output data of the vehicle control task belongs to the task execution result, and the output data is sent to the vehicle terminal as data to be integrated.

[0109] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, it means that the output data of the vehicle control task is the input data of the vehicle control task whose execution subject is the vehicle terminal. In this case, the output data is sent to the vehicle terminal as input data, and the input data carries the task identifier in the output data destination data.

[0110] If the output data destination data in the vehicle control task is a task identifier, and if the output data destination data includes the identifier of a task whose execution subject is a mobile terminal, it means that the output data of the vehicle control task is the input data of a vehicle control task whose execution subject is a mobile terminal. In this case, the output data is retained as input data, and the input data carries the task identifier in the output data destination data.

[0111] It should be noted that after obtaining the directed acyclic graph of task dependencies, the vehicle terminal can determine the destination data of the output data for each vehicle control task and store it in the task data. The method for determining the destination data of the output data is as follows: if the out-degree of the vehicle control task is 0, then the destination data of the output data representing data integration is determined; if the out-degree of the vehicle control task is not 0, then the destination data of the output data is determined to be the task identifier, and it is the identifier of the vehicle control task to which this vehicle control task points.

[0112] S105: The vehicle-mounted terminal receives input data or data to be integrated sent by the mobile terminal.

[0113] In this step, after the mobile terminal sends the input data or data to be integrated to the vehicle terminal, the vehicle terminal can receive the input data or data to be integrated sent by the mobile terminal.

[0114] S106: For each vehicle control task executed by the vehicle terminal, when the input data of the vehicle control task is obtained, the vehicle terminal executes the vehicle control task according to the input data and obtains the output data of the vehicle control task.

[0115] In this step, for each vehicle control task executed by the vehicle terminal, when the input data of the vehicle control task is obtained, the vehicle terminal executes the vehicle control task according to the input data and obtains the output data of the vehicle control task. The input data is sent by the mobile terminal or stored by the vehicle terminal.

[0116] Specifically, if the in-degree of the vehicle control task in the directed acyclic graph of task dependencies is 0, then the task data in the vehicle control task includes the input data of the task, so it can be obtained, and then the vehicle control task can be executed according to the input data to obtain the output data of the vehicle control task.

[0117] If the in-degree of the vehicle control task in the directed acyclic graph of task dependencies is not 0, it means that the output data of other vehicle control tasks is the input data of this vehicle control task.

[0118] The mobile terminal will determine the processing method of the output data of the vehicle control task of the mobile terminal for each execution device. When the mobile terminal determines that the output data is sent to the vehicle terminal as the input data of the vehicle terminal, the input data will carry a task identifier. If the task identifier carried includes the task identifier of the task, the vehicle terminal can obtain the input data of the vehicle control task, and then execute the vehicle control task according to the input data to obtain the output data of the vehicle control task.

[0119] The vehicle terminal will determine the processing method of the output data of the vehicle control task of each execution device. When the vehicle terminal determines that the output data is to be retained as input data, the input data carries a task identifier. If the task identifier carried includes the task identifier of the task, the mobile terminal can obtain the input data of the vehicle control task, and then execute the vehicle control task according to the input data to obtain the output data of the vehicle control task.

[0120] It should be noted that the vehicle control tasks performed by the vehicle terminal can be tasks such as turning on the air conditioning, planning navigation routes, or turning on the windshield wipers. This application embodiment does not limit the vehicle control tasks performed by the vehicle terminal, and can be determined according to the actual situation.

[0121] S107: The vehicle terminal retains the output data as input data, sends it to the mobile terminal as input data, or retains it as data to be integrated, based on the task data of the vehicle control task.

[0122] In this step, after receiving the output data of the vehicle control task, the vehicle terminal, based on the task data of the vehicle control task, retains the output data as input data, sends it to the mobile terminal as input data, or retains it as data to be integrated.

[0123] Specifically, if the output data destination data in the vehicle control task represents data integration, it indicates that the output data of the vehicle control task belongs to the task execution result, and the output data will be retained as data to be integrated.

[0124] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, it means that the output data of the vehicle control task is the input data of the vehicle control task whose execution subject is the vehicle terminal. In this case, the output data is retained as input data, and the input data carries the task identifier in the output data destination data.

[0125] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is a mobile terminal, it means that the output data of the vehicle control task is the input data of the vehicle control task whose execution subject is a mobile terminal. In this case, the output data is sent to the mobile terminal as input data, and the input data carries the task identifier in the output data destination data.

[0126] S108: After obtaining the target number of data to be integrated, the vehicle terminal integrates all the data to be integrated and outputs it.

[0127] In this step, the vehicle terminal will perform vehicle control tasks to obtain data to be integrated, and receive data to be integrated sent by the mobile terminal. After obtaining the target number of data to be integrated, it means that all vehicle control tasks have been completed. All data to be integrated are then integrated to obtain the task execution result, which is then output.

[0128] The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of task dependencies. The output data of vehicle control tasks with an out-degree of 0 belongs to the task execution results.

[0129] It should be noted that large voice models can be deployed on both vehicle-mounted and mobile terminals to perform vehicle control tasks. Mobile terminals can deploy complete large language models, while vehicle-mounted terminals can deploy distilled large language models to save computing power.

[0130] The vehicle control task execution method provided in this embodiment determines the execution device for each vehicle control task based on the task data of each vehicle control task in the acquired directed acyclic graph of task dependencies. Then, the vehicle control task with the mobile terminal as the execution device and its task data are sent to the mobile terminal. When the mobile terminal and the vehicle terminal receive the input data for the vehicle control task, they execute the vehicle control task according to the input data and obtain output data. The mobile terminal, based on the task data, either retains the output data as input data, sends it to the vehicle terminal as input data, or sends it to the vehicle terminal as data to be integrated. The vehicle terminal, based on the task data, either retains the output data as input data, sends it to the mobile terminal as input data, or retains it as data to be integrated. Finally, the vehicle terminal integrates all the data to be integrated and outputs it. This solution determines the execution device for each vehicle control task by using the task data of each vehicle control task in the directed acyclic graph of task dependencies, enabling both the vehicle terminal and the mobile terminal to execute the assigned vehicle control task, thus improving task execution efficiency.

[0131] In addition, after obtaining the output data of the vehicle control task, the processing method of the output data is determined so that other vehicle control tasks can be executed.

[0132] Figure 2 This is a flowchart illustrating a second embodiment of the vehicle control task execution method provided in this application. Based on the above embodiments, this application describes how, when the actuator is not included in the preset list of vehicle terminal devices, the execution device is determined according to the device data of the mobile terminal and the task data of the vehicle control task. Figure 2 As shown, for each vehicle control task, the following steps are performed:

[0133] S201: If the actuator in the vehicle control task data does not belong to the preset vehicle terminal device list, then determine whether the preset conditions are all met based on the obtained mobile terminal device data and vehicle control task data; if there are preset conditions that are not met, then execute step S202; if each preset condition is met, then execute step S203.

[0134] In this step, if the actuator in the vehicle control task data is not in the preset vehicle terminal device list, it means that both the vehicle terminal and the mobile terminal are capable of performing the vehicle control task under normal circumstances. In order to determine who will perform the task, the preset conditions are determined based on the obtained mobile terminal device data and vehicle control task data.

[0135] The device data for the mobile terminal includes: remaining battery power, temperature, available computing power, and packet loss rate in communication between the mobile terminal and the vehicle terminal.

[0136] All preset conditions include at least one of the following: the computational load required for the task in the vehicle control task data is greater than a preset first computational load threshold; the duration required for the task in the vehicle control task data is greater than a preset duration threshold; the remaining battery power of the mobile terminal is greater than a preset battery power threshold; the temperature of the mobile terminal is less than a preset temperature threshold; the available computational load of the mobile terminal is greater than a preset second computational load threshold; and the packet loss rate of the communication between the mobile terminal and the vehicle terminal is less than a preset packet loss rate threshold.

[0137] It should be noted that the preset first computational load threshold can be 80 MFLOPs, 100 MFLOPs, 150 MFLOPs, etc.; the preset duration threshold can be 40ms, 50ms, 60ms, etc.; the preset battery level threshold can be 15%, 20%, 25%, etc.; the preset temperature threshold can be 40 degrees Celsius, 45 degrees Celsius, 50 degrees Celsius, etc.; the preset second computational load threshold can be 0.9 GFLOPs, 1 GFLOPs, 1.2 GFLOPs, etc.; and the preset packet loss rate threshold can be 4%, 5%, 7%, etc. This application embodiment does not limit the preset first computational load threshold, preset duration threshold, preset battery level threshold, preset temperature threshold, preset second computational load threshold, and preset packet loss rate threshold; these can be determined according to actual conditions.

[0138] It should be noted that the vehicle terminal can send a device data acquisition request to the mobile terminal. The mobile terminal sends its own device data to the vehicle terminal, and the vehicle terminal can then obtain the device data from the mobile terminal.

[0139] S202: The device executing the vehicle control task is determined to be the vehicle-mounted terminal.

[0140] In this step, if the vehicle terminal determines that a preset condition is not met, it means that the vehicle terminal is more suitable to perform the vehicle control task than the mobile terminal, and the vehicle terminal is determined to be the device for performing the vehicle control task.

[0141] If the computational load required for the vehicle control task is less than or equal to the preset first computational load threshold, it indicates that the computational load of the vehicle control task is small, the vehicle terminal is highly efficient in executing the vehicle control task, there is no need to send it to the mobile terminal for execution, and communication time can be saved. Therefore, the vehicle terminal is determined to be the device that executes the vehicle control task.

[0142] If the required time for a vehicle control task is less than or equal to a preset time threshold, it indicates that the vehicle control task needs to obtain output data quickly. In order to save time, the execution device for the vehicle control task is determined to be the vehicle terminal.

[0143] If the remaining battery power of the mobile terminal is less than or equal to the preset battery threshold, it indicates that the mobile terminal is in poor condition and is not suitable for performing the vehicle control task. Therefore, the vehicle terminal is determined to be the device that performs the vehicle control task.

[0144] If the temperature of the mobile terminal is greater than or equal to the preset temperature threshold, it indicates that the mobile terminal is in poor condition and is not suitable for performing the vehicle control task. Therefore, the vehicle terminal is determined to be the device that performs the vehicle control task.

[0145] If the available computing power of the mobile terminal is less than or equal to the preset second computing power threshold, it indicates that the efficiency of the available computing power of the mobile terminal in performing vehicle control tasks is low. Therefore, the device for performing vehicle control tasks is determined to be the vehicle terminal.

[0146] If the packet loss rate between the mobile terminal and the vehicle terminal is greater than or equal to the preset packet loss rate threshold, it indicates that the mobile terminal and the vehicle terminal are prone to data loss during the interaction process. In order to ensure the normal execution of the vehicle control task, the vehicle terminal is determined to be the execution device for the vehicle control task.

[0147] S203: The device executing the vehicle control task is determined to be a mobile terminal.

[0148] In this step, if the vehicle terminal determines that each preset condition is met, it means that the computational workload of the vehicle control task is large, the vehicle control task does not need to obtain output data quickly, the mobile terminal is in good condition, the mobile terminal has a lot of available computing power, the mobile terminal is not easy to lose data during the interaction between the mobile terminal and the vehicle terminal, and the mobile terminal has strong computing power. Therefore, the execution device of the vehicle control task is determined to be the mobile terminal.

[0149] In one implementation, if the vehicle-mounted terminal determines that each preset condition is met, and if the in-degree of the vehicle control task is not 0, then the executing device for the vehicle control task is determined to be a mobile terminal. If the in-degree of the vehicle control task is 0, then the ratio of the computational load required by the task to the available computational load of the vehicle-mounted terminal is used as a first ratio, and the ratio of the computational load required by the task to the available computational load of the mobile terminal is used as a second ratio. If the first ratio is less than the second ratio, it indicates that the resource consumption ratio of the vehicle-mounted terminal in executing the vehicle control task is relatively small, and then the executing device for the vehicle control task is determined to be the vehicle-mounted terminal; if the first ratio is greater than or equal to the second ratio, it indicates that the resource consumption ratio of the mobile terminal in executing the vehicle control task is relatively small, and then the executing device for the vehicle control task is determined to be the mobile terminal.

[0150] It should be noted that when the vehicle-mounted terminal and mobile terminal perform vehicle control tasks, they can record the duration of the task and the temperature change data of the mobile terminal during the task execution. This data can be used periodically to update the preset duration and temperature thresholds using a large language model.

[0151] The vehicle control task execution method provided in this embodiment determines the execution device of the vehicle control task through the device data of the mobile terminal and the task data of the vehicle control task, thereby realizing the allocation of the vehicle control task and improving the allocation accuracy.

[0152] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0153] Figure 3 This is a schematic diagram of the structure of an embodiment of the vehicle control task execution device provided in this application; the device can be integrated into the vehicle terminal in the above method embodiments, or it can be implemented through the vehicle terminal in the above method embodiments. Figure 3 As shown, the vehicle control task execution device 30 includes:

[0154] Processing module 31 is used to determine the execution device of each vehicle control task based on the obtained directed acyclic graph of task dependencies and the task data of each vehicle control task in the directed acyclic graph of task dependencies. The execution device is either an in-vehicle terminal or a mobile terminal.

[0155] The sending module 32 is used to send the vehicle control task and its task data of each execution device being a mobile terminal to the mobile terminal;

[0156] The receiving module 33 is used to receive input data or data to be integrated sent by the mobile terminal;

[0157] Processing module 31 is also used for:

[0158] For each vehicle control task executed by an in-vehicle terminal, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is either sent by the mobile terminal or retained by the in-vehicle terminal.

[0159] Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the mobile terminal as input data through the sending module 32, or retained as data to be integrated.

[0160] After obtaining the target number of data to be integrated, all the data to be integrated are integrated and output. The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of task dependencies.

[0161] Furthermore, processing module 31 is specifically used for:

[0162] For each vehicle control task, if the actuator in the task data of the vehicle control task belongs to the preset list of vehicle terminal devices, then the execution device of the vehicle control task is determined to be the vehicle terminal.

[0163] Furthermore, processing module 31 is also used for:

[0164] For each vehicle control task, the following processing is performed:

[0165] If the actuator in the vehicle control task data does not belong to the preset vehicle terminal device list, then determine whether the preset conditions are met based on the obtained mobile terminal device data and vehicle control task data.

[0166] If all preset conditions are met, then the device executing the vehicle control task is determined to be a mobile terminal;

[0167] If any preset conditions are not met, the device executing the vehicle control task is determined to be the vehicle-mounted terminal.

[0168] Furthermore, the device data of the mobile terminal includes: remaining battery power, temperature, available computing power, and packet loss rate in communication between the mobile terminal and the vehicle terminal;

[0169] All preset conditions include at least one of the following: the computational load required for the task in the vehicle control task data is greater than a preset first computational load threshold; the duration required for the task in the vehicle control task data is greater than a preset duration threshold; the remaining battery power of the mobile terminal is greater than a preset battery power threshold; the temperature of the mobile terminal is less than a preset temperature threshold; the available computational load of the mobile terminal is greater than a preset second computational load threshold; and the packet loss rate of the communication between the mobile terminal and the vehicle terminal is less than a preset packet loss rate threshold.

[0170] Furthermore, processing module 31 is specifically used for:

[0171] If the output data destination data in the vehicle control task data represents data integration, then the output data will be retained as the data to be integrated.

[0172] If the output data destination data in the vehicle control task is the task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, then the output data will be retained as input data.

[0173] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose executing entity is a mobile terminal, then the output data will be sent to the mobile terminal as input data.

[0174] The vehicle control task execution device provided in this embodiment is used to execute the technical solution of the vehicle terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0175] Figure 4 This is a schematic diagram of the structure of a second embodiment of the vehicle control task execution device provided in this application; the device can be integrated into the mobile terminal in the above method embodiments, or it can be implemented through the mobile terminal in the above method embodiments. Figure 4 As shown, the vehicle control task execution device 40 includes:

[0176] The receiving module 41 is used to receive the vehicle control task sent by the vehicle terminal and the task data of each vehicle control task;

[0177] Processing module 42 is used for:

[0178] For each vehicle control task, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is sent by the vehicle terminal or stored by the mobile terminal.

[0179] Based on the task data of the vehicle control task, the output data is retained as input data, sent to the vehicle terminal as input data through the sending module 43, or sent to the vehicle terminal as data to be integrated through the sending module 43.

[0180] Furthermore, processing module 42 is specifically used for:

[0181] If the output data in the vehicle control task data represents data integration, then the output data will be sent to the vehicle terminal as the data to be integrated.

[0182] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, then the output data will be sent to the vehicle terminal as input data.

[0183] If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is a mobile terminal, then the output data will be retained as input data.

[0184] The vehicle control task execution device provided in this embodiment is used to execute the technical solution of the mobile terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0185] Figure 5 This is a structural schematic diagram of a vehicle-mounted terminal provided in this application. Figure 5 As shown, the vehicle-mounted terminal 50 includes:

[0186] Processor 51, memory 52, and communication interface 53;

[0187] Memory 52 is used to store executable instructions of processor 51;

[0188] The processor 51 is configured to execute the technical solution of the vehicle terminal in any of the foregoing method embodiments by executing executable instructions.

[0189] Optionally, the memory 52 can be either standalone or integrated with the processor 51.

[0190] Optionally, when the memory 52 is a device independent of the processor 51, the vehicle terminal 50 may further include:

[0191] Bus 54, memory 52 and communication interface 53 are connected to processor 51 through bus 54 and complete communication with each other. Communication interface 53 is used to communicate with other devices.

[0192] Optionally, the communication interface 53 can be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write databases, and read-only databases). The memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk drive.

[0193] Bus 54 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0194] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0195] The vehicle-mounted terminal is used to execute the technical solution of the vehicle-mounted terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0196] Figure 6 This is a schematic diagram of the structure of a mobile terminal provided in this application. Figure 6 As shown, the mobile terminal 60 includes:

[0197] Processor 61, memory 62, and communication interface 63;

[0198] Memory 62 is used to store executable instructions of processor 61;

[0199] The processor 61 is configured to execute the technical solution of the mobile terminal in any of the foregoing method embodiments by executing executable instructions.

[0200] Optionally, the memory 62 can be either standalone or integrated with the processor 61.

[0201] Optionally, when the memory 62 is a device independent of the processor 61, the mobile terminal 60 may further include:

[0202] Bus 64, memory 62 and communication interface 63 are connected to processor 61 through bus 64 and complete communication with each other. Communication interface 63 is used to communicate with other devices.

[0203] Optionally, the communication interface 63 can be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write databases, and read-only databases). The memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk drive.

[0204] Bus 64 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0205] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0206] The mobile terminal is used to execute the technical solution of the mobile terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.

[0207] This application also provides a readable storage medium storing a computer program thereon, which, when executed by a processor, implements the technical solutions provided in any of the foregoing method embodiments.

[0208] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions provided in any of the foregoing method embodiments.

[0209] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. A method for executing a vehicle control task, characterized in that, Applied to vehicle-mounted terminals, the method includes: Based on the task data of each vehicle control task in the obtained directed acyclic graph of task dependencies, the execution device of each vehicle control task is determined, wherein the execution device is an in-vehicle terminal or a mobile terminal. Send the vehicle control task and its data for each execution device (mobile terminal) to the mobile terminal. Receive input data or data to be integrated sent by the mobile terminal; For each vehicle control task executed by an in-vehicle terminal, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is either sent by the mobile terminal or retained by the in-vehicle terminal. Based on the task data of the vehicle control task, the output data may be retained as input data, sent to the mobile terminal as input data, or retained as data to be integrated. After obtaining the target number of data to be integrated, all the data to be integrated are integrated and output. The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of the task dependency relationship.

2. The method according to claim 1, characterized in that, The step of determining the execution device for each vehicle control task based on the task data of each vehicle control task in the obtained directed acyclic graph of task dependencies includes: For each vehicle control task, if the actuator in the task data of the vehicle control task belongs to a preset list of vehicle terminal devices, then the execution device of the vehicle control task is determined to be a vehicle terminal.

3. The method according to claim 2, characterized in that, The method further includes: For each vehicle control task, the following processing is performed: If the actuator in the task data of the vehicle control task does not belong to the preset list of vehicle terminal devices, then based on the obtained device data of the mobile terminal and the task data of the vehicle control task, it is determined whether the preset conditions are met. If each preset condition is met, then the device executing the vehicle control task is determined to be a mobile terminal; If any preset conditions are not met, then the device executing the vehicle control task is determined to be an in-vehicle terminal.

4. The method according to claim 3, characterized in that, The device data of the mobile terminal includes: remaining battery power, temperature, available computing power, and packet loss rate in communication between the mobile terminal and the vehicle terminal. All preset conditions include at least one of the following: the computational load required for the task in the vehicle control task data is greater than a preset first computational load threshold; the duration required for the task in the vehicle control task data is greater than a preset duration threshold; the remaining battery power of the mobile terminal is greater than a preset battery power threshold; the temperature of the mobile terminal is less than a preset temperature threshold; the available computational load of the mobile terminal is greater than a preset second computational load threshold; and the packet loss rate of the communication between the mobile terminal and the vehicle terminal is less than a preset packet loss rate threshold.

5. The method according to any one of claims 1 to 3, characterized in that, The step of retaining the output data as input data, sending it to the mobile terminal as input data, or retaining it as data to be integrated, based on the task data of the vehicle control task, includes: If the output data destination data in the task data of the vehicle control task represents data integration, then the output data will be retained as data to be integrated. If the output data destination data in the task data of the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, then the output data is retained as input data. If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is a mobile terminal, then the output data is sent to the mobile terminal as input data.

6. A method for executing a vehicle control task, characterized in that, Applied to a mobile terminal, the method includes: Receive vehicle control tasks and task data for each vehicle control task sent by the vehicle terminal; For each vehicle control task, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is sent by the vehicle terminal or retained by the mobile terminal. Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the vehicle terminal as input data, or sent to the vehicle terminal as data to be integrated.

7. The method according to claim 6, characterized in that, The step of retaining the output data as input data, sending it to the vehicle terminal as input data, or sending it to the vehicle terminal as data to be integrated, based on the task data of the vehicle control task, includes: If the output data destination data in the task data of the vehicle control task represents data integration, then the output data is sent to the vehicle terminal as data to be integrated. If the output data destination data in the task data of the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is the vehicle terminal, then the output data is sent to the vehicle terminal as input data. If the output data destination data in the vehicle control task is a task identifier, and the output data destination data includes the identifier of the task whose execution subject is a mobile terminal, then the output data will be retained as input data.

8. A device for executing vehicle control tasks, characterized in that, include: The processing module is used to determine the execution device for each vehicle control task based on the obtained directed acyclic graph of task dependencies and the task data of each vehicle control task in the directed acyclic graph of task dependencies. The execution device is an in-vehicle terminal or a mobile terminal. The sending module is used to send the vehicle control task and its task data of each execution device to the mobile terminal. A receiving module is used to receive input data or data to be integrated sent by the mobile terminal; The processing module is further configured to: For each vehicle control task executed by an in-vehicle terminal, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is either sent by the mobile terminal or retained by the in-vehicle terminal. Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the mobile terminal as input data through the sending module, or retained as data to be integrated. After obtaining the target number of data to be integrated, all the data to be integrated are integrated and output. The target number is the number of vehicle control tasks with an out-degree of 0 in the directed acyclic graph of the task dependency relationship.

9. A device for executing vehicle control tasks, characterized in that, include: The receiving module is used to receive vehicle control tasks and task data for each vehicle control task sent by the vehicle terminal. Processing module, used for: For each vehicle control task, upon receiving the input data for the vehicle control task, the vehicle control task is executed based on the input data to obtain the output data for the vehicle control task. The input data is sent by the vehicle terminal or stored by the mobile terminal. Based on the task data of the vehicle control task, the output data can be retained as input data, sent to the vehicle terminal as input data through the sending module, or sent to the vehicle terminal as data to be integrated through the sending module.

10. A vehicle-mounted terminal, characterized in that, include: Processor, memory, communication interface; The memory is used to store the executable instructions of the processor; The processor is configured to execute the method of executing the vehicle control task according to any one of claims 1 to 5 by executing the executable instructions.

11. A mobile terminal, characterized in that, include: Processor, memory, communication interface; The memory is used to store the executable instructions of the processor; The processor is configured to execute the method of executing the vehicle control task according to any one of claims 6 to 7 by executing the executable instructions.

12. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the method for executing the vehicle control task as described in any one of claims 1 to 5, or any one of claims 6 to 7.

13. A computer program product, characterized in that, It includes a computer program, which, when executed by a processor, is used to implement the method for executing the vehicle control task as described in any one of claims 1 to 5, or any one of claims 6 to 7.

Images