Cascading data management method, device, and storage medium

Abstract

The application discloses a kind of cascade data management method, equipment and storage medium, it is related to data management technical field, comprising: periodically summarizing local service data, obtaining the first summary data of corresponding current period;Periodically receive the second summary data reported by the direct subordinate node equipment connected to intermediate node equipment and aggregate the second summary data and the first summary data, obtain the corresponding aggregate data;Aggregate data is pushed to the direct superior node equipment connected to intermediate node equipment;Send the detailed query request corresponding to the summary data item in second summary data to target subordinate node equipment, receive the original detailed data sent by target subordinate node equipment in response to detailed query request and generate detailed display result, solve the technical problems that cannot be summarized in high efficiency in prior art Multi-level data while supporting the depth penetration query of original detail, balance the contradiction between the management efficiency and management depth of multi-level data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data management, in particular to a cascaded data management method, device and storage medium. BACKGROUND

[0002] With the rapid development of the Internet, data assets have gradually become as important as physical assets for enterprises. Many enterprises actively promote the data transformation of assets to achieve more convenient and transparent asset analysis and management. Especially for group customers, their multi-level tree organization structure puts higher requirements on data asset management. It is necessary to ensure the independent management ability of each branch to its own assets and to realize the unified supervision of the headquarters to the whole group assets and risk status. To meet this demand, the industry has developed various technical solutions, such as centralized control deployment, distributed deployment + unified management, hierarchical management scheme, etc. Among them, the centralized control deployment can realize the control of the headquarters to the whole data, but it has problems such as large network bandwidth consumption, limited autonomy of branch institutions, and dramatic increase of storage pressure of the headquarters; while the distributed deployment alleviates the transmission and storage pressure, but it is difficult for the headquarters to obtain the original details due to only reporting summary data, affecting the depth analysis and risk identification; the hierarchical management scheme uses the "on-demand query" mechanism to reduce the amount of transmission at a time and improve flexibility, but the deployment architecture is complex, the system permission model design is strict, and it is heavily dependent on the performance and stability of the branch node interface, which will significantly affect the query efficiency and user experience of the headquarters when the network delay is high or the availability of the branch platform is insufficient. SUMMARY

[0003] The main purpose of the present application is to provide a cascaded data management method, device and storage medium, which aims to solve the technical problem that the prior art cannot support deep penetration query of original detailed data while ensuring efficient aggregation of multi-level data.

[0004] To achieve the above purpose, the present application provides a cascaded data management method applied to any intermediate node device in a cascaded data management system, the cascaded data management system comprising one top node device, at least one intermediate node device and at least one bottom node device, each intermediate node device being connected to one direct superior node device and at least one direct subordinate node device, the cascaded data management method comprising:

[0005] periodically aggregating local business data to obtain first aggregation data corresponding to a current period;

[0006] periodically receiving second aggregation data reported by the direct subordinate node device connected to the intermediate node device, and aggregating the second aggregation data and the first aggregation data to obtain corresponding aggregated data;

[0007] push the aggregated data to the direct superior node device to which the intermediate node device is connected;

[0008] send a detailed query request corresponding to an aggregated data item in the second aggregated data to a target subordinate node device, receive original detailed data sent by the target subordinate node device in response to the detailed query request, and generate a detailed display result, the target subordinate node device being the direct subordinate node device or a cross-level subordinate node device of the intermediate node device.

[0009] In addition, to achieve the above object, the application further provides a cascaded data management device, which comprises:

[0010] a data aggregation module, configured to periodically receive second aggregated data reported by the direct subordinate node device connected to the intermediate node device, and aggregate the second aggregated data and the first aggregated data to obtain corresponding aggregated data;

[0011] a data aggregation module, configured to periodically receive second aggregated data reported by the direct subordinate node device connected to the intermediate node device, and aggregate the second aggregated data and the first aggregated data to obtain corresponding aggregated data;

[0012] a data transmission module, configured to push the aggregated data to the direct superior node device to which the intermediate node device is connected;

[0013] a detailed data query module, configured to send a detailed query request corresponding to an aggregated data item in the second aggregated data to a target subordinate node device, receive original detailed data sent by the target subordinate node device in response to the detailed query request, and generate a detailed display result, the target subordinate node device being the direct subordinate node device or a cross-level subordinate node device of the intermediate node device.

[0014] In addition, to achieve the above object, the application further provides a cascaded data management device, which comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the cascaded data management method as described above.

[0015] In addition, to achieve the above object, the application further provides a storage medium, which is a computer-readable storage medium, and the storage medium stores a computer program, the computer program being executable by a processor to implement the steps of the cascaded data management method as described above.

[0016] In addition, to achieve the above object, the application further provides a computer program product, which comprises a computer program, the computer program being executable by a processor to implement the steps of the cascaded data management method as described above.

[0017] The one or more technical solutions provided in the present application have at least the following technical effects: The cascade data management method is applied to any intermediate node device in a cascade data management system, the cascade data management system includes a top node device, at least one intermediate node device, and at least one bottom node device, each intermediate node device is connected to a direct superior node device and at least one direct subordinate node device. By periodically aggregating local business data, first aggregation data corresponding to a current period is obtained; the second aggregation data reported by the direct subordinate node device connected to the intermediate node device is periodically received, and the second aggregation data and the first aggregation data are aggregated, each intermediate node device periodically aggregates the local aggregation data of the intermediate node device with the aggregation data collected from all direct subordinate node devices to obtain corresponding aggregation data; and the aggregation data is pushed to the direct superior node device connected to the intermediate node device, thereby reducing the bandwidth occupation caused by full data transmission and realizing efficient convergence of data to the top node. When it is necessary to deeply analyze a certain aggregation item, a detailed query request corresponding to the aggregation data item in the second aggregation data is sent to the target subordinate node device, the original detailed data sent by the target subordinate node device in response to the detailed query request is received, and a detailed display result is generated, thereby realizing direct connection penetration without pre-stored details and without dependence on layer-by-layer forwarding. The target subordinate node device is a direct subordinate node device or a cross-level subordinate node device of the intermediate node device, all intermediate node devices and bottom node devices retain original detailed data, local management autonomy is guaranteed, the superior node device does not need to store a large amount of details, and the double needs of distributed management and centralized supervision are balanced by calling and obtaining detailed data on demand. Through the multi-level data aggregation reporting+on-demand detailed data checking dual-track mechanism, the technical problem that the original details cannot be deeply penetrated and queried while efficiently aggregating multi-level data in the prior art is accurately solved, thereby balancing the contradiction between the management efficiency and the management depth of multi-level data. The cascade data management method provided in the present application periodically aggregates local and subordinate aggregation data and transmits it upward, thereby avoiding full original data reporting, reducing network bandwidth consumption and superior storage pressure; meanwhile, when it is necessary to deeply analyze a certain aggregation index, the intermediate node device can directly initiate a detailed query request to the target subordinate node device (including a non-direct subordinate node across multiple levels), and receive the original detailed data returned by the target subordinate node device to generate a display result. The detailed data query process does not need layer-by-layer forwarding and does not depend on intermediate node transfer, which guarantees query efficiency and ensures that the superior node device can truly understand the details of the bottom business. Therefore, on the premise of retaining the data autonomy of each branch, the headquarters or intermediate management layer realizes penetrating supervision of global data assets, effectively solves the technical problem that it is difficult to balance data efficient aggregation and original detailed penetration query in a multi-level organizational structure by constructing a dual-track mechanism combining aggregation reporting and on-demand detailed data checking. BRIEF DESCRIPTION OF DRAWINGS

[0018] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, those skilled in the art can obtain other drawings from these drawings without any creative effort.

[0020] Figure 1 A flowchart provided by the embodiment of the cascade data management method of the present application;

[0021] Figure 2 A group architecture diagram provided by the present application containing a multi-level organization (company);

[0022] Figure 3 A structure diagram of a cascade data management system provided by the present application;

[0023] Figure 4 A flowchart of data flow and processing of bottom-middle-top node devices in the cascade data management system provided by the present application;

