Product blood relationship generation method and device, electronic equipment and program product

Abstract

The invention discloses a product blood relationship generation method and device. The product blood relationship generation method comprises the steps of generating a multi-level product data structure representing a product blood relationship of a multi-level product and defining a product dependence rule of the multi-level product; in response to the product creation request, creating a product and storing product information of the product, the product information including product attribute information and direct dependence product information; constructing a blood relationship node corresponding to the product according to the product attribute information of the product; constructing directional connection of blood relationship nodes according to direct dependence product information of a product; and storing the blood relationship node and the directive connection in a product blood relationship library. The invention further discloses a product blood relationship query method and device. Related electronic devices and program products are disclosed. According to the scheme disclosed by the invention, the product network which comprises multiple levels and multiple service lines and has a complex dependency relationship can be effectively managed and expressed.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method and device for generating product blood relationship, a method and device for querying product blood relationship, and also to related electronic equipment and program products. Background Art

[0002] With the rapid increase in the variety, quantity and assembly (combination) complexity of enterprise products, the dependencies between products are becoming increasingly complex. At present, enterprises mainly rely on product management systems to store and maintain product information. These systems record product names, versions, categories and status, and require business personnel (such as product managers) to update the product information they are responsible for in real time.

[0003] However, existing product management systems have limitations when dealing with complex, multi-level product dependencies. These systems can usually only record and display direct dependencies and cannot effectively represent and manage product networks with multi-level, complex dependencies. Especially in complex product ecosystems involving multiple business lines, it is difficult for users to fully and intuitively understand the complete dependencies between products. This complexity also makes it increasingly difficult and time-consuming to rely on manual real-time maintenance of large amounts of product information.

[0004] The content of this background technology description is only for facilitating understanding of the relevant technology in this field and is not regarded as an admission of the prior art. Summary of the invention

[0005] Accordingly, the present disclosure provides a product lineage relationship generation solution, which at least partially solves the above technical problems. The present disclosure also provides a product lineage relationship query solution, which can further solve the above-mentioned technical problems or technical problems existing in the prior art.

[0006] In a first aspect, a method for generating a product kinship relationship is provided, which may include:

[0007] Generate a multi-level product data structure representing the product lineage relationship of the multi-level product, define the product dependency rules of the multi-level product, the product dependency rules include: in the multi-level product data structure, define that the multi-level product includes a base product and at least one upper-level product, define that the base product directly depends on at least one base product data source, and define that the at least one upper-level product directly or indirectly depends on the base product;

[0008] In response to a product creation request, create a product and store product information of the product, wherein the product information includes product attribute information and directly dependent product information;

[0009] According to the product attribute information of the product, construct a blood relationship node corresponding to the product;

[0010] Constructing a directional connection of the blood relationship nodes according to the directly dependent product information of the product;

[0011] The blood relationship nodes and the directional connections are stored in a product blood relationship library.

[0012] In a second aspect, a product blood relationship query method is provided, which may include:

[0013] In response to a product blood relationship query request, searching a blood relationship node dataset and a directional connection dataset related to a target product in a product blood relationship library, wherein the product blood relationship library is obtained by implementing the product blood relationship generation method described in the first aspect;

[0014] The product blood relationship of the target product is determined according to the blood relationship node data set and the directional connection data set.

[0015] In a third aspect, a device for generating a product blood relationship is provided, which may include:

[0016] A generating unit is configured to generate a multi-level product data structure representing a product lineage relationship of a multi-level product and define product dependency rules of the multi-level product, including: defining that the multi-level product includes a base product and at least one upper-level product, defining that the base product directly depends on at least one base product data source, and defining that the at least one upper-level product directly or indirectly depends on the base product;

[0017] a creation unit, configured to create a product and store product information of the product in response to a product creation request, wherein the product information includes product attribute information and directly dependent product information;

[0018] A node construction unit, configured to construct a blood relationship node corresponding to the product according to the product attribute information of the product;

[0019] A connection construction unit, configured to construct a directional connection of the blood relationship node according to the direct dependent product information of the product;

[0020] A product blood relationship library is configured to store the blood relationship nodes and the directional connections.

[0021] In a fourth aspect, a product blood relationship query device is provided, which may include:

[0022] a retrieval unit configured to, in response to a product kinship query request, retrieve a kinship node data set and a directional connection data set related to a target product in a product kinship library, wherein the product kinship library is the product kinship library of the product kinship generation device of the third aspect;

[0023] The determination unit is configured to determine the product blood relationship of the target product based on the blood relationship node data set and the directional connection data set.

[0024] In a fifth aspect, an electronic device is provided, comprising: a processor and a memory storing a computer program, wherein the processor is configured to implement the method as described in the first aspect or the second aspect when the computer program is executed.

[0025] In a sixth aspect, a program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the method as described in the first aspect or the second aspect is implemented.

[0026] The product lineage generation method proposed in the embodiment of the present disclosure solves the problem that existing product management systems are unable to effectively represent and manage complex multi-level product dependencies by generating a product lineage data structure that represents multi-level products and defines product dependency rules, creating products and storing product information of the products, constructing lineage nodes corresponding to the products, constructing directional connections of the lineage nodes, and storing the lineage nodes and the directional connections in a product lineage library. It can store product lineage in a data structure that comprehensively and intuitively represents a complex product ecosystem containing multiple business lines, thereby reducing the manual burden of manually maintaining a large amount of product information.

[0027] The product blood relationship query method proposed in the embodiment of the present disclosure solves the problem that it is difficult for users to fully and intuitively understand the complete dependency relationship between products by retrieving relevant data in the product blood relationship library and determining the blood relationship of the target product, and realizes the rapid and accurate acquisition and display of blood relationships in complex product networks.

[0028] Other optional features and technical effects of the embodiments of the present disclosure are partially described below, and partially can be understood by reading this document. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The elements shown are not limited by the proportions shown in the accompanying drawings. The same or similar reference numerals in the accompanying drawings represent the same or similar elements, wherein:

[0030] Figure 1 A first flow chart of a method for generating a product blood relationship according to an embodiment of the present disclosure is shown;

[0031] Figure 2 A second flow chart of the method for generating product blood relationship according to an embodiment of the present disclosure is shown;

[0032] Figure 3A third flow chart of the method for generating product blood relationship according to an embodiment of the present disclosure is shown;

[0033] Figure 4 A fourth flow chart of the method for generating product blood relationship according to an embodiment of the present disclosure is shown;

[0034] Figure 5 A fifth flow chart of a method for generating a product blood relationship according to an embodiment of the present disclosure is shown;

[0035] Figure 6 Schematically shows the multi-level products and their dependency relationships defined by the product lineage relationship generation method according to the embodiment of the present disclosure;

[0036] Figure 7 A first flow chart of a product blood relationship query method according to an embodiment of the present disclosure is shown;

[0037] Figure 8 A second flow chart of the product blood relationship query method according to an embodiment of the present disclosure is shown;

[0038] Fig. 9 A third flow chart of the product blood relationship query method according to an embodiment of the present disclosure is shown;

[0039] Fig.10 A fourth flow chart of the product blood relationship query method according to an embodiment of the present disclosure is shown;

[0040] Fig.11 A fifth flow chart of the product blood relationship query method according to an embodiment of the present disclosure is shown;

[0041] Fig.12 A sixth flow chart of the product blood relationship query method according to an embodiment of the present disclosure is shown;

[0042] Fig.13 A seventh flow chart of the product blood relationship query method according to an embodiment of the present disclosure is shown;

[0043] Fig.14 A schematic diagram showing a product lineage relationship visualization interface provided by the product lineage relationship query method according to an embodiment of the present disclosure is shown;

[0044] Fig.15 A module diagram showing a device for generating a product blood relationship according to an embodiment of the present disclosure

[0045] Fig.16 A module diagram of a product blood relationship query device according to an embodiment of the present disclosure is shown;

[0046] Fig.17 A structural diagram of an electronic device for implementing the method of an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with specific implementation methods and drawings. Here, the illustrative implementation methods and descriptions of the present disclosure are used to explain the present disclosure, but are not intended to limit the present disclosure.

[0048] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0049] The information, data and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions.

[0050] With the rapid increase in the variety, quantity and assembly (combination) complexity of enterprise products, the dependencies between products are becoming increasingly complex. At present, enterprises mainly rely on product management systems to store and maintain product information. These systems record product names, versions, categories and status, and require business personnel (such as product managers) to update the product information they are responsible for in real time.

[0051] As mentioned above, existing product management systems have limitations when dealing with complex multi-level product dependencies. These systems can usually only record and display direct dependencies and cannot effectively represent and manage product networks containing multi-level and complex dependencies.

[0052] This limitation brings a series of problems. Especially in a complex product ecosystem involving multiple business lines, it is difficult for people to fully and intuitively understand the complete dependencies between products. Maintainers are forced to rely on internal static documents to maintain information, which not only consumes a lot of manpower, but also faces the risk of delayed and disconnected information updates. When collaborating across departments, the information island effect causes communication costs to soar. In the joint development of multiple business line products, R&D personnel are unable to grasp the progress of dependent products in real time, which seriously slows down the overall R&D efficiency.

