Digital key filling data generation method and device, cloud platform and storage medium

By decrypting and orchestrating digital key filling data through a unified platform, the problem of complex generation process and high cost in existing technologies is solved, and efficient and secure digital key filling data generation is achieved.

CN118570914BActive Publication Date: 2024-11-08SHANGHAI INGEEK CYBER SECURITY CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411054135.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-02
Publication Date
2024-11-08
Estimated Expiration
2044-08-02

AI Technical Summary

Technical Problem

In existing technologies, the data generation process for digital key filling is complex, involving multiple manufacturers, environments, and departments, resulting in long generation times, high costs, and easy verification failures when filling security chips with different versions of personalized data.

Method used

By providing a user interface to input encrypted personalized data and version information, the system decrypts and orchestrates target filling data, unifies the orchestration of personalized data for different environments and versions using the same platform, uses the PGP algorithm for encryption to ensure data security, and automatically generates target filling data in HEX format.

Benefits of technology

It simplifies the generation process, shortens the generation cycle, reduces labor costs, improves generation efficiency, and ensures data security and verification success rate.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118570914B_ABST
    Figure CN118570914B_ABST
Patent Text Reader

Abstract

The embodiment of the present invention relates to the technical field of digital key development, and discloses a method and device for generating digital key filling data, a cloud platform, and a storage medium. The method includes: providing a user interface for a user to input encrypted personalized data and version information related to filling data generation; decrypting the acquired personalized data; and arranging and packaging the personalized data according to the decrypted personalized data and version information to generate target filling data. The personalized data of multiple environments, multiple manufacturers, and multiple versions are uniformly arranged on the same platform, which greatly simplifies the generation process, shortens the generation cycle, and reduces labor costs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of digital key development, and in particular to a method and device for generating digital key filling data, a cloud platform, and a storage medium. Background Art

[0002] With the rapid development of digital keys for cars, digital key functions have become standard configurations for vehicles. Security chips provide important support for the security of digital key systems. Personalized data stored in the vehicle-side security chip is used for security authentication when interacting between the vehicle-side and the cloud, as well as between the vehicle-side and digital key devices such as mobile phones.

[0003] At present, the process of developing and testing the generation of vehicle-side filling data is relatively complicated, involving multiple vehicle manufacturers, multiple environments, and multiple departments. Personalized data is divided into multiple environments, production and non-production. Non-production environments often generate multiple versions of personalized data. In the production environment, it can be upgraded through OTA (Over-the-Air Technology) or hardware burning and filling of personalized data. Involving multiple departments, it is necessary to generate and encrypt personalized data in the cloud, decrypt the encrypted personalized data on the generation platform, and then manually generate H files with the decrypted personalized data. Finally, the H files are compiled and manually called to compile the embedded software development tools of IAR to obtain the filling data in HEX format. It can be seen that the current generation of vehicle-side filling data involves multiple factors such as multiple manufacturers, multiple environments, and multiple departments. There are a lot of implementation costs such as communication and coordination. The entire generation time of Applet varies from half a day to several days. It depends on the vehicle-side R&D. The vehicle-side filling data generation process is relatively complicated and has a high learning cost. Because the development of different versions of personalized data on the vehicle side is different, the corresponding R&D personnel and the IAR tool versions used for R&D are also different, which is time-consuming and laborious to connect.

[0004] In addition, when the security chip is loaded with data for the first time, since there is no security domain key in the security chip, the application personalized data will be loaded into it, and the data will be locked with the security domain key in the HEX file. When the security chip is subsequently loaded with data, it must first be unlocked with the security domain key. Only after the unlocking is successful can the new application personalized data be loaded into it. Currently, due to the operation of R&D personnel from multiple teams, the personalized data loaded with different security domain keys on the same security chip will fail verification. To avoid verification failure, the security domain key of each security chip when initially loaded needs to be manually recorded, which increases the complexity of the loading process. Summary of the invention

[0005] The embodiments of the present invention provide a method and device for generating digital key filling data, a cloud platform and a storage medium, which uniformly arrange personalized data of multiple environments, multiple manufacturers and multiple versions through the same platform, greatly simplifying the generation process, shortening the generation cycle and reducing labor costs.

