Equipment management method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides an equipment management method and device, equipment, a storage medium and a program product, relates to the technical field of block chains, and can also be applied to the field of financial science and technology. The method comprises the following steps: receiving encrypted information sent by first communication equipment; wherein the encrypted information is obtained by encrypting the first attribute information and the identifier of the first storage equipment; determining second attribute information of the first warehousing equipment and circulation information of the first warehousing equipment according to the identifier of the first warehousing equipment, a mapping relation between the identifier of the equipment and the attribute information, and a mapping relation between the identifier of the equipment and the circulation information; under the condition that the first attribute information and the second attribute information are the same, performing hash processing on the identifier of the first warehousing equipment, the first attribute information and the circulation information of the first warehousing equipment to obtain a hash value corresponding to the first warehousing equipment; and storing the hash value corresponding to the first warehousing equipment in the block chain. According to the invention, unified management of the information of the first warehousing equipment is realized.

Description

Equipment management methods, devices, equipment, storage media and program products Technical Field

[0001] This application relates to the field of blockchain technology, and can also be used in the field of financial technology, particularly to a device management method, apparatus, equipment, storage medium, and program product. Background Technology

[0002] The server room is the core infrastructure of a data center. To ensure the stable operation of the data center, it is necessary to manage the equipment in the server room.

[0003] In related technologies, when any device in a data center is put into operation, its identifier and information are obtained through scanning, and then stored in a centralized database. However, the above method cannot achieve unified management of device lifecycle information. Summary of the Invention

[0004] This application provides a device management method, apparatus, equipment, storage medium, and program product to achieve unified management of information on the first inbound device.

[0005] In a first aspect, embodiments of this application provide a device management method applied to a server, comprising:

[0006] The device receives encrypted information sent by a first communication device; wherein the encrypted information is obtained by encrypting first attribute information and the identifier of a first storage device; the first communication device is used to manage at least one storage device on the rack; the first storage device is one of at least one storage device.

[0007] Based on the identifier of the first inbound device, the mapping relationship between the device identifier and attribute information, and the mapping relationship between the device identifier and circulation information, the second attribute information of the first inbound device and the circulation information of the first inbound device are determined.

[0008] If the first attribute information and the second attribute information are the same, perform hash processing on the identifier, first attribute information and circulation information of the first inbound device to obtain the hash value corresponding to the first inbound device;

[0009] The hash value corresponding to the first device entering the warehouse is stored in the blockchain.

[0010] Secondly, embodiments of this application provide a device management method applied to a first communication device, the first communication device being used to manage at least one storage device on a rack, including:

[0011] The system receives the identifier of the first inbound device and the factory information of the first inbound device sent by the second communication device; the first inbound device is one of at least one inbound device; the factory information of the first inbound device is obtained by scanning the attribute tags on the first inbound device;

[0012] Based on the rack where the first inbound device is located, the position of the first inbound device on the rack, and the factory information of the first inbound device, generate the first attribute information of the first inbound device;

[0013] The first attribute information and the identifier of the first inbound device are encrypted to obtain encrypted information;

[0014] Send encrypted information to the server.

[0015] Thirdly, embodiments of this application provide a device management method applied to a second communication device, comprising:

[0016] Receive the identifier and factory information of the first inbound device sent by the scanning device;

[0017] The first communication device sends the identifier of the first inbound device and the factory information of the first inbound device to the first communication device at a preset time interval; the first communication device is used to manage at least one inbound device on the rack; the first inbound device is one of at least one inbound device.

[0018] Fourthly, embodiments of this application provide a device management apparatus applied to a server, comprising:

[0019] A first receiving model is used to receive encrypted information sent by a first communication device; wherein the encrypted information is obtained by encrypting first attribute information and the identifier of the first storage device; the first communication device is used to manage at least one storage device on the rack; the first storage device is one of at least one storage device.

[0020] The determination module is used to determine the second attribute information of the first inbound device and the circulation information of the first inbound device based on the identifier of the first inbound device, the mapping relationship between the device identifier and attribute information, and the mapping relationship between the device identifier and circulation information.

[0021] The first processing module is used to perform hash processing on the identifier, first attribute information and circulation information of the first inbound device when the first attribute information and the second attribute information are the same, so as to obtain the hash value corresponding to the first inbound device.

[0022] The storage module is used to store the hash value corresponding to the first inbound device in the blockchain.

[0023] Fifthly, embodiments of this application provide a device management apparatus applied to a first communication device, the first communication device being used to manage at least one storage device on a rack, including:

[0024] The second receiving module is used to receive the identifier of the first warehouse entry device and the factory information of the first warehouse entry device sent by the second communication device; the first warehouse entry device is one of at least one warehouse entry device; the factory information of the first warehouse entry device is obtained by scanning the attribute tags on the first warehouse entry device;

[0025] The generation module is used to generate the first attribute information of the first inbound device based on the rack where the first inbound device is located, the position of the first inbound device on the rack, and the factory information of the first inbound device.

[0026] The second processing module is used to encrypt the first attribute information and the identifier of the first inbound device to obtain encrypted information.

[0027] The first sending module is used to send encrypted information to the server.

[0028] Sixthly, embodiments of this application provide a device management apparatus applied to a second communication device, comprising:

[0029] The third receiving module is used to receive the identifier of the first inbound device and the factory information of the first inbound device sent by the scanning device.

[0030] The second sending module is used to send the identifier of the first warehouse entry device and the factory information of the first warehouse entry device to the first communication device according to a preset time interval; the first communication device is used to manage at least one warehouse entry device on the rack; the first warehouse entry device is one of at least one warehouse entry device.

[0031] Seventhly, embodiments of this application provide a device management device, including:

[0032] At least one processor; and

[0033] A memory that is communicatively connected to at least one processor; wherein,

[0034] The memory stores instructions executable by at least one processor, which, when executed by at least one processor, cause the at least one processor to perform the device management method involved in the first aspect, or the device management method involved in the second aspect, or the device management method involved in the third aspect.

[0035] Eighthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the device management method as described in the first aspect, or the device management method as described in the second aspect, or the device management method as described in the third aspect.

[0036] Ninthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the device management method involved in the first aspect, or the device management method involved in the second aspect, or the device management method involved in the third aspect.

