Definition Method of In-vehicle Scenario Mode, In-vehicle Device and Medium Thereof

Abstract

The present application relates to the field of intelligent driving technologies, and in particular to a method for defining an in-vehicle scenario mode, an in-vehicle device, and a medium thereof. The method for defining an in-vehicle scenario mode in the present application provides users with semi-preseted in-vehicle scenario modes, and supports users to modify the functions of the semi-preseted in-vehicle scenario modes according to their needs (such as adding or deleting functions). Moreover, after the user modifies the functions, the in-vehicle device will perform validity detection on the modified in-vehicle scenario mode by the user, including detection of the completeness of the modified in-vehicle scenario mode, mutual exclusion operation detection, and so on. After all these detections pass, the user can use the modified in-vehicle scenario mode, or rather, the modified in-vehicle scenario mode can take effect and be executed. During the validity detection process, the in-vehicle device will feedback to the user the reasons why the modified in-vehicle scenario mode cannot take effect, and guide the user on how to modify it to further improve the user experience.

Description

Technical Field

[0001] The present application relates to the field of intelligent driving technology, and in particular to a method for defining an in-vehicle scenario mode, an in-vehicle device, and a medium thereof. Background Art

[0002] With the widespread use of smart vehicles, users' expectations for intelligent cockpits are growing. To meet users' needs for cockpit interaction while driving, major manufacturers have designed different cockpit scenarios. Some cockpit scenarios, such as Sentry Mode, require certain detection and trigger conditions to be met before providing corresponding services. Other scenarios, such as Nap Mode, only require the corresponding trigger conditions to be met before providing corresponding services.

[0003] However, most of these cockpit scene modes are only available to users and cannot be changed. Therefore, if the user wants to add or reduce some functions in a certain cockpit scene mode, it cannot be achieved with the current solution. Summary of the Invention

[0004] In order to solve the above technical problems, the present application provides a method for defining an in-vehicle scenario mode, an in-vehicle device and a computer-readable storage medium thereof.

[0005] In a first aspect, the present application provides a method for defining a vehicle-mounted scenario mode, which is applied to a first electronic device, and includes: detecting a user's modification instruction for a target vehicle-mounted scenario mode; modifying the target vehicle-mounted scenario mode according to the modification instruction to obtain a modified vehicle-mounted scenario mode; performing a validity test on the modified vehicle-mounted scenario mode, and deciding whether to update the target vehicle-mounted scenario mode based on the test result, wherein the target vehicle-mounted scenario mode is updated to the modified vehicle-mounted scenario mode corresponding to the validity test of the first electronic device after the modified vehicle-mounted scenario mode passes.

[0006] That is, the first electronic device modifies the target vehicle scenario mode according to the modification instruction, then performs a validity check on the modified target scenario mode. After the modified target scenario mode passes the validity check of the first electronic device, the target vehicle scenario mode is updated to the modified vehicle scenario mode, or in other words, the modified vehicle scenario mode can take effect and be executed. The validity check includes a completeness check of the modified vehicle scenario mode, a mutually exclusive operation check, and the like. This method can prevent the modified vehicle scenario mode from failing during execution, improving the user experience.

[0007] In combination with the first aspect, in a possible implementation manner of the first aspect, the method further includes: corresponding to the modified in-vehicle scenario mode failing the validity detection of the first electronic device, not updating the target in-vehicle scenario mode. That is, if the modified in-vehicle scenario mode fails the validity detection of the first electronic device, the original target in-vehicle scenario mode is kept unchanged, that is, the target in-vehicle scenario mode is not updated. By this method, it can be ensured that the updated target in-vehicle scenario modes are all executable, which can improve the user experience.

[0008] In combination with the first aspect and the above possible implementation manner, in a possible implementation manner of the first aspect, performing validity detection on the modified in-vehicle scenario mode includes: determining the validity detection conditions corresponding to the modified in-vehicle scenario mode, and performing validity detection on the modified in-vehicle scenario mode according to the corresponding validity detection conditions. That is, since each in-vehicle scenario mode has different functions, each in-vehicle scenario mode has corresponding validity detection conditions. After modifying the target in-vehicle scenario mode, the modified in-vehicle scenario mode is detected by using the validity detection conditions corresponding to the target in-vehicle scenario mode to ensure that the updated target in-vehicle scenario modes can all meet the corresponding validity detection conditions.

[0009] In combination with the first aspect and the above possible implementation manner, in a possible implementation manner of the first aspect, the validity detection at least includes a completeness detection and a mutual exclusion operation detection on the function corresponding to the modified in-vehicle scenario mode.

[0010] Among them, the completeness test refers to the integrity detection of the function of the in-vehicle scenario mode modified by the user to determine whether the function of the modified in-vehicle scenario mode still conforms to the logic of the mode design, etc. For example, for the Sentry Mode, the detection function of the vehicle parking position cannot be deleted. If the user deletes the detection function of the vehicle parking position for the sake of reducing power consumption, then the modified Sentry Mode does not meet the completeness requirements, that is, it cannot pass the validity detection. Another example is that the Sentry Mode generally has various types of risk detections, such as the risk detection of unknown persons approaching, the risk detection of the door / trunk opening, the risk detection of movement and sound in the cockpit, and the risk detection of vehicle tilt. For the Sentry Mode, at least one of the risk detections of unknown persons approaching and the risk detection of the door / trunk opening must be retained to determine whether an unknown person opens the door / trunk. Therefore, when the user deletes the functions of both the risk detection of unknown persons approaching and the risk detection of the door / trunk opening for other purposes such as reducing power consumption, then the modified Sentry Mode does not meet the completeness requirements, that is, it cannot pass the validity detection.

[0011] The mutually exclusive operation detection refers to the detection from the perspective of safety for vehicle driving norms, user personal safety, etc. For example, in the case of the child forgetting reminder mode, for safety reasons, the user cannot delete or disable the voice function and screen clicks to prevent children from accidentally touching and causing danger.

[0012] Through the above-mentioned validity detection, it can be ensured that the updated in-vehicle scenario mode will not have errors during execution due to non-compliance with the completeness requirements or mutually exclusive operation detection. It can ensure the safety of the updated in-vehicle scenario mode and improve the user experience.

