Execution method and execution system of vehicle scenario mode

Abstract

Embodiments of the present application provide a method and system for executing a vehicle context mode. The method may include: generating and broadcasting Bluetooth key information via at least one mobile terminal, wherein the Bluetooth key information includes at least one context mode type corresponding to the mobile terminal; in response to a vehicle within a predetermined distance range of the at least one mobile terminal receiving the Bluetooth key information, determining, based on the Bluetooth key information, a vehicle control operation of at least one vehicle control component requiring execution of the context mode; and controlling the at least one vehicle control component to execute the context mode according to the at least one context mode type in the Bluetooth key information.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle-related technologies, and specifically to a method and system for executing a vehicle context mode. Background Art

[0002] With the development of technology, users are no longer satisfied with simple driving functions when choosing vehicles, but have higher requirements for various interactive functions such as vehicle driving experience. For example, they require vehicles to be personalized for different users.

[0003] Conventional vehicle scenario mode execution schemes often feature multiple scenario modes for users to choose from. When a user approaches the vehicle and triggers a scenario mode execution signal, the vehicle obtains the selected scenario mode type from the vehicle-mounted system via the vehicle-mounted communication module and controls the vehicle control components to execute the scenario mode according to that scenario mode type. However, due to the time required for the vehicle-mounted system to boot up, the vehicle is unable to obtain the selected scenario mode type in a timely manner, and thus cannot smoothly execute the corresponding scenario mode. Furthermore, the scenario mode type obtained from the vehicle-mounted system can only be the scenario mode type last set by the user, making it impossible to achieve personalized display for different users. Summary of the Invention

[0004] The embodiments of the present application provide a method and system for executing a vehicle context mode that can at least partially address at least one of the above-mentioned shortcomings or other shortcomings in the prior art.

[0005] The first aspect of the present application provides a method for executing a vehicle context mode, which includes: forming Bluetooth key information through at least one mobile terminal and broadcasting it externally, wherein the Bluetooth key information includes at least one context mode type corresponding to the mobile terminal; in response to a vehicle within a predetermined distance range of the at least one mobile terminal receiving the Bluetooth key information, determining the vehicle control operation of at least one vehicle control component that needs to execute the context mode based on the Bluetooth key information; and controlling the at least one vehicle control component to execute the context mode according to the at least one context mode type in the Bluetooth key information.

[0006] The second aspect of the present application provides a vehicle scenario mode execution system, which includes at least one mobile terminal and a vehicle; the at least one mobile terminal is configured to: form Bluetooth key information and broadcast it externally, wherein the Bluetooth key information includes at least one scenario mode type corresponding to the mobile terminal; the vehicle is configured to: in response to the vehicle receiving the Bluetooth key information, determine the vehicle control operation of at least one vehicle control component that needs to execute the scenario mode according to the Bluetooth key information; and control the at least one vehicle control component to execute the scenario mode according to the at least one scenario mode type in the Bluetooth key information.

[0007] According to some embodiments of the present application, Bluetooth key information carrying a situational mode type corresponding to the mobile terminal is generated through a mobile terminal and broadcast externally. The vehicle determines the vehicle control operation of the vehicle control components based on the Bluetooth key information and controls the vehicle control components to execute the situational mode according to the situational mode type, so that the vehicle can execute the situational mode according to the situational mode type of different mobile terminals, thereby realizing the vehicle's personalized display of the situational modes of different mobile terminals.

[0008] According to some embodiments of the present application, the mobile terminal can determine the situational mode type corresponding to the mobile terminal and broadcast the situational mode type to the vehicle in the form of Bluetooth key information. The vehicle only needs to receive the Bluetooth key information and determine the vehicle control operation of the vehicle control components based on the Bluetooth key information. There is no need to obtain the situational mode type corresponding to the above-mentioned mobile terminal from the vehicle host through the on-board communication module again, ensuring that the vehicle can quickly execute the situational mode corresponding to the above-mentioned mobile terminal, thereby improving the personalized display effect of the situational mode of different mobile terminals.

[0009] It should be understood that the content described in this section is not intended to identify the key features or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the description below. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Other features, objectives and advantages of the embodiments of the present application will become more apparent by reading the detailed description of the non-limiting embodiments made with reference to the following drawings. In the drawings:

[0011] Figure 1 FIG2 shows a schematic system framework of a vehicle context mode execution system according to an exemplary embodiment of the present application;

[0012] Figure 2a and Figure 2b Schematic block diagrams of vehicles according to exemplary embodiments of the present application are respectively shown;

[0013] Figure 2c FIG2 shows a schematic system framework of a vehicle context mode execution system according to an exemplary embodiment of the present application;

[0014] Figure 3 FIG2 shows a schematic system framework of a vehicle context mode execution system according to an exemplary embodiment of the present application;

[0015] Figure 4 FIG2 shows a schematic system framework of a vehicle context mode execution system according to an exemplary embodiment of the present application;

[0016] Figure 5A schematic flow chart showing a method for executing a vehicle context mode according to an exemplary embodiment of the present application is shown;

[0017] Figure 6a A schematic diagram illustrating an interaction of a mobile terminal determining its welcome mode type according to an exemplary embodiment of the present application is shown;

[0018] Figure 6b A schematic diagram illustrating interaction between a mobile terminal and a vehicle according to an exemplary embodiment of the present application is shown;

[0019] Figure 6c A schematic diagram showing the interaction between the vehicle body controller and the vehicle control component according to an exemplary embodiment of the present application; and

[0020] Figure 7 A schematic structural diagram of an electronic device according to an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0021] For a better understanding of the present application, various aspects of the present application will be described in more detail with reference to the accompanying drawings. It should be understood that these detailed descriptions are merely descriptions of exemplary embodiments of the present application and are not intended to limit the scope of the present application in any way. Throughout the specification, the same reference numerals refer to the same elements. The expression "and / or" includes any and all combinations of one or more of the associated listed items.

[0022] Unless otherwise defined, all terms (including technical and scientific terms) used in this application have the same meaning as commonly understood by those skilled in the art to which this application belongs. It should also be understood that terms (such as those defined in commonly used dictionaries) should be understood to have the same meaning as they have in the context of the relevant technology and should not be interpreted in an idealized or overly formal sense unless expressly defined in this application.

[0023] It should be noted that, unless there is a conflict, the embodiments and features of the embodiments in this application can be combined with each other. In addition, unless explicitly limited or inconsistent with the context, the specific steps included in the methods described in this application are not necessarily limited to the order described, but can be performed in any order or in parallel. The present application will be described in detail below with reference to the accompanying drawings and in conjunction with the embodiments.

[0024] Figure 1 The schematic system framework of a vehicle context mode execution system 10 according to some embodiments of the present application is shown. Solid lines represent mandatory connections (wired or wireless), while dashed lines represent connections that can be modified based on vehicle configuration (limited or wireless).

