Vehicle control method and device, vehicle control system, electronic equipment and storage medium

Abstract

Embodiments of the present application disclose a vehicle control method, device, system, electronic device and storage medium, comprising: the mobile terminal prohibits vehicle control device management operation and prompts in the case where the digital key security channel is not connected; the mobile terminal acquires the identification information of the vehicle control device to be bound through the first Bluetooth connection in response to the binding instruction of the user, and sends the identification information to the DKECU through the digital key security channel; the DKECU establishes the second Bluetooth connection with the vehicle control device to be bound according to the identification information, and stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established; each bound vehicle control device sends the vehicle control instruction to the DKECU through the second Bluetooth connection, the DKECU receives the vehicle control instruction, controls the vehicle to perform the vehicle control operation corresponding to the vehicle control instruction, and realizes the safe and flexible vehicle control through the mobile terminal as a relay hub to realize the management operation such as the binding of the vehicle control device.

Description

Technical Field

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

[0002] The widespread adoption of smartphones and other portable mobile devices as digital car keys has led to a surge in demand for vehicle control functions such as windows, sunroofs, and trunks, driven by rapid advancements in vehicle intelligence. One existing technology utilizes smartphones for vehicle control, requiring users to hold and operate the phone, which is cumbersome and poses safety concerns. Current solutions based on button-based controls require pre-installing the buttons in a whitelist and lack dynamic management capabilities. Therefore, existing technologies lack the ability to securely and conveniently manage independent IoT button devices for vehicle control, hindering users' ability to conveniently control their vehicles using one or more button devices. Summary of the Invention

[0003] This invention provides a vehicle control method, device, system, electronic device, and storage medium, aiming to achieve safe, flexible, and easy-to-manage vehicle control based on the relay hub function of a mobile terminal.

[0004] In a first aspect, embodiments of the present invention provide a vehicle control method applied 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 vehicle control device management operation by determining whether the digital key security channel is connected. If the digital key security channel is connected, the vehicle control device management operation is executed. If the digital key security channel is not connected, the vehicle control device management operation is prohibited and a prompt is given.

[0006] The vehicle control device management operation includes: a binding operation; correspondingly, in response to the user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound through a 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;

[0007] The DKECU establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship. Each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection. The DKECU receives the vehicle control command and controls the vehicle to perform the vehicle control operation corresponding to the vehicle control command.

[0008] 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) and at least one vehicle control device. The mobile terminal is equipped with a digital key application and is capable of establishing a digital key security channel with the DKECU. The vehicle control device is a vehicle control command input device. The method includes:

[0009] In response to a vehicle control device management operation, determine whether the digital key security channel is connected. If the digital key security channel is connected, execute the vehicle control device management operation. If the digital key security channel is not connected, prohibit the vehicle control device management operation and issue a prompt.

[0010] The vehicle control device management operation includes: a binding operation; correspondingly, in response to the user's binding command, the identification information of the vehicle control device to be bound is obtained through a first Bluetooth connection, and the identification information of the vehicle control device is sent to the DKECU through the digital key security channel, so that the DKECU can establish a second Bluetooth connection with the vehicle control device to be bound according to the identification information of the vehicle control device, and store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established, and the DKECU establishes a second Bluetooth connection with each bound vehicle control device according to the established binding relationship, and each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection, the DKECU receives the vehicle control command, and controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

[0011] Thirdly, embodiments of the present invention provide a vehicle control method, applied to a digital key control unit (DKECU) in a vehicle control system. The vehicle control system further includes a mobile terminal 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 method includes:

[0012] In response to the binding request of the mobile terminal, the identification information of the vehicle control device to be bound is received through the digital key security channel; wherein, if the digital key security channel is already connected, the mobile terminal obtains the identification information of the vehicle control device through a first Bluetooth connection.

[0013] A second Bluetooth connection is established with the vehicle control device to be bound based on the identification information of the vehicle control device to be bound. After the second Bluetooth connection is successfully established, the binding relationship between the vehicle control device to be bound and the DKECU is stored.

[0014] Based on the established binding relationship, a second Bluetooth connection is established with each bound vehicle control device. The vehicle control commands sent by each bound vehicle control device are received through the second Bluetooth connection, and the vehicle is controlled to perform the vehicle control operation corresponding to the vehicle control command.

[0015] Fourthly, 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 has a digital key APP and is capable of establishing a digital key secure channel with the DKECU; the method includes:

[0016] In response to the binding request from the mobile terminal, the identification information of the vehicle control device is sent to the mobile terminal via a first Bluetooth connection. The mobile terminal performs vehicle control device management operations when the digital key security channel is connected, and prohibits such operations when the digital key security channel is not connected. The vehicle control device management operations include a binding operation. The mobile terminal sends a binding request to the vehicle control device to be bound in response to the user's binding instruction. The mobile terminal sends the identification information of the vehicle control device to be bound to the DKECU via the digital key security channel, so that the DKECU can initiate a second Bluetooth connection establishment request to the vehicle control device to be bound based on the identification information.

[0017] In response to the second Bluetooth connection establishment request, a second Bluetooth connection is established with the DKECU, so that the DKECU stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established;

[0018] In response to the DKECU's connection request to the bound vehicle control device, a second Bluetooth connection is established with the DKECU. In response to the vehicle control input operation, a vehicle control command is generated and sent to the DKECU through the second Bluetooth connection, so that the DKECU can control the vehicle to perform the corresponding vehicle control operation according to the vehicle control command.

[0019] Fifthly, 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 application installed and capable of establishing a digital key security channel with the DKECU; the vehicle control device is a vehicle control command input device; the device includes:

[0020] The security detection module is used to respond to vehicle control device management operations, determine whether the digital key security channel is connected, execute the vehicle control device management operation if the digital key security channel is connected, and prohibit the vehicle control device management operation and issue a prompt if the digital key security channel is not connected.

[0021] The vehicle control device management operation includes: a binding operation; correspondingly, an identification information forwarding module is used to respond to the user's binding command, obtain the identification information of the vehicle control device to be bound through a first Bluetooth connection, and send the identification information of the vehicle control device to the DKECU through the digital key security channel, so that the DKECU can establish a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device, and store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established, and the DKECU establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship, and each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection, the DKECU receives the vehicle control command, and controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

[0022] Sixthly, embodiments of the present invention provide a vehicle control device, comprising a DKECU configured in a vehicle control system, the vehicle control system further comprising a mobile terminal and at least one vehicle control device, the mobile terminal having a digital key application 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 device comprising:

[0023] The identification receiving module is used to receive the identification information of the vehicle control device to be bound through the digital key security channel in response to the binding request of the mobile terminal; wherein, when the digital key security channel is already connected, the mobile terminal obtains the identification information of the vehicle control device through a first Bluetooth connection.

[0024] The binding connection module is used to establish a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device to be bound, and to store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established;

[0025] The vehicle control execution module is used to establish a second Bluetooth connection with each bound vehicle control device according to the established binding relationship, receive vehicle control commands sent by each bound vehicle control device through the second Bluetooth connection, and control the vehicle to perform the vehicle control operation corresponding to the vehicle control command.

[0026] In a seventh aspect, embodiments of the present invention provide a vehicle control device, a vehicle control equipment configured in a vehicle control system, the vehicle control system further including a mobile terminal and a DKECU, the mobile terminal having a digital key application installed and capable of establishing a digital key security channel with the DKECU; the vehicle control equipment is a vehicle control command input device; the device includes:

[0027] An identification sending module is used to respond to a binding request from the mobile terminal by sending identification information of the vehicle control device to the mobile terminal via a first Bluetooth connection. The mobile terminal performs vehicle control device management operations when the digital key security channel is connected, and prohibits vehicle control device management operations when the digital key security channel is not connected. The vehicle control device management operations include a binding operation. The mobile terminal sends a binding request to the vehicle control device to be bound in response to a user's binding instruction. The mobile terminal sends the identification information of the vehicle control device to be bound to the DKECU via the digital key security channel, so that the DKECU can initiate a second Bluetooth connection establishment request to the vehicle control device to be bound based on the identification information of the vehicle control device to be bound.

[0028] A binding connection module is used to establish a second Bluetooth connection with the DKECU in response to the second Bluetooth connection establishment request, so that the DKECU stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established;

[0029] The vehicle control transmission module is used to establish a second Bluetooth connection with the DKECU in response to the connection request of the DKECU to the bound vehicle control device, generate vehicle control commands in response to vehicle control input operations, and send the vehicle control commands to the DKECU through the second Bluetooth connection so that the DKECU can control the vehicle to perform corresponding vehicle control operations according to the vehicle control commands.

[0030] Eighthly, embodiments of the present invention provide a system comprising:

[0031] The secure channel establishment module is configured to establish a secure channel between the mobile terminal and the DKECU.

[0032] The device management and control module is configured such that: in response to the user's vehicle control device management operation, the mobile terminal determines whether the digital key security channel is connected; if the digital key security channel is connected, the vehicle control device management operation is executed; if the digital key security channel is not connected, the vehicle control device management operation is prohibited and a prompt is given.

[0033] The device binding module is configured as follows: In response to a user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound via a first Bluetooth connection between the mobile terminal and the device to be bound, 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.

[0034] The vehicle control module is configured such that: the DKECU establishes a second Bluetooth connection with each bound vehicle control device according to the established binding relationship; each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection; the DKECU receives the vehicle control command and controls the vehicle to perform the vehicle control operation corresponding to the vehicle control command.

[0035] The aggregation module is configured as follows: the DKECU monitors the connection status of each bound vehicle control device according to the established binding relationship, determines whether any bound vehicle control device has experienced a connection status change event based on the connection status of all bound vehicle control devices, and when the connection status change event occurs, aggregates the connection status of all bound vehicle control devices and sends the aggregated connection status to the mobile terminal through the digital key security channel. The mobile terminal receives the connection status sent by the DKECU and displays the connection status in a visual manner in response to the connection status viewing operation.

