Business object risk early warning method and device, electronic equipment and program product

Abstract

The present disclosure discloses a business object blood relationship risk early warning method, comprising: determining the blood relationship of a target business object according to a business object blood relationship library, wherein the business object blood relationship library comprises a plurality of blood relationship nodes corresponding to a plurality of business objects one by one and a direct dependency relationship between the plurality of blood relationship nodes, and the blood relationship node comprises business attribute information of the corresponding business object; based on a preset risk rule, risk identification is performed on the blood relationship of the target business object; and according to the risk identification result, risk early warning information associated with the blood relationship of the target business object is generated. The scheme of the present disclosure can effectively realize the timely discovery and early warning of potential blood relationship risks in the business object network.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, specifically to a method and device for early warning of risks related to blood relations of business objects, and also to related electronic equipment and program products. Background Technology

[0002] As businesses expand in both variety and scale, they typically employ business management systems to store and maintain data for each business segment in order to manage that data. These business segments often have interdependencies, forming complex dependency networks. In actual business operations, a change in the state of one business segment carries the risk of adversely affecting its related business segments.

[0003] However, existing business management systems only record basic data of corresponding businesses on a per-business-object basis, but lack analysis of dependencies between business objects and risk warning mechanisms. This makes it impossible for the system to proactively discover and warn of potential business operation risks.

[0004] Therefore, there is an urgent need for a solution that can automatically identify and warn of risks in business object dependency networks in order to reduce potential risks in business operations.

[0005] The background description is provided for the purpose of understanding the relevant technologies in this field and is not intended as an admission of prior art. Summary of the Invention

[0006] Accordingly, this disclosure provides a method for early warning of risks related to blood relations among business entities, which includes:

[0007] The lineage of the target business object is determined based on the business object lineage database, wherein the business object lineage database includes multiple lineage nodes that correspond one-to-one with multiple business objects and the dependency relationships between the multiple lineage nodes, and the lineage nodes include the business attribute information of the corresponding business object;

[0008] Based on preset risk rules, risk identification is performed on the blood relationship of the target business object;

[0009] Based on the risk identification results, risk warning information related to the blood relationship of the target business object is generated.

[0010] Optionally, the risk identification of the blood relationship of the target business object based on preset risk rules includes:

[0011] Determine the upstream and downstream relatives that a given relative node in the lineage of the target business object directly or indirectly depends on;

[0012] Determine at least one business attribute information corresponding to the given blood relationship node;

[0013] Based on the business attribute information corresponding to upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information, the risk identification result for the business attribute information is obtained.

[0014] Optionally, the preset risk rules include user-defined risk rules;

[0015] The method for early warning of risks related to blood relations of business objects also includes:

[0016] Obtain user-defined risk rule configuration and generate user-defined risk rules. The risk rule configuration includes at least a risk name, a risk field, upstream business object risk field judgment conditions, and downstream business object risk field judgment conditions, wherein the risk field corresponds to at least one business attribute information.

[0017] Optionally, the risk identification of the blood relationship of the target business object based on preset risk rules includes:

[0018] Determine the risk field value of at least one business attribute information corresponding to a given lineage node in the lineage relationship of the target business object;

[0019] Based on whether the risk field values ​​of the upstream and downstream related nodes match the risk field judgment conditions of the upstream business object and the downstream business object, a user-defined risk identification result is obtained.

[0020] Optionally, the business attribute information includes the scope of business application; wherein,

[0021] Determining at least one business attribute information corresponding to the given blood relationship node includes:

[0022] Determine the scope of business application corresponding to a given lineage node in the lineage relationship of the target business object;

[0023] The step of obtaining a risk identification result for the business attribute information based on the business attribute information corresponding to upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information includes:

[0024] Based on the intersection status of the business application scopes corresponding to the upstream and downstream blood relationship nodes and the preset intersection rules, the risk identification results for the business application scope are obtained.

[0025] Optionally, the business attribute information includes business status; wherein,

[0026] Determining at least one business attribute information corresponding to the given blood relationship node includes:

[0027] Determine the business status corresponding to a given lineage node in the lineage relationship of the target business object;

[0028] The step of obtaining a risk identification result for the business attribute information based on the business attribute information corresponding to upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information includes:

[0029] Based on the consistency status of the business status corresponding to the upstream and downstream blood relationship nodes and the preset consistency rules, the risk identification result for the business status is obtained.

[0030] Optionally, the business object lineage database also includes business object change record information corresponding to the lineage node;

[0031] The step of identifying the risk of blood relations of the target business object based on preset risk rules includes:

[0032] Determine the upstream relatives that a given relative node in the lineage of the target business object directly or indirectly depends on;

[0033] Obtain the business object change record information corresponding to the given bloodline node and the upstream bloodline node;

[0034] Based on the obtained business object change record information, the risk identification results for business object changes are obtained.

[0035] Optionally, after generating risk warning information associated with the blood relationship of the target business object, the method further includes:

[0036] The system combines a visualization interface for displaying the lineage relationships of business objects with a risk warning interface. The risk warning interface displays the risk warning information, while the visualization interface for displaying the lineage relationships of the business objects has a dependency flow graph that presents the determined lineage relationships of the target business objects. The dependency flow graph includes the multiple lineage relationship nodes and directed lines between each lineage relationship node.

[0037] Optionally, the method for early warning of risks related to the blood relations of business objects further includes:

[0038] In response to user interaction with risk warning information, the dependency flow graph in the business object lineage visualization interface highlights the lineage nodes and directed connections related to the selected risk warning information.

[0039] In a second aspect, a business object blood relationship risk warning device is provided, the business object blood relationship risk warning device comprising:

[0040] The determining unit is configured to determine the lineage relationship of the target business object based on the business object lineage relationship database, wherein the business object lineage relationship database includes multiple lineage relationship nodes that correspond one-to-one with multiple business objects and the dependency relationships between the multiple lineage relationship nodes, and the lineage relationship node includes the business attribute information of the corresponding business object;

[0041] The identification unit is configured to perform risk identification on the blood relationship of the target business object based on preset risk rules;

[0042] The generation unit is configured to generate risk warning information that is related to the blood relationship of the target business object based on the risk identification results.

[0043] In a third aspect, an electronic device is provided, comprising: a processor and a memory storing a computer program, the processor being configured to implement the method as described in the first aspect when the computer program is executed.