[0037] The device management method, apparatus, equipment, storage medium, and program product provided in this application embodiment involve a server verifying the accuracy of the first attribute information upon receiving the identifier and first attribute information of a first inbound device. If the first attribute information is confirmed to be accurate, the server hashes the identifier, first attribute information, and circulation information of the first inbound device and stores the resulting hash value in a blockchain. Since the first attribute information of the first inbound device indicates its factory and location information, and the circulation information indicates its information during procurement, maintenance, and other stages, the device management method provided in this application embodiment achieves unified management of information at each stage of the first inbound device. Furthermore, after receiving the first attribute information, the server verifies its accuracy to ensure the accuracy of the factory and location information of the first inbound device; storing the hash value corresponding to the first inbound device in the blockchain ensures that the identifier, first attribute information, and circulation information of the first inbound device cannot be tampered with after it is listed, thus improving the security of unified management of information at each stage of the first inbound device. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0039] Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this application;

[0040] Figure 2 is a flowchart illustrating a device management method provided in an embodiment of this application;

[0041] Figure 3 is a schematic diagram of a process for changing the circulation information of the first warehousing device according to an embodiment of this application;

[0042] Figure 4 is a schematic diagram of a process for changing the location of the first warehousing device according to an embodiment of this application;

[0043] Figure 5 is a schematic diagram of an equipment management system provided in an embodiment of this application;

[0044] Figure 6 is a schematic diagram of a device management method provided in an embodiment of this application;

[0045] Figure 7 is a schematic diagram of the structure of an equipment management device provided in an embodiment of this application;

[0046] Figure 8 is a schematic diagram of another device management device provided in an embodiment of this application;

[0047] Figure 9 is a schematic diagram of another device management device provided in an embodiment of this application;

[0048] Figure 10 is a schematic diagram of the structure of an equipment management device provided in an embodiment of this application.

[0049] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0050] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0051] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, have taken necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation access points for users to choose to authorize or refuse.

[0052] Furthermore, the technical solution involved in this application, which involves big data analysis of user information (including but not limited to personal biometrics, identity data, consumption data, asset data, electronic terminal operation data, etc.) and the use of artificial intelligence technology for automated decision-making, and makes decisions that have a significant impact on personal rights based on the results of automated decision-making, provides users with corresponding operation entry points for users to choose to agree to or reject the results of automated decision-making; if the user chooses to reject, the process will proceed to the expert decision-making process.

[0053] It should be noted that the device management method, apparatus, equipment, storage medium and program products provided in this application can be used in the field of blockchain technology, the field of fintech, or any field other than blockchain technology and fintech. The application fields of the device management method, apparatus, equipment, storage medium and program products in this application are not limited.

[0054] First, let me explain the terms used in this application:

[0055] Blockchain is a decentralized database system based on distributed ledger technology. The core of blockchain lies in storing data through cryptography, consensus mechanisms, and a chain-like data structure. Data stored in the blockchain has the characteristics of transparent sharing and immutability.

[0056] Data center: A physical location used to house computing, storage, and networking equipment, and to provide a data processing and business system operating environment, providing stable, efficient, and secure computing power support for enterprise digital business.

[0057] With the continuous improvement of 5G and AI computing power, the resource density of servers, network devices and storage devices continues to increase. Traditional physical servers are evolving into hybrid architectures such as virtualization and containerized graphics processing unit (GPU) clusters. The number and types of equipment in data center server rooms are increasing. In order to ensure the stable operation of data centers, it is necessary to manage the first batch of equipment entering the server room.

[0058] In related technologies, for each first-entry device in the data center, a physical tag is affixed to indicate the device's identification and manufacturing information. When the device is racked, the physical tag is scanned to obtain the device's identification and manufacturing information, which is then stored in a centralized database. Furthermore, information regarding the procurement, maintenance, and disposal of the first-entry device is stored in different tables or management systems, with different administrators managing the information at each stage.

[0059] However, because the identification, manufacturing information, and other information regarding the first batch of equipment entering the warehouse are scattered across different management systems and managed by different personnel, unified management of the information is impossible. Furthermore, the security of managing the first batch of equipment is low because physical tags are easily damaged, information stored in centralized databases or other tables is easily tampered with or leaked within the management system.

[0060] This application provides a device management method. When a first device is placed in the warehouse, its identifier and first attribute information are received. If the first attribute information is accurate, the circulation information of the first device is determined. Then, the identifier, first attribute information, and circulation information of the first device are hashed to obtain a hash value corresponding to the first device, and this hash value is stored in the blockchain. This achieves unified management of information at each stage of the first device's entry into the warehouse. Furthermore, based on the verification of the first attribute information to ensure its accuracy, and the immutability of data in the blockchain, the security of unified management of information at each stage of the first device's entry into the warehouse is improved.

[0061] To facilitate understanding, the application scenarios applicable to the embodiments of this application will be briefly described below with reference to Figure 1.

[0062] Figure 1 is a schematic diagram of an application scenario provided by an embodiment of this application. As shown in Figure 1, it includes a first communication device 11, a second communication device 12, and a server 13. The first communication device 11 stores the identifier and first attribute information of at least one first inbound device. The second communication device 12 corresponds one-to-one with the first inbound device, and for any second communication device 12, the second communication device 12 stores the identifier and manufacturing information of the corresponding first inbound device. The server 13 can be the backend server of the device management system.

[0063] In practical applications, the first communication device 11 and the server 13 can transmit data. For example, the first communication device 11 sends encrypted information to the server 13. The first communication device 11 and the second communication device 12 can transmit data. For example, the second communication device 12 can send the identifier and factory information of the first warehouse device to the first communication device 11.

[0064] It should be noted that Figure 1 is merely an example of a system architecture diagram and is not intended to limit the scope of system architecture diagrams.

[0065] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0066] Figure 2 is a flowchart illustrating a device management method according to an embodiment of this application. Referring to Figure 2, the method may include the following steps:

[0067] S21. Receive encrypted information sent by the first communication device; wherein the encrypted information is obtained by encrypting the first attribute information and the identifier of the first storage device; the first communication device is used to manage at least one storage device on the rack; the first storage device is one of at least one storage device.

[0068] The execution entity in this application embodiment can be a backend server of the root cause localization system, or a root cause localization device installed in the server. The root cause localization device can be implemented by software, or by a combination of software and hardware.

[0069] Inbound equipment refers to computing, storage, and network devices in a computer room. For example, inbound equipment may include servers, switches, and other devices. In some embodiments, the computer room includes racks for housing at least one inbound device. Since at least one inbound device can be placed on a rack, it can be managed through a first communication device, which stores the attribute information and identifier of each of the at least one inbound device. Specifically, for each of the at least one inbound device, the attribute information indicates its manufacturing information, location information, etc. The identifier of the first inbound device may be, for example, its device code; the manufacturing information may include, for example, the device serial number (SN) and device model.

