Car digital key terminal equipment and vehicle remote control system

Abstract

This application discloses a digital key terminal device for automobiles and a remote control system for vehicles, relating to the technical field of automotive electronics. In this application, the digital key terminal device for automobiles comprises a main controller and a radio frequency transceiver module, with a bidirectional communication link between them. The first communication link, sequentially connecting the radio frequency transceiver module and the main controller, carries the radio frequency signal characteristics of the vehicle's original key received by the radio frequency transceiver module. The main controller configures the communication parameters of the radio frequency transceiver module based on the radio frequency signal characteristics of the vehicle's original key. The radio frequency transceiver module, based on the communication parameters, simulates the vehicle's original key, and the second communication link, sequentially connecting the main controller and the radio frequency transceiver module, carries the key control signals issued by the main controller. Thus, the radio frequency transceiver module can simulate the functions of the vehicle's original remote key, realizing functions such as locking, unlocking, and starting control of the vehicle, without the need to embed the original physical key inside the vehicle.

Description

Technical Field

[0001] This application relates to the technical field of automotive electronics technology, and more particularly to an automotive digital key terminal device and a vehicle remote control system. Background Technology

[0002] Currently available car digital key terminal devices have poor vehicle compatibility. Many aftermarket digital key solutions require in-depth customization for different brands and models, involving significant hardware and software modifications, high costs, and long development cycles, making it difficult to achieve rapid and widespread vehicle coverage. Furthermore, relying on embedding the original car key, most aftermarket digital key solutions on the market (especially those involving engine starting) require disassembling the original car's physical key (smart key) and embedding it in a specific location inside the vehicle as a key box.

