An Edge Node Aggregated Data Repair Method, Device, and Storage Medium

Abstract

The present invention provides a method, apparatus and storage medium for repairing aggregated data of edge nodes. The method includes: loading the aggregation configuration of the original metrics of the device and its original device attributes; obtaining the original metrics of the device according to the aggregation configuration, and performing expansion to obtain the extended attributes of the device, and performing repair processing on the original metrics of the device and / or the extended attributes of the device to generate the original old data and the original new data of the device; calculating the difference of the aggregation strategy for the original old data and the original new data of the device according to the preset aggregation configuration to obtain the repair value of the aggregation dimension; writing the repair value of the aggregation dimension into the preset time series database, which can calculate which high-dimensional data are affected by the attributes to be modified of the device, with unified policy repair input and output, and only calculating for the device-related attributes and metrics affected, solving the problems of large data volume and high resource consumption caused by offline aggregation of all devices, and greatly improving the bandwidth repair efficiency.

Description

Technical Field

[0001] The present invention mainly relates to the technical field of edge node data processing, and particularly relates to a method, device and storage medium for repairing aggregated data of edge nodes. Background Art

[0002] In a large-scale edge node network, whether to store fine-grained raw data, high-dimensional aggregated data, or a combination of both can be determined according to the actual situation. The characteristics of raw data are: detailed, convenient for traceability, but the data volume is too large, making it inconvenient to view high-dimensional data. The characteristics of aggregated data are: convenient for statistical analysis and trend prediction, but part of the accuracy will be lost and the real-time performance is limited.

[0003] In a large-scale edge node network, each device usually collects various metrics (such as 1-minute granular network card bandwidth, service bandwidth, CPU utilization rate, TCP retransmission ratio, etc.) in real time and reports them to the center. The data format of various metrics is roughly as follows: timestamp, device identifier (i.e., SN), network card name, network card bandwidth. Then, the center aggregates various-dimensional data (such as 1m granular bandwidth of a certain node, 5m granular bandwidth, 1m granular TCP retransmission ratio, etc.) in real time according to the labels of the devices (such as operators, nodes, etc., and the labels are usually obtained by the device management center). In addition, considering the complexity of the network, delayed data will be generated, and offline aggregation is used for supplementation. Moreover, this type of data is generally stored in a time-series database, whose characteristic is that time is the main index and generally will not be deleted, only appended and updated.

[0004] During daily operation and maintenance, there will be situations such as incorrect device attributes. If not updated in time, it will lead to inaccurate aggregated data, and there may even be abnormal data caused by adjustments to the acquisition program. The currently commonly used method is to recalculate and overwrite all the data through offline aggregation. The disadvantage of this solution is that most devices are recalculated, consuming a lot of resources. At the same time, there will also be a hidden problem. If a certain attribute value cannot be overwritten, it is necessary to first modify the data to 0 (considering the low deletion efficiency of the time-series database) and then re-aggregate, resulting in low data processing efficiency. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a method, device and storage medium for repairing aggregated data of edge nodes in view of the deficiencies of the prior art.

[0006] The technical solution of the present invention to solve the above technical problem is as follows: A method for repairing aggregated data of edge nodes includes the following steps:

[0007] Load the aggregation configuration of the device's original metrics and its original device attributes;

[0008] Obtain the original device metrics according to the aggregation configuration, expand the original device attributes to obtain the extended device attributes, and perform repair processing on the original device metrics and / or the extended device attributes to generate the original old device data and the original new device data;

[0009] Calculate the aggregation policy difference between the original old device data and the original new device data according to the preset aggregation configuration to obtain the repair value of the aggregation dimension;

[0010] Write the repair value of the aggregation dimension into the preset time series database.

[0011] Based on the above technical solutions, the present invention can also be improved as follows.

[0012] Further, the obtaining the original device metrics according to the aggregation configuration, expanding the original device attributes to obtain the extended device attributes, and performing repair processing on the original device metrics and / or the extended device attributes to obtain the repaired original old device data and the repaired original new device data includes:

[0013] Parse the aggregation configuration according to the set format, and query the original device metrics through the parsing result;

[0014] Expand the original device attributes through the device management center to obtain the extended device attributes;

[0015] Perform repair processing on the original device metrics and / or the extended device attributes according to the preset repair policy rules to generate the original old device data and the original new device data.

[0016] Further, the parsing the aggregation configuration according to the set format and querying the original device metrics through the parsing result includes:

[0017] Parse the aggregation configuration according to the combination of the device identifier and the time range, and query the original device metrics through the parsing results of the device identifier and the time range.

[0018] Further, the performing repair processing on the original device metrics and / or the extended device attributes according to the preset repair policy rules to generate the original old device data and the original new device data includes:

[0019] When the preset repair policy rule is an attribute change policy, perform attribute change processing on the original device metrics and / or the extended device attributes to generate the original old device data corresponding before the attribute change processing, and generate the original new device data corresponding after the attribute change processing;

[0020] When the preset repair strategy rule is the clearing strategy, clear the original device metrics and / or the extended device attributes, generate the original old device data corresponding before the clearing process, and generate the original new device data corresponding after the clearing process.

[0021] Furthermore, perform an aggregation policy difference calculation on the original old device data and the original new device data according to the preset aggregation configuration to obtain the repair value of the aggregation dimension, specifically:

[0022] Calculate the aggregated old data corresponding to the original old device data according to the preset aggregation configuration, and calculate the aggregated new data corresponding to the original new device data according to the preset aggregation configuration, and subtract the aggregated old data from the aggregated new data to obtain the aggregated data difference;

[0023] Import the aggregated data of the aggregation configuration, and subtract the aggregated data difference from the aggregated data to obtain the repair value of the aggregation dimension.

[0024] Another technical solution of the present invention to solve the above technical problems is as follows: An edge node aggregated data repair device includes an aggregation configuration loading module, a policy repair module, an incremental repair module, and a writing module;

[0025] The aggregation configuration loading module is used to load the aggregation configuration of the original device metrics and its original device attributes;

[0026] The policy repair module is used to obtain the original device metrics according to the aggregation configuration, expand the original device attributes to obtain the extended device attributes, perform repair processing on the original device metrics and / or the extended device attributes, and generate the original old device data and the original new device data;

[0027] The incremental repair module is used to perform an aggregation policy difference calculation on the original old device data and the original new device data according to the preset aggregation configuration to obtain the repair value of the aggregation dimension

[0028] The writing module is used to write the repair value of the aggregation dimension into the preset time series database.

[0029] The beneficial effects of the present invention are: By loading the aggregation configuration, obtaining the original device metrics, expanding the original device attributes to obtain the extended device attributes, performing repair processing on the original device metrics and the extended device attributes, obtaining the original old device data and the original new device data, and performing an aggregation policy difference calculation on them, so as to calculate which high-dimensional data are affected by the attributes to be modified of the device, with unified policy repair input and output, and only calculating for the device-related attributes and metrics affected, solving the problems of large data volume and high resource consumption caused by full-scale device offline aggregation, and greatly improving the bandwidth repair efficiency. Description of the Drawings

[0030] Figure 1 Flow schematic diagram of the edge node aggregated data repair method provided by the embodiment of the present invention;

[0031] Figure 2 Flow schematic diagram of the incremental repair provided by the embodiment of the present invention;

[0032] Figure 3 Flow schematic diagram of the aggregated data repair method under multiple aggregation configurations provided by the embodiment of the present invention;

[0033] Figure 4 Module block diagram of the edge node aggregated data repair device provided by the embodiment of the present invention. Detailed implementation manners

[0034] The principles and features of the present invention are described below with reference to the accompanying drawings. The examples given are only used to explain the present invention and are not used to limit the scope of the present invention.

[0035] As Figure 1 shown, the edge node aggregated data repair method provided by the embodiment of the present invention includes the following steps:

[0036] S1. Load the aggregation configuration of the original device metrics and its original device attributes; It should be understood that: when loading the aggregation configuration, only process the original data if not required.

[0037] S2. Obtain the original device metrics according to the aggregation configuration, expand the original device attributes to obtain the device extended attributes, and perform repair processing on the original device metrics and / or the device extended attributes to generate the original old device data and the original new device data.

[0038] S3. Calculate the difference of the aggregation strategy for the original old device data and the original new device data according to the preset aggregation configuration to obtain the repair value of the aggregation dimension.

[0039] S4. Write the repair value of the aggregation dimension into the preset time series database.

[0040] In this embodiment, by loading the aggregation configuration, the original device metrics are obtained, and the original device attributes are extended to obtain the extended device attributes. The original device metrics and the extended device attributes are repaired to obtain the original old device data and the original new device data, and the difference calculation of the aggregation policy is performed on them, so as to calculate which high-dimensional data are affected by the attributes to be modified of the device. The unified policy repair input and output only calculate for the affected device-related attributes and metrics, solving the problems of large data volume and high resource consumption caused by the offline aggregation of all devices, and greatly improving the bandwidth repair efficiency. This method has the characteristics of efficient edge node aggregated data repair through flexible and extensible repair strategies.

[0041] Optionally, obtaining the original device metrics according to the aggregation configuration, extending the original device attributes to obtain the extended device attributes, and performing repair processing on the original device metrics and / or the extended device attributes to obtain the original old repaired device data and the original new repaired device data includes:

[0042] Parsing the aggregation configuration in a set format, and querying the original device metrics through the parsing result;

[0043] Extending the original device attributes through the device management center to obtain the extended device attributes;

[0044] Performing repair processing on the original device metrics and / or the extended device attributes according to the preset repair policy rules to generate the original old device data and the original new device data.

[0045] Optionally, the parsing the aggregation configuration in a set format and querying the original device metrics through the parsing result includes:

[0046] Parsing the aggregation configuration according to the combination mode of the device identifier and the time range, and querying the original device metrics through the parsing results of the device identifier and the time range.

[0047] The performing repair processing on the original device metrics and / or the extended device attributes according to the preset repair policy rules to generate the original old device data and the original new device data includes:

[0048] When the preset repair policy rule is the attribute change policy, performing attribute change processing on the original device metrics and / or the extended device attributes to generate the original old device data corresponding before the attribute change processing, and generating the original new device data corresponding after the attribute change processing;

[0049] When the preset repair policy rule is the clearing policy, clear the original device metrics and / or the extended device attributes, generate the original old device data corresponding before the clearing process, and generate the original new device data corresponding after the clearing process.

[0050] Specifically, in the first step, parse the input aggregation configuration. Each policy rule is input and output in a unified format. The aggregation configuration includes: repair policy name, SN (device identifier), time range, target attribute, and attribute value which are optional;

[0051] For example:

[0052] The information for input repair is in the following format:

[0053] Repair rule: SN: [start time, end time, {target attribute: target attribute value}].

[0054] In the second step, query the original device metrics through "SN + time range", and then expand the attributes of the device (i.e., extended device attributes) according to the original device attributes through the device management center;

[0055] For example:

[0056] Obtain the original device data and attributes:

[0057] Query the original device data according to the device identifier SN + start + end time, and then expand the attributes of the device through the device management center.

[0058] In the third step, according to the rules of the repair policy, such as clearing to zero or attribute change, repair the original device metrics and their attributes, and generate two copies of data: the original old and the original new device data.

[0059] This process is specifically as follows:

[0060] Repair the original data according to the rules;

[0061] Common rules for policy repair: clearing to zero or attribute change, default is clearing to zero; (illustrated uniformly according to the line protocol format of influxdb), all policies use network card bandwidth:

[0062] device_netsn = sn1, area = Beijing, isp = Telecom, interface = eth0tx = 100, rx = 501693450800.

