Method and system for synchronizing data between digital car key servers based on event driving

Abstract

The invention provides an event-driven data synchronization method and system between digital vehicle key servers, and belongs to the technical field of vehicle digital vehicle keys, and the method comprises the steps: obtaining a key state change event notification packet sent by an equipment server; updating a key state database according to the key state change event notification packet; the key status is synchronized to the device server. Through the event-driven architecture, the efficient data format and the dynamic synchronization strategy, the data synchronization efficiency and reliability between the digital vehicle key servers are remarkably improved, the problems of high delay, resource waste and inaccurate event processing in the prior art are solved, and the method is suitable for a digital key system of an intelligent networked vehicle and has a wide application prospect. Wide application prospects and commercial values are realized.

Description

Technical Field

[0001] This invention relates to the field of vehicle digital key technology, and in particular to a method and system for data synchronization between digital key servers based on event-driven principles. Background Technology

[0002] In existing digital car key systems, data synchronization between servers typically uses a polling mechanism or a timed synchronization method, which leads to the following problems:

[0003] High synchronization latency: Timed polling cannot capture key status changes in real time, and notifications for critical events (such as key freezing and recovery) have a delay of more than 500ms, which affects user experience and security.

[0004] Resource waste: The polling mechanism leads to a large amount of invalid communication between servers. According to statistics, about 30% of the communication traffic in the traditional solution is redundant polling data.

[0005] Inaccurate event handling: The lack of an efficient event-driven mechanism makes it impossible to accurately monitor and respond to key nodes in the key lifecycle (activation, revocation, migration). Summary of the Invention

[0006] This invention aims to solve at least one of the above-mentioned problems in the prior art, and proposes an event-driven data synchronization method and system between digital car key servers, focusing particularly on the innovative design of key status synchronization (SyncKeyInfo) and event notification (NotifyKeyEvent) mechanisms. Through a precise event triggering mechanism and an efficient communication protocol, it achieves real-time synchronization of key status and reliable event notification.

[0007] In a first aspect, embodiments of the present invention provide an event-driven method for data synchronization between digital car key servers, comprising:

[0008] Receive the key status change event notification packet sent by the device server;

[0009] Update the key status database based on the key status change event notification package;

[0010] Synchronize the key status with the device server.

[0011] In a preferred embodiment, the steps of obtaining the key status change event notification packet sent by the device server, updating the key status database according to the key status change event notification packet, and synchronizing the key status with the device server are as follows:

[0012] The key status change event notification package includes at least a key ID field and an event type field;

[0013] Parse the event type in the key status change event notification packet;

[0014] Update the key status database if the event type is "key frozen" or "key deleted";

[0015] Synchronize the key status with the device server.

[0016] In a preferred embodiment, the key status change event notification package further includes a certificate signature field.

[0017] In a preferred embodiment, the steps of obtaining the key status change event notification packet sent by the device server, updating the key status database according to the key status change event notification packet, and synchronizing the key status with the device server are as follows:

[0018] The data transmission adopts the TLV data encoding format, and the key fields in the key status change event notification packet use fixed tags.

[0019] In a preferred embodiment, the step of synchronizing the key status with the device server employs an incremental synchronization algorithm, transmitting only changed data.

[0020] In a preferred embodiment, it further includes:

[0021] Obtain the MQTT topic, the MQTT topic message body includes: key ID, vehicle ID and certificate signature fields, the MQTT topic is published by the device server after the vehicle completes its first standard transaction event;

[0022] Verify the certificate signature field, parse the vehicle ID, and update the key status of the vehicle controller corresponding to the vehicle ID to activated;

[0023] The device server is asynchronously returned a key status indicating that the key is active. Multiple key status changes are transmitted at once using a batch synchronization method.

[0024] In a second aspect, embodiments of the present invention provide an event-driven data synchronization system between digital car key servers, the system being capable of implementing any of the methods described in the first aspect, the system comprising:

[0025] The acquisition module is used to acquire key status change event notification packets sent by the device server;

[0026] The update module is used to update the key status database based on key status change event notification packets;