[0006] In a first aspect, an embodiment of the present invention provides a method for generating digital key filling data, the method comprising:

[0007] Provide a user interface for users to input encrypted personalized data and fill data to generate relevant version information;

[0008] Decrypt the acquired personalized data;

[0009] According to the decrypted personalized data and the version information, the personalized data is packaged and organized to generate target filling data;

[0010] The personalized data includes: security domain key and application personalized data; the version information includes: version information of personalized data, version information of compilation tool and version information of Applet corresponding to the filling data;

[0011] Arranging and packaging the personalized data according to the decrypted personalized data and the version information to generate target filling data includes:

[0012] Assembling the personalized data into APDU according to the version information of the Applet to obtain an H file;

[0013] Arranging a verification procedure of the security domain key for the H file so as to perform security verification on the security domain key during filling;

[0014] According to the version information of the compiler tool of the verification program, the corresponding version of the compiler tool is called to compile and package the edited files to obtain the target filling data in HEX format.

[0015] As an embodiment, the step of assembling the personalized data into APDU to obtain the H file according to the version information of the Applet includes:

[0016] Obtain an H file generation script and input parameters of the H file generation script; the input parameters include: project name, SEID, Applet type and version;

[0017] The H file generation script is executed according to the input parameters to generate the H file.

[0018] As an embodiment, calling the corresponding version of the compilation tool according to the version information of the compilation tool of the verification program to compile and package the arranged files to obtain the target filling data in HEX format specifically includes:

[0019] Execute the preset compilation script to traverse the path of the H file and select the H files one by one;

[0020] Copy the H file to the specified project compilation path, clear the remaining files from the last compilation, call the corresponding version of the compilation tool to operate the corresponding program to compile the H file to generate the target filling data in HEX format, and store the generated target filling data in HEX format to the specified path; among them, the compilation script presets the H file, the target filling data in HEX format, and the path of the compilation tool.

[0021] As an embodiment, the personalized data is organized and packaged according to the decrypted personalized data and the version information to generate the target filling data, including: verifying the successfully decrypted personalized data, and after the verification, organizing and packaging the personalized data to generate the target filling data.

[0022] As an embodiment, before providing a user interface for the user to input the encrypted personalized data and filling the data to generate related version information, the method further includes:

[0023] Providing a user interface to receive a personalized data generation task;

[0024] generating personalized data according to the personalized data generation task;

[0025] Encrypting each field of the generated personalized data using a symmetric key of the PGP algorithm;

[0026] The encrypted personalized data is encrypted as a whole using the public key of the PGP algorithm to obtain the encrypted personalized data.

[0027] As an embodiment, the method further includes:

[0028] When filling the target filling data, reading the SEID of the security chip to be filled;

[0029] Select corresponding filling data for filling according to the SEID.

[0030] In a second aspect, an embodiment of the present invention provides a digital key filling data generating device, comprising:

[0031] An input module, used to provide a user interface for users to input encrypted personalized data and fill data to generate related version information;

[0032] A decryption module, used to decrypt the acquired personalized data; and

[0033] An arrangement and generation module, used for arranging and packaging the personalized data according to the decrypted personalized data and the version information to generate target filling data;

[0034] The personalized data includes: security domain key and application personalized data; the version information includes: version information of personalized data, version information of compilation tool and version information of Applet corresponding to the filling data;

[0035] The arrangement generation module includes:

[0036] An H file generating submodule, used for assembling the personalized data into APDU to obtain an H file according to the version information of the Applet;

[0037] an arrangement submodule, used for arranging the verification program of the security domain key for the H file so as to perform security verification on the security domain key when filling; and

[0038] The compiling and packaging submodule is used to call the corresponding version of the compiling tool according to the version information of the compiling tool of the verification program to compile and package the edited files to obtain the target filling data in HEX format.

