Multi-domain multi-level data feedback method and device

Abstract

The invention relates to the technical field of data processing, and discloses a multi-domain multi-level data feedback method and device. The method comprises the steps of confirming data request information needing to be fed back; according to the data request information, establishing a binding relationship between the multi-level through data block and the reverse feedback link block; and obtaining request data needing to be fed back according to the binding relationship. According to the method, the data request information is confirmed, and the binding relationship between the multi-stage through data block and the reverse feedback link block is established, so that the accurate matching of the data composition form and the stack path is realized, the data feedback range is defined, the controllability of the data flow direction is ensured, and the data security and reliability are improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a multi-domain, multi-level data feedback method and apparatus. Background Technology

[0002] In the process of digital transformation of the group enterprise, the reverse data feedback between the unified cloud application system and the remote heterogeneous systems of subordinate institutes, factories and factories faces severe challenges.

[0003] The relevant technologies cannot accurately identify the data content, receiving unit, and boundary range that need to be fed back, resulting in redundant information or unnecessary exposure of sensitive data during the data return process, which affects the efficiency and security of data flow. Summary of the Invention

[0004] This application provides a multi-domain, multi-level data feedback method and apparatus, which can identify the data content and boundary range to be fed back, avoid redundant information or unnecessary exposure of sensitive data during the data feedback process, and improve the efficiency and security of data flow.

[0005] In a first aspect, this application provides a multi-domain, multi-level data feedback method, comprising: confirming the data request information that needs to be fed back; establishing a binding relationship between a multi-level interconnected data block and a reverse feedback link block based on the data request information, wherein the multi-level interconnected data block is used to characterize the data structure, and the reverse feedback link block is used to provide a stack path; and obtaining the request data that needs to be fed back based on the binding relationship.

[0006] In an optional implementation, this application further proposes that the data request information includes organizational levels, including group level, institute level, and factory level; the multi-level interconnected data block includes a binary tree composed of interconnected data domains and interconnected organizational domains, with different levels of binary trees corresponding to different organizational levels, wherein the interconnected organizational domain is used to represent the data routing path; the reverse feedback link block includes a data stack corresponding to the organizational level, and request data of different organizational levels are transmitted through different data stack paths; and a binding relationship is established between the multi-level interconnected data block and the reverse feedback link block according to the data request information, including: determining the data stack path corresponding to the organizational level in the multi-level interconnected data block according to the organizational level, wherein the data stack path is used to represent the flow direction of data at different organizational levels.

[0007] In one optional implementation, this application also proposes to determine the data stack path corresponding to the organization level in the multi-level interconnected data block according to the organization level, including: when the organization level is group level, the data stack path is from the cloud system to the group level receiving stack; when the organization level is institute level, the data stack path is from the group level output stack to the institute level receiving stack; when the organization level is factory / institute level, the data stack path is from the group level output stack to the factory / institute level receiving stack, and / or from the institute level output stack to the factory / institute level receiving stack.

[0008] In an optional implementation, this application also proposes to obtain the request data that needs to be fed back based on the binding relationship, including: obtaining the request data that needs to be fed back and corresponds to the permissions of the organization level based on the data stack path.

[0009] In an optional implementation, this application also proposes establishing a binding relationship between a multi-level interconnected data block and a reverse feedback link block when the data request contains information in a multi-domain associated data block. This further includes establishing an association relationship between the multi-domain associated data block and the multi-level interconnected data block, wherein the association relationship is used to characterize the association between different categories of data at the same organizational level.

[0010] In an optional implementation, this application also proposes that the interconnected data domain includes the interconnected local domain and the interconnected related domain, and the multi-domain related data block includes the data set of the interconnected related domain in the multi-level interconnected data block; establishing the association relationship between the multi-domain related data block and the multi-level interconnected data block includes: associating the data in the multi-domain related data block that is associated with the interconnected local domain according to the organizational level.

[0011] In an optional implementation, this application also proposes to associate data in a multi-domain associated data block that is associated with the data that is connected to the same domain according to the organizational level, including: performing a set operation on the multi-level connected data block and the multi-domain associated data block based on the organizational level.

[0012] In an optional implementation, this application also proposes to establish an association relationship between multi-domain associated data blocks and multi-level interconnected data blocks, and then further includes: based on the interconnected organizational domain, routing data at different organizational levels to the corresponding organizational levels, and assigning data permissions to the corresponding organizational levels.

[0013] Secondly, this application provides a multi-domain, multi-level data feedback device, comprising: a confirmation module for confirming data request information that needs to be fed back; a binding module for establishing a binding relationship between a multi-level interconnected data block and a reverse feedback link block based on the data request information, wherein the multi-level interconnected data block is used to characterize the data structure and the reverse feedback link block is used to provide a stack path; and an acquisition module for acquiring the request data that needs to be fed back based on the binding relationship.

