Device information determination method and device, server and storage medium

Abstract

The invention discloses a device information determination method and device, a server and a storage medium. The method and device are applied to a first server. The first server is in communication connection with the second server; the method comprises the following steps: determining device associated information of the hardware equipment according to a technical architecture of each device in the hardware equipment, and determining a device mapping structure of the hardware equipment according to the device associated information; receiving a device mapping relation fed back by the second server according to the device mapping structure, wherein the device mapping relation comprises the device mapping structure and first device information corresponding to each device in the device mapping structure; acquiring second device information corresponding to each device in the hardware equipment management platform, and determining whether the second device information of each device is consistent with the first device information of each device; if not, sending a checking failure result to the second server, and returning to execute the step of receiving the device mapping relation fed back by the second server; if yes, compressing and splitting the device mapping relation to obtain fragmented files, and storing the fragmented files.

Description

Technical Field

[0001] This invention relates to the field of hardware design, and more particularly to a method, apparatus, server, and storage medium for determining device information. Background Technology

[0002] A switch is a type of network hardware used to connect devices within a local area network (LAN). Its main function is to enable efficient data forwarding between devices by analyzing the Media Access Control (MAC) address in data frames.

[0003] Currently, when a switch supplier delivers a pre-built switch to a user, they also provide the user with a component list. This list specifies the components used in the switch's construction, along with their elemental information. The user then checks the component list to verify that it matches the component information included in the switch itself.

[0004] However, because different manufacturers fill out the component list according to their own component information description system, when the user receives the component list of the switch, the user and the supplier may have different description methods or requirements for component information, which may lead to verification difficulties or verification errors. Summary of the Invention

[0005] This invention provides a method, apparatus, server, and storage medium for determining device information, which solves the problem of verification difficulties or errors caused by differences in the way users and providers describe devices or their device information requirements. It achieves a unified way of describing devices and clarifies the user's requirements for device information, thereby reducing the difficulties and errors in subsequent verification.

[0006] According to one aspect of the present invention, a method for determining device information is provided, applied to a first server; the first server is communicatively connected to a second server; the method includes:

[0007] Based on the technical architecture of each component in the hardware device, determine the component association information of the hardware device, and determine the component mapping structure of the hardware device based on the component association information.

[0008] The system receives the device mapping relationship fed back by the second server based on the device mapping structure. The device mapping relationship includes the device mapping structure and the first device information corresponding to each device in the device mapping structure.

[0009] Obtain the second device information corresponding to each device in the hardware device management platform, and determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device.

[0010] If there is a discrepancy, a verification failure result is sent to the second server, and the process returns to the step of receiving the device mapping relationship fed back by the second server based on the device mapping structure.

[0011] If they match, the device mapping relationship is compressed and split to obtain a fragment file, which is then stored.

[0012] The device information determination method provided in this invention determines device association information of the hardware device based on the technical architecture of each device in the hardware device, and determines the device mapping structure of the hardware device based on the device association information; receives the device mapping relationship fed back by the second server according to the device mapping structure; obtains the second device information corresponding to each device in the management platform of the hardware device, and determines whether the second device information corresponding to each device is consistent with the first device information corresponding to each device; if inconsistent, sends a verification failure result to the second server, and returns to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure; if consistent, compresses and splits the device mapping relationship to obtain fragmented files, and stores the fragmented files. The above technical solution, on the one hand, classifies devices based on the technical architecture of each device to obtain device association information, which can realize the standardization and modularization of devices in complex hardware devices according to structured thinking. Based on the device association information, a device mapping structure is obtained, which can obtain a standardized device mapping structure of the hardware device based on standardized and modular device association information, providing a standard for the provider to feed back a list based on the standardized device mapping structure. On the other hand, the device mapping structure is sent to the second server. The second server fills in the device information of each component of the hardware device according to the standardized device mapping structure. This ensures that the provider fills in the required device information according to the standardized structure given by the user, solving the problem of verification difficulties or errors caused by differences in device description methods or device information requirements between the user and the provider. It achieves a unified device description method, clarifies the user's device information requirements, and reduces the difficulty and errors during subsequent verification. Finally, the second device information is compared with the first device information to achieve a comparison and verification of the device information of each device based on the standardized device information obtained from the provider and the device information in the management platform. If the comparison result of any device is inconsistent, the result of the verification failure is notified to the second server, so that the second server can modify the first device information corresponding to the inconsistent device. This makes the verification process simple and fast, and reduces verification errors. Once the device mapping relationship is confirmed to be correct, it can be compressed and split. The different split files can be stored in different storage locations. This not only allows for the storage of the device mapping relationship but also ensures that the device mapping relationship will not be tampered with by storing the split files in different locations, thus guaranteeing the security of the device mapping relationship.

[0013] According to another aspect of the present invention, a device for determining device information is provided, applied to a first server; the first server is communicatively connected to a second server; the device includes:

[0014] The determination module is used to determine the device association information of the hardware device based on the technical architecture of each device in the hardware device, and to determine the device mapping structure of the hardware device based on the device association information.

[0015] The receiving module is used to receive the device mapping relationship fed back by the second server according to the device mapping structure, wherein the device mapping relationship includes the device mapping structure and the first device information corresponding to each device in the device mapping structure;

[0016] The judgment module is used to obtain the second device information corresponding to each device in the management platform of the hardware device, and determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device. If they are inconsistent, the module sends a verification failure result to the second server and returns to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure. If they are consistent, the module compresses and splits the device mapping relationship to obtain a fragment file and stores the fragment file.

