Vehicle control method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application disclose a vehicle control method and device, electronic equipment and a storage medium. The method comprises: a mobile terminal obtaining configuration data of a vehicle control device to be configured, assembling a configuration instruction according to the configuration data, and sending the configuration instruction to the vehicle control device to be configured through a first Bluetooth connection between the mobile terminal and the vehicle control device; the vehicle control device parses a mapping relationship between an operation type and a vehicle control function identifier issued, and updates a vehicle control mapping relationship stored in the vehicle control device; the vehicle control device responds to an input operation of a user, determines a target vehicle control function identifier according to the operation type and the vehicle control mapping relationship, and encapsulates a vehicle control instruction, and sends the vehicle control instruction to a DKECU; the DKECU performs identity verification and permission verification on the received vehicle control instruction according to a bound device list, controls the vehicle to execute the vehicle control instruction after verification, and fuses the vehicle control device and the vehicle control system through dynamic configuration and safe binding of the vehicle control device, thereby realizing vehicle control.

Description

Technical Field

[0001] The present invention relates to the field of vehicle control technology, and in particular to a vehicle control method, device, electronic device and storage medium. Background Technology

[0002] Portable mobile devices such as smartphones are rapidly becoming ubiquitous as digital car keys. The need for vehicle control functions, such as controlling windows, sunroofs, and trunks, is constantly increasing with the rapid development of vehicle intelligence. One existing technology uses smartphones to control the vehicle, but users must hold and operate the phone to complete the operation, which is cumbersome and affects driving safety. IoT button devices are inexpensive and convenient as vehicle control input devices; however, these devices have limited resources and cannot be integrated with vehicle control systems, failing to meet the needs for safe, convenient, and flexible vehicle control. Summary of the Invention

[0003] This invention provides a vehicle control method, device, electronic device, and storage medium. By using a mobile terminal and a digital key channel, the vehicle control device can be bound and configured, thereby integrating the vehicle control device with the vehicle control system and achieving low-cost, safe, and convenient vehicle control.

[0004] In a first aspect, embodiments of the present invention provide a method for applying to a vehicle control system, the vehicle control system comprising: a mobile terminal, a vehicle digital key control unit (DKECU), and at least one vehicle control device, wherein the mobile terminal is equipped with a digital key application and is capable of establishing a digital key secure channel with the DKECU, and the vehicle control device is a vehicle control command input device; the method comprises:

[0005] The mobile terminal responds to the user's configuration operation to obtain the configuration data of the vehicle control device to be configured, assembles a configuration instruction based on the configuration data, and sends the configuration instruction to the vehicle control device to be configured via a first Bluetooth connection; the configuration data includes: a mapping relationship between operation type and vehicle control function identifier, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device;

[0006] The vehicle control device receives configuration instructions from itself via the first Bluetooth connection and parses them to obtain the mapping relationship between the issued operation type and the vehicle control function identifier. It then updates the vehicle control mapping relationship stored in its storage based on the received mapping relationship between the operation type and the vehicle control function identifier.

[0007] The vehicle control device responds to the user's input operation to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier according to the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command according to the target vehicle control function identifier, and sends the vehicle control command to the DKECU through a second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU.

[0008] The DKECU verifies the identity and permissions of the vehicle control commands received via the second Bluetooth connection based on the list of bound devices. If the identity and permissions verification is successful, the DKECU controls the vehicle to execute the vehicle control commands. The vehicle control device has pre-registered its identity through a binding process with the DKECU. The binding process includes the mobile terminal sending the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel.

[0009] As one embodiment, the mobile terminal, in response to a user's configuration operation, obtains configuration data of the vehicle control device to be configured, assembles a configuration command based on the configuration data, and sends the configuration command to the vehicle control device to be configured via a first Bluetooth connection, including:

[0010] The mobile terminal determines the unified routing identifier URI and target link corresponding to the configuration data based on the functional semantic type of the configuration data and the preset correspondence; the preset correspondence is the correspondence between the URI, the functional semantic type of the communication data in the vehicle control system, and the communication link in the vehicle control system.

[0011] The service payload field of the TLV structure is assembled based on the configuration data. The configuration data is then encapsulated into the configuration instruction according to a preset unified format based on the determined URI and the assembled payload field. The configuration instruction is then sent through the first Bluetooth connection, which is a Bluetooth connection to the target link based on the configuration data.

[0012] As an example, the configuration instruction includes at least one set of key-value pairs, which are operation type and vehicle control function identifier key-value pairs. The key-value pairs of the configuration instruction are assembled in the payload of the configuration instruction according to the TLV format.

[0013] As an example, the vehicle control device has operation buttons, and the operation types include at least two of single click, double click, and long press; the vehicle control functions include one or more of the following: door lock control, tailgate control, window control, sunroof control, sliding door control, and sunshade control; the mapping relationship between operation types and vehicle control function identifiers includes mapping relationships between multiple operation types and the same vehicle control function, and mapping relationships where no mapping is configured for operation types; when the vehicle control function identifier corresponding to the target operation type is in an unconfigured state, the vehicle control device ignores the current input operation.

[0014] As one embodiment, the mobile terminal, in response to a user's configuration operation, obtains configuration data of the vehicle control device to be configured, including:

[0015] The mobile terminal determines the vehicle control function identifier corresponding to each operation type in response to the user's operation on the bottom pop-up window or the selectable vehicle control list in the human-computer interaction interface.

[0016] As one embodiment, the method further includes:

[0017] The DKECU determines whether the vehicle control device sending the vehicle control command is already in the bound device list to authenticate the vehicle control device; the DKECU determines whether the vehicle control operation corresponding to the vehicle control command is allowed to be executed in the current vehicle state based on the current vehicle status information to verify the permission of the vehicle control command; if both the authentication and permission verification are successful, the DKECU controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

[0018] Secondly, embodiments of the present invention provide a vehicle control method applied to a mobile terminal in a vehicle control system. The vehicle control system further includes: a digital key control unit (DKECU) for the vehicle and at least one vehicle control device. The mobile terminal is equipped with a digital key app and is capable of establishing a digital key secure channel with the DKECU. The vehicle control device is a vehicle control command input device. The method includes:

[0019] In response to a user's configuration operation, the system acquires configuration data for the vehicle control device to be configured, assembles a configuration command based on the configuration data, and sends the configuration command to the vehicle control device via a first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers. The first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device receives the configuration command from the mobile terminal via the first Bluetooth connection, parses it to obtain the mapping relationship between the operation types and vehicle control function identifiers sent by the mobile terminal, and updates the vehicle control device according to the received mapping relationship. The system stores vehicle control mapping relationships. The vehicle control device responds to user input to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection. The second Bluetooth connection is the connection between the vehicle control device and the DKECU. The DKECU performs identity verification and authorization verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful.

[0020] The vehicle control device has pre-registered its identity through a binding process with the DKECU. The binding process includes the mobile terminal sending the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel.

