CN111581294A

CN111581294A - Entity relationship display method and device, electronic equipment and readable storage medium

Info

Publication number: CN111581294A
Application number: CN201910120482.7A
Authority: CN
Inventors: 贺勇; 李楠; 曹徽
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-02-18
Filing date: 2019-02-18
Publication date: 2020-08-25
Anticipated expiration: 2039-02-18
Also published as: CN111581294B

Abstract

The embodiment of the disclosure discloses an entity relationship display method, an entity relationship display device, electronic equipment and a readable storage medium, wherein the method comprises the following steps: extracting entity information of a specific entity from the entity table and extracting resource flow information between a plurality of entities including the specific entity from the resource flow table; based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, the specific entity is taken as a central node, the central node and a non-central node representing the entities except the specific entity are constructed and displayed according to an upstream and downstream structure of resource flow, and the resource flow relationship among the plurality of entities, the upstream and downstream structure division with the central node as a reference can be used for distinguishing the upstream and downstream nodes of each node, so that the node and the resource flow relationship among each node are constructed and displayed.

Description

Entity relationship display method and device, electronic equipment and readable storage medium

Technical Field

The disclosure relates to the technical field of computers, in particular to an entity relationship display method and device, electronic equipment and a readable storage medium.

Background

When there is a flow of resources between nodes representing entities, it is a common approach to build and expose a graph of relationships between nodes. However, such a graph is typically structurally confusing, and there is no explicit upstream or downstream structure, i.e., there is no apparent upstream or downstream distinction between nodes. It is difficult to identify each node and the flow of resources between nodes from the perspective of business roles and the like.

For example, the flow of resources such as information, data, storage space, etc., between computer nodes that make up a network results in a network of computer nodes that cannot exhibit a clear upstream and downstream structure from a business perspective, and the business roles between the nodes are difficult to identify. In some cases, this may result in potential anomalies such as security issues that are difficult to discover.

Also for example, in a relational graph constructed for the flow of resources such as goods, services, assets, etc., between nodes representing entities such as businesses, institutions, governments, etc., structures are not divided up or down stream for different business roles. In some cases, this may result in potential anomalies such as traffic being difficult to discover.

Disclosure of Invention

In order to solve the problems in the related art, embodiments of the present disclosure provide an entity relationship display method, an entity relationship display apparatus, an electronic device, and a readable storage medium.

In a first aspect, an embodiment of the present disclosure provides an entity relationship display method, including:

extracting entity information of a specific entity from a preset entity table and extracting resource flow information between a plurality of entities including the specific entity from a preset resource flow table;

based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, the specific entity is taken as a central node, a non-central node representing the entities except the specific entity and the central node are constructed and displayed according to an upstream and downstream structure of resource flow, and resource flow relations among the plurality of entities.

With reference to the first aspect, in a first implementation manner of the first aspect, the constructing and displaying, with the specific entity as a central node and according to an upstream and downstream structure of resource flow, a non-central node representing an entity other than the specific entity and resource flow relationships among a plurality of entities based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity includes:

based on the extracted entity information of a specific entity and the extracted resource flow information among a plurality of entities including the specific entity, constructing and displaying a resource flow relationship among the entities and the entities according to an upstream and downstream structure in a manner that the specific entity is a central node and an entity other than the specific entity is one of an upstream node, a downstream node and a peer node of the central node, wherein an entity providing resources to the specific entity is taken as the upstream node of the central node, an entity providing resources to the specific entity is taken as the downstream node of the central node, and a node providing resources to the upstream node and/or the downstream node in the nodes other than the central node is taken as the peer node of the central node.

With reference to the first implementation manner of the first aspect, the present disclosure provides, in a second implementation manner of the first aspect, that an upstream node of the central node is an entity that directly or indirectly provides resources to the specific entity, a downstream node of the central node is an entity that is directly or indirectly provided with resources by the specific entity, and a peer node of the central node is an entity that is directly provided with resources to the specific entity among entities other than the specific entity and/or directly provides resources to an entity that is directly provided with resources by the specific entity.

With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the peer node of the central node is a level 0 node; among N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as an upstream level 1 node; among the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream M-level nodes starting from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1.

With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the constructing and displaying, by taking the specific entity as a central node and according to an upstream and downstream structure of resource flow, a non-central node of the central node and a non-central node representing entities other than the specific entity, and resource flow relationships among a plurality of entities includes:

and in response to detecting that a node other than the central node is in multiple stages at the same time, synthesizing the display mode of the node according to a preset rule, determining the display position of the node, and displaying the node in the synthesized display mode at the display position.

With reference to the first aspect and any one of the first to fourth implementation manners of the first aspect, in a fifth implementation manner of the first aspect, the constructing and displaying, by taking the specific entity as a central node, a non-central node representing an entity other than the specific entity and a non-central node according to an upstream and downstream structure of resource flow, and resource flow relationships between the central node and the entities include:

and showing the nodes through at least one of symbols, positions, colors, shapes and animation effects according to at least one of the levels, types and node states of the nodes, and showing resource flow among the nodes through at least one of symbols, positions, colors, shapes and animation effects.

With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner of the first aspect, the constructing and displaying, by taking the specific entity as a central node and according to an upstream and downstream structure of resource flow, a non-central node of the central node and an entity other than the specific entity, and resource flow relationships among a plurality of entities further includes:

and displaying the same-level nodes in the same or different modes, wherein the central node is displayed in a mode different from the same-level nodes of the central node, and the mode comprises at least one of symbols, positions, colors, shapes and animation effects.

With reference to the fifth implementation manner of the first aspect, in a seventh implementation manner of the first aspect, the constructing and displaying, by taking the specific entity as a central node and according to an upstream and downstream structure of resource flow, a non-central node of the central node and an entity other than the specific entity, and resource flow relationships among the multiple entities further includes:

and showing the flow of the same amount of resources among different nodes in the same or different modes, wherein the modes comprise at least one of symbols, positions, colors, shapes and animation effects.

With reference to the first aspect and any one of the first to fourth implementation manners of the first aspect, in an eighth implementation manner of the first aspect, the present disclosure further includes:

and presenting entity information of the entity represented by the operated node in response to the operation on the presented node.

With reference to the first aspect and any one of the first to fourth implementation manners of the first aspect, in a ninth implementation manner of the first aspect, the present disclosure further includes:

resource flow information between the nodes represented by the operated resource flow relationships is exposed in response to the operation on the resource flow relationships between the exposed nodes.

With reference to the first aspect and any one of the first to fourth implementation manners of the first aspect, in a tenth implementation manner of the first aspect, the query information includes screening information for screening resource flow relationships between an entity represented by the non-central node and a plurality of entities.

With reference to the first aspect and any one of the first to fourth implementation manners of the first aspect, in an eleventh implementation manner of the first aspect, the entities are business entities, and the resource flow relationship between the multiple entities is a sales relationship of goods and/or services between the multiple business entities, wherein, in the upstream and downstream structure, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services.

With reference to the first aspect and any one of the first to fourth implementation manners of the first aspect, in a twelfth implementation manner of the first aspect, the present disclosure further includes:

acquiring entity information of entities and resource flow information between the entities;

and generating the preset entity table based on the acquired entity information of the entities, and generating the preset resource flow table based on the information of the entities and the resource flow information among the entities.

In a second aspect, an embodiment of the present disclosure provides an entity relationship display apparatus, including:

an extraction module configured to extract entity information of a specific entity from a preset entity table and extract resource flow information between a plurality of entities including the specific entity from a preset resource flow table;

a construction and presentation module configured to construct and present a non-central node representing entities other than the specific entity and a central node in an upstream and downstream structure of resource flow, with the specific entity as a central node, and a plurality of entities based on the extracted entity information of the specific entity and the extracted resource flow information between the plurality of entities including the specific entity.

With reference to the second aspect, in a first implementation manner of the second aspect, the building and presentation module is further configured to:

With reference to the first implementation manner of the second aspect, the present disclosure provides in a second implementation manner of the second aspect, an upstream node of the central node is an entity that directly or indirectly provides resources to the specific entity, a downstream node of the central node is an entity that is directly or indirectly provided with resources by the specific entity, and a peer node of the central node is an entity that directly provides resources to the specific entity among entities other than the specific entity and/or directly provides resources to an entity that is directly provided with resources by the specific entity.

With reference to the second implementation manner of the second aspect, in a third implementation manner of the second aspect of the present disclosure, the peer node of the central node is a level 0 node; among N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as an upstream level 1 node; among the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream M-level nodes starting from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1.

With reference to the third implementation manner of the second aspect, in a fourth implementation manner of the second aspect, the construction and presentation module is further configured to:

With reference to the second aspect, or any one of the first to fourth implementations of the second aspect, in a fifth implementation of the second aspect, the build and show module is further configured to:

With reference to the fifth implementation manner of the second aspect, in a sixth implementation manner of the second aspect, the building and presentation module is further configured to:

