Authentication method, controller, and computer device

By obtaining and verifying the hardware and software parameter characteristics of components in computer equipment, and using hashing operations to ensure their security, it solves the problem that components are prone to counterfeiting, tampering or replacement, and achieves higher security and reliability.

WO2024244873A1PCT designated stage expired Publication Date: 2024-12-05HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/090675
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-07-28
Filing Date
2024-04-29
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Components in computer equipment are produced by different manufacturers and are easily counterfeited, tampered or replaced, making it difficult to guarantee security and reliability.

Method used

By obtaining the hardware and software parameters of the object to be authenticated, generating their features, and using hashing operations to ensure the security of the features, dynamically verifying the compatibility of components, thereby improving security and reliability.

Benefits of technology

Effectively prevent components from being counterfeited, tampered or replaced, ensure their compatibility and security, and improve the overall security and reliability of computer equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024090675_05122024_PF_FP_ABST
    Figure CN2024090675_05122024_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of computers. Disclosed are an authentication method, a controller, and a computer device. The authentication method comprises: according to hardware parameters and software parameters of an object to be authenticated, acquiring the feature of said object; and according to the fusion feature digest and the feature of said object, determining that the compatibility authentication of said object is passed or not passed. The fusion feature digest is used for indicating that a component-based fusion feature component passes the compatibility test. In order to solve the problems of incapability of ensuring the security and reliability of components due to the fact only claimed by manufacturers that the components pass the compatibility test, according to the method provided by the present application, the feature of an object to be authenticated is verified according to the fusion feature digest, and if said object is counterfeited, tampered or replaced, the feature of said object is possibly different from the reference feature of said object, and said object possibly has the risks of security and reliability. Therefore, the compatibility of the components is dynamically verified by means of the security technology, so that the security and reliability of the components are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Authentication method, controller and computer equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 29, 2023, with application number 202310617828.0 and application name “A method of authentication”. This application also claims priority to the Chinese patent application filed with the State Intellectual Property Office on July 28, 2023, with application number 202310950978.3 and application name “Authentication method, controller and computer device”. All of these contents are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of computers, and in particular to an authentication method, a controller, and a computer device. Background Art

[0003] Computer device performance is typically measured by its configuration. This performance can be improved by expanding the types of components within the device. For example, increasing the types of processors within a computer device increases computing power diversity. Another example is increasing the types of memory within a computer device to improve storage diversity, ensuring data reliability and enabling the processor to access data as quickly as possible. However, components within a computer device may be manufactured by different manufacturers, resulting in a wide variety of manufacturers. Furthermore, products (such as components or software) are frequently updated, making components susceptible to counterfeiting, tampering, or replacement, making it difficult to guarantee component security and reliability.

[0004] Summary of the Invention

[0005] The present application provides an authentication method, a controller, and a computer device, thereby improving the security and reliability of components.

[0006] In a first aspect, an authentication method is provided. The method obtains features of an object to be authenticated based on its hardware and software parameters. The method then authenticates the object to be authenticated based on a fused feature summary indicated by its identifier and the features of the object to be authenticated, thereby obtaining a compatibility authentication result for the object to be authenticated. The compatibility authentication result includes a pass or fail condition. The fused feature summary indicates that a component, based on its fused features, has passed compatibility testing. The fused features of a component are generated based on its hardware and software parameters.

[0007] Compared to the problem of simply claiming that a component has passed compatibility certification by the manufacturer, which cannot ensure the safety and reliability of the component, the method provided in this application obtains a fused feature summary of the identification indication based on the identification of the object to be authenticated, and verifies the characteristics of the object to be authenticated based on the fused feature summary. In other words, the characteristics of the object to be authenticated are compared with the baseline characteristics of the object to be authenticated. If the object to be authenticated has been counterfeited, tampered with, or replaced, the characteristics of the object to be authenticated may differ from the baseline characteristics of the object to be authenticated, and the object to be authenticated may be at risk of security and reliability. Therefore, the compatibility of the component is dynamically verified through security technology, thereby improving the security and reliability of the component.

[0008] The object to be authenticated described in the present application may be any one of a memory, a circuit board or a Peripheral Component Interconnect Express (PCIe) standard.

[0009] In a possible implementation, acquiring the characteristics of the object to be authenticated according to the hardware parameters and software parameters of the object to be authenticated includes: performing at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated.

[0010] Thus, a hash operation is performed based on the inherent parameters of the object to be authenticated to generate the characteristics of the object to be authenticated, thereby ensuring the security level of the characteristics of the object to be authenticated and preventing them from being tampered with or obtained at will.

[0011] In some possible embodiments, the hardware parameters include the hardware trusted root and identifier of the object to be authenticated, and the software parameters include the firmware summary of the object to be authenticated; at least two hash operations are performed on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated, including: performing a hash operation on the hardware trusted root of the object to be authenticated to obtain a first hash value; performing a hash operation on the identifier and the first hash value to obtain a second hash value; and performing a hash operation on the firmware summary of the object to be authenticated and the second hash value to obtain the characteristics of the object to be authenticated.

[0012] Therefore, the characteristics of the object to be authenticated are generated based on the parameters representing integrity, uniqueness and confidentiality in the object to be authenticated, thereby improving the security level of the characteristics of the object to be authenticated.

[0013] In other possible embodiments, the hardware parameters include an identifier, and the software parameters include a firmware summary of the object to be authenticated; at least two hash operations are performed on the hardware parameters and software parameters of the object to be authenticated to obtain characteristics of the object to be authenticated, including: performing a hash operation on the identifier to obtain a first hash value; and performing a hash operation on the firmware summary of the object to be authenticated and the first hash value to obtain characteristics of the object to be authenticated.

[0014] Therefore, the characteristics of the object to be authenticated are generated based on the parameters representing the uniqueness and confidentiality of the object to be authenticated, thereby improving the security level of the characteristics of the object to be authenticated.