[0021] Thirdly, embodiments of the present invention provide a vehicle control method applied to at least one vehicle control device in a vehicle control system, wherein the vehicle control device is a vehicle control command input device; the vehicle control system further includes: a mobile terminal and a vehicle digital key control unit (DKECU), wherein the mobile terminal is equipped with a digital key APP and is capable of establishing a digital key security channel with the DKECU; the method includes:

[0022] The vehicle control device receives configuration instructions from the mobile terminal via a first Bluetooth connection and parses them to obtain a mapping relationship between the issued operation type and the vehicle control function identifier. Based on the received mapping relationship, the device updates the vehicle control mapping relationship stored in its storage. The mobile terminal, in response to a user's configuration operation, obtains configuration data for the vehicle control device to be configured, assembles a configuration instruction based on the configuration data, and sends the configuration instruction to the vehicle control device to be configured via the first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device.

[0023] The vehicle control device responds to the user's input operation to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU; wherein, the DKECU performs identity verification and authorization verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful; wherein, the mobile terminal sends the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

[0024] Fourthly, embodiments of the present invention provide a vehicle control device, a mobile terminal configured in a vehicle control system, the vehicle control system further including: a digital key control unit (DKECU) and at least one vehicle control device, the mobile terminal having a digital key APP installed and capable of establishing a digital key security channel with the DKECU, and the vehicle control device being a vehicle control command input device; the vehicle control device includes:

[0025] A configuration generation module is used to obtain configuration data of the vehicle control device to be configured in response to the user's configuration operation, assemble configuration instructions based on the configuration data, and send the configuration instructions to the vehicle control device to be configured via a first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers. The first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device receives the configuration instructions of its own device via the first Bluetooth connection, parses the mapping relationship between the operation types and vehicle control function identifiers sent by the mobile terminal, and updates the configuration based on the received mapping relationship. The vehicle control device stores vehicle control mapping relationships; the vehicle control device responds to user input operations to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU; the DKECU performs identity verification and permission verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and permission verification are successful;

[0026] The binding module is used to send the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

[0027] Fifthly, embodiments of the present invention provide a vehicle control device, comprising at least one vehicle control device configured in a vehicle control system, wherein the vehicle control device is a vehicle control command input device; the vehicle control system further includes: a mobile terminal and a vehicle digital key control unit (DKECU), wherein the mobile terminal is equipped with a digital key APP and is capable of establishing a digital key security channel with the DKECU; the vehicle control device includes:

[0028] A vehicle control configuration module is used to receive configuration instructions for the vehicle control device issued by the mobile terminal via a first Bluetooth connection, parse them to obtain a mapping relationship between the issued operation type and the vehicle control function identifier, and update the vehicle control mapping relationship stored in the vehicle control device according to the received mapping relationship between the operation type and the vehicle control function identifier; wherein the mobile terminal obtains configuration data of the vehicle control device to be configured in response to the user's configuration operation, assembles a configuration instruction according to the configuration data, and sends the configuration instruction to the vehicle control device to be configured via the first Bluetooth connection; the configuration data includes: a mapping relationship between the operation type and the vehicle control function identifier, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device;

[0029] The vehicle control generation module is used to determine the corresponding target operation type in response to user input, determine the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulate the vehicle control command based on the target vehicle control function identifier, and send the vehicle control command to the DKECU via a second Bluetooth connection; the second Bluetooth connection is a connection between the vehicle control device and the DKECU; wherein, the DKECU performs identity verification and authorization verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful; wherein, the mobile terminal sends the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

[0030] In a sixth aspect, embodiments of the present invention provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle control method as described above.

[0031] In a seventh aspect, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle control method as described above.

[0032] In this embodiment, the mobile terminal responds to the user's configuration operation by obtaining the configuration data of the vehicle control device to be configured, assembles a configuration instruction based on the configuration data, and sends the configuration instruction to the vehicle control device to be configured via a first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers. The first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device receives the configuration instruction of its own vehicle control device through the first Bluetooth connection and parses it to obtain the mapping relationship between the issued operation types and vehicle control function identifiers. Based on the received mapping relationship between operation types and vehicle control function identifiers, the vehicle control mapping relationship stored by the vehicle control device is updated, thereby realizing the vehicle control configuration of the vehicle control device through the mobile terminal.

[0033] The vehicle control device responds to user input to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection. The second Bluetooth connection serves as the connection between the vehicle control device and the DKECU. The DKECU verifies the identity and permissions of the vehicle control command received via the second Bluetooth connection according to the list of bound devices. If the identity and permissions verification is successful, the DKECU controls the vehicle to execute the vehicle control command. The mobile terminal sends the vehicle control device's identification information obtained via the first Bluetooth connection to the DKECU through the digital key security channel, allowing the DKECU to bind the vehicle control device. Thus, the vehicle control device is bound to the DKECU via the digital key security channel through the mobile terminal, ensuring the security of the vehicle control device binding without the need for a pre-set whitelist. Furthermore, the vehicle control device directly connects to the DKECU to control the vehicle, eliminating the need for the mobile terminal to be online. Therefore, this application provides a low-cost, easy-to-configure, and safe vehicle control solution, which is beneficial to meeting users' vehicle control needs. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is a schematic diagram of the vehicle control system provided in an embodiment of the present invention;

[0036] Figure 2 A flowchart illustrating the vehicle control method provided in an embodiment of the present invention;

[0037] Figure 3 This is a schematic diagram of the binding process in the vehicle control system provided in an embodiment of the present invention;

[0038] Figure 4 This is a flowchart illustrating the data transmission method in a vehicle control system provided in an embodiment of the present invention.

[0039] Figure 5 This is a schematic diagram of the URI semantic function mapping relationship provided in an embodiment of the present invention;

[0040] Figure 6 This is a flowchart illustrating the vehicle control method on the mobile terminal side provided in an embodiment of the present invention.

[0041] Figure 7 This is a flowchart illustrating the vehicle control method on the vehicle control device side provided in an embodiment of the present invention;

[0042] Figure 8 This is a schematic diagram of the vehicle control device provided in an embodiment of the present invention;

[0043] Figure 9 This is a schematic diagram of the vehicle control device provided in an embodiment of the present invention;

[0044] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0045] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0046] This embodiment provides a vehicle control method, device, electronic device, and storage medium for integrating vehicle control equipment with a vehicle control system. This enables low-cost vehicle control equipment to be easily configured and safely integrated into the vehicle control system, meeting users' needs for high security and convenient vehicle control.

[0047] The vehicle control method, device, electronic device, and storage medium provided in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0048] First, the vehicle control system and vehicle control method disclosed herein will be explained.