[0017] According to another aspect of the present invention, a server is provided, the server comprising:

[0018] At least one processor; and

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

[0020] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to perform the method for determining device information according to any embodiment of the present invention.

[0021] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute a method for determining device information that implements any embodiment of the present invention.

[0022] According to another aspect of the present invention, a computer program product is provided, comprising a computer program that, when executed by a processor, implements a method for determining device information according to any embodiment of the present invention.

[0023] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 A flowchart illustrating a method for determining device information provided in an embodiment of the present invention;

[0026] Figure 2 Another flowchart illustrating the method for determining device information provided in an embodiment of the present invention;

[0027] Figure 3 A schematic diagram of the device for determining device information provided in an embodiment of the present invention;

[0028] Figure 4 This is a schematic diagram of the server structure provided in an embodiment of the present invention. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] Figure 1This is a flowchart illustrating a method for determining device information according to an embodiment of the present invention. This embodiment is applicable to situations where a switch provider provides a list of switches and their components to a user. The method can be executed by a device for determining device information, which can be implemented in hardware and / or software and can be configured in a server. In this embodiment, the device for determining device information can be configured in a first server, which is the server of the switch user, and a second server is the server of the switch provider. The server can be a computer or a terminal device. Figure 1 As shown, the method includes:

[0032] S101. Based on the technical architecture of each component in the hardware device, determine the component association information of the hardware device, and determine the component mapping structure of the hardware device based on the component association information.

[0033] In this context, hardware devices are visible and tangible physical components used to perform functions such as data input, processing, storage, output, and transmission. In this embodiment, hardware devices refer to switches, such as box switches, scalable switches, and stackable switches. The technical architecture of a device refers to the way devices are combined within the hardware device, their interconnections, and the technical rules and logical framework they follow when working together. Device association information indicates the relationships between devices within the hardware device and their corresponding technical architectures. The device mapping structure is the structure used to structure the device information within the hardware device.

[0034] Specifically, after the supplier delivers the hardware equipment to the user, the user needs to verify the hardware equipment against the component list provided by the supplier to ensure that the supplier has manufactured the hardware equipment according to their requirements (component types, brands, or other manufacturing specifications). Each component in the hardware equipment has its corresponding technical function, technical path, and technical positioning, i.e., technical architecture. Therefore, components can be categorized and summarized based on their technical architecture to obtain component association information. Furthermore, based on this component association information, the component mapping structure of the hardware equipment can be determined.

[0035] For example, based on the technical architecture of each device, the devices are classified, and the relationships between each device are determined to obtain device association information. Then, according to the classification of devices, the devices included in the classification, and the information of each device required by the user, a device mapping structure can be obtained.

[0036] In this embodiment, devices are classified based on their technical architecture to obtain device association information. This allows for the standardization and modularization of devices within complex hardware devices using a structured approach. Furthermore, based on the device association information, a device mapping structure is obtained. This standardized and modular device association information enables the creation of a standardized device mapping structure for hardware devices, providing a standard for providers to submit feedback lists based on the standardized device mapping structure.

[0037] S102. Receive the device mapping relationship fed back by the second server based on the device mapping structure.

[0038] The first server and the second server are connected in communication. The device mapping relationship includes the device mapping structure and the first device information corresponding to each device in the device mapping structure. In this embodiment, the first device information is the device information provided by the switch provider.

[0039] Specifically, after the first server determines the device mapping structure, it can send the device mapping structure to the second server. Upon receiving the device mapping structure, the second server's switch provider can manually fill in the first device information corresponding to each device in the device information field of the device mapping structure. Alternatively, the second server can automatically fill in the first device information in the device mapping structure based on the device information of each device in the hardware device pre-stored by the switch provider. After filling in the first device information in the device information field of each device in the device mapping structure, the device mapping relationship is obtained. At this point, the second server can send the device mapping relationship to the first server.

[0040] In this embodiment, the device mapping structure is sent to the second server. The second server fills in the device information of each device in the hardware device according to the standardized device mapping structure. This ensures that the provider fills in the required device information according to the standardized structure given by the user. This solves the problem of verification difficulties or errors caused by the different description methods or device information requirements of the user and the provider. It achieves the unification of the device description method and clarifies the user's requirements for device information, and reduces the difficulties and errors in subsequent verification.

[0041] S103. Obtain the second device information corresponding to each device in the management platform of the hardware device, and determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device.

[0042] The hardware management platform is a set of software systems or tools used to configure, monitor, maintain, and optimize hardware devices. The second component information is the component information determined by the user based on information from the management platform.

[0043] Specifically, hardware devices can connect to the first server via communication methods, wired connections, etc. The first server can then log into the hardware device's management platform and obtain the second device information corresponding to each device from the management platform. In one implementation, for each device, the first device information and the second device information corresponding to that device are compared to determine if they match. If any device's information does not match, step S104 is executed once. In another implementation, for all devices, the first device information and the second device information corresponding to each device are compared to determine consistency. After all devices have been compared, if any device's information does not match, step S104 is executed.

[0044] All of the above methods are based on the premise that if the first device information of any device is inconsistent with the second device information, then step S104 is executed, and if the first device information of all devices is consistent with the second device information, then step S105 is executed.

[0045] S104. If there is a discrepancy, send the verification failure result to the second server and return to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure.

[0046] Among them, the verification failure results include devices corresponding to two devices whose verification results are inconsistent.