[0053] In this regard, the disclosed embodiment proposes a product lineage generation solution, which realizes the efficient storage, update and management of product lineage, and solves the problem that the existing product management system cannot effectively represent and manage complex multi-level product dependencies. It can comprehensively and intuitively present the complex product ecosystem across business lines, greatly reducing the burden of manual maintenance.

[0054] Furthermore, the disclosed embodiment proposes a product blood relationship query solution, which realizes the rapid and accurate acquisition and clear display of blood relationships in complex product networks.

[0055] In addition, the present disclosure also describes further optional, preferred or specific features or embodiments, which can further solve the problems pointed out above or other technical problems in the art.

[0056] As an illustration, the "blood relationship" described in this article is not the blood relationship commonly understood in the field of biology or human science. The "blood relationship" described in this article is applicable to the field of computer technology and has the normal meaning understood by technicians in this field (the field of computer technology). As an exemplary explanation, the "blood relationship" described in this article can be used to describe the interrelated relationships between products, such as nested use, mutual dependence, or derivative iteration.

[0057] Figure 1 FIG. 1 is a flow chart of a method for generating a product kinship relationship according to an embodiment of the present disclosure. Figure 1 As shown, the method for generating product kinship may include:

[0058] S110: Generate a multi-level product data structure that represents the product lineage relationship of the multi-level products, and define product dependency rules of the multi-level products.

[0059] In the embodiments of the present disclosure, the product has a broad meaning in the field (the field of computer technology), including various objects that can be digitally represented, stored, processed and managed, such as but not limited to various applications, cloud service products, data (sources), service components, algorithm models, middleware, configuration files, virtual commodities, their combination products, or at least one of their modules / components / units that can be abstractly defined as products. It will be understood that the product described in the embodiments of the present disclosure is a digital product, and does not include a physical product. However, the product of the embodiments of the present disclosure may include a digital representation of a physical product or a virtualized object corresponding to a physical product as needed, such as data record forms (including product attributes or parameters), simulation models, digital twins, etc. of various physical products (such as systems, devices, modules, components, parts). In addition, the product implemented by the present disclosure may include any suitable combination of the above.

[0060] The product lineage relationship generation method of the embodiment of the present disclosure first generates a multi-level product data structure that represents the product lineage relationship of the multi-level products, and defines the product dependency rules of the multi-level products. Figure 6The multi-level products in the multi-level product data structure may be defined to include a basic product and at least one, preferably multiple (e.g., 4) layers of upper-level products. The basic product data source is located at the bottom layer and is the most basic unit of the product. It does not depend on other products, but can only be depended on by the basic product or the upper-level product.

[0061] In this embodiment, if Figure 6 As shown, in the multi-level product data structure, the base product is defined as directly dependent on at least one base product data source. This dependency is a necessary condition for forming the base product, that is, a necessary dependency. Figure 6 As shown, in the multi-level product data structure, at least one layer, preferably multiple layers (such as 4 layers) of upper-level products are defined as directly or indirectly dependent on the basic product, such as Figure 6 The assembled products in the data structure directly depend on the base product, and the model products and integrated model products indirectly depend on the base product. In some embodiments, the multi-level products in the multi-level product data structure may be defined to include or exclude the base product data source. When the base product data source is an external data source, the latter situation may be applicable.

[0062] As further described below, the definition of a multi-level product can be as described below as one of the product attributes of a specific product, such as as a product category.

[0063] In this article, the term "dependency" refers to the dependency relationship generated by the nested use of lower-level products by upper-level products, and the term "dependent on" indicates the opposite relationship, that is, the dependency relationship generated by the nested use of lower-level products by upper-level products. In this article, the term "direct dependency" refers to the dependency relationship generated by the direct nesting between products. For example, if product A directly nests and uses product B, then it is said that product A directly depends on product B. In this article, the term "indirect dependency" refers to the dependency relationship generated indirectly by the upper-level product and the lower-level product through the nested use of a middle-level product, and the middle-level product directly nests and uses the lower-level product. For example, if product A nests and uses product B, and product B directly depends on product C, then it is said that product A indirectly depends on product C. In this article, "upstream" and "downstream" are determined based on the dependency relationship. The upper-level product that directly or indirectly depends on the lower-level product is located upstream of the lower-level product, and conversely, the lower-level product is located downstream of the upper product.

[0064] like Figure 6 As shown, at least one layer, preferably multiple layers (such as 4 layers) of the upper product may include an assembled product (AssembleProduct). Figure 6 As shown in , you can define that an assembly product directly depends on at least one base product. Figure 6As further shown, an assembled product may be defined to optionally directly depend on at least one base product data source.

[0065] like Figure 6 As shown, at least one layer, preferably multiple layers (such as 4 layers) of the upper product may also include a model product (ModelProduct). Figure 6 As shown in FIG. 1 , a model product can be defined to directly depend on at least one assembly product and / or at least one base product. In other words, Figure 6 In the illustrated embodiment, the model product at least alternatively directly depends on at least one assembled product and at least one base product.

[0066] like Figure 6 As shown, at least one layer, preferably multiple layers (such as 4 layers) of the upper layer product may also include an integrated model product. Figure 6 As shown in , it is possible to define that an integrated model product directly depends on at least one model product. Figure 6 It is further shown that an integrated model product may be defined to optionally directly depend on at least one assembly product and / or at least one base product.

[0067] exist Figure 6 In the embodiment shown, the integrated model product is the top-level product, which in turn can be the product with the highest degree of complexity. Through multi-level dependencies, the integrated model product of the embodiment of the present disclosure can achieve more complex and powerful functions and generate many complex indirect dependencies. However, it can be imagined that the multi-level product of the embodiment of the present disclosure may not be limited to Figure 6 The four layers shown may be more or less layers. In addition, the naming and / or dependency of the above multi-level products may not be limited to Figure 6 Further, although in Figure 6In the described embodiments, each layer of products has only one product category, but it is conceivable that more than one product category may be provided for a given level. For example, in some embodiments, two groups of multi-level product categories may be provided, including: a first group of multi-level products (categories), including a first basic product (category), a first assembled product (category), and a first model product (category); a second group of multi-level products (categories), including a second basic product (category), a second assembled product (category), a second model product (category), a second model product (category), and a second integrated model product (category). At this point, for example, the first layer has two categories of products, the first basic product (category) and the second basic product (category). Embodiments in which at least one layer of products has one or more product categories may also combine multiple features to obtain new embodiments. Optionally, for example, the above-mentioned groups of multi-level products only generate dependencies within the group, and different groups of multi-level products may have different levels, for example, the first group has three layers of products and the second group has four layers of products.

[0068] The multi-level product structure of the disclosed embodiment is adaptable to various product structures from simple to complex; through clear dependency relationships, the system achieves a high degree of traceability, which is conducive to problem location and quality control, and promotes modular design. At the same time, the structure has good scalability and can adapt to future demand changes by adding new product categories or modifying dependency rules. In particular, when it comes to the embodiment of application products, the code reuse rate and system maintenance efficiency are improved; moreover, it is particularly conducive to the implementation of fine-grained version control, simplifying application upgrade and rollback operations.

[0069] S120: In response to the product creation request, create a product and store product information of the product.

[0070] In the product blood relationship generation method of the embodiment of the present disclosure, a product can be created and product information of the product can be stored in response to a product creation request. The product information may include product attribute information and directly dependent product information.

[0071] In some embodiments, for example, a user, such as a product manager of a business line, can create a product through a product entry interface, and enter and select product attribute information (including selecting a product category).

[0072] In some embodiments, product attribute information may include product name, product version, product Chinese name, product category, billing rules, pricing method, scope of application and product status, etc.

[0073] In some specific embodiments, more or less product attribute information may be included. In one specific example, the product attribute information may include a product version, which is particularly useful for application products with strict version control; in another specific example, the product attribute information may not include a product version, which is suitable for various data products that are updated in real time.

[0074] In other embodiments, the above product attribute information may include more specific types or include sub-attribute information, which falls within the scope of the present disclosure. For example, the above application scope may include a promotion scope, which is used in certain marketing products; in another example, the above application scope may include an authority scope, which is applicable to certain products with sensitive data or information.

[0075] In some embodiments, the user may also enter the directly dependent product information of the created product, that is, the product that the created product directly depends on. The directly dependent product information is subject to the dependency relationship of the multi-level products defined above. Table 1 shows an exemplary product information list.

[0076] Table 1 Product information list

[0077]

[0078] Table 2 shows an example of the directly dependent product set data included in the above directly dependent product information, namely, the "directly dependent product (depend_product)" field value.

[0079] Table 2 Example of directly dependent product collection data

[0080]

[0081] In some embodiments, the above step S120 may further include an optional step S120' (not shown in the figure): verifying the directly dependent product information. In these embodiments, before storing the product information, data verification may be performed to ensure that the created product information complies with the predefined product dependency rules. More specifically, the above verification is to verify whether the directly dependent information complies with the dependency relationship of the multi-level products defined above.

[0082] like Figure 2 As shown, the verification step S120' may include: S121: determining the product category of the product according to the basic product information of the product.

[0083] S122: Determine the directly dependent products of the product according to the directly dependent product information of the product.

[0084] S123: Query the stored product information to determine the product category of each directly dependent product.

[0085] S124: According to the product dependency rule, the product category of the product is verified with the product categories of each directly dependent product.

