Vehicle control method, device and vehicle

Abstract

The present disclosure provides a vehicle control method and device, and a vehicle, and relates to the technical fields of intelligent control and intelligent cabin. The vehicle control method is applied to a vehicle terminal device of a vehicle, the vehicle is deployed with an NFC tag, and the method comprises the following steps: in response to receiving a connection request from a mobile device, establishing a connection channel with the mobile device, the connection request being generated based on trigger data stored in the NFC tag; sending at least one control item associated with the vehicle to the mobile device via the connection channel; and in response to receiving a first control instruction corresponding to a target control item in the at least one control item, controlling the vehicle based on the first control instruction. Thus, the connection efficiency of the vehicle terminal device and the mobile device can be improved, and the convenience of vehicle control can be improved.

Description

Technical Field

[0001] This disclosure relates to the fields of intelligent control and intelligent cockpit technology, and in particular to a vehicle control method, device and vehicle. Background Technology

[0002] In related technologies, the implementation of solutions such as using terminal devices to control vehicles and transferring content between terminals and vehicles is generally centered on vehicle owners or authorized users. Passengers often need to download matching application software, log in to their accounts, and then obtain authorization in order to interact with the vehicle. The operation process is complicated and has a high threshold. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides a vehicle control method, device and vehicle.

[0004] According to a first aspect of this disclosure, a vehicle control method is provided, applied to a vehicle-side device, wherein the vehicle is equipped with an NFC tag. The method includes: in response to receiving a connection request from a mobile device, establishing a connection channel with the mobile device, the connection request being generated based on trigger data stored in the NFC tag; sending at least one control item associated with the vehicle to the mobile device via the connection channel; and in response to receiving a first control command corresponding to a target control item among the at least one control item, controlling the vehicle based on the first control command.

[0005] According to a second aspect of this disclosure, a vehicle control method is provided, applied to a mobile device, the method comprising: establishing a connection channel with a vehicle-side device of a vehicle in response to detecting a second triggering event of an NFC tag, the NFC tag being deployed in the vehicle; presenting at least one control item associated with the vehicle, the at least one control item being received via the connection channel; and sending a first control command corresponding to the target control item to the vehicle-side device in response to a triggering operation of a target control item among the at least one control item, to control the vehicle.

[0006] According to a third aspect of this disclosure, a vehicle control device is provided, applied to a vehicle-side device of a vehicle, the vehicle being equipped with an NFC tag. The device includes a first connection establishment module, a content transmission module, and a vehicle control module. The first connection establishment module is configured to establish a connection channel with a mobile device in response to receiving a connection request from a mobile device, the connection request being generated based on trigger data stored in the NFC tag. The content transmission module is configured to send at least one control item associated with the vehicle to the mobile device via the connection channel. The vehicle control module is configured to control the vehicle based on the first control instruction in response to receiving a first control instruction corresponding to a target control item among the at least one control item.

[0007] According to a fourth aspect of this disclosure, a vehicle control device is provided for use in a mobile device. The device includes a second connection module, a content presentation module, and a first transmission module. The second connection module is configured to establish a connection channel with a vehicle-side device in response to detecting a second trigger event with an NFC tag deployed in the vehicle. The content presentation module is configured to present at least one control item associated with the vehicle, the at least one control item being received via the connection channel. The first transmission module is configured to send a first control command corresponding to the target control item to the vehicle-side device in response to a trigger operation on a target control item among the at least one control item, to control the vehicle.

[0008] According to a fifth aspect of this disclosure, a vehicle is provided, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute the executable instructions to implement the vehicle control method provided in the first aspect above.

[0009] According to a sixth aspect of this disclosure, a non-transitory computer-readable storage medium is provided, which, when executed by a processor, enables the processor to perform the vehicle control method provided in the first or second aspect described above.

[0010] The technical solutions provided by the embodiments of this disclosure can include the following beneficial effects: by deploying NFC tags in vehicles and storing trigger data for connecting to vehicle-side devices in the NFC tags, the NFC tags can trigger mobile devices to automatically connect to vehicle-side devices, thereby realizing vehicle control or content transfer between the vehicle and various devices. Therefore, this solution can significantly reduce user operating costs, improve the connection efficiency between mobile devices and vehicle-side devices, and enhance user convenience.

[0011] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

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

[0013] Figure 1 This is a schematic diagram of a scenario in which the vehicle control method disclosed herein can be implemented.

[0014] Figure 2 This is a flowchart illustrating a vehicle control method according to some embodiments of the present disclosure.

[0015] Figure 3 This is a flowchart illustrating a data writing process according to some embodiments of the present disclosure.

[0016] Figure 4 This is a flowchart illustrating a vehicle control method according to some embodiments of the present disclosure.

[0017] Figure 5 This is a structural block diagram of a vehicle control device according to some embodiments of the present disclosure.

[0018] Figure 6 This is a structural block diagram of a vehicle control device according to some embodiments of the present disclosure.

[0019] Figure 7 This is a functional block diagram of a vehicle illustrating an exemplary embodiment. Detailed Implementation

[0020] Some embodiments of this disclosure will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. Various changes, modifications, and equivalents of the methods, apparatus, and / or systems described herein will become apparent upon understanding this disclosure. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but can be changed as will become apparent upon understanding this disclosure, except for operations that must be performed in a particular order. Furthermore, for clarity and brevity, descriptions of features known in the art may be omitted.

[0021] It should be understood that, unless otherwise specifically indicated, features of various embodiments of this disclosure described herein can be combined with each other. As used herein, the term “and / or” includes any one of the relevant listed items and any combination of any two or more; similarly, “at least one of…” includes any one of the relevant listed items and any combination of any two or more.

[0022] In this document, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description herein, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0023] The embodiments described in the following examples of this disclosure are not representative of all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0024] As mentioned earlier, in related technologies, if ordinary passengers need to control or transfer content between terminal devices and vehicles, they often need to download matching application software, log in to an account, and then obtain authorization. The operation process is complicated and has a high threshold, and the temporary use cost for passengers is also high.

[0025] With the development of NFC (Near Field Communication) technology, near-field "tap-to-pay" interaction is gradually entering people's lives. However, most existing "tap-to-pay" solutions can only be bound to a single operating system. For different operating systems, not only is it necessary to deploy corresponding software support, but it is also necessary to deploy corresponding hardware support. It is not possible to share the same hardware entry point between operating systems across different ecosystems.

[0026] In addition, the existing "tap to tap" solution can only achieve "static jump", and one tag can only correspond to one fixed action, such as opening or payment, and cannot trigger business distribution or interaction based on the terminal context. Moreover, the writing of tag data depends on a dedicated card writing device or factory preset. Users cannot write or rewrite according to the needs of the scenario. Even if they rewrite it themselves, they need a special program or auxiliary tool, which is extremely difficult for ordinary users.

[0027] This disclosure provides a vehicle control method that utilizes near-field communication (NFC) tags and stored trigger data for connecting to vehicle-side devices. By using NFC tags as a medium, a connection channel can be quickly established between mobile devices and vehicle-side devices, thereby enabling vehicle control or content transfer between vehicle-side and mobile devices, effectively improving connection efficiency and enhancing the convenience of vehicle control.

[0028] Figure 1 This is a schematic diagram of an exemplary scenario 100 that can implement the vehicle control method of this disclosure. (See reference...) Figure 1 As shown, in some examples, example scenario 100 includes vehicle-mounted device 110 and NFC tag 120 deployed in the vehicle, and also includes mobile device 130.

[0029] In this embodiment, the vehicle can be any type of vehicle capable of carrying people and / or goods and moving via a power system such as an engine. In some implementations, such a vehicle may include, but is not limited to, cars, trucks, buses, electric vehicles, motorcycles, RVs, trains, etc. As an example, such a vehicle may be one with certain assisted driving capabilities or autonomous driving capabilities; such vehicles are also referred to as intelligent driving vehicles. As an example, such a vehicle may also be a non-intelligent driving vehicle, i.e., an ordinary vehicle without assisted driving capabilities, and this is not limited thereto.

[0030] In some examples, the vehicle-side device 110 is a device deployed within a vehicle. For instance, the vehicle-side device 110 may include a vehicle center console, controller, display screen or touchscreen, operation buttons, etc., where the controller may include unit modules such as a communication unit and a control unit. As an example, the communication unit can be used for internal communication with the vehicle-side device 110, or for establishing a connection channel with external devices (such as mobile device 130), and receiving control commands or transferring other shared content via such a connection channel. As an example, the control unit can be used to control the operation of the vehicle based on control commands, or for controlling internal vehicle structural facilities (such as seats, air conditioning, lights, etc.) or software facilities (such as software applications deployed in the vehicle-side device 110). Such control commands may be triggered via in-vehicle buttons, touchscreens, etc., or received from mobile device 130 via a connection channel; this is not limited here.

[0031] In some examples, users can actively trigger a connection channel between mobile device 130 and vehicle-mounted device 110, or vice versa, to control the vehicle or in-vehicle facilities and to facilitate content transfer between the two devices. However, this type of actively triggered connection path is complex to operate, inefficient in establishing connections, and results in a poor user experience.