[0044] In a fourth aspect, a program product is provided, comprising a computer program, wherein the computer program, when executed by a processor, implements the method as described in the first aspect.

[0045] The business object lineage risk warning method proposed in this disclosure identifies and warns of risks in business object lineage based on preset risk rules. This solves the problem that existing systems lack an effective risk management mechanism when dealing with complex dependencies. It enables timely discovery and warning of potential risks in cross-business line business object networks, reducing or even eliminating potential risks caused by manually maintaining a large amount of business object information.

[0046] Other optional features and technical effects of the embodiments of this disclosure are described in part below, and in part will be apparent from reading this document. Attached Figure Description

[0047] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. The elements shown are not limited to the scale shown in the drawings, and the same or similar reference numerals in the drawings denote the same or similar elements, wherein:

[0048] Figure 1 A first flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0049] Figure 2 A second flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0050] Figure 3 A third flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0051] Figure 4 A fourth flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0052] Figure 5 A fifth flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0053] Figure 6 A sixth flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0054] Figure 7 A seventh flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0055] Figure 8 An eighth flowchart of a business object blood relationship risk warning method according to an embodiment of the present disclosure is shown;

[0056] Figure 9 A schematic diagram is shown of a business object lineage visualization interface embedded with a risk warning interface, provided by a business object lineage risk warning method according to a specific embodiment of the present disclosure;

[0057] Figure 10 A block diagram of a business object blood relationship risk warning device according to an embodiment of the present disclosure is shown;

[0058] Figure 11 A structural diagram of an electronic device for implementing the methods of embodiments of the present disclosure is shown. Detailed Implementation

[0059] To make the objectives, technical solutions, and advantages of this disclosure clearer, the disclosure will be further described in detail below with reference to specific embodiments and accompanying drawings. Here, the illustrative embodiments and descriptions of this disclosure are used to explain this disclosure, but are not intended to limit this disclosure.

[0060] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0061] All information, data, and signals disclosed herein are authorized by the user or by all parties, and the collection, use, and processing of such data comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0062] As mentioned earlier, enterprises typically use business management systems to manage data for various business (objects). This data includes, but is not limited to, information such as the business's name, version, category, scope of application, and status. Within an enterprise, dedicated maintenance personnel are usually responsible for manually maintaining and updating this business data.

[0063] However, as businesses grow and the number of operations increases dramatically, complex networks of dependencies emerge between them. For example, business A might rely on business B to perform its intended functions, while business C might simultaneously rely on business A to perform its intended functions. In this scenario, a change in the state of any one business can have a cascading effect on its related businesses. For instance, if the state of business A changes, it could directly impact the normal operation of business C.

[0064] The inventors of this disclosure recognized that while existing business management systems record basic business data and may even record the call relationships between different business processes, they lack effective analysis and early warning mechanisms, especially automated risk warning mechanisms. This results in the business management system's inability to proactively detect and warn of potential operational risks, leading to significant systemic risks when making business decisions, such as launching, decommissioning, or updating data for business processes. For example, a company might decommission business A on a certain day but fail to promptly discover that business C, expected to launch a month later, requires calls to business A to achieve its intended functions. When business C is launched to users a month later, some functions of business C malfunction, leading to user complaints and causing an operational incident.

[0065] Furthermore, the inventors of this disclosure have realized that when an enterprise involves multiple business lines, the boundaries between these lines become increasingly blurred, and cross-line business operations often form more complex dependencies. In some scenarios known to the inventors, different maintenance personnel are responsible for the data maintenance and updates of their respective business lines. This method of simultaneous data maintenance and updates across multiple business lines exacerbates the risk of operational incidents.

[0066] In response, this disclosure proposes a scheme for risk identification and early warning of the lineage relationship of business objects based on preset risk rules. This solves the problem that existing business management systems lack an effective risk management mechanism when dealing with complex dependencies. It enables timely discovery and early warning of potential risks in the network of business objects across business lines, reducing or even eliminating potential risks caused by manually maintaining a large amount of business object information.

[0067] In this disclosure, the term "blood relationship" does not refer to the blood relationship in the usual sense of biology or human sciences. The "blood relationship" described in this disclosure is applicable to the field of computer technology and has the normal meaning understood by those skilled in the art. As an example, the "blood relationship" described herein can be used to describe nested use, interdependence, or derivative iteration relationships between business objects. For example, business object A may depend on the functionality of business object B, while business object C depends on business object A; this dependency relationship is what is referred to as the "blood relationship" in this invention.

[0068] In some embodiments of this disclosure, reference is made to Figure 1 This invention discloses a method for risk warning of business object lineage relationships according to an embodiment of the present disclosure. The method can be used in, but is not limited to, a data management system and a business management system. The method may include at least the following 110, 130 and 140.

[0069] 110: Determine the lineage of the target business object based on the lineage database.

[0070] In this embodiment of the disclosure, the lineage of a target business object can be determined from a pre-established business object lineage database.

[0071] In this disclosure, the term "business object" has a broad meaning within the field of computer technology, including but not limited to various digital objects managed and processed in enterprise data processing systems, business management systems, business decision-making systems, etc. These business objects may include, but are not limited to, various applications, cloud service business objects, data (sources), service components, algorithm models, middleware, configuration files, virtual goods, or combinations thereof, or may be individually abstracted and defined as at least one of the modules / components / units of a business object. Those skilled in the art should understand that the business objects described in this disclosure are digital business objects and do not include physical business objects. However, as needed, the business objects in this disclosure may include digital representations of physical business objects or virtualized objects corresponding to physical business objects, such as data record forms (including business object attributes or parameters), simulation models, digital twins, etc., of various physical business objects (such as systems, devices, modules, components, parts).

[0072] In this embodiment, the business object lineage database includes a database or data structure that persistently stores and manages business information data and inter-business dependency data related to various businesses involved in the enterprise. In this embodiment, the lineage database includes, but is not limited to, graph databases and relational databases, etc. This disclosure does not limit the construction method or specific structure of the business object lineage database.