[0063] When the preset repair policy rule is the attribute change policy:

[0064] Attribute change policy: The rule definition format is as follows:

[0065] Attribute change: {

[0066] SN: [start time, end time, {target attribute: target attribute value}];

[0067] }。

[0068] For example, change the target attribute operator of sn1 with timestamp 1693450800 to China Unicom.

[0069] First step, it is necessary to generate a copy of the metrics of the original attributes of sn1, and then set the original metrics to 0, generating the following records:

[0070] Record 1: device_net sn = sn1, area = Beijing, isp = Telecom, interface = eth0 tx = 0, rx = 0 1693450800.

[0071] Record 2 (copy): device_net sn = sn1, area = Beijing, isp = Telecom, interface = eth0 tx = 100, rx = 50 1693450800.

[0072] Second step, change the target attribute (isp) in the copy to the target attribute value (China Unicom);

[0073] Record 1: device_net sn = sn1, area = Beijing, isp = Telecom, interface = eth0 tx = 0, rx = 0 1693450800.

[0074] Record 2 (copy): device_net sn = sn1, area = Beijing, isp = China Unicom, interface = eth0 tx = 100, rx = 50 1693450800.

[0075] Third step, symmetrically align the original attribute metrics of the device and the repaired attribute metrics (for easy generation of patch), and the final output records are as follows:

[0076] Original old data of the device:

[0077] Record 1: device_net sn = sn1, area = Beijing, isp = Telecom, interface = eth0 tx = 100, rx = 50 1693450800.

[0078] Record 2: device_net sn = sn1, area = Beijing, isp = China Unicom, interface = eth0 tx = 0, rx = 0 1693450800.

[0079] Original new data of the device:

[0080] Record 1: device_net sn=sn1, area=Beijing, isp=Telecom, interface=eth0 tx=0, rx=0 1693450800.

[0081] Record 2: device_net sn=sn1, area=Beijing, isp=China Unicom, interface=eth0 tx=100, rx=50 1693450800.

[0082] When the preset repair strategy rule is the clear strategy:

[0083] Clear strategy: The rule definition format is as follows:

[0084] Clear 0: {

[0085] SN: [start time, end time]

[0086] }.

[0087] For example, clear the bandwidth of sn1 at timestamp 1693450800 to 0.

[0088] First step, set the bandwidth of sn=sn1 and time=1693450800 to 0.

[0089] Record 1: device_net sn=sn1, area=Beijing, isp=Telecom, interface=eth0 tx=0, rx=0 1693450800.

[0090] Second step, make the original attribute metrics of the device symmetric with the repaired attribute metrics (for generating patches conveniently), and the final output record is as follows:

[0091] Original old data of the device:

[0092] Record 1: device_net sn=sn1, area=Beijing, isp=Telecom, interface=eth0 tx=100, rx=50 1693450800.

[0093] Original new data of the device:

[0094] Record 1: devi ce_net sn=sn1, area=Beijing, i sp=Telecom, i nterface=eth0 tx=0, rx=0 1693450800.

[0095] In the above embodiments, the input and output of policy repair are in a unified format, which can facilitate the subsequent generation of patches, avoid the repeated calculation process of most devices, reduce resource consumption, and can overwrite a certain attribute value, improving data processing efficiency.

[0096] Optionally, calculating the aggregation policy difference value of the aggregation dimension for the original old device data and the original new device data according to the preset aggregation configuration specifically includes:

[0097] Calculating the aggregated old data corresponding to the original old device data according to the preset aggregation configuration, and calculating the aggregated new data corresponding to the original new device data according to the preset aggregation configuration, and taking the difference between the aggregated old data and the aggregated new data to obtain the aggregated data difference value;

[0098] Importing the aggregated data of the aggregation configuration, and taking the difference between the aggregated data and the aggregated data difference value to obtain the repair value of the aggregation dimension.

