A PLC system data integration management method, medium and device

By dividing the backup data of the PLC system and coding in multiple PLC systems, the traditional backup data is solved in physical damage and there is a problem of intercepting risks in different places, and the high security and efficient backup of the data are achieved.

CN118689711BActive Publication Date: 2025-01-28杭州泛海科技有限公司
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202411183094.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2025-01-28
Estimated Expiration
2044-08-27

AI Technical Summary

Technical Problem

When the PLC system suffers physical damage, traditional local backup data will also be lost, and existing off-site backups have the risk of third parties intercepting data.

Method used

The backup data is divided into multiple parts, and after encoding, it is backup into multiple PLC systems, and distributes and manage it through the integrated management center to prevent third parties from intercepting complete data.

Benefits of technology

To a large extent, third -party interception of complete data, improved the security of the data, and saved network resources and improved the efficiency of data backup through the process of comparison and re -dividing and encoding.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118689711B_ABST
    Figure CN118689711B_ABST
Patent Text Reader

Abstract

The present invention provides a PLC system data integration management method, medium and equipment, and relates to the technical field of data backup management. The method comprises the following steps: S1, system configuration: configuring an identity identifier and a backup unit for each PLC system; S2, data upload: generating backup data according to a fixed period, and uploading the backup data; S3, first backup: dividing the backup data, encoding them in sequence, and then distributing them to the backup units of at least two other PLC systems; S4, subsequent backup: the integrated management center compares the two backup data, re-divides and encodes them according to the comparison results, and then distributes the sub-data blocks to the backup units of at least other PLC systems; S5, data recovery: when any PLC system fails and needs to recover data, all sub-data blocks are obtained, spliced ​​and then transmitted back to the PLC system. The present invention divides the backup data into multiple copies, and backs them up in multiple PLC systems respectively after encoding, which can prevent a third party from intercepting the complete data to a large extent.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data backup management, and in particular to a PLC system data integration management method, medium and equipment. Background Art

[0002] Industrial control systems, or industrial control systems, are an important part of the national industrial system and critical infrastructure, and programmable logic controllers (PLCs) are important basic control devices in industrial control systems.

[0003] PLC systems generate a variety of data during use. In order to prevent these data from unexpected losses, data backup is an essential means. When the PLC system suffers severe physical damage (such as fire, water, etc.), traditional local backup data will also be lost and cannot provide good data protection. The existing off-site backup, because the entire data is stored off-site, has the risk of being intercepted by a third party.

[0004] Therefore, how to develop a method that can achieve data backup while preventing a third party from intercepting complete data is one of the problems that needs to be solved urgently. Summary of the invention

[0005] The purpose of the present invention is to provide a PLC system data integration management method, medium and equipment, which divides the backup data into multiple copies, and backs up them in multiple PLC systems after encoding, which can prevent a third party from intercepting the complete data to a large extent.

[0006] To achieve the above object, the present invention adopts the following technical solutions:

[0007] In a first aspect, the present invention provides a PLC system data integration management method, comprising the following steps:

[0008] S1, system configuration: configure the identity and backup unit for each PLC system;

[0009] S2, data upload: Each PLC system generates backup data according to a fixed period and uploads the backup data to the integrated management center;

[0010] S3, first backup: the integrated management center divides the backup data into multiple sub-data blocks, encodes the sub-data blocks in sequence in combination with the identity identifiers of the corresponding PLC systems, and then distributes the multiple sub-data blocks to the backup units of at least two other PLC systems;

[0011] S4, subsequent backup: the integrated management center compares the current backup data with the previous backup data, and re-segments and encodes the sub-data blocks according to the comparison results and distributes them to at least the backup units of other PLC systems;

[0012] S5, data recovery: when any PLC system fails and needs data recovery, a recovery request is sent to the integrated management center; the integrated management center obtains all sub-data blocks with the identity of the PLC system in the code from other PLC systems, splices them and then transmits them back to the PLC system.

[0013] In some embodiments of the first aspect of the present invention, in S3, the method of dividing the backup data into a plurality of sub-data blocks is as follows:

[0014] S301, setting a container of a first capacity size,