[0073] In some embodiments of this disclosure, the business object lineage database may include multiple lineage nodes corresponding one-to-one with multiple business objects and the dependencies between these multiple lineage nodes. In this embodiment, the lineage node may include a data structure encapsulating business attribute information of the corresponding business object, wherein the business attribute information includes, but is not limited to: the business object's identifier, business name, business version, business category, business scope of application, business status, etc. In a specific example, the object lineage database may include a lineage node A corresponding to "order payment business": "{"nodeId":"001","Info":{"name":"order payment service","version":"1.1.0","category":"payment service","scope":["B-end","C-end"],"status":"online"}}". It should be understood that the above lineage node is only an example, and this disclosure does not limit the specific format or encapsulation method of the lineage node.

[0074] In this embodiment of the disclosure, the business object lineage database may record the dependency relationships between two lineage nodes. It should be understood that the dependency relationships between the lineage nodes may correspond to the dependency relationships between the business objects associated with those lineage nodes. These dependency relationships may include, but are not limited to, various forms of interaction relationships such as business call relationships, data exchange relationships, and resource sharing relationships, and this disclosure does not impose any limitations on them.

[0075] In this embodiment of the disclosure, the term "direct dependency" refers to a dependency relationship arising from direct calls or data exchanges between business objects. In one example, if business object A directly calls the functions of business object B, uses the data of business object B, or shares the resources of business object B, then business object A can be said to directly depend on business object B.

[0076] In this embodiment of the disclosure, the term "indirect dependency" refers to a dependency relationship between a business object and other business objects that arise indirectly through the business object's dependence on an intermediate business object. In one example, if business object A directly calls data from business object B, and business object B directly depends on the functionality of business object C, then business object A can be said to indirectly depend on business object C.

[0077] In some embodiments of this disclosure, based on the aforementioned dependencies, the concepts of "upstream" and "downstream" are further introduced to describe the direction of dependencies between related nodes, depending on the specific dependencies: A business providing basic functions or services can be referred to as an "upstream business," and a business that depends on and invokes the functions of an upstream business can be referred to as a "downstream business." Correspondingly, the related nodes corresponding to "upstream businesses" can be referred to as "upstream related nodes," and the related nodes corresponding to "downstream businesses" can be referred to as "downstream related nodes." It should be understood that this "upstream" and "downstream" relationship can be caused by direct dependencies or indirect dependencies.

[0078] In a specific example, the data processing business service provides basic data processing capabilities as an upstream business, and the data analysis business service relies on and calls the data processing service to complete the data analysis function as a downstream business, thus forming a dependency chain from "data processing business service to data analysis business service". The data processing business service is the upstream business of the data analysis business service, and the data analysis business service is the downstream business of the data processing business service.

[0079] In some embodiments of this disclosure, the business object lineage database can record the dependencies between lineage nodes in various forms, including but not limited to recording the dependencies between lineage nodes in the form of embedded lineage nodes, independent dependency tables, graph structures, etc. This disclosure does not limit this. Continuing with the previous specific example, lineage node A in the lineage database has the following direct dependency data embedded: "downstream":["002","003"]".

[0080] In this embodiment of the disclosure, the lineage relationship of the target business object determined from the pre-established business object lineage relationship database may include: a lineage relationship node dataset and a dependency relationship dataset related to the target business object.

[0081] In some embodiments of this disclosure, the lineage node dataset and dependency dataset can be obtained from a lineage database. In one example, for a MySQL relational lineage database, existing lineage node tables and dependency tables can be directly queried using SQL queries to obtain the lineage node dataset and dependency dataset of the target business object. In another example, for a Neo4j graph database-type lineage database, graph traversal queries can be performed using the Cypher query language to obtain the lineage node dataset and dependency dataset of the target business object. It should be understood that the query method varies depending on the construction method and data structure of the lineage database, lineage nodes, and dependencies; this disclosure does not impose any limitations on this.

[0082] 130: Based on preset risk rules, identify the risk of business relationship between target business objects.

[0083] In this embodiment of the disclosure, preset risk rules can be applied to analyze and evaluate the blood relationship of the target business object.

[0084] In this embodiment of the disclosure, the risk rule can define a specific judgment rule for whether there is a rule between dependent blood relationship nodes.

[0085] In some embodiments of this disclosure, the risk rules can define comparison criteria for node attributes and constraints for dependencies between dependent related nodes, and determine the existence of risk when related nodes do not meet the comparison criteria or constraints. In one example, a risk is identified when the version difference between upstream and downstream related nodes exceeds the compatibility range; otherwise, no risk exists.

[0086] In some embodiments of this disclosure, the risk rule can define preset risk scenarios or risk ranges between dependent bloodline nodes, and determine the existence of risk when the combination of business attribute information of at least two bloodline nodes falls into a preset risk combination. In one example, for the business attribute information "business nature", a risk is identified as existing when the "business nature" value of the upstream bloodline node is "0" and the "business nature" value of the downstream bloodline node that has a dependency on it is "1".

[0087] In this embodiment of the disclosure, 110 and 130 may be triggered under various conditions. In some embodiments, when a new lineage node is added to the business object lineage database, the newly added lineage node is identified as a target lineage node, triggering lineage determination and risk identification. In some embodiments, when a request is made to delete a lineage node, the requested deletion lineage node is identified as a target lineage node, and lineage determination and risk identification are performed. In some embodiments, when the business attribute information of a lineage node is updated, the updated lineage node is identified as a target lineage node, and lineage determination and risk identification are performed. In other embodiments, a list of key risk-identifying lineage nodes may be preset, and lineage determination and risk identification may be performed periodically on the lineage nodes in the list at predetermined time intervals.

[0088] In some embodiments of this disclosure, the preset risk rules may include risk rules built into the business object management system. In some embodiments of this disclosure, the preset risk rules may also include user-defined risk rules, which will be described in detail below.

[0089] In some embodiments of this disclosure, reference is made to Figure 2 The above 130 may include at least 131 to 133 below.

[0090] 131: Determine the upstream and downstream relatives that a given relative node in the bloodline relationship of the target business object directly or indirectly depends on.

[0091] In some embodiments of this disclosure, referring to the description in S110 above, the lineage of the target business object may include a lineage node dataset and a dependency dataset related to the target business object. Accordingly, in this embodiment, the upstream and / or downstream lineage nodes that a given lineage node in the lineage of the target business object directly or indirectly depends on can be determined based on the relationship node dataset and the dependency dataset.

[0092] 132: Determine at least one business attribute information corresponding to a given bloodline node.

