Vehicle scenario mode setting method, device, vehicle and readable storage medium

Abstract

This invention proposes a vehicle scenario mode setting method, device, vehicle, and readable storage medium. The method includes the steps of: displaying optional condition components and optional execution components; obtaining a target condition component determined by the user in the optional condition components and a target execution component determined in the optional execution components; generating a target scenario mode based on the target condition component and the target execution component; and triggering the target scenario mode to execute the execution operation corresponding to the target execution component when the triggering condition of the target condition component is met. By displaying optional condition components and optional execution components, the invention provides users with triggering conditions and execution operations for scenario modes that can be set based on selection. This allows users to set target scenario modes according to their own needs without requiring specific code operations, reducing the development cost of scenario modes by eliminating the need for complex code development.

Description

Technical Field

[0001] This invention relates to the field of vehicle control, and more particularly to a method, apparatus, vehicle, and readable storage medium for setting vehicle scene modes. Background Technology

[0002] Traditional car scenario modes are usually developed and pre-configured by the car manufacturer's engineers. Users can only select the mode they need, but cannot set scenario modes according to their own personalized needs. Since scenario modes involve the application of vehicle's underlying data, adding scenario modes requires complex code development, hardware adaptation and security verification, resulting in a long development cycle and high cost. Summary of the Invention

[0003] The main objective of this invention is to provide a method, device, vehicle, and readable storage medium for setting vehicle scene modes, aiming to solve the problem in the prior art that users cannot set vehicle scene modes according to their own needs.

[0004] To achieve the above objectives, the present invention provides a method for setting vehicle scene modes, the method comprising the following steps: Displays optional conditional components and optional execution components; Obtain the target condition component determined by the user in the optional condition component, and the target execution component determined in the optional execution component; A target scenario pattern is generated based on the target condition component and the target execution component; When the triggering condition of the target condition component is met, the target scenario mode is triggered to execute the execution operation corresponding to the target execution component.

[0005] Optionally, the display optional condition component and the optional execution component include: Acquire the collected vehicle status data and user behavior data; The vehicle status data and the user behavior data are analyzed to generate suggested scenario patterns corresponding to the vehicle status data and the user behavior data. The suggested scenario patterns include suggested condition components and suggested execution components. Display the optional condition component that includes the suggested condition component, and the optional execution component that includes the suggested execution component.

[0006] Optionally, the optional condition display component is preceded by the optional execution component, which includes: Obtain component generation information, which corresponds to the optional condition component and the optional execution component; Obtain the vehicle component from the component generation information; Obtain the component key corresponding to the vehicle component from the data map; Obtain the component configuration information from the component generation information; The optional condition component or the optional execution component is generated based on the component configuration information and the component key.

[0007] Optionally, the method further includes: Obtain real-time vehicle component data through data maps; Obtain the current storage component data and compare the difference data between the current storage component data and the real-time vehicle component data; Determine the target component corresponding to the difference data, wherein the target component is the optional condition component or the optional execution component; The target component is updated based on the difference data.

[0008] Optionally, triggering the target scenario mode to execute the execution operation corresponding to the target execution component when the triggering condition of the target condition component is met includes: When the triggering condition of the target condition component is met, the target component key and target component value in the target execution component are obtained; The data engine sends the target component value to the vehicle component corresponding to the target component key based on the data map.

[0009] Optionally, generating the target scenario mode based on the target condition component and the target execution component includes: A scenario mode to be configured is generated based on the target condition component and the target execution component; The scenario mode to be configured is run virtually to obtain the virtual running results; Obtain vehicle standard data and determine whether the virtual operation result meets the vehicle standard data; If the virtual operation result meets the vehicle standard data, then the scenario mode to be configured will be used as the target scenario mode.

[0010] Optionally, triggering the target scenario mode to execute the execution operation corresponding to the target execution component when the triggering condition of the target condition component is met includes: When the triggering condition of the target condition component is met, the target scenario mode is triggered; Determine whether there is a conflict between the currently triggered target scenario modes; If there is a conflict among the currently triggered target scenario modes, then the priority of each target scenario mode is obtained; The execution operation corresponding to the target execution component in the target scenario mode with the highest execution priority is executed.

[0011] To achieve the above objectives, the present invention also provides a vehicle scene mode setting device, the vehicle scene mode setting device comprising: The first display module is used to display optional conditional components and optional execution components; The first acquisition module is used to acquire the target condition component determined by the user in the optional condition component, and the target execution component determined in the optional execution component; The first generation module is used to generate a target scenario mode based on the target condition component and the target execution component; The first triggering module is used to trigger the target scenario mode when the triggering condition of the target condition component is met, so as to execute the execution operation corresponding to the target execution component.

[0012] To achieve the above objectives, the present invention also provides a vehicle, the vehicle including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the vehicle scenario mode setting method as described above.

[0013] To achieve the above objectives, the present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the vehicle scenario mode setting method as described above.