[0099] Specifically, in the first step, the original old device data and the original new device data are respectively calculated for the aggregated old and aggregated new data according to the aggregation configuration, and the aggregated old data is subtracted from the aggregated new data to obtain the aggregated data difference value. This operation is to generate a patch;

[0100] In the second step, query the aggregated data of the aggregation configuration, subtract the aggregated data difference value, and obtain the final aggregated policy data.

[0101] The following takes the network card bandwidth after attribute change policy repair as an example. This process is specifically as follows:

[0102] Assume that the aggregation configuration is from the device network card bandwidth to the operator network card bandwidth.

[0103] Calculate the bandwidth from the "original old device data to aggregated old data" and "original new device data to aggregated new data" according to the aggregation configuration, and then calculate the difference value. This operation is called generating a patch.

[0104] Taking the attribute change policy as an example, after the attribute change policy is repaired, the recorded output is as follows:

[0105] Original old device data:

[0106] Record 1: device_net sn=sn1, area=Beijing, isp=China Telecom, interface=eth0 tx=100, rx=50 1693450800.

[0107] Record 2: device_net sn=sn1, area=Beijing, isp=China Unicom, interface=eth0 tx=0, rx=0 1693450800.

[0108] Original new data of the device:

[0109] Record 1: device_net sn=sn1, area=Beijing, isp=China Telecom, interface=eth0 tx=0, rx=0 1693450800.

[0110] Record 2: device_net sn=sn1, area=Beijing, isp=China Unicom, interface=eth0 tx=100, rx=50 1693450800.

[0111] After aggregating to the operator, the record output is as follows:

[0112] Original -> Aggregated old data:

[0113] Record 1: isp_net isp=China Telecom tx=100, rx=50 1693450800.

[0114] Record 2: isp_net isp=China Unicom tx=0, rx=0 1693450800.

[0115] Original -> Aggregated new data:

[0116] Record 1: isp_net isp=China Telecom tx=0, rx=0 1693450800.

[0117] Record 2: isp_net isp=China Unicom tx=100, rx=50 1693450800.

[0118] After generating the patch (aggregated old data - aggregated new data), the record output is as follows:

[0119] Record 1: isp_net isp=China Telecom tx=100, rx=50 1693450800.

[0120] Record 2: isp_net isp=China Unicom tx=-100, rx=-50 1693450800.

[0121] Next, the patching process is as follows:

[0122] Query the aggregated policy bandwidth (i.e., the aggregated data of the aggregation configuration), and the input records are as follows:

[0123] Record 1: isp_net isp=China Telecom tx=1000, rx=500 1693450800.

[0124] Record 2: isp_net isp = China Unicom, tx = 1500, rx = 500, 1693450800.

[0125] The final aggregated bandwidth is obtained by subtracting the patch bandwidth from the aggregated policy bandwidth;

[0126] Record 1: isp_net isp = China Telecom, tx = 900, rx = 450, 1693450800.

[0127] Record 2: isp_net isp = China Unicom, tx = 1600, rx = 550, 1693450800.

[0128] As Figure 2 shown, the above incremental repair process can be understood as:

[0129] Calculate according to the aggregation policy: the metrics from the original old to the aggregated old and the metrics from the original new to the aggregated new:

[0130] (Metrics from the original old to the aggregated old) - (Metrics from the original new to the aggregated new) = Aggregation policy difference.

[0131] Aggregated policy bandwidth - Aggregation policy difference = Repair bandwidth for the aggregation dimension.

[0132] Finally, the landing data: Write the repair bandwidth for the aggregation dimension into the preset time series database.

[0133] In the above embodiments, through the process of generating patches and applying patches, that is, the modifications that need to be made incrementally to the metrics in the aggregation dimension, only the relevant attributes and metrics of the affected devices need to be calculated, solving the problems of large data volume and high resource consumption caused by offline aggregation of all devices, greatly improving the bandwidth repair efficiency, and the repair is idempotent and can be executed repeatedly.

