Data display method, electronic equipment and storage medium

By acquiring and analyzing the flow direction of data between multiple entities and determining and displaying the target flow path, the problem of not being able to quickly detect data abnormal flow in the prior art is solved, and fast and effective data abnormality detection is achieved.

CN120066904APending Publication Date: 2025-05-30HANGZHOU ALICLOUD FEITIAN INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311620210.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-11-28
Publication Date
2025-05-30

AI Technical Summary

Technical Problem

The prior art cannot quickly detect the abnormal flow of data, resulting in abnormal data, resulting in loss.

Method used

By obtaining the data to be displayed, based on the flow direction of the data between multiple entities, it is determined whether there is a target flow path (including the first entity and the last entity duplicate), and displays it when it exists.

Benefits of technology

It realizes rapid detection of data abnormal flow direction, improves the efficiency of data abnormal detection, and avoids losses caused by data abnormality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120066904A_ABST
    Figure CN120066904A_ABST
Patent Text Reader

Abstract

The invention discloses a data display method, electronic equipment and a storage medium. The method is applied to the field of cloud computing in a cloud network and comprises the steps that data to be displayed are acquired, and the data to be displayed circulate among a plurality of entities; based on the flow direction of the to-be-displayed data among the multiple entities, whether a target flow path exists among the multiple entities is determined, and the first entity and the last entity contained in the target flow path are repeated; and under the condition that the target flow path exists among the plurality of entities, displaying the target flow path. The technical problem that the abnormal flow direction of the data cannot be rapidly detected in the prior art is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of cloud computing in a cloud network. Specifically, it relates to a data display method, an electronic device, and a storage medium. Background Art

[0002] In data lineage, "loops" only occur in some special scenarios or when there are configuration errors in user data development tasks. Therefore, once a looped data lineage appears, attention needs to be paid to correct the data dependencies and avoid losses caused by data anomalies. However, in related data lineage technologies, manual detection of abnormal data in data lineage is required, resulting in the inability to quickly detect abnormal data flows.

[0003] In view of the above problems, no effective solutions have been proposed yet. Summary of the Invention

[0004] Embodiments of this application provide a data display method, an electronic device, and a storage medium to at least solve the technical problem in related technologies of being unable to quickly detect abnormal data flows.

[0005] According to one aspect of the embodiments of this application, a data display method is provided, including: obtaining data to be displayed, where the data to be displayed flows among multiple entities; determining whether there is a target flow path among the multiple entities based on the flow direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target flow path are the same; and displaying the target flow path when there is a target flow path among the multiple entities.

[0006] According to another aspect of the embodiments of this application, a data display method is further provided, including: in response to an input instruction acting on an operation interface, displaying the data to be displayed on the operation interface, where the data to be displayed flows among multiple entities; and in response to a display instruction acting on the operation interface, displaying the target flow path existing among the multiple entities on the operation interface, where the target flow path is determined based on the flow direction of the data to be displayed among the multiple entities, and the first entity and the last entity included in the target flow path are the same.

[0007] According to another aspect of the embodiments of the present application, there is also provided a data display method, including: obtaining data to be displayed by calling a first interface, where the first interface includes a first parameter, and the parameter value of the first parameter includes the data to be displayed, and the data to be displayed circulates among multiple entities; determining whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target circulation path are the same; and outputting the target circulation path by calling a second interface when there is a target circulation path among the multiple entities, where the second interface includes a second parameter, and the parameter value of the second parameter includes the target circulation path.

[0008] According to another aspect of the embodiments of the present application, there is also provided a data display device, including: an obtaining module, configured to obtain data to be displayed, where the data to be displayed circulates among multiple entities; a determining module, configured to determine whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target circulation path are the same; and a display module, configured to display the target circulation path when there is a target circulation path among the multiple entities.

[0009] According to another aspect of the embodiments of the present application, there is also provided a data display device, including: a first display module, configured to display data to be displayed on an operation interface in response to an input instruction acting on the operation interface, where the data to be displayed circulates among multiple entities; a second display module, configured to display a target circulation path existing among the multiple entities on the operation interface in response to a display instruction acting on the operation interface, where the target circulation path is determined based on the circulation direction of the data to be displayed among the multiple entities, and the first entity and the last entity included in the target circulation path are the same.

[0010] According to another aspect of the embodiments of the present application, there is also provided a data display device, including: an obtaining module, configured to obtain data to be displayed by calling a first interface, where the first interface includes a first parameter, and the parameter value of the first parameter includes the data to be displayed, and the data to be displayed circulates among multiple entities; a determining module, configured to determine whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target circulation path are the same; and an output module, configured to output the target circulation path by calling a second interface when there is a target circulation path among the multiple entities, where the second interface includes a second parameter, and the parameter value of the second parameter includes the target circulation path.

[0011] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including: a memory storing an executable program; a processor for running the program, wherein when the program runs, it executes the method of any one of the above.

[0012] According to another aspect of the embodiments of the present application, there is also provided a computer-readable storage medium, which includes a stored executable program, wherein when the executable program runs, it controls the device where the storage medium is located to execute the method of any one of the above.

[0013] In the embodiments of the present application, a method is adopted, which includes obtaining data to be displayed, where the data to be displayed circulates among multiple entities; determining whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target circulation path are the same; and when there is a target circulation path among the multiple entities, displaying the target circulation path. It is easy to notice that the target circulation path can be automatically detected through the circulation direction of the data to be displayed. While detecting the existence of the target circulation path, the target circulation path can also be displayed through the user terminal, achieving the purpose of quickly determining the flow direction of abnormal data, thereby realizing the technical effect of being able to quickly determine the flow direction of abnormal data, and further solving the technical problem in the related art that the abnormal flow direction of data cannot be quickly detected.

[0014] It is easy to notice that the above general description and the following detailed description are only for exemplifying and explaining the present application, and do not constitute a limitation to the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The schematic embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0016] Figure 1 is a hardware structure block diagram of a computer terminal (or mobile device) for implementing the data display method according to the embodiments of the present application;

[0017] Figure 2 is a structure block diagram of a computing environment according to the embodiments of the present application;

[0018] Figure 3 is a structure block diagram of a service mesh according to the embodiments of the present application;

[0019] Figure 4 is a flowchart of a data display method according to Embodiment 1 of the present application;

[0020] Figure 5Schematic diagram of an optional path directed graph according to Embodiment 1 of the present application;

[0021] Figure 6 Schematic diagram of an optional plurality of transfer paths according to Embodiment 1 of the present application;

[0022] Figure 7 Schematic diagram of an optional display of a target transfer path according to Embodiment 1 of the present application;

[0023] Figure 8 Schematic diagram of an optional graph pattern according to Embodiment 1 of the present application;

[0024] Figure 9 Schematic diagram of an optional tree pattern according to Embodiment 1 of the present application;

[0025] Figure 10 Processing interaction diagram of an optional target transfer path according to Embodiment 1 of the present application;

[0026] Figure 11 Flowchart of a data display method according to Embodiment 2 of the present application;

[0027] Figure 12 Schematic diagram of an optional operation interface according to Embodiment 2 of the present application;

[0028] Figure 13 Flowchart of a data display method according to Embodiment 3 of the present application;

[0029] Figure 14 Schematic diagram of a data display device according to Embodiment 4 of the present application;

[0030] Figure 15 Schematic diagram of a data display device according to Embodiment 5 of the present application;

[0031] Figure 16 Schematic diagram of a data display device according to Embodiment 6 of the present application;

[0032] Figure 17 Block diagram of a computer terminal according to an embodiment of the present application. Detailed implementation

[0033] In order to enable those skilled in the art to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0034] It should be noted that the terms "first", "second", etc. in the description, claims and the above-mentioned drawings of this application are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0035] First, some nouns or terms that appear in the process of describing the embodiments of this application are applicable to the following explanations:

[0036] Data Lineage: Also known as data pedigree, it is a way to visually represent the flow of data among different entities.

[0037] Cycle: It refers to a non-empty path in a graph where only the first and the last vertices are repeated.

[0038] Data lineage forming a cycle: The "cycle" in the data lineage graph indicates that the data flow forms a loop, which can be simply represented as the data flow flowing out from A and then flowing back to A. Cycles are not common in data lineage and only occur in some special scenarios, such as:

[0039] a. Self-forming a cycle: For example, A->A, the data of node A comes from the integration of the data of node A in the previous cycle + the data in the current cycle;

[0040] b. Multiple parties forming a cycle: For example, A->B->A, which may be a configuration error caused by negligence, and the data of node A flows back to node A again.

[0041] Depth-First-Search (DFS): It is an algorithm used to traverse or search a tree or a graph. This algorithm will search the branches of the tree as deeply as possible. When all the edges of node v have been explored, the search will backtrack to the starting node of the edge where node v was discovered. This process continues until all the nodes reachable from the source node have been discovered.