[0013] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the target in-vehicle scenario mode includes at least one scenario mode, and each scenario mode represents a combination of specific working modes of multiple devices in the vehicle where the first electronic device is located. That is to say, the scenario mode refers to a combination of specific working modes of multiple devices in the vehicle where the first electronic device is located. For example, in the scenario mode of the sentry mode, the vehicle components corresponding to the scenario mode at least include the alarm light and the alarm audio generating part, and the working mode is that the alarm light flashes and the alarm audio generating part emits an alarm voice. In the car wash mode, the vehicle components corresponding to this scenario mode at least include the windows and the in-vehicle charging interface, and the corresponding working mode is that the windows are closed and the in-vehicle charging interface is automatically powered off. In the entertainment mode, when parked, the seat automatically adjusts according to the user's body position, the in-vehicle surround sound effect is turned on, and external entertainment devices such as game pads are supported.

[0014] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the target in-vehicle scenario mode includes at least any one of the following scenario modes: the nap mode, the child left-behind reminder mode, the car wash mode, the entertainment mode, or the sentry mode.

[0015] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the method further includes: displaying on the first electronic device the reason why the modified in-vehicle scenario mode fails the validity detection. That is to say, in the case where the modified in-vehicle scenario mode fails the validity detection, the reason why the modified in-vehicle scenario mode fails the validity detection can be displayed on the first electronic device, so that the user can make adaptive adjustments according to the displayed reason for failing the validity detection, improving the user experience.

[0016] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the method further includes: sending the modified in-vehicle scenario mode to the second electronic device, where the sent modified in-vehicle scenario mode can enable the second electronic device to update the target in-vehicle scenario mode on the second electronic device. That is to say, the process of updating the target in-vehicle scenario mode can be carried out on the first electronic device or on the second electronic device.

[0017] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the method further includes: corresponding to the modified in-vehicle scenario mode failing the validity detection of the first electronic device, not updating the target in-vehicle scenario mode, and sending a second message, where the second message is used to display, on the second electronic device, the reason why the modified in-vehicle scenario mode fails the validity detection. That is, the reason why the modified in-vehicle scenario mode fails the validity detection can be displayed on the first electronic device, or the reason why the modified in-vehicle scenario mode fails the validity detection can be displayed on the second electronic device.

[0018] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the first electronic device includes an in-vehicle device, and the second electronic device includes a smart phone or a tablet computer.

[0019] Combined with the first aspect and the above possible implementation manners, in a possible implementation manner of the first aspect, the first electronic device includes a cockpit controller, and the cockpit controller includes a detection module, where the detection module is used to perform validity detection on the modified in-vehicle scenario mode.

[0020] In a second aspect, an embodiment of the present application further provides an electronic device, which includes a memory storing computer program instructions; a processor, where the processor is coupled to the memory, and when the computer program instructions stored in the memory are executed by the processor, the electronic device implements the method of any item in the above first aspect and any possible implementation manner of the first aspect or the method of any item in the above second aspect and any possible implementation manner of the second aspect.

[0021] In a third aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, characterized in that when the computer program is executed by a processor, the method of any item in the above first aspect and any possible implementation manner of the first aspect or the method of any item in the above second aspect and any possible implementation manner of the second aspect is implemented.

[0022] In a fourth aspect, an embodiment of the present application provides a computer program product, which when running on an electronic device, causes the electronic device to execute the method of any item in the above first aspect and any possible implementation manner of the first aspect or the method of any item in the above second aspect and any possible implementation manner of the second aspect.

[0023] It can be understood that the beneficial effects of the above second aspect to the fourth aspect can refer to the relevant descriptions in the above first aspect, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a schematic diagram of a scenario provided according to an embodiment of the present application;

[0025] Figure 2a is a schematic diagram of an interface for a user to activate an in-vehicle scenario mode provided according to an embodiment of the present application;

[0026] Figure 2b is a schematic diagram of an in-vehicle scenario mode for a user to activate the Sentry Mode provided according to an embodiment of the present application;

[0027] Figure 2c is a schematic diagram of an interface for a user to activate the Sentry Mode provided according to an embodiment of the present application;

[0028] Figure 2d is a schematic diagram of an interface for a user to customize an in-vehicle scenario mode provided according to an embodiment of the present application;

[0029] Figure 2e is a schematic diagram of an interface for a user to set the trigger condition for the Sentry Mode provided according to an embodiment of the present application;

[0030] Figure 2f is a schematic diagram of an interface for a modified Sentry Mode provided according to an embodiment of the present application;

[0031] Figure 2g is a schematic diagram of a prompt interface indicating that the modified Sentry Mode does not meet the requirements of functional completeness provided according to an embodiment of the present application;

[0032] Figure 3 is a schematic diagram of an interface for a user to activate an in-vehicle scenario mode provided according to an embodiment of the present application;

[0033] Figure 4 is a system structure diagram for updating an in-vehicle scenario mode on vehicle 01 provided according to an embodiment of the present application;

[0034] Figure 5 is a system structure diagram for updating an in-vehicle scenario mode on mobile phone 02 provided according to an embodiment of the present application;

[0035] Figure 6 is a schematic diagram of a method flow for customizing an in-vehicle scenario mode provided according to an embodiment of the present application. Detailed implementation manners

[0036] The following will describe various aspects of the illustrative embodiments using the terms commonly employed by those skilled in the art.

[0037] The present application provides a method for defining an in-vehicle scenario mode, an in-vehicle device, and a medium thereof. Hereinafter, terms commonly used by those skilled in the art will be used to describe various aspects of the illustrative embodiments. Among them, in the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may mean: A exists alone, A and B exist simultaneously, or B exists alone. In addition, in the description of the implementation of the present application, "a plurality of" means two or more than two.

[0038] Hereinafter, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first", "second", and "third" may explicitly or implicitly include one or more of such features.

[0039] A method for defining an in-vehicle scenario mode provided by various embodiments of the present application can be applied to terminal devices such as mobile phones, tablet computers, in-vehicle devices, wearable devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), etc. The embodiments of the present application do not impose any restrictions on the specific types of terminal devices.

[0040] Currently, many intelligent vehicles provide pre-set in-vehicle scenario modes for users to use. The in-vehicle scenario mode provides users with a scenario-based service. For example, when the environment where the vehicle is parked is not safe (such as the vehicle parking location is outside the familiar location determined by the user), then the user can turn on the sentry mode. In the sentry mode, after the vehicle is locked, the intelligent vehicle will continuously monitor the surrounding environment through camera devices such as front-view cameras and rear-view cameras, and make corresponding-level alarm responses according to different types of potential threats that occur around. Among them, different types of potential threats can be pre-set when pre-setting the in-vehicle scenario mode (more specifically, the pre-set sentry mode), and the present application does not limit this.