[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Utility Model Content

[0004] The main purpose of this application is to provide a vehicle remote control system that addresses the poor vehicle compatibility and inadequate security of current automotive digital key terminal devices.

[0005] To achieve the above objectives, this application proposes a car digital key terminal device, which includes:

[0006] Main controller and RF transceiver module;

[0007] There is a bidirectional communication link between the main controller and the radio frequency transceiver module. The bidirectional communication link includes a first communication link and a second communication link. The first communication link passes through the radio frequency transceiver module and the main controller in sequence, and the second communication link passes through the main controller and the radio frequency transceiver module in sequence. The first communication link carries the radio frequency signal characteristics of the vehicle's original car key received by the radio frequency transceiver module. The main controller configures the communication parameters of the radio frequency transceiver module according to the radio frequency signal characteristics of the vehicle's original car key. The radio frequency transceiver module simulates the vehicle's original car key based on the communication parameters. The second communication link carries the key control signal sent by the main controller.

[0008] In one embodiment, the car digital key terminal device further includes:

[0009] Wide area network communication module;

[0010] There is a third communication link between the main controller and the wide area network communication module. The third communication link passes through the cloud server, the wide area network communication module and the main controller in sequence. The third communication link carries the vehicle model protocol parameters predefined by the original vehicle key issued by the cloud server. The main controller configures the communication parameters of the radio frequency transceiver module according to the vehicle model protocol parameters.

[0011] In one embodiment, the third communication link also carries the vehicle key control command issued by the cloud server, and the second communication link carries the key control signal corresponding to the vehicle key control command issued by the main controller.

[0012] In one embodiment, the car digital key terminal device further includes:

[0013] Bluetooth communication module;

[0014] The fourth communication link between the main controller and the Bluetooth communication module passes through the Bluetooth communication module and the main controller in sequence. The fourth communication link carries the vehicle key control command forwarded by the Bluetooth communication module. The second communication link carries the key control signal corresponding to the vehicle key control command issued by the main controller.

[0015] In one embodiment, the car digital key terminal device further includes:

[0016] On-board diagnostic system interface module;

[0017] The fifth communication link between the main controller and the on-board diagnostic system interface module passes through the on-board diagnostic system interface module and the main controller in sequence, and carries the vehicle data read by the on-board diagnostic system interface module.

[0018] In one embodiment, the car digital key terminal device further includes:

[0019] Wide area network communication module;

[0020] There is a sixth communication link between the main controller and the wide area network communication module. The sixth communication link passes through the main controller, the wide area network communication module and the cloud server in sequence, and carries the vehicle data.

[0021] To achieve the above objectives, this application proposes a vehicle remote control system, which includes:

[0022] As mentioned above, the car digital key terminal device and user terminal device;

[0023] A seventh communication link exists between the vehicle digital key terminal device and the user terminal device. The seventh communication link passes sequentially through the user terminal device, the cloud server, and the vehicle digital key terminal device. The seventh communication link carries vehicle key control commands issued by the user terminal device.

[0024] In one embodiment, an eighth communication link exists between the vehicle digital key terminal device and the user terminal device. The eighth communication link passes sequentially through the user terminal device and the vehicle digital key terminal device, and carries vehicle key control commands issued by the user terminal device.

[0025] In one embodiment, the seventh or eighth communication link also carries a vehicle data reading instruction sent by the user terminal device to the cloud server.

[0026] In one embodiment, the seventh communication link also carries vehicle model information sent from the user terminal device to the cloud server, and vehicle model protocol parameters predefined by the original car key corresponding to the vehicle model information sent from the cloud server to the car digital key terminal device.

[0027] One or more technical solutions proposed in this application have at least the following technical effects:

[0028] In this application, the automotive digital key terminal device consists of a main controller and an RF transceiver module, with a bidirectional communication link between them. The first communication link, sequentially connecting the RF transceiver module and the main controller, carries the RF signal characteristics of the vehicle's original key received by the RF transceiver module. The main controller configures the communication parameters of the RF transceiver module based on these RF signal characteristics. The RF transceiver module, based on these communication parameters, simulates the vehicle's original key, and the second communication link, sequentially connecting the main controller and the RF transceiver module, carries the key control signals issued by the main controller. This allows the RF transceiver module to simulate the functions of the vehicle's original remote key, enabling functions such as locking, unlocking, and starting the vehicle, without requiring a physical key to be embedded in the vehicle. Ultimately, this improves the vehicle model compatibility and security of the automotive digital key terminal device. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this utility model or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this utility model. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0030] Figure 1 A first structural schematic diagram of an embodiment of the car digital key terminal device provided by this utility model;

[0031] Figure 2 A second structural schematic diagram of an embodiment of the car digital key terminal device provided by this utility model;

[0032] Figure 3 A third structural schematic diagram of an embodiment of the car digital key terminal device provided by this utility model;

[0033] Figure 4 A fourth structural schematic diagram of an embodiment of the car digital key terminal device provided by this utility model;

[0034] Figure 5 A fifth structural schematic diagram of an embodiment of the car digital key terminal device provided by this utility model;

[0035] Figure 6 A first structural schematic diagram of an embodiment of the vehicle remote control system provided by this utility model;

[0036] Figure 7 A second structural schematic diagram of an embodiment of the vehicle remote control system provided by this utility model.

[0037] Explanation of icon numbers:

[0038] 10. Main controller; 20. RF transceiver module; 30. Wide area network communication module; 40. Cloud server; 50. Bluetooth communication module; 60. Vehicle diagnostic system interface module; 70. User terminal equipment; 80. Car digital key terminal equipment.

[0039] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0040] The technical solutions of the present utility model will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present utility model, and not all embodiments. Based on the embodiments of the present utility model, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present utility model.

[0041] It should be noted that if the embodiments of this utility model involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a specific posture. If the specific posture changes, the directional indicators will also change accordingly.

[0042] Furthermore, if the embodiments of this utility model involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the use of "and / or" or "and / or" throughout the text includes three parallel solutions. For example, "A and / or B" includes solution A, solution B, or a solution where both A and B are satisfied simultaneously. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed by this utility model.