[0014] Thirdly, this application provides an electronic device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the multi-domain multi-level data feedback method described in the first aspect or any corresponding embodiment.

[0015] Fourthly, this application provides a computer-readable storage medium storing computer instructions for causing a computer to execute the multi-domain, multi-level data feedback method described in the first aspect or any corresponding embodiment thereof.

[0016] Fifthly, this application provides a computer program product, including computer instructions for causing a computer to execute the multi-domain, multi-level data feedback method described in the first aspect or any corresponding embodiment thereof. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the specific embodiments or related technologies of this application, the drawings used in the description of the specific embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating the multi-domain, multi-level data feedback method according to an embodiment of this application; Figure 2 This is a schematic diagram of the reverse feedback link block according to an embodiment of this application; Figure 3 This is a schematic diagram of a multi-level interconnected data block according to an embodiment of this application; Figure 4 This is a schematic diagram of a multi-domain associated data block according to an embodiment of this application; Figure 5 This is a schematic diagram of a multi-domain, multi-level data feedback process according to an embodiment of this application; Figure 6 This is a structural block diagram of a multi-domain, multi-level data feedback device according to an embodiment of this application; Figure 7 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] It is understood that before using the technical solutions disclosed in the various embodiments of this application, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this application in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0021] 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. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0022] This application proposes a multi-domain, multi-level data feedback method, such as... Figure 1 As shown, the method includes: Step S101: Confirm the data request information that needs to be fed back. Confirming the data request information is to clarify the specific content and target scope of the feedback.

[0023] Step S102: Based on the data request information, establish the binding relationship between the multi-level interconnected data block and the reverse feedback link block. The multi-level interconnected data block is used to characterize the data structure, and the reverse feedback link block is used to provide the stack path.

[0024] Among them, multi-level interconnected data blocks are used to describe the data organization structure and hierarchical data form, which is implemented through a tree structure, such as using a hierarchical directory structure to represent the composition of data, which is used to provide a logical framework for data to facilitate subsequent operations.

[0025] A reverse feedback link block is a data format used to specify a data transmission path. It is implemented through preset routing rules, protocol stacks, or network topology, such as a transmission path definition based on a protocol stack. Its main purpose is to ensure that data can flow to the target unit along the specified path.

[0026] Establishing a binding relationship between multi-level interconnected data blocks and reverse feedback link blocks is a process of dynamically associating the data organization form with the transmission path. Binding data blocks to paths is to achieve collaborative work between data structure and feedback paths.

[0027] Step S103: Obtain the request data that needs to be fed back based on the binding relationship.

[0028] This application achieves precise definition of the data feedback scope through three steps: confirming data request information, establishing binding relationships, and obtaining the requested data. By establishing binding relationships between multi-level interconnected data blocks and reverse feedback link blocks, it ensures that data flows only along the specified path to the target unit, thereby precisely controlling the feedback boundary; by obtaining the requested data based on the binding relationships, it guarantees the accuracy and relevance of the feedback content. Therefore, this application solves the problem of unclear feedback scope when data is reverse-followed to subordinate units in a group enterprise cloud system.

[0029] This application first clarifies the specific content and source of the data feedback by confirming the data request information, providing a foundation for subsequent operations. Further, based on the data request information, a binding relationship is established between multi-level interconnected data blocks and reverse feedback link blocks. The multi-level interconnected data blocks characterize the data's structure, defining its organization and hierarchy, while the reverse feedback link blocks provide the stack path, specifying the direction of data transmission. Thus, the binding relationship dynamically associates the data structure with the feedback path, ensuring that data flows only along the specified path to the target unit, thereby precisely controlling the feedback boundary. Specifically, establishing the binding relationship avoids data redundancy or unnecessary exposure caused by blind feedback. Finally, based on the established binding relationship, the requested data that needs to be fed back is obtained, ensuring the accuracy and relevance of the feedback content. For example, in a group enterprise cloud system, the technical solution in this application can effectively solve the problem of unclear feedback scope when data is reverse-followed to subordinate units, ensuring that data is accurately fed back to the corresponding organizational level. The three technical features mentioned above work together closely: the confirmation of data request information provides input for the establishment of binding relationships; the construction of binding relationships defines a precise path and scope for data acquisition; and data acquisition enables the implementation of feedback results, thus ensuring the accuracy and controllability of the data feedback process.

[0030] In some optional embodiments, the data request information includes organizational levels, including group level, institute level, and factory / institute level. The multi-level interconnected data block includes a binary tree composed of interconnected data domains and interconnected organizational domains. Different levels of the binary tree correspond to different organizational levels, where the interconnected organizational domain is used to characterize the data routing path. The reverse feedback link block includes a data stack corresponding to the organizational level, and request data from different organizational levels is transmitted through different data stack paths. Based on the data request information, a binding relationship is established between the multi-level interconnected data block and the reverse feedback link block, including: determining the data stack path corresponding to the organizational level in the multi-level interconnected data block, where the data stack path is used to characterize the flow direction of data at different organizational levels.

