Bill of materials maintenance method and device, computer device, and storage medium

Abstract

The present application relates to the technical field of computer, disclose bill of materials maintenance method, device, computer equipment and storage medium, the method comprises: constructing module library, the corresponding relationship between module level coding in bill of materials and the interface coding of each backboard interface and the installation sequence of backboard interface are contained in module library;Build cable library, the corresponding relationship between cable coding and interface coding is contained in cable library;Obtain the corresponding relationship between specification level coding and cable coding in bill of materials;According to the corresponding relationship between module level coding and interface coding, the corresponding relationship between cable coding and interface coding and the corresponding relationship between specification level coding and cable coding generate list, the corresponding relationship between module level coding, specification level coding and product characteristic coding is contained in list;According to list and module library, construct case table;Combine list and case table to form cable part in bill of materials.It is realized that cable is maintained into bill of materials automatically and generates case table.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a method, apparatus, computer equipment, and storage medium for maintaining a bill of materials. Background Technology

[0002] As products are updated, the number of Central Processing Units (CPUs) and Local Area Networks (LANs) is increasing, and the number of supported components is also growing. These components communicate using MCIO (Mini Cool Edge IO). TM The interface establishes a connection via cable.

[0003] A Bill of Materials (BOM) is a list of all the sub-materials that make up a product. A modular BOM is a hierarchical BOM, distinct from a flat BOM. The materials that make up the product are divided into several modules, and all modules constitute a complete modular BOM. Each module contains several different specifications, allowing different specifications to be selected for different product configurations.

[0004] The modular BOM contains numerous configurations, with different components reusing MCIO interfaces, and the same interface using different cable codes under different configurations. Currently, the modular BOM is created using a method of superimposing cable codes at the specification level, manually establishing a large number of specification levels containing duplicate cable materials. Because different specification levels are derived for each configuration, the modular BOM data volume increases dramatically, making relationship restrictions difficult. The system has a large number of specification-level part numbers, consuming significant time for management and maintenance, making changes even more difficult, and specification levels cannot be reused across different projects. Summary of the Invention

[0005] In view of this, the present invention provides a bill of materials (BOM) maintenance method, apparatus, computer equipment and medium to solve the problems of numerous cable specifications in the system, inability to reuse specifications between different BOMs, and complex cable restriction relationships in BOM maintenance.

[0006] In a first aspect, the present invention provides a bill of materials (BOM) maintenance method, the method comprising: constructing a module library, the module library containing the correspondence between module-level codes in the BOM and interface codes of each backplane interface, and the installation order of each backplane interface when installing various types of hard drives in different backplanes, wherein one backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes; constructing a cable library, the cable library containing the correspondence between cable codes of each cable and interface codes of each backplane interface, wherein one cable code corresponds to one or more backplane interface codes from different backplanes; obtaining the BOM from the BOM... The document establishes the correspondence between specification-level codes and cable codes; it generates a list based on the correspondence between module-level codes and interface codes, cable codes and interface codes, and specification-level codes and cable codes. The list contains the correspondence between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code. A case study table is constructed based on the list and module library. The case study table represents the constraint relationship between the total number of different types of hard drives and the specification-level codes of each cable. The cable section of the bill of materials is formed by combining the list and the case study table.

[0007] The automatic cable maintenance method provided in this invention enables the system to automatically maintain cables in a modular bill of materials (BOM) and generate a case study table with constraints. This automates the complex cable maintenance process and the creation of numerous manually written case studies, reducing the time required for modular BOM creation and maintenance, and decreasing the probability of human error. Furthermore, in this invention, the correspondence between backplane interfaces and module levels, as well as the installation order of backplane interfaces, are defined first. When a cable is needed, its specification level is retrieved from the system and applied to the subsequent BOM construction. Based on the installation order, backplane interfaces, and corresponding cable specification levels, a case study table with constraints is generated, restricting different configurations from using their corresponding cables. This eliminates the need to stack cable part numbers at the specification level; each specification level has only one cable part number, resulting in a single set of codes in the system. New projects can be maintained quickly, as the system rapidly locates and maintains cables in the modular BOM using preset rules.

[0008] In one optional implementation, the list includes a first sub-list and a second sub-list. The step of generating the list based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes includes: determining multiple module-level codes corresponding to a product; establishing a correspondence between a product's module-level codes and product characteristic codes, where one module-level code corresponds to one product characteristic code; determining the correspondence between module-level codes and specification-level codes based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes; establishing a first sub-list based on the correspondence between module-level codes and product characteristic codes, and the correspondence between module-level codes and specification-level codes, where the first sub-list contains the correspondence between module-level codes, specification-level codes, and product characteristic codes; and establishing a second sub-list based on the first sub-list, where the second sub-list determines the specification-level codes corresponding to each product characteristic code, where one product characteristic code corresponds to one or more specification-level codes.