[0014] This invention proposes a vehicle scenario mode setting method, apparatus, vehicle, and readable storage medium. The method displays optional condition components and optional execution components; acquires a target condition component determined by the user from the optional condition components, and a target execution component determined from the optional execution components; generates a target scenario mode based on the target condition component and the target execution component; and triggers the target scenario mode to execute the corresponding execution operation when the triggering condition of the target condition component is met. By displaying optional condition components and optional execution components, the method provides users with triggering conditions and execution operations for scenario modes that can be set based on selection. This allows users to set target scenario modes according to their needs without requiring specific code operations, reducing the development cost of scenario modes by eliminating the need for complex code development. Attached Figure Description

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

[0016] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating the first embodiment of the vehicle scene mode setting method of the present invention; Figure 2 This is a schematic diagram of the scene mode editing interface in one embodiment of the vehicle scene mode setting method of the present invention; Figure 3 This is a flowchart of AI-recommended scenario modes in one embodiment of the vehicle scenario mode setting method of the present invention; Figure 4 This is a schematic diagram of AI recommendation prompts in one embodiment of the vehicle scene mode setting method of the present invention; Figure 5 This is a data mapping diagram in one embodiment of the vehicle scene mode setting method of the present invention; Figure 6 This is a schematic diagram of DDS update in one embodiment of the vehicle scene mode setting method of the present invention; Figure 7 This is a schematic diagram of the system structure in one embodiment of the vehicle scene mode setting method of the present invention; Figure 8 This is a schematic diagram of the overall process in one embodiment of the vehicle scene mode setting method of the present invention; Figure 9 This is a schematic diagram of data flow in one embodiment of the vehicle scene mode setting method of the present invention; Figure 10 This is a schematic diagram of the modular structure of the vehicle of the present invention. Detailed Implementation

[0018] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0019] This invention provides a method for setting vehicle scene modes, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle scene mode setting method of the present invention. The method includes the following steps: Step S10: Display the optional conditional components and optional execution components; Conditional components are visual objects that encapsulate logical judgment conditions for specific parameters; optional conditional components are conditional components that can be selected by the user. The specific parameters and conditions that a conditional component targets can be set based on actual needs. For example, optional conditional components can be set for in-vehicle sensor data, external vehicle data, or user behavior data. In-vehicle sensor data such as vehicle speed, tire pressure, and temperature; External data such as weather and road conditions; User behavior data, such as driving habits and biometrics.

[0020] An optional condition component can be configured for one or more specific parameters; for example, an optional condition component can be set to trigger when the vehicle speed is greater than a first vehicle speed threshold; another optional condition component can be set to trigger when the vehicle speed is greater than a second vehicle speed threshold and the weather is raining; the thresholds for specific parameters can be set by default or can be set by the user.

[0021] The execution component is a visual object that encapsulates the control behavior of the vehicle; the optional execution component is an execution component that can be selected by the user.

[0022] The specific objects and control conditions controlled by the execution component can be set according to actual needs. For example, the objects controlled by the optional execution component can be vehicle lights, seats, etc.; specific control conditions can be such as turning on the vehicle's fog lights; or adjusting the seat angle to a preset angle. The specific adjustment parameters of the controlled objects can be set by default or can be set by the user.

[0023] Display refers to the display on the vehicle's screen or the screen of a mobile device associated with the vehicle. After displaying the optional condition components and optional execution components, users can select the required condition components and execution components by dragging, clicking or other interactive methods.

[0024] The triggering method for display can be set based on actual needs. For example, when a user needs to create a new scenario mode, they can actively select the creation of the scenario mode through the HMI (Human-Machine Interface) to enter the editing interface and trigger the display of optional condition components and optional execution components. Alternatively, recommended scenario modes can be automatically generated by acquiring vehicle status data and user behavior data and analyzing them. Users can edit the recommended scenario modes to enter the editing interface and display optional condition components and optional execution components in the editing interface.

[0025] Step S20: Obtain the target condition component determined by the user in the optional condition components, and the target execution component determined in the optional execution components; See Figure 2 The target condition component is the condition component selected by the user from the optional condition components; the target execution component is the execution component selected by the user from the optional execution components.

[0026] Step S30: Generate a target scenario mode based on the target condition component and the target execution component; The target scenario pattern is a scenario pattern obtained based on the target condition component and the target execution component.

[0027] It is understandable that the target condition component indicates the triggering condition selected by the user, and the target execution component indicates the control behavior selected by the user. Therefore, after the target condition component and the target execution component are determined, it can be determined that the scenario mode required by the user is to execute the control behavior corresponding to the target execution component when the condition corresponding to the target condition component is triggered. Therefore, the target scenario mode can be obtained through the target condition component and the target execution component.

[0028] Step S40: When the triggering condition of the target condition component is met, the target scenario mode is triggered to execute the execution operation corresponding to the target execution component.

[0029] After the target scenario mode is set, the target scenario mode runs; the triggering of the target scenario mode depends on the triggering conditions of the target condition component; when the triggering conditions of the target condition component are met, the target scenario mode is triggered and the execution operation corresponding to the target execution component is executed.

[0030] This embodiment provides users with triggering conditions and execution operations for selectable scenario modes by displaying optional condition components and optional execution components. This allows users to set target scenario modes according to their own needs without requiring them to perform specific code operations, thus reducing the development cost of scenario modes by eliminating the need for complex code development.