[0015] In another possible implementation, the fusion feature of the component is generated based on at least two hash operations of the hardware parameters and software parameters of the component.

[0016] Thus, a hash operation is performed based on the inherent parameters of the component to generate the fusion feature of the component, thereby ensuring the security level of the fusion feature of the component and preventing it from being tampered with or obtained at will.

[0017] In some possible embodiments, at least two hash operations are performed on the hardware parameters and software parameters of the component to obtain the fusion characteristics of the component, including: performing a hash operation on the hardware trusted root of the component to obtain a first hash value; performing a hash operation on the identifier and the first hash value to obtain a second hash value; and performing a hash operation on the firmware summary of the component and the second hash value to obtain the fusion characteristics of the component.

[0018] In some other possible embodiments, at least two hash operations are performed on the hardware parameters and software parameters of the component to obtain the fusion characteristics of the component, including: performing a hash operation on the identification of the component to obtain a first hash value; and performing a hash operation on the firmware summary of the component and the first hash value to obtain the fusion characteristics of the component.

[0019] In another possible implementation, the object to be authenticated is authenticated based on the fusion feature summary indicated by the identification of the object to be authenticated and the features of the object to be authenticated, including: decrypting the fusion feature summary based on the public key to obtain the fusion feature; and determining the compatibility authentication result of the object to be authenticated based on the comparison result of the fusion feature and the features of the object to be authenticated.

[0020] Therefore, using a signature method to encrypt the component's fusion features, such as using the signature key used in the original compatibility authentication, ensures the security of the component's fusion features and prevents them from being tampered with or accessed. Furthermore, the changes and impact to the existing compatibility list are minimal; simply adding a component fusion feature option to the existing compatibility list is sufficient.

[0021] For example, when the characteristics of the object to be authenticated are the same as the fusion characteristics, the compatibility authentication result of the object to be authenticated indicates that the object to be authenticated has passed the compatibility authentication; when the characteristics of the object to be authenticated are different from the fusion characteristics, the compatibility authentication result of the object to be authenticated indicates that the object to be authenticated has not passed the compatibility authentication.

[0022] In another possible implementation, the method further includes: acquiring a fused feature digest and a public key from the electronic tag of the object to be authenticated, where the public key is used to decrypt the fused feature digest.

[0023] Therefore, the fusion feature summary of the component is written into the electronic tag, which reduces the cost of compatibility certification, makes little change to the original component, and reduces security risks such as software and hardware tampering or replacement.

[0024] In another possible implementation, the method further includes: obtaining the fusion feature summary and the public key from a compatibility list published by the manufacturer according to the identifier of the object to be authenticated.

[0025] Therefore, a summary of the fusion characteristics of the components is added to the original compatibility list, and a benchmark for the compatibility certification of the components is published, which is easy to obtain evidence, private key encrypted, and has integrity protection capabilities.

[0026] In a second aspect, an authentication device is provided, including: an authentication module, used to obtain characteristics of an object to be authenticated based on hardware parameters and software parameters of the object to be authenticated; the authentication module is also used to authenticate the object to be authenticated based on a fusion feature summary indicated by an identification of the object to be authenticated and the characteristics of the object to be authenticated, and obtain a compatibility authentication result of the object to be authenticated, the compatibility authentication result includes compatibility authentication passed and compatibility authentication failed, the fusion feature summary is used to indicate that a component based on the fusion feature of the component passes the compatibility test, and the fusion feature of the component is generated based on the hardware parameters and software parameters of the component.

[0027] In a possible implementation, when the authentication module obtains the characteristics of the object to be authenticated based on the hardware parameters and software parameters of the object to be authenticated, it is specifically configured to: perform at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated.

[0028] In another possible implementation, the hardware parameters include a hardware root of trust and an identifier of the object to be authenticated, and the software parameters include a firmware digest of the object to be authenticated. When the authentication module performs at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain characteristics of the object to be authenticated, the authentication module is specifically configured to: perform a hash operation on the hardware root of trust of the object to be authenticated to obtain a first hash value; perform a hash operation on the identifier and the first hash value to obtain a second hash value; and perform a hash operation on the firmware digest of the object to be authenticated and the second hash value to obtain the characteristics of the object to be authenticated.

[0029] In another possible implementation, the hardware parameter includes an identifier, and the software parameter includes a firmware digest of the object to be authenticated;

[0030] When the authentication module performs at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated, it is specifically used to: perform a hash operation on the identifier to obtain a first hash value; and perform a hash operation on the firmware summary of the object to be authenticated and the first hash value to obtain the characteristics of the object to be authenticated.

[0031] In another possible implementation, the fusion feature of the component is generated based on at least two hash operations of the hardware parameters and software parameters of the component.

[0032] In another possible implementation, when the authentication module authenticates the object to be authenticated based on the fusion feature summary indicated by the identification of the object to be authenticated and the features of the object to be authenticated, it is specifically used to: decrypt the fusion feature summary according to the public key to obtain the fusion feature; and determine the compatibility authentication result of the object to be authenticated based on the comparison result of the fusion feature and the features of the object to be authenticated.

[0033] In another possible implementation, the device further includes a communication module; the communication module is configured to obtain a fusion feature summary and a public key from an electronic tag of the object to be authenticated.

[0034] In another possible implementation, the apparatus further includes a communication module; the communication module is configured to obtain the fusion feature summary and the public key from a compatibility list published by a manufacturer according to an identifier of the object to be authenticated.

[0035] In another possible implementation, the object to be authenticated includes any one of a memory, a circuit board, or a PCIe card.

[0036] In a third aspect, a controller is provided, comprising a logic circuit and a power supply circuit; wherein the power supply circuit is configured to supply power to the logic circuit; and the logic circuit is configured to execute the steps of the method described in the first aspect or any possible implementation of the first aspect. For example, the logic circuit is a baseboard management controller (BMC).