[0093] In some embodiments of this disclosure, business attribute information included in a given lineage node can be determined. As mentioned above, the business attribute information may include, but is not limited to: the identifier of the business object, the business name, the business version, the business category, the business scope of application, and the business status. In embodiments of this disclosure, one or more related business attribute information can be determined according to the specific needs of preset risk rules.

[0094] 133: Based on the business attribute information corresponding to upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information, the risk identification results for the business attribute information are obtained.

[0095] In some embodiments of this disclosure, risk identification (analysis) can be performed based on the business attribute information corresponding to the determined upstream and downstream kinship nodes, combined with corresponding preset risk rules, to obtain risk identification results (analysis results) for specific business attribute information. As an explanation and not a limitation, the risk identification results may reflect whether there is any risk to the upstream and downstream kinship nodes regarding specific business attribute information.

[0096] The above embodiments of this disclosure provide a general description of the risk identification steps of the embodiments of this disclosure. The following will further describe various types of risk identification in conjunction with multiple embodiments of this disclosure. Figures 3 to 6 To describe different types of risk identification.

[0097] In some embodiments of this disclosure, reference is made to Figure 3 This illustrates risk identification for the scope of application of the business object. In this embodiment, 130 may include at least 132' to 133' as described below.

[0098] 132': Determine the scope of application of the business object corresponding to the given lineage node in the business object lineage of the target business object.

[0099] In this embodiment, the scope of application of the business objects included in the given lineage node can be determined. The scope of application of the business objects should be interpreted broadly and may include any business attribute information related to the scope of application of the business objects. In one example, the scope of application of the business objects corresponds, for example, to the "scope of application" field included in the business attribute information of the lineage node. In a specific example, the "scope of application" field includes, for example, personal business, corporate business, domestic business, cross-border business, etc., and this disclosure does not impose any limitations thereon.

[0100] 133': Based on the intersection status of the applicable scope of business objects corresponding to upstream and downstream blood relationship nodes and the preset intersection rules, the risk identification results for the applicable scope of business objects are obtained.

[0101] In this embodiment, the intersection states of the business object's applicable scope include, but are not limited to: the business object's applicable scope of a downstream related node includes the business object's applicable scope of an upstream related node; the business object's applicable scope of an upstream related node includes the business object's applicable scope of a downstream related node; the business object's applicable scope of a downstream related node partially overlaps with the business object's applicable scope of an upstream related node; and the business object's applicable scope of a downstream related node is mutually exclusive with the business object's applicable scope of an upstream related node. In this embodiment, the business object management system can determine whether there is a risk of overlapping business object applicable scopes based on the intersection states and preset intersection rules.

[0102] In one example, the preset intersection rule may include: when the scope of application of the business objects of an upstream related node includes the scope of application of the business objects of a downstream related node, it is determined to be risk-free. In a specific example, the scope of application of the upstream node is "all businesses," and the scope of application of the downstream node is "personal businesses." The upstream node has the ability to handle the needs of all business scenarios of the upstream node, and in this case, it is determined to be risk-free.

[0103] In another example, the preset intersection rule may include: when the business object scope of a downstream related node includes the business object scope of an upstream related node, it is determined to be of medium risk. In a specific example, the upstream node's scope of application is "online payment business," and the downstream node's scope of application is "all payment businesses." The business logic of the upstream node may not be applicable to certain payment scenarios of the downstream node, in which case it is determined to be of medium risk.

[0104] In another example, the preset intersection rule may include: when the applicable scope of the business object of a downstream related node is mutually exclusive with that of an upstream related node, it is determined to be high-risk. In a specific example, the applicable scope of the upstream node is "enterprise business," and the applicable scope of the downstream node is "personal business." The two business scenarios are completely different, and the business logic is completely incompatible, which may lead to serious errors in business processing. In this case, it is determined to be high-risk.

[0105] Accordingly, in some embodiments of this disclosure, the 133' may include at least: determining whether the intersection state meets preset requirements.

[0106] As previously stated, the scope of application of the business object may include any attribute information related to the scope of application of the business object, and the preset requirements may also be set in multiple ways. In one example, the preset requirement may be set such that the scope of application of the business object of the downstream bloodline node includes the scope of application of the business object of the upstream bloodline node. In another example, the preset requirement may be set such that the scope of application of the business object of the upstream bloodline node includes the scope of application of the business object of the downstream bloodline node.

[0107] In some embodiments of this disclosure, reference is made to Figure 4 This illustrates risk identification for the status of business objects. In this embodiment, 130 may include at least the following 132” to 133”.

[0108] 132”: Determine the state of the business object corresponding to a given lineage node in the lineage of the target business object.

[0109] In this embodiment, the status of business objects included in the given lineage node can be determined, wherein the status of the business objects includes, but is not limited to, "available", "unavailable" and "to be enabled".

[0110] 133”: Based on the consistency status of the business object status corresponding to the upstream and downstream blood relationship nodes and the preset consistency rules, the risk identification result for the business object status is obtained.

[0111] In this embodiment, the consistency state is, for example, both consistent and inconsistent business object states. In some embodiments, the consistency rule may include determining a risk of business object inconsistency when the business object states are inconsistent, and conversely, determining no risk of business object inconsistency when they are consistent. In one example, the consistency state is, for example, both consistent and inconsistent business object states. In some embodiments, the consistency rule may include determining a risk of business object inconsistency when the business object states are inconsistent, and conversely, determining no risk of business object inconsistency when they are consistent. In a specific example, when the state of an upstream business object is "pending activation," while the state of a downstream business service that depends on that upstream business object is "activated," a risk of inconsistency is determined. Similarly, when the state of an upstream data service is "service suspended," while the state of a downstream data analysis service is "operating normally," a risk of inconsistency is also determined. Furthermore, when the state of an upstream payment service is "version upgrade in progress," while the state of a downstream order service is "normal service," a risk of inconsistency is also determined. These inconsistencies may lead to problems such as downstream business call failures, abnormal data processing, or service response timeouts.

