Controller key filling method, device, service system, diagnostic instrument and vehicle

Abstract

The application relates to the technical field of vehicles, in particular to a controller key filling method and device, a service system, a diagnostic instrument and a vehicle. The method comprises the following steps: when an original controller is filled with a key, a reference key check value issued by a key management system is stored; when the original controller is replaced by a new controller, if a diagnostic device is successfully logged in, a key filling request sent by the diagnostic device and vehicle end information of a target vehicle are acquired, a derivative parameter is generated according to the vehicle end information, a derivative key and a derivative key check value are generated by the key management system according to the derivative parameter, the reference key check value of the target vehicle is found according to a vehicle identifier, if the check value of the derivative key is consistent with the reference key check value, the ciphertext of the derivative key is issued to the diagnostic device, and the diagnostic device fills the new controller of the target vehicle with the ciphertext of the derivative key. The method solves the problems of low efficiency, low safety and low consistency of vehicle controller key filling.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a controller key filling method, apparatus, service system, diagnostic instrument, and vehicle. Background Technology

[0002] With increasing concerns about electric vehicle safety, most electric vehicles now require communication authentication. Successful authentication is a prerequisite for unlocking, powering on, starting the vehicle, and outputting power. It should be noted that there are two types of controllers involved in communication authentication: the authentication initiator and the authentication verification and result feedback provider, both using symmetric keys.

[0003] However, in existing technologies, operators write the controller key using offline electrical testing equipment, which is prone to failure or omissions due to improper human operation, resulting in low success rate and low efficiency when filling the key. When replacing the controller of an electric vehicle after-sales service, it is necessary to either return to the factory to apply for key filling or send it to a controller that already has the key. The former has low security, and the latter has too high requirements and is often difficult to achieve. Therefore, the entire after-sales controller replacement process is inefficient and insecure. Summary of the Invention

[0004] This application provides a controller key filling method, apparatus, service system, diagnostic instrument, and vehicle to solve problems such as low efficiency, low security, and low consistency in vehicle controller key filling.

[0005] The first aspect of this application provides a controller key injection method applied to a front-end service system, comprising the following steps: when injecting a key into the original controller, storing a reference key verification value issued by a key management system; when the original controller is replaced with a new controller, if the diagnostic device successfully logs in, establishing a communication connection between the front-end service system and the diagnostic device; obtaining the key injection request sent by the diagnostic device and the vehicle-side information of the target vehicle, identifying the original controller identifier, vehicle identifier, and supplier identifier in the vehicle-side information; responding to the key injection request, generating derived parameters based on the controller identifier, vehicle identifier, and supplier identifier, and uploading the derived parameters to the key management system, wherein the key management system generates a derived key and a derived key verification value based on the derived parameters; searching for the reference key verification value of the target vehicle based on the vehicle identifier, and if the verification value of the derived key matches the reference key verification value, sending the encrypted text of the derived key to the diagnostic device, wherein the diagnostic device injects a key into the new controller of the target vehicle based on the encrypted text of the derived key.

[0006] Optionally, in this embodiment, both the front-end service system and the key management system are deployed in the cloud.

[0007] Optionally, in this embodiment of the application, the front-end service system has at least one of the following functions: vehicle model management, supplier management, parts management, vehicle management, key management, and database management.

[0008] Optionally, in this embodiment of the application, establishing a communication connection between the front-end service system and the diagnostic device includes: completing two-way authentication between the front-end service system and the diagnostic device through the TLS protocol; and establishing a communication connection through the HTTPS protocol after the two-way authentication is successful.

[0009] A second aspect of this application provides a controller key injection method applied to a diagnostic device, comprising the following steps: obtaining a target vehicle authorization code from an OEM; verifying the target vehicle using the authorization code and then connecting to the target vehicle; obtaining the vehicle's terminal information; successfully logging in based on login data issued by a front-end service system; establishing a communication connection between the front-end service system and the diagnostic device; uploading a key injection request and the target vehicle's terminal information to the front-end service system; wherein the front-end service system responds to the key injection request, generates derived parameters, and uploads the derived parameters to a key management system; wherein the key management system generates a derived key and a derived key verification value based on the derived parameters; searches for a reference key verification value for the target vehicle based on the vehicle identifier; if the derived key verification value matches the reference key verification value, sends the encrypted derived key to the diagnostic device; and injecting a new controller for the target vehicle based on the encrypted derived key.

