Display method and device of object group, electronic equipment and storage medium

Abstract

This application provides a method, apparatus, electronic device, and storage medium for displaying object groups. The solution in this application identifies entity objects and their relationships within the data. By distinguishing at least two identified object subgroups with corresponding display styles, different object subgroups exhibit different display effects on the canvas. This allows for the intuitive presentation of different object subgroups while displaying the entity objects and relationships within a large amount of data. The differentiation and display of different object subgroups clarifies the visual presentation of complex data, reduces complexity, highlights different object subgroups, and improves readability. Especially when dealing with massive amounts of data and a large number of entity objects, the differentiation of subgroups into display areas can efficiently and clearly show the relationships between entity objects.

Description

Technical Field

[0001] This application relates to the field of data analysis technology, and in particular to a method, apparatus, electronic device, storage medium, and computer program product for displaying a group of objects. Background Technology

[0002] Graphs are a form of data visualization that presents complex data in an intuitive and vivid way. They can uncover data relationships, help users quickly understand data and discover patterns, and comprehend the content conveyed and expressed by large amounts of data. A graph visualization engine is a tool for analyzing data relationships. Through visualization capabilities such as rendering, drawing, interactivity, and animation, it presents data with complex relationships to users in a readable graph format.

[0003] When using graph visualization engines to render large amounts of data, there is still room for improvement in how the relationships between the data are specifically displayed, especially when dealing with large amounts of complex data. The data needs to be presented to users with lower visual complexity and higher readability. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, storage medium, and computer program product for displaying a group of objects to solve one or more of the above-mentioned technical problems.

[0005] In a first aspect, embodiments of this application provide a method for displaying a group of objects, comprising: obtaining entity object data from at least one data source, the entity object data including object identifiers of multiple entity objects and object relationship description information describing the relationships between the multiple entity objects; constructing an object group relationship diagram corresponding to the object group based on the object relationship description information between the entity objects; identifying object subgroups corresponding to at least two subgroup relationship types from the object group relationship diagram according to the connection relationships between the entity objects in the object group relationship diagram; updating the display attributes of entity objects in the object subgroups according to the display style corresponding to the subgroup relationship types of the object subgroups; and outputting the updated display attributes of entity objects in the object subgroups to a canvas loading terminal to display the object group relationship diagram of multiple objects on a canvas.

[0006] Secondly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor implements the above-described method when executing the computer program.

[0007] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0008] Fourthly, embodiments of this application provide a computer program product, wherein the computer program product includes a computer program that, when executed by a processor, implements the above-described method.

[0009] According to the embodiments of this application, entity object data including object identifiers of multiple entity objects and object relationship description information describing the association between multiple entity objects is obtained from at least one data source. Further, an object group relationship diagram corresponding to the object group is constructed based on the object relationship description information. According to the connection relationship between entity objects in the object group relationship diagram, object subgroups corresponding to at least two subgroup relationship types are identified from the object group relationship diagram. This is so that the display attributes of entity objects in the object subgroups are updated according to the display style corresponding to the subgroup relationship type of the object subgroups. After the updated display attributes of entity objects in the object subgroups are output to the canvas loading end, the object group relationship diagram of multiple objects is displayed on the canvas. Therefore, the solution of this application identifies entity objects and their relationships within the data. By distinguishing at least two identified object subgroups with corresponding display styles, different object subgroups exhibit different display effects on the canvas. This allows for the intuitive presentation of different object subgroups while displaying the entity objects and relationships within a large amount of data. The differentiation and display of these subgroups clarifies the visual presentation of complex data, reduces complexity, highlights different object subgroups, and improves readability. Especially when dealing with massive amounts of data and a large number of entity objects, the segmented display of subgroups efficiently and clearly shows the relationships between entity objects, providing strong support for users to further analyze object relationships and improving analysis efficiency.

[0010] This application embodiment can also determine entity objects of different object types from the object subgroup based on the object types of multiple entity objects corresponding to the subgroup relationship type, and then update the display attributes of entity objects in the object subgroup according to the display style corresponding to the object type of the entity object, so that entity objects of different object types present different display effects, intuitively highlighting entity objects of different object types and other types of entity objects associated with each object type entity object.

[0011] Furthermore, embodiments of this application can also identify common entity objects belonging to multiple non-hierarchical object subgroups. Further, based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, the display attributes of the common entity object and at least some other entity objects in its object subgroup are updated. This ensures that the updated common entity object corresponds to different display attributes than other entity objects in its object subgroup, thereby highlighting key nodes that constitute the association relationships between object subgroups and clearly presenting the association paths between groups in the object group relationship diagram.

[0012] Furthermore, the embodiments of this application can also be applied to scenarios with different business types. After determining the business type of the current application, at least two subgroup relationship types for this object group relationship diagram are further determined, so that the display of group relationships can adapt to different scenarios and meet the needs of different object relationship presentation in different scenarios.