[0009] In one optional implementation, a case table is constructed based on the manifest and module library, including: determining multiple configuration information, which includes product feature codes and the number of hard drives installed for each type, the range of which is limited by the installation order of each backplane interface in the module library; determining the specification-level code and module-level code corresponding to the product feature codes in the configuration information based on the manifest; determining the hard drive type corresponding to the module-level code and the interface installation order of the hard drive based on the module-level code and the module library; and generating a case table based on the number of hard drives installed for each type, the interface installation order, and the specification-level code corresponding to the product feature code in the configuration information, the case table being used to restrict the correspondence between different configuration information and cables.

[0010] In an optional implementation, the method further includes: receiving updated configuration information; selecting a target cable from a cable library based on the updated configuration information, and determining the target interface code corresponding to the target cable; if the cable library contains all cables, and the information in the module library is consistent with that in the cable library, determining the target module-level code corresponding to the target interface code based on the module library; determining the correspondence between specification-level codes and cable codes in the bill of materials, and determining the target specification-level code corresponding to the target cable; if the target interface code is not duplicated, updating the list based on the correspondence between the target module-level code, the target specification-level code, and the target product characteristic code, wherein the target product characteristic code corresponds to the updated configuration information; determining the hard drive type corresponding to the target module-level code and the interface installation order corresponding to the hard drive based on the target module-level code and the module library; and updating the case table restriction relationship based on the installation quantity of each type of hard drive, the interface installation order, and the target specification-level code corresponding to the target product characteristic code in the updated configuration information.

[0011] In one alternative implementation, if the cable library does not contain all cables, the cable library is maintained.

[0012] In one alternative implementation, if the information in the module library and the cable library is inconsistent, the module library is maintained.

[0013] In one alternative implementation, if the target interface code is duplicated, distinguishing conditions are maintained.

[0014] Secondly, the present invention provides a bill of materials (BOM) maintenance device, comprising: a module library construction module for constructing a module library, the module library containing the correspondence between module-level codes in the BOM and interface codes of each backplane interface, and the installation order of each backplane interface when installing various types of hard drives in different backplanes, wherein one backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes; a cable library construction module for constructing a cable library, the cable library containing the correspondence between cable codes of each cable and interface codes of each backplane interface, wherein one cable code corresponds to one or more backplane interface codes from different backplanes; and a specification-level code acquisition module for acquiring the BOM. The system includes: a specification-level code and a cable code mapping module; a bill of materials generation module, which generates a bill of materials based on the mappings between module-level codes and interface codes, cable codes and interface codes, and specification-level codes and cable codes. The bill of materials includes mappings between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code; a case table generation module, which constructs a case table based on the bill of materials and the module library. The case table represents the constraint relationship between the total number of hard drives of different types and the specification-level codes of each cable; and a bill of materials maintenance module, which combines the bill of materials and the case table to form the cable section of the bill of materials.

[0015] Thirdly, the present invention provides a computer device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to perform the bill of materials maintenance method of the first aspect or any corresponding embodiment described above.

[0016] Fourthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to perform the bill of materials maintenance method of the first aspect or any corresponding embodiment thereof. Attached Figure Description

[0017] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the bill of materials maintenance method according to an embodiment of the present invention;

[0019] Figure 2 This is an example diagram of a module library according to an embodiment of the present invention;

[0020] Figure 3 This is an example diagram of a cable library according to an embodiment of the present invention;

[0021] Figure 4 This is an example diagram illustrating the correspondence between specification-level coding and cable coding according to an embodiment of the present invention;

[0022] Figure 5 This is an example diagram of the first sub-list of items according to an embodiment of the present invention;

[0023] Figure 6 This is an example diagram of the second sub-list according to an embodiment of the present invention;

[0024] Figure 7 This is a flowchart illustrating another bill of materials maintenance method according to an embodiment of the present invention;

[0025] Figure 8 This is a flowchart illustrating another bill of materials maintenance method according to an embodiment of the present invention;

[0026] Figure 9 These are example diagrams illustrating embodiments of the present invention;

[0027] Figure 10 This is a flowchart illustrating another bill of materials maintenance method according to an embodiment of the present invention;

[0028] Figure 11 This is a structural block diagram of a bill of materials maintenance device according to an embodiment of the present invention;

[0029] Figure 12 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. Detailed Implementation

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

[0031] With product updates, the number of CPUs and LANs has increased, as has the number of supported components. Motherboard designs have become more flexible, using MCIO interfaces to connect expansion devices or hard drives via cables. This has resulted in a significantly greater number and variety of cables compared to previous products. MCIO is a flexible, robust, and cost-effective connector and cable assembly solution that helps servers and network equipment design flexibility, reduces overall space, and extends the coverage of high-data-rate signals.