[0010] A third aspect of this application provides a controller key filling device, which is applied to a front-end service system. The device includes: a storage module for storing a reference key verification value issued by a key management system when filling a key on the original controller; a communication module for establishing a communication connection between the front-end service system and the diagnostic device if the diagnostic device successfully logs in when the original controller is replaced with a new controller; a first acquisition module for acquiring a key filling request sent by the diagnostic device and vehicle-side information of the target vehicle, and identifying the original controller identifier, vehicle identifier, and supplier identifier in the vehicle-side information; a generation module for responding to the key filling request, generating derived parameters based on the controller identifier, vehicle identifier, and supplier identifier, and uploading the derived parameters to the key management system, wherein the key management system generates a derived key and a derived key verification value based on the derived parameters; and a distribution module for searching the reference key verification value of the target vehicle based on the vehicle identifier, and if the verification value of the derived key matches the reference key verification value, distributing the encrypted text of the derived key to the diagnostic device, wherein the diagnostic device performs key filling on the new controller of the target vehicle based on the encrypted text of the derived key.

[0011] A fourth aspect of this application provides a controller key filling device, which is applied to a diagnostic device and includes: a second acquisition module for obtaining a target vehicle authorization code from a vehicle manufacturer; a verification module for verifying the target vehicle using the authorization code and then connecting to the target vehicle; an upload module for acquiring vehicle-side information of the target vehicle, establishing a communication connection between the front-end service system and the diagnostic device after successful login based on login data issued by the front-end service system, and uploading a key filling request and the vehicle-side information of the target vehicle to the front-end service system, wherein the front-end service system responds to the key filling request, generates derived parameters, and uploads the derived parameters to a key management system, wherein the key management system generates a derived key and a derived key verification value based on the derived parameters, searches for a reference key verification value of the target vehicle based on the vehicle identifier, and if the verification value of the derived key matches the reference key verification value, sends the encrypted text of the derived key to the diagnostic device; and a filling module for filling a new controller of the target vehicle with a key based on the encrypted text of the derived key.

[0012] The fifth aspect of this application provides a front-end service system, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the controller key filling method as described in the above embodiments.

[0013] A sixth aspect of this application provides a diagnostic instrument, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed, it is used to implement the controller key filling method as described in the above embodiments.

[0014] A seventh aspect of this application provides a vehicle including a controller, wherein the controller performs key injection based on the controller key injection method described above.

[0015] Therefore, this application has the following beneficial effects:

[0016] This application's embodiment enables communication between the front-end service system and diagnostic equipment during after-sales controller replacement. The entire communication process is encrypted. After logging in, the diagnostic equipment can apply for a key online from the front-end service system, while the front-end service system can obtain vehicle-side information provided by the diagnostic equipment. Furthermore, when the key management system issues keys, the front-end service system ensures consistency across all services, achieving one key per vehicle and one service. This improves both the security and efficiency of key writing during after-sales controller replacement. Therefore, it solves the technical problems of low efficiency, low security, and low consistency in vehicle controller key writing.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0019] Figure 1 This is a flowchart of a controller key filling method provided according to an embodiment of this application;

[0020] Figure 2 This is a flowchart of a controller key filling method according to an embodiment of this application;

[0021] Figure 3 A flowchart of a controller key filling method according to another embodiment of this application;

[0022] Figure 4 This is an example diagram of a controller key filling device according to an embodiment of this application;

[0023] Figure 5 This is an example diagram of a controller key filling device according to another embodiment of this application. Detailed Implementation

[0024] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0025] The following description, with reference to the accompanying drawings, outlines a controller key injection method, apparatus, service system, diagnostic tool, and vehicle according to embodiments of this application. Addressing the issues of low efficiency, low security, and low consistency in vehicle controller key injection mentioned in the background art, this application provides a controller key injection method. In this method, a diagnostic device sends vehicle-side information and a key injection request to a front-end service system. The front-end service system generates derived parameters, and the key management system derives a key based on these parameters. Finally, the front-end service system verifies the generated key. This solves the problems of low efficiency, low security, and low consistency in vehicle controller key injection.

[0026] Specifically, Figure 1 This is a flowchart illustrating a controller key injection method provided in an embodiment of this application. This controller key injection method is applied to a front-end service system, such as... Figure 1 As shown, the controller key filling method includes the following steps:

[0027] In step S101, when the original controller is filled with the key, the reference key verification value issued by the key management system is stored.

[0028] Understandably, the checksum is generated in the key management system and maintained in the front-end service system. Therefore, when the key management system distributes a pre-configured key, it includes the key's checksum. During the initial key loading, after receiving the key ciphertext and key checksum, the front-end system maintains the checksum corresponding to that key within the system.

[0029] In step S102, when the original controller is replaced with a new controller, if the diagnostic device successfully logs in, a communication connection is established between the front-end service system and the diagnostic device.

[0030] It can be understood that logging into a diagnostic device requires a set of data issued by the front-end service system. If the data is incorrect, the diagnostic device cannot log in; if the data is correct, the diagnostic device logs in successfully, thus improving the security of establishing a communication connection.

[0031] In this embodiment of the application, establishing a communication connection between the front-end service system and the diagnostic device includes: completing two-way authentication between the front-end service system and the diagnostic device through the TLS protocol; and establishing a communication connection through the HTTPS protocol after the two-way authentication is successful.

[0032] Two-way authentication is a security guarantee. Before performing key filling operations, after-sales diagnostic equipment must apply for login authorization from the OEM (Original Equipment Manufacturer) through the system. Only after authorization is granted can the equipment log in to the system to perform key-related operations.

[0033] It is understood that in this application embodiment, the front-end service system and the diagnostic equipment need to be mutually authenticated before a communication connection can be established. After-sales diagnostic equipment operators must pass the security code verification before they can connect to the front-end service system and apply for the key required by the vehicle controller. This security code ensures the security of the communication link and makes key transmission more secure.

[0034] Specifically, TLS is a security protocol that protects network communication security by encrypting communication data, verifying the identity of communicating parties, and ensuring data integrity. HTTPS (Hypertext Transfer Protocol) is a communication protocol for securely transmitting hypertext over computer networks. It is an extension of the HTTP protocol and uses TLS encryption technology to protect data security.

[0035] In this embodiment, the front-end service system has at least one of the following functions: vehicle model management, supplier management, parts management, vehicle management, key management, and database management.

[0036] Specifically, vehicle model management refers to managing vehicles according to their type, such as SUVs, sedans, and sports cars; supplier management refers to managing vehicles according to their controller suppliers; parts management is equivalent to controller management; and vehicle management requires management down to a specific vehicle model. Key management is typically used to securely store, generate, and manage encryption keys. Database management involves managing and maintaining all aspects of the database system to ensure its reliability, security, and performance.

[0037] In step S103, the key filling request sent by the diagnostic device and the vehicle information of the target vehicle are obtained, and the original controller identifier, vehicle identifier and supplier identifier in the vehicle information are identified.

[0038] The vehicle-side information can include vehicle identification information, engine and vehicle performance data, fault codes and diagnostic information, and other information carried by the vehicle itself.

[0039] It is understood that in this embodiment of the application, the diagnostic device sends a key filling request and vehicle-side information of the target vehicle to the front-end service system for communication. The communication process is based on HTTP and uses the TLS protocol, which greatly improves the confidentiality of information during the transmission of key filling requests and vehicle-side information, and significantly improves the transmission efficiency compared to manual writing.

[0040] In step S103, in response to the key filling request, derived parameters are generated based on the controller identifier, vehicle identifier, and supplier identifier, and the derived parameters are uploaded to the key management system. The key management system generates a derived key and a derived key verification value based on the derived parameters.

[0041] Derived parameters refer to new parameters obtained by further processing the controller identifier, vehicle identifier, and supplier identifier, including but not limited to part numbers, vehicle identification numbers, and supplier codes. The key management system and diagnostic equipment also connect bidirectionally via the TLS protocol.

[0042] It should be noted that the front-end service system and key management system in this application embodiment are both deployed in the cloud, which is not limited by location or device and allows access anytime and anywhere, thus providing greater flexibility and convenience. At the same time, the cloud often has stronger security measures, and deploying the front-end service system and key management system in the cloud can improve data security, reliability and fault tolerance.

[0043] In this embodiment, the key management system generates the controller key and cloud key verification value of the target vehicle based on the derivation parameters. Specifically, the key management system uses multi-level derivation and different derivation algorithms to derive different keys based on the key usage services of different vehicle models, different vehicles, and different controllers, ensuring one key per service.