[0049] Figure 1 This is a schematic diagram of the vehicle control system provided in an embodiment of the present invention, such as... Figure 1As shown, the vehicle control system includes: a mobile terminal 102, a digital key control unit (DKECU) 104, and at least one vehicle control device 106. The mobile terminal 102 is equipped with a digital key application and can establish a digital key security channel with the DKECU 104. The mobile terminal 102 can be a portable smart terminal such as a smartphone or wearable device. The vehicle control device 106 is a vehicle control command input device. The DKECU 104 is responsible for digital key management, identity authentication, and execution of vehicle control commands. The mobile terminal 102, DKECU 104, and vehicle control device 106 can communicate based on Bluetooth technology. It is understood that the vehicle control device 106 can be an independent IoT control device with a Bluetooth communication module. The vehicle control device 106 includes, but is not limited to, button input devices and touch input devices. Users can input various vehicle control commands as needed through one or more vehicle control devices 106. The mobile terminal has a vehicle control app installed. Link-A between the vehicle control app and the vehicle control device is the configuration channel, Link-B between the vehicle control app and the DKECU is the management channel, and Link-C between the DKECU and the vehicle control device is the execution channel. These three independent Bluetooth links achieve a closed-loop information flow through the vehicle control app: the device completes the discovery and binding process via Link-A and Link-B; configuration is sent via Link-A; vehicle control data is transmitted directly via Link-C; and status is transmitted back via Link-B.

[0050] Figure 2 A flowchart illustrating a vehicle control method provided in an embodiment of the present invention. Figure 2 As shown, the method includes steps 201 to 204.

[0051] Step 201: The mobile terminal responds to the user's configuration operation by obtaining the configuration data of the vehicle control device to be configured, assembles a configuration command based on the configuration data, and sends the configuration command to the vehicle control device to be configured via the first Bluetooth connection. The configuration data includes: the mapping relationship between operation type and vehicle control function identifier, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device.

[0052] As an example and not a limitation, the vehicle control device may be a button device with a Bluetooth communication module. The vehicle control device may include at least one physical button, which may support single-click (one-time press), double-click (quick double press), and long-press operation types. It is understood that the operation type of the vehicle control device may also be a touch input device, and the operation types of a touch input device may include clicking, swiping, etc. The input device of the vehicle control device may also be a knob, and the operation types corresponding to a knob may include clockwise rotation, counterclockwise rotation, or rotation to different positions. This application does not impose excessive limitations on the vehicle control device. In this embodiment, the vehicle control device may have operation buttons, and the operation types include at least two of single-click, double-click, and long-press; the vehicle control functions include one or more of the following: door lock control, tailgate control, window control, sunroof control, sliding door control, and sunshade control; the mapping relationship between operation types and vehicle control function identifiers includes mapping relationships between multiple operation types and the same vehicle control function, and operation types without configured mapping relationships.

[0053] The mobile terminal's response to the user's configuration operation to obtain configuration data for the vehicle control device to be configured may include: the mobile terminal determining the vehicle control function identifier corresponding to each operation type based on the user's operation on the bottom pop-up window or the optional vehicle control list in the human-machine interface. Specifically, the mobile terminal displays the currently mapped vehicle control function name and function icon for each operation type (single click, double click, long press, etc.) of the vehicle control device in a list format in the human-machine interface. During the initial configuration, the mapping relationship of the vehicle control device can be preset to unconfigured for all operation types, and unconfigured operation types are marked as "unconfigured". When the user selects to modify the vehicle control function mapped to a certain operation type, a list of optional vehicle control functions is displayed in the form of a bottom pop-up window or list page, highlighting the currently selected item, allowing the user to select a single function or select "unconfigured" to clear the mapping. The system tracks whether the user has modified the function mapping, controls the activation / grayout state of the "Save Configuration" button, and undoes all local changes when exiting without saving the modifications. Configuration data is generated when the user saves the modifications and exits.

[0054] The mobile terminal assembles all changes to the vehicle control function mapping relationship of all operation types into a single TLV (Tag-Length-Value) format configuration instruction. Each change to the vehicle control function mapping relationship of each operation type corresponds to a set of Tag-Length-Value, where Tag is the operation type identifier and Value is the corresponding vehicle control function identifier.

[0055] The mobile terminal sends configuration commands to the vehicle control device to be configured via the first Bluetooth connection. It should be noted that the user can configure one or more vehicle control devices at the same time, generating configuration commands for each device and sending them to the corresponding devices.

[0056] Step 202: The vehicle control device receives the configuration command of this vehicle control device through the first Bluetooth connection and parses it to obtain the mapping relationship between the issued operation type and the vehicle control function identifier. Based on the received mapping relationship between the operation type and the vehicle control function identifier, the vehicle control device updates the vehicle control mapping relationship stored in this vehicle control device.

[0057] The vehicle control device receives configuration commands from the mobile terminal via the first Bluetooth connection, parses the TLV key-value pairs one by one, verifies the legality of the Tag (operation type) and Value (function identifier), and writes the legal mapping relationship into the vehicle control mapping table in the internal non-volatile storage.

[0058] In steps 201 and 202: The mobile terminal App displays the current vehicle control function mapping status of the vehicle control device, including the currently mapped vehicle control function for each operation type of the buttons (single click, double click, long press, etc.). The user selects the operation type vehicle control function mapping to be modified, and a vehicle control function selector pops up, with a list containing available vehicle control function items (door lock control, tailgate control, window control, sunroof control, sliding door control, sunshade control, etc.) and a "Not Configured" option. After the user selects a new vehicle control function, they return to the configuration page. The App encapsulates the mapping modifications of multiple operation types into a single configuration command. The configuration command contains one or more button operation type tags (e.g., 0x01=single click, 0x02=double click, 0x03=long press) and corresponding function identifier values ​​(e.g., 0x063E=door lock control, 0x0623=tailgate control) TLV key-value pairs. The mobile terminal sends the configuration command to the vehicle control device via the Link-A BLEGATT data channel. After receiving the data, the vehicle control device parses each TLV key-value pair, updates the internally stored vehicle control function mapping table, and returns a success or failure response upon completion.

[0059] Step 203: The vehicle control device responds to the user's input operation to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via the second Bluetooth connection. The second Bluetooth connection is the connection between the vehicle control device and the DKECU.

[0060] The vehicle control equipment detects user actions on physical buttons and identifies the operation type (single click, double click, long press, etc.). Specifically, the vehicle control equipment can perform hardware or software debouncing on the button press signal (debouncing window 30-50ms), and determine the operation type by the press duration and press interval: short press (less than the corresponding threshold) is identified as a single click, two quick short presses are identified as a double click, and long press exceeding the corresponding threshold is identified as a long press.

[0061] The vehicle control device searches for the corresponding vehicle control function identifier in the vehicle control mapping table based on the detected operation type. It then retrieves the corresponding vehicle control function identifier (Value) from the table based on the identified operation type (Tag). This Value is then assembled with the action identifier (open / close) to form a vehicle control command frame. The vehicle control command frame contains a TLV key-value pair of the vehicle control function identifier and the action identifier. The vehicle control command is then sent to the DKECU via a second Bluetooth connection, without going through a mobile terminal.

[0062] Step 204: The DKECU verifies the identity and permissions of the vehicle control commands received via the second Bluetooth connection based on the list of bound devices. If the identity and permissions verification is successful, the DKECU controls the vehicle to execute the vehicle control commands. The vehicle control devices have pre-registered their identities through a binding process with the DKECU. This binding process involves the mobile terminal sending the identification information of the vehicle control devices obtained via the first Bluetooth connection to the DKECU through the digital key security channel, allowing the DKECU to bind the vehicle control devices.