[0032] The modular BOM contains a large number of configurations, and different components reuse MCIO interfaces. Under different configurations, the same interface changes different cable codes. Currently, when creating the modular BOM, the method of superimposing cable codes at the specification level is used, which manually creates a large number of specification levels containing duplicate cable materials. Different specification levels are brought out according to each configuration, resulting in a surge in the amount of modular BOM data and making it difficult to make relationship restrictions. The system has a large number of specification-level part numbers, which consumes a lot of time in management and maintenance, and changes are even more difficult. Specification levels cannot be reused for different projects.

[0033] To address the aforementioned problems, this invention provides an embodiment for maintaining a bill of materials. It should be noted that the steps shown in the flowcharts in the accompanying drawings can be executed in a computer system (computer device) including a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0034] This embodiment provides a bill of materials maintenance method, which can be used in the aforementioned terminal devices, such as mobile phones and tablet computers. Figure 1 This is a flowchart of a bill of materials maintenance method according to an embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps:

[0035] Step S101: Construct a module library. The module library contains the correspondence between the module-level codes in the bill of materials and the interface codes of each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives in different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes.

[0036] In one optional embodiment, the bill of materials is hierarchically divided from top to bottom into module level, specification level, substitute level, and physical materials.

[0037] In one optional embodiment, a backplane corresponds to multiple interfaces, and different interfaces have different interface codes. In the module library, a module-level code corresponds to one or more interface codes. When a module-level code corresponds to multiple interface codes, each interface code comes from a different backplane.

[0038] In one optional embodiment, hard drive backplanes are generally categorized into SAS / SATA backplanes, NVMe backplanes, and SAS / SATA / NVMe backplanes. SAS / SATA backplanes only support SAS / SATA hard drives, NVMe backplanes only support NVMe hard drives, and SAS / SATA / NVMe backplanes support both SAS / SATA and NVMe hard drives. Different backplanes support different types of hard drives, and the installation order of the hard drives may vary in different products and configurations.

[0039] In one alternative embodiment, when different hard drives are installed on different backplanes, the installation order of the backplane interfaces is different, and the installation order can be set according to actual needs.

[0040] For example, the constructed module library is as follows Figure 2 As shown, the backplane interfaces are mapped to module levels in the module library, and the interface order for different hard drives installed on the backplane is defined. For example, backplane XXA has interfaces J0-J8, corresponding to module levels XXX-00001-XXX-00011; similarly, backplane XXB has interfaces J9-J17, corresponding to module levels XXX-00001-XXX-00011. When only SAS / SATA hard drives are installed, the module level order is XXX-00001-XXX-00003; when only NVMe hard drives are installed, the order is XXX-00004-XXX-00009; and when SAS / SATA and NVMe hard drives are mixed, the module level order is XXX-00001-XXX-00003 and XXX-00009-XXX-00001.

[0041] Depend on Figure 2As can be seen, the relationship between module-level and backplane interfaces is defined by a human-defined interface order. The module-level code is automatically generated according to the existing coding rules based on the order when the project calls it and corresponds to the subsequent process.

[0042] When different hard drives are used in different projects, their installation positions on the backplane vary, which may result in different cable part numbers. Cables and backplane reference numbers are correlated; each backplane reference number corresponds to a specific cable. Different hard drive installation orders may correspond to different cable part numbers, and different projects may also use different cable part numbers. Therefore, the hard drive wiring order affects the cable part numbers. The hard drive wiring order is a manually defined backplane interface installation order.

[0043] Step S102: Construct a cable library. The cable library contains the correspondence between the cable codes of each cable and the interface codes of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes.

[0044] In one alternative embodiment, when the hard drive is mounted on the backplane, the interface of the backplane needs to be matched. For different backplanes, the cable needs to correspond to different interfaces. Therefore, one cable code corresponds to one or more backplane interface codes from different backplanes.

[0045] For example, the constructed cable library is as follows Figure 3 As shown, in Figure 3 In the cable library shown, for example, VXXXXXXXX001 corresponds to the XXA-J0 interface, indicating that this cable will be connected to the XXA-J0 interface when used in the project. VXXXXXXXX006 corresponds to the XXA-J14 and XXA-J17 interfaces, indicating that this cable will be connected to the XXA-J14 and XXA-J17 interfaces when used in the project. VXXXXXXXX009 also corresponds to the XXA-J14 and XXA-J17 interfaces, indicating that this cable will also be connected to the J14 and J17 interfaces when used in the project, but the configuration used is different, and the configuration used needs to be distinguished.

[0046] Step S103: Obtain the correspondence between specification-level codes and cable codes in the bill of materials.

[0047] In an optional embodiment, the related technology uses a method of superimposing cable codes at the specification level when creating a modular BOM, and manually establishes a large number of specification levels containing duplicate cable materials. Therefore, the correspondence between specification level codes and cable codes can be obtained through the pre-established modular BOM.

[0048] For example, the correspondence between specification-level codes and cable codes is as follows: Figure 4 As shown. In Figure 4In the embodiment shown, the first column represents the cable code, and the second column represents the specification level code. The specification level code corresponding to VXXXXXXXX001 is AAA-01001.