[0032] In example scenario 100 of this disclosure embodiment, the vehicle may also be equipped with at least one NFC tag 120 (e.g., a passive magnetic patch). Such an NFC tag 120 may be pre-configured with trigger data for connecting to the vehicle-mounted device 110. This trigger data may include, but is not limited to, information such as the device identifier of the vehicle-mounted device 110 and the connection methods allowed by the vehicle-mounted device 110. Through the NFC tag 120, users can quickly establish a connection between the mobile device 130 and the vehicle-mounted device 110.

[0033] As an example, the NFC tag 120 can be configured to be touched to send trigger data to the vehicle-mounted device 110. For instance, a user can quickly obtain trigger data from the vehicle-mounted device 110 by touching the NFC tag 120 with their mobile device 130 to identify the corresponding device identifier and candidate connection method, and then automatically initiate a connection request to establish a connection with the vehicle-mounted device 110, thereby enabling vehicle control or content transfer between the vehicle-mounted device 110 and the device. Therefore, this embodiment of the present disclosure can significantly reduce user operating costs and improve the connection efficiency between the mobile device 130 and the vehicle-mounted device 110, thereby improving vehicle control efficiency.

[0034] In some implementations, NFC tags 120 can be deployed at any touch-screen location in the vehicle's cabin space, so that users (such as drivers or passengers) can use mobile devices 130 to quickly trigger and establish a connection with the vehicle-side device 110 by touching the NFC tag 120, thereby improving vehicle control or content transfer efficiency and enhancing the convenience of user operation.

[0035] As an example, the mobile device 130 in this disclosure may be any type of mobile terminal, portable computer, multimedia tablet, personal communication system device, personal navigation device, personal digital assistant, audio / video player, digital camera / camcorder, positioning device, television receiver, radio broadcast receiver, e-book device, gaming device, or any combination thereof, including accessories and peripherals of such devices or any combination thereof, without limitation herein.

[0036] Figure 2 This is a flowchart illustrating an example process 200 of a vehicle control method according to some embodiments of the present disclosure. The vehicle control method is applied to vehicle-side equipment (such as...) Figure 1 The vehicle-mounted device 110 shown in the diagram indicates that such a vehicle has at least one NFC tag 120 deployed. (See also: [reference needed]) Figure 1 and Figure 2 As shown, process 200 may include the following steps: In step S210, the vehicle-mounted device 110 establishes a connection channel with the mobile device 130 in response to receiving a connection request from the mobile device 130. Such a connection request is generated based on trigger data stored in the NFC tag 120.

[0037] In some implementations, the NFC tag 120 can be written with data by the user or manufacturer to associate the NFC tag 120 with the corresponding vehicle and its vehicle-mounted device 110. For example, a user can write trigger data such as the device identifier of the vehicle-mounted device 110, the allowed connection method, and the communication path to at least one NFC tag 120, and then place such at least one NFC tag 120 in the vehicle cabin.

[0038] As an example, a passenger can use a mobile device 130 (such as a mobile phone) to touch an NFC tag 120 to obtain trigger data from the NFC tag 120 for establishing a connection with the vehicle-side device 110, generate a connection request based on such trigger data, and then send the connection request to the corresponding vehicle-side device 110, thereby quickly triggering a connection request with the vehicle-side device 110.

[0039] As an example, such triggering data may include, but is not limited to: the device identifier of the vehicle-side device 110, path information corresponding to at least one connection path, etc. For example, such at least one connection path is a connection path that is allowed (can be implemented) by the vehicle-side device 110, including but not limited to: Bluetooth, WiFi, wireless magnetic attraction, end-to-end connection paths based on the same operating system, etc.

[0040] After receiving a connection request, the vehicle-mounted device 110 can establish a connection channel with the mobile device 130 based on the data in the connection request. As an example, the connection path corresponding to such a connection channel can be associated with the first operating system of the vehicle-mounted device 110 and the second operating system of the mobile device 130. For example, such a connection path may include, but is not limited to: Bluetooth connection, wireless connection (such as in-vehicle hotspot or in-vehicle WiFi), end-to-end connection based on the same operating system, etc.

[0041] In some implementations, the vehicle-side device 110 can autonomously select an appropriate connection path based on the device identifier of the mobile device 130 carried in the connection request, or it can select the optimal connection path based on the priority of multiple connection paths to establish a connection channel between the vehicle-side device 110 and the mobile device 130.

[0042] In step S220, the vehicle-side device 110 sends at least one control item associated with the vehicle to the mobile device 130 via a connection channel.

[0043] As an example, the vehicle-mounted device 110 can communicate and interact with the mobile device 130 via the established connection channel. For instance, the vehicle-mounted device 110 can receive analytics (such as application data), control commands, etc., from the mobile device 130.

[0044] After establishing a connection channel between the vehicle-side device 110 and the mobile device 130, at least one control item can be automatically acquired. This control item is associated with at least one device and / or structural module deployed in the vehicle. As an example, such at least one device and / or structural module may include, but is not limited to: doors, windows, seats, air conditioning, lights, displays, media playback components, etc.

[0045] In some implementations, such at least one control item may include, but is not limited to: a first control item for facilities such as doors, windows, and seats; a second control item for air conditioning; a third control item for media playback; a fourth control item for coordinating with devices such as displays; and a fifth control item for vehicle start-stop and other operation controls.

[0046] In some examples, each control item can be presented on the display screen of the mobile device 130 in the form of any interactive component, such as an interactive card or a content pop-up. As an example, the mobile device 130 can present one control item within the same interactive card or content pop-up, or multiple control items via an information stream; this is not limited to this. As an example, multiple interactive cards or content pop-ups corresponding to multiple control items can also be presented on the display screen of the mobile device 130 via an information stream.

[0047] In some implementations, users can switch the control items currently displayed on the screen by swiping, and trigger the corresponding control items by any feasible interaction method such as tapping or long-pressing, so that the mobile device 130 can generate corresponding control commands and send them to the vehicle-side device 110 for execution.

[0048] In step S230, the vehicle-side device 110 responds to receiving a first control command corresponding to a target control item among at least one control item, and controls the vehicle based on the first control command.

[0049] As an example, in response to receiving a first control command from mobile device 130, vehicle-side device 110 can, based on the first control command, invoke the controller to control the corresponding facilities or drive devices. In some examples, such a first control command is associated with a target control item among at least one control item. Such a target control item is selected and triggered by the user through the interactive interface of mobile device 130. As an example, such a target control item can be used to adjust the status of vehicle facilities such as windows, seats, air conditioning, lights, and audio facilities, and can also be used to adjust the vehicle's driving status (e.g., stationary, moving, parked), speed, and driving direction.

[0050] It should be noted that the purpose of this solution is to improve the connection efficiency between vehicle-side equipment and mobile devices, thereby improving vehicle control efficiency and ease of control. For specific control command sending methods and corresponding execution processes, please refer to all feasible solutions in related technologies, which will not be elaborated here.

[0051] According to the vehicle control method provided in this disclosure, by deploying an NFC tag in the vehicle and storing trigger data for connecting to vehicle-side devices in the NFC tag, the NFC tag can trigger a mobile device to automatically connect to the vehicle-side devices, thereby realizing vehicle control or content transfer between the mobile device and the vehicle-side devices. Furthermore, by sending at least one control item associated with the vehicle to the mobile device, the installation of vehicle control-related application software on the mobile device can be effectively avoided, enabling the mobile device to quickly control the vehicle without installation or login, thus improving the convenience of vehicle control. Therefore, this solution can significantly reduce user operating costs, improve the connection efficiency between mobile devices and vehicle-side devices, and enhance user convenience.

[0052] The vehicle control method provided in this disclosure uses NFC tags as storage and interaction medium through near-field communication, which can quickly realize unauthorized temporary connections, allowing any passenger in the vehicle to interact with the vehicle-side device 110. This greatly reduces the need for interaction identity and eliminates the need for installation and login. The command flow between the mobile device and the vehicle-side device is completed through at least one control item, providing great convenience for vehicle control.

[0053] The vehicle control method of this disclosure can include not only the connection establishment process between the vehicle-side device 110 and the mobile device 130 based on the NFC tag 120, but also the data writing process of the NFC tag 120. In some implementations, such data writing can be completed by the user through other auxiliary devices, such as a dedicated data writing device; or it can be completed by the vehicle-side device 110.

[0054] In some examples, the vehicle-mounted device 110 can connect to the NFC tag 120 via any feasible wired or wireless connection method, and then write the trigger data of the vehicle-mounted device 110 into the NFC tag 120. For example, after confirming that a connection has been established with the NFC tag 120, the vehicle-mounted device 110 can write the corresponding trigger data into the NFC tag 120.

[0055] In some implementations of the embodiments of this disclosure, the vehicle control method further includes: the vehicle-side device 110 acquiring the vehicle's gear position information in response to detecting a first trigger event of the NFC tag 120; and writing trigger data into the NFC tag 120 in response to the gear position information meeting the writing conditions.

[0056] As an example, such a first trigger event indicates that the NFC tag 120 is connected to the data output terminal of the vehicle-side device 110. For example, the NFC tag 120 is placed near the wireless output port of the vehicle's center console (e.g., near the wireless charging port, the principle of which can be referred to as the wireless charging interface).