[0024] Figure 5 A flowchart of security verification provided by the present application;

[0025] Figure 6 A topology change diagram of a node device to be cascaded in the cascade data management system provided by the present application;

[0026] Figure 7 A flowchart of detailed data query and presentation provided by the present application;

[0027] Figure 8 A diagram of decoupling and independent running of a subset cluster in the cascade data management system provided by the present application;

[0028] Figure 9 A module structure diagram of the cascade data management device of the embodiment of the present application;

[0029] Figure 10 A device structure diagram of the hardware running environment involved in the cascade data management method in the embodiment of the present application.

[0030] The purpose implementation, functional features and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0031] It should be understood that the specific embodiments described herein are merely intended to explain the technical solutions of the present application, and are not used to limit the present application.

[0032] In order to better understand the technical solutions of the present application, the following will be described in detail in combination with the drawings of the specification and specific embodiments.

[0033] The main solution of the embodiment of the present application is: applied to any intermediate node device in a cascaded data management system, the cascaded data management system includes a top node device, at least one intermediate node device and at least one bottom node device, each intermediate node device is connected to a direct superior node device and at least one direct subordinate node device, the cascaded data management method includes: periodically aggregating local business data to obtain first aggregation data corresponding to a current period; periodically receiving second aggregation data reported by the direct subordinate node device connected to the intermediate node device, and aggregating the second aggregation data and the first aggregation data to obtain aggregation data; pushing the aggregation data to the direct superior node device connected to the intermediate node device; sending a detailed query request corresponding to the aggregation data item in the second aggregation data to the target subordinate node device, receiving the original detailed data sent by the target subordinate node device in response to the detailed query request and generating a detailed display result, and the target subordinate node device is a direct subordinate node device or a cross-level subordinate node device of the intermediate node device.

[0034] In the present embodiment, for the convenience of description, the following is described by identifying the cascaded data management system as the execution subject.

[0035] With the rapid development of the Internet, data assets have gradually become as important as physical assets for enterprises. Many enterprises actively promote the data transformation of assets to achieve more convenient and transparent asset analysis and management. Especially for group customers, the multi-level tree organization structure puts higher requirements on data asset management. It is necessary to ensure the independent management ability of each branch to its own assets and to realize the unified supervision of the headquarters to the whole group assets and risk status. To meet this demand, the industry has developed various technical solutions, such as centralized control deployment, distributed deployment + unified management, hierarchical management solution, and data exchange platform solution. Among them, although the centralized control deployment can realize the control of the headquarters to the whole data, it has problems such as large network bandwidth consumption, limited autonomy of branch institutions, and dramatic increase of storage pressure of the headquarters. While the distributed deployment alleviates the transmission and storage pressure, it is difficult for the headquarters to obtain the original details due to only reporting summary data, which affects in-depth analysis and risk identification. The hierarchical management solution uses the "on-demand query" mechanism to reduce the amount of transmission and improve flexibility, but its deployment architecture is complex, the system permission model design is strict, and it is heavily dependent on the performance and stability of the branch node API. When the network delay is high or the branch platform availability is insufficient, it will significantly affect the query efficiency and user experience of the headquarters.

[0036] The present application provides a solution, the intermediate node device periodically aggregates local and subordinate summary data and transmits it upwards, avoiding the reporting of whole original data, which can reduce network bandwidth consumption and upper storage pressure; at the same time, when in-depth analysis of a certain summary index is needed, the intermediate node device can directly initiate a detailed query request to the target subordinate node device (including non-direct subordinates across multiple levels), and receive the original detailed data returned by the target subordinate node device to generate a display result. The detailed data query process does not need to be forwarded layer by layer and does not depend on intermediate node transit, which not only guarantees the query efficiency, but also ensures that the upper node device can truly understand the underlying business details. Thus, on the premise of preserving the data autonomy of each branch, the headquarters or intermediate management layer realizes penetrating supervision of global data assets, effectively solves the technical problem of difficult to balance data efficient aggregation and original detailed penetrating query in multi-level organization structure by building a double-track mechanism combining summary reporting and on-demand detailed inquiry.

[0037] It should be noted that the execution subject of the present embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or a cascading data management device capable of realizing the above functions. The following will take the cascading data management system as an example to illustrate the present embodiment and the following embodiments.

[0038] Based on this, the present embodiment provides a cascading data management method, which refers to Figure 1 , Figure 1Flowchart of the first embodiment of the cascaded data management method.

[0039] In this embodiment, the cascaded data management method is applied to any intermediate node device in the cascaded data management system, which includes a top node device, at least one intermediate node device, and at least one bottom node device. Each intermediate node device is connected to one direct superior node device and at least one direct inferior node device. The cascaded data management method includes steps 101-104.

[0040] Step 101: Periodically aggregate local business data to obtain first aggregated data corresponding to a current period.

[0041] Specifically, a set of node devices are deployed in the group headquarters and each branch. The node devices are connected through a dedicated network. Before the node devices are established in cascade, it is necessary to ensure that the network of the group and each branch can communicate normally in both directions. Consistent with the group architecture, the node device architecture deployed in each institution also presents a multi-layer tree structure. After the node devices of each institution are deployed, the cascade mode of the device needs to be turned on, so that it can normally connect with other node devices. The node device can actively initiate cascade to other node devices, or be cascaded to access other node devices. There is a superior-inferior relationship between node devices, which is determined according to the actual relationship of the company institutions to which each node device belongs. Each node device can access multiple inferior node devices, but can only access one superior node device at the same time. Reference Figure 2 , Figure 2 The group architecture can be a schematic diagram of a multi-level organization (company), Figure 3 The cascaded data management system architecture can be a schematic diagram of a cascaded data management system, which has the same architecture as the group architecture.

[0042] The cascade data management system is a distributed data management system suitable for a multi-layer tree organization structure of a group, which is composed of top node devices, intermediate node devices and bottom node devices. Data aggregation and query are realized through cascading between node devices, and the autonomy of branch organizations and the control of headquarters are taken into account. The top node device is the highest-level core control device in the cascade data management system (corresponding to the device deployed by the headquarters of the group), which can receive aggregated data pushed by the next-level intermediate node device, realize unified supervision and management of data of the whole group, and is not directly connected to the bottom node device. The intermediate node device is a transfer / management device in the cascade data management system (corresponding to the device deployed by a first-level subsidiary, a second-level subsidiary or other branch organizations), which is a data reporting party of the superior node and a data receiving and control party of the subordinate node. Each intermediate node device is strictly connected to one direct superior node device and at least one direct subordinate node device in the cascade data management system, forming a clear and loop-free superior-inferior relationship. The bottom node device is the lowest-level terminal device in the cascade data management system (corresponding to the device deployed by a branch company, an office or other basic organizations), which periodically aggregates local business data and reports to the direct superior intermediate node device, and has no subordinate node. The direct superior node device is the device located at the previous level of the current intermediate node device (which can be another intermediate node device or a top node device) and has a direct cascading relationship with the current intermediate node device, and the direct superior node device is the pushing object of the aggregated data of the current device. The direct subordinate node device is the device located at the next level of the current intermediate node device (which can be another intermediate node device or a bottom node device) and has a direct cascading relationship with the current intermediate node device, and the direct subordinate node device is the receiving source of the aggregated data of the current device. In the cascade data management method provided in the application, each bottom node device in the cascade data management system periodically aggregates local business data (such as asset list, risk log, etc.) generated locally, and reports the generated aggregation result to its direct superior; the intermediate node device periodically aggregates its own local business data to obtain first aggregation data, and receives second aggregation data reported by all direct subordinate node devices, aggregates the first aggregation data and the second aggregation data to form new aggregated data, and pushes the aggregated data to its direct superior node, thereby building a complete aggregation view step by step; at the same time, when the intermediate node device needs to perform in-depth analysis on a certain aggregation index, it can initiate a detailed query request to the target subordinate node device (including direct subordinate or non-direct subordinate across multiple levels) based on the global cascade topology corresponding to the locally maintained cascade data management system, and the target node device returns the original detailed data after responding, and the intermediate node device completes data integration and display.The top node device in the cascaded data management system periodically aggregates local business data generated locally, receives aggregated data uploaded by the intermediate node device directly connected to the top node device, and when the top node device needs to perform in-depth analysis on a certain aggregation index, can initiate a detailed query request to the target lower node device (including direct lower node or non-direct lower node across multiple levels) based on the locally maintained global cascaded topology, and the target node device returns the original detailed data in response, and the detailed data integration and display are realized directly in the top node device. Each intermediate node device in the cascaded data management system serves as a pivotal link between the upper and lower nodes, periodically aggregates local data and lower node reported data to form new aggregation results for upward pushing, and builds an efficient low-bandwidth consumption data channel, and at the same time, as a query scheduling center, can directly obtain the original detailed data of any lower node (including cross-level node) according to the demand through remote calling, forming a high-precision data penetration capability triggered on demand. The cascaded data management system provided in the application breaks through the technical bottleneck that the headquarters cannot deeply explore the original data in the traditional scheme, and realizes fine control of global data while maintaining the advantages of low network pressure and high branch autonomy of the distributed architecture.

