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

Abstract

The invention discloses a business object blood relationship risk early warning method, which comprises the steps of determining a blood relationship of a target business object according to a business object blood relationship library, the business object blood relationship library comprises a plurality of blood relationship nodes in one-to-one correspondence with a plurality of business objects and a direct dependency relationship among the plurality of blood relationship nodes, and the blood relationship nodes comprise business attribute information of the corresponding business objects; performing risk identification on the blood relationship of the target business object based on a preset risk rule; and generating risk early warning information associated with the blood relationship of the target business object according to a risk identification result. According to the scheme disclosed by the invention, the potential blood relationship risk in the business object network can be effectively discovered and early warned in time.

Description

Technical Field

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

[0002] As the types and scale of enterprise businesses continue to expand, in order to manage the data of these businesses, enterprises usually use business management systems to store and maintain the data information of each business. These businesses often have interdependencies and form a complex dependency network. In actual business operations, the status change of a business has the risk of adversely affecting its related businesses.

[0003] However, the existing business management system only records the basic data of the corresponding business in units of business objects, but lacks analysis of the dependencies between business objects and risk warning mechanisms, which makes the system unable 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 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

[0006] Accordingly, the present disclosure provides a business object blood relationship risk early warning method, which includes:

[0007] Determining the kinship of the target business object according to a business object kinship library, wherein the business object kinship library includes a plurality of kinship nodes corresponding to a plurality of business objects one by one and dependency relationships between the plurality of kinship nodes, and the kinship nodes include business attribute information of the corresponding business objects;

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

[0009] Based on the risk identification result, risk warning information associated with 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 a preset risk rule includes:

[0011] Determine the upstream and downstream blood relationship nodes on which a given blood relationship node in the blood relationship of the target business object directly or indirectly depends;

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

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

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

[0015] The business object blood relationship risk early warning method also includes:

[0016] Obtain a user-defined risk rule configuration and generate a user-defined risk rule, wherein the risk rule configuration includes at least a risk name, a risk field, an upstream business object risk field determination condition, and a downstream business object risk field determination condition, 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 a preset risk rule includes:

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

[0019] A user-defined risk identification result is obtained based on whether the risk field values ​​of the upstream and downstream blood relationship nodes match the upstream business object risk field determination condition and the downstream business object risk field determination condition.

[0020] Optionally, the service attribute information includes a service applicable scope; wherein,

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

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

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

[0024] According to the intersection status of the business application scopes corresponding to the upstream and downstream blood relationship nodes and the preset intersection rules, a risk identification result for the business application scope is obtained.

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

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

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

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

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

[0030] Optionally, the business object blood relationship library also includes business object change record information corresponding to the blood relationship node;

[0031] The risk identification of the blood relationship of the target business object based on the preset risk rules includes:

[0032] Determine an upstream blood relationship node on which a given blood relationship node in the blood relationship of the target business object directly or indirectly depends;

[0033] Obtaining business object change record information corresponding to the given blood relationship node and the upstream blood relationship node;

[0034] Based on the acquired business object change record information, a risk identification result for the business object change is obtained.

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

[0036] In combination with a visualization interface for displaying the blood relationship of business objects and a risk warning interface, the risk warning interface displays the risk warning information, and the visualization interface for displaying the blood relationship of business objects has a dependency flow graph that presents the blood relationship of the determined target business objects, and the dependency flow graph includes the multiple blood relationship nodes and directed connections between the blood relationship nodes.

[0037] Optionally, the business object blood relationship risk early warning method further includes:

[0038] In response to the user's interactive operation on the risk warning information, the blood relationship nodes and directed lines related to the selected risk warning information are highlighted in the dependency flow diagram in the business object blood relationship visualization interface.

[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] a determination unit configured to determine the blood relationship of the target business object according to a business object blood relationship library, wherein the business object blood relationship library includes a plurality of blood relationship nodes corresponding to a plurality of business objects one by one and dependency relationships between the plurality of blood relationship nodes, and the blood relationship nodes include business attribute information of the corresponding business objects;

[0041] an identification unit configured to perform risk identification on the blood relationship of the target business object based on a preset risk rule;

[0042] The generating unit is configured to generate risk warning information associated with the blood relationship of the target business object according to the risk identification result.

[0043] In a third 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 when the computer program is executed.

[0044] In a fourth 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 is implemented.

[0045] The business object lineage risk warning method proposed in the disclosed embodiment solves the problem of the existing system lacking an effective risk management mechanism when dealing with complex dependencies by identifying and warning risks in business object lineages based on preset risk rules, and achieves timely discovery and warning of potential risks in cross-business line business object networks, thereby reducing or even eliminating potential risks caused by manual maintenance of large amounts of business object information.