[0031] Further, see Figure 3 In the second embodiment of the vehicle scenario mode setting method of the present invention based on the first embodiment, step S10 includes the following steps: Step S11: Obtain the collected vehicle status data and user behavior data; Step S12: Analyze the vehicle status data and the user behavior data to generate a suggested scenario pattern corresponding to the vehicle status data and the user behavior data. The suggested scenario pattern includes a suggested condition component and a suggested execution component. Step S13: Display the optional condition component containing the suggested condition component, and the optional execution component containing the suggested execution component.

[0032] Vehicle status data reflects the vehicle's own condition and the state of its environment; vehicle status data includes in-vehicle sensor data and external data.

[0033] User behavior data refers to data reflecting user behavior generated from interactions with the vehicle's infotainment system.

[0034] It is understandable that during vehicle use, users may perform specific behaviors under certain vehicle status scenarios based on their habits. Therefore, by analyzing vehicle status data and user behavior data, we can obtain correlated vehicle status scenarios and user behaviors that meet the requirements for setting scenario modes. Thus, in order to further set scenario modes that fit the actual driving needs of users, we generate suggested scenario modes.

[0035] The recommended scenario mode is a scenario mode that meets the user's needs, obtained by analyzing vehicle status data and user behavior data.

[0036] The suggested scenario mode includes suggested conditions components and suggested execution components.

[0037] The suggested condition component is obtained through the analysis of vehicle status data, while the suggested execution component is obtained through the analysis of user behavior data.

[0038] The specific analysis method can be set according to actual needs. For example, by setting up AI algorithms or related models to analyze the correlation between vehicle status data and user behavior data, corresponding suggested scenario modes can be output.

[0039] After the recommended scenario mode is determined, a suggestion prompt for the recommended scenario mode is displayed. The user can choose to apply the recommended scenario mode immediately, and then the recommended scenario mode will be run.

[0040] See Figure 4 Users can also edit the suggested scenario modes to adjust them. Specifically, after selecting the arrangement, the user enters the editing interface. In the editing interface, the completed condition component is set as the suggested condition component, and the completed execution component is set as the suggested execution component. At the same time, other optional condition components and optional execution components are displayed in the selection area. Users can add optional condition components to the selected condition component or replace the suggested condition component through interaction. Users can also add optional execution components to the selected execution component or replace the suggested execution component through interaction.

[0041] Users can also choose to cancel the suggested scenario mode. In this case, the suggested scenario mode will not be executed, nor will the editing interface be entered.

[0042] Furthermore, in the third embodiment of the vehicle scenario mode setting method of the present invention based on the first embodiment of the present invention, the step S10 includes the following steps: Step S50: Obtain component generation information, wherein the component generation information corresponds to the optional condition component and the optional execution component; Step S60: Obtain the vehicle component from the component generation information; Step S70: Obtain the component key corresponding to the vehicle component from the data map; Step S80: Obtain component configuration information from the component generation information; Step S90: Generate the optional condition component or the optional execution component based on the component configuration information and the component key.

[0043] Component generation information is used to generate conditional or execution components. This information is generated by developers through component settings on the component orchestration platform.

[0044] Vehicle components are the sources or control objects corresponding to the data involved in the component generation information. For example, if the component generation information corresponds to an optional condition component, and the optional condition component specifically detects the vehicle speed, then the vehicle component corresponding to the component generation information is the source of the vehicle speed data, i.e., the VCU (Vehicle Control Unit). Similarly, if the component generation information corresponds to an optional execution component, and the optional execution component specifically controls the vehicle speed, then the vehicle component corresponding to the component generation information is the object controlling the vehicle speed, i.e., the ECU (Electronic Control Unit).

[0045] The vehicle components described above are merely illustrative examples. In practical applications, the corresponding vehicle components can be determined based on specific data and control objects.

[0046] See Figure 5 DataMap is used for data mapping.

[0047] The composite key is the key determined by mapping the relevant interfaces of the vehicle components in the DataMap.

[0048] It is understandable that in practical applications, the specific settings of the underlying interfaces of vehicles of different models or with different software are different. Therefore, in this embodiment, DataMap is used to map the vehicle's DDS (Data Distribution Service), vehicle status data and data structure. Specifically, DataMap includes ServiceMap, ParamMap, and FuncStructMap; among them, ServiceMap is used to establish a mapping relationship with DDS service names; ParamMap is used to establish a mapping relationship with DDS parameter names; and FuncStructMap is used to establish a mapping relationship between DDS services and structures.

[0049] In this embodiment, components are generated using the combination keys corresponding to vehicle components mapped by the DataMap. This ensures that the setting of scenario modes relies on stable combination keys constructed by the DataMap, unaffected by changes in the underlying interface. For example, when the underlying interface changes, the DataMap updates the mapping of the corresponding interface. However, for the scenario mode, the combination keys it depends on remain unchanged; what is updated is the mapping relationship between the combination keys and the interface. Therefore, when the interface changes, the scenario mode can maintain its implementation without adjustment. Similarly, for vehicles of different models or with different software, the unified combination keys mapped by the DataMap enable scenario modes to interface with vehicle components based on the combination keys in the DataMap when applied to different vehicles. This achieves automatic adaptation for different models and software versions, improving cross-model and cross-version compatibility.