[0041] When the user needs to rest in the vehicle, the nap mode can be activated. In the nap mode, the in-vehicle device controls the seat of the intelligent vehicle to recline and sink automatically, providing a comfortable resting position for the user. At the same time, the in-vehicle device controls other devices in the vehicle to enter a specific working mode. For example, the in-vehicle device controls the vehicle air conditioner to switch to the automatic circulation mode to ensure sufficient oxygen in the vehicle and create a good resting environment for the user.

[0042] However, in this way, to ensure the logic and safety of the functions corresponding to various types of in-vehicle scenario modes, users can only use the functions and cannot modify (such as adding or deleting) the functions in a certain in-vehicle scenario mode according to their own needs. For example, in the nap mode, to ensure the safety of the users in the vehicle, the vehicle air conditioner will enter the automatic circulation mode to keep sufficient oxygen in the vehicle. When the user does not want the air conditioner to be automatically turned on in the nap mode, the user cannot delete the function of starting and turning on the air conditioner in the nap mode.

[0043] Moreover, for these pre-set in-vehicle scenario modes, before they are put into use, they will be repeatedly modified according to the feedback of the test users and require a certain R & D and test cycle. Therefore, they cannot meet the needs of various users in a timely manner. Moreover, different users have different needs, and these needs may even conflict with each other. For example, one type of user hopes that the air conditioner will be automatically turned on in the nap mode, while another type of user does not want the air conditioner to be automatically turned on in the nap mode. Therefore, these pre-set in-vehicle scenario modes cannot meet the personalized needs of different users even after R & D and testing.

[0044] In response to this, in some implementation methods, some intelligent vehicles support in-vehicle scenario modes that can be fully customized by users. Users can, through various in-vehicle application programs (APPs), arrange and combine the function services they want according to their needs for a certain type of in-vehicle scenario mode.

[0045] However, this method, firstly, requires users to be clear about the arrangement process and logical requirements of the in-vehicle scenario mode, which is not user-friendly for users without relevant experience. Secondly, intelligent vehicles have strict requirements for user safety and the compliance of the in-vehicle scenario mode process. For this type of in-vehicle scenario mode that is completely customized by users, there is a high probability that it will fail to execute due to non-compliance with safety and compliance during the execution process, and the reason for the execution failure will not be feedback to the user. In this way, users will only know whether the modified in-vehicle scenario mode can be successfully executed after executing the modified in-vehicle scenario mode. And in the case of the execution failure of the in-vehicle scenario mode, users do not know whether the execution failure is because the modified in-vehicle scenario mode does not meet the requirements of safety and compliance, or because the code corresponding to the modified in-vehicle scenario mode is incorrect. This affects the user experience.

[0046] To solve the above technical problems, the present application provides a method for defining an in-vehicle scenario mode.

[0047] The method of the present application provides a semi-preconfigured in-vehicle scenario mode for users, and supports users to modify the functions of the semi-preconfigured in-vehicle scenario mode according to their needs (such as adding or deleting functions). Moreover, after the user modifies the functions, the in-vehicle device will perform validity detection on the modified in-vehicle scenario mode, including completeness detection, mutually exclusive operation detection, etc. of the modified in-vehicle scenario mode. After all these detections pass, the user can use the modified in-vehicle scenario mode, or rather, the modified in-vehicle scenario mode can take effect and be executable. Among them, the specific method for performing validity detection on the modified in-vehicle scenario mode will be introduced below.

[0048] Moreover, during the detection process, the in-vehicle device will feedback to the user the reasons why the modified in-vehicle scenario mode cannot take effect, and guide the user on how to modify it, so as to avoid the failure of the in-vehicle scenario mode during execution and improve the user experience.

[0049] Figure 1 According to an embodiment of the present application, an applicable scenario of a method for defining an in-vehicle scenario mode is shown.

[0050] As Figure 1 shown, it includes an intelligent vehicle 01 (hereinafter referred to as vehicle 01) and a smart phone 02 (hereinafter referred to as phone 02). Vehicle 01 and phone 02 can communicate with each other. More specifically, the in-vehicle device on vehicle 01 and phone 02 are communicatively connected through wireless communication methods including Bluetooth, wireless network, etc. or wired communication methods.

[0051] In some implementation manners, vehicle 01 includes a screen A, and the user can select to turn on the required in-vehicle scenario mode through the human-machine interaction interface provided by screen A. For example, Figures 2a to 2c shows a schematic diagram of the corresponding interface change when the user selects to turn on the in-vehicle scenario mode through screen A.

[0052] As Figure 2a shown, screen A displays interface A00, and this interface A00 includes applications such as radio station application A1, in-vehicle application A2, Bluetooth application A3, phone application A4, navigation application A5, voice recognition application A6, etc. In some implementation manners, when the user clicks on the icon corresponding to in-vehicle application A2, screen A displays as Figure 2bThe interface A10 shown, which displays the in-vehicle scenario modes supported by the vehicle 01, including but not limited to the sentry mode A21, the nap mode A22, the child left-behind reminder mode, the entertainment mode, the car wash mode, etc., and this application does not limit this. Among them, the sentry mode A21 and the nap mode A22 can refer to the relevant descriptions above. The car wash mode means that when the user sends the vehicle to be washed, if the car wash mode is turned on, the vehicle will automatically close the charging interface, close the windows, windshield wipers, and trunk, and at the same time the sentry mode will also be automatically turned on, so as to avoid damage to the vehicle during the car wash process. The child left-behind reminder mode means that when a child is alone in the vehicle, the air conditioner is default turned on for heat preservation, and at the same time the windows and the charging interface are closed to prevent the child from climbing over the window.

[0053] The user can select and turn on the corresponding in-vehicle scenario mode according to needs. For example, if the user is not sure whether the parking location is safe and reliable, the user can turn on the sentry mode. For example, as Figure 2b shown, the user can select the sentry mode A21 from the interface A10, and then in the interface A30 as Figure 2c shown, turn on the sentry mode through the control A311. Another example is that if the user wants to rest in the vehicle, then the user can turn on the nap mode. Another example is that during the process of the user sending the vehicle for washing, the user can turn on the car wash mode, etc., and this application does not limit this. Among them, the process of the user turning on the nap mode or the car wash mode is the same as the process of turning on the sentry mode, and this application does not limit this.

[0054] In some implementation manners, the user can modify the functions of the selected in-vehicle scenario mode according to needs. For example, continuing with the sentry mode as an example, the user can enter the custom mode through the control A32 in the interface A30 as Figure 2c shown, to modify the functions of the sentry mode. For example, as Figure 2d shown, the user can select to modify the trigger condition of the sentry mode by clicking the control A401, select to modify the abnormal alarm light mode by clicking the control A402, select to modify the abnormal alarm sound mode by clicking the control A403, and select whether to turn on the function of reminding pedestrians by clicking the control A404.