[0112] In other embodiments of this disclosure, to address the inconsistency in the states of business objects, the consistency rule may further specify the states of business objects corresponding to upstream and downstream related nodes separately. In one example, to address the inconsistency between the states of upstream and downstream business objects, the consistency rule may include: when the state of the business object corresponding to the upstream business object is "available," and the state of the business object corresponding to the downstream related node is "unavailable," it is determined that there is no risk of a business object state in the upstream. As an explanation, and not a limitation, the downstream business object depends on the functionality of the upstream business object. The shutdown of the downstream business object reduces the operational pressure on its corresponding upstream business object and does not cause any adverse effects on the upstream business object; therefore, it can be determined that there is no risk of a business object state in the downstream.

[0113] In some embodiments of this disclosure, the business object lineage database also includes business object change record information corresponding to the lineage node, and the product change record information includes, but is not limited to, product attribute information before and after the change of the lineage node.

[0114] In this embodiment, reference Figure 5 This illustrates the risk identification for changes in business objects. In this embodiment, 130 may also include at least 134, 135, and 136 as described below.

[0115] 134: Determine the downstream relatives that a given relative node in the business object lineage of the target business object directly or indirectly depends on.

[0116] In some embodiments of this disclosure, the given bloodline node includes, but is not limited to, the bloodline node corresponding to the target business object and other bloodline nodes included in the determined bloodline relationship of the target business object.

[0117] 135: Retrieve the business object change record information corresponding to the given bloodline node and downstream bloodline node.

[0118] In some embodiments of this disclosure, business object change record information of the blood relationship node can be obtained. The business object change record information includes, but is not limited to, business object attribute information before and after the change of the blood relationship node. For a detailed description of the business object attribute information, please refer to the content in 110 above, which will not be repeated here.

[0119] 136: Based on the obtained business object change record information, obtain the risk identification results for business object changes.

[0120] In some embodiments of this disclosure, for any bloodline node, the current bloodline node information can be compared with the corresponding business object change record information to determine whether the bloodline node information is the latest updated information in the business object change record.

[0121] In some embodiments of this disclosure, when the bloodline relationship node information is not the latest updated information in the business object change record, it is determined that the bloodline relationship node has changed. The business object management system will update the business object change record based on the current information of the bloodline relationship node and determine that there is a risk of business object change. Conversely, it is determined that the bloodline relationship node has not changed and that there is no risk of business object change.

[0122] As previously stated, in some embodiments of this disclosure, the preset risk rules may further include user-defined risk rules. Accordingly, in some embodiments of this disclosure, such as... Figure 6 As shown, before identifying the risk of blood relations of the target business object based on preset risk rules, the business object blood relation risk warning method may further include the following 120.

[0123] 120: Obtain user-defined risk rule configuration and generate user-defined risk rules.

[0124] As previously stated, the preset risk rules may include user-defined risk rules. In some embodiments of this disclosure, user-defined risk rule configurations can be obtained, and user-defined risk rules can be generated based on these configurations. The risk rule configuration includes, but is not limited to, information such as risk name, risk field, upstream business object risk field judgment conditions, and downstream business object risk field judgment conditions. In this embodiment, the risk field may correspond to one or more business attribute information of a business object. The business attribute information includes, but is not limited to, the business attribute information described in section 110 above. The judgment conditions include, but are not limited to, specific risk values ​​(such as a certain rate rule type code), value ranges (such as a rate type code range), and may also be an enumerated set of values ​​(such as a set of allowed rate rule type codes).

[0125] Accordingly, in some embodiments of this disclosure, reference is made to Figure 7 This illustrates risk identification for user-defined risk rules. In this embodiment, 130 may also include at least 137 and 138 as described below.

[0126] 137: Determine the risk field value of at least one business object attribute information corresponding to a given lineage node in the lineage relationship of the target business object.

[0127] As mentioned earlier, user-defined risk rules can specify risk fields for business object attribute information. Accordingly, in this embodiment, the risk field values ​​for the business object attribute information of a given lineage node can be determined. In one example, if the user-defined risk rule includes a risk field "rate type," the business object management system will determine the risk field value corresponding to the "rate type" of the given lineage node.

[0128] 138: Based on whether the risk field values ​​of the upstream and downstream related nodes match the risk field thresholds of the upstream and downstream business objects, a user-defined risk identification result is obtained.

[0129] In this embodiment, after determining the risk field value specified in the given blood relationship node, the risk field value can be matched with the upstream / downstream risk field threshold in the user-defined risk rule. The risk identification result is determined based on whether the risk field value in the given blood relationship node matches the upstream / downstream risk field judgment condition: if the judgment condition is matched, it is determined that there is a user-defined risk; otherwise, there is no user-defined risk.

[0130] In some embodiments, the business object management system can identify upstream / downstream relatives that have a direct dependency relationship with the relatives corresponding to the target business object, and determine whether the risk field value of each upstream / downstream relative node hits the upstream / downstream risk field threshold. If it does, it is determined that there is a user-defined risk; otherwise, there is no user-defined risk. In one example, the target business object is "business object A," and the business object management system determines that its directly associated upstream / downstream relatives are "business object B" and "business object data source C." If the risk field value included in either of them hits the upstream / downstream risk field threshold, it is determined that there is a user-defined risk; otherwise, there is no user-defined risk.

[0131] In other embodiments, the business object management system can further identify upstream / downstream lineage nodes that have an indirect dependency relationship with the target business object, and determine whether the risk field value of the upstream / downstream lineage node hits the upstream / downstream risk field threshold to determine the risk identification result. In one example, the target business object is "business object C", the upstream lineage node directly associated with it is "business object B", and the upstream lineage node directly associated with "business object B" is "business object A". That is, "business object C" is indirectly associated with "business object A". If the risk field value in "business object A" hits the upstream risk field threshold, it is determined that there is a user-defined risk; otherwise, there is no user-defined risk.

[0132] 140: Based on the risk identification results, generate risk warning information that is related to the blood relationship of the target business object.

[0133] In this embodiment of the disclosure, the risk identification result of the business object is obtained, for example, by step 130 and its sub-steps described above. In this embodiment, the risk identification result can be transformed into specific risk warning information, which includes, but is not limited to, risk level, risk description text related to the relationship with the target business object, and possible impact. In a specific example, the risk identification warning information for the scope of application of the business object is, for example, "Upstream business object A is 'available,' downstream business object B is 'unavailable'; Risk level: 'High'; Possible impact: 'Upstream business object A is functionally abnormal.'"

[0134] In other embodiments of this disclosure, such as Figure 8 As shown in the present disclosure, the business object blood relationship risk warning method may further include the following 150.