With reference to the fifth implementation manner of the second aspect, in a seventh implementation manner of the second aspect, the building and presentation module is further configured to:

With reference to the second aspect, or any one of the first implementation manner to the fourth implementation manner of the second aspect, in an eighth implementation manner of the second aspect, the disclosure further includes:

a first exposure module configured to expose entity information of an entity represented by the operated node in response to the operation of the exposed node.

With reference to the second aspect or any one of the first to fourth implementation manners of the second aspect, in a ninth implementation manner of the second aspect, the present disclosure further includes:

a second exposing module configured to expose resource flow information between the nodes represented by the operated resource flow relationship in response to the operation on the resource flow relationship between the exposed nodes.

With reference to the second aspect and any one of the first to fourth implementation manners of the second aspect, in a tenth implementation manner of the second aspect, the query information includes screening information for screening resource flow relationships between the entity represented by the non-central node and a plurality of entities.

With reference to the second aspect, or any one of the first to fourth implementations of the second aspect, in an eleventh implementation of the second aspect, the entity is a business entity, and the resource flow relationship between the plurality of entities is a sales relationship of goods and/or services between the plurality of business entities, wherein, in the upstream and downstream structure, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services.

With reference to the second aspect or any one of the first to fourth implementation manners of the second aspect, in a twelfth implementation manner of the second aspect, the present disclosure further includes:

an acquisition module configured to acquire entity information of entities and resource flow information between the entities;

a table generating module configured to generate the preset entity table based on the obtained entity information of the entities, and generate the preset resource flow table based on the information of the entities and resource flow information between the entities.

In a third aspect, an embodiment of the present disclosure provides an entity relationship display method, including:

acquiring entity information of a specific entity, and acquiring resource flow information among a plurality of entities including the specific entity;

the method comprises the steps of taking the specific entity as a central node, showing the central node and non-central nodes representing entities other than the specific entity, and showing resource flow relations among a plurality of entities.

In a fourth aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor; wherein,

the memory is configured to store one or more computer instructions, where the one or more computer instructions are executed by the processor to implement the method according to the first aspect, the first implementation manner to the twelfth implementation manner of the first aspect, and the third aspect.

In a fifth aspect, an embodiment of the present disclosure provides a readable storage medium, on which computer instructions are stored, and the computer instructions, when executed by a processor, implement the method according to any one of the first aspect, the first implementation manner to the twelfth implementation manner of the first aspect, and the third aspect.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:

according to the technical scheme provided by the embodiment of the disclosure, the entity information of a specific entity is extracted from a preset entity table, and the resource flow information among a plurality of entities including the specific entity is extracted from a preset resource flow table; based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, the specific entity is taken as a central node, the central node and a non-central node representing the entities except the specific entity are constructed and displayed according to an upstream and downstream structure of resource flow, and the resource flow relationship among the plurality of entities, the upstream and downstream nodes of each node can be distinguished by dividing the upstream and downstream structure with the central node as a reference, so that the node and the resource flow relationship among the nodes are constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical solution provided by the embodiment of the present disclosure, by using the specific entity as a central node, constructing and displaying a non-central node representing an entity other than the specific entity and the central node according to an upstream and downstream structure of resource flow and resource flow relationships among a plurality of entities based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, the method includes: constructing and exhibiting a resource flow relationship between entities and a plurality of entities in an upstream and downstream structure in such a manner that an entity other than the specific entity is one of an upstream node, a downstream node, and a peer node of the central node, with the specific entity being a central node, and with entities other than the specific entity being one of the upstream node, the downstream node, and the peer node, wherein an entity providing resources to the specific entity is taken as the upstream node of the central node, an entity providing resources to the specific entity is taken as the downstream node of the central node, and a node providing resources to the upstream node and/or the downstream node among the nodes other than the central node is taken as the peer node of the central node, and the upstream and downstream nodes of each node may be distinguished by dividing the upstream and downstream structure with respect to the central node, so that the nodes and the resource flow relationship among the nodes can be constructed and shown. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical solution provided by the embodiment of the present disclosure, an upstream node of the central node is an entity that directly or indirectly provides resources to the specific entity, a downstream node of the central node is an entity that is directly or indirectly provided with resources by the specific entity, and a peer node of the central node is an entity that directly provides resources to the specific entity among entities other than the specific entity and/or directly provides resources to the entity that is directly provided with resources by the specific entity, and the direct or indirect upstream and downstream nodes of each node may be distinguished by upstream and downstream structural division with the central node as a reference, so that a resource flow relationship between the nodes and each node is constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, the peer node passing through the central node is a 0 th node; among N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as an upstream level 1 node; in the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream level M nodes from the node directly provided with resources by the level 0 node as the downstream level 1 node, where N and M are positive integers greater than 1, and the upstream and downstream nodes at each level can be clearly divided with the central node as a reference, so that the resource flow relationship between the nodes and each node can be clearly constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the present disclosure, constructing and displaying the central node and a non-central node representing an entity other than the specific entity according to an upstream and downstream structure of resource flow by using the specific entity as a central node, and resource flow relationships among a plurality of entities includes: in response to the fact that a node except the central node is detected to be in multiple stages at the same time, the display mode of the node is synthesized according to a preset rule, the display position of the node is determined, the node is displayed in the display position in the synthesized display mode, and the upstream and downstream nodes of each stage can be clearly divided by taking the central node as a reference, so that the resource flow relationship between the node and each node can be clearly constructed and displayed, and the role of the node in the resource flow relationship is prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the present disclosure, constructing and displaying the central node and a non-central node representing an entity other than the specific entity according to an upstream and downstream structure of resource flow by using the specific entity as a central node, and resource flow relationships among a plurality of entities includes: according to at least one of the level, the type and the node state of the node, the node is shown through at least one of symbols, positions, colors, shapes and animation effects, and the resource flow between the nodes is shown through at least one of symbols, positions, colors, shapes and animation effects, so that the role of each node in a node system constructed by taking the central node as a reference and the relationship between the nodes can be clearly shown, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical solution provided by the embodiment of the present disclosure, the method for constructing and displaying a non-central node of the central node and an entity other than the specific entity and resource flow relationships among a plurality of entities according to an upstream and downstream structure of resource flow by using the specific entity as a central node further includes: the same-level nodes are displayed in the same or different modes, wherein the display mode of the central node is different from that of the same-level nodes of the central node, and the mode comprises at least one of symbol, position, color, shape and animation effect, so that the roles of each node in a node system constructed by taking the central node as a reference and the relationships among the nodes can be clearly displayed, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical solution provided by the embodiment of the present disclosure, the method for constructing and displaying a non-central node of the central node and an entity other than the specific entity and resource flow relationships among a plurality of entities according to an upstream and downstream structure of resource flow by using the specific entity as a central node further includes: the flow of the same amount of resources among different nodes is shown in the same or different modes, wherein the modes comprise at least one of symbols, positions, colors, shapes and animation effects, so that the resource flow relationship among the nodes can be clearly shown, and the resource flow relationship among the nodes is prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, the entity information of the entity represented by the operated node is displayed in response to the operation of the displayed node, so that the specific information of the node can be clearly known, the service role and the resource flow relation of the node in the resource flow can be conveniently identified, and the potential problems in the system formed by the nodes can be controlled according to the service role and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, by responding to the operation of the resource flow relationship among the displayed nodes to display the resource flow information among the nodes represented by the operated resource flow relationship, the details of the resource flow relationship among the nodes can be clearly known, the service roles and the resource flow relationship of the nodes in the resource flow can be conveniently identified, and the potential problems in the system formed by the nodes can be controlled accordingly.

According to the technical scheme provided by the embodiment of the disclosure, the query information comprises screening information for screening the resource flow relationship between the entity represented by the non-central node and the plurality of entities, so that the resource flow relationship between the central node and the non-central node and the plurality of entities can be constructed and displayed in an expected dimension and accuracy. Moreover, the roles of each node in the node system constructed by taking the central node as the reference and the relationships among the nodes can be clearly shown, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, the entity is a business entity, and the resource flow relationship among the multiple entities is a sales relationship of goods and/or services among the multiple business entities, wherein in the upstream and downstream structure, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services, and upstream and downstream nodes representing various nodes of other business entities can be distinguished by dividing the upstream and downstream structure with a central node representing a specific business entity as a reference, so that the sales relationship of the goods and/or services among the business entities and the various business entities can be constructed and displayed. Therefore, the business roles of the business entities and the sales relations of the goods and/or services in the sales process of the goods and/or services are identified, and potential problems in a system formed by the business entities can be controlled accordingly.

According to the technical scheme provided by the embodiment of the disclosure, the entity information of the entities and the resource flow information between the entities are acquired; the preset entity table is generated based on the acquired entity information of the entities, the preset resource flow table is generated based on the entity information and the resource flow information among the entities, and the upstream and downstream nodes of each node can be distinguished by upstream and downstream structure division with the central node as a reference, so that the nodes and the resource flow relationship among the nodes can be constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