[0037] In a fourth aspect, a computer device is provided, which includes a memory, a controller and multiple components, the memory being used to store a set of computer instructions; when the controller executes the set of computer instructions, the operating steps of the method described in the first aspect or any possible implementation of the first aspect are executed to achieve compatibility certification of multiple components.

[0038] In a fifth aspect, a communication system is provided, comprising a remote device and a computer device. The remote device is configured to perform the steps of the method described in the first aspect or any possible implementation of the first aspect to perform compatibility authentication of multiple components in the computer device.

[0039] In a sixth aspect, a computer-readable storage medium is provided, comprising: computer software instructions; when the computer software instructions are executed in a computer device, the computer device executes the operating steps of the method described in the first aspect or any possible implementation of the first aspect.

[0040] In a seventh aspect, a computer program product is provided. When the computer program product is run on a computer, it enables the computer to perform the operating steps of the method described in the first aspect or any possible implementation of the first aspect.

[0041] The technical effects brought about by any design method from the second to the seventh aspects can refer to the technical effects brought about by the first aspect or different possible implementation methods of the first aspect, and will not be repeated here.

[0042] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] FIG1 is a schematic structural diagram of a computer device provided by the present application;

[0044] FIG2 is a schematic diagram of a scenario for performing compatibility authentication provided by this application;

[0045] FIG3 is a flow chart of an authentication method provided by this application;

[0046] FIG4 is a schematic diagram of extracting features of a component provided by the present application;

[0047] FIG5 is a schematic diagram of extracting fusion features of a component provided by this application;

[0048] FIG6 is a flow chart of another authentication method provided by this application;

[0049] FIG7 is a flow chart of another authentication method provided by this application;

[0050] FIG8 is a schematic diagram of a message format provided by this application;

[0051] FIG9 is a schematic diagram showing an interface display of a compatibility list provided by the present application;

[0052] FIG10 is a flow chart of another authentication method provided by this application;

[0053] FIG11 is a schematic diagram of the structure of an authentication device provided by this application;

[0054] FIG12 is a schematic structural diagram of a controller provided by the present application;

[0055] FIG13 is a schematic diagram of the structure of another controller provided in this application. DETAILED DESCRIPTION

[0056] To facilitate understanding, the main terms involved in this application are first explained.

[0057] Compatibility refers to the degree of interoperability between hardware, software, or a combination of hardware and software. For example, if hardware (e.g., central processing unit (CPU), motherboard, graphics card, etc.) can work together and stably, hardware compatibility is high; conversely, hardware compatibility is low. Similarly, if software can run stably on multiple operating systems without unexpected failures, software compatibility is high; conversely, software compatibility is low.

[0058] Root of Trust: Also known as the root of trust, it serves as the basis for trust in a trusted computer system. Roots of Trust include the root of trusted measurement, the root of trusted storage, and the root of trusted reporting.

[0059] Hardware root of trust: refers to the root of trust implemented based on the chip or hardware anti-tampering capabilities, and is used to protect the integrity of hardware and firmware through trusted chain technology.

[0060] Firmware: This refers to the hardware "driver" stored within the hardware, which determines the hardware's functionality and performance. Through firmware, the operating system implements specific machine operations according to standard hardware drivers. For example, hardware such as optical drives and burners store internal firmware. Firmware is typically stored in erasable programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM).

[0061] Firmware digest: refers to the hash value obtained by performing a hash operation on the firmware, and the value obtained by encrypting the hash value based on the private key.

[0062] Mainboard: Also known as the mainboard, system board, or motherboard, it is one of the most basic and important components of a computer. A motherboard is a circuit board that houses the computer's main circuitry, typically including the Basic Input / Output System (BIOS) chip, input / output (I / O) controller chip, keyboard and panel control switch connectors, indicator light connectors, expansion slots, and DC power supply connectors.

[0063] Network Interface Controller (NIC): Also known as a network adapter or network interface card, a network card is a piece of hardware that connects a computer to an external local area network, allowing the computer to communicate with other devices on the computer network.

[0064] Baseboard management controller (BMC): A dedicated controller integrated into the motherboard or plugged into the motherboard using a chip such as Peripheral Component Interconnect Express (PCIe). It monitors and manages the server. Examples include device information management, server status monitoring, remote server control, and maintenance management.

[0065] In order to solve the problem of component security and reliability in a scenario where the types of components are diverse and components are easily counterfeited, tampered with or replaced, the present application provides an authentication method, namely, obtaining the characteristics of the object to be authenticated based on the hardware parameters and software parameters of the object to be authenticated; authenticating the object to be authenticated based on the fusion feature summary indicated by the identification of the object to be authenticated and the characteristics of the object to be authenticated, and obtaining the compatibility authentication result of the object to be authenticated, the compatibility authentication result including compatibility authentication passed and compatibility authentication failed. The fusion feature summary is used to indicate that the component based on the fusion feature of the component has passed the compatibility test. The fusion feature of the component is generated based on the hardware parameters and software parameters of the component.

[0066] Compared to the problem of simply claiming that a component has passed compatibility certification by the manufacturer, which cannot ensure the safety and reliability of the component, the method provided in this application obtains a fused feature summary of the identification indication based on the identification of the object to be authenticated, and verifies the characteristics of the object to be authenticated based on the fused feature summary. In other words, the characteristics of the object to be authenticated are compared with the baseline characteristics of the object to be authenticated. If the object to be authenticated has been counterfeited, tampered with, or replaced, the characteristics of the object to be authenticated may differ from the baseline characteristics of the object to be authenticated, and the object to be authenticated may be at risk of security and reliability. Therefore, the compatibility of the component is dynamically verified through security technology, thereby improving the security and reliability of the component.