[0134] As Figure 3 shown, in some embodiments, if there are multiple aggregation configurations, the aggregation data repair process under multiple aggregation policies is as follows:

[0135] Aggregation configuration loading process: Load multiple aggregation configurations (policies), including Aggregation Policy 1, Aggregation Policy 2... Aggregation Policy n.

[0136] Policy repair process: According to multiple aggregation configurations, obtain the original data and its attributes, and perform repair processing respectively according to the corresponding repair policy rules to obtain the original old data and original new data of each repaired device.

[0137] Incremental repair process: Calculate the aggregation data difference between the original old data and original new data of the device (generate patches);

[0138] Query the aggregated data of the aggregation configuration;

[0139] Subtract the aggregation data difference between the original old data and the original new data of the device from the device aggregation policy bandwidth (patch), and obtain the repaired aggregation bandwidth (i.e., the repair value of the aggregation dimension).

[0140] Writing process: Store the original repaired bandwidth and the repaired aggregation bandwidth.

[0141] As Figure 4 shown, the edge node aggregation data repair device provided by the embodiment of the present invention includes an aggregation configuration loading module, a policy repair module, an incremental repair module, and a writing module;

[0142] The aggregation configuration loading module is used to load the aggregation configuration of the original device metrics and its original device attributes;

[0143] The policy repair module is used to obtain the original device metrics according to the aggregation configuration, expand the original device attributes to obtain device extended attributes, and perform repair processing on the original device metrics and / or the device extended attributes to generate the original old data and the original new data of the device;

[0144] The incremental repair module is used to calculate the aggregation policy difference between the original old data and the original new data of the device according to a preset aggregation configuration to obtain the repair value of the aggregation dimension;

[0145] The writing module is used to write the repair value of the aggregation dimension into a preset time series database.

[0146] Optionally, in the policy repair module, obtaining the original device metrics according to the aggregation configuration, expanding the original device attributes to obtain device extended attributes, and performing repair processing on the original device metrics and the device extended attributes to obtain the original repaired old data and the original repaired new data of the device includes:

[0147] Parse the aggregation configuration in a set format, and query the original device metrics through the parsing result;

[0148] Expand the original device attributes through the device management center to obtain device extended attributes;

[0149] Perform repair processing on the original device metrics and / or the device extended attributes according to a preset repair policy rule to generate the original old data and the original new data of the device.

[0150] Optionally, the calculating the aggregation policy difference between the original old data and the original new data of the device according to a preset aggregation configuration to obtain the repair value of the aggregation dimension is specifically:

[0151] Calculate the aggregated old data corresponding to the original old data of the device according to a preset aggregation configuration, and calculate the aggregated new data corresponding to the original new data of the device according to the preset aggregation configuration, and subtract the aggregated old data from the aggregated new data to obtain an aggregated data difference;

[0152] Import the aggregated data of the aggregation configuration, and subtract the aggregated data difference from the aggregated data to obtain a repair value of the aggregation dimension.

[0153] The edge node aggregated data repair device provided by the embodiment of the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the edge node aggregated data repair method as described above is implemented.

[0154] A computer-readable storage medium provided by the embodiment of the present invention stores a computer program. When the computer program is executed by a processor, the edge node aggregated data repair method as described above is implemented.

[0155] It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device.

[0156] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described device and unit can refer to the corresponding processes in the foregoing method embodiments, and will not be described herein again.

[0157] In several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0158] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or may be distributed over multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present invention.

[0159] In addition, each functional unit in various embodiments of the present invention may be integrated in a processing unit, may exist separately as individual physical units, or two or more units may be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0160] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. For such understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs and other various media that can store program codes.