[0046] 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

[0047] 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:

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

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

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

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

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

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

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

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

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

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

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

[0059] 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.

[0060] 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.

[0061] 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.

[0062] As mentioned above, current enterprises usually use business management systems to manage data of various businesses (objects), including but not limited to the name, version, category, scope of application and status of the business. In enterprises, special maintenance personnel are usually responsible for manually maintaining and updating the data of these businesses.

[0063] However, as the scale of the enterprise expands, the number of businesses increases dramatically, and a complex network of dependencies is formed between the businesses. For example, business A may rely on calling business B to achieve its expected business functions, while business C also relies on calling business A to achieve its expected business functions. In this case, the status change of any business may have a chain effect on the businesses associated with it. For example, if the status of business A changes, it may directly affect the normal operation of business C.

[0064] The inventors of the present disclosure realize that although the existing business management system records the basic data of the business and may even record the calling relationship between different businesses, it lacks an effective analysis and early warning mechanism, especially an automated risk early warning mechanism. This results in the business management system being unable to proactively discover and warn of potential operational risks. When making business decisions, such as when performing operations such as going online, going offline, or updating data on a business, it faces huge systemic risks. For example, one day, the enterprise took business A offline, but failed to discover in time that business C, which was expected to be online in a month, must call business A to implement the expected function. When business C was launched to users one month later, some functions of user business C were abnormal, which triggered user complaints and led to operational accidents.

[0065] In addition, the inventors of the present disclosure further realized that when an enterprise involves multiple business lines, the boundaries between business lines gradually blur, and businesses across business lines often form more complex dependencies. In some scenarios known to the inventors, different business lines are managed by different maintenance personnel who are responsible for data maintenance and updates of businesses in their respective business lines. This method of synchronous data maintenance and updates for multiple business lines increases the risk of causing operational accidents.

[0066] In this regard, the disclosed embodiments propose a solution for risk identification and early warning of business object lineage relationships based on preset risk rules, which solves the problem that existing business management systems lack an effective risk management mechanism when dealing with complex dependencies, and achieves timely discovery and early warning of potential risks in business object networks across business lines, thereby reducing or even eliminating potential risks caused by manual maintenance of large amounts of business object information.

[0067] In the embodiments of the present disclosure, the "bloodline relationship" is not a bloodline relationship in the usual sense of the biological or human science fields. The "bloodline relationship" described in the embodiments of the present disclosure 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 "bloodline relationship" described in this article can be used to describe the association relationships such as nested use, mutual dependence or derivative iteration between businesses (objects). For example, business (object) A may depend on the function of business (object) B, and business object C depends on business (object) A. This dependency relationship is the "bloodline relationship" referred to in the present invention.

[0068] In some embodiments of the present disclosure, reference Figure 1 , showing a business object blood relationship risk warning method according to an embodiment of the present disclosure, the method can be used for including but not limited to data management systems, business management systems, and the method can at least include the following 110, 130 and 140.

[0069] 110: Determine the blood relationship of the target business object according to the business object blood relationship library.

[0070] In the disclosed embodiment, the blood relationship of the target business object may be determined from a pre-established business object blood relationship library.

[0071] In the embodiments of the present disclosure, the business object has a broad meaning in the field (the field of computer technology), including but not limited to various digital objects managed and processed in the enterprise's data processing system, business management system, business decision system and other systems. 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 commodities or combinations thereof, or may be individually abstractly defined as at least one of the modules / components / units of the business object. It should be understood by those skilled in the art that the business objects described in the embodiments of the present disclosure are digital business objects and do not include physical business objects. However, as needed, the business objects of the embodiments of the present 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 the embodiment of the present disclosure, the business object kinship database includes a database or data structure for persistently storing and managing business information data of various businesses involved in the enterprise and inter-business dependency data. In this embodiment, the kinship database includes but is not limited to a graph database ( Database) and relational database, etc. The present disclosure does not limit the component method and specific structure of the business object blood relationship library.

[0073] In some embodiments of the present disclosure, the business object kinship library may include multiple kinship nodes corresponding to multiple business objects one by one and dependencies between the multiple kinship nodes. In this embodiment, the kinship 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: business object identification, business name, business version, business category, business application scope, business status, etc. In a specific example, the object kinship library may include a kinship 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": "onlihne"}}". It should be understood that the above kinship nodes are only used as examples, and the present disclosure does not limit the specific format and specific encapsulation method of the kinship node.

[0074] In the embodiment of the present disclosure, the business object blood relationship library may record the dependency relationship between two blood relationship nodes. In the embodiment of the present disclosure, it should be understood that the dependency relationship between the blood relationship nodes may correspond to the dependency relationship between the business objects associated with the blood relationship nodes, wherein the dependency relationship may include but is not limited to the calling relationship, data exchange relationship, resource sharing relationship and other forms of interactive relationship between businesses, and the present disclosure does not limit this.