[0135] 150: Combine the visualization interface for displaying the bloodline relationship of business objects with the risk warning interface.

[0136] In some embodiments of this disclosure, the generated risk warning information can be visualized in a risk warning interface. In one example, refer to... Figure 9 For example, risk warning information can be displayed in the form of a block diagram. In some embodiments, when visualizing the generated risk warning information, the risk warning information can also be displayed in different colors (not shown) according to the risk level of the risk warning information.

[0137] In some embodiments of this disclosure, while visualizing the generated risk warning information in the risk warning interface, a business object lineage visualization interface can also be displayed. In this embodiment, the business object lineage visualization interface has a dependency flow graph presenting the determined lineage of the target business object. The dependency flow graph includes the plurality of lineage nodes and directed lines between each lineage node. In one example, the direction of the arrow is used to indicate the direction of the dependency relationship. In a specific example, refer to... Figure 9The diagram shows a visualization of the business object lineage relationships displayed on the left side of the risk warning interface. It shows 26 lineage relationship nodes (see the 26 gray cuboids in the figure), where each lineage relationship node corresponds to a business object. There are 36 directed lines between the lineage relationship nodes, which show the dependencies between them. Each directed line includes a starting arrow, a main body of the directed line, an ending arrow, and a directed line number. For example, the diagram shows a directed line 1 pointing from lineage relationship node D (corresponding to business object D) to lineage relationship node A (corresponding to business object A). This directed line 1 indicates that lineage relationship node D directly depends on lineage relationship node A. Other directed lines will not be described in detail.

[0138] In other embodiments of this disclosure, the generated risk warning information can be displayed in the form of a block diagram on the risk warning interface. In one specific example, refer to... Figure 9 The diagram shows a visualization of the business object lineage on the left side of the risk warning interface. It schematically illustrates four risk warning diagrams, including a high-risk warning message: "Target business object C's business scope is personal business, upstream business object B's business scope is enterprise business. The business scopes of target business object C and upstream business object B are mutually exclusive! Please assess the rationality of the business scope configuration!" It should be understood that the number of risk warning diagrams and the specific text displayed in the above specific embodiment are only illustrative. In other embodiments, the risk warning interface may further include more risk warning diagrams and display more risk warning text, such as... Figure 9 The risk warning text "Medium Risk - User-defined Risk 2" is used to inform users of the risks corresponding to user-defined rules, and the level is medium risk; for example, Figure 9 The risk warning text "Low Risk - Business Object Status Risk 2" is used to indicate the risk identification result of the business status, and the level is low risk; for example... Figure 9 The risk warning text "Attention - Risk of Change in Business Target" is used to indicate the risk identification result of the change in business target, and the level is "Attention".

[0139] In other embodiments of this disclosure, such as Figure 8 As shown in the embodiments of this disclosure, a human-computer interaction scheme for risk warning information and business object blood relationship is also provided. The business object blood relationship risk warning method may further include the following 160.

[0140] 160: In response to user interaction with risk warning information, the nodes and directed connections related to the selected risk warning information are highlighted in the dependency flow diagram of the business object lineage visualization interface.

[0141] In some embodiments of this disclosure, in response to a user's interactive operation on risk warning information, such as moving the operation cursor to the risk warning information or clicking the operation cursor to select the risk warning information, the business object relationship system can also simultaneously highlight the blood relationship nodes and directed connections related to the selected risk warning information in the business object blood relationship visualization interface that is displayed together.

[0142] In one example, reference Figure 9 For example, when a user clicks Figure 9 When the high-risk warning information box diagram on the right side of the page is displayed, the corresponding bloodline nodes A and C1 that have a direct dependency relationship with the target business object C in the business object bloodline visualization interface on the left side of the page are highlighted. The directed connection lines 13 and 241 between the target business object C and the bloodline nodes A and C1 are also highlighted. The directed connection lines 13 and 241 between the bloodline nodes D and E1 that have an indirect dependency relationship with the target business object C are also highlighted.

[0143] In this embodiment, risk warning information can be presented to users in an intuitive way and interactive functions can be provided to facilitate users' in-depth understanding and analysis of risk situations.

[0144] The business object lineage risk warning method of this disclosure not only visualizes complex business object dependencies but also incorporates multi-dimensional risk analysis, enabling a more comprehensive and accurate grasp of the dependencies between business objects and timely identification of potential risks. Furthermore, by introducing preset risk rules, this method achieves timely detection and warning of potential risks in cross-business line business object networks, effectively improving the security and reliability of business object management.

[0145] 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. Furthermore, these methods themselves can also be combined or spliced ​​together to form new methods.

[0146] To better understand the specific application of the embodiments of this disclosure, the implementation of the above method will be described in detail below with reference to specific examples.

[0147] First, the business object management system receives a request from a user to perform risk warning analysis on "Model Business Object A", version V1.0.

[0148] In response to the request from maintenance personnel to perform risk warning analysis on target business object A received by the business object management system, the business object management system retrieves information related to target business object A from the business object lineage database to determine its lineage: the target business object directly depends on upstream business object B and upstream business object C, while downstream business object D depends on the target business object.

[0149] Subsequently, the business object management system retrieves the user-defined risk configuration: "RiskRule1{level:HIGH,name:"Rate Rule Risk",checkField:"charge_rule",upstreamThreshold:"0",downstreamThreshold:"1",warningTemplate:"{upstreamObject} rate rule is {0}, downstreamObject} rate rule is {1}, please pay attention!", where "0" is used to identify different types of rate rules. The business object management system converts this configuration into an executable risk rule for subsequent risk identification. When it is found that the charge_rule field values ​​of upstream and downstream business objects match the configured thresholds, for example, when the charge_rule field value of the upstream business object is "0" and the charge_rule field value of the downstream business object is "1", a high-risk warning will be triggered. The business object management system also retrieves the preset risk rules in the system, including business scope risk rules and business status risk rules.