[0025] like Figure 1 As shown, the execution system 10 of the vehicle scenario mode may include at least one mobile terminal 20 and a vehicle 30, wherein the mobile terminal 20 may be a mobile phone, an electronic bracelet, a ring, smart glasses, or other devices that a user can carry or wear, and is not limited here.

[0026] The mobile terminal 20 is equipped with a Bluetooth module 210, which can at least sense the location of the mobile terminal 20 and broadcast Bluetooth key information. The Bluetooth key information includes at least one context mode type corresponding to the mobile terminal 20. The Bluetooth key information may also include the pairing key of the Bluetooth key of the mobile terminal 20. Each mobile terminal 20 corresponds to at least one context mode type and a Bluetooth key pairing key. The vehicle 30 may include an in-vehicle communication module 310, a vehicle host 320, at least one vehicle control component 330, and a body controller 340 for controlling the at least one vehicle control component 330. Different vehicle control components 330 execute context modes according to different context mode types. Each vehicle control component 330 may execute a variety of context mode types. The at least one context mode type corresponding to the mobile terminal 20 is selected based on the identity of the mobile terminal 20.

[0027] For ease of understanding, Figure 2a and Figure 2b Schematic block diagrams of a vehicle 30 according to some embodiments of the present application are shown below. Figure 2a and Figure 2b Some exemplary descriptions of the connection methods within the vehicle 30 are given.

[0028] In some embodiments of the present application, Figure 2a As shown, the vehicle-mounted communication module 310 may include a communication module A311, wherein the communication module A311 is connected to the vehicle body controller 340. The vehicle body controller 340 can control at least one vehicle-controlled component 330 based on the Bluetooth key information received by the vehicle-mounted communication module 310. In addition, the vehicle host 320 can be connected to the vehicle body controller 340 via wireless or wired communication to send control instructions for controlling the at least one vehicle-controlled component 330 to the vehicle body controller 340, thereby controlling the at least one vehicle-controlled component 330.

[0029] In other embodiments of the present application, Figure 2b As shown, the vehicle communication module 310 may include a communication module A 311 and a communication module B 312, wherein the communication module A 311 is connected to the vehicle body controller 340, and the communication module B 312 is connected to the vehicle host 320. In this case, the execution system 10 of the vehicle context mode is as follows: Figure 2cThe communication module A 311 and the communication module B 312 are communicably connected. The vehicle body controller 340 can control at least one vehicle control component 330 according to the Bluetooth key information received by the vehicle communication module 310.

[0030] It should be understood that, without departing from the teachings of this application, communication module A311 and communication module B 312 may be, for example, ultra-wideband (UWB) communication modules, star flash modules, and other wireless communication modules with positioning and / or communication functions, and this application does not impose any restrictions on this.

[0031] After completing the exemplary description of the connection mode inside the vehicle 30 , the types of the vehicle control components 330 of the vehicle 30 are exemplarily described below.

[0032] In some embodiments of the present application, the vehicle control component 330 may include at least one of a light emitting device of the vehicle 30, a sound emitting device of the vehicle 30, an air conditioner of the vehicle 30, and a seat of the vehicle 30. For example, the light emitting device of the vehicle 30 may include an exterior lighting system of the vehicle 30, an interior lighting system of the vehicle 30, etc., and the sound emitting device of the vehicle 30 may include an exterior sound emitting device of the vehicle 30, an interior sound emitting device of the vehicle 30, etc., without limitation herein.

[0033] It should be understood that, without departing from the teachings of this application, the vehicle control component 330 of the vehicle 30 may also be other components of the vehicle that have the need to execute scenario modes, which are not listed here one by one.

[0034] After the exemplary description of the types of the vehicle control components 330 of the vehicle 30 , the functions of the vehicle host 320 of the vehicle 30 will be exemplarily described below.

[0035] In some embodiments of the present application, the vehicle host 320 is configured with an identity identifier corresponding to at least one user and a preset scenario mode type. Each user may correspond to at least one preset scenario mode type. For example, each user may log in to an in-vehicle service account on the vehicle host 320 and select at least one preset scenario mode type through the central control screen of the vehicle 30, wherein the in-vehicle service account may serve as the user's identity identifier. In the example, Figure 3 As shown, the user's identity and the preset scenario mode type can be pre-uploaded and stored in the cloud server 40 through the vehicle communication module 310. In another example, Figure 3 As shown, the cloud server 40 can also synchronize the user's identity and preset scenario mode type to the mobile terminal 20 that logs in to the corresponding in-vehicle service account, and the mobile terminal 20 saves the user's identity and preset scenario mode type.

[0036] After the exemplary description of the functions of the vehicle host 320 of the vehicle 30 , the functions of the mobile terminal 20 will be exemplarily described below.

[0037] In some embodiments of the present application, a user logs in to an in-vehicle service account on a mobile terminal 20. For example, the user logs in to the in-vehicle service account on an application on the mobile terminal 20 used to control the vehicle 30. The mobile terminal 20 reads the in-vehicle service account as the identity of the mobile terminal 20 and determines whether the mobile terminal 20 has a preset context mode type corresponding to the identity. If the mobile terminal 20 has a preset context mode type, the preset context mode type is determined to be the context mode type of the mobile terminal 20, without having to obtain the preset context mode type corresponding to the identity from the cloud server 40 or the vehicle host 320. The number of preset context mode types corresponding to the in-vehicle service account stored in the mobile terminal 20 can be one or more.

[0038] In other embodiments of the present application, when the mobile terminal 20 does not have a preset context mode type corresponding to the identity identifier, the mobile terminal 20 obtains the preset context mode type corresponding to the identity identifier from the cloud server 40 and determines that the preset context mode type is the context mode type of the mobile terminal 20. In this case, the execution system 10 of the vehicle context mode is as follows: Figure 3 The number of preset scenario mode types corresponding to the vehicle service account stored in the cloud server 40 may be one or more.

[0039] In other embodiments of the present application, when the Bluetooth module 210 of the mobile terminal 20 is turned on and receives a signal that the distance between the mobile terminal 20 and the vehicle 30 is less than a predetermined distance, for example, less than 10 meters, the Bluetooth key (not shown) on the mobile terminal 20 is activated and generates Bluetooth key information, wherein the Bluetooth key information includes at least one context mode type corresponding to the mobile terminal 20 and a pairing key for the Bluetooth key. The mobile terminal 20 broadcasts the Bluetooth key information externally via the Bluetooth module 210. The Bluetooth key may be a Bluetooth key that the user has pre-applied for on the mobile terminal 20 application and that is bound to the vehicle 30.

[0040] After the exemplary description of the functions of the mobile terminal 20 , the functions of the vehicle-mounted communication module 310 and the vehicle body controller 340 of the vehicle 30 will be exemplarily described below.