[0027] The output module is used to synchronize the key status with the device server.

[0028] Thirdly, embodiments of the present invention provide an event-driven digital car key server-to-server data synchronization device, the device comprising: a device server, a vehicle server, a terminal device, and a vehicle controller;

[0029] The vehicle server includes: an acquisition module, an update module, and an output module; the acquisition module is used to acquire key status change event notification packets sent by the device server; the update module is used to update the key status database according to the key status change event notification packets; and the output module is used to synchronize the key status with the device server.

[0030] The device server is equipped with an event listening module to listen for key status change notifications sent by terminal devices; the device server also implements event-driven asynchronous communication through an HTTPS bidirectional SSL channel.

[0031] The terminal device includes a digital key frame and a security unit, used to capture key status changes and generate key status change notifications;

[0032] The vehicle controller interacts with the vehicle server in real time to verify the validity of the key status and supports event-based seamless entry and engine start functions.

[0033] Fourthly, embodiments of the present invention provide an electronic device, comprising:

[0034] One or more processors;

[0035] Memory, used to store one or more programs;

[0036] When the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described in the first aspect.

[0037] Fifthly, embodiments of the present invention provide a computer-readable medium storing a computer program that, when executed by a processor, implements the steps of any of the methods described in the first aspect.

[0038] Beneficial effects of this invention:

[0039] This invention significantly improves the data synchronization efficiency and reliability between digital car key servers through an event-driven architecture, efficient data format, and dynamic synchronization strategy. It solves the problems of high latency, resource waste, and inaccurate event processing in existing technologies, and is suitable for digital key systems for intelligent connected vehicles, with broad application prospects and commercial value. Attached Figure Description

[0040] Figure 1This is a schematic diagram of a data synchronization method between digital car key servers based on event-driven principles, provided in an embodiment of the present invention.

[0041] Figure 2 This is a schematic diagram of the data synchronization architecture between digital car key servers provided in an embodiment of the present invention.

[0042] Figure 3 This is a schematic diagram of the event notification proof format provided in an embodiment of the present invention.

[0043] Figure 4 The key state synchronization timing diagram provided for embodiments of the present invention.

[0044] Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0045] To enable those skilled in the art to better understand the technical solutions of the present invention, exemplary embodiments of the present invention are described below in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0046] Where there is no conflict, the various embodiments of the present invention and the features thereof may be combined with each other.

[0047] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.

[0048] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of the stated feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded. Terms such as “connected” or “linked” are not limited to physical or mechanical connections but can include electrical connections, whether direct or indirect.

[0049] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art and the invention, and will not be interpreted as having an idealized or overly formal meaning unless expressly so defined herein.

[0050] In the technical solution of this invention, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information all comply with relevant laws and regulations and do not violate public order and good morals. The use of user data in this technical solution follows relevant national laws and regulations (e.g., the "Information Security Technology - Personal Information Security Specification"). For example: appropriate measures are taken for personal information access control; restrictions are imposed on the display of personal information; the purpose of using personal information does not exceed the scope of direct or reasonable association; and explicit identity targeting is eliminated when using personal information to avoid precisely locating a specific individual.

[0051] List of abbreviations in this invention:

[0052]

[0053] Key terms defined in this invention:

[0054]

[0055] Figure 1 This is a flowchart illustrating an event-driven data synchronization method between digital car key servers, provided by an embodiment of the present invention; as shown below. Figure 1 As shown, the method includes:

[0056] Receive the key status change event notification packet sent by the device server;

[0057] Update the key status database based on the key status change event notification package;

[0058] Synchronize the key status with the device server.

[0059] This method can be used for Figure 2 The data synchronization architecture between digital car key servers is shown below. For example... Figure 2As shown, the device server manages the key lifecycle of the terminal device, deploys the SyncKeyInfo and NotifyKeyEvent interfaces, and interacts with the terminal device through the Digital Key Framework (DKF); the vehicle server manages the key status of the vehicle, communicates directly with the vehicle controller, and stores key certificates and permission information; the terminal device contains the Digital Key Framework (DKF) and Security Element (SE / TEE), communicates with the vehicle via Bluetooth / NFC, and triggers key status change events; the communication interface uses an HTTPS bidirectional SSL encrypted channel to ensure secure data transmission, and the interface conforms to the RESTful specification, supporting event-driven asynchronous communication.