[0043] This utility model proposes a car digital key terminal device 80.

[0044] In one embodiment of this utility model, the car digital key terminal device 80 includes:

[0045] Main controller 10 and RF transceiver module 20;

[0046] There is a bidirectional communication link between the main controller 10 and the radio frequency transceiver module 20. The bidirectional communication link includes a first communication link and a second communication link. The first communication link passes through the radio frequency transceiver module 20 and the main controller 10 in sequence, and the second communication link passes through the main controller 10 and the radio frequency transceiver module 20 in sequence. The first communication link carries the radio frequency signal characteristics of the vehicle's original car key received by the radio frequency transceiver module 20. The main controller 10 configures the communication parameters of the radio frequency transceiver module 20 according to the radio frequency signal characteristics of the vehicle's original car key. The radio frequency transceiver module 20 simulates the vehicle's original car key based on the communication parameters. The second communication link carries the key control signal sent by the main controller 10.

[0047] The digital key terminal (In-Vehicle Device) is fixedly installed inside the vehicle, usually near the OBD (On-Board Diagnostics) interface or in a concealed location.

[0048] Please see Figure 1The main controller 10, as the main control unit (MCU), is the core processor of the car digital key terminal device 80, responsible for overall logic control, data processing, protocol conversion, and communication scheduling. A high-performance, low-power ARM Cortex-M series microcontroller can be selected. For the RF transceiver module 20, a configurable 433MHz RF module can be used, integrated into the car digital key terminal device 80 at the factory. Transceiver chips that support FSK / OOK modulation, have adjustable data rates, and whose parameters can be dynamically configured by the main control unit (MCU) via SPI / I2C / UART interfaces can be selected, such as the Semtech SX127x series, Silicon Labs Si446x series, or their integrated solutions.

[0049] The software of the RF transceiver module 20 is definable; its key parameters, such as transmit / receive frequency, modulation method, encoding protocol, and data packet structure, can be dynamically and independently configured and updated via the main control unit (MCU). The RF transceiver module 20 has a protocol library; that is, the automotive digital key terminal device 80 firmware or cloud storage contains a remote control key protocol library covering mainstream automotive brands and models.

[0050] It can learn the key control signal of the original car key. In one embodiment, in the learning mode, when the user triggers a specific function of the original car key (such as unlocking), the radio frequency transceiver module 20 of the car digital key terminal device 80 captures the radio frequency signal. The main control unit (MCU) analyzes the characteristics of the radio frequency signal (such as frequency, encoding, rolling code algorithm, etc.) and learns or matches it to the corresponding protocol library item or generates new communication parameters. In this way, the communication parameters of the radio frequency transceiver module 20 are configured, and the main controller 10 can directly send the key control signal to the radio frequency transceiver module 20, which can simulate the key control signal.

[0051] In one embodiment, the car digital key terminal device 80 further includes:

[0052] 30 wide area network communication modules;

[0053] There is a third communication link between the main controller 10 and the wide area network communication module 30. The third communication link passes through the cloud server 40, the wide area network communication module 30 and the main controller 10 in sequence. The third communication link carries the vehicle model protocol parameters predefined by the original vehicle key issued by the cloud server 40. The main controller 10 configures the communication parameters of the radio frequency transceiver module 20 according to the vehicle model protocol parameters.

[0054] Please see Figure 2 The wide area network communication module 30 provides wide area network connectivity for remote data interaction with the cloud server 40 (such as receiving control commands and reporting vehicle status / OBD data). It can be a 4G module, specifically an LTE module that supports Cat 1 or Cat 4.

[0055] The radio frequency transceiver module 20 can also be configured with the key control signal of the original car key. In one embodiment, in the configuration mode, the cloud server 40 issues the configuration, that is, according to the vehicle VIN or model information, the configuration parameters of the 433MHz radio frequency protocol corresponding to the model are obtained from the cloud server 40 and downloaded to the car digital key terminal device 80 to configure the 433MHz radio frequency transceiver module 20.

