Management system for processing digital car key through APDU instruction set

Abstract

The invention provides a management system for processing a digital car key through an APDU (Application Protocol Data Unit) instruction set, which relates to the technical field of car networking and comprises a key management instruction set module, a security authentication instruction set module and a control interaction instruction set module, wherein the key management instruction set module is used for realizing full-life-cycle management of digital keys, and at least comprises generation, storage and deletion operations; the security authentication instruction set module is used for establishing an encrypted communication channel between the equipment and the vehicle and realizing identity authentication through ECDH key negotiation and ECDSA signature verification; and the control interaction instruction set module is used for realizing vehicle function control and equipment end state feedback. Through layered architecture design, the system comprises three types of core instructions of key management, security authentication and control interaction, and solves the technical problems that an existing vehicle key system is insufficient in instruction universality, low in security authentication efficiency and poor in key management flexibility.

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a management system that processes digital car keys through the APDU instruction set. Background Technology

[0002] With the development of intelligent vehicle technology, digital car keys are gradually replacing traditional physical keys, becoming the core carrier for vehicle unlocking, starting, and function control. Digital car key systems typically rely on short-range communication technology to achieve interaction between the device and the vehicle. Among these, APDU (Application Protocol Data Unit) commands serve as the core carrier for data interaction, and their design rationality directly affects the system's compatibility, security, and efficiency.

[0003] The existing technology has the following drawbacks:

[0004] Insufficient universality of instruction sets: Traditional car key systems mostly use proprietary instruction formats. Digital key devices from different car manufacturers lack a unified instruction standard, making it difficult for cross-brand devices to interoperate. Users need to re-adapt when changing devices or vehicles, resulting in a poor user experience.

[0005] Low security authentication efficiency: The existing secure channel establishment process requires multiple handshake interactions, with typical standard transactions taking more than 300ms. In addition, the static key mechanism has a long key update cycle (usually 72 hours), which poses a risk of key leakage.

[0006] The key management lacks flexibility: the key generation, storage, sharing and revocation processes lack standardized interfaces, making it difficult to support dynamic permission configuration. Setting permissions for friend keys usually takes more than 5 minutes, which cannot meet the needs of rapid sharing.

[0007] Therefore, there is an urgent need for an APDU instruction set processing method for digital car key systems to solve the existing technical problems. Summary of the Invention

[0008] The present invention aims to solve at least one of the technical problems existing in the prior art, and proposes a management system for processing digital car keys through the APDU instruction set.

[0009] This invention provides a management system for processing digital car keys using the APDU instruction set, comprising: a key management instruction set module, a security authentication instruction set module, and a control interaction instruction set module; wherein:

[0010] The key management instruction set module is used to implement the full lifecycle management of digital keys, including at least generation, storage, and deletion operations;

[0011] The security authentication instruction set module is used to establish an encrypted communication channel between the device and the vehicle, and to achieve identity authentication through ECDH key negotiation and ECDSA signature verification.

[0012] The control interaction instruction set module is used to implement vehicle function control and device status feedback.

[0013] Furthermore, the instructions in the key management instruction set module include at least the CREATE DK instruction and the DELETE DK instruction, which are used to generate, store, and delete digital keys.

[0014] Furthermore, the format of the CREATE DK command is CLA600000Lc[CSR data]00, where the CSR data includes the digital key ID and session ID. The CREATE DK command workflow includes:

[0015] The device-side security element (SE) generates a key pair;

[0016] Construct a Certificate Signing Request (CSR) containing KeyID and SessionID;

[0017] The Certificate Signing Request (CSR) is sent to the vehicle server via the APDU command to complete the digital certificate issuance.

[0018] Furthermore, the format of the DELETE DK instruction is CLA6E0000Lc[KeyID]00, and the workflow of the DELETE DK instruction includes:

[0019] The device verifies the user's operation permissions.

[0020] The APDU command is used to notify the device-side security unit (SE) to delete the key pair and associated certificate corresponding to the specified KeyID.

