Diagnostic equipment authentication method, computer equipment and computer readable storage medium
By receiving unique hardware identifiers and generating security tokens after the security authentication of the automotive diagnostic equipment, the security authentication process of the diagnostic equipment is simplified, the problems of complex authentication and high resource utilization in the existing technology are solved, and diagnostic efficiency and safety are improved sex.
Patent Information
- Application Number
- CN202411055925.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-01
- Publication Date
- 2024-11-08
AI Technical Summary
The safety certification process of existing automotive diagnostic equipment is complex, has a lot of resources, takes up time, and has short time, resulting in low certification efficiency when used frequently, affecting diagnostic efficiency.
By receiving a unique hardware identifier within the preset time after the diagnostic device passes security authentication and storing it into the certified directory, a security token is generated, and subsequent security authentication is performed based on this information, simplifying the authentication process and improving efficiency.
On the premise of ensuring safety, the safety certification process of diagnostic equipment is simplified, the certification and diagnosis efficiency is improved, resource utilization is reduced, and efficiency problems caused by frequent certification are avoided.
Smart Images

Figure CN118916863A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the technical field of device authentication, and in particular, relates to a diagnostic device authentication method, a computer device, and a computer-readable storage medium. Background Art
[0002] In order to facilitate vehicle fault detection, the use of automobile diagnostic equipment is becoming more and more popular. Automobile diagnostic equipment is a portable intelligent automobile fault self-test device used to detect automobile faults. Users can use it to quickly read the faults in the automobile electronic control system and display the fault information through the LCD screen to quickly find out the location and cause of the fault.
[0003] Considering the safety of the vehicle, before establishing a communication connection with the diagnostic device, the diagnostic device needs to be authenticated to ensure the safety of the diagnostic device. The current authentication process is relatively complicated, requires more resources, and takes a lot of time. The validity period of each authentication is relatively short. Therefore, if the diagnostic device is used to frequently diagnose a vehicle, it needs to be authenticated multiple times. The authentication efficiency is low, which not only takes up resources but also affects the diagnostic efficiency. Summary of the invention
[0004] In view of this, the embodiments of the present application provide a diagnostic device authentication method, a computer device, and a computer-readable storage medium, which can simplify the security authentication of the diagnostic device while ensuring reliability, and improve the authentication efficiency and diagnosis efficiency.
[0005] A first aspect of an embodiment of the present application provides a diagnostic device authentication method, which is applied to a central gateway, including:
[0006] Within a first preset time after the diagnostic device passes the first security authentication, if a unique hardware identifier sent by the diagnostic device is received, the unique hardware identifier and its validity period are stored in an authenticated directory;
[0007] If a unique hardware identifier sent by a diagnostic device is received, and the unique hardware identifier is in the authenticated directory and within the validity period, then determining that the diagnostic device is safe;
[0008] If a unique hardware identifier sent by a diagnostic device is received and the unique hardware identifier is not in the authenticated directory or is not within the validity period, a first authentication result indicating authentication failure is sent to the diagnostic device.
[0009] A second aspect of an embodiment of the present application provides a diagnostic device authentication method, which is applied to a central gateway, including:
[0010] Within a first preset time after the diagnostic device passes the first security authentication, if a unique hardware identifier sent by the diagnostic device is received, generating a security token according to the unique hardware identifier;
[0011] storing the unique hardware identifier, the security token and the validity period in an authenticated directory; the unique hardware identifier and the security token correspond one to one;
[0012] sending the security token to the diagnostic device;
[0013] If a token authentication request sent by a diagnostic device is received, token security authentication is performed on the diagnostic device based on the token authentication request; the token authentication request includes a unique hardware identifier of the diagnostic device and a security token.
[0014] In an implementation of the second aspect, performing token security authentication on the diagnostic device based on the token authentication request includes:
[0015] If the security token in the token authentication request is within the validity period and its corresponding unique hardware identifier in the authenticated directory is consistent with the unique hardware identifier in the token authentication request, then determining that the diagnostic device is secure;
[0016] If the security token in the token authentication request is not in the authenticated directory or is not within the validity period, or its corresponding unique hardware identifier in the authenticated directory is inconsistent with the unique hardware identifier in the token authentication request, a first authentication result indicating authentication failure is sent to the diagnostic device.
[0017] In an implementation of the second aspect, the unique hardware identifier includes at least one of a serial number of the diagnostic device, a hard disk number, and a MAC address of a network card.
[0018] A third aspect of the embodiments of the present application provides a diagnostic device authentication method, which is applied to a diagnostic device, including:
[0019] Sending a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication;
[0020] If an authentication command is detected, the unique hardware identifier is sent to the target central gateway.
[0021] A fourth aspect of the present application provides a diagnostic device authentication method, which is applied to a diagnostic device, including:
[0022] Sending a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication;
[0023] Receive the security token sent by the target gateway and store it in the token library;
[0024] If an authentication instruction is detected, a token authentication request is sent to the target central gateway; the token authentication request includes a unique hardware identifier and the security token.
[0025] In an implementation of the fourth aspect, after sending the token authentication request to the target central gateway, the method further includes:
[0026] If a first authentication result indicating authentication failure is received from the target central gateway, the target central gateway is requested to perform a first security authentication.
[0027] In an implementation of the fourth aspect, the receiving the security token sent by the target gateway and storing it in a token library includes:
[0028] Receive a security token sent by the target gateway, and store the target gateway identifier and the security token in a token library, wherein the target gateway identifier corresponds to the security token one by one;
[0029] The token authentication request includes a unique hardware identifier and a security token corresponding to the target gateway identifier in the token repository.
[0030] A fifth aspect of the embodiments of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor.
[0031] When the computer device is a central gateway, the processor implements the steps of the method described in the first aspect to the second aspect when executing the computer program;
[0032] When the computer device is a diagnostic device, the processor implements the steps of the method described in the third aspect to the fourth aspect when executing the computer program.
[0033] A sixth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in the first to fourth aspects are implemented.
[0034] The beneficial effect of the first aspect of the embodiment of the present application is: by receiving a unique hardware identifier sent by the diagnostic device within a first preset time after the diagnostic device passes the first security authentication, the unique hardware identifier and its validity period are stored in an authenticated directory to ensure the reliability of the hardware identifiers in the authenticated directory, and subsequently by receiving the hardware identifier sent by the diagnostic device and judging whether the diagnostic device is safe based on the hardware identifier and its validity period, the security authentication of the diagnostic device is simplified while ensuring reliability, thereby improving authentication efficiency and diagnosis efficiency.
[0035] It can be understood that the beneficial effects of the second to sixth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0037] Figure 1 This is a schematic diagram of the implementation process of the first diagnostic device authentication method provided in the embodiment of the present application;
[0038] Figure 2 It is a schematic diagram of the implementation process of the second diagnostic device authentication method provided in the embodiment of the present application;
[0039] Figure 3 It is a schematic diagram of the implementation process of the third diagnostic device authentication method provided in the embodiment of the present application;
[0040] Figure 4 It is a schematic diagram of the implementation flow of the fourth diagnostic device authentication method provided in the embodiment of the present application;
[0041] Figure 5 is a schematic diagram of a first diagnostic device authentication system provided in an embodiment of the present application;
[0042] Figure 6 is a schematic diagram of a second diagnostic device authentication system provided in an embodiment of the present application;
[0043] Figure 7 It is a schematic diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0044] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0045] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.
[0046] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0047] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.
[0048] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.
[0049] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.
[0050] The embodiment of the present application provides a diagnostic device authentication method, which is applied to a central gateway and is used to simplify the security authentication of a diagnostic device. The method receives a unique hardware identifier sent by a diagnostic device within a first preset time after the diagnostic device passes the first security authentication, and stores the unique hardware identifier and its validity period in an authenticated directory, thereby ensuring the reliability of the hardware identifier in the authenticated directory. Subsequently, the method receives the hardware identifier sent by the diagnostic device, and determines whether the diagnostic device is safe based on the hardware identifier and its validity period, thereby simplifying the security authentication of the diagnostic device and improving the authentication efficiency and the diagnosis efficiency while ensuring reliability.
[0051] Considering the safety of the vehicle, before diagnosing the vehicle through the diagnostic equipment, the vehicle's central gateway needs to first perform security authentication on the diagnostic equipment. Only after the diagnostic equipment passes the security authentication can the communication connection between the diagnostic equipment and the central gateway be established. In order to further improve safety, the security authentication has a certain time limit, generally 5 minutes or 10 minutes. After the time limit expires, the diagnostic equipment needs to be re-authenticated.
[0052] In one embodiment of the present application, the central gateway of the vehicle performs security authentication on the diagnostic device through the first security authentication. The first security authentication includes one-way or two-way digital certificate verification, symmetric and asymmetric encryption key negotiation, data key encryption and data challenge, etc., which require a lot of resources, such as central processing unit (CPU) resources, and take a long time. Each time the diagnostic device successfully passes the first security authentication, it has a time limit of 5 minutes. After the diagnostic device passes the first security authentication, a communication connection with a time limit of five minutes will be established between the diagnostic device and the central gateway. After 5 minutes, the communication connection will be disconnected, and the diagnostic device needs to perform the first security authentication again to ensure security before it can establish a communication connection with a time limit of 5 minutes again. It can be understood that the above-mentioned embodiment has certain limitations. For example, in some scenarios, it is necessary to use the diagnostic device to perform long-term maintenance diagnosis on the vehicle. The maintenance time is long, which may be several hours or even a day, and the time limit of each first security authentication is short, which leads to the need to continuously perform the first security authentication during the entire maintenance diagnosis process to maintain communication between the diagnostic device and the central gateway. However, the first security authentication requires more resources and consumes more time. Frequent first security authentication will lead to resource shortage in the diagnosis process, affect the diagnosis efficiency, and lead to a longer diagnosis time.
[0053] like Figure 1 As shown, the embodiment of the present application provides a diagnostic device authentication method applied to a central gateway, including the following steps S11 to S13:
[0054] Step S11, within a first preset time after the diagnostic device passes the first security authentication, if a unique hardware identifier sent by the diagnostic device is received, the unique hardware identifier and its validity period are stored in an authenticated directory.
[0055] In the application, the first preset time is generally a few seconds to tens of seconds, and the longest time does not exceed the first security authentication time limit, so as to ensure that within the first preset time after the diagnostic device passes the first security authentication, if the unique hardware identifier sent by the diagnostic device is received, the unique hardware identifier is a safe hardware identifier of the diagnostic device, and its security can be guaranteed. After ensuring the security of the received unique hardware identifier, the unique hardware identifier and its validity period are stored in the authenticated directory. In the application, the validity period of the unique hardware identifier in the authenticated directory can be set to a fixed time, such as 12 hours; the validity period can also be generated according to an intelligent generation strategy, for example, automatically generating the latest validity period of the unique hardware identifier based on the historical validity period of the unique hardware identifier.
[0056] In the application, after the diagnostic device passes the first security authentication, the central gateway will establish a communication connection with the diagnostic device. The communication connection has a certain validity period, which can generally be the same as the first security authentication period.
[0057] Step S12: If a unique hardware identifier sent by the diagnostic device is received, and the unique hardware identifier is in the authenticated directory and within the validity period, it is determined that the diagnostic device is safe.
[0058] In the application, if the received unique hardware identifier of the diagnostic device is in the authenticated directory and is within the validity period, it means that the diagnostic device has passed the first security authentication and is safe. Furthermore, if the unique hardware identifier is within the validity period, it can now be judged as a safe device. If the diagnostic device is a safe device, a communication connection is established with the diagnostic device, and the validity period of the communication connection can be the same as the validity period of the first security authentication.
[0059] Step S13: If a unique hardware identifier sent by the diagnostic device is received and the unique hardware identifier is not in the authenticated directory or is not within the validity period, a first authentication result indicating authentication failure is sent to the diagnostic device.
[0060] In the application, if the unique hardware identifier sent by the received diagnostic device is not in the authenticated directory, then the diagnostic device has not passed the first security authentication or has not sent the unique hardware identifier to the central gateway within the first preset time after passing the first security authentication; if the unique hardware identifier sent by the received diagnostic device is in the authenticated directory but is not within the validity period, it means that the diagnostic device was a safe device but the unique hardware identifier is invalid; in both of the above situations, the diagnostic device cannot be judged as a safe device, so the diagnostic device is judged as an unsafe device, and the first authentication result indicating the authentication failure is sent to the diagnostic device. After receiving the first authentication result indicating the authentication failure, the diagnostic device can send other unique hardware identifiers to the central gateway or re-perform the first security authentication.
[0061] It can be understood that in the above method, each time the diagnostic device passes the first security authentication, within the first preset time, the central gateway records the unique hardware identifier of the diagnostic device and its validity period, thereby realizing security verification of the diagnostic device through the unique hardware identifier, solving the problem of frequent first security authentication of the diagnostic device, occupying resources and affecting diagnostic efficiency, and realizing efficient and reliable security authentication of the diagnostic device.
[0062] In one embodiment, the unique hardware identifier includes at least one of a serial number of the diagnostic device, a hard disk number, and a MAC address of a network card.
[0063] In the application, the unique hardware identifier includes a unique and unmodifiable hardware identifier, such as the serial number of the diagnostic device, the hard disk number of the diagnostic device, the MAC (Media Access Control Address) of the network card, etc. Therefore, the unique hardware identifier is also unique and unmodifiable. In the application, the diagnostic device may need to replace the hardware. For example, if the network card fails, the old network card needs to be removed and replaced with a new one. If the old network card replaced in the above scenario is installed on a malicious diagnostic device, it may cause the malicious diagnostic device to communicate with the central gateway based on the old network card, posing a safety hazard to the vehicle. Therefore, the unique hardware identifier may include two or more unmodifiable hardware identifiers to reduce the probability of the above situation and improve the reliability of security verification of the diagnostic device based on the unique hardware identifier.
[0064] In an application, after step S11 , the central gateway may send the validity period of the unique hardware identifier to the diagnostic device.
[0065] like Figure 2 As shown, the embodiment of the present application provides a diagnostic device authentication method, which is applied to a central gateway, including the following steps S21 to S24:
[0066] Step S21 : within a first preset time after the diagnostic device passes the first security authentication, if a unique hardware identifier sent by the diagnostic device is received, a security token is generated according to the unique hardware identifier.
[0067] In the application, the central gateway will establish a communication connection with the diagnostic device after the diagnostic device passes the first security authentication. If the unique hardware identifier sent by the diagnostic device is received within the first preset time, the security of the unique hardware identifier can be guaranteed. The first preset time can be the same as the validity period of the communication connection, or it can be less than the validity period of the communication connection. After ensuring the security of the unique hardware identifier, a security token can be generated based on the unique hardware identifier, and the security token can be an encrypted data character.
[0068] Step S22, storing the unique hardware identifier, the security token and the validity period in an authenticated directory; the unique hardware identifier and the security token correspond one to one.
[0069] In the application, the unique hardware identifier, security token and validity period are stored in the authenticated directory. The security token and the unique hardware identifier correspond one to one, which facilitates the subsequent security authentication of the diagnostic device based on this information.
[0070] Step S23: sending the security token to the diagnostic device.
[0071] In the application, the central gateway sends a security token to the diagnostic device, so that the diagnostic device can subsequently perform security authentication through the security token, thereby improving the efficiency of security authentication.
[0072] Step S24: If a token authentication request sent by the diagnostic device is received, token security authentication is performed on the diagnostic device based on the token authentication request; the token authentication request includes a unique hardware identifier of the diagnostic device and a security token.
[0073] In the application, the token authentication request includes the unique hardware identifier and security token of the diagnostic device. After the central gateway receives the token authentication request, it can not only efficiently determine whether the diagnostic device is safe based on the unique hardware identifier and the unique security token and the one-to-one correspondence between the two, but also improve the reliability of the judgment result.
[0074] In one embodiment, in step S24, performing token security authentication on the diagnostic device based on the token authentication request includes:
[0075] If the security token in the token authentication request is within the validity period and its corresponding unique hardware identifier in the authenticated directory is consistent with the unique hardware identifier in the token authentication request, then determining that the diagnostic device is secure;
[0076] If the security token in the token authentication request is not in the authenticated directory or is not within the validity period, or its corresponding unique hardware identifier in the authenticated directory is inconsistent with the unique hardware identifier in the token authentication request, a first authentication result indicating authentication failure is sent to the diagnostic device.
[0077] In the application, the security token in the token authentication request sent by the diagnostic device is within the validity period, and its corresponding unique hardware identifier in the authenticated directory is consistent with the unique hardware identifier in the token authentication request, which not only indicates that the diagnostic device has passed the first security authentication request and the security token is within the validity period, but also indicates that the security token owned by the diagnostic device corresponds to its unique hardware identifier, so it can be determined that the diagnostic device is safe. If the diagnostic device is determined to be safe, a communication connection can be established with the diagnostic device, and the time limit of the communication connection can be set according to security requirements, which can be the first security authentication time limit or less than the first security authentication time limit.
[0078] In the application, the security token in the token authentication request sent by the diagnostic device is not in the authenticated directory, indicating that the diagnostic device has not passed the first security authentication; the security token in the token authentication request sent by the diagnostic device is in the authentication directory but is not within the validity period, indicating that the diagnostic device has been securely authenticated but the security token has expired; the unique hardware identifier corresponding to the security token in the token authentication request sent by the diagnostic device in the authenticated directory is inconsistent with the unique hardware identifier in the token authentication request, indicating that the correspondence between the security token and the unique hardware identifier of the diagnostic device does not conform to the corresponding information in the authenticated directory. It is understandable that the above situations cannot determine that the diagnostic device is safe, so the diagnostic device is judged to be an unsafe device, and the first authentication result indicating the authentication failure is sent to the diagnostic device. The diagnostic device can re-perform the first security authentication or reselect the security token and unique hardware identifier in the token authentication request to be sent.
[0079] It can be understood that in the above method, a security token is generated based on the unique hardware identifier sent by the diagnostic device within the first preset time after passing the first security authentication, and the security token, the unique hardware identifier and its validity period are stored in the authenticated directory, and then the security token is sent to the diagnostic device, thereby realizing the security authentication of the diagnostic device through the security token and the unique hardware identifier, solving the problem of frequent first security authentication of the diagnostic device, occupying resources and affecting the diagnostic efficiency, and realizing efficient and reliable security authentication of the diagnostic device.
[0080] In applications, the central gateway can periodically clean up invalid data in the authenticated directory to free up storage space.
[0081] In the application, after step S22, the method further includes: sending the validity period of the security token to the diagnostic device.
[0082] like Figure 3 , the embodiment of the present application provides a diagnostic device authentication method, which is applied to a diagnostic device, including steps S31 to S32:
[0083] Step S31, sending a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication.
[0084] In the application, before the diagnostic device communicates with the target central gateway for the first time, or after receiving the first authentication result sent by the target central gateway indicating authentication failure, it will request the target central gateway to perform the first security authentication. The first preset time is generally a few seconds to tens of seconds, and the longest time does not exceed the first security authentication time limit, so as to ensure the security of the unique hardware identifier sent to the target central gateway.
[0085] Step S32: If an authentication instruction is detected, the unique hardware identifier is sent to the target central gateway.
[0086] In the application, the diagnostic device sends a unique hardware identifier to the target central gateway. If the target central gateway can perform security authentication based on the unique hardware identifier, a communication connection can be established with the target central gateway.
[0087] In the application, the unique hardware identifier includes a unique and unmodifiable hardware identifier, such as the serial number of the diagnostic device, the hard disk number of the diagnostic device, the MAC (Media Access Control Address) of the network card, etc. Therefore, the unique hardware identifier is also unique and unmodifiable.
[0088] In the application, after step S31, it further includes: receiving and storing the validity period of the unique hardware identifier sent by the central gateway. Step S32 includes: if the authentication instruction is detected and the unique hardware identifier to be sent is within the validity period, sending the unique hardware identifier to the target central gateway; if the unique hardware identifier to be sent is not within the validity period, requesting the central gateway to perform a first security authentication.
[0089] like Figure 4 , the embodiment of the present application provides a diagnostic device authentication method, which is applied to a diagnostic device, including steps S41 to S43:
[0090] Step S41, sending a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication.
[0091] Step S42, receiving the security token sent by the target gateway and storing it in a token library.
[0092] Step S43: If an authentication instruction is detected, a token authentication request is sent to the target central gateway; the token authentication request includes a unique hardware identifier and the security token.
[0093] In the application, the security token corresponds to the unique hardware identifier sent within the first preset time through the first security authentication, and the unique hardware identifier and the security token in the token authentication request also correspond.
[0094] In one embodiment, after sending the token authentication request to the target central gateway, the method further includes:
[0095] If a first authentication result indicating authentication failure is received from the target central gateway, the target central gateway is requested to perform a first security authentication.
[0096] In the application, the first authentication result indicating authentication failure sent by the target central gateway may be due to the fact that the security token has expired, the security token is not in the authenticated directory of the target central gateway, or the unique hardware identifier corresponding to the security token in the token authentication request is different from the unique hardware identifier corresponding to the same security token in the authenticated directory. Therefore, the first security authentication can be re-passed, the unique hardware identifier can be re-sent and a new security token can be obtained.
[0097] In one embodiment, receiving the security token sent by the target gateway and storing it in a token repository includes:
[0098] Receive a security token sent by the target gateway, and store the target gateway identifier and the security token in a token library, wherein the target gateway identifier corresponds to the security token one by one;
[0099] The token authentication request includes a unique hardware identifier and a security token corresponding to the target gateway identifier in the token repository.
[0100] In applications, one diagnostic device can be used to diagnose different vehicles, so there may be multiple tokens in the token library of the diagnostic device. By storing the target central gateway identifier and the security token in the token library, when diagnosing the vehicle, the corresponding security token can be selected according to the vehicle's central gateway identifier, and the target central gateway can be requested to perform security authentication based on the security token.
[0101] In the application, step S42 includes: receiving the security token and its validity period sent by the target gateway, and storing it in the token library. Step S43 includes: if an authentication instruction is detected and the security token is within the validity period, sending a token authentication request to the target central gateway; the token authentication request includes a unique hardware identifier and the security token; if the security token is not within the validity period, requesting the target central gateway to perform a first security authentication.
[0102] The present application also provides a diagnostic device authentication system for executing the steps in the above diagnostic device authentication method embodiment. The diagnostic device authentication system can be a virtual appliance in a computer device, run by a processor of the computer device, or can be the computer device itself.
[0103] like Figure 5 As shown, the embodiment of the present application provides a diagnostic device authentication system 5, including:
[0104] The authentication information recording module 501 is used to store the unique hardware identifier and its validity period in the authenticated directory if the unique hardware identifier sent by the diagnostic device is received within a first preset time after the diagnostic device passes the first security authentication;
[0105] The security authentication module 502 is used to determine that the diagnostic device is secure if a unique hardware identifier is received from the diagnostic device and the unique hardware identifier is in the authenticated directory and within the validity period; if a unique hardware identifier is received from the diagnostic device and the unique hardware identifier is not in the authenticated directory or the unique hardware identifier is not within the validity period, send a first authentication result indicating authentication failure to the diagnostic device.
[0106] In one embodiment, the diagnostic device authentication system 5 comprises:
[0107] The security token module 503 is used to generate a security token according to the unique hardware identifier sent by the diagnostic device within a first preset time after the diagnostic device passes the first security authentication; and send the security token to the diagnostic device;
[0108] The authentication information recording module 501 is used to store the unique hardware identifier, the security token and the validity period into the authenticated directory; the unique hardware identifier and the security token correspond one to one;
[0109] The security authentication module 502 is used to perform token security authentication on the diagnostic device based on the token authentication request if a token authentication request sent by the diagnostic device is received; the token authentication request includes the unique hardware identifier of the diagnostic device and the security token.
[0110] In one embodiment, the security authentication module 502 is used to determine that the diagnostic device is secure if the security token in the token authentication request is within the validity period and its corresponding unique hardware identifier in the authenticated directory is consistent with the unique hardware identifier in the token authentication request; if the security token in the token authentication request is not in the authenticated directory or is not within the validity period or its corresponding unique hardware identifier in the authenticated directory is inconsistent with the unique hardware identifier in the token authentication request, then send a first authentication result indicating authentication failure to the diagnostic device.
[0111] The present application embodiment also provides a diagnostic device authentication system 6, including:
[0112] The authentication information registration module 601 is used to send a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication;
[0113] The authentication request module 602 is configured to send a unique hardware identifier to a target central gateway if an authentication instruction is detected.
[0114] In one embodiment, the diagnostic device authentication system 6 further includes:
[0115] The token storage module 603 is used to receive the security token sent by the target gateway and store it in the token library;
[0116] The authentication request module 602 is used to send a token authentication request to the target central gateway if an authentication instruction is detected; the token authentication request includes a unique hardware identifier and the security token.
[0117] In the application, the authentication request module 602 is further used to request the target central gateway to perform a first security authentication if a first authentication result indicating authentication failure is received from the target central gateway.
[0118] In one embodiment, the token storage module 603 is used to receive the security token sent by the target gateway, and store the target gateway identifier and the security token in a token library, wherein the target gateway identifier corresponds to the security token one by one; the token authentication request includes a unique hardware identifier and the security token corresponding to the target gateway identifier in the token library.
[0119] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0120] Figure 7 This is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. Figure 7As shown, the computer device 7 of this embodiment includes: at least one processor 70 ( Figure 7 Only one is shown in the figure) a processor, a memory 71, and a computer program 72 stored in the memory 71 and executable on the at least one processor 70, wherein the processor 70 implements the steps of any of the above-mentioned diagnostic device authentication method embodiments when executing the computer program 72.
[0121] When the computer device 7 is a diagnostic device, it can be a computer device such as a tablet computer, a notebook, a handheld computer, etc. The computer device may include, but is not limited to, a processor 70 and a memory 71. Those skilled in the art will understand that Figure 7 It is only an example of the computer device 7 and does not constitute a limitation on the computer device 7. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.
[0122] The processor 70 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0123] In some embodiments, the memory 71 may be an internal storage unit of the computer device 7, such as a hard disk or memory of the computer device 7. In other embodiments, the memory 71 may also be an external storage device of the computer device 7, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the computer device 7. Further, the memory 71 may also include both an internal storage unit and an external storage device of the computer device 7. The memory 71 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 71 may also be used to temporarily store data that has been output or is to be output.
[0124] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.
[0125] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.
[0126] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.
[0127] An embodiment of the present application provides a computer program product. When the computer program product is run on a computer device, the computer device can implement the steps in the above-mentioned method embodiments when executing the computer device.
[0128] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.
[0129] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0130] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0131] In the embodiments provided in the present application, it should be understood that the disclosed computer devices and methods can be implemented in other ways. For example, the computer device / diagnostic device authentication system embodiment described above is only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0132] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0133] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. A diagnostic device authentication method, characterized in that: Applicable to central gateway, including: Within a first preset time after the diagnostic device passes the first security authentication, if a unique hardware identifier sent by the diagnostic device is received, the unique hardware identifier and its validity period are stored in an authenticated directory; If a unique hardware identifier sent by a diagnostic device is received, and the unique hardware identifier is in the authenticated directory and within the validity period, then determining that the diagnostic device is safe; If a unique hardware identifier sent by a diagnostic device is received and the unique hardware identifier is not in the authenticated directory or is not within the validity period, a first authentication result indicating authentication failure is sent to the diagnostic device.
2. A diagnostic equipment authentication method, characterized in that: Applicable to central gateway, including: Within a first preset time after the diagnostic device passes the first security authentication, if a unique hardware identifier sent by the diagnostic device is received, generating a security token according to the unique hardware identifier; storing the unique hardware identifier, the security token and the validity period in an authenticated directory; the unique hardware identifier and the security token correspond one to one; sending the security token to the diagnostic device; If a token authentication request sent by a diagnostic device is received, token security authentication is performed on the diagnostic device based on the token authentication request; the token authentication request includes a unique hardware identifier of the diagnostic device and a security token.
3. The diagnostic device authentication method according to claim 2, characterized in that: The performing token security authentication on the diagnostic device based on the token authentication request comprises: If the security token in the token authentication request is within the validity period and its corresponding unique hardware identifier in the authenticated directory is consistent with the unique hardware identifier in the token authentication request, then determining that the diagnostic device is secure; If the security token in the token authentication request is not in the authenticated directory or is not within the validity period, or its corresponding unique hardware identifier in the authenticated directory is inconsistent with the unique hardware identifier in the token authentication request, a first authentication result indicating authentication failure is sent to the diagnostic device.
4. The diagnostic equipment authentication method according to claim 2 or 3, characterized in that: The unique hardware identifier includes at least one of a serial number of the diagnostic device, a hard disk number, and a MAC address of a network card.
5. A diagnostic device authentication method, characterized in that: Applications in diagnostic equipment, including: Sending a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication; If an authentication command is detected, the unique hardware identifier is sent to the target central gateway.
6. A diagnostic device authentication method, characterized in that: Applications in diagnostic equipment, including: Sending a unique hardware identifier to a target central gateway within a first preset time after passing a first security authentication; Receive the security token sent by the target gateway and store it in the token library; If an authentication instruction is detected, a token authentication request is sent to the target central gateway; the token authentication request includes a unique hardware identifier and the security token.
7. The diagnostic device authentication method according to claim 6, characterized in that: After sending the token authentication request to the target central gateway, the method further includes: If a first authentication result indicating authentication failure is received from the target central gateway, the target central gateway is requested to perform a first security authentication.
8. The diagnostic device authentication method according to claim 6 or 7, characterized in that: The receiving the security token sent by the target gateway and storing it in a token library includes: Receive a security token sent by the target gateway, and store the target gateway identifier and the security token in a token library, wherein the target gateway identifier corresponds to the security token one by one; The token authentication request includes a unique hardware identifier and a security token corresponding to the target gateway identifier in the token repository.
9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the computer device is a central gateway, the processor implements the steps of the method according to any one of claims 1 to 5 when executing the computer program; When the computer device is a diagnostic device, the processor implements the steps of the method according to any one of claims 6 to 8 when executing the computer program.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.