[0041] In some embodiments of the present application, the vehicle-mounted communication module 310 may be configured to receive Bluetooth key information and determine whether to trigger a context mode execution signal based on a verification result of a Bluetooth key pairing key in the Bluetooth key information. The vehicle body controller 340 may be configured to obtain the Bluetooth key information after the vehicle-mounted communication module 310 triggers the context mode execution signal and determine a vehicle control operation for at least one vehicle-control component 330 based on the Bluetooth key information, thereby controlling the at least one vehicle-control component 330 to execute a context mode according to at least one context mode type in the Bluetooth key information.

[0042] In other embodiments of the present application, there are multiple mobile terminals 20, and the number of scenario mode types for each mobile terminal 20 corresponds to the number of vehicle control components 300 that execute the scenario modes of the mobile terminal 20. The body controller 340 can control each vehicle control component 330 to execute multiple scenario modes corresponding to the multiple mobile terminals 20 according to the multiple scenario mode types.

[0043] After the exemplary description of the functions of the vehicle communication module 310 and the vehicle body controller 340 of the vehicle 30 , the UWB module 220 of the mobile terminal 20 and the UWB controller 350 of the vehicle 30 are exemplarily described below.

[0044] In some embodiments of the present application, each mobile terminal 20 further includes a UWB module 220, and the vehicle 30 further includes a UWB controller 350. In this case, the execution system 10 of the vehicle context mode is as follows: Figure 4 As shown, the UWB module 220 can be configured to transmit a broadcast signal when the mobile terminal 20 approaches the vehicle 30. The UWB controller 350 can be configured to generate location information of at least one mobile terminal 20 based on the broadcast signal continuously received within a predetermined time period, so that at least one vehicle control component 330 can execute a contextual mode based on the location information of the at least one mobile terminal 20.

[0045] In other embodiments of the present application, there are multiple mobile terminals 20, each of which corresponds to a context mode. The number of context mode types for each mobile terminal 20 corresponds to the number of vehicle control components 300 that execute the context modes of the mobile terminal 20. The body controller 340 controls each vehicle control component 330 to respectively execute multiple context modes corresponding to the multiple mobile terminals 20. When each vehicle control component 330 executes any one of the multiple context modes, each vehicle control component 330 executes the context mode based on the location information of the mobile terminal 20 corresponding to the context mode.

[0046] In other embodiments of the present application, the vehicle body controller 340 obtains the position information of at least one mobile terminal 20, and after determining the vehicle control operation, controls the component in each vehicle control component 330 whose position corresponds to the position information to execute the context mode first, and controls the component in each vehicle control component 330 whose position does not correspond to the position information to execute the context mode later.

[0047] For ease of understanding, the following uses a vehicle 30 welcome scenario as an example to illustrate the vehicle context mode execution system 10 provided by embodiments of the present application. In the vehicle 30 welcome scenario, the vehicle 30 context mode may be, for example, a welcome mode, the context mode type may be, for example, a welcome mode type, and the vehicle control component 330 may include, for example, an exterior lighting system and / or an exterior sound device. The welcome mode type corresponding to the mobile terminal 20 may include a first welcome mode type corresponding to the exterior lighting system and / or a second welcome mode type corresponding to the exterior sound device.

[0048] The following takes the welcome mode type of the mobile terminal 20 including the first welcome mode type and the second welcome mode type as an example to illustrate the process in which the vehicle 30 executes the welcome mode based on the welcome mode type of the mobile terminal 20 .

[0049] The mobile terminal 20 determines its welcome mode type according to the method described above, where the welcome mode type includes a first welcome mode type and a second welcome mode type. Upon receiving a signal that the distance between the mobile terminal 20 and the vehicle 30 is less than a predetermined distance, the Bluetooth key on the mobile terminal 20 is activated and broadcasts Bluetooth key information, where the Bluetooth key information includes the welcome mode type of the mobile terminal 20 and a pairing key for the Bluetooth key.

[0050] The vehicle communication module 310 receives the Bluetooth key information and determines a trigger signal for executing the welcome mode based on the verification result of the Bluetooth key pairing key. The module then transmits the Bluetooth key information to the vehicle body controller 340. The vehicle body controller 340 determines vehicle control operations for the exterior lighting system and the exterior sound device based on the received Bluetooth key information, controls the exterior lighting system to execute the welcome mode according to the first welcome mode type, and controls the exterior sound device to execute the welcome mode according to the second welcome mode type.

[0051] After determining the vehicle control operations of the exterior lighting system and the exterior sound device, the body controller 340 obtains the position information of the mobile terminal 20 and transmits the received position information of the mobile terminal 20 to the exterior lighting system and the exterior sound device, respectively. The position information of the mobile terminal 20 is obtained based on the method described above. When the exterior lighting system executes the first welcome mode type, the lights in the exterior lighting system whose positions match the position information of the mobile terminal 20 are illuminated first, and then the lights whose positions match the position information of the mobile terminal 20 are gradually illuminated. Similarly, when the exterior sound device executes the second welcome mode type, the sound output devices in the exterior sound device whose positions match the position information of the mobile terminal 20 are activated first, and then the sound output devices whose positions match the position information of the mobile terminal 20 are gradually activated.

[0052] After completing the exemplary description of the vehicle context model execution system 10 , the following exemplary description of the vehicle context model execution method 500 corresponding to the vehicle context model execution system 10 is given.

[0053] Figure 5 A flow chart of a method 500 for executing a vehicle context mode according to some embodiments of the present application is shown. It should be understood that the method 500 for executing a vehicle context mode may further include additional steps not shown and / or may omit the steps shown, and the scope of the present application is not limited in this respect. The method 500 for executing a vehicle context mode may be applicable to application scenarios such as a welcoming scene in the vehicle 30. It should be understood that the method 500 for executing a vehicle context mode may also be applied to other application scenarios with context modes, such as emotional care application scenarios.

[0054] like Figure 5 As shown, the execution method 500 of the vehicle context mode may include:

[0055] S51 . Generate Bluetooth key information through at least one mobile terminal 20 and broadcast it externally, wherein the Bluetooth key information at least includes at least one context mode type corresponding to the mobile terminal 20 .

[0056] S52 : In response to a vehicle 30 within a predetermined distance range of at least one mobile terminal 20 receiving Bluetooth key information, determining a vehicle control operation of at least one vehicle control component 330 requiring execution of a contextual mode according to the Bluetooth key information.

[0057] S53: Control at least one vehicle control component 330 to execute a context mode according to at least one context mode type in the Bluetooth key information.

[0058] According to some embodiments of the present application, Bluetooth key information carrying a situational mode type corresponding to the mobile terminal 20 is generated by the mobile terminal 20 and broadcast outwardly, and the vehicle 30 determines the vehicle control operation of the vehicle control component 330 based on the Bluetooth key information and controls the vehicle control component 330 to execute the situational mode according to the situational mode type selected by the mobile terminal 20, so that the vehicle 30 can execute different situational modes corresponding to different mobile terminals 20 according to the different situational mode types selected by different mobile terminals 20, thereby realizing the personalized display of the situational modes of different mobile terminals 20 by the vehicle 30.