[0031] Organizational level refers to the basis for dividing the scope of data feedback within the enterprise's hierarchical architecture. It is implemented using a clear hierarchical structure such as group level, institute level, and factory level to accurately define the boundaries of data feedback and avoid data redundancy or exposure risks caused by ambiguous hierarchies. Multi-level interconnected data blocks are data structures used to represent the form of data composition. They are implemented using a binary tree structure composed of interconnected data domains and interconnected organizational domains. The interconnected organizational domains define the data routing path to ensure that the direction of data flow is consistent with the hierarchical logic. Reverse feedback link blocks are structures that provide stack paths. They are implemented using a data stack corresponding to the organizational level to isolate data flows at different levels and ensure that permissions remain stable during transmission. Data stack paths are specific paths used to represent the direction of data flow. They are dynamically selected according to the organizational level to ensure that the binding relationship closely matches the actual hierarchy, thereby clearly defining the feedback boundaries.

[0032] like Figure 2 As shown, the reverse feedback link block consists of a data stack. The data stack comprises output and receiving stacks at the group, institute, and factory / institute levels. The receiving stack contains the complete data set of the group's unified cloud system, while the output stack contains a subset of the data flowing back from the unified group's cloud system. The reverse feedback link block records the stack paths between the upper-level output stack and the lower-level input stack.

[0033] Depend on Figure 2 It is understood that the group-level system sets up data receiving and output stacks. Data from the unified cloud application system enters the receiving stack and then flows back to the heterogeneous application systems at the institute and factory levels via the output stack. The group-level reverse feedback link block records the data return stack paths at the institute and factory levels, and the necessary paths consist of the organizational domains at the institute and factory levels. The institute level sets up both data output and receiving stacks. Group-level data flows into the institute-level receiving stack and then through the output stack to the factory level. The institute-level reverse feedback link block records the data return stack paths at the factory level, and the necessary paths consist of the organizational domains at the factory level. The factory level only sets up a receiving stack. Group-level or institute-level data flows into the factory-level receiving stack.

[0034] like Figure 3 As shown, multi-level interconnected data blocks are the structural form of data flow in reverse feedback. A multi-level interconnected data block is a binary tree connecting (data domains) and (organizational domains), consisting of a root, branches, and leaves. The organizational domain records the necessary paths for data backflow. The root is the root node of the binary tree connecting the data domain and organizational domain, and the connection point between two leaves. Depending on the level, the root is divided into three categories: group-level, institute-level, and factory / institute-level. The group-level root is the root node of the entire group's data domain and organizational domain.

[0035] It is understood that the technical solution in this embodiment achieves precise definition of the data feedback scope through a deep integration of organizational level and data structure. First, the data request information explicitly includes the organizational level, enabling the system to identify the hierarchical attribute of the request source, providing a crucial basis for subsequent routing. Second, the multi-level interconnected data block adopts a binary tree structure composed of interconnected data domains and interconnected organizational domains. Different levels of the binary tree correspond to different organizational levels, and the routing definition of the interconnected organizational domain ensures the consistency of data flow direction with hierarchical logic. Based on this, the reverse feedback link block introduces a data stack corresponding to the organizational level. Request data from different organizational levels is transmitted through dedicated data stack paths, effectively isolating data flows at different levels and avoiding cross-level interference. Finally, the data stack path in the multi-level interconnected data block is confirmed according to the organizational level, ensuring that the binding relationship closely matches the actual hierarchy, thereby precisely controlling the data flow direction and eliminating range uncertainty. Through the above technical solution, the problem of ambiguous feedback boundaries is solved, ensuring that the data feedback scope is based on actual hierarchical requirements, while also guaranteeing the stability of permissions during transmission.

[0036] In some embodiments, this application further proposes a method for determining the data stack path corresponding to the organization level in a multi-level interconnected data block based on the organization level, including the following steps: Step a1: When the organization level is group level, the data stack path is from the (group-built) cloud system to the group-level receiving stack; Step a2: When the organization level is institute level, the data stack path is from the group level output stack to the institute level receiving stack. Step a3: When the organization level is factory / institute level, the data stack path is from the group-level output stack to the factory / institute level receiving stack, and / or from the institute-level output stack to the factory / institute level receiving stack.

[0037] Organizational level refers to the different hierarchical units within an enterprise according to management levels, including group level, institute level, or factory level, used to clarify the target scope of data feedback. Data stack path refers to the specific flow channel of data transmission in multi-level interconnected data blocks, implemented through predefined routing rules or stack structure, used to ensure that data can be transmitted accurately according to organizational level, avoiding feedback errors caused by unclear paths.