Other labels, objects and advantages of the present disclosure will become more apparent from the following detailed description of non-limiting embodiments when taken in conjunction with the accompanying drawings. In the drawings:

FIG. 1 shows a flow diagram of an entity relationship presentation method according to an embodiment of the present disclosure;

FIG. 2 shows a flow diagram of an entity relationship presentation method according to another embodiment of the present disclosure;

FIG. 3 shows a flow diagram of an entity relationship presentation method according to yet another embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating an application scenario of an entity relationship presentation method according to an embodiment of the present disclosure;

FIG. 5 shows a flow diagram of an entity relationship presentation method according to yet another embodiment of the present disclosure;

FIG. 6 is a block diagram of an entity relationship presentation apparatus according to an embodiment of the present disclosure;

FIG. 7 is a block diagram of an entity relationship presentation apparatus according to another embodiment of the present disclosure;

FIG. 8 is a block diagram showing the structure of an entity relationship exhibiting apparatus according to still another embodiment of the present disclosure;

FIG. 9 is a block diagram showing the structure of an entity relationship exhibiting apparatus according to still another embodiment of the present disclosure;

FIG. 10 shows a block diagram of an electronic device according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a computer system suitable for implementing an entity relationship presentation method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. Also, for the sake of clarity, parts not relevant to the description of the exemplary embodiments are omitted in the drawings.

In the present disclosure, it is to be understood that terms such as "including" or "having," etc., are intended to indicate the presence of labels, numbers, steps, actions, components, parts, or combinations thereof disclosed in the present specification, and are not intended to preclude the possibility that one or more other labels, numbers, steps, actions, components, parts, or combinations thereof are present or added.

It should be further noted that the embodiments and labels in the embodiments of the present disclosure may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.

Fig. 1 shows a flowchart of an entity relationship presentation method according to an embodiment of the present disclosure. As shown in fig. 1, the entity relationship display method includes the following steps S110 and S120:

in step S110, entity information of a specific entity is extracted from a preset entity table and resource flow information between a plurality of entities including the specific entity is extracted from a preset resource flow table.

In step S120, based on the extracted entity information of the specific entity and the extracted resource flow information between the plurality of entities including the specific entity, the specific entity is used as a central node, a non-central node representing an entity other than the specific entity and a central node are constructed and displayed according to an upstream and downstream structure of resource flow, and a resource flow relationship between the plurality of entities.

According to the technical scheme provided by the embodiment of the disclosure, the entity information of the specific entity is extracted from the preset entity table, and the resource flow information among a plurality of entities including the specific entity is extracted from the preset resource flow table; based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, the specific entity is taken as a central node, the central node and a non-central node representing the entities except the specific entity are constructed and displayed according to an upstream and downstream structure of resource flow, and the resource flow relationship among the plurality of entities, the upstream and downstream structure division with the central node as a reference can be used for distinguishing the upstream and downstream nodes of each node, so that the node and the resource flow relationship among each node are constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In this disclosure, resource flow may refer to the flow of various resources between various nodes. For example, the flow of resources, such as information, data, storage space, etc., between computer nodes that make up a network. Also for example, the flow of resources such as goods, services, assets (liquidity assets (such as cash), fixed assets, creditory assets, equity assets, intangible assets, etc.) among nodes for entities on behalf of an enterprise, institution, government, etc. Resource flow information may refer to information related to the flow of resources between entities. In the present disclosure, any real or virtual object that may flow or transition between nodes of a relationship graph may be considered a resource.

In this disclosure, an entity may refer to any object that may provide or receive a resource. For example, when the resource is a resource such as information, data, storage space, etc., the entity may be a computer or any electronic device. As another example, when the resource is a good, service, asset, etc., the entity may be a social organization such as a business, organization, government, etc. In the present disclosure, an entity may be represented by a node in a relationship graph.

Example one

In this embodiment of the present disclosure, how to generate an entity table based on the acquired entity information of the entity is described with a business as an example of the entity.

FIG. 5 shows a flowchart of an entity relationship presentation method according to yet another embodiment of the present disclosure. The embodiment shown in fig. 5 is different from the embodiment shown in fig. 1 in that steps S510 and S520 are further included.

In step S510, entity information of entities and resource flow information between entities are acquired.

In step S520, a preset entity table is generated based on the acquired entity information of the entities, and a preset resource flow table is generated based on the information of the entities and the resource flow information between the entities.

According to the technical scheme provided by the embodiment of the disclosure, the entity information of the entities and the resource flow information between the entities are acquired; and generating a preset entity table based on the acquired entity information of the entities, and generating a preset resource flow table based on the entity information and the resource flow information among the entities, wherein upstream and downstream nodes of each node can be distinguished by upstream and downstream structure division with the central node as a reference, so that the nodes and the resource flow relationship among the nodes can be constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In this embodiment of the present disclosure, the entity information of the enterprise may include: enterprise name, enterprise code, registration date, industry name, address, business scope, legal person, financial responsible person, etc. The following table 1 exemplifies the entity table of the enterprise:

TABLE 1

Name of an enterprise

Enterprise code

Date of registration

Name of trade

Address

Extent of operation

Legal person

Financial responsible person

AAA Corp

10001

20150102

Manufacturing industry

And A is omitted. . .

Manufacture …

Sheet …

King. . .

BBB Corp Ltd

10002

20160508

Service industry

And B, saving. . .

Service …

Plum …

Zhao. . .

。。。

CCC Corp Ltd

11000

20130601

Agricultural production

And C, saving. . .

Production …

Money …

And (5) grandchild. . .

In this embodiment of the present disclosure, how to generate a resource flow table based on resource flow information between entities is described with funds, goods, or services of an enterprise as an example of a resource.

In this embodiment of the present disclosure, resource flow between enterprises may be embodied by invoices. Thus, resource flow between enterprises may be constructed based on the information documented by the invoices. In this case, the resource flow information between enterprises may include: invoice ID, seller name, seller identification number (taxpayer identification number), buyer name, buyer identification number (taxpayer identification number), invoicing date, commodity and service name, amount of money and the like. The resource flow table of the enterprise is shown in table 2 as an example below:

TABLE 2

In this embodiment of the present disclosure, when a business is an entity and funds, goods, or services of the business are resources, query information related to the flow of resources between a particular business and a plurality of businesses including the particular business may refer to querying by entering, for example, a name of the particular business or an identification number of the business.

In one embodiment of the present disclosure, the query information includes screening information for screening the entity represented by the central node (e.g., a particular business in the foregoing embodiments) and resource flow relationships between the plurality of entities. For example, the query information may also include some structural filtering information (screening information), such as the start and stop date of invoice issuing, topk1 (k 1 bits before transaction amount) of a business immediately upstream of the business (directly providing resources to a particular business), topk2 (k 2 bits before transaction amount) of a business immediately downstream (directly providing resources by a particular business), topk3 (k 3 bits before transaction amount) of a business indirectly upstream (indirectly providing resources to a particular business), topk4 (k 4 bits before transaction amount) of a business indirectly downstream (indirectly providing resources by a particular business), a resource flow relationship filtering amount (e.g., invoices smaller than the amount and related information of the invoice are not shown), topk5 goods or services for each resource flow relationship (goods or services with transaction amount between each business party and a seller party ranked in k5 bits before purchase amount), and so on. The information can be filtered from the entity table or the resource flow table by the structure without inquiring all the information, so that the system resource can be saved. It is understood that k1, k2, k3, k4 and k5 are all positive integers. It is noted that in one embodiment of the present disclosure, a central node may have no sibling nodes, but only upstream nodes (including direct upstream nodes and indirect upstream nodes) and/or downstream nodes (including direct downstream nodes and indirect downstream nodes). In another embodiment of the present disclosure, the central node may have sibling nodes, i.e., topk6 (k 6 digits before transaction amount) of a business immediately downstream of topk1 of a business immediately upstream of the business, and/or topk7 (k 7 digits before transaction amount) of a business immediately upstream of topk2 of a business immediately downstream of the business, where both k6 and k7 are positive integers.

In this embodiment of the present disclosure, the entity information of the queried specific entity may be extracted from the business entity table, e.g., table 1, through the aforementioned query information, and the resource flow information between a plurality of entities including the queried specific entity may be extracted from the resource flow table, e.g., table 2.

In this embodiment of the present disclosure, resource flow relationships between a central node and non-central nodes representing enterprises other than a specific enterprise and a plurality of enterprises are constructed and exposed in an upstream and downstream structure of resource flow with the specific enterprise as a central node based on entity information of the specific enterprise extracted from an enterprise entity table such as table 1 and resource flow information between the plurality of enterprises including the specific enterprise extracted from a resource flow table such as table 2. Namely, based on the enterprise information and resource flow information of the query, a node structure is constructed in which the specific enterprise to be queried is the central node and the other queried enterprises are non-central nodes. In the node structure, nodes except the central node are divided into an upstream node, a peer node and a downstream node according to a resource flow relation with the central node.