[0050] The component configuration information specifically indicates the parameter settings of the conditional component or the execution component. For example, if the component configuration information is for an optional conditional component, then the component configuration information can set the parameters and trigger conditions in the optional conditional component; similarly, if the component configuration information is for an optional execution component, then the component configuration information can set the control object and specific control parameters in the optional execution component.

[0051] After obtaining the component configuration information, the main structure of the conditional component or execution component is constructed using the component configuration information; and the connection with the required interface is realized through the corresponding component key, thereby realizing the generation of the corresponding component.

[0052] Further, see Figure 6 In the fourth embodiment of the vehicle scenario mode setting method of the present invention proposed based on the first embodiment of the present invention, the method further includes the step of: Step 100: Obtain real-time vehicle component data through the data map; Step 110: Obtain the current storage component data and compare the difference data between the current storage component data and the real-time vehicle component data; Step 120: Determine the target component corresponding to the difference data, wherein the target component is the optional condition component or the optional execution component; Step 130: Update the target component based on the difference data.

[0053] Real-time vehicle component data refers to real-time data indicating the underlying interfaces of the vehicle; specifically, real-time vehicle component data is the version information of the real-time DDS service.

[0054] The current storage component data is the version of the DDS service used in the current data map application.

[0055] When the real-time vehicle component data differs from the storage component data, it indicates that the DDS service has changed. Therefore, in order to maintain an accurate interface mapping, the DataMap needs to be updated based on the new DDS service.

[0056] The difference data indicates the difference between real-time vehicle component data and storage component data; the specific method for determining the difference data can be set based on actual needs, such as performing difference calculations on real-time vehicle component data and storage component data to obtain the difference data.

[0057] The difference data can specifically indicate the addition, update, or deletion of relevant modules in the DDS service. When the difference data indicates the addition of a module, a new condition component or execution component can be created based on the added module. When the difference data indicates the update of a module, the relevant condition components and execution components are updated based on the updated content. When the difference data indicates the deletion of a module, the corresponding condition components and execution components are deleted.

[0058] When real-time vehicle component data differs from stored component data, developers can be notified on the component orchestration platform. Developers can choose to update automatically, which will update the DataMap and related components based on the above-mentioned methods of adding, updating, and deleting. Developers can also manually update by referring to the difference data.

[0059] After the update is complete, the real-time vehicle component data will be saved to replace the currently stored component data.

[0060] Furthermore, in the fifth embodiment of the vehicle scenario mode setting method of the present invention based on the first embodiment of the present invention, step S40 includes the following steps: Step S41: When the triggering condition of the target condition component is met, obtain the target component key and target component value in the target execution component; Step S42: The target component value is sent to the vehicle component corresponding to the target component key through the data engine based on the data map.

[0061] The DataEngine is used to convert target component values ​​into real service calls and structured instructions that can be recognized and executed by the DDS service in real time through DataMap configuration rules. The DataEngine not only adapts to composite or enhanced services, but also is compatible with individual components and assembles complex structures in the DDS service.

[0062] The target component key is the component key mapped in the DataMap to the control object targeted by the target execution component; such as the component key corresponding to the seat.

[0063] The target component value is the value that indicates the specific control operation in the target execution component, such as adjusting the seat angle to a preset angle.

[0064] DataEngine specifically includes getDataByFunc(func), getParamValue(func, param), assembleStruct(func, paramObj); Among them, getDataByFunc(func) is used to retrieve data by passing the service name; getParamValue(func, param) is used to retrieve the current value of the parameter by passing the service name and parameter name, and func and param are obtained from the dataMap mapping relationship; assembleStruct(func, paramObj) is used to assemble the downlink data structure and return a new data structure struct.

[0065] By setting up DataEngine to work in conjunction with DataMap, the semantic configurations of componentized conditional components and execution components are transformed into standardized instructions that can be executed by the vehicle, thereby enabling the accurate construction and execution of scenario patterns.

[0066] Furthermore, in the sixth embodiment of the vehicle scenario mode setting method of the present invention based on the first embodiment of the present invention, step S30 includes the following steps: Step S31: Generate a scenario mode to be configured based on the target condition component and the target execution component; Step S32: Perform a virtual run on the scenario mode to be configured to obtain the virtual run result; Step S33: Obtain vehicle standard data and determine whether the virtual operation result meets the vehicle standard data; Step S34: If the virtual operation result meets the vehicle standard data, then the scenario mode to be configured is taken as the target scenario mode.

[0067] The scenario mode to be configured is the scenario mode obtained based on the target condition component and the target execution component.

[0068] Before applying a scenario pattern, its feasibility needs to be verified. Only after the feasibility of the scenario pattern has been successfully verified can the target scenario pattern be started.

[0069] Virtual operation refers to testing and running in a virtual scenario outside the actual vehicle environment; specifically, scenario modes can be virtually run through 3D model simulation or white-box testing.

[0070] By using virtual operation to verify the scenario model, it is possible to avoid affecting the actual operation of the vehicle when there are feasibility issues with the scenario model.

[0071] The virtual run result is the relevant data obtained by virtually running the scenario mode to be configured. Specifically, it can be the status of the vehicle's operating parameters after running the scenario mode.

[0072] Vehicle standard data indicates the vehicle's requirements for operating parameters.