[0013] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application, it can be implemented according to the contents of the specification. In order to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0014] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments according to this application and should not be construed as limiting the scope of this application.

[0015] Figure 1 A schematic diagram of an object group relationship is shown. Figure 1 ;

[0016] Figure 2 This illustration shows a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 2 ;

[0017] Figure 3 This illustration shows a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 3 ;

[0018] Figure 4 This illustration shows a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 4 ;

[0019] Figure 5 This illustration shows a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 5 ;

[0020] Figure 6 This illustration shows a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 6 ;

[0021] Figure 7 A flowchart illustrating a method for displaying a group of objects provided in an embodiment of this application is shown;

[0022] Figure 8 A structural block diagram of a display device for a group of objects provided in an embodiment of this application is shown; and

[0023] Figure 9 A block diagram of an electronic device used to implement embodiments of this application is shown. Detailed Implementation

[0024] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the concept or scope of this application. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0025] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and all of them fall within the protection scope of the embodiments of this application.

[0026] This application provides a method for displaying a group of objects, where the entity objects mentioned can be people or objects, such as users on social media platforms, vehicles or pedestrians in urban street scenes, etc. Entity objects can have corresponding identifiers, such as a person's name, mobile phone number, user nickname, vehicle number, etc., or can use any one or more attributes of the entity object as object identifiers. Entity objects can have object relationships, such as family relationships, colleague relationships, friend relationships, or social media platform friend relationships, or access relationships generated based on page visits, etc. Entity object data includes the object identifiers corresponding to the entity objects and description information of the object relationships between entity objects, which can be obtained from one or more data sources, which can be local or third-party data systems, databases, data platforms, etc. Taking a user behavior database as an example, entity object data is obtained from the user behavior database that records entity object behaviors. If user A visits another user B's page on a webpage, a relationship is established between the two users based on this one visit behavior. For each user, the object identifiers are used as entity objects, and description information of the object relationship is recorded in the user behavior database.

[0027] The data obtained from one or more data sources may contain various redundant information or formatting issues. After obtaining the entity object data, further preprocessing can be performed, such as data cleaning, data format conversion, data merging, and data deduplication. Data cleaning removes unnecessary information from the data; data format conversion adjusts the data to a unified representation; data merging simplifies data representing the same or similar meanings into a single data entry. For example, if entity object A and entity object B have family and colleague relationships, these two relationships can be merged to indicate a connection between entity object A and entity object B. Of course, in actual business scenarios, merging may not be necessary; instead, weighting can be performed based on the number and / or type of relationships between entity object A and entity object B, and the distinction can be made through the length and thickness of the connecting lines; data deduplication removes duplicate data, significantly reducing the amount of data processing.

[0028] Object relationship description information represents the association between entity objects. After extracting object identifiers and object relationship description information from entity object data, object group relationship diagrams between multiple entity objects can be constructed based on the object relationship description information. The object group relationship diagram displays multiple entity objects and shows the association between entity objects by connecting them. Entity objects in the diagram can be displayed as set icons, images, or object identifiers. The object identifiers of entity objects in the underlying data of the same diagram can be the same type of identifier or different types of identifiers. For example, a person can be identified by a mobile phone number or by an avatar.

[0029] After constructing a preliminary object group relationship diagram, object subgroups can be further identified from the diagram based on the connections between entity objects. An object subgroup refers to a subset of an object group that shares specific links, and each subgroup has a corresponding subgroup relationship type. For example, a subgroup with one or more entity objects as the central entity object, and all other entity objects connected to these central entity objects, is a centrally clustered subgroup (or a force-directed subgroup). Similarly, multiple entity objects directly or indirectly connected to each other in a hierarchical layout constitute a hierarchical subgroup. Furthermore, some entity objects have no connections to any other entity objects, belonging to isolated nodes within the group, and can be considered isolated subgroups. In practice, the number of subgroups can be set according to actual needs; this application does not limit this.

[0030] After identifying at least two types of object subgroups in the object group relationship diagram through the above process, display styles corresponding to different subgroup relationship types can be found. The presentation of the display style is specifically reflected in the display attributes of entity objects within the object subgroup. For example, the display style of a central cluster type subgroup can be centered on a central entity object, with other entity objects arranged around it, and the central entity object and other entity objects displayed using different colors. As another example, in a hierarchical subgroup, the top-level entity objects (entity objects with the most direct connections or entity objects connected to other groups) are arranged above other entity objects in the subgroup, with other level entity objects arranged below them, and entity objects of different levels displayed using different display methods.

[0031] Update the display properties of entity objects according to the display style, so that different subgroup types can be displayed according to the corresponding display style, making it easier for users to distinguish different object subgroups based on the display style. Display properties can include position coordinates on the canvas, color, line length, line color, line thickness, etc.