[0056] In one embodiment, the third communication link also carries the vehicle key control command issued by the cloud server 40, and the second communication link carries the key control signal corresponding to the vehicle key control command issued by the main controller 10.

[0057] For cloud server 40, it can: 1. Receive and process vehicle status / OBD data from car digital key terminal device 80; 2. Receive control requests from terminal applications of user terminal device 70, verify permissions, and forward them to the target vehicle; 3. Manage user accounts, vehicle binding relationships, and key permissions (such as creating, distributing, modifying, revoking, and setting vehicle rental and sharing time limits); 4. Store and distribute 433MHz radio frequency protocol configuration parameter library; 5. Provide a management backend for rental companies to manage their fleet and view reports, etc.

[0058] In one embodiment, the car digital key terminal device 80 further includes:

[0059] Bluetooth communication module 50;

[0060] A fourth communication link exists between the main controller 10 and the Bluetooth communication module 50. This fourth communication link passes sequentially through the Bluetooth communication module 50 and the main controller 10. The fourth communication link carries the vehicle key control command forwarded by the Bluetooth communication module 50. The second communication link carries the key control signal corresponding to the vehicle key control command issued by the main controller 10.

[0061] Please see Figure 3 The Bluetooth communication module 50 provides near-field communication capabilities with the user terminal device 70's terminal application for short-range control in network-free environments (such as contactless unlocking and starting), and for rapid pairing between the user terminal device 70 and the car digital key terminal device 80. A Bluetooth communication module 50 supporting BLE 5.0+ can be selected. In this embodiment, the vehicle key control commands from the user terminal device 70 can be forwarded to the main controller 10 via the Bluetooth communication module 50.

[0062] In one embodiment, the car digital key terminal device 80 further includes:

[0063] On-board diagnostic system interface module 60;

[0064] The fifth communication link between the main controller 10 and the on-board diagnostic system interface module 60 passes through the on-board diagnostic system interface module 60 and the main controller 10 in sequence. The fifth communication link carries the vehicle data read by the on-board diagnostic system interface module 60.

[0065] Please see Figure 4 It can read standard OBD-II PID data (such as vehicle speed, RPM, fuel level, mileage, and fault codes) and private data from the body control module (such as door and window status, light status, and tire pressure information) via a physical connection to the vehicle's OBD-II diagnostic interface. A standard OBD-II 16-pin interface connector with built-in necessary level conversion and protection circuitry can be used. Additionally, it can connect to the vehicle control interface; for certain vehicle models / functions that cannot be fully controlled via OBD or 433MHz radio frequency, access can be achieved through additional hardwired connections such as the CAN bus. Furthermore, it can draw power from the vehicle's OBD interface or constant power via a power management unit to provide stable power and manage power consumption (e.g., sleep / wake-up mechanisms).

[0066] In one embodiment, the car digital key terminal device 80 further includes:

[0067] 30 wide area network communication modules;

[0068] There is a sixth communication link between the main controller 10 and the wide area network communication module 30. The sixth communication link passes through the main controller 10, the wide area network communication module 30 and the cloud server 40 in sequence. The sixth communication link carries vehicle data.

[0069] Please see Figure 5 After the vehicle data is read through the on-board diagnostic system interface module 60, it can be uploaded to the cloud server 40 through the wide area network communication module 30, and then the cloud server 40 forwards the vehicle data to the user terminal device 70.

[0070] This utility model proposes a vehicle remote control system.

[0071] In one embodiment of this utility model, the vehicle remote control system includes:

[0072] As described above, the car digital key terminal device 80 and the user terminal device 70;