[0043] Specifically, the local business data is the original data generated by the node (intermediate node device) itself, such as asset account, security log, risk event record, etc., which is stored in a local database or a log system. The aggregation can be a processing process of performing statistical, counting, summing, de-duplication, etc. aggregation operation on the local business data according to a certain dimension (such as asset type, risk level, region, state), to generate summary information. The first aggregation data refers to the result data generated by the intermediate node device after aggregating the local business data itself, and does not include any data reported by the lower node device, which is the basis data for subsequent aggregation with lower data.

[0044] In some embodiments, the intermediate node device is pre-configured with a fixed aggregation period (which can be the default every hour, and can be adjusted as needed), and the system automatically triggers the local business data aggregation task according to the period. First, the full amount of original business data in the current period is extracted from the local secure storage unit of the device, after invalid and duplicate data are removed, the data are classified and counted according to the preset rules (such as asset type, risk level), to generate result data containing core indicators, i.e. the first aggregation data. The first aggregation data only covers the local business information of the device and does not include lower node data, and after being generated, can be stored in a local special aggregation database, marked with a timestamp and a device identifier, to prepare for subsequent aggregation with lower reported data.

[0045] Step 102, periodically receiving the second aggregation data reported by the direct lower node device connected to the intermediate node device, and aggregating the second aggregation data and the first aggregation data to obtain corresponding aggregated data.

[0046] Specifically, the direct lower-level node device is a next-level node device having a direct cascade relationship with the current intermediate node device, which can be another intermediate node device or a bottom-level node device. The direct lower-level node device is the reporting source of the second summary data. The second summary data is the result data generated by the direct lower-level node device according to its own period, which is the local business data summary result of the bottom-level node or the aggregation result of the "local data + own lower-level data" of the lower-level intermediate node. The second summary data only contains core statistical information and does not contain original detailed data. Aggregation refers to the process of integrating the first summary data generated by the intermediate node device and the second summary data reported by all direct lower-level nodes. The aggregation process can include data merging, index summarizing, and logical verification to form complete result data covering "local data + all direct lower-level data". The aggregated data is the final result data generated after aggregation, which contains the business data summary information of the intermediate node device and the summary data of all direct lower-level nodes. The aggregated data is the core data pushed to the upper-level node.

[0047] In some embodiments, the intermediate node device can periodically receive the second summary data (i.e., the result data generated by the lower-level node itself) reported by all direct lower-level node devices at a preset time interval matching the lower-level summary period through a dedicated data receiving interface. During the receiving process, the intermediate node device automatically checks the data format and field integrity. If the check fails, the lower-level node retries to report. After the check passes, the intermediate node device retrieves the first summary data stored locally, performs aggregation processing on the two types of data (second summary data and first summary data) according to the preset rules, sums the accumulative indexes, merges the classified data, and completes the logical consistency check. Finally, the intermediate node device generates standardized aggregated data covering the overall status of itself and all direct lower-level nodes, stores the aggregated data in the local aggregation database, and marks it as a pending push state, preparing for transmission to the upper-level node. The aggregated data is the only data unit reported by the intermediate node device to its direct upper-level node device, which can avoid the complexity of multiple source dispersed reporting and ensure the completeness and consistency of the information obtained by the direct upper-level node device, laying a foundation for efficient hierarchical summarization.

[0048] Step 103, pushing the aggregated data to the direct upper-level node device connected to the intermediate node device.

[0049] Specifically, the directly superior node device connected to the intermediate node device is a node device at the upper level of the current intermediate node device and having a direct cascade relationship with the current intermediate node device. The directly superior node device can be a top-level node device (group headquarters deployment) or a higher-level intermediate node device (superior branch deployment). The directly superior node device is the receiving and controlling party of the aggregated data. Pushing can refer to the behavior of the intermediate node device actively transmitting aggregated data to the directly superior node device, which is performed based on a dedicated line network and a preset communication protocol and belongs to one-way data reporting (only the lower level pushes to the upper level, and the upper level does not actively pull). This ensures the initiative and timeliness of data transmission.

[0050] In some embodiments, after the intermediate node device generates aggregated data and marks it as a to-be-pushed state, the intermediate node device triggers a pushing task at a preset time synchronized with the aggregation period. Before pushing, the system confirms the cascade IP, dedicated receiving interface, and other communication information of the directly superior node device. The system can initiate data transmission through the dedicated line network using an encrypted transmission protocol. During transmission, the cascade security verification logic is linked to ensure data security. After the directly superior node device receives the data, the directly superior node device verifies the data legality through an integrity check code. If the network is abnormal or the superior is unavailable, a retry mechanism is started. If the retry fails, the data is temporarily stored locally, and the data is pushed again after the network is restored. After successful reception, the intermediate node device updates the data state to "pushed" and records a log. The superior node device stores the aggregated data for display or further aggregation, achieving efficient upward convergence of multi-level data. In the cascade data management method of the present application, after the intermediate node device completes the aggregation of local and subordinate summary data, the intermediate node device actively pushes the generated aggregated data to the directly superior node device corresponding to the intermediate node device, thereby ensuring that the summary data is efficiently, orderly, and safely transmitted upward along the organizational level, so that the superior node device can master the overall situation of the entire domain without directly interfacing with the bottom node device, significantly reducing system coupling and communication overhead.

[0051] In some embodiments, with reference to Figure 4 , Figure 4 Figure 1 is a flowchart of the data flow and processing of the bottom-middle-top node devices in the cascade data management system. Figure 4This demonstrates the data flow and processing mechanism from bottom-level node devices to top-level node devices. At the bottom-level node devices, the system periodically summarizes local business data and pushes the resulting statistics to its superior intermediate node devices. Intermediate node devices receive statistical data from the bottom-level devices through a data acquisition interface, store it in their local database, and use it for both local visualization and periodic statistical analysis of their own and lower-level data, pushing the results to the top-level node devices. Similarly, top-level node devices receive summarized data from intermediate nodes through a data acquisition interface, complete data storage, and then visualize the global data. This entire process involves hierarchical reporting and aggregation, ensuring that each level of node device can independently manage its local data while providing a unified summary view to its superiors, supporting efficient data monitoring and analysis across multi-level enterprise organizations.

[0052] Step 104: Send a detailed query request corresponding to the summary data item in the second summary data to the target lower-level node device, receive the original detailed data sent by the target lower-level node device in response to the detailed query request, and generate detailed display results. The target lower-level node device is either a direct lower-level node device of the intermediate node device or a cross-level lower-level node device.