In this embodiment of the present disclosure, step S110 may further include: in response to receiving query information related to resource flows between a specific entity and a plurality of entities including the specific entity, entity information of the specific entity is extracted from a preset entity table and resource flow information between the plurality of entities including the specific entity is extracted from the preset resource flow table. That is, corresponding information may be extracted from the entity table and the resource flow table in response to the received query information. Therefore, the entity relation showing method according to the embodiment of the disclosure is convenient to actually execute.

A schematic diagram of an entity relationship constructed by using the entity relationship display method in the embodiment according to the present disclosure is described below with reference to the second embodiment.

Example two

Fig. 4 is a flowchart illustrating an application scenario of the entity relationship displaying method according to an embodiment of the present disclosure.

In an example of an entity relationship structure constructed according to an embodiment of the present disclosure as shown in fig. 4, resource flow relationships between a central node 400 and non-central nodes, and a plurality of nodes, constructed and illustrated according to an upstream and downstream structure of resource flow between nodes, are shown. In the embodiment shown in fig. 4, the resource flow relationship between nodes is represented by arrowed lines (including straight lines or curved lines), and the arrowed lines include broken lines, thin solid lines, and thick solid lines. In embodiments of the present disclosure, the arrowed line may be referred to as an edge, the direction of the edge being from the resource provider to the resource recipient. In the embodiment of the present disclosure, an edge shown in a dotted line form may be referred to as a dotted line edge, an edge shown in a thin solid line form may be referred to as a solid line edge, and an edge shown in a thick solid line form may be referred to as a thick line edge.

In the embodiment shown in fig. 4, the dashed, solid and thick line sides may represent different magnitudes or different classes of resource flow relationships, respectively. It will be understood by those skilled in the art that although the resource flow relationships are shown as dashed, solid and bold lines in fig. 4, more or fewer or other different forms of resource flow relationships may exist and are not described in detail in this disclosure.

As shown in fig. 4, the middle column of nodes are level 0 nodes, and the level 0 nodes include a central node 400 and peer nodes having no edge (i.e., resource providing relationship) with the central node 400. For example, peer nodes having no edges with the central node 400 include

nodes

411, 412, 413, 414, 415, 416, 417, and 418.

It is noted that the inclusion of a level 0 node in addition to the central node 400 is merely an example, and a level 0 node may include only the central node 400. In this case, the nodes and the resource flow relationship between the nodes displayed by the method for displaying the entity relationship in the surgical method according to the present disclosure can be focused on the central node, which is beneficial to simplify the displayed node and the view of the resource flow relationship between the nodes, and is convenient for the user to master other nodes and resource flow relationships closely related to the central node.

As shown in fig. 4, according to the upstream and downstream structure of resource flow, a node that supplies resources to the center node 400 is an upstream node of the center node 400. In one embodiment, the nodes upstream of the central node 400 are nodes that provide resources directly or indirectly to the central node 400. As shown in fig. 4, the upstream nodes of the central node 400 include an upstream level 1 node that is an upstream node that directly provides resources to the central node 400 and an upstream level 2 node that indirectly provides resources to the central node 400.

As shown in fig. 4,

nodes

421, 422 and 423 in the upstream level 1 node provide resources directly to the central node 400. As shown in FIG. 4,

nodes

431, 432, 433, 434, 435, 436, and 437 in the upstream level 2 node provide resources directly to

nodes

421, 422, and 423, respectively, in the upstream level 1 node. That is,

nodes

431, 432, 433, 434, 435, 436 and 437 in the upstream level 2 node indirectly provide resources to central node 400 through

nodes

421, 422 and 423 in the upstream level 1 node. In addition, the

nodes

421, 422, and 423 in the upstream level 1 node may also directly provide resources to some or all of the level 0

nodes

411, 412, 413, 414, 415, 416, 417, and 418.

In addition, although

only nodes

431, 432, 433, 434, 435, 436, and 437 in the upstream level 2 node are shown in FIG. 4 as each providing resources directly to only one of

nodes

421, 422, and 423 in the upstream level 1 node, this is merely an example. In another embodiment,

nodes

431, 432, 433, 434, 435, 436, and 437 in the upstream level 2 node may each provide resources directly to multiple ones of

nodes

421, 422, and 423 in the upstream level 1 node, or directly to other nodes not shown in the upstream level 1 node.

As shown in fig. 4, according to the upstream and downstream structure of resource flow, the node to which the central node 400 supplies resources is a downstream node of the central node 400. In one embodiment, the nodes downstream of the central node 400 are nodes that are directly or indirectly provided with resources by the central node 400. As shown in fig. 4, the downstream nodes of the central node 400 include a downstream level 1 node that is directly provided with resources by the central node 400 and a downstream level 2 node that is indirectly provided with resources by the central node 400.

As shown in FIG. 4, central node 400 provides resources directly to

nodes

441, 442, 443, and 444 in the downstream level 1 nodes. As shown in FIG. 4,

nodes

441, 442, 443, and 444 in the downstream level 1 node provide resources directly to

nodes

451, 452, 453, 454, 455, 456, and 457, respectively, in the downstream level 2 node. That is, central node 400 provides resources indirectly to

nodes

451, 452, 453, 454, 455, 456, and 457 in downstream level 2 nodes through

nodes

441, 442, 443, and 444 in downstream level 1 nodes. In addition, some or all of the level 0

nodes

411, 412, 413, 414, 415, 416, 417, and 418 may also provide resources directly to

nodes

441, 442, 443, and 444 in the downstream level 1 node.

In addition, although

only nodes

451, 452, 453, 454, 455, 456, and 457 in the downstream level 2 node are each shown in FIG. 4 as being directly provided with resources by only one of

nodes

441, 442, 443, and 444 in the downstream level 1 node, this is merely an example. In another embodiment,

nodes

451, 452, 453, 454, 455, 456, and 457 of the downstream level 2 nodes may each be directly provided with resources by multiple ones of

nodes

441, 442, 443, and 444 of the downstream level 1 nodes, or by other nodes not shown in the downstream level 1 nodes.

In an embodiment of the present disclosure, the peer node of the central node is a level 0 node; among the N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as the upstream level 1 node; among the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream M-level nodes starting from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1.

According to the technical scheme provided by the embodiment of the disclosure, the peer node passing through the central node is the 0 th node; among the N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as the upstream level 1 node; in M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream level M nodes from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1, and the upstream and downstream nodes at each level can be clearly divided by taking the central node as a reference, so that the resource flow relationship between the nodes and each node can be clearly constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

It should be noted that although fig. 4 shows a 5-level upstream and downstream structure of the center node 400, the 5-level upstream and downstream structure may be integrally divided into an upstream, present-level, and downstream 3-level structure. Wherein, the upstream level 1 node and the upstream level 2 node may be collectively regarded as an upstream node, and the downstream level 1 node and the downstream level 2 node may be collectively regarded as a downstream node. In addition, those skilled in the art can understand that the number of stages of the upstream node is not limited to 2 stages shown in fig. 4, and may be 1 stage, or may be 3 stages or more; the number of stages of the downstream node is not limited to 2 stages shown in fig. 4, and may be 1 stage, or 3 or more stages. Additionally, it is understood that the number of levels of upstream nodes may be different from the number of levels of downstream nodes.

As shown in fig. 4, the same level nodes may be presented in the same or different manner, wherein the central node 400 is presented in a different manner than the same level nodes (level 0

nodes

411, 412, 413, 414, 415, 416, 417, and 418) of the central node 400. For example, the presentation comprises presentation using at least one of a symbol, a position, a color, a shape, and an animation effect.

As shown in fig. 4, the nodes may be exposed by setting different sizes for different nodes. For example, the size of the central node 400 is the largest, and the size of the same level nodes (level 0

nodes

411, 412, 413, 414, 415, 416, 417, and 418) of the central node 400 is the smallest. The

nodes

421, 422 and 423 in the upstream level 1 nodes are the same size as the

nodes

441, 442, 443 and 444 in the downstream level 1 nodes, just smaller than the central node 400.

Nodes

431, 432, 433, 434, 435, 436 and 437 in the upstream level 2 node are the same size as

nodes

451, 452, 453, 454, 455, 456 and 457 in the downstream level 2 node, larger than the same level node of the central node 400 (level 0

nodes

411, 412, 413, 414, 415, 416, 417 and 418), but smaller than

nodes

421, 422 and 423 in the upstream level 1 node and

nodes

441, 442, 443 and 444 in the downstream level 1 node.

In another example, different nodes may be exposed by at least one of different symbols, positions, colors, shapes, animation effects.