[0070] The first inbound device refers to the inbound device in the computer room. When the first inbound device is racked, that is, when the first inbound device is placed on the rack, the first communication device encrypts the attribute information and identifier of the first inbound device to obtain encrypted information, and then sends the encrypted information to the server. The first attribute information is the attribute information of the first inbound device.

[0071] S22. Based on the identifier of the first inbound device, the mapping relationship between the device identifier and attribute information, and the mapping relationship between the device identifier and circulation information, determine the second attribute information of the first inbound device and the circulation information of the first inbound device.

[0072] After the server decrypts the encrypted information, it obtains the first attribute information and the identifier of the first device to be entered into the database.

[0073] In some embodiments, the server includes second attribute information of the first inbound device and circulation information of the first inbound device. The second attribute information of the first inbound device indicates its original factory information and preset location information; the circulation information of the first inbound device indicates information about the first inbound device at various stages such as procurement, maintenance, and disposal. For example, the circulation information of the first inbound device may indicate contract information during the procurement process, maintenance records during maintenance, and the operating status of the first inbound device.

[0074] The mapping relationship between device identifiers and attribute information includes identifiers of multiple devices and second attribute information of multiple devices. For each of the multiple devices, there is a mapping relationship between the device identifier and the device's second attribute information. In some embodiments, the second attribute information of the first device to be stored can be determined based on the identifier of the first device to be stored and the mapping relationship between the device identifiers and attribute information.

[0075] For example, suppose the mapping relationship between device identifiers and attribute information is as shown in Table 1:

[0076] Table 1

[0077]

[0078] If the identifier of the first inbound device is AABEDA, then based on the identifier of the first inbound device and the mapping relationship between the device identifier and attribute information, the second attribute information of the first inbound device is determined to be: the device serial number is XXXX; the preset position is the third row on the second rack.

[0079] The mapping relationship between device identifiers and circulation information includes the identifiers of multiple devices and the circulation information of multiple devices. For each device among the multiple devices, there is a mapping relationship between the device identifier and the circulation information of that device. In some embodiments, the circulation information of the first inbound device can be determined based on the identifier of the first inbound device and the mapping relationship between the device identifiers and circulation information.

[0080] For example, suppose the mapping relationship between device identifiers and circulation information is as shown in Table 2:

[0081] Table 2

[0082]

[0083] If the identifier of the first inbound device is AABEDA, then based on the identifier of the first inbound device and the mapping relationship between the device identifier and the circulation information, the circulation information of the first inbound device is determined to be: Purchase Contract 1; Maintenance Record A.

[0084] S23. If the first attribute information and the second attribute information are the same, perform hash processing on the identifier, first attribute information and circulation information of the first inbound device to obtain the hash value corresponding to the first inbound device.

[0085] In some embodiments, since the factory information of the first receiving device is affixed to the first entry device in the form of a physical label, the factory information of the first receiving device may be damaged or modified before the first receiving device is put on the shelf. Furthermore, the position of the first receiving device is predetermined before it is put on the shelf.

[0086] To prevent the factory information of the first inbound device from being corrupted or modified, and / or from being placed in the wrong location during the initial inbound process, the server compares the received first attribute information with the second attribute information of the first inbound device to verify the accuracy of the first attribute information. This verifies whether the factory information of the first inbound device is accurate and whether it has been placed in the correct location. If the first and second attribute information are the same, it indicates that the factory information of the first inbound device is accurate and that it has been placed in the correct location.

[0087] At this point, the identifier, first attribute information, and circulation information of the first inbound device can be managed. Specifically, the identifier, first attribute information, and circulation information of the first inbound device are hashed to obtain a hash value corresponding to the first inbound device. It should be noted that at this point, the hash value of the first inbound device uniquely indicates its identifier, first attribute information, and circulation information. The identifier, first attribute information, and circulation information of the first inbound device can be determined based on its hash value. Furthermore, if any of the identifier, first attribute information, or circulation information of the first inbound device changes, the resulting hash value will be inconsistent with the hash value corresponding to the first inbound device. Therefore, the hash value of the first inbound device can be used to determine whether its identifier, first attribute information, and circulation information have been tampered with.

[0088] S24. Store the hash value corresponding to the first inbound device in the blockchain.

[0089] After obtaining the hash value corresponding to the first device entering the database, the server stores the hash value in the blockchain. Because data stored in the blockchain is immutable, this prevents the hash value corresponding to the first device from being tampered with.

[0090] In the embodiment shown in Figure 2, when the first inbound device is mounted, the server receives the identifier and first attribute information of the first inbound device. Since the server stores attribute information of multiple devices, it determines the second attribute information of the first inbound device from the second attribute information of multiple devices based on the identifier of the first inbound device. Then, the first attribute information of the first inbound device is verified based on the second attribute information of the first inbound device. If the first attribute information and the second attribute information are the same, it means that the first attribute information is accurate. At this time, the identifier, first attribute information, and circulation information of the first inbound device are hashed to obtain the hash value corresponding to the first inbound device, and the hash value corresponding to the first inbound device is stored in the blockchain.

[0091] In the above method, the circulation information of the first inbound device is used to indicate information about the first inbound device in multiple stages such as procurement and operation and maintenance. The identifier, first attribute information, and circulation information of the first inbound device are hashed, and the hash value corresponding to the first inbound device is stored in the blockchain, realizing unified management of the information of the first inbound device at each stage. In addition, when the server receives the identifier and first attribute information of the first inbound device, it receives encrypted information obtained by encrypting the identifier and first attribute information of the first inbound device, ensuring the security of the identifier and first attribute information during transmission; when the first inbound device is put into storage, the accuracy of the first attribute information is verified, avoiding the possibility that the factory information of the first inbound device may be damaged or tampered with before it is put into storage; and storing the hash value of the first inbound device in the blockchain prevents the possibility that the first attribute information and circulation information of the first inbound device may be tampered with after it is put into storage, thus improving the security of unified management of the information of the first inbound device at each stage.

[0092] Based on the embodiment shown in Figure 2, in some embodiments, the purchase contract, operation and maintenance records, etc., of the first inbound equipment may change, in which case it is necessary to modify the circulation information of the first inbound equipment. Below, with reference to the embodiment shown in Figure 3, the process for modifying the circulation information of the first inbound equipment provided by this application embodiment will be further explained.

[0093] Figure 3 is a schematic diagram illustrating a process for modifying the flow information of a first warehousing device according to an embodiment of this application. Referring to Figure 3, the process may include the following steps:

[0094] S31. Receive first instruction information sent by the client, wherein the first inbound device includes at least one type of operation and maintenance management object, and the first instruction information is used to indicate that the operation and maintenance management object of the first inbound device has changed.

[0095] At least one type of operation and maintenance management object refers to the operation and maintenance management object of the first inbound equipment at different stages. For example, at least one type of operation and maintenance management object may include the operation and maintenance management object of the first inbound equipment at the procurement stage, the operation and maintenance stage, and the scrapping stage.

[0096] Among them, the operation and maintenance management object of the first inbound equipment in the procurement stage can be, for example, the procurement contract of the first inbound equipment; the operation and maintenance management object of the first inbound equipment in the operation and maintenance stage can include, for example, the software and hardware of the first inbound equipment; the operation and maintenance management object of the first inbound equipment in the scrapping stage can be, for example, the scrapping time node of the first inbound equipment.

[0097] The first instruction information includes the identifier of the target type, the identifier of the first operation and maintenance management object that has changed in the target type, and the identifier of the second operation and maintenance management object after the change; the circulation information of the first inbound equipment is used to record the operation and maintenance management object of the first inbound equipment, and the circulation process of the operation and maintenance management object of the first inbound equipment.

[0098] The target type identifier indicates the type of operation and maintenance management object that needs to be changed, among at least one type of operation and maintenance management object. The first operation and maintenance management object refers to the operation and maintenance management object that needs to be changed.

[0099] For example, suppose the identifier of the target type indicates the procurement process of the first inbound equipment; the identifier of the first operation and maintenance management object is used to indicate the procurement contract 1 of the first inbound equipment at the current time; and the identifier of the second operation and maintenance management object is used to indicate the revised procurement contract as procurement contract 2.

[0100] The circulation information of the first inbound equipment includes the identifier of the operation and maintenance management object of the first inbound equipment, which is used to record the operation and maintenance management object of the first inbound equipment. In addition, the circulation information of the first inbound equipment also includes the circulation process of the operation and maintenance management object of the first inbound equipment.

[0101] For each maintenance management object of the first inbound device, the flow process of the maintenance management object is used to indicate the change process of the maintenance management object. For example, assuming the maintenance management object is the board of the first inbound device, and the current board of the first inbound device is board X, and the board before the change was Y, then the flow process of the maintenance management object can be: the board of the first inbound device is changed from board Y to board X.

[0102] S32. Update the flow information of the first inbound device according to the first instruction information to obtain the first flow information.

[0103] Specifically, the method for updating the circulation information of the first inbound device can be as follows: based on the identifier of the target type, the identifier of the first maintenance management object, and the identifier of the second maintenance management object, update the maintenance management object of the first inbound device and the circulation process of the maintenance management object of the first inbound device to obtain the first circulation information; wherein, the first circulation information is used to record the updated maintenance management object of the first inbound device and the updated circulation process of the maintenance management object of the first inbound device.

[0104] Based on the identifier of the target type, the type of the operation and maintenance management object that needs to be changed is determined in at least one type. Then, based on the identifier of the first operation and maintenance management object, the first operation and maintenance management object is determined from among multiple operation and maintenance management objects under that type. Finally, the identifier of the first operation and maintenance management object in the flow information of the first inbound device is changed to the identifier of the second operation and maintenance management object. In addition, the flow process of the operation and maintenance management object of the first inbound device is updated to obtain the updated flow process. For example, the updated flow process may include: the second operation and maintenance management object is obtained by changing the first operation and maintenance object.

[0105] Based on the above method, the first flow information can be obtained, which includes the identifier of the second operation and maintenance management object and the updated flow process.

[0106] S33. Perform hash processing on the identifier, first attribute information and first circulation information of the first inbound device to generate a first hash value.

[0107] After the server modifies the circulation information of the first inbound device and obtains the first circulation information, it performs hash processing on the identifier, first attribute information and first circulation information of the first inbound device. The resulting first hash value is used to identify the identifier, first attribute information and first circulation information of the first inbound device.

[0108] It should be noted that if any of the information in the first entry device's identifier, first attribute information, and first circulation information is changed, the generated hash value will be different from the first hash value.

[0109] S34. Update the hash value corresponding to the first inbound device based on the first hash value.

[0110] After obtaining the first hash value, the server updates the first hash value to the hash value corresponding to the first data entry device, obtains the updated hash value corresponding to the first data entry device, and stores the updated hash value corresponding to the first data entry device in the blockchain.

[0111] In the embodiment shown in Figure 3, when it is necessary to change the flow information of the first inbound device, the flow information of the first inbound device is changed by using the identifier of the target type, the identifier of the first maintenance management object, and the identifier of the second maintenance management object in the instruction information, thus obtaining the first flow information. In this way, the identifier of the first maintenance management object that needs to be changed in the flow information of the first inbound device can be precisely changed to the identifier of the second maintenance management object, and this change is recorded in the flow process of the maintenance management object of the first inbound device. This improves the flexibility and efficiency of managing the flow information of the first inbound device.

[0112] Based on the above embodiments, after the first receiving device is put into service, it may be necessary to change the location of the first receiving device. Below, with reference to Figure 4, we will further explain the content regarding the change of the location of the first receiving device provided in this application embodiment.

[0113] Figure 4 is a schematic flowchart illustrating the process of changing the location of a first warehousing device according to an embodiment of this application. Referring to Figure 4, the process may include the following steps:

[0114] S41. Receive second indication information sent by the client. The second indication information is used to indicate that the current position of the first inbound device has changed. The current position of the first inbound device includes the rack where the first inbound device is located, and / or the position of the first inbound device on the rack.

[0115] The first attribute information is used to indicate the factory information and location of the first inbound device. The factory information of the first inbound device is obtained by scanning the attribute tags on the first inbound device. The attribute tags on the first inbound device can be physical tags that indicate the factory information of the first inbound device.

[0116] In some embodiments, a change in the current location of the first receiving device may include, for example, a change in the rack on which the first receiving device is located, and / or a change in the position of the first receiving device on the rack. The position of the first receiving device on the rack may be, for example, the U-position information of the first receiving device, used to indicate the vertical installation position and space occupancy of the first receiving device within the rack.

[0117] S42. Based on the second instruction information, update the first attribute information and the circulation information of the first warehousing device to obtain the third attribute information and the second circulation information.

[0118] The second indication information is used to indicate the current location and the changed location of the first inbound device; the flow information of the first inbound device is used to record the flow process of the location of the first inbound device. In some embodiments, the flow process of the location of the first inbound device is used to indicate the change process of the location of the first inbound device.

