Trusted data operation management system based on microservice architecture

Abstract

The present invention provides a trusted data operations management system based on a microservices architecture, comprising: an alliance establishment module, which responds to alliance applications sent by operating enterprises corresponding to multiple demand nodes on a blockchain to establish an enterprise alliance, and generates enterprise display areas corresponding to each operating enterprise in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data; a target determination module, which responds to an employee terminal belonging to any operating enterprise performing regional interaction with the enterprise display areas of other operating enterprises, determines the display sub-area selected based on the regional interaction as the target sub-area, and determines the regional attributes of the corresponding target sub-area based on the access permissions of the corresponding employee terminal; and a data retrieval module, which responds to the regional attribute being a retrieval attribute and sends a retrieval connector corresponding to the target sub-area to the employee terminal, so that the employee terminal receives the hierarchical data of the corresponding target sub-area based on the retrieval connector. The present invention at least enables data sharing between enterprises.

Description

Technical Field

[0001] The present invention relates to data processing technology, and in particular to a trusted data operation and management system based on a microservice architecture. Background Art

[0002] With the continuous development of information technology, every operating enterprise has accumulated massive amounts of data, including customer information, production data, market trends, etc.; these data contain huge value. If they can be shared among multiple enterprises, it will help enterprises better understand market demand, optimize production processes, and reduce costs.

[0003] In the past, enterprise data exchange often relied on file transfers and direct database connections. Structured or unstructured data files were transferred between businesses via USB drives and other methods. However, this approach has significant drawbacks, including poor timeliness in file transfers. The massive amounts of data transferred are not only time-consuming but also lack a real-time update mechanism, making it difficult for businesses to quickly respond to market trends. While direct database connections enable real-time data exchange, they pose serious security risks. Different enterprise databases have varying permission management standards, and direct connections can lead to sensitive data leaks and increase the risk of data tampering.

[0004] Therefore, there is an urgent need for a trusted data operation and management system based on a microservice architecture that can realize data sharing between enterprise data. Summary of the Invention

[0005] Based on the above problems, the present invention is proposed to provide a trusted data operation and management system based on a microservice architecture that overcomes the above problems or at least partially solves the above problems.

[0006] According to one aspect of the present invention, a trusted data operation and management system based on a microservice architecture is provided, comprising:

[0007] an alliance establishment module configured to respond to alliance applications sent by operating enterprises corresponding to multiple demand nodes of the blockchain to establish an enterprise alliance, and generate an enterprise display area corresponding to each operating enterprise in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data;

[0008] a target determination module configured to, in response to an employee terminal belonging to any operating enterprise performing a regional interaction on an enterprise display area of ​​another operating enterprise, determine a display sub-area selected based on the regional interaction as a target sub-area, and determine a regional attribute corresponding to the target sub-area based on the access permission corresponding to the employee terminal;

[0009] The data retrieval module is configured to send a retrieval connector corresponding to the target sub-region to the employee terminal in response to the region attribute being a retrieval attribute, so that the employee terminal receives the hierarchical data corresponding to the target sub-region based on the retrieval connector.

[0010] Optionally, in the system according to the present invention, an enterprise display area corresponding to each operating enterprise is generated in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data, including:

[0011] In response to determining that there is shared data based on the enterprise data corresponding to each operating enterprise, obtaining a shared percentage of the enterprise data corresponding to the shared data;

[0012] The retrieved initial area size is updated based on the shared proportion, and an enterprise display area corresponding to each operating enterprise is generated based on the obtained current area size;

[0013] Overlap the areas of all enterprise display areas corresponding to the same shared data according to the shared proportions to obtain independent areas and shared areas corresponding to the same enterprise display area;

[0014] The data difference set between the enterprise data and the shared data is determined as independent data, and the independent area and the shared area are divided based on the independent data and the shared data to obtain display sub-areas corresponding to different hierarchical data.

[0015] Optionally, in the system according to the present invention, the alliance establishment module further comprises: obtaining an independent outline corresponding to each independent area, a common outline corresponding to each common area, and configuring different preset pixel values ​​for each enterprise display area;

[0016] Rendering the independent outlines based on the preset pixel values, and aggregating the preset pixel values ​​of all enterprise display areas corresponding to the same common area into a common rendering group;

[0017] The common contour is alternately rendered based on each predetermined pixel value in the common rendering group.

[0018] Optionally, in the system according to the present invention, in response to determining that common data exists based on the enterprise data corresponding to each operating enterprise, obtaining a common ratio of the common data to the enterprise data includes:

[0019] Divide the enterprise data corresponding to each operating enterprise into hierarchical groups, and perform data comparison based on each obtained data structure tree, wherein the data structure tree includes hierarchical nodes corresponding to different hierarchical levels;

[0020] In response to determining that the same level node exists in different data structure trees based on the comparison results, the level node and all level nodes below the level node are determined as common data;

[0021] Determine the data structure tree containing the common data as an association structure tree, and determine the number of nodes of all levels included in the common data and the total number of nodes of all levels included in the association structure tree;

[0022] The ratio of the number of nodes to the total number of nodes is calculated to obtain the proportion of the shared data corresponding to the enterprise data.

[0023] Optionally, in the system according to the present invention, the independent area and the shared area are divided based on the independent data and the shared data to obtain display sub-areas corresponding to different hierarchical data, including:

[0024] Establishing a division relationship between the independent data, shared data, independent areas, and shared areas;

[0025] Determining the independent data and the shared data as sorted data, and determining the independent area and the shared area as sorted areas;

[0026] Determine all hierarchical nodes corresponding to the same hierarchical level included in each sorted data as the same hierarchical data, and determine the number of levels corresponding to all hierarchical data;

[0027] The sorting area having a division relationship with the sorting data is divided into areas corresponding to the number of levels, and each level of data is filled into the obtained display sub-area.

[0028] Optionally, in the system according to the present invention, in response to an employee terminal belonging to any operating enterprise performing regional interaction on an enterprise display area of ​​another operating enterprise, determining a display sub-area selected based on the regional interaction as a target sub-area, and determining the regional attributes corresponding to the target sub-area based on the access permission corresponding to the employee terminal, including:

[0029] Determine the regional pixels constituting each display sub-region;

[0030] In response to an employee terminal belonging to any operating enterprise moving a selection indicator to any regional pixel point, a display sub-region including the regional pixel point is determined as a preview sub-region, and a data directory formed based on the hierarchical data of the corresponding preview sub-region is sent to the employee terminal;

[0031] Determine the pixel point in the region as the starting pixel point, obtain the point distance between the starting pixel point and all remaining regional pixel points constituting the preview sub-region, and determine the regional pixel point corresponding to the point distance as the ending pixel point;

[0032] In response to the employee terminal moving the selection indicator from the starting pixel point to the ending pixel point along the selection determination line formed by the starting pixel point and the ending pixel point, determining whether the operating enterprise corresponding to the enterprise display area including the preview sub-area is the same as the operating enterprise to which the employee terminal belongs;

[0033] When it is determined that they are the same, the graded data corresponding to the preview sub-area is sent to the employee terminal;

[0034] If they are determined to be different, the preview sub-area is determined as the target sub-area, and the area attribute corresponding to the target sub-area is determined based on the access authority corresponding to the employee terminal.

[0035] Optionally, in the system according to the present invention, determining the area attribute corresponding to the target sub-area based on the access permission corresponding to the employee terminal includes:

[0036] Determining access permissions corresponding to the employee terminal based on the retrieved employee connector corresponding to the employee terminal;