[0055] Furthermore, assuming that the user hopes to modify the trigger condition of the sentry mode, then in the interface A50 as Figure 2e shown, the user can select to turn on the function of automatically triggering the sentry mode by geographical fence by clicking the control A501. In some implementation manners, the user can add a location blacklist corresponding to the sentry mode by clicking the control A502. Among them, the geographical fence used to trigger the sentry mode can be set by the user according to needs, or can be set by the user by adding a location blacklist or whitelist, and this application does not make any restrictions on this.

[0056] It can be understood that in some implementation manners, after the user completes the modification of the in-vehicle scenario mode, the vehicle 01 can control the screen A to display a confirmation interface for the user to confirm the completion of the modification of the in-vehicle scenario mode. This application does not limit this.

[0057] In some implementation manners, when the modified in-vehicle scenario mode can be used, a prompt flag can be displayed on the icon of the corresponding in-vehicle scenario mode to remind the user that the modified in-vehicle scenario mode can be used. For example, continuing with the sentry mode as an example, when the modified sentry mode can be used, as Figure 2f shown, a prompt flag P can be displayed in the upper right corner of the icon corresponding to the sentry mode to prompt the user that the modified in-vehicle scenario mode can be used. In some other implementation manners, the prompt flag P can be displayed at any position of the icon corresponding to the sentry mode. This application does not limit this.

[0058] In some other implementation manners, when the modified in-vehicle scenario mode cannot be used, that is, the modified in-vehicle scenario mode by the user fails the above-mentioned validity detection. To improve the user experience, the vehicle 01 can display the reason why the modified in-vehicle scenario mode by the user fails the above-mentioned validity detection.

[0059] For example, assuming that the modified sentry mode fails the above-mentioned validity detection, then as Figure 2g shown, the screen A of the vehicle 01 displays the interface A60 and displays "Hello, owner. Your modification operation does not meet the requirements of functional completeness. Please modify it again." In some implementation manners, the user can click on the control A602 to view the details to understand the more detailed and specific reason for failing the validity detection. This application does not limit this.

[0060] In some implementation manners, the vehicle 01 may also include more other screens, such as the screen B. The user can select to turn on or modify the in-vehicle scenario mode through the human-machine interaction interface provided by the screen B. During the process of the user turning on or modifying the in-vehicle scenario mode through the screen B, the change of the screen B interface is the same as the above Figures 2a to 2g and will not be elaborated.

[0061] In some other implementation manners, the user can also select the in-vehicle scenario mode to be turned on through the in-vehicle APP installed on the mobile phone 02. After the mobile phone 02 detects the start instruction for the user to turn on the in-vehicle scenario mode, it controls the in-vehicle device to turn on the corresponding in-vehicle scenario mode, or after sending the start instruction to the in-vehicle device, the in-vehicle device turns on the corresponding in-vehicle scenario mode according to the start instruction. This application does not limit this. For example, as Figure 3As shown, the desktop 020 of the mobile phone 02 displays applications such as the in-vehicle application 0101, the phone application 0102, and the navigation application 0103. Similar to the user enabling the in-vehicle scenario mode through the in-vehicle application A2 displayed on the screen A of the vehicle 01, the user can enable the required in-vehicle scenario mode through the in-vehicle application 0101 on the desktop 020 of the mobile phone 02, which will not be elaborated here.

[0062] Figure 4 According to the implementation manner of the present application, a system structure diagram for defining an in-vehicle scenario mode is shown. As Figure 4 shown, the system includes a vehicle 01, a mobile phone 02, and a cloud server 03.

[0063] Among them, the vehicle 01 includes a display module 011, an error feedback module 012, a cockpit domain controller (CDC) 01A, and a telematics box (T-Box) 010. Specifically, in some implementation manners, the display module 011 provides a user interface, such as Figures 2a to 2c interfaces such as interface A00, interface A10, and interface A20 shown, so that the user can interact with the vehicle 01 through the user interface. For example, the user starts the in-vehicle application A2 through Figure 2a interface A00 shown. Another example is that the user enables the sentry mode A21 through Figure 2b interface A10 shown.

[0064] In other implementation manners, after the in-vehicle scenario mode modified by the user fails to be detected, according to the feedback of the error feedback module 012, the display module 011 displays the reason for the failure to detect the modified in-vehicle scenario mode as Figure 2g shown. In some implementation manners, while displaying the foregoing failure reason, the display module 011 can also display the corresponding modification method. The present application does not limit this.

[0065] The CDC 01A includes a first storage module 013, a second storage module 014, a detection module 015, and an update module 016. Among them, the first storage module 013 is used to store the information of the preset in-vehicle scenario mode (hereinafter referred to as preset data), such as the type of the preset in-vehicle scenario mode and the corresponding functions under each type of in-vehicle scenario mode. Exemplarily, the types of some in-vehicle scenario modes involved in the present application and some functions under each type of in-vehicle scenario mode can be as shown in Table 1 below:

[0066] Table 1 Types of some in-vehicle scenario modes and some functions under each type of in-vehicle scenario mode

[0067]

[0068] That is, the vehicle scenario mode includes at least one scenario mode, and each scenario mode represents a combination of specific working modes of multiple components in the vehicle. For example, as shown in Table 1 above, in the scenario mode of the sentry mode, the vehicle components corresponding to the scenario mode at least include an alarm light and an alarm audio emitting part, and the working modes are that the alarm light flashes and the alarm audio emitting part emits an alarm voice. In the car wash mode, the vehicle components corresponding to this scenario mode at least include the windows and the in-vehicle charging interface, and the corresponding working modes are that the windows are closed and the in-vehicle charging interface is automatically powered off. In the entertainment mode, when parked, the seat automatically adjusts according to the user's body position, the in-vehicle surround sound effect is turned on, and external entertainment devices such as game pads are supported.

[0069] The second storage module 014 is used to store preset data and user-modified data. Among them, the user-modified data includes the type of the vehicle scenario mode corresponding to the user's modification operation and the functions in the vehicle scenario mode of this type targeted by the user's modification operation. For example, if the user modifies the trigger condition of the sentry mode, then the user-modified data includes the sentry mode and the trigger condition of the sentry mode modified by the user in the sentry mode (such as the function of automatically triggering the sentry mode by the geographical fence).