[0032] After updating the display properties of entity objects in the object subgroup, the updated display properties of entity objects can be input into the canvas loading end, so that the object group relationship diagram of multiple objects can be displayed on the canvas.

[0033] like Figure 1 The image shown is a schematic diagram of a group of objects. Figure 1 This diagram includes three centrally clustered subgroups, each centered on a red entity object. The bottommost centrally clustered subgroup is connected to a hierarchical subgroup, which in turn connects to the bottommost central entity object. Isolated entity objects are also present at the top of the diagram. The central entity object is distinguished by color from the other entity objects, and the centrally clustered subgroups are displayed using a style corresponding to their respective subgroup types. Figure 2 This is a schematic diagram of an object group relationship according to an embodiment of this application. Figure 2 Compared to Figure 1The hierarchical subgroups in the lower right corner are displayed in different colors, and hierarchical object subgroups are displayed in a hierarchical style, thus intuitively distinguishing different types of object subgroups. Using corresponding display styles for different types of object subgroups makes the display effect clearer. Therefore, through the above process, while displaying the entity objects contained in a large amount of data and the relationships between them, different object subgroups are presented intuitively and differentiated. This makes the visual display of complex data clear, reduces complexity, highlights different object subgroups, and improves readability. Especially when dealing with huge amounts of data and a large number of entity objects, the display effect of distinguishing subgroups can efficiently and clearly show the relationships between entity objects, providing strong support for users to further analyze object relationships and improving analysis efficiency.

[0034] In the embodiments of this application, key entity objects can also be selected interactively, and special display effects can be configured for the key entity objects, or special display effects can be configured for entity objects occupying special positions in subgroup types (such as central entity objects).

[0035] The rendering of the above object group relationship graph can be achieved based on a graph visualization engine. By creating a view container, obtaining entity object data, instantiating and creating the object group relationship graph through the above process, and configuring the data source for rendering, the object group relationship graph can finally be displayed on the canvas.

[0036] In practical applications, at least two subgroup relationship types can be determined based on the business type corresponding to the object group, and the business type can be used to determine the object group relationship diagram. That is to say, different subgroup relationship types can be identified for different business types, so that the display of group relationships can adapt to different scenarios and meet the needs of different object relationship presentation in different scenarios.

[0037] When constructing an object group relationship graph based on the relationship description information between entity objects, based on the object identifiers extracted from the entity object data, for any two entity objects corresponding to the object identifiers, further extract the object relationship description information of these two entity objects from the entity object data, and then further generate the connection relationship between these two entity objects based on at least one object relationship description information extracted from the two entity objects, so as to create an object group relationship graph corresponding to the object group based on the connection relationship between the two entity objects.

[0038] When identifying object subgroups with at least two subgroup relationship types, an analysis is performed on each entity object. The analysis specifically includes analyzing the tendency data of the entity object to belong to various subgroup relationship types, comparing the tendency data, and determining the subgroup relationship type with the greater tendency as the subgroup relationship type to which the entity object belongs. Taking hierarchical and centrally clustered subgroups as examples of subgroup relationship types, when analyzing the tendency data belonging to the centrally clustered subgroup type, the number of relational nodes connected to a single node is counted. When analyzing the tendency data belonging to the hierarchical subgroup type, other nodes associated with a single node are searched starting from that single node. The maximum number of connections between a single node and another node is used as the link level of the single node. In other words, the number of relational nodes and the link level are used as tendency data. By comparing the number of relational nodes and the link level, the subgroup relationship type of the object subgroup formed by the single node and other nodes is determined based on the numerical comparison. If the number of relational nodes is greater than the link level, the entity object belongs to the centrally clustered subgroup; if the number of relational nodes is less than the link level, the entity object belongs to the hierarchical subgroup. After identifying the corresponding subgroup type for different subgroup types, a suitable display style can be used. For example, hierarchical subgroups with clear upstream and downstream relationships use a hierarchical layout display style.

[0039] The display style corresponding to the subgroup relationship type includes not only the display style of the subgroup as a whole, but also the display style of the entity objects in the object subgroup. When updating the display attributes of entity objects in the object subgroup according to the display style corresponding to the subgroup relationship type, entity objects of various object types can be found from the object subgroup based on the object types of the various entity objects corresponding to the subgroup relationship type. For example, a central clustered object subgroup can be divided into a central entity object and other entity objects, and a hierarchical object subgroup can be divided into entity objects of different levels. Furthermore, the display attributes of entity objects in the object subgroup can be updated according to the display style corresponding to the object type of the entity object. For example, different object types use different colors, shapes, position coordinates, etc.

[0040] Furthermore, embodiments of this application can also identify and highlight common entity objects belonging to multiple non-hierarchical object subgroups. First, common entity objects belonging to multiple non-hierarchical object subgroups are identified. Then, based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, the display attributes of the common entity object and at least some other entity objects within its object subgroups are updated. The goal is to ensure that the updated common entity object corresponds to different display attributes than other entity objects within its object subgroups. By differentiating the display attributes, key nodes constituting the relationships between object subgroups can be highlighted, clearly presenting the relationship paths between groups in the object group relationship diagram.

