Deployment method and device of vehicle control scene, medium and electronic equipment

Abstract

The invention discloses a vehicle control scene deployment method and device, a medium and electronic equipment, and the method comprises the steps: obtaining the deployment demand information of a candidate control scene if a scene deployment instruction of a target user is received, and enabling the candidate control scene to comprise a candidate instruction group and a candidate triggering condition of the candidate instruction group, the deployment demand information comprises execution hardware configuration and execution software support required for executing the candidate control scene; based on the deployment demand information and function configuration information of the target vehicle, a target instruction group allowed to be deployed in the target vehicle is determined from the candidate control scene, and the function configuration information comprises actual hardware configuration and actual software support of the target vehicle; and deploying the target control scene in the target vehicle based on the target instruction group and the candidate trigger condition. Through the technical scheme provided by the invention, the deployment efficiency of the vehicle control scene can be improved.

Description

Technical Field

[0001] This application belongs to the field of vehicle control technology, and in particular relates to a deployment method, device, medium and electronic equipment for vehicle control scenarios. Background Technology

[0002] Current intelligent vehicle systems allow users to customize various control scenarios (such as driving modes and entertainment modes), but the control commands and triggering conditions in each control scenario need to be manually bound and deployed in the vehicle by the user. In other words, the control scenarios that a user can use depend on their logic programming capabilities. For users with weak logic programming capabilities, the control scenarios they can use are relatively limited, resulting in reduced deployment efficiency of vehicle control scenarios.

[0003] Therefore, the low deployment efficiency of vehicle control scenarios is a technical problem that urgently needs to be solved. Summary of the Invention

[0004] The embodiments of this application provide a method, apparatus, medium, and electronic device for deploying vehicle control scenarios, which can at least improve the deployment efficiency of vehicle control scenarios to a certain extent.

[0005] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0006] According to a first aspect of the embodiments of this application, a method for deploying a vehicle control scenario is provided. At least one user-added control scenario is displayed in a multi-source scenario library. The control scenario includes a control command group for a vehicle corresponding to the user and triggering conditions for the control command group. The control command group includes at least one control command. The method is applied to a target vehicle and includes:

[0007] If a scenario deployment instruction from a target user is received, deployment requirement information for candidate control scenarios is obtained. The candidate control scenarios include candidate instruction groups and candidate triggering conditions for the candidate instruction groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenarios.

[0008] Based on the deployment requirement information and the functional configuration information of the target vehicle, a target instruction group that can be deployed in the target vehicle is determined from the candidate control scenarios, wherein the functional configuration information includes the actual hardware configuration and actual software support of the target vehicle;

[0009] Based on the target instruction group and the candidate triggering conditions, a target control scenario is deployed in the target vehicle.

[0010] In some embodiments of this application, based on the foregoing scheme, determining the target instruction group that can be deployed in the target vehicle from the candidate control scenarios based on the deployment requirement information and the functional configuration information of the target vehicle includes: obtaining the functional configuration information of the target vehicle; determining whether the target vehicle is allowed to execute the candidate triggering condition based on the functional configuration information; if the target vehicle is allowed to execute the candidate triggering condition, determining the target instruction group from the candidate instruction group based on the functional configuration information.

[0011] In some embodiments of this application, based on the foregoing scheme, determining the target instruction group from the candidate instruction group based on the functional configuration information includes: extracting instruction requirement information corresponding to each candidate control instruction from the deployment requirement information, wherein the candidate instruction group includes at least one candidate control instruction, and the instruction requirement information includes instruction hardware configuration and instruction software support required to execute the candidate control instruction; extracting the candidate control instructions whose instruction requirement information is supported by the functional configuration information from the candidate instruction group as target control instructions to obtain the target instruction group, wherein the target instruction group includes at least one target control instruction.

[0012] In some embodiments of this application, based on the foregoing scheme, the step of extracting the candidate control instruction from the candidate instruction group that supports the instruction requirement information of the function configuration information as the target control instruction includes: for each candidate control instruction, determining whether the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and determining whether the actual software support supports the instruction software support of the candidate control instruction; if the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and the actual software support supports the instruction software support of the candidate control instruction, the candidate control instruction is determined as the target control instruction.

[0013] In some embodiments of this application, based on the foregoing scheme, the step of deploying the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions includes: logically binding the target control instructions with the candidate triggering conditions to generate an executable scenario logic tree; compiling the scenario logic tree into a target control protocol recognizable by the vehicle's in-vehicle system; and deploying the target control scenario in the in-vehicle system based on the target control protocol.

[0014] In some embodiments of this application, based on the foregoing scheme, the multi-source scenario library is updated in the following manner: if a scenario addition instruction from a reference user is received, the reference instruction group to be executed by the reference vehicle already added by the reference user and the reference triggering conditions of the reference instruction group are obtained; based on the reference configuration information of the reference vehicle, it is determined whether the deployment of the reference instruction group and the reference triggering conditions of the reference instruction group in the reference vehicle is permitted; if the deployment of the reference instruction group and the reference triggering conditions of the reference instruction group in the reference vehicle is permitted, a reference control scenario is generated based on the reference instruction group and the reference triggering conditions; and the reference control scenario is added to the multi-source scenario library.

[0015] In some embodiments of this application, based on the foregoing scheme, determining whether to allow the deployment of the reference instruction group and the reference triggering condition of the reference instruction group in the reference vehicle based on the reference configuration information of the reference vehicle includes: obtaining the reference hardware configuration and reference software support of the reference vehicle as the reference configuration information; determining whether the reference vehicle is allowed to execute the reference triggering condition based on the reference configuration information, and determining whether the reference vehicle is allowed to execute the reference instruction group based on the reference configuration information; if the reference vehicle is allowed to execute the reference triggering condition, and the reference vehicle is allowed to execute the reference instruction group, determining whether to allow the deployment of the reference instruction group and the reference triggering condition of the reference instruction group in the reference vehicle.

