Implementation method of standby NFC key in CCC application mobile terminal

Abstract

The invention provides a method for realizing a standby NFC key in a CCC application mobile terminal. A vehicle enterprise provides a legally authorized NFC card to a vehicle owner; when a car owner carries out key sharing through a mobile phone APP, mobile phone NFC is set to be in a card reader mode, and a frequency field and an NFC card are started to carry out interaction; the mobile phone NFC requests a random number and returns a signature result and a certificate chain; the mobile phone verifies the signature result and the certificate chain information, and the card is uploaded and identified to the cloud of the vehicle enterprise; the vehicle enterprise returns a vehicle end certificate public key of the bound vehicle and NFCID special data; a mobile phone NFC (Near Field Communication) and an NFC card generate a standard shareinfo and a shareinfo PD as a data source to generate an AESKEY symmetric key through a standard ECDH (Equal Code Data Hierarchy) mode. According to the method for realizing the standby NFC key in the CCC application mobile terminal, vehicle NFC key sharing can be conveniently, simply and quickly carried out, encryption manufacturing is ensured, and data leakage is avoided.

Description

[0001] This application is a divisional application of a patent application entitled "A method for implementing a spare NFC key in a CCC application mobile terminal". The application date of the original application is November 5, 2021, and the application number is 202111306067.4. Technical Field

[0002] The present invention relates to the technical field of vehicle network and smart car digital key, and in particular to a method for implementing a spare NFC key in a CCC application mobile terminal. Background Art

[0003] In the current CCC (Car Connectivity Consortium) alliance, there are two protocol versions of digital key specifications (Car Connectivity Consortium Digital Key Release 2) and CCC3.0 (Car Connectivity Consortium DigitalKeyRelease 3). The former supports NFC usage, while the latter adds BLE communication and UWB positioning functions on the basis of the former.

[0004] In the CCC2.0 protocol specification, all digital keys must be carried by mobile phones, and data interaction must be carried out through on-line methods, whether it is activation by the owner's mobile phone or key sharing. The proportion of mobile phones that support NFC function modules is less than 20%. For example, when sharing keys with family or friends, the other party must have a mobile phone that supports the NFC module function, otherwise it will not be usable. More often, when car companies sell cars with digital keys, they will also prepare matching spare keys (NFC cards) for car owners, so that they can use the vehicle in some emergencies. Because CCC2.0 has obvious technical and rule definitions for key sharing strategies, it is difficult for car companies to provide usable spare NFC keys for unbound factory vehicles.

[0005] Therefore, we propose a method for implementing a spare NFC key in a CCC application mobile terminal to solve the above problems. Summary of the invention

[0006] The purpose of the present invention is to provide a method for implementing a spare NFC key in a CCC application mobile terminal to solve the problem raised in the above background technology that it is difficult for car companies to provide usable spare NFC keys for unbound factory vehicles because CCC2.0 has obvious technical and rule definitions for key sharing strategies.

[0007] To achieve the above object, the present invention provides the following technical solution: a method for implementing a spare NFC key in a CCC application mobile terminal, characterized in that the implementation method comprises the following steps:

[0008] Step 1: The car manufacturer provides a legally authorized NFC card to the car owner;

[0009] Step 2: When the car owner shares the key through the mobile phone APP, set the mobile phone NFC to card reader mode, open the frequency field and interact with the NFC card;

[0010] Step 3: The mobile phone NFC requests a random number (a), and the NFC card performs standard SHA256withECDSA on it, returning the signature result and certificate chain;

[0011] Step 4: The mobile phone verifies the signature result and certificate chain information, and sends the card identification mark to the car company's cloud;

[0012] Step 5: The car company returns the vehicle certificate public key and NFCID special proprietary data PD bound to the vehicle in the cloud; PD contains the vehicle identification code, vehicle certificate, vehicle public key, anti-theft token, device public and private keys, vehicle number, and key slot information;

[0013] Step 6: The mobile phone NFC and NFC card generate standard shareinfo through the standard ECDH method, and shareinfo|PD is used as the data source to generate the AESKEY symmetric key. The generated AESKEY is used to encrypt the shared key data sharing and send it to the NFC card through the AES_CBC mode;

[0014] Step 7: The NFC card generates ECC_KP and uses ECC_SK to sign the sharing. The response data generated in the standard format is encrypted in AES_CBC mode;

[0015] Step 8: The mobile phone NFC selects CFA and calls its standard CCC command> to form a private mailbox spare NFC key for sharing verification. The method attestation data is implemented in the CCC application mobile terminal, and the result is encrypted in AES_CBC mode and sent to the NFC card; CFA is an Android mobile phone proxy tool that supports multiple proxy protocols;

[0016] Step 9: Save the mailbox spare NFC key on the NFC card and implement the attestation method in the CCC mobile application. You can then use the key as a standard sharing user.

[0017] Compared with the prior art, the beneficial effects of the present invention are: the spare NFC key is implemented in the CCC application mobile terminal, which is convenient and fast to share the vehicle NFC key, can ensure encryption and avoid data leakage. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0019] Figure 1 It is a schematic diagram of the system flow of the present invention. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0021] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0022] See also Figure 1 The present invention provides a technical solution: a method for implementing a spare NFC key in a CCC application mobile terminal, the implementation method comprising the following steps:

[0023] Step 1: The car manufacturer provides a legally authorized NFC (Near Field Communication) card to the car owner;

[0024] Step 2: When the car owner shares the key through the mobile phone APP, set the mobile phone NFC to reader mode and turn on the frequency field to interact with the NFC card.

[0025] Step 3: The mobile phone NFC requests a random number (a), and the NFC card performs standard SHA256withECDSA on it, returning the signature result and certificate chain.

[0026] Step 4: The mobile phone verifies the signature result and certificate chain information, and sends the card identification identifier (NFCID) to the car company's cloud.

[0027] Step 5: The car manufacturer returns the vehicle certificate public key (Vehicle Public Key——V_PK) and NFCID special proprietary data (Prop Data——PD) bound to the vehicle;

[0028] Step 6: The NFC phone and NFC card generate standard shareinfo through the standard ECDH (Elliptic Curve Diffie-HellmankeyExchange) method, and shareinfo|PD is used as the data source to generate the AESKEY symmetric key, which is sent to the NFC card through the AES_CBC (Advanced Encryption Standard) mode for standard shared key data.

[0029] Step 7: The NFC card generates ECC_KP (ECC Key Pair) and uses ECC_SK (ECC Public Key) to sign the sharing, and the sharing format response is encrypted in AES_CBC mode in the standard format.

[0030] Step 8: The mobile phone NFC selects CFA (CCC FrameworkAID - CCC component application AID), calls its standard CCC command>, forms a private mailbox spare NFC key for sharing verification, implements the method attestation data in the CCC application mobile terminal, and the result is encrypted in AES_CBC mode and sent to the NFC card.

[0031] Step 9: NFC saves the mailbox backup NFC key and implements the attestation method in the CCC mobile application. You can then use the key as a standard sharing user.

[0032] Furthermore, the PD contains a vehicle identification code, a vehicle certificate, a vehicle public key, an anti-theft token, a device public and private key, a vehicle number, and key slot information.

[0033] When sharing keys through a mobile phone APP, set the mobile phone NFC to reader mode, and enable the frequency field to interact with the NFC card;

[0034] Request a random number (a) through the mobile phone NFC, let the NFC card perform standard SHA256withECDSA (elliptic curve signature) on it, and return the signature result (signature) and certificate chain (chain) to the mobile phone.

[0035] The mobile phone verifies the signature result and certificate chain information, sends the card NFCID to the car company's cloud, and queries the card's proprietary information;

[0036] The car manufacturer returns the vehicle-side certificate public key (V_PK) bound to the vehicle and the NFCID special proprietary data (PD); the mobile phone NFC and NFC card generate standard shareinfo through the standard ECDH method, and shareinfo|PD is used as the data source to generate the AESKEY symmetric key, which is sent to the NFC card for standard sharing through AES_CBC mode encryption.

[0037] The NFC card generates ECC_KP and uses ECC_SK to sign (sharing), and the standard format sharing format response is encrypted through AES_CBC mode. The mobile phone NFC selects CFA and calls its standard CCC instruction> to form private mailbox attestation data for sharing verification. The result is encrypted in AES_CBC mode and sent to the NFC card.

[0038] NFC saves the mailbox attestation, and the key can be used as a standard sharing user later.

[0039] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0040] The principles and implementation methods of the present invention are described in this article using specific examples. The description of the above embodiments is only used to help understand the method and core idea of ​​the present invention. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present invention.

Claims

1. A method for implementing a spare NFC key in a CCC application mobile terminal, characterized in that: The implementation method comprises the following steps: Step 1: The car manufacturer provides a legally authorized NFC card to the car owner; Step 2: When the car owner shares the key through the mobile phone APP, set the mobile phone NFC to card reader mode, open the frequency field and interact with the NFC card; Step 3: The mobile phone NFC requests a random number (a), and the NFC card performs standard SHA256withECDSA on it, returning the signature result and certificate chain; Step 4: The mobile phone verifies the signature result and certificate chain information, and sends the card identification mark to the car company's cloud; Step 5: The car company returns the vehicle certificate public key and NFCID special proprietary data PD bound to the vehicle in the cloud; PD contains the vehicle identification code, vehicle certificate, vehicle public key, anti-theft token, device public and private keys, vehicle number, and key slot information; Step 6: The mobile phone NFC and NFC card generate standard shareinfo through the standard ECDH method, and shareinfo|PD is used as the data source to generate the AESKEY symmetric key. The generated AESKEY is used to encrypt the shared key data sharing and send it to the NFC card through the AES_CBC mode; Step 7: The NFC card generates ECC_KP and uses ECC_SK to sign the sharing. The response data generated in the standard format is encrypted in AES_CBC mode; Step 8: Select CFA on the mobile phone NFC and call its standard CCC command> to form a private mailbox spare NFC key for sharing verification. Implement the method attestation data in the CCC application mobile terminal, and the result is encrypted in AES_CBC mode and sent to the NFC card; Step 9: Save the mailbox spare NFC key on the NFC card and implement the attestation method in the CCC mobile application. You can then use the key as a standard sharing user.

Images