[0042] Embodiment 1

[0043] According to an embodiment of the present application, a data display method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0044] The method embodiment provided by the first embodiment of the present application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Figure 1 It is a hardware structure block diagram of a computer terminal (or mobile device) for implementing the data display method according to an embodiment of the present application. As Figure 1 shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b,..., 102n in the figure) (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. In addition, it may further include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply, and / or a camera. Those of ordinary skill in the art can understand that Figure 1 the structure shown is only schematic and does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 may further include more or fewer components than Figure 1 shown, or have a different configuration from Figure 1 shown.

[0045] It should be noted that the above one or more processors 102 and / or other data processing circuits are generally referred to as "data processing circuits" in this article. The data processing circuit can be embodied as software, hardware, firmware, or any combination thereof, in whole or in part. In addition, the data processing circuit can be a single independent processing module, or be incorporated in whole or in part into any one of the other elements in the computer terminal 10 (or mobile device). As involved in the embodiments of the present application, the data processing circuit is a processor control (such as the selection of a variable resistor terminal path connected to an interface).

[0046] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the data display method in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the above data display method. The memory 104 may include a high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely disposed relative to the processor 102, and these remote memories can be connected to the computer terminal 10 through a network. Examples of the above network include but are not limited to the Internet, enterprise intranet, local area network, mobile communication network, and combinations thereof.

[0047] The transmission device 106 is used to receive or send data via a network. Specific examples of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one instance, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0048] The display can be, for example, a touch-screen liquid crystal display (Liquid Crystal Display, LCD), and the liquid crystal display enables a user to interact with the user interface of the computer terminal 10 (or mobile device).

[0049] Figure 1 The shown hardware structure block diagram can be used not only as an exemplary block diagram of the above computer terminal 10 (or mobile device), but also as an exemplary block diagram of the above server. In an alternative embodiment, Figure 2 is shown in a block diagram using the above Figure 1 shown computer terminal 10 (or mobile device) as a computing node in the computing environment 201 in one embodiment. Figure 2 is a structural block diagram of a computing environment according to an embodiment of the present application, such as Figure 2As shown, the computing environment 201 includes multiple computing nodes (such as servers, shown as 210-1, 210-2, … in the figure) running on a distributed network. Each computing node contains local processing and memory resources, and end users 202 can remotely run applications or store data in the computing environment 201. The applications can be provided as multiple services 220-1, 220-2, 220-3, and 220-4 in the computing environment 201, representing services "A", "D", "E", and "H" respectively.

[0050] End users 202 can provide and access services through a web browser or other software applications on the client side. In some embodiments, the provision and / or requests of end users 202 can be provided to the ingress gateway 230. The ingress gateway 230 can include a corresponding proxy to handle the provision and / or requests for services (one or more services provided in the computing environment 201).

[0051] Services are provided or deployed according to various virtualization technologies supported by the computing environment 201. In some embodiments, services can be provided based on virtual machine (VM)-based virtualization, container-based virtualization, and / or similar means. VM-based virtualization can simulate a real computer by initializing a virtual machine and execute programs and applications without directly accessing any actual hardware resources. While virtualizing the machine with a virtual machine, according to container-based virtualization, containers can be launched to virtualize the entire operating system (OS) so that multiple workloads can run on a single operating system instance.

[0052] In one embodiment of container-based virtualization, several containers of a service can be assembled into a Pod (e.g., Kubernetes Pod). For example, as Figure 2 shown, service 220-2 can be equipped with one or more Pods 240-1, 240-2, …, 240-N (collectively referred to as Pods). A Pod can include a proxy 245 and one or more containers 242-1, 242-2, …, 242-M (collectively referred to as containers). One or more containers in the Pod handle requests related to one or more corresponding functions of the service, and the proxy 245 generally controls network functions related to the service, such as routing, load balancing, etc. Other services can also be equipped with similar Pods.

[0053] During operation, executing user requests from end users 202 may require invoking one or more services in the computing environment 201, and executing one or more functions of a service may require invoking one or more functions of another service. As Figure 2As shown, service "A" 220-1 receives a user request from end user 202 at the ingress gateway 230. Service "A" 220-1 may invoke service "D" 220-2, and service "D" 220-2 may request service "E" 220-3 to perform one or more functions.

[0054] The computing environment described above may be a cloud computing environment where the allocation of resources is managed by a cloud service provider, allowing the development of functions without considering the implementation, tuning, or scaling of servers. This computing environment allows developers to execute code in response to events without building or maintaining complex infrastructure. Services can be split into sets of functions that can scale automatically and independently, rather than scaling a single hardware device to handle potential loads.

[0055] In another alternative embodiment, Figure 3 is shown in block diagram form an embodiment of a service mesh using the Figure 1 computer terminal 10 (or mobile device) shown above. Figure 3 is a structural block diagram of a service mesh according to an embodiment of the present application, as Figure 3 shown. The service mesh 300 is mainly used to facilitate secure and reliable communication between multiple microservices. A microservice refers to decomposing an application into multiple smaller services or instances and running them on different clusters / machines.

[0056] As Figure 3 shown, the microservices may include application service instance A and application service instance B. Application service instance A and application service instance B form the functional application layer of the service mesh 300. In one implementation, application service instance A runs in the form of a container / process 308 on a machine / workload container group 314 (Pod), and application service instance B runs in the form of a container / process 310 on a machine / workload container group 316 (Pod).

[0057] In one implementation, application service instance A may be a product query service, and application service instance B may be a product order service.

[0058] As Figure 3As shown, application service instance A and mesh proxy (sidecar) 303 coexist in machine workload container group 314, and application service instance B and mesh proxy 305 coexist in machine workload container 316. Mesh proxy 303 and mesh proxy 305 form the data plane layer of service mesh 300. Among them, mesh proxy 303 and mesh proxy 305 run in the form of container / process 304 and container / process 306 respectively, and can receive requests 312 for commodity query services. Bidirectional communication is possible between mesh proxy 303 and application service instance A, and between mesh proxy 305 and application service instance B. In addition, bidirectional communication is also possible between mesh proxy 303 and mesh proxy 305.

[0059] In one implementation, the traffic of application service instance A is routed to the appropriate destination through mesh proxy 303, and the network traffic of application service instance B is routed to the appropriate destination through mesh proxy 305. It should be noted that the network traffic mentioned here includes but is not limited to forms such as Hyper Text Transfer Protocol (abbreviated as HTTP), Representational State Transfer (abbreviated as REST), high-performance, general open-source framework (google Remote Procedure Call, gRPC), open-source in-memory data structure storage system (Redis), etc.

[0060] In one implementation, the function of the extended data plane layer can be realized by writing custom filters for the Envoy in service mesh 300. The service mesh proxy configuration can be used to correctly proxy service traffic in the service mesh, realizing service intercommunication and service governance. Mesh proxy 303 and mesh proxy 305 can be configured to perform at least one of the following functions: service discovery, health checking, routing, load balancing, authentication and authorization, and observability.

[0061] As Figure 3 shown, the service mesh 300 also includes a control plane layer. Among them, the control plane layer can be a group of services running in a dedicated namespace, and these services are hosted by the managed control plane component 301 in machine / workload container group (machine / Pod) 302. As Figure 3As shown in the figure, the managed control plane component 301 communicates bidirectionally with the grid agents 303 and 305. The managed control plane component 301 is configured to perform some control and management functions. For example, the managed control plane component 301 receives the telemetry data transmitted by the grid agents 303 and 305, and can further aggregate this telemetry data. For these services, the managed control plane component 301 can also provide user-facing application programming interfaces (APIs) to more easily manipulate network behavior and provide configuration data to the grid agents 303 and 305, etc.

[0062] Under the above operating environment, the present application provides a data display method as Figure 4 shown. Figure 4 It is a flowchart of a data display method according to Embodiment 1 of the present application. As Figure 4 shown, it includes a user terminal 20 and a server terminal 10. Among them, the user terminal is connected to the server terminal through a network. On the server side, it can execute: obtain the data to be displayed, determine whether there is a target transfer path between multiple entities based on the transfer direction of the data to be displayed between the multiple entities, and after determining that there is a target transfer path, send the target transfer path to the user terminal. After receiving the target transfer path, the user terminal displays the target transfer path through the user interface. As Figure 4 shown, the method includes the following steps:

[0063] Step S402, obtain the data to be displayed, where the data to be displayed is transferred among multiple entities;

[0064] The above data to be displayed can be data that requires multiple entities to process sequentially, which can be one type or multiple types. The specific data type is not limited in this embodiment, and the user can set it according to actual needs. In this embodiment, one type of data to be displayed is used as an example for illustration. Among them, the data to be displayed can be transferred between different entities (for example, it can be different devices or components, but not limited to this). For example, the data to be displayed can be transferred among multiple sub-servers in a distributed server, and can also be transferred among the R & D side, the test side, the packaging side, and the client side, but not limited to this.