[0037] In response to the retrieval permission having a permission adaptation relationship with the hierarchical level of the hierarchical data of the corresponding target sub-region, the employee connector corresponding to the employee terminal is determined as the retrieval connector, and the regional attribute of the corresponding target sub-region is determined as the retrieval attribute. Otherwise, the retrieval log corresponding to the operating enterprise to which the employee terminal belongs is obtained;

[0038] Determining other employee terminals having a first retrieval record of the hierarchical data as collaborative terminals based on the retrieval log;

[0039] In response to receiving the collaboration request sent by the collaboration end based on the employee end, the collaboration connector corresponding to the collaboration end is determined as a calling connector, and the area attribute corresponding to the target sub-area is determined as a calling attribute, otherwise it is determined as a prohibition attribute.

[0040] Optionally, in the system according to the present invention, the call connector is a cooperative connector;

[0041] Sending a call connector corresponding to the target sub-area to the employee terminal, so that the employee terminal receives the graded data corresponding to the target sub-area based on the call connector, and then further comprising:

[0042] In response to the employee terminal receiving the hierarchical data corresponding to the target sub-area based on the retrieving connector, generating a second retrieving record corresponding to the employee terminal and the hierarchical data based on the retrieving log;

[0043] In response to the number of records corresponding to all second retrieval records being greater than a preset number, the retrieval authority corresponding to the employee terminal is updated to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data.

[0044] Optionally, in the system according to the present invention, in response to the number of records corresponding to all second retrieval records being greater than a preset number, updating the retrieval permission corresponding to the employee terminal to have a permission adaptation relationship with the hierarchical level corresponding to the hierarchical data includes:

[0045] Establishing a scheduled task corresponding to a preset continuous retrieval duration on the employee side, and determining, based on the scheduled task, a number of first records corresponding to all second retrieval records generated in the retrieval log within the preset retrieval duration;

[0046] In response to the number of the first records being greater than or equal to a preset first number, updating the access permission corresponding to the employee terminal to have a permission adaptation relationship with the hierarchical level corresponding to the hierarchical data;

[0047] In response to the first record quantity being less than a preset first quantity, determining a second record quantity corresponding to all second retrieval records generated in the retrieval log;

[0048] In response to the second record quantity being greater than or equal to a preset second quantity, the access authority corresponding to the employee terminal is updated to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data.

[0049] Optionally, the system according to the present invention further comprises:

[0050] Identify enterprise data corresponding to island characteristics of different operating enterprises as island data, and establish island areas connected to enterprise display areas corresponding to the same operating enterprise based on each island data;

[0051] In response to the employee side belonging to any operating enterprise performing regional interaction with the island area of ​​other operating enterprises, the island difficulty value of the corresponding island data and the island approval chain consisting of multiple approval nodes corresponding to the number of island approvals are determined;

[0052] Sending a call connector corresponding to the island area to the employee terminal, and obtaining an island receiving time corresponding to the employee terminal receiving the island data based on the call connector;

[0053] Creating a difficulty comparison coordinate system, wherein the difficulty comparison coordinate system includes an X-axis corresponding to different preset difficulty values, a Y-axis corresponding to different preset approval numbers, and a Z-axis corresponding to a preset receipt time;

[0054] Determine an island coordinate point located in the comparison coordinate system based on the island difficulty value, the number of island approvals, and the island reception time, and generate an island identifier based on the island coordinate point and the coordinate origin of the corresponding difficulty comparison coordinate system;

[0055] In response to the island volume corresponding to the island identifier being greater than the retrieved preset volume, the difficult comparison coordinate system including the island identifier is sent to the management end.

[0056] According to the solution of the present invention, first, the alliance establishment module establishes an enterprise alliance space based on the alliance application of multiple operating enterprises, and generates an enterprise display area for each operating enterprise containing different hierarchical data display sub-areas. On the one hand, each operating enterprise can display each hierarchical data it owns in the enterprise alliance space, so that the enterprise data can be presented in a systematic way; on the other hand, the enterprise data of different operating enterprises are displayed in a unified enterprise alliance space, breaking down the data barriers between enterprises and laying the foundation for data interaction and cooperation between enterprises; secondly, the target determination module responds to the regional interaction of the employee end belonging to any operating enterprise with the enterprise display area of ​​other operating enterprises, determines the display sub-area selected based on the interaction as the target sub-area, and determines the regional attributes of the target sub-area according to the employee end's access authority, thereby realizing precise positioning and authority control in the data interaction process. The employee end can accurately select the required target sub-area by performing interactive operations in the enterprise display area corresponding to other operating enterprises, avoiding blind searches in a large amount of data, and providing It improves the efficiency of data acquisition. At the same time, it determines the regional attributes of the target sub-area in combination with the retrieval permissions of the employee side, ensuring the security and standardization of data interaction. That is, only employees with corresponding retrieval permissions can perform related operations such as retrieval attributes on the target sub-area. This effectively prevents unauthorized data access and operation, ensures the security of enterprise data, and meets the strict requirements for permission control in data operation management. Finally, when the regional attribute of the target sub-area is the retrieval attribute, the data retrieval module sends the corresponding retrieval connector to the employee side, so that the employee side can receive the hierarchical data of the target sub-area based on the retrieval connector, thereby realizing safe and efficient data retrieval. The retrieval connector serves as a bridge for data transmission, providing a reliable channel for data transmission, ensuring that the hierarchical data can be accurately transmitted from the target sub-area to the employee side. On the premise of ensuring data security, it realizes the circulation and sharing of data between enterprises, enabling each operating enterprise to make full use of the relevant data of other enterprises in the alliance, and provide strong data support for the enterprise's decision-making, business expansion, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 The following is a structural diagram of a trusted data operation and management system based on a microservice architecture according to an embodiment of the present invention;

[0058] Figure 2 is a schematic diagram of the enterprise alliance space in this embodiment;

[0059] Figure 3 A flowchart of a trusted data operation management method based on a microservice architecture according to another embodiment of the present invention is shown. DETAILED DESCRIPTION

[0060] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0061] In order to solve the problems existing in the above-mentioned prior art, the inventors propose the solution of the present invention. One embodiment of the present invention provides a trusted data operation and management system based on a microservice architecture. Figure 1 The structural block diagram of the corresponding system is shown in FIG. Figure 1 As shown, the system includes: an alliance establishment module, a target determination module and a data retrieval module.

[0062] The following is a corresponding introduction to the various modules included in the system proposed in this embodiment:

[0063] As for the alliance establishment module, this module is mainly configured to respond to alliance applications sent by operating enterprises corresponding to multiple demand nodes of the blockchain to establish enterprise alliances, and generate enterprise display areas corresponding to each operating enterprise in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data.

[0064] For example, an operating enterprise can be understood as an enterprise that operates based on a business model, and its corresponding operating scope may include but is not limited to finance, IT, construction, etc.; it can be explained that, since in the normal operation process, multiple operating enterprises may establish corresponding cooperative relationships based on the same enterprise project, and in order to improve the corresponding cooperation efficiency, the system mentioned in this embodiment can be used to allow employees of each operating enterprise to retrieve and view the data of other operating enterprises; and in order to achieve the above purpose, an enterprise alliance can be established in response to the alliance application sent by the operating enterprises corresponding to the multiple demand nodes based on the blockchain, that is, the multiple operating enterprises with cooperative relationships can jointly send the corresponding alliance application to the corresponding party. The alliance establishment module of the system enables the establishment of an enterprise alliance space corresponding to the alliance application, and further generates an enterprise display area corresponding to each operating enterprise in the enterprise alliance space. It can be explained that the corresponding enterprise alliance space can visually display each operating enterprise with a cooperative relationship, and further, each enterprise display area can also include display sub-areas corresponding to different hierarchical data. Here, the hierarchical data is obtained by hierarchically processing the enterprise data of the corresponding operating enterprise. Each hierarchical data corresponds to a different hierarchical level, and different hierarchical levels require different retrieval permissions to retrieve and view the corresponding hierarchical data. The hierarchical data can specifically include corresponding R&D data, etc.