[0039] As an embodiment, the compilation and packaging submodule is specifically used to: execute a preset compilation script to select H files one by one according to the path traversal of the H files; copy the H files to the specified project compilation path, clear the legacy files from the last compilation, call the corresponding version of the compilation tool to operate the corresponding program to compile the H files to generate target filling data in HEX format, and store the generated target filling data in HEX format to the specified path; wherein the compilation script presets the H file, the target filling data in HEX format, and the path of the compilation tool.

[0040] In the third aspect, an embodiment of the present invention provides a vehicle end, including a memory and a processor; the memory is used to store a computer program; the processor is used to read the computer program in the memory and implement the digital key filling data generation method as described in the first aspect when executing the program.

[0041] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for generating digital key filling data as described in the first aspect.

[0042] Compared with the prior art, the technical solution provided by the embodiment of the present invention has at least the following positive effects:

[0043] In the technical solution of the embodiment of the present invention, a user interface is provided for the user to input encrypted personalized data and version information related to the filling data generation to obtain the encrypted personalized data and version information related to the filling data generation, the obtained personalized data is decrypted, and the personalized data is arranged and packaged according to the decrypted personalized data and version information to generate target filling data, thereby realizing unified arrangement, compilation and packaging of filling data under different environments, different versions of personalized data, different versions of compilation tools and different versions of applets through the same platform, simplifying the generation process, greatly shortening the generation cycle and labor costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0045] Figure 1 A schematic diagram of a flow chart of a method for generating digital key filling data provided in the first embodiment of the present invention;

[0046] Figure 2 A schematic diagram of the structure of a digital key filling data generating device provided in Embodiment 2 of the present invention;

[0047] Figure 3 This is a schematic diagram of the structure of the cloud platform provided in Example 3 of the present invention. DETAILED DESCRIPTION

[0048] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0049] The following describes the digital key filling data generation method and device, cloud platform and storage medium of the embodiment of the present application with reference to the accompanying drawings. The filling data generation process mentioned in the background technology involves the management of multiple vehicle-side Applet versions. At the same time, the vehicle-side developers corresponding to different personalized data versions may be different, and the IAR tool versions used in research and development are different, resulting in the generation of vehicle-side Applet filling data. There are problems such as complex processes, high labor consumption and long generation cycles. The present application provides a digital key filling data generation method, in which a user interface is provided for users to input encrypted personalized data and filling data generation-related version information, the obtained personalized data is decrypted, and the personalized data is arranged and packaged according to the decrypted personalized data and version information to generate target filling data, thereby realizing unified arrangement, compilation and packaging of filling data under different environments, different versions of personalized data, different versions of compilation tools and different versions of Applets through the same platform, simplifying the generation process, greatly shortening the generation cycle and labor costs.

[0050] Specifically, Figure 1 This is a flow chart of a method for generating digital key filling data provided in the first embodiment of the present application, which is used to generate filling data for a digital key vehicle-side security chip. The method can be executed by a digital key filling data generating device provided in the embodiment of the present application, which can be implemented in software and / or hardware and configured on a cloud platform.

[0051] like Figure 1 As shown, the digital key filling data generation method of the present application includes the following steps:

[0052] Step 101: Provide a user interface for the user to input encrypted personalized data and fill data to generate relevant version information.

[0053] Personalized data includes security domain keys and application personalized data. The security domain key is used for access authentication of the security chip SE (Security Element), that is, the security chip can be operated only after the security domain key is verified. Application personalized data is used for communication authentication between the vehicle and the cloud, and between the vehicle and digital key devices such as mobile phones. Application personalized data may include keys for communication between the vehicle and the cloud, and between the vehicle and the digital key device.

[0054] The method for generating personalized data may include the following steps: providing a user interface to receive a personalized data generation task; generating personalized data according to the personalized data generation task; performing a layer of encryption on each field of the generated personalized data using a symmetric key of a PGP (Pretty Good Privacy) algorithm; encrypting the personalized data after a layer of encryption as a whole using a public key of the PGP algorithm to obtain encrypted personalized data, thereby obtaining encrypted personalized data. The first layer of encryption algorithm may use any one of the AES128 / CTR / NoPadding algorithms, and the encryption key may be provided by the manufacturer of the data for the security chip filling. When encrypting each data field, each data field is encrypted independently, and the encrypted IV is 16-byte length data, the first byte indicates the number of data, and the other 15 bytes of data are 0x00. When the public key of the PGP algorithm is used to encrypt the personalized data after a layer of encryption as a whole, the public key of the PGP algorithm may be provided by the manufacturer of the security chip.