[0057] As an example, vehicle gear information can indicate the vehicle's current driving status. Such gear information could include at least the parking gear, driving gear, and starting gear.

[0058] In some examples, the data writing conditions for the NFC tag 120 can be related not only to the connection status between the NFC tag 120 and the vehicle-mounted device 110, but also to vehicle gear information. For example, data writing to the NFC tag 120 may only be permitted when the vehicle is not in motion.

[0059] In this way, the present embodiment can further determine whether the vehicle's gear information meets the writing conditions while ensuring that the NFC tag 120 and the vehicle-side device 110 are connected. This avoids writing data to the NFC tag 120 when the gear information is not suitable, which could affect the vehicle's driving status or control execution and thus affect driving safety. As a result, the accuracy of the written data can be guaranteed while ensuring driving safety, and data writing errors caused by vehicle control can be avoided.

[0060] Figure 3 A flowchart illustrating an example process 300 for writing data to an NFC tag according to some embodiments of this disclosure is shown. (Refer to...) Figure 3 As shown, the example process 300 for writing this data includes the following steps: In step 310, the vehicle-mounted device 110 obtains the vehicle's gear position information in response to the detection of the first trigger event of the NFC tag 120.

[0061] In step 320, the vehicle-mounted device 110 obtains the binding information of the NFC tag 120 in response to the gear position information meeting the writing conditions.

[0062] In some implementations, after determining that the NFC tag 120 is connected to the vehicle-mounted device 110 and that the vehicle's gear information meets the writing conditions (e.g., the vehicle is in a stopped gear), the vehicle-mounted device 110 can further verify the association between the NFC tag 120 and the vehicle-mounted device 110. For example, such an association could refer to whether the NFC tag 120 is bound to the vehicle-mounted device 110, that is, verifying whether the NFC tag 120 stores trigger data from the vehicle-mounted device 110.

[0063] In step 330, the vehicle-side device 110 issues a binding prompt in response to the binding information indicating that the NFC tag 120 is not bound to the vehicle.

[0064] As an example, if it is determined that the NFC tag 120 does not store trigger data from the vehicle-mounted device 110, the vehicle-mounted device 110 can determine that the NFC tag 120 is not bound to the vehicle-mounted device 110. In this case, the vehicle-mounted device 110 can issue a binding prompt to ask the user to confirm whether they need to bind the NFC tag 120 to the vehicle-mounted device 110. For example, the vehicle-mounted device 110 can issue a corresponding audio-visual prompt, or it can present the binding prompt as a message pop-up on the display screen.

[0065] In step 340, the vehicle-mounted device 110 writes trigger data into the NFC tag 120 in response to receiving the first confirmation information corresponding to the binding prompt.

[0066] As an example, if the user closes the binding prompt, or if the user triggers a confirmation operation to unbind via the binding prompt, the vehicle-mounted device 110 may not write data to the NFC tag 120. If the user triggers a binding operation via the binding prompt, the vehicle-mounted device 110 may trigger the writing of trigger data to the NFC tag 120 based on the first confirmation information corresponding to the binding operation.

[0067] In this way, the present invention can effectively ensure the validity of the trigger data writing process through multiple confirmations such as connection status, vehicle gear information, and binding information between NFC tag 120 and vehicle-side device 11, thereby ensuring the accuracy of the trigger data in NFC tag 120.

[0068] In some implementations of the embodiments of this disclosure, writing trigger data to the NFC tag further includes: the vehicle-side device 110 issuing an update prompt in response to the binding information indicating that the NFC tag has been bound to the vehicle; and writing trigger data to the NFC tag in response to receiving the second confirmation information corresponding to the update prompt.

[0069] As an example, while maintaining the connection between the NFC tag 120 and the vehicle-mounted device 110, if the binding information confirms that the NFC tag 120 is bound to the vehicle's vehicle-mounted device 110, the vehicle-mounted device 110 can issue an update prompt, allowing the user to choose whether to update the binding relationship, i.e., whether to update the written trigger data. For example, such an update prompt can be issued via an audible and visual alarm, or it can be presented as a message pop-up on the display screen.

[0070] In some examples, if a user triggers a cancellation or stop operation via an update prompt, the vehicle-mounted device 110 can keep the data in the NFC tag 120 unchanged, without verification or update. If a user triggers a confirmation or update operation via an update prompt, the vehicle-mounted device 110 can write the latest trigger data into the NFC tag 120.

[0071] In some implementations, the vehicle-mounted device 110 may write new trigger data to the NFC tag 120 in ways including but not limited to: erasing the old data first and then writing the new data; retaining the old data and writing the new data; or overwriting the old data with the new data, i.e. erasing the old data by writing the new data.

[0072] Therefore, once it is confirmed that the NFC tag 120 has been bound to the vehicle-side device 110, an update prompt can be used to determine whether the original trigger data should be updated, so as to ensure the accuracy of the trigger data in the NFC tag 120. This ensures that the data in the NFC tag 120 can be updated as the configuration of the vehicle-side device 110 is updated, thus guaranteeing the timeliness of the trigger data stored in the NFC tag 120.

[0073] In some implementations of the embodiments of this disclosure, the vehicle control method further includes: the vehicle-side device 110 clears the trigger data in the NFC tag 120 in response to receiving the third confirmation information corresponding to the update prompt.

[0074] As an example, if a user triggers a clear or release operation via an update prompt, the vehicle-mounted device 110 will no longer write new trigger data to the NFC tag 120 and will clear its original trigger data to release the binding relationship between the NFC tag 120 and the vehicle-mounted device 110.

[0075] Therefore, upon receiving the update notification, the vehicle-mounted device 110 can clear the data in the NFC tag 120 to remove the binding relationship between the NFC tag 120 and the original vehicle, thereby improving the circulation and usability of the NFC tag 120.

[0076] In some implementations of the embodiments of this disclosure, before the trigger data writing is completed, the vehicle control method further includes: the vehicle-side device 110 determining the event state of the first trigger event in response to detecting an interrupt event; and continuing to write the trigger data in response to the event state indicating that the first trigger event is ongoing and valid.

[0077] As an example, such interruption events may include, but are not limited to, changes in the vehicle's driving state. For example, the vehicle switches from a stopped state to a started state or a driving state.

[0078] In this way, the present embodiment can maintain the continuity of the data writing process in the event of an interruption while the NFC tag 120 and the data output port of the vehicle-side device 110 remain connected during the process of triggering data writing to the NFC tag 120, thus ensuring the continuity of trigger data writing and guaranteeing the accuracy and validity of the written trigger data.

[0079] In some implementations of the embodiments of this disclosure, the vehicle control method further includes: the vehicle-side device 110 stops writing trigger data in response to an event status indication that the first trigger event is interrupted or timed out.

[0080] As an example, the first triggering event interruption or timeout may include, but is not limited to: the vehicle-side device 110 losing connection with the NFC tag 120, the NFC tag 120 shifting in position on the center console, the connection duration between the NFC tag 120 and the vehicle-side device 110 reaching a first duration threshold, or the data writing duration reaching a second duration threshold.

[0081] In this way, when the vehicle-mounted device 110 determines that the connection with the NFC tag 120 is abnormal or has timed out, it can promptly stop writing trigger data, effectively avoiding data loss and waste of writing resources.

[0082] In this embodiment of the disclosure, if the NFC tag 120 contains trigger data for the vehicle-side device 110, the NFC tag 120 can be placed at any triggerable location in the vehicle, such as the side of the rear seat, the door corresponding to the passenger seat, or the ceiling inside the vehicle, so that passengers can quickly touch it with their mobile devices to trigger the connection with the vehicle-side device 110.

[0083] In some implementations of the embodiments of this disclosure, establishing a connection channel with the mobile device 130 includes: the vehicle-side device 110 establishing a connection channel with the mobile device in response to a connection request that meets the connection conditions.

[0084] In some implementations, after receiving a connection request, the vehicle-side device 110 can verify the connection request, or verify at least one of the vehicle's connection status, connection permissions, control permissions, etc., to determine whether the received connection request meets the connection conditions.

[0085] As an example, the vehicle-side device 110 can parse the device identifier, connection path, and other data carried in the connection request and match them with the device identifier and allowed connection path of the vehicle-side device 110. In some examples, if the device identifier carried in the connection request matches the device identifier of the vehicle-side device 110, and the allowed connection path of the vehicle-side device 110 includes the connection path carried in the connection request, the vehicle-side device 110 can determine that the connection request meets the connection conditions; otherwise, if either of these does not match, the vehicle-side device 110 can determine that the connection request does not meet the connection conditions.

[0086] If the information carried in the connection request meets the connection conditions, the vehicle-mounted device 110 can establish a connection channel with the mobile device 130 based on the corresponding connection path.

[0087] In some optional implementations of the embodiments of this disclosure, establishing a connection channel with the mobile device 130 includes: in response to a connection request satisfying the connection conditions, the vehicle-side device 110 establishes a connection channel with the mobile device 130 based on the connection path corresponding to the connection request. Such a connection path can be determined based on the configuration information of the mobile device 130.