[0063] The DKECU verifies the identity of the vehicle control device sending the control command by checking if it is already on the list of bound devices. It then verifies the permission of the control operation corresponding to the command based on the current vehicle status information. If both identity verification and permission verification are successful, the DKECU controls the vehicle to execute the control operation corresponding to the command. Specifically, the DKECU confirms that the sender is a bound device (identity verification) and that the requested control function is allowed in the current vehicle status (permission verification). After successful verification, the command is converted into a CAN bus command and sent to the body controller for execution. The DKECU extracts the sender's Bluetooth device address and compares it with the bound device list stored internally to confirm that the sender is an authorized device. The DKECU determines whether the requested control function is allowed based on the vehicle's current operating status (e.g., driving / parking / charging, etc.) (e.g., opening the tailgate is not allowed while driving). After successful verification, the DKECU converts the control function identifier and action identifier in the command into the corresponding CAN bus standard command and sends it to the corresponding body controller (e.g., BCM) for execution via the CAN bus.

[0064] The mobile terminal configuration module interacts with the vehicle control device function module via Link-A to complete the vehicle control function mapping configuration; the vehicle control device function module interacts with the DKECU module via Link-C to complete the execution of vehicle control commands. The two interaction stages of vehicle control configuration and vehicle control execution are decoupled through the vehicle control function mapping table inside the vehicle control device. Configuration can be completed at any time, and execution is triggered at the moment of pressing.

[0065] The mobile terminal will send the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU via the digital key security channel, so that the DKECU can bind the vehicle control device. This may include:

[0066] Step 301: The mobile terminal responds to the user's vehicle control device management operation, determines whether the digital key security channel is connected, and executes the vehicle control device management operation if the digital key security channel is connected; if the digital key security channel is not connected, the vehicle control device management operation is prohibited and a prompt is given.

[0067] Step 302: The mobile terminal responds to the user's binding command, obtains the identification information of the vehicle control device to be bound through the first Bluetooth connection, and sends the identification information of the vehicle control device to be bound to the DKECU through the digital key security channel; the DKECU establishes a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device, and stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established.

[0068] Step 302 includes sub-steps 3021 to 3026.

[0069] Sub-step 3021: Scanning vehicle control equipment.

[0070] When performing the vehicle control device binding operation, the car owner carries a mobile terminal and places the vehicle control device to be bound, such as a Bluetooth physical button device, near the driver's seat in the car. At this time, the mobile terminal and DKECU automatically establish a digital key security channel connection.

[0071] With the digital key security channel already connected, the mobile terminal responds to the user's binding command by scanning for vehicle control devices to be bound according to preset filtering rules. Specifically, the scan is filtered according to preset UUIDs and preset device name prefixes (such as "AIOT*") to ensure that only devices of the target type are discovered.

[0072] Sub-step 3022: First Bluetooth connection establishment and acquisition of device identification information.

[0073] The mobile terminal establishes a first Bluetooth connection with the scanned vehicle control device to be bound. The first Bluetooth connection is a Bluetooth GATT (Generic Attribute Profile) connection. The device information of the vehicle control device to be bound is obtained through the first Bluetooth connection. The identification information of the vehicle control device to be bound includes, but is not limited to, the MAC (Media Access Control) address, and the MAC address can be 6 bytes long.

[0074] Sub-step 3023: Bind request forwarding.

[0075] The mobile terminal encapsulates the binding request (also known as the add request) based on the identification information of the vehicle control device to be bound. The binding request may include the identification information of the vehicle control device to be bound and the request type identifier. The mobile terminal sends the binding request to the DKECU through the Link-B-based digital key security channel.

[0076] Sub-step 3024: DKECU verifies the identification information and reconnects to the vehicle control device.

[0077] DKECU receives and verifies the binding request, checks whether the number of currently bound devices has reached the threshold, and verifies the legality of the device's identification information. Upon successful verification, DKECU uses the received identification information of the vehicle control device to be bound as the target address and initiates a second Bluetooth connection with the vehicle's Bluetooth module as the master device. This second Bluetooth connection is a Bluetooth GATT connection.

[0078] Sub-step 3025: Two-way confirmation and status reporting.

[0079] After the second Bluetooth connection (i.e., Link-C connection) is successfully established, the DKECU stores the binding relationship established by the current binding operation and reports the binding success status notification to the digital key application on the mobile terminal via Link-B. Upon receiving the binding success notification, the mobile terminal visually displays the binding success result. The DKECU can add the successfully connected vehicle control device to the bound device list, thereby storing the binding relationship between the bound vehicle control device and the DKECU. The bound device list may contain the identification information of the successfully connected vehicle control device.

[0080] Sub-step 3026: Binding failure handling.

[0081] If DKECU verification fails, for example, if the number of bound devices has reached the threshold, DKECU will return a binding failure response with the corresponding error code via Link-B. If DKECU reconnection times out in sub-step 2024, with a timeout threshold of, for example, 5 seconds, DKECU will also return a binding failure response with a timeout error code.

[0082] Step 303: DKECU establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship. Each bound vehicle control device sends vehicle control commands to DKECU through the second Bluetooth connection. DKECU receives the vehicle control commands and controls the vehicle to perform the corresponding vehicle control operations.

[0083] Optionally, the various links in the vehicle control system adopt a unified binary frame structure to achieve data transmission. The data transmission method of the vehicle control system may include steps 401 and 402.

[0084] Step 401: Obtain the data to be transmitted, and determine the unified routing identifier URI and target link corresponding to the data to be transmitted based on the functional semantic type of the data to be transmitted and the preset correspondence.

[0085] The data to be transmitted can be various data from the vehicle control system, such as binding data, configuration data, unbinding data, device connection status query data, vehicle control commands, and device connection status notification data. It can be understood that the data to be transmitted can be various data required by the functions of the vehicle control system, and no specific restrictions are imposed here.

[0086] The default mapping is between URIs, the functional semantic types of communication data in the vehicle control system, and the correspondence between communication links in the vehicle control system. The URI (Uniform Resource Identifier) ​​field serves as a bridge between the frame structure and business logic. Link-A uses URI 0x0801 (configuration), Link-B uses URIs 0x0802 (add), 0x0803 (status notification), 0x0804 (delete), and 0x0805 (query), and Link-C uses URI 0x0806 (vehicle control command). Within the same frame structure, the URI determines the semantics and processing path of the payload.

[0087] Please see Figure 5 The example of the preset correspondence shown may include the following:

[0088] Configuration command (URI: 0x0801) is used to configure the mapping relationship between the operation type and vehicle control command sent by the mobile terminal on the Link-A link to the vehicle control device.

[0089] The Add Binding instruction (URI: 0x0802) is used by mobile terminals on the Link-B link to initiate a device add binding request to the DKECU.

[0090] Status notification command (URI: 0x0803) is used by the DKECU on the Link-B link to actively push the connection status of multiple devices to the mobile terminal.