[0047] Specifically, following the example above, one implementation involves sending the device and its corresponding first device information as a verification failure result to the second server for each device if the first device information and the second device information are inconsistent. This process is repeated for the next device until all devices have been verified. Another implementation involves comparing the two device information sets for each device. After the comparison is complete, the device with inconsistent information and its corresponding first device information are sent to the second server as a verification failure result.

[0048] The two implementation methods described above differ in their approaches. The first method compares each device individually, and if any discrepancy occurs, the result is sent to the second server, allowing the second server to promptly determine the verification result and re-determine the corresponding primary device information. The second method compares all devices and then sends all discrepancies to the second server, enabling the second server to promptly re-determine the primary device information for all problematic devices.

[0049] Specifically, after sending the verification failure result to the second server, the second server will, based on the device in the verification failure result, re-determine and modify the first device information of that device in the device mapping relationship. Then, it will send the modified device mapping relationship to the first server. The first server can then receive the device mapping relationship re-feedback from the second server.

[0050] In this embodiment, by utilizing the second device information corresponding to each device in the hardware device management platform and the first device information corresponding to each device in the device mapping relationship sent by the second server, the device information of each device is compared and verified based on the standardized device information obtained from the provider and the device information in the management platform. Furthermore, when the comparison result of any device is inconsistent, the verification failure result is notified to the second server, so that the second server can re-modify the first device information corresponding to the inconsistent device. This makes the verification process simple and fast, and reduces verification errors.

[0051] S105. If they match, compress and split the device mapping relationship to obtain a fragment file, and store the fragment file.

[0052] Specifically, if the first and second device information of all devices are consistent, it indicates that the device mapping relationship is correct. At this point, the device mapping relationship can be stored. Specifically, the device mapping relationship is stored as a file, compressed, and split. After splitting, at least two fragment files can be obtained, and these different fragment files can be stored in different storage locations.

[0053] In this embodiment, when the device mapping relationship is determined to be correct, the device mapping relationship can be compressed and split, and the different split files can be stored in different storage locations. This not only enables the storage of the device mapping relationship, but also ensures that the device mapping relationship will not be tampered with by storing it in different locations, thus ensuring the security of the device mapping relationship.

[0054] The device information determination method provided in this invention determines device association information of the hardware device based on the technical architecture of each device in the hardware device, and determines the device mapping structure of the hardware device based on the device association information; receives the device mapping relationship fed back by the second server according to the device mapping structure; obtains the second device information corresponding to each device in the management platform of the hardware device, and determines whether the second device information corresponding to each device is consistent with the first device information corresponding to each device; if inconsistent, sends a verification failure result to the second server, and returns to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure; if consistent, compresses and splits the device mapping relationship to obtain fragmented files, and stores the fragmented files. The above technical solution, on the one hand, classifies devices based on the technical architecture of each device to obtain device association information, which can realize the standardization and modularization of devices in complex hardware devices according to structured thinking. Based on the device association information, a device mapping structure is obtained, which can obtain a standardized device mapping structure of the hardware device based on standardized and modular device association information, providing a standard for the provider to feed back a list based on the standardized device mapping structure. On the other hand, the device mapping structure is sent to the second server. The second server fills in the device information of each component of the hardware device according to the standardized device mapping structure. This ensures that the provider fills in the required device information according to the standardized structure given by the user, solving the problem of verification difficulties or errors caused by differences in device description methods or device information requirements between the user and the provider. It achieves a unified device description method, clarifies the user's device information requirements, and reduces the difficulty and errors during subsequent verification. Finally, the second device information is compared with the first device information to achieve a comparison and verification of the device information of each device based on the standardized device information obtained from the provider and the device information in the management platform. If the comparison result of any device is inconsistent, the result of the verification failure is notified to the second server, so that the second server can modify the first device information corresponding to the inconsistent device. This makes the verification process simple and fast, and reduces verification errors. Once the device mapping relationship is confirmed to be correct, it can be compressed and split. The different split files can be stored in different storage locations. This not only allows for the storage of the device mapping relationship but also ensures that the device mapping relationship will not be tampered with by storing the split files in different locations, thus guaranteeing the security of the device mapping relationship.

[0055] Figure 2This is another flowchart illustrating the method for determining device information provided in this embodiment of the invention. Based on the above embodiments and other examples, this embodiment provides a detailed explanation of the steps of "determining device association information of the hardware device," "determining the device mapping structure of the hardware device based on the device association information," and "compressing and splitting the device mapping relationship to obtain fragmented files, and storing the fragmented files." Figure 2 As shown, the method includes:

[0056] S201. Determine the corresponding device category based on the technical positioning of the hardware device.

[0057] The technical architecture includes the technical path, technical function, and technical positioning. In this embodiment, the technical path refers to the specific technical route, principles, and methods adopted to realize the device's function. The technical function refers to the specific function and role the device plays in the hardware device and its contribution to the device's performance. Technical positioning is used to classify devices. One device category corresponds to one technical positioning.

[0058] Specifically, within a hardware device, multiple technological positioning points are determined based on its application scenario and technological system. These technological positioning points allow for the classification of the device. Therefore, each device category corresponds to a specific technological positioning point.