[0055] Among them, encryption of sensitive data in application personal data includes encryption keys for test and production environments. Sensitive data encryption keys can be generated by digital key service providers and transmitted to security chip manufacturers using PGP public key encryption. For security reasons, encryption keys need to be distinguished between keys in the test phase and keys in the production phase. In the test phase, test encryption keys are used for testing, and after the test is completed, they are converted to production encryption keys for formal production.

[0056] Personalized data needs to be loaded into the vehicle-side SE module, which is the guarantee for establishing secure communication between the vehicle, cloud, and mobile phone. Therefore, it is very important to ensure the security of personalized data. When the generated personalized data is exported, we encrypt the personalized data and generate a PGP (PGP is a hybrid encryption algorithm, which consists of a symmetric encryption algorithm (IDEA), an asymmetric encryption algorithm (RSA), a one-way hash algorithm (MD5), and a random number generator (generating a pseudo-random number sequence from the user's keystroke frequency)) file. When importing the Applet automatic generation program, the service decrypts the data internally to ensure the security of the data flow. Protecting personalized data through PGP encryption ensures data security and solves the risks brought by plaintext data in previous manual processing.

[0057] The version information related to the generation of filling data includes: the version information of personalized data, the version information of the compilation tool, and the version information of the Applet corresponding to the filling data. The version information of personalized data can be determined according to different car manufacturers. The compilation tool can be the compilation software provided by IAR. The version information of the Applet of filling data is determined according to the actual needs of the car manufacturer. The Applet of the security chip refers to a small program embedded in the security chip. These small programs are usually used to implement specific functions, such as identity authentication, data encryption, etc. The digital key security chip Applet is used to implement digital key related functions. The security chip can simultaneously install CCC (Car Connectivity Consortium), ICCE (Intelligent Car Connectivity Industry Ecosystem Alliance), ICCOA (Intelligent Car Connectivity Open Alliance), private protocol and other Applets, which are compatible with different digital key protocols. This flexibility enables the security chip to better adapt to different application scenarios and needs. The Applet is directly embedded in the security chip, so its security and stability are well guaranteed. At the same time, since the Applet is programmed, the functions and performance of the security chip can be enhanced through upgrading and updating.

[0058] Step 102: Decrypt the acquired personalized data.

[0059] The private key of the PGP algorithm can be used to perform the first-level decryption of the personalized data, and then the symmetric key corresponding to the PGP symmetric encryption algorithm mentioned above can be used to decrypt the personalized data to obtain the decrypted data.

[0060] The personalized data that has been successfully decrypted is verified, and after the verification is passed, the personalized data is organized and packaged to generate the target filling data.

[0061] Step 103: The personalized data is packaged and organized according to the decrypted personalized data and version information to generate target filling data.

[0062] Step 103 compiles and packages the personalized data according to the decrypted personalized data and version information to generate target filling data, which may specifically include: assembling the personalized data into APDU to obtain an H file according to the version information of the Applet; compiling a verification program for the security domain key in the H file to perform security verification on the security domain key during filling; calling a compilation tool of a corresponding version according to the version information of the compilation tool of the verification program to compile and package the compiled file to obtain the target filling data in HEX format.

[0063] According to the version information of the Applet, the personalized data is assembled into APDU (Application Protocol Data Unit) to obtain an H file, including: obtaining the H file generation script and the input parameters of the H file generation script, and executing the H file generation script according to the input parameters to generate the H file. The input parameters include: project name, SEID, Applet type and version. Among them, the project name is used for file classification, and SEID is used to select the personalized data that needs to be processed currently from the batch of personalized data files. The automatic generation program selects the corresponding Applet application from the vehicle-side program configuration according to the type and version of the Applet. Select a batch script to generate the personalized data H file according to the personalized data version. The H file generation script is executed to generate individual personalized data H files in sequence. If it is a batch of personalized data, repeat the steps of assembling personalized data into APDU until all personalized data generate H files.

[0064] According to the version information of the compiler tool of the verification program, the corresponding version of the compiler tool is called to compile and package the arranged files to obtain the target filling data in HEX format, which specifically includes: executing the preset compilation script to select H files one by one according to the path traversal of the H file; copying the H file to the specified project compilation path, clearing the legacy files of the last compilation, calling the corresponding version of the compilation tool to operate the corresponding program to compile the H file to generate the target filling data in HEX format, and storing the generated target filling data in HEX format to the specified path; wherein, the compilation script presets the H file, the target filling data in HEX format, and the path of the compilation tool. Among them, the corresponding program can be C++, which is used to compile the verification program and the filling program, and the filling program is used to cooperate with the burner to realize the filling of the filling data.

[0065] When composing, compiling and packaging the H file of the personalized data, select the IAR compilation tool version used by the corresponding version according to the personalized data version, the corresponding vehicle-side C program (compilation program) and the compiled script file.

[0066] In this embodiment, in the process of generating H and HEX files from personalized data, the process is processed on the internal Window system machine, and the processing result is notified by callback using webhook (a callback processing method).

[0067] When filling data is automatically generated, the corresponding version of the vehicle-side program is used for compilation and packaging of different versions of personalized data. The cloud platform integrates different versions of IAR tools and different automated compilation scripts, and automatically identifies and generates the required Applet version and compilation tool version to achieve automated arrangement, compilation and packaging. Applets of different versions of personalized data are managed, and the vehicle-side code is compiled using scripts to automatically package and generate H and HEX vehicle-side filling files.

[0068] When filling the target filling data, read the SEID of the security chip to be filled, and select the corresponding filling data for filling according to the SEID, so that each time the data is refilled, the same security domain key is always filled into the same security chip, simplifying the filling process and ensuring that the security domain key verification is successful, and the filling proceeds smoothly.

[0069] In this method, to generate an Applet for a new board, you only need to generate personalized data first, and then import the personalized data on the Applet generation page to automatically generate and fill the Applet data; to generate an Applet for a security chip that needs to be upgraded, you only need to import the previous personalized data on the Applet generation page, select the version that needs to be upgraded, and you can generate a new version of the Applet filling file.

[0070] In the Applet automatic generation process of this method, different versions of personalized data processing methods are compiled in different ways. The data of personalized data version 1.0 and personalized data version 2.0 are quite different. The vehicle-side R&D personnel are different, and the programs developed by the vehicle-side and the IAR tool versions used to compile the vehicle-side programs are all different. When the Applet is automatically generated, different versions of personalized data are compiled for the vehicle-side programs. The IAR tool versions and automatic compilation scripts used are different, which ensures the consistency of the user experience.

[0071] Generally speaking, the security chip application programs that originally required multiple terminals, multiple R&D personnel, and multiple different programming languages ​​to complete can now be uniformly orchestrated by the cloud, which not only ensures the security of the data, but also ensures the convenience of generating security chip applications.

[0072] The application examples of the method for generating digital key filling data according to the embodiment of the present invention are as follows:

[0073] Take the first filling as an example:

[0074] 1) Log in to the management backend to generate personalized data;

[0075] 2) Create personalized data task batches;