[0053] Specifically, the target subordinate node device refers to the device to which the intermediate node device initiates a detailed query, including two categories: one is a direct subordinate node device with a direct cascading relationship to the intermediate node device (which can be either an intermediate node device or a bottom-level node device); the other is a cross-level subordinate node device that does not have a direct cascading relationship to the intermediate node device but belongs to its subordinate level (such as a subordinate node of a subordinate of an intermediate node device), thus breaking through the hierarchical limitation. The summary data items in the second summary data refer to the specific statistical indicator items (such as total assets, number of risk events, business completion volume, etc.) contained in the second summary data received by the intermediate node device and reported by the direct subordinate nodes, which serve as the basis for triggering the detailed query. A detailed query request is a request instruction initiated by the intermediate node device to the target subordinate node device for a specific summary data item to obtain the corresponding original data. The detailed query request may include all content such as the query data item identifier, the query time range, and the intermediate node device's identity verification information. The raw detailed data consists of unprocessed, native business data (such as specific asset ledgers, single risk event records, and detailed business operation logs) stored locally on the target lower-level node devices. This raw detailed data serves as the data source for the aggregated data items. The detailed data display results are visual data generated by intermediate node devices after receiving the raw detailed data and processing it according to preset formats (such as tables, lists, and charts), facilitating user viewing and analysis.

[0054] In some embodiments, when an intermediate node device needs to conduct in-depth analysis on a certain summary index (i.e., summary data item), it can select a specific summary data item (such as "high-risk asset quantity is 15") from the received second summary data, and based on the locally maintained global cascading topology, locate the target lower-level node device where the original detailed data corresponding to the data item is located. The target lower-level node device can be a direct lower-level node of the current intermediate node device, or a non-direct lower-level node across multiple levels. Subsequently, the intermediate node device initiates a structured detailed query request to the target lower-level node device, such as through a Representational State Transfer Application Programming Interface (RESTful API) or a gRPC Remote Procedure Call (gRPC), carrying data item identification, time range, etc. After receiving the detailed query request, the target lower-level node device retrieves the matching original detailed data (such as specific asset ID, location, responsible person, etc.) from the local database, and returns the original detailed data after encryption. After receiving the original detailed data, the intermediate node device parses, filters and formats the original detailed data, and finally generates a visual detailed display page for user viewing, realizing on-demand penetration query without pre-stored details and without dependence on intermediate forwarding, thereby effectively supporting deep supervision needs under multi-level organizations.

[0055] For example, if the direct lower-level node device of intermediate node device A (a first-level subsidiary company) is intermediate node device B (a second-level subsidiary company), and the direct lower-level node device of intermediate node device B is bottom-level node device C (a branch company). When a user clicks on the summary data item "branch company C asset total quantity 100" on the summary page of intermediate node device A to initiate a query: intermediate node device A generates a query request containing "asset total quantity", "last whole point period", and "device A identity verification code", directly locates the communication address of bottom-level node device C and sends the request; after verification by bottom-level node device C, the local original asset ledger (containing the model, purchase time, storage location, etc. of the 100 assets) is extracted and returned to intermediate node device A after encryption; intermediate node device A arranges the original detailed data into a standardized table and displays it on the summary page, and the user can directly view the specific information of each asset, realizing accurate traceability.

[0056] The cascade data management method provided in the application is applied to any intermediate node device in a cascade data management system, the cascade data management system comprising a top node device, at least one intermediate node device and at least one bottom node device, each intermediate node device being connected to one directly superior node device and at least one directly inferior node device. By periodically aggregating local business data, first aggregation data corresponding to a current period is obtained; second aggregation data reported by the directly inferior node device connected to the intermediate node device is periodically received, and the second aggregation data and the first aggregation data are aggregated, each intermediate node device periodically re-aggregates its local aggregation data and the aggregation data collected from all directly inferior node devices to obtain corresponding aggregated data; and the aggregated data is pushed to the directly superior node device connected to the intermediate node device, thereby reducing bandwidth occupation caused by full data transmission and realizing efficient convergence of data to the top node. When in-depth analysis of a certain aggregation item is required, a detailed query request corresponding to the aggregation data item in the second aggregation data is directly sent to the target inferior node device, original detailed data sent by the target inferior node device in response to the detailed query request is received, and a detailed display result is generated, thereby realizing direct connection penetration without pre-stored details and without dependence on layer-by-layer forwarding, the target inferior node device being a directly inferior node device or a cross-level inferior node device of the intermediate node device, all intermediate node devices and bottom node devices retaining original detailed data, guaranteeing local management autonomy, and the superior node device not needing to store massive details, thereby balancing the dual needs of distributed management and centralized supervision. Through the multi-level data aggregation reporting + on-demand detailed data checking dual-track mechanism, the technical problem that the existing technology cannot support in-depth penetration query of original details while efficiently aggregating multi-level data is accurately solved, thereby balancing the contradiction between management efficiency and management depth of multi-level data.

[0057] In some embodiments, before the step of periodically receiving the second aggregation data reported by the directly inferior node device connected to the intermediate node device, the method further comprises:

[0058] obtaining connection parameter information for establishing a connection relationship with the target node device, the connection parameter information comprising a network address, a port number and a cascade code, the cascade code being an identity authentication credential randomly generated by the cascade data management system, the cascade data management system comprising the target node device;

[0059] based on the connection parameter information, sequentially performing a plurality of security check sub-steps in a preset logical order;

[0060] after all the security check sub-steps are successfully passed, establishing a secure cascade connection between the intermediate node device and the target node device, obtaining a global cascade topology corresponding to the updated cascade data management system, the updated cascade data management system comprising the intermediate node device.

[0061] Specifically, the connection parameter information is core configuration data for the intermediate node device and the target node device to establish cascading connection, which can contain network address (cascading IP), port number, cascading code and other key information, and the connection parameter information is the basis for identity authentication and communication establishment. The target node device is the object device to which the intermediate node device intends to establish a cascading relationship, which can be the direct superior node device or the direct subordinate node device (including intermediate node and bottom layer node device) of the intermediate node device, and the target node device belongs to the component part of the cascading data management system. The network address is the unique network identifier of the target node device, such as IPv4 / IPv6 address, which is used to locate the communication position of the target node device in the private line network and ensure the accuracy of the data transmission path. The port number is a special cascading communication port opened on the target node device, which cooperates with the network address to realize the accurate positioning of "device + communication channel", and is used for data transmission and verification related to cascading connection. The cascading code is a series of unique character codes randomly generated by the cascading data management system, which can be used as the core credential for device identity authentication, supports manual refresh, and does not affect the established cascading relationship after update. The security verification sub-step is a series of verification processes before the establishment of cascading connection, which is executed in the preset logical order, including network connectivity verification, target node device legitimacy verification, cascading mode enablement verification, system time consistency verification, cascading code matching verification, and hierarchical relationship rationality verification. The secure cascading connection is an encrypted communication link established after full security verification, which realizes data transmission encryption and identity permission control based on private line network, and ensures the security and uniqueness of data interaction between devices. The global cascading topology is the overall architecture map recording all device cascading relationships in the cascading data management system, which contains device identification, hierarchical relationship, communication path and other information, and is automatically updated after connection establishment, providing topology support for subsequent data transmission and cross-level query.

[0062] In the cascade data management method of the present application, before the intermediate node device starts to periodically receive the second summary data reported by its direct subordinate node, the security connection establishment process between the intermediate node device (to-be-cascaded node device) and the target subordinate node needs to be completed first. As an example, the intermediate node device (to-be-cascaded node device) can enter the connection parameter information of the target node device (direct superior or direct subordinate node device) through the system interface as the cascade initiator, including the network address for positioning the device, the port number for special communication, and the unique identity authentication credential cascade code randomly generated by the system. After the connection parameter information is entered, a series of security checks are performed in a preset logical order: specifically, first, verify the dedicated line network connectivity to ensure normal communication between devices; then check whether the target node device is in the system whitelist and whether the cascade mode has been enabled; then compare the system time of the target node device and the intermediate node device (to-be-cascaded node device) to ensure that the deviation is within the threshold; the core verification is the cascade code consistency to verify the identity legitimacy; finally, check the hierarchical relationship to avoid circular cascade. After all the verification sub-steps pass, a dedicated secure cascade connection can be established based on the encryption protocol to ensure the security of subsequent data transmission. At the same time, the system automatically updates the global cascade topology, adds the hierarchy and communication information of the intermediate node device and the target node device, and forms a complete tree architecture map, providing legal and stable connection support for subsequent periodic reception of subordinate summary data, cross-level query and other operations, and avoiding illegal access and data security risks from the source.