[0059] For example, in a hardware device, there are devices technically positioned for device configuration, protocol processing, and system management functions. These devices need to comply with network management and routing protocol standards. This technical positioning belongs to the control plane technology path; therefore, the device category can be a management control module integrated circuit. There are devices technically positioned for performing data frame / Internet Protocol packet forwarding, filtering, and hardware acceleration functions. These devices need to comply with data link layer standards and Internet Protocol routing and forwarding specifications. This technical positioning belongs to the data plane technology path; therefore, the device category can be a data plane module integrated circuit. There are devices technically positioned for implementing physical layer signal access, electrical signal processing, and power supply to terminal devices. These devices need to comply with physical layer standards and power supply specifications. This technical positioning belongs to the physical layer and interface technology path; therefore, the device category can be a service interface module integrated circuit. Furthermore, there are devices technically positioned for providing the energy, heat dissipation, and physical structural support required for device operation. These devices need to comply with hardware engineering specifications such as thermal design and power engineering. This technical positioning belongs to the physical support technology path; therefore, the device category can be a complete machine component.

[0060] In this embodiment, the device category corresponding to the hardware device is determined according to the different technical positioning of the hardware device, which can provide an accurate basis for the subsequent structural division of the device.

[0061] S202. Determine the device association information based on the device category, the technical path of each device, and the technical function of each device.

[0062] Specifically, each device has its own technical path and function. For example, a switch includes the following devices, along with their corresponding technical paths and functions:

[0063] (1) Central Processing Unit (CPU): The technical path is to run control plane software (such as routing protocol stack), then issue routing policies to the switching chip through the bus, and finally maintain control plane data structures such as routing table and address resolution protocol table; the technical role is to act as the core processor of the control plane, realize device logic decision-making and resource scheduling. (2) Dynamic Random Access Memory (DRAM): The technical path is to provide running memory for the CPU, then store routing protocol messages, real-time configuration data and statistical information, and finally support fast read and write to respond to the real-time needs of the control plane; the technical role is to act as a data cache carrier of the control plane, ensuring the efficiency of software operation. (3) Switching chip: The technical path is to receive frame data input from the physical layer chip, then parse the Media Access Control (MAC) address / Internet Protocol (IP) address, finally query the MAC address table / routing table, and forward to the target port; the technical role is to realize high-speed line-speed forwarding. Optionally, switching chips can be divided into application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and network processors (NPs) according to their functions and usage scenarios. Their functions differ depending on the type of switching chip. (4) Ternary Content Addressable Memory (TCAM): The technical path is to work with the switching chip to perform hardware-accelerated longest prefix matching of routing tables and access control list rule lookup, and then reduce the software microsecond-level query latency to the nanosecond level. The technical role is to serve as a performance optimization component for the data plane and solve the efficiency bottleneck of traditional memory table lookup. (5) Physical Layer Chip (PHY): The technical path is that the optical module outputs electrical signals, and the PHY chip performs encoding and clock recovery of 8-bit binary data into 10-bit symbols, and then converts them into frame data that conforms to the MAC layer specification and transmits them to the switching chip. The technical role is to serve as the interface hub between the physical layer and the data link layer, ensuring signal integrity and protocol compatibility. (6) Power over Ethernet (PoE) chip: The technical path is that the power module outputs DC voltage, and the PoE chip supplies power to the terminal device through the Ethernet cable, and performs power negotiation and overload protection; the technical function is to realize a composite interface technology solution for "data + power" co-line transmission.(7) Optical module: The technical path is to receive optical signals transmitted by optical fiber, convert the optical signals into electrical signals, and then connect them to the PHY chip through the interface; the technical function is to serve as a signal conversion component of the physical layer, supporting interface adaptation for different transmission media (optical fiber / copper cable). (8) Fan: The technical path is to use axial / centrifugal fans to force convection, remove the heat from heat-generating devices such as CPU and switching chips, and use heat sinks to achieve heat conduction, maintaining the internal temperature of the equipment within the technical specifications (e.g., 0℃~40℃); the technical function is to serve as an active heat dissipation component for thermal management, ensuring the long-term reliable operation of the device. (9) Power module (AC / DC power supply): The technical path is to use external input power (e.g., 220V AC), which is converted into the DC voltage required by the device (e.g., 12V / 5V) through PFC circuit and switching power supply module, and outputs a stable power supply through the filter circuit to power the entire device; the technical function is to serve as an energy supply component, ensuring the stability of the power supply and electromagnetic compatibility. (10) Flash memory (NOR Flash / NAND Flash): The technical path is to support data reading and storage after the CPU is powered on or communicates with the CPU through an interface; the technical function is to serve as a basic component of non-volatile storage, carrying the necessary data for the operation of device software. (11) Clock chip: The technical path is to generate a reference clock signal (such as a 25MHz reference clock) through a crystal oscillator, and provide a synchronous clock for PHY chip, switching chip, CPU, etc. through a frequency divider / multiplier circuit; the technical function is to serve as a reference source for system synchronization, avoiding data transmission errors caused by clock deviation (such as frame misalignment caused by clock drift). (12) Printed circuit board (PCB): The technical path is to use a multi-layer board design (such as a 12-layer board), power layer and ground layer isolation, signal layer characteristic impedance control (such as 50Ω impedance matching), realize the electrical connection of components through vias / traces, and mount surface mount technology (SMT) soldering devices; the technical function is to serve as the physical carrier of the hardware system, realizing the technical balance of signal integrity, power integrity and mechanical structure stability.

[0064] Specifically, after determining the technical path and function of each component in a hardware device according to the above example, the device category to which each component belongs can be determined by matching similar technical positions based on the technical path and function of each component.

[0065] For example, since the technical paths and functions of CPUs and DRAMs are biased towards the control plane, they can be classified as management and control module integrated circuits. Since the technical paths and functions of switching chips and TCAM chips are biased towards the data plane, they can be classified as data plane module integrated circuits. Since the technical paths and functions of PHY chips, PoE chips, and optical modules are all related to the physical layer and interface, they can be classified as service interface module integrated circuits. Since the technical paths and functions of fans and power modules are biased towards physical support, they can be classified as system components. Since the technical paths and functions of flash memory, clock chips, and PCBs are biased towards basic support, they can be classified as auxiliary components.