[0067] The object to be authenticated may be a component in a computer device. For example, the object to be authenticated may be an independent device in the computer device, such as a memory and a processor. Memory includes dynamic random access memory (DRAM), solid state drives (SSDs), and storage-class memory (SCM). The processor may be a computing unit with computing power, such as a central processing unit (CPU), graphics processing unit (GPU), data processing unit (DPU), or neural processing unit (NPU). Another example is that the object to be authenticated may be a board composed of multiple components in the computer device. For example, the object to be authenticated may include a circuit board or a PCIe card. For example, the circuit board may be a mainboard, a baseboard, or an expansion board. The circuit board may also integrate a CPU, a baseboard management system (BMC), a BIOS chip, and an I / O control chip. PCIe cards include network cards, artificial intelligence (AI) cards, reader cards, GPUs, DPUs, and NPUs.

[0068] The certification scheme provided in this application can be applied to traditional computer devices that provide computing and storage functions, verifying the compatibility of components in traditional computer devices, and can also be applied to servers in cluster networks. For example, in a high-performance computing (HPC) network, computing servers provide high-performance computing, and the compatibility of components in the computing servers must be verified to ensure the reliability of the computing servers.

[0069] The following describes in detail the implementation of the authentication method provided by this application with reference to the accompanying drawings.

[0070] Figure 1 is a schematic diagram of the structure of a computer device provided in this application. As shown in Figure 1, computer device 100 includes a circuit board 110, a bus 120, a memory 130, a PCIe card 140, and a BMC 150. Circuit board 110, memory 130, PCIe card 140, and BMC 150 are connected via bus 120.

[0071] In some embodiments, the circuit board 110 includes a processor 111 , a memory unit 112 , and a communication interface 113 .

[0072] Processor 111 is the control center of computer device 100. Processor 111 can be a computing unit with computing power, such as a CPU, GPU, DPU, or NPU. Processor 111 includes one or more processor cores. For example, processor 111 shown in FIG1 includes N processor cores.

[0073] In some embodiments, processor 111 includes registers 11 and cache memory 12 .

[0074] The cache memory 12 is used to store instructions or data that may be accessed multiple times by the processor core in the processor 111 , thereby increasing the speed at which the processor processes data and preventing the processor from frequently accessing the memory unit 112 .

[0075] In terms of physical form, the cache memory 12 may be a random access memory (RAM), a static random-access memory (SRAM), a dynamic random access memory (DRAM), or other types of storage devices that can store information and instructions.

[0076] In terms of logical form, the cache memory 12 can be a level 1 cache (L1 cache), a level 2 cache (L2 cache), a level 3 cache (L3 cache), or any other level of cache. For example, as shown in FIG1 , the cache memory 12 disposed inside the processor core can be a level 1 cache (L1 cache) and a level 2 cache (L2 cache). The cache memory 12 disposed outside the processor core can be a level 3 cache (L3 cache).

[0077] Register 11 is used to store instructions or data that may be accessed multiple times by the processor core in processor 111. Because register access speed is higher than cache memory access speed, instructions or data that may be accessed multiple times by the processor core can be stored in registers first, which can further increase the speed at which the processor processes data.

[0078] Alternatively, the processor 111 may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (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.

[0079] The memory unit 112 (also referred to as the main memory unit) can be a volatile memory pool or a non-volatile memory pool, or can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0080] The communication interface 113 is used to implement communication between the computer device 100 and an external device or component. In this application, the computer device 100 can obtain the fusion feature summary from the component manufacturer's server through the communication interface 113.

[0081] The memory 130 may be a persistent storage medium, for example, a disk, such as a mechanical hard disk or a solid-state drive.

[0082] The PCIe card 140 may refer to a peripheral device, for example, a network card, etc.

[0083] In this application, the memory unit 112 can be used to store the compatibility authentication instructions or data described in this application, such as the characteristics of the object to be authenticated and the fusion feature summary of the identification indication of the object to be authenticated, etc. The memory 130 stores the compatibility authentication instructions or data.

[0084] The bus 120 may include a path for transmitting information between the above-mentioned components (such as the circuit board 110, the PCIe card 140, the BMC 150, and the memory 130). In addition to the data bus, the bus 120 may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, various buses are labeled as bus 120 in the figure. The bus 120 may be a Peripheral Component Interconnect Express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus 120 can be divided into an address bus, a data bus, a control bus, etc.

[0085] It is worth noting that FIG1 only takes the computer device 100 including a circuit board 110 and a memory 130 as an example. Here, the circuit board 110 and the memory 130 are respectively used to indicate a type of device or equipment. In a specific embodiment, the number of each type of device or equipment can be determined according to business requirements.

[0086] The device structure shown in Figure 1 does not limit the computer device and may include more or fewer components than shown, or combine certain components, or arrange the components differently. For example, the computer device may also include an artificial intelligence card, a read card, a GPU, a DPU, and an NPU.

[0087] The components described herein may include processors, memory, memory units, registers, cache memory, network cards, and circuit boards included in a computer device. The components included in the computer device may be manufactured by different manufacturers. When the computer device is started, compatibility certification is performed on the components included in the computer device. For example, features of the object to be certified are obtained based on the hardware and software parameters of the object to be certified; and a determination is made as to whether the compatibility certification of the object to be certified has passed or failed based on a fused feature summary and the features of the object to be certified.

[0088] In addition, the subject of the compatibility authentication is not limited in this application. The computer device may perform compatibility authentication on the components included therein, or a remote device may perform compatibility authentication on the components included in the computer device.

[0089] For example, as shown in FIG2(a), a remote device 200 performs compatibility authentication on components included in a computer device 100. The remote device 200 may be a management controller in a system, such as a controller in a data center. The remote device 200 obtains the fused feature summary of the component published by the manufacturer and receives the features of the object to be authenticated reported by the computer device. Based on the fused feature summary and the features of the object to be authenticated, the remote device 200 determines whether the compatibility authentication of the object to be authenticated has passed or failed.