[0088] In some implementations, such a connection path can be obtained directly from the connection request; or it can be obtained by first parsing the configuration information of the mobile device 130 from the connection request, and then matching it from multiple candidate connection paths based on the configuration information.

[0089] As an example, after receiving a connection request from the mobile device 130, the vehicle-side device 110 can parse the connection request to obtain the configuration information of the mobile device 130, and then determine the connection path that is allowed by both the mobile device 130 and the vehicle-side device 110 based on the configuration information, which is the connection path corresponding to the connection request.

[0090] As an example, such configuration information may include, but is not limited to, at least one of the following: the device identifier of the mobile device 130, the system identifier corresponding to the operating system of the mobile device 130, and the connection paths allowed or prohibited by the device identifier and / or system identifier.

[0091] In this way, the present invention can determine the corresponding connection path based on the configuration information of the mobile device 130 carried in the connection request, and then establish a connection channel between the vehicle-side device 110 and the mobile device 130, which can effectively ensure the success rate and effectiveness of the connection channel establishment.

[0092] In some examples, the connection path determined based on configuration information may include one or more paths.

[0093] In some optional implementations of the embodiments of this disclosure, the connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, establishing a connection channel with the mobile device based on the connection path corresponding to the connection request includes: the vehicle-side device 110 responding to the failure of the first path connection to obtain the connection request corresponding to the second path; and establishing a connection channel based on the second path.

[0094] In some examples, the vehicle-side device 110 can support multiple connection paths to enable connections to be initiated by mobile devices with different operating systems, hardware types, and software configurations.

[0095] As an example, for the multiple connection paths that the vehicle-side device 110 can support, at least one priority can be configured. For instance, the vehicle-side device 110 can support connections with mobile devices operating systems of at least two different operating systems, and it supports a total of three connection paths (e.g., connection paths a, b, and c). The first operating system only supports one connection path, a; the second operating system can support connection paths b and c, and the path priority for the second operating system in the vehicle-side device 110 can be configured such that connection path b takes precedence over connection path c.

[0096] As an example, corresponding to the mobile device 130 configured with the second operating system, after receiving its connection request, the vehicle-side device 110 first attempts to establish a connection channel with the mobile device 130 using connection path b. If this fails, or fails after a preset number of retries, it then attempts to establish a connection channel using connection path c. Alternatively, after receiving a connection request from the mobile device 130 based on connection path c, it then establishes a connection channel with the mobile device 130 based on connection path c. For example, the second operating system can be the same series or the same operating system as the vehicle-side device 110, connection path b can be an end-to-end connection path based on the same or the same series of operating systems, and connection path c can be a vehicle hotspot or a local area network communication path.

[0097] In this way, the present invention can, when supporting multiple connection paths at the same time, attempt to establish connection channels sequentially based on the priority of the connection paths until the connection channel is successfully established, thereby ensuring the orderliness and uniqueness of the connection channel establishment process, avoiding duplicate establishment, and also avoiding the inability to establish a connection due to the failure of a connection path, thereby ensuring the success rate of establishing the connection channel between the vehicle-side device 110 and the mobile device 130.

[0098] In some optional implementations of the embodiments of this disclosure, the vehicle control method may further include: the vehicle-side device 110 sending control permissions to the mobile device 130 via a connection channel, wherein the control permissions are associated with the connection channel.

[0099] In some examples, such control permissions can refer to control permissions over a vehicle or vehicle-related facilities. Such control permissions are associated with the currently established connection channel.

[0100] As an example, the vehicle-mounted device 110 may send control permissions to the mobile device 130 in ways including but not limited to: sending session tokens (such as temporary tokens), sending permission passwords and verification codes, etc.

[0101] In this way, the present embodiment can authorize the mobile device 130 by sending control permissions through the connection channel, so as to ensure the validity of subsequent received control commands and thus ensure the reliability of vehicle control.

[0102] In some optional implementations of the embodiments of this disclosure, the vehicle control method may further include: the vehicle-side device 110 revoking control authority in response to the connection channel being closed.

[0103] In some examples, to avoid accidental reconnections from the same mobile device and resulting misoperations, the session token sent by the vehicle-mounted device 110 to the mobile device after each connection is established can be configured as a one-time token, meaning it is only valid during the continuous connection period of the connection channel; once the connection channel is closed, the session token automatically expires, and the vehicle-mounted device 110 revokes the control permission. For example, the vehicle-mounted device 110 can destroy (or clear) the session token, or mark the post-session token as invalid.

[0104] As an example, the connection channel may be closed in at least one of the following situations: the mobile device exits the corresponding operation interface, the mobile device exceeds the connection distance, the user triggers the disconnection on the mobile device, the user triggers the disconnection on the vehicle device 110, the vehicle is powered off, etc.

[0105] In some implementations of the embodiments of this disclosure, controlling the vehicle based on a first control command includes: vehicle-side device 110 responding to a target device associated with the vehicle by a target control item, adjusting the drive information of the target device based on the first control command.

[0106] As an example, in response to receiving a first control command, the vehicle-side device 110 can parse the first control command to determine the control object corresponding to the first control command. In response to determining that the target control object corresponding to the first control command is a target device of the vehicle (e.g., door, window, air conditioning, seat, lights, etc.), the vehicle-side device 110 can adjust the corresponding target's driving information based on the control parameters corresponding to the first control command. For example, such a first control command may include, but is not limited to: opening the door, closing / locking the door, lowering / raising the window, turning the air conditioning on / off, adjusting the air conditioning temperature or operating mode, adjusting the seat mode (e.g., sleep, massage, etc.) / seat backrest tilt angle, adjusting the lighting mode (e.g., high brightness, reading, rest, etc.), etc.

[0107] In this way, any user in the vehicle can quickly establish a connection channel between the mobile device 130 and the vehicle-end device 110 through the vehicle control method provided in this embodiment of the disclosure, and send corresponding control commands from the mobile device 130 to the vehicle-end device 110 through at least one control item associated with the vehicle. Without installation and login, the target device of the vehicle can be adjusted quickly and efficiently to meet the diverse needs of different users.

[0108] In some implementations, the vehicle-mounted device 110 can also combine the positioning information of the mobile device 130 inside the vehicle or the location information specified by the control command to adjust the vehicle's hardware facilities and improve the accuracy and efficiency of the execution of the control command.

[0109] In some implementations, the control commands sent by the user through the mobile device 130 to the vehicle-side device 110 can also instruct the control of the vehicle's display screen or other electronic modules. For example, the control commands can instruct the vehicle-side device 110 and the mobile device 130 to coordinate control, share screens, etc. Therefore, the embodiments of this disclosure enable passengers to control the vehicle's display screen or playback facilities from any position inside the vehicle, enriching vehicle control methods, improving vehicle control efficiency, enriching the interaction methods of vehicle facilities, and enhancing the controllability of vehicle facilities.

[0110] In some examples, the control commands sent by the user to the vehicle-mounted device 110 via the mobile device 130 can also be used to control the application software equipped on the vehicle-mounted device 110.

[0111] In some implementations of the embodiments of this disclosure, the vehicle control method may further include: the vehicle-side device 110, in response to receiving a second control command, obtaining a software list of the vehicle, the second control command being associated with a first application software of the mobile device 130; in response to the software list not including a second application software identical to the first application software, receiving instruction data corresponding to the second control command; and calling a third application software from the software list to output instruction data, the third application software being determined based on the instruction data.

[0112] When a user wishes to control the software of the vehicle-mounted device 110 via control commands, such as displaying or playing application software data from the mobile device 130 on the vehicle-mounted device 110, this can be achieved not only through collaborative control or screen sharing between the vehicle-mounted device 110 and the mobile device 130, but also through software data sharing. For example, the mobile device 130 can generate a second control command and / or corresponding command data based on the application data corresponding to the first application software to be shared, and then send such a second control command and / or command data to the vehicle-mounted device 110 for execution.

[0113] In some examples, after receiving instruction data associated with an application software, the vehicle-mounted device 110 can search for a second application software that is identical to the first application software from the configured software list. If no second application software is found, it will invoke a third application software that matches the instruction data to execute. For example, a user shares music data from a first music software on a mobile device 130, hoping to play it on the vehicle-mounted device 110. The vehicle-mounted device 110 can first check if the same music software is configured. If not, it will retrieve the music data from the mobile device 130, parse it, and then invoke the music software configured in the vehicle-mounted device 110 to play the music data. For example, such music data can be packaged by the mobile device 130 in the form of a data packet or data card and presented in the interactive interface. It can then be sent to the vehicle-mounted device 110 via a user-triggered operation (e.g., sharing), thereby realizing content flow between the mobile device 130 and the vehicle-mounted device 110.

[0114] In some implementations of the embodiments of this disclosure, controlling the vehicle based on the second control command received via the connection channel further includes: the vehicle-side device 110 responding to the software list including the second application software by calling the second application software to execute the second control command.

[0115] In this implementation, if the vehicle-side device 110 finds a second application software (deployed on the vehicle-side device 110) that is the same as the first application software (deployed on the mobile device 130) in the software list, the vehicle-side device 110 can directly call the second application software to execute based on the control instructions received from the mobile device 130, so as to realize the collaborative control between the mobile device 130 and the vehicle-side device 110 and the content flow between the two.

