Method and apparatus for constructing component database of server, storage medium

Abstract

The application discloses a kind of server component database construction method and device, storage medium, the server component database construction method includes: obtaining the compatible relationship of each server in server database on component type;Find the corresponding component specification set of each server in compatible server group on target component type from server database, obtain multiple component specification sets;Create the component type information corresponding to target component type in component database for compatible server group;Establish the association between component type information and multiple component specification sets in server database in component database, using the above technical solution, solve the problem that the association degree of server component database and server database is lower in related art, and then the technical effect of improving the association degree of server component database and server database is achieved.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a method and apparatus for constructing a component database for a server, and a storage medium. Background Technology

[0002] A Bill of Material (BOM) is a list of all the sub-materials that make up a product. The current component-based BOM is built on a per-component basis. It is recorded and managed by assigning a BOM code to each component product. Users can place an order by entering the corresponding component product's BOM code.

[0003] However, in existing component-based BOMs, BOM codes are established for individual component products. This can result in an extremely large number of BOM codes in the component database. On the one hand, this is not conducive to management and application. On the other hand, the component-based BOM is not related to the server product BOM and is independent of each other. This makes it difficult to find the BOM code of the compatible component product from the massive number of component product BOM codes when expanding the component products for the server product. Often, the component product with the selected BOM code is incompatible with the server product, resulting in a poor user experience.

[0004] There is still no effective solution to the problem of low correlation between the component database and the server database in related technologies. Summary of the Invention

[0005] This application provides a method, apparatus, and storage medium for constructing a server component database, in order to at least solve the problem in related technologies where the correlation between the server component database and the server database is low.

[0006] According to one embodiment of this application, a method for constructing a component database of a server is provided, comprising:

[0007] Obtain the compatibility relationship of each server in the server database in terms of component type, wherein the compatibility relationship is used to indicate that multiple servers as a compatible server group allow the use of server components that belong to the target component type;

[0008] The server database is searched for the component specification set corresponding to the target component type for each server in the compatible server group, resulting in multiple component specification sets. Each component specification set records the component specifications that the corresponding server is allowed to use.

[0009] In the component database, component type information corresponding to the target component type is created for the compatible server group, wherein the component type information is used to identify server components of the target component type applicable to servers in the compatible server group;

[0010] An association is established between the component type information in the component database and the multiple component specification sets in the server database, wherein the association is used to find server components that are allowed to be used by the servers included in the compatible server group.

[0011] Optionally, the step of searching the server database for the component specification set corresponding to each server in the compatible server group for the target component type yields multiple component specification sets, including:

[0012] Send a first read instruction to the server database, wherein the first read instruction is used to read the component specification set identifier of the component specification set corresponding to the target component type for each server from the server database;

[0013] Receive the set of multiple component specification identifiers returned by the server database in response to the first read command.

[0014] Optionally, establishing the association between the component type information in the component database and the multiple component specification sets in the server database includes:

[0015] Allocate first storage space for the component type information in the bill of materials in the component database;

[0016] The first storage space stores the component type information and the identifiers of the multiple component specification sets that have an association relationship, wherein the identifiers of the multiple component specification sets are used to indicate that the corresponding component specification set is found in the server database.

[0017] Optionally, the step of searching the server database for the component specification set corresponding to each server in the compatible server group for the target component type yields multiple component specification sets, including:

[0018] Send a second read instruction to the server database, wherein the second read instruction is used to read from the server database the set of component specifications corresponding to each server for the target component type;

[0019] The server database receives the set of multiple component specifications returned by the second read instruction.

[0020] Optionally, establishing the association between the component type information in the component database and the multiple component specification sets in the server database includes:

[0021] Request a second storage space for the component type information in the bill of materials in the component database;

[0022] The second storage space stores the associated component type information and target component specification set, wherein the target component specification set is the union of the multiple component specification sets, and the target component specification set is used to find server components belonging to the target component type that are allowed to be used by the servers included in the compatible server group.

[0023] Optionally, establishing the association between the component type information in the component database and the multiple component specification sets in the server database includes:

[0024] Extract the first information field from the component type information that indicates the target component type;

[0025] The auxiliary component specification set corresponding to the first information field is searched from the auxiliary component library stored in the component database, and the installation manual specification set corresponding to the first information field is searched from the installation manual specification library stored in the component database, wherein the component specification set records the main component specifications belonging to the target component type.

[0026] Extract the second information field from the component type information, which indicates the component size of the main material component belonging to the target component type;

[0027] Search the packaging specification set corresponding to the second information field from the component packaging specification library stored in the component database;

[0028] In the component database, auxiliary component information is created for the auxiliary component specification set, installation manual information is created for the installation manual specification set, and packaging information is created for the packaging specification set. The auxiliary component information is used to identify the auxiliary component specification set, the installation manual information is used to identify the installation manual specification set, and the packaging information is used to identify the packaging specification set.

[0029] Establish the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database.

[0030] Optionally, after establishing the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database, the method further includes:

[0031] Receive server orders from the target server;

[0032] Detect whether the target server belongs to the compatible server group;

[0033] If the target server is detected to belong to the compatible server group, it is detected whether the server order indicates that the target server has an expansion requirement;

[0034] If the server order indicates that the target server has an expansion requirement, the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information is extracted from the component database.

[0035] Based on the correlation between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information, a component expansion order is generated for the target server.

[0036] According to another embodiment of the present application, an apparatus for constructing a component database of a server is also provided, comprising:

[0037] The acquisition module is used to acquire the compatibility relationship of each server in the server database in terms of component type, wherein the compatibility relationship is used to indicate that multiple servers as a compatible server group allow the use of server components that belong to the target component type.

[0038] The lookup module is used to look up the set of component specifications corresponding to each server in the compatible server group for the target component type from the server database, and obtain multiple sets of component specifications, wherein each set of component specifications records the component specifications that the corresponding server is allowed to use;

[0039] A creation module is used to create component type information corresponding to the target component type for the compatible server group in the component database, wherein the component type information is used to identify server components of the target component type applicable to servers in the compatible server group;

[0040] A module is established to create an association between the component type information in the component database and the multiple component specification sets in the server database, wherein the association is used to find server components that are allowed to be used by the servers included in the compatible server group.