[0063] In some embodiments, based on the connection parameter information, the step of sequentially performing a plurality of security check sub-steps in a preset logical order comprises:

[0064] sending a network connectivity performance detection request to the target node device through the network address and the port number;

[0065] In the case where the response information sent by the target node device in response to the network connectivity performance detection request is received within a preset time, the bidirectional data communication capability check is passed;

[0066] sending a cascade service detection request to the target node device through the network address and the port number; receiving response information sent by the target node device in response to the cascade service detection request, and determining whether the target node device has enabled the cascade service according to the response information;

[0067] In the case where it is determined that the target node device has enabled the cascade service, the cascade service state check is passed;

[0068] obtaining the system time stamp returned by the target node device, calculating the deviation value between the system time stamp and the current system time of the intermediate node device, and determining whether the deviation value is less than or equal to a preset time threshold;

[0069] If the deviation value is less than or equal to the preset time threshold, the system time consistency verification passes;

[0070] sending a concatenated code query request to the target node device; receiving the current concatenated code of the target node device sent by the target node device in response to the concatenated code query request, and performing consistency comparison on the concatenated code and the current concatenated code of the target node device to obtain a corresponding comparison result;

[0071] In the case of consistent comparison result, the concatenated code legality verification passes;

[0072] Based on the current concatenated topology of the locally stored concatenated data management system, it is judged whether there is any node in the concatenated path simultaneously serving as the superior and subordinate of another node after the intermediate node device is added as a node to the current concatenated topology;

[0073] In the case of no, the topology logic verification passes.

[0074] Specifically, the network connectivity performance detection request can be a lightweight alive detection request, such as an Internet Control Message Protocol (ICMP) ping or a Transmission Control Protocol Synchronize (TCP SYN), which is used to verify whether the target node device is reachable at the network level. The concatenated service detection request is a detection for a specific concatenated service port / interface of the target node device, such as GET / cascade / health, which is used to determine whether the concatenated function has been enabled. The topology logic verification is a verification based on the current concatenated topology, which checks whether there is a circular concatenation problem of "the same node serving as the superior and subordinate of another node" after the intermediate node device is added, to ensure that the concatenated architecture conforms to the "tree-like hierarchical" logic.

[0075] As an example, refer to Figure 5First, the intermediate node device can initiate a network connectivity performance detection request, such as a TCP SYN packet or a lightweight Hypertext Transfer Protocol (HTTP) GET request, through the network address and port number of the target node device. If a valid response returned by the target node device is received within a preset timeout time (for example, 3 seconds), it is determined that the two-way data communication capability check is passed, and it is confirmed that the underlying network link is available. Second, the intermediate node sends a dedicated cascade service detection request (such as calling the / api / cascade / health interface) to the same address and port, and parses the response information returned by the target node device. If it is explicitly identified that "cascade service is enabled" (such as the field "cascade_enabled": true) in the response, the cascade service state check is passed, and it is ensured that the target node device has the ability to participate in the cascade system. Third, the intermediate node device can extract the system timestamp returned by the target node device in the response, and calculate the deviation value of the system time between the target node device and the intermediate node device (the node device to be cascaded) in combination with the local sending and receiving time. If the deviation value does not exceed a preset time threshold (such as ±1 millisecond), the system time consistency check is passed, effectively preventing the risk of replay attacks or session invalidation caused by different system times. Subsequently, the intermediate node device sends a cascade code query request (such as GET / api / cascade / current-code) to the target node device, receives the current valid cascade code returned by the target node device, and strictly compares the cascade code input or configured by the user with the cascade code. Only when the two are completely consistent and not expired, the cascade code legality check is passed, thereby completing the identity authentication. Finally, the intermediate node device simulates the new topology relationship after connecting itself as a superior node to the target node device based on the locally stored current cascade topology (usually maintained in a directed acyclic graph structure), and performs a Depth-First Search (DFS) or topological sorting algorithm to detect whether there is any node that simultaneously serves as the superior and subordinate of another node in the cascade path (i.e., forms a loop). If the judgment result is "no", i.e., there is no loop risk, the topology logic check is passed. Only when all the above security check sub-steps are successfully completed in sequence, the system allows the establishment of an encrypted secure cascade connection, and writes the new relationship into the global cascade topology. This multi-level, sequentially dependent check mechanism builds a defense-in-depth system from five dimensions of network reachability, service availability, identity authenticity, time synchronization, and structure compliance, eliminating the risks of illegal device access, service misconnection, credential forgery, and topology loop, and laying a solid and reliable foundation for subsequent efficient, reliable, and secure periodic data aggregation and penetrating detail query.

[0076] In addition, after the secure cascade between the intermediate node device (to-be-cascaded node device) and the target node device is successfully established, the to-be-cascaded node device and all subordinate node devices of the to-be-cascaded node device are added in the overall cascade data management system to form a new cascade data management system. Referring to Figure 6 , Figure 6 The topological change process of the to-be-cascaded node device joining a new cluster in the cascade data management system is shown. Initially, the node device D, the node device F, and the node device G constitute a "cluster 1" (the original cascade data management system), the node device A is a top-level node device, the node device B and the node device C are direct subordinate node devices of the node device A, and the node device E and the node device H are direct subordinate node devices of the node device B. When the node device B establishes a cascade connection with the node device D (i.e., a to-be-cascaded node device), the system integrates the node device D and all subordinates (F, G) of the node device D into the original cluster to form a new cascade architecture, i.e., a "new cluster" (i.e., an updated cascade data management system). At this time, the node device D is accessed as a direct subordinate node device of the node device B, the subtree structure is completely retained, the original internal cascade relationship is unchanged, and the smooth merging of the sub-cluster is achieved.

[0077] In some embodiments, the step of sending a detailed query request corresponding to the summary data item in the second summary data to the target subordinate node device, receiving the original detailed data sent by the target subordinate node device in response to the detailed query request, and generating a detailed display result includes:

[0078] In response to the detailed query request for the summary data item in the second summary data, determining the node device corresponding to the summary data item as a target subordinate node device according to the locally pre-stored global cascade topology of the cascade data management system, the node device being a direct subordinate node device or a cross-level subordinate node device of the intermediate node device;

[0079] Initiating a remote call to the target subordinate node device to request to obtain the original detailed data associated with the summary data item;

[0080] Receiving the original detailed data returned by the target subordinate node device, and filling the original detailed data into the detailed data page corresponding to the summary data item to generate a detailed display result.

[0081] Specifically, the target subordinate node device is a data source node determined based on the global cascading topology and corresponding to the summary data item, including a direct subordinate node device of the intermediate node device (without hierarchical interval) and a cross-level subordinate node device (with an interval of one or more levels), and the target subordinate node device is a storage carrier of the original detailed data. The remote call is a remote data interaction protocol between the intermediate node device and the target subordinate node device, is initiated through an encrypted channel of a dedicated line network, does not need to be forwarded by an intermediate level, directly implements data request and response, and guarantees query efficiency and security. The detailed data page is a page module specially used for displaying detailed data in a visual interface of the intermediate node device, is associated with the summary data page, supports field filtering, sorting, exporting and the like, and provides an intuitive detailed viewing entry for a user.

[0082] As an example, reference is made to Figure 7 When the intermediate node device receives a detailed query request of a user for a summary data item (such as “high-risk asset quantity: 15”) in the second summary data, the system first accurately locates an actual device storing original detailed data of the summary data item according to the locally pre-stored global cascading topology, as a target subordinate node device; the target subordinate node device can be a direct subordinate (such as a city company) of the intermediate node device or a cross-level non-direct subordinate (such as a county or a branch device). Subsequently, the intermediate node initiates a remote call to the target subordinate node device based on the established secure cascading connection, such as through gRPC or RESTful API, requests to obtain original detailed data associated with the summary data item, such as specific asset ID, location, risk details and the like, and the calling parameters can include index type, time period and the like context information to ensure data consistency. After the target subordinate node device receives the detailed query request, the matching original detailed data is retrieved from the local database and returned. After the intermediate node receives the returned original detailed data, the original detailed data is structured and automatically filled into a pre-configured detailed data page (such as a table or a list view), and finally a visual detailed display result is generated for the user to view. Through topology-driven accurate positioning and cross-level remote calling, the detailed data of the subordinate node device is realized without intermediate forwarding and does not depend on on-demand penetration query of full data synchronization, which guarantees the query efficiency and data accuracy of the detailed data and supports cross-level deep drilling, and can effectively meet the fine management needs of the group-type enterprise for multi-level data assets.