[0060] In some embodiments, the steps of obtaining the key status change event notification packet sent by the device server, updating the key status database according to the key status change event notification packet, and synchronizing the key status with the device server are as follows:

[0061] The key status change event notification package includes at least a key ID (keyID) field and an event type (eventType) field;

[0062] Parse the event type in the key status change event notification packet;

[0063] Update the key status database if the event type is "key frozen (TERMINATED)" or "key deleted (SUSPENDED)".

[0064] Synchronize the key status with the device server;

[0065] The system introduces an event priority queue, setting emergency events such as "key deleted" and "key frozen" to the highest priority, ensuring that notifications are completed within 100ms, which improves response speed by 60% compared to the traditional polling solution.

[0066] In some embodiments, the key status change event notification package further includes a certificate signature field (dkAttestation) to ensure the integrity and non-repudiation of the event notification, achieving a key status synchronization accuracy of 99.99%.

[0067] In some embodiments, the steps of obtaining the key status change event notification packet sent by the device server, updating the key status database according to the key status change event notification packet, and synchronizing the key status with the device server are as follows:

[0068] The data transmission adopts the TLV data encoding format. The key fields (such as keyID and eventType) in the key status change event notification packet use fixed tags (such as 0x89 for keyID and 0x5E for eventType), which improves parsing efficiency by 30% and reduces server parsing time.

[0069] In some embodiments, the step of synchronizing the key status with the device server is as follows: an incremental synchronization algorithm is used to transmit only the changed data, thereby reducing the amount of data transmitted.

[0070] In some embodiments, such as Figure 3 As shown, the key status change event notification packet adopts the event notification proof format and is encoded using the TLV data encoding format. 0x75 is the root tag, which includes the event type tag (0x5E), the key ID tag (0x89), the business ID tag (0xB0), and the certificate signature tag (0xC0).

[0071] In some embodiments, it also includes:

[0072] Obtain the MQTT topic, the MQTT topic message body includes: key ID (keyID), vehicle ID (vehicleID) and certificate signature field (dkAttestation), the MQTT topic is published by the device server after the vehicle completes its first standard transaction event;

[0073] Verify the certificate signature field, parse the vehicle ID, and update the key status of the vehicle controller corresponding to the vehicle ID to activated, allowing for subsequent quick transactions;

[0074] The device server asynchronously returns the key status as active, using a batch synchronization method to transmit the status changes of multiple keys at once, reducing the number of communications. After receiving the synchronization data, the terminal device updates its local key list and displays the "key activated" status.

[0075] Figure 4 The key state synchronization timing diagram provided for embodiments of the present invention; in some embodiments, such as Figure 4 As shown, the key status synchronization steps include:

[0076] When a terminal device triggers a state change, the device server generates an event notification packet (containing a dkAttestation signature).

[0077] After receiving the request, the vehicle server updates the database and returns the latest status via SyncKeyInfo using the HTTPSPOST method. The request body contains data such as KeyAccessProfile.

[0078] Before a transaction, the vehicle controller queries the vehicle server to ensure that the key status is valid in real time.

[0079] In some embodiments, the WebSocket-based real-time event push step includes:

[0080] Event release (terminal device):

[0081] 1. When a user revokes a friend key in the Native App, the terminal device's DKF generates a deletion request, calls the device server's manageKey interface, and triggers the event listening module;

[0082] 2. The device server generates an event notification packet:

[0083] json

[0084] {

[0085] "keyId": "DKID00000000",

[0086] "eventType": "TERMINATED",

[0087] "dkAttestation": "64 bytes of signature data"

[0088] }

[0089] Event transmission (between servers):

[0090] 1. Send a NotifyKeyEvent request via a WebSocket long connection. The HTTP header includes parameters such as X-ICCOA-Request-ID and timestamp, and the request body is TLV-encoded data.