[0086] S125: When the verification is passed, the product information of the product is stored.

[0087] This verification process ensures the legitimacy of the product dependency definition for the generated multi-level product structure. Taking Table 2 as an example, optionally, the basic product data source, as the basic unit constituting the product, has no direct or indirect dependency, so its directly dependent product field can be empty. According to the above definition, the basic product directly depends on one or more basic product data sources, so it is necessary to judge that the direct dependent product information (such as the direct dependent product field value) of the product with the product category of "basic product" contains a non-empty set of basic product data sources (such as represented by basicSourceProduct). According to the above definition, the direct dependent product information (such as the direct dependent product field value) of the assembled product includes the basic product set (basicProduct) and the basic product data source set (basicSourceProduct). Since the assembled product can optionally directly depend on the basic product data source, the basic product data source set can be empty. According to the above definition, the model product directly depends on the product information (such as the direct dependent product field value) including the assembled product set (assembleProduct) and the basic product set (basicProduct). Since the model product at least selectively directly depends on the assembled product and the basic product, the assembled product set and the basic product set are either non-empty. According to the above definition, the directly dependent product information (such as the directly dependent product field value) of the integrated model product includes the model product set (modelProduct), the assembly product set (assembleProduct) and the basic product set (basicProduct). Since the integrated model product directly depends on the model product, and optionally directly depends on the assembly product and / or the basic product, the model product set is not empty, and the assembly product set and / or the basic product set can be empty. Here, the "directly dependent product set" can be, for example, one or more lists or arrays containing all directly dependent products, especially one or more arrays determined according to the direct dependency relationship.

[0088] In some embodiments, after the product information is stored, i.e., persisted, it can be optionally packaged and pushed. For example, in some examples, the product information is packaged as a message body and sent to a given message queue, which can be processed by a related processing unit (e.g., a unit that constructs a kinship node and / or a directional relationship) in any suitable manner.

[0089] In the embodiments of the present disclosure, for example, in steps S130 and S140 described below, each specific product can be abstracted as a corresponding node, and the blood relationship between products can be abstracted as a directional connection between each node, thereby constructing a product blood relationship model.

[0090] S130: Construct a blood relationship node corresponding to the product according to the product attribute information of the product.

[0091] In step S130, the product may be abstracted into a corresponding node in the blood relationship graph, and the node-related product attributes may be assigned to the corresponding node fields.

[0092] like Figure 3 As shown, the step S130 may specifically include the following S131-S132:

[0093] S131: Extracting product attribute information related to the node.

[0094] In some embodiments, the node-related attribute information may include product name, product category, and product status. In other embodiments, the node-related attribute information may include product name, product version, product category, and product status. Optionally, the node-related attribute information may also include other product attributes, such as those mentioned above or any other suitable product attributes, such as but not limited to billing rules, pricing methods, scope of application, etc.

[0095] S132: Create a node object, and assign the extracted node-related product attribute information to the corresponding node field.

[0096] Here, a node object representing a product can be created, and the extracted information can be assigned to the corresponding node fields defined in the node object. In some embodiments, the node field includes a node name, a node category, and a node status, which correspond to the product name, product category, and product status, respectively. In other embodiments, the node field includes a node name, a node version, a node category, and a node status, which correspond to the product name, product version, product category, and product status, respectively. In an additional step not shown, a new node field can also be generated according to multiple product attributes or multiple assigned node fields, for example, a node name version can be generated by splicing the node name and the node version. Table 3 shows an example of a node field for a kinship node.

[0097] Table 3 Blood relationship node field information table

[0098] Field Chinese name Field Name Node Name node_name Node version node_version Node Name Version node_name_version Node Chinese node_cn_name Node Class node_type Node Status node_status

[0099] S140: Construct directional connections of blood relationship nodes based on the product's directly dependent product information.

[0100] In this step S140, the blood relationship between products can be abstracted as a directed connection between nodes in the blood relationship graph. In this embodiment, the directed connection includes a dependency connection between mapped products. In this embodiment, the directed connection may include a directed connection from an upstream node to a downstream node. In one example, where product A is directly dependent on product B, a directed connection from product A (upstream node) to product B (downstream node) can be created. Thus, the directed connections between multiple nodes can be used to fully represent the complex relationship network between multiple products in the product ecosystem.

[0101] In some embodiments, a directional link may be constructed based on the product name of the directly dependent product in the directly dependent product information. Figure 4 As shown, step S140 may specifically include:

[0102] S141: Parse the information of directly dependent products of the product and obtain a set of directly dependent products of the product.

[0103] In this step S141, the directly dependent product information includes, for example, the set of all directly dependent products described above. For example, the directly dependent product set of the integrated model product may include a model product set, an assembled product set, and a basic product set. Taking Table 2 above as an example, the directly dependent product set of the integrated model product A is, for example, {"modelProduct":[TestB:V1.0], / / Model product set "assembleProduct":[TestC:V1.0], / / Assembled product set "basicProduct":[TestD:V1.0] / / Basic product set}. For other products, the directly dependent product set of the obtained product is not repeated.

[0104] Here, it will be understood that in the above example, the product's direct dependency product set contains the version information of the direct dependency product, but Figure 4 The embodiment shown is also applicable to the situation where the directly dependent product set includes the product name of the directly dependent product but does not include the version information of the directly dependent product.

[0105] S142: For each directly dependent product in the directly dependent product set, extract the product name of the directly dependent product as the downstream node name.

[0106] Here, the product names of all directly dependent products of the product can be obtained by traversing the directly dependent product set. And the product names of the directly dependent products can be extracted accordingly as the downstream node names (to_node_name). Still taking Table 2 above as an example, multiple (direct) downstream node names of the integrated model product A can be extracted from the (3) directly dependent product sets, for example, modelProduct_TestB, assembleProduct_TestC, basicProduct_TestD.

[0107] S143: Extract the product name of the product attribute information of the product as the upstream node name.

[0108] Here, the product name (product_name) in the product attribute information can be directly obtained as the upstream node name (from_node_name) corresponding to the product. In steps S142 and S143, the "upstream" and "downstream" in the upstream node and downstream node can be understood as direct upstream and direct downstream. Still taking Table 2 above as an example, "integrated model product A" can be extracted as the upstream node name, such as EnModelProduct_TestA.

[0109] S144: Create a directional connection including the upstream node name and the downstream node name.

[0110] Based on the upstream and downstream node names extracted above, a directional connection including the upstream node name and the downstream node name can be created. The directional connection can be in the form of a data list or array, for example. In different embodiments, the directional connection, such as a data list or array, can have different forms.

[0111] In this embodiment, the association relationship can be constructed by using the product name, which is applicable to scenarios where version information does not need to be considered. This embodiment is particularly suitable for real-time update products, such as data products, including but not limited to big data products, real-time data stream products, or dynamic data set management products. Here, this embodiment can more intuitively reflect the real-time association between data products and help reflect the data dependency network.

[0112] In other embodiments, a directional link may be constructed based on the product name and product version of the directly dependent product in the directly dependent product information. Figure 5 As shown, step S140 may specifically include:

[0113] S141': parse the product information directly dependent on the product, and obtain the product set directly dependent on the product.

[0114] Similar to step S141, in step S141', the directly dependent product information includes, for example, a set of all directly dependent products described above. However, in this embodiment, the directly dependent product information, such as the directly dependent product set, may include product version information.

[0115] S142': For each directly dependent product in the directly dependent product set, extract the product name of the directly dependent product as the downstream node name.

[0116] In this embodiment, the description of step S142' may refer to step S142, which will not be repeated here.

[0117] S143': For each directly dependent product in the directly dependent product set, extract the product version of the directly dependent product as the downstream node version.

[0118] In this embodiment, the product versions of all directly dependent products of the product can be obtained by traversing the directly dependent product set, where. And, the product versions of the directly dependent products can be extracted accordingly as the downstream node version (to_node_version). Still taking Table 2 above as an example, the product versions of the products corresponding to multiple (direct) downstream nodes of the integrated model product A can be extracted from the (3) directly dependent product sets, for example, V1.0 (version of model product modelProduct_TestB), V1.0 (version of assembly product assembleProduct_TestC), V1.0 (version of basic product basicProduct_TestD).

[0119] Compared to Figure 4 The embodiment shown further obtains product version information of dependent products, which helps to achieve dependency control that is beneficial to product iteration and is suitable for version compatibility analysis.

[0120] S144': Extract the product name of the product attribute information of the product as the upstream node name.

[0121] In this embodiment, the description of step S144' may refer to step S143, which will not be repeated here.

[0122] S145': extract the product version of the product attribute information of the product as the upstream node version.

[0123] Here, the product version (version) in the product attribute information can be directly obtained as the upstream node name (from_node_version) corresponding to the product. Assuming that the version of the integrated model product A is "V1.0", the version information "V1.0" of the integrated model product A can be extracted.

[0124] S146': Create a directional connection including an upstream node name, an upstream node version, a downstream node name, and a downstream node version.

[0125] Compared to Figure 4 In the embodiment shown, the directional connection in this embodiment also involves node version information. Figure 4 Compared with the embodiment shown in FIG. 14 , the directional connection created in step S146 ′ can more accurately represent the product dependency relationship, which is helpful for version control and compatibility management.