[0065] Furthermore, in this embodiment, the aforementioned "generating an enterprise display area corresponding to each operating enterprise in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data" may further include:

[0066] In response to determining that there is shared data based on the enterprise data corresponding to each operating enterprise, obtaining a shared percentage of the enterprise data corresponding to the shared data;

[0067] The retrieved initial area size is updated based on the shared proportion, and an enterprise display area corresponding to each operating enterprise is generated based on the obtained current area size;

[0068] Overlap the areas of all enterprise display areas corresponding to the same shared data according to the shared proportions to obtain independent areas and shared areas corresponding to the same enterprise display area;

[0069] The data difference set between the enterprise data and the shared data is determined as independent data, and the independent area and the shared area are divided based on the independent data and the shared data to obtain display sub-areas corresponding to different hierarchical data.

[0070] For example, in this embodiment, the generation of the enterprise display area can be implemented based on the following technical solutions:

[0071] First, when the alliance establishment module analyzes the enterprise data of each operating enterprise and determines the existence of shared data, it can obtain the shared proportion of the shared data in the corresponding enterprise data, providing a quantitative basis for subsequent regional division, so that regional generation is directly linked to the actual data sharing situation. It can be explained that shared data can be understood as data jointly owned by at least two operating enterprises, such as data with the same intellectual property rights;

[0072] Next, the pre-retrieved initial area size is updated based on the obtained shared proportion, and a company display area corresponding to each operating company is generated based on the updated current area size. It can be explained that the initial area size can be set by the system administrator, and the initial area size is dynamically adjusted based on the shared proportion, so that the size of the company display area can intuitively reflect the degree of shared company data between the operating company and other operating companies.

[0073] Subsequently, all enterprise display areas corresponding to the same shared data are overlapped according to the shared proportion, thereby obtaining independent areas and shared areas within the same enterprise display area. Here, by overlapping areas based on the shared proportion, the shared data and independent data of the corresponding enterprise data can be spatially divided in a visual form. In other words, the shared area can intuitively present the data intersection between different operating enterprises, while the independent area clearly displays the data unique to each operating enterprise, making it possible to quickly distinguish data types through regional form and improve information recognition;

[0074] Finally, the difference between the enterprise data and the shared data can be determined as independent data, and the independent area and the shared area can be divided based on the independent data and the shared data, and finally the display sub-areas corresponding to the different hierarchical data are obtained. Here, by defining the independent data by the data difference and dividing the enterprise display area in combination with the shared data, each display sub-area obtained can correspond to different hierarchical data, forming a clearly hierarchical data display structure. It can be explained that independent data can be understood as data in which each operating enterprise independently owns a certain intellectual property right.

[0075] For example, Figure 2 This is a schematic diagram of the enterprise alliance space in this embodiment, based on Figure 2 From the content, we can see that the enterprise alliance space includes enterprise display areas corresponding to the three operating enterprises. Among them, operating enterprises A and B have a shared area, while operating enterprise C only has an independent area. It can be seen that due to the existence of the shared area, the current area sizes of the enterprise display areas corresponding to operating enterprises A and B are both larger than the current area size of operating enterprise C.

[0076] Here, based on the above content, it can be understood that shared data can be understood as data jointly owned by at least two operating companies, such as data with the same intellectual property rights, while independent data can be understood as data in which each operating company independently owns a certain intellectual property right. Shared data can be filled into the shared area, while independent data can be filled into the independent area. In order to distinguish the independent area from the shared area based on a visual form, in this embodiment, the above-mentioned alliance establishment module further includes:

[0077] Obtain the independent outline corresponding to each independent area and the shared outline corresponding to each shared area, and configure different preset pixel values ​​for each enterprise display area;

[0078] Rendering the independent outlines based on the preset pixel values, and aggregating the preset pixel values ​​of all enterprise display areas corresponding to the same common area into a common rendering group;

[0079] The common contour is alternately rendered based on each predetermined pixel value in the common rendering group.

[0080] For example, in this embodiment, the distinction between independent areas and shared areas can be achieved based on the following technical solutions:

[0081] First, the alliance establishment module obtains the independent outline of each independent area and the shared outline of each shared area, and configures different preset pixel values ​​for each enterprise display area. This means that by obtaining the outlines corresponding to different areas, the spatial boundaries between independent and shared data can be accurately defined. Furthermore, by configuring differentiated preset pixel values, the enterprise display areas corresponding to different operating companies can be distinguished through visual features in subsequent processes, avoiding confusion about data sources and improving the initial recognition of data interaction.

[0082] Next, the alliance establishment module can render independent outlines based on the determined preset pixel values, so that independent areas can be identified based on the preset pixel values. At the same time, the preset pixel values ​​of all enterprise display areas in the same shared area can be aggregated into a shared rendering group, providing a data set for unified visual processing of the shared area, ensuring that all preset pixel values ​​related to the same shared data are centrally managed, so that the shared area can be visually connected as a whole, making it easier to identify the scope of the shared data between different operating enterprises;

[0083] Finally, the alliance establishment module can alternately render the shared contour based on each preset pixel value in the shared rendering group, that is, the shared area will be periodically visually switched (such as alternating colors) with the preset pixel values ​​corresponding to different business enterprises, so as to significantly highlight the shared area, help intuitively perceive which data are shared by different business enterprises, and can quickly understand the participation status of different business enterprises in the shared data through the corresponding relationship of alternating pixel values; for example, when two business enterprises A and B have the same shared area, and the preset pixel value of business enterprise A corresponds to red, and the preset pixel value of business enterprise B corresponds to blue, at this time, the independent contour of the independent area of ​​business enterprise A is rendered red, and the independent contour of the independent area of ​​business enterprise B is rendered blue, and the shared contour of the corresponding shared area will be rendered alternately based on red and blue.

[0084] Furthermore, in this embodiment, the above-mentioned "determining the existence of shared data based on the enterprise data corresponding to each operating enterprise, and obtaining the shared proportion of the enterprise data corresponding to the shared data" may also include:

[0085] Divide the enterprise data corresponding to each operating enterprise into hierarchical groups, and perform data comparison based on each obtained data structure tree, wherein the data structure tree includes hierarchical nodes corresponding to different hierarchical levels;

[0086] In response to determining that the same level node exists in different data structure trees based on the comparison results, the level node and all level nodes below the level node are determined as common data;

[0087] Determine the data structure tree containing the common data as an association structure tree, and determine the number of nodes of all levels included in the common data and the total number of nodes of all levels included in the association structure tree;

[0088] The ratio of the number of nodes to the total number of nodes is calculated to obtain the proportion of the shared data corresponding to the enterprise data.

[0089] For example, in this embodiment, the determination of the shared proportion of shared data can be achieved based on the following technical solutions:

[0090] First, after obtaining the enterprise data of each operating enterprise, hierarchical division can be performed based on the enterprise data to form a data structure tree containing hierarchical nodes at different hierarchical levels;

[0091] Then, data comparison is performed based on these data structure trees. If, based on the comparison results, it is determined that the same level node exists in different data structure trees, then this level node and all level nodes below it are collectively determined as shared data, so as to fully capture the shared parts of the corresponding enterprise data between different operating enterprises, and include not only directly matching level nodes, but also all level nodes derived from them at the lower level, to avoid missing related shared data due to only considering a single level node, and ensure the comprehensiveness of the definition of shared data;