[0041] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0042] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0043] In this embodiment, the compatibility relationships of each server in the server database on component types are obtained. These compatibility relationships indicate that multiple servers, as a compatible server group, allow the use of server components of the target component type. The component specification set corresponding to the target component type for each server in the compatible server group is searched from the server database, resulting in multiple component specification sets. Each component specification set records the component specifications allowed for use by the corresponding server. Component type information corresponding to the target component type is created in the component database for the compatible server group. This component type information identifies server components of the target component type applicable to servers in the compatible server group. An association relationship is established between the component type information in the component database and the multiple component specification sets in the server database. This association relationship is used to find server components allowed for use by servers included in the compatible server group, i.e., the association between the component database and the server database in related technologies. To address the current low compatibility between server component databases and server databases, this application proposes a method for constructing a server component database. First, the compatibility relationships between servers in the server database are obtained. A compatibility relationship indicates that multiple servers forming a compatible server group are allowed to use server components belonging to the target component type. Then, the component specification set corresponding to the target component type for each server in the compatible server group is searched from the server database, resulting in multiple component specification sets. To establish the association between the server component database and the server database, component type information corresponding to the target component type is created in the component database for the compatible server group. This component type information identifies server components of the target component type applicable to servers in the compatible server group. Finally, an association is established between the component type information in the component database and the multiple component specification sets in the server database. This association can be used to find server components that are allowed to be used by servers included in the compatible server group. This technical solution solves the problem of low compatibility between the server component database and the server database in related technologies, achieving the technical effect of improving the compatibility between the server component database and the server database. Attached Figure Description

[0044] Figure 1 This is a hardware structure block diagram of a computer device for a method of constructing a component database of a server according to an embodiment of this application.

[0045] Figure 2 This is a flowchart of a method for constructing a component database of a server according to an embodiment of this application;

[0046] Figure 3 This is a schematic diagram illustrating the updating of a target component specification set according to an embodiment of this application;

[0047] Figure 4 This is a schematic diagram of an installation manual specification library according to an embodiment of this application;

[0048] Figure 5 This is a schematic diagram of a component packaging specification library according to an embodiment of this application;

[0049] Figure 6 This is a schematic diagram illustrating how to search for an installation manual specification set and a packaging specification set based on component type information, according to an embodiment of this application.

[0050] Figure 7 This is a schematic diagram illustrating the process of constructing and using a server component database according to an embodiment of this application;

[0051] Figure 8 This is a structural block diagram of a component database construction apparatus for a server according to an embodiment of this application. Detailed Implementation

[0052] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0053] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0054] The methods and embodiments provided in this application can be executed on a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware structure block diagram of a computer device for a method of constructing a component database of a server according to an embodiment of this application. Figure 1 As shown, the server device may include one or more ( Figure 1Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The server device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the server equipment described above. For example, the server equipment may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0055] The memory 104 can be used to store computer programs, such as application software programs and module-level programs, such as the computer program corresponding to the method for constructing a server component database in this embodiment. The processor 102 executes various functional applications and data processing by running the computer programs stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the server device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0056] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the server device. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a radio frequency (RF) module for wireless communication with the Internet.

[0057] The terms used in the embodiments of this application are explained as follows:

[0058] Modular BOM: Modular BOM refers to the modular management of common product components, which can generally be assembled into modules according to the requirements of the final assembled product;

[0059] Module level: A hierarchical structure in a modular BOM, below the product level and below the specification level;

[0060] Master Material: In the component product BOM, the parent module level that is consistent with the component category of the component product code is defined as the master material of this component product BOM;

[0061] Auxiliary materials: In the component product BOM, materials other than the main materials are called auxiliary materials;

[0062] Standard auxiliary materials: All auxiliary materials that are required in the product BOM of all components are called standard auxiliary materials.

[0063] This embodiment provides a method for constructing a server component database. Figure 2 This is a flowchart of a method for constructing a server component database according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps:

[0064] Step S12: Obtain the compatibility relationship of each server in the server database in terms of component type, wherein the compatibility relationship is used to indicate that multiple servers as a compatible server group allow the use of server components that belong to the target component type.

[0065] Step S14: Search the server database for the component specification set corresponding to each server in the compatible server group for the target component type, and obtain multiple component specification sets, wherein each component specification set records the component specifications that the corresponding server is allowed to use;

[0066] Step S16: Create component type information corresponding to the target component type for the compatible server group in the component database, wherein the component type information is used to identify server components of the target component type applicable to servers in the compatible server group;

[0067] Step S18: Establish an association between the component type information in the component database and the multiple component specification sets in the server database, wherein the association is used to find server components that are allowed to be used by the servers included in the compatible server group.

[0068] The component database proposed in this application stores the specifications of various server components in the component product BOM. Its storage and management are based on coding. Before describing the relevant optional embodiments of this application, the coding specifications used in the component database and server database of this application are first explained. The component product BOM proposed in this application is divided into three levels of coding, which are, from top to bottom, according to their hierarchical relationship: product-level coding, module-level coding, and specification-level coding. The coding at each level is explained below:

[0069] 1. Product-level coding rules: The product level is a 12-bit code. The first 6 bits are for component classification, and any missing bits are represented by 0, for example, memory is MEM000; the 7th to 12th bits are the serial number.

[0070] 2. Module-level coding rules: There are slight differences between the server database and the component database. In this application, the module-level coding in the component database is defined as the parent module-level coding, with the format MBV-XXXXXX. The first 3 digits are fixed as MBV, the 4th and 5th digits represent the component category (e.g., memory is 03), the 6th digit represents the component size information, and the 7th to 9th digits are the serial number. In contrast, the module-level coding in the server database is the sub-module-level coding, with the format EBV-XXXXXX. The first 3 digits are fixed as EBV, the 4th to 6th digits represent the component category, and the 7th to 9th digits are the serial number.

[0071] 3. Specification-level coding rules: Specification-level coding is used in server component products and services. The coding format is defined as EGV-XXXXXX. The first 3 digits are fixed as EGV, which indicates the specification level. The 4th to 6th digits indicate the component category, such as memory as 003. The 7th to 9th digits are the serial number.

[0072] Optionally, in this embodiment, the server database stores multiple server specifications, as well as the component specifications of various component types of server components that each server specification is compatible with.