[0041] For example, the display style of a non-hierarchical subgroup of objects to which a shared entity object belongs can be the position coordinates of the central entity object within that subgroup. The updated display attribute of the shared entity object can then be its position coordinates; that is, the position of the shared entity object on the canvas is determined by the position of the central entity object in each of the multiple subgroups it is connected to. Alternatively, the display attribute of the shared entity object can be determined by other display styles of the multiple subgroups it is connected to. For instance, the display color of the shared entity object can be determined by using multiple colors displayed together in its icon, based on the display colors of the connected subgroups. Or, the length of the connecting lines between the connected subgroups can be determined.

[0042] The length of the connection between shared entity objects can also be distinguished from the length of the connection between them and other subgroup objects to highlight the shared entity objects. The display attributes of the aforementioned entity objects can be set according to actual needs, and this application does not impose any restrictions on this.

[0043] See Figure 3 This illustration shows a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 3 The identified common entity objects include the four orange nodes in the middle of the object group relationship graph. At the same time, the lines connecting the common entity objects to the entity objects of other subgroups are stretched to several times the length of the lines connecting the nodes of other subgroups, thus making the common entity objects clear.

[0044] When updating the display attributes of a shared entity object and at least some other entity objects in its subgroups based on the display style of multiple non-hierarchical object subgroups to which the shared entity object belongs in the object group relationship diagram, the number of object subgroups with non-hierarchical subgroup relationship types (e.g., the number of centrally clustered subgroups) can be identified. The central entity object that multiple entity objects in the non-hierarchical object subgroups are connected to can be found respectively. The shared entity object belonging to multiple non-hierarchical object subgroups can be identified, that is, the shared entity object is connected to the central entity node of multiple non-hierarchical object subgroups. Then, based on the position coordinates of multiple central entity objects in the object group relationship diagram, the position coordinates of the shared entity object and at least some other entity objects in its subgroups can be re-determined.

[0045] In the process of redetermining the position coordinates of a common entity object and at least some other entity objects in its subgroup based on the position coordinates of multiple central entity objects in the object group relationship diagram, the coordinate position of the common entity object is first redetermined based on the position coordinates of multiple central entity objects in the object group relationship diagram. If it is necessary to change the length of the connection between the common entity object and other entity objects with connection relationships, the position coordinates of at least some other entity objects in the subgroup can be redetermined based on the length relationship between the first type of connection between the common entity object and the central entity object and the second type of connection between other entity objects in the subgroup and the central entity object, thereby achieving the highlighting of the common entity object.

[0046] For isolated entity objects within an object group, they are treated as non-group entity objects and grouped and displayed in certain areas for easier individual analysis and display. After identifying non-group entity objects that do not belong to the object's subgroup, the display style of the remaining entity objects is determined based on the distance between the non-group entity objects and the subgroup, and the display attributes of the non-group entity objects are updated. In one implementation, the distance between non-group entity objects and other entity objects belonging to the object's subgroup can be calculated, and the X-axis and Y-axis averages of all distances can be calculated. The minimum X-axis value of all group and non-group entity objects on the canvas is subtracted from the X-axis average to obtain the X-axis position coordinates of the non-group entity objects, and the minimum Y-axis value is subtracted from the Y-axis average to obtain the Y-axis position coordinates of the non-group entity objects. See also Figure 4 This is a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 4 The non-group entity object in the upper left corner of the diagram is compared to Figure 3 The layout has been made neater, making the displayed content clearer and more intuitive.

[0047] Figure 5 This is a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 5 This involves more entity objects, a greater number of object subgroups, and a larger number of shared nodes. It is evident that the solution adopted in this application embodiment can present an object group diagram with a clear layout and well-defined object relationships, even when dealing with a larger amount of data. Figure 6 This is a schematic diagram of an object group relationship provided in an embodiment of this application. Figure 6 In this diagram, each subgroup of objects is displayed separately, with no shared entity objects. The layout between and within groups is very clear.

[0048] The execution entity in this application embodiment can be an application, service, instance, functional module in software form, virtual machine (VM), container, or cloud server, or hardware device with data processing capabilities (such as server or terminal device) or hardware chip (such as CPU, GPU, FPGA, NPU, AI accelerator card, or DPU). The device for providing the service can be deployed on the computing device of the application providing the corresponding service or on a cloud computing platform providing computing power, storage, and network resources. The cloud computing platform can provide services in the following modes: IaaS (Infrastructure as a Service), PaaS (Platform as a Service), SaaS (Software as a Service), or DaaS (Data as a Service). Taking the platform providing SaaS (Software as a Service) as an example, the cloud computing platform can utilize its own computing resources to provide the functional execution of the display module for the target group, and the specific application architecture can be built according to service requirements.