[0044] It is understood that in this embodiment of the application, derived parameters carrying vehicle characteristic values ​​are obtained from the controller identifier, vehicle identifier, and supplier identifier. The key management system generates keys based on the derived parameters. Therefore, the generated keys are highly consistent with the vehicles, ensuring that the vehicles, services, and keys correspond one-to-one. This ensures that different vehicles and different services use different keys, and that the leakage of a key in a single vehicle will not affect other vehicles, greatly improving the security of key loading.

[0045] In step S105, the reference key verification value of the target vehicle is found based on the vehicle identifier. If the verification value of the derived key matches the verification value of the reference key, the ciphertext of the derived key is sent to the diagnostic device. The diagnostic device then performs key loading on the new controller of the target vehicle based on the ciphertext of the derived key.

[0046] Understandably, during after-sales replacement, it's crucial to ensure that the original key refilled into the new controller is identical to the previous one. However, since the key is transmitted in encrypted form, and to prevent replay issues, the encrypted key data is different each time it's issued, a key checksum is used to guarantee consistency. Before issuing the encrypted key for after-sales replacement, the front-end service system verifies the key checksum; only if they match will the key be issued. Inconsistencies indicate a problem with the derived key.

[0047] It should be noted that if there is a problem parsing the key after it is written into the vehicle, and an incorrect key is parsed, the key in the controller will not be the one issued by the platform. In this case, this check value can also be used to troubleshoot the problem.

[0048] Specifically, after the key management system generates a key, it sends the encrypted key to the front-end service system. The front-end service system verifies whether the key verification value on the vehicle side matches the key verification value on the cloud side. Only if they match will the key be issued. Subsequently, the diagnostic equipment uses the controller key to install a new key on the target vehicle's controller. The key verification value is a checksum, used to verify the key's consistency.

[0049] Different keys are derived for different controllers in the cloud. Since different controllers use symmetric keys for the same service, key consistency is ensured by the front-end service system. After the key management system issues the derived keys, it also calculates a checksum. The front-end service system verifies the checksum in the background. If the checksums match, it means the issued keys are consistent; if there is a discrepancy, it means the issued keys are inconsistent. This can be achieved by dividing the verification data into data blocks, summing the data blocks to obtain a total value, and then performing one or more methods such as modulo or complement operations on the total value to calculate the checksum.

[0050] Therefore, in this embodiment, the consistency of the issued keys is guaranteed by the front-end service system. By verifying whether the vehicle-side key verification value is consistent with the cloud-side key verification value, the condition for key issuance is met. This enables different keys to be derived for different vehicle models, different vehicles, and different controllers, ensuring a one-to-one correspondence between vehicle, service, and key, and improving the efficiency of key loading.

[0051] According to the controller key filling method proposed in this application embodiment, when the controller is replaced after the sale, the front-end service system and the diagnostic equipment communicate with each other. The entire communication process is encrypted. After logging in, the diagnostic equipment can apply for a key online from the front-end service system. At the same time, the front-end service system can obtain the vehicle-side information provided by the diagnostic equipment. When the key management system issues the key, the front-end service system ensures that the key issuance is consistent across all services, realizing one key per vehicle and one service. This not only improves the security of key filling when replacing the controller after the sale but also improves the key writing efficiency.

[0052] Figure 2 This is a schematic flowchart of a controller key filling method provided in an embodiment of this application.

[0053] This controller key filling method is applied to diagnostic equipment, such as... Figure 2 As shown, the controller key filling method includes the following steps:

[0054] In step S201, the target vehicle authorization code is obtained from the vehicle manufacturer.

[0055] The target vehicle authorization code is provided by the OEM factory and is used for authorized login of after-sales diagnostic equipment.

[0056] It is understood that the key filling method in this application embodiment is applied to diagnostic equipment that needs to obtain the target vehicle authorization code. This authorization code can be regarded as the vehicle's identity authentication, used to identify the vehicle, and can serve as a prerequisite for subsequent connection to the target vehicle.

[0057] In step S202, the target vehicle is verified using the authorization code and then connected to the target vehicle.

[0058] It is understood that, in this embodiment of the application, after obtaining the target vehicle authorization code from the supplier, the vehicle is verified using the authorization code. Only after successful authentication can the connection to the target vehicle be established, thus avoiding the risk of key leakage and ensuring the security of key transmission.