[0090] As shown in Figure 2(b), the local device performs compatibility certification on the included components. For example, a computer device includes a baseboard management controller (BMC) 150. The BMC 150 obtains the fused feature summary of the component published by the manufacturer and the features of the object to be certified within the computer device. Based on the fused feature summary and the features of the object to be certified, the BMC determines whether the object to be certified has passed or failed compatibility certification.

[0091] Next, the authentication method provided by this application is described in detail with reference to the accompanying drawings.

[0092] For ease of explanation, the remote authentication scenario shown in FIG2 (a), in which a remote device 200 performs compatibility authentication on components included in a computer device, is used as an example for illustration. Referring to FIG3 , FIG3 is a flow chart of an authentication method provided by this application. As shown in FIG3 , the method includes the following steps.

[0093] Step 310: Acquire the characteristics of the object to be authenticated.

[0094] When the computer device is started, compatibility certification is performed on the components included in the computer device. The object to be certified can be a component included in the computer device, which can be an independent device in the computer device or a board composed of multiple components in the computer device. In some embodiments, the computer device obtains component characteristics based on the hardware and software parameters of the component in the computer device, reports the component characteristics to the remote device, and the remote device obtains the component characteristics reported by the computer device (step 310a).

[0095] In other embodiments, the remote device receives hardware parameters and software parameters of components in the computer device reported by the computer device, and obtains characteristics of the components based on the hardware parameters and software parameters of the components in the computer device (step 310b).

[0096] The hardware parameters include the hardware root of trust and identification of the component, and the software parameters include the firmware digest of the object to be authenticated.

[0097] The remote device or computer device may perform at least two hash operations on the hardware parameters and software parameters of the component to obtain the characteristics of the component.

[0098] In some embodiments, as shown in (a) in Figure 4, first, the chip features are extracted. For example, a hash operation is performed on the hardware trusted root of the component to obtain a first hash value. Secondly, the chip features are extracted and the identity is fused with the board features. For example, a hash operation is performed on the identifier and the first hash value to obtain a second hash value. The identifier can be the equipment serial number (ESN) of the board, the board identifier (Board ID) or the equivalent original equipment manufacturer certificate (Original Equipment Manufacturer, OEM Key). Finally, the firmware features are extracted. For example, a hash operation is performed on the firmware of the component to obtain a firmware digest, and a hash operation is performed on the firmware digest of the component and the second hash value to obtain the features of the component.

[0099] In other embodiments, as shown in FIG4(b), first, board features are extracted. For example, a hash operation is performed on the identifier to obtain a first hash value. Next, firmware features are extracted. For example, a hash operation is performed on the component firmware to obtain a firmware digest, and a hash operation is performed on the component firmware digest and the first hash value to obtain the component features.

[0100] Because information such as the hardware root of trust is burned into the component's storage medium (e.g., EFUSE or OTP), it provides physical resistance to tampering. The identifier uniquely identifies the component and serves as its identity. Therefore, component characteristics are derived based on the component's hardware and software parameters. The hardware root of trust ensures the integrity of the component's characteristics. The identifier ensures the uniqueness of the component's characteristics. The firmware digest ensures the confidentiality of the component's characteristics.

[0101] Optionally, the hardware root of trust may also be replaced by an equivalent hardware root of trust, such as a chip identifier (Die ID or Chip ID) of a component. The chip identifier is used to uniquely indicate a chip and is an identification number of the chip.

[0102] Step 320: Authenticate the object to be authenticated based on the fusion feature summary indicated by the identifier of the object to be authenticated and the features of the object to be authenticated, and obtain a compatibility authentication result of the object to be authenticated.

[0103] Component manufacturers can generate a fusion signature based on the component's hardware and software parameters and calculate the fusion signature using a private key to obtain a fusion signature digest. If a component passes compatibility testing based on the fusion signature digest, the fusion signature digest and public key are published in the compatibility list. The fusion signature digest is used to verify the unique identity of the component and indicates that the component passed compatibility testing based on the fusion signature.

[0104] For example, at least two hash operations are performed on the hardware parameters and software parameters of the component to obtain the fused features of the component. For example, as shown in FIG5(a), a hash operation is performed on the hardware root of trust of the component to obtain a first hash value; a hash operation is performed on the identifier and the first hash value to obtain a second hash value; and a hash operation is performed on the firmware digest of the component and the second hash value to obtain the fused features of the component. As shown in FIG5(b), a hash operation is performed on the identifier to obtain a first hash value; and a hash operation is performed on the firmware digest of the component and the first hash value to obtain the fused features of the component.

[0105] It should be noted that the component fusion characteristics are generated based on the hardware and software parameters of the component produced by the manufacturer. The component fusion characteristics can be used as reference information for component compatibility certification.

[0106] The remote device obtains the features and identifiers of the components reported by the computer device, and obtains a fusion feature summary of the components according to the identifiers of the components.

[0107] In some embodiments, as shown in FIG6 , based on the identification of the component, the fusion feature summary and public key of the component are obtained from the compatibility list published by the manufacturer (step 321). The fusion feature summary is decrypted according to the public key to obtain the fusion feature (step 322). The compatibility certification result of the component is determined based on the comparison result of the fusion feature and the feature of the component (step 323). The compatibility certification result includes compatibility certification passed and compatibility certification failed. For example, when the feature of the component is the same as the fusion feature, the compatibility certification result of the component indicates that the component compatibility certification passed; when the feature of the component is different from the fusion feature, the compatibility certification result of the component indicates that the component compatibility certification failed.

[0108] In other embodiments, as shown in FIG7 , the component's fusion feature digest and public key are stored in the component's electronic tag. For example, the electronic tag can be burned into the storage medium 160 (e.g., EFUSE or OTP) of the computer device 100. The computer device obtains the component's fusion feature digest and public key from the electronic tag and reports them to the remote device (step 324). The remote device receives the component's fusion feature digest and public key reported by the computer device.

[0109] Optionally, the remote device may also feed back the compatibility authentication result of the component to the computer device.

