Interaction method, vehicle, server, and storage medium
By confirming the safety risk level of the actions or functions to be executed before the customized solution is implemented and providing feedback, the safety issues in the execution process of customized solutions in the vehicle system are resolved, thereby improving user experience and safety.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GUANGZHOU XIAOPENG MOTORS TECH CO LTD
- Filing Date
- 2022-09-09
- Publication Date
- 2026-07-03
Smart Images
Figure CN115520207B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle technology, and more specifically, to an interaction method, a vehicle, a server, and a computer-readable storage medium. Background Technology
[0002] Customized solutions for in-vehicle system functions greatly improve the convenience of vehicle use for users. Users pre-customize the in-vehicle system functions, and the customized solutions include trigger conditions and execution instructions and / or execution functions. However, while providing users with highly automated customization options, these solutions also introduce significant uncertainties. Because the customized solutions run in the background of the in-vehicle system for extended periods, the vehicle's state may change during the entire triggering process. Ensuring vehicle safety during the execution of customized solutions becomes a pressing issue that needs to be addressed. Summary of the Invention
[0003] This application provides an interaction method, a vehicle, a server, and a computer-readable storage medium.
[0004] The interaction method of this application includes:
[0005] When the customized solution for the customized in-vehicle system functions is triggered under the given conditions, the safety risk level of each execution action and / or execution function in the customized solution is confirmed during the execution of the customized solution, based on the pre-set safety rules for execution actions and vehicle status information and the current status information of the vehicle.
[0006] Based on the security risk level, corresponding execution status feedback is sent to the user when each action and / or function is executed.
[0007] In this application, during the execution of the customized solution, the risk level of each upcoming action or function is determined based on the pre-set safety rules for the execution actions and vehicle status information, as well as the real-time status information of the vehicle. The user is then given corresponding feedback, enabling them to be aware of the expected risks of the upcoming execution and to take timely action based on the actual situation. This, to a certain extent, ensures the safety of the customized solution execution.
[0008] The method further includes:
[0009] Before the customized solution is executed, it is checked whether there are any security risks in the customized solution;
[0010] If the customized solution includes an action and / or function with a security risk level greater than or equal to a preset security risk level, the customized solution is confirmed to have a security risk and a confirmation message is sent to the user to confirm whether to execute the customized solution.
[0011] In response to the user's confirmation of the implementation of the solution, the customized solution is executed.
[0012] Therefore, before the customized solution is executed, the overall security risks of the solution will be confirmed. If the customized solution includes execution actions and / or execution functions with a high level of security risk, it can only be executed after the user confirms it a second time. This allows the user to have an overall risk expectation before the customized solution is executed, and the user can confirm whether to execute it based on the actual situation, which can ensure the security of the customized solution execution to a certain extent.
[0013] The method further includes:
[0014] If the customized solution does not include any execution actions or functions with a security risk level greater than or equal to the preset security risk level, the customized solution is confirmed to have no security risk and feedback is sent to the user indicating that the customized solution has started execution.
[0015] In this way, once the overall security of the customized solution is confirmed to be high, the customized solution will automatically begin execution and inform the user, so that the user can mentally anticipate the action to be performed and will not feel surprised by the execution.
[0016] The method further includes:
[0017] When the currently executing action or function is being executed, the user interface of the vehicle system fully displays the status information of the customized solution being executed in a first state.
[0018] When the current action or function is completed and the time interval between the next action or function to be executed is greater than a predetermined time interval, the status information switches from the first state to the second state, which briefly displays the status information of the customized solution being executed.
[0019] When the execution action or function to be executed begins, the state information switches from the second state to the first state.
[0020] In this way, based on the execution status of the actions during the customized solution process, the user is prompted with different statuses. The prompting effect is enhanced when it is necessary, while the prompting effect is weakened when the solution is triggered but there is no execution content yet.
[0021] The security risk levels include a first security risk level, a second security risk level, a third security risk level, and a fourth security risk level, ranging from high to low risk.
[0022] The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes:
[0023] If the security risk level is the first security risk level, a feedback message will be sent to the user indicating that the action cannot be performed.
[0024] If it is determined that performing an action poses an extremely high safety risk under the current vehicle condition, the relevant action will not be performed, and feedback will be provided to the user.
[0025] The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes:
[0026] If the security risk level is the second security risk level, the user is sent feedback indicating that there is an immediate risk of executing the action, as well as confirmation information on whether to execute the action.
[0027] In this way, if it is determined that there is a high safety risk in performing an action under the current vehicle status, a risk warning will be given to the user, and the action can only be performed after the user confirms it a second time, thus ensuring the safety of the action.
[0028] The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes:
[0029] If the security risk level is the third security risk level, a feedback message will be sent to the user indicating that the action is about to be performed.
[0030] In this way, if it is determined that there is a low safety risk in performing an action under the current vehicle status, the user is informed that the action is about to be performed, but the action can be performed without the user's confirmation, effectively balancing safety and smooth execution.
[0031] The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes:
[0032] If the security risk level is the fourth security risk level, after the execution action is completed, the user will be given execution feedback on the execution action.
[0033] In this way, if the current vehicle status is determined and there is basically no safety risk in performing the action, the user is directly given feedback that the action has been performed after it is completed, effectively balancing safety and smooth execution.
[0034] During the execution of the customized solution, confirming the security risk level of each execution action and / or execution function in the customized solution includes:
[0035] When the customized solution includes the execution function, the security risk level of the execution function is determined based on the highest security risk level of each executable sub-execution action in the execution function.
[0036] In this way, the security risks of the execution function are determined based on the highest security risk level of the sub-execution actions in the execution function, and the security risk warning is given as a whole for the execution function. The risk warning for the execution function is more holistic and avoids frequent warnings when there are many sub-execution actions.
[0037] The method further includes:
[0038] In response to the user's stop operation during the execution of the customized solution, the execution of the customized solution is stopped.
[0039] In this way, users can stop the process at any stage of the customized solution execution, providing users with proactive security measures.
[0040] The interaction method of this application includes:
[0041] When the customized solution for the customized vehicle system functions is triggered under the given conditions, the safety risk level of each execution action and / or execution function in the customized solution is confirmed during the execution of the customized solution, based on the pre-set safety rules for execution actions and vehicle status information and the current status information reported by the vehicle.
[0042] Generate execution instructions based on the security risk level;
[0043] The execution instructions are sent to the vehicle so that the vehicle executes the execution instructions generated according to the safety risk level, and sends corresponding execution status feedback to the user when each execution action and / or execution function is executed.
[0044] Thus, during the execution of the customized solution, based on the pre-set safety rules for the execution actions and vehicle status information, as well as the real-time status information of the vehicle, the risk level of each execution action or function to be executed is determined, and corresponding feedback is given to the user. This allows the user to be aware of the expected risks of the content to be executed and to take timely action based on the actual situation, thereby ensuring the safety of the customized solution execution to a certain extent.
[0045] The vehicle of this application includes a memory and a processor, wherein the memory stores a computer program, which, when executed by the processor, implements the method described above.
[0046] The server of this application includes a processor and a memory, wherein the memory stores a computer program, which, when executed by the processor, implements the above-described method.
[0047] The computer-readable storage medium of this application stores a computer program that, when executed by one or more processors, implements the above-described method.
[0048] In this application, during the execution of the customized solution, the risk level of each upcoming action or function is determined based on the pre-set safety rules for the execution actions and vehicle status information, as well as the real-time status information of the vehicle. The user is then given corresponding feedback, enabling them to be aware of the expected risks of the upcoming execution and to take timely action based on the actual situation. This, to a certain extent, ensures the safety of the customized solution execution.
[0049] Additional aspects and advantages of embodiments of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of embodiments of this application. Attached Figure Description
[0050] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, wherein:
[0051] Figure 1 This is a flowchart illustrating the interaction method of this application;
[0052] Figure 2 This is a scenario diagram illustrating the interaction method of this application;
[0053] Figure 3 This is a scenario diagram illustrating the interaction method of this application;
[0054] Figure 4 This is a scenario diagram illustrating the interaction method of this application;
[0055] Figure 5 This is a scenario diagram illustrating the interaction method of this application;
[0056] Figure 6 This is a scenario diagram illustrating the interaction method of this application;
[0057] Figure 7 This is a scenario diagram illustrating the interaction method of this application;
[0058] Figure 8 This is a scenario diagram illustrating the interaction method of this application;
[0059] Figure 9 This is a scenario diagram illustrating the interaction method of this application;
[0060] Figure 10 This is a scenario diagram illustrating the interaction method of this application;
[0061] Figure 11 This is a scenario diagram illustrating the interaction method of this application;
[0062] Figure 12 This is a scenario diagram illustrating the interaction method of this application;
[0063] Figure 13 This is a scenario diagram illustrating the interaction method of this application. Detailed Implementation
[0064] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the embodiments of this application, and should not be construed as limiting the embodiments of this application.
[0065] With the fast pace of life, users' demands for vehicles go beyond manual operation; they want more intelligent vehicles, and electric vehicles are gradually developing towards intelligence and personalization. For intelligent vehicles, users often need to manually operate multiple steps to achieve their personalized needs. Manual operation is mostly repetitive and simple, which is time-consuming. Furthermore, manual operation often cannot meet users' more personalized needs, thus reducing the user experience of intelligent vehicles.
[0066] Currently, some technologies offer users simple customization options for in-vehicle system functions. Users can use trigger conditions and execution commands to execute several actions within the customized solution when the trigger conditions are met during vehicle use. However, these customized solutions execute multiple actions sequentially according to the order they were added during customization, covering relatively simple and limited scenarios. This may not meet the customization needs of some users, resulting in a poor user experience. To improve the intelligence of customized solutions and enhance their ability to handle complex scenarios, execution functions and various forms of execution commands can be added to enrich the execution logic. This allows for more complex perception and execution capabilities, supporting asynchronous execution of multiple actions or long-term monitoring of different conditions or vehicle state changes in states such as unmanned or prolonged driving. However, customized solutions run in the background of the in-vehicle system for extended periods. During the entire monitoring, triggering, and execution process, vehicle state changes are diverse, and the execution environment of the actions and / or functions may also change. This can lead to situations ranging from minor disturbances and interruptions to serious threats to driving safety and personal and property safety. Therefore, ensuring vehicle safety during the implementation of customized solutions is extremely important.
[0067] Please see Figure 1 This application provides an interaction method including:
[0068] 01: When the customized solution for the customized in-vehicle system functions is triggered under the given conditions, the safety risk level of each action and / or function in the customized solution is confirmed during the execution of the customized solution, based on the pre-set safety rules for the execution actions and vehicle status information and the current status information of the vehicle.
[0069] 02: Based on the security risk level, send corresponding execution status feedback to the user when each execution action and / or execution function is executed.
[0070] This application also provides a vehicle, which includes a memory and a processor. The interaction method of this application can be implemented by the vehicle of this application. Specifically, the memory stores a computer program, and the processor is used to, when the customized scheme of the customized in-vehicle system functions is triggered under the triggering conditions, determine the safety risk level of each execution action and / or execution function in the customized scheme according to the preset safety rules of the execution action and vehicle status information and the current status information of the vehicle, and to send corresponding execution status feedback to the user when each execution action and / or execution function is executed according to the safety risk level.
[0071] A customized scheme is a user-created in-vehicle system function that automatically executes a series of actions and / or functions when the vehicle meets certain trigger conditions. Users can customize in-vehicle system function schemes through relevant applications on their terminal devices, adding trigger conditions, actions, and / or functions. After filling in the relevant information and completing the settings, the customized scheme can be saved. The saved customized scheme will be synchronized to the vehicle so that it can take effect on the vehicle. An action refers to an execution item that occurs only when the trigger condition is met, without any other sensing conditions. An execution function includes a relatively independent listening period, sensing conditions, and sub-actions and / or sub-functions. When the trigger condition is met, the listening execution function is started. Listening for the execution function means determining whether to execute a sub-action within the listening period based on whether the sensing condition is met, rather than directly executing the sub-action.
[0072] In this application, a safety risk level is established for all user-added actions (including sub-actions within execution functions) under different vehicle states, forming pre-defined safety rules for actions and vehicle state information, which can be stored in advance. After a customized scheme is triggered, these safety rules and the vehicle's current state information are used to confirm the safety risk level of the actions and / or functions. The vehicle state information may include the vehicle's gear position, speed, and battery level, such as whether the vehicle is currently in park (P), the current speed, and the estimated remaining battery level.
[0073] Safety risk levels are categorized into multiple levels based on the degree of risk that an action might pose when performed under different vehicle conditions. For example, there are levels such as: actions with immediate risk that cannot be performed, actions with immediate risk that can be performed after user confirmation, actions with potential risk that can be performed without user confirmation, and actions that can be performed directly. Different execution and feedback strategies are developed for each safety risk level.
[0074] During vehicle use, the vehicle senses whether the triggering conditions are met by using multi-dimensional information from inside and outside the vehicle, as well as user input, to execute the customized plan. During the execution of the customized plan after it is triggered, the vehicle's state may change for each action or function. Therefore, it is necessary to combine real-time vehicle state information with each action and / or function to confirm the safety risk level of the execution and send corresponding execution status feedback to the user, ensuring the customized plan can be executed safely.
[0075] This application provides different devices to provide execution status feedback to the user depending on whether there are people in the cabin during the execution of the customized solution. For example, for a customized solution, the triggering conditions are: Monday to Friday at 8:00 AM, the interior temperature of the car is greater than 40 degrees Celsius, and the vehicle is at home. The execution actions and / or execution functions include: 1. Logic action group: If the weather is not rainy, execute the window ventilation mode and the air conditioning rapid cooling mode; otherwise, execute the air conditioning rapid cooling mode; 2. Execute the cabin constant temperature function: If the interior temperature is detected to reach 25 degrees Celsius within 15 minutes after the start of action I, turn off the air conditioning rapid mode and maintain the cabin constant temperature at 25 degrees Celsius; 3. Execute the instant cooling function: Simultaneously with the cabin constant temperature function, the monitoring is turned on. Within 15 minutes after the start of action I, when the driver gets into the car, the monitoring and execution of the cabin constant temperature function (a sub-execution action of this function) ends, and the instant cooling operation is executed, first adjusting the cabin to a cool state, then going to the company in the exploration mode, and playing today's recommended music.
[0076] It's understandable that during the execution of Action I and the listening process for the execution of Function II, the user may not be in the vehicle cabin. In this case, feedback information can be sent to the user through a terminal device that communicates with the vehicle. After the driver gets into the vehicle, feedback can be provided to the user through the central control screen, combined with push notification cards in the user interface and TTS voice broadcasts, among other methods.
[0077] In summary, during the execution of the customized solution, based on the pre-set safety rules for the execution actions and vehicle status information, as well as the vehicle's real-time status information, the risk level of each upcoming execution action or function is determined, and corresponding feedback is provided to the user. This allows the user to be aware of the expected risks of the upcoming execution and to take timely action based on the actual situation, thus ensuring the safety of the customized solution execution to a certain extent.
[0078] Please see Figure 2 and Figure 3 The interaction method also includes the following steps:
[0079] Before implementing a customized solution, check for any security risks.
[0080] If the customized solution includes actions and / or functions with a security risk level greater than or equal to the preset security risk level, the customized solution is confirmed to have a security risk and a confirmation message is sent to the user to confirm whether to execute the customized solution.
[0081] In response to the user's confirmation of the execution plan, the customized plan will be executed.
[0082] The processor is used to detect whether there are security risks in the customized solution before the customized solution is executed, and to confirm that there are security risks in the customized solution and send a confirmation message to the user whether to execute the customized solution if the customized solution includes an action and / or function with a security risk level greater than or equal to the preset security risk level, and to start executing the customized solution in response to the user's feedback confirming the execution of the solution.
[0083] Before the customized plan is executed, the safety risk level of all actions and / or functions in the customized plan will be confirmed based on the aforementioned safety rules and the vehicle status information at the time the customized plan is triggered. If there is at least one action and / or function with a safety risk level greater than or equal to the preset safety risk level, a confirmation message will be sent to the user to confirm whether to execute the customized plan. This allows the user to have the psychological expectation that there may be actions with a high safety risk level in the customized plan, so that they can prepare countermeasures in advance.
[0084] Based on the aforementioned classification of security risk levels, for example, security risk levels that present immediate risks and are executable only after user confirmation can be classified as preset security risk levels. When there is at least one execution action or function in the customized solution with a security risk level greater than or equal to that security risk level, the execution of the entire customized solution requires secondary confirmation from the user. Only after the user confirms that it is executable can the customized solution begin to be executed; otherwise, the customized solution will not be executed.
[0085] If there are users in the cabin, pre-set sound effects can be played to inform them that the customized plan is about to be implemented. A TTS voice prompt will then read, "Confirm implementation of [Customized Plan Name]? Please ensure the vehicle environment is safe before implementation." Simultaneously, relevant notification information will be pushed to the in-vehicle system's user interface in the form of cards, providing confirmation and cancellation buttons for the user to choose between. Figure 2 As shown.
[0086] If there are no users in the cabin, similar reminders can be sent to the user via the terminal, such as push notifications. Unlike in-cabin reminders, terminal reminders do not have preset sound effects; the sound effects must adhere to the terminal's message reminder rules. For example, a push notification could ask: "Confirm execution of [Customized Solution Name]? Please ensure the vehicle environment is safe before execution." The user can confirm or cancel the operation based on the notification. Simultaneously, to prevent the vehicle from misjudging whether someone is in the cabin, the push notification information will also be displayed as a card in the in-vehicle system's user interface, but without playing related sound effects or TTS (Text-to-Speech) announcements. Figure 3 As shown.
[0087] Therefore, before the customized solution is executed, the overall security risks of the solution will be confirmed. If the customized solution includes execution actions and / or execution functions with a high level of security risk, it can only be executed after the user confirms it a second time. This allows the user to have an overall risk expectation before the customized solution is executed, and the user can confirm whether to execute it based on the actual situation, which can ensure the security of the customized solution execution to a certain extent.
[0088] Please see Figure 4 and Figure 5 The interaction method also includes the following steps:
[0089] If the customized solution does not include any execution actions or functions with a security risk level greater than or equal to the preset security risk level, confirm that the customized solution does not pose a security risk and send feedback to the user that the customized solution has started execution.
[0090] The processor is used to confirm that there is no security risk in the customized solution and send feedback to the user that the customized solution has started execution, provided that the customized solution does not include any execution actions or functions with a security risk level greater than or equal to the preset security risk level.
[0091] If, at the trigger time, it is confirmed that the execution risk of the actions and / or functions in the customized solution is lower than the preset security risk level, the execution of the customized solution can begin directly without user confirmation. However, the security risk level will still be re-confirmed and appropriate processing will be performed when each action and / or function in the customized solution is executed.
[0092] If there are users in the cabin, a pre-set sound effect can be played to notify them that the customized plan has been triggered and started execution. A TTS voice announcement will be broadcast: "[Customized Plan Name] Triggered, Execution Begins." Simultaneously, relevant notification information will be pushed to the in-vehicle system's user interface in the form of a card, which includes a cancellation button. Users can actively cancel the execution of the customized plan at any time as needed. Figure 4 As shown.
[0093] If there are no users in the cabin, a similar reminder can be sent to the user via the terminal, such as a push notification: "[Customized Plan Name] Triggered, Start Execution." Users can also cancel the notification. To prevent the vehicle from misjudging whether someone is in the cabin, the push notification information will also be displayed as a card in the in-vehicle system's user interface, but without accompanying sound effects or TTS (Text-to-Speech) announcements. Figure 5 As shown.
[0094] In this way, once the overall security of the customized solution is confirmed to be high, the customized solution will automatically begin execution and inform the user, so that the user can mentally anticipate the action to be performed and will not feel surprised by the execution.
[0095] Please see Figures 6 to 8 The method further includes:
[0096] When the currently executing action or function is being executed, the user interface of the vehicle system fully displays the status information of the customized solution being executed in the first state.
[0097] When the current action or function is completed and the time interval between the next action or function to be executed is greater than a predetermined time interval, the status information switches from the first state to the second state, and the status information of the customized solution being executed is displayed in a thumbnail.
[0098] When the execution action or function to be executed begins, the status information switches from the second state to the first state.
[0099] The processor is used to fully display the status information of the customized solution being executed in a first state on the user interface of the vehicle system when the current execution action or the current execution function is being executed, and to switch the status information from the first state to a second state when the current execution action or the current execution function is completed and the time interval between the next execution action or execution function to be executed is greater than a predetermined time interval, thereby displaying a simplified version of the status information of the customized solution being executed, and to switch the status information from the second state to the first state when the execution action or execution function to be executed begins to be executed.
[0100] During the execution of the customized solution, the user interface of the in-vehicle system fully displays the status information of the customized solution in its initial state. For example, the card is fully expanded to show the user the execution status of the customized solution, and the card provides the user with interactive options to stop the execution of the customized solution. For example, the card displays "Executing [Customized Solution Name]" and provides a stop button. Figure 7 As shown, for the currently executing function, the message "Executing [Custom Scheme Name] [Function Name]" can be displayed. For unnamed executing functions, the message "Executing [Custom Scheme Name]" can be displayed. Pre-defined sound effects can be played to inform the user that the customized scheme or executing function is in progress. The text information of the execution action and / or executing function can be omitted from the card to avoid excessive information affecting driving safety. Users can obtain execution details through voice announcements before and after the execution of the action or function, such as... Figure 8 As shown.
[0101] Because customized plans take a long time to run, there may be situations where a customized plan, although triggered, does not perform any actions for a period of time. For example, it may be in a listening state while executing a certain function. In this case, to avoid affecting the push of other information, after the current action or function has completed and there are no pending actions or functions to be executed within a predetermined time interval, the card can be collapsed into a second state, i.e., a minimized state, to weaken the display of the execution status. The displayed information could be "Executing [Customized Plan Name]", but the stop button would not be displayed. The predetermined time interval can be 20 seconds, 30 seconds, etc., and is not limited here. Figure 6 As shown.
[0102] When in the second state, when the subsequent execution action or function begins to execute, it will switch back to the first state and display the card information in full according to the security risk level of the execution action or function.
[0103] In addition, when in the second state, users can interact with the card to switch it back to the first state and fully display the card information.
[0104] In this way, based on the execution status of the actions during the customized solution process, the user is prompted with different statuses. The prompting effect is enhanced when it is necessary, while the prompting effect is weakened when the solution is triggered but there is no execution content yet.
[0105] The safety risk levels are divided into four levels, from highest to lowest: Level 1, Level 2, Level 3, and Level 4.
[0106] Step 02 includes:
[0107] If the security risk level is at the highest level, send feedback to the user that the action cannot be performed.
[0108] The processor is used to send feedback to the user that an action cannot be performed when the security risk level is the highest level.
[0109] In this application, based on the degree of risk that may be caused by performing the action under the current vehicle condition, the safety risk level is divided into four levels from high to low:
[0110] The first level of safety risk refers to actions that pose an immediate risk and are not feasible.
[0111] The second level of security risk refers to actions that pose an immediate risk but can be executed after user confirmation.
[0112] The third level of security risk refers to actions that may pose a risk but can be performed without user confirmation.
[0113] The actions to be taken at the fourth level of safety risk are those that can be taken directly.
[0114] When the current action is confirmed to be at the highest safety risk level, it can be considered that performing the action in the current state would pose an extremely high safety risk. For example, adjusting the seat while the vehicle is traveling at a speed exceeding a predetermined speed. For such actions, if there is a user in the cabin, the action will not be executed, and relevant feedback will be broadcast to the user via TTS (Traffic Response System). For example, it could broadcast, "Action execution failed; seat adjustment is not supported while driving."
[0115] To minimize disruption to users when they are not in the cockpit, no feedback may be provided.
[0116] After the feedback that the current action will not be executed is broadcast, the customized solution will continue to execute without stopping. Furthermore, no related prompts will be displayed in the user interface; the interface will still display "Executing [Customized Solution Name]" in the card, such as... Figure 7 As shown.
[0117] If it is determined that performing an action poses an extremely high safety risk under the current vehicle condition, the relevant action will not be performed, and feedback will be provided to the user.
[0118] Please see Figure 9 and Figure 10 Step 02 includes:
[0119] If the security risk level is the second level, send the user feedback that there is an immediate risk of executing the action and a confirmation message on whether to execute the action.
[0120] The processor is used to send feedback to the user that there is an immediate risk of executing an action, as well as confirmation information on whether to execute the action, when the security risk level is the second security risk level.
[0121] The second level of security risk refers to actions that pose an immediate risk but can be executed after user confirmation.
[0122] When the current action is confirmed to be at the second safety risk level, it can be considered that performing the action in the current state may pose a high safety risk, and the user should be consulted before proceeding. For example, opening a car window when the vehicle speed exceeds a predetermined speed. For such actions, if there is a user in the cabin, a text-to-speech (TTS) announcement can be made, and a card in the user interface can be displayed indicating an immediate risk associated with the action, along with secondary confirmation information. For example, the TTS could announce, "The [Action Name] of [Customized Solution Name] may pose a risk. Confirm execution?", and the card could display: "The [Action Name] of [Customized Solution Name] may pose a risk. Confirm execution?" A button for the user to confirm or cancel execution should be provided, such as... Figure 8 As shown.
[0123] If there are no users in the cabin, a similar reminder can be sent to the user via the terminal, such as a push notification: "The [Action Name] of [Customized Solution Name] may pose a risk. Confirm execution?" A button for the user to confirm or cancel execution will be provided. Simultaneously, to prevent the vehicle from misjudging the presence of anyone in the cabin, the push notification information will also be displayed as a card in the in-vehicle system's user interface, but without accompanying sound effects or TTS (Text-to-Speech) announcements. Figure 9 As shown.
[0124] After user confirmation, the action will be executed, and the prompt message on the relevant interface will change to "Executing [Customized Solution Name]", such as... Figure 7 As shown.
[0125] In this way, if it is determined that there is a high safety risk in performing an action under the current vehicle status, a risk warning will be given to the user, and the action can only be performed after the user confirms it a second time, thus ensuring the safety of the action.
[0126] Please see Figure 10 and Figure 11 Step 02 includes:
[0127] If the security risk level is level 3, send feedback to the user that the action is about to be executed.
[0128] The processor is used to send feedback to the user that an action is about to be performed when the security risk level is level three.
[0129] The third level of security risk refers to actions that may pose a risk but can be performed without user confirmation.
[0130] When the current action is confirmed to be at the third safety risk level, it can be assumed that performing the action in the current state may pose a low safety risk, but it can be performed without asking the user. For example, switching the driving mode from park to comfort mode when not in park. For such actions, if there is a user in the cabin, the action can be announced via TTS and displayed as a card in the user interface. For example, TTS could announce "About to perform [Action Name]", and the card could display: About to perform [Action Name], such as... Figure 10 As shown.
[0131] If there are no users in the cabin, similar reminders can be sent to the user via the terminal, such as a push notification: "[Action Name] is about to be executed." Simultaneously, to prevent the vehicle from misjudging the presence of anyone in the cabin, the push notification information will also be displayed as a card in the in-vehicle system's user interface, but without accompanying sound effects or TTS (Text-to-Speech) announcements. Figure 11 As shown.
[0132] It should be understood that while there may be execution risks associated with actions at the third safety risk level, the probability of such risks is generally low. To ensure the overall smooth execution of the customized solution, only feedback similar to that described above will be provided, without risk warnings to the user or requiring secondary confirmation. Furthermore, a cancel button will be provided in the user interface of the in-vehicle system or in the information pushed to the terminal, allowing users to proactively cancel the execution of the customized solution at any time as needed.
[0133] In this way, if it is determined that there is a low safety risk in performing an action under the current vehicle status, the user is informed that the action is about to be performed, but the action can be performed without the user's confirmation, effectively balancing safety and smooth execution.
[0134] Step 02 includes:
[0135] When the security risk level is level four, after the action is completed, the user will receive feedback on the execution of the action.
[0136] The processor is used to send execution feedback to the user after the execution of an action is completed, when the security risk level is fourth.
[0137] The actions to be taken at the fourth level of safety risk are those that can be taken directly.
[0138] When the current action is confirmed to be at the fourth security risk level, it can be considered that performing the action under the current state poses virtually no security risk, and can be executed directly. For example, playing today's recommended songs. For actions like this, if there are users in the cockpit, after the action is completed, the user can receive feedback via TTS (Text-to-Speech) or the content of the action can be directly read aloud so the user is aware that the action has been performed.
[0139] If there are no users in the cockpit, it is not necessary to prompt the users with specific action information.
[0140] In this way, if the current vehicle status is determined and there is basically no safety risk in performing the action, the user is directly given feedback that the action has been performed after it is completed, effectively balancing safety and smooth execution.
[0141] Step 01 includes:
[0142] When a customized solution includes an execution function, the security risk level of the execution function is determined based on the highest security risk level of each executable sub-execution action within the execution function.
[0143] The processor is used to determine the security risk level of an execution function, based on the highest security risk level of each executable sub-execution action within the execution function, when the customized scheme includes the execution function.
[0144] In this application, the execution function is considered as a whole, and its security risk level is determined by the highest security risk level of its feasible sub-execution actions. The executable sub-execution actions are those classified as security risk levels two through four in the aforementioned security risk level classification. That is, sub-execution actions of the first security risk level within the execution function are not considered.
[0145] If the highest security risk level among the executable sub-actions is the second security risk level, the entire execution function will be processed according to the execution actions of the second security risk level. This means that the execution function will be prompted that there is an execution risk and that user confirmation is required before execution can continue. However, no similar prompts will be given when the execution function reaches that sub-action.
[0146] If the highest security risk level among the executable sub-actions is the third security risk level, the entire execution function will be processed according to the execution action of the third security risk level. That is, the execution function will be prompted that it is about to be executed, and the execution of the function does not require user confirmation.
[0147] If the highest security risk level among the executable sub-actions is the fourth security risk level, then the execution function as a whole will be processed in accordance with the execution action of the fourth security risk level, that is, the execution function will be executed directly.
[0148] In this way, the security risks of the execution function are determined based on the highest security risk level of the sub-execution actions in the execution function, and the security risk warning is given as a whole for the execution function. The risk warning for the execution function is more holistic and avoids frequent warnings when there are many sub-execution actions.
[0149] Interaction methods also include:
[0150] In response to the user's stop operation during the execution of the customized solution, the customized solution is stopped.
[0151] The processor is used to respond to a user's stop operation during the execution of a customized solution, thereby stopping the execution of the customized solution.
[0152] During the execution of the customized solution, although some actions are confirmed to have minimal or low security risks, a safety measure is provided to allow users to actively stop the process in case of unforeseen circumstances.
[0153] In this way, users can stop the process at any stage of the customized solution execution, providing users with proactive security measures.
[0154] After all actions and / or functions in the customized solution have been executed, notify the user that the customized solution has been completed.
[0155] If there are users in the cabin, after the customized solution is completed, a sound effect indicating the end of the customized solution can be played, and a text-to-speech (TTS) announcement can be made stating "[Customized Solution Name] Completed". The card will also display: "[Customized Solution Name] Completed". Figure 12 As shown.
[0156] If there are no users in the cabin, send a notification to the user stating "[Customized Solution Name] Execution Completed". Figure 13 As shown.
[0157] This application also provides an interaction method, including:
[0158] When the customized solution for the customized vehicle system functions is triggered under the given conditions, the safety risk level of each execution action and / or execution function in the customized solution is confirmed during the execution of the customized solution, based on the pre-set safety rules for execution actions and vehicle status information and the current status information reported by the vehicle.
[0159] Generate execution instructions based on the security risk level;
[0160] The execution instructions are sent to the vehicle so that the vehicle can execute the instructions generated according to the safety risk level, and send corresponding execution status feedback to the user when each execution action and / or execution function is executed.
[0161] This application also provides a server, which includes a memory and a processor. The interaction method of this application can be implemented by the server of this application. Specifically, the memory stores a computer program, and the processor is used to, when the customized scheme of the customized vehicle system function is triggered under the triggering conditions, determine the safety risk level of each execution action and / or execution function in the customized scheme according to the preset safety rules of execution actions and vehicle status information and the current status information reported by the vehicle, during the execution of the customized scheme, and generate execution instructions according to the safety risk level, and send the execution instructions to the vehicle so that the vehicle executes the execution instructions generated according to the safety risk level, and send corresponding execution status feedback to the user when each execution action and / or execution function is executed.
[0162] It should be noted that the difference between this interaction method and the aforementioned interaction methods is that, in this interaction, the security rules are stored on the vehicle's server. The confirmation of the security risk level of the currently executed action and / or function, as well as the execution command for the currently executed action and / or function based on the confirmed security risk level, are all generated on the server. The execution command includes the action to be executed and the execution strategy for that action, such as not executing, asking the user whether to execute, or executing directly. After being issued by the server, the vehicle executes the command. The user interface in the in-vehicle system or terminal device can be found in the explanations of the relevant sections above, and will not be repeated here.
[0163] This application also provides a computer-readable storage medium containing a computer program. When the computer program is executed by one or more processors, it causes the one or more processors to perform the interactive method of this application.
[0164] In the description of this specification, the references to terms such as "some embodiments," "in one example," "exemplarily," etc., indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of this application. 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.
[0165] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the function involved, as will be understood by those skilled in the art to which embodiments of this application pertain.
[0166] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.
Claims
1. An interaction method, characterized in that, The method includes: When the customized solution for the customized in-vehicle system functions is triggered under the given conditions, the safety risk level of each execution action and / or execution function in the customized solution is confirmed during the execution of the customized solution, based on the pre-set safety rules for execution actions and vehicle status information and the current status information of the vehicle. Based on the security risk level, send corresponding execution status feedback to the user when each execution action and / or execution function is executed; The method further includes: When the currently executing action or function is being executed, the user interface of the vehicle system fully displays the status information of the customized solution being executed in a first state. When the current action or function is completed and the time interval between the next action or function to be executed is greater than a predetermined time interval, the status information switches from the first state to the second state, which briefly displays the status information of the customized solution being executed. When the execution action or function to be executed begins, the state information switches from the second state to the first state.
2. The method according to claim 1, characterized in that, The method further includes: Before the customized solution is executed, it is checked whether there are any security risks in the customized solution; If the customized solution includes an action and / or function with a security risk level greater than or equal to a preset security risk level, the customized solution is confirmed to have a security risk and a confirmation message is sent to the user to confirm whether to execute the customized solution. In response to the user's confirmation of the implementation of the solution, the customized solution is executed.
3. The method according to claim 2, characterized in that, The method further includes: If the customized solution does not include any execution actions or functions with a security risk level greater than or equal to the preset security risk level, the customized solution is confirmed to have no security risk and feedback is sent to the user indicating that the customized solution has started execution.
4. The method according to claim 1, characterized in that, The security risk levels include a first security risk level, a second security risk level, a third security risk level, and a fourth security risk level, with the risk level ranging from high to low. The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes: If the security risk level is the first security risk level, a feedback message will be sent to the user indicating that the action cannot be performed.
5. The method according to claim 4, characterized in that, The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes: If the security risk level is the second security risk level, the user is sent feedback indicating that there is an immediate risk of executing the action, as well as confirmation information on whether to execute the action.
6. The method according to claim 4, characterized in that, The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes: If the security risk level is the third security risk level, a feedback message will be sent to the user indicating that the action is about to be performed.
7. The method according to claim 4, characterized in that, The step of sending corresponding execution status feedback to the user based on the security risk level during each execution action and / or function execution includes: If the security risk level is the fourth security risk level, after the execution action is completed, the user will be given execution feedback on the execution action.
8. The method according to claim 4, characterized in that, During the execution of the customized solution, confirming the security risk level of each execution action and / or execution function in the customized solution includes: When the customized solution includes the execution function, the security risk level of the execution function is determined based on the highest security risk level of each executable sub-execution action in the execution function.
9. The method according to any one of claims 1-8, characterized in that, The method further includes: In response to the user's stop operation during the execution of the customized solution, the execution of the customized solution is stopped.
10. An interaction method, characterized in that, The method includes: When the customized solution for the customized vehicle system functions is triggered under the given conditions, the safety risk level of each execution action and / or execution function in the customized solution is confirmed during the execution of the customized solution, based on the pre-set safety rules for execution actions and vehicle status information and the current status information reported by the vehicle. Generate execution instructions based on the security risk level; The execution command is sent to the vehicle so that the vehicle executes the execution command generated according to the safety risk level, and sends corresponding execution status feedback to the user when each execution action and / or execution function is executed; and when the vehicle is executing the current execution action or the current execution function, the user interface of the vehicle system fully displays the status information of the customized solution being executed in a first state. When the current action or function is completed and the time interval between the next action or function to be executed is greater than a predetermined time interval, the status information switches from the first state to the second state, which briefly displays the status information of the customized solution being executed. When the execution action or function to be executed begins, the state information switches from the second state to the first state.
11. A vehicle, characterized in that, The vehicle includes a memory and a processor, the memory storing a computer program that, when executed by the processor, implements the method according to any one of claims 1-9.
12. A server, characterized in that, The vehicle includes a memory and a processor, the memory storing a computer program that, when executed by the processor, implements the method of claim 10.
13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by one or more processors, implements the method as described in any one of claims 1-11.