[0066] After classifying each device, the device association information can be determined according to the device classification and the technical architecture of each device.

[0067] For example, device association information can be as follows:

[0068]

[0069] Among them, core technology standards and protocols refer to the technical standards and protocols that the corresponding devices must comply with.

[0070] In this embodiment, based on the technical positioning of the hardware device, the corresponding component category is determined, thus clearly defining the functions of each component within the hardware device. This provides a foundation for standardized selection and supply chain management, and also enables the standardization and unification of component description methods. Furthermore, based on the component category and the technical path and function of each component, component association information can be determined, enabling component classification. Based on the standard protocols and technical functions that each category of components must meet, the importance of each component within the hardware device is clarified, providing a basis for subsequently determining the component mapping structure.

[0071] S203. Determine the information to be determined for each device, and determine the device mapping structure based on the device association information and the information to be determined.

[0072] The information to be determined for each device is the list of device information that the user needs from the provider for each device.

[0073] Specifically, the first server can use the device information required by the supplier for each device in this transaction as the information to be determined. For example, the user needs the supplier to provide information such as the supplier, model, quantity required, and supplier country for each device in the switch. The first server then obtains the information to be determined as: the supplier, model, quantity required, and supplier country for each device. At this point, the first server can determine the device mapping structure based on the device association information and the information to be determined.

[0074] For example, the device mapping structure is as follows:

[0075]

[0076] The table headers for "Component Category," "Component Name," and "Component Information" are the component mapping structure. The five component categories under "Component Category" and the corresponding components under "Component Name" are determined based on component association information. The "Supplier," "Model," "Required Quantity," and "Supplier Country" under "Component Information" represent the component information that the user needs from the supplier for each component—in other words, the information to be determined for each component. Blank areas in the table represent content to be filled in.

[0077] In this embodiment, based on device association information and the information to be determined for each device, a device mapping structure containing a standardized device description and the device information required by the user can be obtained. This provides a basis for the provider to provide a device information list to the user according to the user's requirements.

[0078] S204. Send the device mapping structure and the information to be determined for each device to the second server, so that the second server can determine the device mapping relationship based on the device mapping structure and the information to be determined.

[0079] Specifically, the device mapping structure as shown in Table 2 above can be sent to the second server. Alternatively, the information to be determined for each device can be sent to the second server in particular, so that the second server can fill in the corresponding device information for each device in the "Device Information" section of Table 2 according to the device mapping structure and the information to be determined.

[0080] For example, in one implementation, the second server displays a device mapping structure and information to be determined to the provider. Then, the second server directly receives the information to be determined provided by the provider, i.e., the first device information, and obtains a device mapping structure filled with the device information, which serves as the device mapping relationship. In another implementation, the provider pre-stores device information corresponding to each hardware device. When the second server receives the device mapping structure, it either matches the corresponding hardware device according to the device mapping structure or determines the target hardware device based on the information to be determined for each device. After determining the target hardware device, it retrieves the device information corresponding to the target hardware device from the storage and uses it as the first device information, filling it into the corresponding position of the device information in the device mapping structure to obtain the device mapping relationship.

[0081] S205, Receive the device mapping relationship sent by the second server.

[0082] Specifically, after the second server obtains the device mapping relationship, the second server sends the device mapping relationship to the first server, and the first server can then receive the device mapping relationship.

[0083] S206. Accept the connection request from the hardware device and log in to the management platform after the hardware device is successfully connected.

[0084] Specifically, the hardware device can connect to the first server via a wired connection or a communication connection. Initially, the first server receives and approves the connection request from the hardware device. At this point, the hardware device successfully connects to the first server. Afterward, the first server can receive instructions from the user and log into the hardware device's management platform.

[0085] S207. Obtain the second device information corresponding to each device that matches the command line query command from the management platform.

[0086] Specifically, the first server can obtain secondary device information for each component in the hardware device based on command-line query instructions. For example, by querying the hardware device's registers and sensors, such as the built-in registers of the CPU and switching chips, the server can determine the device's manufacturer identification, model, and firmware version. Furthermore, during hardware device startup, the Basic Input / Output System / Unified Extensible Firmware Interface or bootloader scans the hardware device and stores the information in memory. At this point, the device information within the hardware device system can be accessed.

[0087] Optionally, for each component's supplier country, the first server will, based on the user's instructions and the component's supplier information, browse the product documentation on the supplier's official website to determine the corresponding supplier country for that component. Alternatively, blockchain technology can be used to determine the supplier country for that component.

[0088] After determining the second device information, the second device information can be filled into the blank positions in Table 2 above, and the user's "device mapping relationship" can be obtained.

[0089] In this embodiment, the first server can directly determine all the second device information based on the device information of each device stored in the hardware device and the supplier of each device, thus realizing the accurate device information of each device contained in the hardware device directly based on the hardware device itself.

[0090] S208. Determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device; if they are inconsistent, proceed to S209; if they are consistent, proceed to S210.