[0016] According to a second aspect of the embodiments of this application, a vehicle control scenario deployment device is provided, wherein at least one user-added control scenario is displayed in a multi-source scenario library, the control scenario includes a control command group for a vehicle corresponding to the user and triggering conditions for the control command group, the control command group includes at least one control command, the device is applied to a target vehicle, and the device includes:

[0017] The first acquisition module is used to acquire deployment requirement information of candidate control scenarios if a scenario deployment instruction is received from a target user. The candidate control scenarios include candidate instruction groups and candidate triggering conditions of the candidate instruction groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenarios.

[0018] The first determining module is used to determine, based on the deployment requirement information and the functional configuration information of the target vehicle, a target instruction group that can be deployed in the target vehicle from the candidate control scenarios, wherein the functional configuration information includes the actual hardware configuration and actual software support of the target vehicle;

[0019] The deployment module is used to deploy the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions.

[0020] According to a third aspect of the embodiments of this application, a computer-readable storage medium is provided, the computer-readable storage medium storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by a processor to perform the operation as described in any of the first aspects above.

[0021] According to a fourth aspect of the present application, an electronic device is provided, the electronic device including one or more processors and one or more memories, the one or more memories storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by the one or more processors to implement the method described in any of the embodiments of the first aspect above.

[0022] In this application, a multi-source scenario library demonstrates at least one user-added control scenario. Each control scenario includes a control command group for the user's corresponding vehicle and triggering conditions for that control command group. Each control command group includes at least one control command. If a scenario deployment command from a target user is received, deployment requirement information for candidate control scenarios is obtained. Candidate control scenarios include candidate command groups and candidate triggering conditions for those candidate command groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenarios. Based on the deployment requirement information and the target vehicle's functional configuration information, a target command group that can be deployed in the target vehicle is determined from the candidate control scenarios. The functional configuration information includes the target vehicle's actual hardware configuration and actual software support. The target control scenario is then deployed in the target vehicle based on the target command group and the candidate triggering conditions. In other words, the multi-source scenario library allows the deployment of control scenarios added by other users in the target user's target vehicle, reducing the limitations of the target user's own logic orchestration capabilities and thus improving the deployment efficiency of vehicle control scenarios.

[0023] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0024] 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. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0025] Figure 1A flowchart illustrating the deployment method of the vehicle control scenario in an embodiment of this application is shown;

[0026] Figure 2 A schematic diagram illustrating the actual triggering conditions of the sub-table in an embodiment of this application is shown;

[0027] Figure 3 This illustration shows the actual control instructions for the sub-table in an embodiment of this application. Figure 1 ;

[0028] Figure 4 This illustration shows the actual control instructions for the sub-table in an embodiment of this application. Figure 2 ;

[0029] Figure 5 This illustration shows a scenario in an embodiment of this application where the candidate control scenario is completely unavailable.

[0030] Figure 6 This illustration shows a schematic diagram in which a portion of the candidate control scenario is unavailable in an embodiment of this application;

[0031] Figure 7 A schematic diagram showing that the candidate control scenarios in the embodiments of this application are fully available is shown;

[0032] Figure 8 A schematic diagram of a publication reference control scenario in an embodiment of this application is shown;

[0033] Figure 9 A diagram illustrating the deployment process of a vehicle control scenario in an embodiment of this application is shown.

[0034] Figure 10 A block diagram of a deployment device for a vehicle control scenario in an embodiment of this application is shown;

[0035] Figure 11 A schematic diagram of the structure of an electronic device in an embodiment of this application is shown. Detailed Implementation

[0036] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0037] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0038] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0039] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily need to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0040] It should be noted that "multiple" in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0041] It should also be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such uses of these terms 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.

[0042] Figure 1 A flowchart illustrating a vehicle control scenario deployment method according to an embodiment of this application is shown. At least one user-added control scenario is displayed in a multi-source scenario library. Each control scenario includes a control command group for the user's corresponding vehicle and triggering conditions for the control command group. The control command group includes at least one control command. The method is applied to the target vehicle. This vehicle control scenario deployment method can be executed by a device with computing processing capabilities. (Refer to...) Figure 1 As shown, the deployment method for this vehicle control scenario includes:

[0043] Step 101: If a scenario deployment instruction from the target user is received, obtain the deployment requirement information of the candidate control scenario, wherein the candidate control scenario includes a candidate instruction group and the candidate triggering conditions of the candidate instruction group, and the deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenario;

[0044] Step 102: Based on the deployment requirement information and the functional configuration information of the target vehicle, determine the target instruction group that can be deployed in the target vehicle from the candidate control scenarios, wherein the functional configuration information includes the actual hardware configuration and actual software support of the target vehicle;

[0045] Step 103: Deploy the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions.

[0046] Through the above steps, the multi-source scenario library displays at least one user-added control scenario. Each control scenario includes a control command group for the user's corresponding vehicle and the triggering conditions for that control command group. Each control command group includes at least one control command. If a scenario deployment command from a target user is received, deployment requirement information for candidate control scenarios is obtained. Candidate control scenarios include candidate command groups and candidate triggering conditions for those candidate command groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenario. Based on the deployment requirement information and the target vehicle's functional configuration information, a target command group that can be deployed in the target vehicle is determined from the candidate control scenarios. The functional configuration information includes the target vehicle's actual hardware configuration and actual software support. The target control scenario is then deployed in the target vehicle based on the target command group and the candidate triggering conditions. In other words, the multi-source scenario library allows the deployment of control scenarios added by other users in the target user's target vehicle, reducing the limitations of the target user's own logic orchestration capabilities and thus improving the deployment efficiency of vehicle control scenarios.

[0047] Optionally, in this embodiment, a database or platform for centrally storing and managing multiple vehicle control scenarios can be used as the aforementioned multi-source scenario library, but is not limited to. The multi-source scenario library includes control scenarios from multiple sources, such as user-defined scenarios, officially provided standard scenarios (e.g., driving modes, entertainment modes), and scenarios shared by other users (added to the scenario library after approval). The aforementioned user-defined scenarios can be, but are not limited to, control scenarios created and published by users through a web application, mobile app, or vehicle app.