[0091] The deletion command (URI: 0x0804) is used by mobile terminals on the Link-B link to initiate a device deletion request to the DKECU;

[0092] The query command (URI: 0x0805) is used by mobile terminals on the Link-B link to query the DKECU for a list of bound devices.

[0093] Vehicle control command (URI: 0x0806) is used by IoT devices on the Link-C link to send vehicle control commands to the DKECU.

[0094] The preset correspondence can be expanded according to the communication needs within the system. This disclosure does not impose specific restrictions on the preset correspondence.

[0095] Step 402: Assemble the service payload field of the TLV structure based on the data to be transmitted, encapsulate the data to be transmitted into a data frame according to a preset unified format based on the determined URI and the assembled payload field, and send the data frame through the target link.

[0096] Encapsulating data frames according to a pre-defined uniform format may involve assembling the following fields in sequence: Start of Frame (SOF) field, Length field, Control field, Frame Sequence Number (FSN) field, Message field, Command field, Payload field, URI field, and Checksum field. The checksum is used in data processing and communication to check data integrity; it typically involves summing a set of data items (such as bytes or 16-bit binary numbers) and generating a checksum value according to specific rules. The Control field includes a direction indicator bit, an encryption indicator bit, a response indicator bit, and a packet splitting indicator bit, where the direction indicator bit indicates request and response frames.

[0097] The following is an example of the unified binary data frame structure encapsulated according to this disclosure:

[0098] SOF field (1 byte): Fixed at 0x5A, serving as the start of frame identifier;

[0099] Length field (2 bytes): Records the total number of bytes from the Header Control field to the end of the Body.

[0100] Control field (1 byte): contains direction indicator bit, encryption indicator bit, response indicator bit and packetization indicator bit, where the direction indicator bit is used to distinguish between request frames and response frames;

[0101] FSN field (1 byte): Intra-session auto-incrementing frame sequence number, used for request-response matching and replay prevention;

[0102] The Message ID field (1 byte) and Command ID field (1 byte) jointly identify the message type and command category;

[0103] URI field (2 bytes): Routing identifier, used to distinguish the business function semantics carried by the frame. Different URI values ​​correspond to different functional semantic types (i.e. business functions). The receiving end distributes the payload to the corresponding business processing module according to the URI.

[0104] Payload field (variable length): It uses a Tag-Length-Value structure to carry business data and supports carrying multiple TLV key-value pairs within the same frame;

[0105] CheckSum field (2 bytes): CRC checksum value.

[0106] Different links and different business semantics can be distinguished by different URI values. The remaining fields of the frame format are defined consistently across the three links, thus enabling the use of a unified protocol frame structure across the three links Link-A, Link-B, and Link-C of the vehicle control system. This achieves cross-link, full-scenario business data transmission functionality and reduces system communication complexity.

[0107] Optionally, the data transmission method may further include step 403:

[0108] Step 403: Obtain the received data frame, extract the URI from the received data frame, determine the functional semantic type of the received data frame based on the extracted URI and the preset correspondence, and distribute the service payload of the received data frame to the service processing module corresponding to the functional semantic type of the received data frame.

[0109] When assembling protocol frames, the sending end selects the corresponding URI value based on the service's link affiliation and functional semantics, and assembles the corresponding TLV payload. After completing frame synchronization and integrity verification, the receiving end routes the payload to the corresponding service processing module based on the URI. The URIs of request and response frames are the same, distinguished by the response indication bit in the control field.

[0110] In one example, a mobile terminal responds to a user's configuration operation by obtaining configuration data for a vehicle control device to be configured. Based on the configuration data, it assembles a configuration command and sends the configuration command to the vehicle control device via a first Bluetooth connection. This process may include: the mobile terminal determining the unified routing identifier (URI) and target link corresponding to the configuration data based on the functional semantic type of the configuration data and a preset correspondence; the preset correspondence is the correspondence between the URI, the functional semantic type of communication data in the vehicle control system, and the communication links in the vehicle control system. Based on the configuration data, it assembles the service payload field of a TLV structure. Based on the determined URI and the assembled payload field, it encapsulates the configuration data into the configuration command according to a preset unified format and sends the configuration command via the first Bluetooth connection, which is a Bluetooth connection based on the target link of the configuration data.

[0111] The configuration instruction includes at least one set of key-value pairs, which are operation type and vehicle control function identifier key-value pairs. The key-value pairs of the configuration instruction are assembled in the payload of the configuration instruction according to the TLV format.

[0112] The following example illustrates the assembly and transmission of configuration command frames, as well as the entire process of multi-device status aggregation monitoring.

[0113] Assembly and transmission of configuration command frames

[0114] Application scenario: Mobile terminals need to map single clicks of button devices to door lock control and double clicks to tailgate control. The following is the complete process from frame assembly to reception and parsing.

[0115] Sending end frame assembly process:

[0116] Determine URI=0x0801 (Configuration directive, Link-A link).

[0117] Assemble the Payload TLV:

[0118] Item 1: Tag=0x01 (Click), Length=2, Value=0x063E (Door lock control)

[0119] Item 2: Tag=0x02 (double-click), Length=2, Value=0x0623 (tailgate control)

[0120] Fill in each field of the protocol frame in sequence:

[0121] SOF = 0x5A

[0122] Length = Calculate the number of bytes from Control to the end of the Body.

[0123] Control = 0x01 (Direction = sender → receiver, other indicator bits are 0)

[0124] FSN = Current session sequence number (e.g., 0x01)

[0125] Message ID = 0x80 (Frame Communication)

[0126] Command ID = 0x82 (Remote control command)

[0127] URI = 0x0801

[0128] Payload = (0x01 0x02 0x063E) + (0x02 0x02 0x0623)

[0129] CheckSum = CRC calculation result

[0130] Transmitted via the Link-A BLE GATT data channel.

[0131] Frame parsing process at the receiving end:

[0132] The button device receives frame data via Link-A and completes frame synchronization by reading SOF=0x5A.

[0133] Read the Length field and verify that the frame length matches the Length field value.

[0134] Read Control and confirm that the direction indicator is sender → receiver.

[0135] Read URI=0x0801 and route to the configuration processing module.

[0136] The configuration processing module parses each TLV entry in the payload and updates the internal function mapping table.

[0137] Construct a response frame (URI is 0x0801, Control direction bit is flipped, response indicator bit = 1), Payload is (Tag 0x01, Length 1, Value 0x00 = Success), and return via Link-A.

[0138] The vehicle control method provided in this disclosure will now be introduced from the perspective of the mobile terminal side of the vehicle control system.

[0139] Please refer to Figure 6 This disclosure provides a vehicle control method, which can be executed by a vehicle control device provided in this embodiment. The vehicle control device can be implemented in software and / or hardware and configured in a mobile terminal within the aforementioned vehicle control system. For example... Figure 6 As shown, the vehicle control method of this invention includes the following steps:

[0140] Step 601: Respond to the user's configuration operation to obtain the configuration data of the vehicle control device to be configured.

[0141] Step 602: Assemble the configuration command based on the configuration data, and send the configuration command to the vehicle control device to be configured via the first Bluetooth connection.