[0150] The business object management system then identifies risks related to the lineage of target business objects based on the aforementioned risk rules: For user-defined billing rule risk rules: the system obtains the billing rule field value of upstream business object B as "0", matches the upstream business object's risk field threshold, and triggers a risk warning. For business scope risk rules: the system determines that the target business object's business scope is "personal business," while the upstream business object B's business scope is "enterprise business." Based on the preset intersection rule: "When the business object scope of a downstream lineage node is mutually exclusive with the business object scope of an upstream lineage node, it is judged as high risk," thus determining the existence of high risk and triggering a risk warning. For business status risk rules: the system determines that the target business object's business status is "enabled," while the upstream business object C's business status is "pending activation," determining that the business statuses of the target business object and upstream business object C are inconsistent, triggering a risk warning. For business object change risk: the system discovers that upstream business object C recently underwent a significant update that may affect the functionality of the target business object, triggering a risk warning.

[0151] Subsequently, the business object management system generated the following risk warning information based on the above risk identification results:

[0152] "[High Risk]: The target business object's billing rule is based on business traffic, while the upstream business object B's billing rule is based on the number of times the business is used. The billing rules of the target business object and the upstream business object B are inconsistent! Please pay attention to coordinating the billing rules!"

[0153] "[High Risk] The target business object's business scope is personal business, while the upstream business object B's business scope is enterprise business. The business scopes of the target business object and the upstream business object B are mutually exclusive! Please evaluate the rationality of the business scope configuration!"

[0154] "[Low Risk] The target business object's business status is 'Enabled,' and the upstream business object C's business status is 'Pending Enabling'! Please note whether upstream business object C needs to be enabled!"

[0155] "[Attention] Upstream business object C changed on 2024-01-01! Please pay attention!"

[0156] Finally, refer to Figure 9 The business object management system displays these risk warning information in the risk warning interface and highlights the relevant nodes and connections in the visualization interface of the business object lineage.

[0157] In some embodiments of this disclosure, such as Figure 10 As shown, a business object blood relationship risk warning device 1000 is also provided, which may include a determination unit 1010, an identification unit 1020 and a generation unit 1030.

[0158] The determining unit 1010 is configured to determine the lineage relationship of the target business object based on the business object lineage relationship database, wherein the business object lineage relationship database includes multiple lineage relationship nodes that correspond one-to-one with multiple business objects and the direct dependency relationships between the multiple lineage relationship nodes, and the lineage relationship nodes include the business attribute information of the corresponding business object.

[0159] The identification unit 1020 is configured to identify the blood relationship of the target business object based on preset risk rules.

[0160] The generation unit 1030 is configured to generate risk warning information that is associated with the business object lineage of the target business object based on the risk identification result.

[0161] The corresponding apparatus for processing business object lineage relationships in this disclosure can be implemented through software, hardware, or a combination of both. In some embodiments, the apparatus can be a standalone system or integrated into an existing business object management system. For example, in terms of software implementation, the apparatus can be an application running on a server or cloud platform, including data processing modules, query modules, and visualization interface modules. These modules can be implemented using programming languages ​​(such as Java, Python, etc.) and may use database management systems (such as MySQL, MongoDB, etc.) to store and manage business object lineage relationship data. In terms of hardware, the apparatus may include components such as processors, memory, and network interfaces to support software operation and data processing. Furthermore, it may include a dedicated graphics processing unit (GPU) to improve the rendering efficiency of complex business object lineage relationship graphs.

[0162] The apparatus, components, modules, units, and features described in the embodiments of this disclosure can be incorporated into the methods of the embodiments of this disclosure in a non-contradictory manner, and the methods, steps, sub-steps, and features described in the embodiments of this disclosure can also be incorporated into the apparatus of the embodiments of this disclosure in a non-contradictory manner.

[0163] In embodiments of this disclosure, an electronic device may also be provided, including: a processor and a memory storing a computer program, the processor being configured to perform the method of any of the embodiments of this disclosure when running the computer program.

[0164] Figure 11 The illustration shows a method or electronic device 1100 that can implement embodiments of the present disclosure. In some embodiments, it may include more or fewer electronic devices than illustrated. In some embodiments, it may be implemented using a single or multiple electronic devices. In some embodiments, it may be implemented using cloud-based or distributed electronic devices.

[0165] like Figure 11As shown, the electronic device 1100 includes a processor 1101, which can perform various appropriate operations and processes based on programs and / or data stored in read-only memory (ROM) 1102 or programs and / or data loaded from storage portion 1108 into random access memory (RAM) 1103. The processor 1101 may be a multi-core processor or may contain multiple processors. In some embodiments, the processor 1101 may include a general-purpose 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. Various programs and data required for the operation of the electronic device 1100 are also stored in RAM 1103. The processor 1101, ROM 1102, and RAM 1103 are interconnected via bus 1104. An input / output (I / O) interface 1105 is also connected to bus 1104.

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

[0167] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, touchscreen, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1110 as needed so that computer programs read from them can be installed into storage section 1108 as needed. Figure 11 The diagram only shows a portion of the components and does not imply that the computer system 1100 includes only these components. Figure 11 The components shown.

[0168] The systems, devices, modules, or units described in the above embodiments can be implemented by a computer or its associated components. The computer may be, for example, a mobile terminal, smartphone, personal computer, laptop computer, in-vehicle human-machine interface device, personal digital assistant, media player, navigation device, game console, tablet computer, wearable device, smart TV, Internet of Things system, smart home, industrial computer, server, or a combination thereof.

[0169] Although not shown, in embodiments of this disclosure, a program product is provided, the program product comprising a computer program configured to be run to implement the methods of any embodiment of this disclosure.

[0170] Although not shown, in embodiments of this disclosure, a storage medium is provided storing a computer program configured to be executed to implement the methods of any of the embodiments of this disclosure.

[0171] The storage media in embodiments of this disclosure include articles that are permanent and non-permanent, removable and non-removable, capable of storing information by any method or technology. 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0172] The methods, programs, systems, apparatuses, etc., of the embodiments of this disclosure can be executed or implemented in one or more networked computers, or practiced in a distributed computing environment. In the embodiments of this specification, in these distributed computing environments, tasks can be performed by remote processing devices connected via a communication network.

[0173] Those skilled in the art will understand that the embodiments described in this specification can be provided as methods, systems, or computer program products. Therefore, those skilled in the art will realize that the functional modules / units or controllers and related method steps described in the above embodiments can be implemented in software, hardware, or a combination of both.

[0174] Unless explicitly stated otherwise, the actions or steps of the methods or procedures described in the embodiments of this disclosure do not necessarily 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.