[0076] 3) Wait for the batch of personalized data generation to be completed and download the personalized data PGP encrypted file;

[0077] 4) Log in to the Applet automatic generation management platform and import the personalized data PGP encrypted file generated above (the personalized data can be one or a batch, such as hundreds or thousands of pieces);

[0078] 5) Wait for the filling Applet data to be generated and download the corresponding file (the cloud platform arrangement process includes: after the personalized data is imported, the imported encrypted file is decrypted and the validity of each personalized data is verified. After that, the saving service will be called to save the personalized data file, and the operator will be prompted that the data has been successfully imported and the task is being processed; at this time, the C program on the vehicle side and IAR and other programs are arranged according to the version of the personalized data and the version of the Applet to perform a series of compilation processing on the data; after the processing is completed, the cloud program will notify the operator of the processing results of each personalized data, and the operator can download the successfully generated HEX file at this time; when the entire batch is generated successfully, the operator will be prompted that all the generation is completed, and the operator can package and download the HEX file of the entire batch;

[0079] 6) If the execution result is failed, click Re-execute. The system will check whether the previous personalized data still exists. If it exists, it will be re-compiled and generated. If not, the personalized data needs to be re-imported;

[0080] 7) If the execution is successful, the Applet filling data can be exported;

[0081] 8) The filling data can be filled into the SE module through the filling tool. When the HEX target filling file is filled into the SE module (i.e., the security chip), the security domain key of the data will be verified. When it is the first filling, since there is no key, the application personalized data will be filled in, and the data will be locked with the security domain key in the HEX file. When it is not the first filling, the security domain key will be used to unlock it first. After the unlocking is successful, the new application personalized data will be filled in. Previously, due to the operation of R&D personnel from multiple teams, the same SE module would be filled with personalized data with different security domain keys, and verification failure would occur at this time. Therefore, it is necessary to manually record the security domain key of each SE module at the time of initial filling, so as to ensure that the new application personalized data can still be written successfully during multiple fillings, which increases the complexity of the filling process. This application unifies the processing flow of different ends through the cloud platform, and uses the same security domain key for personalized data of the same security chip, thereby simplifying the filling process.