[0038] This application addresses the issue of ambiguous data feedback paths by defining specific data stack paths for different organizational levels. For the group level, the data stack path goes directly from the cloud system to the group-level receiving stack, precisely defining the feedback boundaries of group-level data and preventing data redundancy or exposure. For the institute level, the data stack path goes from the group-level output stack to the institute-level receiving stack, establishing a dedicated transmission channel to ensure data flows only through the designated path, effectively maintaining data and permission consistency. For the plant / institute level, a dual-path design is adopted, meaning the data stack path can go from the group-level output stack to the plant / institute-level receiving stack, or from the institute-level output stack to the plant / institute-level receiving stack. This dynamic selection mechanism adapts to business scenarios where plant / institute-level data may originate from different superior units, ensuring complete synchronization of cross-business domain related data. Furthermore, the above methods, combined with the binding relationship between multi-level interconnected data blocks and reverse feedback link blocks, further improve the accuracy and efficiency of data feedback, solving the technical problems of unclear reverse feedback scope, inconsistent permissions, and lack of correlation.

[0039] Through the above technical solutions, the embodiments of this application not only clarify the feedback path of data at each level, but also realize the accurate transmission of data between different organizational levels, while ensuring the consistency of data permissions and the integrity of related data, providing reliable technical support for data reverse feedback in enterprise digital transformation.

[0040] In some embodiments, this application further proposes obtaining the request data that needs to be fed back based on the binding relationship, including: obtaining the request data that needs to be fed back with the permissions corresponding to the organization level based on the data stack path.

[0041] The data stack path employs different levels of transmission links, such as group-level to institute-level and institute-level to factory / institute-level, to clearly define the physical flow and logical boundaries of data between each level. Organization-level permissions refer to dynamically binding data access permissions to the organization level. This is achieved by embedding permission verification mechanisms or role-based access control policies during the data extraction phase, ensuring that only data within the authorized scope of that level is extracted.

[0042] The technical solution in this embodiment achieves precise permission control during the data retrieval process by deeply coupling the data stack path with organizational-level permissions. First, the data stack path not only defines the physical flow of data between group, institute, or factory levels, but also implicitly defines the logical boundaries at the organizational level. Therefore, retrieving data based on this path naturally embeds permission control into the data transmission link. Second, organizational-level permission attributes are directly bound during the data extraction stage. For example, factory-level units can only access production or material data covered by their permissions, and cannot access sensitive group-level information, thus blocking the risk of unauthorized access at the source of data flow. Furthermore, this solution, combined with the aforementioned binding relationship between multi-level interconnected data blocks and reverse feedback link blocks, further strengthens permission consistency during cross-system data feedback, effectively solving the problem of data detaching from permission constraints.

[0043] The above technical solutions not only achieve dynamic correspondence between data permissions and organizational levels, but also establish an effective permission control mechanism at the source of data flow, significantly improving the security and reliability of cross-system data feedback. In some embodiments, this application further proposes that when a data request contains information in a multi-domain associated data block, after establishing the binding relationship between the multi-level interconnected data block and the reverse feedback link block, the application further includes: establishing an association relationship between the multi-domain associated data block and the multi-level interconnected data block, wherein the association relationship is used to characterize the association between different categories of data under the same organizational level.

[0044] A multi-domain associated data block refers to a collection of data related to multiple business domains, used to integrate data resources scattered across different business domains. The association relationship is a mapping mechanism used to ensure that various types of data at the same organizational level can form a logical whole.

[0045] like Figure 4As shown, a multi-domain associated data block is a collection of associated domain data from multi-level interconnected data blocks, used to express the data relationship between data in this domain and associated domains. A multi-domain associated data block is a binary tree of associated domain data, composed of roots, branches, and leaves. The root of the associated domain tree is the root node of the binary tree, connecting two leaves. Depending on the level, associated domain roots are divided into three categories: group-level, institute-level, and factory / institute-level. A group-level associated domain root is the root node of the group-level associated domain data, encompassing its professional business areas. A institute-level associated domain root is the root node of the institute-level associated domain data, encompassing its professional business areas. A factory / institute-level associated domain root is the root node of the factory / institute-level associated domain data, encompassing its professional business areas. A branch of the associated domain tree is the connector between the root and leaves. Multiple levels of branch connections are allowed between the root and leaves. A branch connects the group-level, institute-level, and factory / institute-level associated domain roots. A leaf of the associated domain tree is the terminal node of the binary tree. Based on different levels, the leaves of the related domain are divided into three categories: group-level, institute-level, and factory / institute-level. Group-level related domain leaves refer to data under the group-level related domain. Institute-level related domain leaves refer only to data under the institute-level related domain. Factory / institute-level related domain leaves refer only to data under the factory / institute-level related domain. Multi-domain related data blocks consist of related domain data and data permissions. In the group-level, institute-level, and factory / institute-level receiving stacks, the related domain data is the complete set of related domain data. When extracting subsets, it is ensured that the subsets are not empty sets, and the data permissions are the permissions of the complete data set. The group-level receiving stack receives the complete set of related domain data for the group, the institute-level receiving stack receives the complete set of related domain data for its own institute, and the factory / institute-level receiving stack receives the complete set of related domain data for its own factory / institute. Data permissions match the complete set of related domain data at each level. In the output stack, data is retrieved on demand, the minimum set is returned, subset operations are performed on the related domain data, and subsets are extracted from the related domain data. Data permissions match the data subsets. The group-level output stack outputs the data set from the group's data that corresponds to the data in the institute's related domain. The institute-level output stack outputs the data set from the institute-level data that corresponds to the data in the plant's related domain. Data permissions are matched with subsets of data in each level of related domain.