[0110] In a component-based hardware system design, components can be independently developed by component manufacturers and partners. However, because components in computer devices can be counterfeited, tampered with, or replaced, the characteristics of the components within the computer device may differ from the fused characteristics. Therefore, using the fused characteristics of the components as reference information, the aforementioned certification process automatically determines whether the component has passed compatibility certification. This improves component security and reliability compared to simply relying on the manufacturer's declaration of compatibility certification.

[0111] Understandably, the method for generating the component's features should be the same as the method for generating the component's fusion features. If the component is counterfeited, tampered with, or replaced, the component's features may differ from the component's fusion features, and the component may pose a security risk.

[0112] Optionally, the compatibility list may also include component codes. The computer device may also report component codes to the remote device. For example, FIG8 shows a schematic diagram of a message format provided in this application. The message includes the component identifier, component code, and component characteristics. Based on the component identifier and component code, the remote device obtains the component's fusion feature summary and public key from the manufacturer's published compatibility list.

[0113] For example, Figure 9 is a schematic diagram of the interface display of a compatibility list provided by this application. As shown in (a) in Figure 9, the component compatibility query interface displays the product model option box, the network card type option box, the network card model option box, the component type option box, etc. Enter the content of each option box and click the "Query" button to display the compatibility list. As shown in (b) in Figure 9, a schematic diagram of the compatibility list display is shown. The content of the compatibility list is displayed based on the selected table item. For example, the compatibility list may include items such as encoding, encoding type, card type, model, description, interface type, and compatibility certification. The compatibility certification item contains the fusion feature summary and public key of the component.

[0114] It is worth noting that for the local authentication scenario shown in (b) of Figure 2, that is, the computer device performs compatibility authentication on the components contained in the computer device, the authentication process is similar to the authentication process in (a) of Figure 2. The difference is that the computer device does not need to report the characteristics of the component or the hardware parameters and software parameters of the component to the remote device. The computer device obtains the characteristics of the component based on the hardware parameters and software parameters of the component, obtains the fusion characteristics of the component based on the identification of the component, compares the characteristics of the component with the fusion characteristics of the component, and determines the compatibility authentication result of the component. For example, as shown in Figure 10, when the computer device is started, the BMC obtains the hardware parameters and software parameters of the component, obtains the characteristics of the component based on the hardware parameters and software parameters of the component (step 1010), obtains the fusion characteristics of the component based on the identification of the component, compares the characteristics of the component with the fusion characteristics of the component, and determines the compatibility authentication result of the component (step 1020). The BMC can obtain the fusion characteristic summary and public key of the component from the compatibility list published by the manufacturer based on the identification of the component. Alternatively, the BMC obtains the fusion characteristic summary and public key of the component from the electronic tag of the component. For the sake of brevity, only the scenario shown in (a) in Figure 2 is used as an example for explanation. The authentication process of other scenarios is similar to the authentication process shown in Figure 3. Please refer to the description of the above embodiment and will not be repeated here.

[0115] It should be noted that the methods for generating component features shown in Figure 4 and the method for generating the fused features of the component shown in Figure 5 are merely examples. In actual applications, other methods can be used to generate component features and fused features. For example, the order in which the hash operations are performed on hardware and software parameters can be changed. For example, a hash operation is performed on the component's hardware root of trust to obtain a first hash value; a hash operation is performed on the component's firmware digest and the first hash value to obtain a second hash value; and a hash operation is performed on the identifier and the second hash value to obtain the component's fused features or component features. In another example, at least two hash operations are performed on the hardware parameters, software parameters, and a random number of the authentication object to obtain the component's fused features or component features. The component's electronic label contains the random number, or the manufacturer's published compatibility list contains the random number. This allows a remote device or computer to obtain the random number from the electronic label or compatibility list to generate the component's fused features or component features. This further enhances the security level of the component's fused features or component features, improving the security and reliability of the component.

[0116] In addition, this application does not limit the format of each parameter such as hardware parameters, software parameters, fusion features, features and hash values. They can be text, numbers or binary values.

[0117] For each component in the computer device, compatibility certification can be performed on the component according to the certification method provided in this application. The relevant steps can be referred to the description of the above embodiment and will not be repeated here.

[0118] The authentication method provided in this application can be executed when a computer device is started or when a component in the computer device is started. When the computer device is started, compatibility authentication is performed on the components in the computer device according to the authentication method provided in this application to ensure the security and reliability of the components. When the component is started, compatibility authentication is performed on the component according to the authentication method provided in this application. For example, after the component is restarted and reconnected to the computer device, compatibility authentication is performed on the component according to the authentication method provided in this application. For another example, when the original component is replaced and the new component is reconnected to the computer device, compatibility authentication is performed on the component according to the authentication method provided in this application.

[0119] In other embodiments, the authentication method provided by the present application is not only applied to perform compatibility authentication on components within a computer device, but can also be applied to perform compatibility authentication on the entire machine. For example, the BMC obtains the fusion feature summary and public key of the component from the electronic tag of each component, decrypts the fusion feature summary based on the public key to obtain the fusion feature, compares the fusion feature with the feature of the component to obtain the compatibility authentication result of the component, and implements compatibility authentication for each component running in a single computer device. Optionally, the memory on the backplane of the server stores the electronic tag of the entire machine, and the BMC can obtain the fusion feature summary and public key of each component from the electronic tag of the entire machine, so as to perform compatibility authentication on each component separately. Optionally, the electronic tag of the entire machine contains the fusion feature summary and public key of the entire machine. The fusion feature summary of the entire machine can be obtained by performing a hash operation based on the attributes of multiple components in the computer device. For example, a hash operation is performed on the hardware parameters and software parameters of components such as circuit boards, memories, and PCIe boards in the computer device to obtain the entire machine fusion features of multiple components, and then the entire machine fusion feature summary is calculated based on the private key to obtain the entire machine fusion feature. The BMC decrypts the whole-machine fusion feature summary according to the public key to obtain the whole-machine fusion feature, compares the whole-machine fusion feature with the whole-machine features of multiple components to obtain the compatibility certification result of the whole machine, and realizes the whole-machine compatibility certification of multiple components in the computer equipment.