[0116] According to the vehicle control method of this disclosure, corresponding to the control command of the application software, the vehicle-side device 110 can execute different execution strategies based on whether the same application software has been configured: if the same application software has been configured, the application software can be directly called to achieve collaborative control; if the same application software has not been configured, the instruction data corresponding to the control command can be received, and the same type of application software can be called to execute, thereby adaptively selecting the execution mode and effectively ensuring the execution rate and execution effect of the control command.

[0117] In some implementations, the vehicle-mounted device 110 of the same vehicle can simultaneously establish connections and interact with multiple mobile devices 130 via the same or more NFC tags 120. For example, multiple passengers in the same vehicle can simultaneously use different mobile devices 130 to connect to the vehicle-mounted device 110 and control at least one device in the vehicle.

[0118] As an example, for equipment or structural modules in different locations within the vehicle cabin, the vehicle-side equipment 110 can execute them synchronously or sequentially according to their respective control commands.

[0119] In some examples, for the same device or structural module within the cabin space, if multiple control commands are received from different mobile devices 130, the vehicle-mounted device 110 can automatically select to execute them sequentially or only execute the last control command based on the time interval between their reception. For example, if the time interval between the reception of two different control commands for the same structural module is greater than a first time threshold, the vehicle-mounted device 110 can execute these two control commands sequentially; if the time interval between their reception is less than a second time threshold, the vehicle-mounted device 110 can execute only the last received control command and ignore the previous one. As an example, the second time threshold is less than or equal to the first time threshold, for example, the second time threshold is 0.2 ms.

[0120] Figure 4 This is a flowchart illustrating an example process 400 of a vehicle control method according to some embodiments of the present disclosure. This vehicle control method is applied to mobile devices (such as…) Figure 1 The mobile device 130 shown is referenced. Figure 4 As shown, example process 400 may include the following steps: In step 410, in response to detecting a second trigger event with NFC tag 120, mobile device 130 establishes a connection channel with vehicle-side device 110 of the vehicle, and NFC tag is deployed in the vehicle.

[0121] In some implementations, the mobile device 130 can obtain association data from the NFC tag 120 to establish a connection channel with the vehicle-mounted device 110, and send a corresponding connection request to establish a connection channel with the vehicle-mounted device 110. As an example, such association data may include, but is not limited to, at least one of the following: at least one candidate connection path, connection triggering method, etc.

[0122] In scenarios where an NFC tag 120 is deployed inside a vehicle, a user can trigger a second trigger event by touching the NFC tag 120 with a mobile device 130 (e.g., via a "tap-to-pay" contact method). After touching the NFC tag 120, the mobile device 130 can retrieve the data stored in the NFC tag 120 via near-field communication. For example, any user in the vehicle cabin can use their mobile phone to touch the nearest NFC tag 120 to quickly establish a temporary connection between the mobile phone and the vehicle-side device 110, thereby reducing restrictions on the connection to the vehicle-side device and improving connection efficiency.

[0123] In some implementations, the mobile device 130 can obtain trigger data from the NFC tag 120 in response to the detection of a second trigger event; and then establish a connection channel with the vehicle-mounted device 110 based on such trigger data.

[0124] As an example, such trigger data includes at least the device identifier of the vehicle-mounted device 110 deployed in the vehicle, and at least one supported connection path.

[0125] As an example, after obtaining the trigger data, the mobile device 130 can parse the trigger data to obtain at least one of the following information about the vehicle-side device 110: device identifier, operating system, and at least one supported connection path, etc. Then, based on the parsed information, the mobile device 130 can generate a corresponding connection request and send it to the vehicle-side device 110 to trigger the establishment of a connection channel between the mobile device 130 and the vehicle-side device 110.

[0126] In step 420, the mobile device 130 presents at least one control item associated with the vehicle, such control item being received via a connection channel.

[0127] After a connection channel is successfully established, the mobile device 130 can receive and present at least one control item associated with the vehicle from the vehicle-side device 110 to facilitate user interaction. In some examples, such at least one control item is associated with at least one device or structural module of the vehicle. As an example, such at least one device and / or structural module may include, but is not limited to: doors, windows, seats, air conditioning, lights, displays, media playback components, etc.

[0128] In some implementations, such at least one control item may include, but is not limited to: a first control item for facilities such as doors, windows, and seats; a second control item for air conditioning; a third control item for media playback; a fourth control item for coordinating with devices such as displays; and a fifth control item for vehicle start-stop and other operation controls.

[0129] In some implementations of the embodiments of this disclosure, presenting at least one control item includes: the mobile device 130 receiving at least one control item from the vehicle-mounted device 110 via a connection channel; and presenting the at least one control item in the interactive interface of the mobile device 130.

[0130] In some examples, each control item can be presented on the display screen or interactive interface of the mobile device 130 in the form of any interactive component such as an interactive card or a content pop-up. As an example, the mobile device 130 can present one control item in the same interactive card or content pop-up, or it can present multiple control items in the form of an information flow; this is not limited here.

[0131] As an example, multiple interactive cards or content pop-ups corresponding to multiple control items can also be presented on the display screen of the mobile device 130 in the form of an information flow.

[0132] In some implementations, such controls can be presented in the user interface of the mobile device 130 in any feasible form, such as a "light app" or a floating window. In some examples, taking a floating window as an example, in response to the closing operation of the floating window, the mobile device 130 can disconnect the connection channel with the vehicle-side device 110, or it can maintain the connection channel and present it in the form of an interactive control or interactive entry point, so that the user can trigger it to reopen the floating window to continue interacting with the vehicle-side device 110.

[0133] In step 430, in response to a triggering operation on a target control item among at least one control item, the mobile device 130 sends a first control command corresponding to the target control item to the vehicle-side device 110 to control the vehicle.

[0134] After confirming that the connection channel has been successfully established, the mobile device 130 can receive at least one control item from the vehicle-side device 110. Then, based on the user's trigger operation on any of the control items, it generates a corresponding control command and sends the control command to the vehicle-side device 110, which executes the command to control the vehicle.

[0135] In some implementations, users can switch at least one control item currently displayed on the screen by swiping (e.g., swiping left or right or up or down), and trigger the target control item to be operated by any feasible interaction method such as tapping or long pressing, so that the mobile device 130 generates the corresponding first control command and sends it to the vehicle-side device 110 for execution.

[0136] According to the vehicle control method provided in this embodiment, the mobile device 130 can use the NFC tag 120 as a medium to obtain trigger data that triggers connection with the vehicle-side device 110, thereby automatically establishing a connection channel with the vehicle-side device 110. Through this connection channel, it can receive at least one control item associated with the vehicle and send corresponding control commands. It can achieve connection with the vehicle-side device and control of the vehicle without installation or login, greatly reducing the user's operating costs and improving connection efficiency and vehicle control efficiency. Furthermore, it reduces the restrictions on connection permissions, allowing any passenger in the vehicle to use this control method to temporarily control the vehicle, improving the convenience of passenger operation and vehicle control.

[0137] In some optional implementations of the embodiments of this disclosure, establishing a connection channel with the vehicle-side device 110 based on trigger data includes: the mobile device 130 determining a connection path based on the configuration information of the mobile device 130; sending a connection request to the vehicle-side device 110 based on the trigger data and the connection path; and receiving response information corresponding to the connection request to establish a connection channel.

[0138] As an example, the configuration information of mobile device 130 may include, but is not limited to, the following: the operating system type of mobile device 130, system identifier, and the connection types supported by mobile device 130.

[0139] In some examples, the mobile device 130 can determine at least one reference connection path supported by the mobile device 130 based on its own configuration information; then, based on the at least one reference connection path and the trigger data obtained from the NFC tag 120, it generates a corresponding connection request and sends it to the vehicle-side device 110.

[0140] As an example, the mobile device 130 can also match at least one reference path with at least one candidate path supported by the vehicle-side device 110 in the trigger data, determine at least one connection path that the mobile device 130 and the vehicle-side device 110 can establish a connection based on the matching result, generate a corresponding connection request, and then send it to the vehicle-side device 110. The vehicle-side device 110 performs connection feasibility verification based on the connection request, and establishes a connection path between the mobile device 130 and the vehicle-side device 110 if the connection conditions are met.

[0141] The vehicle-mounted device 110 can feed back the connection result (success or failure) to the mobile device 130. Based on the received response information, the mobile device 130 determines whether the connection channel has been successfully established.

[0142] In some optional implementations of the embodiments of this disclosure, determining the connection path based on the configuration information of the mobile device 130 includes: the mobile device 130 parsing the trigger data to determine the vehicle identifier; determining the association relationship between the vehicle identifier and the configuration information of the mobile device 130; and determining the connection path based on the association relationship.

[0143] As an example, if the vehicle identification and configuration information of mobile device 130 indicate that vehicle-side device 110 and mobile device 130 have the same or similar operating system, or indicate that the user has identification information associated with vehicle-side device 110 (such as an account or identity identifier of the same operating system), mobile device 130 can further verify the association between mobile device 130 or the user and the vehicle. For example, such an association can indicate whether mobile device 130 or the user is bound to the vehicle.