[0049] 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 used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0050] The technical solution of this application and how it solves the aforementioned technical problems are described in detail below with specific embodiments. The listed specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0051] This application provides a method for displaying a group of objects, such as... Figure 7 The diagram shown is a flowchart of a method 700 for displaying a group of objects according to an embodiment of this application. The method 700 may include:

[0052] In step 701, entity object data is obtained from at least one data source. The entity object data includes object identifiers of multiple entity objects and object relationship description information used to describe the association between the multiple entity objects.

[0053] In step 702, an object group relationship diagram corresponding to the object group is constructed based on the object relationship description information between the entity objects.

[0054] In step 703, object subgroups corresponding to at least two subgroup relationship types are identified from the object group relationship graph according to the connection relationships between the entity objects in the object group relationship graph.

[0055] In step 704, the display attributes of entity objects in the object subgroup are updated according to the display style corresponding to the subgroup relationship type of the object subgroup.

[0056] In step 705, the updated display attributes of the entity objects in the object subgroup are output to the canvas loading end to display the object group relationship diagram of multiple objects on the canvas.

[0057] In one embodiment, when constructing an object group relationship graph corresponding to an object group based on the object relationship description information between entity objects, object relationship description information of two entity objects can be extracted from the entity object data based on the object identifiers of any two entity objects; a connection relationship between the two entity objects can be generated based on at least one object relationship description information extracted from the two entity objects; and an object group relationship graph corresponding to an object group can be created based on the connection relationship between the two entity objects.

[0058] In one embodiment, when identifying object subgroups corresponding to at least two subgroup relationship types from the object group relationship diagram according to the connection relationships between entity objects described in the object group relationship diagram, the number of relational nodes that have connection relationships with a single node can be found for an entity object that is a single node in the object group relationship diagram; other nodes associated with a single node can be found starting from the single node, and the maximum number of connection relationships between a single node and another other node can be used as the link level of the single node; the subgroup relationship type of the object subgroup formed by the single node and other nodes can be determined according to the numerical comparison relationship between the number of relational nodes and the link level.

[0059] In one embodiment, the display style corresponding to the subgroup relationship type includes the display style corresponding to the entity objects in the object subgroup. When updating the display attributes of entity objects in the object subgroup according to the display style corresponding to the subgroup relationship type, entity objects of various object types can be searched from the object subgroup based on the object types of various entity objects corresponding to the subgroup relationship type; and the display attributes of entity objects in the object subgroup can be updated according to the display style corresponding to the object type of the entity object.

[0060] In one embodiment, a common entity object belonging to multiple non-hierarchical object subgroups can also be identified; based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, the display attributes of the common entity object and at least some of the other entity objects in the object subgroups to which it belongs are updated, and the updated common entity object corresponds to different display attributes than the other entity objects in the object subgroups to which it belongs.

[0061] In one embodiment, when updating the display attributes of the shared entity object and at least some other entity objects in its subgroups based on the display style of multiple non-hierarchical object subgroups to which the shared entity object belongs in the object group relationship diagram, it is possible to identify the number of object subgroups with non-hierarchical subgroup relationship types among the multiple object subgroups; find the central entity object that is commonly connected to multiple entity objects in the non-hierarchical object subgroups; identify the shared entity object belonging to multiple non-hierarchical object subgroups; and redetermine the position coordinates of the shared entity object and at least some other entity objects in its subgroups based on the position coordinates of the multiple central entity objects in the object group relationship diagram.

[0062] In one embodiment, when redetermining the position coordinates of a common entity object and at least some other entity objects in its subgroup based on the position coordinates of multiple central entity objects in the object group relationship diagram, the coordinate position of the common entity object can be redetermined based on the position coordinates of multiple central entity objects in the object group relationship diagram; and the position coordinates of at least some other entity objects in its subgroup can be redetermined based on the length relationship between the first type of connection between the common entity object and the central entity object and the second type of connection between other entity objects in the subgroup and the central entity object.

[0063] In one embodiment, before outputting the updated display attributes of entity objects in the object subgroup to the canvas loading end to display the object group relationship graph of multiple objects on the canvas, it is also possible to find non-group entity objects among the multiple entity objects that do not belong to the object subgroup, and determine the display style corresponding to the remaining entity objects and update the display attributes of the non-group entity objects based on the distance between the non-group entity objects and the subgroup of objects.

[0064] In one embodiment, after obtaining entity object data from at least one data source, the business type corresponding to the object group can be determined, and at least two subgroup relationship types for this object group relationship diagram can be determined based on the business type.