[0048] Optionally, in this embodiment, the aforementioned multi-source scene library may, but is not limited to, storing control scenes in structured formats such as JSON (JavaScript Object Notation). This multi-source scene library provides users with a rich selection of scenes, avoids redundant configuration, and forms a scene ecosystem through a sharing mechanism.

[0049] Optionally, in this embodiment, the aforementioned control scenario is a set of predefined vehicle behavior logic, consisting of trigger conditions and a control command group. When a specific condition (i.e., the trigger condition) is met, the vehicle automatically executes the associated control command group. For example, in rain mode, upon detecting a rain sensor signal (trigger condition), the vehicle automatically closes the windows and turns on the fog lights (control command group). This control scenario enables intelligent and automated control of vehicle functions, enhancing the user experience.

[0050] Optionally, in this embodiment, the aforementioned control instruction group is a collection of all operations to be executed in a control scenario, composed of multiple control instructions arranged in a logical order. Each control instruction in the control instruction group corresponds to a specific vehicle operation, such as turning on the seat heating. The control instruction group can sort multiple control instructions according to priority or dependency, for example, adjusting the seat first and then playing music.

[0051] Optionally, in this embodiment, the aforementioned triggering conditions are prerequisites for the execution of the control scenario, typically a logical combination of vehicle status or environmental signals. These can be a single logical element of the vehicle status or environmental signal, such as: vehicle speed > 100 km / h, gear in D (Drive) mode, rain sensor detecting heavy rain, GPS (Global Positioning System) positioning on a highway, or voice command "Activate Sport Mode," etc. Alternatively, they can be a logical combination of vehicle status or environmental signals, such as: driver's seatbelt not fastened AND vehicle speed > 30 km / h, etc.

[0052] Optionally, in this embodiment, the control command is the smallest execution unit in the control command group, corresponding to a specific vehicle function operation. The control command needs to explicitly specify the required hardware configuration (e.g., seat motor) and software support (e.g., in-vehicle voice SDK (Software Development Kit)), and may also include, but is not limited to, dynamic parameters (e.g., setting the air conditioning temperature to 24°C).

[0053] Optionally, in this embodiment, the target vehicle is a specific vehicle instance of the control scenario to be deployed.

[0054] Optionally, in this embodiment, taking the control scenario A added by user A and the control scenario B added by user B from the aforementioned multi-source scenario library as examples, the explanation is as follows: The trigger condition for control scenario A is: vehicle speed > 100km / h AND gear = D gear; the control command group for control scenario A includes: switching the driving mode to sport mode, lowering the suspension, and turning on the exhaust sound. The trigger condition for control scenario B is: rain sensor = heavy rain; the control command group for control scenario B includes: closing the sunroof, turning on the fog lights, and adjusting the air conditioning dehumidification.

[0055] The method proposed in this application, based on relevant custom control scenarios, adds a multi-source scenario library to the vehicle-side app. This library allows users to select control scenarios published by other users or official control scenarios. All control scenarios in the multi-source scenario library support preview, trial run, and addition functions. Furthermore, considering vehicle model and version compatibility, a vehicle-control scenario compatibility check is added. In addition to supporting user-defined orchestration, the method proposed in this application frees up users' time, eliminating the need to orchestrate frequently used scenarios. It allows different users' vehicles to add control scenarios from the multi-source scenario library. The triggering process of the control scenarios deployed on the vehicle is both accurate and stable, greatly enhancing the user experience.

[0056] In the embodiment provided in step 101, the target user is the user who requests the deployment of candidate control scenarios to the target vehicle. The target user can, but is not limited to, associate the target vehicle with a vehicle account to obtain control of the target vehicle and thus deploy the candidate control scenarios to the target vehicle.

[0057] Optionally, in this embodiment, the aforementioned scenario deployment command is initiated by the target user, requesting the deployment of candidate control scenarios from the multi-source scenario library to the target vehicle. The scenario deployment command can be triggered in various ways, including but not limited to: the target user selecting a candidate control scenario via the vehicle's infotainment system / mobile app and clicking the "Add Scenario" button; or the target user triggering the scenario deployment command via voice commands such as "Install Rain Mode (Candidate Control Scenario)".

[0058] Optionally, in this embodiment, the aforementioned candidate control scenarios are control scenarios selected by the target user from a multi-source scenario library and to be deployed to the target vehicle. These can be scenarios shared by other users, officially recommended, or provided by a third party, such as the "camping mode" scenario selected by the target user from the multi-source scenario library.

[0059] Optionally, in this embodiment, the above deployment requirement information is a list of software / hardware conditions required for the normal operation of the candidate control scenario. It may include, but is not limited to, execution hardware configuration, i.e., the vehicle hardware that the scenario depends on (e.g., a seat massage module is required), and execution software support, i.e., the software functions that the scenario depends on (e.g., an in-vehicle system ≥ v3.2 is required).

[0060] Optionally, in this embodiment, the aforementioned candidate instruction group is a collection of all control instructions included in the candidate control scenario.

[0061] Optionally, in this embodiment, the above-mentioned candidate triggering conditions are the original triggering condition logic defined in the candidate control scenario.

[0062] Optionally, in this embodiment, the aforementioned execution hardware configuration is a list of vehicle hardware devices necessary for running each candidate control command and candidate triggering condition included in the candidate control scenario. It may include, but is not limited to, execution hardware (e.g., seat motor, window controller, air conditioning compressor, etc.) and sensing hardware (e.g., vehicle speed sensor, temperature sensor, camera, etc.).

[0063] Optionally, in this embodiment, the aforementioned execution software support refers to the software functions or interfaces necessary for running each candidate control instruction and candidate triggering condition included in the candidate control scenario. This may include, but is not limited to, vehicle system version requirements, specific API (Application Programming Interface) support, software function switches, etc.