[0021] Synchronously send a key status update notification to the vehicle server.

[0022] Furthermore, the instructions in the security authentication instruction set module include at least the AUTH0 instruction, the AUTH1 instruction, and instructions for establishing a secure channel between the device and the vehicle and for certificate verification.

[0023] Furthermore, the AUTH1 instruction has the format CLA630000Lc[signature data]00, and is used to establish a secure channel. The workflow of the AUTH1 instruction includes:

[0024] The device uses a private key to perform ECDSA-SHA256 signing on the authentication data;

[0025] The signature data is sent to the vehicle via APDU command;

[0026] The vehicle uses the device's public key to verify the signature's legitimacy, and establishes a secure communication link after successful verification.

[0027] Furthermore, the control interaction instruction set module includes CONTROL FLOW and RKE instructions, which are used to trigger the device's UI display and vehicle function control.

[0028] Furthermore, the format of the CONTROL FLOW instruction is CLA61P1P200[status parameter], and the workflow of the CONTROL FLOW instruction includes:

[0029] After successful vehicle-side authentication, a CONTROL FLOW command carrying status parameters is sent to the device.

[0030] The device parses the P1 / P2 parameters and displays the corresponding authentication result UI.

[0031] The vehicle-side synchronously executes vehicle control commands corresponding to the status parameters.

[0032] Furthermore, the instruction sets in the key management instruction set module, security authentication instruction set module, and control interaction instruction set module adopt a unified application protocol data unit (APDU) format framework, which is adapted to NFC and Bluetooth short-range communication scenarios.

[0033] Furthermore, the instruction sets in the key management instruction set module, security authentication instruction set module, and control interaction instruction set module support the ISO-14443 standard and the Bluetooth GATT protocol, enabling seamless switching between NFC and Bluetooth communication scenarios.

[0034] This invention discloses a management system for digital car keys that processes data using the APDU instruction set. Through a layered architecture design, it incorporates three core instruction categories: key management, security authentication, and control interaction. This addresses the technical problems of insufficient instruction universality, low security authentication efficiency, and lack of key management flexibility in existing car key systems. This invention employs an ECDH key negotiation mechanism to construct a dynamic secure channel, unifies the instruction format for NFC and Bluetooth scenarios, achieves cross-brand device compatibility, and optimizes the key lifecycle management process. This significantly improves the security, efficiency, and flexibility of the digital car key system, making it suitable for multi-brand, cross-platform digital car key application scenarios.

[0035] Compared with the prior art, the beneficial effects of the present invention include:

[0036] Efficiency improvements: The standard transaction process has been shortened from 5 steps to 3 steps, and the transaction time has been reduced from 300ms to 240ms, resulting in a 20% improvement in response speed; key generation time has been optimized from 150ms to 80ms, resulting in a 46.7% improvement in efficiency.

[0037] Enhanced security: Employs the ECDSA-SHA256 signature algorithm, which offers 10 times better collision resistance than SHA1 and reduces the risk of key leakage by 60%; effectively resists replay attacks through a nonce and timestamp mechanism;

[0038] Improved compatibility: Cross-brand device compatibility has increased from 30% to 95%, supporting interoperability of digital key devices from different car manufacturers and reducing user costs;

[0039] Enhanced flexibility: Supports full lifecycle management of digital keys, including activation, sharing, freezing, recovery, and revocation, adapting to the differentiated permission requirements of car owner keys and friend keys. Attached Figure Description

[0040] Figure 1 A structural block diagram of a management system for processing digital car keys using the APDU instruction set is provided in an embodiment of the present invention;

[0041] Figure 2 This is a schematic diagram illustrating the working principle of the CREATE DK instruction provided in an embodiment of the present invention;

[0042] Figure 3 This is a schematic diagram illustrating the working principle of the AUTH0 instruction provided in an embodiment of the present invention;

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

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

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

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

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

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

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