[0065] According to the embodiments of this application, entity object data including object identifiers of multiple entity objects and object relationship description information describing the association between multiple entity objects is obtained from at least one data source. Further, an object group relationship diagram corresponding to the object group is constructed based on the object relationship description information. According to the connection relationship between entity objects in the object group relationship diagram, object subgroups corresponding to at least two subgroup relationship types are identified from the object group relationship diagram. This is so that the display attributes of entity objects in the object subgroups are updated according to the display style corresponding to the subgroup relationship type of the object subgroups. After the updated display attributes of entity objects in the object subgroups are output to the canvas loading end, the object group relationship diagram of multiple objects is displayed on the canvas. Therefore, the solution of this application identifies entity objects and their relationships within the data. By distinguishing at least two identified object subgroups with corresponding display styles, different object subgroups exhibit different display effects on the canvas. This allows for the intuitive presentation of different object subgroups while displaying the entity objects and relationships within a large amount of data. The differentiation and display of these subgroups clarifies the visual presentation of complex data, reduces complexity, highlights different object subgroups, and improves readability. Especially when dealing with massive amounts of data and a large number of entity objects, the segmented display of subgroups efficiently and clearly shows the relationships between entity objects, providing strong support for users to further analyze object relationships and improving analysis efficiency.

[0066] This application embodiment can also determine entity objects of different object types from the object subgroup based on the object types of multiple entity objects corresponding to the subgroup relationship type, and then update the display attributes of entity objects in the object subgroup according to the display style corresponding to the object type of the entity object, so that entity objects of different object types present different display effects, intuitively highlighting entity objects of different object types and other types of entity objects associated with each object type entity object.

[0067] Furthermore, embodiments of this application can also identify common entity objects belonging to multiple non-hierarchical object subgroups. Further, based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, the display attributes of the common entity object and at least some other entity objects in its object subgroup are updated. This ensures that the updated common entity object corresponds to different display attributes than other entity objects in its object subgroup, thereby highlighting key nodes that constitute the association relationships between object subgroups and clearly presenting the association paths between groups in the object group relationship diagram.

[0068] Furthermore, the embodiments of this application can also be applied to scenarios with different business types. After determining the business type of the current application, at least two subgroup relationship types for this object group relationship diagram are further determined, so that the display of group relationships can adapt to different scenarios and meet the needs of different object relationship presentation in different scenarios.

[0069] Corresponding to the examples and method embodiments provided in this application, this application also provides a display device for a group of objects. For example... Figure 8 The diagram shown is a structural block diagram of a display device 800 for a group of objects according to an embodiment of this application. The device 800 may include:

[0070] The object data acquisition module 801 is used to acquire entity object data from at least one data source. The entity object data includes object identifiers of multiple entity objects and object relationship description information describing the relationships between the multiple entity objects. The relationship graph construction module 802 is used to construct an object group relationship graph corresponding to the object group based on the object relationship description information between the entity objects. The subgroup identification module 803 is used to identify object subgroups corresponding to at least two subgroup relationship types from the object group relationship graph according to the connection relationships between the entity objects in the object group relationship graph. The first display attribute update module 804 is used to update the display attributes of entity objects in the object subgroup according to the display style corresponding to the subgroup relationship type of the object subgroup. The display attribute output module 805 is used to output the updated display attributes of entity objects in the object subgroup to the canvas loading end to display the object group relationship graph of multiple objects on the canvas.

[0071] In one embodiment, the relationship graph construction module is specifically used to: extract object relationship description information of two entity objects from the entity object data based on the object identifiers of any two entity objects; generate a connection relationship between the two entity objects based on at least one object relationship description information extracted from the two entity objects; and create an object group relationship graph corresponding to the object group based on the connection relationship between the two entity objects.

[0072] In one embodiment, the subgroup identification module is specifically used to: find the number of relational nodes that are connected to a single node in the object group relationship graph; find other nodes associated with the single node starting from the single node; use the maximum number of connection relationships between the single node and another other node as the link level of the single node; and determine the subgroup relationship type of the object subgroup formed by the single node and other nodes based on the numerical comparison between the number of relational nodes and the link level.

[0073] In one embodiment, the display style corresponding to the subgroup relationship type includes the display style corresponding to the entity objects in the object subgroup; the first display attribute update module is specifically used to search for entity objects of various object types in the object subgroup according to the object types of various entity objects corresponding to the subgroup relationship type; and update the display attributes of entity objects in the object subgroup according to the display style corresponding to the object type of the entity object.

[0074] In one embodiment, the apparatus further includes: a common entity object identification module, used to identify common entity objects belonging to multiple non-hierarchical object subgroups; and a second display attribute update module, used to update the display attributes of the common entity object and at least some other entity objects in its object subgroup according to the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, wherein the updated common entity object has different display attributes from the other entity objects in its object subgroup.