[0083] In some embodiments, after the step of receiving the original detailed data sent by the target subordinate node device in response to the detailed query request and generating the detailed display result, the method further includes:

[0084] In response to the locally generated first cascading relationship release instruction, the cascading connection between the target exit node device and the direct superior node device is terminated, and the target exit node device is the intermediate node device;

[0085] The first data deletion instruction is sent to a direct superior node device, and the first data deletion instruction is used to instruct the direct superior node device to delete relevant summary data items related to the target exit node device. The first data deletion instruction is forwarded to the top node device in a cascade path step by step in a direction, until the top node device is reached, so that the relevant summary data items related to the target exit node device in all superior node devices of the target exit node device are cleared.

[0086] Specifically, the first cascade relationship release instruction is an active release cascade relationship instruction generated locally by the target exit node device (intermediate node device), and the trigger condition can include that the device no longer needs to report / receive data, exits the cascade architecture, etc. The first cascade relationship release instruction is the core trigger signal to start the cascade release process. The target exit node device is an intermediate node device that initiates the release of the cascade relationship, i.e., a device that intends to exit the cascade architecture, which will no longer participate in the data summary reporting and receiving process after exiting. The direct superior node device is the last level device (which can be a top node device or other intermediate node device) that has a direct cascade relationship with the target exit node device, and is the direct interaction object of the cascade connection release. The first data deletion instruction is an instruction sent by the target exit node device to instruct the superior node to delete relevant data, which can include the target exit node device identifier, the summary data range to be deleted, and other core information to ensure the accuracy of data deletion. The relevant summary data items are all aggregated data stored in the superior node devices at each level, which are related to the target exit node device (including the aggregated data reported by the target exit node device itself, and the associated aggregated data containing the subordinate level data). The cascade path is a communication path in the cascade data management system from the target exit node device to the top node device in layers upwards, and the cascade path is the only channel for data deletion instruction forwarding and data clearing.

[0087] As an example, after the target exit node device (intermediate node device) locally generates the first cascading relationship release instruction, the system immediately responds and terminates the secure cascading connection between the target exit node device and the direct superior node device, and stops the data transceiving interaction between the target exit node device and the direct superior node device. Subsequently, the target exit node device sends a first data deletion instruction to the direct superior node, and after the direct superior node of the target exit node device receives the first data deletion instruction, the relevant summary data items related to the target exit node device stored locally are accurately deleted, and the first data deletion instruction is forwarded to the higher-level nodes in sequence along the cascading path until the top node device. The top node no longer forwards after completing local cleaning, thereby ensuring that the summary data related to the exit device is completely and automatically cleared in all superior nodes from the direct superior to the top.

[0088] Exemplarily, if the architecture of the cascading data management system is "top node device (head office) → intermediate node device A (first-level subsidiary) → intermediate node device B (second-level subsidiary, target exit node device) → bottom node device C (branch)", when the intermediate node device B generates the first cascading relationship release instruction, the intermediate node device B (target exit node device) terminates the cascading connection with the direct superior intermediate node device A and sends a first data deletion instruction to the intermediate node device A. The intermediate node device A deletes the relevant summary data items related to the intermediate node device B, and forwards the first data deletion instruction to the top node device; the top node device deletes the relevant summary data items related to the intermediate node device B, and completes the full-link cleaning. Finally, there is no relevant data of the intermediate node device B remaining in the intermediate node device A and the top node device, ensuring the accuracy of subsequent summary data.

[0089] In some embodiments, after the step of receiving the original detailed data sent by the target lower-level node device in response to the detailed query request and generating a detailed display result, the method further comprises:

[0090] receiving a second cascading relationship release instruction sent by the target exit node device, and in response to the second cascading relationship release instruction, terminating the cascading connection between the intermediate node device and the target exit node device, the target exit node device being a direct lower-level node device connected by the intermediate node device;

[0091] generating a second data deletion instruction, and in response to the second data deletion instruction, deleting the relevant summary data items related to the target exit node device stored locally;

[0092] The second data deletion instruction is sent to the direct superior node device, and the second data deletion instruction is forwarded to the top node device step by step along the cascade path, so that the relevant summary data items related to the target exit node device in all superior node devices of the target exit node device are cleared.

[0093] Specifically, the second cascade relationship release instruction is an instruction initiated by the target exit node device (the direct inferior node device of the intermediate node device) for requesting to release the cascade relationship with the intermediate node device. The target exit node device is a node device that intends to release the cascade relationship, and here refers to the inferior node device (which can be an intermediate node or a bottom node device) that has a direct cascade relationship with the intermediate node device, and after exiting, no longer reports data to the intermediate node device, and no longer responds to the query request of the intermediate node device. The second data deletion instruction is an instruction generated by the intermediate node device for instructing itself and all superior nodes to delete relevant data, which can include the identification of the target exit node device, the range of summary data to be deleted (such as associated aggregation data, subordinate hierarchical associated data, etc.).

[0094] As an example, when the intermediate node device receives the second cascade relationship release instruction sent by a direct inferior node device (i.e. the target exit node device) of the intermediate node device, the intermediate node device first verifies the legality of the second cascade relationship release instruction, and immediately terminates the secure cascade connection between the intermediate node device and the target exit node device, and stops receiving subsequent data reports of the target exit node device. Subsequently, the intermediate node device generates a second data deletion instruction, which can include the unique identification of the target exit node device, and deletes all relevant summary data items (such as the second summary data reported by the target exit node device and the part participating in the aggregation) contributed by the target exit node device in the local database. Then, the intermediate node device sends the second data deletion instruction to the direct superior node device of the intermediate node device through the established secure channel; after receiving the second data deletion instruction, the direct superior node device also performs the cleaning operation of the local relevant summary data, and judges whether it is a top node device or not - if it is not a top node device, it continues to forward the second data deletion instruction to the next level node device along the cascade path. This process is repeated step by step until the second data deletion instruction reaches the top node device, and finally realizes that the relevant summary data items related to the target exit node device are completely and automatically cleared from the intermediate node to all superior nodes of the top node, effectively coping with the scene of branch exit or withdrawal, and guaranteeing the data consistency and regulatory reliability of the cascade system under the dynamic organizational change.

[0095] Exemplarily, if the architecture of the cascaded data management system is "top node device (headquarters) -> intermediate node device A (first-level subsidiary) -> target exit node device B (second-level subsidiary, direct subordinate) -> bottom node device C (branch office)": when the target exit node device B sends a second cascaded relationship release instruction, the intermediate node device A receives the second cascaded relationship release instruction, terminates the cascaded connection with the target exit node device B, and at the same time generates a second data deletion instruction to delete the relevant summary data items related to the target exit node device B stored locally in the intermediate node device A. The intermediate node device A forwards the second data deletion instruction to the top node, and the top node deletes the relevant summary data items related to the target exit node device B, completing the full-link cleaning of the relevant data related to the target exit node device B; if there is network fluctuation during forwarding, the intermediate node device A triggers a retry, and if the retry fails, the instruction is temporarily stored, and after the network recovers, it is pushed again to ensure that there is no data residue.

[0096] In some embodiments, when it is detected that the data deletion process fails due to network anomalies, a retry process is started;

[0097] If the retry still fails and the number of remaining retries is exhausted, the second data deletion instruction is stored persistently in the local memory;

[0098] When it is detected that the network connection is restored, the second data deletion instruction that has been persisted is automatically reattempted to be pushed to the direct superior node device.