[0050] To address at least one of the technical problems existing in the aforementioned related technologies, the present invention provides a management system for processing digital car keys through the APDU instruction set.

[0051] This embodiment discloses a management system for processing digital car keys using the APDU instruction set, such as... Figure 1 It includes: a key management instruction set module, a security authentication instruction set module, and a control interaction instruction set module; wherein:

[0052] The key management instruction set module is used to implement the full lifecycle management of digital keys, including at least generation, storage, and deletion operations;

[0053] In this embodiment, the digital car key comprises three core components: a device side, a vehicle side, and a server side. Each component interacts with the other using the APDU instruction set of this invention.

[0054] The device integrates a digital key framework (DKF), supporting both native apps and vehicle manufacturer apps. It interacts with the security element (SE / TEE) through the APDU command interface, and is responsible for key generation, signature calculation, and command response.

[0055] The vehicle-mounted system includes an NFC card reader, a Bluetooth module, and a DK authentication module. It uses APDU commands to perform security authentication and control command parsing, and executes operations such as unlocking and starting the vehicle.

[0056] The server side includes a device server and a vehicle server, which synchronize key and certificate information via REST API and support cross-platform key lifecycle management.

[0057] In this embodiment, the instructions in the key management instruction set module include at least the CREATE DK instruction and the DELETEDK instruction, which are used to generate, store, and delete digital keys.

[0058] The format of the CREATE DK command is CLA600000Lc[CSR data]00, where the CLA field is 60, identifying the key management function category; Lc is the length of the CSR data; and the CSR data includes the digital key ID (KeyID) and session ID (SessionID), such as... Figure 2 The CREATE DK command workflow includes:

[0059] The device-side security element (SE) generates a key pair;

[0060] Construct a Certificate Signing Request (CSR) containing KeyID and SessionID;

[0061] The Certificate Signing Request (CSR) is sent to the vehicle server via the APDU command to complete the digital certificate issuance.

[0062] Specifically, after the user on the device confirms the activation of the key, the Digital Key Framework (DKF) triggers the SE to generate an EC key pair with a NISTP-256 curve, constructs a CSR containing KeyID and SessionID, and sends it to the vehicle server via this instruction; after verifying the user information, the vehicle server issues an X.509V3 format certificate and returns it to the SE on the device for storage.

[0063] In this embodiment, the format of the DELETE DK command is CLA6E0000Lc[KeyID]00, where CLA is 6E and Lc is the length of the KeyID data; KeyID is used to uniquely identify the digital key to be deleted; the DELETE DK command workflow includes:

[0064] The device verifies the user's operation permissions.

[0065] The APDU command is used to notify the device-side security unit (SE) to delete the key pair and associated certificate corresponding to the specified KeyID.

[0066] Synchronously send a key status update notification to the vehicle server.

[0067] Specifically, after verifying the user's deletion permission, the device notifies the SE to delete the key pair and certificate corresponding to KeyID through this command, and at the same time sends a status update request to the vehicle server, which synchronously updates the key status to deleted.

[0068] The security authentication instruction set module is used to establish an encrypted communication channel between the device and the vehicle, and to achieve identity authentication through ECDH key negotiation and ECDSA signature verification. In this embodiment, the instructions in the security authentication instruction set module include at least the AUTH0 instruction and the AUTH1 instruction, which are used to establish a secure channel between the device and the vehicle and to verify certificates.

[0069] The AUTH1 command has the format CLA630000Lc[signature data]00, where the CLA field is 67, indicating the security authentication function category; P1 is the communication protocol identifier (01 for NFC, 02 for Bluetooth); VehicleID is the unique vehicle identifier; and the vehicle-side public key is a temporary EC public key generated on the vehicle side. Used to establish a secure channel, the AUTH1 command workflow includes:

[0070] The device uses a private key to perform ECDSA-SHA256 signing on the authentication data;

[0071] The signature data is sent to the vehicle via APDU command;