[0046] Specifically, when a data request contains information about multi-domain related data blocks, the system first identifies the cross-business domain data requirements that need to be processed. Based on the established binding relationships between multi-level interconnected data blocks and reverse feedback link blocks, it further constructs the association relationships between multi-domain related data blocks and multi-level interconnected data blocks. Through organizational-level constraints, previously scattered business data, such as production costs and material information, are precisely bound together. During this process, the system filters and reorganizes data from different business domains according to preset rules, ensuring that the returned data carries complete business context information. This approach not only solves the problem of data fragmentation but also strengthens boundary control of data permissions, enabling subordinate units to conduct reliable analysis based on complete datasets.

[0047] The technical solution in this embodiment effectively solves the data correlation problem and achieves logical consistency of cross-business domain data at the target organizational level.

[0048] In some embodiments, this application further proposes that the interconnected data domain includes an interconnected local domain and an interconnected related domain, and the multi-domain related data block includes a data set of interconnected related domains in the multi-level interconnected data block; establishing the association relationship between the multi-domain related data block and the multi-level interconnected data block includes: associating the data in the multi-domain related data block that is associated with the interconnected local domain according to the organizational level.

[0049] The interconnected data domain is implemented using a hierarchical binary tree structure, specifically divided into two parts: the interconnected local domain and the interconnected related domain. The interconnected local domain focuses on the core business data, while the interconnected related domain covers data from other business domains related to the core business, providing a clear classification framework for cross-domain data backflow. A multi-domain related data block is a logical unit containing a set of interconnected related domain data from multi-level interconnected data blocks. It can be implemented through data mapping or data indexing to ensure that related data strictly originates from the interconnected related domain, thus avoiding the mixing of irrelevant data. Data in the multi-domain related data block that is associated with the interconnected local domain is linked according to organizational level, using organizational level as a constraint. This can be implemented through hierarchical permission control or hierarchical data routing to avoid erroneous binding of cross-level data and maintain the consistency of data permissions.

[0050] like Figure 3As shown, the interconnected data domain consists of the interconnected local domain and the interconnected related domains. The interconnected organizational domain consists of institute-level organizations, which oversee both data domains and organizational domains. The organizational domain records the necessary path for data backflow. The group-level root is the group-level data stack, i.e., the carrier of the receiving and output stacks. The institute-level root is the root node of the entire institute-level data domain and organizational domain. The data domain consists of the local domain and related domains. The organizational domain consists of plant / institute-level organizations, which oversee data domains. The organizational domain records the necessary path for data backflow. The institute-level root is the institute-level data stack, i.e., the carrier of the receiving and output stacks. The plant / institute-level root is the root node of the specific plant / institute data domain. The data domain consists of the local domain and related domains, without organizational domains. The plant / institute-level root is the plant / institute-level data stack, i.e., the carrier of the receiving and output stacks. Branches are the connectors between the roots and leaves. There can be multiple levels of branch connections between the roots and leaves. Branches connect the group-level, institute-level, and plant / institute-level roots. A leaf node refers to the terminal node of a binary tree. Based on different levels, leaves are divided into three categories: group-level, institute-level, and factory / institute-level. Group-level leaves refer only to data under the group's own domain. Institute-level leaves refer only to data under the institute's own domain. Factory / institute-level leaves refer to data under the factory / institute's own domain. The local data in a multi-level interconnected data block consists of local data and data permissions. In the group-level, institute-level, and factory / institute-level receive stacks, local data is the complete set of local data, and data permissions are the permissions of the complete set of data. In the output stack, local data is a subset of local data, and data permissions are the permissions of the subset of data.