[0099] As an example, to ensure the reliability of the cascaded data management system in the dynamic node exit process, when the intermediate node device pushes the second data deletion instruction to its direct superior node device, if it is detected that the sending fails due to network anomalies (such as connection timeout, service unreachable), a preset retry process is immediately started. The retry process can use an exponential backoff strategy (for example, the first retry after 1 second, the second retry after 2 seconds, the third retry after 4 seconds), and checks the current network state before each retry; if the number of retries reaches the upper limit (such as 3 times) and still fails to send successfully, the second data deletion instruction is stored persistently in the local secure memory queue or the pending task table of the local database in a structured format (such as JSON), and is marked as "to be retransmitted". Thereafter, the intermediate node device continuously monitors the network connection state with the superior node, and as soon as it detects that the network is restored, such as the heartbeat probe succeeds or the API call returns to normal, the system automatically triggers the retransmission mechanism, reads the unfinished deletion instruction from the persistent storage, and reattempts to push it to the direct superior node device. After receiving the instruction, the superior node continues to execute the local data cleaning and forwarding logic, thereby ensuring that even in an unstable network environment, the relevant summary data of the exit node can be finally completely cleaned up in the full link.

[0100] In some embodiments, after completing the global data cleaning, the target exit node device and all subordinate node devices of the target exit node device are removed from the cascading data management system;

[0101] For the target exit node device and all subordinate node devices of the target exit node device, the target exit node device is taken as an independent top node device, and an independent cascading sub-cluster is formed according to the original subordinate relationship of each node device, and the cascading data aggregation and query function within the cascading sub-cluster is maintained to normally operate.

[0102] As an example, after the global data cleaning related to the target exit node device is completed, the cascading data management system automatically updates the global cascading topology, removes the target exit node device and all subordinate node devices of the target exit node device from the original cascading architecture, eliminates all association relationships with the original cluster, and ensures that the original cluster level logic is clear and the data is pure. At the same time, the system takes the target exit node device as an independent top node, retains the original subordinate relationship of each node subordinate to it, and automatically builds an independent cascading sub-cluster. The cascading sub-cluster inherits the original cascading data aggregation mechanism (subordinate nodes regularly report aggregated data, superior nodes aggregate and transmit) and detailed query function (superior nodes remotely call to query details of subordinate nodes, supporting cross-level penetration), and can maintain the normal operation of internal data flow and management and control function without additional configuration. Through local topology snapshot replication, role redefinition (re-mapping the original intermediate / bottom node in the sub-cluster as a top / middle / bottom node) and communication domain isolation implementation, the architecture purity and data accuracy of the original cascading data management system are ensured, and the target exit node and its subordinate nodes are prevented from interrupting the business due to the disconnection from the original cluster, achieving the effect of architecture splitting without interrupting the business, and balancing the group management needs and branch business continuity.

[0103] Exemplarily, referring to Figure 8 , Figure 8 The process of device exit and formation of an independent cascading sub-cluster in the cascading data management system is shown. Initially, node device B is connected to top node device A as an intermediate node device, and its subordinate nodes include node device D and node device E. Node device D and node device F, node device G form "cluster 1", and device E and H form "cluster 2". When node device D and node device E exit from the original cascading data management system, the system performs global data cleaning and removes node device D and node device E and all subordinate node devices (F, G, H) of node device D and node device E from the main cluster (cascading data management system). Subsequently, taking node device D and node device E as new independent top node devices, according to the original internal superior-inferior relationship, "cluster 1" (i.e. cascading sub-cluster) and "cluster 2" (i.e. cascading sub-cluster) are respectively rebuilt, and the cascading data aggregation and detailed query function within each cluster is maintained to normally operate.

[0104] In some embodiments, the application further provides a cascaded data management method, applied to a top node device in a cascaded data management system, the cascaded data management system comprising one top node device, at least one intermediate node device, and at least one bottom node device, each intermediate node device being connected to at least one directly subordinate node device, the cascaded data management method comprising:

[0105] periodically receiving third summary data reported by the directly subordinate node devices connected to the top node device, sending a second detailed query request corresponding to a summary data item in the third summary data to a second target subordinate node device, receiving second raw detailed data sent by the second target subordinate node device in response to the second detailed query request and generating a second detailed display result, the second target subordinate node device being a directly subordinate node device or a cross-level subordinate node device of the top node device.

[0106] In some embodiments, the application further provides a cascaded data management method, applied to any bottom node device in a cascaded data management system, the cascaded data management system comprising one top node device, at least one intermediate node device, and at least one bottom node device, each bottom node device being connected to one directly superior node device, the cascaded data management method comprising:

[0107] periodically summarizing local business data to obtain fourth summary data corresponding to a current period, and pushing the fourth summary data to the directly superior node device connected to the bottom node device.

[0108] In some embodiments, the application further provides another cascaded data management method, applied to a cascaded data management system, when the cascaded data management system comprises only two levels of node devices, the cascaded data management system comprising one top node device and at least one bottom node device, each bottom node device being connected to the top node device, the cascaded data management method comprising:

[0109] periodically summarizing local business data to obtain fifth summary data corresponding to a current period, pushing the fifth summary data to the top node device connected to the bottom node device, periodically receiving the fifth summary data reported by the connected bottom node device, sending a third detailed query request corresponding to a summary data item in the fifth summary data to a target bottom node device, receiving third raw detailed data sent by the target bottom node device in response to the third detailed query request and generating a third detailed display result, the bottom node device comprising the target bottom node device.

[0110] It should be noted that the above examples are only used for understanding the present application and do not constitute a limitation on the cascade data management method of the present application, and more forms of simple transformation based on this technical concept are within the protection scope of the present application.

[0111] The present application also provides a cascade data management device, please refer to Figure 9 , the cascade data management device comprises:

[0112] The data aggregation module 901 is configured to periodically aggregate the local business data to obtain the first aggregated data corresponding to the current period;

[0113] The data aggregation module 902 is configured to periodically receive the second aggregated data reported by the directly subordinate node device connected to the intermediate node device, and aggregate the second aggregated data and the first aggregated data to obtain the corresponding aggregated data;

[0114] The data transmission module 903 is configured to push the aggregated data to the directly superior node device connected to the intermediate node device;

[0115] The detailed data query module 904 is configured to send a detailed query request corresponding to the aggregated data item in the second aggregated data to the target subordinate node device, receive the original detailed data sent by the target subordinate node device in response to the detailed query request and generate a detailed display result, and the target subordinate node device is a directly subordinate node device or a cross-level subordinate node device of the intermediate node device.

[0116] The cascade data management device provided by the present application adopts the cascade data management method in the above embodiment, which can solve the technical problem that the prior art cannot support deep penetration query of original detailed data while ensuring efficient aggregation of multi-level data. Compared with the prior art, the cascade data management device provided by the present application has the same beneficial effects as the cascade data management method provided by the above embodiment, and other technical features in the cascade data management device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0117] The present application provides a cascade data management device, which comprises at least one processor and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the cascade data management method in the above embodiment one.

[0118] The following refers to Figure 10This document illustrates a structural diagram of a cascaded data management device suitable for implementing embodiments of this application. The cascaded data management device in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), tablet computers (PADs), portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 10 The cascaded data management device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0119] like Figure 10 As shown, the cascaded data management device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The random access memory 1004 also stores various programs and data required for the operation of the cascaded data management device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the cascaded data management device to communicate wirelessly or wiredly with other devices to exchange data. Although a cascaded data management device with various systems is shown in the figure, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0120] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program codes for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiments disclosed in the present application are executed.

[0121] The cascade data management device provided by the present application adopts the cascade data management method in the above-mentioned embodiments, and can solve the technical problem that the prior art cannot support deep penetration query on original detailed data while ensuring efficient aggregation of multi-level data. Compared with the prior art, the cascade data management device provided by the present application has the same beneficial effects as the cascade data management method provided by the above-mentioned embodiments, and other technical features in the cascade data management device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0122] It should be understood that various parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0123] The above is merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0124] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for executing the cascade data management method in the above-mentioned embodiments.