[0015] S302, filling the container with data starting from the head of the backup data until the container is full, extracting the data in the container from the original backup data, and encrypting the data to obtain a sub-data block;

[0016] S303, continue to fill the container with the remaining backup data according to the method of S302, until all the backup data are intercepted to obtain multiple sub-data blocks.

[0017] In certain embodiments of the first aspect of the present invention, in S3, the method of distributing the plurality of sub-data blocks to backup units of at least two other PLC systems is as follows:

[0018] S311, obtaining the memory size of the sub-data blocks in sequence;

[0019] S312, counting the remaining memory capacities of the backup units of all other PLC systems, and selecting the backup unit of the PLC system whose remaining memory capacity is greater than the memory size of the sub-data block;

[0020] S313, select one of the selected PLC systems and send the sub-data block to the backup unit of the PLC system.

[0021] In certain embodiments of the first aspect of the present invention, the backup unit of the PLC system sent by each sub-data block is recorded, and when the backup unit of the PLC system whose remaining memory capacity is greater than the memory size of the sub-data block is selected in step S312, the backup unit of the PLC system sent by the previous sub-data block is eliminated.

[0022] In certain embodiments of the first aspect of the present invention, in S4, the method in which the integrated management center compares the current backup data with the previous backup data is as follows:

[0023] The current backup data is compared with the previous backup data in text format, and the difference data is marked in the previous backup data, and the sub-data blocks containing the difference data are filtered out.

[0024] In certain embodiments of the first aspect of the present invention, in S4, the method of re-segmenting and encoding the sub-data blocks according to the comparison result and distributing them to the backup units of at least other PLC systems is as follows:

[0025] If a sub-data block does not contain differential data, the backup unit and code of the PLC system where the sub-data block is located remain unchanged, and the part of the current backup data corresponding to the sub-data block is deleted;

[0026] If a sub-data block contains differential data, the sub-data block is deleted from the backup unit of the PLC system where it is located, and a container of a second capacity size is used to further divide the portion of the current backup data corresponding to the sub-data block to obtain multiple sub-data blocks; sub-codes are generated sequentially based on the original codes for the multiple sub-data blocks obtained, and then distributed to the backup units of other PLC systems.

[0027] In some embodiments of the first aspect of the present invention, if two or more consecutive sub-data blocks contain differential data, then during further segmentation, the two or more consecutive sub-data blocks are segmented together with corresponding parts of the current backup data.

[0028] In certain embodiments of the first aspect of the present invention, in S5, after the splicing, the integrity of the backup data is verified, the codes of all the acquired sub-data blocks are extracted, and the extracted codes are arranged in sequence, and statistics are made to see whether there are any missing codes. If there are no missing codes, the backup data is complete.

[0029] In a second aspect, the present invention provides a non-transitory storage medium storing computer instructions for causing the computer to execute the steps of a PLC system data integration management method as described in the first aspect.

[0030] In a third aspect, the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of a PLC system data integration management method as described in the first aspect are implemented.

[0031] Compared with the prior art, the present invention has the following beneficial effects:

[0032] 1. The present invention divides the backup data into multiple copies, and backs them up in multiple PLC systems after encoding, which can prevent a third party from intercepting the complete data to a large extent and improve the security of the data.

[0033] 2. In the subsequent backup process, the present invention compares the current backup data with the previous backup data, and re-divides and encodes them according to the comparison results; for sub-data blocks that do not contain differential data, there is no need to re-issue them, saving network resources; for sub-data blocks that contain differential data, they are re-divided into smaller sub-data blocks and re-encoded for comparison and analysis of the next backup. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a schematic diagram of the overall process of the present invention.

[0035] Figure 2 It is a schematic diagram of the system structure of the present invention.

[0036] Figure 3 This is a backup data segmentation flow chart of the present invention.

[0037] Figure 4 Schematic diagram of backup data segmentation according to the present invention.

[0038] Figure 5 This is a flow chart of sub-data block distribution of the present invention.

[0039] Figure 6 It is a text comparison schematic diagram of the present invention.

[0040] Figure 7 This is a schematic diagram of further segmenting sub-data blocks according to the present invention.