[0091] Specifically, one implementation involves scanning the "device mapping relationship" sent by the second server, which includes information about the second device, and scanning the "device mapping relationship" determined by the hardware device management platform, which includes information about the first device, resulting in two editable text files. These editable text files are then processed, such as by unifying structure and handling special characters. The two tables in the two text files are then linked according to common fields to form a new table containing all information from both tables. Information in the same field within the table is then aligned. Finally, based on Boolean conditions, the differences between missing information and field values ​​are determined, thus identifying whether the second device information corresponding to each device is consistent with the first device information corresponding to each device, and, if inconsistent, identifying the inconsistent content. Another implementation involves treating each row in both the "device mapping relationship" sent by the second server (including information about the second device) and the "device mapping relationship" determined by the hardware device management platform (including information about the first device) as a record, and each column as a field. A difference operation is performed on the two mapping relationships to quickly locate and determine the similarities and differences between them, thereby determining whether the second device information corresponding to each device is consistent with the first device information corresponding to each device, and, if inconsistent, identifying the inconsistent content.

[0092] S209. Send the verification failure result to the second server.

[0093] Specifically, if it is determined that the second device information corresponding to each device is inconsistent with the first device information corresponding to each device, that is, if the second device information of any device is inconsistent with the first device information, a verification failure result is sent to the second server. The verification failure result includes the device corresponding to the inconsistent device information, the incorrect first device information, and a modification instruction. After receiving the verification failure result, the first server can execute step S205. That is, the second server modifies the first device information according to the modification instruction. The modification method can be receiving modification information from the provider, or re-determining the first device information of the device from the storage area. Furthermore, after the second server completes the modification, the first server can receive the modified device mapping relationship from the second server.

[0094] S210. Determine the device information file based on the hardware device identification information and device mapping relationship.

[0095] Specifically, once it is determined that the second device information corresponding to each device is consistent with the first device information corresponding to each device, the step of storing the device mapping relationship can be performed. At this time, the device mapping relationship can be named according to the identification information of the hardware device and stored as a file for subsequent storage, i.e., the device information file is determined.

[0096] For example, the device mapping relationship is stored as a document file, ending with the corresponding file extension. This document file is then named according to the hardware device's identification information. For instance, the naming convention could be: "Switch Manufacturer Name_Product Model_Standardized Date Format_Serial Number.Document File Extension". This allows the identification of the device information file. The serial number serves as a unique identifier for files from the same manufacturer / model / date.

[0097] In this embodiment, the device information document containing the device is named using the identification information of the hardware device, which provides a basis for retrieving the device information of the corresponding hardware device from the storage space later.

[0098] S211. Determine the encryption key based on the device information file, and use the encryption key to compress the device information file to obtain a compressed file.

[0099] Specifically, one implementation involves determining the encryption key based on the serial number and product model in the device information file. For example, the product model and serial number can be directly combined as the alphanumeric encryption key. Another implementation involves calculating the data digest value of the device information file and using that data digest value as the encryption key. For example, the device information file can be processed using an encryption hash function that converts input data of arbitrary length into a fixed-length 256-bit binary hash value to obtain the encryption key.

[0100] Additionally, the device information file is compressed using an encryption key to obtain a compressed file.

[0101] In this embodiment, since the device information file is determined by the different device information of different devices in each hardware device, the data digest value of the device information file can be directly calculated and used as an encryption key to encrypt and compress the device information file, thus ensuring the uniqueness, accuracy and security of the device information file.

[0102] Optionally, after determining the encryption key based on the device information file, the method further includes:

[0103] Associate the filename of the device information file with the encryption key to obtain the device key information, and store the device key information in a local text file.

[0104] In other words, to ensure the subsequent retrieval of stored device information files, it is necessary to store the encryption key for the encrypted device information files. To facilitate identification of which encryption key belongs to the target device information file, the filename of the device information file can be associated with the encryption key when storing the encryption key, and the device key information can then be stored in a local text file. This allows for the storage of encryption keys for each device information file, and also provides a foundation for quickly finding the corresponding encryption key for a device information file later; that is, the corresponding encryption key can be found simply by using the hardware device identification information in the filename of the device information file.

[0105] S212. Split the compressed file to obtain at least two split files, and store the at least two split files in different storage locations.

[0106] Specifically, to ensure the encrypted compressed file cannot be tampered with, it can be split into at least two fragments, each stored in a different location. For example, it can be split into two fragments, one stored in the cloud and the other on local storage. Furthermore, to facilitate retrieval of all fragments from different storage locations, a naming convention can be set for the fragments. For instance, it could be formatted as "Switch Manufacturer Name_Product Model_Standardized Date Format Timestamp (accurate to the minute)_Fragment Number_Preset Number of Encryption Key.Compressed File Extension.Compressed Fragment File Extension Number". This way, retrieving all fragments from different storage locations can be done directly based on the "Manufacturer Name, Product Model, and Preset Number of Encryption Key" in the naming. For example, if the preset number is 8, then the "Preset Number of Encryption Key" in the naming is the first 8 digits of the encryption key.

[0107] In this embodiment, the compressed file is split into fragments, and different fragments are stored in different storage locations, which can improve data reliability and disaster recovery capabilities, and improve data transmission and storage efficiency.

[0108] Alternatively, if it is necessary to obtain the device information file of the target hardware device later, the following operations can be performed:

[0109] (i) Based on the identification information of the hardware device to be queried, determine the storage location of the fragment file corresponding to the device information file to be queried of the hardware device to be queried.

[0110] The target hardware device mentioned above is the hardware device to be queried.

[0111] Specifically, based on the identification information of the hardware device to be queried, such as the manufacturer's name, product model, and standardized date format, the fragment files in each storage location that match the above identification information can be matched to locate the fragment storage path and obtain the storage location corresponding to the fragment file.