[0073] A seventh communication link exists between the car digital key terminal device 80 and the user terminal device 70. The seventh communication link passes through the user terminal device 70, the cloud server 40 and the car digital key terminal device 80 in sequence. The seventh communication link carries the vehicle key control commands issued by the user terminal device 70.

[0074] In one embodiment, an eighth communication link exists between the vehicle digital key terminal device 80 and the user terminal device 70. The eighth communication link passes through the user terminal device 70 and the vehicle digital key terminal device 80 in sequence, and carries the vehicle key control command issued by the user terminal device 70.

[0075] In one embodiment, the seventh or eighth communication link also carries a vehicle data reading instruction sent by the user terminal device 70 to the cloud server 40.

[0076] Please see Figure 6 When operations such as locking, unlocking, or starting the engine are required, users can remotely control the vehicle (lock / unlock, start / stop, locate the vehicle, etc.) from anywhere in the world with cellular network coverage via the terminal application of the user terminal device 70, such as a mobile APP. They can also view vehicle data such as real-time status / OBD data, thus meeting the needs of car owners and rental scenarios for remote vehicle return, remote authorization, and vehicle status monitoring. In one embodiment, the data flow is as follows: User APP command from user terminal device 70 -> Cloud server 40 -> Car digital key terminal device 80 (4G receiver) -> Main controller 10 (MCU) -> Radio frequency transceiver module 20, i.e., the configured 433MHz module transmits the corresponding RF signal -> The vehicle receives the signal as if it were the original car key -> Performs the corresponding operation.

[0077] Please see Figure 7 Correspondingly, users can also perform near-field control via Bluetooth. When a user approaches the vehicle, the terminal application of the user terminal device 70, such as a mobile APP, automatically connects to the car digital key terminal device 80 via BLE, enabling convenient operations such as unlocking the car door without contact and starting the engine with one button, providing an experience close to the original digital key. In one embodiment, the data flow is as follows: user approaches the vehicle -> user APP of user terminal device 70 connects to car digital key terminal device 80 via BLE -> APP sends command -> car digital key terminal device 80 (Bluetooth reception) -> main controller 10 (MCU) -> RF transceiver module 20, i.e., the configured 433MHz module transmits the corresponding RF signal -> vehicle executes the operation.

[0078] For user mobile apps, they are installed on user terminal devices 70 such as smartphones, providing a user interface for remote control (such as 4G), local control (such as Bluetooth), viewing vehicle status / OBD data, managing key permissions, etc.

[0079] Therefore, dual-mode control based on cloud server 40 and Bluetooth near-field communication is provided.

[0080] Vehicle data can be read by the on-board diagnostic system interface module 60. This means the car digital key terminal device 80 continuously or on-demand reads vehicle data through the on-board diagnostic system interface module 60 (e.g., OBD-II interface). The read vehicle data is then uploaded to the cloud server 40 via the wide area network communication module 30 (e.g., a 4G module). On the user terminal device 70, applications such as a mobile app can display information including vehicle location, remaining fuel / battery charge, total mileage, remaining driving range, door and window status (if supported), and fault alarm information. The rental company's backend can view comprehensive fleet information, including the above data, as well as driving behavior analysis (e.g., rapid acceleration / braking), vehicle health status, usage records, and electronic fence alarms, greatly improving management efficiency.

[0081] Physical keys currently present security risks: Since the physical key is embedded inside the vehicle, if the vehicle is illegally entered (e.g., by smashing a window), the attacker could easily find and use the key to start the vehicle. Furthermore, maintenance is difficult: the key box requires power (potentially consuming the vehicle battery), and repairs require disassembly, resulting in high costs and low efficiency.

[0082] In this embodiment, keyless entry is achieved: since the radio frequency transceiver module 20 of the car digital key terminal device 80 is independently configured to accurately simulate the RF signal of the original car key, there is absolutely no need to disassemble and bury any of the original car's physical keys inside the vehicle. All original physical keys of the vehicle can be safely kept by the owner or rental company in a place far away from the vehicle (such as a safe). With no physical keys present inside the vehicle, even if an attacker physically enters the vehicle, they will not be able to find the original physical key used to start the vehicle (because it is not inside the vehicle), greatly improving anti-theft security.