[0120] It is understood that in order to implement the functions in the above embodiments, the device includes hardware structures and / or software modules that perform the corresponding functions. Those skilled in the art should easily appreciate that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0121] The above text describes in detail the authentication method provided by the present application in conjunction with Figures 1 to 10. The following text will describe the authentication device provided by the present application in conjunction with Figure 10.

[0122] Figure 11 is a schematic diagram of the structure of possible authentication devices provided by this application. These authentication devices can be used to implement the functions of the remote device or computer device in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments. In this embodiment, the authentication device can be the device shown in Figure 1, or it can be a module (such as a chip) applied to the server.

[0123] As shown in Figure 11, the authentication device 1100 includes a communication module 1110, an authentication module 1120, and a storage module 1130. The authentication device 1100 is used to implement the functions of the remote device or computer device in the method embodiments shown in Figures 3, 6, 7, or 10 above.

[0124] As shown in FIG. 11( a ), the authentication apparatus 1100 is used to implement the functions of the remote device in the method embodiments shown in FIG. 3 , FIG. 6 , and FIG. 7 .

[0125] The communication module 1110 is used to obtain hardware parameters and software parameters of the object to be authenticated or characteristics of the object to be authenticated. For example, the communication module 1110 is used to execute step 310 in FIG. 3 .

[0126] The communication module 1110 is further configured to feed back the compatibility authentication result to the computer device.

[0127] The authentication module 1120 is configured to obtain the characteristics of the object to be authenticated based on the hardware parameters and software parameters of the object to be authenticated. For example, the authentication module 1120 is configured to execute step 310b in FIG3 .

[0128] The authentication module 1120 is configured to authenticate the object to be authenticated based on the fusion feature summary indicated by the identifier of the object to be authenticated and the features of the object to be authenticated, and obtain a compatibility authentication result of the object to be authenticated. For example, the authentication module 1120 is configured to execute step 320 in FIG. 3 .

[0129] Optionally, the authentication module 1120 has a feature for performing at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the object to be authenticated.

[0130] The storage module 1130 is used to store the fusion feature summary and the public key to facilitate the execution of the compatibility authentication process.

[0131] As shown in FIG11( b ), the authentication device 1100 is used to implement the functions of the computer device in the method embodiment shown in FIG10 .

[0132] The communication module 1110 is configured to obtain the fusion feature summary and the public key from the compatibility list.

[0133] The authentication module 1120 is configured to obtain the characteristics of the object to be authenticated based on the hardware parameters and software parameters of the object to be authenticated. For example, the authentication module 1120 is configured to execute step 1010 in FIG. 10 .

[0134] The authentication module 1120 is configured to authenticate the object to be authenticated based on the fusion feature summary indicated by the identifier of the object to be authenticated and the features of the object to be authenticated, and obtain a compatibility authentication result of the object to be authenticated. For example, the authentication module 1120 is configured to execute step 1020 in FIG. 10 .

[0135] The storage module 1130 is used to store the features, fused feature summary, and public key of the object to be authenticated, so as to facilitate the execution of the compatibility authentication process.

[0136] It should be understood that the authentication device 1100 of the embodiments of the present application can be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. Alternatively, when the authentication method shown in FIG. 3 , FIG. 6 , FIG. 7 , or FIG. 10 is implemented using software, the authentication device 1100 and its modules can also be software modules.

[0137] According to the embodiment of the present application, the authentication device 1100 may correspond to executing the method described in the embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the authentication device 1100 are respectively for realizing the corresponding processes of each method in Figure 3, Figure 6, Figure 7 or Figure 10. For the sake of brevity, they will not be repeated here.

[0138] FIG12 is a schematic diagram of the structure of a controller 1200 provided in this application. As shown in FIG12 , controller 1200 includes a processor 1210, a bus 1220, a memory 1230, a communication interface 1240, and a memory unit 1250 (also referred to as a main memory unit). Processor 1210, memory 1230, memory unit 1250, and communication interface 1240 are connected via bus 1220.

[0139] It should be understood that in this embodiment, the processor 1210 may be a CPU, but may also be other general-purpose processors, digital signal processors (DSPs), ASICs, FPGAs 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.

[0140] Communication interface 1240 is used to enable communication between controller 1200 and external devices or components. In the present application, when controller 1200 is used to implement the functions of the remote device shown in Figures 3, 6, and 7, communication interface 1240 is used to obtain the fused feature digest, public key, and characteristics of the object to be authenticated, so that processor 1210 can authenticate the object to be authenticated based on the fused feature digest and the characteristics of the object to be authenticated, and obtain a compatibility authentication result for the object to be authenticated. When controller 1200 is used to implement the functions of the computer device shown in Figure 10, communication interface 1240 is used to obtain the fused feature digest and public key, so that processor 1210 can authenticate the object to be authenticated based on the fused feature digest and the characteristics of the object to be authenticated, and obtain a compatibility authentication result for the object to be authenticated.

[0141] The bus 1220 may include a path for transmitting information between the above-mentioned components (such as the processor 1210, the memory unit 1250, and the memory 1230). In addition to the data bus, the bus 1220 may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, various buses are labeled as bus 1220 in the figure. The bus 1220 may be a Peripheral Component Interconnect Express (PCIe) bus, an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus 1220 can be divided into an address bus, a data bus, a control bus, etc.

[0142] As an example, the controller 1200 may include multiple processors. The processor may be a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or computing units for processing data (e.g., computer program instructions).

[0143] It is worth noting that Figure 12 only takes the controller 1200 including 1 processor 1210 and 1 memory 1230 as an example. Here, the processor 1210 and the memory 1230 are respectively used to indicate a type of device or equipment. In a specific embodiment, the number of each type of device or equipment can be determined according to business requirements.