[0065] In an optional embodiment, in the case where multiple types of data are transferred among multiple entities, when the user wants to detect the abnormal flow of a certain type of data, first, the corresponding data to be displayed of the user terminal can be obtained through the server, where the data to be displayed is transferred among multiple entities.

[0066] Step S404: Determine whether there is a target transfer path among multiple entities based on the transfer direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target transfer path are the same.

[0067] The above transfer direction can reflect the movement path and direction of the data to be displayed among multiple entities. For example, when the data to be displayed is transferred from entity A to entity B, the corresponding transfer direction can indicate that the movement path and direction of the data to be displayed are from entity A to entity B. The above target transfer path can reflect the transfer direction of the data to be displayed among multiple entities, that is, the target transfer path can reflect the movement path and direction of the data to be displayed flowing from the current entity to the last entity. It should be noted that the target transfer path can be one or multiple. In the target transfer path, the first entity and the last entity are the same entity, that is, the target transfer path is a circular path.

[0068] In an alternative embodiment, when the data to be displayed is obtained, first, the transfer direction of the data to be displayed among multiple entities can be determined. For example, first, the transfer direction of the data to be displayed among multiple sub-servers of a distributed server can be determined. Second, based on the transfer direction, it can be determined whether there is a target transfer path where the first entity and the last entity are the same. For example, first, a path directed graph corresponding to the data to be displayed can be generated based on the transfer path of the data to be displayed, where Figure 5 is a schematic diagram of an alternative path directed graph according to Embodiment 1 of the present application, as Figure 5 shown. The path directed graph includes nodes 1-5 and multiple edges. The nodes 1-5 can represent multiple entities through which the data to be displayed flows (for example, they can be sub-servers numbered 1-5 in a distributed server, but are not limited thereto), and the edges can represent the direction of the data to be displayed flowing through the entities. Second, the path directed graph can be traversed to obtain multiple nodes 1-5, and then the multiple nodes can be judged to determine whether there are duplicate nodes. As Figure 5 can be seen, in the path directed graph, after the data to be displayed flows to node 4, it then flows to nodes 1 and 5 respectively. Therefore, it can be determined that the transfer path of the data to be displayed flowing back from node 1 to node 1 has duplicate nodes. At this time, it can be shown that the data to be displayed has flowed through the same entity, so it can be determined that there is a target transfer path among multiple entities.

[0069] For another example, after obtaining the transfer direction of the data to be displayed among multiple entities, first, multiple transfer paths of the data to be displayed flowing through multiple entities can be generated respectively. Second, the multiple transfer paths can be judged in sequence to determine whether the first entity and the last entity in each of the multiple transfer paths are the same. Figure 6It is a schematic diagram of an optional multiple flow paths according to Embodiment 1 of the present application. As Figure 6 shown, after the data to be displayed flows out of Node 1, there are three flow paths respectively. Among them, the flow order of Flow Path 1 is that the data to be displayed flows from Node 1 to Node 2, then from Node 2 to Node 3, then from Node 3 to Node 4, and finally from Node 4 to Node 5; the flow order of Flow Path 2 is that the data to be displayed flows from Node 1 to Node 3, then from Node 3 to Node 4, and finally from Node 4 to Node 1; the flow order of Flow Path 3 is that the data to be displayed flows from Node 1 to Node 2, then from Node 2 to Node 4, then from Node 4 to Node 5, and finally from Node 5 to Node 6. From Figure 6 it can be seen that in Flow Path 2, the first node is the same as the last node, which indicates that the last entity is the same as the first entity, that is, it can be explained that the data to be displayed has flowed through the same entity. Therefore, it can be determined that this flow path is the target flow path. If in multiple flow paths, the first entity is not the same as the last entity, as shown in Flow Path 1 and Flow Path 3, it indicates that the data to be displayed has not flowed through the same entity. Therefore, it can be determined that there is no target flow path among the multiple flow paths.

[0070] It should be noted that the schematic diagram of the above path directed graph and the schematic diagram of multiple flow paths are only examples in this embodiment. This embodiment may also include other various path directed graphs and various multiple flow paths.

[0071] Step S406, when there is a target flow path among multiple entities, display the target flow path.

[0072] In an optional embodiment, when it is determined that there is a target flow path among multiple entities, as Figure 4 shown, the server can send the target flow path to the user terminal. After receiving the target flow path, the user terminal can render and display the target flow path. For example, the user terminal can display the target flow path through a display screen. Among them, the user terminal can only display the target flow path on the display screen, or can also display multiple flow paths of various data on the screen, and then highlight the target flow path of the data to be displayed. For example, the lines and colors of the target flow path can be distinguished from multiple flow paths and then displayed, or multiple regions can be divided on the display screen, and the target flow path can be separately displayed in one of the sub-regions, but not limited to this.

[0073] Optionally, when the client wants to detect the abnormal flow of multiple data among multiple entities, it can first obtain the data to be displayed through the server. Secondly, the server can determine the transfer direction of the data to be displayed among multiple entities. Then, the server can determine whether there is a target transfer path among the multiple entities based on the transfer direction. When it is determined that there is a target transfer path among the multiple entities, the server can send the data to be displayed to the client. After receiving the target transfer path, the client can display the target transfer path to the user on the display screen. Therefore, the user can quickly and intuitively detect the abnormal flow of the data to be displayed. Figure 7 is a schematic diagram of the display of an optional target transfer path according to Embodiment 1 of the present application, as Figure 7 shown. This interface includes a transfer display area and a display area for the target transfer path. It can be Figure 7 seen that the transfer display area contains multiple nodes 1-10 and Structured Query Language (SQL) tasks. Among them, the SQL task flowing out of node 9 returns to node 9 again. Therefore, it can be determined that node 9 includes the target transfer path. At this time, the target transfer path of node 9 can be separately displayed in the display area of the target transfer path so that the user can quickly and intuitively see the target transfer path.

[0074] In the embodiments of the present application, the method includes: obtaining the data to be displayed, where the data to be displayed is transferred among multiple entities; determining whether there is a target transfer path among the multiple entities based on the transfer direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target transfer path are repeated; and displaying the target transfer path when there is a target transfer path among the multiple entities. It is easy to notice that the target transfer path can be automatically detected through the transfer direction of the data to be displayed. While detecting the existence of the target transfer path, the target transfer path can also be displayed through the client, achieving the purpose of quickly determining the flow direction of abnormal data, thus realizing the technical effect of being able to quickly determine the flow direction of abnormal data, and further solving the technical problem in the related art that the abnormal flow of data cannot be quickly detected.

[0075] In the above embodiments of the present application, determining whether there is a target transfer path among multiple entities based on the transfer direction of the data to be displayed among the multiple entities includes: generating a target directed graph based on the transfer direction of the data to be displayed among the multiple entities, where the target directed graph includes multiple nodes and edges connected between two nodes, different nodes are used to represent different entities, and the direction of the edge is used to represent the transfer direction of the data to be displayed between the entities corresponding to the two nodes; and traversing the multiple nodes in the target directed graph to determine whether there is a target transfer path in the target directed graph.

[0076] In an alternative embodiment, after obtaining the flow direction of the data to be displayed among multiple entities, first, the flow order of the data to be displayed among multiple entities can be determined based on the flow direction. Second, multiple nodes and multiple edges between the multiple nodes can be generated based on the flow order. Then, a target directed graph can be generated based on the multiple nodes and the multiple edges, where the nodes in the target directed graph are the corresponding entities, and the edges in the target directed graph can reflect the flow direction of the entities between two nodes. Finally, the multiple nodes in the target directed graph can be traversed to determine whether there is a target flow path in the target directed graph where the first node and the last node are repeated. For example, after traversing the target directed graph, if there is a flow path where the first node and the last node are repeated, it can be determined that this flow path is the target flow path. If there is no flow path where the first node and the last node are repeated, it can be determined that there is no target flow path in the target directed graph.

[0077] It should be noted that in this embodiment, the target directed graph can be traversed by the Depth First Search (DFS) algorithm, but it is not limited to this. Any algorithm in the prior art that can traverse the target directed graph can also be implemented. Among them, the DFS algorithm has low time and space complexity and can efficiently detect and output all loops in the graph to achieve loop detection and prompting.

[0078] In the above embodiment of the present application, generating a target directed graph based on the flow direction of the data to be displayed among multiple entities includes: determining the flow order among multiple entities based on the flow direction of the data to be displayed among multiple entities; generating multiple nodes based on the flow order among multiple entities; and generating an edge connecting two nodes based on the flow direction of the data to be displayed among multiple entities to obtain the target directed graph.