[0175] This document describes several embodiments of the present disclosure; however, for the sake of brevity, the descriptions of the embodiments are not exhaustive, and identical or similar features or portions between the embodiments may be omitted. In this document, "one embodiment," "some embodiments," "example," "specific example," or "some examples" refers to at least one embodiment or example applicable to the present disclosure, but not all embodiments. The above terms do not necessarily refer to the same embodiment or example. Without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of the different embodiments or examples.

[0176] The exemplary systems and methods of this disclosure have been specifically shown and described with reference to the foregoing embodiments, and are merely examples of the best mode for implementing the systems and methods. Those skilled in the art will understand that various changes can be made to the embodiments of the systems and methods described herein without departing from the spirit and scope of this disclosure as defined in the appended claims when implementing the systems and / or methods.

Claims

1. A method for early warning of blood relationship risk of business objects, characterized in that, include: The lineage relationship of the target business object is determined based on the business object lineage relationship database. The business object lineage relationship database includes multiple lineage relationship nodes that correspond one-to-one with multiple business objects and the dependency relationships between the multiple lineage relationship nodes. The dependency relationships between the multiple lineage relationship nodes correspond to the dependency relationships between the business objects associated with the multiple lineage relationship nodes. The lineage relationship node includes the business attribute information of the corresponding business object. Based on preset risk rules, risk identification is performed on the bloodline relationships of the target business object, including: determining the upstream and downstream bloodline nodes that a given bloodline node in the bloodline relationship of the target business object directly or indirectly depends on; determining at least one business attribute information corresponding to the given bloodline node; and, based on the business attribute information corresponding to the upstream and downstream bloodline nodes and the preset risk rules corresponding to the business attribute information, obtaining a risk identification result for the business attribute information when the combination of business attribute information of the upstream and downstream bloodline nodes falls within the risk rules, wherein the risk rules are preset risk scenarios or risk ranges between upstream and downstream bloodline nodes; and generating risk warning information associated with the bloodline relationship of the target business object based on the risk identification result.

2. The method of claim 1, wherein, The preset risk rules include user-defined risk rules; The method for early warning of risks related to blood relations of business objects also includes: Obtain user-defined risk rule configuration and generate user-defined risk rules. The risk rule configuration includes at least a risk name, a risk field, upstream business object risk field judgment conditions, and downstream business object risk field judgment conditions, wherein the risk field corresponds to at least one business attribute information.

3. The method of claim 2, wherein, The risk identification of the blood relationship of the target business object based on preset risk rules includes: Determine the risk field value of at least one business attribute information corresponding to a given lineage node in the lineage relationship of the target business object; Based on whether the risk field values ​​of the upstream and downstream related nodes match the risk field judgment conditions of the upstream business object and the downstream business object, a user-defined risk identification result is obtained.

4. The method of claim 1, wherein, The business attribute information includes the scope of business application; wherein... Determining at least one business attribute information corresponding to the given blood relationship node includes: Determine the scope of business application corresponding to the given blood relationship node; The step of obtaining a risk identification result for the business attribute information based on the business attribute information corresponding to upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information includes: Based on the intersection status of the business application scopes corresponding to the upstream and downstream blood relationship nodes and the preset intersection rules, the risk identification results for the business application scope are obtained.

5. The method of claim 1, wherein, The business attribute information includes business status; wherein... Determining at least one business attribute information corresponding to the given blood relationship node includes: Determine the business status corresponding to a given lineage node in the lineage relationship of the target business object; The step of obtaining a risk identification result for the business attribute information based on the business attribute information corresponding to upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information includes: Based on the consistency status of the business status corresponding to the upstream and downstream blood relationship nodes and the preset consistency rules, the risk identification result for the business status is obtained.

6. The method of claim 1, wherein, The business object lineage database also includes business object change record information corresponding to the lineage nodes; The step of identifying the risk of blood relations of the target business object based on preset risk rules includes: Determine the upstream relatives that a given relative node in the lineage of the target business object directly or indirectly depends on; Obtain the business object change record information corresponding to the given bloodline node and the upstream bloodline node; Based on the obtained business object change record information, the risk identification results for business object changes are obtained.

7. The method according to any one of claims 1 to 6, characterized in that, After generating risk warning information associated with the blood relationship of the target business object, the method further includes: The system combines a visualization interface for displaying the lineage relationships of business objects with a risk warning interface. The risk warning interface displays the risk warning information, while the visualization interface for displaying the lineage relationships of the business objects has a dependency flow graph that presents the determined lineage relationships of the target business objects. The dependency flow graph includes the multiple lineage relationship nodes and directed lines between each lineage relationship node.

8. The method of claim 7, wherein, The method further includes: In response to user interaction with risk warning information, the dependency flow graph in the business object lineage visualization interface highlights the lineage nodes and directed connections related to the selected risk warning information.

9. A business object blood relationship risk early warning device, characterized in that, The business object blood relationship risk warning device includes: The determining unit is configured to determine the lineage relationship of a target business object based on a business object lineage relationship database. The business object lineage relationship database includes multiple lineage relationship nodes that correspond one-to-one with multiple business objects and the dependency relationships between the multiple lineage relationship nodes. The dependency relationships between the multiple lineage relationship nodes correspond to the dependency relationships between business objects associated with the multiple lineage relationship nodes. The lineage relationship node includes business attribute information of the corresponding business object. An identification unit is configured to perform risk identification on the lineage relationship of the target business object based on preset risk rules. The identification unit is further configured to determine the upstream and downstream lineage relationship nodes that a given lineage relationship node in the lineage relationship of the target business object directly or indirectly depends on, determine at least one business attribute information corresponding to the given lineage relationship node, and, based on the business attribute information corresponding to the upstream and downstream lineage relationship nodes and the preset risk rules corresponding to the business attribute information, obtain a risk identification result for the business attribute information when the combination of business attribute information of the upstream and downstream lineage relationship nodes falls into the risk rules. The risk rules are preset risk situations or risk ranges between upstream and downstream lineage relationship nodes. The generation unit is configured to generate risk warning information that is related to the blood relationship of the target business object based on the risk identification results.

10. An electronic device, characterized in that, include: A processor and a memory storing a computer program, the processor being configured to implement the method as described in any one of claims 1-8 when the computer program is executed.

11. A program product comprising a computer program, wherein, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-8.

Images