[0092] Next, the data structure tree containing the common data may be determined as an association structure tree, and the number of nodes of all levels of nodes included in the common data and the total number of nodes of all levels of nodes included in the association structure tree may be determined respectively;

[0093] Finally, the ratio of the number of nodes of shared data to the total number of nodes in the associated structure tree is calculated to obtain the shared proportion of enterprise data corresponding to the shared data, thereby converting the degree of shared enterprise data between different operating enterprises into a specific proportion value. The shared proportion can intuitively reflect the degree of shared enterprise data between a certain operating enterprise and the corresponding enterprise data of other operating enterprises. It can be explained that the higher the shared proportion, the higher the degree of shared data between the operating enterprise and other operating enterprises.

[0094] In addition, in this embodiment, the above-mentioned "dividing the independent area and the shared area based on the independent data and the shared data to obtain display sub-areas corresponding to different hierarchical data" may also include

[0095] Establishing a division relationship between the independent data, shared data, independent areas, and shared areas;

[0096] Determining the independent data and the shared data as sorted data, and determining the independent area and the shared area as sorted areas;

[0097] Determine all hierarchical nodes corresponding to the same hierarchical level included in each sorted data as the same hierarchical data, and determine the number of levels corresponding to all hierarchical data;

[0098] The sorting area having a division relationship with the sorting data is divided into areas corresponding to the number of levels, and each level of data is filled into the obtained display sub-area.

[0099] For example, in this embodiment, the division of independent areas and shared areas can be achieved based on the following technical solutions:

[0100] First, the alliance establishment module can establish the division relationship between independent data, shared data, independent areas, and shared areas to clearly map different data to different areas. This ensures that each type of data (independent data or shared data) has a corresponding physical display space in the enterprise display area, ensuring that the data type matches the area type.

[0101] Next, the independent data and the shared data are uniformly determined as the sorted data, and the independent areas and the shared areas are determined as the sorted areas. Furthermore, all the hierarchical nodes corresponding to the same hierarchical level in each sorted data are further determined as the same hierarchical data, and the number of levels of all the hierarchical data is determined.

[0102] Finally, the alliance establishment module can divide the sorting areas that have a division relationship with the sorting data into areas corresponding to the hierarchical number, that is, divide the independent areas into areas corresponding to the hierarchical number of independent data, and divide the shared areas into areas corresponding to the hierarchical number of shared data, that is, by dividing the areas proportionally or adaptively based on the hierarchical number, so that the physical space of each display sub-area and the logical level of the corresponding hierarchical data form an intuitive mapping, completing the regional division of independent areas and shared areas, and further filling each hierarchical data into the different display sub-areas obtained, so that the corresponding hierarchical data can be retrieved and viewed based on different display sub-areas in the future.

[0103] As for the target determination module, this module is mainly configured to respond to the employee terminal belonging to any operating enterprise to conduct regional interaction with the corporate display area of ​​other operating enterprises, determine the display sub-area selected based on the regional interaction as the target sub-area, and determine the regional attributes corresponding to the target sub-area based on the access authority corresponding to the employee terminal.

[0104] For example, in this embodiment, based on the above content, it can be seen that the establishment of the enterprise alliance space mainly allows employees corresponding to each operating enterprise to retrieve and view the data of other operating enterprises. Therefore, when the employee terminal belonging to any operating enterprise is determined to conduct regional interaction with the enterprise display area of ​​other operating enterprises based on the target determination module, it indicates that the employee using the employee terminal wants to retrieve and view the corresponding data. At this time, the target determination module can further determine the display sub-area selected by the employee terminal based on the regional interaction to determine it as the target sub-area, and obtain the retrieval authority of the corresponding employee terminal, and determine the area attributes of the corresponding target sub-area based on the retrieval authority; it can be explained that the employee terminal can be understood as a terminal with data processing function, display function, communication function, etc., such as a mobile phone or computer, and the corresponding retrieval authority can be determined based on the rank of each employee. It can be explained that the retrieval authority corresponding to the general manager rank should be greater than the retrieval authority corresponding to the team leader rank.

[0105] Furthermore, in this embodiment, the aforementioned "responding to an employee terminal belonging to any operating enterprise performing regional interaction with an enterprise display area of ​​another operating enterprise, determining a display sub-area selected based on the regional interaction as a target sub-area, and determining the regional attributes corresponding to the target sub-area based on the access permission corresponding to the employee terminal" may further include:

[0106] Determine the regional pixels constituting each display sub-region;

[0107] In response to an employee terminal belonging to any operating enterprise moving a selection indicator to any regional pixel point, a display sub-region including the regional pixel point is determined as a preview sub-region, and a data directory formed based on the hierarchical data of the corresponding preview sub-region is sent to the employee terminal;

[0108] Determine the pixel point in the region as the starting pixel point, obtain the point distances between the starting pixel point and all remaining pixel points in the region constituting the preview sub-region, and determine the pixel point in the region with the largest corresponding point distance as the ending pixel point;

[0109] In response to the employee terminal moving the selection indicator from the starting pixel point along the selection determination line formed by the starting pixel point and the ending pixel point to the ending pixel point, determining whether the operating enterprise corresponding to the enterprise display area including the preview sub-area is the same as the operating enterprise to which the employee terminal belongs;

[0110] When it is determined that they are the same, the graded data corresponding to the preview sub-area is sent to the employee terminal;

[0111] If they are determined to be different, the preview sub-area is determined as the target sub-area, and the area attribute corresponding to the target sub-area is determined based on the access authority corresponding to the employee terminal.

[0112] For example, in this embodiment, the determination of the regional attributes of the target sub-region determined based on the regional interaction of employees can be implemented based on the following technical solutions:

[0113] First, since the display sub-areas are displayed in the enterprise alliance space, the target determination module can determine the regional pixels constituting each display sub-area based on the enterprise alliance space;

[0114] Next, when an employee terminal belonging to a certain operating enterprise moves the selection indicator to any pixel point in the area, the target determination module will determine the display sub-area containing the pixel point as the preview sub-area, and form a data directory based on the hierarchical data of the preview sub-area and send it to the employee terminal, so that the employee using the employee terminal can first understand the data overview of the target sub-area through the data directory before officially selecting the hierarchical data, avoiding data retrieval errors caused by blind selection. At the same time, the pre-display of the data directory can help employees quickly determine whether the hierarchical data meets their own needs, reduce invalid data interaction operations, and improve data interaction efficiency. It can be explained that the selection indicator can be understood as a digital symbol displayed on the employee terminal for employee interaction, which can be moved accordingly under the control of the employee. When the employee terminal is a computer, the selection indicator can be, for example, a mouse cursor;

[0115] Afterwards, the target determination module may determine the pixel point of the area where the employee terminal initially moves as the starting pixel point, obtain the point distances between the starting pixel point and all remaining pixel points constituting the preview sub-area, determine the pixel point with the largest corresponding point distance as the ending pixel point, and thereby form a selection determination line connecting the starting pixel point and the ending pixel point;

[0116] Finally, after completing the generation of the selection determination line, if it is identified that the employee side moves the selection indicator from the starting pixel point along the selection determination line formed by the two to the ending pixel point, it can indicate that the employee using the employee side has determined that the hierarchical data needs to be retrieved and viewed. At this time, the target determination module will determine whether the operating enterprise corresponding to the enterprise display area containing the preview sub-area is the same as the operating enterprise to which the employee side belongs; if they are the same, the hierarchical data of the corresponding preview sub-area can be directly sent to the employee side; if they are different, the preview sub-area needs to be determined as the target sub-area, and its area attributes are determined based on the retrieval authority of the employee side. It can be explained that differentiated processing based on enterprise affiliation can achieve convenient internal and external data interaction distinction, that is, for hierarchical data belonging to the same operating enterprise, direct retrieval is allowed, thereby improving the efficiency of internal data interaction within the enterprise; and for hierarchical data across enterprises, it is necessary to enter the corresponding authority verification process to ensure security and authority controllability when sharing data across enterprises, effectively prevent unauthorized access and leakage of data, and ensure data security.