[0126] In a further specific embodiment, a first (upstream) directional connection can be created based on the upstream node name and upstream node version extracted above, and a second (downstream) directional connection can be created based on the downstream node name and downstream node version extracted above. The directional connection can be in the form of a data list or array, for example.

[0127] In a further specific embodiment, as an additional step to the above steps or combined with related steps (such as S142' to S144'), the following operations may also be performed: A1: Generate an upstream node name version based on the upstream node name and the upstream node version; A2: Generate a downstream node name version based on the downstream node name and the downstream node version. Correspondingly, the above step S146' may include: including the generated upstream node name version and downstream node name version in the directional connection. The following Table 4 exemplarily shows a kinship node directional connection table, which displays the node name version on the basis of the node name and the node version. People will understand that the generated node name version can be used as a supplement or substitute for the above-mentioned node name and node name, which all fall within the scope of the present disclosure. For example, in some schemes, the directional connection table may only include the node name version.

[0128] Table 4. Directed connection table of blood relationship nodes

[0129] Field Chinese Field Name Upstream node name from_node_name Upstream node version from_version Upstream node name version from_name_version Downstream node name to_node_name Downstream node version to_version Downstream node name version to_name_version

[0130] In an optional embodiment, the directional connection of the blood relationship node constructed in step S140 can be encrypted. Here, this encryption process is optionally applicable to, for example, Figure 4 The node name-based directional connection scheme shown can also be applied to, for example, Figure 5 The directional connection scheme based on node name and node version (including node name version) is shown.

[0131] against Figure 4The node name-based directional connection scheme shown may also include additional steps or be combined with the following processing in step S144 of creating a directional connection: encrypt the node name, such as encoding or hashing, to generate an encrypted directional connection identifier (i.e., node name identifier). Optionally, the upstream node name and the downstream node name may be concatenated and encrypted, or may be encrypted separately, all of which fall within the scope of the present disclosure. For example, for a downstream node named "ProductA", a hash value such as "7b52009b64fd0a2a49e6d8a939753077792b0554" may be generated as a unique identifier that characterizes the downstream node in the directional connection.

[0132] against Figure 5 The directional connection scheme based on node name and node version (including node name version) shown may also include additional steps or combine the following processing in step S146' of creating a directional connection: concatenate the node name and node version; encrypt the concatenation result, such as encoding or hashing, to generate an encrypted directional connection identifier (i.e., node name version identifier). Optionally, the upstream node name version and the downstream node name version may be further concatenated and encrypted, or may be encrypted separately, which all fall within the scope of the present disclosure. For example, for a downstream node named "ProductA" and with a version of "V1.0", it may be first concatenated into "ProductA_V1.0", and then a hash value such as "d5f12e53a182c062b6bf30c1445153faff12269a" may be generated as a unique identifier representing the downstream node in the directional connection.

[0133] This encryption process not only effectively prevents unauthorized access and tampering, but also helps compress data, which may reduce the need for storage space; more importantly, for example, for financial products, risk isolation between products may be important, and when conducting subsequent blood relationship queries, it can help to ensure the security of product data or information. In addition, such a solution also facilitates fast query and comparison, especially when processing large-scale data, which can improve the efficiency of the system.

[0134] In an optional embodiment, the directional connection of the blood relationship node constructed in step S140 may also be verified, including but not limited to at least one of the following verifications: verifying whether the upstream node and the downstream node exist in the product blood relationship library; verifying whether the upstream node version is compatible with the downstream node version; verifying whether the dependency relationship between the upstream node and the downstream node complies with predetermined rules.

[0135] Through this verification mechanism, the accuracy and reliability of the directional connection of product blood relationship can be further improved.

[0136] Subsequently, the constructed blood relationship nodes and directional connections may be persistently stored in step S150.

[0137] Step S150: Store the blood relationship nodes and directional connections in the product blood relationship library.

[0138] In this embodiment, the above-mentioned blood relationship nodes and directional connections can be stored in a special product blood relationship library to provide data support for subsequent query and update operations. After the constructed blood relationship nodes and directional connections between each node are persisted, an enterprise-level product blood relationship library can be obtained.

[0139] The method for generating product blood relationship of the embodiment of the present disclosure may further include a product information updating step to maintain the real-time and accuracy of the product blood relationship.

[0140] In some embodiments of the present disclosure, the method further includes steps B1 to B3 of updating product information:

[0141] B1: In response to the product update request, the stored product information is updated.

[0142] In step B1, the stored product information may be updated in response to a product update request, and the update may involve changes to product attribute information and / or directly dependent product information.

[0143] In a further embodiment, the updated product information may also be verified. In a specific embodiment, the verification includes: determining the updated product category of the product; determining the directly dependent products of the product based on the updated directly dependent product information; querying the stored product information to determine the product category of each directly dependent product; and verifying whether the product category of the product and the product category of each directly dependent product meet the preset product dependency rules based on the product dependency rules. The verification process can refer to the verification method when creating the product to ensure that the updated product information still meets the predefined product dependency rules.

[0144] B2: According to the updated content of the product information, the blood relationship node corresponding to the updated product in the product blood relationship database is updated.

[0145] In step B2, the corresponding blood relationship nodes in the product blood relationship library may be updated according to the updated product attribute information.

[0146] In a further embodiment, updating the blood relationship node may include: extracting node related information from the updated product attribute information; updating the attributes of the corresponding blood relationship node object; and re-storing the updated blood relationship node object into the product blood relationship library. This can refer to the embodiment of the reference blood relationship node to ensure that the updated node information is consistent with the product information.

[0147] B3: According to the updated content of the product information, the directional connection of the blood relationship node corresponding to the updated product in the product blood relationship library is updated.

[0148] In this embodiment, for example, in step B3, the corresponding directional connection in the product blood relationship library may be updated according to the updated directly dependent product information.

[0149] In a further embodiment, updating the directional connection includes: parsing the updated direct dependent product information to obtain the updated direct dependent product set; comparing the direct dependent product set before and after the update to determine the directional connection that needs to be added, deleted or modified; for the directional connection that needs to be added, a new directional connection object is created; for the directional connection that needs to be deleted, the corresponding directional connection object is removed from the product kinship library; for the directional connection that needs to be modified, the upstream and downstream node information (such as the node name or node name version) of the directional connection is updated. The embodiment of constructing the directional connection can be referred to to ensure that the updated connection information accurately reflects the dependency relationship between products.

[0150] In the above, multiple embodiments of the method for generating product lineage relationships have been described in detail. The method effectively constructs a product lineage relationship library containing complex product dependencies. Based on this product lineage relationship library, the embodiment of the present disclosure provides a product lineage relationship query method, which can comprehensively and intuitively display the complex dependencies between products and can update the visualization effect in real time, thereby realizing comprehensive management and analysis of product lineage relationships.

[0151] The product blood relationship query method of the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.

[0152] like Figure 7 As shown, the product blood relationship query method of the embodiment of the present disclosure may include the following steps:

[0153] S710: In response to a product lineage query request, a lineage node dataset and a directional connection dataset related to a target product are retrieved from a product lineage database.

[0154] In this embodiment, the product management system can retrieve all blood relationship nodes and directional connections related to the target product in a pre-established product blood relationship library according to a preset strategy, wherein the preset strategy includes but is not limited to a graph traversal strategy.

[0155] In this embodiment, the product kinship library is obtained, for example, by the product kinship generation method disclosed above. However, it is understandable that, in other embodiments, a suitable product kinship library may also be obtained from other sources, such as an online database, and the present disclosure does not limit this.

[0156] In some embodiments, Figure 8 As shown, the S710 may include at least the following S711-S712:

[0157] S711: Determine a target blood relationship node corresponding to the target product according to the product information of the target product.

[0158] In this embodiment, the product management system can locate the corresponding kinship node in the product kinship database according to the target product information in the user request, such as product name, version number, etc. By way of explanation and not limitation, this node will serve as the starting point for subsequent queries.

[0159] S712: Taking the target blood relationship node as the starting point, recursively retrieve the associated blood relationship nodes along the query direction according to the directional connection of the blood relationship nodes, until reaching a predetermined level in the query direction or traversing all the associated blood relationship nodes, to obtain a blood relationship node data set including the target blood relationship node and the retrieved associated blood relationship nodes.

[0160] In this embodiment, a preset strategy can be utilized to recursively retrieve associated blood relationship nodes along the query direction. In some embodiments of the present disclosure, the preset strategy is a graph traversal strategy. In this embodiment, the directional connection is, for example, a directional connection including the upstream node name and the downstream node name created by the above S144 of the present disclosure. In one example, for the current blood relationship node, the directional connection is, for example: current blood relationship node name → downstream blood relationship node name.

[0161] In some embodiments of the present disclosure, the user can specify a predetermined level of query, such as querying level 3 in the query direction. In other embodiments, the user can also specify to traverse all associated blood relationship nodes until no new blood relationship nodes can be queried in the query direction. In this embodiment, the preset graph traversal strategy includes but is not limited to depth-first search or breadth-first search. In one example, the preset graph traversal strategy is a graph traversal strategy based on a depth-first search (DFS) algorithm. In this embodiment, the query direction can be specified by the user, including but not limited to performing an upward query, performing a downward query, and performing an upward query and a downward query at the same time.