[0075] In one embodiment, the second display attribute update module includes: a count identification submodule, used to identify the number of object subgroups whose subgroup relationship type is not hierarchical among the plurality of object subgroups; a central entity object search submodule, used to search for the central entity object that is commonly connected to the plurality of entity objects in the non-hierarchical object subgroups; a common entity object identification submodule, used to identify the common entity object belonging to the plurality of non-hierarchical object subgroups; and a position coordinate determination submodule, used to redetermine the position coordinates of the common entity object and at least some other entity objects in the object subgroup to which it belongs, based on the position coordinates of the plurality of central entity objects in the object group relationship graph.

[0076] In one embodiment, the position coordinate determination submodule is specifically used to redetermine the coordinate position of the common entity object based on the position coordinates of multiple central entity objects in the object group relationship diagram; and to redetermine the position coordinates of at least some other entity objects in the object subgroup based on the length relationship between the first type of connection between the common entity object and the central entity object and the second type of connection between other entity objects in the object subgroup and the central entity object.

[0077] In one embodiment, the apparatus further includes: a non-group entity object lookup module, configured to find non-group entity objects among the multiple entity objects that do not belong to the object subgroup before the updated display attributes of entity objects in the object subgroup are output to the canvas loading end, so as to display the object group relationship graph of multiple objects on the canvas, and update the display attributes of the non-group entity objects according to the distance between the non-group entity objects and the subgroup of objects.

[0078] In one embodiment, the apparatus further includes: a business type determination module, configured to determine a business type corresponding to the object group after obtaining entity object data from at least one data source; and a relationship type determination module, configured to determine at least two subgroup relationship types for the current object group relationship diagram based on the business type.

[0079] The functions of each module in each device in the embodiments of this application can be found in the corresponding description in the above method, and they have corresponding beneficial effects, which will not be repeated here.

[0080] According to the embodiments of this application, entity object data including object identifiers of multiple entity objects and object relationship description information describing the association between multiple entity objects is obtained from at least one data source. Further, an object group relationship diagram corresponding to the object group is constructed based on the object relationship description information. According to the connection relationship between entity objects in the object group relationship diagram, object subgroups corresponding to at least two subgroup relationship types are identified from the object group relationship diagram. This is so that the display attributes of entity objects in the object subgroups are updated according to the display style corresponding to the subgroup relationship type of the object subgroups. After the updated display attributes of entity objects in the object subgroups are output to the canvas loading end, the object group relationship diagram of multiple objects is displayed on the canvas. Therefore, the solution of this application identifies entity objects and their relationships within the data. By distinguishing at least two identified object subgroups with corresponding display styles, different object subgroups exhibit different display effects on the canvas. This allows for the intuitive presentation of different object subgroups while displaying the entity objects and relationships within a large amount of data. The differentiation and display of these subgroups clarifies the visual presentation of complex data, reduces complexity, highlights different object subgroups, and improves readability. Especially when dealing with massive amounts of data and a large number of entity objects, the segmented display of subgroups efficiently and clearly shows the relationships between entity objects, providing strong support for users to further analyze object relationships and improving analysis efficiency.

[0081] This application embodiment can also determine entity objects of different object types from the object subgroup based on the object types of multiple entity objects corresponding to the subgroup relationship type, and then update the display attributes of entity objects in the object subgroup according to the display style corresponding to the object type of the entity object, so that entity objects of different object types present different display effects, intuitively highlighting entity objects of different object types and other types of entity objects associated with each object type entity object.

[0082] Furthermore, embodiments of this application can also identify common entity objects belonging to multiple non-hierarchical object subgroups. Further, based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, the display attributes of the common entity object and at least some other entity objects in its object subgroup are updated. This ensures that the updated common entity object corresponds to different display attributes than other entity objects in its object subgroup, thereby highlighting key nodes that constitute the association relationships between object subgroups and clearly presenting the association paths between groups in the object group relationship diagram.

[0083] Furthermore, the embodiments of this application can also be applied to scenarios with different business types. After determining the business type of the current application, at least two subgroup relationship types for this object group relationship diagram are further determined, so that the display of group relationships can adapt to different scenarios and meet the needs of different object relationship presentation in different scenarios.

[0084] Figure 9 This is a block diagram of an electronic device used to implement embodiments of this application. For example... Figure 9 As shown, the electronic device includes a memory 901 and a processor 902. The memory 901 stores a computer program that can run on the processor 902. When the processor 902 executes the computer program, it implements the method described in the above embodiments. The number of memories 901 and processors 902 can be one or more.

[0085] The electronic device also includes:

[0086] The communication interface 903 is used to communicate with external devices and exchange and transmit data.

[0087] If the memory 901, processor 902, and communication interface 903 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0088] Optionally, in a specific implementation, if the memory 901, processor 902, and communication interface 903 are integrated on a single chip, then the memory 901, processor 902, and communication interface 903 can communicate with each other through an internal interface.

[0089] This application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in this application.

[0090] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the methods provided in any embodiment of this application.