[0051] The technical solution described in this application achieves precise control of the association dimension during cross-domain data backflow by using a structured definition of the data domain and an organization-level driven association mechanism. The design of the data domain distinguishes the logical boundaries between core business data and related business data. The data domain focuses on the main business domain, while the related domain covers related business domains such as materials and suppliers, providing a clear data source basis for subsequent association operations. The multi-domain associated data block ensures accurate capture of associated data through the aggregated processing of the related domain data, solving the problem of difficulty in binding scattered business domain data. Based on this, data associated with the data domain in the multi-domain associated data block is associated according to the organization level. Using the organization level as a natural isolation layer, data association is strictly limited to the same level, ensuring both the integrity of the backflow data and maintaining consistent permissions. For example, in a plant-level scenario, only the data in the corresponding data domain and related domains at that level are associated, avoiding the situation where group-level data is incorrectly associated with plant-level scenarios, thus effectively supporting accurate decision-making by subordinate units.

[0052] It is understandable that the above technical solution solves the problem of missing association dimensions in cross-domain data backflow by defining structured data domains and an organization-level driven association mechanism, ensuring that data forms a complete business context within the correct organizational hierarchy, while maintaining the consistency of data permissions, and realizing accurate synchronization and secure flow of cross-domain data.

[0053] In some embodiments, this application further proposes associating data in a multi-domain associated data block with data that is associated across the same domain according to organizational level, including: performing a set operation on the multi-level interconnected data block and the multi-domain associated data block based on organizational level.

[0054] Specifically, a multi-domain related data block refers to a collection containing related data from multiple business domains. Data that connects these domains is a set of data with direct logical relationships within a specific business domain, used to ensure that data at the same organizational level maintains business context integrity. Set operations are mathematical operations that can be implemented through operations such as intersection, union, or difference, used to filter and bind related data using precise rules.

[0055] Specifically, the technical solution in this application addresses the problem of inaccurate cross-business domain data association in multi-level organizational environments by introducing an organization-level set operation mechanism. This solution uses the organization level as the core benchmark dimension for data association, fully utilizing the data routing paths and permission boundaries defined at the organization level by performing set operations on multi-level interconnected data blocks and multi-domain associated data blocks. For example, when processing plant-level data, the set operation focuses only on the data stack path range corresponding to the plant level, avoiding invalid mixing of cross-level data. This not only ensures that association operations are strictly limited to the same-level business context but also effectively prevents unauthorized access risks through a level isolation mechanism. Furthermore, the organization-level operation method directly couples the data structure and routing path, enabling the association process to dynamically adapt to multi-level architectures, thereby significantly improving the reliability and security of data backflow.

[0056] This application's embodiments, through clearly defined set operation rules, not only achieve precise matching between different categories of data at the same organizational level, but also effectively avoid association errors and data fragmentation issues that may occur during cross-business domain data backflow, while ensuring the clarity of permission boundaries. This design is particularly suitable for complex data backflow scenarios in multi-level organizational structures such as group-level, institute-level, and factory-level organizations, demonstrating its technical advantages in improving data integrity and permission consistency. In some embodiments, this application further proposes to establish an association relationship between multi-domain associated data blocks and multi-level interconnected data blocks, and then further includes: based on the interconnected organizational domain, routing data at different organizational levels to the corresponding organizational levels, and assigning data permissions at the corresponding organizational levels.

[0057] The "connected organizational domain" refers to the routing path used to characterize data. It employs predefined hierarchical structure information to ensure data flows precisely to the target level according to organizational hierarchy. In practical applications, data routing refers to the process of distributing data to matching receivers according to predetermined rules. This is achieved through automated allocation based on path information within the connected organizational domain, preventing data misalignment or redundancy. Data permissions refer to access control policies bound to specific organizational levels. They are implemented by dynamically generating and binding permission rules during data transmission, preventing permission disconnection or invalidation during cross-system transfers.

[0058] The technical solution in this embodiment solves the permission consistency problem in the data reverse feedback process by leveraging the path dependency mechanism provided by the organizational domain, ensuring that data flows strictly to the target level according to the organizational hierarchy. Furthermore, data routing and permissions are executed synchronously; that is, as soon as data is routed to the corresponding organizational level, a matching access control policy is immediately assigned. This not only strengthens the synchronous management of data and permissions but also ensures the reliability of routing and the immediate effectiveness of permissions through the path dependency characteristics of the organizational domain.

[0059] It is understandable that the above technical solutions effectively solve the problem of unauthorized access or invalidation of permissions to data in heterogeneous systems, achieve consistent management of data and permissions, and enhance the security and reliability of data feedback.

[0060] In some embodiments, this application further proposes routing data from different organizational levels to the corresponding organizational level and granting data permissions to the corresponding organizational level. It also includes synchronizing multi-level interconnected data blocks and multi-domain associated data blocks according to the association relationship and organizational level.