[0144] In some examples, if it is determined that the mobile device 130 or the user is associated with the vehicle, the mobile device 130 may determine that it can establish a connection with the vehicle-side device 110 based on an end-to-end shortcut path, or it may establish a connection based on other wireless connection paths (such as Bluetooth, WiFi, or LAN); if it is determined that neither the mobile device 130 nor the user is associated with the vehicle, the mobile device 130 may determine that it cannot establish a connection with the vehicle-side device 110 based on an end-to-end shortcut path, but it may establish a connection based on other wireless connection paths.

[0145] In some optional implementations of the embodiments of this disclosure, determining the association relationship with the vehicle based on the vehicle identifier and the configuration information of the mobile device includes: the mobile device 130 sending a relationship determination request to the cloud device based on the vehicle identifier and configuration information; and receiving response information from the cloud device to determine whether there is a corresponding association relationship with the vehicle.

[0146] As an example, such cloud devices can be standalone physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Cloud devices can include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in cloud environments, and so on.

[0147] A communication connection can be established between the mobile device 130 and the cloud device. This communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth connections, mobile network connections, Universal Serial Bus connections, Wi-Fi connections, etc., and the embodiments disclosed herein are not limited in this respect.

[0148] In some examples, the connection path determined based on configuration information may include one or more paths.

[0149] According to some optional implementations of embodiments of this disclosure, the connection path may include at least a first path and a second path, with the first path having a higher priority than the second path. In some examples, sending a connection request to the vehicle-side device based on trigger data and the connection path includes: the mobile device 130 sending a first connection request to the vehicle-side device based on the trigger data and the first path; resending the first connection request in response to a connection failure along the first path; and sending a second connection request to the vehicle-side device based on the trigger data and the second path in response to the number of times the first connection request has been sent reaching a threshold.

[0150] As an example, both the mobile device 130 and the vehicle-mounted device 110 can support multiple connection paths, enabling them to initiate connections and successfully establish connection channels even if they have different operating systems, hardware types, and software configurations.

[0151] As an example, for the multiple connection paths that the vehicle-side device 110 can support, at least one priority can be configured. For instance, the vehicle-side device 110 can support connections with mobile devices operating systems of at least two different operating systems, and it supports a total of three connection paths (e.g., connection paths a, b, and c). The first operating system only supports one connection path, a; the second operating system can support connection paths b and c, and the path priority for the second operating system in the vehicle-side device 110 can be configured such that connection path b takes precedence over connection path c.

[0152] In some examples, corresponding to a mobile device 130 configured with a second operating system, after receiving a connection request, the vehicle-mounted device 110 first attempts to establish a connection channel with the mobile device 130 using connection path b. If this fails, or fails after a preset number of retries, it then attempts to establish a connection channel using connection path c. Alternatively, after receiving a connection request from the mobile device 130 based on connection path c, it then establishes a connection channel with the mobile device 130 based on connection path c. For example, the second operating system can be the same series or the same operating system as the vehicle-mounted device 110, connection path b can be an end-to-end connection path based on the same or the same series of operating systems, and connection path c can be a vehicle hotspot or a local area network communication path.

[0153] In some examples, for a mobile device 130 configured with a second operating system, when it is determined that the supported and achievable connection paths include connection paths b and c, the mobile device 130 can, according to priority, first generate a first connection request corresponding to connection path b and send it to the vehicle-side device 110, which then executes the corresponding connection establishment process. If the connection establishment fails, the vehicle-side device 110 can retry a preset number of times. If all preset number of retries fail, the vehicle-side device 110 can report the failure result back to the mobile device 130. After receiving the feedback information, the mobile device 130 downgrades to connection path c, generates a corresponding second connection request, sends it to the vehicle-side device 110, and then the vehicle-side device 110 continues to attempt to establish a connection channel based on the second connection request.

[0154] In this way, the present invention can, when supporting multiple connection paths at the same time, attempt to establish connection channels sequentially based on the priority of the connection paths until the connection channel is successfully established, thereby ensuring the orderliness and uniqueness of the connection channel establishment process, avoiding duplicate establishment, and also avoiding the inability to establish a connection due to the failure of a connection path, thereby ensuring the success rate of establishing the connection channel between the vehicle-side device 110 and the mobile device 130.

[0155] In some optional implementations of the embodiments of this disclosure, the vehicle control method may further include: the mobile device 130 generating sharing data corresponding to the target content in response to a sharing operation of the target content in the mobile device 130; and sending a second control command to the vehicle-side device 110 via a connection channel, the second control command including the sharing data.

[0156] As an example, such target content may include, but is not limited to, at least one of the following: text content, audio content, video content, route data, geographic location information, etc.

[0157] In some examples, such target content can be a standalone data file or associated with at least one application software pre-installed on the mobile device 130, without limitation.

[0158] In some implementations, the mobile device 130 can receive user analysis operations on target content via an interactive interface or operation buttons, and generate corresponding sharing data. As an example, such sharing data may include, but is not limited to, at least one of the following data formats: data cards, data addresses (e.g., URL links), compressed files, multimedia content (e.g., audio, video, images, text), data files, etc.

[0159] After generating the sharing data, the mobile device 130 can send the sharing data or the corresponding second control command (such as a sharing command) to the vehicle-side device 110 through the connection channel.

[0160] In some examples, if such shared data is not associated with a specific application in the mobile device 130, the vehicle-mounted device 110 can automatically select the appropriate format (or application) to play or present the data based on its data type.

[0161] In some examples, if such shared data is associated with a fixed application in the mobile device 130, the vehicle-side device 110 can verify whether the fixed application is installed according to the second control command. If it is installed, the application can be launched directly to play the shared data corresponding to the second control command. If the fixed application is not installed, the vehicle-side device 110 can search for similar applications or applications that can effectively present the shared data according to the application type of the fixed application and the data type of the shared data, and call the application to present the corresponding shared data.

[0162] In this way, the embodiments of this disclosure can automatically select the optimal data presentation method according to the data format of the shared data and the corresponding application software, so as to ensure the presentation effect of the shared data.

[0163] In some optional implementations of the embodiments of this disclosure, the vehicle control method may further include: the mobile device 130 generating a third control command associated with the fourth application software in response to detecting a second trigger event while presenting the fourth application software; and sending the third control command to the vehicle-side device via a connection channel.

[0164] According to the vehicle control method provided in this embodiment, the mobile device 130 can not only establish a connection channel with the vehicle-side device 110 before determining the corresponding control command or data flow, but also determine the data flow before establishing a connection channel with the vehicle-side device 110.

[0165] In some implementations, users can determine the data content that can be transferred to the vehicle-side device 110 through their fourth application software while interacting with the mobile device 130. As an example, such a fourth application software may include, but is not limited to, media playback software (such as audio playback software, video playback software, etc.), map / navigation application software, social or entertainment software that can interact with the intelligent agent, etc.

[0166] Taking map application software as an example, after a user finds destination location information or route information in the map application software on mobile device 130, while the map application software is running, the user can touch mobile device 130 with the NFC tag 120 in the cabin to quickly establish a connection with vehicle-mounted device 110. After the connection channel is successfully established, mobile device 130 can automatically send the third control command corresponding to the destination location information or route information to vehicle-mounted device 110; or it can send the third control command corresponding to the data to be shared and / or the data to be analyzed to vehicle-mounted device 110 based on the user's trigger operation.

[0167] As an example, such third control commands may include, but are not limited to: sharing commands (e.g., sharing location information), playback commands (e.g., playing media content), application commands (e.g., using route navigation), etc.

[0168] According to the vehicle control method provided in this disclosure, by deploying an NFC tag in the vehicle, a mobile device can be automatically connected to the vehicle-side device, thereby enabling vehicle control or content transfer between the vehicle-side device and the vehicle-side device. Furthermore, by having the vehicle-side device send at least one control item associated with the vehicle to the mobile device, the installation of vehicle control-related applications on the mobile device can be effectively avoided, allowing the mobile device to quickly control the vehicle without installation or login, thus improving the convenience of vehicle control. Therefore, this solution can significantly reduce user operating costs, improve the connection efficiency between the mobile device and the vehicle-side device, and enhance user convenience.

[0169] Figure 5 This is a schematic block diagram illustrating the structure of a vehicle control device 500 according to some embodiments of the present disclosure. As an example, the device 500 can be applied to vehicle-side equipment (e.g., vehicle-mounted devices). Figure 1 The vehicle-mounted device 110 shown is used, and such vehicles are equipped with NFC tags.

[0170] Reference Figure 5 The device 500 includes a first connection establishment module 510, a content transmission module 520, and a vehicle control module 530. The first connection establishment module 510 is configured to establish a connection channel with a mobile device in response to receiving a connection request from the mobile device, the connection request being generated based on trigger data stored in an NFC tag; the content transmission module 520 is configured to send at least one control item associated with the vehicle to the mobile device via the connection channel; and the vehicle control module 530 is configured to control the vehicle based on a first control command corresponding to a target control item among the at least one control item, in response to receiving such a command.