[0091] 2. After receiving the event, the vehicle server verifies dkAttestation (using the device server authentication certificate G). If successful, it performs the key deletion operation.

[0092] Status synchronization (vehicle server):

[0093] 1. After the vehicle server deletes the local friend key record, it synchronizes the latest status with the device server via the SyncKeyInfo interface:

[0094] json

[0095] {

[0096] "keyId": "DKID00000000",

[0097] "keyStatus": "5:TERMINATED",

[0098] "sharedKeys": []

[0099] };

[0100] 2. The device server updates the key list of the terminal device and notifies the user that the revocation was successful.

[0101] Key technical parameters description:

[0102] The communication protocol uses WebSocket, supports full-duplex communication, and has an event push latency of < 100ms;

[0103] The encryption algorithm uses ECDHE-RSA-AES256-GCM, and the key exchange security strength reaches 256 bits;

[0104] The event priority is emergency, and the priority of revocation / freeze events is higher than that of normal status changes.

[0105] In some embodiments, the asynchronous event processing steps based on MQTT include:

[0106] Event Release (Terminal Device):

[0107] 1. After the vehicle completes its first standard transaction, the terminal device DKF detects that the key status changes from "2:DELIVERED" to "3:ACTIVATED", triggering the event listening module;

[0108] 2. The device server publishes the event to the MQTT topic "iccoa / key / event / activated", with the message body containing keyID, vehicleID, and dkAttestation.

[0109] Event subscription (vehicle server):

[0110] 1. The vehicle server subscribes to this topic, and upon receiving a message, verifies dkAttestation (using the public key of the device server certificate G) and parses the vehicle ID corresponding to keyID;

[0111] 2. Update the vehicle controller's key status to "activated" to allow for subsequent quick transactions.

[0112] State synchronization (asynchronous processing):

[0113] 1. The vehicle server asynchronously returns the activation status via the SyncKeyInfo interface, using a batch synchronization method to transmit the status changes of multiple keys at once, reducing the number of communications;

[0114] 2. After receiving the synchronization data, the terminal device updates the local key list and displays the "Key activated" status.

[0115] Key technical parameters description:

[0116] Message Queuing MQTT 5.0 supports QoS 2 to guarantee at least one delivery of events;

[0117] The topic structure features hierarchical topics, categorized by event type and vehicle ID, facilitating filtering and subscription.

[0118] The asynchronous strategy enables batch synchronization, aggregating 10 state changes every 50ms to reduce network overhead.

[0119] In some embodiments, the performance test data of the conventional solution and the present invention are compared as follows:

[0120]

[0121] Based on the same inventive concept, embodiments of the present invention also provide an event-driven data synchronization system between digital car key servers. The system is capable of implementing any of the methods described in the above embodiments, and includes:

[0122] The acquisition module is used to acquire key status change event notification packets sent by the device server;

[0123] The update module is used to update the key status database based on key status change event notification packets;

[0124] The output module is used to synchronize the key status with the device server.

[0125] Based on the same inventive concept, embodiments of the present invention also provide an event-driven digital car key server-to-server data synchronization device, the device comprising: a device server, a vehicle server, a terminal device, and a vehicle controller.

[0126] The vehicle server includes: an acquisition module, an update module, and an output module; the acquisition module is used to acquire key status change event notification packets sent by the device server; the update module is used to update the key status database according to the key status change event notification packets; and the output module is used to synchronize the key status with the device server.

[0127] The device server is equipped with an event listening module to listen for key status change notifications sent by terminal devices; the device server also implements event-driven asynchronous communication through an HTTPS bidirectional SSL channel.

[0128] The terminal device includes a digital key frame and a security unit, used to capture key status changes and generate key status change notifications;

[0129] The vehicle controller interacts with the vehicle server in real time to verify the validity of the key status and supports event-based seamless entry and engine start functions.