[0070] The detection module 015 is used to detect whether the user-modified vehicle scenario mode is valid. In some implementation manners, the items for which the detection module 015 performs validity detection on the user-modified vehicle scenario mode include performing a completeness detection and a mutual exclusion operation detection on the modified vehicle scenario mode. Among them, the completeness test refers to the integrity detection of the functions of the user-modified vehicle scenario mode to determine whether the functions of the modified vehicle scenario mode still conform to the logic of the mode design, etc., For example, for the sentry mode, the detection function of the parking position of vehicle 01 cannot be deleted. If the user deletes the detection function of the parking position of vehicle 01 for the sake of reducing power consumption, then the modified sentry mode does not meet the completeness requirements, that is, it cannot pass the validity detection. Another example is that the sentry mode generally has various types of risk detections, such as the risk detection of an unknown person approaching, the risk detection of the door / trunk being opened, the risk detection of movement and sound in the cockpit, and the risk detection of vehicle tilt. For the sentry mode, at least one of the risk detection of an unknown person approaching and the risk detection of the door / trunk being opened must be retained to determine whether an unknown person opens the door / trunk. Therefore, when the user deletes both the functions of the risk detection of an unknown person approaching and the risk detection of the door / trunk being opened for other purposes such as reducing power consumption, then the modified sentry mode does not meet the completeness requirements, that is, it cannot pass the validity detection.

[0071] The mutually exclusive operation detection refers to the detection from the perspective of safety for vehicle driving specifications, user personal safety, etc. For example, for the child forgetting reminder mode, for safety reasons, the user cannot delete or disable the voice function and screen clicks to prevent children from accidentally touching and causing danger.

[0072] It can be understood that each type of in-vehicle scenario mode has corresponding validity detection conditions. These validity detection conditions can be set by R & D personnel according to the functions corresponding to each type of in-vehicle scenario mode, and this application does not impose any restrictions on this. Correspondingly, in some implementation manners, the preset data may include the validity detection conditions corresponding to various in-vehicle scenario modes.