[0162] In some embodiments of the present disclosure, the query direction is downward query, and S712 optionally includes the following step S7121 (not shown):

[0163] S7121: Determine the associated blood relationship node directly associated with the current blood relationship node according to the downstream node name in the directional connection corresponding to the current blood relationship node.

[0164] In this embodiment, the product management system can search for all directional connections of the current blood relationship node, where the directional connection of the current blood relationship node is, for example, "current blood relationship node name→downstream blood relationship node name", and the product management system can use the downstream node of the directional connection as an associated blood relationship node directly associated with the current blood relationship node.

[0165] In some embodiments of the present disclosure, Fig. 9 As shown, the query direction is upward query, and S712 optionally includes the following steps S7121'-S7122':

[0166] S7121': Determine upward association directional connections in the product lineage library.

[0167] In this embodiment, the directional connection is, for example, a directional connection including the upstream node name and the downstream node name created by the above S144 of the present disclosure. In a specific example, for "model product A", its corresponding blood relationship node and node directional connection are shown in Table 5 below:

[0168] Table 5. Model product A blood relationship and node directional connection

[0169]

[0170] In this embodiment, the product management system cannot directly determine the upstream node of the current blood relationship node based on the node directional connection of the current blood relationship node.

[0171] In this embodiment, the product management system may search the product blood relationship library and determine an upward-associated directional connection, wherein the downstream node name in the upward-associated directional connection corresponds to the node name of the current blood relationship node.

[0172] S7122': Determine the associated blood relationship node directly associated with the current blood relationship node according to the upstream node name in the upward association directional connection.

[0173] In this embodiment, the product management system can determine the name of the upstream node in the determined upward association directional connection as the associated blood relationship node directly associated with the current blood relationship node. In one example, the upward association directional connection is, for example, "upstream blood relationship node→current blood relationship node".

[0174] In other embodiments of the present disclosure, for example, in the above steps S7121, S7122'-S7122', the directional connection may optionally be a directional connection created in the above step S146' that includes the upstream node name, upstream node version, downstream node name and downstream node version. In this embodiment, when recursively retrieving associated blood relationship nodes along the query direction, the associated blood relationship node directly associated with the current blood relationship node may be determined in combination with the downstream node name and downstream node version in the directional connection corresponding to the current blood relationship node.

[0175] S713: According to the query direction, a directional connection dataset related to the target product is determined from the blood relationship node dataset.

[0176] In this embodiment, the product management system can obtain a blood relationship node data set based on the blood relationship nodes related to the current blood relationship node, wherein the blood relationship node data set includes but is not limited to node name, node version, node Chinese, node category, node status, etc.

[0177] In a specific example, the relationship node data set of "Model Product A" is shown in Table 6 below:

[0178] Table 6. Model product A blood relationship node dataset

[0179] Node Name Node version Node Chinese Node Class Node Status TestEnModelProductD1 V2.6 Integrated Model Product D1 Integrated model products Online TestModelProductA V1.0 Model Product A Model products Online TestAssembleProductB V2.0 Assemble product B Assembled products Online TestAssembleProductB5 V1.0 Assembled product B5 Assembled products Online TestAssembleProductB7 V1.0 Assembled product B7 Assembled products Online TestBasicProductC V1.8 Basic Product C Basic products To be launched TestBasicProductC5 V1.0 Basic product C5 Basic products Online TestBasicProductC7 V1.0 Basic product C7 Basic products Online TestBasicSourceProductE V1.0 Basic product data source E Basic product data source Online TestBasicSourceProductE6 V1.0 Basic product data source E6 Basic product data source Online

[0180] S720: Determine the product blood relationship of the target product according to the blood relationship node data set and the directional connection data set.

[0181] In this embodiment, the product management system can use, for example, the directional connection data set obtained by the aforementioned step S710 to construct a complete blood relationship map of the target product, which includes not only direct dependencies but also indirect dependencies, thereby comprehensively reflecting the position and influence of the target product in the entire product ecosystem.

[0182] In some embodiments of the present disclosure, Fig.10 The steps shown may optionally include:

[0183] S730: Perform data cleaning on the directional connection data set.

[0184] In this embodiment, the product management system can filter and clean the obtained directional connection data set. Fig.11 , the S730 may at least include the following steps:

[0185] S731: Remove the directional connection data whose upstream node name or downstream node name is not in the blood relationship node dataset.

[0186] In this embodiment, the directional connection data includes, for example, the upstream node name or downstream node name of the blood relationship node, and the product management system can retain the blood relationship nodes whose ends of the connection exist in the node data set. For example, if a directional connection pointing to a non-existent node name is found, the directional connection will be removed.

[0187] S732: Remove directional connection data in which at least one of the upstream node name, upstream node version, downstream node name and downstream node version is not in the blood relationship node data set.

[0188] In this embodiment, the directional connection data includes, for example, the upstream node name, upstream node version, downstream node name and downstream node version of the blood relationship node, and the product management system can retain the directional connection data containing all of the above information. For example, if a directional connection is found that does not have an upstream node version, the directional connection will be removed. In a specific example, referring again to the aforementioned S713 and table, the cleaned relationship node data set of "Model Product A" is shown in Table 7 below:

[0189] Table 7 Model product A directional node data set

[0190] Upstream node name Upstream node version Downstream node name Downstream node version TestEnModelProductD1 V2.6 TestModelProductA V1.0 TestEnModelProductD1 V2.6 TestAssembleProductB7 V1.0 TestEnModelProductD1 V2.6 TestBasicProductC5 V1.0 TestModelProductA V1.0 TestAssembleProductB V2.0 TestModelProductA V1.0 TestAssembleProductB5 V1.0 TestModelProductA V1.0 TestAssembleProductB7 V1.0 TestModelProductA V1.0 TestBasicProductC7 V1.0 TestAssembleProductB5 V1.0 TestBasicProductC V1.8 TestAssembleProductB5 V1.0 TestBasicSourceProductE6 V1.0 TestBasicProductC7 V1.0 TestBasicSourceProductE6 V1.0

[0191] S740: Use a dependency flow diagram to visualize the product lineage relationship of the determined target product.

[0192] In this embodiment, the product management system converts abstract directional connection data into intuitive visual graphics to facilitate user understanding and analysis.

[0193] In some embodiments of the present disclosure, reference Fig.12 , the 740 may include the following steps:

[0194] S741: Generate nodes in a dependency flow graph according to the blood relationship node data in the blood relationship node data set.

[0195] In this embodiment, the product management system represents the blood relationship node of each product as a node in the interface view, and the node may include information such as the product name and product version.

[0196] S742: Generate directed links between nodes in the dependency flow graph according to the directional connection data in the directional connection data set.

[0197] In this embodiment, the product management system draws directed lines between the corresponding blood relationship nodes according to the direct / indirect dependency relationship between the blood relationship nodes of the products in the directional connection data set, and the direction of the arrow indicates the direction of the dependency relationship. Fig.14 , which shows a schematic diagram of the product lineage visualization interface, and displays the product dependency network structure including four layers of products in a hierarchical structure, from left to right: integrated product layer (including integrated products D and D1), model product layer (including model product A), assembly product layer (including assembly products B and B1 to B7), basic product layer (including basic products C and C1 to C7) and basic product data source layer including basic products E and E1 to E6). Specifically, the dependency network contains 26 product lineage nodes (represented by gray boxes), which are interconnected through 36 directed lines. Each line includes a starting arrow, a line body, an end arrow and a serial number mark, which are used to clearly show the dependency direction between product lineage nodes. For example, the directed line numbered 1 in the figure shows the dependency relationship from integrated product D to model product A: integrated product D directly depends on model product A. It should be understood that although this embodiment shows a four-layer structure, the number of levels in actual applications can be adjusted according to specific needs. Each level can also contain a larger number of product lineage relationship nodes, and there can also be a larger number of directed connections between product lineage relationship nodes based on dependency relationships.

[0198] In some embodiments of the present disclosure, reference Fig.14 After visually displaying the blood relationship nodes and the dependencies between the blood relationship nodes, the user can also update the blood relationship nodes in the visualization view, and the update will also be reflected in a visual form.

[0199] Accordingly, the method of the embodiment of the present disclosure may include: S750: updating the product blood relationship of the target product.

[0200] In some embodiments, Fig.13 As shown, the S750 may include at least the following steps:

[0201] S751: In response to at least one node in the user's interactive operation dependency flow graph, determine that a product corresponding to the at least one node is a new target product.

[0202] In this embodiment, the user can click on any node in the visualization view, and the product management system will set the product corresponding to the node as a new target product.

[0203] S752: Determine the product lineage relationship of the new target product and dynamically update the dependency flow graph, where the updated dependency flow graph at least partially visualizes the product lineage relationship of the new target product.

[0204] In this embodiment, after confirming the new target product, the product management system may re-execute the aforementioned blood relationship query process and update the product blood relationship visualization interface to display the upstream and downstream dependencies of the new target product.

[0205] In the embodiments of the present disclosure, multiple embodiments of the product lineage generation method and multiple embodiments of the product lineage query method are described in detail. The product lineage generation method of the embodiments of the present disclosure builds a product lineage library containing complex product dependencies. The product lineage query method of the embodiments of the present disclosure achieves a comprehensive and intuitive display of complex dependencies between products, greatly improving the user's understanding and analysis capabilities of product dependencies.