[0142] The configuration data includes: a mapping relationship between operation types and vehicle control function identifiers; the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device; wherein, the vehicle control device receives configuration instructions from its own device via the first Bluetooth connection and parses them to obtain the mapping relationship between operation types and vehicle control function identifiers sent by the mobile terminal, and updates the vehicle control mapping relationship stored in the vehicle control device according to the received mapping relationship. The vehicle control device responds to user input operations to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier according to the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control instruction according to the target vehicle control function identifier, and sends the vehicle control instruction to the DKECU via a second Bluetooth connection, which is a connection between the vehicle control device and the DKECU. The DKECU performs authentication and authorization verification on the vehicle control instruction received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control instruction if the authentication and authorization verification are successful.

[0143] The vehicle control device has completed its identity registration in advance through the binding process with DKECU. The binding process includes the mobile terminal sending the identification information of the vehicle control device obtained through the first Bluetooth connection to DKECU through the digital key security channel, so that DKECU can bind the vehicle control device.

[0144] Please refer to Figure 7 This disclosure provides a vehicle control method, which can be executed by a vehicle control device provided in this embodiment. The vehicle control device can be implemented in software and / or hardware and configured in the vehicle control equipment of the aforementioned vehicle control system. For example... Figure 7 As shown, the vehicle control method of this invention includes the following steps:

[0145] Step 701: The vehicle control device receives the configuration command sent by the mobile terminal through the first Bluetooth connection and parses it to obtain the mapping relationship between the sent operation type and the vehicle control function identifier. Based on the received mapping relationship between the operation type and the vehicle control function identifier, the vehicle control device updates the vehicle control mapping relationship stored in the device.

[0146] The mobile terminal responds to the user's configuration operation to obtain the configuration data of the vehicle control device to be configured, assembles the configuration command based on the configuration data, and sends the configuration command to the vehicle control device to be configured through the first Bluetooth connection; the configuration data includes: the mapping relationship between operation type and vehicle control function identifier, and the first Bluetooth connection is the Bluetooth connection between the mobile terminal and the vehicle control device.

[0147] Step 702: The vehicle control device responds to the user's input operation to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier according to the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command according to the target vehicle control function identifier, and sends the vehicle control command to DKECU through the second Bluetooth connection.

[0148] The second Bluetooth connection serves as the link between the vehicle control device and the DKECU. The DKECU verifies the identity and permissions of vehicle control commands received via the second Bluetooth connection based on a list of bound devices. If the identity and permissions verification is successful, the DKECU controls the vehicle to execute the vehicle control commands. The mobile terminal sends the identification information of the vehicle control device obtained via the first Bluetooth connection to the DKECU through the digital key security channel, allowing the DKECU to bind the vehicle control device.

[0149] The parts of the vehicle control method executed by the mobile terminal and vehicle control equipment that are the same as those executed by the aforementioned vehicle control system will not be repeated here.

[0150] The following are examples illustrating the application of the personalized configuration method for vehicle control equipment according to embodiments of the present invention.

[0151] Basic configuration and usage scenarios

[0152] Application Scenario: Car owners use a smartphone's digital key app to configure the vehicle control functions of Bluetooth physical buttons (vehicle control devices) that are already bound to the vehicle. The owner wants to map a single click to "door lock control," a double click to "tailgate control," and a long press to "window control."

[0153] Configuration process:

[0154] The car owner accesses the detailed configuration page of the button device in the App (the function mapping display submodule loads the current mapping relationship configuration status). Currently displayed: Single click = door lock control (already configured), Double click = not configured, Long press = not configured.

[0155] When the car owner clicks the "double-click" button, a pop-up window appears at the bottom of the vehicle control function selector submodule, displaying a list of available vehicle control functions: door lock control, tailgate control, window control, sunroof control, sliding door control, sunshade control, and not configured. The currently highlighted item is "not configured".

[0156] The car owner selects "Tailgate Control" and clicks OK, returning to the configuration page. Double-clicking displays "Tailgate Control". Similarly, the car owner long-presses to select "Window Control".

[0157] The configuration instruction assembly submodule detected the following modifications: double-click → tailgate control, long press → window control. The assembly configuration instruction contains two TLV entries: (Tag 0x02, Length 2, Value 0x0623) indicates double-click = tailgate control; (Tag 0x03, Length 2, Value 0x0621) indicates long press = window control.

[0158] The car owner clicks "Save Configuration", and the App sends the configuration command to the button device via Link-A BLE GATT.

[0159] The configuration parsing submodule for button devices receives instructions, parses the TLV entries one by one, and updates the function mapping table: writing double-click → 0x0623, long press → 0x0621. A success response is then returned.

[0160] After receiving a successful response, the app displays a toast message saying "Configuration saved".

[0161] Execution process:

[0162] The driver does not need to take out their phone while driving; they can press buttons inside the car. The button debounce and type recognition submodule captures the press signal, with a debounce window of 40ms. The press duration is used to determine whether it is a single click (Tag 0x01).

[0163] The instruction assembly submodule uses Tag 0x01 as the index to look up the function mapping table, obtains Value=0x063E (door lock control), and attaches the action flag open (0x00) to assemble the vehicle control instruction.

[0164] The direct-connect transmission submodule sends vehicle control commands to the DKECU via Link-C BLE GATT.

[0165] The DKECU's authentication submodule verifies that the sender's Bluetooth address is in the list of bound devices, and authentication is successful.

[0166] The vehicle status permission verification submodule confirms that the current vehicle is in a parked state, and door lock operations are allowed to be executed.

[0167] The CAN command conversion submodule converts the commands into CAN bus door lock control commands and sends them to the BCM. The BCM then performs the door lock unlocking operation.

[0168] Double-clicking (triggers tailgate control), and long-pressing (triggers window control) work similarly.

[0169] One-to-one multi-function mapping and multi-button collaboration