[0036] The data transmission module is used to acquire data to be transmitted on the link between the mobile terminal, the vehicle control device, and the DKECU; 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 a 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 various communication links between the mobile terminal, the vehicle control device, and the DKECU; assemble the service payload (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.

[0037] In a ninth 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.

[0038] In a tenth 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.

[0039] In this embodiment, the mobile terminal responds to the user's vehicle control device management operation. If the digital key security channel is connected, the mobile terminal performs the vehicle control device management operation; if the digital key security channel is not connected, the mobile terminal prohibits the vehicle control device management operation and provides a prompt. This ensures the management authority of the vehicle control device based on the highly secure digital key security channel connection, guaranteeing the security and legality of the vehicle control device management operation. In response to the user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound via a first Bluetooth connection and sends this identification information to the DKECU via 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, and stores the binding relationship between the vehicle control device and the DKECU after the second Bluetooth connection is successfully established. The mobile terminal acts as a relay hub to forward the identification information of the vehicle control device to be bound, and the data transmission security is ensured based on the digital key security channel. This allows the DKECU to conveniently and securely obtain the vehicle control device identification information and achieve secure binding between the vehicle control device and the DKECU. Subsequently, the 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 the DKECU through the second Bluetooth connection. The DKECU receives the vehicle control commands and controls the vehicle to execute the corresponding vehicle control operations. Therefore, binding the vehicle control devices to the DKECU through the digital key security channel ensures the legitimacy and high security of the vehicle control devices. Direct vehicle control via the vehicle control devices eliminates the need to send vehicle control commands through the digital key security channel, reducing the complexity of vehicle control. Attached Figure Description

[0040] 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.

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

[0042] Figure 2 A flowchart illustrating the vehicle control method based on a vehicle control system provided in an embodiment of the present invention;

[0043] Figure 3 A flowchart illustrating a vehicle control method based on a mobile terminal in a vehicle control system, provided in an embodiment of the present invention.

[0044] Figure 4 A flowchart illustrating a vehicle control method based on a DKECU in a vehicle control system, provided in an embodiment of the present invention;

[0045] Figure 5 A flowchart illustrating a vehicle control method based on a vehicle control device in a vehicle control system, provided in an embodiment of the present invention;

[0046] Figure 6 A schematic diagram of the structure of a vehicle control device applied to a mobile terminal provided in an embodiment of the present invention;

[0047] Figure 7 This is a schematic diagram of the structure of a vehicle control device applied to a DKECU, provided in an embodiment of the present invention;

[0048] Figure 8 This is a schematic diagram of the structure of a vehicle control device applied to vehicle control equipment, provided in an embodiment of the present invention;

[0049] Figure 9 This is a functional block diagram of a vehicle control system provided in an embodiment of the present invention;

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

[0051] 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.

[0052] This embodiment provides a vehicle control system, method, device, electronic device, and storage medium for coordinating the binding, configuration, and status management operations between a vehicle control device (an independent IoT control device) and a vehicle digital key control unit (DKECU) when a digital key security channel is already connected, using a mobile terminal as a relay hub. This enables the independent IoT device to become a secure, easy-to-operate, and easily managed vehicle control device, meeting the user's vehicle control needs.

[0053] The vehicle control system, 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.

[0054] Figure 1 This is a schematic diagram of the vehicle control system provided in an embodiment of the present invention, such as... Figure 1 As shown, the vehicle control system includes: a mobile terminal 102, a vehicle 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. In this embodiment, the DKECU 104 is responsible for digital key management, identity authentication, and vehicle control command execution. 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 configured 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.

[0055] Figure 2 A flowchart of the vehicle control method provided in the embodiments of the present invention is shown below. Figure 2 As shown, the vehicle control method includes steps 201 to 203.

[0056] Step 201: 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.

[0057] To ensure the legitimate authorization of users' vehicle control device management operations, in this embodiment, the mobile terminal, in response to each user's vehicle control device management operation, checks whether the mobile terminal and the DKECU are connected and authenticated (i.e., whether a digital key secure channel has been established). If the digital key secure channel is connected, the current vehicle control device management operation is allowed; if the digital key secure channel is not connected, the operation is prohibited, and the user is prompted to establish a digital key secure channel first. The digital key secure channel is established based on the Bluetooth link (i.e., Link-B) between the mobile terminal and the DKECU. As a digital key infrastructure, the digital key secure channel has high security. The mobile terminal executes vehicle control device management operations only if the digital key secure channel is connected, ensuring high security for these operations. In this embodiment, when transmitting vehicle control device management operation-related data through the digital key secure channel, the transmitted data can be encrypted and signed to guarantee data transmission security.

[0058] User vehicle control device management operations include: binding, deletion, configuration, and query operations. Binding allows an independent vehicle control device to become a legally authorized vehicle control input device. Configuration allows dynamic setting of the mapping relationship between the input operations of the vehicle control device and the vehicle control function. Deletion allows unbinding of bound vehicle control devices. Query allows querying the DKECU for a list of bound devices.

[0059] Step 202: In response to the user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound via the first Bluetooth connection and sends this identification information to the DKECU through the digital key security channel. The DKECU establishes a second Bluetooth connection with the vehicle control device based on its identification information and stores the binding relationship between the vehicle control device and the DKECU after the second Bluetooth connection is successfully established. The first Bluetooth connection is a Bluetooth connection based on the Bluetooth link between the mobile terminal and the vehicle control device (i.e., Link-A). The second Bluetooth connection is a Bluetooth connection based on the Bluetooth link between the vehicle control device and the DKECU (i.e., Link-C).

[0060] Step 202 includes sub-steps 2021 to 2026.

[0061] Sub-step 2021: Scanning vehicle control equipment.

[0062] 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.

[0063] 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.

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

[0065] 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.

[0066] Sub-step 2023: Bind request forwarding.

[0067] 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.

[0068] Sub-step 2024: DKECU verifies identification information and reconnects to vehicle control equipment.

[0069] 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.

[0070] Sub-step 2025: Two-way confirmation and status reporting.

[0071] 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.

[0072] Sub-step 2026: Binding failure handling.

[0073] 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.

[0074] Step 203: 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.

[0075] When the vehicle is not in use, the DKECU can be in sleep mode, during which the second Bluetooth connection between the paired vehicle control device and the DKECU can be disconnected. Upon waking, the DKECU can automatically reconnect to the paired vehicle control device. Users can input vehicle control commands through the vehicle control device, such as pressing buttons. The vehicle control device responds to the input, generates corresponding vehicle control commands, and sends them directly to the DKECU via the second Bluetooth connection. The DKECU then controls the vehicle to execute these commands.

[0076] Alternatively, the vehicle control method may also include:

[0077] Step 204: DKECU monitors the connection status of each bound vehicle control device according to the established binding relationship. Based on the connection status of all bound vehicle control devices, it determines whether any bound vehicle control device has experienced a connection status change event. If a connection status change event occurs, it aggregates the connection status of all bound vehicle control devices and sends the aggregated connection status to the mobile terminal through the digital key security channel. The mobile terminal receives the connection status sent by DKECU and responds to the connection status viewing operation to visualize the connection status.

[0078] In other words, the DKECU continuously monitors the Link-C connection status of all bound vehicle control devices. Connection statuses can include: not connected, connected, and connected, each identified by a different status code. When the connection status of any device changes, such as from "connected" to "not connected," from "not connected" to "connecting," or from "connecting" to "connected," the DKECU aggregates the current status of all bound devices into a single notification message. The status of each device is organized as a key-value pair containing a status code and a device identifier. The DKECU pushes the aggregated notification message to the mobile terminal through the Link-B digital key secure channel. After receiving the message, the mobile terminal parses the status of each device and updates the status indicator of the corresponding device on the interface. By using the DKECU as a proxy node and employing an aggregation push mechanism, the status notifications for N devices are compressed from N independent queries to a single aggregated notification, significantly reducing the resource consumption for status notification communication. It is understood that the DKECU-based vehicle control device status aggregation push mechanism of this embodiment can also be applied independently to similar scenarios, and no specific limitations are imposed here.

[0079] Optionally, the vehicle control device management operation may also include a deletion operation. Correspondingly, the vehicle control method may also include: the mobile terminal responding to the user's device deletion command by sending the identification information of the vehicle control device to be deleted to the DKECU through the digital key security channel; the DKECU disconnecting from the vehicle control device to be deleted based on the identification information of the vehicle control device to be deleted and deleting the binding relationship between the vehicle control device to be deleted and the DKECU.

[0080] The process of deleting a bound device also requires that the digital key security channel be connected. After the user selects the device to be deleted, the mobile terminal may display a secondary confirmation pop-up to ensure operational security and prevent accidental operation. In response to the user's secondary confirmation, the mobile terminal sends a deletion request containing the device's identification information to the DKECU via Link-B. The DKECU disconnects the Bluetooth connection with the device and removes the device from the list of bound devices. After receiving a successful deletion response from the DKECU, the card of the deleted vehicle control device disappears from the management list on the mobile terminal.

[0081] The following is a description of an application example of the vehicle control method based on embodiments of the present invention:

[0082] 1. Binding process for single-button devices

[0083] The car owner has successfully connected the vehicle's DKECU (digital key is authenticated) through the digital key application and placed a Bluetooth physical button device to be bound near the driver's seat inside the car.

[0084] The binding method operation process is as follows:

[0085] S11. The user opens the device management interface in the vehicle control App on the mobile terminal and clicks the "Add Device" button.

[0086] S12. When the vehicle control app confirms that the digital key is not connected, a prompt "Please connect the digital key first" will pop up, and the current operation will be disabled. When the vehicle control app confirms that the digital key is connected, it will start a BLE scan with the following parameters: service UUID filter condition is 0xFC47, and broadcast name prefix filter condition is "AIOT*". The scan timeout is set to 15 seconds. After about 3 seconds, the vehicle control app will scan for a Bluetooth physical button device with a name such as "AIOT001A7DDA7108" and display the device and signal strength indicator in the scan list.

[0087] S13. When the user clicks on the device entry scanned this time, the vehicle control App establishes a Link-A BLE GATT connection with the button device. The connection parameters are: minimum connection interval 45ms, maximum connection interval 60ms, slave device delay 0, connection timeout 5000ms, and MTU (Maximum Transmission Unit) 203 bytes.

[0088] S14. After successful connection, the vehicle control app obtains the MAC address of the button device: 001A7DDA7108 (6 bytes).

[0089] S15. The vehicle control app sends an add request to the DKECU through the Link-B digital key security channel, and the add request carries the device's identification information (MAC: 001A7DDA7108).

[0090] S16. After receiving the add request, DKECU performs the following verification: For example, if the number of currently bound devices is 0, which is below the binding threshold (the binding threshold is 3), and the device identifier format is valid, the verification passes.

[0091] S17. DKECU initiates a BLE GATT connection request (Link-C) with MAC address 001A7DDA7108 as the target address and the vehicle's Bluetooth module as the master device. The connection parameters are the same as for Link-A. The Link-C connection is successfully established after approximately 2 seconds. DKECU records the binding relationship (Device MAC="001A7DDA7108" → Status="Connected").

[0092] The S18 and DKECU send a successful binding notification to the vehicle control app via Link-B. Upon receiving the notification, the vehicle control app displays a "Successfully Added" message, the button device card is added to the management list, and the status indicator light turns green (connected).

[0093] Using the vehicle control method of this invention, the entire process of adding a single button device to the binding can be completed in about 10 seconds. The operation is simple and user-friendly, and does not require the vehicle manufacturer to pre-set binding information or return the device to the factory for programming.

[0094] 2. Simultaneous binding and management of multiple devices

[0095] Application scenario: The car owner has installed two Bluetooth physical button devices in the car (device A is located on the left side of the driver's seat, and device B is located on the right side of the passenger seat). He wants to bind the two devices to the vehicle and check their connection status in the car control app.

[0096] The binding and management process is as follows:

[0097] S21. The vehicle owner first binds device A (e.g., MAC: 001A7DDA7108) according to the binding process of the single-button device mentioned above. After the binding is completed, the DKECU binds the device count to 1.

[0098] S22. The car owner clicks "Add Device" again, and the vehicle control app scans and finds device B (e.g., MAC: 013A6DDA8109). The car owner selects device B, completes the Link-A connection, and obtains the MAC address of device B.

[0099] S23. The vehicle control app sends a request to add device B to the DKECU via Link-B. After the DKECU verifies the request, it initiates a Link-C reconnection to device B.

[0100] S24. After the Link-C connection of device B is successfully established, DKECU will set the binding count to 2.

[0101] S25 and DKECU detected a change in the binding list, triggering an aggregation operation that iterates through the two bound devices:

[0102] Device A (001A7DDA7108): Status = Connected (0x01)

[0103] Device B (013A6DDA8109): Status = Connected (0x01)

[0104] S26 and DKECU aggregate the status of the two devices into a single notification message (URI 0x0803), which is then pushed to the vehicle control app via Link-B. The Uniform Resource Identifier (URI) and its application methods are described below.

[0105] S27. After the vehicle control app parses the notification message, it displays two device cards in the device management list: Device A's status light is green (connected), and Device B's status light is also green (connected).

[0106] If three devices (also known as dynamic stickers) are already bound to the DKECU, when attempting to add a fourth device, the DKECU detects that the number of bound devices has reached the binding threshold (e.g., 3) and returns the error code "Quantity Exceeded" (ERR_STICKER_COUNT_EXCEED). The vehicle control app prompts "The number of bound dynamic stickers has reached the limit. Please delete them before adding again," and the addition operation is blocked.

[0107] 3. Device connection disconnection and automatic recovery

[0108] Application scenario: Device A, which has been bound to the device, loses its Link-C connection due to battery depletion. After DKECU detects the status change, it actively notifies the vehicle control app.

[0109] The device status notification process is described as follows:

[0110] S31, DKECU continuously monitors the Link-C connection status of device A and device B. Under normal conditions, both devices are "connected" (0x01).

[0111] S32. At a certain moment, device A loses its Link-C Bluetooth connection because its battery voltage drops below the minimum operating voltage of the BLE module.

[0112] S33, DKECU detects that the Link-C connection of device A changes from "connected" to "not connected" (0x00), triggering an aggregation operation:

[0113] Device A: Not connected (0x00)

[0114] Device B: Connected (0x01)

[0115] S34 and DKECU generate aggregated status notifications and push them to the vehicle control app via Link-B.

[0116] S35. After receiving the notification, the vehicle control app updates its interface: the status indicator light on device A changes from green to gray (not connected), while device B remains green (connected).

[0117] S36. The vehicle control app can additionally display the text "Not Connected" next to the device A card to guide users to check the device status.

[0118] S37. Device Reconnection: After the owner replaces the battery of Device A, Device A is powered on again and broadcasts. DKECU detects the broadcast signal of Device A and actively re-establishes the Link-C connection. After the connection is established, the status changes to "Connected" (0x01). DKECU triggers the aggregated push again, and the status indicator light of Device A in the vehicle control app returns to green.

[0119] Example parameter settings are as follows: Link-C connection timeout is set to 5 seconds; maximum number of devices bound to a single vehicle is set to 3; broadcast scan timeout is set to 15 seconds; DKECU status monitoring cycle is real-time (triggered when connection status changes, not timed polling); status code definition: 0x00 = not connected, 0x01 = connected, 0x02 = connecting.

[0120] 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.

[0121] Please refer to Figure 3 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 3 As shown, the vehicle control method of this invention includes the following steps:

[0122] Step 301: In response to the vehicle control device management operation, determine whether the digital key security channel is connected. If the digital key security channel is connected, perform the vehicle control device management operation. If the digital key security channel is not connected, prohibit the vehicle control device management operation and issue a prompt.

[0123] Step 302: In response to the user's binding command, the identification information of the vehicle control device to be bound is obtained through the first Bluetooth connection. This identification information is then sent to the DKECU via the digital key security channel. The DKECU establishes a second Bluetooth connection with the vehicle control device to be bound based on this identification information. After the second Bluetooth connection is successfully established, the binding relationship between the vehicle control device to be bound and the DKECU is stored. The DKECU also establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship. Each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection. The DKECU receives the vehicle control command and controls the vehicle to execute the corresponding vehicle control operation. The first Bluetooth connection is a GATT Bluetooth connection based on Link-A between the mobile terminal and the vehicle control device, and the second Bluetooth connection is a GATT Bluetooth connection based on Link-C between the vehicle control device and the DKECU.

[0124] As the relay hub of the vehicle control system, the mobile terminal mainly plays three roles:

[0125] First, the device management role: scanning, connecting, binding, configuring, and deleting vehicle control devices.

[0126] Second, the information forwarding role: forwards the identification information of the vehicle control device to the DKECU through the digital key security channel, and sends back the connection status and execution results of the DKECU to the user interface.

[0127] Third, the security management role: Presumably, the digital key must be connected before any device management operation can be blocked if the device is not authenticated. Before each device management operation (add, delete, query, configure), the system checks if the digital key is connected and authenticated. If not, the operation is blocked and the user is prompted.

[0128] After receiving and parsing the multi-device connection status notification reported by DKECU, the mobile terminal displays the real-time connection status of each device in a visual manner (such as status indicator lights of different colors) on the device management interface.

[0129] Next, we will introduce the vehicle control method provided in this publication from the perspective of the DKECU in the vehicle control system.

[0130] Please refer to Figure 4 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 DKECU of the aforementioned vehicle control system. For example... Figure 4 As shown, the vehicle control method of this invention includes the following steps:

[0131] Step 401: In response to the binding request from the mobile terminal, receive the identification information of the vehicle control device to be bound through the digital key security channel.

[0132] In this scenario, the mobile terminal obtains the identification information of the vehicle control device via the first Bluetooth connection when the digital key security channel is already connected.

[0133] Step 402: Establish a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device to be bound, and store the binding relationship between the vehicle control device to be bound and DKECU after the second Bluetooth connection is successfully established.

[0134] Step 403: Establish a second Bluetooth connection with each bound vehicle control device based on the established binding relationship, receive vehicle control commands sent by each bound vehicle control device through the second Bluetooth connection, and control the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

[0135] The core functions of DKECU include: receiving the identification information of the vehicle control device to be bound from the mobile terminal and initiating an active BLE reconnection; real-time monitoring and aggregation reporting of the connection status of all bound IoT control devices; and converting vehicle control commands from vehicle control devices into CAN bus commands for execution after identity verification and permission checks. For vehicle control commands from Link-C, it performs sender identity verification (e.g., confirming the sender exists in the list of bound devices) and vehicle status permission checks (e.g., confirming that the requested vehicle control function is allowed to be executed under the current vehicle status).

[0136] The following section will introduce the vehicle control method provided in this disclosure from the perspective of the vehicle control equipment in the vehicle control system.

[0137] Please refer to Figure 5 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 5 As shown, the vehicle control method of this invention includes the following steps:

[0138] Step 501: In response to the binding request from the mobile terminal, the identification information of the vehicle control device is sent to the mobile terminal via the first Bluetooth connection; wherein, the mobile terminal performs vehicle control device management operations when the digital key security channel is connected, and prohibits vehicle control device management operations when the digital key security channel is not connected. The vehicle control device management operations include binding operations. The mobile terminal sends a binding request to the vehicle control device to be bound in response to the user's binding instruction; the mobile terminal sends the identification information of the vehicle control device to be bound to the DKECU via the digital key security channel, so that the DKECU can initiate a second Bluetooth connection establishment request to the vehicle control device to be bound based on the identification information of the vehicle control device to be bound.

[0139] Step 502: In response to the second Bluetooth connection establishment request, establish a second Bluetooth connection with the DKECU, so that the DKECU stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established.

[0140] Step 503: In response to the DKECU's connection request to the bound vehicle control device, establish a second Bluetooth connection with the DKECU; in response to the vehicle control input operation, generate a vehicle control command and send the vehicle control command to the DKECU through the second Bluetooth connection, so that the DKECU can control the vehicle to perform the corresponding vehicle control operation according to the vehicle control command.

[0141] The vehicle control device serves as the user's physical input interface, including at least one operable button and a BLE communication module. The device supports three operating modes: broadcast mode (sending a BLE broadcast containing the device identifier for discovery by mobile terminals and the DKECU), configuration receiving mode (receiving button function mapping configurations from the mobile terminal via Link-A), and direct-connection vehicle control mode (sending vehicle control commands directly to the DKECU via Link-C, without requiring online involvement from the mobile terminal).

[0142] The parts of the vehicle control methods executed by the mobile terminal, DKECU, and vehicle control equipment that are consistent with the vehicle control methods executed by the aforementioned vehicle control system will not be repeated here.

[0143] In summary, the vehicle control method disclosed in this invention allows the mobile terminal to perform vehicle control device management operations only when the digital key security channel is connected. When the digital key security channel is not connected, vehicle control device management operations are prohibited, and a prompt is issued. Responding to the user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound via a first Bluetooth connection and sends this information to the DKECU via 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 and stores the binding relationship between the vehicle control device to be bound and the DKECU after successful establishment. The DKECU then establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship. Each bound vehicle control device sends a vehicle control command to the DKECU via the second Bluetooth connection. The DKECU receives the vehicle control command and controls the vehicle to perform the corresponding vehicle control operation.

[0144] The embodiments of the present invention have the following advantages:

[0145] (1) Three-layer relay architecture: By integrating independent IoT control devices (such as Bluetooth physical button input devices) with DKECU through mobile terminals, the mobile terminal, DKECU and vehicle control device can cooperate through three independent communication links, Link-A, Link-B and Link-C, to form a three-layer architecture of "mobile terminal as the hub, IoT control device as the input and DKECU as the execution". This realizes a complete closed loop of device binding, configuration distribution, vehicle control execution and status monitoring, so that the mobile terminal can play an active relay role in the entire life cycle management of the device.

[0146] (2) Binding security mechanism with digital key as a prerequisite: The connection and authentication of the digital key is a prerequisite for the device binding operation. Combined with the closed-loop process of "mobile terminal discovery → DKECU back connection → two-way confirmation", the binding operation is ensured to be performed only in scenarios where a secure session has been established. This solves the problem that the traditional pre-set whitelist method is difficult to support the dynamic addition and deletion of devices, while also providing higher security.

[0147] (3) DKECU proactive aggregation monitoring: As a status aggregation node, DKECU continuously listens to the connection status changes of all bound devices and proactively reports them, which reduces communication overhead and mobile terminal power consumption compared to the traditional polling method.

[0148] (4) Reuse of digital key security channel: The Link-B management channel reuses the existing BLE secure communication channel of the digital key. All IoT device management commands (add, delete, query, status notification) are transmitted through this encrypted channel, without the need to establish an additional independent encrypted channel for IoT device management.

[0149] This invention provides a vehicle control device, which is configured on a mobile terminal configured in a vehicle control system, such as... Figure 6 As shown, the vehicle control device 600 includes a safety detection module 602 and an identification information forwarding module 604.

[0150] The security detection module 602 is used to respond to vehicle control device management operations, determine whether the digital key security channel is connected, and perform vehicle control device management operations if the digital key security channel is connected, and prohibit vehicle control device management operations and issue a prompt if the digital key security channel is not connected.

[0151] The vehicle control device management operation includes: binding operation; correspondingly, the identification information forwarding module 604 is used to respond to the user's binding command, obtain the identification information of the vehicle control device to be bound through the first Bluetooth connection, and send the identification information of the vehicle control device to the DKECU through the digital key security channel, so that the DKECU can establish a second Bluetooth connection with the vehicle control device to be bound according to the identification information of the vehicle control device, and store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established, and the DKECU establishes a second Bluetooth connection with each bound vehicle control device according to the established binding relationship, and each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection, the DKECU receives the vehicle control command and controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

[0152] This invention provides a vehicle control device, which is configured in a DKECU, such as... Figure 7 As shown, the vehicle control device 700 includes: an identification receiving module 702, a binding connection module 704, and a vehicle control execution module 706.

[0153] The identification receiving module 702 is used to receive the identification information of the vehicle control device to be bound through the digital key security channel in response to the binding request of the mobile terminal; wherein, when the digital key security channel is already connected, the mobile terminal obtains the identification information of the vehicle control device through the first Bluetooth connection.

[0154] The binding connection module 704 is used to establish a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device to be bound, and to store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established.

[0155] The vehicle control execution module 706 is used to establish a second Bluetooth connection with each bound vehicle control device according to the established binding relationship, receive vehicle control commands sent by each bound vehicle control device through the second Bluetooth connection, and control the vehicle to perform the vehicle control operation corresponding to the vehicle control command.

[0156] This invention provides a vehicle control device, which is configured in a vehicle control system, such as... Figure 8 As shown, the vehicle control device 800 includes: an identification sending module 802, a binding connection module 804, and a vehicle control sending module 806.

[0157] The identification sending module 802 is used to respond to the binding request of the mobile terminal and send the identification information of the vehicle control device to the mobile terminal through the first Bluetooth connection. The mobile terminal performs vehicle control device management operations when the digital key security channel is connected, and prohibits vehicle control device management operations when the digital key security channel is not connected. Vehicle control device management operations include binding operations. The mobile terminal sends a binding request to the vehicle control device to be bound in response to the user's binding instruction. The mobile terminal sends the identification information of the vehicle control device to be bound to the DKECU through the digital key security channel, so that the DKECU can initiate a second Bluetooth connection establishment request to the vehicle control device to be bound based on the identification information of the vehicle control device to be bound.

[0158] The binding connection module 804 is used to establish a second Bluetooth connection with the DKECU in response to a second Bluetooth connection establishment request, so that the DKECU stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established.

[0159] The vehicle control transmission module 806 is used to establish a second Bluetooth connection with the DKECU in response to the DKECU's connection request to the bound vehicle control device, generate vehicle control commands in response to vehicle control input operations, and send the vehicle control commands to the DKECU through the second Bluetooth connection so that the DKECU can control the vehicle to perform corresponding vehicle control operations according to the vehicle control commands.

[0160] Figure 9 This is a schematic diagram of the vehicle control system provided in an embodiment of the present invention. Figure 9 As shown, the vehicle control system includes: a safety channel establishment module 901, a device management and control module 902, a device binding module 903, a vehicle control module 904, an aggregation module 905, and a data transmission module 906.

[0161] The secure channel establishment module 901 is configured to establish a secure channel between the mobile terminal and the DKECU.

[0162] The device management control module 902 is configured as follows: the mobile terminal responds to the user's vehicle control device management operation, determines whether the digital key security channel is connected, executes the vehicle control device management operation if the digital key security channel is connected, and prohibits the vehicle control device management operation and provides a prompt if the digital key security channel is not connected.

[0163] The device binding module 903 is configured as follows: In response to the user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound through the first Bluetooth connection between the mobile terminal and the vehicle control device to be bound, 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.

[0164] The vehicle control module 904 is configured such that: the 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 the DKECU through the second Bluetooth connection; the DKECU receives the vehicle control commands and controls the vehicle to execute the vehicle control operations corresponding to the vehicle control commands.

[0165] The aggregation module 905 is configured as follows: DKECU monitors the connection status of each bound vehicle control device according to the established binding relationship, determines whether any bound vehicle control device has experienced a connection status change event based on the connection status of all bound vehicle control devices, and aggregates the connection status of all bound vehicle control devices in the event of a connection status change event. The aggregated connection status is then sent to the mobile terminal through the digital key security channel. The mobile terminal receives the connection status sent by DKECU and displays the connection status in a visual manner in response to the connection status viewing operation.

[0166] Please refer to the aforementioned embodiments for the modules in the vehicle control system; they will not be repeated here.

[0167] The data transmission module 906 is used to acquire data to be transmitted on the link between the mobile terminal, the vehicle control device, and the DKECU. It determines the unified routing identifier (URI) and target link corresponding to the data to be transmitted based on the functional semantic type of the data and a preset correspondence. The preset correspondence includes the URI, the functional semantic type of the communication data in the vehicle control system, and the correspondence between the various communication links between the mobile terminal, the vehicle control device, and the DKECU. It assembles the service payload field of the TLV structure based on the data to be transmitted, encapsulates 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 sends the data frame through the target link.

[0168] The data transmission module 906 is described in detail below:

[0169] 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.

[0170] 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 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.

[0171] For example, the preset correspondence may include the following correspondence:

[0172] 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.

[0173] 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.

[0174] 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.

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

[0176] 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.

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

[0178] 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.

[0179] Encapsulating data frames according to a pre-defined unified 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 to check data integrity in data processing and communication. It is usually generated by summing a group of data items (such as bytes or 16-bit binary numbers) and generating a check value according to specific rules. The Control field contains direction indicator bits, encryption indicator bits, response indicator bits, and packet splitting indicator bits. The direction indicator bits are used to indicate request frames and response frames.

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

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

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

[0183] 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;

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

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

[0186] 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.

[0187] 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;

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

[0189] 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.

[0190] The vehicle control system may also include a distribution module, configured to: acquire received data frames, extract URIs from the received data frames, determine the functional semantic type of the received data frames based on the extracted URIs and preset correspondences, and distribute the service payload of the received data frames to the service processing modules corresponding to the functional semantic type of the received data frames.

[0191] 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.

[0192] The aggregation module 905 can be configured as follows: DKECU loads a list of bound devices, which records the identification information and current connection status of each bound device. DKECU listens to the Link-C link connection status of each device based on the identification information of each device in the bound device list, and perceives the connection status changes of each device in real time through the Bluetooth protocol stack connection status callback mechanism. When any bound device experiences a Link-C connection status change event, it iterates through the list of bound devices to obtain the current connection status code of each device. Based on the identification information and current connection status code of each device, it obtains the connection status notification data of the bound device.

[0193] Accordingly, the data transmission module 906 can be configured such that: the DKECU obtains the target URI and target link corresponding to the connection status notification data based on the functional semantic type of the connection status notification data and the preset correspondence, wherein the target link is a Link-B link. The DKECU assembles the key-value pairs of the current connection status of all bound devices into the service payload of the data frame to be transmitted; wherein, the key-value pairs of the connection status of multiple bound devices are assembled into multiple TLVs and then placed sequentially into the payload field of the same data frame, and the Value in the TLV is the concatenation value of the connection status code of the bound device and the device MAC address. The connection status of the device includes: connected, connected, and not connected. The direction indicator bit in the control field of the connection status notification data frame is used to indicate that the data transmission direction is from server to client, and the response indicator bit is set to no response requirement. The DKECU pushes the connection status notification data frame to the mobile terminal through the Link-B digital key security channel.

[0194] The process for transmitting and processing connection status notification data in the vehicle control system of this embodiment is as follows:

[0195] Service initialization: DKECU starts the status aggregation monitoring service, loads the list of bound IoT control devices (maintained by the bound device list management submodule), and establishes continuous listening for the Link-C Bluetooth connection status of each device in the list (the Bluetooth protocol stack callback is registered by the Link-C connection status listening submodule).

[0196] State change detection: When the Link-C connection state of any bound device changes (including from "connected" to "not connected", from "not connected" to "connecting", and from "connecting" to "connected"), the Link-C connection state monitoring submodule receives a Bluetooth protocol stack callback notification and activates the state aggregation submodule.

[0197] Status Aggregation: The status aggregation submodule iterates through the list of bound devices and queries the current Link-C connection status code for each device. It organizes the status information of each device into a TLV set in the format of (status code + device MAC address), where each device's tag is the device serial number and its value is the concatenation of the status code and MAC address.

[0198] Notification Frame Construction and Push: The notification frame construction and push submodule encapsulates the aggregated TLV entry set into a payload, sets the URI to 0x0803 according to the pre-stored preset correspondence, and sends the entire data frame to the mobile terminal through the Link-B digital key secure channel. The direction indicator bit in the Control field of this frame is marked as "server → client", and the response indicator bit is set to no response required. This notification is a one-way push and does not require a response.

[0199] App-side parsing and display: After receiving the data frame with URI 0x0803, the mobile terminal app's notification frame parsing submodule performs frame integrity verification (Length + CRC), extracts each TLV entry from the payload, and parses the (MAC address, status code) of each device. The status visualization update submodule updates the connection status indication of the corresponding device card on the interface according to the status code.

[0200] The vehicle control system in this embodiment uses URIs and preset link affiliation relationships to enable the transmission of different functional semantic business data in cross-link scenarios based on a unified format encapsulation, which can reduce the communication complexity of the vehicle control system.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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.

[0205] 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 vehicle control device management operation by determining whether the digital key security channel is connected. If the digital key security channel is connected, the vehicle control device management operation is executed. If the digital key security channel is not connected, the vehicle control device management operation is prohibited and a prompt is given. The vehicle control device management operation includes: a binding operation; correspondingly, in response to the user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound through a 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; The DKECU establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship. Each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection. The DKECU receives the vehicle control command and controls the vehicle to perform the vehicle control operation corresponding to the vehicle control command.

2. The method according to claim 1, characterized in that, The method further includes: The DKECU monitors the connection status of each bound vehicle control device according to the established binding relationship. Based on the connection status of all bound vehicle control devices, it determines whether a connection status change event has occurred for any bound vehicle control device. If such a connection status change event occurs, the DKECU aggregates the connection status of all bound vehicle control devices and sends the aggregated connection status to the mobile terminal through the digital key security channel. The mobile terminal receives the connection status sent by the DKECU and displays the connection status in a visual manner in response to a connection status viewing operation.

3. The method according to claim 1, characterized in that, The vehicle control device management operation also includes: a deletion operation; correspondingly, the method also includes: In response to the user's device deletion command, the mobile terminal sends the identification information of the vehicle control device to be deleted to the DKECU through the digital key security channel. The DKECU disconnects from the vehicle control device to be deleted based on the identification information of the vehicle control device to be deleted and deletes the binding relationship between the vehicle control device to be deleted and the DKECU.

4. A vehicle control method, characterized in that, A mobile terminal used in a vehicle control system, the vehicle control system also includes a vehicle digital key control unit (DKECU) 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 method includes: In response to a vehicle control device management operation, determine whether the digital key security channel is connected. If the digital key security channel is connected, execute the vehicle control device management operation. If the digital key security channel is not connected, prohibit the vehicle control device management operation and issue a prompt. The vehicle control device management operation includes: a binding operation; correspondingly, in response to the user's binding command, the identification information of the vehicle control device to be bound is obtained through a first Bluetooth connection, and the identification information of the vehicle control device is sent to the DKECU through the digital key security channel, so that the DKECU can establish a second Bluetooth connection with the vehicle control device to be bound according to the identification information of the vehicle control device, and store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established, and the DKECU establishes a second Bluetooth connection with each bound vehicle control device according to the established binding relationship, and each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection, the DKECU receives the vehicle control command, and controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

5. A vehicle control method, characterized in that, A digital key control unit (DKECU) is used in a vehicle control system. The vehicle control system also includes a mobile terminal 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 method includes: In response to the binding request of the mobile terminal, the identification information of the vehicle control device to be bound is received through the digital key security channel; wherein, if the digital key security channel is already connected, the mobile terminal obtains the identification information of the vehicle control device through a first Bluetooth connection. A second Bluetooth connection is established with the vehicle control device to be bound based on the identification information of the vehicle control device to be bound. After the second Bluetooth connection is successfully established, the binding relationship between the vehicle control device to be bound and the DKECU is stored. Based on the established binding relationship, a second Bluetooth connection is established with each bound vehicle control device. The vehicle control commands sent by each bound vehicle control device are received through the second Bluetooth connection, and the vehicle is controlled to perform the vehicle control operation corresponding to the vehicle control command.

6. 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 has a digital key APP and is capable of establishing a digital key security channel with the DKECU; the method includes: In response to the binding request from the mobile terminal, the identification information of the vehicle control device is sent to the mobile terminal via a first Bluetooth connection. The mobile terminal performs vehicle control device management operations when the digital key security channel is connected, and prohibits such operations when the digital key security channel is not connected. The vehicle control device management operations include a binding operation. The mobile terminal sends a binding request to the vehicle control device to be bound in response to the user's binding instruction. The mobile terminal sends the identification information of the vehicle control device to be bound to the DKECU via the digital key security channel, so that the DKECU can initiate a second Bluetooth connection establishment request to the vehicle control device to be bound based on the identification information. In response to the second Bluetooth connection establishment request, a second Bluetooth connection is established with the DKECU, so that the DKECU stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established; In response to the DKECU's connection request to the bound vehicle control device, a second Bluetooth connection is established with the DKECU. In response to the vehicle control input operation, a vehicle control command is generated and sent to the DKECU through the second Bluetooth connection, so that the DKECU can control the vehicle to perform the corresponding vehicle control operation according to the vehicle control command.

7. A vehicle control device, characterized in that, A mobile terminal configured in a vehicle control system, the vehicle control system also includes a vehicle digital key control unit (DKECU) 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 device includes: The security detection module is used to respond to vehicle control device management operations, determine whether the digital key security channel is connected, execute the vehicle control device management operation if the digital key security channel is connected, and prohibit the vehicle control device management operation and issue a prompt if the digital key security channel is not connected. The vehicle control device management operation includes: a binding operation; correspondingly, an identification information forwarding module is used to respond to the user's binding command, obtain the identification information of the vehicle control device to be bound through a first Bluetooth connection, and send the identification information of the vehicle control device to the DKECU through the digital key security channel, so that the DKECU can establish a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device, and store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established, and the DKECU establishes a second Bluetooth connection with each bound vehicle control device based on the established binding relationship, and each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection, the DKECU receives the vehicle control command, and controls the vehicle to execute the vehicle control operation corresponding to the vehicle control command.

8. A vehicle control device, characterized in that, The DKECU is configured in the vehicle control system, which also includes a mobile terminal 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 device includes: The identification receiving module is used to receive the identification information of the vehicle control device to be bound through the digital key security channel in response to the binding request of the mobile terminal; wherein, when the digital key security channel is already connected, the mobile terminal obtains the identification information of the vehicle control device through a first Bluetooth connection. The binding connection module is used to establish a second Bluetooth connection with the vehicle control device to be bound based on the identification information of the vehicle control device to be bound, and to store the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established; The vehicle control execution module is used to establish a second Bluetooth connection with each bound vehicle control device according to the established binding relationship, receive vehicle control commands sent by each bound vehicle control device through the second Bluetooth connection, and control the vehicle to perform the vehicle control operation corresponding to the vehicle control command.

9. A vehicle control device, characterized in that, The vehicle control device is configured in the vehicle control system, which also includes a mobile terminal and a DKECU. 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 device includes: An identification sending module is used to respond to a binding request from the mobile terminal by sending identification information of the vehicle control device to the mobile terminal via a first Bluetooth connection. The mobile terminal performs vehicle control device management operations when the digital key security channel is connected, and prohibits vehicle control device management operations when the digital key security channel is not connected. The vehicle control device management operations include a binding operation. The mobile terminal sends a binding request to the vehicle control device to be bound in response to a user's binding instruction. The mobile terminal sends the identification information of the vehicle control device to be bound to the DKECU via the digital key security channel, so that the DKECU can initiate a second Bluetooth connection establishment request to the vehicle control device to be bound based on the identification information of the vehicle control device to be bound. A binding connection module is used to establish a second Bluetooth connection with the DKECU in response to the second Bluetooth connection establishment request, so that the DKECU stores the binding relationship between the vehicle control device to be bound and the DKECU after the second Bluetooth connection is successfully established; The vehicle control transmission module is used to establish a second Bluetooth connection with the DKECU in response to the connection request of the DKECU to the bound vehicle control device, generate vehicle control commands in response to vehicle control input operations, and send the vehicle control commands to the DKECU through the second Bluetooth connection so that the DKECU can control the vehicle to perform corresponding vehicle control operations according to the vehicle control commands.

10. A vehicle control system, characterized in that, include: The secure channel establishment module is configured to establish a digital key secure channel between the mobile terminal and the DKECU. The device management and control module is configured such that: in response to the user's vehicle control device management operation, the mobile terminal determines whether the digital key security channel is connected; if the digital key security channel is connected, the vehicle control device management operation is executed; if the digital key security channel is not connected, the vehicle control device management operation is prohibited and a prompt is given. The device binding module is configured as follows: In response to a user's binding command, the mobile terminal obtains the identification information of the vehicle control device to be bound via a first Bluetooth connection between the mobile terminal and the device to be bound, 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. The vehicle control module is configured such that: the DKECU establishes a second Bluetooth connection with each bound vehicle control device according to the established binding relationship; each bound vehicle control device sends a vehicle control command to the DKECU through the second Bluetooth connection; the DKECU receives the vehicle control command and controls the vehicle to perform the vehicle control operation corresponding to the vehicle control command. The aggregation module is configured as follows: the DKECU monitors the connection status of each bound vehicle control device according to the established binding relationship, determines whether any bound vehicle control device has experienced a connection status change event based on the connection status of all bound vehicle control devices, and when the connection status change event occurs, aggregates the connection status of all bound vehicle control devices and sends the aggregated connection status to the mobile terminal through the digital key security channel. The mobile terminal receives the connection status sent by the DKECU and displays the connection status in a visual manner in response to the connection status viewing operation. The data transmission module is used to acquire data to be transmitted on the link between the mobile terminal, the vehicle control device, and the DKECU, and to 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 a 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 various communication links between the mobile terminal, the vehicle control device, and the DKECU. The service payload field of the TLV structure is assembled based on the data to be transmitted. The data to be transmitted is encapsulated into a data frame according to a preset unified format based on the determined URI and the assembled payload field, and the data frame is sent through the target link.

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 6.

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 6.

Images