[0079] In an alternative embodiment, after obtaining the flow direction of the data to be displayed, first, the flow order of the data to be displayed among multiple entities can be determined. For example, it can be determined that the data to be displayed first flows to entity A, then from entity A to entity B, then from entity B to entity C, and finally from entity C back to entity A. After obtaining the flow order, multiple nodes can be generated based on the multiple flow orders among multiple entities, where the multiple nodes correspond to the multiple entities through which the data to be displayed flows, and the flow order of the data to be displayed changes at different nodes. Then, an edge connecting two nodes can be generated based on the flow direction of the data to be displayed among multiple entities to obtain the target directed graph, where the edge can reflect the flow direction of the data to be displayed between two nodes.

[0080] In the above embodiments of the present application, when generating a target directed graph, based on the transfer order between multiple entities, multiple nodes are generated, including: obtaining the display mode of the target directed graph, where the display mode is used to characterize the mode of displaying the target directed graph; when the display mode is the graph mode, based on the transfer order between multiple entities, determine whether the target entity of the node to be generated appears repeatedly, and when the target entity does not appear repeatedly, generate the node corresponding to the target entity; when the display mode is the tree mode, based on the dependency relationship between multiple entities, generate multiple nodes in sequence.

[0081] The above display modes may include, but are not limited to, the graph mode and the tree mode. Among them, the graph mode can accurately display the data flow, without duplicate nodes, and is convenient for viewing the relationship between nodes from a global perspective. Figure 8 It is a schematic diagram of an optional graph mode according to Embodiment 1 of the present application. As Figure 8 shown, the display interface includes an option selection area, a transfer display area, and a target transfer path display area. The transfer display area contains nodes 1-10. It can be Figure 8 seen that after a certain SQL task flows out from nodes 1 and 2, it will flow to node 8. After a certain SQL task flows out from node 3, it will flow to node 9. After a certain SQL task flows out from nodes 4-7, it will flow to node 10. Among them, node 8 will flow the SQL task back to itself. Therefore, node 8 contains the target transfer path. It can be Figure 8 seen that when the options "unique node display" and "enable loop detection" are selected (i.e., Figure 8 the black circles shown indicate being selected), the transfer display area can display the display mode of the target directed graph as the graph mode, and can display the target transfer path in the target transfer path display area.

[0082] The tree mode is convenient for users to view the upstream and downstream of a single node, and the node hierarchy display is clearer. Even with a large number of nodes, it will not affect readability. Figure 9 It is a schematic diagram of an optional tree mode according to Embodiment 1 of the present application. As Figure 9 shown, the display interface includes an option selection area and a transfer display area. The transfer display area contains nodes 1-10. It can be Figure 9 seen that a certain SQL task flows from nodes 1 and 2 to node 2, and then flows to node 3. A certain SQL task flows from node 3 to node 8, and then flows to node 3. A certain SQL task flows from nodes 4-7 to node 9, and then flows to node 3. That is, the nodes are generated in sequence based on the flow direction and dependency relationship of the data to be displayed. It can be Figure 9 seen that when the option "unique node display" is not selected (i.e., Figure 9The white circles shown indicate not selected), and the flow display area can display the display mode of the target directed graph as a tree mode.

[0083] The above-mentioned dependencies may include, but are not limited to: Data dependency: The data or information of one node is derived from another node. Time dependency: The occurrence of one node depends on the completion or status of another node. Functional dependency: The function of one node requires the support or service provided by another node. Hierarchical dependency: The position or status of one node depends on the position or status of another node.

[0084] In an alternative embodiment, after obtaining the target directed graph, first, the display mode of the target directed graph can be obtained. When the display mode of the target directed graph is the graph mode, first, based on the flow order among multiple entities, it can be determined whether the target entity appears repeatedly. When it is determined that the target entity does not appear repeatedly, nodes corresponding to the target entity can be generated. When the display mode of the target directed graph is the tree mode, multiple nodes can be generated in sequence based on the dependency relationships among multiple entities. For example, when the display mode of the target directed graph is the tree mode, when there is a dependency relationship (such as a data dependency relationship) between the current entity and the next entity, nodes of the current entity and the next entity can be generated in sequence.

[0085] In the above embodiments of the present application, when the display mode is the graph mode, the method further includes: determining the target type of the edge, where the target type is used to characterize whether two nodes are repeated and whether there are multiple edges connected between the two nodes; determining the distance between the edge and the two nodes based on the target type; generating an edge connected between the two nodes based on the distance.

[0086] The above-mentioned target types of the edge may include, but are not limited to: ordinary edge, self-loop edge, multiplexing edge. Among them, when there is no repetition between two nodes and there are no multiple edges connected, the edge between the two nodes is an ordinary edge; when there is no repetition between two nodes but there are multiple edges connected, the edge between the two nodes is a multiplexing edge; when there is a repetition between two nodes, the edge between the two nodes is a self-loop edge. The above-mentioned distances may include, but are not limited to: a quarter of the distance from the current node, a half of the distance from the current node, and three-quarters of the distance from the current node. Among them, the distance of the ordinary edge from the current node is three-quarters of the distance, the distance of the multiplexing edge from the current node is a half of the distance, and the distance of the self-loop edge from the current node is a quarter of the distance.

[0087] In an alternative embodiment, when the display mode of the target directed graph is the graph mode, the target type of the edge can first be determined. After determining the target type of the edge, the distance between the edge and the two nodes can be determined based on a preset correspondence relationship. Finally, an edge connecting the two nodes can be generated based on the distance. The preset correspondence relationship can reflect the correspondence between the type of the edge and the distance between the two nodes.

[0088] It should be noted that if the upstream of the current node contains both ordinary edges and reused edges, the position of the ordinary edge is also changed to the 1 / 2 position, so as to maintain visual unity; for the node rendering order, from top to bottom, nodes with reused edges are preferentially rendered, which can avoid line crossing and overlapping to a certain extent.

[0089] In the above embodiments of the present application, after generating the target directed graph based on the flow direction of the data to be displayed among multiple entities, the method further includes: determining the states of the multiple nodes included in the target directed graph and the state of the edge; determining the display modes of the multiple nodes based on the states of the multiple nodes, and determining the display mode of the edge based on the state of the edge; displaying the multiple nodes according to the display modes of the multiple nodes, and displaying the edge according to the display mode of the edge.

[0090] The states of the above nodes may include but are not limited to: default state, active state, selected state, and highlighted state. The states of the above edges are default state, active state, selected state, highlighted state, and flowing state. The display modes of the multiple nodes may include but are not limited to: different states will be displayed and distinguished by different styles. For example, the "selected state" will thicken the outer border and change the border color, etc. for distinction.

[0091] In an alternative embodiment, after generating the target directed graph based on the flow direction of the data to be displayed among multiple entities, first, the states of the nodes and edges included in the target directed graph can be determined. Secondly, the display mode of the nodes can be determined based on the states of the nodes, and the display mode of the edge can be determined based on the state of the edge. Finally, the nodes can be displayed according to the node display mode, and the edges can be displayed according to the edge display mode. For example, when it is determined that the state of the node is the active state and the state of the edge is the active state, it can be determined that the display mode of the node is to change the color to be highlighted, and the display mode of the edge is to change the color to be highlighted. Finally, the color of the node can be changed to be highlighted based on the display mode of the node, and the color of the edge can also be changed to be highlighted based on the display mode of the edge.

[0092] In the above embodiments of the present application, the method further includes: when detecting a first operation performed on a target node, obtaining the initial state of the target node; determining the target state of the target node based on the first operation and the initial state; adjusting the state of the edge connected to the target node to the highlighted state.

[0093] The initial states of the above-mentioned target nodes may include, but are not limited to: default state, active state, selected state, and highlighted state. The above-mentioned first operation may include, but is not limited to: sliding operation, selection operation, and associated response operation on the target node. Table 1 is a schematic table of the target state of an optional target node and the state of the edges connected thereto according to Embodiment 1 of the present application, where the priority 1 has the highest priority and the priority 4 has the lowest priority. As shown in Table 1, the default state is the default generated state of the node without an interaction method, the interaction methods of the active state and the selected state are active, and the interaction method of the highlighted state is passive.

[0094] Table 1

[0095]

[0096] In an optional embodiment, the initial state and the target state of the target node include: default state, active state, selected state, and highlighted state. After detecting that the user terminal performs a first operation on the initial state of the target node, for example, when the mouse hovers over or selects the target node, or after not performing the first operation on the target node, the target state of the target node can be determined based on the first operation. For example, as can be seen from Table 1, when the mouse does not select or hover over the target node, the target state of the target node does not change; when the mouse hovers over the target node, the target state of the target node becomes the active state; when the target node is selected, the target state of the target node becomes the selected state; when the target node is associated with a response, the target state of the target node becomes the highlighted state.