[0041] Figure 8 It is a schematic diagram of two consecutive sub-data blocks containing difference data according to the present invention. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0043] Embodiment 1:

[0044] This embodiment provides a PLC system data integration management method, please refer to Figure 1 , the management method includes the following steps:

[0045] S1, System Configuration: Configure the identity for each PLC system and backup unit ;

[0046] in, Represents the serial number of the PLC system. Figure 2 As shown, a total of N PLC systems are configured with identity tags in sequence. To Identity ; Also with identity tag PLC system configuration backup unit , and so on, with an identity tag PLC system configuration backup unit .

[0047] And all PLC systems are connected to an integrated management center to realize backup data transmission and backup data processing between PLC systems.

[0048] S2, data upload: Each PLC system generates backup data according to a fixed period and uploads the backup data to the integrated management center.

[0049] PLC system For example, generate backup data every half an hour , and upload it to the integrated management center.

[0050] S3, first backup: the integrated management center divides the backup data into multiple sub-data blocks, encodes the sub-data blocks in sequence in combination with the identity of the corresponding PLC system, and then distributes the multiple sub-data blocks to the backup units of at least two other PLC systems.

[0051] Please refer to Figure 3 , to back up data For example, back up the data The method of splitting into multiple sub-data blocks is as follows:

[0052] S301, such as Figure 4 As shown, a container of the first capacity size is set , the container It is a small storage unit that can be used to temporarily store data;

[0053] S302, from backup data The head of the container begins to move toward Fill the data until the container is full , the container The data in the backup is extracted from the original backup data and encrypted to obtain a sub-data block ;

[0054] S303, then the remaining backup data Continue filling the container according to the method of S302 until all the backup data is intercepted and encrypted in sequence to obtain sub-data blocks To sub-block .

[0055] It is worth mentioning that backing up data The last part fills the container When filling to the backup data At the end of the time, if the container is not full, Part of the data in is intercepted and encrypted to obtain the last sub-data block, i.e., the sub-data block .

[0056] At this point, the encoding of these sub-data blocks has been completed, that is, the identity of the PLC system The subscript is the current order of the sub-data block, and the PLC system For example, to At the same time, the integrated management center records the PLC system The coding information of the corresponding sub-data block is prepared for data processing in subsequent steps S4 and S5.

[0057] Or PLC system For example, please refer to Figure 5 , multiple sub-data blocks to The method of distributing the backup unit to at least two other PLC systems is as follows:

[0058] S311, obtaining sub-data blocks in sequence to Memory size;

[0059] S312, count the backup units of all other PLC systems The remaining memory capacity of the PLC system is selected, and the backup unit of the PLC system whose remaining memory capacity is greater than the sub-data block memory size is selected;

[0060] Here, all other PLC systems refer to PLC systems other than All PLC systems except the backup unit of Not equal to 1;

[0061] S313, for each sub-data block to , select one of the selected PLC systems and send the sub-data block to the backup unit of the PLC system .

[0062] At this point, backup data is realized The off-site segmented storage can not only prevent the loss of backup data caused by local disasters (such as fire, flooding, etc.), but also disperse the overall backup data in various locations, reducing the risk of overall data leakage.

[0063] It is worth mentioning that the container The smaller the capacity, the more sub-data blocks are divided, and the lower the risk of overall data leakage. However, the amount of data processing calculations will increase greatly, causing an excessive load on the integrated management center.

[0064] In order to prevent all sub-data blocks from being assigned to the backup unit of the same PLC system, it is necessary to record the backup unit of the PLC system to which each sub-data block is assigned. , and when selecting a backup unit of a PLC system whose remaining memory capacity is greater than the memory size of a sub-data block in step S312, the backup unit of the PLC system issued by the previous sub-data block is eliminated.

[0065] Therefore, it can be ensured that two adjacent sub-data blocks are allocated to the backup units of two different PLC systems, thereby ensuring that the situation in which all sub-data blocks are allocated to the backup units of the same PLC system will not occur.

[0066] S4, subsequent backup: the integrated management center compares the current backup data with the previous backup data, and re-segments and encodes the sub-data blocks according to the comparison result and distributes them to at least the backup units of other PLC systems.