[0073] The virtual operation results indicate the vehicle status after running the scenario mode, while the vehicle standard data indicates the allowed vehicle status. Therefore, by comparing the virtual operation results with the vehicle standard data, it can be determined whether the operation of the scenario mode to be configured can meet the vehicle requirements. When the virtual operation results meet the vehicle standard data, the operation of the scenario mode to be configured is considered to meet the vehicle requirements, and the scenario mode to be configured is used as the target scenario mode. When the virtual operation results do not meet the vehicle standard data, the operation of the scenario mode to be configured is considered to not meet the vehicle requirements, and the scenario mode to be configured is not used as the target scenario mode. At the same time, the specific parameters in the virtual operation results that do not meet the vehicle standard data can also be obtained and displayed to remind the user that the scenario mode to be configured is incorrect, so that the user can modify the scenario mode to be configured based on the parameters that are not met.

[0074] In this embodiment, the reliability of the scenario mode can be guaranteed by virtually running the scenario mode to be configured and making judgments in combination with standard vehicle data.

[0075] Furthermore, in the seventh embodiment of the vehicle scenario mode setting method of the present invention based on the first embodiment of the present invention, step S40 includes the following steps: Step S41: When the triggering condition of the target condition component is met, the target scenario mode is triggered; Step S42: Determine whether there is a conflict between the currently triggered target scenario modes; Step S43: If there is a conflict among the currently triggered target scenario modes, then obtain the priority of each target scenario mode; Step S44: Execute the execution operation corresponding to the target execution component in the target scenario mode with higher priority.

[0076] It is understandable that in practical applications, multiple scenario modes may run simultaneously; and different scenario modes may control related devices, leading to conflicts in control strategies. For example, target scenario mode A is the nap mode; The trigger conditions for the nap mode are that the vehicle is in P gear, the vehicle speed is 0, and the user clicks "Start Nap" on the central control screen; The actions performed in the nap mode are: closing all windows, reclining the seats to 120°, dimming the ambient lights to 20%, setting the air conditioning to 24°C, and locking all doors.

[0077] Target scenario mode B is the welcoming mode; The conditions for triggering the welcome mode are that the mobile phone Bluetooth key enters within 5 meters of the vehicle and the vehicle is currently locked. In welcome mode, the driver's door is automatically unlocked, the driver's seat is automatically moved forward to the memory position, the ambient lights turn blue with a brightness of 60%, and the instrument panel displays "Welcome Home". Based on the triggering conditions of the nap mode and the welcome mode, it can be determined that the triggering conditions of the welcome mode are met after the action is performed in the nap mode. At the same time, there are several opposite actions between the actions performed in the welcome mode and the actions performed in the nap mode; for example, there is a conflict between locking all doors and unlocking the driver's door; there is a conflict between adjusting the ambient lighting and adjusting the seats; the two scene modes will repeatedly switch the settings of the doors and ambient lighting.

[0078] To resolve the conflict between scenario modes, this embodiment sets a priority for scenario modes; the priority can be set manually by the user or automatically based on specific conditions.

[0079] For example, manually triggered scenario modes have a higher priority than automatically triggered scenario modes; since manually triggered scenarios are more in line with the user's actual needs, their priority is set higher. Another example is setting priorities based on the application scenarios of the scenario mode, such as application scenarios including driving safety, functional safety, and assistance functions; Driving safety involves interventions during driving, such as activating hazard lights after a vehicle collision. Because it involves specific driving processes and has high safety requirements, the priority of scenarios related to driving safety is set to the highest. Functional safety refers to intervention operations involving basic driving functions, such as activating child locks, opening and closing windows. Although these scenarios involve settings related to driving, their impact on safety is relatively small compared to driving safety scenarios. Therefore, the priority of the scenario mode corresponding to functional safety can be set to a lower level compared to driving safety scenarios. Assistance functions are operations that do not involve driving, such as playing music and setting ambient lighting. These scenarios are mainly used to achieve personalized settings and have little impact on driving safety. Therefore, the priority of the scenario mode corresponding to the assistance function can be set to the lowest.

[0080] The above priority settings are for illustrative purposes only. In practical applications, priorities can be set according to actual needs.

[0081] After determining the priority of each target scenario mode, for items with conflicts, only the execution operation corresponding to the scenario mode with the highest priority is executed; for items without conflicts, they can still be executed normally.

[0082] Taking the aforementioned target scenario modes A and B as examples, target scenario mode A has the highest priority. Therefore, in the conflicting settings for car locks, ambient lighting, and seats, only the settings for target scenario mode A will be executed. Meanwhile, target scenario mode B also has a non-conflicting instrument display "Welcome Home". Therefore, target scenario mode B can still execute the operations displayed on the instrument display.

[0083] In this embodiment, by setting priorities for target scenario modes, a precise control strategy can be executed when conflicts occur between target scenario modes.

[0084] The overall implementation of this application is described below: See Figure 7 System components: AI model platform: Based on user data and habits, it conducts in-depth analysis of user behavior and provides recommendations for suggested scenario patterns based on users' objective needs.

[0085] Low-code orchestration platform: Provides visual logic orchestration components that encapsulate logical operations, vehicle atomic services, atomic states, and other vehicle data into drag-and-drop logic components, including conditional components and execution components, enabling binding and parameter adjustment control of underlying related service mapping data.