[0061] A data synchronization mechanism for multi-level interconnected data blocks and multi-domain associated data blocks is used to ensure that core business data and its associated information remain consistent in real time. The technical solution effectively solves the problem of missing associated information during data feedback by introducing a data synchronization mechanism based on relationships and organizational levels.

[0062] In one example, the scope of data to be synchronized is first determined based on relationships, ensuring that when data from one business domain is fed back, data from other related business domains can be automatically bound and fed back, avoiding data silos and fragmentation. Secondly, synchronization operations are strictly constrained according to organizational levels, ensuring that data at each level is only transmitted to the organizational level with the corresponding permissions, preventing unauthorized access risks, and ensuring data availability and permission consistency at the target level. Furthermore, by synchronizing multi-level interconnected data blocks and multi-domain related data blocks, core business data and its cross-business domain relationships are kept consistent in real time, providing subordinate units with a complete business view and supporting them in making accurate decisions and analyses based on comprehensive data. This process not only compensates for potential data integrity issues arising from previous data routing and permission allocation but also further enhances the overall reliability of data feedback and the consistency of the business context.

[0063] The above-described technical solution in this embodiment enables efficient synchronization of multi-level interconnected data blocks and multi-domain associated data blocks during the data reverse feedback process, ensuring the integrity and logical consistency of the returned data and providing comprehensive and reliable business data support for subordinate units. In one example, such as Figure 5 As shown, data transmission consists of pushing onto the stack, rotating onto the stack, and popping from the stack. Specifically, it is implemented in the following way: Stack rules: When a multi-domain associated data block is selected, the multi-domain associated data block is pushed onto the stack first, followed by the multi-level interconnected data block, and finally the reverse feedback link block. If no multi-domain associated data block is selected, the multi-level interconnected data block is pushed onto the stack first, followed by the reverse feedback link block.

[0064] Stack rules: Stack swapping is the medium for converting between the receiving stack and the output stack. It primarily provides operations such as association, binding, routing, synchronization, and subset operations, enabling unified management of data flow. The specific operation process is as follows: First, the entire data set enters the receiving stack, where two operations are performed: one is to establish a multi-domain associated data block to associate with multi-level interconnected data blocks; the other is to complete the binding with the multi-level interconnected data block through the reverse feedback link block.

[0065] Secondly, according to business requirements, the entire set of data entering the receiving stack is processed and converted into a subset of data that meets the requirements.

[0066] Finally, the transformed subset is pushed into the output stack, the reverse feedback link block is reset, and the multi-domain associated data blocks are synchronized through the multi-level interconnected data blocks to complete the entire stack transfer process.

[0067] When multi-domain associated data blocks are not selected, the stack transfer function only retains binding, routing, and subset operations, and the process is simplified accordingly: First, after the entire data set enters the receiving stack, there is no need to establish multi-domain associated data blocks. Instead, a reverse feedback link block is directly established, and multi-level interconnected data blocks are bound through this link block.

[0068] Secondly, the entire data set is converted into a subset of data according to business needs.

[0069] Finally, the data subset is pushed onto the output stack, and the reverse feedback link block is reset to route multi-level data blocks, completing a simplified stack rollover operation.

[0070] The subset operation extracts a subset of data that meets the requirements based on business needs and data permissions from the entire dataset. The specific rules include the following two aspects: First, when extracting a subset of data, it is necessary to ensure that the subset is not an empty set. Specifically, data from the current domain is based on the entire dataset of data from the current domain, and the corresponding data permissions are consistent with the permissions of the entire dataset; data from related domains is based on the entire dataset of data from the related domains, and the corresponding data permissions are also consistent with the permissions of the entire dataset.

[0071] Secondly, subsets are extracted using set operations. Specifically, for data in the current domain, a subset of the current domain data needs to be extracted, and the permissions of the extracted data must match the data subset; for data in related domains, a subset of the related domain data needs to be extracted, and the permissions of the extracted data must also match the data subset.

[0072] This embodiment also provides a multi-domain, multi-level data feedback device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0073] This embodiment provides a multi-domain, multi-level data feedback device, such as... Figure 6 As shown, it includes: The confirmation module 601 is used to confirm the data request information that needs to be fed back.

[0074] The binding module 602 is used to establish a binding relationship between multi-level interconnected data blocks and reverse feedback link blocks based on data request information. The multi-level interconnected data blocks are used to characterize the data structure, and the reverse feedback link blocks are used to provide stack paths.

[0075] The retrieval module 603 is used to retrieve the request data that needs to be returned based on the binding relationship.

[0076] The multi-domain, multi-level data feedback device provided in this application can execute the multi-domain, multi-level data feedback method provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing the method. Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0077] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0078] The following is a detailed reference. Figure 7 The diagram illustrates a structural schematic suitable for implementing the electronic device described in the embodiments of this application. The electronic device may include a processor (e.g., a central processing unit, graphics processor, etc.) 701, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 702 or a program loaded from memory 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device. The processor 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0079] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; memory devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic devices to exchange data via wireless or wired communication with other devices. Although Figure 7 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown, and more or fewer devices may be implemented or have instead.