[0059] In step S203, the vehicle information of the target vehicle is obtained. After successful login based on the login data issued by the front-end service system, a communication connection is established between the front-end service system and the diagnostic device. The key filling request and the vehicle information of the target vehicle are uploaded to the front-end service system. The front-end service system responds to the key filling request, generates derived parameters, and uploads the derived parameters to the key management system. The key management system generates a derived key and a derived key verification value based on the derived parameters. It searches for the reference key verification value of the target vehicle based on the vehicle identifier. If the verification value of the derived key matches the verification value of the reference key, the encrypted text of the derived key is sent to the diagnostic device.

[0060] It should be noted that the front-end service system then responds to the key filling request and derives the controller key derivation parameters of the target vehicle based on the vehicle information. After the controller of the target vehicle is verified, the controller key is sent to the diagnostic device.

[0061] It is understood that after the diagnostic device in this embodiment connects to the target vehicle, it can obtain the vehicle-side information of the target vehicle and transmit the obtained vehicle-side information to the front-end service system. At the same time, it also transmits the key filling request. The whole process is done without human intervention, which greatly improves the efficiency of key filling.

[0062] In step S204, the new controller of the target vehicle is key-filled based on the ciphertext of the derived key.

[0063] It is understood that the key injection method in this application embodiment uses vehicle-side information transmitted by diagnostic equipment to determine the target vehicle, generates derived parameters based on the key injection request, and then issues the key for key injection. This ensures the consistency of key issuance and improves the efficiency and security of key injection.

[0064] It should be understood that the foregoing explanation of the embodiment of the controller key filling method applied to the front-end service system also applies to the embodiment of the method applied to the diagnostic equipment, and will not be repeated here.

[0065] According to the controller key filling method proposed in this application embodiment, when the controller is replaced after the sale, the front-end service system and the diagnostic equipment communicate with each other. The entire communication process is encrypted. After logging in, the diagnostic equipment can apply for a key online from the front-end service system. At the same time, the front-end service system can obtain the vehicle-side information provided by the diagnostic equipment. When the key management system issues the key, the front-end service system ensures that the key issuance is consistent across all services, realizing one key per vehicle and one service. This not only improves the security of key filling when replacing the controller after the sale but also improves the key writing efficiency.

[0066] The controller key injection method is illustrated below through a specific embodiment, such as... Figure 3 As shown, the specific steps are as follows:

[0067] 1. After-sales diagnostic equipment first obtains the vehicle's authorization code from the OEM factory through specific channels;

[0068] 2. After the after-sales diagnostic equipment passes the authorization code verification, it can connect to the vehicle, collect vehicle information, and transmit it to the front-end service system;

[0069] 3. The after-sales diagnostic equipment connects to the front-end service system through a specific connection, and the security of the communication link is ensured through two-way authentication;

[0070] 4. The after-sales diagnostic equipment sends a key filling request to the forward service system;

[0071] 5. The front-end service system ensures the consistency of key data sent to the controller that applies for the key by using information from the vehicle and cloud records.

[0072] 6. After receiving the key data from the front-end service system, the after-sales diagnostic equipment requests to write it to the vehicle.

[0073] 7. After receiving the key data, the vehicle-side device writes it into the controller and feeds back the key writing result;

[0074] 8. The after-sales diagnostic equipment writes the key and feeds back the result to the front-end service system, thus achieving a closed loop in the business.

[0075] In summary, when a controller needs to be replaced after the service is completed and the key needs to be refilled, the after-sales diagnostic equipment, after being authorized to log in, can apply for a key online from the OEM key management front-end service system. The front-end service system will then perform background verification to ensure the consistency of the issued key. This reduces the development logic of the controller, reduces the risk of bugs, improves the security of key filling, and also ensures the security and consistency of the controller replacement after the service is completed.

[0076] Next, the controller key filling device according to an embodiment of this application is described with reference to the accompanying drawings.

[0077] Figure 4 This is a block diagram illustrating the application of the controller key filling device in a front-end service system according to an embodiment of this application.

[0078] like Figure 4 As shown, the controller key filling device 10 includes: a storage module 401, a communication module 402, a first acquisition module 403, a generation module 404, and a distribution module 405.