[0073] In some implementation manners, the detection module 015 can also perform scenario tests on the modified in-vehicle scenario mode. Specifically, the detection module 015 can preset a variety of conventional test scenarios, and then perform validity detection on the modified in-vehicle scenario mode under each conventional test scenario. For example, for the child left-behind reminder mode, its conventional test scenario can be to simulate the duration that the vehicle 01 can maintain operation after turning on the services selected by the user (such as turning on the air conditioner and playing children's books on the central control screen) at different battery levels, so that the detection module 015 can determine a more reasonable minimum battery level threshold corresponding to turning on the child left-behind reminder mode based on the duration that the vehicle 01 can maintain operation under the conventional test scenarios corresponding to different battery levels, to prevent safety accidents caused by insufficient battery power of the vehicle 01 after turning on the child left-behind reminder mode at the minimum battery level threshold.

[0074] It can be understood that in some implementation manners, the detection module 015 can only perform completeness detection and mutually exclusive operation detection on the modified in-vehicle scenario mode, or can also perform scenario tests on the modified in-vehicle scenario mode, and the test order is not restricted. That is, the detection module 015 can perform scenario tests on the modified in-vehicle scenario mode and then perform completeness tests and mutually exclusive operation detection on it, or can perform completeness tests and mutually exclusive operation detection on the modified in-vehicle scenario mode and then perform scenario tests on the modified in-vehicle scenario mode, and this application does not impose any restrictions on this.

[0075] In some implementation manners, after the detection module 015 completes the validity test on the modified in-vehicle scenario mode, and if the modified in-vehicle scenario mode fails the validity test, the detection module 015 sends the reason for the failure of the in-vehicle scenario mode to pass the validity test to the error feedback module 012, and the error feedback module 012 sends it to the display module 011 for display to the user.

[0076] In some implementations, when the detection module 015 completes the validity test of the modified in-vehicle scenario mode and the modified in-vehicle scenario mode passes the validity test, the update module 016 updates the original in-vehicle scenario mode to the modified in-vehicle scenario mode.

[0077] Moreover, in some implementations, since the user may modify the in-vehicle scenario mode through the mobile phone 02, in order to ensure that the user can achieve the same modification effect through the mobile phone 02 or the vehicle 010, it is necessary to keep the in-vehicle scenario modes provided by the mobile phone 02 and the vehicle 010 consistent. That is to say, if the in-vehicle scenario mode on the vehicle 010 is not updated, then the same type of in-vehicle scenario mode provided by the mobile phone 02 should also not be updated; if the in-vehicle scenario mode on the vehicle 010 is updated, then the same type of in-vehicle scenario mode provided by the mobile phone 02 should also be updated. Vice versa. Among them, the situation where the in-vehicle scenario mode is not updated includes that the user has not modified it, or the user has modified the in-vehicle scenario mode, but the modified in-vehicle scenario mode fails the validity test of the detection module 015.

[0078] In some implementations, data transmission and update between the vehicle 01 and the mobile phone 02 are carried out through the T-BOX 010 and the cloud server 03.

[0079] In some implementations, the T-B0X 010 can also be called a vehicle box. Its main function is that when the user sends a control instruction through the in-vehicle application A2 of the mobile phone 02, the vehicle 01 will send a monitoring request instruction to the T-BOX 010. After receiving the monitoring request instruction, the T-BOX 010 sends a control message corresponding to the monitoring request instruction to the corresponding components in the vehicle 01 through the controller area network (CAN) bus to achieve vehicle control, and feeds back the control result to the in-vehicle application A2 of the mobile phone 02. In this way, the user can remotely start the headlights, turn on the air conditioner, adjust the seat, start the engine, etc. through the mobile phone 02.

[0080] In some implementations, the cloud server 03 is used to obtain and store the data corresponding to the in-vehicle scenario mode in the vehicle 01, including the data of the preset in-vehicle scenario mode and the data of the in-vehicle scenario mode that passes the validity test after being modified by the user, so that the update module 021 of the mobile phone 02 can update the in-vehicle scenario mode based on these data to keep it consistent with the in-vehicle scenario mode of the vehicle 010.

[0081] Figure 5 Another system diagram for defining the in-vehicle scenario mode is shown according to the implementation manner of the present application. Among them, Figure 5 And Figure 4 The difference is that based onFigure 5 As shown in the system diagram, the user can modify the in-vehicle scenario mode through the mobile phone 02. The following is an introduction to this, and the same parts as Figure 4 will not be elaborated below.

[0082] Such as Figure 5 shown, the system includes a mobile phone 02, a vehicle 01, and a cloud server 03. Among them, the mobile phone 02 includes a display module 022, an error feedback module 023, and an update module 021. The display module 022 is used to provide the user interface 020 as Figure 3 shown to enable the user to select and modify the in-vehicle scenario mode through the in-vehicle application 0101. The function and role of the error feedback module 023 are the same as those of the error feedback module 012 in Figure 4 , and the function and role of the update module 021 are the same as those of the update module 021 in Figure 4 . The functions and roles of the modules in the vehicle 010 are the same as those of the modules in the vehicle 010 in Figure 4 and will not be elaborated below.

[0083] In some implementation manners, after the user selects to start the in-vehicle application 0101 through the user interface 020 provided by the display module 022 of the mobile phone 02 and selects the in-vehicle scenario mode to be modified, the mobile phone 02 sends a modification instruction to the CDC 01A in the vehicle 010 through the cloud server 03 and the T-B0X 010. The CDC 01A stores the user-modified data in the second storage module 014, and then the detection module 015 performs a validity detection on the modified in-vehicle scenario mode. If the detection fails, the CDC 01 synchronizes the failure reason to the error feedback module 023 through the T-B0X 010, and the error feedback module 023 sends it to the display module 022 for display. If the detection passes, the CDC 01 still synchronizes and updates the modified in-vehicle scenario mode to the update module 021 through the T-B0X 010 to keep the in-vehicle scenario mode on the mobile phone 02 consistent with the in-vehicle scenario mode of the vehicle 010.

[0084] It can be understood that in addition to the user modifying the in-vehicle scenario mode, the in-vehicle applications corresponding to the in-vehicle scenario mode (such as in-vehicle application A2) will also automatically update the in-vehicle scenario mode, or automatically update the above-mentioned preset data. For example, when traffic road regulations and the like are updated, in-vehicle application A2 needs to update the validity detection conditions corresponding to each type of in-vehicle scenario mode, especially the mutually exclusive operation detection conditions in the validity detection conditions, so as to avoid non-compliance due to the user modifying the function. For example, for the entertainment mode, if the user adds a seat swaying function, then perhaps a function to detect whether there are children in the vehicle needs to be added at the same time, otherwise there may be a situation where children are in the vehicle, but the child's riding method does not comply with the traffic road regulations. Another example is that if the R & D personnel need to update the sound effect database, lighting mode database, etc. under some in-vehicle scenario modes according to data statistics, then the corresponding in-vehicle application A2 needs to update the in-vehicle scenario modes related to functions such as sound effects and lighting modes.

[0085] To avoid the in-vehicle application's own system or version upgrade from overwriting the in-vehicle scenario mode modified by the user, in some implementation manners of the present application, the user-modified data and the preset data (including the data corresponding to the in-vehicle scenario mode that has not undergone system or version update or the data corresponding to the in-vehicle scenario mode that has undergone system or version update) can be stored separately. Then, when vehicle 01 detects an update of the in-vehicle application's own system or version, first use the updated version data to update the original preset data to obtain the preset data corresponding to the updated version, and then use the user-modified data to modify the preset data corresponding to the updated version to obtain the data corresponding to the in-vehicle scenario mode modified by the user. That is, when vehicle 01 detects a user modification instruction and an update of the in-vehicle application A2 system, first update the system of in-vehicle application A2, and then modify the updated in-vehicle scenario mode according to the user modification instruction to obtain the in-vehicle scenario mode modified by the user.

[0086] By this method, it is ensured that the user modification operation is performed on the in-vehicle scenario mode after system or version update, so as to ensure that the user-modified data is not overwritten by the version update data.

[0087] The following combines Figure 6 to introduce the definition method of the in-vehicle scenario mode of the present application. For ease of explanation, vehicle 01 implementing the present solution is taken as an example. Specifically, as Figure 6 shown, the method includes:

[0088] 601, detecting a modification instruction of the user for the target in-vehicle scenario mode.

[0089] In some implementation manners, after the user selects the target in-vehicle scenario mode, the target in-vehicle scenario mode can be modified. In some implementation manners, when vehicle 01 detects that the user makes such asFigures 2b to 2d After the operations shown, it is determined that a modification instruction for the target vehicle scenario mode has been detected by the user.

[0090] It can be understood that the user operations include but are not limited to Figures 2b to 2d the click operations shown, and other operations that can trigger the corresponding functions can also be used, such as the user inputting a preset voice command, etc. This application does not limit this.

[0091] In some implementation manners, the target vehicle scenario mode includes but is not limited to the sentry mode, child left-behind reminder mode, entertainment mode, nap mode, and car wash mode mentioned above.

[0092] 602. The vehicle 01 modifies the target vehicle scenario mode according to the modification instruction to obtain the modified vehicle scenario mode.

[0093] For example, for the nap mode, the user adds or deletes the devices linked to the vehicle 01, or modifies the music types, music volumes, music sound effects in the nap mode, increases the aromatherapy concentration, seat angle, and the way of automatic massage in the nap mode, etc., to obtain the modified nap mode. Among them, the devices linked to the vehicle 01 include the user's mobile phone 02, Bluetooth headset, intelligent massager, etc. This application does not limit this.

[0094] For another example, for the child left-behind reminder mode, the user can modify the air-conditioning heat preservation function to the air-conditioning internal circulation or external circulation function to obtain the modified child left-behind reminder mode. Or in the child left-behind reminder mode, the user can add the function that the window can automatically open a preset distance gap to obtain the modified child left-behind reminder mode. Among them, the preset distance is an empirical value or an experimental value. This application does not limit this. Or, in the child omission reminder mode, the user can add the function that the screen A automatically plays the selected animation or music album to obtain the modified child left-behind reminder mode. This application does not limit this.

[0095] For still another example, for the entertainment mode, the user can modify the linked devices in the vehicle 01. For example, the user can add the linkage of devices such as seats, air conditioners, sound effects, and lights to obtain the modified entertainment mode.

[0096] For another example, in the car wash mode, the user can modify the combination of gear shifting, powering off, locking the vehicle, etc. of vehicle 01 to obtain different car wash modes for different car wash scenarios. Among them, locking the vehicle means cutting off all the power of vehicle 01 when the vehicle 01 is powered off or turned off. Correspondingly, not locking the vehicle means that after vehicle 01 is powered off or turned off, the anti-theft alarm, warning indicator and other devices in vehicle 01 still continue to work. Therefore, when cleaning the exterior of the vehicle body, in order to avoid damaging vehicle 01, it is also necessary to monitor the risks borne by vehicle 01 at the same time to remind the user of the possible risks that vehicle 01 may suffer. Therefore, the user can use the parking gear, powering off and not locking the vehicle as a combination when cleaning the exterior of the vehicle body to ensure that the devices related to the risk monitoring of vehicle 01 in vehicle 01 can continue to work to monitor the risks of vehicle 01.

[0097] 603. Vehicle 01 performs an effectiveness detection on the modified in-vehicle scenario mode and decides whether to update the target in-vehicle scenario mode according to the detection result. If the effectiveness detection of the modified in-vehicle scenario mode passes, then execute 604. Vehicle 01 updates the target in-vehicle scenario mode to the modified in-vehicle scenario mode. If the effectiveness detection of the modified in-vehicle scenario mode does not pass, then execute 605. Do not update the target in-vehicle scenario mode and display the reason why the effectiveness detection fails.

[0098] It can be understood that each type of in-vehicle scenario mode has corresponding effectiveness detection conditions. When vehicle 01 performs an effectiveness detection on the modified in-vehicle scenario mode, it detects whether the in-vehicle scenario mode of this type is effective according to the effectiveness detection conditions corresponding to this in-vehicle scenario mode.

[0099] For example, if vehicle 01 determines that the in-vehicle scenario mode is the sentry mode, vehicle 01 performs an effectiveness detection on the modified sentry mode by using the effectiveness detection conditions corresponding to the sentry mode. Among them, the effectiveness detection conditions of the sentry mode can be preset by the R & D personnel according to the functions supported by the sentry mode. And it can be understood that the functions supported by the sentry mode include the functions corresponding to the preset sentry mode and the functions modified by the user (such as the functions added by the user).

[0100] Exemplarily, for the sentry mode, it can be understood that the location detection function regarding the parking position of vehicle 01 cannot be deleted, and at the same time, it is necessary to ensure that vehicle 01 has enough power to return. Therefore, the trigger power value for the user to modify the activation of the sentry mode cannot be lower than the first threshold. That is to say, when the trigger power value in the activation condition of the newly added sentry mode by the user is lower than the first threshold, vehicle 01 determines that the sentry mode modified by the user does not meet the completeness condition and cannot take effect. Among them, the first threshold is an empirical value or an experimental value. For example, it can be 20% to 30%.

[0101] Exemplarily, for the nap mode, in order to prevent power depletion during use, when starting the nap mode, the power detection of the corresponding vehicle 01 needs to be associated with the duration of the nap mode set by the user. That is to say, the longer the duration of the nap mode set by the user, the greater the power of the corresponding vehicle 01 when the user starts the nap mode, so as to ensure that the power is always sufficient in the nap mode. Then, if the user independently cancels the association between the power detection of vehicle 01 in the nap mode and the duration of the nap mode, vehicle 01 determines that the modified nap mode by the user does not meet the completeness condition and cannot take effect. For another example, in order to ensure the user's rest quality, the vehicle 01 will automatically turn on the do-not-disturb function in the nap mode. However, at the same time, in order to improve the user experience, the nap mode also needs to provide an alarm clock or a timing function to avoid the situation where the user oversleeps and misses an important meeting arrangement. Therefore, the do-not-disturb function and the timing function also need to exist simultaneously in the nap mode. If the user deletes the do-not-disturb function and / or the timing function, vehicle 01 determines that the modified nap mode by the user does not meet the completeness condition, that is, it cannot take effect. Among them, the do-not-disturb function includes, but is not limited to, vehicle 01 not prompting the user with any information of vehicle 01 or other electronic devices associated with vehicle 01.

[0102] Exemplarily, for the child left-behind reminder mode, for safety considerations, at least one of the services related to ventilation of vehicle 01 needs to be retained. Therefore, when the user deletes all the services related to ventilation in the child left-behind reminder mode, vehicle 01 determines that the modified child left-behind reminder mode by the user does not meet the completeness condition and cannot take effect. Among them, in some implementation manners, the services related to ventilation include services such as the air-conditioning internal circulation and external circulation, and the present application does not limit this.

[0103] In some implementation manners, for the child left-behind reminder mode, for the consideration of reducing the battery power consumption of vehicle 01, the upper limit value of the volume customized by the user cannot exceed the volume threshold either. That is to say, when the user modifies the volume of the sound effect related to the child left-behind reminder in the child left-behind reminder mode, if the user modifies the upper limit value of the volume of this sound effect to exceed the volume threshold, vehicle 01 determines that the modified child left-behind reminder mode by the user does not meet the completeness condition and cannot take effect.

[0104] Exemplarily, for the car wash mode, in order to avoid damage to vehicle 01, when washing the car, the windows, charging ports, air-conditioning internal circulation, external circulation, etc. of vehicle 01 need to be closed. Therefore, the detection functions such as whether the windows of the car wash mode are closed, whether the charging ports are closed, and whether the air-conditioning is closed cannot be deleted. That is to say, when the user modifies any of the above detection functions in the car wash mode, vehicle 01 determines that the modified car wash mode by the user does not meet the completeness condition and cannot take effect.

[0105] Similarly, vehicle 01 uses the preset mutually exclusive operation detection conditions corresponding to various types of in-vehicle scenario modes to detect the effectiveness of the in-vehicle scenario modes. Among them, the preset mutually exclusive operation detection conditions corresponding to various types of in-vehicle scenario modes are also set by R & D personnel according to requirements and according to the communication corresponding to various types of in-vehicle scenario modes. This application does not limit this.

[0106] Exemplarily, for the child left-behind reminder mode, for safety reasons, the user cannot delete the voice disable function and the screen touch disable function to prevent children from accidentally triggering and causing danger, and background application updates and upgrades are prohibited in the child left-behind reminder mode to prevent conflicts between some services during the update and the ventilation service, resulting in the ventilation service being unavailable and insufficient oxygen in vehicle 01. That is to say, when the user modifies the child left-behind reminder mode and deletes the voice disable function or the screen touch disable function, vehicle 01 determines that the modified child left-behind reminder mode does not meet the mutually exclusive operation detection conditions and cannot take effect.

[0107] Exemplarily, for the entertainment mode, also for safety reasons, when the user adds the seat sway function, it is necessary to detect whether there are children in the vehicle and whether the driving is safe in the current entertainment mode. That is to say, when the user modifies the entertainment mode and adds the seat sway function, if vehicle 01 does not detect the detection of whether there are children in the vehicle and whether the driving is safe in the modified entertainment mode, vehicle 01 determines that the modified entertainment mode does not meet the mutually exclusive operation detection conditions and cannot take effect.

[0108] 604. Vehicle 01 determines that the effectiveness detection of the modified in-vehicle scenario mode passes, and vehicle 01 updates the target in-vehicle scenario mode to the modified in-vehicle scenario mode.

[0109] Among them, the specific update method can refer to Figure 4 、 Figure 6 for relevant descriptions and will not be elaborated here.

[0110] 605. Vehicle 01 determines that the effectiveness detection of the modified in-vehicle scenario mode fails, and vehicle 01 does not update the target in-vehicle scenario mode and displays the reason for the failure of the effectiveness detection. For example Figure 2g as shown, when the user modifies the sentry mode and does not meet the completeness condition, a prompt message "Hello, owner. Your modification does not meet the functional completeness requirements. Please modify it again" is displayed.

[0111] Through the above method, the user can modify the preset in-vehicle scenario mode according to their own needs. Moreover, since the effectiveness of the in-vehicle scenario mode will be detected before it is executed, and the reason for the failure of the effectiveness detection will be fed back to the user, so that the user can make targeted modifications to avoid the situation where the modified in-vehicle scenario mode cannot be executed during the execution process, thus improving the user experience.

[0112] An embodiment of the present application further provides an electronic device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor. When the processor executes the computer program, the steps in any of the above method embodiments are implemented.

[0113] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in each of the above method embodiments can be implemented.

[0114] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, it enables the mobile terminal to implement the steps in each of the above method embodiments when executed.

[0115] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, to implement all or part of the processes in the above method embodiments of the present application, a computer program can be used to instruct relevant hardware to complete. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps in each of the above method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file, or some intermediate form, etc. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk, or an optical disc, etc. In some jurisdictions, according to legislation and patent practice, the computer-readable medium cannot be an electrical carrier signal and a telecommunication signal.

[0116] In the above embodiments, the descriptions of each embodiment have their own emphases. For the parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0117] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0118] In the embodiments provided in this application, it should be understood that the disclosed device / network device and method can be implemented in other ways. For example, the device / network device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