[0049] Step S104: Generate a list based on the correspondence between module-level codes and interface codes, cable codes and interface codes, and specification-level codes and cable codes. The list contains the correspondence between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code.

[0050] In this embodiment of the invention, since there is a one-to-one correspondence between cable codes and specification-level codes, but a module-level code corresponds to one or more interface codes, and different interface codes correspond to different cable codes, a module-level code corresponds to one or more specification-level codes; and since a cable code may also correspond to one or more interface codes, a specification-level code may also correspond to one or more module-level codes.

[0051] For example, the constructed list is as follows Figure 5 and Figure 6 As shown, in Figure 5 In this context, one module-level code XXX-0005 corresponds to two specification-level codes AAA-01005 and AAA-01008, and one specification-level code AAA-01004 corresponds to two module-level codes XXX-00004 and XXX-00008.

[0052] In this embodiment of the invention, the product characteristic code has no actual meaning and is only used as an intermediate node to represent the connection relationship between different information.

[0053] In this embodiment of the invention, when constructing the manifest based on the module library and cable library, the interface is used as a bridge to automatically generate the manifest. Figure 5 and Figure 6 As shown, for example, VXXXXXXXX001 corresponds to the specification level AAA-01001, and its corresponding backplane interface is J0. Therefore, its specification level AAA-01001 is placed under the module level XXX-00001. VXXXXXXXX004 corresponds to the specification level AAA-01004, and its corresponding backplane interfaces are J12 and J16. Therefore, its specification level AAA-01004 is placed under the module levels XXX-00004 and XXX-00008.

[0054] Step S105: Construct a case table based on the list and module library. The case table is used to characterize the constraint relationship between the total number of different types of hard drives and the specification level code of each cable.

[0055] In the embodiments of the invention, the instance table can characterize the restriction relationship between the total number of different types of hard drives and the specification level code of each cable. Therefore, the instance table can restrict different configurations from bringing out their corresponding cables.

[0056] Step S106: Combine the list and the case list to form the cable section in the bill of materials.

[0057] The automatic cable maintenance method provided in this invention enables the system to automatically maintain cables in a modular bill of materials (BOM) and generate a case study table with constraints. This automates the complex cable maintenance process and the creation of numerous manually written case studies, reducing the time required for modular BOM creation and maintenance, and decreasing the probability of human error. Furthermore, in this invention, the correspondence between backplane interfaces and module levels, as well as the installation order of backplane interfaces, are defined first. When a cable is needed, its specification level is retrieved from the system and applied to the subsequent BOM construction. Based on the installation order, backplane interfaces, and corresponding cable specification levels, a case study table with constraints is generated, restricting different configurations from using their corresponding cables. This eliminates the need to stack cable part numbers at the specification level; each specification level has only one cable part number, resulting in a single set of codes in the system. New projects can be maintained quickly, as the system rapidly locates and maintains cables in the modular BOM using preset rules.

[0058] This embodiment provides a bill of materials maintenance method, which can be used on the aforementioned mobile terminals, such as mobile phones and tablets. Figure 7 This is a flowchart of a bill of materials maintenance method according to an embodiment of the present invention, such as... Figure 7 As shown, the process includes the following steps:

[0059] Step S201: Construct a module library. The module library contains the correspondence between module-level codes in the bill of materials and interface codes for each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives on different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes. For details, please refer to [link to relevant documentation]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0060] Step S202: Construct a cable library. The cable library contains the correspondence between the cable codes of each cable and the interface codes of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes. For details, please refer to [link to details]. Figure 1 Step S102 of the illustrated embodiment will not be described again here.

[0061] Step S203: Obtain the correspondence between specification-level codes and cable codes in the bill of materials. For details, please refer to [link to relevant documentation]. Figure 1Step S103 of the illustrated embodiment will not be described again here.

[0062] Step S204: Generate a list based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes. The list contains the correspondence between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code.

[0063] Specifically, the list includes a first sub-list and a second sub-list, and step S204 above includes:

[0064] Step S2041: Determine multiple module-level codes corresponding to a product.

[0065] In one alternative embodiment, one product may correspond to multiple hardware devices; therefore, one product may correspond to multiple module-level codes. For example, as shown... Figure 5 As shown, the module-level code corresponding to a product is XXX-00001-XXX-00009.

[0066] Step S2042: Establish a correspondence between the module-level code and the product feature code of a product, with one module-level code corresponding to one product feature code.

[0067] For example, such as Figure 5 As shown, the product characteristic code corresponding to module-level code XXX-00001 is "S_Product Name_C1", and the product characteristic code corresponding to module-level code XXX-00002 is "S_Product Name_C2", etc.

[0068] Step S2043: Determine the correspondence between module-level codes and specification-level codes based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes.

[0069] In this embodiment of the invention, interface coding is used as a bridge to determine the correspondence between module-level coding and specification-level coding.