As shown in fig. 4, the flow of the same number of resources between different nodes may be shown in the same or different manners, including at least one of symbols, positions, colors, shapes, and animation effects. Although the flow of resources between different nodes is shown as dotted, solid and thick line edges in fig. 4, respectively, it is also possible to show different resource flow relationships (resource flow relationships between different pairs of directly upstream and downstream nodes) by at least one of different symbols, positions, colors, shapes, animation effects.

The entity relationship display method according to the embodiment of the present disclosure will be described below by combining the second embodiment with the embodiment described with reference to fig. 1.

In one embodiment, step S120 shown in fig. 1 includes: based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, constructing and displaying a resource flow relationship among the entities and the plurality of entities according to an upstream and downstream structure in a manner that the specific entity is taken as a central node and an entity other than the specific entity is taken as one of an upstream node, a downstream node and a peer node of the central node, wherein an entity providing resources to the specific entity is taken as the upstream node of the central node, an entity providing resources by the specific entity is taken as the downstream node of the central node, and a node providing resources by the upstream node and/or the downstream node in the nodes other than the central node is taken as the peer node of the central node.

According to the technical scheme provided by the embodiment of the present disclosure, based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity, the resource flow relationship among the plurality of entities, which is based on the specific entity as a central node, a non-central node representing the central node and entities other than the specific entity, and the plurality of entities, is constructed and displayed according to an upstream and downstream structure of resource flow by using the specific entity as a central node, and includes: constructing and exhibiting a resource flow relationship between the entity and the plurality of entities in an upstream and downstream structure in such a manner that the specific entity is a central node and the entity other than the specific entity is one of an upstream node, a downstream node, and a peer node of the central node, based on the extracted entity information of the specific entity and the extracted resource flow information between the plurality of entities including the specific entity, wherein the upstream node of the central node is an entity providing resources to the specific entity, the downstream node of the central node is an entity providing resources to the specific entity, the peer node of the central node is a node providing resources to the upstream node and/or a node providing resources to the downstream node among the nodes other than the central node, and the upstream and downstream nodes of the respective nodes can be distinguished by upstream and downstream structure division with respect to the central node, so that the nodes and the resource flow relationship among the nodes can be constructed and shown. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

The following describes an entity relationship display method according to an embodiment of the present disclosure, in which the first embodiment and the second embodiment are combined with the embodiment described with reference to fig. 1.

In an embodiment of the present disclosure, the enterprises may serve as nodes in fig. 4, and the resource flow relationship between the enterprises (the resource flow relationship in which the seller points to the buyer for the invoice) may serve as edges in fig. 4. Thus, the entity table of an enterprise may be referred to as a node table and the resource flow table of the enterprise may be referred to as an edge table. In embodiments of the present disclosure, each row in the node table is information for one enterprise. Each row in the edge table is information on the granularity of goods or services for one invoice. Since there may be multiple information for goods or services in one invoice, there may be multiple lines in the side table for the same invoice, and there may also be multiple invoices between the same seller and buyer. That is, there is a one-to-many relationship between the seller and buyer pairs and the invoice, and there is also a one-to-many relationship between the invoice and the goods or services.

In the embodiment of the present disclosure, when querying a structure of a business and a business resource flow relationship for a specific business, a name of the business or an identification number of the business may be input, and some structure filtering information may be provided, such as a start and stop date of invoicing, topk1 (k 1 bits before transaction amount) of a business immediately upstream of the business, topk2 (k 2 bits before transaction amount) of a business immediately upstream, topk3 (k 3 bits before transaction amount), topk4 (k 4 bits before transaction amount), a resource flow relationship filtering amount (for example, invoices smaller than the amount and related information of the invoices are not shown), topk5 goods or services of each resource flow relationship (goods or services of which the transaction amount between each business buyer and seller pair is ranked in k5 bits before transaction amount), and the like. The information can be filtered from the entity table or the resource flow table by the structure without inquiring all the information, so that the system resource can be saved. It is understood that k1, k2, k3, k4 and k5 are all positive integers.

In the query process, first, invoice data having an invoicing date within the time window of the start and stop date may be selected based on the input start and stop date. Since the invoice data in the edge table is detail data with the goods or services as the granularity, the total transaction amount between each seller and buyer pair and the collection of the goods or services (the collection is the seller collection; and the collection is the buyer collection) need to be obtained by using the seller and buyer pairs as the granularity.

In the embodiment of the present disclosure, a specific enterprise to be queried may serve as a central node, and by querying the node table and the edge table, the resource flow relationship between the enterprise and multiple enterprises may be constructed and displayed according to an upstream and downstream structure in a manner that the specific enterprise serves as the central node, and an enterprise other than the specific enterprise serves as one of an upstream node, a downstream node, and a peer node of the central node. That is, an enterprise resource flow relationship diagram may be constructed as shown in FIG. 4. The central node 400 in fig. 4 is a peer node of the central node, and is configured to serve, for a specific enterprise to be queried, an enterprise providing resources to the specific enterprise as an upstream node (seller in the invoice) of the central node 400, serve an enterprise provided resources by the specific enterprise as a downstream node (buyer in the invoice) of the central node 400, and serve, among nodes other than the central node 400, a node provided resources by the upstream node (seller in the invoice) and/or providing resources to the downstream node (buyer in the invoice).

In an embodiment of the present disclosure, an upstream node of a central node is an entity that directly or indirectly provides resources to a specific entity, a downstream node of the central node is an entity that is directly or indirectly provided with resources by the specific entity, and a peer node of the central node is an entity that is directly provided with resources to the specific entity among entities other than the specific entity and/or directly provides resources to the entity that is directly provided with resources by the specific entity.

According to the technical scheme provided by the embodiment of the disclosure, an upstream node of a central node is an entity which directly or indirectly provides resources for a specific entity, a downstream node of the central node is an entity which is directly or indirectly provided with resources by the specific entity, a peer node of the central node is an entity which directly provides resources for the specific entity in entities other than the specific entity and/or an entity which directly provides resources for the entity which is directly provided with resources by the specific entity, and the direct or indirect upstream and downstream nodes of each node can be distinguished by dividing an upstream and downstream structure with the central node as a reference, so that the nodes and the resource flow relationship between each node can be constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

As shown in fig. 4, in the case where the central node 400 is a specific enterprise, upstream nodes of the central node 400 are enterprises (upstream level 1 node and upstream level 2 node) that directly or indirectly provide resources to the specific enterprise, downstream nodes of the central node are enterprises (downstream level 1 node and downstream level 2 node) that are directly or indirectly provided with resources by the specific enterprise, and peer nodes (level 0 node) of the central node are nodes that are provided with resources by the upstream nodes (upstream level 1 node) and/or provided with resources to the downstream nodes (downstream level 1 node).

The specific manner of showing the enterprises and the resource flow relationship between the enterprises will be further described below on the basis of the combination of the embodiment, the first embodiment and the second embodiment described with reference to fig. 1.

In an embodiment of the present disclosure, step S120 in fig. 1 may include: and showing the nodes through at least one of symbols, positions, colors, shapes and animation effects according to at least one of the levels, types and node states of the nodes, and showing resource flow among the nodes through at least one of symbols, positions, colors, shapes and animation effects.

According to the technical scheme provided by the embodiment of the disclosure, the resource flow relationship between a central node and a non-central node representing entities other than a specific entity and among a plurality of entities is constructed and displayed according to an upstream and downstream structure of resource flow by taking the specific entity as the central node, and the resource flow relationship comprises the following steps: according to at least one of the level, the type and the node state of the node, the node is shown through at least one of symbols, positions, colors, shapes and animation effects, and the resource flow between the nodes is shown through at least one of symbols, positions, colors, shapes and animation effects, so that the role of each node in a node system constructed by taking the central node as a reference and the relationship between the nodes can be clearly shown, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In an embodiment of the present disclosure, step S120 in fig. 1 may include: and displaying the same-level nodes in the same or different modes, wherein the central node is displayed in a mode different from the same-level nodes of the central node, and the mode comprises at least one of symbols, positions, colors, shapes and animation effects.

According to the technical scheme provided by the embodiment of the present disclosure, by using a specific entity as a central node, and constructing and displaying a non-central node of the central node and entities other than the specific entity according to an upstream and downstream structure of resource flow, and resource flow relationships among a plurality of entities, the method further includes: the same-level nodes are displayed in the same or different modes, wherein the display mode of the central node is different from that of the same-level nodes of the central node, and the mode comprises at least one of symbol, position, color, shape and animation effect, so that the roles of each node in a node system constructed by taking the central node as a reference and the relationship among the nodes can be clearly displayed, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In an embodiment of the present disclosure, step S120 in fig. 1 may include: and showing the flow of the same amount of resources among different nodes in the same or different modes, wherein the modes comprise at least one of symbols, positions, colors, shapes and animation effects.