[0082] 9) As described in 8, for security chips that have already been installed, when Applet needs to be upgraded, you only need to import the previously existing personalized data, select the new version of Applet, and the cloud will complete the orchestration of the entire process.

[0083] The method for generating digital key filling data provided by the embodiment of the present invention has the following advantages:

[0084] 1. The personnel who need to fill the Applet data generate personalized data, and then import the personalized data into the Applet generation page to complete the generation of the data filling Applet. The whole process reduces the manpower consumption from the original three to five people to one person, and the operation process is simple;

[0085] 2. The personnel who need to fill the Applet data can generate personalized data and then import the personalized data into the Applet generation page to complete the generation of the data filling Applet. The time consumption is reduced from half a day or even several days to minutes to half an hour, which greatly improves the efficiency.

[0086] 3. When the generated personalized data is exported, we encrypt the personalized data and generate a PGP file. When it is imported into the Applet for automatic generation, the service decrypts the data internally to ensure the security of the data flow process. Compared with the previous manual processing, the confidentiality of the data is guaranteed;

[0087] 4. When the Applet is automatically generated, different versions of personalized data are compiled by different vehicle-side programs. The IAR tool versions and automated compilation scripts used are different. This shields the variability of different personalized data developed by different vehicle-side developers, allowing users to experience the same way.

[0088] 5. For Applet upgrades, we can use existing personalized data and directly select the corresponding Applet version when importing the Applet generation page.

[0089] The present invention provides an efficiency-enhancing solution for automatically generating vehicle-side SE module Applet filling data from personalized encrypted data, which is suitable for initializing vehicle-side filling data of digital keys. The main steps of the method include: a person who needs to fill the Applet data generates personalized data, and then imports the personalized data into the Applet generation page to complete the generation of the filling data Applet. The entire process is reduced in manpower consumption from the original three to five people to one person, and in time consumption from the original half a day or even several days to the current minutes to half an hour, which greatly improves efficiency and reduces manpower and time consumption.

[0090] Embodiment 2 of the present invention provides a digital key filling data generating device, which is configured on a cloud platform. Figure 2 As shown, the filling data generating device 200 includes: an input module 202 , a decryption module 204 and a layout generating module 206 .

[0091] The input module 202 is used to provide a user interface for the user to input the encrypted personalized data and the filling data to generate related version information.

[0092] The decryption module 204 is used to decrypt the acquired personalized data.

[0093] The compilation and generation module 206 is used to compile and package the personalized data according to the decrypted personalized data and version information to generate target filling data.

[0094] Optionally, the personalized data includes: a security domain key and application personalized data. The version information includes: version information of the personalized data, version information of the compilation tool, and version information of the Applet corresponding to the filling data.