[0070] Step S2044: Based on the correspondence between module-level codes and product characteristic codes, and the correspondence between module-level codes and specification-level codes, a first sub-list is established. The first sub-list contains the correspondences between module-level codes, specification-level codes, and product characteristic codes. For example, the constructed first sub-list is as follows: Figure 5 As shown.

[0071] Step S2045: Establish a second sublist based on the first sublist. The second sublist determines the specification level code corresponding to each product characteristic code. One product characteristic code corresponds to one or more specification level codes.

[0072] Since a module-level code corresponds to one or more specification-level codes, and a module-level code corresponds to one product feature code, a product feature code corresponds to one or more specification-level codes.

[0073] For example, the second sub-list is created as follows Figure 6 As shown, in Figure 6 In the illustrated embodiment, “S_product name_C1_QTY” represents the number of specification-level codes corresponding to the product characteristic code “S_product name_C1”.

[0074] Step S205: Construct a case table based on the manifest and module library. The case table represents the constraint relationship between the total number of hard drives of different types and the specification-level coding of each cable. See details... Figure 1 Step S105 of the illustrated embodiment will not be described again here.

[0075] Step S206: Combine the list and the example table to form the cable section of the bill of materials. For details, please refer to [link to relevant documentation]. Figure 1 Step S106 of the illustrated embodiment will not be described again here.

[0076] This embodiment provides a bill of materials maintenance method, which can be used on the aforementioned mobile terminals, such as mobile phones and tablets. Figure 8 This is a flowchart of a bill of materials maintenance method according to an embodiment of the present invention, such as... Figure 8 As shown, the process includes the following steps:

[0077] Step S301: Construct a module library. The module library contains the correspondence between module-level codes in the bill of materials and interface codes for each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives on different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes. For details, please refer to [link to relevant documentation]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0078] Step S302: Construct a cable library. The cable library contains the correspondence between the cable codes of each cable and the interface codes of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes. For details, please refer to [link to relevant documentation]. Figure 1 Step S102 of the illustrated embodiment will not be described again here.

[0079] Step S303: Obtain the correspondence between specification-level codes and cable codes in the bill of materials. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again here.

[0080] Step S304: Generate a list based on the correspondence between module-level codes and interface codes, cable codes and interface codes, and specification-level codes and cable codes. The list includes the correspondence between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code. For details, please refer to [link to details]. Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0081] Step S305: Construct a case table based on the manifest and module library. The case table is used to characterize the constraint relationship between the total number of different types of hard drives and the specification level code of each cable.

[0082] Specifically, step S305 includes:

[0083] Step S3051: Determine multiple configuration information, which includes product feature codes and the number of hard drives to be installed. The range of the number of hard drives to be installed is limited by the installation order of each backplane interface in the module library.

[0084] In an alternative embodiment, the type of drive (front / rear), SAS / SATA, or U2 drive can be determined by the cable module level description, where U2 drive refers to NVME drive.

[0085] Step S3052: Determine the specification-level code and module-level code corresponding to the product characteristic code in the configuration information based on the list.

[0086] Step S3053: Determine the hard disk type corresponding to the module-level code and the installation order of the hard disk interface based on the module-level code and module library.

[0087] Step S3054: Generate a case table based on the number of hard drives installed, the interface installation order, and the specification-level code corresponding to the product characteristic code in the configuration information. The case table is used to restrict the correspondence between different configuration information and cables.

[0088] In one specific embodiment, when installing different numbers of SAS / SATA disks and NVMe disks, corresponding to the product characteristic codes "S_Product Name_C4" and "S_Product Name_C5", the resulting example table is as follows. Figure 9 As shown.

[0089] exist Figure 9The table automatically generates the total number of front hard drives (S_product name_FHDD_QTY), the total number of front U2 hard drives (S_product name_FU2_QTY), and cables. The range of these numbers is limited by the installation order. In the table, X represents the number of hard drives in the modular BOM. [1-X] refers to the number of hard drives from 1 to X, and [(X-1)-X] refers to the number of hard drives from X-1 to X.

[0090] exist Figure 9 In the context of a system where the total number of front-side hard drives ranges from 1 to X, and the total number of front-side U2 hard drives is 0, then... Figure 5 It can be seen that the module-level code corresponding to "S_Product Name_C4" is XXX-00004, which is... Figure 2 It is known that the cable corresponding to XXX-00004 is only required when installing the NVMe disk. Therefore, under this configuration, the cable corresponding to "S_Product Name_C4" is not needed. Figure 9 In the text, the value corresponding to "S_Product Name_C4" is "NONE".

[0091] When the total number of front-panel hard drives is [number] and the total number of front-panel U2 hard drives is 1-2, [the following is determined by] Figure 5 It can be seen that the module-level code corresponding to "S_Product Name_C4" is XXX-00004, which is... Figure 2 It is known that when installing the NVMe drive, the interface installation sequence corresponding to XXX-00004 is 1. In this case, the cable corresponding to XXX-00004 needs to be brought out. The specification level code of the cable corresponding to XXX-00004 is AAA-01004. Therefore, under this configuration, the cable corresponding to "S_Product Name_C4" needs to be used. Figure 9 In the text, the value corresponding to "S_Product Name_C4" is "AAA-01004".