[0117] Furthermore, in this embodiment, the above-mentioned “determining the area attribute corresponding to the target sub-area based on the access permission corresponding to the employee terminal” may also include:

[0118] Determining access permissions corresponding to the employee terminal based on the retrieved employee connector corresponding to the employee terminal;

[0119] In response to the retrieval permission having a permission adaptation relationship with the hierarchical level of the hierarchical data of the corresponding target sub-region, the employee connector corresponding to the employee terminal is determined as the retrieval connector, and the regional attribute of the corresponding target sub-region is determined as the retrieval attribute. Otherwise, the retrieval log corresponding to the operating enterprise to which the employee terminal belongs is obtained;

[0120] Determining other employee terminals having a first retrieval record of the hierarchical data as collaborative terminals based on the retrieval log;

[0121] In response to receiving the collaboration request sent by the collaboration end based on the employee end, the collaboration connector corresponding to the collaboration end is determined as a calling connector, and the area attribute corresponding to the target sub-area is determined as a calling attribute, otherwise it is determined as a prohibition attribute.

[0122] For example, in this embodiment, determining the regional attributes of the target sub-region based on the access authority of the employee terminal can be specifically implemented based on the following technical solutions:

[0123] First, the target determination module can determine the access permissions of the employee end based on the employee connector corresponding to the employee end. It can be explained that the employee connector can be understood as a corresponding access plug-in, which can be generated based on the access permissions of the employee end. In other words, the access permissions can be used to limit the data access scope of the employee connector. By determining the access permissions of the corresponding employee connector in real time, it can ensure that permissions are checked before each data interaction, preventing unauthorized personnel from illegally accessing cross-enterprise data.

[0124] Among them, if the retrieval authority has a permission adaptation relationship with the hierarchical level of the hierarchical data of the corresponding target sub-area, it means that the employee end can directly retrieve and view the selected hierarchical data based on its corresponding employee connector. In this case, the target determination module can determine the employee connector corresponding to the employee end as the retrieval connector, and mark the regional attribute of the target sub-area as "retrieval attribute"; otherwise, the retrieval log corresponding to the operating enterprise to which the employee end belongs is obtained. It can be explained that based on the above method, the efficiency of data retrieval during permission adaptation is guaranteed, and the corresponding coordination mechanism can be executed through the retrieval log when the permissions do not match, avoiding the complete blocking of data sharing due to permission barriers, and balancing security and sharing needs.

[0125] Next, the target determination module can perform content traversal based on the obtained retrieval log. When it is determined that the retrieval log records the first retrieval record for retrieving the hierarchical data, the other employee terminals that retrieve and view the hierarchical data can be determined based on the first retrieval record, and further determined as the corresponding collaborative terminals. It can be explained that since the first retrieval record is stored in the retrieval log, it can form an interactive credential that has passed the historical permission verification, indicating that other employees using the collaborative terminal have the permission qualifications to access the hierarchical data. Determining the collaborative terminal based on the first retrieval record can ensure the legitimacy of the permissions of the collaborative object.

[0126] Finally, the employee side can request the collaborative side to collaboratively retrieve the corresponding hierarchical data. The request method may include offline or online forms, etc., which are not limited in this embodiment. When the collaborative side agrees to collaboratively retrieve the employee side, the collaborative side can correspondingly send a collaborative request to the target determination module included in this embodiment. After receiving the collaborative request, the target determination module can retrieve the collaborative connector corresponding to the collaborative side and determine it as the retrieval connector, so that in the subsequent process, the employee side can retrieve and view the corresponding hierarchical data based on the retrieval connector, and at the same time, the regional attribute of the target sub-area can be determined as "retrieval attribute". If the target determination module does not receive the collaborative request, it means that the collaborative side does not agree to collaboratively retrieve the employee side. In this case, the regional attribute of the target sub-area can be synchronously determined as "prohibited attribute". Based on this, in this embodiment, through the permission transfer of the collaborative side, employees without direct permission are allowed to obtain data in the collaborative scenario, which not only meets the actual business needs of cross-enterprise data sharing, but also ensures the controllability of permission transfer through two-way verification of collaborative requests to prevent permission abuse.

[0127] As for the data retrieval module, the module is mainly configured to respond to the area attribute being a retrieval attribute, and send the retrieval connector corresponding to the target sub-area to the employee end, so that the employee end receives the hierarchical data corresponding to the target sub-area based on the retrieval connector.

[0128] For example, in this embodiment, when it is determined that the area attribute of the target sub-area is a retrieval attribute, it indicates that the corresponding employee end can retrieve and view the hierarchical data of the corresponding target sub-area. At this time, the data retrieval module can send the retrieval connector of the corresponding target sub-area to the employee end, so that the employee end can establish a retrieval channel with the hierarchical data of the corresponding target sub-area through the retrieval connector, thereby obtaining the corresponding hierarchical data for viewing; it can be explained that, based on the above content, the retrieval connector can be understood as a corresponding retrieval plug-in, which can be deployed on the employee end after being sent to the employee end.

[0129] In addition, in this embodiment, based on the above content, it can be seen that when the retrieval authority of the corresponding employee terminal does not have a permission adaptation relationship with the hierarchical level of the corresponding hierarchical data, it can determine other employee terminals with the first retrieval record of the hierarchical data as collaborative terminals based on the retrieval log, and determine the collaborative connector of the corresponding collaborative terminal as the corresponding retrieval connector, so as to use the collaborative connector as a relay station to assist the employee terminal in obtaining the corresponding hierarchical data. If the employee terminal obtains the hierarchical data multiple times through the collaborative connector, in order to improve its acquisition efficiency, in this embodiment, the above-mentioned "sending the retrieval connector corresponding to the target sub-area to the employee terminal, so that the employee terminal receives the hierarchical data corresponding to the target sub-area based on the retrieval connector" can also include:

[0130] In response to the employee terminal receiving the hierarchical data corresponding to the target sub-area based on the retrieving connector, generating a second retrieving record corresponding to the employee terminal and the hierarchical data based on the retrieving log;

[0131] In response to the number of records corresponding to all second retrieval records being greater than a preset number, the retrieval authority corresponding to the employee terminal is updated to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data.

[0132] For example, in this embodiment, in order to improve the acquisition efficiency of the corresponding employee side, the employee side's access permissions can be updated accordingly based on the actual situation of the employee side obtaining hierarchical data through the collaborative connector. The corresponding technical solution can be implemented based on the following:

[0133] First, after the data retrieval module sends the retrieval connector corresponding to the target sub-region (that is, the collaborative connector corresponding to the collaborative end) to the employee end, the employee end can receive the hierarchical data of the target sub-region based on the retrieval connector. At the same time, the data retrieval module generates a second retrieval record corresponding to the hierarchical data on the employee end based on the retrieval log. Here, the generation of the second retrieval record can track the actual use of cross-enterprise data by employees in real time, improving the traceability of data operations.

[0134] Secondly, since the employee can retrieve and view the hierarchical data multiple times, there may be multiple second retrieval records in the retrieval log. To improve the retrieval efficiency, the number of records corresponding to all second retrieval records can be simultaneously determined, and the number of records retrieved can be compared with the preset number of retrievals.