[0097] As can be seen from Table 1, the priority of the target node after being selected is the highest. If the target node is selected, the previous state of the target node can be cleared, the state of the target node can be changed to the selected state, and the states of the upstream and downstream edges connected to the target node can be set to the highlighted state. The priority of the target node being hovered over by the mouse is the second highest. If the initial state of the target node is the default state or the highlighted state and the target node is hovered over by the mouse, the target state of the target node can be changed to the active state, and the states of the upstream and downstream edges connected to the target node can be set to the highlighted state; if the initial state of the target node is the selected state and the target node is hovered over by the mouse, the initial state of the target node remains unchanged, and only the states of the upstream and downstream edges connected to the target node are set to the highlighted state. The priority of the target node being associated with a response is the third highest. If the target node is associated with a response, the target state of the target node can be changed to the highlighted state, and the states of the upstream and downstream edges connected to the target node can be set to the highlighted state; if the target node is selected, the state of the target node can be changed to the selected state, and the states of the upstream and downstream edges connected to the target node can be set to the highlighted state. The priority of the default state of the target node is the lowest. At this time, the target node is not selected or hovered over by the mouse, so the state of the target node may not change.

[0098] In the above embodiments of the present application, the method further includes: when detecting a second operation performed on an edge, obtaining the initial state of the edge; determining the target state of the edge based on the second operation and the initial state; and adjusting the states of the two nodes connected to the edge to a highlighted state.

[0099] The above initial state of the edge may include, but is not limited to: default state, active state, selected state, and highlighted state. The above second operation may include, but is not limited to: a sliding operation on the edge, a selection operation, and an association response operation. Table 2 is a schematic table of an optional target state of an edge and the states of its connected nodes according to Embodiment 1 of the present application, where the priority 1 has the highest priority and the priority 4 has the lowest priority. As shown in Table 2, the default state is the default generated state of the edge without an interaction method, the interaction methods of the active state and the selected state are active, and the interaction method of the highlighted state is passive.

[0100] In an optional embodiment, the initial state and the target state of the edge include: default state, active state, selected state, and highlighted state. After detecting that the user terminal performs a second operation on the initial state of the edge, for example, when the mouse hovers over or selects the edge, or when no second operation is performed on the edge, the target state of the edge can be determined based on the second operation. For example, as can be seen from Table 2, when the mouse does not select or hover over the edge, the target state of the edge does not change; when the mouse hovers over the edge, the target state of the edge becomes the active state; when the edge is selected, the target state of the edge becomes the selected state; when the edge is associated with a response, the target state of the edge becomes the highlighted state.

[0101] As can be seen from Table 2, the priority is the highest after the edge is selected. If the edge is selected, the previous state of the edge can be cleared, the state of the edge can be changed to the selected state, and the states of the two nodes connected to the edge can be set to the highlighted state. The priority of the edge being hovered over by the mouse is the second highest. If the initial state of the edge is the default state or the highlighted state and the edge is hovered over by the mouse, the target state of the edge can be changed to the active state, and the states of the two nodes connected to the edge can be set to the highlighted state; if the initial state of the edge is the selected state and the edge is hovered over by the mouse, the initial state of the edge remains unchanged, and only the states of the two nodes connected to the edge are set to the highlighted state. The priority of the edge being associated with a response is the third highest. If the edge is associated with a response, the target state of the edge can be changed to the highlighted state, and the states of the edges and nodes on the entire loop connected to the edge can be set to the highlighted state; if the edge is hovered over by the mouse, the target state of the edge can be changed to the active state and the states of the two nodes connected to the edge can be set to the highlighted state; if the edge is selected, the state of the edge can be changed to the selected state, and the states of the two nodes connected to the edge can be set to the highlighted state. The priority of the default state of the edge is the lowest. At this time, the edge is not selected or hovered over by the mouse, so the state of the edge may not change.

[0102] Table 2

[0103]

[0104] In the above embodiments of the present application, the method further includes: during the process of displaying the target transfer path, determining that the states of the nodes and edges included in the target transfer path are highlighted states; when the target transfer path is in a highlighted state, determining that the states of the edges included in the target transfer path are flowing states.

[0105] In an alternative embodiment, when the target transfer path is obtained, the user terminal can display the target transfer path. During the display process, the states of the edges and nodes in the target transfer path can be set to highlighted states, so that the user can quickly and intuitively see the target transfer path. In addition, when the target transfer path is in a highlighted state, the states of the edges in the target transfer path can be set to flowing states. For example, the edges in the target transfer path can be made into flowing animation effects to highlight the target transfer path, enabling the user to intuitively see the abnormal flow direction.

[0106] In the above embodiments of the present application, the method further includes: when a search instruction for searching a target node is detected, determining that the state of the target node is a highlighted state.

[0107] In an alternative embodiment, after the user terminal obtains the target transfer path, it can also search for the target node in the target transfer path. For example, the user can enter the target node in the search box in the display area to perform a search. Based on the search instruction, the display area can search for the target node and change the state of the searched target node to a highlighted state.

[0108] In the above embodiments of the present application, obtaining the data to be displayed includes: obtaining the original data; performing data structure conversion on the original data to obtain the converted data; aggregating the data belonging to the same entity in the converted data to obtain the aggregated data; and performing format conversion on the aggregated data to obtain the data to be displayed.

[0109] In an alternative embodiment, first, the original data can be obtained from a database. Secondly, the data structure of the original data can be converted. The data structure of the original data is converted from the back-end database data structure to the structure required for front-end rendering, and necessary information (for example, it may include but is not limited to the field names, data types, hierarchical relationships, etc. of the original data) is supplemented to obtain the converted data. Then, the converted data can be sorted again. To determine the order before and after of the nodes of the data to be displayed, the data belonging to the same entity can be aggregated based on the re-sorting to obtain the aggregated data. Finally, the format of the aggregated data can be converted, and the data with a nested structure is converted into a "node-edge" structure that can be rendered, and thus the data to be displayed can be obtained.

[0110] It should be noted that the format conversion of the aggregated data can be achieved by using an algorithm. The specific algorithm is not limited in this embodiment, and the user can set it according to actual needs.

[0111] This application provides a display and detection solution for a circular data lineage (hereinafter referred to as "ring" for short) in data lineage. In the data map - data lineage function, it can clearly display the flow of data between entities and quickly detect abnormal data flows. Since in data lineage, a "ring" only occurs in some special scenarios or when the user data development task configuration is incorrect, once a circular data lineage appears, attention needs to be paid to correct the data dependencies to avoid losses caused by data anomalies.

[0112] Figure 10 It is a processing interaction diagram of an alternative target transfer path according to Embodiment 1 of this application, as Figure 10As shown in the figure, the interaction process mainly includes: data request, data processing, rendering, detection, and prompting. First, upstream and downstream data can be obtained from the database. Among them, the upstream and downstream data needs to conform to the definition of a specific data structure, and the upstream and downstream data specifically refers to the upstream and downstream node data of the current node. Secondly, the upstream and downstream data can be basically processed and format conversion can be performed to obtain the data to be displayed. Secondly, duplicate node judgment can be performed on the data to be displayed to determine whether there are duplicate nodes in the flow path of the data to be displayed, that is, to determine whether the rendering node already exists in the graph. If it exists, it will not be rendered again, but the existing node will be reused and the edge attributes will be set. Then, the rendering of the nodes and edges in the link will be performed, and the rendered nodes and edges will be detected for forming a loop. If it is detected that the rendered nodes and edges form a loop, the target flow path will be highlighted. If it is detected that the rendered nodes and edges do not form a loop, the process will end. If there are no duplicate nodes in the flow path of the data to be displayed, ordinary node and edge rendering will be performed, and the rendered ordinary nodes and edges will be detected for forming a loop. If it is detected that the rendered ordinary nodes and edges form a loop, the target flow path will be highlighted. If it is detected that the rendered ordinary nodes and edges do not form a loop, the process will end.

[0113] It should be noted that both the loop display and detection provided by this solution are front-end technology display solutions, and the back-end only provides blood relationship instance data. The front-end technology processing flow includes:

[0114] 1. Data processing: Data structure conversion. The back-end returns child nodes, and the front-end needs to convert them into the structure of nodes and edges for convenient visual display; Upstream and downstream dependency judgment and blood relationship aggregation: In actual display, if there are the same blood relationships, they need to be aggregated first and then displayed, so that users can clearly see that downstream nodes are all produced by a Structured Query Language (SQL) task; Filter duplicate nodes. If the node already exists in the graph, the node needs to be deleted from the newly added data to prevent node duplication; The edges of duplicate nodes need to be specially set, and the display is also different from ordinary edges, and "loop" is one of them.

[0115] 2. Node & edge rendering: Based on the predefined types of nodes and edges, the newly added nodes and edges are rendered into the graph. During rendering, different data models in the previous data processing process will be used to render different nodes and edges, including looped nodes and edges;