[0119] In some embodiments, the method for updating the first attribute information and the flow information of the first inbound device according to the second indication information can be as follows: update the position of the first inbound device according to the current position and the changed position to obtain the third attribute information; update the flow process of the position of the first inbound device according to the current position and the changed position to obtain the second flow information; wherein, the third attribute information is used to indicate the updated position of the first inbound device; the second flow information is used to record the flow process of the first inbound device after the position is updated.

[0120] The first attribute information is used to indicate the current location of the first inbound device. Based on the current location and the changed location of the first inbound device indicated in the second indication information, the current location of the first inbound device indicated in the first attribute information is updated to the changed location. The resulting third attribute information is used to indicate the updated location of the first inbound device.

[0121] In addition, the flow process of the first inbound device's location needs to be updated to obtain the updated flow process of the first inbound device's location. For example, assuming that the current location of the first inbound device is position O on rack M; and the changed location of the first inbound device is position P on rack N, then the updated flow process of the first inbound device's location may include: the first inbound device being moved from position O on rack M to position P on rack N.

[0122] S43. Perform hash processing on the identifier, third attribute information and second circulation information of the first inbound device to generate a second hash value.

[0123] After updating the first attribute information and flow information of the first inbound device, the server obtains the third attribute information and the second flow information. Then, the identifier of the first inbound device, the third attribute information, and the second flow information are hashed, and the generated second hash value is used to represent the identifier of the first inbound device, the third attribute information, and the second flow information.

[0124] It should be noted that if any of the identifier of the first inbound device, the third attribute information, or the second flow information is changed, the generated hash value will be different from the second hash value.

[0125] S44. Determine the second hash value as the hash value corresponding to the first data entry device.

[0126] After obtaining the second hash value, the server updates the second hash value with the hash value corresponding to the first input device, obtains the updated hash value corresponding to the first input device, and stores the updated hash value corresponding to the first input device in the blockchain.

[0127] In the embodiment shown in Figure 4, when the location of the first inbound device needs to be changed, the current location of the first inbound device indicated in the first attribute information is updated to the changed location using the current location and the changed location indicated in the second indication information, thus obtaining the third attribute information. Furthermore, the flow process of the first inbound device's location needs to be updated to obtain the second flow information. In this way, while changing the current location of the first inbound device indicated in the first attribute information, the process of changing the location of the first inbound device is also recorded. This method improves the flexibility and efficiency of managing the location information of the first inbound device.

[0128] In the embodiments shown in Figures 3 and 4, a normal method for modifying the flow information and first attribute information of the first inbound device is described. In some embodiments, there are cases where the flow information and first attribute information of the first inbound device are modified abnormally. For example, before the first inbound device is put on the shelf, the factory information of the first inbound device is tampered with. In this case, the first attribute information and the second attribute information of the first inbound device received by the server are different.

[0129] In some embodiments, if the first attribute information and the second attribute information are different, a prompt message is sent to the client; the prompt message indicates that the first attribute information is abnormal. After receiving the prompt message through the client, the staff checks the attribute labels on the first inbound device and changes the attribute labels on the first inbound device. The changed attribute labels on the first inbound device are then rescanned.

[0130] Based on the above embodiments, the device management system provided in the embodiments of this application will be described below with reference to Figure 5.

[0131] Figure 5 is a schematic diagram of a device management system provided in an embodiment of this application. Referring to Figure 5, the system includes an information verification module, a blockchain storage module, a management module, a display module, and a prompting module.

[0132] The information verification module, upon receiving encrypted information from the first communication device, decrypts the encrypted information to obtain the identifier and first attribute information of the first storage device. Then, it determines the second attribute information of the first storage device using the identifier and verifies the accuracy of the first attribute information based on the second attribute information. If the first attribute information is accurate, it determines the flow information of the first storage device based on the identifier, and then performs hash processing on the identifier, first attribute information, and flow information to obtain the hash value corresponding to the first storage device. Finally, it transmits the hash value corresponding to the first storage device to the storage module.

[0133] It should be noted that, to ensure the security of the hash value corresponding to the first inbound device, the hash value can be transmitted to the storage module using encrypted transmission. For example, Transport Layer Security (TLS) can be used to encrypt the hash value of the first inbound device before transmitting it to the storage module.

[0134] The blockchain storage module verifies whether the hash value corresponding to the first inbound device meets the requirements. If the hash value of the first inbound device meets the requirements, it is stored in the blockchain. For example, the verification method for whether the hash value corresponding to the first inbound device meets the requirements can be: using algorithms such as Proof of Work (PoW), Proof of Stake (PoS), or Practical Byzantine Fault Tolerance (PBFT) to verify whether the hash value corresponding to the first inbound device meets the requirements.

[0135] The management module is used to dynamically construct and update the resource relationship network among multiple inbound devices in the data center. Specifically, it obtains the primary attribute information and flow information of each inbound device, determines the association between these information, and constructs a resource relationship network based on these associations. This network is then displayed through the display module. This allows staff to easily understand the real-time operating status and other information of the multiple inbound devices in the data center. Furthermore, the management module also manages access permissions for each inbound device based on the services they carry, checks their operating status, and sends alerts to clients in case of abnormal operating conditions.

[0136] The notification module is used to send notification messages to the client. Specifically, the notification module calls the interface of the SMS or email system to send notification messages to the client via SMS or email.

[0137] Optionally, taking the abnormality of the first attribute information of the first inbound device as an example, in the case of abnormality of the first attribute information of the first inbound device, the administrator identifier corresponding to the first inbound device, the identifier of the first inbound device, the first attribute information of the first inbound device, and the second attribute information of the first inbound device are determined. Then, based on the administrator identifier corresponding to the first inbound device, the identifier of the first inbound device, the first attribute information of the first inbound device, and the second attribute information of the first inbound device, email content is generated, and the email system interface is called to send the email.

[0138] Optionally, in the event of an anomaly in the first attribute of the first inbound device, the contact information of the manager corresponding to the first inbound device, the identifier of the first inbound device, the first attribute information of the first inbound device, and the second attribute information of the first inbound device are determined. Then, based on the contact information of the manager corresponding to the first inbound device, the identifier of the first inbound device, the first attribute information of the first inbound device, and the second attribute information of the first inbound device, SMS content is generated, and the SMS system interface is called to send the SMS.