[0095] The arrangement generation module 206 includes:

[0096] The H file generation submodule is used to assemble the personalized data into APDU to obtain the H file according to the version information of the Applet;

[0097] An arrangement submodule, used for arranging a verification program of the security domain key for the H file so as to perform security verification on the security domain key when filling; and

[0098] The compiling and packaging submodule is used to call the corresponding version of the compiling tool according to the version information of the compiling tool of the verification program to compile and package the edited files to obtain the target filling data in HEX format.

[0099] Optionally, the H file generation submodule is specifically used to obtain an H file generation script and input parameters of the H file generation script; the input parameters include: project name, SEID (Secure Element ID security chip unique number), Applet type and version; execute the H file generation script according to the input parameters to generate an H file.

[0100] The compilation and packaging submodule is specifically used to execute the preset compilation script to select H files one by one according to the path traversal of the H files; copy the H files to the specified project compilation path, clear the remaining files from the last compilation, call the corresponding version of the compilation tool to operate the corresponding program to compile the H files to generate target filling data in HEX format, and store the generated target filling data in HEX format to the specified path; among them, the compilation script presets the H file, the target filling data in HEX format, and the path of the compilation tool.

[0101] The arrangement generation module 206 can also be used to verify the personalized data that has been successfully decrypted, and after the verification is passed, the personalized data is arranged and packaged to generate target filling data.

[0102] The filling data generating device 200 may further include:

[0103] A personalized data input module, used for providing a user interface to receive a personalized data generation task;

[0104] A personalized data generation module, used to generate personalized data according to a personalized data generation task;

[0105] The first encryption module is used to encrypt each field of the generated personalized data using a symmetric key of the PGP algorithm;

[0106] The second encryption module is used to encrypt the encrypted personalized data of one layer as a whole using the public key of the PGP algorithm to obtain encrypted personalized data.

[0107] The filling data generating device 200 may further include:

[0108] SEID reading module, used to read the SEID of the security chip to be filled when filling the target filling data;

[0109] The filling module is used to select corresponding filling data for filling according to SEID.

[0110] Compared with the prior art, the digital key filling data generating device of the embodiment of the present invention provides a user interface for the user to input encrypted personalized data and filling data generation-related version information to obtain the encrypted personalized data and filling data generation-related version information, decrypts the obtained personalized data, and arranges and packages the personalized data according to the decrypted personalized data and version information to generate target filling data. In this way, unified arrangement, compilation and packaging of filling data under different environments, different versions of personalized data, different versions of compilation tools and different versions of applets can be achieved through the same platform, thereby simplifying the generation process and greatly shortening the generation cycle and labor costs.

[0111] Embodiment 3 of the present invention provides a cloud platform. Figure 3 A schematic diagram of the structure of a cloud platform provided in an embodiment of the present invention. The cloud platform 30 includes a memory 31 and a processor 32;

[0112] The memory 31 is used to store computer programs; the processor 32 is used to read the computer program in the memory 31 and implement the digital key filling data generation method as described in the above embodiment when executing the program.

[0113] An embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a computer processor, the computer program is used to execute the technical solution of any method embodiment.

[0114] Through the above description of the implementation methods, the technicians in the relevant field can clearly understand that the present invention can be implemented by means of software and necessary general hardware, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a grid device, etc.) to execute the methods described in each embodiment of the present invention.

[0115] It is worth noting that in the embodiment of the above-mentioned device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0116] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for generating digital key filling data, characterized in that: The method comprises: Providing a user interface for the user to input encrypted personalized data and related version information required for the filling data generation process; the personalized data includes: security domain key and application personalized data; the version information includes: version information of the personalized data, version information of the compilation tool and version information of the Applet corresponding to the filling data; Decrypt the acquired personalized data; According to the decrypted personalized data and the version information, the personalized data is packaged and organized to generate target filling data; Arranging and packaging the personalized data according to the decrypted personalized data and the version information to generate target filling data includes: Assembling the personalized data into APDU according to the version information of the Applet to obtain an H file; Arranging a verification procedure of the security domain key for the H file so as to perform security verification on the security domain key during filling; According to the version information of the compilation tool of the verification program, the compilation tool of the corresponding version is called to compile and package the edited files to obtain the target filling data in HEX format.