[0092] When the total number of front-panel hard drives is 3-X, and the total number of front-panel U2 hard drives is 3-X, then... Figure 5 It can be seen that the module-level code corresponding to "S_Product Name_C4" is XXX-00004, which is... Figure 2 It can be seen that when installing NVMe drives, the interface installation order corresponding to XXX-00004 is 1. Since the installation order of the 3rd to Xth NVMe drives is not 1, the cable corresponding to "S_Product Name_C4" does not need to be used in this configuration. Figure 9 In the text, the value corresponding to "S_Product Name_C4" is "NONE".

[0093] Following this logic, we can obtain the following: Figure 9 The example table shown is obtained through Figure 9 The example table shown can display the corresponding cable specification level code under different configurations.

[0094] Step S306: Combine the bill of materials and the example table to form the cable section of the bill of materials. For details, please refer to [link to relevant documentation]. Figure 1 Step S106 of the illustrated embodiment will not be described again here.

[0095] This embodiment provides a bill of materials maintenance method, which can be used on the aforementioned mobile terminals, such as mobile phones and tablets. Figure 10 This is a flowchart of a bill of materials maintenance method according to an embodiment of the present invention, such as... Figure 10 As shown, the process includes the following steps:

[0096] Step S401: Construct a module library. The module library contains the correspondence between module-level codes in the bill of materials and interface codes for each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives on different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes. For details, please refer to [link to relevant documentation]. Figure 1 Step S101 of the illustrated embodiment will not be described again here.

[0097] Step S402: Construct a cable library. The cable library contains the correspondence between the cable codes of each cable and the interface codes of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes. For details, please refer to [link to relevant documentation]. Figure 1 Step S102 of the illustrated embodiment will not be described again here.

[0098] Step S403: Obtain the correspondence between specification-level codes and cable codes in the bill of materials. For details, please refer to [link to relevant documentation]. Figure 1 Step S103 of the illustrated embodiment will not be described again here.

[0099] Step S404: Generate a list based on the correspondence between module-level codes and interface codes, cable codes and interface codes, and specification-level codes and cable codes. The list includes the correspondence between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code. For details, please refer to [link to details]. Figure 1 Step S104 of the illustrated embodiment will not be described again here.

[0100] Step S405: Construct a case table based on the manifest and module library. The case table characterizes the constraint relationship between the total number of hard drives of different types and the specification-level coding of each cable. See details... Figure 1 Step S105 of the illustrated embodiment will not be described again here.

[0101] Step S406: Combine the bill of materials and the example table to form the cable section of the bill of materials. For details, please refer to [link to relevant documentation]. Figure 1 Step S106 of the illustrated embodiment will not be described again here.

[0102] Step S407: Receive updated configuration information.

[0103] Step S408: Select the target cable from the cable library according to the updated configuration information, and determine the target interface code corresponding to the target cable.

[0104] If the cable library does not contain all cables, proceed to step S409 to maintain the cable library.

[0105] If the cable library contains all cables, perform the following steps.

[0106] If the information in the module library and the cable library is inconsistent, proceed to step S410 to maintain the module library.

[0107] If the information in the module library and the cable library is consistent, perform the following steps.

[0108] Step S411: Determine the target module-level code corresponding to the target interface code based on the module library. For details, please refer to the description in the above embodiments, which will not be repeated here.

[0109] Step S412: Determine the target specification level code corresponding to the target cable based on the correspondence between specification level codes and cable codes in the bill of materials. For details, please refer to the description in the above embodiments, which will not be repeated here.

[0110] If the target interface code is duplicated, proceed to step S413 to maintain the distinguishing conditions.

[0111] If the target interface code is unique, proceed with the following steps.

[0112] Step S414: Update the list according to the correspondence between the target module-level code, the target specification-level code, and the target product characteristic code, ensuring that the target product characteristic code corresponds to the updated configuration information. For details, please refer to the description in the above embodiments, which will not be repeated here.

[0113] Step S415: Determine the hard disk type corresponding to the target module-level code and the corresponding interface installation order of the hard disk based on the target module-level code and module library. For details, please refer to the description in the above embodiments, which will not be repeated here.

[0114] Step S416: Update the case table restrictions based on the installation quantity of various hard drives, interface installation order, and target specification-level code corresponding to the target product characteristic code in the updated configuration information. For details, please refer to the description in the above embodiments, which will not be repeated here.

[0115] This embodiment also provides a bill of materials maintenance device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs 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.

[0116] This embodiment provides a bill of materials maintenance device, such as Figure 11 As shown, it includes:

[0117] Module library construction module 111 is used to build a module library. The module library contains the correspondence between the module-level codes in the bill of materials and the interface codes of each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives in different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes.

[0118] The cable library construction module 112 is used to construct the cable library. The cable library contains the correspondence between the cable code of each cable and the interface code of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes.

[0119] Specification-level code acquisition module 113 is used to obtain the correspondence between specification-level codes and cable codes in the bill of materials;

[0120] The manifest generation module 114 is used to generate a manifest based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes. The manifest contains the correspondence between module-level codes, specification-level codes, and product characteristic codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product characteristic code.

[0121] The case table generation module 115 is used to build a case table based on the list and module library. The case table is used to characterize the constraint relationship between the total number of different types of hard drives and the specification level code of each cable.

[0122] The bill of materials maintenance module 116 is used to combine the bill of materials and the case table to form the cable section in the bill of materials.

[0123] In an optional embodiment, the list includes a first sub-list and a second sub-list, and the list generation module 114 specifically includes:

[0124] Module-level coding determination unit, used to determine multiple module-level codes corresponding to a product;

[0125] The first correspondence establishment unit is used to establish a correspondence between a product's module-level code and product feature code, with one module-level code corresponding to one product feature code.

[0126] The second correspondence establishment unit is used to determine the correspondence between module-level codes and specification-level codes based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes.

[0127] The first sublist creation unit is used to create a first sublist based on the correspondence between module-level codes and product characteristic codes, and the correspondence between module-level codes and specification-level codes. The first sublist contains the correspondence between module-level codes, specification-level codes, and product characteristic codes.

[0128] The second sublist creation unit is used to create a second sublist based on the first sublist. The second sublist determines the specification level code corresponding to each product characteristic code. One product characteristic code corresponds to one or more specification level codes.

[0129] In an optional embodiment, the case table generation module 115 specifically includes:

[0130] The configuration information determination unit is used to determine multiple configuration information, which includes product feature codes and the number of hard drives to be installed. The range of the number of hard drives to be installed is determined by the installation order of each backplane interface in the module library.

[0131] The first information matching unit is used to determine the specification-level code and module-level code corresponding to the product characteristic code in the configuration information based on the list;

[0132] The second information matching unit is used to determine the hard disk type corresponding to the module-level code and the interface installation order of the hard disk based on the module-level code and the module library.

[0133] The case table creation unit is used to generate a case table based on the number of hard drives installed, the interface installation order, and the specification-level code corresponding to the product characteristic code in the configuration information. The case table is used to restrict the correspondence between different configuration information and cables.

[0134] In an optional embodiment, the bill of materials maintenance apparatus further includes:

[0135] The configuration update module is used to receive updated configuration information;

[0136] The target interface code determination module is used to select a target cable from the cable library based on the updated configuration information and determine the target interface code corresponding to the target cable.

[0137] The target module-level coding determination module is used to determine the target module-level coding corresponding to the target interface coding based on the module library if the cable library contains all cables and the information in the module library is consistent with that in the cable library.

[0138] The target specification level code determination module is used to determine the target specification level code corresponding to the target cable based on the correspondence between the specification level codes and cable codes in the bill of materials.

[0139] If the target interface code does not have duplicates.

[0140] The manifest update module updates the manifest based on the correspondence between the target module-level code, the target specification-level code, and the target product feature code, provided that the target interface code does not have duplicates. The target product feature code corresponds to the updated configuration information.

[0141] The information matching module is used to determine the hard disk type corresponding to the target module-level code and the interface installation order of the hard disk based on the target module-level code and module library;

[0142] The case table update module is used to update the case table restriction relationships based on the number of hard drives installed, the interface installation order, and the target specification level code corresponding to the target product feature code in the updated configuration information.

[0143] The cable library maintenance module is used to maintain the cable library if it does not contain all cables.

[0144] The module library maintenance module is used to maintain the module library if the information in the module library is inconsistent with that in the cable library.

[0145] The distinction condition maintenance module is used to maintain the distinction conditions if the target interface code is duplicated.

[0146] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0147] In this embodiment, the XXX device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0148] This invention also provides a computer device having the above-described features. Figure 11 The bill of materials maintenance device shown.

[0149] Please see Figure 12 , Figure 12 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of the present invention, such as... Figure 12 As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 12 Take a processor 10 as an example.

[0150] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0151] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0152] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0153] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0154] The computer device also includes an input device 30 and an output device 40. The processor 10, memory 20, input device 30, and output device 40 can be connected via a bus or other means. Figure 12 Taking the example of a connection between China and Israel via a bus.

[0155] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the computer device, such as a touchscreen, keypad, mouse, trackpad, touchpad, joystick, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touchscreen.