[0072] The vehicle uses the device's public key to verify the signature's legitimacy, and establishes a secure communication link after successful verification.

[0073] Specifically, after the device enters the vehicle's communication range, the vehicle broadcasts a pairing code, which the device parses to obtain the VehicleID. The vehicle generates a temporary EC public key and sends it to the device via this command. Upon receiving the command, the device generates its own temporary EC public key, calculates the shared key based on the ECDH algorithm, and returns the device public key and authentication data.

[0074] The AUTH0 command has the format CLA67P100Lc[VehicleID, Vehicle Public Key]00, where CLA is 67, indicating the security authentication function category; P1 is the communication protocol identifier (01 for NFC, 02 for Bluetooth); VehicleID is the unique vehicle identifier; and the vehicle public key is the temporary EC public key generated by the vehicle; it is used for secure channel initialization, such as... Figure 3 The workflow includes:

[0075] The vehicle broadcasts a pairing code, which is then parsed by the device to obtain the VehicleID.

[0076] The vehicle generates a temporary public key and sends it to the device via APDU command.

[0077] The device generates a temporary public key, generates a shared key based on the ECDH algorithm, and returns the device public key and authentication data.

[0078] Specifically, after the device enters the vehicle's communication range, the vehicle broadcasts a pairing code, which the device parses to obtain the VehicleID. The vehicle generates a temporary EC public key and sends it to the device via this command. Upon receiving the command, the device generates its own temporary EC public key, calculates the shared key based on the ECDH algorithm, and returns the device public key and authentication data.

[0079] The control interaction command set module is used to implement vehicle function control and device status feedback. This module includes the CONTROL FLOW and RKE commands, which are used to trigger the device's UI display and vehicle function control.

[0080] In this embodiment, the format of the CONTROL FLOW command is CLA61P1P200[status parameter], where the CLA field is 61, identifying the control interaction function category; P1 is the function identifier (01 for unlocking, 02 for locking, 03 for starting the engine); P2 is the execution status (00 for success, 01 for failure); the status parameter includes an operation timestamp and a random number; the CONTROL FLOW command workflow includes:

[0081] After successful vehicle-side authentication, a CONTROL FLOW command carrying status parameters is sent to the device.

[0082] The device parses the P1 / P2 parameters and displays the corresponding authentication result UI.

[0083] The vehicle-side synchronously executes vehicle control commands corresponding to the status parameters.

[0084] Specifically, after the vehicle completes security authentication, it generates a CONTROL FLOW command based on the user's operation requirements and sends it to the device. The device parses the P1 / P2 parameters and displays the corresponding UI prompts (such as "Unlock successful"). The vehicle synchronously executes the vehicle function corresponding to P1 and returns the execution result.

[0085] In this embodiment, the RKE command enables remote keyless entry control and supports Bluetooth remote operation;

[0086] Its command format is: CLA62P10000; the CLA field is 62; P1 is the remote control function identifier (01 indicates remote unlocking, 02 indicates remote locking, and 03 indicates remote horn honking).

[0087] RKE command workflow: The device connects to the vehicle via Bluetooth GATT and sends an RKE command; after receiving the command, the vehicle triggers a security verification (such as a random number challenge). If the verification is successful, the corresponding remote control function is executed, and the execution result is returned.

[0088] The management system disclosed in this implementation divides the instruction set into three layers: key management, security authentication, and control interaction. Each layer's modules are deployed independently, improving decoupling. Adding new functions (such as UWB positioning extended instructions) does not affect the existing layers, thus reducing maintenance costs.

[0089] In this embodiment, the instruction sets in the key management instruction set module, security authentication instruction set module, and control interaction instruction set module adopt a unified application protocol data unit (APDU) format framework, which is suitable for NFC and Bluetooth short-range communication scenarios.