[0206] It should be noted that the features of the various embodiments in the above methods can be flexibly combined according to specific needs to obtain new embodiments. In addition, these methods themselves can also be combined or spliced ​​to form new methods. These new combination or splicing methods also fall within the protection scope of the present disclosure.

[0207] In order to better understand the specific application of the embodiments of the present disclosure, the implementation of the above method will be described in detail below with reference to specific examples.

[0208] In a specific embodiment of the present disclosure, a multi-level product data structure representing the product lineage relationship of the multi-level products is first defined, and product dependency rules of the multi-level products are defined. Here, reference may be made to the aforementioned methods and steps related to S110 to generate the multi-level product data structure and define the product dependency rules. Specifically, reference may be made to the aforementioned S110. Figure 6, define the basic product data source (Basic Product Data Source) of the multi-level product data structure and the multi-level products: basic product (Basic Product), assembly product (Assemble Product), model product (Model Product) and integrated model product (Integrated Model Product), wherein the basic product is defined as directly dependent on at least one of the basic product data sources; the assembly product is defined as directly dependent on at least one of the basic products; the model product is defined as directly dependent on at least one of the assembly products and / or at least one of the basic products; the integrated model product is defined as directly dependent on at least one of the model products, and the following basic product data sources and products are obtained: basic product data source: TestBasicSourceProductE (V1.0); basic product: TestBasicProductC (V1.8); assembly product: TestAssembleProductB (V2.0); model product: TestModelProductA (V1.0); integrated model product: TestEnModelProductD1 (V2.6).

[0209] Next, the process of product creation and blood relationship building is specifically described by taking the user creating product TestModelProductA as an example. The process can refer to the aforementioned methods and steps related to S120:

[0210] The system receives a request from a user to create a product TestModelProductA, which includes basic product information: product name (productName) "TestModelProductA", product version (version) "V1.0", product category (productType) "model product", product charging rule (chargeRule) "1", promotion scope (scope) "customer group A, customer group B", product status (productName) "online", and product direct dependent product information (dependProduct): product TestModelProductA directly depends on product TestAssembleProductB and product TestBasicProductC.

[0211] At this time, the product management system verifies the directly dependent product information of the product TestModelProductA. This process can refer to the relevant description of the aforementioned S121-S125: Specifically, the product management system determines that the product category of the product TestModelProductA is a model product, and queries the stored product information to determine that the category of the product TestAssembleProductB is an assembly product, and the category of the product TestBasicProductC is a basic product. Therefore, according to the product dependency rules, it is verified that the model product (TestModelProductA) can depend on the assembly product (TestAssembleProductB) and the basic product (TestBasicProductC), and the verification passes. After the verification passes, the product management system constructs the blood relationship node corresponding to the product TestModelProductA. This process can refer to the methods and steps related to the aforementioned S130:

[0212] Specifically, referring to the relevant description of S131-S132 above, the product management system extracts the basic product information related to the blood relationship node, including the product name (productName) "TestModelProductA", product version (version) "V1.0", product category (productType) "model product", product charging rule (chargeRule) "1", promotion scope (scope) "customer group A, customer group B", product status (productName) "launched", and the product's directly dependent product information (dependProduct), and creates a node object based on the above information, assigns the extracted information to the corresponding node field, and obtains the blood relationship node corresponding to the following product TestModelProductA: "Blood relationship node: Model product A: "product_name: TestModelProductA; version: V1.0; product_name_version: TestModelProductA-V1.0; product_cn_name: Model product A; product_type: Model product; chargeRule: calculated based on the number of users; pricingType: calculated when used and there is a result; scope: customer group A, customer group B; status: launched".

[0213] Subsequently, the product management system constructs a directional connection for the product TestModelProductA. This process may refer to the methods and steps related to the aforementioned step S140: the product management system parses the dependent product information of the direct product TestModelProductA, obtains the direct dependent product set {TestAssembleProductB, TestBasicProductC} of the product TestModelProductA, and performs the following processing: For the product TestAssembleProductB: the product management system extracts its product name "TestAssembleProductB" as the downstream node name, and extracts its product version "V2.0" as the downstream node version. For the product TestBasicProductC: the product management system extracts its product name "TestBasicProductC" as the downstream node name, and extracts its product version "V1.8" as the downstream node version. For the product TestModelProductA: the product management system extracts its product name "TestModelProductA" as the upstream node name, and extracts its product version "V1.0" as the upstream node version.

[0214] Subsequently, the product management system creates two directional connections based on the extracted information above: Directional connection 1: TestModelProductA(V1.0)→TestAssembleProductB(V2.0): "from_product_name:TestModelProductA:from_version:V1.0:from_name_version:TestModelProductA-V1.0:to_product_name:TestAssembleProductB:to_version:V2.0:to_name_version:TestAssembleProductB-V2.0", Directional connection 2: TestModelProductA(V1.0)→TestBasicProductC(V1.8): "from_product_name:TestModelProductA;from_version:V1.0;from_name_version:TestModelProductA-V1.0;to_product_name:TestAssembleProductC;to_version:V1.8;to_name_version:TestAssembleProductB-V1.8".

[0215] The product management system stores the constructed blood relationship node of the above-mentioned product TestModelProductA and the above-mentioned two directional connections in the product blood relationship library. This process can refer to the methods and steps related to the above-mentioned S150.

[0216] In a specific embodiment, the product management system includes a target product named "model product A" with a version of V1.0. The product management system receives a downward query request from a user regarding the blood relationship of the target product, hoping to understand the downstream dependency of the product.

[0217] First, the product management system searches for data related to "model product A" in the product lineage database. This process may refer to the methods and steps related to the aforementioned step S710.

[0218] Specifically, the product management system locates the target blood relationship node representing "model product A", which contains the following information: product name (productName) "TestModelProductA", product version (version) "V1.0", product Chinese name (productCnName) "Model Product A", product status (status) "online". This process can refer to the methods and steps related to the aforementioned step S711.

[0219] Then, referring to the description of the aforementioned step S712, the product management system uses a preset depth-first search (DFS) strategy, starting from the "model product A" node, to query its directly associated associated blood relationship nodes.

[0220] Specifically, referring to the description of the aforementioned step S712, the product management system first queries downward the products on which the "model product A" node directly depends, and determines that the "model product A" directly depends on the following two products: "Assembly product B": TestAssembleProduct, version V2.0; "Basic product C": TestBasicProductC, version V1.8.

[0221] The product management system continues to execute this process recursively. It will further query the dependency of "Assembly Product B" and determine that "Assembly Product B" directly depends on "Basic Product C5" (TestBasicProductC5), version V1.0; "Assembly Product B" directly depends on "Basic Product Data Source E6" (TestBasicSourceProductE6), version V1.0. Similarly, the product management system will also query the dependency of "Basic Product C" until all relevant blood relationship nodes are traversed.

[0222] Subsequently, referring to the relevant description of the aforementioned step S713, the product management system will determine the directional connection data sets between them based on the previously collected blood relationship node information: the connection from "TestModelProductA-V1.0" to "TestAssembleProductB-V2.0"; the connection from "TestModelProductA-V1.0" to "TestBasicProductC-V1.8"; the connection from "TestAssembleProductB-V2.0" to "TestBasicProductC5"; the connection from "TestAssembleProductB-V2.0" to "TestBasicSourceProductE6-V1.0".

[0223] The product management system can use the above-mentioned directional connection data set determined by retrieval to construct a complete blood relationship map of the target product. This process can refer to the relevant description of the aforementioned step S720.

[0224] Next, the product management system performs a data cleaning step, which may refer to the relevant description of S730 above:

[0225] The product management system will check each directional connection to ensure that both end nodes of the connection exist in the blood relationship node data set. Referring to the relevant description of S731 mentioned above, the product management system will check the version information of the blood relationship node and find that a connection points to "TestBasicProductC-V1.7", but there is only "TestBasicProductC-V1.8" in the node data set. At this time, the product management removes the connection pointing to the V1.7 version.

[0226] Subsequently, referring to the description of the aforementioned step S740, the product management system generates a dependency flow graph using the cleaned directional connection data set. Referring to the description of the aforementioned step S741, the product management system creates a node for each product: a central node marked as "Model Product A (V1.0)"; downstream of the central node is a node of "Assembled Product B (V2.0)"; downstream of the "Assembled Product B (V2.0)" node are nodes of "Basic Product C (V1.8)" and "Basic Product C5 (V1.0)"; downstream of the nodes of "Basic Product C (V1.8)" and "Basic Product C5 (V1.0)" is a node of "Basic Product Data Source E6 V1.0".

[0227] Next, referring to the relevant description of S742 mentioned above, the product management system adds directed connection lines between these nodes, with arrows pointing in the direction of dependency: the arrow from "model product A" to "assembly product B", the arrow from "model product A" to "basic product C", and the arrow from "assembly product B" to "basic product C5" and "basic product data source E6 V1.0", thereby presenting the downward query results of the blood relationship of "model product A".

[0228] In a specific embodiment of the present disclosure, the product management system includes a target product named "basic product C" with a version of V1.8. The product management system receives an upward query request from a user regarding the blood relationship of the target product, hoping to understand the upstream dependency of the product.

