Diagnostic instrument security access system and method and electronic equipment
By using a server to generate a token in the intelligent Internet of Vehicles remote diagnostic system and passing it to the target vehicle end by the diagnostic device, the target vehicle end grants access rights based on the token, solving the security risk of excessive permissions after the diagnostic device obtains the key in the prior art, and improving the security of the system.
Patent Information
- Application Number
- CN202411816882.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-10
- Publication Date
- 2025-03-18
AI Technical Summary
In the existing smart Internet of Vehicles remote diagnosis security access, the diagnostic device can access all information on the vehicle after obtaining the communication key, which poses a security risk, because the identities of different diagnostic devices are different, resulting in insufficient permission management.
The token is generated through the server based on the number, identity information and private key of the diagnostic device, and the diagnostic device sends the token to the target vehicle end. The target vehicle end grants corresponding access rights based on the token to restrict the access rights of the diagnostic device.
It improves the security of the diagnostic device's secure access, ensures that the diagnostic devices of different identities have different permissions when accessing the target vehicle, reducing security risks.
Smart Images
Figure CN119652620A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of secure access technology, and in particular to a diagnostic instrument secure access system, method, and electronic device. Background Art
[0002] The Internet of Vehicles is an IoT technology that can provide remote control services related to vehicle safety, including remote diagnostic and secure access to vehicles, which can bring users a safe and convenient driving experience.
[0003] In the current intelligent vehicle network remote diagnosis security access, the diagnostic instrument is mainly used to request information from the vehicle side, and then obtain the communication key to unlock access to the vehicle side.
[0004] However, in the current diagnostic security access, once the diagnostic instrument obtains the communication key, it can access all the information on the vehicle side, but different diagnostic instruments have different identities, so the method of allowing all diagnostic instruments to obtain all permissions poses a security risk. Summary of the invention
[0005] The embodiments of the present invention provide a diagnostic instrument security access system, method and electronic device to solve or alleviate the technical problems in the prior art.
[0006] The technical solution adopted by the present invention is:
[0007] In a first aspect, an embodiment of the present application provides a diagnostic instrument security access system, comprising: a diagnostic instrument, used to obtain the number of a target vehicle end and upload it to a server; the server, used to generate a token based on the number, the identity information of the diagnostic instrument and a private key, and send it to the diagnostic instrument; the diagnostic instrument, used to send the token to the target vehicle end; the target vehicle end, used to grant corresponding access rights to the diagnostic instrument based on the token, so that the diagnostic instrument can access the target vehicle end within the access rights.
[0008] Optionally, in one embodiment, the target vehicle is used to verify the integrity and time validity of the token and the correctness of the identity information of the diagnostic instrument, and grant the access rights to the diagnostic instrument based on the token after the verification is passed.
[0009] Optionally, in one embodiment, the target vehicle end is used to decrypt the token according to a stored key, obtain permission information, and grant the access permission to the diagnostic instrument according to the permission information.
[0010] Optionally, in one embodiment, the server is used to send an updated key to the target vehicle according to a preset key period; the target vehicle is used to update the stored key according to the received updated key, and send the key update result to the server after the key update is completed.
[0011] Optionally, in one embodiment, the server is used to count the number uploaded by the diagnostic instrument to request a token, and when the count value reaches a count threshold, send an updated key to the target vehicle end; the target vehicle end is used to update the stored key according to the received updated key, and send the key update result to the server after the key update is completed.
[0012] Optionally, in one embodiment, the identity information of the diagnostic instrument and the serial number of the target vehicle are unique.
[0013] In the second aspect, an embodiment of the present application provides a diagnostic instrument security access method, which is applied to a server and includes: receiving the number of a target vehicle end sent by the diagnostic instrument; generating a token based on the number, the identity information of the diagnostic instrument and a private key and sending it to the diagnostic instrument, so that the diagnostic instrument sends the token to the target vehicle end, obtains the access permission granted by the target vehicle end based on the token, and then accesses the target vehicle end within the access permission.
[0014] Optionally, in one embodiment, the process of secure access of the diagnostic instrument may also include: counting the number of times the diagnostic instrument uploads the number to request a token to obtain a count value; when the count value reaches a count threshold, sending an update key to the target vehicle end, so that the target vehicle end updates the stored key according to the received update key, and sending the key update result to the server after the key update is completed.
[0015] Optionally, in one embodiment, the diagnostic instrument's secure access process may also include: sending an updated key to the target vehicle according to a preset key period, so that the target vehicle updates the stored key according to the received updated key, and sending the key update result to the server after the key update is completed.
[0016] In a third aspect, an embodiment of the present application provides an electronic device having a computer program stored thereon, which, when executed by a processor, implements a diagnostic instrument security access method as described in any one of the second aspects of the embodiments.
[0017] A processor, a communication interface, a memory and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations corresponding to the diagnostic instrument security access method described in any one of the second aspects of the embodiment.
[0018] From the above scheme, it can be seen that by generating a token based on the number, identity information of the diagnostic instrument and private key through the server, different access rights can be set for diagnostic instruments with different identity information when accessing the target vehicle, thereby improving the security of secure access to the diagnostic instrument. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 A schematic diagram of a diagnostic instrument security access system according to an embodiment of the present application;
[0020] Figure 2 A schematic diagram of a diagnostic instrument security access system according to another embodiment of the present application;
[0021] Figure 3 A flowchart of a diagnostic instrument security access method according to an embodiment of the present application;
[0022] Figure 4 A schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0023] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.
[0024] Figure 1 This is a schematic diagram of a diagnostic instrument security access system according to an embodiment of the present application. Figure 1 As shown, the diagnostic instrument security access system 100 includes:
[0025] The diagnostic instrument 101 is used to obtain the serial number of the target vehicle end 102 and upload it to the server 103. The server 103 is used to generate a token according to the serial number, the identity information of the diagnostic instrument 101 and the private key and send it to the diagnostic instrument 101. The diagnostic instrument 101 is used to send the token to the target vehicle end 102. The target vehicle end 102 is used to grant the diagnostic instrument 101 corresponding access rights according to the token, so that the diagnostic instrument 101 can access the target vehicle end within the access rights.
[0026] In order to achieve secure access to the diagnostic instrument, the diagnostic instrument 101 will first obtain the number (partnumber) of the target vehicle end 102 that needs to be accessed, and then the diagnostic instrument 101 will upload the partnumber to the server 103. The server 103 can be deployed on a local server or in the cloud. After obtaining the partnumber, the server 103 will generate a token based on the partnumber, the identity information of the diagnostic instrument 101 that sent the partnumber, and the private key stored in itself, and send the token to the diagnostic instrument 101 that sent the partnumber. The diagnostic instrument 101 sends the token to the target vehicle end 102. After receiving the token, the target vehicle end 102 will grant the diagnostic instrument 101 corresponding access rights based on the information included in the token. The diagnostic instrument 101 with the access rights can at least partially access the information of the target vehicle end 102. After being granted the access rights, the diagnostic instrument 101 can access the target vehicle end 102 to achieve the corresponding access function.
[0027] Specifically, the identity information of the diagnostic instrument 101 and the serial number of the target vehicle 102 are unique, so that the erroneous granting of access rights that do not match the diagnostic instrument 101 can be avoided.
[0028] In an embodiment of the present application, the server 103 generates a token based on the number, identity information of the diagnostic instrument 101 and a private key, and can set different access rights for diagnostic instruments 101 with different identity information when accessing the target vehicle end 102, thereby improving the security of secure access to the diagnostic instrument.
[0029] In one possible implementation, the target vehicle 102 is used to verify the integrity and time validity of the token and the correctness of the identity information of the diagnostic instrument 101, and grant access rights to the diagnostic instrument 101 based on the token after the verification.
[0030] like Figure 2 As shown, the target vehicle end 102 may include a security diagnostic module 1021. After receiving the token sent by the diagnostic instrument 101, the target vehicle end 102 can verify the integrity and time validity of the token through the security diagnostic module 1021 (SecurityDiag). In addition, the correctness of the identity information of the diagnostic instrument 101 will also be verified. After all the above verifications are passed, the target vehicle end 102 will grant access rights to the diagnostic instrument 101 based on the token.
[0031] In the embodiment of the present application, the target vehicle 102 can ensure that the correct access rights are granted to the correct diagnostic instrument 101 by verifying the integrity and time validity of the token and the correctness of the identity information of the diagnostic instrument 101, thereby further improving the security of the diagnostic instrument's secure access.
[0032] In one possible implementation, the target vehicle 102 is used to decrypt the token according to the stored key, obtain the permission information, and grant access rights to the diagnostic instrument 101 according to the permission information.
[0033] A key is stored in the target vehicle end 102, and the key is an associated key with a private key in the server. The token obtained after encryption with the private key of the server 103 can be decrypted by the target vehicle end 102 using the key stored therein. Specifically, the target vehicle end 102 can be decrypted by the security diagnosis module 1021, and the security diagnosis module 1021 calls the hardware security module 1022 (Hardware Security Module) for decryption, thereby obtaining permission information indicating that the diagnostic instrument 101 should be granted. The hardware security module 1022 will grant corresponding access rights to the diagnostic instrument 101 based on the permission information.
[0034] In the embodiment of the present application, asymmetric encryption is implemented by performing private key encryption through the server 103 and decrypting the target vehicle 102 according to the stored key, thereby avoiding leakage of authority due to exhaustive attacks.
[0035] In a possible implementation, the server 103 is used to send an update key to the target vehicle 102 according to a preset key period. The target vehicle 102 is used to update the stored key according to the received update key, and send a key update result to the server 103 after the key update is completed.
[0036] The server 103 will send a key to the target vehicle end 102 when the target vehicle end 102 leaves the factory, so that the target vehicle end 102 can store it. In order to reduce the complexity of production and the difficulty of communication, the target vehicle end 102 is usually not given an overly complex key. Therefore, after a period of use, the server 103 needs to update the key in the target vehicle end 102. Specifically, the server 103 can send an updated key to the target vehicle end 102 according to a preset key period. The preset key period can be a freely configurable period such as 15 days or 20 days. After receiving the updated key, the target vehicle end 102 will use the updated key to update the stored key and discard or seal the old key. After the target vehicle end 102 completes the key update, it will send the key update result to the server 103. The server 103 can determine whether the target vehicle end 102 has correctly completed the key update based on the key update result. After confirming that the target vehicle end 102 has completed the key update, the server 103 will determine that the target vehicle end 102 has entered a new key period.
[0037] In the embodiment of the present application, the server 103 updates the key stored in the target vehicle end 102 by sending an updated key to the target vehicle end 102 according to a preset key period, which can further improve the security of the diagnostic instrument's secure access.
[0038] In a possible implementation, the server 103 is used to count the number of token requests uploaded by the diagnostic instrument 101, and when the count value reaches the count threshold, send the update key to the target vehicle end 102. The target vehicle end 102 is used to update the stored key according to the received update key, and send the key update result to the server 103 after the key update is completed.
[0039] Each time the diagnostic instrument 101 uploads the serial number of the target vehicle 102 to the server 103 to request a token, the server 103 will count. When the count value reaches the count threshold, such as 100, 120, etc., which are configured according to the requirements, the server 103 will send an update key to the target vehicle 102. After receiving the update key, the target vehicle 102 will use the update key to update the stored key, and discard or seal the old key. After the target vehicle 102 completes the key update, it will send the key update result to the server 103. The server 103 can determine whether the target vehicle 102 has correctly completed the key update based on the key update result. After confirming that the target vehicle 102 has completed the key update, the server 103 will clear the count.
[0040] In the embodiment of the present application, the server 103 can avoid exhaustive attacks by counting each time the diagnostic instrument 101 uploads the number of the target vehicle end 102 to the server 103 to request a token, and updating the key stored in the target vehicle end 102 when the count value reaches the count threshold. When the attacker is far from being able to exhaustively enumerate the key of the target vehicle end 102, the key of the target vehicle end 102 is updated, thereby improving the security of the system.
[0041] Figure 3 This is a flow chart of a diagnostic instrument security access method according to an embodiment of the present application, such as Figure 3 As shown, the diagnostic instrument security access method applied to the server includes the following steps:
[0042] Step 301, receiving the target vehicle number sent by the diagnostic instrument.
[0043] Step 302, generate a token according to the serial number, the identity information of the diagnostic instrument and the private key and send it to the diagnostic instrument, so that the diagnostic instrument sends the token to the target vehicle end, obtains the access permission granted by the target vehicle end according to the token, and then accesses the target vehicle end within the access permission.
[0044] In order to achieve secure access to the diagnostic instrument, the diagnostic instrument will first obtain the number of the target vehicle that needs to be accessed, and then upload the number to the server. The server can be deployed on a local server or in the cloud. After the server obtains the number of the target vehicle, it will generate a token based on the number of the target vehicle, the identity information of the diagnostic instrument that sends the number of the target vehicle, and the private key stored in itself, and send the token to the diagnostic instrument that sent the number of the target vehicle. The diagnostic instrument sends the token to the target vehicle. After receiving the token, the target vehicle will grant the corresponding access rights to the diagnostic instrument based on the information included in the token. The diagnostic instrument can at least partially access the information of the target vehicle with this access right. After being granted the access right, the diagnostic instrument can access the target vehicle to achieve the corresponding access function.
[0045] In an embodiment of the present application, the server generates a token based on the number, identity information of the diagnostic instrument and a private key, and can set different access rights for diagnostic instruments with different identity information when accessing the target vehicle, thereby improving the security of secure access to the diagnostic instrument.
[0046] In one possible implementation, the process of secure access to the diagnostic instrument may also include: counting the number of times the diagnostic instrument uploads a number to request a token, obtaining a count value, and when the count value reaches a count threshold, sending an update key to the target vehicle so that the target vehicle updates the stored key based on the received update key, and sending the key update result to the server after the key update is completed.
[0047] Each time the diagnostic instrument uploads the target vehicle number to the server to request a token, the server will count. When the count value reaches the count threshold, the server will send an update key to the target vehicle. After receiving the update key, the target vehicle will use the update key to update the stored key and discard or seal the old key. After the target vehicle completes the key update, it will send the key update result to the server. The server can determine whether the target vehicle has correctly completed the key update based on the key update result. After confirming that the target vehicle has completed the key update, the server will clear the count.
[0048] In an embodiment of the present application, the server can avoid exhaustive attacks by counting each time the diagnostic instrument uploads the target vehicle number to the server to request a token, and updating the key stored in the target vehicle when the count value reaches the count threshold. When the attacker is far from being able to exhaustively enumerate the key of the target vehicle, the key of the target vehicle 102 is updated, thereby improving the security of the system.
[0049] In one possible implementation, the diagnostic instrument's secure access process may also include: sending an updated key to the target vehicle according to a preset key period, so that the target vehicle updates the stored key according to the received updated key, and sending the key update result to the server after the key update is completed.
[0050] The server will send a key to the target vehicle when it leaves the factory so that the target vehicle can store it. In order to reduce the complexity of production and the difficulty of communication, the target vehicle is usually not given an overly complex key. Therefore, after a period of use, the server needs to update the key in the target vehicle. Specifically, the server can send an updated key to the target vehicle according to a preset key period. The preset key period can be a freely configurable period such as 15 days or 20 days. After receiving the updated key, the target vehicle will use the updated key to update the stored key and discard or seal the old key. After the target vehicle completes the key update, it will send the key update result to the server. The server can determine whether the target vehicle has correctly completed the key update based on the key update result. After confirming that the target vehicle has completed the key update, the server will determine that the target vehicle has entered a new key period.
[0051] In an embodiment of the present application, the server updates the key stored in the target vehicle by sending an updated key to the target vehicle according to a preset key period, which can further improve the security of the diagnostic instrument's secure access.
[0052] Figure 4 This is a schematic diagram of an electronic device according to an embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device. Figure 4 As shown, the electronic device 400 may include: a processor 401, a communications interface 402, a memory 403, and a communications bus 404. Among them:
[0053] The processor 401 , the communication interface 402 , and the memory 403 communicate with each other via the communication bus 404 .
[0054] The communication interface 402 is used to communicate with other electronic devices or servers.
[0055] The processor 401 is used to execute the program 405, and specifically can execute the relevant steps in any method embodiment of the aforementioned multiple method embodiments.
[0056] Specifically, the program 405 may include program codes, which include computer operation instructions.
[0057] The processor 401 may be a CPU, or an application specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.
[0058] The memory 403 is used to store the program 405. The memory 403 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0059] The program 405 can be specifically used to enable the processor 401 to execute any one of the multiple method embodiments in the aforementioned embodiments.
[0060] The specific implementation of each step in program 405 can refer to the corresponding description of the corresponding steps and units in the above-mentioned diagnostic instrument security access method embodiment, which will not be repeated here. The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described equipment and modules can refer to the corresponding process description in the above-mentioned method embodiment, which will not be repeated here.
[0061] The electronic device of the embodiment of the present application generates a token through a server according to the number, identity information of the diagnostic instrument and a private key, and can set different access rights for diagnostic instruments with different identity information when accessing the target vehicle, thereby improving the security of secure access to the diagnostic instrument.
[0062] The present application also provides a computer-readable storage medium storing instructions for causing a machine to execute any of the methods in the multiple method embodiments described herein. Specifically, a system or device equipped with a storage medium may be provided, on which a software program code implementing the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device is enabled to read and execute the program code stored in the storage medium.
[0063] In this case, the program code read from the storage medium itself can implement the function of any one of the above embodiments, so the program code and the storage medium storing the program code constitute part of the present application.
[0064] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.
[0065] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to perform any corresponding operation in the above-mentioned multiple method embodiments.
[0066] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.
[0067] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as a computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a special-purpose processor or programmable or special-purpose hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the method shown here, the execution of the code converts the general-purpose computer into a special-purpose computer for executing the method shown here.
[0068] It should be noted that not all steps and modules in the above-mentioned processes and system structure diagrams are necessary, and some steps or modules can be ignored according to actual needs. The execution order of each step is not fixed and can be adjusted as needed. The system structure described in the above-mentioned embodiments can be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by multiple physical entities, or some components in multiple independent devices may be implemented together.
[0069] In the above embodiments, the hardware module can be implemented mechanically or electrically. For example, a hardware module can include permanent dedicated circuits or logic (such as special processors, FPGA or ASIC) to complete the corresponding operation. The hardware module can also include programmable logic or circuits (such as general-purpose processors or other programmable processors), which can be temporarily set by software to complete the corresponding operation. The specific implementation method (mechanical method, or dedicated permanent circuit, or temporarily set circuit) can be determined based on cost and time considerations.
[0070] The present application is presented and described in detail above through the accompanying drawings and preferred embodiments; however, the present application is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the code review methods in the above different embodiments can be combined to obtain more embodiments of the present application, and these embodiments are also within the scope of protection of the present application.
Claims
1. A diagnostic instrument security access system, characterized in that: include: Diagnostic instrument, used to obtain the target vehicle ID and upload it to the server; The server is used to generate a token according to the number, the identity information of the diagnostic instrument and a private key, and send the token to the diagnostic instrument; The diagnostic instrument is used to send the token to the target vehicle end; The target vehicle end is used to grant corresponding access rights to the diagnostic instrument according to the token, so that the diagnostic instrument can access the target vehicle end within the access rights.
2. The system according to claim 1, characterized in that The target vehicle end is used to verify the integrity and time validity of the token and the correctness of the identity information of the diagnostic instrument, and grant the access right to the diagnostic instrument according to the token after the verification is passed.
3. The system according to claim 1, characterized in that The target vehicle end is used to decrypt the token according to the stored key, obtain the authority information, and grant the access right to the diagnostic instrument according to the authority information.
4. The system according to claim 3, characterized in that The server is used to send an update key to the target vehicle terminal according to a preset key period; The target vehicle end is used to update the stored key according to the received update key, and send the key update result to the server after the key update is completed.
5. The system according to claim 3, characterized in that The server is used to count the number uploaded by the diagnostic instrument to request the token, and when the count value reaches the count threshold, send an update key to the target vehicle end; The target vehicle end is used to update the stored key according to the received update key, and send the key update result to the server after the key update is completed.
6. The system according to claim 1, characterized in that The identity information of the diagnostic instrument and the serial number of the target vehicle are unique.
7. A diagnostic instrument security access method, applied to a server, characterized in that: include: Receive the target vehicle number sent by the diagnostic instrument; A token is generated according to the number, the identity information of the diagnostic instrument and a private key and sent to the diagnostic instrument, so that the diagnostic instrument sends the token to the target vehicle end, obtains the access permission granted by the target vehicle end according to the token, and then accesses the target vehicle end within the access permission.
8. The method according to claim 7, characterized in that The method further comprises: Counting the number of times the diagnostic instrument uploads the serial number to request a token, and obtaining a count value; When the count value reaches the count threshold, an update key is sent to the target vehicle end, so that the target vehicle end updates the stored key according to the received update key, and sends the key update result to the server after the key update is completed.
9. The method according to claim 7, characterized in that: The method further comprises: The target vehicle terminal sends an updated key to the target vehicle terminal according to a preset key period, so that the target vehicle terminal updates the stored key according to the received updated key, and sends a key update result to the server after the key update is completed.
10. An electronic device, comprising: A processor, a communication interface, a memory and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the diagnostic instrument security access method as described in any one of claims 7-9.