[0059] In addition, the mobile terminal 20 can determine the situational mode type corresponding to the mobile terminal 20 and broadcast the situational mode type to the vehicle 30 in the form of Bluetooth key information. The vehicle 30 only needs to receive the Bluetooth key information and determine the vehicle control operation of the vehicle control component 330 based on the Bluetooth key information. There is no need to obtain the situational mode type corresponding to the above-mentioned mobile terminal 20 from the vehicle host 320 through the on-board communication module 310 again, ensuring that the vehicle 30 can quickly and smoothly execute the situational mode corresponding to the above-mentioned mobile terminal 20, thereby improving the personalized display effect of the situational modes of different mobile terminals 20.

[0060] For ease of understanding, the following is an exemplary description of the method 500 for executing the vehicle context mode provided in an embodiment of the present application.

[0061] First, the following exemplifies the manner in which each mobile terminal 20 determines the context mode type corresponding to the mobile terminal 20 .

[0062] In some embodiments of the present application, a user logs in to an in-vehicle service account on a mobile terminal 20. For example, the user logs in to the in-vehicle service account on an application on the mobile terminal 20 used to control the vehicle 30. The mobile terminal 20 reads the in-vehicle service account as the identity of the mobile terminal 20 and determines whether the mobile terminal 20 has a preset context mode type corresponding to the identity. If the mobile terminal 20 has a preset context mode type, the preset context mode type is determined to be the context mode type of the mobile terminal 20. The number of preset context mode types corresponding to the in-vehicle service account stored in the mobile terminal 20 can be one or more.

[0063] In other embodiments of the present application, when the mobile terminal 20 does not have a preset context mode type corresponding to the identity identifier, the mobile terminal 20 obtains the preset context mode type corresponding to the identity identifier from the cloud server 40 and determines the preset context mode type as the context mode type of the mobile terminal 20. The preset context mode type is pre-sent by the vehicle 30 to the cloud server 40. For example, the preset context mode type may be pre-sent by the vehicle host 320 to the cloud server 40 via the in-vehicle communication module 310. The number of preset context mode types corresponding to the in-vehicle service account stored in the cloud server 40 may be one or more.

[0064] The execution method of the vehicle scenario mode provided in the present application can directly determine the scenario mode type corresponding to the mobile terminal 20 through the mobile terminal 20. It can not only quickly obtain the scenario mode type of the mobile terminal 20 and ensure that the vehicle 30 smoothly executes the scenario mode corresponding to the mobile terminal 20, but also reduce the burden on the vehicle communication module 310 and reduce the cost of the vehicle communication module 310.

[0065] After completing the exemplary description of the manner in which each mobile terminal 20 determines the type of the situation mode corresponding to the mobile terminal 20 , the manner in which the vehicle 30 obtains the location information of the mobile terminal 20 is exemplarily described below.

[0066] In some embodiments of the present application, the method of obtaining the location information of the mobile terminal 20 through the vehicle-mounted communication module 310 of the vehicle 30 includes but is not limited to: obtaining the location information of the mobile terminal 20 through the communication module A 311 and / or the communication module B 312. For example, if the block diagram of the vehicle 30 is as follows Figure 2a As shown, the vehicle 30 can obtain the location information of the mobile terminal 20 through the communication module A 311; if the block diagram of the vehicle 30 is as shown Figure 2b As shown, the vehicle can obtain the location information of the mobile terminal 20 through the communication module A 311 , and can also obtain the location information of the mobile terminal 20 through the communication module B 312 .

[0067] As an example, the location information of the mobile terminal 20 may include distance information between the mobile terminal 20 and the vehicle 30. For example, the vehicle communication module 310 may determine the distance between itself and the Bluetooth module 210 of the mobile terminal 20 by time of flight (ToF) measurement.

[0068] It should be understood that, without departing from the teachings of this application, the on-board communication module 310 may also use methods other than ToF to determine the distance between itself and the Bluetooth module 210 of the mobile terminal 20. This application does not limit the manner in which the on-board communication module 310 determines the distance between itself and the Bluetooth module 210 of the mobile terminal 20.

[0069] After completing the exemplary description of the manner in which the vehicle 30 obtains the location information of the mobile terminal 20 , the manner in which each mobile terminal 20 generates Bluetooth key information and broadcasts it externally is now exemplified.

[0070] In some embodiments of the present application, when the Bluetooth module 210 of the mobile terminal 20 is turned on and receives a signal that the distance between the mobile terminal 20 and the vehicle 30 is less than a predetermined distance, for example, less than 10 meters, the Bluetooth key on the mobile terminal 20 is activated and generates Bluetooth key information, wherein the Bluetooth key information includes at least one context mode type corresponding to the mobile terminal 20 and a pairing key for the Bluetooth key. The mobile terminal 20 broadcasts the Bluetooth key information externally via the Bluetooth module 210.

[0071] After completing the exemplary description of how each mobile terminal 20 generates Bluetooth key information and broadcasts it externally, the following exemplary description is given of how the vehicle 30 determines the vehicle control operation of at least one vehicle control component 330 that needs to execute a scenario mode based on the Bluetooth key information of at least one mobile terminal 20.

[0072] In some embodiments of the present application, there is one mobile terminal 20. The in-vehicle communication module 310 can receive Bluetooth key information broadcasted by the mobile terminal 20 and determine whether to trigger a context mode execution signal based on the verification result of the Bluetooth key pairing key in the Bluetooth key information. If the in-vehicle communication module 310 verifies that the Bluetooth key pairing key is correct, it determines that the Bluetooth key is a match for the vehicle 30 and triggers a context mode execution signal. If the in-vehicle communication module 310 verifies that the Bluetooth key pairing key is incorrect, it determines that the Bluetooth key is not a match for the vehicle 30 and does not trigger a context mode execution signal.

[0073] The body controller 340 can obtain the Bluetooth key information after the on-board communication module 310 triggers the scenario mode execution signal and determine the vehicle control operation of at least one vehicle control component 330 based on the Bluetooth key information, so as to control at least one vehicle control component 330 to execute the scenario mode according to at least one scenario mode type in the Bluetooth key information.

[0074] In other embodiments of the present application, there are multiple mobile terminals 20, each of which corresponds to a Bluetooth key, a Bluetooth key pairing key, and at least one context mode type. The number of context mode types for each mobile terminal 20 corresponds to the number of vehicle control components 300 that execute the context mode of the mobile terminal 20.