[0079] The system comprises the following modules: storage module 401 stores the reference key verification value issued by the key management system when the original controller is keyed; communication module 402 establishes a communication connection between the front-end service system and the diagnostic device when the original controller is replaced with a new controller, provided the diagnostic device successfully logs in; first acquisition module 403 acquires the key keying request sent by the diagnostic device and the vehicle information of the target vehicle, identifying the original controller identifier, vehicle identifier, and supplier identifier in the vehicle information; generation module 404 responds to the key keying request, generates derived parameters based on the controller identifier, vehicle identifier, and supplier identifier, and uploads the derived parameters to the key management system, wherein the key management system generates a derived key and a derived key verification value based on the derived parameters; and distribution module 405 searches for the reference key verification value of the target vehicle based on the vehicle identifier. If the verification value of the derived key matches the reference key verification value, the encrypted text of the derived key is distributed to the diagnostic device, wherein the diagnostic device performs key keying on the new controller of the target vehicle based on the encrypted text of the derived key.

[0080] It should be noted that the foregoing explanation of the controller key filling method embodiment also applies to the controller key filling device of this embodiment, and will not be repeated here.

[0081] The controller key filling device proposed in this application enables communication between the front-end service system and the diagnostic equipment during after-sales controller replacement, with the entire communication process encrypted. After logging in, the diagnostic equipment can apply for a key online from the front-end service system, while the front-end service system can obtain vehicle-side information provided by the diagnostic equipment. Furthermore, when the key management system issues keys, the front-end service system ensures consistency across all services, achieving one key per vehicle and one service. This improves both the security of key filling during after-sales controller replacement and the efficiency of key writing.

[0082] Figure 5 This is a block diagram illustrating the application of the controller key filling device of this application to a diagnostic device.

[0083] like Figure 5 As shown, the controller key filling device 20 includes: a second acquisition module 501, a verification module 502, an upload module 503, and a filling module 504.

[0084] The second acquisition module 501 is used to obtain the target vehicle authorization code from the vehicle manufacturer; the verification module 502 is used to verify the target vehicle using the authorization code and then connect to the target vehicle; the upload module 503 is used to obtain the vehicle-side information of the target vehicle, and after successfully logging in according to the login data issued by the front-end service system, establish a communication connection between the front-end service system and the diagnostic equipment, and upload the key filling request and the vehicle-side information of the target vehicle to the front-end service system. The front-end service system responds to the key filling request, generates derived parameters, and uploads the derived parameters to the key management system. The key management system generates a derived key and a derived key verification value according to the derived parameters, and searches for the reference key verification value of the target vehicle according to the vehicle identifier. If the verification value of the derived key is consistent with the reference key verification value, the encrypted text of the derived key is sent to the diagnostic equipment; the filling module 504 is used to fill the new controller of the target vehicle with the key based on the encrypted text of the derived key.

[0085] It should be noted that the foregoing explanation of the controller key filling method embodiment also applies to the controller key filling device of this embodiment, and will not be repeated here.

[0086] The controller key filling device proposed in this application enables communication between the front-end service system and the diagnostic equipment during after-sales controller replacement, with the entire communication process encrypted. After logging in, the diagnostic equipment can apply for a key online from the front-end service system, while the front-end service system can obtain vehicle-side information provided by the diagnostic equipment. Furthermore, when the key management system issues keys, the front-end service system ensures consistency across all services, achieving one key per vehicle and one service. This improves both the security of key filling during after-sales controller replacement and the efficiency of key writing.

[0087] This application also provides a front-end service system, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the above-described controller key filling method.

[0088] This application also provides a diagnostic instrument, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the controller key filling method as described in the above embodiments.

[0089] This application also provides a vehicle, including a controller, which uses the above-described controller key filling method to fill in a key.

[0090] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0091] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0092] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0093] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any of the following techniques known in the art, or a combination thereof: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0094] Those skilled in the art will understand that all or part of the steps of the methods implementing the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0095] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for filling controller keys, characterized in that, The method is applied to a front-end service system, and the method includes the following steps: When the original controller is loaded with the key, the reference key verification value issued by the key management system is stored. When the original controller is replaced with a new controller, if the diagnostic device successfully logs in based on the login data issued by the front-end service system, a communication connection is established between the front-end service system and the diagnostic device. Obtain the key filling request sent by the diagnostic device and the vehicle information of the target vehicle, and identify the original controller identifier, vehicle identifier and supplier identifier in the vehicle information; In response to the key filling request, derived parameters are generated based on the controller identifier, the vehicle identifier, and the supplier identifier. The derived parameters are then uploaded to the key management system, which generates a derived key and a derived key verification value based on the derived parameters. The reference key verification value of the target vehicle is found based on the vehicle identifier. If the verification value of the derived key matches the reference key verification value, the ciphertext of the derived key is sent to the diagnostic device. The diagnostic device performs key loading on the new controller of the target vehicle based on the ciphertext of the derived key.