[0125] The computer readable storage medium provided in the application may be, for example, a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, system, or device, or any combination of the above. More specific examples of the computer readable storage medium may include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiment, the computer readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system, or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency: radio frequency), and the like, or any suitable combination of the above.

[0126] The computer readable storage medium described above may be contained in the cascaded data management device, or may exist separately without being assembled into the cascaded data management device.

[0127] The computer readable storage medium described above carries one or more programs, when the one or more programs are executed by the cascaded data management device, the cascaded data management device: periodically aggregates local business data to obtain first aggregation data corresponding to a current period; periodically receives second aggregation data reported by a directly subordinate node device connected to the intermediate node device, and aggregates the second aggregation data and the first aggregation data to obtain aggregation data; pushes the aggregation data to a directly superior node device connected to the intermediate node device; sends a detailed query request corresponding to an aggregation data item in the second aggregation data to a target subordinate node device, receives original detailed data sent by the target subordinate node device in response to the detailed query request and generates a detailed display result, and the target subordinate node device is a directly subordinate node device or a cross-level subordinate node device of the intermediate node device.

[0128] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0129] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may

[0130] The modules involved in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0131] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e., computer programs) for executing the above-mentioned cascade data management method, and can solve the technical problem that the prior art cannot support deep penetration query on original detailed data while ensuring efficient aggregation of multi-level data. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the cascade data management method provided by the above-mentioned embodiments, and will not be described here.

[0132] The application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the cascade data management method as described above.

[0133] The computer program product provided by the application can solve the technical problem that the prior art cannot support deep penetration query of original detailed data while ensuring efficient aggregation of multi-level data. Compared with the prior art, the beneficial effects of the computer program product provided by the application are the same as those of the cascade data management method provided by the above-mentioned embodiments, and are not described here.

[0134] The above only describes some embodiments of the application, and does not limit the patent scope of the application. Any equivalent structural transformation, direct / indirect application in other related technical fields, or direct / indirect application in other related technical fields based on the technical concept of the application and the content of the specification and drawings are included in the patent protection scope of the application.

Claims

1. A cascaded data management method, characterized in that, The method is applied to any intermediate node device in a cascaded data management system, wherein the cascaded data management system includes a top-level node device, at least one intermediate node device, and at least one bottom-level node device, and each intermediate node device is connected to a direct superior node device and at least one direct subordinate node device. The local business data is periodically aggregated to obtain the first aggregated data for the current period. The system periodically receives the second summary data reported by the direct subordinate node device connected to the intermediate node device, and aggregates the second summary data and the first summary data to obtain the corresponding aggregated data. The aggregated data is pushed to the direct parent node device connected to the intermediate node device; Send a detailed query request corresponding to the summary data item in the second summary data to the target lower-level node device, receive the original detailed data sent by the target lower-level node device in response to the detailed query request and generate a detailed display result, wherein the target lower-level node device is the direct lower-level node device or the cross-level lower-level node device of the intermediate node device; Prior to the step of periodically receiving the second aggregated data reported by the direct subordinate node device connected to the intermediate node device, the method further includes: Obtain connection parameter information for establishing a connection with the target node device. The connection parameter information includes network address, port number, and concatenation code. The concatenation code is an authentication credential randomly generated by the concatenation data management system, which includes the target node device. Based on the connection parameter information, multiple security verification sub-steps are executed sequentially according to a preset logical order; After all the security verification sub-steps are successfully passed, a secure cascading connection is established between the intermediate node device and the target node device to obtain the updated global cascading topology corresponding to the cascading data management system. The updated cascading data management system includes the intermediate node device.

2. The cascading data management method as described in claim 1, characterized in that, The step of executing multiple security verification sub-steps sequentially according to a preset logical order based on the connection parameter information includes: Send a network connectivity performance detection request to the target node device using the network address and the port number; If the bidirectional data communication capability verification is passed when the response information sent by the target node device in response to the network connectivity performance detection request is received within a preset time, the bidirectional data communication capability verification is passed. Send a cascading service probe request to the target node device using the network address and the port number; receive the response information sent by the target node device in response to the cascading service probe request, and determine whether the target node device has enabled cascading service based on the response information; If it is determined that the target node device has enabled the cascading service, the cascading service status verification passes. Obtain the system timestamp returned by the target node device, calculate the deviation between the system timestamp and the current system time of the intermediate node device, and determine whether the deviation is less than or equal to a preset time threshold. If the deviation value is less than or equal to the preset time threshold, the system time consistency check passes. Send a concatenation code query request to the target node device; receive the target node device's current concatenation code sent in response to the concatenation code query request, and perform a consistency comparison between the concatenation code and the target node device's current concatenation code to obtain the corresponding comparison result; If the comparison results are consistent, the concatenation code validity check passes. Based on the current cascading topology corresponding to the cascading data management system stored locally, determine whether, after adding the intermediate node device as a node to the current cascading topology, any node in the cascading path simultaneously serves as both the superior and inferior of another node. If the result is negative, the topology logic verification passes.

3. The cascading data management method as described in claim 1, characterized in that, The steps of sending a detailed query request corresponding to the summary data item in the second summary data to the target lower-level node device, receiving the original detailed data sent by the target lower-level node device in response to the detailed query request, and generating a detailed display result include: In response to the detailed query request for the summary data item in the second summary data, the node device corresponding to the summary data item is determined as the target lower-level node device according to the global cascading topology corresponding to the cascading data management system stored locally. The node device is the direct lower-level node device or the cross-level lower-level node device of the intermediate node device. Initiate a remote call to the target lower-level node device to request the original detailed data associated with the summary data item; Receive the original detailed data returned by the target lower-level node device, and fill the detailed data page corresponding to the summary data item with the original detailed data to generate the detailed display result.

4. The cascading data management method as described in claim 1, characterized in that, After the step of receiving the raw detail data sent by the target lower-level node device in response to the detail query request and generating the detail display result, the method further includes: In response to the locally generated first cascading relationship release command, the cascading connection between the target exit node device and the direct parent node device is terminated, wherein the target exit node device is the intermediate node device; A first data deletion instruction is sent to the direct superior node device. The first data deletion instruction is used to instruct the direct superior node device to delete the relevant summary data items related to the target exiting node device. The first data deletion instruction is forwarded level by level along the cascading path towards the top-level node device until it reaches the top-level node device, so that the relevant summary data items related to the target exiting node device are cleared in all superior node devices of the target exiting node device.

5. The cascading data management method as described in claim 1, characterized in that, After the step of receiving the raw detail data sent by the target lower-level node device in response to the detail query request and generating the detail display result, the method further includes: Receive a second cascading relationship termination instruction sent by the target exit node device, and in response to the second cascading relationship termination instruction, terminate the cascading connection between the intermediate node device and the target exit node device, wherein the target exit node device is the direct downstream node device connected to the intermediate node device; Generate a second data deletion instruction, and in response to the second data deletion instruction, delete the relevant summary data items related to the target exit node device stored locally; The second data deletion instruction is sent to the direct superior node device and forwarded to the top-level node device along the cascading path, so that the relevant summary data items related to the target exiting node device are cleared in all superior node devices of the target exiting node device.

6. The cascading data management method as described in claim 5, characterized in that, Also includes: When a data deletion process fails due to a network anomaly, a retry process is initiated. If the retry fails and the remaining retry count is exhausted, the second data deletion instruction will be persistently stored in local memory. When the network connection is detected to be restored, the persistent second data deletion command is automatically retried and pushed to the direct parent node device.

7. The cascaded data management method as described in any one of claims 4 to 6, characterized in that, Also includes: After completing the global data cleanup, the target exit node device and all its subordinate node devices are removed from the cascaded data management system. For the target exit node device and all its subordinate node devices, the target exit node device is used as an independent top-level node device. Based on the original subordinate relationships of each node device, an independent cascaded sub-cluster is formed, and the cascaded data aggregation and query functions within the cascaded sub-cluster are maintained to operate normally.

8. A cascaded data management device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the cascaded data management method as described in any one of claims 1 to 7.

9. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the cascaded data management method as described in any one of claims 1 to 7.

Images