[0112] (ii) Obtain the fragment file corresponding to the device information file to be queried from the storage location of the fragment file corresponding to the device information file to be queried.

[0113] Specifically, after determining the storage location of the fragmented file, the fragmented file corresponding to the device information file to be queried can be directly obtained from these storage locations.

[0114] (iii) Determine the encryption key of the device information file to be queried from a local text file based on the filename of the device information file to be queried.

[0115] Specifically, one implementation involves directly inputting keywords from the filename of the device information file to be queried, such as "manufacturer name, product model, and standardized date format," and determining the encryption key for the device information file from a local text file. Another implementation involves associating the encryption key with the filename of the device information file when storing it; therefore, the encryption key can be directly determined from the text file based on the filename of the device information file.

[0116] (iv) Using the encryption key of the device information file to be queried and the corresponding fragment file of the device information file to be queried, the device information file to be queried is obtained.

[0117] Specifically, the acquired fragment files are downloaded to the same temporary folder, and the fragment files are automatically merged and decrypted using an encryption key. After decryption, the device information file to be queried can be obtained.

[0118] Optionally, after obtaining the device information file to be queried, the table can be parsed and visualized. For example, a webpage can be used to display the device information file as structured data. Alternatively, a data analysis library can be used to process the device information file and render it onto the display interface.

[0119] Optionally, in the above steps, the file decrypted for the first time, i.e., the file in the temporary folder, can be cached locally for 24 hours. Subsequent similar queries can then prioritize retrieving the cached file for faster results. Furthermore, before merging fragments, the "first preset digits of the encryption key" in each fragment's filename can be compared to ensure consistency, preventing mismatches. Also, if fragments in some storage locations are lost, the device information file can be regenerated using the fragments from the remaining storage locations and the encryption key, and then re-encrypted, compressed, and fragmented.

[0120] Optionally, the aforementioned check of archived data is applied to verify the manufacturer and other component information involved in the hardware devices at preset intervals. This ensures that if the manufacturer of an individual component is acquired or changes, the content of the stored component information file needs to be updated accordingly in a timely manner. The main change may be a change in the supplier's country of origin. This ensures that the archived data remains real-time as the supply chain dynamically changes, avoiding the risk of information lag caused by manufacturer mergers and acquisitions or business changes.

[0121] Figure 3 This is a schematic diagram of the device for determining device information provided in an embodiment of the present invention. Figure 3 As shown, it is applied to a first server; the first server is communicatively connected to a second server; the device includes:

[0122] The determination module 301 is used to determine the device association information of the hardware device based on the technical architecture of each device in the hardware device, and to determine the device mapping structure of the hardware device based on the device association information.

[0123] The receiving module 302 is used to receive the device mapping relationship fed back by the second server according to the device mapping structure, wherein the device mapping relationship includes the device mapping structure and the first device information corresponding to each device in the device mapping structure;

[0124] The judgment module 303 is used to obtain the second device information corresponding to each device in the management platform of the hardware device, and determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device. If they are inconsistent, the module sends a verification failure result to the second server and returns to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure. If they are consistent, the module compresses and splits the device mapping relationship to obtain a fragment file and stores the fragment file.

[0125] Optionally, the technical architecture includes the technical path, technical function, and technical positioning; based on the technical architecture of each component in the hardware device, the component association information of the hardware device is determined, and the specific use of module 301 is determined:

[0126] Based on the technical positioning of the hardware equipment, determine the corresponding device category; based on the device category, the technical path and technical function of each device, determine the device association information.

[0127] Optionally, the device mapping structure of the hardware device is determined based on the device association information, and module 301 is specifically used for:

[0128] Determine the information to be determined for each device, and determine the device mapping structure based on the device association information and the information to be determined;

[0129] The receiving module 302 receives the device mapping relationship fed back by the second server based on the device mapping structure. Specifically, it is used for:

[0130] Send the device mapping structure and the information to be determined for each device to the second server, so that the second server can determine the device mapping relationship based on the device mapping structure and the information to be determined; receive the device mapping relationship sent by the second server.

[0131] Optionally, the second device information corresponding to each device in the hardware device management platform is obtained, and the judgment module 303 is specifically used for:

[0132] Accept connection requests from hardware devices and log in to the management platform after the hardware devices are successfully connected; retrieve the second device information corresponding to each device that matches the command-line query command from the management platform.

[0133] Optionally, the device mapping relationship is compressed and split to obtain fragmented files, and the fragmented files are stored. The judgment module 303 is specifically used for:

[0134] The device information file is determined based on the identification information of the hardware device and the device mapping relationship; the encryption key is determined based on the device information file, and the device information file is compressed using the encryption key to obtain a compressed file; the compressed file is split to obtain at least two fragment files, and the at least two fragment files are stored in different storage locations.

[0135] Optionally, the encryption key is determined based on the device information file, and the judgment module 303 is specifically used for:

[0136] Calculate the data digest value of the device information file and determine the data digest value as the encryption key;

[0137] After determining the encryption key based on the device information file, the judgment module 303 is also used for:

[0138] Associate the filename of the device information file with the encryption key to obtain the device key information, and store the device key information in a local text file.

[0139] Optionally, the device further includes a query module, which is specifically used for:

[0140] Based on the identification information of the hardware device to be queried, determine the storage location of the fragment file corresponding to the device information file to be queried; retrieve the fragment file corresponding to the device information file to be queried from the storage location of the fragment file corresponding to the device information file to be queried; determine the encryption key of the device information file to be queried from a local text file based on the filename of the device information file to be queried; and obtain the device information file to be queried using the encryption key of the device information file to be queried and the fragment file corresponding to the device information file to be queried.