[0139] In the equipment management system shown in Figure 5, since the first attribute information of the first inbound device is used to indicate the manufacturing and location information of the first inbound device, and the circulation information of the first inbound device is used to indicate the information of the first inbound device in procurement, operation and maintenance, etc., the equipment management method provided in this embodiment realizes unified management of information of the first inbound device at each stage. When the information verification module receives the identifier and first attribute information of the first inbound device, it verifies the accuracy of the first attribute information. If the first attribute information is confirmed to be accurate, the identifier, first attribute information, and circulation information of the first inbound device are hashed to obtain the hash value corresponding to the first inbound device. By verifying the accuracy of the first attribute information, the accuracy of the manufacturing and location information of the first inbound device is ensured. Then, the information verification module encrypts and transmits the hash value corresponding to the first inbound device to the storage module, ensuring the security of the hash value corresponding to the first inbound device during transmission.

[0140] Based on the above embodiments, this application embodiment further includes a first communication device and a second communication device, wherein the first communication device is used to manage at least one inbound device on the rack; and the second communication device is used to manage the identification and manufacturing information of the first inbound device. Specifically, with reference to Figure 6, the device management method provided by this application embodiment will be further described from three aspects: the first communication device, the second communication device, and the server.

[0141] Figure 6 is a schematic diagram of a device management method provided in an embodiment of this application. Referring to Figure 6, after the first device is stored in the warehouse, the scanning device obtains the identification and manufacturing information of the first device by scanning. Specifically, the first device includes an identification module and an attribute tag. The scanning device obtains the identification of the first device by scanning the identification module and obtains the manufacturing information of the first device by scanning the attribute tag. Then, the identification and manufacturing information of the first device are sent to the second communication device.

[0142] The second communication device receives the identifier of the first inbound device and the factory information of the first inbound device sent by the scanning device; sends the identifier of the first inbound device and the factory information of the first inbound device to the first communication device according to a preset time interval; the first communication device is used to manage at least one inbound device on the rack; the first inbound device is one of at least one inbound device.

[0143] It should be noted that the second communication device corresponds one-to-one with the first receiving device. The second communication device is used to manage the identification and manufacturing information of the first receiving device. After receiving the identification and manufacturing information of the first receiving device, the second communication device periodically sends the identification and manufacturing information of the first receiving device back to the first communication device.

[0144] The first communication device receives the identifier of the first inbound device and the factory information of the first inbound device sent by the second communication device; the first inbound device is one of at least one inbound device; the factory information of the first inbound device is obtained by scanning the attribute tags on the first inbound device.

[0145] It should be noted that communication can occur between the first communication device and the second communication device when the distance between them is less than or equal to a preset distance.

[0146] In some embodiments, the second communication device is used to manage the identification and manufacturing information of the first inbound device, and the second communication device is on the first inbound device, or attached to the first inbound device. Correspondingly, the first communication device is on a rack, or attached to a rack. Therefore, after the first inbound device is placed on the rack, the distance between the second communication device and the first communication device is less than or equal to a preset distance. At this time, the first communication device can receive the identification and manufacturing information of the first inbound device sent by the second communication device.

[0147] It should be noted that when the first inbound device is put into storage, the information receiving capability of the first communication device can be checked to confirm that the first communication device can communicate normally.

[0148] The rack containing the first inbound device is managed by the first communication device. In some embodiments, the first communication device includes multiple receiving modules, each located at the position where the first inbound device is placed on the rack. Therefore, after receiving the identifier and manufacturing information of the first inbound device sent by the second communication device, the first communication device can determine the position of the first inbound device on the rack based on the position of the receiving module.

[0149] In some embodiments, the second communication device generates first attribute information of the first inbound device based on the rack where the first inbound device is located, the position of the first inbound device on the rack, and the manufacturing information of the first inbound device. Then, the first attribute information and the identifier of the first inbound device are encrypted to obtain encrypted information; the encrypted information is then sent to the server.

[0150] In some embodiments, the location of the first receiving device may change. Specifically, the rack where the first receiving device is located may be changed, or the position of the first receiving device on the rack may be changed. Taking the rack location of the first receiving device as an example, the first communication device may not be able to receive the identification and manufacturing information of the first receiving device sent by the second communication device. In this case, the first communication device can send an indication message to the server, which indicates that the rack location of the first receiving device has changed. After receiving the indication message, the server determines whether the location change of the first receiving device is a normal change based on the indication message. If the location change of the first receiving device is an abnormal change, the server sends a location abnormality prompt message to the client through the prompt module, which indicates that the location of the first receiving device has changed abnormally.

[0151] After receiving the encrypted information, the server decrypts it to obtain the identifier and primary attribute information of the first inbound device. The information verification module in the device management system verifies the accuracy of the primary attribute information. If the primary attribute information is accurate, it generates a hash value corresponding to the first inbound device and stores this hash value in the blockchain via the blockchain storage module. The management module determines the association between the primary attribute information and flow information of multiple inbound devices and constructs a resource relationship network among them based on this relationship. This network is then displayed via the display module. Furthermore, the management module monitors the operating status of each inbound device and sends a notification to the client in case of abnormal operating status.

[0152] In the above embodiments, the first communication device is used to manage at least one storage device on the rack; the second communication device is used to manage the first storage device. In the process of managing multiple storage devices in the computer room, the first and second communication devices are used to realize the regional management and centralized control of multiple storage devices, thereby improving the management efficiency of the storage devices.

[0153] Figure 7 is a schematic diagram of a device management apparatus provided in an embodiment of this application. Referring to Figure 7, the device management apparatus 70 may include: a first receiving module 71, a determining module 72, a first processing module 73, and a storage module 74, wherein:

[0154] The first receiving model 71 is used to receive encrypted information sent by the first communication device; wherein, the encrypted information is obtained by encrypting the first attribute information and the identifier of the first storage device; the first communication device is used to manage at least one storage device on the rack; the first storage device is one of at least one storage device.

[0155] The determination module 72 is used to determine the second attribute information of the first inbound device and the circulation information of the first inbound device based on the identifier of the first inbound device, the mapping relationship between the device identifier and attribute information, and the mapping relationship between the device identifier and circulation information.

[0156] The first processing module 73 is used to perform hash processing on the identifier, first attribute information and circulation information of the first inbound device when the first attribute information and the second attribute information are the same, so as to obtain the hash value corresponding to the first inbound device.

[0157] Storage module 74 is used to store the hash value corresponding to the first inbound device in the blockchain.

[0158] In one possible implementation, the device management device 70 further includes a first update module, wherein the first update module is used for:

[0159] The system receives a first instruction message sent by the client, wherein the first inbound device includes at least one type of operation and maintenance management object, and the first instruction message is used to indicate that the operation and maintenance management object of the first inbound device has changed.