[0073] Optionally, in this embodiment, the compatibility relationship is used to indicate that multiple servers, as a compatible server group, allow the use of server components belonging to the target component type. For example, taking the memory component type as the target component type, the server database stores three different server specifications: Product A, Product B, and Product C. Among them, the component specifications of the memory component type server components adapted to Product A include: EGV-003000, EGV-003001, and EGV-003002; the component specifications of the memory component type server components adapted to Product B include: EGV-003001, EGV-003002, and EGV-003003. If Product A and Product B, as a compatible server group, allow the use of server components belonging to the memory component type, it means that Product A and Product B use EGV-003000, EGV-003001, EGV-003002, and EGV-003003. The server database is searched to find the component specification set corresponding to each server in the compatible server group for the target component type, resulting in multiple component specification sets. These multiple component specification sets include the component specification set {EGV-003000, EGV-003001, EGV-003002} corresponding to Product A, and the component specification set {EGV-003001, EGV-003002, EGV-003003} corresponding to Product B.

[0074] Optionally, in this embodiment, component type information corresponding to the target component type is created in the component database for the compatible server group. The aforementioned multiple component specification sets include the component specification set {EGV-003000, EGV-003001, EGV-003002} corresponding to Product A, and the component specification set {EGV-003001, EGV-003002, EGV-003003} corresponding to Product B. Each component specification belongs to the memory component type. If Product A and Product B, as a compatible server group, allow the use of server components belonging to the memory component type, it means that Product A and Product B... Based on the above, in order to establish the association between the component database and the server database, component type information corresponding to the target component type can be created in the component database for the compatible server group. For example, component type information MBV-033000 can be created. MBV-033000 is used to identify the server component {EGV-003000, EGV-003001, EGV-003002, EGV-003003} of the memory component type applicable to the server (Product A or Product B) in the compatible server group.

[0075] Optionally, in this embodiment, an association is established between the component type information in the component database and the multiple component specification sets in the server database. An association is established between the component type information MBV-033000 and {EGV-003000, EGV-003001, EGV-003002}, {EGV-003001, EGV-003002, EGV-003003} in the component database. The specific establishment method will be described below.

[0076] By establishing an association between the component type information in the component database and the multiple component specification sets in the server database, it is possible to use the association in the component database to find server components that can be used by servers included in the compatible server group. For example, if it is necessary to find server components of the memory component type of server Product A, the specification-level code can be directly found from the {EGV-003000, EGV-003001, EGV-003002} and {EGV-003001, EGV-003002, EGV-003003} associated with the component type information MBV-033000, thereby obtaining server components of the memory component type that can be used by Product A. This greatly improves the timeliness of selection and can also ensure the accuracy of the compatibility between the selected server components and Product A.

[0077] The process involves: obtaining compatibility relationships between servers in the server database based on component types. These compatibility relationships indicate which servers, as a compatible server group, are allowed to use server components of the target component type. The process also involves retrieving the corresponding component specification set for each server in the compatible server group from the server database, resulting in multiple component specification sets. Each component specification set records the component specifications allowed for use by the corresponding server. Finally, the process involves creating component type information for the compatible server group in the component database, identifying server components of the target component type suitable for servers in the compatible server group. Finally, the process involves establishing an association between the component type information and the multiple component specification sets in the server database. This association is used to find the server components allowed for use by servers included in the compatible server group, addressing the current issue of low correlation between server component databases and server databases in related technologies. This application proposes a method for constructing a server component database. First, it obtains the compatibility relationships of various servers in the server database regarding component types. A compatibility relationship means that multiple servers forming a compatible server group are allowed to use server components belonging to the target component type. Then, it searches the server database for the component specification set corresponding to the target component type for each server in the compatible server group, obtaining multiple component specification sets. To establish the association between the server component database and the server database, it next creates component type information corresponding to the target component type in the component database for the compatible server group. This component type information identifies server components of the target component type applicable to servers in the compatible server group. Finally, it establishes an association between the component type information in the component database and the multiple component specification sets in the server database. The association established in this way can be used to find server components that are allowed to be used by servers included in the compatible server group. This technical solution solves the problem of low correlation between the server component database and the server database in related technologies, achieving the technical effect of improving the correlation between the server component database and the server database.

[0078] As an optional solution, the step of searching the server database for the component specification set corresponding to each server in the compatible server group for the target component type to obtain multiple component specification sets further includes:

[0079] S21, send a first read instruction to the server database, wherein the first read instruction is used to read the component specification set identifier of the component specification set corresponding to the target component type of each server from the server database;

[0080] S22, receive the set identifiers of multiple component specifications returned by the server database in response to the first read instruction.

[0081] The module-level coding rules mentioned above differ slightly between the server database and the component database. This application defines the module-level coding in the component database as parent module-level coding, with the format MBV-XXXXXX. The first three digits are fixed as MBV, the fourth and fifth digits represent the component category (e.g., memory is 03), the sixth digit represents the component size information, and the seventh to ninth digits are serial numbers. In contrast, the module-level coding in the server database is sub-module-level coding, with the format EBV-XXXXXX. The first three digits are fixed as EBV, the fourth to sixth digits represent the component category, and the seventh to ninth digits are serial numbers. The application also mentions that the component product BOM proposed in this application is divided into three levels of coding, from top to bottom according to the hierarchical relationship: product-level coding, module-level coding, and specification-level coding.

[0082] Optionally, in this embodiment, the component specification set includes multiple component specifications. For example, the component specification set corresponding to Product A is {EGV-003000, EGV-003001, EGV-003002}, and the component specification set corresponding to Product B is {EGV-003001, EGV-003002, EGV-003003}. EGV-XXXXXX in each component specification set is a specification-level code. The server database can use a submodule-level code as the component specification set identifier to identify the corresponding component specification set. For example, the submodule-level code EBV-003000 can be used as the component specification set identifier to identify the component specification set {EGV-003000, EGV-003001, EGV-003002} of Product A, and the submodule-level code EBV-003001 can be used as the component specification set identifier to identify Product B. The component specification set of B is {EGV-003001, EGV-003002, EGV-003003}.

[0083] Optionally, in this embodiment, the server database receives multiple component specification set identifiers returned in response to the first read instruction, that is, the component database can receive EBV-003000 and EBV-003001.

[0084] As an optional approach, establishing the association between the component type information in the component database and the multiple component specification sets in the server database further includes:

[0085] S31, request a first storage space for the component type information in the bill of materials in the component database;

[0086] S32, the component type information and the identifiers of the plurality of component specification sets with the relationship are stored in the first storage space, wherein the identifiers of the plurality of component specification sets are used to indicate that the corresponding component specification set is found in the server database.