[0064] In the embodiment provided in step 102, the aforementioned functional configuration information is a complete list describing the actual software / hardware capabilities of the target vehicle. It includes the actual hardware configuration indicating the list of physical devices installed in the vehicle, and the actual software support indicating the list of software functions integrated into the vehicle system. This functional configuration information can be obtained in various ways, including, but not limited to, self-testing during vehicle system startup, querying from the manufacturer's database using the vehicle's VIN (Vehicle Identification Number), and dynamic updates after OTA (Over-the-Air Technology) upgrades.

[0065] Optionally, in this embodiment, the target instruction group is a subset of valid instructions that can ultimately be executed on the target vehicle after adaptation checks.

[0066] Optionally, in this embodiment, the aforementioned actual hardware configuration refers to the physical devices and performance parameters actually installed in the target vehicle. This may include, but is not limited to, actuators (e.g., window motors, seat adjustment modules), sensors (e.g., rain sensors, PM2.5 detectors), and computing platforms (e.g., autonomous driving chip computing power).

[0067] Optionally, in this embodiment, the aforementioned actual software support refers to the functional interfaces provided by the target vehicle's operating system and applications. This may include, but is not limited to, system version, service modules (e.g., whether a voice assistant or navigation engine is pre-installed), and permission configurations (e.g., allowing third-party scenario control of the chassis system).

[0068] In one embodiment of this application, a target instruction group that can be deployed in the target vehicle can be determined from the candidate control scenarios based on the deployment requirement information and the functional configuration information of the target vehicle in the following manner, but not limited to: obtaining the functional configuration information of the target vehicle; determining whether the target vehicle is allowed to execute the candidate triggering condition based on the functional configuration information; if the target vehicle is allowed to execute the candidate triggering condition, determining the target instruction group from the candidate instruction group based on the functional configuration information.

[0069] Optionally, in this embodiment, whether the target vehicle is allowed to execute the candidate triggering condition can be determined based on the functional configuration information in the following ways, but not limited to: obtaining the triggering hardware configuration and triggering software support required to execute the candidate triggering condition; determining whether the actual hardware configuration supports the triggering hardware configuration, and determining whether the actual software support supports the triggering software support; if the actual hardware configuration supports the triggering hardware configuration, and the actual software support supports the triggering software support, then the target vehicle is allowed to execute the candidate triggering condition.

[0070] In one embodiment of this application, the target instruction group can be determined from the candidate instruction group based on the functional configuration information in the following manner, but not limited to: extracting instruction requirement information corresponding to each candidate control instruction from the deployment requirement information, wherein the candidate instruction group includes at least one candidate control instruction, and the instruction requirement information includes instruction hardware configuration and instruction software support required to execute the candidate control instruction; extracting the candidate control instructions whose instruction requirement information is supported by the functional configuration information from the candidate instruction group as target control instructions to obtain the target instruction group, wherein the target instruction group includes at least one target control instruction.

[0071] In one embodiment of this application, candidate control instructions that support the instruction requirement information of the function configuration information can be extracted from the candidate instruction group as target control instructions in the following manner, but not limited to: for each candidate control instruction, determining whether the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and determining whether the actual software support supports the instruction software support of the candidate control instruction; if the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and the actual software support supports the instruction software support of the candidate control instruction, the candidate control instruction is determined as the target control instruction.

[0072] Optionally, in this embodiment, the basic capabilities can be determined according to the vehicle model version, and then modified based on the vehicle's optional equipment, firmware version, etc., to obtain the actual capabilities. Specifically, an initial capability table for the corresponding vehicle model version is built into the vehicle. Then, based on the vehicle's subsequent optional equipment, firmware version, etc., operations such as adding / deleting / querying / modifying are performed on the initial capability table to obtain the vehicle's actual capability table. The actual capability table includes two sub-tables: actual triggering conditions and actual control commands. The actual capability table is obtained as the functional configuration information of the target vehicle.

[0073] Whether the actual hardware configuration supports the triggering hardware configuration can be determined, but is not limited to, by the following methods:

[0074] Search for the first hardware field that triggers the hardware configuration in the actual trigger conditions of the sub-table; if the first hardware field is found, extract the first field attribute corresponding to the first hardware field; if the first field attribute is "supported", determine that the actual hardware configuration supports triggering the hardware configuration; if the first field attribute is "not supported", or if the first hardware field does not exist in the actual trigger conditions of the sub-table, determine that the actual hardware configuration does not support triggering the hardware configuration.

[0075] Whether the actual software support supports the triggering software support can be determined, but is not limited to, by the following methods:

[0076] Search for the first software field that triggers software support in the actual triggering conditions of the sub-table; if the first software field is found, extract the second field attribute corresponding to the first software field; if the second field attribute is "support", determine that the actual software supports the triggering software support; if the second field attribute is "non-support", or if the first software field does not exist in the actual software support of the sub-table, determine that the actual software does not support the triggering software support.

[0077] It should be noted that, but not limited to, the same sub-table can be used to record hardware and software fields based on the actual trigger conditions. Alternatively, the actual trigger conditions in the sub-table can be further split into two sub-tables to record hardware and software fields respectively.

[0078] Furthermore, in the process of determining whether the target vehicle is allowed to execute the candidate triggering conditions based on the functional configuration information, the candidate triggering conditions can be simply triggering software support, such as: if the vehicle speed is detected to be greater than or equal to 30km / h, start the voice broadcast "the vehicle speed has exceeded 30km / h"; or, the candidate triggering conditions can be simply triggering hardware configuration, such as: if there is a change in the vehicle hardware, start the voice broadcast "the hardware has changed", etc.

[0079] Whether the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction can be determined, but is not limited to, by the following methods:

[0080] Search for the second hardware field of the instruction hardware configuration in the actual control instructions in the sub-table; if the second hardware field is found, extract the third field attribute corresponding to the second hardware field; if the third field attribute is "supported", determine that the actual hardware configuration supports the instruction hardware configuration; if the third field attribute is "not supported", or if the second hardware field does not exist in the actual control instructions in the sub-table, determine that the actual hardware configuration does not support the instruction hardware configuration.