[0067] Specifically, the method in which the integrated management center compares the current backup data with the previous backup data is as follows:

[0068] like Figure 6 As shown, a text comparison is performed between the current backup data and the last backup data, and the difference data is marked in the last backup data, and the sub-data blocks containing the difference data are screened out.

[0069] It is worth mentioning that this embodiment uses the OCR text comparison algorithm. Figure 6 The shaded That is, the sub-data block containing the difference data is filtered out. The text comparison results of other data blocks are consistent, and there is no difference data.

[0070] The method of re-segmenting and encoding the sub-data blocks according to the comparison results and then distributing them to the backup units of at least other PLC systems includes the following two situations.

[0071] Scenario 1: If a sub-data block (such as a sub-data block , , ) does not contain differential data, it means that the backup data corresponding to the sub-data block does not need to be backed up again, so the backup unit and code of the PLC system where the sub-data block is located remain unchanged, and the part of the current backup data corresponding to the sub-data block is deleted.

[0072] Scenario 2: If a sub-data block (such as a sub-data block ) contains differential data, the sub-data block is deleted from the backup unit of the current PLC system, and the current backup data is transferred to the container of the second capacity size. The corresponding sub-data block The parts are further divided into Figure 7 As shown, multiple sub-data blocks are obtained to ; Generate sub-codes on the original codes in sequence for the obtained multiple sub-data blocks, and then distribute them to the backup units of other PLC systems. Similarly, all codes and sub-codes need to be recorded for use in integrity verification in step S5.

[0073] The method for further dividing the sub-data block is the same as step S301 to step S303, and the second capacity is smaller than the first capacity so as to divide the sub-data block into smaller units.

[0074] It is worth mentioning that the specific method of generating sub-codes in sequence on the original code is to add the next level order based on the current order of the sub-data block as the superscript of the original code. For example, if the superscript of the divided sub-data block is the first-level code 2, then the superscripts after further division are the second-level codes 2-1, 2-2, 2-3, and so on.

[0075] Similarly, if the sub-data block to be divided is already coded, for example, 2-1, the superscript after further division is the third-level code 2-1-1, 2-1-2, and so on. Similarly, the capacity of the container used for division will be further reduced.

[0076] Through the above further segmentation, the sub-data blocks containing the difference data can be further divided into smaller units. The reason is that in the previous text comparison process, although the sub-data blocks The difference data is included, but the difference data is likely to be only a small part of it. Therefore, it is divided into smaller units, so that in the next comparison process, the part that does not contain the difference data can be further compared to avoid repeated backup of this part at a later time.

[0077] S5, data recovery: when any PLC system fails and needs data recovery, a recovery request is sent to the integrated management center; the integrated management center obtains all sub-data blocks with the identity of the PLC system in the code from other PLC systems, splices them and then transmits them back to the PLC system.

[0078] It is worth mentioning that after splicing, the integrity of the backup data is verified. The codes and sub-codes of all sub-data blocks are extracted, and the extracted codes are arranged in sequence. The coding information in the record is compared to count whether there are any missing codes. If there are no missing codes, the backup data is complete.

[0079] Embodiment 2:

[0080] In the solution of embodiment 1, Figure 8 As shown, in step S4, if two or more consecutive sub-data blocks contain difference data, the sub-data blocks and sub-blocks For example, in the current backup data, the corresponding sub-data block and sub-blocks When further split, the corresponding sub-data blocks in the current backup data and sub-blocks The boundary between the two is not clear, so it is impossible to accurately separate the contents of the two corresponding sub-data blocks.

[0081] Therefore, in the second embodiment, when further segmenting, the two or more consecutive sub-data blocks containing differential data are segmented together with the corresponding parts of the current backup data. The specific segmentation method is the same as step S4 in the first embodiment, and will not be repeated here.

[0082] Embodiment three:

[0083] This embodiment provides a non-transitory storage medium, which stores computer instructions, and the computer instructions are used to enable the computer to execute the steps of a PLC system data integration management method as described in Example 1 or Example 2.

[0084] Embodiment 4:

[0085] This embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps of a PLC system data integration management method as described in Embodiment 1 or Embodiment 2 are implemented.