According to the technical scheme provided by the embodiment of the present disclosure, by using a specific entity as a central node, and constructing and displaying a non-central node of the central node and entities other than the specific entity according to an upstream and downstream structure of resource flow, and resource flow relationships among a plurality of entities, the method further includes: the flow of the same quantity of resources among different nodes is shown in the same or different modes, wherein the modes comprise at least one of symbols, positions, colors, shapes and animation effects, so that the resource flow relationship among the nodes can be clearly shown, and the resource flow relationship among the nodes is prevented from being mixed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In one example, to focus on a particular enterprise as a central node, when the enterprise and the resource flow relationships between the enterprises are exposed, the following may be exposed.

For the central node in the level 0 node: for the center node, color-0 is used for display, and the node size is size-0, the display position being the center of the graph.

For upstream level 1 nodes: the enterprise represented by the upstream level 1 node is topk1 (k 1 digits prior to the transaction amount) of the particular enterprise (central node 400) directly upstream of the enterprise, displayed using color-10, and the node size using size-10; the display position is to the left of the center node 400.

For downstream level 1 nodes: the business represented by the downstream level 1 node is topk2 (k 2 digits prior to the transaction amount) for that particular business (central node 400) directly downstream of the business, shown using color 11, node size using size-11, and shown to the right of the central node 400 of the graph.

For upstream level 2 nodes: the upstream level 2 node is the immediately upstream business to the upstream level 1 node, i.e., the topk3 (k 3 digits before the transaction amount) of the immediately upstream business to topk1 of the particular business (central node 400), displayed using color-100, node size using size-100, and displayed in a position to the left of the upstream level 1 node.

For downstream level 2 nodes: the downstream level 2 node is the immediately downstream business of topk4 (k 4 before the transaction amount) for the downstream level 1 node, i.e., the topk2 immediately downstream business of the particular business (central node 400), displayed using color-101, the node size using size-101, and the display location to the right of the downstream level 1 node.

For peer nodes of the central node in level 0 nodes: sibling nodes of the central node in level 0 nodes may include nodes immediately downstream of the upstream level 1 node, i.e., topk6 (k 6 before the transaction amount) of the immediately upstream enterprise of topk1 of the particular enterprise (central node 400), displayed using color-1001, node size using size-1001, displayed at the right of the upstream level 1 node; sibling nodes of the central node in level 0 nodes may also include the node immediately upstream of the downstream level 1 node, i.e., the topk7 (k 7 before the transaction amount) of the topk2 immediately downstream business of the particular business (central node 400), displayed using color-1002, node size using size-1002, displayed in a position to the left of the downstream level 1 node.

It will be appreciated by those skilled in the art that the defined node color "color-xxxx" can be a color customized by those skilled in the art in light of the teachings of the present disclosure, and that those skilled in the art can name node colors in other ways. Those skilled in the art will appreciate that the "size-xxxx" that defines the node size may be a size customized by those skilled in the art in light of the teachings of the present disclosure, and those skilled in the art may name the node size in other ways.

It is to be understood that some or all of the sibling nodes of the central node (level 0 nodes other than the central node) among the level 0 nodes may be both an enterprise immediately downstream of the enterprise immediately upstream of the particular enterprise (central node 400) and an enterprise immediately upstream of the enterprise immediately downstream of the particular enterprise (central node 400).

It should be noted that, in the embodiment of the present disclosure, the level 0 node may only include the central node 400, and not include the peer node of the aforementioned central node, and the nodes and the resource flow relationship between the nodes displayed by the entity relationship displaying method may be more focused on the central node, which is beneficial to simplify the diagram of the displayed nodes and the resource flow relationship between the nodes, and is convenient for the user to master other nodes and resource flow relationships closely related to the central node.

In one embodiment of the present disclosure, a direct downstream node of the upstream level 1 node and/or a direct upstream node of the downstream level 1 node other than the central node may be exhibited by the entity relationship exhibiting method, but the direct downstream node of the upstream level 1 node and/or the direct upstream node of the downstream level 1 node other than the central node is not taken as a peer node (level 0 node) of the central node. In this case, a node immediately downstream of the upstream level 1 node other than the center node may be referred to as a downstream level 1 node of the upstream level 1 node, and a node immediately upstream of the downstream level 1 node may be referred to as an upstream level 1 node of the downstream level 1 node.

In one embodiment of the present disclosure, for edges between nodes, the direction of the edge may be represented using a curved line with an arrow, the direction of the arrow pointing from the seller to the buyer. In one example, although not shown in FIG. 4, each edge may carry a good or service that the seller sells to the buyer's topk5 (k 5 digits before the transaction amount) and each good or service carries an amount. In addition, each edge may carry the total amount of goods or services sold by the seller to the purchaser. In addition, as shown in FIG. 4, the amount may also be differentiated by different patterns of edges. For example, when displaying resource flows between nodes, 2/3 that exceeds the set maximum amount of money uses a thick solid line, 1/3 to 2/3 that is the set maximum amount of money uses a solid line, and 1/3 that is less than the set maximum amount of money uses a dashed line.

In one embodiment of the present disclosure, the aforementioned topks (topk 1-topk 7) may all be calculated using amount sizes and may be ordered in order from large to small. For example, a topk upstream business of a particular business (central node) is the top-ranked topk business for the amount sold to that particular business. However, those skilled in the art will appreciate that the present disclosure is not so limited and that the amounts may be ordered sequentially from small to large or otherwise.

It is to be appreciated that while the foregoing has been described in terms of a business, the nodes of embodiments of the present disclosure are not limited to businesses, and that the nodes at which the flow of funds, goods, and services occurs may include various business entities, such as businesses, schools, governments, and the like. In one embodiment of the present disclosure, the entity is a business entity, and the resource flow relationship between the plurality of entities is a sales relationship of goods and/or services between the plurality of business entities, wherein, in the upstream and downstream configuration, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services.

According to the technical scheme provided by the embodiment of the disclosure, the entity is a business entity, and the resource flow relationship among the multiple entities is the sales relationship of the commodities and/or the services among the multiple business entities, wherein in the upstream and downstream structure, the business entity selling the commodities and/or the services is upstream of the business entity purchasing the commodities and/or the services, and the upstream and downstream nodes representing the nodes of other business entities can be distinguished by dividing the upstream and downstream structure with the central node representing a specific business entity as a reference, so that the sales relationship of the commodities and/or the services among the business entities and the various business entities can be constructed and displayed. Therefore, the business roles of the business entities and the sales relations of the goods and/or services in the sales process of the goods and/or services are identified, and potential problems in a system formed by the business entities can be controlled accordingly.

In one embodiment of the present disclosure, at the same level of nodes, the ordering of the nodes in the same level may be highlighted by a slight size change, with the top-ranked business being larger in size.

In one embodiment of the present disclosure, for enterprises spanning multiple levels, for example, some enterprises are directly upstream and downstream enterprises of a specific enterprise represented by a central node, and may also be indirectly upstream and downstream enterprises, the display mode of the node is a combined display mode according to a preset rule, a display position is determined according to the preset rule, and the node is displayed in the combined display mode at the determined display position. For example, the display position uses the position closest to the center point, using the composite color of the colors of the characters where the polygon node is located, and the size of the display using the average size of the characters where the node is located. For another example, the node may be presented by additionally determining at least one of a symbol, a position, a color, a shape, and an animation effect different from all the characters in which the node is located. For another example, the display position of the multi-role node may select the position of the role where the edge represents the largest amount. Of course, the present disclosure is not limited to the foregoing examples, and nodes displaying a plurality of roles may be displayed using various ways according to different preset rules.

In one embodiment of the present disclosure, step S120 includes: and in response to detecting that a node other than the central node is in multiple stages at the same time, synthesizing the display mode of the node according to a preset rule, determining the display position of the node, and displaying the node in the synthesized display mode at the display position.

According to the technical scheme provided by the embodiment of the disclosure, the resource flow relationship between a central node and a non-central node representing entities other than a specific entity and among a plurality of entities is constructed and displayed according to an upstream and downstream structure of resource flow by taking the specific entity as the central node, and the resource flow relationship comprises the following steps: in response to the fact that a node except the central node is detected to be in multiple stages at the same time, the display mode of the node is synthesized according to the preset rule, the display position of the node is determined, the node is displayed in the display position in the synthesized display mode, the upstream and downstream nodes of each stage can be clearly divided by taking the central node as a reference, the resource flow relationship between the node and each node can be clearly constructed and displayed, and the role of the node in the resource flow relationship is prevented from being mixed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

Fig. 2 shows a flowchart of an entity relationship presentation method according to another embodiment of the present disclosure. The embodiment shown in fig. 2 is different from the embodiment shown in fig. 1 in that it further includes step S210.

In step S210, entity information of an entity represented by the operated node is exposed in response to the operation on the exposed node.

In one embodiment of the present disclosure, each node may have various label information thereon. In one example, the tag information of a node may be viewed when a mouse hovers over the node. In another example, the information of the node can be viewed through other implementation manners, for example, the node information is displayed by right clicking a mouse and then listing, or the node information is displayed by listing after clicking the node by a single mouse, and the like.