[0119] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0120] In the above description, specific details such as specific system structures and technologies are proposed for the purpose of illustration rather than limitation, so as to thoroughly understand the embodiments of this application. However, those skilled in the art should clearly understand that this application can also be implemented in other embodiments without these specific details. In other cases, the detailed descriptions of well-known systems, devices, circuits and methods are omitted to avoid unnecessary details from interfering with the description of this application.

[0121] It should be understood that when used in the specification of this application and the appended claims, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or their combinations.

[0122] It should also be understood that the term " / and" used in the specification of this application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0123] As used in the specification of this application and the appended claims, the term "if" can be construed as "when" or "once" or "in response to determining" or "in response to detecting" depending on the context. Similarly, the phrase "if determined" or "if [described condition or event] is detected" can be construed as meaning "once determined" or "in response to determining" or "once [described condition or event] is detected" or "in response to detecting [described condition or event]" depending on the context.

[0124] In addition, in the description of the specification of this application and the appended claims, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be construed as indicating or implying relative importance.

[0125] Reference to "one embodiment" or "some embodiments" or the like described in the specification of this application means that a particular feature, structure, or characteristic described in connection with that embodiment is included in one or more embodiments of this application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "comprising", "including", "having" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in another way.

[0126] The above-described embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application and should all be included within the protection scope of this application.