[0086] Data Mapping Relationships: To reduce the complexity of the code generator and improve the maintainability of later scenario modes, two utility classes are defined: DataMap and DataEngine. DataMap is used for data mapping, while DataEngine not only adapts to some composite or enhanced services but also supports single atomic services and assembles complex structures. DataMap maintains the unique keys of services, parameters, and structures, aligning components with DDS services and facilitating scenario mode version management.

[0087] Differential Calculation: DataMap is used to perform differential calculations after DDS service version iterations, yielding three types of differences: additions, updates, and removals. The calculation results are then fed back to developers, allowing them to perceive the differences between the current and historical versions, which is beneficial for updating scenario-mode components. For example, if a component is added, it will be added to the scenario-mode component; if it is updated, the corresponding component will also be updated; if it is removed, the corresponding component will be removed or hidden. The results of these three calculations in DataMap will be sent to developers. Developers can automate the addition, update, and removal of components programmatically, and the execution results will be notified to them. If automation fails, developers can manually develop the component.

[0088] The DataMap is used for mapping DDS services, states, and data structures. In scenario patterns, specific service names, parameter names, and structures are not specified; instead, they are retrieved from the DataMap using a unique key. This avoids the problem of historical scenario patterns becoming invalid due to later modifications to services, parameters, and structures. The DataMap mainly consists of the following three parts: (1) ServiceMap: Establishes a mapping relationship with DDS service names.

[0089] (2) ParamMap: Establishes a mapping relationship with DDS parameter names.

[0090] (3) FuncStructMap: Establishes the mapping relationship between services and structures.

[0091] DataEngine consists of the following three parts: (1) getDataByFunc(func): Retrieves data by passing the service name; (2) getParamValue(func, param): Gets the current value of the parameter by passing the service name and parameter name. func and param are obtained from the dataMap mapping relationship; (3) assembleStruct(func, paramObj): Assembles the downlink data body and returns a new struct (data structure).

[0092] Vehicle Data Center: Real-time access to in-vehicle sensor data, such as vehicle speed, tire pressure, and temperature; external data, such as weather and road conditions; and user behavior data, such as driving habits and biometrics.

[0093] Cloud service module: Provides stable and reliable service capabilities, data persistence capabilities, version management capabilities, more robust complex logic operation capabilities, and platform deployment capabilities.

[0094] Security verification module: Through software testing environments, such as 3D model simulation and white-box testing, the system simulates user-programmed scenario modes, adds permission verification and abnormal data behavior interception, and improves the security of scenario modes when getting on the vehicle.

[0095] Scenario execution code instruction generation module: After the scenario mode is configured in the visual interface, it will be converted into script code instructions for vehicle control through the code generator.

[0096] Gateways are responsible for communication between the vehicle's internal and external networks, such as BCM (Body Control Module), TMS (Thermal Management System), EMS (Energy Management System), and ECS.

[0097] SceneEngine: Parses the logic rules of low-code configuration and sends executable script code instructions to the ECU; it consists of the following two parts: (1) requestAtomicState(func): Service data uplink channel, where func is the service name, obtained through the ServiceMap of DataMap; (2) requestAtomicServer(func, struct): Service data downlink channel, struct is returned after processing by assembleStruct.

[0098] AI Recommendation Module: Based on historical usage data, user feedback data, and the current vehicle environment, this module incorporates AI algorithms to automatically recommend scenario modes, such as adjusting parameters like air conditioning temperature and fan speed, to assist users in selecting and setting scenarios. It primarily offers the following two recommendation scenarios: 1. Recommended existing scenario modes: scenario modes that are inherent to the vehicle, scenario modes that are already available in the cloud, or scenario modes shared by other vehicle owners.

[0099] 2. Recommending non-existent scenario modes: Based on vehicle conditions, user behavior, and the environment, such as temperature, weather, road conditions, and traffic, the system automatically generates a scenario mode for recommendation by combining AI model training and current scenario mode generation scheme. Users can choose to execute the scenario immediately or arrange scenarios. Scenario modes can be arranged in the scenario arrangement module. By incorporating AI recommendation algorithms, the system automatically recommends scenario modes based on historical data and the vehicle's environment, thereby improving the user experience.

[0100] See Figure 8 , 9 Method execution flow: 1. Scenario mode arrangement; 1.1 Users can drag and drop components through the visual interface as trigger conditions for scenario modes, such as "User Mode" and "Temperature".

[0101] 1.2 Users can drag and drop relevant execution components to associate vehicle parameters, such as turning on fog lights or moving the seat forward or backward by 100%.

[0102] 1.3 Configure execution priority and conflict resolution strategies for scenario modes, such as the weight allocation when two scenario modes coexist.

[0103] 2. Dynamic data binding; 2.1 Real-time monitoring of relevant data sources inside and outside the vehicle, binding of data sources, and real-time triggering of conditions via API.

[0104] 3. Security Deployment; 3.1 The system automatically simulates the configuration logic to detect whether there are conflicting instructions or out-of-limit parameters.

[0105] 3.2 Users need biometric authentication, such as fingerprints, faces, or authorization activation scenarios via physical buttons or in-vehicle confirmation buttons. Simulation and biometric authentication mechanisms are introduced to balance personalization and security.