[0170] Application Scenario: The car owner has installed button device A (driver's seat) and button device B (rear seat) in the vehicle. The owner wants button device A to be mapped to "door lock control" with a single click and "door lock control" with a double click (for convenient two-way triggering); and button device B to be mapped to "window control" with a single click and "sunroof control" with a double click.

[0171] Configuration process:

[0172] The vehicle owner enters the configuration page of device A and sets both single-click and double-click to "door lock control". The configuration instructions contain two TLVs: single-click → 0x063E, double-click → 0x063E (the two operation types map to the same vehicle control function).

[0173] After saving, go to the configuration page of device B, and set the single click to "window control" (0x0621) and the double click to "sunroof control" (0x0622).

[0174] Each button device independently stores its own vehicle control mapping table, without affecting each other.

[0175] Execution effect: Pressing the button on device A, whether single or double-clicking, triggers the door lock operation. Pressing the button on device B, a single click triggers window control, and a double click triggers sunroof control.

[0176] Operation type "Not Configured" and Ignore handling

[0177] Application scenario: Car owners only need the button device to respond to single-click operations (door lock control), and do not want double-clicks and long presses to trigger any actions.

[0178] Configuration process:

[0179] Enter the configuration page, click the current mapping as "Door Lock Control" (keep), double-click to select "Not Configured", or long-press to select "Not Configured".

[0180] Save configuration and update device function mapping table: Click → 0x063E, Double-click → null, Long press → null.

[0181] Execution result:

[0182] When a user presses a button: the button debounce and type recognition submodule identifies it as a single click, looks up the table to obtain Value=0x063E, and then proceeds to assemble and send vehicle control commands normally.

[0183] If a user presses the button twice in quick succession, it is recognized as a double-click. The table value is null (not configured), so the operation is ignored and no command is generated.

[0184] User long press: Recognized as a long press, the table lookup also returns null, and the operation is ignored.

[0185] In summary, the vehicle control method disclosed in this invention has the following advantages compared with the prior art:

[0186] (1) Decoupling of configuration and execution phases: The mobile terminal only participates in the configuration phase, while the vehicle control device independently sends vehicle control commands to the DKECU in the execution phase. Compared with using a mobile phone to control the car, users can control the vehicle by using physical buttons without taking out their mobile phones while driving, which balances driving safety and ease of operation.

[0187] (2) Portable dynamic configuration capability of mobile terminal: The button function is mapped and sent to the vehicle control device as a TLV structured instruction through the BLE GATT bidirectional channel and its internal mapping table is updated. The configuration of the vehicle control device is realized by utilizing the human-computer interaction capability of the mobile terminal.

[0188] (3) Flexible vehicle control function mapping: Supports mapping multiple operation modes of the same button (single click, double click, long press, etc.) to different vehicle control functions, and also supports mapping multiple operation modes to the same vehicle control function. Meets users' personalized button definition needs.

[0189] (4) Reuse of digital key security system: When the vehicle control device is directly connected to the vehicle control execution, DKECU uses the established binding relationship and identity verification system to verify the source of the command, thus ensuring control security.

[0190] This invention provides a vehicle control device, which is configured in a vehicle control system, such as... Figure 8 As shown, the data transmission device 800 includes a configuration generation module 802 and a binding module 804.

[0191] The configuration generation module 802 is used to obtain configuration data of the vehicle control device to be configured in response to the user's configuration operation, assemble configuration instructions according to the configuration data, and send the configuration instructions to the vehicle control device to be configured through a first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers. The first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device receives the configuration instructions of its own vehicle control device through the first Bluetooth connection and parses them to obtain the mapping relationship between the operation types and vehicle control function identifiers sent by the mobile terminal. It updates the vehicle control mapping relationship stored in the vehicle control device according to the received mapping relationship between the operation types and vehicle control function identifiers. The vehicle control device determines the corresponding target operation type in response to the user's input operation, determines the corresponding target vehicle control function identifier according to the target operation type and vehicle control mapping relationship, encapsulates the vehicle control instruction according to the target vehicle control function identifier, and sends the vehicle control instruction to the DKECU through a second Bluetooth connection. The second Bluetooth connection is a connection between the vehicle control device and the DKECU. The DKECU performs identity verification and permission verification on the vehicle control instruction received through the second Bluetooth connection according to the list of bound devices. If the identity verification and permission verification are successful, the DKECU controls the vehicle to execute the vehicle control instruction.

[0192] The binding module 804 is used to send the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

[0193] This invention provides a vehicle control device, comprising at least one vehicle control device configured in a vehicle control system, such as... Figure 9 As shown, the vehicle control device 900 includes a vehicle control configuration module 902 and a vehicle control generation module 904.

[0194] The vehicle control configuration module 902 is used to receive configuration instructions from the mobile terminal via a first Bluetooth connection, parse them to obtain the mapping relationship between the issued operation type and the vehicle control function identifier, and update the vehicle control mapping relationship stored in the vehicle control device according to the received mapping relationship between the operation type and the vehicle control function identifier. The mobile terminal responds to the user's configuration operation to obtain the configuration data of the vehicle control device to be configured, assembles the configuration instructions according to the configuration data, and sends the configuration instructions to the vehicle control device to be configured via the first Bluetooth connection. The configuration data includes: the mapping relationship between the operation type and the vehicle control function identifier, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device.

[0195] The vehicle control generation module 904 is used to respond to user input operations to determine the corresponding target operation type, determine the corresponding target vehicle control function identifier based on the target operation type and vehicle control mapping relationship, encapsulate the vehicle control command based on the target vehicle control function identifier, and send the vehicle control command to the DKECU via the second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU; wherein, the DKECU performs identity verification and authorization verification on the vehicle control command received through the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful; wherein, the mobile terminal sends the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

[0196] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. The electronic device 100 includes a memory 110, a processor 120, and a computer program stored in the memory 110 and executable on the processor 120. When the processor 120 executes the program, it implements the vehicle control method as described in the foregoing embodiments.

[0197] This invention provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer processor, is used to perform the technical solution of any method embodiment.

[0198] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or grid device, etc.) to execute the methods described in the various embodiments of the present invention.

[0199] It is worth noting that in the embodiments of the above-mentioned device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy distinction between each other and are not used to limit the scope of protection of the present invention.

[0200] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A vehicle control method, characterized in that, The method is applied to a vehicle control system, which includes: a mobile terminal, a digital key control unit (DKECU) for the vehicle, and at least one vehicle control device. The mobile terminal is equipped with a digital key application and can establish a digital key security channel with the DKECU. The vehicle control device is a vehicle control command input device. The mobile terminal responds to the user's configuration operation to obtain the configuration data of the vehicle control device to be configured, assembles a configuration instruction based on the configuration data, and sends the configuration instruction to the vehicle control device to be configured via a first Bluetooth connection; the configuration data includes: a mapping relationship between operation type and vehicle control function identifier, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device; The vehicle control device receives configuration instructions from itself via the first Bluetooth connection and parses them to obtain the mapping relationship between the issued operation type and the vehicle control function identifier. It then updates the vehicle control mapping relationship stored in its storage based on the received mapping relationship between the operation type and the vehicle control function identifier. The vehicle control device responds to the user's input operation to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier according to the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command according to the target vehicle control function identifier, and sends the vehicle control command to the DKECU through a second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU. The DKECU verifies the identity and permissions of the vehicle control commands received via the second Bluetooth connection based on the list of bound devices. If the identity and permissions verification is successful, the DKECU controls the vehicle to execute the vehicle control commands. The vehicle control device has pre-registered its identity through a binding process with the DKECU. The binding process includes the mobile terminal sending the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel.

2. The method according to claim 1, characterized in that, The mobile terminal responds to the user's configuration operation by acquiring configuration data of the vehicle control device to be configured, assembling a configuration command based on the configuration data, and sending the configuration command to the vehicle control device to be configured via a first Bluetooth connection, including: The mobile terminal determines the unified routing identifier URI and target link corresponding to the configuration data based on the functional semantic type of the configuration data and the preset correspondence; the preset correspondence is the correspondence between the URI, the functional semantic type of the communication data in the vehicle control system, and the communication link in the vehicle control system. The service payload field of the TLV structure is assembled based on the configuration data. The configuration data is then encapsulated into the configuration instruction according to a preset unified format based on the determined URI and the assembled payload field. The configuration instruction is then sent through the first Bluetooth connection, which is a Bluetooth connection to the target link based on the configuration data.