[0081] Whether the actual software supports the instruction software support of the candidate control instruction can be determined, but is not limited to, by the following methods:

[0082] Search for the second software field supported by the instruction software in the actual control instructions in the sub-table; if the second software field is found, extract the fourth field attribute corresponding to the second software field; if the fourth field attribute is "supported", determine that the actual software supports the instruction software support; if the fourth field attribute is "not supported", or if the second software field does not exist in the actual control instructions in the sub-table, determine that the actual software does not support the instruction software support.

[0083] It should be noted that, but not limited to, the same sub-table can be used to record hardware and software fields in the actual control instructions. Alternatively, the actual control instructions in the sub-table can be further split into two sub-tables to record hardware and software fields respectively.

[0084] Optionally, in this embodiment, Figure 2 This illustration shows a schematic diagram of the actual triggering conditions of the sub-table in an embodiment of this application, such as... Figure 2 As shown, the actual triggering conditions that the target vehicle is allowed to achieve include:

[0085] The first skill (ID: 0xf912, Name: When Boarding) is a state-conditional skill used to detect passenger boarding actions. Its function description is "When Boarding %d" (dynamic parameter format). It specifies the monitoring area through the Int32_t type parameter currentArea (default value: 2 / passenger seat), and the parameter uses the radiolistvel enumeration to limit the value: 1 (driver's seat), 2 (passenger seat), 3 (rear left), 4 (rear right). When the system detects that the door in the specified area (such as the passenger seat) is open and the seat pressure sensor is triggered, the skill will be activated and the area code will be filled into the descriptor (such as "When Boarding 2").

[0086] The second skill (ID: 0xf806, Name: Occupant Seatbelt) belongs to the Status Monitoring class (Type: TriggerCondition). It is a trigger condition skill used to monitor the seatbelt status in different seat areas of a vehicle. Its function description is "Occupant Seatbelt %d%d" (dynamic parameter format). It requires an Int32_t parameter vehicleArea (default value: 1). This parameter is limited to an enumerated range of values ​​using radiolistvel: 1 (driver's seat), 2 (passenger's seat), 3 (rear left), 4 (rear right), to precisely specify which seat's seatbelt status (e.g., fastened / unfastened) needs to be detected. When the target seat's seatbelt status changes, the skill is triggered, and the area code and status value are filled into the placeholders in the descriptor (e.g., occupant seatbelt 1 0 indicates the driver's seatbelt is not fastened).

[0087] The third skill (ID: 0xf90b, Name: Occupant Age) is a trigger condition skill used for intelligently identifying the age grouping of occupants in the vehicle. It is described using a dynamic parameter format of "Occupant Age %d%d". It specifies the age category through the Int32_t parameter ageType (default value: 1), which is limited to: 1 (elderly), 2 (adult), and 3 (child) using the radiolistvel single-choice enumeration method. When the vehicle vision system or weight sensor detects a change in the occupant's age group (such as a child sitting in the seat), this skill will be triggered and the age code and confidence level will be filled into the descriptor (e.g., "Occupant Age 3 85" indicates that a child has been identified with a confidence level of 85%).

[0088] Optionally, in this embodiment, Figure 3 This illustration shows the actual control instructions for the sub-table in an embodiment of this application. Figure 1 ,like Figure 3 As shown, configuring the attribute 2 in the SHOWTYPE column of the table represents the product being removed from the shelves.

[0089] further, Figure 4 This illustration shows the actual control instructions for the sub-table in an embodiment of this application. Figure 2 ,like Figure 4 As shown, for equipment that is optional on a particular vehicle model, a configuration word option can be added to the CONFIGINFO field of the actual control command in the sub-table.

[0090] Optionally, in this embodiment, after configuring the actual capability table, the actual capability table can be imported into the cloud capability service and stored in the cloud database. When the target vehicle starts, a list is obtained via HTTP (Hypertext Transfer Protocol). <skill>The capability data contains capabilities with SHOWTYPE equal to 2. The vehicle then uses the CONFIGINFO configuration word to determine whether this capability is supported in the current vehicle model. If the vehicle does not support it, it will mark the capability with SHOWTYPE equal to 3.

[0091] In the embodiment provided in step 103, before deploying the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions, the following methods may also be included, but are not limited to: virtually executing the target instruction group and the candidate triggering conditions; monitoring the response of the target instruction group and the candidate triggering conditions; if there is an abnormal response in the target instruction group or the candidate triggering conditions, outputting an error log and suspending the deployment.

[0092] Optionally, in this embodiment, the target user can trigger the scenario deployment instruction by clicking the trial run button of the candidate control scenario, and after determining the target instruction group, simulate the completion of the target instruction group and candidate trigger conditions on the target vehicle.

[0093] Optionally, in this embodiment, the target instruction group and candidate triggering conditions can be extracted from the multi-source scene library in the following ways, but not limited to: using an HTTP request to access the scene file path. If the request fails, the vehicle will receive an error message and display a failure message. If the path access is successful, the cloud will return a file stream. The InputStreamReader in Java will be used to read the content of the file stream and return a String. The JSONParser in Java will be used to parse the string content. If the parsing fails, a failure message will be returned. If the parsing succeeds, JSON content will be returned.

[0094] Furthermore, a preview model can be defined in Java, including: PreviewScenarioModel{

[0095] / / Basic scene information

[0096] private scenario;

[0097] / / Enable this scenario?

[0098] private boolean enable;

[0099] / / Is this a complex scenario (containing nested logic)?

[0100] private boolean isComplex;

[0101] / / List of triggering conditions (collection of Skill objects)

[0102] private List <skill>triggerConditionList=new ArrayList<>();

[0103] / / Logical expression for triggering condition (default "And")

[0104] private String triggerExpression="And";

[0105] / / Action list (collection of Skill objects)

[0106] private List <skill>actionList=new ArrayList<>();

[0107] / / List of complex subtasks (for nested scenarios)

[0108] private List <scenariotaskmodel>complexModelList=new ArrayList<>();

[0109] }

[0110] Extract the conditions from the JSON using the preview model described above, and compare them with the List. <skill>Perform ID matching loop, retrieve Skill condition data, store the condition capabilities in triggerConditionList, and extract the actions and List from the sequence in the JSON. <skill>Perform ID loop matching, retrieve Skill action data, store action capabilities in actionList, until the completed target instruction group (actionList) is obtained.

[0111] Optionally, in this embodiment, the target instruction group and candidate triggering conditions can be virtually executed in the target vehicle in the following ways, but not limited to: In a multi-source scenario library, a dialog is popped up in Android; the data is read from the entity class PreviewScenarioModel and rendered via XML. When displaying capabilities, the SHOWTYPE field is checked to indicate unavailability.

[0112] Taking the candidate control scenario, which includes candidate trigger conditions such as detecting a passenger getting into the vehicle, and candidate command groups such as a voice announcement of "Please fasten your seatbelt" and turning on the air conditioning in the passenger seat, as an example, the explanation is as follows:

[0113] Figure 5 This illustration shows a scenario where the candidate control scenario is completely unavailable in an embodiment of this application, such as... Figure 5 As shown, if the candidate triggering condition is unavailable, the candidate control scenario is determined to be completely unavailable; or, if the candidate triggering condition is available, but the voice prompt "Please fasten your seatbelt" and the air conditioning in the passenger seat are both unavailable, the candidate control scenario is determined to be completely unavailable.

[0114] Figure 6 This illustration shows a schematic diagram in which a portion of the candidate control scenario is unavailable in an embodiment of this application, such as... Figure 6 As shown, if the candidate triggering conditions are available, but the voice prompt "Please fasten your seat belt" or the air conditioning in the passenger seat is not available, it is determined that part of the candidate control scenario is unavailable, and the available candidate control commands are grouped into a target command group.

[0115] Figure 7 A schematic diagram showing the complete availability of candidate control scenarios in the embodiments of this application is illustrated, such as... Figure 7 As shown, if the candidate triggering conditions, the voice broadcast "Please fasten your seat belt", and the air conditioning in the passenger seat are all available, the candidate control scenario is determined to be fully available, and all candidate control commands are combined into a target command group.

[0116] In one embodiment of this application, a target control scenario can be deployed in the target vehicle based on the target instruction group and the candidate triggering conditions in the following manner, but not limited to: logically binding the target control instructions with the candidate triggering conditions to generate an executable scenario logic tree; compiling the scenario logic tree into a target control protocol recognizable by the vehicle's in-vehicle system; and deploying the target control scenario in the in-vehicle system based on the target control protocol.

[0117] In one embodiment of this application, the multi-source scenario library may be updated, but is not limited to, in the following manner: if a scenario addition instruction from a reference user is received, the reference instruction group to be executed by the reference vehicle already added by the reference user and the reference triggering conditions of the reference instruction group are obtained; based on the reference configuration information of the reference vehicle, it is determined whether the deployment of the reference instruction group and the reference triggering conditions of the reference instruction group in the reference vehicle is permitted; if the deployment of the reference instruction group and the reference triggering conditions of the reference instruction group in the reference vehicle is permitted, a reference control scenario is generated based on the reference instruction group and the reference triggering conditions; and the reference control scenario is added to the multi-source scenario library.

[0118] In one embodiment of this application, whether the deployment of the reference instruction group and the reference triggering condition of the reference instruction group in the reference vehicle is permitted can be determined based on the reference configuration information of the reference vehicle in the following manner, but not limited to: obtaining the reference hardware configuration and reference software support of the reference vehicle as the reference configuration information; determining whether the reference vehicle is permitted to execute the reference triggering condition based on the reference configuration information, and determining whether the reference vehicle is permitted to execute the reference instruction group based on the reference configuration information; if the reference vehicle is permitted to execute the reference triggering condition, and the reference vehicle is permitted to execute the reference instruction group, determining whether the deployment of the reference instruction group and the reference triggering condition of the reference instruction group in the reference vehicle is permitted.

[0119] Optionally, in this embodiment, the reference user can orchestrate scenarios through a combination of web, mobile app, and vehicle-side application, and then publish them to the web. Figure 8 A schematic diagram of a publication reference control scenario in an embodiment of this application is shown, such as... Figure 8 As shown, click the + button to add trigger conditions, and add actions below the execution button. After the user has finished choreographing the scene, they can publish the scene through the publish button on the interface. When publishing, the current scene will be converted into JSON content.

[0120] By converting the scene data into JSON structure, it becomes a code description and becomes input that can be read by the Java program. Then, the program reads the JSON content through read / write streams (I / O streams), writes it to a file, and then uploads the file to the web file server through the HTTPS communication protocol.

[0121] On the web side, a database query allows users to view all user-posted scenarios. Furthermore, an approval mechanism can be added to review user-posted scenarios before adding them to a multi-source scenario library. After reviewers assess the applicability and stability of a scenario, it is approved and added to the multi-source scenario library for display to other users.

[0122] On the multi-source scene library side, the Android Retrofit framework is used to request access to the cloud interface using the OkHttpClient protocol. Observable is used to receive the list data of recommended scenes, and the data is converted into Java objects Model using the Gson framework. Android RecyclerView is used to traverse and populate the Model, and the page is rendered into XML for display.

[0123] To enable those skilled in the art to better understand the deployment methods for the aforementioned vehicle control scenarios, the following will combine... Figure 9 To explain, Figure 9 The diagram illustrates the deployment process of a vehicle control scenario in an embodiment of this application. Figure 9 As shown, when the target user selects a candidate control scenario, the deployment requirement information of the candidate control scenario is obtained from the cloud of the multi-source scenario library; if the deployment requirement information is obtained, the functional configuration information of the target vehicle is obtained from the cloud of the target vehicle; based on the deployment requirement information and the functional configuration information, the target control scenario is deployed in the target vehicle.

[0124] The technical solution proposed in this application achieves the following effects by constructing a standardized process for scene creation, review, adaptation checking, and deployment:

[0125] 1) User-friendliness: Ordinary users can quickly access verified high-quality scenarios through the recommendation square without professional technical knowledge, significantly reducing the barrier to entry;

[0126] 2) Cross-vehicle compatibility: Through triple protection of hardware configuration table, software version verification and dynamic downgrade strategy, it ensures safe and stable operation on different vehicle configurations in the same scenario;