[0144] Memory unit 1250 may be a volatile memory pool or a non-volatile memory pool, or may include both volatile and non-volatile memories. Non-volatile memories may be read-only memories (ROMs), programmable read-only memories (PROMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), or flash memory. Volatile memories may be random access memories (RAMs), which serve as external cache memory. By way of example and not limitation, many forms of RAM may be used, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). Memory unit 1250 is used to store features of an object to be authenticated, a fused feature digest, a public key, compatibility authentication results, and the like.

[0145] The memory 1230 may correspond to a storage medium used to store information such as features of the object to be authenticated, fused feature digests, public keys, etc. in the above method embodiments, for example, a disk such as a mechanical hard disk or a solid-state drive.

[0146] It should be understood that the controller 1200 according to this embodiment may correspond to the authentication device 1100 in this embodiment, and may correspond to the corresponding subject executing any method according to Figure 3, Figure 6, Figure 7 or Figure 10, and the above-mentioned and other operations and / or functions of each module in the authentication device 1100 are respectively for realizing the corresponding processes of each method in Figure 3, Figure 6, Figure 7 or Figure 10, which will not be repeated here for the sake of brevity.

[0147] Figure 13 is a schematic diagram of the structure of a controller 1300 provided in this application. As shown in Figure 13, controller 1300 includes a logic circuit 1310 and a power supply circuit 1320; wherein power supply circuit 1320 is used to supply power to logic circuit 1310; logic circuit 1310 is used to execute the operation steps of the authentication method described in the above method embodiment.

[0148] The present application provides a communication system, which includes a remote device and a computer device. The computer device includes multiple components. The remote device is used to execute the operating steps of the authentication method described in the above method embodiment to achieve compatibility authentication of multiple components.

[0149] The method steps in this embodiment can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a computing device. Of course, the processor and storage medium can also exist as discrete components in a computing device.

[0150] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is performed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instruction can be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it can also be an optical medium, such as a digital video disc (DVD); it can also be a semiconductor medium, such as a solid state drive (SSD). The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present application, and such modifications or substitutions should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. An authentication method, characterized in that: include: Acquiring the characteristics of the object to be authenticated according to the hardware parameters and software parameters of the object to be authenticated; The object to be authenticated is authenticated according to the fusion feature summary indicated by the identification of the object to be authenticated and the feature of the object to be authenticated, and a compatibility authentication result of the object to be authenticated is obtained, wherein the compatibility authentication result includes a compatibility authentication passed and a compatibility authentication failed, the fusion feature summary is used to indicate that the component passes the compatibility test based on the fusion feature of the component, and the fusion feature of the component is generated based on the hardware parameters and software parameters of the component.

2. The method according to claim 1, characterized in that Acquiring the characteristics of the object to be authenticated according to the hardware parameters and software parameters of the object to be authenticated includes: Perform at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated.

3. The method according to claim 2, characterized in that The hardware parameters include the hardware trusted root of the object to be authenticated and the identifier, and the software parameters include the firmware digest of the object to be authenticated; Performing at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated includes: Performing a hash operation on the hardware trusted root of the object to be authenticated to obtain a first hash value; Performing a hash operation on the identifier and the first hash value to obtain a second hash value; A hash operation is performed on the firmware digest of the object to be authenticated and the second hash value to obtain the characteristics of the object to be authenticated.

4. The method according to claim 2, characterized in that: The hardware parameter includes the identifier, and the software parameter includes the firmware digest of the object to be authenticated; Performing at least two hash operations on the hardware parameters and software parameters of the object to be authenticated to obtain the characteristics of the object to be authenticated includes: Performing a hash operation on the identifier to obtain a first hash value; A hash operation is performed on the firmware digest of the object to be authenticated and the first hash value to obtain the characteristics of the object to be authenticated.

5. The method according to any one of claims 1 to 4, characterized in that The fusion feature of the component is generated based on at least two hash operations of the hardware parameters and software parameters of the component.

6. The method according to any one of claims 1 to 5, characterized in that Authenticating the object to be authenticated according to the fused feature summary indicated by the identification of the object to be authenticated and the feature of the object to be authenticated, comprising: Decrypting the fusion feature summary according to the public key to obtain the fusion feature; The compatibility authentication result of the object to be authenticated is determined according to the comparison result between the fusion feature and the feature of the object to be authenticated.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The fused feature summary and the public key are obtained from the electronic tag of the object to be authenticated, and the public key is used to decrypt the fused feature summary.

8. The method according to any one of claims 1 to 6, characterized in that The method further comprises: According to the identifier of the object to be authenticated, the fused feature summary and the public key are obtained from the compatibility list released by the manufacturer, and the public key is used to decrypt the fused feature summary.

9. The method according to any one of claims 1 to 8, characterized in that The object to be authenticated includes any one of a memory, a circuit board or a Peripheral Component Interconnect Express (PCIe) card.

10. A controller, characterized in that: The controller includes a logic circuit and a power supply circuit; wherein the power supply circuit is used to supply power to the logic circuit; and the logic circuit is used to execute the operation steps of the method described in any one of claims 1 to 9.

11. The controller according to claim 10, characterized in that: The logic circuit includes a baseboard management controller BMC or a control unit.

12. A computer device, characterized in that: The computer device includes a memory, a controller and multiple components, the memory is used to store a set of computer instructions; when the controller executes the set of computer instructions, the operating steps of the method described in any one of claims 1 to 9 are performed to achieve compatibility authentication of the multiple components.

Citation Information

Patent Citations

  • Method for implementing computer terminal safety admittance based on credible authentication gateway

    CN101330494A

  • Soft hardware integrality detection method and system for network appliance

    CN101588374A

  • System for verification of integrity of unmanned aerial vehicles

    CN109392310A

  • Physics-based authentication

    US20150156184A1