[0171] In some optional implementations of the embodiments of this disclosure, the first connection module 510 is configured to: in response to the connection request meeting the connection conditions, establish a connection channel based on the connection path corresponding to the connection request, wherein the connection path is determined based on the configuration information of the mobile device.

[0172] In some optional implementations of the embodiments of this disclosure, the connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, the first connection establishment module 510 is configured to: in response to the failure of the first path connection, obtain the connection request corresponding to the second path; and establish a connection channel based on the second path.

[0173] In some optional implementations of the embodiments of this disclosure, the apparatus 500 may further include a permission sending module, which is configured to send control permissions to the mobile device via a connection channel, wherein the control permissions are associated with the connection channel.

[0174] In some optional implementations of the embodiments of this disclosure, the vehicle control module 530 is configured to: adjust the driving information of the target device based on a first control command in response to a target device associated with the vehicle for the target control item.

[0175] In some optional implementations of the embodiments of this disclosure, the device 500 may further include a list acquisition module, a data receiving module, and a software invocation module. The list acquisition module is configured to acquire a software list of the vehicle in response to receiving a second control command, wherein the second control command is associated with a first application software of the mobile device. The data receiving module is configured to receive instruction data corresponding to the second control command in response to the software list not including a second application software identical to the first application software. The software invocation module is configured to invoke a third application software in the software list to output instruction data, wherein the third application software is determined based on the instruction data and the software type of the third application software is the same as that of the first application software.

[0176] In some optional implementations of the embodiments of this disclosure, the device 500 further includes a gear position determination module and a data writing module, wherein the gear position determination module is configured to acquire the gear position information of the vehicle in response to detecting a first trigger event of the NFC tag; and the data writing module is configured to write trigger data into the NFC tag in response to the gear position information meeting the writing conditions.

[0177] In some optional implementations of the embodiments of this disclosure, the data writing module is configured to: obtain the binding information of the NFC tag; issue a binding prompt in response to the binding information indicating that the NFC tag is not bound to the vehicle; and write trigger data into the NFC tag in response to receiving the first confirmation information corresponding to the binding prompt.

[0178] In some optional implementations of the embodiments of this disclosure, the data writing module may also be configured to: issue an update prompt in response to the binding information indicating that the NFC tag has been bound to the vehicle; and write trigger data into the NFC tag in response to receiving the second confirmation information corresponding to the update prompt.

[0179] In some optional implementations of the embodiments of this disclosure, the apparatus 500 further includes an event determination module and a task continuation module, wherein the event determination module is configured to determine the event state of the first triggering event in response to detecting an interruption event before the triggering data writing is completed; and the task continuation module is configured to continue writing the triggering data in response to the event state indicating that the first triggering event is ongoing and valid.

[0180] Figure 6 This is a schematic block diagram illustrating the structure of a vehicle control device 600 according to some embodiments of the present disclosure. As an example, this device can be applied to mobile devices (e.g., mobile devices). Figure 1 The mobile device 130 shown is referenced. Figure 6 The device 600 includes a second connection establishment module 610, a content presentation module 620, and a first transmission module 630. The second connection establishment module 610 is configured to establish a connection channel with a vehicle-mounted device in response to detecting a second trigger event related to an NFC tag deployed in the vehicle. The content presentation module 620 is configured to present at least one control item associated with the vehicle, the at least one control item being received via the connection channel. The first transmission module 630 is configured to send a first control command corresponding to the target control item to the vehicle-mounted device in response to a trigger operation on a target control item among the at least one control item, to control the vehicle.

[0181] In some optional implementations of the embodiments of this disclosure, the second connection module 610 is configured to: obtain trigger data from the NFC tag; and establish a connection channel based on the trigger data.

[0182] In some optional implementations of the embodiments of this disclosure, establishing a connection channel with the vehicle-side device based on trigger data includes: determining a connection path based on the configuration information of the mobile device; sending a connection request to the vehicle-side device based on the trigger data and the connection path; and receiving response information corresponding to the connection request to establish a connection channel.

[0183] In some optional implementations of the embodiments of this disclosure, determining the connection path based on the configuration information of the mobile device includes: parsing trigger data to determine the vehicle identifier; determining the association relationship between the vehicle identifier and the mobile device configuration information; and determining the connection path based on the association relationship.

[0184] In some optional implementations of the embodiments of this disclosure, determining the association relationship with a vehicle based on the vehicle identifier and the configuration information of the mobile device includes: sending a relationship determination request to a cloud device based on the vehicle identifier and the configuration information; and receiving response information from the cloud device to determine the association relationship with the vehicle.

[0185] In some optional implementations of the embodiments of this disclosure, the connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, sending a connection request to the vehicle-side device based on trigger data and the connection path includes: sending a first connection request to the vehicle-side device based on trigger data and the first path; resending the first connection request in response to a connection failure of the first path; and sending a second connection request to the vehicle-side device based on the trigger data and the second path in response to the number of times the first connection request has been sent reaching a threshold.

[0186] In some optional implementations of the embodiments of this disclosure, the content presentation module 620 is configured to: receive at least one control item via a connection channel; and present at least one control item in the interactive interface of a mobile device.

[0187] In some optional implementations of the embodiments of this disclosure, the device 600 further includes an information sharing module and a second sending module, wherein the information sharing module is configured to generate sharing data corresponding to the target content in response to a sharing operation of the target content in the mobile device; and the second sending module is configured to send a second control command to the vehicle-end device via a connection channel, the second control command including the sharing data.

[0188] In some optional implementations of the embodiments of this disclosure, the apparatus 600 may further include an instruction generation module and a third sending module, wherein the instruction generation module is configured to generate a third control instruction associated with the fourth application software in response to detecting a second trigger event in a state where the fourth application software is presented; and the third sending module is configured to send the third control instruction to the vehicle-end device via a connection channel.

[0189] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0190] Figure 7 This is a block diagram illustrating a vehicle 700 according to an exemplary embodiment. For example, vehicle 700 can be a hybrid vehicle, a non-hybrid vehicle, an electric vehicle, a fuel cell vehicle, or other types of vehicle. Vehicle 700 can be an autonomous vehicle, a semi-autonomous vehicle, or a non-autonomous vehicle.

[0191] Reference Figure 7The vehicle 700 may include various subsystems, such as an infotainment system 710, a perception system 720, a decision control system 730, a drive system 740, and a computing platform 750. The vehicle 700 may also include more or fewer subsystems, and each subsystem may include multiple components. Furthermore, each subsystem and each component of the vehicle 700 can be interconnected via wired or wireless means.

[0192] In some embodiments, the infotainment system 710 may include a communication system, an entertainment system, and a navigation system, etc.

[0193] The perception system 720 may include several sensors for sensing information about the environment surrounding the vehicle 700. For example, the perception system 720 may include a global positioning system (which may be GPS, BeiDou, or other positioning systems), an inertial measurement unit (IMU), lidar, millimeter-wave radar, ultrasonic radar, and a camera device.

[0194] The decision control system 730 may include a computing system, a vehicle controller, a steering system, a throttle, and a braking system.

[0195] The drive system 740 may include components that provide powered motion to the vehicle 700. In one embodiment, the drive system 740 may include an engine, an energy source, a transmission system, and wheels. The engine may be one or a combination of internal combustion engines, electric motors, and compressed air engines. The engine is capable of converting energy provided by the energy source into mechanical energy.

[0196] Some or all of the functions of vehicle 700 are controlled by computing platform 750. Computing platform 750 may include at least one processor 751 and memory 752, and processor 751 may execute instructions 753 stored in memory 752.

[0197] Processor 751 can be any conventional processor, such as a commercially available CPU. Processors may also include graphics processing units (GPUs), field-programmable gate arrays (FPGAs), systems-on-chips (SoCs), application-specific integrated circuits (ASICs), or combinations thereof.

[0198] The memory 752 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0199] In addition to instruction 753, memory 752 can also store data, such as road maps, route information, vehicle position, direction, speed, and other data. The data stored in memory 752 can be used by computing platform 750.

[0200] In this embodiment of the disclosure, the processor 751 may execute instructions 753 to complete all or part of the steps of the vehicle control method described above.

[0201] This disclosure also provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the steps of the vehicle control method provided in this disclosure.

[0202] Furthermore, the term “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous compared to other aspects or designs. Rather, the use of the term “exemplary” is intended to present the concept in a concrete manner. As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or clear from the context, “X applies A or B” is intended to mean any of the natural inclusive arrangements. That is, “X applies A or B” satisfies any of the foregoing instances if X applies A; X applies B; or both X applies A and B. Additionally, unless otherwise specified or clear from the context to refer to the singular form, the articles “a” and “an” as used in this application and the appended claims are generally understood to mean “one or more.”

[0203] Similarly, although this disclosure has been shown and described with respect to one or more implementations, equivalent variations and modifications will occur to those skilled in the art upon reading and understanding this specification and the accompanying drawings. This disclosure includes all such modifications and variations and is limited only by the scope of the claims. In particular, with respect to the various functions performed by the components described above (e.g., elements, resources, etc.), unless otherwise indicated, the terminology used to describe such components is intended to correspond to any component (functionally equivalent) that performs the specific function of the described component, even if structurally not equivalent to the disclosed structure. Furthermore, although specific features of this disclosure may have been disclosed with respect to only one of several implementations, such features may be combined with one or more other features of other implementations, as may be desired and advantageous to any given or particular application. Moreover, with regard to the terms “comprising,” “owning,” “having,” “having,” or variations thereof as used in the detailed description or claims, such terms are intended to be inclusive in a manner similar to the term “including.”