[0090] In this embodiment, the instruction sets in the key management instruction set module, security authentication instruction set module, and control interaction instruction set module support the ISO-14443 standard and the Bluetooth GATT protocol, enabling seamless switching between NFC and Bluetooth communication scenarios.

[0091] This embodiment implements ECDH key negotiation based on AUTH0 / AUTH1 commands. The key update cycle is configurable (default 24 hours), which improves security by 3 times compared to traditional static key schemes and effectively resists the risk of key leakage.

[0092] This embodiment unifies the instruction format for NFC (ISO-14443 standard) and Bluetooth (GATT protocol) scenarios, distinguishes communication protocols through the P1 parameter, supports seamless switching between the two communication methods, and achieves cross-brand device compatibility of over 95%.

[0093] This embodiment implements dynamic permission configuration through certificate extensions, reducing the permission setting time for friend keys from 5 minutes to 30 seconds and improving the sharing process efficiency by 90%.

[0094] To better understand this embodiment, the management system of the present invention will be described below in different scenarios. First, taking NFC-based car key authentication and unlocking as an example, the working method of this system includes:

[0095] When a user brings their phone close to the NFC reader on the car door, the vehicle detects the device and broadcasts a pairing code, which the phone then parses to obtain the VehicleID.

[0096] The vehicle sends the AUTH0 command (CLA670100Lc[VehicleID, vehicle temporary public key]00) to the mobile phone;

[0097] The mobile SE generates a temporary EC public key, calculates a shared key based on the ECDH algorithm, and returns the device public key and authentication data.

[0098] The mobile phone sends the signature to the vehicle via the AUTH1 command (CLA630000Lc[ECDSA-SHA256 signature data]00);

[0099] After the vehicle verifies the signature, it sends the CONTROL FLOW command (CLA61010000[timestamp, random number]).

[0100] The phone displays a "Unlock successful" UI, and the car terminal performs the door unlocking operation.

[0101] Next, this embodiment takes remote vehicle control in a Bluetooth scenario as an example. The working method of this system includes:

[0102] The user initiates a remote unlocking request through the car manufacturer's app, and the mobile phone connects to the vehicle's Bluetooth module via GATT;

[0103] The vehicle sends a random number challenge request, and the mobile phone signs the random number using the friend's private key and returns it.

[0104] After the vehicle-side signature verification is successful, it receives the RKE command (CLA62010000) sent from the mobile phone.

[0105] The vehicle executes a remote unlocking operation and returns a result (unlocked successfully);

[0106] The mobile app displays a message indicating that remote unlocking was successful.

[0107] Next, taking the implementation of instruction optimization under high-temperature environment as an example, the working method of this system includes:

[0108] The SE device uses a high-temperature resistant model (operating temperature range -40℃~85℃) to avoid key storage abnormalities under high temperatures;

[0109] When the vehicle detects an ambient temperature ≥60℃, it automatically triggers a fast authentication process. The AUTH0 / AUTH1 commands merge some data fields to reduce the number of interactions.

[0110] The instruction data volume is compressed by 30%, reducing the power consumption of the SE chip and ensuring instruction response speed under high temperature environments.

[0111] Finally, taking instruction adaptation for low-power devices as an example, the working method of this system includes:

[0112] By employing instruction format compression technology, the KeyID is compressed from 16 bytes to 8 bytes (local hash algorithm), reducing the APDU instruction length by 20%.

[0113] When a low-power device enters sleep mode, it only listens for the SELECT and AUTH0 commands; other commands trigger the device wake-up mechanism.

[0114] The key negotiation process is optimized, reducing the number of operations performed by the SE chip and lowering device power consumption by 50%.

[0115] As demonstrated by the examples above, the management system provided by this invention solves the problems of universality, security, and efficiency in existing technologies through its layered architecture design, dynamic security channel mechanism, and cross-protocol compatibility scheme. This instruction set supports full lifecycle management of digital keys, is compatible with various communication scenarios including NFC and Bluetooth, and can be widely applied to intelligent vehicle connectivity systems of different automakers. It possesses significant technological advantages and market application value, and can promote the standardization of the digital car key industry.