[0116] 3. Loop detection: After the rendering is completed, the loop detection program will be automatically started. If a looped link is found in the graph, a pop-up prompt will be given, and at the same time, the nodes and edges involved in the loop will be marked; In addition, a "highlight" operation is also provided. After clicking, the looped nodes and edges in the graph can be highlighted in the form of a water flow animation.

[0117] The present application provides a clear and recognizable scheme for drawing circular links, including how to make the distribution of lines more reasonable and how to reduce crossovers, etc. It realizes the detection and discovery of all loops in a directed graph on the pure browser side based on depth-first traversal. The loop detection algorithm of the present application is based on the depth-first traversal algorithm (DFS), which has low time and space complexity and can efficiently detect and output all loops in the graph to achieve loop detection and prompting. For the detection and prompting of circular links at the interaction level, it supports the highlighting of data flow directions and circular links. The present application provides easy-to-use interactions to highlight and identify the nodes and edges in the loop, and at the same time, it identifies the data flow direction in the form of a water-like animation, allowing users to easily discover the loops in the graph and thus discover potential problems. The present application also supports the free switching between two display modes. Among them, the graph mode can accurately display the data flow direction without duplicate nodes, facilitating the viewing of the relationships between nodes from a global perspective; the tree mode is convenient for viewing the upstream and downstream of a single node, and the node hierarchy is more clearly displayed, and even a large number of nodes will not affect readability.

[0118] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0119] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0120] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc), including several instructions to enable a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present application.

[0121] Embodiment 2

[0122] Figure 11 It is a flowchart of a data display method according to Embodiment 2 of the present application. As Figure 11 shown, the method includes the following steps:

[0123] Step S1102, in response to an input instruction acting on the operation interface, display the data to be displayed on the operation interface, where the data to be displayed flows among multiple entities;

[0124] Step S1104, in response to a display instruction acting on the operation interface, display the target flow path existing among multiple entities on the operation interface, where the target flow path is determined based on the flow direction of the data to be displayed among multiple entities, and the first entity and the last entity included in the target flow path are repeated.

[0125] In an alternative embodiment, Figure 12 It is a schematic diagram of an alternative operation interface according to Embodiment 2 of the present application. As Figure 12 shown, the operation interface includes: a display area, an input button, and a display button. When a user wants to determine the target flow path existing among multiple entities, first, the user can perform an operation on the input button on the operation interface (for example, it can be a pressing, clicking, etc. operation), and in response to the operation, an input instruction can be generated. The operation interface can display the data to be displayed in the display area based on the input instruction. Secondly, the user can perform an operation on the display button (for example, it can be a pressing, clicking, etc. operation), and in response to the operation, a display instruction can be generated. The operation interface can display the target flow path existing among multiple entities in the display area based on the display instruction.

[0126] It should be noted that the data to be displayed flows among multiple entities, the target flow path is determined based on the flow direction of the data to be displayed among multiple entities, and the first entity and the last entity included in the target flow path are repeated.

[0127] Embodiment 3

[0128] Figure 13 It is a flowchart of a data display method according to Embodiment 3 of the present application. As Figure 13 shown, the method includes the following steps:

[0129] Step S1302, obtain the data to be displayed by calling a first interface, where the first interface includes a first parameter, and the parameter value of the first parameter includes the data to be displayed, and the data to be displayed flows among multiple entities;

[0130] Step S1304: Determine whether there is a target transfer path among multiple entities based on the transfer direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target transfer path are the same.

[0131] Step S1306: When there is a target transfer path among multiple entities, output the target transfer path by calling the second interface, where the second interface includes a second parameter, and the parameter value of the second parameter includes the target transfer path.

[0132] The above first interface can be an interface for the server to obtain the data to be displayed from the user terminal. The above second interface can be an interface for the server to output the target transfer path to the user terminal.

[0133] In an optional embodiment, when a user wants to determine whether there is a target transfer path among multiple entities, first, the server can obtain the data to be displayed by calling the first interface. Second, the server can determine whether there is a target transfer path among multiple entities based on the transfer direction of the data to be displayed among the multiple entities. Finally, when it is determined that there is a target transfer path among multiple entities, the server can output the target transfer path to the user by calling the second interface.

[0134] It should be noted that the first interface includes a first parameter, and the parameter value of the first parameter includes the data to be displayed. The data to be displayed is transferred among multiple entities. The first entity and the last entity included in the target transfer path are the same. The second interface includes a second parameter, and the parameter value of the second parameter includes the target transfer path.

[0135] Embodiment 4

[0136] According to the embodiments of the present application, there is also provided a data display device for implementing the above data display method. Figure 14 It is a schematic diagram of a data display device according to Embodiment 4 of the present application. As Figure 14 shown, the device includes: an acquisition module 1402, a determination module 1404, and a display module 1406.

[0137] Among them, the acquisition module is used to acquire the data to be displayed, where the data to be displayed is transferred among multiple entities; the determination module is used to determine whether there is a target transfer path among multiple entities based on the transfer direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target transfer path are the same; the display module is used to display the target transfer path when there is a target transfer path among multiple entities.

[0138] It should be noted here that the above-mentioned acquisition module 1402, determination module 1404, and display module 1406 correspond to steps S402 to S406 in Embodiment 1. The instances and application scenarios implemented by the three modules and the corresponding steps are the same, but are not limited to the content disclosed in the above-mentioned Embodiment 1. It should be noted that the above-mentioned module or unit can be a hardware component or a software component stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n), and the above-mentioned module can also be a part of the device and can run in the computer terminal 10 provided in Embodiment 1.

[0139] In the above-mentioned embodiments of the present application, the determination module includes: a generation unit and a traversal unit.

[0140] Among them, the generation unit is used to generate a target directed graph based on the flow direction of the data to be displayed among multiple entities. The target directed graph includes multiple nodes and edges connected between two nodes. Different nodes are used to represent different entities, and the direction of the edge is used to represent the flow direction of the data to be displayed between the entities corresponding to the two nodes; the traversal unit is used to traverse multiple nodes in the target directed graph to determine whether there is a target flow path in the target directed graph.

[0141] In the above-mentioned embodiments of the present application, the generation unit includes: a determination subunit, a first generation subunit, and a second generation subunit.

[0142] Among them, the determination subunit is used to determine the flow order among multiple entities based on the flow direction of the data to be displayed among multiple entities; the first generation subunit is used to generate multiple nodes based on the flow order among multiple entities; the second generation subunit is used to generate an edge connected between two nodes based on the flow direction of the data to be displayed among multiple entities to obtain a target directed graph.

[0143] In the above-mentioned embodiments of the present application, in the case of generating a target directed graph, the first generation subunit is further used to: obtain the display mode of the target directed graph, where the display mode is used to represent the mode of displaying the target directed graph; in the case where the display mode is a graph mode, based on the flow order among multiple entities, determine whether the target entity of the node to be generated appears repeatedly, and if the target entity does not appear repeatedly, generate a node corresponding to the target entity; in the case where the display mode is a tree mode, generate multiple nodes in sequence based on the dependency relationship among multiple entities.

[0144] In the above embodiments of the present application, when the display mode is the graph mode, the first generating subunit is further configured to: determine the target type of the edge, where the target type is used to characterize whether two nodes are repeated or belong to the target transfer path; determine the distance between the edge and the two nodes based on the target type; and generate an edge connected between the two nodes based on the distance.

[0145] In the above embodiments of the present application, after generating the target directed graph based on the transfer direction of the data to be displayed among multiple entities, the determining module further includes: a first determining unit, a second determining unit, and a display unit.

[0146] Among them, the first determining unit is configured to determine the states of the multiple nodes included in the target directed graph and the state of the edge; the second determining unit is configured to determine the display mode of the multiple nodes based on the states of the multiple nodes and determine the display mode of the edge based on the state of the edge; and the display unit is configured to display the multiple nodes according to the display mode of the multiple nodes and display the edge according to the display mode of the edge.

[0147] In the above embodiments of the present application, the first generating subunit is further configured to: when detecting a first operation performed on the target node, obtain the initial state of the target node; determine the target state of the target node based on the first operation and the initial state; and adjust the state of the edge connected to the target node to the highlighted state.

[0148] In the above embodiments of the present application, the first generating subunit is further configured to: when detecting a second operation performed on the edge, obtain the initial state of the edge; determine the target state of the edge based on the second operation and the initial state; and adjust the states of the two nodes connected to the edge to the highlighted state.

[0149] In the above embodiments of the present application, the first generating subunit is further configured to: during the display process of the target transfer path, determine that the states of the nodes and edges included in the target transfer path are in the highlighted state; when the target transfer path is in the highlighted state, determine that the state of the edge included in the target transfer path is in the flowing state.