[0106] 4. Version updates and scenario sharing; 4.1 The vehicle's scenario mode version can be upgraded through cloud OTA technology. The cloud OTA method can realize the batch distribution of scenario modes and remote debugging, which greatly saves manpower costs.

[0107] 4.2 Users can upload their custom-designed scenario modes to the cloud application store for other users to download and use.

[0108] By deeply integrating large-scale AI models with low-code technology into the field of vehicle control, we can efficiently achieve intelligent and personalized recommendations for scenario-based modes using AI. Low-code technology makes creating scenario-based modes as simple as "building blocks," reducing the development threshold and cognitive burden on users, meeting their personalized needs, and enhancing their emotional experience. Simultaneously, dynamic binding of multi-source data ensures accurate execution of scenario-based modes.

[0109] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by 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 is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0111] This application also provides a vehicle scene mode setting device for implementing the above-described vehicle scene mode setting method, the vehicle scene mode setting device comprising: The first display module is used to display optional conditional components and optional execution components; The first acquisition module is used to acquire the target condition component determined by the user in the optional condition component, and the target execution component determined in the optional execution component; The first generation module is used to generate a target scenario mode based on the target condition component and the target execution component; The first triggering module is used to trigger the target scenario mode when the triggering condition of the target condition component is met, so as to execute the execution operation corresponding to the target execution component.

[0112] This vehicle scenario mode setting device provides users with trigger conditions and execution operations for the scenario modes that can be set based on the selection by displaying optional condition components and optional execution components. In this way, users can set the target scenario mode according to their own needs without having to deal with specific code operations, without the need for complex code development, thus reducing the development cost of scenario modes.

[0113] It should be noted that the first display module in this embodiment can be used to execute step S10 in this application embodiment, the first acquisition module in this embodiment can be used to execute step S20 in this application embodiment, the first generation module in this embodiment can be used to execute step S30 in this application embodiment, and the first trigger module in this embodiment can be used to execute step S40 in this application embodiment.

[0114] Furthermore, the first display module includes: The first acquisition unit is used to acquire the collected vehicle status data and user behavior data; The first analysis unit is used to analyze the vehicle status data and the user behavior data, and generate a suggested scenario pattern corresponding to the vehicle status data and the user behavior data. The suggested scenario pattern includes a suggested condition component and a suggested execution component. The first display unit is configured to display the optional condition component containing the suggested condition component, and the optional execution component containing the suggested execution component.

[0115] Furthermore, the device also includes: The second display module is used to obtain component generation information before displaying the optional condition component and the optional execution component, wherein the component generation information corresponds to the optional condition component and the optional execution component; The second acquisition module is used to acquire the vehicle component from the component generation information; The third acquisition module is used to acquire the component key corresponding to the vehicle component from the data map; The fourth acquisition module is used to acquire component configuration information from the component generation information; The second generation module is used to generate the optional condition component or the optional execution component based on the component configuration information and the component key.

[0116] Furthermore, the device also includes: The fifth acquisition module is used to acquire real-time vehicle component data through a data map; The sixth acquisition module is used to acquire the current storage component data and compare the difference data between the current storage component data and the real-time vehicle component data; The first determining module is used to determine the target component corresponding to the difference data, wherein the target component is the optional condition component or the optional execution component; The first update module is used to update the target component based on the difference data.

[0117] Furthermore, the first triggering module includes: The second acquisition unit is used to acquire the target component key and the target component value in the target execution component when the triggering condition of the target condition component is met. The first sending unit is used to send the target component value to the vehicle component corresponding to the target component key based on the data map through the data engine.

[0118] Furthermore, the first generation module includes: The first generation unit is used to generate a configurable scenario mode based on the target condition component and the target execution component; The first running unit is used to perform virtual running of the scenario mode to be configured and obtain virtual running results; The third acquisition unit is used to acquire vehicle standard data and determine whether the virtual operation result meets the vehicle standard data. The first execution unit is configured to use the scenario mode to be configured as the target scenario mode if the virtual operation result meets the vehicle standard data.

[0119] Furthermore, the first triggering module includes: The first triggering unit is used to trigger the target scenario mode when the triggering condition of the target condition component is met; The first judgment unit is used to determine whether there is a conflict between the currently triggered target scenario modes; The fourth acquisition unit is used to acquire the priority of each target scenario mode if there is a conflict among the currently triggered target scenario modes. The second execution unit is used to execute the execution operations corresponding to the target execution component in the target scenario mode with higher priority.

[0120] Reference Figure 10 In terms of hardware structure, the vehicle may include components such as a communication module 10, a memory 20, and a processor 30. In the vehicle, the processor 30 is connected to both the memory 20 and the communication module 10. The memory 20 stores a computer program, which is executed by the processor 30. When the computer program is executed, it implements the steps of the above-described method embodiments.

[0121] The communication module 10 can connect to external communication devices via a network. The communication module 10 can receive requests from the external communication devices and can also send requests, instructions, and information to the external communication devices, which can be other vehicles, servers, or IoT devices, such as televisions, etc.