[0087] Optionally, in this embodiment, as mentioned above, component type information MBV-033000 can be created to identify server components of memory component type suitable for servers (Product A or Product B) in the compatible server group. Since component specification set identifier EBV-003000 is associated with component specification sets {EGV-003000, EGV-003001, EGV-003002} of Product A, and component specification set identifier EBV-003001 is associated with Product A... The component specification set {EGV-003001, EGV-003002, EGV-003003} of B allows for the direct allocation of first storage space for MBV-033000. This first storage space stores the associated component type information MBV-033000 and the multiple component specification set identifiers EBV-003000 and EBV-003001. Thus, based on the component type information MBV-033000, it can be associated with the component specification set identifiers EBV-003000 and EBV-003001, thereby determining the server component {EGV-003000, EGV-003001, EGV-003002, EGV-003003} of the memory component type suitable for the server (Product A or Product B) in the compatible server group.

[0088] In the above method, the association between the component type information in the component database and the multiple component specification sets in the server database is established by establishing an association between the component type information MBV-033000 and the component specification set identifiers EBV-003000 and EBV-003001. MBV-033000 is the parent module-level code in the component database, and EBV-003000 and EBV-003001 are the sub-module-level codes in the server database. By establishing an association between the parent module-level codes and the sub-module-level codes, the association between the component database and the server database is achieved. This solves the problem of low association between the server's component database and the server database in related technologies, and achieves the technical effect of improving the association between the server's component database and the server database.

[0089] The above method establishes an association between component type information MBV-033000 and component specification set identifiers EBV-003000 and EBV-003001, thereby establishing an association between the component type information in the component database and the multiple component specification sets in the server database. This method enables mutual access to data between different databases. In other words, the component specification sets {EGV-003000, EGV-003001, EGV-003002} of Product A and the component specification sets {EGV-003001, EGV-003002, EGV-003003} of Product B in the server database can directly access the specific specification-level codes in the server database from the component database side through the association between component type information MBV-033000 and component specification set identifiers EBV-003000 and EBV-003001, saving data synchronization resources and computational resources used to create data in the component database.

[0090] Unlike the above method that only associates the component type information MBV-033000 with the component specification set identifiers EBV-003000 and EBV-003001, it is also possible to establish an association between the component type information MBV-033000 and the corresponding component specification set, which will be introduced below.

[0091] As an optional solution, the step of searching the server database for the component specification set corresponding to each server in the compatible server group for the target component type to obtain multiple component specification sets further includes:

[0092] S41, send a second read instruction to the server database, wherein the second read instruction is used to read the set of component specifications corresponding to each server for the target component type from the server database;

[0093] S42, receive the set of multiple component specifications returned by the server database in response to the second read instruction.

[0094] Optionally, in this embodiment, unlike the first read instruction mentioned above which returns multiple component specification set identifiers, namely EBV-003000 and EBV-003001, the second read instruction in this embodiment returns multiple component specification sets, namely the component specification set {EGV-003000, EGV-003001, EGV-003002} of Product A and the component specification set {EGV-003001, EGV-003002, EGV-003003} of Product B.

[0095] As an optional approach, establishing the association between the component type information in the component database and the multiple component specification sets in the server database further includes:

[0096] S51, request a second storage space for the component type information in the bill of materials in the component database;

[0097] S52, the component type information and target component specification set with association relationship are stored in the second storage space, wherein the target component specification set is the union of the multiple component specification sets, and the target component specification set is used to find server components belonging to the target component type that are allowed to be used by the servers included in the compatible server group.

[0098] Optionally, in this embodiment, the target component specification set is the union of the plurality of component specification sets. When the plurality of component specification sets are the component specification set {EGV-003000, EGV-003001, EGV-003002} of Product A and the component specification set {EGV-003001, EGV-003002, EGV-003003} of Product B, the target component specification set is {EGV-003000, EGV-003001, EGV-003002, EGV-003003}. By applying for a second storage space for the component type information MBV-033000, the associated component type information MBV-033000 and the target component specification set {EGV-003000, EGV-003001, EGV-003002, EGV-003003} are stored in the second storage space.

[0099] This approach directly establishes the association between the component type information MBV-033000 and the target component specification set {EGV-003000, EGV-003001, EGV-003002, EGV-003003} in the component database. On the one hand, it can accelerate the efficiency of finding the corresponding component specification based on MBV-033000 without accessing other databases to obtain data. On the other hand, when cross-database access between databases fails, local lookup can be achieved without affecting the efficiency of component specification lookup, thus improving the stability of component specification lookup.

[0100] As an optional approach, after storing the associated component type information and target component specification set in the second storage space, the method further includes: detecting the component specifications allowed to be used by each server in the server database; and if it is detected that one or more new component specifications have been added to the target component specification set for each server in the compatible server group that are allowed to use the target component type. Figure 3 This is a schematic diagram illustrating the updating of a target component specification set according to an embodiment of this application, such as... Figure 3 As shown, the parent module-level code MBV-033000 in the component database is associated with the sub-module-level codes EBV-003000 and EBV-003001 in the server database. The parent module-level code is applied for in the PLM (Product Lifecycle Management) system, and the associated sub-module-level codes are filled in. The sub-module-level codes are required and multiple sub-module-level codes can be associated. After the application is completed, the specification-level code under the parent module level of the component product is the collection of the specification-level codes under all sub-module level codes. For example, if the specification-level codes under EBV-003000 include {EGV-003000, EGV-003001, EGV-003002}, and the specification-level codes under EBV-003001 include {EGV-003001, EGV-003002, EGV-003003}, then the specification-level codes under the parent module level are {EGV-003000, EGV-003001, EGV-003002, EGV-003003}. After the parent module level codes are created, sub-module level codes can be added through modifications. Submodule-level coding is used in the server product BOM. As the server product components are continuously adapted, the component specification-level coding of the adapted components is added. For example, if the latest adaptation of server Product A adds EGV-003006, the parent module-level coding will synchronize with the change of the submodule-level coding to obtain the updated target component specification set {EGV-003000, EGV-003001, EGV-003002, EGV-003003, EGV-003006}.

[0101] As an optional approach, establishing the association between the component type information in the component database and the multiple component specification sets in the server database further includes:

[0102] S61, extract the first information field from the component type information that indicates the target component type;