[0141] The device information determination apparatus provided in the embodiments of the present invention can execute the device information determination method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0142] Figure 4 This is a schematic diagram of a server provided for an embodiment of the present invention. The server is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The server can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0143] like Figure 4 As shown, server 10 includes at least one processor 11 and memory, such as read-only memory (ROM) 12 and random access memory (RAM) 13, communicatively connected to at least one processor 11. The memory stores computer programs executable by at least one processor. Processor 11 can perform various appropriate actions and processes based on the computer program stored in ROM 12 or loaded from storage unit 18 into RAM 13. RAM 13 may also store various programs and data required for the operation of server 10. Processor 11, ROM 12, and RAM 13 are interconnected via bus 14. Input / output (I / O) interface 15 is also connected to bus 14.

[0144] Multiple components in server 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of monitors, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows server 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0145] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as methods for determining device information.

[0146] In some embodiments, the method for determining device information may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on server 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the method for determining device information described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the method for determining device information by any other suitable means (e.g., by means of firmware).

[0147] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0148] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0149] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0150] To provide interaction with the user, the systems and techniques described herein can be implemented on a server having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the server. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including voice input, speech input, or tactile input).

[0151] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0152] A computing system can include clients and servers. Clients and servers are generally geographically separated and typically interact via communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0153] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the method for determining device information as provided in any embodiment of this invention.

[0154] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0155] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0156] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for determining device information, characterized in that, Applied to the first server; The first server communicates with the second server; the method includes: Based on the technical architecture of each component in the hardware device, determine the component association information of the hardware device, and determine the component mapping structure of the hardware device based on the component association information; The system receives a device mapping relationship from the second server based on the device mapping structure, wherein the device mapping relationship includes the device mapping structure and first device information corresponding to each device in the device mapping structure. Obtain the second device information corresponding to each device in the management platform of the hardware device, and determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device; If there is a discrepancy, a verification failure result is sent to the second server, and the process returns to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure. If they match, the device mapping relationship is compressed and split to obtain a fragment file, and the fragment file is stored.

2. The method for determining device information according to claim 1, characterized in that, The technical architecture includes technical paths, technical functions, and technical positioning; determining the device association information of the hardware device based on the technical architecture of each component includes: Based on the technical positioning of the hardware device, determine the corresponding device category; The device association information is determined based on the device category, the technical path of each device, and the technical function of each device.

3. The method for determining device information according to claim 1, characterized in that, Determining the device mapping structure of the hardware device based on the device association information includes: The information to be determined for each device is determined, and the device mapping structure is determined based on the device association information and the information to be determined. Receiving the device mapping relationship fed back by the second server according to the device mapping structure includes: The device mapping structure and the information to be determined for each device are sent to the second server so that the second server can determine the device mapping relationship based on the device mapping structure and the information to be determined. Receive the device mapping relationship sent by the second server.

4. The method for determining device information according to claim 1, characterized in that, The step of obtaining the second device information corresponding to each device in the management platform of the hardware device includes: Accept the connection request from the hardware device, and log in to the management platform after the hardware device is successfully connected; Obtain the second device information corresponding to each device that matches the command line query command from the management platform.

5. The method for determining device information according to claim 1, characterized in that, The step of compressing and splitting the device mapping relationship to obtain fragmented files, and storing the fragmented files, includes: The device information file is determined based on the identification information of the hardware device and the device mapping relationship; The encryption key is determined based on the device information file, and the device information file is compressed using the encryption key to obtain a compressed file; The compressed file is split into at least two fragment files, and the at least two fragment files are stored in different storage locations.

6. The method for determining device information according to claim 5, characterized in that, The step of determining the encryption key based on the device information file includes: Calculate the data digest value of the device information file, and determine the data digest value as the encryption key; After determining the encryption key based on the device information file, the process also includes: The filename of the device information file is associated with the encryption key to obtain device key information, and the device key information is stored in a local text file.

7. The method for determining device information according to claim 6, characterized in that, The method also includes: Based on the identification information of the hardware device to be queried, determine the storage location of the fragment file corresponding to the device information file of the hardware device to be queried; Obtain the fragment file corresponding to the device information file to be queried from the storage location of the fragment file corresponding to the device information file to be queried; Based on the filename of the device information file to be queried, determine the encryption key of the device information file to be queried from a local text file; The device information file to be queried is obtained using the encryption key of the device information file to be queried and the corresponding fragment file.

8. A device for determining device information, characterized in that, Applied to the first server; The first server is communicatively connected to the second server; the device includes: The determination module is used to determine the device association information of the hardware device based on the technical architecture of each device in the hardware device, and to determine the device mapping structure of the hardware device based on the device association information; The receiving module is configured to receive the device mapping relationship fed back by the second server according to the device mapping structure, wherein the device mapping relationship includes the device mapping structure and the first device information corresponding to each device in the device mapping structure; The judgment module is used to obtain the second device information corresponding to each device in the management platform of the hardware device, and determine whether the second device information corresponding to each device is consistent with the first device information corresponding to each device; if they are inconsistent, the module sends a verification failure result to the second server and returns to the step of receiving the device mapping relationship fed back by the second server according to the device mapping structure; if they are consistent, the module compresses and splits the device mapping relationship to obtain a fragment file and stores the fragment file.

9. A server, characterized in that, include: One or more processors; Memory, used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method for determining device information as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method for determining device information as described in any one of claims 1 to 7.

Images