[0091] This application also provides a chip including a processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform the method provided in this application.

[0092] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in this application.

[0093] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture.

[0094] Further, optionally, the aforementioned memory may include read-only memory and random access memory. The memory may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available. Examples include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0095] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0096] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0097] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0098] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.

[0099] The logic and / or steps described in the flowchart or otherwise herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0100] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware, the program being stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiments.

[0101] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0102] The above description is merely an exemplary embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope described in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for displaying a group of objects, wherein, include: Entity object data is obtained from at least one data source, wherein the entity object data includes object identifiers of multiple entity objects and object relationship description information used to describe the association relationships between the multiple entity objects; Construct an object group relationship diagram corresponding to the object group based on the object relationship description information between the entity objects; Based on the connection relationships between entity objects in the object group relationship diagram, identify object subgroups corresponding to at least two subgroup relationship types from the object group relationship diagram; Update the display attributes of entity objects in the object subgroup according to the display style corresponding to the subgroup relationship type of the object subgroup; The updated display attributes of the entity objects in the object subgroup are output to the canvas loading end to display an object group relationship graph of multiple objects on the canvas.

2. The display method according to claim 1, wherein, The step of constructing an object group relationship diagram corresponding to the object group based on the object relationship description information between the entity objects includes: Based on the object identifiers of any two entity objects, extract the object relationship description information of the two entity objects from the entity object data; Based on at least one object relationship description information extracted from the two entity objects, a connection relationship between the two entity objects is generated; Create an object group relationship graph corresponding to the object group based on the connection relationship between each pair of entity objects.

3. The display method according to claim 1, wherein, The step of identifying object subgroups corresponding to at least two subgroup relationship types from the object group relationship graph based on the connection relationships between entity objects in the object group relationship graph includes: For an entity object that is a single node in the object group relationship graph, find the number of relational nodes that have a connection relationship with the single node; Starting from the single node, find other nodes associated with the single node, and use the maximum number of connections between the single node and another other node as the link level of the single node; Based on the numerical comparison between the number of relational nodes and the number of link levels, the subgroup relationship type of the object subgroup formed by the single node and other nodes is determined.

4. The display method according to claim 1, wherein, The display style corresponding to the subgroup relationship type includes the display style corresponding to the entity objects in the object subgroup; The step of updating the display attributes of entity objects in the object subgroup according to the display style corresponding to the subgroup relationship type of the object subgroup includes: Based on the object types of various entity objects corresponding to the subgroup relationship type, find entity objects of various object types from the object subgroup; Update the display attributes of entity objects in the object subgroup according to the display style corresponding to the object type of the entity object.

5. The display method according to claim 1, wherein, The method further includes: Identify common entity objects belonging to multiple non-hierarchical object subgroups; Based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, update the display attributes of the common entity object and at least some other entity objects in its object subgroup. The updated common entity object corresponds to different display attributes than other entity objects in its object subgroup.

6. The display method according to claim 5, wherein, The step of updating the display attributes of the common entity object and at least some other entity objects in its subgroups, based on the display style of the multiple non-hierarchical object subgroups to which the common entity object belongs in the object group relationship diagram, includes: Identify the number of object subgroups whose subgroup relationship type is not hierarchical among the multiple object subgroups; Find the central entity object that is commonly connected to multiple entity objects within the non-hierarchical object subgroup; Identify common entity objects belonging to multiple non-hierarchical object subgroups; Based on the position coordinates of multiple central entity objects in the object group relationship diagram, the position coordinates of the common entity object and at least some other entity objects in its subgroup are re-determined.

7. The display method according to claim 6, wherein, The step of re-determining the position coordinates of the common entity object and at least some other entity objects in its subgroup based on the position coordinates of multiple central entity objects in the object group relationship graph includes: Based on the position coordinates of multiple central entity objects in the object group relationship diagram, the coordinate position of the common entity object is re-determined; Based on the length relationship between the first type of connection between the shared entity object and the central entity object and the second type of connection between other entity objects in the object subgroup and the central entity object, the position coordinates of at least some other entity objects in the object subgroup are recalculated.

8. The display method according to claim 1, wherein, Before outputting the updated display attributes of entity objects in the object subgroup to the canvas loading end to display the object group relationship graph of multiple objects on the canvas, the method further includes: Find non-group entity objects among the multiple entity objects that do not belong to the object subgroup, and update the display attributes of the non-group entity objects according to the distance between the non-group entity objects and the subgroup of objects.

9. The display method according to claim 1, wherein, After obtaining entity object data from at least one data source, the method further includes: Determine the business type corresponding to the object group, and determine at least two subgroup relationship types for this object group relationship diagram based on the business type.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory, wherein the processor, when executing the computer program, implements the method of any one of claims 1-9.

11. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of any one of claims 1-9.

12. A computer program product, wherein, The computer program product includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-9.

Images