Fig. 3 shows a flowchart of an entity relationship presentation method according to another embodiment of the present disclosure. The embodiment shown in fig. 3 is different from the embodiment shown in fig. 1 in that it further includes step S310.

In step S310, resource flow information between nodes represented by the operated resource flow relationship is exhibited in response to the operation on the resource flow relationship between the exhibited nodes.

In one embodiment of the present disclosure, to highlight structural information (resource flow relationships) between nodes, a certain amount (e.g., topk5) of goods or services information may be displayed on each edge. For example, the goods or services information represented by each edge may be displayed by hovering over the edge using a mouse. In another example, the information of the side can be viewed through other implementation manners, such as right clicking the mouse to display the information of the side in the list, or clicking the mouse to display the information of the side in the list after one side is clicked, and the like.

In an embodiment of the present disclosure, an entity relationship display method is provided, including:

According to the technical scheme provided by the embodiment of the disclosure, the entity information of a specific entity is obtained, and the resource flow information among a plurality of entities including the specific entity is obtained; the specific entity is used as a central node, the central node and a non-central node representing entities other than the specific entity are displayed, and the resource flow relationship among a plurality of entities, the upstream node and the downstream node of each node can be distinguished by structural division with the central node as a reference, so that the nodes and the resource flow relationship among the nodes are constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

The solution of this embodiment differs from the solution of the embodiment described with reference to fig. 1 in that: 1. the corresponding information is not limited to be acquired from the entity table and the resource flow table, but the entity information and the resource flow information can be acquired in any mode; 2. the resource flow relationship between the plurality of nodes including the center node and the plurality of nodes is shown without limitation in a particular manner. It can be understood by those skilled in the art that the technical solutions of the embodiments can be combined with the embodiments described with reference to fig. 1 to 5, so as to achieve the technical effects achieved by the embodiments described with reference to fig. 1 to 5. For details, reference may be made to the description above with reference to fig. 1 to 5, and details thereof are not described herein again.

Fig. 6 shows a block diagram of an entity relationship presentation apparatus according to an embodiment of the present disclosure.

As shown in fig. 6, the entity relationship exposing apparatus 600 includes an extracting module 610 and a constructing and exposing module 620.

The extraction module 610 is configured to extract entity information of the specific entity from a preset entity table and extract resource flow information between a plurality of entities including the specific entity from a preset resource flow table.

The construction and presentation module 620 is configured to construct and present a resource flow relationship between a central node and a non-central node representing an entity other than the specific entity, and a plurality of entities, with the specific entity as a central node, in an upstream and downstream structure of resource flow, based on the extracted entity information of the specific entity and the extracted resource flow information between the plurality of entities including the specific entity.

According to the technical scheme provided by the embodiment of the disclosure, the extracting module is configured to extract entity information of the specific entity from a preset entity table and extract resource flow information among a plurality of entities including the specific entity from a preset resource flow table; and the building and displaying module is configured to build and display a non-central node representing entities other than the specific entity and the central node according to upstream and downstream structures of resource flow and resource flow relations among the entities by taking the specific entity as a central node based on the extracted entity information of the specific entity and the extracted resource flow information among the entities including the specific entity, and the upstream and downstream structures based on the central node are divided to distinguish the upstream and downstream nodes of each node, so that the nodes and the resource flow relations among the nodes are constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In one embodiment of the present disclosure, the build and presentation module 620 is further configured to:

According to the technical scheme provided by the embodiment of the disclosure, the construction and display module is further configured to: constructing and exhibiting a resource flow relationship between entities and a plurality of entities in an upstream and downstream structure in such a manner that an entity other than the specific entity is one of an upstream node, a downstream node, and a peer node of the central node, with the specific entity being a central node, and with entities other than the specific entity being one of the upstream node, the downstream node, and the peer node, wherein an entity providing resources to the specific entity is taken as the upstream node of the central node, an entity providing resources to the specific entity is taken as the downstream node of the central node, and a node providing resources to the upstream node and/or the downstream node among the nodes other than the central node is taken as the peer node of the central node, and the upstream and downstream nodes of each node may be distinguished by dividing the upstream and downstream structure with respect to the central node, so that the nodes and the resource flow relationship among the nodes can be constructed and shown. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In one embodiment of the present disclosure, an upstream node of the central node is an entity that directly or indirectly provides resources to the specific entity, a downstream node of the central node is an entity that is directly or indirectly provided with resources by the specific entity, and a peer node of the central node is an entity that is directly provided with resources to the specific entity among entities other than the specific entity and/or directly provides resources to an entity that is directly provided with resources by the specific entity.

In one embodiment of the present disclosure, the peer node of the central node is a level 0 node; among N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as an upstream level 1 node; among the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream M-level nodes starting from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1.

According to the technical scheme provided by the embodiment of the disclosure, the construction and display module is further configured to: in response to the fact that a node except the central node is detected to be in multiple stages at the same time, the display mode of the node is synthesized according to a preset rule, the display position of the node is determined, the node is displayed in the display position in the synthesized display mode, and the upstream and downstream nodes of each stage can be clearly divided by taking the central node as a reference, so that the resource flow relationship between the node and each node can be clearly constructed and displayed, and the role of the node in the resource flow relationship is prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, the construction and display module is further configured to: according to at least one of the level, the type and the node state of the node, the node is shown through at least one of symbols, positions, colors, shapes and animation effects, and the resource flow between the nodes is shown through at least one of symbols, positions, colors, shapes and animation effects, so that the role of each node in a node system constructed by taking the central node as a reference and the relationship between the nodes can be clearly shown, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, the construction and display module is further configured to: the same-level nodes are displayed in the same or different modes, wherein the display mode of the central node is different from that of the same-level nodes of the central node, and the mode comprises at least one of symbol, position, color, shape and animation effect, so that the roles of each node in a node system constructed by taking the central node as a reference and the relationships among the nodes can be clearly displayed, and the roles of the nodes in the resource flow relationship are prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

According to the technical scheme provided by the embodiment of the disclosure, the construction and display module is further configured to: the flow of the same amount of resources among different nodes is shown in the same or different modes, wherein the modes comprise at least one of symbols, positions, colors, shapes and animation effects, so that the resource flow relationship among the nodes can be clearly shown, and the resource flow relationship among the nodes is prevented from being mixed up. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

Fig. 7 shows a block diagram of an entity relationship exhibiting apparatus 700 according to another embodiment of the present disclosure. The embodiment shown in fig. 7 is different from the embodiment shown in fig. 6 in that a first display module 710 is further included.

The first exposure module 710 is configured to expose entity information of an entity represented by an operated node in response to an operation on the exposed node.

According to the technical scheme provided by the embodiment of the disclosure, the first display module is configured to display the entity information of the entity represented by the operated node in response to the operation on the displayed node, so that the specific information of the node can be clearly known, the service role and the resource flow relationship of the node in the resource flow can be conveniently identified, and the potential problems in the system formed by the nodes can be controlled accordingly.

Fig. 8 shows a block diagram of an entity relationship exhibiting apparatus 800 according to still another embodiment of the present disclosure. The embodiment shown in fig. 8 differs from the embodiment shown in fig. 6 by further including a second display module 810.

The second exposing module 810 is configured to expose resource flow information between the nodes represented by the operated resource flow relationship in response to the operation on the resource flow relationship between the exposed nodes.

According to the technical scheme provided by the embodiment of the disclosure, the second display module is configured to display the resource flow information between the nodes represented by the operated resource flow relation in response to the operation of the resource flow relation between the displayed nodes, so that the details of the resource flow relation between the nodes can be clearly understood, the service roles and the resource flow relation of the nodes in the resource flow can be conveniently identified, and the potential problems in the system formed by the nodes can be controlled accordingly.

In one embodiment of the present disclosure, the query information includes screening information for screening resource flow relationships between the entity represented by the non-central node and a plurality of entities.

In one embodiment of the present disclosure, the entities are business entities, and the resource flow relationship between the plurality of entities is a sales relationship of goods and/or services between the plurality of business entities, wherein, in the upstream and downstream configuration, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services.

Fig. 9 shows a block diagram of an entity relationship exhibiting apparatus 900 according to still another embodiment of the present disclosure. The embodiment shown in fig. 9 is different from the embodiment shown in fig. 6 in that the embodiment further includes an obtaining module 910 and a table generating module 920.

The obtaining module 910 is configured to obtain entity information of entities and resource flow information between entities.

The table generating module 920 is configured to generate a preset entity table based on the obtained entity information of the entities, and generate a preset resource flow table based on the information of the entities and resource flow information between the entities.

According to the technical scheme provided by the embodiment of the disclosure, the acquisition module is configured to acquire entity information of entities and resource flow information between the entities; the table generation module is configured to generate a preset entity table based on the acquired entity information of the entities, and generate a preset resource flow table based on the entity information and the resource flow information among the entities, so that upstream and downstream nodes of each node can be distinguished by upstream and downstream structure division with the central node as a reference, and a resource flow relationship between the nodes is constructed and displayed. Therefore, the service roles and the resource flow relation of the nodes in the resource flow are identified, and the potential problems in the system formed by the nodes can be controlled according to the service roles and the resource flow relation.