[0156] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0157] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for maintaining a bill of materials, characterized in that, The method includes: A module library is constructed, which contains the correspondence between the module-level codes in the bill of materials and the interface codes of each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives in different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes. Construct a cable library containing the correspondence between the cable codes of each cable and the interface codes of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes. Obtain the correspondence between specification-level codes and cable codes in the bill of materials; A list is generated based on the correspondence between module-level codes and interface codes, cable codes and interface codes, and specification-level codes and cable codes. The list contains the correspondence between module-level codes, specification-level codes, and product feature codes. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product feature code. Based on the aforementioned list and module library, a case table is constructed, which is used to characterize the constraint relationship between the total number of different types of hard drives and the specification-level code of each cable; The cable portion of the bill of materials is formed by combining the list and the case table.

2. The method according to claim 1, characterized in that, The list includes a first sub-list and a second sub-list. The steps for generating the list based on the correspondence between module-level codes and interface codes, the correspondence between cable codes and interface codes, and the correspondence between specification-level codes and cable codes include: Determine the multiple module-level codes corresponding to a product; Establish a correspondence between product module-level codes and product feature codes, with one module-level code corresponding to one product feature code; Based on the correspondence between the module-level code and the interface code, the correspondence between the cable code and the interface code, and the correspondence between the specification-level code and the cable code, the correspondence between the module-level code and the specification-level code is determined. Based on the correspondence between the module-level code and the product characteristic code, and the correspondence between the module-level code and the specification-level code, a first sublist is established, which contains the correspondence between the module-level code, the specification-level code, and the product characteristic code. A second sublist is established based on the first sublist. The second sublist determines the specification-level code corresponding to each product characteristic code. One product characteristic code corresponds to one or more specification-level codes.

3. The method according to claim 1 or 2, characterized in that, Construct a case table based on the aforementioned list and module library, including: Multiple configuration information is determined, including product feature codes and the number of hard drives to be installed. The range of the number of hard drives to be installed is limited by the installation order of each backplane interface in the module library. Based on the aforementioned list, determine the specification-level code and module-level code corresponding to the product characteristic codes in the configuration information; The hard disk type corresponding to the module-level code and the interface installation order of the hard disk are determined based on the module-level code and the module library. The case table is generated based on the number of hard drives installed in the configuration information, the installation order of the interfaces, and the specification-level code corresponding to the product feature code. The case table is used to restrict the correspondence between different configuration information and cables.

4. The method according to claim 1, characterized in that, The method further includes: Receive updated configuration information; Select a target cable from the cable library based on the updated configuration information, and determine the target interface code corresponding to the target cable; If the cable library contains all cables, and the information in the module library is consistent with that in the cable library, Determine the target module-level code corresponding to the target interface code based on the module library; Based on the correspondence between specification-level codes and cable codes in the bill of materials, determine the target specification-level code corresponding to the target cable; If the target interface code does not have duplicates. The list is updated according to the correspondence between the target module-level code, the target specification-level code, and the target product feature code, wherein the target product feature code corresponds to the updated configuration information; The hard disk type corresponding to the target module-level code and the interface installation order of the hard disk are determined based on the target module-level code and the module library. The instance table restriction relationship is updated based on the number of hard drives installed for each type, the interface installation order, and the target specification level code corresponding to the target product feature code in the updated configuration information.

5. The method according to claim 4, characterized in that, If the cable library does not contain all cables, maintain the cable library.

6. The method according to claim 4, characterized in that, If the information in the module library is inconsistent with that in the cable library, maintain the module library.

7. The method according to claim 4, characterized in that, If the target interface code is duplicated, maintain the distinguishing conditions.

8. A bill of materials maintenance device, characterized in that, The device includes: The module library construction module is used to build the module library. The module library contains the correspondence between the module-level codes in the bill of materials and the interface codes of each backplane interface, as well as the installation order of each backplane interface when installing various types of hard drives in different backplanes. One backplane corresponds to multiple backplane interfaces, and one module-level code corresponds to one or more backplane interface codes from different backplanes. The cable library construction module is used to construct a cable library, which contains the correspondence between the cable codes of each cable and the interface codes of each backplane interface. One cable code corresponds to one or more backplane interface codes from different backplanes. The specification-level code acquisition module is used to obtain the correspondence between specification-level codes and cable codes in the bill of materials; The manifest generation module is used to generate a manifest based on the correspondence between the module-level code and the interface code, the correspondence between the cable code and the interface code, and the correspondence between the specification-level code and the cable code. The manifest contains the correspondence between the module-level code, the specification-level code, and the product feature code. One module-level code corresponds to one or more specification-level codes, and one module-level code corresponds to one product feature code. The case table generation module is used to construct a case table based on the list and the module library. The case table is used to characterize the constraint relationship between the total number of different types of hard drives and the specification-level code of each cable. The bill of materials maintenance module is used to combine the bill of materials and the case table to form the cable portion of the bill of materials.

9. A computer device, characterized in that, include: A memory and a processor are communicatively connected, the memory storing computer instructions, and the processor performing bill of materials maintenance as described in any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the bill of materials maintenance as described in any one of claims 1 to 7.

Images