[0150] In the above embodiments of the present application, the first generating subunit is further configured to include: when detecting a search instruction for searching the target node, determine that the state of the target node is in the highlighted state.

[0151] In the above embodiments of the present application, the obtaining module includes: an obtaining unit, a first conversion unit, an aggregation unit, and a second conversion unit.

[0152] Among them, the acquisition unit is used to acquire the original data; the first conversion unit is used to perform data structure conversion on the original data to obtain the converted data; the aggregation unit is used to aggregate the data belonging to the same entity in the converted data to obtain the aggregated data; the second conversion unit is used to perform format conversion on the aggregated data to obtain the data to be displayed.

[0153] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0154] Embodiment 5

[0155] According to an embodiment of the present application, there is also provided a data display device for implementing the above data display method. Figure 15 It is a schematic diagram of a data display device according to Embodiment 5 of the present application. As Figure 15 shown, the device includes: a first display module 1502 and a second display module 1504.

[0156] Among them, the first display module is used to respond to an input instruction acting on the operation interface and display the data to be displayed on the operation interface, where the data to be displayed flows between multiple entities; the second display module is used to respond to a display instruction acting on the operation interface and display the target flow path existing between multiple entities, where the target flow path is determined based on the flow direction of the data to be displayed between multiple entities, and the first entity and the last entity included in the target flow path are repeated.

[0157] It should be noted here that the above first display module 1502 and second display module 1504 correspond to steps S1102 to S1104 in Embodiment 2, and the examples and application scenarios implemented by the two modules and the corresponding steps are the same, but are not limited to the content disclosed in the above Embodiment 1. It should be noted that the above modules or units may be hardware components or software components stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n), and the above modules may also be part of the device and can run in the computer terminal 10 provided in Embodiment 1.

[0158] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0159] Embodiment 6

[0160] According to an embodiment of the present application, there is also provided a data display device for implementing the above data display method.Figure 16 It is a schematic diagram of a data display device according to Embodiment 6 of the present application. As Figure 16 shown, the device includes: an acquisition module 1602, a determination module 1604, and an output module 1606.

[0161] Among them, the acquisition module is used to obtain the data to be displayed by calling a first interface. The first interface includes a first parameter, and the parameter value of the first parameter includes the data to be displayed, and the data to be displayed circulates among multiple entities; the determination module is used to determine whether there is a target circulation path among multiple entities based on the circulation direction of the data to be displayed among multiple entities, where the first entity and the last entity included in the target circulation path are repeated; the output module is used to output the target circulation path by calling a second interface when there is a target circulation path among multiple entities. The second interface includes a second parameter, and the parameter value of the second parameter includes the target circulation path.

[0162] It should be noted here that the above acquisition module 1602, determination module 1604, and output module 1606 correspond to steps S1302 to S1306 in Embodiment 3. The instances and application scenarios implemented by the three modules and the corresponding steps are the same, but are not limited to the content disclosed in the above Embodiment 1. It should be noted that the above modules or units can be hardware components or software components stored in a memory (for example, memory 104) and processed by one or more processors (for example, processors 102a, 102b,..., 102n), and the above modules can also be part of the device and can run in the computer terminal 10 provided in Embodiment 1.

[0163] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0164] Embodiment 7

[0165] An embodiment of the present application can provide a computer terminal, and the computer terminal can be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the above computer terminal can also be replaced with a terminal device such as a mobile terminal.

[0166] Optionally, in this embodiment, the above computer terminal can be located in at least one of multiple network devices in a computer network.

[0167] In this embodiment, the above computer terminal may execute the program code of the following steps in the data display method: obtain the data to be displayed, where the data to be displayed circulates among multiple entities; based on the circulation direction of the data to be displayed among multiple entities, determine whether there is a target circulation path among the multiple entities, where the first entity and the last entity included in the target circulation path are the same; when there is a target circulation path among the multiple entities, display the target circulation path.

[0168] Optionally, Figure 17 is a structural block diagram of a computer terminal according to an embodiment of the present application. As Figure 17 shown, the computer terminal A may include: one or more (only one is shown in the figure) processors 1702, a memory 1704, a storage controller, and a peripheral interface, where the peripheral interface is connected to a radio frequency module, an audio module, and a display.

[0169] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the data display method and device in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implements the above data display method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory may further include a memory remotely disposed relative to the processor, and these remote memories may be connected to the terminal A through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0170] The processor may call the information and application programs stored in the memory through a transmission device to execute the following steps: obtain the data to be displayed, where the data to be displayed circulates among multiple entities; based on the circulation direction of the data to be displayed among multiple entities, determine whether there is a target circulation path among the multiple entities, where the first entity and the last entity included in the target circulation path are the same; when there is a target circulation path among the multiple entities, display the target circulation path.

[0171] Optionally, the above processor may also execute the program code of the following steps: generate a target directed graph based on the circulation direction of the data to be displayed among multiple entities, where the target directed graph includes multiple nodes and edges connected between two nodes, different nodes are used to represent different entities, and the direction of the edge is used to represent the circulation direction of the data to be displayed between the entities corresponding to the two nodes; traverse the multiple nodes in the target directed graph to determine whether there is a target circulation path in the target directed graph.

[0172] Optionally, the above-mentioned processor may also execute the program code of the following steps: determine the transfer order among multiple entities based on the transfer direction of the data to be displayed among the multiple entities; generate multiple nodes based on the transfer order among the multiple entities; generate edges connected between two nodes based on the transfer direction of the data to be displayed among the multiple entities, and obtain the target directed graph.

[0173] Optionally, the above-mentioned processor may also execute the program code of the following steps: obtain the display mode of the target directed graph, where the display mode is used to represent the mode of displaying the target directed graph; in the case where the display mode is the graph mode, determine whether the target entity of the node to be generated appears repeatedly based on the transfer order among the multiple entities, and generate the node corresponding to the target entity in the case where the target entity does not appear repeatedly; in the case where the display mode is the tree mode, generate multiple nodes in sequence based on the dependency relationship among the multiple entities.

[0174] Optionally, the above-mentioned processor may also execute the program code of the following steps: determine the target type of the edge, where the target type is used to represent whether two nodes are repeated and whether there are multiple edges connected between the two nodes; determine the distance between the edge and the two nodes based on the target type; generate the edge connected between the two nodes based on the distance.

[0175] Optionally, the above-mentioned processor may also execute the program code of the following steps: determine the states of the multiple nodes included in the target directed graph and the state of the edge; determine the display mode of the multiple nodes based on the states of the multiple nodes, and determine the display mode of the edge based on the state of the edge; display the multiple nodes according to the display mode of the multiple nodes, and display the edge according to the display mode of the edge.

[0176] Optionally, the above-mentioned processor may also execute the program code of the following steps: in the case of detecting a first operation performed on a target node, obtain the initial state of the target node; determine the target state of the target node based on the first operation and the initial state; adjust the state of the edge connected to the target node to the highlighted state.

[0177] Optionally, the above-mentioned processor may also execute the program code of the following steps: in the case of detecting a second operation performed on an edge, obtain the initial state of the edge; determine the target state of the edge based on the second operation and the initial state; adjust the states of the two nodes connected to the edge to the highlighted state.

[0178] Optionally, the above-mentioned processor may also execute the program code of the following steps: during the process of displaying a target transfer path, determine that the states of the nodes and edges included in the target transfer path are in the highlighted state; in the case where the target transfer path is in the highlighted state, determine that the state of the edge included in the target transfer path is in the flowing state.

[0179] Optionally, the above-mentioned processor may also execute the program code of the following steps: when detecting a search instruction for searching a target node, determine the state of the target node as a highlighted state.

[0180] Optionally, the above-mentioned processor may also execute the program code of the following steps: obtain original data; perform data structure conversion on the original data to obtain converted data; aggregate the data belonging to the same entity in the converted data to obtain aggregated data; perform format conversion on the aggregated data to obtain data to be displayed.

[0181] In the embodiments of the present application, a method is adopted to obtain data to be displayed, where the data to be displayed circulates among multiple entities; based on the circulation direction of the data to be displayed among multiple entities, determine whether there is a target circulation path among the multiple entities, where the first entity and the last entity included in the target circulation path are repeated; in the case where there is a target circulation path among the multiple entities, a way to display the target circulation path. It is easy to notice that the target circulation path can be automatically detected through the circulation direction of the data to be displayed. While detecting the existence of the target circulation path, the target circulation path can also be displayed through the user terminal, achieving the purpose of quickly determining the flow direction of abnormal data, thus realizing the technical effect of being able to quickly determine the flow direction of abnormal data, and further solving the technical problem in the related art that the abnormal flow direction of data cannot be quickly detected.