[0122] The memory 20 can be used to store software programs and various data. The memory 20 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as display optional conditional components and optional execution components), etc.; the data storage area may include a database, and may store data or information created according to system usage, etc. Furthermore, the memory 20 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0123] The processor 30 is the control center of the vehicle. It connects to various parts of the vehicle via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 20, and by calling data stored in the memory 20, it performs various vehicle functions and processes data, thereby providing overall vehicle monitoring. The processor 30 may include one or more processing units; optionally, the processor 30 may integrate an application processor and a modem processor. The application processor primarily handles the operating system, user interface, and applications, while the modem processor primarily handles wireless communication. It is understood that the modem processor may not be integrated into the processor 30.

[0124] although Figure 10 Not shown, but the vehicle described above may also include a circuit control module for connecting to a power source to ensure the normal operation of other components. Those skilled in the art will understand that... Figure 10 The vehicle structure shown does not constitute a limitation on the vehicle and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0125] The present invention also proposes a computer-readable storage medium having a computer program stored thereon. The computer-readable storage medium may be... Figure 10 The memory 20 in the vehicle may be at least one of ROM (Read-Only Memory) / RAM (Random Access Memory), magnetic disk, optical disk, etc. The computer-readable storage medium includes a number of instructions to cause a terminal device with a processor (which may be a television, automobile, mobile phone, computer, server, terminal, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0126] In this invention, the terms "first," "second," "third," "fourth," and "fifth" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0127] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0128] Although embodiments of the present invention have been shown and described above, the scope of protection of the present invention is not limited thereto. It is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, and substitutions to the above embodiments within the scope of the present invention, and such changes, modifications, and substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for setting vehicle scenario modes, characterized in that, The method for setting vehicle scenario modes includes: Displays optional conditional components and optional execution components; Obtain the target condition component determined by the user in the optional condition component, and the target execution component determined in the optional execution component; A target scenario pattern is generated based on the target condition component and the target execution component; When the triggering condition of the target condition component is met, the target scenario mode is triggered to execute the execution operation corresponding to the target execution component.

2. The vehicle scenario mode setting method as described in claim 1, characterized in that, The optional display condition component and optional execution component include: Acquire the collected vehicle status data and user behavior data; The vehicle status data and the user behavior data are analyzed to generate suggested scenario patterns corresponding to the vehicle status data and the user behavior data. The suggested scenario patterns include suggested condition components and suggested execution components. Display the optional condition component that includes the suggested condition component, and the optional execution component that includes the suggested execution component.

3. The vehicle scenario mode setting method as described in claim 1, characterized in that, The section preceding the optional condition display component and the optional execution component includes: Obtain component generation information, which corresponds to the optional condition component and the optional execution component; Obtain the vehicle component from the component generation information; Obtain the component key corresponding to the vehicle component from the data map; Obtain the component configuration information from the component generation information; The optional condition component or the optional execution component is generated based on the component configuration information and the component key.

4. The vehicle scenario mode setting method as described in claim 1, characterized in that, The method further includes: Obtain real-time vehicle component data through data maps; Obtain the current storage component data and compare the difference data between the current storage component data and the real-time vehicle component data; Determine the target component corresponding to the difference data, wherein the target component is the optional condition component or the optional execution component; The target component is updated based on the difference data.

5. The vehicle scenario mode setting method as described in claim 1, characterized in that, The step of triggering the target scenario mode when the triggering condition of the target condition component is met, so as to execute the execution operation corresponding to the target execution component, includes: When the triggering condition of the target condition component is met, the target component key and target component value in the target execution component are obtained; The data engine sends the target component value to the vehicle component corresponding to the target component key based on the data map.

6. The vehicle scenario mode setting method as described in claim 1, characterized in that, The generation of the target scenario mode based on the target condition component and the target execution component includes: A scenario mode to be configured is generated based on the target condition component and the target execution component; The scenario mode to be configured is run virtually to obtain the virtual running results; Obtain vehicle standard data and determine whether the virtual operation result meets the vehicle standard data; If the virtual operation result meets the vehicle standard data, then the scenario mode to be configured will be used as the target scenario mode.

7. The vehicle scenario mode setting method as described in claim 1, characterized in that, The step of triggering the target scenario mode when the triggering condition of the target condition component is met, so as to execute the execution operation corresponding to the target execution component, includes: When the triggering condition of the target condition component is met, the target scenario mode is triggered; Determine whether there is a conflict between the currently triggered target scenario modes; If there is a conflict among the currently triggered target scenario modes, then the priority of each target scenario mode is obtained; The execution operation corresponding to the target execution component in the target scenario mode with the highest execution priority is executed.

8. A vehicle scene mode setting device, characterized in that, The vehicle scenario mode setting device includes: The first display module is used to display optional conditional components and optional execution components; The first acquisition module is used to acquire the target condition component determined by the user in the optional condition component, and the target execution component determined in the optional execution component; The first generation module is used to generate a target scenario mode based on the target condition component and the target execution component; The first triggering module is used to trigger the target scenario mode when the triggering condition of the target condition component is met, so as to execute the execution operation corresponding to the target execution component.

9. A vehicle, characterized in that, The vehicle includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the vehicle scenario mode setting method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the vehicle scenario mode setting method as described in any one of claims 1 to 7.

Images