[0127] 3) Sustainability: User-created scenarios, after being reviewed, feed back into the scenario library, forming a positive cycle of "creation-sharing-optimization" and continuously enriching the functional ecosystem of the smart cockpit.

[0128] The following describes an embodiment of the apparatus described in this application, which can be used to execute the deployment method for the vehicle control scenario in the above embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the deployment method for the vehicle control scenario described above.

[0129] See Figure 10 The diagram shows a block diagram of a deployment device for a vehicle control scenario in an embodiment of this application.

[0130] like Figure 10 As shown, the vehicle control scenario deployment device (1000) according to an embodiment of this application displays at least one user-added control scenario in a multi-source scenario library. The control scenario includes a control command group for the user's vehicle and triggering conditions for the control command group. The control command group includes at least one control command. The device is applied to a target vehicle and includes:

[0131] The system comprises a first acquisition module 1001, a first determination module 1002, and a deployment module 1003.

[0132] The first acquisition module is used to acquire deployment requirement information of candidate control scenarios if a scenario deployment instruction is received from a target user. The candidate control scenarios include candidate instruction groups and candidate triggering conditions of the candidate instruction groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenarios.

[0133] The first determining module is used to determine, based on the deployment requirement information and the functional configuration information of the target vehicle, a target instruction group that can be deployed in the target vehicle from the candidate control scenarios, wherein the functional configuration information includes the actual hardware configuration and actual software support of the target vehicle;