[0182] Those of ordinary skill in the art can understand that the structure shown in the figure is only schematic, and the computer terminal may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, and a mobile Internet device (Mobile Internet Devices, MID), a PAD and other terminal devices. Figure 17 It does not limit the structure of the above-mentioned electronic device. For example, computer terminal A may further include more or fewer components (such as a network interface, a display device, etc.) than those shown in Figure 17 or have a different configuration from that shown in Figure 17 shown.

[0183] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the relevant hardware of the terminal device through a program, and the program can be stored in a computer-readable storage medium. The storage medium may include: a flash drive, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disc, etc.

[0184] Embodiment 8

[0185] Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the above storage medium may be used to store the program code executed by the data display method provided in the first embodiment above.

[0186] Optionally, in this embodiment, the above storage medium may be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group.

[0187] Optionally, in this embodiment, the storage medium is set to store the program code for performing the following steps: obtaining the data to be displayed, where the data to be displayed circulates among multiple entities; determining whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities, where the first entity and the last entity included in the target circulation path are repeated; and displaying the target circulation path when there is a target circulation path among the multiple entities.

[0188] Optionally, in this embodiment, the storage medium is also set to store the program code for performing the following steps: generating a target directed graph based on the circulation direction of the data to be displayed among the multiple entities, where the target directed graph includes multiple nodes and edges connected between two nodes, different nodes are used to represent different entities, and the direction of the edge is used to represent the circulation direction of the data to be displayed between the entities corresponding to the two nodes; traversing the multiple nodes in the target directed graph to determine whether there is a target circulation path in the target directed graph.

[0189] Optionally, in this embodiment, the storage medium is also set to store the program code for performing the following steps: determining the circulation order among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities; generating multiple nodes based on the circulation order among the multiple entities; and generating edges connected between two nodes based on the circulation direction of the data to be displayed among the multiple entities to obtain a target directed graph.

[0190] Optionally, in this embodiment, the storage medium is also set to store the program code for performing the following steps: obtaining the display mode of the target directed graph, where the display mode is used to represent the mode of displaying the target directed graph; when the display mode is the graph mode, determining whether the target entity of the node to be generated appears repeatedly based on the circulation order among the multiple entities, and generating the node corresponding to the target entity when the target entity does not appear repeatedly; when the display mode is the tree mode, generating multiple nodes in sequence based on the dependency relationship among the multiple entities.

[0191] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: determining a target type of an edge, where the target type is used to characterize whether two nodes are repeated and whether there are multiple edges connected between the two nodes; determining a distance between the edge and the two nodes based on the target type; and generating an edge connected between the two nodes based on the distance.

[0192] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: determining states of multiple nodes included in a target directed graph and states of edges; determining display modes of the multiple nodes based on the states of the multiple nodes and determining display modes of the edges based on the states of the edges; and displaying the multiple nodes according to the display modes of the multiple nodes and displaying the edges according to the display modes of the edges.

[0193] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: when detecting a first operation performed on a target node, obtaining an initial state of the target node; determining a target state of the target node based on the first operation and the initial state; and adjusting a state of an edge connected to the target node to a highlighted state.

[0194] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: when detecting a second operation performed on an edge, obtaining an initial state of the edge; determining a target state of the edge based on the second operation and the initial state; and adjusting states of two nodes connected to the edge to a highlighted state.

[0195] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: during a process of displaying a target transfer path, determining that states of nodes and edges included in the target transfer path are in a highlighted state; and when the target transfer path is in the highlighted state, determining that a state of an edge included in the target transfer path is in a flowing state.

[0196] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: when detecting a search instruction for searching a target node, determining that a state of the target node is in a highlighted state.

[0197] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: obtaining original data; performing data structure conversion on the original data to obtain converted data; aggregating data belonging to the same entity in the converted data to obtain aggregated data; and performing format conversion on the aggregated data to obtain data to be displayed.

[0198] The serial numbers of the embodiments of the present application above are only for description and do not represent the advantages and disadvantages of the embodiments.

[0199] In the above embodiments of the present application, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0200] In the several embodiments provided by the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of units or modules can be in an electrical or other form.

[0201] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0202] In addition, the functional units in the various embodiments of the present application can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0203] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. And the aforementioned storage medium includes: USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks or optical disks and other various media that can store program codes.

[0204] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A data display method, characterized in that, it includes: obtaining data to be displayed, wherein the data to be displayed circulates among multiple entities; determining whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities, wherein the first entity and the last entity included in the target circulation path are the same; displaying the target circulation path when the target circulation path exists among the multiple entities.

2. The method according to claim 1, characterized in that, determining whether there is a target circulation path among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities includes: generating a target directed graph based on the circulation direction of the data to be displayed among the multiple entities, wherein the target directed graph includes multiple nodes and edges connected between two nodes, different nodes are used to represent different entities, and the direction of the edge is used to represent the circulation direction of the data to be displayed between the entities corresponding to the two nodes; traversing the multiple nodes in the target directed graph to determine whether the target circulation path exists in the target directed graph.

3. The method according to claim 2, characterized in that, generating a target directed graph based on the circulation direction of the data to be displayed among the multiple entities includes: determining the circulation order among the multiple entities based on the circulation direction of the data to be displayed among the multiple entities; generating the multiple nodes based on the circulation order among the multiple entities; generating an edge connected between the two nodes based on the circulation direction of the data to be displayed among the multiple entities to obtain the target directed graph.

4. The method according to claim 3, characterized in that, when generating the target directed graph, generating the multiple nodes based on the circulation order among the multiple entities includes: obtaining the display mode of the target directed graph, wherein the display mode is used to represent the mode of displaying the target directed graph; when the display mode is a graph mode, determining whether the target entity of the node to be generated appears repeatedly based on the circulation order among the multiple entities, and generating a node corresponding to the target entity when the target entity does not appear repeatedly; when the display mode is a tree mode, generating the multiple nodes in sequence based on the dependency relationship among the multiple entities.

5. The method according to claim 4, characterized in that, when the display mode is a graph mode, the method further includes: determining the target type of the edge, wherein the target type is used to represent whether the two nodes are repeated and whether there are multiple edges connected between the two nodes; determining the distance between the edge and the two nodes based on the target type; generating an edge connected between the two nodes based on the distance.

6. The method according to claim 2, characterized in that, After generating a target directed graph based on the flow direction of the data to be displayed among the multiple entities, the method further includes: Determining the states of the multiple nodes included in the target directed graph and the states of the edges; Determining the display modes of the multiple nodes based on the states of the multiple nodes, and determining the display modes of the edges based on the states of the edges; Displaying the multiple nodes according to the display modes of the multiple nodes, and displaying the edges according to the display modes of the edges.

7. The method according to claim 5, wherein, the method further includes: When detecting a first operation performed on a target node, obtaining the initial state of the target node; Determining the target state of the target node based on the first operation and the initial state; Adjusting the states of the edges connected to the target node to a highlighted state.

8. The method according to claim 5, wherein, the method further includes: When detecting a second operation performed on the edge, obtaining the initial state of the edge; Determining the target state of the edge based on the second operation and the initial state; Adjusting the states of the two nodes connected to the edge to a highlighted state.

9. The method according to claim 5, wherein, the method further includes: During the process of displaying the target flow path, determining that the states of the nodes and edges included in the target flow path are in a highlighted state; When the target flow path is in a highlighted state, determining that the states of the edges included in the target flow path are in a flowing state.

10. The method according to claim 1, wherein, obtaining the data to be displayed includes: Obtaining the original data; Performing data structure conversion on the original data to obtain the converted data; Aggregating the data belonging to the same entity in the converted data to obtain the aggregated data; Performing format conversion on the aggregated data to obtain the data to be displayed.

11. A data display method, wherein, it includes: Responding to an input instruction acting on an operation interface, and displaying the data to be displayed on the operation interface, wherein the data to be displayed flows among multiple entities; Responding to a display instruction acting on the operation interface, and displaying a target flow path existing among the multiple entities on the operation interface, wherein the target flow path is determined based on the flow direction of the data to be displayed among the multiple entities, and the first entity and the last entity included in the target flow path are repeated.

12. A data display method, wherein, it includes: Obtaining the data to be displayed by calling a first interface, wherein the first interface includes a first parameter, and the parameter value of the first parameter includes the data to be displayed, and the data to be displayed flows among multiple entities; Based on the flow direction of the data to be displayed among the multiple entities, determining whether there is a target flow path among the multiple entities, wherein the first entity and the last entity included in the target flow path are repeated; When there is the target transfer path among the multiple entities, output the target transfer path by calling a second interface, where the second interface includes a second parameter, and the parameter value of the second parameter includes the target transfer path.

13. An electronic device, characterized in that it includes: a memory storing an executable program; a processor for running the program, where when the program runs, it executes the method according to any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a stored executable program, where when the executable program runs, it controls the device where the storage medium is located to execute the method according to any one of claims 1 to 12.