[0160] Based on the first instruction information, the circulation information of the first inbound device is updated to obtain the first circulation information;

[0161] The identifier, first attribute information, and first circulation information of the first inbound device are hashed to generate a first hash value;

[0162] Update the hash value corresponding to the first inbound device based on the first hash value.

[0163] In one possible implementation, the first indication information includes an identifier of the target type, an identifier of the first maintenance management object that has changed within the target type, and an identifier of the changed second maintenance management object; the flow information of the first inbound equipment is used to record the maintenance management object of the first inbound equipment and the flow process of the maintenance management object of the first inbound equipment; the first update module is specifically used for:

[0164] Based on the identifier of the target type, the identifier of the first maintenance management object, and the identifier of the second maintenance management object, update the maintenance management object of the first inbound device and the transfer process of the maintenance management object of the first inbound device to obtain the first transfer information;

[0165] The first transfer information is used to record the operation and maintenance management object of the first inbound equipment after the update, as well as the transfer process of the operation and maintenance management object of the first inbound equipment after the update.

[0166] In one possible implementation, the first attribute information is used to indicate the manufacturing information and location of the first inbound device, wherein the manufacturing information of the first inbound device is obtained by scanning the attribute tags on the first inbound device; the device management device 70 further includes a second update module, wherein the second update module is specifically used for:

[0167] The system receives a second instruction message sent by the client. The second instruction message is used to indicate that the current location of the first inbound device has changed. The current location of the first inbound device includes the rack where the first inbound device is located, and / or the position of the first inbound device on the rack.

[0168] Based on the second instruction information, the first attribute information and the circulation information of the first warehousing device are updated to obtain the third attribute information and the second circulation information;

[0169] The identifier, third attribute information, and second flow information of the first inbound device are hashed to generate a second hash value;

[0170] The second hash value is determined to be the hash value corresponding to the first data entry device.

[0171] In one possible implementation, the second indication information is used to indicate the current location and the changed location of the first inbound device; the flow information of the first inbound device is used to record the flow process of the location of the first inbound device; the second update module is specifically used for:

[0172] Based on the current and changed locations of the first inbound device, update the location of the first inbound device to obtain the third attribute information;

[0173] Based on the current location and the changed location of the first inbound device, update the flow process of the first inbound device's location to obtain the second flow information;

[0174] The third attribute information is used to indicate the updated location of the first inbound device; the second circulation information is used to record the circulation process of the first inbound device after its location is updated.

[0175] In one possible implementation, the device management device 70 further includes a prompting module, which is used for:

[0176] If the first attribute information and the second attribute information are different, a prompt message is sent to the client; the prompt message is used to indicate that the first attribute information is abnormal.

[0177] The device management device 70 provided in this application embodiment can execute the technical solution with the server as the execution subject in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0178] Figure 8 is a schematic diagram of another device management device provided in an embodiment of this application. As shown in Figure 8, the device management device 80 includes: a second receiving module 81, a generating module 82, a second processing module 83, and a first sending module 84, wherein:

[0179] The second receiving module 81 is used to receive the identifier of the first warehouse entry device and the factory information of the first warehouse entry device sent by the second communication device; the first warehouse entry device is one of at least one warehouse entry device; the factory information of the first warehouse entry device is obtained by scanning the attribute tags on the first warehouse entry device;

[0180] The generation module 82 is used to generate the first attribute information of the first inbound device based on the rack where the first inbound device is located, the position of the first inbound device on the rack, and the factory information of the first inbound device.

[0181] The second processing module 83 is used to encrypt the first attribute information and the identifier of the first inbound device to obtain encrypted information.

[0182] The first sending module 84 is used to send encrypted information to the server.

[0183] The device management device 80 provided in this application embodiment can execute the technical solution with the first communication device as the execution subject in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0184] Figure 9 is a schematic diagram of another device management device provided in an embodiment of this application. Referring to Figure 9, the device management device 90 may include: a third receiving module 91 and a second transmitting module 92, wherein:

[0185] The third receiving module 91 is used to receive the identifier of the first inbound device and the factory information of the first inbound device sent by the scanning device.

[0186] The second sending module 92 is used to send the identifier of the first warehouse entry device and the factory information of the first warehouse entry device to the first communication device according to a preset time interval; the first communication device is used to manage at least one warehouse entry device on the rack; the first warehouse entry device is one of at least one warehouse entry device.

[0187] The device management device 90 provided in this application embodiment can execute the technical solution with the second communication device as the execution subject in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0188] Figure 10 is a schematic diagram of the structure of a device management device provided in an embodiment of this application. As shown in Figure 10, the device management device 100 may include: a memory 101 and at least one processor 102. Exemplarily, the memory 101 and the at least one processor 102 are interconnected via a bus 103.

[0189] Memory 101 is used to store program instructions;

[0190] At least one processor 102 is used to execute program instructions stored in the memory, so that the device management device 100 performs the device management method with the server as the execution subject in the above method embodiment, or the device management method with the first communication device as the execution subject, or the device management method with the second communication device as the execution subject.

[0191] Optionally, the aforementioned processor can be a central processing unit (CPU), or it can be a GPU, other general-purpose processors, digital signal processors (DSPs), or application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0192] The device management device 100 provided in this application embodiment can execute the technical solutions in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0193] This application provides a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these instructions are used to implement a device management method with a server as the execution subject, as described in the above method embodiments, or a device management method with a first communication device as the execution subject, or a device management method with a second communication device as the execution subject.

[0194] This application provides a computer program product, including a computer program that, when executed by a processor, implements the device management method in the above-described method embodiments, which is executed by a server, a device management method executed by a first communication device, or a device management method executed by a second communication device.

[0195] This application provides a chip that stores a computer program. When the computer program is executed by the chip, it implements the device management method with a server as the execution subject in the above method embodiments, or the device management method with a first communication device as the execution subject, or the device management method with a second communication device as the execution subject.

[0196] This application provides a chip module with a computer program stored on it. When the computer program is executed by the chip module, it implements the device management method with a server as the execution subject in the above method embodiments, or the device management method with a first communication device as the execution subject, or the device management method with a second communication device as the execution subject.