[0134] The deployment module is used to deploy the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions.

[0135] In some embodiments of this application, based on the foregoing scheme, the first determining module includes:

[0136] The first acquisition unit is used to acquire the functional configuration information of the target vehicle;

[0137] The first determining unit is configured to determine, based on the functional configuration information, whether the target vehicle is permitted to execute the candidate triggering condition;

[0138] The second determining unit is configured to determine the target instruction group from the candidate instruction group based on the function configuration information if the target vehicle allows the execution of the candidate triggering conditions.

[0139] In some embodiments of this application, based on the foregoing scheme, the second determining unit is further configured to: extract instruction requirement information corresponding to each candidate control instruction from the deployment requirement information, wherein the candidate instruction group includes at least one candidate control instruction, and the instruction requirement information includes instruction hardware configuration and instruction software support required to execute the candidate control instruction; extract the candidate control instructions supported by the instruction requirement information in the function configuration information from the candidate instruction group as target control instructions to obtain the target instruction group, wherein the target instruction group includes at least one target control instruction.

[0140] In some embodiments of this application, based on the foregoing scheme, the second determining unit is further configured to: for each candidate control instruction, determine whether the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and determine whether the actual software supports the instruction software support of the candidate control instruction; if the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and the actual software supports the instruction software support of the candidate control instruction, determine the candidate control instruction as the target control instruction.

[0141] In some embodiments of this application, based on the foregoing scheme, the deployment module includes:

[0142] A binding unit is used to logically bind the target control command with the candidate triggering condition to generate an executable scene logic tree;

[0143] A compilation unit is used to compile the scene logic tree into a target control protocol that can be recognized by the vehicle's onboard system.

[0144] The deployment unit is used to deploy the target control scenario in the vehicle system based on the target control protocol.

[0145] In some embodiments of this application, based on the foregoing solution, the apparatus further includes:

[0146] The second acquisition module is used to acquire, if a scenario addition instruction is received from a reference user, a reference instruction group to be executed for the reference vehicle that has been added by the reference user and the reference triggering conditions of the reference instruction group.

[0147] The second determining module is used to determine, based on the reference configuration information of the reference vehicle, whether it is permissible to deploy the reference instruction group in the reference vehicle and the reference triggering conditions of the reference instruction group;

[0148] The generation module is used to generate a reference control scenario based on the reference instruction group and the reference triggering conditions of the reference instruction group, if it is permissible to deploy the reference instruction group and the reference triggering conditions of the reference instruction group in the reference vehicle;

[0149] An add module is used to add the reference control scenario to the multi-source scenario library.

[0150] In some embodiments of this application, based on the foregoing scheme, the second determining module includes:

[0151] The second acquisition unit is used to acquire the reference hardware configuration and reference software support of the reference vehicle as the reference configuration information;

[0152] The third determining unit is configured to determine, based on the reference configuration information, whether the reference vehicle is allowed to execute the reference triggering condition, and, based on the reference configuration information, whether the reference vehicle is allowed to execute the reference instruction group;

[0153] The fourth determining unit is configured to determine, if the reference vehicle is allowed to execute the reference triggering condition and the reference vehicle is allowed to execute the reference instruction group, the reference triggering condition that allows the deployment of the reference instruction group in the reference vehicle.

[0154] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium storing at least one computer program instruction, which is loaded and executed by a processor to perform the operations described above.

[0155] Based on the same inventive concept, this application also provides an electronic device, see reference. Figure 11 The diagram shows a schematic of the structure of an electronic device according to an embodiment of this application. The electronic device includes one or more memories 1104, one or more processors 1102, and at least one computer program (computer program instructions) stored in the memory 1104 and executable on the processor 1102. When the processor 1102 executes the computer program, it implements the method described above.