[0075] The in-vehicle communication module 310 can receive multiple Bluetooth key information broadcasted by multiple mobile terminals 20 and determine whether to trigger a scenario mode execution signal based on the verification results of the Bluetooth key pairing keys in the multiple Bluetooth key information. If the in-vehicle communication module 310 verifies that the Bluetooth key pairing key in at least one Bluetooth key information is correct, it determines that the Bluetooth key of at least one mobile terminal 20 is a match with the vehicle 30, and the scenario mode execution signal is triggered. If the in-vehicle communication module 310 verifies that the Bluetooth key pairing keys in all the multiple Bluetooth key information are incorrect, it determines that the Bluetooth keys of the multiple mobile terminals 20 are not a match with the vehicle 30, and the scenario mode execution signal is not triggered. The mobile terminal 20 whose Bluetooth key is matched with the vehicle 30 is referred to as the target mobile terminal.

[0076] After the vehicle communication module 310 triggers the context mode execution signal, the vehicle body controller 340 can obtain the Bluetooth key information of all target mobile terminals and, based on the Bluetooth key information, determine at least one vehicle control component 330 to execute the vehicle control operation of the context mode of any target mobile terminal, thereby controlling the at least one vehicle control component 330 to execute the context mode of any target mobile terminal. The number of target mobile terminals can be one or more.

[0077] For ease of understanding, the following exemplary description is given by assuming that the multiple mobile terminals 20 include a first mobile terminal and a second mobile terminal.

[0078] As an example, the mobile terminal 20 includes a first mobile terminal and a second mobile terminal, wherein the first mobile terminal corresponds to first Bluetooth key information including at least a first scenario mode type and a first scenario mode, and the second mobile terminal corresponds to second Bluetooth key information including at least a second scenario mode type and a second scenario mode. The number of each of the first scenario mode type and the second scenario mode type is at least one.

[0079] The in-vehicle communication module 310 can receive the first Bluetooth key information and the second Bluetooth key information and determine whether to trigger a contextual mode execution signal based on the verification result of the Bluetooth key pairing key in the first Bluetooth key information and the second Bluetooth key information. If the in-vehicle communication module 310 verifies that the Bluetooth key pairing key in the first Bluetooth key information and / or the second Bluetooth key information is correct, it is determined that the Bluetooth key of the first mobile terminal and / or the second mobile terminal is a match with the vehicle 30, and the contextual mode execution signal is triggered. If the in-vehicle communication module 310 verifies that the Bluetooth key pairing key in both the first Bluetooth key information and the second Bluetooth key information is incorrect, it is determined that the Bluetooth key of the first mobile terminal and / or the second mobile terminal is not a match with the vehicle 30, and the contextual mode execution signal is not triggered.

[0080] If only the Bluetooth key of the first mobile terminal is matched with the vehicle 30, after the vehicle communication module 310 triggers the scenario mode execution signal, the body controller 340 obtains the first Bluetooth key information and, based on the first Bluetooth key information, determines that at least one vehicle control component 330 executes a first vehicle control operation of the first scenario mode, thereby controlling the at least one vehicle control component 330 to execute the first scenario mode according to the first scenario mode type. The first mobile terminal herein corresponds to the target mobile terminal described above.

[0081] If only the Bluetooth key of the second mobile terminal is matched with the vehicle 30, after the vehicle communication module 310 triggers the context mode execution signal, the body controller 340 obtains the second Bluetooth key information and, based on the second Bluetooth key information, determines that at least one vehicle control component 330 executes a second vehicle control operation of the second context mode, thereby controlling the at least one vehicle control component 330 to execute the second context mode according to the second context mode type. The second mobile terminal herein corresponds to the target mobile terminal described above.

[0082] If both the first and second mobile terminals' Bluetooth keys are paired with the vehicle 30 , after the vehicle-mounted communication module 310 triggers the scenario mode execution signal, the vehicle body controller 340 obtains the first and second Bluetooth key information and, based on the first Bluetooth key information, determines that at least one vehicle control component 330 executes a first vehicle control operation in the first scenario mode and, based on the second Bluetooth key information, determines that the vehicle control component 330 executes a second vehicle control operation in the second scenario mode, thereby controlling the at least one vehicle control component 330 to execute the first and second scenario modes, respectively. The first and second mobile terminals herein both correspond to the target mobile terminal described above.

[0083] The method for executing the vehicle scenario mode provided in this application is that the vehicle-mounted communication module 310 can determine the triggering of the scenario mode execution signal after verifying that the pairing key of the Bluetooth key is correct. There is no need to obtain the scenario mode type corresponding to the above-mentioned mobile terminal 20 from the vehicle host 320 through the vehicle-mounted communication module 310, and the body controller 340 can determine the vehicle control operation of the vehicle control component 330 according to the scenario mode type, thereby ensuring that the vehicle 30 can quickly and smoothly execute the scenario mode corresponding to the above-mentioned mobile terminal 20.

[0084] After completing the exemplary description of the method in which the vehicle 30 determines the vehicle control operation of at least one vehicle control component 330 that needs to execute a scenario mode based on the Bluetooth key information of at least one mobile terminal 20, the following exemplary description is given of the method of controlling at least one vehicle control component 330 to execute a scenario mode according to at least one scenario mode type in the Bluetooth key information.

[0085] In some embodiments of the present application, there is only one mobile terminal 20. After determining a vehicle control operation of at least one vehicle control component 330 based on the Bluetooth key information corresponding to the mobile terminal 20, the vehicle body controller 340 controls the at least one vehicle control component 330 to execute a context mode corresponding to the mobile terminal 20 according to at least one context mode type of the mobile terminal 20.

[0086] In other embodiments of the present application, there are multiple mobile terminals 20, each of which corresponds to a Bluetooth key, a Bluetooth key pairing key, and at least one context mode type. Each mobile terminal 20 corresponds to a context mode. The number of context mode types for each mobile terminal 20 corresponds to the number of vehicle control components 300 that execute the context mode of the mobile terminal 20.

[0087] The Bluetooth keys of multiple mobile terminals 20 are all matched with the vehicle 30, and the body controller 340 determines the vehicle control operation of each vehicle control component 330 based on the multiple Bluetooth key information of the multiple mobile terminals 20, and controls each vehicle control component 330 to execute multiple situation modes corresponding to the multiple mobile terminals 20 according to multiple situation mode types.

[0088] Some mobile terminals 20 have Bluetooth keys that are paired with the vehicle 30. These mobile terminals 20 with Bluetooth keys that are paired with the vehicle 30 are referred to as target mobile terminals. The vehicle body controller 340 determines the vehicle control operation of each vehicle control component 330 based on the Bluetooth key information of the target mobile terminals and then controls each vehicle control component 330 to execute a context mode corresponding to the target mobile terminal. There is at least one target mobile terminal.

[0089] The vehicle scenario mode execution method provided in this application enables the vehicle control component 330 to execute multiple scenario modes corresponding to multiple mobile terminals 20 according to multiple scenario mode types, thereby realizing personalized display of the scenario modes of multiple mobile terminals 20 by the vehicle 30.