[0103] S62, search for the auxiliary component specification set corresponding to the first information field from the auxiliary component library stored in the component database, and search for the installation manual specification set corresponding to the first information field from the installation manual specification library stored in the component database, wherein the component specification set records the main component specifications belonging to the target component type;

[0104] S63, extract the second information field from the component type information that indicates the component size of the main material component belonging to the target component type;

[0105] S64, Search for the set of packaging specifications corresponding to the second information field from the component packaging specification library stored in the component database;

[0106] S65, In the component database, auxiliary component information is created for the auxiliary component specification set, installation manual information is created for the installation manual specification set, and packaging information is created for the packaging specification set, wherein the auxiliary component information is used to identify the auxiliary component specification set, the installation manual information is used to identify the installation manual specification set, and the packaging information is used to identify the packaging specification set;

[0107] S66, Establish the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database.

[0108] The above mentions module-level coding rules: there are slight differences between the server database and the component database. In this application, the module-level coding in the component database is defined as the parent module-level coding, with the format MBV-XXXXXX. The first 3 digits are fixed as MBV, the 4th and 5th digits represent the component category (e.g., memory is 03), the 6th digit represents the component size information, and the 7th to 9th digits are the serial number. In contrast, the module-level coding in the server database is the sub-module-level coding, with the format EBV-XXXXXX. The first 3 digits are fixed as EBV, the 4th to 6th digits represent the component category, and the 7th to 9th digits are the serial number.

[0109] Optionally, in this embodiment, taking MBV-033000 as an example, MBV-033000 is a parent module-level code. The 4th and 5th digits "03" indicate the component category, such as memory being 03. The 6th digit "3" indicates the component size information. The first information field consists of the 4th and 5th digits of the parent module-level code. Based on the first information field, the target component type can be determined, and thus the auxiliary component specification set and installation manual specification set can be determined. The component specification set records the main component specifications belonging to the target component type. The relationship between auxiliary components and main components can be understood as mutual cooperation to complete specific functions. In this process, the main component undertakes the core function, and the auxiliary component assists the main component in achieving the core function. For example, if the main component is a hard drive, the auxiliary main component can be a hard drive bracket. The hard drive and the hard drive bracket are assembled together to achieve storage functionality. The hard drive is used for storage, and the hard drive bracket is used for mounting the hard drive. Therefore, the target component type can be clearly identified through the first information field, and thus the corresponding auxiliary component specification set can be determined.

[0110] Optionally, in this embodiment, server components of the same target component type have essentially the same installation methods, and therefore their installation manuals are also largely similar. The target component type can be clearly identified through the first information field, thereby determining the corresponding set of installation manual specifications. Figure 4 This is a schematic diagram of an installation manual specification library according to an embodiment of this application, such as... Figure 4 As shown, different component categories correspond to different component installation manual specification levels. 03 indicates the memory component type, and the corresponding installation manual specification level is EGV-XXX003.

[0111] Optionally, in this embodiment, the packaging specifications are related to the component dimensions and shipping method of the main material component. The packaging specification set corresponding to the second information field is retrieved from the component packaging specification library stored in the component database. Figure 5 This is a schematic diagram of a component packaging specification library according to an embodiment of this application, such as... Figure 5 As shown, the component size information is represented by the 6th bit (i.e., the second information field) of the parent module level code, and the corresponding shipping method determines the set of packaging specifications. Among them, there are two shipping methods: BULK-PACKAGE and SINGLE-PACKAGE.

[0112] Optionally, in this embodiment, Figure 6 This is a schematic diagram illustrating how to search for an installation manual specification set and a packaging specification set based on component type information, according to an embodiment of this application. Figure 6As shown, the standard accessories for component productization include installation manuals and packaging boxes, which are essential for all component productization BOMs. A standard accessory specification library is established, namely an installation manual specification library and a component packaging specification library, which are retrieved by maintaining a specification-level correspondence table. Installation manuals are only related to component categories (component types), and a maintenance table is established to link manual specification levels with component categories. Packaging boxes are related to component dimensions and shipping methods. The component packaging specification library contains packaging specifications for all component products, each corresponding to a different component size. These are associated with the component size information in the parent module-level code of the main component. For example, a 590x490x340 packaging box is suitable for components with size codes 1 and 2. There are two shipping methods: bulk packaging and single packaging. The bulk packaging option is BULK-PACKAGE, and the single packaging option is SINGLE-PACKAGE. The final selected shipping method determines the final packaging specifications to be retrieved.

[0113] The method for constructing a server component database proposed in this application includes creating component type information corresponding to the target component type for the compatible server group in the component database; and establishing an association between the component type information and the multiple component specification sets in the server database. The component product BOM is constructed in the component database through the above operations. The component product BOM can be generated by uploading it to the PLM system using an Excel loadsheet tool. A detailed description of the BOM loadsheet is provided below:

[0114] The tool Loadsheet consists of two parts: BOM Information and Character Information. BOM Information mainly reflects the structure information of the BOM hierarchy (the subordinate relationship between each level, such as the subordinate relationship between product-level codes, module-level codes, and specification-level codes) and specification-level output conditions. Character Information mainly reflects the optional items information.

[0115] 1. BOM Information, as shown in Table 1, includes the following: Component Product Code (MEM000000001), Mother Module Level Code (MBV-033000, MBV-089001, MBV-079001), Specification Level Code (EGV-089000, EGV-089001, EGV-079000, EGV-079001), Basic Quantity, Selection Criteria, and Quantity Criteria. The main component's parent module-level code (MBV-033000) has been associated with the sub-module-level codes (EBV-003000 and EBV-003001) in the component database and the server database. Since the sub-module-level codes already have specification-level codes, it is not necessary to fill in the specification-level codes under the parent module level. For other parent module levels besides the main component (MBV-089001, MBV-079001), specification-level information must be filled in. These other parent module-level codes can identify the corresponding auxiliary component specification set, or an installation manual. A specification set, or a packaging specification set, for example, MEM000000001 indicates a memory product with a memory component type identified by MBV-033000, a packaging box identified by MBV-089001, and a paper label identified by MBV-079001. The specific packaging box specifications identified by MBV-089001 include EGV-089000 and EGV-089001, and the specific paper label specifications identified by MBV-079001 include EGV-079000 and EGV-079001.

[0116] Table 1