Claims

1. A method for defining an in-vehicle scenario mode, applied to a first electronic device, characterized in that Including: Detecting a modification instruction of the user for a target vehicle scenario mode; Modifying the target vehicle scenario mode according to the modification instruction to obtain a modified vehicle scenario mode; Performing a scenario test on the modified vehicle scenario mode, where the scenario test is used to determine the minimum power threshold for turning on the modified vehicle scenario mode; Determining an effectiveness detection condition corresponding to the modified vehicle scenario mode, where the effectiveness detection condition corresponding to each type of vehicle scenario mode is set based on the corresponding function; Performing an effectiveness detection on the modified vehicle scenario mode according to the corresponding effectiveness detection condition, where the effectiveness detection at least includes a completeness detection and a mutual exclusion operation detection on the function corresponding to the modified vehicle scenario mode; Deciding whether to update the target vehicle scenario mode according to the detection result, where corresponding to the modified vehicle scenario mode passing the effectiveness detection of the first electronic device, updating the target vehicle scenario mode to the modified vehicle scenario mode.

2. The method according to claim 1, wherein The method further includes: corresponding to the modified vehicle scenario mode not passing the effectiveness detection of the first electronic device, not updating the target vehicle scenario mode.

3. The method according to claim 1, where the target vehicle scenario mode includes at least one scenario mode, and each scenario mode represents a combination of specific working modes of multiple devices in the vehicle where the first electronic device is located.

4. The method according to claim 3, wherein The target vehicle scenario mode includes at least any one of the following scenario modes: a nap mode, a child left-behind reminder mode, a car wash mode, an entertainment mode, or a sentry mode.

5. The method according to claim 2 or 3, characterized in that, The method further includes: displaying, on the first electronic device, the reason why the modified vehicle scenario mode fails the effectiveness detection.

6. The method according to any one of claims 1 to 4, characterized in that The method further includes: sending the modified vehicle scenario mode to a second electronic device, where the sent modified vehicle scenario mode can cause the second electronic device to update the target vehicle scenario mode on the second electronic device.

7. The method according to any one of claims 2 to 4, characterized in that The method further includes: corresponding to the modified vehicle scenario mode not passing the effectiveness detection of the first electronic device, not updating the target vehicle scenario mode, and sending a second message, where the second message is used to display, on the second electronic device, the reason why the modified vehicle scenario mode fails the effectiveness detection.

8. The method according to claim 6, where the first electronic device includes a vehicle-mounted device, and the second electronic device includes a smart phone or a tablet computer.

9. The method according to claim 7, where the first electronic device includes a vehicle-mounted device, and the second electronic device includes a smart phone or a tablet computer.

10. The method according to claim 1, characterized in that, The first electronic device includes a cockpit controller, and the cockpit controller includes a detection module for performing an effectiveness detection on the modified vehicle scenario mode.

11. A computer-readable medium, characterized in that, Instructions are stored on the computer-readable medium, and when executed on a computer, the instructions cause the computer to execute the method according to any one of claims 1 to 10.

12. An electronic device, characterized in that, The electronic device includes: a memory for storing instructions executed by one or more processors of the electronic device, and One or more processors for executing instructions stored in the memory such that the electronic device performs the method according to any one of claims 1 to 10.

13. A computer program product, characterized in that, When the computer program product runs on an electronic device, the electronic device is caused to perform the method according to any one of claims 1 to 10.

Images