[0090] In other embodiments of the present application, after determining the vehicle control operation of at least one vehicle control component 330, the body controller 340 may further control the at least one vehicle control component 330 to execute a contextual mode based on the location information of at least one mobile terminal 20. For example, the body controller 340 may obtain the location information of at least one mobile terminal 20 and, after determining the vehicle control operation of each vehicle control component 330, control the components in each vehicle control component 330 whose positions correspond to the location information to execute the contextual mode first, and control the components in each vehicle control component 330 whose positions do not correspond to the location information to execute the contextual mode later.

[0091] Among them, the method for obtaining the location information of at least one mobile terminal 20 includes but is not limited to: when at least one mobile terminal 20 approaches the vehicle 30, a broadcast signal is sent through the UWB module 220 of at least one mobile terminal 20; and the UWB controller 350 of the vehicle 30 continuously receives the broadcast signal within a predetermined time period and generates the location information of at least one mobile terminal 20.

[0092] In other embodiments of the present application, there is only one mobile terminal 20. After determining the vehicle control operation of at least one vehicle control component 330 based on the Bluetooth key information corresponding to the mobile terminal 20, the vehicle body controller 340 obtains the location information of the mobile terminal 20 and controls each vehicle control component 330 to execute a context mode corresponding to the mobile terminal 20 based on the location information of the mobile terminal 20.

[0093] In other embodiments of the present application, there are multiple mobile terminals 20, each of which corresponds to a Bluetooth key, a Bluetooth key pairing key, and at least one context mode type. Each mobile terminal 20 corresponds to a context mode. The number of context mode types for each mobile terminal 20 corresponds to the number of vehicle control components 300 that execute the context mode of the mobile terminal 20.

[0094] The Bluetooth keys of multiple mobile terminals 20 are all matched with the vehicle 30, and the body controller 340 determines the vehicle control operation of each vehicle control component 330 based on the multiple Bluetooth key information of the multiple mobile terminals 20, obtains the orientation information of the multiple mobile terminals 20, and controls each vehicle control component 330 to execute multiple scenario modes corresponding to the multiple mobile terminals 20. When each vehicle control component 330 executes any scenario mode among the multiple scenario modes, each vehicle control component 330 executes the scenario mode based on the orientation information of the mobile terminal 20 corresponding to the scenario mode.

[0095] Some mobile terminals 20 have Bluetooth keys that are paired with the vehicle 30. These mobile terminals 20 with Bluetooth keys that are paired with the vehicle 30 are referred to as target mobile terminals. The vehicle body controller 340 determines the vehicle control operation of each vehicle control component 330 based on the Bluetooth key information of the target mobile terminals, obtains the location information of the target mobile terminals, and controls each vehicle control component 330 to execute a context mode corresponding to the target mobile terminal based on the location information of the target mobile terminals. There is at least one target mobile terminal.

[0096] For ease of understanding, the following exemplary description is given by assuming that the multiple mobile terminals 20 include a first mobile terminal and a second mobile terminal.

[0097] As an example, the mobile terminal 20 includes a first mobile terminal and a second mobile terminal, wherein the first mobile terminal corresponds to first Bluetooth key information including at least a first scenario mode type, first location information, and a first scenario mode, and the second mobile terminal corresponds to second Bluetooth key information including at least a second scenario mode type, second location information, and a second scenario mode. The number of each of the first scenario mode type and the second scenario mode type is at least one.

[0098] If only the Bluetooth key of the first mobile terminal is paired with the vehicle 30, the vehicle body controller 340 determines, based on the first Bluetooth key information, that at least one vehicle control component 330 is executing a first vehicle control operation in a first scenario mode. It then obtains first location information and controls at least one vehicle control component 330 to execute the first scenario mode based on the first location information. For example, each vehicle control component 330 whose location corresponds to the first location information is controlled to execute the first scenario mode first, and each vehicle control component 330 whose location does not correspond to the first location information is controlled to execute the first scenario mode later. The first mobile terminal in this context corresponds to the target mobile terminal described above.

[0099] If only the Bluetooth key of the second mobile terminal is paired with the vehicle 30, the body controller 340 determines, based on the second Bluetooth key information, that at least one vehicle-control component 330 is executing the second vehicle-control operation in the second scenario mode. It then obtains the second location information and controls the at least one vehicle-control component 330 to execute the second scenario mode based on the second location information. For example, each vehicle-control component 330 whose location corresponds to the second location information is controlled to execute the second scenario mode first, and each vehicle-control component 330 whose location does not correspond to the second location information is controlled to execute the second scenario mode later. The second mobile terminal in this case corresponds to the target mobile terminal described above.

[0100] If the Bluetooth keys of the first and second mobile terminals are both paired with the vehicle 30, the vehicle body controller 340 determines, based on the first and second Bluetooth key information, that at least one vehicle control component 330 is to perform a first vehicle control operation in a first scenario mode and at least one vehicle control component 330 is to perform a second vehicle control operation in a second scenario mode. The vehicle body controller 340 then obtains the first and second position information and controls each vehicle control component 330 to perform the first scenario mode based on the first position information and the second scenario mode based on the second position information. The first and second mobile terminals herein both correspond to the target mobile terminal.

[0101] The method for executing the vehicle scenario mode provided in the present application is that the body controller 340 controls the vehicle control component 330 to execute the scenario mode based on the orientation information of at least one mobile terminal 20, so that components in different orientation orders in the vehicle control component 330 execute the scenario mode in sequence. For example, the component in the vehicle control component 330 close to the mobile terminal 20 executes the scenario mode first, and the component far away from the mobile terminal 20 executes the scenario mode later, thereby enhancing the interactivity and ritual sense of the vehicle 30.

[0102] For ease of understanding, the following illustrative example illustrates the method 500 for executing a vehicle context mode provided by an embodiment of the present application using a vehicle 30 welcoming scenario. In the vehicle 30 welcoming scenario, the vehicle 30 context mode may be, for example, a welcoming mode, the context mode type may be, for example, a welcoming mode type, and the vehicle control component 330 may include, for example, an exterior lighting system and / or an exterior sound device. The welcoming mode type corresponding to the mobile terminal 20 may include a first welcoming mode type corresponding to the exterior lighting system and / or a second welcoming mode type corresponding to the exterior sound device.

[0103] The following takes the vehicle control component 330 including the exterior lighting system and the exterior sound device as an example to illustrate the interactive process of the vehicle 30 executing the welcome mode based on the welcome mode type of the mobile terminal 20.

[0104] Figure 6a is an interactive diagram of the mobile terminal 20 determining its welcome mode type in some embodiments of the present application, Figure 6b It is a schematic diagram of the interaction between the mobile terminal 20 and the vehicle 30 in some embodiments of the present application. Figure 6c It is a schematic diagram of the interaction between the vehicle body controller 340 and the vehicle control component 330 in some embodiments of the present application.