[0130] Based on the same inventive concept, embodiments of the present invention also provide an electronic device. Figure 5 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Figure 5 As shown, an embodiment of the present invention provides an electronic device including: one or more processors 101, a memory 102, and one or more I / O interfaces 103. The memory 102 stores one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement any of the methods described in the above embodiments; the one or more I / O interfaces 103 are connected between the processor and the memory, configured to enable information interaction between the processor and the memory.

[0131] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read / write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0132] In some embodiments, the processor 101, memory 102, and I / O interface 103 are interconnected via bus 104, and thus connected to other components of the computing device.

[0133] In some embodiments, the one or more processors 101 include a field-programmable gate array.

[0134] Based on the same inventive concept, embodiments of the present invention also provide a computer-readable medium. This computer-readable medium stores a computer program, wherein, when executed by a processor, the program implements the steps of any of the methods described in the above embodiments. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0135] Those skilled in the art will understand that all or some of the steps, systems, and apparatuses disclosed above, and their functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media).

[0136] As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information, such as computer-readable program instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, it is known to those skilled in the art that communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0137] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0138] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing state information from the computer-readable program instructions. This electronic circuitry can execute the computer-readable program instructions to implement various aspects of the invention.

[0139] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0140] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0141] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0142] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0143] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0144] Example embodiments have been disclosed herein, and while specific terminology has been used, it is for illustrative purposes only and should be construed as such, and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A method for data synchronization between digital car key servers based on event-driven principles, characterized in that, include: Receive the key status change event notification packet sent by the device server; Update the key status database based on the key status change event notification package; Synchronize the key status with the device server.

2. The method according to claim 1, characterized in that, In the steps of obtaining the key status change event notification packet sent by the device server, updating the key status database according to the key status change event notification packet, and synchronizing the key status with the device server: The key status change event notification package includes at least a key ID field and an event type field; Parse the event type in the key status change event notification packet; Update the key status database if the event type is "key frozen" or "key deleted"; Synchronize the key status with the device server.

3. The method according to claim 1 or 2, characterized in that, The key status change event notification package also includes a certificate signature field.

4. The method according to claim 1 or 2, characterized in that, In the steps of obtaining the key status change event notification packet sent by the device server, updating the key status database according to the key status change event notification packet, and synchronizing the key status with the device server: The data transmission adopts the TLV data encoding format, and the key fields in the key status change event notification packet use fixed tags.

5. The method according to claim 1 or 2, characterized in that, In the step of synchronizing the key status with the device server, an incremental synchronization algorithm is used, and only changed data is transmitted.

6. The method according to claim 1 or 2, characterized in that, Also includes: Obtain the MQTT topic, the MQTT topic message body includes: key ID, vehicle ID and certificate signature fields, the MQTT topic is published by the device server after the vehicle completes its first standard transaction event; Verify the certificate signature field, parse the vehicle ID, and update the key status of the vehicle controller corresponding to the vehicle ID to activated; The device server is asynchronously returned a key status indicating that the key is active. Multiple key status changes are transmitted at once using a batch synchronization method.

7. An event-driven digital car key server-to-server data synchronization system, characterized in that, The system is capable of implementing the method as described in any one of claims 1 to 6, and the system comprises: The acquisition module is used to acquire key status change event notification packets sent by the device server; The update module is used to update the key status database based on key status change event notification packets; The output module is used to synchronize the key status with the device server.

8. A data synchronization device between digital car key servers based on event-driven principles, characterized in that, The device includes: an equipment server, a vehicle server, a terminal device, and a vehicle controller; The vehicle server includes: an acquisition module, an update module, and an output module; the acquisition module is used to acquire key status change event notification packets sent by the device server; the update module is used to update the key status database according to the key status change event notification packets; and the output module is used to synchronize the key status with the device server. The device server is equipped with an event listening module to listen for key status change notifications sent by terminal devices; the device server also implements event-driven asynchronous communication through an HTTPS bidirectional SSL channel. The terminal device includes a digital key frame and a security unit, used to capture key status changes and generate key status change notifications; The vehicle controller interacts with the vehicle server in real time to verify the validity of the key status and supports event-based seamless entry and engine start functions.

9. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1 to 6.

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

Images