2. The method for generating digital key filling data according to claim 1, characterized in that: The step of assembling the personalized data into APDU to obtain an H file according to the version information of the Applet includes: Obtain an H file generation script and input parameters of the H file generation script; the input parameters include: project name, SEID, Applet type and version; The H file generation script is executed according to the input parameters to generate the H file.

3. The method for generating digital key filling data according to claim 1, characterized in that: The calling of the corresponding version of the compilation tool according to the version information of the compilation tool of the verification program to compile and package the arranged files to obtain the target filling data in HEX format specifically includes: Execute the preset compilation script to traverse the path of the H file and select the H files one by one; Copy the H file to the specified project compilation path, clear the remaining files from the last compilation, call the corresponding version of the compilation tool to operate the corresponding program to compile the H file to generate the target filling data in HEX format, and store the generated target filling data in HEX format to the specified path; among them, the compilation script presets the H file, the target filling data in HEX format, and the path of the compilation tool.

4. The method for generating digital key filling data according to claim 1, characterized in that: The step of arranging and packaging the personalized data according to the decrypted personalized data and the version information to generate the target filling data includes: verifying the successfully decrypted personalized data, and arranging and packaging the personalized data to generate the target filling data after the verification passes.

5. The method for generating digital key filling data according to claim 1, characterized in that: Before providing a user interface for the user to input the encrypted personalized data and filling the data to generate related version information, it also includes: Providing a user interface to receive a personalized data generation task; generating personalized data according to the personalized data generation task; Encrypting the generated personalized data field by field using a symmetric key of the PGP algorithm; The encrypted personalized data is encrypted as a whole using the public key of the PGP algorithm to obtain the encrypted personalized data.

6. The method for generating digital key filling data according to claim 2, characterized in that: The method further comprises: When filling the target filling data, reading the SEID of the security chip to be filled; Select corresponding filling data for filling according to the SEID.

7. A digital key filling data generating device, characterized in that: include: An input module, used for providing a user interface for a user to input encrypted personalized data and related version information required for the filling data generation process; The personalized data includes: security domain key and application personalized data; the version information includes: version information of personalized data, version information of compilation tool and version information of Applet corresponding to the filling data; A decryption module, used to decrypt the acquired personalized data; and An arrangement and generation module, used for arranging and packaging the personalized data according to the decrypted personalized data and the version information to generate target filling data; The arrangement generation module includes: An H file generating submodule, used for assembling the personalized data into APDU to obtain an H file according to the version information of the Applet; an arrangement submodule, used for arranging the verification program of the security domain key for the H file so as to perform security verification on the security domain key when filling; and The compiling and packaging submodule is used to call the corresponding version of the compiling tool according to the version information of the compiling tool of the verification program to compile and package the edited files to obtain the target filling data in HEX format.

8. The digital key filling data generating device according to claim 7, characterized in that: The compilation and packaging submodule is specifically used for: executing a preset compilation script to select H files one by one according to the path traversal of the H files; copying the H files to the specified project compilation path, clearing the legacy files of the last compilation, calling the corresponding version of the compilation tool to operate the corresponding program to compile the H files to generate target filling data in HEX format, and storing the generated target filling data in HEX format to the specified path; wherein the compilation script presets the H files, the target filling data in HEX format, and the path of the compilation tool.

9. A cloud platform, characterized in that: Including memory and processor; A memory for storing a computer program; the processor is used to read the computer program in the memory and implement the digital key filling data generation method as described in any one of claims 1-6 when executing the program.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the digital key filling data generating method as described in any one of claims 1-6 is implemented.

Citation Information

Patent Citations

  • Digital key generation system

    CN110855616A

  • Automobile Bluetooth key safety management system and method

    CN111186414A

  • Secret key filling method and system of digital key

    CN115696321A

  • Method for designing POS machine remote key filling protocol based on TR34 specification

    CN115720141A

  • Vehicle digital key secret key filling method, system and device and medium

    CN117793709A