[0105] like Figures 6a to 6c As shown, the vehicle 30 may perform the welcome mode based on the welcome mode type of the mobile terminal 20, including the following steps:

[0106] S601: Upon detecting a login to an in-vehicle service account, the mobile terminal 20 determines whether a preset welcome mode type corresponding to the in-vehicle service account is locally stored. The preset welcome mode type includes a first preset welcome mode type corresponding to an exterior vehicle lighting system and a second preset welcome mode type corresponding to an exterior vehicle sound device.

[0107] S602: If a preset welcome mode type corresponding to the in-vehicle service account is locally stored, the mobile terminal 20 reads the locally stored preset welcome mode type corresponding to the in-vehicle service account as the welcome mode type of the mobile terminal 20. The welcome mode type of the mobile terminal 20 includes a first welcome mode type corresponding to an exterior vehicle lighting system and a second welcome mode type corresponding to an exterior vehicle sound device.

[0108] S603: If the preset welcome mode type corresponding to the in-vehicle service account is not stored locally, a first request for obtaining the preset welcome mode type corresponding to the in-vehicle service account is sent to the cloud server 40.

[0109] S604 : After receiving the first request, the cloud server 40 feeds back the preset welcome mode type corresponding to the in-vehicle service account to the mobile terminal 20 .

[0110] S605 : After receiving the preset welcome mode type corresponding to the in-vehicle service account from the cloud server 40 , the mobile terminal 20 determines that the preset welcome mode type corresponding to the in-vehicle service account from the cloud server 40 is the welcome mode type of the mobile terminal 20 .

[0111] S606: Upon receiving a signal that the distance between the mobile terminal 20 and the vehicle 30 is less than a predetermined distance, the Bluetooth key on the mobile terminal 20 is activated and broadcasts Bluetooth key information, wherein the Bluetooth key information includes the welcome mode type of the mobile terminal 20 and the pairing key of the Bluetooth key.

[0112] S607 , the vehicle communication module 310 receives the Bluetooth key information and determines a trigger signal for executing the welcome mode according to a verification result of the pairing key of the Bluetooth key.

[0113] S608 , after determining that the welcome mode execution signal is triggered, the vehicle communication module 310 sends the above-mentioned Bluetooth key information to the vehicle body controller 340 .

[0114] S609 : The vehicle body controller 340 determines the vehicle control operations of the exterior lighting system and the exterior sound device respectively according to the received Bluetooth key information.

[0115] S610: The vehicle body controller 340 sends a first control instruction to the exterior lighting system to execute a welcome mode according to a first welcome mode type.

[0116] S611: The vehicle body controller 340 sends a second control instruction to the vehicle exterior sound emitting device to execute the welcome mode according to the second welcome mode type.

[0117] S612: Upon receiving the first control instruction, the exterior lighting system executes a welcome mode according to the first welcome mode type.

[0118] S613: Upon receiving the second control instruction, the vehicle exterior sound emitting device executes the welcome mode according to the second welcome mode type.

[0119] In some other embodiments of the present application, the vehicle 30 executing the welcome mode based on the welcome mode type of the mobile terminal 20 may further include the following steps:

[0120] S614 : Upon receiving a signal indicating that the distance between the mobile terminal 20 and the vehicle 30 is less than a predetermined distance, the UWB module 220 on the mobile terminal 20 sends a broadcast signal.

[0121] S615 : The UWB controller 350 of the vehicle 30 generates the position information of the mobile terminal 20 based on the broadcast signal continuously received within a predetermined period of time.

[0122] S616 : After determining the vehicle control operations of the exterior lighting system and the exterior sound device, the vehicle body controller 340 sends a second request to the UWB controller 350 for obtaining the position information of the mobile terminal 20 .

[0123] S617 . Upon receiving the second request, the UWB controller 350 feeds back the position information of the mobile terminal 20 to the vehicle body controller 340 .

[0124] S618: The vehicle body controller 340 sends the received position information of the mobile terminal 20 to the exterior lighting system and the exterior sound device respectively.

[0125] S619: After receiving the position information of the mobile terminal 20, the exterior lighting system executes the welcome mode according to the position information of the mobile terminal 20 and the first welcome mode type.

[0126] S620: Upon receiving the position information of the mobile terminal 20, the vehicle exterior sound emitting device executes the welcome mode according to the position information of the mobile terminal 20 and the second welcome mode type.

[0127] It should be understood that the number and type of vehicle control components 330 that execute the welcome mode of the vehicle 30 are only examples. The number and type of vehicle control components 330 that execute the welcome mode of the vehicle 30 can be other numbers and other types, and are not limited here.

[0128] The steps of the various methods above are divided only for the purpose of clear description. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0129] An embodiment of the present application also provides an electronic device, which includes at least one processor and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute one or more steps of the above-mentioned vehicle scenario mode execution method 500.

[0130] The embodiments of the present application further provide a non-transitory computer-readable storage medium having machine-executable instructions stored thereon. When the machine-executable instructions are executed, the machine executes one or more steps of the above-mentioned vehicle scenario mode execution method 500.

[0131] Figure 7 Schematically shows a block diagram of an electronic device 700 suitable for implementing the embodiments of the present application. Figure 7 As shown, electronic device 700 includes a processor 701, which can perform various appropriate steps and processes according to computer program instructions stored in a read-only memory (ROM) 702 or computer program instructions loaded from a memory 708 into a random access memory (RAM) 703. Various programs and data required for the operation of electronic device 700 can also be stored in RAM 703. Processor 701, ROM 702, and RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to bus 704.

[0132] Various components in electronic device 700 are connected to I / O interface 705, including: an input unit 706; an output unit 707; a memory 708, including any medium for storing computer-executable programs; and a communication unit 709, such as a network card, a modem, a wireless communication transceiver, etc. Communication unit 709 allows electronic device 700 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0133] The processor 701 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 701 can perform the various methods and processes described above, such as executing one or more steps of the vehicle context mode execution method 500. For example, in some embodiments, one or more steps of the vehicle context mode execution method 500 can be implemented as a computer software program stored in a machine-readable medium, such as the memory 708. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 700 via the ROM 702 and / or the communication unit 709. When the computer program is loaded into the RAM 703 and executed by the processor 701, one or more steps of the vehicle context mode execution method 500 described above can be executed. Alternatively, in other embodiments, the processor 701 may be configured to execute one or more steps in the above-mentioned vehicle context mode execution method 500 in any other appropriate manner (for example, by means of firmware).

[0134] Various aspects of the present application are described herein with reference to flowcharts and / or step diagrams of methods, devices (systems), and computer program products according to exemplary embodiments of the present application. It should be understood that each step of the flowcharts and / or step diagrams, as well as combinations of the steps in the flowcharts and / or step diagrams, can be implemented by computer-readable program instructions.