[0117] operate Product-level coding Parent component coding Sub-component coding Sub-component overview line number Basic quantity Selection criteria Quantity control Add MEM000000001 MEM000000001 MBV-033000 XXX XX 1 MEM000000001 MBV-089001 XXX XX 1 MEM000000001 MBV-079001 XXX XX 1 MBV-089001 EGV-089000 XXX XX 1 MBV-089001 EGV-089001 XXX XX 1 MBV-079001 EGV-079000 XXX XX 1 MBV-079001 EGV-079001 XXX XX 1

[0118] 2. Character Information: As shown in Table 2, first fill in the component product-level code. The rule for filling in the characteristic code is as follows: Product line category abbreviation_Product model_Component type_Other. For example, the characteristic code for a hard drive tray is S_M6_HDD_TRAY. Then fill in the characteristic name, which is the name of this characteristic in the configuration interface. After that, fill in information such as whether it is displayed and whether it is required. The characteristic value code of auxiliary materials should be filled in with the specification-level code in the BOM Information. For example, the specification level of the hard drive tray should be filled in under the characteristics of the hard drive tray. Specification levels that do not need to be displayed in the configuration interface should not be filled in. The characteristic value code of the main component should be filled in with the parent module-level code of the main component. The PLM system retrieves the specification-level code under the parent module level for configuration.

[0119] In the BOM Information, the selection criteria for specification-level codes and quantity conditions are derived by entering the characteristic code or performing certain calculations on the characteristic code. For example, if selecting this specification-level code will retrieve this specification-level, then simply enter the characteristic code of the characteristic containing this specification-level in the selection criteria. For the quantity condition, enter the quantity characteristic corresponding to this characteristic. Furthermore, module-level codes are derived along with the specification-level codes of their subordinate levels. If none of the subordinate specification-level codes are derived, then the module-level codes will also not be derived. The parent module-level code is mandatory and does not require a selection criterion.

[0120] Table 2

[0121] operate Optional product-level coding Feature coding Feature Name Feature value encoding Characteristic value Show or not? Is it mandatory? #EOF S00HDD000001 S_M6_CATEGORY Product Category Y Y 0010 1010 S00HDD000001 S_M6_SHIP Packaging Y Y BULK-PACKAGE SINGLE-PACKAGE S00HDD000001 S_M6_HDD_TRAY hard drive caddy Y Y EGV-089000 EGV-089001 S00HDD000001 S_M6_HDD_25HD harddisk MBV-002000

[0122] As an optional approach, after establishing the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database, the following further steps are included:

[0123] S71, receives server orders from the target server;

[0124] S72, Detect whether the target server belongs to the compatible server group;

[0125] S73, if the target server is detected to belong to the compatible server group, detect whether the server order indicates that the target server has an expansion requirement;

[0126] S74, if the server order indicates that the target server has an expansion requirement, extract the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information and the packaging information from the component database;

[0127] S75, generate a component expansion order for the target server based on the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information.

[0128] Optionally, in this embodiment, to meet the later upgrade and expansion needs of the server product, a "nopart" option is added under the options of the server product BOM, indicating that expansion is required. The selected quantity is the quantity to be expanded later. The BOM will list the corresponding accessories (i.e., auxiliary components) required for expansion. For example, expanding a hard drive will include the hard drive backplane and cables. The component product BOM and the server product BOM are associated through parent-child module-level coding. After the server product BOM is selected and an order is placed, the system identifies whether the server order has a "nopart" option. If so, it indicates that the server order indicates that the target server has expansion requirements. The module-level coding corresponding to the "nopart" characteristic is associated with the parent module-level coding of the component product to form a component expansion order. As shown in Table 3, the information of the component expansion order includes the product order number, the expanded component, the quantity of the expanded component, the corresponding component product-level coding, and the generated expansion order number. For later customer service expansion, you can directly enter the server order number of the server order to find the corresponding component expansion order number, and then enter the corresponding component product-level code to select the component. The expansion quantity is the number of noparts selected for the product by default.

[0129] Table 3

[0130] Server order number Expansion components Number of expanded components Component product level coding Component expansion order number XXXXXX harddisk 8 S00HDD00000 XXXXXX XXXXXX Memory 12 S00MEM00000 XXXXXX

[0131] Optionally, in this embodiment, in order to better understand the process of constructing the component database of the server, the process of constructing and using the component database of the server will be described below in conjunction with optional embodiments, but this is not intended to limit the technical solution of the embodiments of this application.

[0132] This embodiment provides a method for constructing a server component database. Figure 7 This is a schematic diagram illustrating the process of constructing and using a server component database according to an embodiment of this application, as shown below. Figure 7 As shown, the main steps include the following:

[0133] Step S701: Apply for a component product-level code.

[0134] Define the component product level coding rules: ① Apply for a component product level code in the PLM system. When applying, fill in the component name, the quoted model name / platform, and other information. The completed component product level code is, for example, S00HDD000001.

[0135] ② Apply for a parent module-level code for the component product. Fill in the component category and sub-module-level code; these two items are mandatory. After completion, the system will verify the information. The sub-module-level code must be an existing and officially released sub-module-level code in the system. The component category of the sub-module-level code must be consistent with the parent module-level code; otherwise, the system will report an error and the application will fail. After the application is completed, the specification-level codes under the parent module-level code will be extracted from the sub-module-level codes and merged. Duplicate specification-level codes will be verified and deleted by the system.

[0136] ③ Apply for module-level and specification-level codes for other related auxiliary materials, and attach the relevant physical materials to the corresponding specification-level codes;

[0137] Step S702: Create a component product BOM Loadsheet.

[0138] BOM Information: Enter the component product code in the Product Code column, such as MEM000000001. Enter the component product code and module-level code in the parent component code column. Enter the module-level code and specification-level code in the corresponding child component codes respectively. Do not enter the child component code in the parent module-level code column. Enter the corresponding quantity in the Basic Quantity column. The quantity of the module-level code is fixed at 1. Enter the quantity of the specification-level code according to the actual situation.