[0083] In one embodiment, the seventh communication link also carries vehicle model information sent from user terminal device 70 to cloud server 40, and vehicle model information sent from cloud server 40 to car digital key terminal device 80, corresponding to the vehicle model information and the vehicle model predefined vehicle model protocol parameters of the original car key.

[0084] In this embodiment, a method is provided to initiate a vehicle model adaptation process to eliminate vehicle model restrictions.

[0085] Method A (Learning Mode): The user terminal device 70's terminal application, such as a mobile app, prompts the user to press the "unlock" button on the original car key. The RF transceiver module 20 of the car digital key terminal device 80 captures this RF signal. The main controller 10 (MCU) analyzes this RF signal, automatically matches the protocol library or learns characteristic parameters, and independently configures the RF transceiver module 20 to simulate the same RF signal as the original car key's "unlock" function. This process is repeated to learn button signals such as "lock car" and "start engine" (if needed).

[0086] Method B (Cloud Configuration): The user terminal device 70's terminal application, such as a mobile APP, guides the user to enter the VIN or select the vehicle model. The cloud server 40 finds the corresponding configuration parameters of the RF transceiver module 20 based on the vehicle model information and sends them to the car digital key terminal device 80. The main controller 10 (MCU) receives the parameters and independently configures the RF transceiver module 20.

[0087] Once configured, the radio frequency transceiver module 20 of the car digital key terminal device 80 is programmed to simulate the original remote key of that specific vehicle.

[0088] This application incorporates a highly flexible, independently configurable radio frequency transceiver module 20 into the automotive digital key terminal device 80. Combined with 4G communication, Bluetooth communication, and OBD-II interface technology, it constructs a complete keyless digital key system. This system is widely compatible with various vehicle models, completely eliminates the need for burying the original vehicle's physical key, supports remote (4G) and local (Bluetooth) dual-mode control, and can read vehicle OBD data. It specifically addresses the core pain points of the car rental market in vehicle management, user authorization, and security / anti-theft.

[0089] In one application scenario of this application, 1. Software process example (learning mode adaptation) is as follows: The user installs the IVD into the vehicle's OBD port, and the mobile APP and IVD are paired and connected via BLE. In the APP, select "Add Vehicle" -> "Learning Mode". The APP prompts "Please press the unlock button on the original car key". The user presses the unlock button on the original car key. The configurable 433MHz module of the IVD captures the RF signal, and the MCU records the signal characteristics (center frequency, bandwidth, modulation method, data rate, encoding rules, rolling code counter position, etc.). The MCU matches the captured signal characteristics with the local / cloud protocol library. If the match is successful, the 433MHz module is configured using the protocol parameters. If it is a new protocol, the characteristics are analyzed and stored, configuration parameters are generated to configure the 433MHz module, and optional upload to the cloud. The APP prompts that learning is successful (unlock function). Repeat steps 3-6 to learn the "lock car", "start" and other function keys. After learning is complete, the user can remove the original car key. Test the execution of the corresponding functions through the IVD (APP control). 2. Implementation in the rental scenario is as follows: The rental company installs the IVD in batches on the fleet vehicles and completes the adaptation configuration. Vehicle information is entered into the cloud platform and linked to the IVD (In-Vehicle Diagnostics Device). When a renter places an order, the administrator creates an "electronic key" permission for the rental period on the platform and associates it with the renter's mobile phone number / APP account. The renter receives the key permission through their mobile APP and can remotely / locally control the vehicle and check its status during the rental period. At the end of the rental period, the administrator can revoke the key permission with one click on the cloud. The platform provides functions such as vehicle location monitoring, OBD data reports (fuel consumption, mileage), and electronic fence alarms.