[0116] Based on the same inventive concept, embodiments of the present invention also provide an electronic device. Figure 4 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Figure 4 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 the working method of any of the digital car key management systems 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.

[0117] 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).

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

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

[0120] This invention also provides a computer-readable medium. The computer-readable medium stores a computer program, which, when executed by a processor, implements the steps of any of the digital car key management system operation methods described in the above embodiments. The computer-readable storage medium can be volatile or non-volatile.

[0121] This invention also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-described digital car key management system working method.

[0122] 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).

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

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

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

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

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

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

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

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

[0131] 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 management system for processing digital car keys using the APDU instruction set, characterized in that, include: The module comprises a key management instruction set module, a security authentication instruction set module, and a control interaction instruction set module; among which: The key management instruction set module is used to implement the full lifecycle management of digital keys, including at least generation, storage, and deletion operations; The security authentication instruction set module is used to establish an encrypted communication channel between the device and the vehicle, and to achieve identity authentication through ECDH key negotiation and ECDSA signature verification. The control interaction instruction set module is used to implement vehicle function control and device status feedback.

2. The management system according to claim 1, characterized in that, The instructions in the key management instruction set module include at least the CREATE DK instruction and the DELETE DK instruction, which are used to generate, store, and delete digital keys.

3. The management system according to claim 2, characterized in that, The format of the CREATE DK command is CLA600000Lc[CSR data]00, where the CSR data includes the digital key ID and session ID. The CREATE DK command workflow includes: The device-side security element (SE) generates a key pair; Construct a Certificate Signing Request (CSR) containing KeyID and SessionID; The Certificate Signing Request (CSR) is sent to the vehicle server via the APDU command to complete the digital certificate issuance.

4. The management system according to claim 2, characterized in that, The format of the DELETE DK command is CLA6E0000Lc[KeyID]00, and the DELETE DK command workflow includes: The device verifies the user's operation permissions. The APDU command is used to notify the device-side security unit (SE) to delete the key pair and associated certificate corresponding to the specified KeyID. Synchronously send a key status update notification to the vehicle server.

5. The management system according to claim 1, characterized in that, The instructions in the security authentication instruction set module include at least the AUTH0 instruction and the AUTH1 instruction, which are used to establish a secure channel between the device and the vehicle and to verify certificates.

6. The management system according to claim 5, characterized in that, The AUTH1 instruction has the format CLA630000Lc[signature data]00 and is used to establish a secure channel. The AUTH1 instruction workflow includes: The device uses a private key to perform ECDSA-SHA256 signing on the authentication data; The signature data is sent to the vehicle via APDU command; The vehicle uses the device's public key to verify the signature's legitimacy, and establishes a secure communication link after successful verification.

7. The management system according to claim 5, characterized in that, The control interaction instruction set module includes CONTROLFLOW and RKE instructions, which are used to trigger the device's UI display and vehicle function control.

8. The management system according to claim 7, characterized in that, The format of the CONTROL FLOW command is CLA61P1P200[status parameter]. The workflow of the CONTROL FLOW command includes: After successful vehicle-side authentication, a CONTROL FLOW command carrying status parameters is sent to the device. The device parses the P1 / P2 parameters and displays the corresponding authentication result UI. The vehicle-side synchronously executes vehicle control commands corresponding to the status parameters.

9. The management system according to claim 1, characterized in that, The instruction sets in the key management instruction set module, security authentication instruction set module, and control interaction instruction set module adopt a unified application protocol data unit (APDU) format framework, which is adapted to NFC and Bluetooth short-range communication scenarios.

10. The management system according to claim 1, characterized in that, The instruction sets in the key management instruction set module, security authentication instruction set module, and control interaction instruction set module support the ISO-14443 standard and the Bluetooth GATT protocol, enabling seamless switching between NFC and Bluetooth communication scenarios.

Images