[0139] Character Information: First, fill in the product parent module level code, then the component product level code, and finally the characteristic code. The characteristic code filling rules are as follows: Product line category abbreviation_Product model_Component type_Other. For example, the characteristic code for a hard drive tray is S_M6_HDD_TRAY. Then, fill in the characteristic name, which is the name of this characteristic in the configuration interface, followed by information such as whether it is displayed and whether it is required. Characteristic values ​​must be filled in under the characteristic code. Under the main material characteristic, fill in the parent module level code; for other characteristics, fill in the specification level code or text value. After filling in the information, fill in the selection conditions and quantity conditions for the specification level code in BOMInformation. If selecting this specification level code will bring it out, then write the characteristic code of the characteristic containing this specification level code in the selection conditions, and fill in the quantity characteristic corresponding to this characteristic in the quantity conditions. The module level code is brought out according to the lower-level specification level code conditions; the parent module level code is mandatory.

[0140] Step S703: Upload the Loadsheet and perform system verification.

[0141] After completing the loadsheet, upload it to the PLM system. During the upload process, the system will verify the following information:

[0142] ① First, search for all required fields and fill them in. If any fields are missing, report an error and make corrections.

[0143] ② All module-level and specification-level codes are verified in the system and must be codes that exist in the system;

[0144] ③ The parent module-level code under the retrieval feature is searched in the system, and the specification-level code under the parent module-level code in the system is added to this feature. If there are multiple parent module-level codes, they are all searched and added using this feature.

[0145] ④ The system verifies the selection criteria and quantity control criteria in the BOM Information. All characteristics entered must exist in the Character Information.

[0146] Step S704: Retrieve the installation manual and packaging specifications.

[0147] After the Loadsheet is uploaded, the system recognizes it as a component product-level code. It then retrieves the installation manual specification library, comparing the component classification information in the parent module-level code with that in the library. The system finds the installation manual specifications for components in the same category and appends the specification-level code to the corresponding parent module-level code. This specification is not displayed in the selection interface but is carried over with the parent module-level code. Next, the system retrieves the packaging specification library, comparing the component size information in the parent module-level code with that in the library. The system finds the corresponding packaging specifications and appends the packaging specifications for different shipping methods to the parent module-level code. These specifications are not displayed in the selection interface but are carried over with the parent module-level code and the selected shipping method. If there are multiple parent module-level codes, this process is repeated until all parent module-level codes have been retrieved. If no matching specification is found during the comparison, the system reports an error, and the Loadsheet cannot be uploaded. The installation manual and packaging specification libraries need to be maintained before re-uploading.

[0148] Step S705: Generate the component product BOM.

[0149] After the loadsheet is uploaded and the installation manual and packaging specifications are retrieved, the initial creation of the component product BOM is completed. Simulation and selection are performed. If there are any problems, adjustments are made. If there are no problems, it is released, and the creation of the component product BOM is completed. At this point, the construction of the component database on the server is complete.

[0150] Step S706: Generate component expansion order.

[0151] The process of using the server's component database is as follows: After the component product BOM is completed and published, the front end selects a menu. After the menu is completed, the system verifies whether the server order contains the "nopart" option information. If "nopart" is selected in the server order, it means that this server order needs to be expanded. The system retrieves the server order and generates a product expansion order. The system first retrieves the submodule-level code where "nopart" is located, associates it with the corresponding parent module-level code, fills the component product-level code where the parent module-level code is located and the server order number selected this time into the product expansion order database, generates this component expansion order number, and fills the component category of this parent module-level code into this component expansion order. Then, it retrieves the quantity of "nopart" selected and fills it into the expansion component quantity of the component expansion order. This generates a complete component expansion order.

[0152] Step S707: Optional server component expansion order.

[0153] After the server product is shipped, if you need to expand its configuration, first go to the product expansion order database, enter the server order number when the product was previously ordered, find the corresponding component expansion order, click to enter the corresponding component product level code to select the components. The number of components to be selected is the number of expansion components in the expansion order by default. You only need to select the specifications of the components to be expanded this time. After the selection is completed, place the order and ship the product to upgrade and expand the server.

[0154] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0155] This embodiment also provides a device for constructing a server component database, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module level" can refer to a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0156] Figure 8 This is a structural block diagram of a component database construction apparatus for a server according to an embodiment of this application; as shown... Figure 8As shown, it includes:

[0157] The acquisition module 802 is used to acquire the compatibility relationship of each server in the server database in terms of component type, wherein the compatibility relationship is used to indicate that multiple servers as a compatible server group allow the use of server components that belong to the target component type.

[0158] The lookup module 804 is used to look up the set of component specifications corresponding to each server in the compatible server group for the target component type from the server database, and obtain multiple sets of component specifications, wherein each set of component specifications records the component specifications that the corresponding server is allowed to use.

[0159] A creation module 806 is used to create component type information corresponding to the target component type for the compatible server group in the component database, wherein the component type information is used to identify server components of the target component type applicable to servers in the compatible server group;

[0160] A module 808 is established to establish an association between the component type information in the component database and the multiple component specification sets in the server database, wherein the association is used to find server components that are allowed to be used by the servers included in the compatible server group.

[0161] In one exemplary embodiment, the lookup module includes:

[0162] The first sending unit is configured to send a first read instruction to the server database, wherein the first read instruction is configured to read from the server database the part specification set identifier of the part specification set corresponding to the target part type for each server;

[0163] The first receiving unit is configured to receive a set of multiple component specification identifiers returned by the server database in response to the first read instruction.

[0164] In one exemplary embodiment, the establishment module includes:

[0165] The first application unit is used to apply for a first storage space for the component type information in the bill of materials in the component database;

[0166] The first storage unit is used to store the associated component type information and the multiple component specification set identifiers in the first storage space, wherein the multiple component specification set identifiers are used to indicate that the corresponding component specification set is found in the server database.

[0167] In one exemplary embodiment, the lookup module includes:

[0168] The second sending unit is used to send a second read instruction to the server database, wherein the second read instruction is used to read from the server database the set of component specifications corresponding to each server for the target component type;

[0169] The second receiving unit is used to receive the set of multiple component specifications returned by the server database in response to the second read instruction.

[0170] In one exemplary embodiment, the establishment module includes:

[0171] The second application unit is used to apply for a second storage space for the component type information in the bill of materials in the component database;

[0172] The second storage unit is used to store the associated component type information and target component specification set in the second storage space, wherein the target component specification set is the union of the multiple component specification sets, and the target component specification set is used to find server components belonging to the target component type that are allowed to be used by the servers included in the compatible server group.

[0173] In one exemplary embodiment, the establishment module includes:

[0174] The first extraction unit is used to extract the first information field in the component type information that indicates the target component type;