[0229] First, the product management system searches for data related to "basic product C" in the product lineage database. This process may refer to the methods and steps related to the aforementioned step S710.

[0230] Specifically, the product management system locates the target blood relationship node representing "basic product C", which contains the following information: product name (productName) "TestBasicProductC", product version (version) "V1.8", product Chinese name (productCnName) "Basic Product C", product status (status) "online". This process can refer to the methods and steps related to the aforementioned step S711.

[0231] Then, referring to the description of the aforementioned step S712, the product management system uses a preset depth-first search (DFS) strategy, starting from the "basic product C" node, to query its directly associated associated blood relationship nodes.

[0232] Specifically, referring to the description of the aforementioned step S712, the product management system first queries upward for products that directly depend on the "basic product C" node, and determines that the following two products directly depend on the "basic product C": "model product A": TestModelProductA, version V1.0; "assembly product B": TestAssembleProductB, version V2.0.

[0233] The product management system continues to recursively execute this process. It will further query the dependency of "Model Product A" and determine that the product that directly depends on "Model Product A" is "Integrated Model D1" (TestEnModelProductD1), version V2.6. Similarly, the product management system will also query the dependency of "Assembly Product B" until all related lineage nodes are traversed.

[0234] Subsequently, referring to the relevant description of the aforementioned step S713, the product management system will determine the directional connection data sets between them based on the previously collected blood relationship node information: the connection from "TestEnModelProductD1-V2.6" to "TestModelProductA"; the connection from "TestModelProductA-V1.0" to "TestBasicProductC-V1.8"; the connection from "TestAssembleProductB-V2.0" to "TestBasicProductC-V1.8".

[0235] The product management system can use the above-mentioned directional connection data set determined by retrieval to construct a complete blood relationship map of the target product. This process can refer to the relevant description of the aforementioned step S720.

[0236] Next, the product management system performs a data cleaning step, which may refer to the relevant description of S730 above:

[0237] The product management system will check each directional connection to ensure that both end nodes of the connection exist in the lineage node data set. Referring to the relevant description of S731 above, the product management system will check the version information of the lineage node and find that a connection comes from "TestAssembleProductB-V1.0", but there is only "TestAssembleProductB-V2.0" in the node data set. At this time, the product management removes the connection pointing to the V1.0 version.

[0238] Subsequently, referring to the description of the aforementioned step S740, the product management system generates a dependency flow graph using the cleaned directional connection data set. Referring to the description of the aforementioned step S741, the product management system creates a node for each product: a central node marked as "Basic Product C (V1.8)"; upstream of the central node are nodes of "Model Product A (V1.0)" and "Assembly Product B (V2.0)"; upstream of the nodes of "Model Product A (V1.0)" and "Assembly Product B (V2.0)" is a node of "Integrated Model Product D1 (V2.6)".

[0239] Next, referring to the relevant description of S742 mentioned above, the product management system adds directed connection lines between these nodes, with arrows pointing in the direction of dependency: an arrow from "integrated model product D1" to "model product A", an arrow from "model product A" to "basic product C", and an arrow from "assembled product B" to "basic product C", thereby presenting the upward query results of the blood relationship of "basic product C".

[0240] The above describes the product kinship generation method and query method of the embodiments of the present disclosure and its specific examples.

[0241] The corresponding device for processing product kinship relationships described in the embodiment of the present disclosure will also be introduced below. The device can be implemented by software, hardware, or a combination of software and hardware. In some embodiments, the device can be an independent system or integrated into an existing product management system. For example, in terms of software implementation, the device can be a set of applications running on a server or a cloud platform, including a data processing module, a query module, and a visualization interface module. These modules can be implemented in programming languages ​​​​(such as Java, Python, etc.), and may use a database management system (such as MySQL, MongoDB, etc.) to store and manage product kinship data. In terms of hardware, the device may include components such as a processor, a memory, and a network interface to support the operation of the software and the processing of data. In addition, a dedicated graphics processing unit (GPU) may also be included to improve the rendering efficiency of complex product kinship diagrams.

[0242] The functional modules of the device for processing product blood relationship according to the embodiment of the present disclosure will be described in detail below.

[0243] In some embodiments of the present disclosure, Fig.15 As shown, a product kinship generation device 1500 is provided, which may include a generation unit 1501, a creation unit 1502, a node construction unit 1503, a connection construction unit 1504 and a product kinship library 1505. The generation unit 1501 is configured to generate a multi-level product data structure representing the product kinship of multi-level products and define product dependency rules of the multi-level products, wherein the product dependency rules include: in the multi-level product data structure, the multi-level products are defined to include a base product and at least one upper-level product, the base product is defined to directly depend on at least one base product data source, and the at least one upper-level product is defined to directly or indirectly depend on the base product. The creation unit 1502 is configured to create a product and store product information of the product in response to a product creation request, wherein the product information includes product attribute information and directly dependent product information. The node construction unit 1503 is configured to construct a kinship node corresponding to the product according to the product attribute information of the product. The connection construction unit 1504 is configured to construct a directional connection of the kinship node according to the directly dependent product information of the product. The product blood relationship library 1505 is configured to store the blood relationship nodes and the directional connections.

[0244] In some embodiments of the present disclosure, Fig.16As shown, a product lineage query device 1600 is also provided, which may include a retrieval unit 1601 and a determination unit 1602. The retrieval unit 1601 is configured to respond to a product lineage query request and retrieve a lineage node data set and a directional connection data set related to a target product in a product lineage database, wherein the product lineage database is, for example, based on Fig.15 The product blood relationship library 1505 of the product blood relationship generation device 1500 is shown. The determination unit 1602 is configured to determine the product blood relationship of the target product according to the blood relationship node data set and the directional connection data set. The device and its components, modules, units and features described in the embodiments of the present disclosure can be combined with the method of the embodiments of the present disclosure in a non-contradictory manner, and the method and its steps, sub-steps and features described in the embodiments of the present disclosure can also be combined with the device of the embodiments of the present disclosure in a non-contradictory manner.

[0245] In an embodiment of the present disclosure, an electronic device may also be provided, including: a processor and a memory storing a computer program, wherein the processor is configured to execute any method of the embodiment of the present disclosure when running the computer program.

[0246] Fig.17 A schematic diagram of an electronic device 1700 that can implement the method of the disclosed embodiment or implement the disclosed embodiment is shown, and in some embodiments, more or fewer electronic devices may be included than shown. In some embodiments, it can be implemented using a single or multiple electronic devices. In some embodiments, it can be implemented using cloud or distributed electronic devices.

[0247] like Fig.17 As shown, the electronic device 1700 includes a processor 1701, which can perform various appropriate operations and processes according to the programs and / or data stored in the read-only memory (ROM) 1702 or the programs and / or data loaded from the storage part 1708 to the random access memory (RAM) 1703. Processor 1701 can be a multi-core processor or can include multiple processors. In some embodiments, processor 1701 can include a general main processor and one or more special coprocessors, such as a graphics processing unit (GPU), a neural network processor (NPU), a digital signal processor (DSP), etc. In RAM 1703, various programs and data required for the operation of electronic device 1700 are also stored. Processor 1701, ROM 1702 and RAM 1703 are connected to each other via bus 1704. Input / output (I / O) interface 1705 is also connected to bus 1704.

[0248] The processor and the memory are used together to execute the program stored in the memory. When the program is executed by the computer, the steps or functions of the methods described in the above embodiments can be implemented.

[0249] The following components are connected to the I / O interface 1705: an input section 1706 including a keyboard, a mouse, a touch screen, etc.; an output section 1707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1708 including a hard disk, etc.; and a communication section 1709 including a network interface card such as a LAN card, a modem, etc. The communication section 1709 performs communication processing via a network such as the Internet. A drive 1710 is also connected to the I / O interface 1805 as needed. A removable medium 1711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1710 as needed, so that a computer program read therefrom is installed into the storage section 1708 as needed. Fig.17 Only some components are schematically shown in the figure, which does not mean that the computer system 1700 only includes Fig.17 Components shown.

[0250] In some embodiments, the electronic device refers to a mobile terminal or a computer, including a mobile phone, a car terminal, a smart TV, etc. Taking a mobile phone as an example, the electronic device also includes a display screen with a touch function, an external speaker, a gyroscope, a camera, a 4G / 5G antenna and other device modules.

[0251] Although not shown, in an embodiment of the present disclosure, a program product is provided. The program product includes a computer program. The computer program is configured to implement any method of the embodiments of the present disclosure when executed.

[0252] Although not shown, in an embodiment of the present disclosure, a storage medium is provided, the storage medium storing a computer program, the computer program being configured to implement any method of the embodiments of the present disclosure when executed.

[0253] The storage media in the embodiments of the present disclosure include permanent and non-permanent, removable and non-removable items that can be implemented by any method or technology to store information. Examples of storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0254] The methods, programs, systems, devices, etc. of the embodiments of the present disclosure may be executed or implemented in a single or multiple networked computers, or may be practiced in a distributed computing environment. In the embodiments of the present specification, in these distributed computing environments, tasks may be performed by remote processing devices connected via a communication network.