[0135] Finally, when the number of all second retrieval records exceeds the preset number, it means that the employee terminal retrieves and views the hierarchical data more frequently. Therefore, the data retrieval module will update the retrieval authority of the employee terminal to have a permission adaptation relationship with the hierarchical level of the hierarchical data, that is, automatically enhance its retrieval authority. Subsequently, the employee terminal does not need to use the collaborative connector as a relay station, and can complete the direct retrieval and viewing of the hierarchical data based on its own employee connector, avoiding employees repeatedly initiating retrieval requests through the collaborative terminal, reducing the process loss of cross-enterprise data interaction, and improving data sharing efficiency.

[0136] Furthermore, in this embodiment, the above-mentioned "in response to the number of records corresponding to all second retrieval records being greater than a preset number, updating the retrieval authority corresponding to the employee terminal to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data" may further include the following steps:

[0137] Establishing a scheduled task corresponding to a preset continuous retrieval duration on the employee side, and determining, based on the scheduled task, a number of first records corresponding to all second retrieval records generated in the retrieval log within the preset retrieval duration;

[0138] In response to the number of the first records being greater than or equal to a preset first number, updating the access permission corresponding to the employee terminal to have a permission adaptation relationship with the hierarchical level corresponding to the hierarchical data;

[0139] In response to the first record quantity being less than a preset first quantity, determining a second record quantity corresponding to all second retrieval records generated in the retrieval log;

[0140] In response to the second record quantity being greater than or equal to a preset second quantity, the access authority corresponding to the employee terminal is updated to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data.

[0141] For example, in this embodiment, updating the access permission of the employee terminal based on the number of records retrieved by the second adjustment can be implemented based on the following technical solutions:

[0142] First, the data retrieval module can establish a scheduled task for the employee side with a preset retrieval duration, and based on this scheduled task, count the number of first records of all second retrieval records generated in the retrieval log within the preset retrieval duration. Here, the preset retrieval duration can correspond to one week or one month. By setting a scheduled task, employees' retrieval behavior of graded data within a specific time period can be periodically monitored;

[0143] Next, the first retrieved record obtained can be compared with the preset first number of retrieved records. If, based on the comparison result, it is determined that the number of first records is greater than or equal to the preset first number, it indicates that the employee has a regular demand for the hierarchical data in a short period of time. At this time, the data retrieval module can directly update the employee's retrieval authority to be compatible with the hierarchical level of the hierarchical data, that is, complete the automatic upgrade of the retrieval authority, thereby eliminating the need to repeatedly retrieve data through the collaborative end and improving the efficiency of cross-enterprise data interaction.

[0144] If, based on the comparison result, it is determined that the number of first records is less than the preset first number, this indicates that the employee terminal has a low frequency of retrieving the hierarchical data in a short period of time. However, it can be shown that the long-term cumulative retrieval behavior can still reflect the necessity of the employee terminal to use the hierarchical data. Therefore, the data retrieval module can further count the second record number of all second retrieval records in the retrieval log (i.e., the historical cumulative number of retrievals of the hierarchical data by the employee terminal), and compare the second record number with the preset second number of retrievals. It can be shown that the preset second number should be greater than the preset first number.

[0145] Finally, when the number of second records is greater than or equal to the preset second number, the data retrieval module can also directly update the retrieval permissions on the employee side to match the hierarchical level of the hierarchical data, ensuring that permission management can respond to both short-term interaction needs and long-term interaction needs. On the premise of ensuring data security, it can realize intelligent and adaptive adjustment of cross-enterprise data sharing permissions, reduce manual permission configuration costs, and improve the flexibility of multi-enterprise data operations.

[0146] To sum up, firstly, the alliance establishment module establishes an enterprise alliance space based on the alliance application of multiple operating enterprises, and generates an enterprise display area for each operating enterprise containing different hierarchical data display sub-areas. On the one hand, each operating enterprise can display each hierarchical data it owns in the enterprise alliance space, so that the enterprise data can be presented in a systematic way; on the other hand, the enterprise data of different operating enterprises are displayed in a unified enterprise alliance space, breaking down the data barriers between enterprises and laying the foundation for data interaction and cooperation between enterprises; secondly, the target determination module responds to the regional interaction of the employee end belonging to any operating enterprise with the enterprise display area of ​​other operating enterprises, determines the display sub-area selected based on the interaction as the target sub-area, and determines the regional attributes of the target sub-area according to the employee end's access authority, thereby realizing precise positioning and authority control in the data interaction process. The employee end can accurately select the required target sub-area by performing interactive operations in the enterprise display area corresponding to other operating enterprises, avoiding blind searches in large amounts of data, and improving The efficiency of data acquisition is improved. At the same time, the regional attributes of the target sub-area are determined in combination with the retrieval permissions of the employee side, ensuring the security and standardization of data interaction. That is, only employees with corresponding retrieval permissions can perform related operations such as retrieval attributes on the target sub-area. This effectively prevents unauthorized data access and operation, ensures the security of enterprise data, and meets the strict requirements for permission control in data operation management; finally, when the regional attribute of the target sub-area is a retrieval attribute, the data retrieval module sends the corresponding retrieval connector to the employee side, so that the employee side can receive the hierarchical data of the target sub-area based on the retrieval connector, thereby realizing safe and efficient data retrieval. The retrieval connector serves as a bridge for data transmission, providing a reliable channel for data transmission, ensuring that the hierarchical data can be accurately transmitted from the target sub-area to the employee side. On the premise of ensuring data security, the circulation and sharing of data between enterprises is realized, so that each operating enterprise can make full use of the relevant data of other enterprises in the alliance, and provide strong data support for the enterprise's decision-making, business expansion, etc.

[0147] In addition, based on the above content, it can be seen that this embodiment can help share data between different operating enterprises based on the generated enterprise alliance space. Specifically, the corresponding hierarchical data can be obtained based on the corresponding call connector. In some cases, certain operating enterprises may have corresponding data islands, that is, data is stored and maintained independently in different departments, and is isolated from each other, forming physical islands. In this case, it is difficult to obtain the corresponding enterprise data with data islands. The difficulty mainly comes from the format settings, encryption settings, or unique permission approval settings of different departments for enterprise data. In order to optimize the data acquisition method mentioned in this embodiment based on the existence of data islands and improve its data acquisition efficiency, this embodiment can further include the following content:

[0148] Identify enterprise data corresponding to island characteristics of different operating enterprises as island data, and establish island areas connected to enterprise display areas corresponding to the same operating enterprise based on each island data;

[0149] In response to the employee side belonging to any operating enterprise performing regional interaction with the island area of ​​other operating enterprises, the island difficulty value of the corresponding island data and the island approval chain consisting of multiple approval nodes corresponding to the number of island approvals are determined;

[0150] Sending a call connector corresponding to the island area to the employee terminal, and obtaining an island receiving time corresponding to the employee terminal receiving the island data based on the call connector;

[0151] Creating a difficulty comparison coordinate system, wherein the difficulty comparison coordinate system includes an X-axis corresponding to different preset difficulty values, a Y-axis corresponding to different preset approval numbers, and a Z-axis corresponding to a preset receipt time;

[0152] Determine an island coordinate point located in the comparison coordinate system based on the island difficulty value, the number of island approvals, and the island reception time, and generate an island identifier based on the island coordinate point and the coordinate origin of the corresponding difficulty comparison coordinate system;

[0153] In response to the island volume corresponding to the island identifier being greater than the retrieved preset volume, the difficult comparison coordinate system including the island identifier is sent to the management end.

[0154] For example, in this embodiment, in an application scenario where multiple operating enterprises share data, in order to quantify and visualize the sharing barriers of data silos between enterprises, this embodiment can be based on the following specific content:

[0155] First, the server identifies the isolated data corresponding to different operating enterprises (i.e., enterprise data independently owned by each enterprise, not shared with other enterprises, and corresponding to the island characteristics). Based on each isolated data, it establishes an isolated region connected to the enterprise display area of ​​the corresponding operating enterprise. The "connection relationship" here refers to the visual mapping of the isolated region with the enterprise display area in the enterprise alliance space, directly linking the physical location of the isolated data with the enterprise data architecture. In this way, the "island" state of data isolation between enterprises can be transformed into a visual regional form, helping employees intuitively identify the boundaries of data sharing, providing a spatial positioning foundation for subsequent cross-enterprise data interaction, and effectively solving the problem of data silos being difficult to visualize.

[0156] Next, similar to the aforementioned technical solution, when an employee of a particular operating enterprise interacts with (e.g., clicks or selects) an island area of ​​another enterprise, the server also needs to determine the regional attributes of the corresponding island area based on the employee's access permissions. Furthermore, when the corresponding regional attribute is an access attribute, the server determines an "island difficulty value" for the corresponding enterprise data, as well as an island approval chain consisting of multiple approval nodes corresponding to the "number of island approvals." It can be noted that the island difficulty value can be calculated based on factors such as data format differences and access barriers, reflecting the difficulty of cross-enterprise data access. Since the circumstances of each operating enterprise vary, the island difficulty value can be manually determined for each operating enterprise. The method for determining this value is not specifically limited in this embodiment. For example, a rough assessment can be performed based on the circumstances of different operating enterprises to improve the efficiency of data determination. After determining the island difficulty value, each operating enterprise can upload the data to the server. Similarly, the number of island approvals represents the complexity of the approval process required to access the data, thereby making implicit barriers to data sharing explicit through quantitative indicators.

[0157] Next, the service area can send the retrieval connector corresponding to the island area to the employee end, and obtain the "island reception time" (i.e., the time from initiating the retrieval to completing the data reception) for the employee end to receive the island data based on the retrieval connector. At the same time, a difficulty comparison coordinate system is created: it is necessary to construct a three-dimensional coordinate system with different preset difficulty values ​​as the X-axis, different preset approval numbers as the Y-axis, and the preset reception time as the Z-axis. By integrating the reception time as a real-time efficiency indicator, combining the difficulty value and the approval number, the obstacles to data sharing are converted into quantifiable three-dimensional coordinate parameters. This gives the originally abstract sharing efficiency problem a visual analysis dimension, facilitating subsequent multi-dimensional comparison and trend analysis.

[0158] Finally, the server can determine the island coordinate point in the comparison coordinate system based on the obtained island difficulty value, the number of island approvals and the island reception time, and generate an "island identifier" (such as a three-dimensional graphic such as a cube, the volume of which is determined by the comprehensive parameters of each dimension) based on the spatial relationship between the point and the coordinate origin. If the volume of the island identifier is larger than the preset volume, it means that the sharing barrier of the island data has exceeded the threshold. The difficulty comparison coordinate system containing the identifier will be sent to the management end for subsequent data optimization or process optimization, helping the management end to intuitively judge the severity of the data island through the volume of the three-dimensional graphic - the larger the volume, the higher the sharing difficulty and the lower the efficiency, so as to optimize the data architecture or approval process in a targeted manner (for example, modifying the format settings, encryption settings or streamlining the permission approval settings), realize the automatic identification and management intervention of data sharing barriers, and improve the overall efficiency and smoothness of multi-enterprise data sharing.

[0159] Figure 3 A flowchart of a trusted data operation management method based on a microservice architecture according to an embodiment of the present invention is shown. The method is suitable for execution in a computing device, wherein the computing device can be understood as a terminal with data processing capabilities, such as a mobile phone or a computer.

[0160] like Figure 3 As shown, the method includes the following steps:

[0161] Responding to alliance applications sent by operating enterprises corresponding to multiple demand nodes of the blockchain to establish an enterprise alliance, and generating an enterprise display area corresponding to each operating enterprise in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data;

[0162] In response to an employee terminal belonging to any operating enterprise performing regional interaction on an enterprise display area of ​​another operating enterprise, determining a display sub-area selected based on the regional interaction as a target sub-area, and determining a regional attribute corresponding to the target sub-area based on the access permission corresponding to the employee terminal;

[0163] In response to the area attribute being a call attribute, a call connector corresponding to the target sub-area is sent to the employee terminal, so that the employee terminal receives the hierarchical data corresponding to the target sub-area based on the call connector.

[0164] In the description provided herein, the algorithms and displays are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems may also be used in conjunction with the examples of the present invention. Based on the above description, it is apparent that the structure required for constructing such systems is well understood. In addition, the present invention is not directed to any specific programming language. It should be understood that various programming languages ​​may be utilized to implement the present invention described herein, and the description of specific languages ​​above is provided for the purpose of disclosing preferred embodiments of the present invention.

[0165] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.

[0166] Similarly, it should be understood that in order to streamline the disclosure and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or description thereof.

[0167] Those skilled in the art will appreciate that the modules, units, or components of the devices in the examples disclosed herein may be arranged in the device described in the embodiment, or alternatively may be located in one or more devices different from the devices in the examples. The modules in the foregoing examples may be combined into one module or further divided into multiple submodules.

[0168] Those skilled in the art will appreciate that the modules in the devices of the embodiments can be adaptively changed and installed in one or more devices different from the embodiments. The modules, units, or components in the embodiments can be combined into one module, unit, or component, and furthermore, they can be divided into multiple submodules, subunits, or subcomponents.

[0169] Furthermore, those skilled in the art will appreciate that although some embodiments described herein include certain features and not other features included in other embodiments, the combination of features from different embodiments is intended to be within the scope of the invention and to form different embodiments.

[0170] In addition, some of the embodiments are described herein as methods or combinations of method elements that can be implemented by a processor of a computer system or by other devices that perform the functions described. Thus, a processor having the necessary instructions for implementing the method or method element forms a device for implementing the method or method element. Furthermore, the elements described herein of the device embodiments are examples of devices for implementing the functions performed by the elements for the purpose of implementing the invention.

[0171] As used herein, unless otherwise specified, the use of ordinal numbers "first," "second," "third," etc. to describe common objects merely indicates that different instances of similar objects are involved and are not intended to imply that the objects so described must have a given order in time, space, ranking, or in any other manner.

[0172] Although the present invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the foregoing description, will appreciate that other embodiments are contemplated within the scope of the invention thus described. Furthermore, it should be noted that the language used in this specification has been selected primarily for readability and instructional purposes and is not selected to explain or limit the subject matter of the present invention.

Claims