[0161] The above is only the specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for repairing aggregated data of edge nodes, characterized in that, The steps are as follows: Load the aggregation configuration of the original device metrics and its original device attributes; Obtain the original device metrics according to the aggregation configuration, expand the original device attributes to obtain device extended attributes, and perform repair processing on the original device metrics and / or the device extended attributes to generate original old device data and original new device data; Perform aggregation policy difference calculation on the original old device data and the original new device data according to a preset aggregation configuration to obtain a repair value for the aggregation dimension; specifically: calculate the aggregated old data corresponding to the original old device data according to the preset aggregation configuration, and calculate the aggregated new data corresponding to the original new device data according to the preset aggregation configuration, and subtract the aggregated old data from the aggregated new data to obtain an aggregated data difference; import the aggregated data of the aggregation configuration, and subtract the aggregated data difference from the aggregated data to obtain a repair value for the aggregation dimension; Write the repair value of the aggregation dimension into a preset time series database.

2. The method for repairing aggregated data of edge nodes according to claim 1, wherein The step of obtaining the original device metrics according to the aggregation configuration, expanding the original device attributes to obtain device extended attributes, and performing repair processing on the original device metrics and / or the device extended attributes to obtain repaired original old device data and repaired original new device data includes: Parse the aggregation configuration in a set format, and query the original device metrics through the parsing result; Expand the original device attributes through the device management center to obtain device extended attributes; Perform repair processing on the original device metrics and / or the device extended attributes according to a preset repair policy rule to generate original old device data and original new device data.

3. The edge node aggregated data repair method according to claim 2, wherein The step of parsing the aggregation configuration in a set format and querying the original device metrics through the parsing result includes: Parse the aggregation configuration according to the combination method of the device identifier and the time range, and query the original device metrics through the parsing results of the device identifier and the time range.

4. The edge node aggregation data repair method according to claim 3, wherein The step of performing repair processing on the original device metrics and / or the device extended attributes according to a preset repair policy rule to generate original old device data and original new device data includes: When the preset repair policy rule is an attribute change policy, perform attribute change processing on the original device metrics and / or the device extended attributes to generate original old device data corresponding to before the attribute change processing, and generate original new device data corresponding to after the attribute change processing; When the preset repair policy rule is a clearing policy, perform clearing processing on the original device metrics and / or the device extended attributes to generate original old device data corresponding to before the clearing processing, and generate original new device data corresponding to after the clearing processing.

5. An edge node aggregated data repair device, characterized in that It includes an aggregation configuration loading module, a policy repair module, an incremental repair module, and a writing module; The aggregation configuration loading module is used to load the aggregation configuration of the original device metrics and its original device attributes; A policy repair module, which is used to obtain the original device metrics according to the aggregation configuration, expand the original device attributes to obtain device extended attributes, and perform repair processing on the original device metrics and / or the device extended attributes to generate original old device data and original new device data; An incremental repair module, which is used to calculate the aggregation policy difference between the original old device data and the original new device data according to a preset aggregation configuration to obtain the repair value of the aggregation dimension; Calculate the aggregated old data corresponding to the original old device data according to the preset aggregation configuration, and calculate the aggregated new data corresponding to the original new device data according to the preset aggregation configuration, and subtract the aggregated old data from the aggregated new data to obtain the aggregated data difference; Import the aggregated data of the aggregation configuration, and subtract the aggregated data difference from the aggregated data to obtain the repair value of the aggregation dimension; A writing module, which is used to write the repair value of the aggregation dimension into a preset time series database.

6. The edge node aggregation data repair device according to claim 5, wherein In the policy repair module, obtaining the original device metrics according to the aggregation configuration, expanding the original device attributes to obtain device extended attributes, and performing repair processing on the original device metrics and / or the device extended attributes to obtain repaired original old device data and repaired original new device data, including: Parsing the aggregation configuration in a set format, and querying the original device metrics through the parsing result; Expanding the original device attributes through the device management center to obtain device extended attributes; Performing repair processing on the original device metrics and / or the device extended attributes according to a preset repair policy rule to generate original old device data and original new device data.

7. An edge node aggregated data repair device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, the edge node aggregated data repair method according to any one of claims 1 to 4 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, the edge node aggregated data repair method according to any one of claims 1 to 4 is implemented.

Images