[0197] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0198] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0199] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0200] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0201] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, Field Programmable Gate Array (FPGA), DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random-Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0202] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0203] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0204] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0205] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for managing equipment, characterized in that, Applied to a server, the method includes: receiving encrypted information sent by a first communication device; wherein the encrypted information is obtained by encrypting first attribute information and the identifier of a first inbound device; the first communication device is used to manage at least one inbound device on a rack; the first inbound device is one of the at least one inbound devices; determining second attribute information and flow information of the first inbound device based on the identifier of the first inbound device, the mapping relationship between the device identifier and attribute information, and the mapping relationship between the device identifier and flow information; when the first attribute information and the second attribute information are the same, performing hash processing on the identifier of the first inbound device, the first attribute information, and the flow information of the first inbound device to obtain a hash value corresponding to the first inbound device; and storing the hash value corresponding to the first inbound device in a blockchain.

2. The method according to claim 1, characterized in that, The method further includes: receiving first indication information sent by a client, wherein the first inbound device includes at least one type of operation and maintenance management object, and the first indication information is used to indicate that the operation and maintenance management object of the first inbound device has changed; updating the flow information of the first inbound device according to the first indication information to obtain first flow information; performing hash processing on the identifier of the first inbound device, the first attribute information and the first flow information to generate a first hash value; and updating the hash value corresponding to the first inbound device according to the first hash value.

3. The method according to claim 2, characterized in that, The first indication information includes the identifier of the target type, the identifier of the first operation and maintenance management object that has changed in the target type, and the identifier of the second operation and maintenance management object after the change; the circulation information of the first inbound equipment is used to record the operation and maintenance management object of the first inbound equipment and the circulation process of the operation and maintenance management object of the first inbound equipment. The step of updating the circulation information of the first inbound device according to the first instruction information to obtain the first circulation information includes: updating the operation and maintenance management object of the first inbound device and the circulation process of the operation and maintenance management object of the first inbound device according to the identifier of the target type, the identifier of the first operation and maintenance management object and the identifier of the second operation and maintenance management object to obtain the first circulation information; wherein, the first circulation information is used to record the updated operation and maintenance management object of the first inbound device and the updated circulation process of the operation and maintenance management object of the first inbound device.

4. The method according to any one of claims 1-3, characterized in that, The first attribute information is used to indicate the factory information and location of the first inbound device. The factory information of the first inbound device is obtained by scanning the attribute tags on the first inbound device. The method further includes: receiving second indication information sent by a client, the second indication information being used to indicate that the current location of the first inbound device has changed; the current location of the first inbound device includes the rack where the first inbound device is located, and / or, the position of the first inbound device on the rack; updating the first attribute information and the circulation information of the first inbound device according to the second indication information to obtain third attribute information and second circulation information; performing hash processing on the identifier of the first inbound device, the third attribute information, and the second circulation information to generate a second hash value; and determining the second hash value as the hash value corresponding to the first inbound device.

5. The method according to claim 4, characterized in that, The second indication information is used to indicate the current location and the changed location of the first inbound device; the flow information of the first inbound device is used to record the flow process of the location of the first inbound device. The step of updating the first attribute information and the flow information of the first inbound device according to the second indication information to obtain third attribute information and second flow information includes: updating the position of the first inbound device according to the current position and the changed position to obtain the third attribute information; updating the flow process of the position of the first inbound device according to the current position and the changed position to obtain the second flow information; wherein, the third attribute information is used to indicate the updated position of the first inbound device; the second flow information is used to record the flow process of the first inbound device after the position is updated.

6. The method according to any one of claims 1-3, characterized in that, The method further includes: sending a prompt message to the client when the first attribute information is different from the second attribute information; the prompt message is used to indicate that the first attribute information is abnormal.

7. A method for managing equipment, characterized in that, An application is made to a first communication device, which manages at least one inbound device on a rack. The method includes: receiving an identifier of a first inbound device and factory information of the first inbound device from a second communication device; the first inbound device is one of the at least one inbound devices; the factory information of the first inbound device is obtained by scanning attribute tags on the first inbound device; generating first attribute information of the first inbound device based on the rack where the first inbound device is located, the position of the first inbound device on the rack, and the factory information of the first inbound device; encrypting the first attribute information and the identifier of the first inbound device to obtain encrypted information; and sending the encrypted information to a server.

8. A method for managing equipment, characterized in that, The second communication device includes: receiving the identifier of a first inbound device and the factory information of the first inbound device sent by a scanning device; sending the identifier of the first inbound device and the factory information of the first inbound device to a first communication device according to a preset time interval; the first communication device is used to manage at least one inbound device on a rack; the first inbound device is one of the at least one inbound device.

9. An equipment management device, characterized in that, The device, applied to a server, includes: a first receiving model for receiving encrypted information sent by a first communication device; wherein the encrypted information is obtained by encrypting first attribute information and the identifier of a first inbound device; the first communication device is used to manage at least one inbound device on a rack; the first inbound device is one of the at least one inbound device; a determining module for determining second attribute information and flow information of the first inbound device based on the identifier of the first inbound device, the mapping relationship between the device identifier and attribute information, and the mapping relationship between the device identifier and flow information; a first processing module for performing hash processing on the identifier of the first inbound device, the first attribute information, and the flow information of the first inbound device when the first attribute information and the second attribute information are the same, to obtain a hash value corresponding to the first inbound device; and a storage module for storing the hash value corresponding to the first inbound device in a blockchain.

10. An equipment management device, characterized in that, An apparatus applied to a first communication device for managing at least one inbound device on a rack, the apparatus comprising: a second receiving module for receiving an identifier of a first inbound device and factory information of the first inbound device sent by the second communication device; the first inbound device being one of the at least one inbound devices; the factory information of the first inbound device being obtained by scanning attribute tags on the first inbound device; a generating module for generating first attribute information of the first inbound device based on the rack where the first inbound device is located, the position of the first inbound device on the rack, and the factory information of the first inbound device; a second processing module for encrypting the first attribute information and the identifier of the first inbound device to obtain encrypted information; and a first sending module for sending the encrypted information to a server.

11. An equipment management device, characterized in that, The device is applied to a second communication device and includes: a third receiving module for receiving the identifier of a first inbound device and the factory information of the first inbound device sent by a scanning device; a second sending module for sending the identifier of the first inbound device and the factory information of the first inbound device to the first communication device according to a preset time interval; the first communication device is used to manage at least one inbound device on a rack; the first inbound device is one of the at least one inbound device.

12. An equipment management device, characterized in that, include: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the device management method of any one of claims 1 to 6, or the device management method of claim 7, or the device management method of claim 8.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the device management method as described in any one of claims 1 to 6, or the device management method as described in claim 7, or the device management method as described in claim 8.

14. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the device management method according to any one of claims 1 to 6, or the device management method according to claim 7, or the device management method according to claim 8.

Images