[0090] The above description is merely an exemplary embodiment of the present utility model and does not limit the patent scope of the present utility model. Any equivalent structural transformations made based on the technical concept of the present utility model and the contents of the present utility model specification and drawings, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present utility model.

Claims

1. An automotive digital key terminal device, characterized by, The vehicle digital key terminal device includes: Main controller and RF transceiver module; There is a bidirectional communication link between the main controller and the radio frequency transceiver module. The bidirectional communication link includes a first communication link and a second communication link. The first communication link passes through the radio frequency transceiver module and the main controller in sequence, and the second communication link passes through the main controller and the radio frequency transceiver module in sequence. The first communication link carries the radio frequency signal characteristics of the vehicle's original car key received by the radio frequency transceiver module. The main controller configures the communication parameters of the radio frequency transceiver module according to the radio frequency signal characteristics of the vehicle's original car key. The radio frequency transceiver module simulates the vehicle's original car key based on the communication parameters. The second communication link carries the key control signal sent by the main controller.

2. The automotive digital key terminal device as described in claim 1, characterized in that, The car digital key terminal device also includes: Wide area network communication module; There is a third communication link between the main controller and the wide area network communication module. The third communication link passes through the cloud server, the wide area network communication module and the main controller in sequence. The third communication link carries the vehicle model protocol parameters predefined by the original vehicle key issued by the cloud server. The main controller configures the communication parameters of the radio frequency transceiver module according to the vehicle model protocol parameters.

3. The automotive digital key terminal device as described in claim 2, characterized in that, The third communication link also carries the vehicle key control command issued by the cloud server, and the second communication link carries the key control signal corresponding to the vehicle key control command issued by the main controller.

4. The automotive digital key terminal device as described in claim 1, characterized in that, The car digital key terminal device also includes: Bluetooth communication module; The fourth communication link between the main controller and the Bluetooth communication module passes through the Bluetooth communication module and the main controller in sequence. The fourth communication link carries the vehicle key control command forwarded by the Bluetooth communication module. The second communication link carries the key control signal corresponding to the vehicle key control command issued by the main controller.

5. The automotive digital key terminal device as described in claim 1, characterized in that, The car digital key terminal device also includes: On-board diagnostic system interface module; The fifth communication link between the main controller and the on-board diagnostic system interface module passes through the on-board diagnostic system interface module and the main controller in sequence, and carries the vehicle data read by the on-board diagnostic system interface module.

6. The automotive digital key terminal device as described in claim 5, characterized in that, The car digital key terminal device also includes: Wide area network communication module; There is a sixth communication link between the main controller and the wide area network communication module. The sixth communication link passes through the main controller, the wide area network communication module and the cloud server in sequence, and carries the vehicle data.

7. A vehicle remote control system, characterized in that, The vehicle remote control system includes: The vehicle digital key terminal device and user terminal device as described in any one of claims 1 to 6; A seventh communication link exists between the vehicle digital key terminal device and the user terminal device. The seventh communication link passes sequentially through the user terminal device, the cloud server, and the vehicle digital key terminal device. The seventh communication link carries vehicle key control commands issued by the user terminal device.

8. The vehicle remote control system as described in claim 7, characterized in that, An eighth communication link exists between the vehicle digital key terminal device and the user terminal device. The eighth communication link passes sequentially through the user terminal device and the vehicle digital key terminal device, and carries vehicle key control commands issued by the user terminal device.

9. The vehicle remote control system as described in claim 8, characterized in that, The seventh or eighth communication link also carries a vehicle data reading command sent from the user terminal device to the cloud server.

10. The vehicle remote control system as described in claim 7, characterized in that, The seventh communication link also carries vehicle model information sent from the user terminal device to the cloud server, and vehicle model protocol parameters predefined by the original car key corresponding to the vehicle model information sent from the cloud server to the car digital key terminal device.

Images