[0086] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0087] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A PLC system data integration management method, characterized in that: The following steps are involved: S1, system configuration: configure the identity and backup unit for each PLC system; S2, data upload: Each PLC system generates backup data according to a fixed period and uploads the backup data to the integrated management center; S3, first backup: the integrated management center divides the backup data into multiple sub-data blocks, encodes the sub-data blocks in sequence in combination with the identity identifiers of the corresponding PLC systems, and then distributes the multiple sub-data blocks to the backup units of at least two other PLC systems; S4, subsequent backup: the integrated management center compares the current backup data with the previous backup data, and re-segments and encodes the sub-data blocks according to the comparison results and distributes them to at least the backup units of other PLC systems; S5, data recovery: when any PLC system fails and needs to recover data, a recovery request is sent to the integrated management center; the integrated management center obtains all sub-data blocks with the identity of the PLC system in the code from other PLC systems, splices them and then transmits them back to the PLC system; In S3, the method of distributing the multiple sub-data blocks to the backup units of at least two other PLC systems is as follows: S311, obtaining the memory size of the sub-data blocks in sequence; S312, counting the remaining memory capacities of the backup units of all other PLC systems, and selecting the backup unit of the PLC system whose remaining memory capacity is greater than the memory size of the sub-data block; S313, select one of the selected PLC systems and send the sub-data block to the backup unit of the PLC system; Record the backup unit of the PLC system issued by each sub-data block, and when selecting the backup unit of the PLC system whose remaining memory capacity is greater than the memory size of the sub-data block in step S312, remove the backup unit of the PLC system issued by the previous sub-data block; In S4, the method in which the integrated management center compares the current backup data with the previous backup data is as follows: Perform text comparison between the current backup data and the previous backup data, mark the difference data in the previous backup data, and filter out the sub-data blocks containing the difference data; In S4, the method of re-segmenting and encoding the sub-data blocks according to the comparison results and distributing them to at least the backup units of other PLC systems is as follows: If a sub-data block does not contain differential data, the backup unit and code of the PLC system where the sub-data block is located remain unchanged, and the part of the current backup data corresponding to the sub-data block is deleted; If a sub-data block contains differential data, the sub-data block is deleted from the backup unit of the PLC system where it is located, and a container of a second capacity size is used to further divide the portion of the current backup data corresponding to the sub-data block to obtain multiple sub-data blocks; sub-codes are generated sequentially based on the original codes for the multiple sub-data blocks obtained, and then distributed to the backup units of other PLC systems; the second capacity is smaller than the first capacity.

2. A PLC system data integration management method according to claim 1, characterized in that: In S3, the method of dividing the backup data into multiple sub-data blocks is as follows: S301, setting a container of a first capacity size, S302, filling the container with data starting from the head of the backup data until the container is full, extracting the data in the container from the original backup data, and encrypting the data to obtain a sub-data block; S303, continue to fill the container with the remaining backup data according to the method of S302, until all the backup data are intercepted to obtain multiple sub-data blocks.

3. A PLC system data integration management method according to claim 1, characterized in that: If two or more consecutive sub-data blocks contain differential data, then during further segmentation, the two or more consecutive sub-data blocks are segmented together with the corresponding parts in the current backup data.

4. A PLC system data integration management method according to claim 1, characterized in that: In S5, after the splicing, the integrity of the backup data is verified, the codes of all the acquired sub-data blocks are extracted, and the extracted codes are arranged in order, and the code is counted to see if there are any missing codes. If there are no missing codes, the backup data is complete.

5. A non-transitory storage medium storing computer instructions, characterized in that: The computer instructions are used to enable the computer to execute the steps of a PLC system data integration management method as described in any one of claims 1 to 4.

6. An electronic 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 program, the steps of a PLC system data integration management method as described in any one of claims 1 to 4 are implemented.

Citation Information

Patent Citations

  • A data backup and recovery method based on source data re-deletion

    CN109101365A

  • Data backup method and device of cloud platform virtual machine and electronic equipment

    CN117009147A

  • Data backup method and device based on hyper-fusion mechanism and medium

    CN118312359A