[0175] The first search unit is used to search for the auxiliary component specification set corresponding to the first information field from the auxiliary component library stored in the component database, and to search for the installation manual specification set corresponding to the first information field from the installation manual specification library stored in the component database, wherein the component specification set records the main component specifications belonging to the target component type.

[0176] The second extraction unit is used to extract the second information field from the component type information, which indicates the component size of the main material component belonging to the target component type;

[0177] The second search unit is used to search for the set of packaging specifications corresponding to the second information field from the component packaging specification library stored in the component database;

[0178] A creation unit is used to create auxiliary component information for the auxiliary component specification set, installation manual information for the installation manual specification set, and packaging information for the packaging specification set in the component database, wherein the auxiliary component information is used to identify the auxiliary component specification set, the installation manual information is used to identify the installation manual specification set, and the packaging information is used to identify the packaging specification set;

[0179] A creation unit is used to establish the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database.

[0180] In one exemplary embodiment, the apparatus further includes:

[0181] The receiving module is used to establish the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information and the packaging information in the component database, and then receive the server order from the target server.

[0182] The first detection module is used to detect whether the target server belongs to the compatible server group;

[0183] The second detection module is used to detect whether the server order indicates that the target server has an expansion requirement when the target server is detected to belong to the compatible server group.

[0184] The extraction module is used to extract the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information from the component database when the server order indicates that the target server has an expansion requirement.

[0185] The generation module is used to generate a component expansion order for the target server based on the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information.

[0186] It should be noted that the above-mentioned module levels can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to these: all the above-mentioned module levels are located in the same processor; or, the above-mentioned module levels are located in different processors in any combination.

[0187] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0188] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0189] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0190] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0191] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0192] Obviously, those skilled in the art should understand that the various module levels or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit module levels, or multiple module levels or steps can be fabricated as a single integrated circuit module level. Thus, this application is not limited to any particular combination of hardware and software.

[0193] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for constructing a component database for a server, characterized in that, include: Obtain the compatibility relationship of each server in the server database in terms of component type, wherein the compatibility relationship is used to indicate that multiple servers as a compatible server group allow the use of server components that belong to the target component type; The server database is searched for the component specification set corresponding to the target component type for each server in the compatible server group, resulting in multiple component specification sets. Each component specification set records the component specifications that the corresponding server is allowed to use. In the component database, component type information corresponding to the target component type is created for the compatible server group, wherein the component type information is used to identify server components of the target component type applicable to servers in the compatible server group; An association is established between the component type information in the component database and the multiple component specification sets in the server database, wherein the association is used to find server components that are allowed to be used by the servers included in the compatible server group.

2. The method according to claim 1, characterized in that, The step involves searching the server database for the component specification set corresponding to each server in the compatible server group for the target component type, resulting in multiple component specification sets, including: Send a first read instruction to the server database, wherein the first read instruction is used to read the component specification set identifier of the component specification set corresponding to the target component type for each server from the server database; Receive the set of multiple component specification identifiers returned by the server database in response to the first read command.

3. The method according to claim 2, characterized in that, The step of establishing the association between the component type information in the component database and the multiple component specification sets in the server database includes: Allocate first storage space for the component type information in the bill of materials in the component database; The first storage space stores the component type information and the identifiers of the multiple component specification sets that have an association relationship, wherein the identifiers of the multiple component specification sets are used to indicate that the corresponding component specification set is found in the server database.

4. The method according to claim 1, characterized in that, The step involves searching the server database for the component specification set corresponding to each server in the compatible server group for the target component type, resulting in multiple component specification sets, including: Send a second read instruction to the server database, wherein the second read instruction is used to read from the server database the set of component specifications corresponding to each server for the target component type; The server database receives the set of multiple component specifications returned by the second read instruction.

5. The method according to claim 4, characterized in that, The step of establishing the association between the component type information in the component database and the multiple component specification sets in the server database includes: Request a second storage space for the component type information in the bill of materials in the component database; The second storage space stores the associated component type information and target component specification set, wherein the target component specification set is the union of the multiple component specification sets, and the target component specification set is used to find server components belonging to the target component type that are allowed to be used by the servers included in the compatible server group.

6. The method according to claim 1, characterized in that, The step of establishing the association between the component type information in the component database and the multiple component specification sets in the server database includes: Extract the first information field from the component type information that indicates the target component type; The auxiliary component specification set corresponding to the first information field is searched from the auxiliary component library stored in the component database, and the installation manual specification set corresponding to the first information field is searched from the installation manual specification library stored in the component database, wherein the component specification set records the main component specifications belonging to the target component type. Extract the second information field from the component type information, which indicates the component size of the main material component belonging to the target component type; Search the packaging specification set corresponding to the second information field from the component packaging specification library stored in the component database; In the component database, auxiliary component information is created for the auxiliary component specification set, installation manual information is created for the installation manual specification set, and packaging information is created for the packaging specification set. The auxiliary component information is used to identify the auxiliary component specification set, the installation manual information is used to identify the installation manual specification set, and the packaging information is used to identify the packaging specification set. Establish the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database.

7. The method according to claim 6, characterized in that, After establishing the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information in the component database, the method further includes: Receive server orders from the target server; Detect whether the target server belongs to the compatible server group; If the target server is detected to belong to the compatible server group, it is detected whether the server order indicates that the target server has an expansion requirement; If the server order indicates that the target server has an expansion requirement, the association between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information is extracted from the component database. Based on the correlation between the component type information and the multiple component specification sets, the auxiliary component information, the installation manual information, and the packaging information, a component expansion order is generated for the target server.

8. An apparatus for constructing a component database for a server, characterized in that, include: The acquisition module is used to acquire the compatibility relationship of each server in the server database in terms of component type, wherein the compatibility relationship is used to indicate that multiple servers as a compatible server group allow the use of server components that belong to the target component type. The lookup module is used to look up the set of component specifications corresponding to each server in the compatible server group for the target component type from the server database, and obtain multiple sets of component specifications, wherein each set of component specifications records the component specifications that the corresponding server is allowed to use; A creation module is used to create component type information corresponding to the target component type for the compatible server group in the component database, wherein the component type information is used to identify server components of the target component type applicable to servers in the compatible server group; A module is established to create an association between the component type information in the component database and the multiple component specification sets in the server database, wherein the association is used to find server components that are allowed to be used by the servers included in the compatible server group.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 7.

Images