2. The controller key filling method according to claim 1, characterized in that, Both the front-end service system and the key management system are deployed in the cloud.

3. The controller key filling method according to claim 1, characterized in that, The front-end service system has at least one of the following functions: vehicle model management, supplier management, parts management, vehicle management, key management, and database management.

4. The controller key filling method according to claim 1, characterized in that, Establishing a communication connection between the front-end service system and the diagnostic device includes: The two-way authentication between the front-end service system and the diagnostic equipment is completed using the TLS protocol. After successful two-way authentication, a communication connection is established via the HTTPS protocol.

5. A method for filling controller keys, characterized in that, The method is applied to a diagnostic device, and the method includes the following steps: The target vehicle authorization code obtained from the vehicle manufacturer; After verifying the target vehicle using the authorization code, the connection is established with the target vehicle. After successfully logging in based on the login data issued by the front-end service system, a communication connection is established between the front-end service system and the diagnostic device. The vehicle-side information of the target vehicle is obtained, and a key loading request and the vehicle-side information of the target vehicle are uploaded to the front-end service system. The front-end service system responds to the key loading request, generates derived parameters based on the vehicle-side information of the target vehicle, and uploads the derived parameters to the key management system. The key management system generates a derived key and a derived key verification value based on the derived parameters. The front-end service system searches for the reference key verification value of the target vehicle based on the vehicle identifier. The reference key verification value is issued by the key management system when the original controller is loaded with the key. If the verification value of the derived key is consistent with the verification value of the reference key, the encrypted text of the derived key is sent to the diagnostic device. The new controller of the target vehicle is key-filled based on the ciphertext of the derived key.

6. A controller key filling device, characterized in that, The device is used in a front-end service system, wherein the device includes: The storage module is used to store the reference key verification value issued by the key management system when the original controller is loaded with keys; The communication module is used to establish a communication connection between the front-end service system and the diagnostic device when the original controller is replaced with a new controller, provided that the diagnostic device successfully logs in based on the login data issued by the front-end service system. The first acquisition module is used to acquire the key filling request sent by the diagnostic device and the vehicle information of the target vehicle, and to identify the original controller identifier, vehicle identifier and supplier identifier in the vehicle information; The generation module is used to respond to the key filling request, generate derived parameters based on the controller identifier, the vehicle identifier, and the supplier identifier, upload the derived parameters to the key management system, and the key management system generates a derived key and a derived key verification value based on the derived parameters. The delivery module is used to find the reference key verification value of the target vehicle based on the vehicle identifier. If the verification value of the derived key is consistent with the verification value of the reference key, the ciphertext of the derived key is delivered to the diagnostic device. The diagnostic device performs key loading on the new controller of the target vehicle based on the ciphertext of the derived key.

7. A controller key filling device, characterized in that, The device is used in diagnostic equipment, wherein the device includes: The second acquisition module is used to obtain the target vehicle authorization code from the vehicle manufacturer; The verification module is used to verify the target vehicle using the authorization code and then connect to the target vehicle. The upload module is used to establish a communication connection between the front-end service system and the diagnostic device after successful login based on the login data issued by the front-end service system, obtain the vehicle terminal information of the target vehicle, and upload the key filling request and the vehicle terminal information of the target vehicle to the front-end service system. The front-end service system responds to the key filling request, generates derived parameters, and uploads the derived parameters to the key management system. The key management system generates a derived key and a derived key verification value based on the derived parameters. The front-end service system searches for the reference key verification value of the target vehicle based on the vehicle identifier. The reference key verification value is issued by the key management system when the original controller is filled with the key. If the verification value of the derived key is consistent with the verification value of the reference key, the encrypted text of the derived key is sent to the diagnostic device. A filling module is used to fill a new controller for the target vehicle with a key based on the ciphertext of the derived key.

8. A front-end service system, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the controller key filling method according to any one of claims 1-4.

9. A diagnostic instrument, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the controller key filling method of claim 5.

10. A vehicle, characterized in that, The controller includes a controller that performs key filling based on the controller key filling method according to any one of claims 1-5.

Images