[0204] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0205] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A vehicle control method, characterized in that, A vehicle-mounted device applied to a vehicle, the vehicle being equipped with an NFC tag, the method comprising: In response to receiving a connection request from a mobile device, a connection channel is established with the mobile device, the connection request being generated based on trigger data stored in the NFC tag; Send at least one control item associated with the vehicle to the mobile device via the connection channel; and In response to receiving a first control instruction corresponding to a target control item among the at least one control item, the vehicle is controlled based on the first control instruction.

2. The method according to claim 1, characterized in that, The establishment of the connection channel with the mobile device includes: In response to the connection request satisfying the connection conditions, a connection channel is established with the connection based on the connection path corresponding to the connection request, wherein the connection path is determined based on the configuration information of the mobile device.

3. The method according to claim 2, characterized in that, The connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, establishing a connection channel with the mobile device based on the connection path corresponding to the connection request includes: In response to the failure of the first path connection, obtain the connection request corresponding to the second path; and Based on the second path, the connection channel is established.

4. The method according to claim 1, characterized in that, The method further includes: Control permissions are sent to the mobile device via the connection channel, and the control permissions are associated with the connection channel.

5. The method according to claim 1, characterized in that, The control of the vehicle based on the first control command includes: In response to the target control item associated with the target device of the vehicle, the drive information of the target device is adjusted based on the first control command.

6. The method according to claim 1, characterized in that, The method further includes: In response to receiving a second control command, the system obtains a software list of the vehicle, wherein the second control command is associated with a first application software of the mobile device; In response to the software list not including a second application software identical to the first application software, instruction data corresponding to the second control instruction is received; and The third application software in the software list is invoked to output the instruction data. The third application software is determined based on the instruction data, and the software type of the third application software is the same as that of the first application software.

7. The method according to claim 1, characterized in that, The method further includes: In response to a first trigger event detected by the NFC tag, the vehicle's gear position information is obtained; and In response to the gear position information meeting the writing conditions, the trigger data is written to the NFC tag.

8. The method according to claim 7, characterized in that, The step of writing the trigger data into the NFC tag includes: Obtain the binding information of the NFC tag; In response to the binding information indicating that the NFC tag is not bound to the vehicle, a binding prompt is issued; and In response to receiving the first confirmation information corresponding to the binding prompt, the trigger data is written into the NFC tag.

9. The method according to claim 8, characterized in that, The step of writing the trigger data into the NFC tag further includes: In response to the binding information indicating that the NFC tag has been bound to the vehicle, an update prompt is issued; and In response to receiving the second confirmation information corresponding to the update prompt, the trigger data is written into the NFC tag.

10. The method according to claim 7, characterized in that, Before the trigger data writing is completed, the method further includes: In response to detecting an interrupt event, determine the event state of the first triggering event; and In response to the event status indicating that the first triggering event is ongoing and valid, the triggering data continues to be written.

11. A vehicle control method, characterized in that, Applied to mobile devices, the method includes: In response to the detection of a second trigger event with the NFC tag, a connection channel is established with the vehicle's on-board equipment, the NFC tag being deployed in the vehicle; Presenting at least one control item associated with the vehicle, the at least one control item being received via the connection channel; and In response to a triggering operation of a target control item among the at least one control item, a first control command corresponding to the target control item is sent to the vehicle-mounted device to control the vehicle.

12. The method according to claim 11, characterized in that, The establishment of a connection channel with the vehicle's on-board equipment includes: Obtain trigger data from the NFC tag; and Based on the trigger data, the connection channel is established.

13. The method according to claim 12, characterized in that, The step of establishing a connection channel with the vehicle's on-board equipment based on the trigger data includes: Based on the configuration information of the mobile device, determine the connection path; Based on the trigger data and the connection path, a connection request is sent to the vehicle-mounted device; and Receive the response information corresponding to the connection request to establish the connection channel.

14. The method according to claim 13, characterized in that, Determining the connection path based on the configuration information of the mobile device includes: The trigger data is parsed to determine the vehicle identifier of the vehicle; Based on the vehicle identifier and the configuration information of the mobile device, determine the association relationship between the device and the vehicle; and Based on the aforementioned association, the connection path is determined.

15. The method according to claim 14, characterized in that, Determining the association relationship with the vehicle based on the vehicle identifier and the configuration information of the mobile device includes: Based on the vehicle identifier and the configuration information, a relationship determination request is sent to the cloud device; and Receive response information from the cloud device to determine the association with the vehicle.

16. The method according to claim 13, characterized in that, The connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, sending a connection request to the vehicle-side device based on the trigger data and the connection path includes: Based on the trigger data and the first path, a first connection request is sent to the vehicle-side device; In response to the failure of the first path connection, the first connection request is resent; and In response to the first connection request being sent a threshold number of times, a second connection request is sent to the vehicle-mounted device based on the trigger data and the second path.

17. The method according to claim 12, characterized in that, The presentation of at least one control associated with the vehicle includes: Receive the at least one control item via the connection channel; and The at least one control item is presented in the interactive interface of the mobile device.

18. The method according to claim 11, characterized in that, The method further includes: In response to a sharing operation on target content in the mobile device, share data corresponding to the target content is generated; and A second control command is sent to the vehicle-side device via the connection channel, the second control command including the shared data.

19. The method according to claim 11, characterized in that, The method further includes: In response to detecting the second triggering event while the fourth application software is in a presented state, a third control command associated with the fourth application software is generated; and The third control command is sent to the vehicle-mounted device via the connection channel.

20. A vehicle control device, characterized in that, A vehicle-mounted device for use in a vehicle, the vehicle being equipped with an NFC tag, the device comprising: The first connection module is configured to establish a connection channel with the mobile device in response to receiving a connection request from the mobile device, the connection request being generated based on trigger data stored in the NFC tag; A content delivery module is configured to send at least one control item associated with the vehicle to the mobile device via the connection channel; and The vehicle control module is configured to control the vehicle based on the first control instruction received in response to receiving a first control instruction corresponding to a target control item among the at least one control item.

21. The apparatus according to claim 20, characterized in that, The first connection module is configured as follows: In response to the connection request satisfying the connection conditions, a connection channel is established with the connection based on the connection path corresponding to the connection request, wherein the connection path is determined based on the configuration information of the mobile device.

22. The apparatus according to claim 21, characterized in that, The connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, the first connection establishment module is configured as follows: In response to the failure of the first path connection, obtain the connection request corresponding to the second path; and Based on the second path, the connection channel is established.

23. The apparatus according to claim 20, characterized in that, The device further includes: The list acquisition module is configured to acquire a list of software of the vehicle in response to receiving a second control command, wherein the second control command is associated with a first application software of the mobile device; The data receiving module is configured to receive instruction data corresponding to the second control instruction in response to the software list not including a second application software identical to the first application software; and The software invocation module is configured to invoke a third application software from the software list to output the instruction data. The third application software is determined based on the instruction data, and the software type of the third application software is the same as that of the first application software.

24. A vehicle control device, characterized in that, Applied to a mobile device, the device includes: The second connection module is configured to establish a connection channel with the vehicle's on-board equipment in response to the detection of a second trigger event with the NFC tag deployed in the vehicle; A content presentation module is configured to present at least one control item associated with the vehicle, the at least one control item being received via the connection channel; and The first sending module is configured to send a first control command corresponding to the target control item to the vehicle-end device in response to a triggering operation of the target control item among the at least one control item, so as to control the vehicle.

25. The apparatus according to claim 24, characterized in that, The second connection module is configured as follows: Obtain trigger data from the NFC tag; Based on the trigger data, the connection channel is established.

26. The apparatus according to claim 25, characterized in that, The process of establishing the connection channel based on the trigger data includes: Based on the configuration information of the mobile device, determine the connection path; Based on the trigger data and the connection path, a connection request is sent to the vehicle-mounted device; and Receive the response information corresponding to the connection request to establish the connection channel.

27. The apparatus according to claim 26, characterized in that, The connection path includes a first path and a second path, with the first path having a higher priority than the second path; wherein, sending a connection request to the vehicle-side device based on the trigger data and the connection path includes: Based on the trigger data and the first path, a first connection request is sent to the vehicle-side device; In response to the failure of the first path connection, the first connection request is resent; In response to the first connection request being sent a threshold number of times, a second connection request is sent to the vehicle-mounted device based on the trigger data and the second path.

28. The apparatus according to claim 24, characterized in that, The device further includes: The content analysis module is configured to generate sharing data corresponding to the target content in response to a sharing operation on the mobile device; and The second sending module is configured to send a second control command to the vehicle-side device via the connection channel, the second control command including the shared data.

29. A vehicle, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured as follows: Implement the method according to any one of claims 1 to 10.

30. A non-transitory computer-readable storage medium, wherein when instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to perform the method of any one of claims 1-10 or 11-19.

Images