In the embodiments according to the present disclosure, the embodiments described with reference to fig. 6 to 9 may be combined with the embodiments described with reference to fig. 1 to 5, respectively, to achieve the technical effects of the technical solutions described with reference to fig. 1 to 5 in whole or in part.

The internal functions and structures of the entity relationship exhibition apparatus are described above, and in one possible design, the structure of the entity relationship exhibition apparatus may be implemented as an entity relationship exhibition device, as shown in fig. 10, and the processing device 1000 may include a processor 1001 and a memory 1002.

The memory 1002 is used for storing a program supporting the entity relationship display apparatus to execute the entity relationship display method in any one of the embodiments, and the processor 1001 is configured to execute the program stored in the memory 1002.

The memory 1002 is configured to store one or more computer instructions, which are executed by the processor 1001 to implement the steps of:

In one embodiment of the present disclosure, the constructing and displaying, with the specific entity as a central node, a non-central node representing an entity other than the specific entity and a plurality of entities according to an upstream and downstream structure of resource flow based on the extracted entity information of the specific entity and the extracted resource flow information between the plurality of entities including the specific entity, and the resource flow relationship between the plurality of entities includes:

In an embodiment of the present disclosure, the constructing and displaying, by taking the specific entity as a central node, a non-central node representing entities other than the specific entity and a non-central node according to an upstream and downstream structure of resource flow, and resource flow relationships between a plurality of entities includes:

In an embodiment of the present disclosure, the constructing and displaying, by taking the specific entity as a central node and according to an upstream and downstream structure of resource flow, a non-central node of the central node and a non-central node representing entities other than the specific entity, and a resource flow relationship among a plurality of entities further includes:

In one embodiment of the present disclosure, the one or more computer instructions are further executable by the processor 1001 to implement the steps of:

The processor 1001 is configured to perform all or some of the method steps described above.

The structure of the entity relationship display device may further include a communication interface, which is used for the entity relationship display device to communicate with other devices or a communication network.

The exemplary embodiments of the present disclosure also provide a computer storage medium, configured to store computer software instructions for the entity relationship display apparatus, where the computer software instructions include a program for executing the entity relationship display method in any of the embodiments, so as to achieve the technical effect of the method.

As shown in fig. 11, the computer system 1100 includes a Central Processing Unit (CPU)1101, which can execute various processes in the embodiments shown in fig. 1 to 5 described above according to a program stored in a Read Only Memory (ROM)1102 or a program loaded from a storage section 1108 into a Random Access Memory (RAM) 1103. In the RAM1103, various programs and data necessary for the operation of the system 1100 are also stored. The CPU1101, ROM1102, and RAM1103 are connected to each other by a bus 1104. An input/output (I/O) interface 1105 is also connected to bus 1104.

The following components are connected to the I/O interface 1105: an input portion 1106 including a keyboard, mouse, and the like; an output portion 1107 including a signal output unit such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 1108 including a hard disk and the like; and a communication section 1109 including a network interface card such as a LAN card, a modem, or the like. The communication section 1109 performs communication processing via a network such as the internet. A driver 1110 is also connected to the I/O interface 1105 as necessary. A removable medium 1111 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1110 as necessary, so that a computer program read out therefrom is mounted into the storage section 1108 as necessary.

In particular, according to embodiments of the present disclosure, the method described above with reference to fig. 1 may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a medium readable thereby, the computer program comprising program code for performing the data processing method of fig. 1. In such an embodiment, the computer program can be downloaded and installed from a network through the communication portion 1109 and/or installed from the removable medium 1111.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, a program segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units or modules described in the embodiments of the present disclosure may be implemented by software or hardware. The units or modules described may also be provided in a processor, and the names of the units or modules do not in some cases constitute a limitation of the units or modules themselves.

As another aspect, the present disclosure also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the apparatus in the above-described embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer-readable storage medium stores one or more programs which are used by one or more processors to perform the methods described in the present disclosure, thereby providing technical effects brought by the methods.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is possible without departing from the inventive concept. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims

1. An entity relationship display method is characterized by comprising the following steps:

2. The method of claim 1, wherein the constructing and displaying the central node and the non-central node representing the entity other than the specific entity according to the upstream and downstream structure of resource flow and the resource flow relationship among the plurality of entities with the specific entity as a central node based on the extracted entity information of the specific entity and the extracted resource flow information among the plurality of entities including the specific entity comprises:

3. The method as claimed in claim 2, wherein an upstream node of the central node is an entity directly or indirectly providing resources to the specific entity, a downstream node of the central node is an entity directly or indirectly provided resources by the specific entity, and a peer node of the central node is an entity directly provided resources to the specific entity among entities other than the specific entity and/or directly provided resources to an entity directly provided resources by the specific entity.

4. The method of claim 3, wherein the sibling node of the central node is a level 0 node; among N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as an upstream level 1 node; among the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream M-level nodes starting from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1.

5. The method of claim 4, wherein constructing and displaying the central node and non-central nodes representing entities other than the specific entity according to the upstream and downstream structure of resource flow by taking the specific entity as a central node and resource flow relationships among a plurality of entities comprises:

6. The method according to any one of claims 1 to 5, wherein the constructing and displaying the central node and the non-central node representing the entity other than the specific entity according to the upstream and downstream structure of resource flow by taking the specific entity as the central node and the resource flow relationship among the plurality of entities comprises:

7. The method of claim 6, wherein the constructing and displaying the resource flow relationship between the central node and non-central nodes representing entities other than the specific entity according to the upstream and downstream structure of resource flow with the specific entity as the central node, and the plurality of entities further comprises:

8. The method of claim 6, wherein the constructing and displaying the resource flow relationship between the central node and non-central nodes representing entities other than the specific entity according to the upstream and downstream structure of resource flow with the specific entity as the central node, and the plurality of entities further comprises:

9. The method of any of claims 1 to 5, further comprising:

10. The method of any of claims 1 to 5, further comprising:

11. The method according to any one of claims 1 to 5, wherein the query information comprises screening information for screening resource flow relationships between the entity represented by the non-central node and a plurality of entities.

12. The method of any one of claims 1 to 5, wherein the entities are business entities and the resource flow relationship between the plurality of entities is a sales relationship of goods and/or services between the plurality of business entities, wherein, in the upstream and downstream configuration, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services.

13. The method of any of claims 1 to 5, further comprising:

14. An entity relationship exhibiting device, comprising:

15. The apparatus of claim 14, wherein the build and show module is further configured to:

16. The apparatus as claimed in claim 15, wherein an upstream node of the central node is an entity directly or indirectly providing resources to the specific entity, a downstream node of the central node is an entity directly or indirectly provided resources by the specific entity, and a peer node of the central node is an entity directly provided resources to the specific entity among entities other than the specific entity and/or directly provided resources to an entity directly provided resources by the specific entity.

17. The apparatus of claim 16, wherein a sibling node of the central node is a level 0 node; among N-level upstream nodes of the central node, dividing the N-level upstream nodes into upstream level 1 nodes to upstream N-level nodes starting from a node directly providing resources to the level 0 node as an upstream level 1 node; among the M-level downstream nodes of the central node, the M-level downstream nodes are divided into downstream level 1 nodes to downstream M-level nodes starting from a node directly provided with resources by the level 0 node as the downstream level 1 node, wherein N and M are positive integers greater than 1.

18. The apparatus of claim 17, wherein the build and show module is further configured to:

19. The apparatus of any one of claims 14 to 18, wherein the build and display module is further configured to:

20. The apparatus of claim 19, wherein the build and show module is further configured to:

21. The apparatus of claim 19, wherein the build and show module is further configured to:

22. The apparatus of any one of claims 14 to 18, further comprising:

23. The apparatus of any one of claims 14 to 18, further comprising:

24. The apparatus according to any of claims 14 to 18, wherein the query information comprises screening information for screening resource flow relationships between the entity represented by the non-central node and a plurality of entities.

25. The apparatus of any one of claims 14 to 18, wherein the entities are business entities and the resource flow relationship between the plurality of entities is a sales relationship of goods and/or services between the plurality of business entities, wherein in the upstream and downstream configuration, the business entity selling the goods and/or services is upstream of the business entity purchasing the goods and/or services.

26. The apparatus of any one of claims 14 to 18, further comprising:

27. An entity relationship display method is characterized by comprising the following steps:

28. An electronic device comprising a memory and a processor; wherein,

the memory is to store one or more computer instructions, wherein the one or more computer instructions are to be executed by the processor to implement the method of any of claims 1-13, 27.

29. A readable storage medium having stored thereon computer instructions, which when executed by a processor, implement the method of any one of claims 1-13, 27.