1. A trusted data operation and management system based on microservice architecture, characterized in that: include: an alliance establishment module configured to respond to alliance applications sent by operating enterprises corresponding to multiple demand nodes of the blockchain to establish an enterprise alliance, and generate an enterprise display area corresponding to each operating enterprise in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data; a target determination module configured to, in response to an employee terminal belonging to any operating enterprise performing a regional interaction on an enterprise display area of ​​another operating enterprise, determine a display sub-area selected based on the regional interaction as a target sub-area, and determine a regional attribute corresponding to the target sub-area based on the access permission corresponding to the employee terminal; a data retrieval module configured to, in response to the region attribute being a retrieval attribute, send a retrieval connector corresponding to the target sub-region to the employee terminal, so that the employee terminal receives the hierarchical data corresponding to the target sub-region based on the retrieval connector; An enterprise display area corresponding to each operating enterprise is generated in the enterprise alliance space, wherein each enterprise display area includes display sub-areas corresponding to different hierarchical data, including: In response to determining that there is shared data based on the enterprise data corresponding to each operating enterprise, obtaining a shared percentage of the enterprise data corresponding to the shared data; The retrieved initial area size is updated based on the shared proportion, and an enterprise display area corresponding to each operating enterprise is generated based on the obtained current area size; Overlap the areas of all enterprise display areas corresponding to the same shared data according to the shared proportions to obtain independent areas and shared areas corresponding to the same enterprise display area; Determine the data difference set between the enterprise data and the shared data as independent data, and divide the independent area and the shared area into regions based on the independent data and the shared data to obtain display sub-regions corresponding to different hierarchical data; In response to determining that shared data exists based on the enterprise data corresponding to each operating enterprise, obtaining a shared percentage of the shared data corresponding to the enterprise data includes: Divide the enterprise data corresponding to each operating enterprise into hierarchical groups, and perform data comparison based on each obtained data structure tree, wherein the data structure tree includes hierarchical nodes corresponding to different hierarchical levels; In response to determining that the same level node exists in different data structure trees based on the comparison results, the level node and all level nodes below the level node are determined as common data; Determine the data structure tree containing the common data as an association structure tree, and determine the number of nodes of all levels included in the common data and the total number of nodes of all levels included in the association structure tree; The ratio of the number of nodes to the total number of nodes is calculated to obtain the proportion of the shared data corresponding to the enterprise data.

2. The trusted data operation and management system based on microservice architecture according to claim 1 is characterized in that: The alliance building module also includes: Obtain the independent outline corresponding to each independent area and the shared outline corresponding to each shared area, and configure different preset pixel values ​​for each enterprise display area; Rendering the independent outlines based on the preset pixel values, and aggregating the preset pixel values ​​of all enterprise display areas corresponding to the same common area into a common rendering group; The common contour is alternately rendered based on each predetermined pixel value in the common rendering group.

3. The trusted data operation and management system based on microservice architecture according to claim 1 is characterized in that: Based on the independent data and the shared data, the independent area and the shared area are divided into regions to obtain display sub-areas corresponding to different hierarchical data, including: Establishing a division relationship between the independent data, shared data, independent areas, and shared areas; Determining the independent data and the shared data as sorted data, and determining the independent area and the shared area as sorted areas; Determine all hierarchical nodes corresponding to the same hierarchical level included in each sorted data as the same hierarchical data, and determine the number of levels corresponding to all hierarchical data; The sorting area having a division relationship with the sorting data is divided into areas corresponding to the number of levels, and each level of data is filled into the obtained display sub-area.

4. The trusted data operation and management system based on microservice architecture according to claim 1, characterized in that: In response to an employee terminal belonging to any operating enterprise performing regional interaction on an enterprise display area of ​​another operating enterprise, a display sub-area selected based on the regional interaction is determined as a target sub-area, and a regional attribute corresponding to the target sub-area is determined based on the access permission corresponding to the employee terminal, including: Determine the regional pixels constituting each display sub-region; In response to an employee terminal belonging to any operating enterprise moving a selection indicator to any regional pixel point, a display sub-region including the regional pixel point is determined as a preview sub-region, and a data directory formed based on the hierarchical data of the corresponding preview sub-region is sent to the employee terminal; Determine the pixel point in the region as the starting pixel point, obtain the point distance between the starting pixel point and all remaining regional pixel points constituting the preview sub-region, and determine the regional pixel point corresponding to the point distance as the ending pixel point; In response to the employee terminal moving the selection indicator from the starting pixel point along the selection determination line formed by the starting pixel point and the ending pixel point to the ending pixel point, determining whether the operating enterprise corresponding to the enterprise display area including the preview sub-area is the same as the operating enterprise to which the employee terminal belongs; When it is determined that they are the same, the graded data corresponding to the preview sub-area is sent to the employee terminal; If they are determined to be different, the preview sub-area is determined as the target sub-area, and the area attribute corresponding to the target sub-area is determined based on the access authority corresponding to the employee terminal.

5. The trusted data operation and management system based on microservice architecture according to claim 4 is characterized in that: Determining the area attribute corresponding to the target sub-area based on the access permission corresponding to the employee terminal includes: Determining access permissions corresponding to the employee terminal based on the retrieved employee connector corresponding to the employee terminal; In response to the retrieval permission having a permission adaptation relationship with the hierarchical level of the hierarchical data of the corresponding target sub-region, the employee connector corresponding to the employee terminal is determined as the retrieval connector, and the regional attribute of the corresponding target sub-region is determined as the retrieval attribute. Otherwise, the retrieval log corresponding to the operating enterprise to which the employee terminal belongs is obtained; Determining other employee terminals having a first retrieval record of the hierarchical data as collaborative terminals based on the retrieval log; In response to receiving the collaboration request sent by the collaboration end based on the employee end, the collaboration connector corresponding to the collaboration end is determined as a calling connector, and the area attribute corresponding to the target sub-area is determined as a calling attribute, otherwise it is determined as a prohibition attribute.

6. The trusted data operation and management system based on microservice architecture according to claim 5 is characterized in that: The calling connector is a cooperative connector; Sending a call connector corresponding to the target sub-area to the employee terminal, so that the employee terminal receives the graded data corresponding to the target sub-area based on the call connector, and then further comprising: In response to the employee terminal receiving the hierarchical data corresponding to the target sub-area based on the retrieving connector, generating a second retrieving record corresponding to the employee terminal and the hierarchical data based on the retrieving log; In response to the number of records corresponding to all second retrieval records being greater than a preset number, the retrieval authority corresponding to the employee terminal is updated to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data.

7. The trusted data operation and management system based on microservice architecture according to claim 6 is characterized in that: In response to the number of records corresponding to all second retrieved records being greater than a preset number, updating the retrieval authority corresponding to the employee terminal to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data, including: Establishing a scheduled task corresponding to a preset continuous retrieval duration on the employee side, and determining, based on the scheduled task, a number of first records corresponding to all second retrieval records generated in the retrieval log within the preset retrieval duration; In response to the number of the first records being greater than or equal to a preset first number, updating the access permission corresponding to the employee terminal to have a permission adaptation relationship with the hierarchical level corresponding to the hierarchical data; In response to the first record quantity being less than a preset first quantity, determining a second record quantity corresponding to all second retrieval records generated in the retrieval log; In response to the second record quantity being greater than or equal to a preset second quantity, the access authority corresponding to the employee terminal is updated to have an authority adaptation relationship with the hierarchical level corresponding to the hierarchical data.

8. The trusted data operation and management system based on microservice architecture according to claim 1, characterized in that: Also includes: Identify enterprise data corresponding to island characteristics of different operating enterprises as island data, and establish island areas connected to enterprise display areas corresponding to the same operating enterprise based on each island data; In response to the employee side belonging to any operating enterprise performing regional interaction with the island area of ​​other operating enterprises, the island difficulty value of the corresponding island data and the island approval chain consisting of multiple approval nodes corresponding to the number of island approvals are determined; Sending a call connector corresponding to the island area to the employee terminal, and obtaining an island receiving time corresponding to the employee terminal receiving the island data based on the call connector; Creating a difficulty comparison coordinate system, wherein the difficulty comparison coordinate system includes an X-axis corresponding to different preset difficulty values, a Y-axis corresponding to different preset approval numbers, and a Z-axis corresponding to a preset receipt time; Determine an island coordinate point located in a comparison coordinate system based on the island difficulty value, the number of island approvals, and the island reception time, and generate an island identifier based on the island coordinate point and the coordinate origin of the corresponding difficulty comparison coordinate system; In response to the island volume corresponding to the island identifier being greater than the retrieved preset volume, the difficult comparison coordinate system including the island identifier is sent to the management end.

Images