Distributed scenario script execution method, device, system and storage medium
By allocating scene scripts between the Android subsystem and the QNX subsystem, the problem that the in-vehicle host Android system could not meet the high real-time requirements was solved, and the effect of executing high real-time scene tasks within 2 seconds after the whole vehicle is woken up was achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA FAW CO LTD
- Filing Date
- 2023-05-16
- Publication Date
- 2026-06-12
AI Technical Summary
Existing technologies cannot meet the high real-time requirements of script execution in scenarios under the Android system of the vehicle host, especially during the vehicle startup period.
A distributed scenario script execution system is adopted, which utilizes the multi-task collaborative scheduling service of the Android subsystem and the QNX subsystem to allocate scenario scripts to appropriate subsystems for execution. The Android subsystem is used for scripts with non-real-time requirements, while the QNX subsystem is used for scripts with high real-time requirements, ensuring execution within 2 seconds after the vehicle is woken up.
It enables the execution of high real-time tasks within 2 seconds after the vehicle is woken up, meeting the high real-time requirements of complex scenarios.
Smart Images
Figure CN116594746B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automotive control technology, and in particular to a distributed scene script execution method, apparatus, system, and storage medium. Background Technology
[0002] With the development of technology, the control of automobiles is becoming more and more automated and intelligent. In order to meet users' personalized needs for automobile control, some automatic control editing interfaces are usually reserved for users so that users can automatically control some functions of the car according to their own needs.
[0003] To facilitate user editing, a no-code development tool, namely a distributed scene engine, is typically provided. This distributed scene engine can be used to create functional flowcharts of vehicle atomic capabilities, enabling the vehicle to dynamically invoke various atomic capabilities according to the set logic.
[0004] Currently, the scenario development solution typically uses the easyrule rule engine under the single-process vehicle host Android system. By installing the easyrule rule engine under the vehicle host Android system, the scenario script is parsed on the vehicle terminal, the scenario execution trigger is determined, and the corresponding action is executed based on the condition judgment of the rules.
[0005] However, the single-process mode cannot meet the needs of more complex scenarios. Moreover, when running on the vehicle's Android system, the scenario scripts can only be executed after the vehicle system has fully started up. For some scenario scripts with high real-time requirements, the high real-time requirement cannot be met during the vehicle system startup. Summary of the Invention
[0006] This application provides a distributed scene script execution method, apparatus, system, and storage medium to meet the high real-time requirements of scene scripts with high real-time performance.
[0007] In a first aspect, embodiments of this application provide a distributed scenario script execution system, the system comprising:
[0008] The scene task manager and the first scene executor are set in the Android subsystem, and the second scene executor is set in the QNX subsystem;
[0009] The scene task manager allocates the scene scripts to be executed to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service that links the Android subsystem and the QNX subsystem.
[0010] The first scene executor is used to execute scene scripts assigned to the Android subsystem, and the second scene executor is used to execute scene scripts assigned to the QNX subsystem.
[0011] Secondly, embodiments of this application also provide a distributed scene script execution method, which includes:
[0012] After the scene script is generated, the scene task manager in the Android subsystem allocates the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service.
[0013] The Android subsystem executes the scene scripts assigned to it through the first scene executor.
[0014] The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor.
[0015] Thirdly, embodiments of this application also provide a distributed scene script execution device, which includes:
[0016] The allocation module is used to allocate the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service after the scene script is generated.
[0017] The first execution module is used by the Android subsystem to execute the scene scripts allocated to the Android subsystem through the first scene executor;
[0018] The second execution module is used by the QNX subsystem to execute the scene scripts assigned to the QNX subsystem through the second scene executor.
[0019] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the distributed scene script execution method provided in any embodiment of this application.
[0020] The technical solution of this application embodiment includes a scene task manager and a first scene executor configured in the Android subsystem, and a second scene executor configured in the QNX subsystem. The scene task manager allocates scene scripts to be executed to either the Android or QNX subsystem via a multi-task collaborative scheduling service linking the Android and QNX subsystems. The first scene executor executes the scene scripts allocated to the Android subsystem, and the second scene executor executes the scene scripts allocated to the QNX subsystem. Therefore, for scene tasks with high real-time requirements, they can be allocated to the QNX subsystem, allowing execution approximately 2 seconds after the entire vehicle is woken up, thus meeting the high real-time requirements of such tasks to a certain extent. Attached Figure Description
[0021] Figure 1 A schematic diagram of the architecture of the distributed scene script execution system provided in Embodiment 1 of this application;
[0022] Figure 2 This is a flowchart illustrating the distributed scenario script execution method provided in Embodiment 2 of this application;
[0023] Figure 3 This is a schematic diagram of the structure of a distributed scene script execution device provided in Embodiment 3 of this application;
[0024] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of this application. Detailed Implementation
[0025] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present application, not the entire structure.
[0026] Example 1
[0027] Figure 1 This is a schematic diagram of the architecture of the distributed scenario script execution system provided in Embodiment 1 of this application.
[0028] like Figure 1 As shown, the system provided in this embodiment may include: a scene task manager and a first scene executor set in the Android subsystem, and a second scene executor set in the QNX subsystem;
[0029] The scene task manager allocates the scene scripts to be executed to the Android subsystem or the QNX subsystem by linking the multi-task collaborative scheduling service of the Android subsystem and the QNX subsystem;
[0030] The first scene executor is used to execute scene scripts assigned to the Android subsystem, and the second scene executor is used to execute scene scripts assigned to the QNX subsystem.
[0031] The first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route;
[0032] The first scenario execution engine is used to parse the scenario scripts allocated to the Android subsystem to obtain scenario script execution rules; the first rule engine is connected to the first scenario execution engine and is used to execute the scenario scripts according to the scenario script execution rules; during the execution of the scenario scripts, the first rule engine is used to call the whole vehicle atomic-level service through the first atomic service route.
[0033] The first scene execution engine is used to parse scene scripts assigned to the Android subsystem. Specifically, it can parse multiple process branches, process advancement, node relationship judgment in the process, conflict detection, and split node execution in the scene script. For details, please refer to the business process modeling of BPMN, which will not be elaborated here.
[0034] In addition, when the first rule engine executes the scene script according to the scene script execution rules, it mainly includes judging the scene execution trigger conditions, judging the conditions based on the rules, and executing the corresponding actions.
[0035] Furthermore, the second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route; the second scenario execution engine is used to parse the scenario scripts allocated to the QNX subsystem to obtain scenario script execution rules; the second rule engine is connected to the second scenario execution engine and is used to execute the scenario scripts according to the scenario script execution rules; during the execution of the scenario scripts, the second rule engine is used to call the whole vehicle atomic-level services through the second atomic service route.
[0036] The second scene execution engine is used to parse scene scripts assigned to the Android subsystem. Specifically, it can parse multiple process branches, process advancement, node relationship judgment in the process, conflict detection, and split node execution in the scene script. For details, please refer to the business process modeling of BPMN, which will not be elaborated here.
[0037] In addition, when the second rule engine executes the scene script according to the scene script execution rules, it mainly includes judging the scene execution trigger conditions, judging the conditions based on the rules, and executing the corresponding actions.
[0038] The technical solution of this application embodiment includes a scene task manager and a first scene executor located in the Android subsystem, and a second scene executor located in the QNX subsystem. The scene task manager allocates scene scripts to be executed to either the Android or QNX subsystem via a multi-task collaborative scheduling service linking the Android and QNX subsystems. The first scene executor executes the scene scripts allocated to the Android subsystem, and the second scene executor executes the scene scripts allocated to the QNX subsystem. Therefore, for scene tasks with high real-time requirements, they can be allocated to the QNX subsystem, and the scene task can be executed approximately 2 seconds after the entire vehicle is woken up, which can meet the high real-time requirements of the scene task to a certain extent.
[0039] Example 2
[0040] Figure 2This is a flowchart illustrating the distributed scene script execution method provided in Embodiment 1 of this application. This embodiment is applicable to scenarios involving distributed scene script execution. The method can be executed by a distributed scene script execution device, which can be implemented in hardware and / or software and is generally integrated into electronic devices such as computers with data processing capabilities. Specifically, it includes the following steps:
[0041] Step 201: After the scene script is generated, the scene task manager in the Android subsystem allocates the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service.
[0042] In this step, the scene script can be generated by a dedicated script generator, such as manually generating the scene script corresponding to the requirements using a script generator.
[0043] The real-time requirements of different scenario scripts are different. The real-time requirement refers to the degree of rapid response required by the corresponding scenario script. For example, if the script needs to be executed as soon as the whole vehicle is woken up, its real-time requirement will be higher.
[0044] Since the Android subsystem in the vehicle system can only run normally 20 seconds after the vehicle is woken up, while the QNX subsystem can run normally 2 seconds after the vehicle is woken up, scenario scripts with high real-time requirements can be assigned to the QNX subsystem for execution.
[0045] Specifically, the scene task manager in the Android subsystem obtains the real-time requirements of scene scripts.
[0046] If the real-time requirement is greater than the preset threshold, the scenario script will be allocated to the QNX subsystem through the multi-task collaborative scheduling service; if the real-time requirement is less than or equal to the preset threshold, the scenario script will be allocated to the Android subsystem through the multi-task collaborative scheduling service.
[0047] There are two ways to obtain the real-time requirement score. One is to manually mark the real-time requirement score when the scene script is generated, and then directly obtain the marked real-time requirement score when it is obtained. That is, the scene task manager in the Android subsystem obtains the real-time requirement score configured when the scene script is generated.
[0048] Another approach is to determine the real-time requirement based on the result object of the scenario script. Here, the result object refers to the object that the scenario script ultimately affects. For example, if the ultimate goal of a scenario script is to control the temperature of the vehicle's air conditioning, then the result object of that scenario script is the air conditioning unit.
[0049] In addition, the mapping relationship between objects and real-time requirements can be pre-set. Different objects have different real-time requirements. For example, the air conditioner does not affect the safe operation of the whole vehicle and has a low real-time requirement, so it can be assigned a value less than the preset threshold.
[0050] Of course, the mapping relationship can be modified by the car owner according to their needs. It should be noted that the car owner's modification authority is limited to the mapping relationship of objects that do not affect the overall driving safety of the vehicle.
[0051] Specifically, the scene task manager in the Android subsystem obtains the result object corresponding to the scene script, and determines the target real-time requirement corresponding to the result object according to the pre-set mapping relationship between the object and the real-time requirement; the target real-time requirement is determined as the real-time requirement of the scene script.
[0052] Step 202: The Android subsystem executes the scene scripts assigned to the Android subsystem through the first scene executor.
[0053] In this step, the first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route.
[0054] Specifically, the execution process of this step can be as follows: the first scene execution engine parses the scene scripts allocated to the Android subsystem to obtain the scene script execution rules; the first rule engine executes the scene scripts according to the scene script execution rules; during the execution of the scene scripts, the first rule engine calls the whole vehicle atomic-level service through the first atomic service route.
[0055] It should be noted that the relevant explanations can be found in the section of the aforementioned Embodiment 1, and will not be repeated here.
[0056] Step 203: The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor.
[0057] In this step, the second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route.
[0058] The specific execution process of this step can be as follows: the second scenario execution engine parses the scenario scripts allocated to the QNX subsystem to obtain the scenario script execution rules; the second rule engine executes the scenario scripts according to the scenario script execution rules; during the execution of the scenario scripts, the second rule engine calls the whole vehicle atomic-level service through the second atomic service route.
[0059] It should be noted that the relevant explanations can be found in the section of the aforementioned Embodiment 1, and will not be repeated here.
[0060] In this embodiment, the system includes a scene task manager and a first scene executor located in the Android subsystem, and a second scene executor located in the QNX subsystem. The scene task manager allocates scene scripts to be executed to either the Android or QNX subsystem via a multi-task collaborative scheduling service linking the Android and QNX subsystems. The first scene executor executes the scene scripts allocated to the Android subsystem, and the second scene executor executes the scene scripts allocated to the QNX subsystem. Therefore, for scene tasks with high real-time requirements, they can be allocated to the QNX subsystem and executed approximately 2 seconds after the entire vehicle is woken up, thus meeting the high real-time requirements of such scene tasks to a certain extent.
[0061] Example 3
[0062] Please see Figure 3 , Figure 3 This is a schematic diagram of a distributed scene script execution device provided in Embodiment 3 of this application. The distributed scene script execution device provided in this embodiment can execute the distributed scene script execution method provided in any embodiment of this application, and possesses the corresponding functional modules and beneficial effects of the execution method. This device can be implemented in software and / or hardware, such as... Figure 3 As shown, the distributed scene script execution device specifically includes: allocation module 301, first execution module 302, and second execution module 303.
[0063] The allocation module is used to allocate the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service after the scene script is generated.
[0064] The first execution module is used by the Android subsystem to execute the scene scripts assigned to the Android subsystem through the first scene executor;
[0065] The second execution module is used by the QNX subsystem to execute the scene scripts assigned to the QNX subsystem through the second scene executor.
[0066] In this embodiment, the system includes a scene task manager and a first scene executor located in the Android subsystem, and a second scene executor located in the QNX subsystem. The scene task manager allocates scene scripts to be executed to either the Android or QNX subsystem via a multi-task collaborative scheduling service linking the Android and QNX subsystems. The first scene executor executes the scene scripts allocated to the Android subsystem, and the second scene executor executes the scene scripts allocated to the QNX subsystem. Therefore, for scene tasks with high real-time requirements, they can be allocated to the QNX subsystem and executed approximately 2 seconds after the entire vehicle is woken up, thus meeting the high real-time requirements of such scene tasks to a certain extent.
[0067] Example 4
[0068] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of this application, as shown below. Figure 4 As shown, the electronic device includes a processor 410, a memory 420, an input device 430, and an output device 440; the number of processors 410 in the electronic device can be one or more. Figure 4 Taking a processor 410 as an example; the processor 410, memory 420, input device 430, and output device 440 in the electronic device can be connected via a bus or other means. Figure 4 Taking the example of a connection between China and Israel via a bus.
[0069] The memory 420, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the distributed scene script execution method in this embodiment (e.g., the allocation module 301, the first execution module 302, and the second execution module 303 in the distributed scene script execution device). The processor 410 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the memory 420, thereby implementing the aforementioned distributed scene script execution method.
[0070] That is, after the scene script is generated, the scene task manager in the Android subsystem allocates the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service.
[0071] The Android subsystem executes the scene scripts assigned to it through the first scene executor.
[0072] The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor.
[0073] Furthermore, the scene task manager in the Android subsystem allocates scene scripts to the Android subsystem or QNX subsystem through a multi-task collaborative scheduling service, including:
[0074] The scene task manager in the Android subsystem obtains the real-time requirements of scene scripts;
[0075] If the real-time requirement exceeds the preset threshold, the scenario script will be allocated to the QNX subsystem through the multi-task collaborative scheduling service.
[0076] If the real-time requirement is less than or equal to a preset threshold, the scenario script will be allocated to the Android subsystem through the multi-task collaborative scheduling service.
[0077] Furthermore, the scene task manager in the Android subsystem obtains the real-time requirements of the scene script, including:
[0078] The scene task manager in the Android subsystem obtains the real-time requirement configured when generating scene scripts;
[0079] or,
[0080] The scene task manager in the Android subsystem obtains the result object corresponding to the scene script and determines the target real-time requirement corresponding to the result object based on the pre-set mapping relationship between the object and the real-time requirement.
[0081] The target real-time requirement is defined as the real-time requirement of the scenario script.
[0082] Furthermore, the first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route;
[0083] The Android subsystem executes the scene scripts assigned to it through the first scene executor, including:
[0084] The first scene execution engine parses the scene scripts assigned to the Android subsystem to obtain the scene script execution rules;
[0085] The first rule engine executes the scene script according to the scene script execution rules;
[0086] During the execution of the scenario script, the first rule engine calls the whole vehicle atomic-level service through the first atomic service route.
[0087] Furthermore, the second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route;
[0088] The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor, including:
[0089] The second scene execution engine parses the scene scripts assigned to the QNX subsystem to obtain the scene script execution rules;
[0090] The second rule engine executes the scene script according to the scene script execution rules;
[0091] During the execution of the scenario script, the second rule engine calls the whole vehicle atomic-level service through the second atomic service route.
[0092] The memory 420 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on terminal usage. Furthermore, the memory 420 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 420 may further include memory remotely located relative to the processor 410, which can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0093] Input device 430 can be used to receive input electrical construction drawings and generate key signal inputs related to user settings and function control of electronic equipment. Output device 440 may include display devices such as a display screen.
[0094] Example 5
[0095] Embodiment 5 of this application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to execute a distributed scenario script execution method, the method comprising:
[0096] After the scene script is generated, the scene task manager in the Android subsystem allocates the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service.
[0097] The Android subsystem executes the scene scripts assigned to it through the first scene executor.
[0098] The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor.
[0099] Furthermore, the scene task manager in the Android subsystem allocates scene scripts to the Android subsystem or QNX subsystem through a multi-task collaborative scheduling service, including:
[0100] The scene task manager in the Android subsystem obtains the real-time requirements of scene scripts;
[0101] If the real-time requirement exceeds the preset threshold, the scenario script will be allocated to the QNX subsystem through the multi-task collaborative scheduling service.
[0102] If the real-time requirement is less than or equal to a preset threshold, the scenario script will be allocated to the Android subsystem through the multi-task collaborative scheduling service.
[0103] Furthermore, the scene task manager in the Android subsystem obtains the real-time requirements of the scene script, including:
[0104] The scene task manager in the Android subsystem obtains the real-time requirement configured when generating scene scripts;
[0105] or,
[0106] The scene task manager in the Android subsystem obtains the result object corresponding to the scene script and determines the target real-time requirement corresponding to the result object based on the pre-set mapping relationship between the object and the real-time requirement.
[0107] The target real-time requirement is defined as the real-time requirement of the scenario script.
[0108] Furthermore, the first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route;
[0109] The Android subsystem executes the scene scripts assigned to it through the first scene executor, including:
[0110] The first scene execution engine parses the scene scripts assigned to the Android subsystem to obtain the scene script execution rules;
[0111] The first rule engine executes the scene script according to the scene script execution rules;
[0112] During the execution of the scenario script, the first rule engine calls the whole vehicle atomic-level service through the first atomic service route.
[0113] Furthermore, the second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route;
[0114] The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor, including:
[0115] The second scene execution engine parses the scene scripts assigned to the QNX subsystem to obtain the scene script execution rules;
[0116] The second rule engine executes the scene script according to the scene script execution rules;
[0117] During the execution of the scenario script, the second rule engine calls the whole vehicle atomic-level service through the second atomic service route.
[0118] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the above-described method operations, but can also execute related operations in the distributed scene script execution method provided in any embodiment of this application.
[0119] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.
[0120] It is worth noting that in the embodiments of the search device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.
[0121] Note that the above description is merely a preferred embodiment and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments. Many other equivalent embodiments may be included without departing from the concept of this application, and the scope of this application is determined by the scope of the appended claims.
Claims
1. A distributed scenario script execution system, characterized in that, The system includes: The scene task manager and the first scene executor are set in the Android subsystem, and the second scene executor is set in the QNX subsystem; The scene task manager allocates the scene scripts to be executed to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service that links the Android subsystem and the QNX subsystem. The first scene executor is used to execute the scene scripts assigned to the Android subsystem, and the second scene executor is used to execute the scene scripts assigned to the QNX subsystem; The first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route; The first scene execution engine is used to parse the scene scripts allocated to the Android subsystem to obtain scene script execution rules; The first rule engine is connected to the first scene execution engine and is used to execute the scene script according to the scene script execution rules; During the execution of the scenario script, the first rule engine is used to invoke the whole vehicle atomic-level service through the first atomic service route; The second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route; The second scene execution engine is used to parse the scene scripts allocated to the QNX subsystem to obtain scene script execution rules; The second rule engine is connected to the second scene execution engine and is used to execute the scene script according to the scene script execution rules; During the execution of the scenario script, the second rule engine is used to invoke the whole vehicle atomic-level service through the second atomic service route.
2. A distributed scenario script execution method, characterized in that, The method includes: After the scene script is generated, the scene task manager in the Android subsystem allocates the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service. The Android subsystem executes the scene scripts allocated to the Android subsystem through the first scene executor; The QNX subsystem executes the scene scripts assigned to the QNX subsystem through the second scene executor; The first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route; The Android subsystem executes the scene scripts allocated to the Android subsystem through the first scene executor, including: The first scene execution engine parses the scene scripts allocated to the Android subsystem to obtain scene script execution rules; The first rule engine executes the scene script according to the scene script execution rules; During the execution of the scenario script, the first rule engine invokes the whole vehicle atomic-level service through the first atomic service route; The second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route; The QNX subsystem executes the scene scripts allocated to the QNX subsystem through the second scene executor, including: The second scene execution engine parses the scene scripts allocated to the QNX subsystem to obtain scene script execution rules; The second rule engine executes the scene script according to the scene script execution rules; During the execution of the scenario script, the second rule engine invokes the whole vehicle atomic-level service through the second atomic service route.
3. The method according to claim 2, characterized in that, The scene task manager in the Android subsystem allocates the scene scripts to the Android subsystem or the QNX subsystem through a multi-task collaborative scheduling service, including: The scene task manager in the Android subsystem obtains the real-time requirement of the scene script; If the real-time requirement exceeds a preset threshold, the scenario script is allocated to the QNX subsystem via the multi-task collaborative scheduling service. If the real-time requirement is less than or equal to the preset threshold, the scenario script is allocated to the Android subsystem through the multi-task collaborative scheduling service.
4. The method according to claim 3, characterized in that, The scene task manager in the Android subsystem obtains the real-time requirement of the scene script, including: The scene task manager in the Android subsystem obtains the real-time requirement configured when generating the scene script; or, The scene task manager in the Android subsystem obtains the result object corresponding to the scene script and determines the target real-time requirement corresponding to the result object according to the pre-set mapping relationship between the object and the real-time requirement. The target real-time requirement is defined as the real-time requirement of the scene script.
5. A distributed scene script execution device, characterized in that, The device includes: The allocation module is used to allocate the scene script to the Android subsystem or the QNX subsystem through the multi-task collaborative scheduling service after the scene script is generated. The first execution module is used by the Android subsystem to execute the scene scripts allocated to the Android subsystem through the first scene executor; The second execution module is used by the QNX subsystem to execute the scene scripts allocated to the QNX subsystem through the second scene executor; The first scenario executor includes a first scenario execution engine, a first rule engine, and a first atomic service route; The Android subsystem executes the scene scripts allocated to the Android subsystem through the first scene executor, including: The first scene execution engine parses the scene scripts allocated to the Android subsystem to obtain scene script execution rules; The first rule engine executes the scene script according to the scene script execution rules; During the execution of the scenario script, the first rule engine invokes the whole vehicle atomic-level service through the first atomic service route; The second scenario executor includes a second scenario execution engine, a second rule engine, and a second atomic service route; The QNX subsystem executes the scene scripts allocated to the QNX subsystem through the second scene executor, including: The second scene execution engine parses the scene scripts allocated to the QNX subsystem to obtain scene script execution rules; The second rule engine executes the scene script according to the scene script execution rules; During the execution of the scenario script, the second rule engine invokes the whole vehicle atomic-level service through the second atomic service route.
6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the distributed scene script execution method as described in any one of claims 2-4.