[0075] In the embodiments of the present disclosure, the term "direct dependency" refers to the dependency relationship generated by direct calls, data exchange, etc. 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 be directly dependent on business object B.

[0076] In the embodiments of the present disclosure, the term "indirect dependency" refers to the dependency relationship between a business object and other business objects indirectly generated by relying on an intermediate business object. In one example, if business object A directly calls the data of business object B, and business object B directly depends on the function of business object C, then business object A can be said to be indirectly dependent on business object C.

[0077] In some embodiments of the present disclosure, on the basis of the above-mentioned dependency relationships, according to the specific dependency relationships, the concepts of "upstream" and "downstream" are further introduced to describe the direction of the dependency relationship between the blood relationship nodes: the business that provides basic functions or business services can be called "upstream business", and the business that depends on and calls the upstream business functions can be called "downstream business". Accordingly, the blood relationship node corresponding to the "upstream business" can be called the "upstream blood relationship node", and the blood relationship node corresponding to the "downstream business" can be called the "downstream blood relationship node". It should be understood that this "upstream" and "downstream" relationship can be caused by direct dependence or indirect dependence.

[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, as a downstream business, relies on and calls the data processing service to complete the data analysis function, thus forming a dependency chain of "data processing business service to data analysis business service", in which 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 the present disclosure, the business object blood relationship library can record the dependencies between blood relationship nodes in various forms, including but not limited to recording the dependencies between blood relationship nodes in the form of blood node embedding, independent dependency table, graph structure, etc., and the present disclosure does not impose any restrictions on this. Continuing with the previous specific example, the blood relationship node A in the blood relationship library is embedded with the following direct dependency data ""downstream": ["002", "003"]".

[0080] In the embodiment of the present disclosure, the blood relationship of the target business object determined from the pre-established business object blood relationship library may include: a blood relationship node data set and a dependency relationship data set related to the target business object.

[0081] In some embodiments of the present disclosure, the blood relationship node data set and the dependency relationship data set can be queried from the blood relationship database. In one example, for a MySQL relational blood relationship library, the existing blood relationship node table and dependency relationship table can be directly queried through SQL query to obtain the blood relationship node data set and dependency relationship data set of the target business object. In another example, for a Neo4j graph database blood relationship library, a graph traversal query can be performed through the Cypher query language to obtain the blood relationship node data set and dependency relationship data set of the target business object. It should be understood that the query method varies depending on the construction method of the blood relationship database, blood relationship nodes, and dependency relationships, as well as the data structure, and the present disclosure does not limit this.

[0082] 130: Based on preset risk rules, risk identification is performed on the business object blood relationship of the target business object.

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

[0084] In the embodiment of the present disclosure, the risk rule may define a specific judgment rule as to whether there is a rule between blood relationship nodes with dependencies.

[0085] In some embodiments of the present disclosure, the risk rule may define the comparison standard of node attributes between blood relationship nodes with dependencies and the constraint conditions of the dependencies, and determine that there is a risk when the blood relationship nodes do not meet the comparison standard or constraint conditions. In one example, when the version difference between the upstream and downstream blood relationship nodes exceeds the compatible range, it is identified as a risk, otherwise there is no risk.

[0086] In some embodiments of the present disclosure, the risk rule may define a preset risk situation or risk range between dependent blood relationship nodes, and determine that there is a risk when the business attribute information combination of at least two blood relationship nodes falls into the preset risk combination. In one example, for the business attribute information "business nature", when the corresponding value of the "business nature" of the upstream blood relationship node is "0", and the corresponding value of the "business nature" of the downstream blood relationship node with which it has a dependent relationship is "1", it is identified as a risk.

[0087] In the embodiments of the present disclosure, the above 110 and 130 may exist in the presence of multiple triggering conditions. In some embodiments, when a new blood relationship node is added to the business object blood relationship library, the newly added blood relationship node is determined as a target relationship node, and blood relationship determination and risk identification are triggered. In some embodiments, when a blood relationship node is requested to be deleted, the blood relationship node requested to be deleted is determined as a target relationship node, and blood relationship determination and risk identification are performed. In some embodiments, when the business attribute information of a blood relationship node is updated, the updated blood relationship node is determined as a target relationship node, and blood relationship determination and risk identification are performed. In other embodiments, a list of blood relationship nodes with key risk identification can be preset, and blood relationship determination and risk identification can be performed regularly on the blood relationship nodes in the list at predetermined time intervals.

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

[0089] In some embodiments of the present disclosure, reference Figure 2 , the above 130 may at least include the following 131~133.

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

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

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

[0093] In some embodiments of the present disclosure, the business attribute information included in a given blood relationship node may be determined. As mentioned above, the business attribute information may include, but is not limited to: business object identification, business name, business version, business category, business application scope, business status, etc. In an embodiment of the present disclosure, one or more relevant business attribute information may be determined according to the specific needs of the preset risk rules.

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

[0095] In some embodiments of the present disclosure, risk identification (analysis) can be performed based on the business attribute information corresponding to the determined upstream and downstream blood relationship nodes in combination with the corresponding preset risk rules to obtain a risk identification result (analysis result) for specific business attribute information. As an explanation but not limitation, the risk identification result can reflect whether there is a risk in the upstream and downstream blood relationship nodes in terms of specific business attribute information.

[0096] The above embodiment of the present disclosure generally describes the steps of risk identification in the embodiment of the present disclosure. The following will further describe various types of risk identification in the embodiment of the present disclosure in combination with multiple embodiments of the present disclosure. Figures 3 to 6 To describe different types of risk identification.

[0097] In some embodiments of the present disclosure, reference Figure 3 , showing the risk identification for the applicable scope of the business object. In this embodiment, the 130 may at least include the following 132'~133'.

[0098] 132': Determine the applicable scope of the business object corresponding to the given blood relationship node in the business object blood relationship of the target business object.

[0099] In this embodiment, the applicable scope of the business object included in the given blood relationship node can be determined, wherein the applicable scope of the business object should be understood in a broad sense and may include any business attribute information related to the applicable scope of the business object. In one example, the applicable scope of the business object corresponds to, for example, the "scope of application" field included in the business attribute information of the blood relationship node. In a specific example, the "scope of application" field includes, for example: personal business, corporate business, domestic business, cross-border business, etc., which is not limited in this disclosure.

[0100] 133': According to the intersection status of the applicable scope of the business object corresponding to the upstream and downstream blood relationship nodes and the preset intersection rule, the risk identification result for the applicable scope of the business object is obtained.

[0101] In this embodiment, the intersection state of the business object applicable scope includes but is not limited to: the business object applicable scope of the downstream blood relationship node includes the business object applicable scope of the upstream blood relationship node, the business object applicable scope of the upstream blood relationship node includes the business object applicable scope of the downstream blood relationship node, the business object applicable scope of the downstream blood relationship node partially overlaps with the business object applicable scope of the upstream blood relationship node, and the business object applicable scope of the downstream blood relationship node is mutually exclusive with the business object applicable scope of the upstream blood relationship node. In this embodiment, the business object management system can determine whether there is a risk of business object applicable scope based on the intersection state and the preset intersection rule.

[0102] In one example, the preset intersection rule may include: when the business object applicable scope of the upstream lineage node includes the business object applicable scope of the downstream lineage node, it is determined to be risk-free. In a specific example, the upstream node applicable scope is "all businesses" and the downstream node applicable scope is "personal business". The upstream node has the ability to cope with all business scenario requirements of the upstream node, and it is determined to be risk-free at this time.

[0103] In another example, the preset intersection rule may include: when the business object applicable scope of the downstream lineage node includes the business object applicable scope of the upstream lineage node, it is determined to be a medium risk. In a specific example, the upstream node is applicable to "online payment business" and the downstream node is applicable to "all payment business". The business logic of the upstream node may not be applicable to some payment scenarios of the downstream node, and it is determined to be a medium risk.

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

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

[0106] As mentioned above, the business object applicable scope may include any attribute information related to the business object applicable scope, and the preset requirements may also be set accordingly. In one example, the preset requirement may be set such that the business object applicable scope of the downstream blood relationship node requires to include the business object applicable scope of the upstream blood relationship node. In another example, the preset requirement may be set such that the business object applicable scope of the upstream blood relationship node requires to include the business object applicable scope of the downstream blood relationship node.

[0107] In some embodiments of the present disclosure, reference Figure 4 , showing the risk identification for the business object status, in this embodiment, the 130 may at least include the following 132''~133''.

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

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

[0110] 133'': According to 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, the business object state is consistent and the business object state is inconsistent. In some embodiments, the consistency rule may include that when the business object state is inconsistent, it is judged that there is a risk of the business object state, otherwise there is no risk of the business object state. In one example, the consistency state is, for example, the business object state is consistent and the business object state is inconsistent. In some embodiments, the consistency rule may include that when the business object state is inconsistent, it is judged that there is a risk of the business object state, otherwise there is no risk of the business object state. In a specific example, when the state of the upstream business object is "to be enabled", and the state of the downstream business service that depends on the upstream business object is "enabled", it is judged that there is a risk of inconsistent state. For another example, when the upstream data service state is "suspended service" and the downstream data analysis service state is "normal operation", it is also judged that there is a risk of inconsistent state. For another example, when the upstream payment service state is "version upgrade", and the downstream order service state is "normal service", it is also judged that there is a risk of inconsistent state. These inconsistent states may cause problems such as failure of downstream business calls, abnormal data processing or service response timeout.

[0112] In other embodiments of the present disclosure, in response to inconsistent business object states, the consistency rules may also be separately specified for the business object states corresponding to the upstream and downstream blood relationship nodes. In one example, in response to inconsistent states between the upstream business object and the downstream business object, the consistency rules may include: when the business object state corresponding to the upstream business object is "available" and the business object state corresponding to the downstream blood relationship node is "unavailable", it is judged that there is no risk of business object state. As an explanation and not limitation, the downstream business object is dependent on the functions of the upstream business object, and the offline of the downstream business object reduces the operating pressure of its corresponding upstream business object and does not cause any adverse effects on the upstream business object. Therefore, it can be judged that there is no risk of business object state.

[0113] In some embodiments of the present disclosure, the business object blood relationship library also includes business object change record information corresponding to the blood relationship node, and the product change record information includes but is not limited to product attribute information before and after the blood relationship node is changed.

[0114] In this embodiment, reference Figure 5 , showing the risk identification for business object changes. In this embodiment, the 130 may also include at least the following 134, 135 and 136.

[0115] 134: Determine the downstream blood relationship node on which a given blood relationship node in the business object blood relationship of the target business object directly or indirectly depends.

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

[0117] 135: Get the business object change record information corresponding to the given lineage relationship node and the downstream lineage relationship node.

[0118] In some embodiments of the present disclosure, the business object change record information of the recorded blood relationship node can be obtained, wherein the business object change record information includes but is not limited to the business object attribute information before and after the blood relationship node is changed. For the specific description of the business object attribute information, please refer to the content in the aforementioned 110, which will not be repeated here.

[0119] 136: Obtain risk identification results for business object changes based on the acquired business object change record information.

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

[0121] In some embodiments of the present disclosure, when the blood relationship node information is not the latest updated information in the business object change record, it is determined that the blood relationship node has changed, and the business object management system will update the business object change record based on the current information of the blood relationship node, and judge whether there is a risk of business object change; otherwise, it is determined that the blood relationship node has not changed, and it is judged that there is no risk of business object change.

[0122] As mentioned above, in some embodiments of the present disclosure, the preset risk rules may also include risk rules pre-defined by the user. Figure 6 As shown, before the risk identification of the blood relationship of the target business object is performed based on the preset risk rules, the business object blood relationship risk warning method may also include the following 120.

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

[0124] As mentioned above, the preset risk rules may include user-defined risk rules. In some embodiments of the present disclosure, a user-defined risk rule configuration may be obtained, and a user-defined risk rule may be generated based on the risk rule configuration, wherein the risk rule configuration includes but is not limited to information such as risk name, risk field, upstream business object risk field determination condition, and downstream business object risk field determination condition. In this embodiment, the risk field may correspond to one or more business attribute information of the business object, and the business attribute information includes but is not limited to the business attribute information described in the aforementioned 110, and the determination condition includes but is not limited to a specific risk value (such as a certain rate rule type code), a value range (such as a rate type code range), and may also be an enumerated value set (such as an allowed rate rule type code set), etc.

[0125] Accordingly, in some embodiments of the present disclosure, reference Figure 7 , showing the risk identification for user-defined risk rules. In this embodiment, the 130 may also include at least the following 137 and 138.

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

[0127] As mentioned above, the risk field of the business object attribute information may be specified in the user-defined risk rule. Accordingly, in this embodiment, the risk field value of the business object attribute information of a given lineage node may be determined. In one example, for example, if the risk field "rate type" is included in the user-defined risk rule, the business object management system will determine the risk field value corresponding to the "rate type" of the given lineage node.

[0128] 138: A user-defined risk identification result is obtained based on whether the risk field values ​​of the upstream and downstream blood relationship nodes match the upstream business object risk field threshold and the downstream business object risk field threshold.

[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, and the risk identification result is determined based on whether the risk field value in the given blood relationship node hits the upstream / downstream risk field judgment condition: if it matches the judgment condition, it is judged that there is a user-defined risk, otherwise there is no user-defined risk.

[0130] In some embodiments, the business object management system may determine the upstream / downstream blood relationship nodes that have a direct dependency relationship with the blood relationship node corresponding to the target business object, and respectively determine whether the risk field values ​​of the upstream / downstream blood relationship nodes hit the upstream / downstream risk field thresholds. If they do, it is determined that a user-defined risk exists; 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 the upstream / downstream blood relationship nodes directly associated with it are "Business Object B" and "Business Object Data Source C", respectively. When the risk field value included in either of the two hits the upstream / downstream risk field threshold, it is determined that a user-defined risk exists; otherwise, there is no user-defined risk.

[0131] In other embodiments, the business object management system may also determine the upstream / downstream blood relationship nodes that have an indirect dependency relationship with the target business object, and determine whether the risk field value of the upstream / downstream blood relationship 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", and the upstream blood relationship node directly associated with it is determined to be "Business Object B", and the upstream blood relationship node directly associated with "Business Object B" is "Business Object A", that is, "Business Object C" is indirectly associated with "Business Object A", and when the risk field value in "Business Object A" hits the upstream risk field threshold, it is judged that there is a user-defined risk, otherwise there is no user-defined risk.

[0132] 140: Generate risk warning information associated with the blood relationship of the target business object based on the risk identification result.

[0133] In the disclosed embodiment, the risk identification result of the business object is obtained, for example, by the above-mentioned step 130 and its sub-steps. In this embodiment, the result of risk identification can be converted into specific risk warning information, and the information risk warning includes but is not limited to risk level, risk description text related to the blood relationship of the target business object, possible impact, etc. In a specific example, the warning information for risk identification of the applicable scope of the business object is, for example: "The status of the upstream business object A is "available", and the status of the downstream business object B is "unavailable"; risk level: "high"; possible impact: "upstream business object A function is abnormal".

[0134] In other embodiments of the present disclosure, Figure 8 As shown, the business object blood relationship risk warning method of the embodiment of the present disclosure may also include the following 150.

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

[0136] In some embodiments of the present disclosure, the risk warning information generated can be visualized in the risk warning interface. Fig. 9 , for example, the risk warning information is displayed in the form of a block diagram. In some embodiments, when the risk warning information generated is visualized, the risk warning information can also be displayed in different colors according to the risk level of the risk warning information (not shown).

[0137] In some embodiments of the present disclosure, while visualizing the risk warning information generated in the risk warning interface, a visualization interface for displaying the business object lineage relationship can also be combined. In this embodiment, the visualization interface for the business object lineage relationship has a dependency flow diagram that presents the lineage relationship of the target business object determined, and the dependency flow diagram includes the multiple lineage relationship nodes and the directed lines between the lineage relationship nodes. In one example, the direction of the dependency relationship is represented by the direction of the arrow. In a specific example, refer to Fig. 9, which shows a schematic diagram of the business object blood relationship visualization interface displayed on the left side of the risk warning interface, wherein 26 blood relationship nodes are shown (see the 26 gray rectangles in the figure), wherein any of the blood relationship nodes corresponds to a business object, and there are 36 directed lines between the blood relationship nodes that present the dependency relationship between the blood relationship nodes, wherein any of the directed lines includes a starting arrow, a directed line body, an ending arrow and a directed line sequence number. As an example, there is a directed line 1 pointing from blood relationship node D (corresponding to business object D) to blood relationship node A (corresponding to business object A), which indicates that blood relationship node D is directly dependent on blood relationship node A, and other directed lines are not repeated.

[0138] In some other embodiments of the present disclosure, the generated risk warning information can be displayed in the form of a block diagram on the risk warning interface. Fig. 9 , which shows a schematic diagram of the business object blood relationship visualization interface displayed on the left side of the risk warning interface, which schematically shows 4 risk warning diagrams, including high-risk warning information: "The business application scope of the target business object C is personal business, and the business application scope of the upstream business object B is corporate business. The business application scopes of the target business object C and the upstream business object B are mutually exclusive! Please evaluate the rationality of the business application scope configuration!". It should be understood that the number of risk warning diagrams and the specific displayed text in the above specific embodiment are only for illustration. In other embodiments, the risk warning interface may further include a larger number of risk warning diagrams and display more risk warning texts: such as Fig. 9 The risk warning text of "Medium Risk - User-defined Risk 2" is used to remind users of the risks corresponding to the customized rules, and the level is medium risk; Fig. 9 The risk warning text of "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; Fig. 9 The risk warning text of "Attention-Business Object Change Risk" is used to prompt the risk identification results of business object changes, and the level is attention.

[0139] In other embodiments of the present disclosure, Figure 8 As shown, the embodiment of the present disclosure also provides a human-computer interaction solution for risk warning information and business object blood relationship, and the business object blood relationship risk warning method may also include the following 160.

[0140] 160: In response to the user's interactive operation on the risk warning information, highlight the nodes and directed lines related to the selected risk warning information in the dependency flow diagram in the business object lineage relationship visualization interface.

[0141] In some embodiments of the present disclosure, in response to a user's interactive operation on risk warning information, such as moving an 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 synchronously highlight the blood relationship nodes and directed connections related to the selected risk warning information in a business object blood relationship visualization interface that is displayed together.

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

[0143] In this embodiment, risk warning information can be presented to the user in an intuitive manner, and interactive functions can be provided to facilitate the user to deeply understand and analyze the risk situation.

[0144] The business object lineage risk warning method of the disclosed embodiment not only visualizes the complex business object dependency relationships, but also combines multi-dimensional risk analysis to more comprehensively and accurately grasp the dependency relationships between business objects and timely identify potential risks. The business object lineage risk warning method of the disclosed embodiment also realizes the timely discovery and warning of potential risks in the cross-business line business object network by introducing preset risk rules, 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. In addition, these methods themselves can also be combined or spliced ​​to form new methods.

[0146] 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.

[0147] First, the business object management system receives a user's request for risk warning analysis on "model business object A", version V1.0.

[0148] In response to the business object management system receiving the maintenance personnel's request for risk warning analysis on the target business object A, the business object management system retrieves information related to the target business object A from the business object lineage library and determines its lineage relationship: the target business object directly depends on the upstream business object B and the upstream business object C, while the downstream business object D depends on the target business object.

[0149] Subsequently, the business object management system obtains the risk configuration customized by the user: "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 the configuration into executable risk rules for subsequent risk identification processes. When it is found that the charge_rule field values ​​of the upstream and downstream business objects match the configured thresholds respectively, for example, 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 obtains the preset risk rules in the system, including business applicability risk rules and business status risk rules.

[0150] The business object management system then identifies the risk of the target business object's blood relationship according to the above risk rules: For the user-defined billing rule risk rule: the system obtains the billing rule field value of the upstream business object B as "0", matches the upstream business object risk field threshold, and triggers a risk warning. For the business application scope risk rule: the system determines that the business application scope of the target business object is "personal business" and the business application scope of the upstream business object B is "enterprise business". According to the preset intersection rule: "When the business object application scope of the downstream blood relationship node is mutually exclusive with the business object application scope of the upstream blood relationship node, it is judged to be high risk", so it is judged that there is a high risk and a risk warning is triggered. For the business status risk rule: the system determines that the business status of the target business object is "enabled" and the business status of the upstream business object C is "to be enabled", and determines that the business status of the target business object and the upstream business object C are inconsistent, triggering a risk warning. For the business object change risk: the system finds that the upstream business object C has been updated recently, which may affect the function of the target business object, triggering a risk warning.

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

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

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

[0154] "[Low Risk] The business status of the target business object is "Enabled", and the business status of the upstream business object C is "To be Enabled"! Please pay attention to whether the upstream business object C needs to be enabled!".

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

[0156] Finally, reference Fig. 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 the present disclosure, Fig.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 determination unit 1010 is configured to determine the blood relationship of the target business object based on a business object blood relationship library, wherein the business object blood relationship library includes multiple blood relationship nodes corresponding to multiple business objects one by one and direct dependency relationships between the multiple blood relationship nodes, and the blood relationship nodes include business attribute information of the corresponding business objects.

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

[0160] The generating unit 1030 is configured to generate risk warning information associated with the business object blood relationship of the target business object according to the risk identification result.

[0161] The corresponding device for processing the blood relationship of business objects in the embodiment of the present disclosure 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 business object 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 business object blood relationship 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 business object blood relationship diagrams.

[0162] The apparatus and its components, modules, units and features described in the embodiments of the present disclosure may 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 may also be combined with the apparatus of the embodiments of the present disclosure in a non-contradictory manner.

[0163] 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.

[0164] Fig.11 A schematic diagram of an electronic device 1100 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.

[0165] like Fig.11As shown, the electronic device 1100 includes a processor 1101, which can perform various appropriate operations and processes according to the program and / or data stored in the read-only memory (ROM) 1102 or the program and / or data loaded from the storage part 1108 to the random access memory (RAM) 1103. Processor 1101 can be a multi-core processor or include multiple processors. In some embodiments, processor 1101 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 1103, various programs and data required for the operation of electronic device 1100 are also stored. Processor 1101, ROM 1102 and RAM 1103 are connected to each other via bus 1104. Input / output (I / O) interface 1105 is also connected to bus 1104.

[0166] 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.

[0167] The following components are connected to the I / O interface 1105: an input section 1106 including a keyboard, a mouse, a touch screen, etc.; an output section 1107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, 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, a modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to the I / O interface 1105 as needed. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as needed, so that a computer program read therefrom is installed into the storage section 1108 as needed. Fig.11 Only some components are schematically shown in the figure, which does not mean that the computer system 1100 only includes Fig.11 Components shown.

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

[0169] 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.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] 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 business object blood relationship risk early warning method, characterized in that: include: Determining the kinship of the target business object according to a business object kinship library, wherein the business object kinship library includes a plurality of kinship nodes corresponding to a plurality of business objects one by one and dependency relationships between the plurality of kinship nodes, and the kinship nodes include business attribute information of the corresponding business objects; Based on the preset risk rules, risk identification is performed on the blood relationship of the target business object; Based on the risk identification result, risk warning information associated with the blood relationship of the target business object is generated.

2. The method according to claim 1, characterized in that: The risk identification of the blood relationship of the target business object based on the preset risk rules includes: Determine the upstream and downstream blood relationship nodes on which a given blood relationship node in the blood relationship of the target business object directly or indirectly depends; Determine at least one business attribute information corresponding to the given blood relationship node; According to the business attribute information corresponding to the upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information, a risk identification result for the business attribute information is obtained.

3. The method according to claim 1, characterized in that The preset risk rules include user-defined risk rules; The business object blood relationship risk early warning method also includes: Obtain a user-defined risk rule configuration and generate a user-defined risk rule, wherein the risk rule configuration includes at least a risk name, a risk field, an upstream business object risk field determination condition, and a downstream business object risk field determination condition, wherein the risk field corresponds to at least one business attribute information.

4. The method according to claim 3, characterized in that The risk identification of the blood relationship of the target business object based on the preset risk rules includes: Determine a risk field value of the at least one business attribute information corresponding to a given blood relationship node in the blood relationship of the target business object; A user-defined risk identification result is obtained based on whether the risk field values ​​of the upstream and downstream blood relationship nodes match the upstream business object risk field determination condition and the downstream business object risk field determination condition.

5. The method according to claim 2, characterized in that: The business attribute information includes the business application scope; wherein, The determining of at least one business attribute information corresponding to the given blood relationship node includes: Determine the business application scope corresponding to the given blood relationship node; The step of obtaining a risk identification result for the business attribute information according to the business attribute information corresponding to the upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information includes: According to the intersection status of the business application scopes corresponding to the upstream and downstream blood relationship nodes and the preset intersection rules, a risk identification result for the business application scope is obtained.

6. The method according to claim 2, characterized in that The service attribute information includes service status; wherein, The determining of at least one business attribute information corresponding to the given blood relationship node includes: Determine the business state corresponding to a given blood relationship node in the blood relationship of the target business object; The step of obtaining a risk identification result for the business attribute information according to the business attribute information corresponding to the upstream and downstream blood relationship nodes and the preset risk rules corresponding to the business attribute information includes: According to the consistency status of the business status corresponding to the upstream and downstream blood relationship nodes and the preset consistency rules, a risk identification result for the business status is obtained.

7. The method according to claim 1, characterized in that The business object blood relationship library also includes business object change record information corresponding to the blood relationship node; The risk identification of the blood relationship of the target business object based on the preset risk rules includes: Determine an upstream blood relationship node on which a given blood relationship node in the blood relationship of the target business object directly or indirectly depends; Obtaining business object change record information corresponding to the given blood relationship node and the upstream blood relationship node; Based on the acquired business object change record information, a risk identification result for the business object change is obtained.

8. The method according to any one of claims 1 to 7, characterized in that After generating risk warning information associated with the blood relationship of the target business object, the method further includes: In combination with a visualization interface for displaying the blood relationship of business objects and a risk warning interface, the risk warning interface displays the risk warning information, and the visualization interface for displaying the blood relationship of business objects has a dependency flow graph that presents the blood relationship of the determined target business objects, and the dependency flow graph includes the multiple blood relationship nodes and directed connections between the blood relationship nodes.

9. The method according to claim 8, characterized in that The method further comprises: In response to the user's interactive operation on the risk warning information, the blood relationship nodes and directed lines related to the selected risk warning information are highlighted in the dependency flow diagram in the business object blood relationship visualization interface.

10. A business object blood relationship risk early warning device, characterized in that: The business object blood relationship risk early warning device comprises: a determination unit configured to determine the blood relationship of the target business object according to a business object blood relationship library, wherein the business object blood relationship library includes a plurality of blood relationship nodes corresponding to a plurality of business objects one by one and dependency relationships between the plurality of blood relationship nodes, and the blood relationship nodes include business attribute information of the corresponding business objects; an identification unit configured to perform risk identification on the blood relationship of the target business object based on a preset risk rule; The generating unit is configured to generate risk warning information associated with the blood relationship of the target business object according to the risk identification result.

11. 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 9 when the computer program is executed.

12. 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 9 is implemented.

Images