[0255] Those skilled in the art should understand that the embodiments of the present specification may be provided as methods, systems or computer program products. Therefore, those skilled in the art may imagine that the functional modules / units or controllers and related method steps described in the above embodiments may be implemented in software, hardware or a combination of software / hardware.

[0256] Unless explicitly stated, the actions or steps of the methods, programs, and embodiments of the present disclosure do not have to be performed in a specific order and can still achieve the desired results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

[0257] In this article, multiple embodiments of the present disclosure are described, but for the sake of brevity, the description of each embodiment is not exhaustive, and the same or similar features or parts between the embodiments may be omitted. In this article, "one embodiment", "some embodiments", "example", "specific example", or "some examples" are meant to be applicable to at least one embodiment or example according to the present disclosure, rather than all embodiments. The above terms do not necessarily mean to refer to the same embodiment or example. In the absence of contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples.

[0258] The exemplary systems and methods of the present disclosure have been specifically shown and described with reference to the above embodiments, which are merely examples of the best modes for implementing the present systems and methods. It will be appreciated by those skilled in the art that various changes may be made to the embodiments of the systems and methods described herein when implementing the present systems and / or methods without departing from the spirit and scope of the present disclosure as defined in the appended claims.

Claims

1. A method for generating product kinship relationships, characterized in that: include: Generate a multi-level product data structure representing the product lineage relationship of the multi-level product, define the product dependency rules of the multi-level product, the product dependency rules include: in the multi-level product data structure, define that the multi-level product includes a base product and at least one upper-level product, define that the base product directly depends on at least one base product data source, and define that the at least one upper-level product directly or indirectly depends on the base product; In response to a product creation request, create a product and store product information of the product, wherein the product information includes product attribute information and directly dependent product information; According to the product attribute information of the product, construct a blood relationship node corresponding to the product; Constructing a directional connection of the blood relationship nodes according to the directly dependent product information of the product; The blood relationship nodes and the directional connections are stored in a product blood relationship library.

2. The method according to claim 1, characterized in that: The product dependency rules for defining the multi-level products further include: defining said at least one upper product to include an assembled product; The assembled product is defined to at least directly depend on at least one of the base products and optionally directly depend on at least one of the base product data sources.

3. The method according to claim 2, characterized in that The product dependency rules for defining the multi-level products further include: Defining that the at least one upper layer product comprises a model product; The model product is defined to be directly dependent on at least one of the assembly products and / or at least one of the base products.

4. The method according to claim 3, characterized in that The product dependency rules for defining the multi-level products further include: Defining that the at least one upper layer product also includes an integrated model product; It is defined that the integrated model product directly depends on at least one of the model products and optionally directly depends on at least one of the assembled products and / or at least one of the base products.

5. The method according to any one of claims 1 to 4, characterized in that The step of constructing a blood relationship node corresponding to the product according to the product attribute information of the product includes: Extract product attribute information related to the node; A node object including a plurality of node fields is created, and the extracted product attribute information related to the node is assigned to the corresponding node fields.

6. The method according to any one of claims 1 to 4, characterized in that The step of constructing the directional connection of the blood relationship nodes according to the directly dependent product information of the product includes: Parsing the information of directly dependent products of the product, and obtaining a set of directly dependent products of the product; For each directly dependent product in the directly dependent product set, extract the product name of the directly dependent product as the downstream node name; Extract the product name of the product attribute information of the product as the upstream node name; A directional connection including the upstream node name and the downstream node name is created.

7. The method according to any one of claims 1 to 4, characterized in that The step of constructing the directional connection of the blood relationship nodes according to the directly dependent product information of the product includes: Parsing the information of directly dependent products of the product, and obtaining a set of directly dependent products of the product; For each directly dependent product in the directly dependent product set, extract the product name of the directly dependent product as the downstream node name; For each directly dependent product in the directly dependent product set, extract the product version of the directly dependent product as the downstream node version; Extract the product name of the product attribute information of the product as the upstream node name; Extracting a product version of the product attribute information of the product as an upstream node version; A directional connection including the upstream node name, upstream node version, downstream node name and downstream node version is created.

8. The method according to any one of claims 1 to 4, characterized in that The step of responding to the product creation request, creating a product and storing product information of the product, further includes: verifying the directly dependent product information, specifically including: Determine the product category of the product according to the basic product information of the product; Determining the directly dependent products of the product according to the directly dependent product information of the product; Query the stored product information to determine the product category of each directly dependent product; According to the product dependency rule, verify the product category of the product and the product categories of each directly dependent product; When the verification passes, the product information of the product is stored.

9. A product lineage query method, characterized in that: include: In response to a product lineage query request, a lineage node data set and a directional connection data set related to a target product are retrieved from a product lineage database, wherein the product lineage database is obtained by implementing the product lineage generation method according to any one of claims 1 to 8; The product blood relationship of the target product is determined according to the blood relationship node data set and the directional connection data set.

10. The method according to claim 9, characterized in that The product blood relationship query request includes product information of the target product and a query direction; The step of responding to the product blood relationship query request and retrieving the blood relationship node data set and the directional connection data set related to the target product in the product blood relationship database includes: Determine, according to the product information of the target product, a target blood relationship node corresponding to the target product; Taking the target blood relationship node as the starting point, recursively searching for associated blood relationship nodes along the query direction according to the directional connection of the blood relationship nodes, until reaching a predetermined level in the query direction or traversing all associated blood relationship nodes, to obtain the blood relationship node data set including the target blood relationship node and the retrieved associated blood relationship nodes; According to the query direction, a directional connection data set related to the target product is determined by the blood relationship node data set.

11. The method according to claim 10, characterized in that The product blood relationship library is obtained by implementing the product blood relationship generation method according to claim 6; Wherein, the query direction includes upward query and / or downward query; When the query direction is a downward query, the related blood relationship nodes are recursively retrieved along the query direction based on the directional connection of the blood relationship node, including: determining the related blood relationship node directly associated with the current blood relationship node based on the downstream node name in the directional connection corresponding to the current blood relationship node; and / or When the query direction is an upward query, the related blood relationship nodes are recursively retrieved along the query direction based on the directional connection of the blood relationship node, including: determining the upward related directional connection in the product blood relationship library, the downstream node name in the upward related directional connection corresponds to the node name of the current blood relationship node; determining the related blood relationship node directly associated with the current blood relationship node based on the upstream node name in the upward related directional connection.

12. The method according to claim 10, characterized in that The product blood relationship library is obtained by implementing the product blood relationship generation method according to claim 7; Wherein, the query direction includes downward query and / or upward query; When the query direction is a downward query, the related blood relationship nodes are recursively retrieved along the query direction based on the directional connection of the blood relationship node, including: determining the related blood relationship node directly associated with the current blood relationship node based on the downstream node name and downstream node version in the directional connection corresponding to the current blood relationship node; and / or When the query direction is an upward query, the related blood relationship nodes are recursively retrieved along the query direction based on the directional connection of the blood relationship node, including: determining the upward related directional connection in the product blood relationship library, the downstream node name in the upward related directional connection corresponds to the node name of the current blood relationship node and the downstream node version in the upward related directional connection corresponds to the node version of the current blood relationship node; determining the related blood relationship node directly associated with the current blood relationship node based on the upstream node name and the upstream node version in the upward related directional connection.

13. The method according to any one of claims 9 to 12, characterized in that Also includes: The determined product lineage relationships of the target product are presented using a dependency flow graph in a product lineage visualization interface, wherein the nodes in the dependency flow graph are generated based on the lineage node data in the lineage node data set, and the directed lines between the nodes in the dependency flow graph are generated based on the directional connection data in the directional connection data set.

14. The method according to claim 13, characterized in that Also includes: In response to a user's interactive operation on at least one node in the dependency flow graph, determining a product corresponding to the at least one node as a new target product; The product lineage relationship of the new target product is determined and the dependency flow graph is dynamically updated, wherein the updated dependency flow graph at least partially visualizes the product lineage relationship of the new target product.

15. A device for generating product blood relationship, characterized in that: The product blood relationship generating device comprises: A generating unit is configured to generate a multi-level product data structure representing a product lineage relationship of a multi-level product and define product dependency rules of the multi-level product, including: defining that the multi-level product includes a base product and at least one upper-level product, defining that the base product directly depends on at least one base product data source, and defining that the at least one upper-level product directly or indirectly depends on the base product; a creation unit, configured to create a product and store product information of the product in response to a product creation request, wherein the product information includes product attribute information and directly dependent product information; A node construction unit, configured to construct a blood relationship node corresponding to the product according to the product attribute information of the product; A connection construction unit, configured to construct a directional connection of the blood relationship node according to the direct dependent product information of the product; A product blood relationship library is configured to store the blood relationship nodes and the directional connections.

16. A product blood relationship query device, characterized in that: The product blood relationship query device comprises: a retrieval unit configured to, in response to a product kinship query request, retrieve a kinship node data set and a directional connection data set related to a target product in a product kinship library, wherein the product kinship library is a product kinship library of the product kinship generation device according to claim 15; The determination unit is configured to determine the product blood relationship of the target product based on the blood relationship node data set and the directional connection data set.

17. An electronic device, characterized in that: include: A processor and a memory storing a computer program, wherein the processor is configured to implement the method according to any one of claims 1 to 14 when the computer program is executed.

18. A program product comprising a computer program, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 14 is implemented.

Images