[0156] Among them, Figure 11 In this document, a bus architecture (represented by bus 1100) is used. Bus 1100 may include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 1102 and memory represented by memory 1104. Bus 1100 may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1105 provides an interface between bus 1100 and receiver 1101 and transmitter 1103. Receiver 1101 and transmitter 1103 may be the same element, i.e., a transceiver, providing a unit for communicating with various other devices over a transmission medium. Processor 1102 is responsible for managing bus 1100 and general processing, while memory 1104 may be used to store data used by processor 1102 during operation.

[0157] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and embodiments are within the scope and spirit of this application and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Furthermore, the functional units may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit.

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

[0159] The units described as separate components may or may not be physically separate. Similarly, the components of the control device may or may not be physical units; they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

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

[0161] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.< / skill> < / skill> < / scenariotaskmodel> < / skill> < / skill> < / skill>

Claims

1. A deployment method for a vehicle control scenario, characterized in that, The multi-source scenario library displays at least one user-added control scenario. The control scenario includes a control command group for the user's corresponding vehicle and triggering conditions for the control command group. The control command group includes at least one control command. The method is applied to the target vehicle and includes: If a scenario deployment instruction from a target user is received, deployment requirement information for candidate control scenarios is obtained. The candidate control scenarios include candidate instruction groups and candidate triggering conditions for the candidate instruction groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenarios. Based on the deployment requirement information and the functional configuration information of the target vehicle, a target instruction group that can be deployed in the target vehicle is determined from the candidate control scenarios, wherein the functional configuration information includes the actual hardware configuration and actual software support of the target vehicle; Based on the target instruction group and the candidate triggering conditions, a target control scenario is deployed in the target vehicle.

2. The method according to claim 1, characterized in that, The step of determining the target instruction group that can be deployed in the target vehicle from the candidate control scenarios based on the deployment requirement information and the functional configuration information of the target vehicle includes: Obtain the functional configuration information of the target vehicle; Based on the functional configuration information, determine whether the target vehicle is allowed to execute the candidate triggering condition; If the target vehicle allows the execution of the candidate triggering conditions, the target instruction group is determined from the candidate instruction group based on the function configuration information.

3. The method according to claim 2, characterized in that, Determining the target instruction group from the candidate instruction group based on the functional configuration information includes: Extract instruction requirement information corresponding to each candidate control instruction from the deployment requirement information, wherein the candidate instruction group includes at least one candidate control instruction, and the instruction requirement information includes the instruction hardware configuration and instruction software support required to execute the candidate control instruction; The candidate control instructions that support the instruction requirement information of the function configuration information are extracted from the candidate instruction group as target control instructions to obtain the target instruction group, wherein the target instruction group includes at least one target control instruction.

4. The method according to claim 3, characterized in that, The candidate control instruction from which the instruction requirement information supported by the function configuration information is extracted from the candidate instruction group is used as the target control instruction, including: For each candidate control instruction, determine whether the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and determine whether the actual software supports the instruction software support of the candidate control instruction. If the actual hardware configuration supports the instruction hardware configuration of the candidate control instruction, and the actual software supports the instruction software support of the candidate control instruction, then the candidate control instruction is determined as the target control instruction.

5. The method according to claim 1, characterized in that, The deployment of the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions includes: The target control command is logically bound to the candidate triggering conditions to generate an executable scene logic tree; The scenario logic tree is compiled into a target control protocol that can be recognized by the vehicle's in-vehicle system; The target control scenario is deployed in the vehicle system based on the target control protocol.

6. The method according to claim 1, characterized in that, The multi-source scene library is updated in the following way: If a scenario addition instruction is received from a reference user, obtain the reference instruction group to be executed for the reference vehicles already added by the reference user and the reference triggering conditions of the reference instruction group; Based on the reference configuration information of the reference vehicle, determine whether it is permissible to deploy the reference instruction group in the reference vehicle and the reference triggering conditions of the reference instruction group; If it is permissible to deploy the reference instruction group and the reference triggering conditions of the reference instruction group in the reference vehicle, a reference control scenario is generated based on the reference instruction group and the reference triggering conditions; Add the reference control scenario to the multi-source scenario library.

7. The method according to claim 6, characterized in that, The step of determining whether to allow the deployment of the reference instruction group in the reference vehicle and the reference triggering conditions of the reference instruction group based on the reference configuration information of the reference vehicle includes: The reference hardware configuration and reference software support of the reference vehicle are obtained as the reference configuration information; Based on the reference configuration information, determine whether the reference vehicle is allowed to execute the reference triggering condition, and determine whether the reference vehicle is allowed to execute the reference instruction group; If the reference vehicle is allowed to execute the reference triggering condition, and the reference vehicle is allowed to execute the reference instruction group, then the reference instruction group and the reference triggering condition for deploying the reference instruction group in the reference vehicle are determined.

8. A deployment device for a vehicle control scenario, characterized in that, The multi-source scenario library displays at least one user-added control scenario. The control scenario includes a control command group for the user's corresponding vehicle and triggering conditions for the control command group. The control command group includes at least one control command. The device is applied to the target vehicle and includes: The first acquisition module is used to acquire deployment requirement information of candidate control scenarios if a scenario deployment instruction is received from a target user. The candidate control scenarios include candidate instruction groups and candidate triggering conditions of the candidate instruction groups. The deployment requirement information includes the execution hardware configuration and execution software support required to execute the candidate control scenarios. The first determining module is used to determine, based on the deployment requirement information and the functional configuration information of the target vehicle, a target instruction group that can be deployed in the target vehicle from the candidate control scenarios, wherein the functional configuration information includes the actual hardware configuration and actual software support of the target vehicle; The deployment module is used to deploy the target control scenario in the target vehicle based on the target instruction group and the candidate triggering conditions.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that are loaded and executed by a processor to perform the operations performed by the method as described in any one of claims 1 to 7.

10. An electronic device comprising a processor and a memory, characterized in that, The memory stores computer program instructions that can be executed by the processor, and when the processor executes the computer program instructions, it implements the instructions of the method as described in any one of claims 1 to 7.

Images