[0080] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 709, or installed from memory 708, or installed from ROM 702. When the computer program is executed by processor 701, it performs the functions defined in the multi-domain, multi-level data feedback method of embodiments of this application.

[0081] Figure 7The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0082] This application also provides a computer-readable storage medium. The methods described in this application can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code downloaded over a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the multi-domain, multi-level data feedback method shown in the above embodiments is implemented.

[0083] A portion of this application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0084] Although embodiments of this application have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of this application, and all such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A multi-domain, multi-level data feedback method, characterized in that, The method includes: Confirm the data request information that needs to be returned; Based on the data request information, a binding relationship is established between the multi-level interconnected data block and the reverse feedback link block, wherein the multi-level interconnected data block is used to characterize the data structure, and the reverse feedback link block is used to provide the stack path; Based on the binding relationship, obtain the request data that needs to be fed back.

2. The multi-domain, multi-level data feedback method according to claim 1, characterized in that, The data request information includes organizational levels, which include group level, institute level, and factory / research institute level. The multi-level interconnected data block includes a binary tree composed of interconnected data domains and interconnected organization domains. Different levels of the binary tree correspond to different organization levels. The interconnected organization domain is used to characterize the routing path of the data. The reverse feedback link block includes a data stack corresponding to the organization level, and the request data of different organization levels are transmitted through different data stack paths; The step of establishing a binding relationship between multi-level interconnected data blocks and reverse feedback link blocks based on the data request information includes: Based on the organizational level, the data stack path corresponding to the organizational level in the multi-level interconnected data block is determined, wherein the data stack path is used to characterize the flow direction of data at different organizational levels.

3. The multi-domain, multi-level data feedback method according to claim 2, characterized in that, The step of determining the data stack path corresponding to the organization level in the multi-level interconnected data block based on the organization level includes: When the organization level is the group level, the data stack path is from the cloud system to the group-level receiving stack; When the organization level is the institute level, the data stack path is from the group-level output stack to the institute-level receiving stack; When the organization level is the factory / institute level, the data stack path is from the group-level output stack to the factory / institute-level receiving stack, and / or from the institute-level output stack to the factory / institute-level receiving stack.

4. The multi-domain, multi-level data feedback method according to claim 3, characterized in that, The step of obtaining the request data to be returned based on the binding relationship includes: Based on the data stack path, obtain the request data that needs to be returned and corresponds to the permissions of the organization level.

5. The multi-domain, multi-level data feedback method according to claim 2, characterized in that, When the data request contains information from multi-domain associated data blocks, the process of establishing the binding relationship between multi-level interconnected data blocks and reverse feedback link blocks further includes: Establish the association relationship between the multi-domain associated data block and the multi-level interconnected data block, wherein the association relationship is used to characterize the association between different categories of data under the same organizational level.

6. The multi-domain, multi-level data feedback method according to claim 5, characterized in that, The connected data domain includes connected local domain and connected related domain, and the multi-domain related data block includes the data set of the connected related domain in the multi-level connected data block; The process of establishing the association between the multi-domain associated data block and the multi-level interconnected data block includes: The data in the multi-domain associated data block that are associated with the data in the same domain are associated according to the organizational level.

7. The multi-domain, multi-level data feedback method according to claim 6, characterized in that, The step of associating the data in the multi-domain associated data block that is associated with the data in the same domain according to the organizational level includes: Based on the organizational level, a set operation is performed on the multi-level interconnected data block and the multi-domain associated data block.

8. The multi-domain, multi-level data feedback method according to claim 6, characterized in that, The process of establishing the association between the multi-domain associated data block and the multi-level interconnected data block further includes: Based on the interconnected organizational domain, data from different organizational levels is routed to the corresponding organizational level, and data permissions for the corresponding organizational level are assigned.

9. The multi-domain, multi-level data feedback method according to claim 8, characterized in that, The step of routing data from different organizational levels to their corresponding organizational levels and granting data permissions to the appropriate organizational levels also includes: Based on the aforementioned relationship, the multi-level interconnected data block and the multi-domain associated data block are synchronized according to the aforementioned organizational level.

10. A multi-domain, multi-level data feedback device, characterized in that, The device includes: The confirmation module is used to confirm the data request information that needs to be returned. The binding module is used to establish a binding relationship between a multi-level interconnected data block and a reverse feedback link block based on the data request information, wherein the multi-level interconnected data block is used to characterize the data structure, and the reverse feedback link block is used to provide a stack path. Acquisition module: Used to obtain the request data that needs to be returned based on the binding relationship.

Images