3. The method according to claim 2, characterized in that, The configuration instruction includes at least one set of key-value pairs, which are operation type and vehicle control function identifier key-value pairs. The key-value pairs of the configuration instruction are assembled in the payload of the configuration instruction according to the TLV format.

4. The method according to claim 1, characterized in that, The vehicle control device has operation buttons, and the operation types include at least two of the following: single click, double click, and long press; the vehicle control functions include one or more of the following: door lock control, tailgate control, window control, sunroof control, sliding door control, and sunshade control; the mapping relationship between operation types and vehicle control function identifiers includes mapping relationships between multiple operation types and the same vehicle control function, and mapping relationships where no mapping is configured for operation types; when the vehicle control function identifier corresponding to the target operation type is in an unconfigured state, the vehicle control device ignores the current input operation.

5. The method according to claim 1, characterized in that, The mobile terminal responds to the user's configuration operation by obtaining configuration data for the vehicle control device to be configured, including: The mobile terminal determines the vehicle control function identifier corresponding to each operation type in response to the user's operation on the bottom pop-up window or the selectable vehicle control list in the human-computer interaction interface.

6. The method according to claim 1, characterized in that, The method further includes: The DKECU determines whether the vehicle control device sending the vehicle control command is already in the bound device list to authenticate the vehicle control device; the DKECU determines whether the vehicle control operation corresponding to the vehicle control command is allowed to be executed in the current vehicle state based on the current vehicle status information to verify the permission of the vehicle control command; if both the authentication and permission verification are successful, the DKECU controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

7. A vehicle control method, characterized in that, A mobile terminal applied to a vehicle control system, the vehicle control system further including: a digital key control unit (DKECU) for the vehicle and at least one vehicle control device, the mobile terminal having a digital key APP installed and capable of establishing a digital key security channel with the DKECU, the vehicle control device being a vehicle control command input device; the method includes: In response to a user's configuration operation, the system acquires configuration data for the vehicle control device to be configured, assembles a configuration command based on the configuration data, and sends the configuration command to the vehicle control device via a first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers. The first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device receives the configuration command from the mobile terminal via the first Bluetooth connection, parses it to obtain the mapping relationship between the operation types and vehicle control function identifiers sent by the mobile terminal, and updates the vehicle control device according to the received mapping relationship. The system stores vehicle control mapping relationships. The vehicle control device responds to user input to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection. The second Bluetooth connection is the connection between the vehicle control device and the DKECU. The DKECU performs identity verification and authorization verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful. The vehicle control device has pre-registered its identity through a binding process with the DKECU. The binding process includes the mobile terminal sending the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel.

8. A vehicle control method, characterized in that, At least one vehicle control device is applied to a vehicle control system, wherein the vehicle control device is a vehicle control command input device; the vehicle control system further includes: a mobile terminal and a vehicle digital key control unit (DKECU), wherein the mobile terminal is equipped with a digital key APP and is capable of establishing a digital key security channel with the DKECU; the method includes: The vehicle control device receives configuration instructions from the mobile terminal via a first Bluetooth connection and parses them to obtain a mapping relationship between the issued operation type and the vehicle control function identifier. Based on the received mapping relationship, the device updates the vehicle control mapping relationship stored in its storage. The mobile terminal, in response to a user's configuration operation, obtains configuration data for the vehicle control device to be configured, assembles a configuration instruction based on the configuration data, and sends the configuration instruction to the vehicle control device to be configured via the first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device responds to the user's input operation to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU; wherein, the DKECU performs identity verification and authorization verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful; wherein, the mobile terminal sends the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

9. A vehicle control device, characterized in that, A mobile terminal configured in a vehicle control system, the vehicle control system further including: a digital key control unit (DKECU) and at least one vehicle control device, the mobile terminal having a digital key APP installed and capable of establishing a digital key security channel with the DKECU, the vehicle control device being a vehicle control command input device; the vehicle control device includes: A configuration generation module is used to obtain configuration data of the vehicle control device to be configured in response to the user's configuration operation, assemble configuration instructions based on the configuration data, and send the configuration instructions to the vehicle control device to be configured via a first Bluetooth connection. The configuration data includes a mapping relationship between operation types and vehicle control function identifiers. The first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device. The vehicle control device receives the configuration instructions of its own device via the first Bluetooth connection, parses the mapping relationship between the operation types and vehicle control function identifiers sent by the mobile terminal, and updates the configuration based on the received mapping relationship. The vehicle control device stores vehicle control mapping relationships; the vehicle control device responds to user input operations to determine the corresponding target operation type, determines the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulates the vehicle control command based on the target vehicle control function identifier, and sends the vehicle control command to the DKECU via a second Bluetooth connection; the second Bluetooth connection is the connection between the vehicle control device and the DKECU; the DKECU performs identity verification and permission verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and permission verification are successful; The binding module is used to send the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

10. A vehicle control device, characterized in that, At least one vehicle control device configured in the vehicle control system, wherein the vehicle control device is a vehicle control command input device; the vehicle control system further includes: a mobile terminal and a vehicle digital key control unit (DKECU), wherein the mobile terminal is equipped with a digital key APP and is capable of establishing a digital key security channel with the DKECU; the vehicle control device includes: A vehicle control configuration module is used to receive configuration instructions for the vehicle control device issued by the mobile terminal via a first Bluetooth connection, parse them to obtain a mapping relationship between the issued operation type and the vehicle control function identifier, and update the vehicle control mapping relationship stored in the vehicle control device according to the received mapping relationship between the operation type and the vehicle control function identifier; wherein the mobile terminal obtains configuration data of the vehicle control device to be configured in response to the user's configuration operation, assembles a configuration instruction according to the configuration data, and sends the configuration instruction to the vehicle control device to be configured via the first Bluetooth connection; the configuration data includes: a mapping relationship between the operation type and the vehicle control function identifier, and the first Bluetooth connection is a Bluetooth connection between the mobile terminal and the vehicle control device; The vehicle control generation module is used to determine the corresponding target operation type in response to user input, determine the corresponding target vehicle control function identifier based on the target operation type and the vehicle control mapping relationship, encapsulate the vehicle control command based on the target vehicle control function identifier, and send the vehicle control command to the DKECU via a second Bluetooth connection; the second Bluetooth connection is a connection between the vehicle control device and the DKECU; wherein, the DKECU performs identity verification and authorization verification on the vehicle control command received via the second Bluetooth connection according to the list of bound devices, and controls the vehicle to execute the vehicle control command if the identity verification and authorization verification are successful; wherein, the mobile terminal sends the identification information of the vehicle control device obtained through the first Bluetooth connection to the DKECU through the digital key security channel, so that the DKECU can bind the vehicle control device.

11. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle control method as described in any one of claims 1 to 8.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the vehicle control method as described in any one of claims 1 to 8.

Images