[0135] These computer-readable program instructions can be provided to a processor in a voice interaction device, a general-purpose computer, a special-purpose computer, or a processing unit of another programmable data processing device, thereby producing a machine such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / steps specified in one or more steps in the flowchart and / or step diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / steps specified in one or more steps in the flowchart and / or step diagram.

[0136] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / steps specified in one or more steps in the flowchart and / or step diagram.

[0137] The flowcharts and step diagrams in the accompanying drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each step in the flowchart or step diagram can represent a part of a module, program segment or instruction, and a part of this module, program segment or instruction contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the steps can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each step in the step diagram and / or flowchart, and the combination of the steps in the step diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0138] The above description is merely an exemplary embodiment of the present application and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of protection involved in this application is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the technical concept. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for executing a vehicle context mode, characterized in that: include: forming Bluetooth key information through at least one mobile terminal and broadcasting the information externally, wherein the Bluetooth key information at least includes at least one context mode type corresponding to the mobile terminal; In response to a vehicle within a predetermined distance range of the at least one mobile terminal receiving the Bluetooth key information, determining a vehicle control operation of at least one vehicle control component requiring execution of a contextual mode according to the Bluetooth key information; and controlling the at least one vehicle control component to execute the context mode according to the at least one context mode type in the Bluetooth key information; Also includes: In response to the at least one mobile terminal approaching the vehicle, sending a broadcast signal through a UWB module of the at least one mobile terminal; and In response to continuously receiving the broadcast signal within a predetermined time period, generating, by the UWB controller of the vehicle, location information of the at least one mobile terminal, so that the at least one vehicle control component executes the context mode based on the location information of the at least one mobile terminal; Wherein, controlling the at least one vehicle control component to execute the context mode according to the at least one context mode type in the Bluetooth key information includes: The vehicle body controller acquires the position information of the at least one mobile terminal; and In response to determining the vehicle control operation, the body controller controls each vehicle control component whose position corresponds to the orientation information to execute the situational mode first, and each vehicle control component whose position does not correspond to the orientation information to execute the situational mode later.

2. The method according to claim 1, wherein Before forming Bluetooth key information through at least one mobile terminal and broadcasting it externally, the method further includes: Obtaining the identity of the mobile terminal; and The context mode type of the mobile terminal is determined according to whether the mobile terminal has a preset context mode type corresponding to the identity identifier.

3. The method according to claim 2, wherein: Determining the context mode type of the mobile terminal according to whether the mobile terminal has a preset context mode type corresponding to the identity identifier includes: In response to the mobile terminal not having the preset scenario mode type, obtaining the preset scenario mode type from a cloud server and determining the preset scenario mode type as the scenario mode type of the mobile terminal, wherein the preset scenario mode type is sent to the cloud server in advance by the vehicle.

4. The method according to claim 2, wherein: Determining the context mode type of the mobile terminal according to whether the mobile terminal has a preset context mode type corresponding to the identity identifier includes: In response to the mobile terminal having the preset context mode type, the preset context mode type is determined to be the context mode type of the mobile terminal.

5. The method according to claim 2, wherein: Obtaining the identity of the mobile terminal includes: In response to the mobile terminal logging into the in-vehicle service account, the in-vehicle service account is determined to be the identity identifier of the mobile terminal.

6. The method according to any one of claims 1 to 5, wherein The Bluetooth key information further includes a pairing key of the Bluetooth key of the mobile terminal, wherein determining, based on the Bluetooth key information, a vehicle control operation of at least one vehicle control component requiring execution of a context mode includes: determining whether the vehicle-mounted communication module of the vehicle triggers a context mode execution signal according to a verification result of the pairing key of the Bluetooth key; and In response to triggering the scenario mode execution signal, the vehicle body controller obtains the Bluetooth key information and determines the vehicle control operation according to the Bluetooth key information.

7. The method according to any one of claims 1 to 5, wherein The at least one mobile terminal includes a plurality of mobile terminals, wherein controlling the at least one vehicle control component to execute the context mode according to the at least one context mode type in the Bluetooth key information includes: Each of the vehicle control components is controlled to respectively execute a plurality of the scenario modes corresponding to the plurality of mobile terminals according to a plurality of scenario mode types.

8. The method according to claim 1, wherein The at least one mobile terminal includes a plurality of mobile terminals, wherein controlling the at least one vehicle control component to execute the context mode according to the at least one context mode type in the Bluetooth key information includes: Control each of the vehicle control components to respectively execute multiple scenario modes corresponding to the multiple mobile terminals, wherein when each of the vehicle control components executes any one of the multiple scenario modes, each of the vehicle control components executes the scenario mode based on the orientation information of the mobile terminal corresponding to the scenario mode.

9. A vehicle scenario mode execution system, characterized in that: include: At least one mobile terminal is configured to: generate and broadcast Bluetooth key information, wherein the Bluetooth key information includes at least one context mode type corresponding to the mobile terminal; wherein each mobile terminal further includes a UWB module, and the vehicle further includes a UWB controller; wherein the UWB module is configured to emit a broadcast signal when the at least one mobile terminal approaches the vehicle; and wherein the UWB controller is configured to generate location information of the at least one mobile terminal based on the broadcast signal, so that the at least one vehicle control component executes the context mode based on the location information of the at least one mobile terminal; and A vehicle is configured to: in response to the vehicle receiving the Bluetooth key information, determine the vehicle control operation of at least one vehicle control component that needs to execute the scenario mode based on the Bluetooth key information, wherein, in response to continuously receiving the broadcast signal within a predetermined time period, generate the orientation information of the at least one mobile terminal through the UWB controller of the vehicle, so that the at least one vehicle control component executes the scenario mode based on the orientation information of the at least one mobile terminal; and control the at least one vehicle control component to execute the scenario mode according to the at least one scenario mode type in the Bluetooth key information, and controlling the at least one vehicle control component to execute the scenario mode according to the at least one scenario mode type in the Bluetooth key information includes: the body controller of the vehicle obtains the orientation information of the at least one mobile terminal; and in response to determining the vehicle control operation, the body controller controls each component in the vehicle control component whose position corresponds to the orientation information to execute the scenario mode first, and each component in the vehicle control component whose position does not correspond to the orientation information to execute the scenario mode later.

10. The system according to claim 9, wherein: Each of the mobile terminals is further configured to: read the identity identifier of the mobile terminal; in response to the absence of a preset scenario mode type corresponding to the identity identifier of the mobile terminal, obtain the preset scenario mode type from the cloud server and determine that the preset scenario mode type is the scenario mode type of the mobile terminal, wherein the preset scenario mode type is sent to the cloud server in advance by the vehicle.

11. The system according to claim 9, wherein: Each of the mobile terminals is further configured to: read the identity identifier of the mobile terminal; and in response to the presence of a preset context mode type corresponding to the identity identifier of the mobile terminal, determine the preset context mode type as the context mode type of the mobile terminal.

Images