A blockchain-based archive information monitoring and management system

By introducing archive operation unit, system setting unit, block synchronization unit, remote monitoring unit and log processing unit in the archive information security management system, combined with RESTful interface and blockchain technology, the monitoring and alarm problems during archive data update are solved. , realizes secure and reliable storage and efficient access of archive data, and improves the security and execution efficiency of the system.

CN118227415BActive Publication Date: 2024-11-26SHANXI SANYOUHUO INTELLIGENCE INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410341890.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-03-25
Publication Date
2024-11-26
Estimated Expiration
2044-03-25

AI Technical Summary

Technical Problem

The existing blockchain-based archive information security management system lacks effective monitoring and error message alerts when updating archive data, which makes it difficult for the management system to quickly deal with abnormal situations in emergencies, which poses a major security risk and affects the system's execution efficiency. In addition, inconsistent information between block nodes reduces data access efficiency.

Method used

A blockchain-based archive information monitoring and management system is designed, including archive operation unit, system setting unit, block synchronization unit, remote monitoring unit and log processing unit, and archives are realized through RESTful interface, Ceph cluster and Ethereum network. Distributed storage and management, combined with McEliece public key cryptography system and digital signature technology, provides secure storage, and uses status monitoring and error monitoring units to realize system security monitoring and exception handling.

Benefits of technology

Through distributed storage and security monitoring mechanisms, the security and integrity of archive data are ensured, the execution efficiency of the system is improved, security risks are reduced, and the efficiency of data access is ensured through block synchronization, providing system maintenance in accordance with.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118227415B_ABST
    Figure CN118227415B_ABST
Patent Text Reader

Abstract

The present invention discloses a blockchain-based archive information monitoring and management system, which relates to the technical field of archive management, including an archive operation unit, a system setting unit, a block synchronization unit, a remote monitoring unit and a log processing unit, an archive management unit, and the archive management unit is used to realize the business function of archive management. All modifications and migrations of archives are stored on the blockchain through a RESTful interface. For specific archives queried, the user end needs to verify the archives in the local database and the viewing authority of the archive data on the blockchain. The present invention uses the archive operation unit and the archive management unit to distribute the archives, and ensures the security of archive management based on the archive operation. The service configuration unit provides a RESTful interface and communicates with the object gateway of the Ceph cluster and the nodes in the Ethereum network. The status monitoring unit and the error monitoring unit realize the security monitoring of the entire system and report the monitoring information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of archive management, and in particular to an archive information monitoring and management system based on blockchain. Background Art

[0002] With the development of computer technology, it is a social trend to ensure the information security of archives through effective monitoring and management. The software upgrades and updates used in electronic archives over the years are constantly recorded and saved, and data integrity and non-arbitrary tampering are required to strengthen the security management of archive information. A blockchain-based archive information security management system and method are disclosed in the Chinese patent application number 201911155247.X. The system includes a unified data management tool, a local archive system database, and a blockchain network. The unified data management tool is configured to have a communication connection with the local archive system database and adapt to multiple types of archive databases. The blockchain network includes multiple nodes that have communication connections with each other and interact with the unified data management tool. The unified data management tool obtains the operation log of the local archive system database and unifies the operation log as transaction data and publishes it to the blockchain network; the blockchain network performs signature verification and transaction data consensus on the received transaction data; the unified data management tool operates the local archive system database according to the transaction results.

[0003] The above-mentioned documents realize efficient and automated database log consensus, and provide support for authentication of archive integrity, operation traceability and archive data backup. However, when updating archive data, in addition to data consensus to ensure the correctness of data, there is a lack of monitoring of archive security information and alarm of error information. When encountering emergencies such as management system paralysis, it is impossible to quickly handle abnormal situations, and it is difficult to implement countermeasures in a short period of time. There are major security risks, which affect the execution efficiency of the system and make it difficult to ensure data integrity. In addition, based on the blockchain, there are multiple block nodes. If there is inconsistency in information between blocks, the possibility of errors will increase and data access efficiency will be reduced. Summary of the invention

[0004] The purpose of the present invention is to provide an archive information monitoring and management system based on blockchain to solve the problems raised in the above background technology.

[0005] To achieve the above-mentioned purpose, the present invention provides the following technical solutions: a blockchain-based archive information monitoring and management system, comprising an archive operation unit, a system setting unit, a block synchronization unit, a remote monitoring unit and a log processing unit;

[0006] The archive management unit is used to implement the business function of archive management. All modifications and migrations of archives are stored on the blockchain through the RESTful interface. For specific archives queried, the user end needs to verify the archives in the local database and obtain the viewing authority of the archive data on the blockchain;

[0007] A service configuration unit, wherein the service configuration unit uses the central server as a service end, communicates with the user end of the archive management unit, and provides a RESTful interface for the user end. In addition, the service end communicates with the object gateway of the Ceph cluster and the nodes in the Ethereum network, and calls the interface of the object gateway to complete the data update operation;

[0008] A secure storage unit, which stores the archive data accessed by the user end in the form of files in the Ceph cluster, stores the file location information in the blockchain, and deploys the developed smart contract on the blockchain node, and then uses the encryption algorithm and digital signature technology of the McEliece public key cryptography system to provide RESTful interface services;

[0009] The status monitoring unit sends the monitoring information in the target server to the central server in an active reporting manner, configures the central server with a public IP, collects and summarizes the monitoring information on each edge server, and then actively establishes a TCP connection with the central server to report the monitoring information.

[0010] The error monitoring unit collects error information in the application through the HTTP interface and executes the corresponding alarm strategy. The HTTP interface will send alarm information to the corresponding system manager according to the alarm rules while recording the error information.

[0011] Preferably, the archive operation unit includes an archive query module, an archive borrowing module, an archive update module and an archive migration module. The archive query module is divided into fuzzy query and precise query. The archive is fuzzily queried by using keywords, and the archive is precisely queried by using file numbers. Both of them uniformly query the local database and call the RESTful interface to obtain the file storage address in the blockchain, and then obtain the archive data from the Ceph cluster, take the union of the data and the queried data set in the local database, and send it to the user end. The archive borrowing module performs authority verification before borrowing the archive, and the user who passes the verification authority successfully borrows. The archive update module checks the archive information in the update form, stores the newly added attachments to the local disk, directly replaces the updated attachments, updates the archive attributes in the local database, and stores the modified attachments and attributes of the archive on the blockchain. The archive migration module system automatically displays the original storage path configured for this part of the data, and the user specifies the new storage path to perform migration. During migration, the data under the original storage path is retained and not deleted. After the migration is completed, the migrated data is compared and verified with the original data. After confirming that the migrated data is accurate, the original data is deleted.

[0012] Preferably, the archive management unit includes a permission check module, an archive synchronization module and an archive verification module. The permission check module obtains the user role of the logged-in user, determines whether the user's operation permissions are included in the pre-recorded permission list, and allows access if it is included, otherwise denies access. The archive synchronization module keeps the archive information in the local database consistent with the Ceph cluster storage information. The archive verification module obtains archive attributes and attachment information, calculates digital fingerprints for existing attachments, and then sends the archive attributes to the RESTful interface for verification. Non-existent attachments are sent to the RESTful interface for direct verification.

[0013] Preferably, the system setting unit includes a template management module, a user management module and a RESTful interface setting module. The template management module is used to specify the attribute list of a certain type of archives. Template management includes adding, querying, deleting and updating operations on existing template attributes, and when there are archives using this module, deletion operations cannot be performed. The user management module includes ordinary users, archive administrators and system administrators. The system administrator has the highest authority. According to actual needs, ordinary users are set as archive administrators and any ordinary users or archive administrator users are set as blacklist users. The RESTful interface setting module is used to add and update related keys required for interface calls, and the login password needs to be verified before querying and updating the keys.

[0014] Preferably, the secure storage unit includes a data upload module, a data access module, a data verification module and a record tracing module. The data upload module encrypts the data through an asymmetric encryption algorithm and then sends it to the server. The server generates a file based on the received data and calculates a digital summary. The data access module verifies the transaction signature of the user's request. After the correct completion, the Pow algorithm is used to reach a blockchain transaction consensus. The server obtains the file address and obtains the ciphertext from the file address, and then obtains the file data from the Ceph cluster. The data verification module performs integrity verification on the obtained ciphertext data based on the user's access data. The record tracing module 504 verifies the transaction signature through the blockchain node, and then packages the access transaction and broadcasts it to the entire network. Finally, the blockchain network uses the Pow algorithm to reach a consensus on the transaction. The Pow algorithm is specifically:

[0015]

[0016] In the formula, Indicates twice Hash operation, Represents the block header information, which contains Fields, represents the target threshold difficulty, represents the maximum target value, Indicates the current difficulty value.

[0017] Preferably, the block synchronization unit user starts the blockchain node to access the alliance chain. During the access process, the alliance chain network will authenticate the node, and only legitimate nodes will successfully join the alliance chain. After accessing the network, the node starts a listening thread, waits for the peer node in the network to broadcast data, and checks whether its own block is the latest. If not, it synchronizes blocks from other nodes. The error monitoring unit captures error information through the application and sends an HTTP request to the error collection interface. The error collection interface verifies the legitimacy of the request. If it is illegal, it will directly alarm, otherwise it will store the decrypted data in the message queue. The error handling script requests data from the message queue and determines whether there is a corresponding alarm strategy. If there is, the alarm strategy is executed and the error information is displayed to the system administrator, otherwise the error information is displayed directly.

[0018] Preferably, when the server is offline or stops running, the remote monitoring unit continuously checks whether the system is in an abnormal state. If an abnormality is detected, it attempts to start server status monitoring and application error monitoring to obtain specific monitoring information, and sends an alarm notification to the system administrator. The system sets a counter to count the number of startups. First, it checks whether the status monitoring unit has successfully completed the TCP connection. If the connection is successful, it indicates normal startup and the counter is set to 0. Otherwise, the counter starts counting. When the counter is 3, an alarm message is sent. Otherwise, it continues to determine whether the counter is greater than 3. If it is not satisfied, the counter is increased by 1. Otherwise, the counter is set to 4 to lock the system and force an alarm, and the monitoring and judgment are repeated.

[0019] Preferably, the log processing unit includes a data recording module, a data statistics module and an auxiliary analysis module. The data recording module automatically records the change log of the archive and regularly searches whether there is any log missing. The data statistics module counts the number of archives according to the archive category, file type and upload time. The auxiliary analysis module summarizes the log information of different time periods to analyze and evaluate the timeliness of the log data later, providing a reference for subsequent system maintenance.

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

[0021] The present invention completes the distributed storage of archives through the archive operation unit and the archive management unit, and can ensure the security of archive management based on the archive operation. It provides an upper-level service for the management of archive data by providing a RESTful interface and communicating with the object gateway of the Ceph cluster and the nodes in the Ethereum network through the service configuration unit, and provides a lower-level service for uploading and accessing archives for the secure storage unit. The secure storage unit combines the characteristics of blockchain de-trust and data non-tamperability with the characteristics of distributed storage with large capacity and easy expansion, providing archives with safe and reliable private data storage and data access record tracing functions, thereby ensuring data security.

[0022] The present invention realizes security monitoring of the entire system through a status monitoring unit and an error monitoring unit, reports abnormal operating status through a server and a TCP connection to complete abnormal monitoring information, collects application error information through an HTTP interface, executes corresponding and existing alarm strategies, and then displays the error information. It can technically handle abnormal situations or notify system administrators, reduce safety hazards, and improve the execution efficiency of the system. The remote detection unit continuously monitors offline servers to improve the emergency execution efficiency of the system. The block synchronization unit keeps the data between each block consistent, and the required data can be accessed from any block to improve the access node efficiency. The log processing unit statistically records archive change information and historical access logs, providing a reference basis for subsequent system maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 Provides a schematic diagram of the overall system flow for an embodiment of the present invention;

[0024] Figure 2 A block diagram of the internal modules of the archive operation unit provided by the embodiment of the present invention;

[0025] Figure 3 A block diagram of the internal modules of the archive management unit provided in an embodiment of the present invention;

[0026] Figure 4 An internal module block diagram of a system setting unit provided in an embodiment of the present invention;

[0027] Figure 5 An internal module block diagram of a secure storage unit provided by an embodiment of the present invention;

[0028] Figure 6 This is a block diagram of the internal modules of the log processing unit provided in an embodiment of the present invention.

[0029] In the figure: 1. Archive operation unit; 101. Archive query module; 102. Archive borrowing module; 103. Archive update module; 104. Archive migration module; 2. Archive management unit; 201. Permission check module; 202. Archive synchronization module; 203. Archive verification module; 3. Service configuration unit; 4. System setting unit; 401. Template management module; 402. User management module; 403. RESTful interface setting module; 5. Secure storage unit; 501. Data upload module; 502. Data access module; 503. Data verification module; 504. Record tracing module; 6. Block synchronization unit; 7. Status monitoring unit; 8. Error monitoring unit; 9. Remote monitoring unit; 10. Log processing unit; 1001. Data recording module; 1002. Data statistics module; 1003. Auxiliary analysis module. DETAILED DESCRIPTION

[0030] 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.

[0031] See also Figure 1-6 , the present invention provides a technical solution: an archive information monitoring and management system based on blockchain, comprising an archive operation unit 1, a system setting unit 4, a block synchronization unit 6, a remote monitoring unit 9 and a log processing unit 10;

[0032] Archives management unit 2, which is used to implement the business function of archives management. All modifications and migrations of archives are stored on the blockchain through the RESTful interface. For specific archives queried, the user end needs to verify the archives in the local database and obtain the viewing authority of the archive data on the blockchain;

[0033] Service configuration unit 3, which uses the central server as the server and communicates with the user end of the archive management unit 2, providing a RESTful interface for the user end. In addition, the server communicates with the object gateway of the Ceph cluster and the nodes in the Ethereum network, and calls the interface of the object gateway to complete the data update operation;

[0034] The secure storage unit 5 stores the archive data accessed by the user in the Ceph cluster in the form of files, stores the file location information in the blockchain, and deploys the developed smart contract on the blockchain node, and then uses the encryption algorithm and digital signature technology of the McEliece public key cryptography system to provide RESTful interface services;

[0035] Status monitoring unit 7, status monitoring unit 7 takes the initiative to report the monitoring information in the target server to the central server, configures the public network IP for the central server, collects and summarizes the monitoring information on each edge server, and then takes the initiative to establish a TCP connection with the central server to report the monitoring information.

[0036] The error monitoring unit 8 collects error information in the application through the HTTP interface and executes the corresponding alarm strategy. The HTTP interface will send alarm information to the corresponding system manager according to the alarm rules while recording the error information.

[0037] The archive operation unit 1 includes an archive query module 101, an archive borrowing module 102, an archive update module 103 and an archive migration module 104. The archive query module 101 is divided into fuzzy query and precise query. The archive is fuzzy queried by using keywords, and the archive is precisely queried by using file numbers. Both of them query the local database and call the RESTful interface to obtain the file storage address in the blockchain, and then obtain the archive data from the Ceph cluster, take the union of the data set queried in the local database, and send it to the user end. The archive borrowing module 102 performs a query before the archive is borrowed. Permission verification: users with verified permissions can successfully borrow the files. The file update module 103 checks the file information in the update form, stores the newly added attachments to the local disk, directly replaces the updated attachments, updates the file attributes in the local database, and stores the modified attachments and attributes of the files on the blockchain. The file migration module 104 system automatically displays the original storage path configured for this part of the data. The user specifies a new storage path to perform the migration. During the migration, the data under the original storage path is retained and not deleted. After the migration is completed, the migrated data is compared and verified with the original data. After confirming that the migrated data is accurate, the original data is deleted.

[0038] The archive management unit 2 includes a permission check module 201, an archive synchronization module 202 and an archive verification module 203. The permission check module 201 obtains the user role of the logged-in user, and determines whether the user's operation permissions are included in the pre-recorded permission list. If yes, access is allowed, otherwise access is denied. The archive synchronization module 202 makes the archive information in the local database consistent with the Ceph cluster storage information. The archive verification module 203 obtains archive attributes and attachment information, calculates digital fingerprints for existing attachments, and then sends the archive attributes to the RESTful interface for verification. Non-existent attachments are directly sent to the RESTful interface for verification.

[0039] The system setting unit 4 includes a template management module 401, a user management module 402 and a RESTful interface setting module 403. The template management module 401 is used to specify the attribute list of a certain type of archive. Template management includes adding, querying, deleting and updating operations on existing template attributes, and when there are archives using this module, the deletion operation cannot be performed. The user management module 402 includes ordinary users, archive administrators and system administrators. The system administrator has the highest authority. According to actual needs, ordinary users can be set as archive administrators and any ordinary users or archive administrator users can be set as blacklist users. The RESTful interface setting module 403 is used to add and update the relevant keys required for interface calls, and the login password needs to be verified before querying and updating the keys.

[0040] The secure storage unit 5 includes a data upload module 501, a data access module 502, a data verification module 503 and a record tracing module 504. The data upload module 501 encrypts the data through an asymmetric encryption algorithm and then sends it to the server. The server generates a file based on the received data and calculates a digital summary. The data access module 502 verifies the transaction signature of the user's request. After the correct completion, the Pow algorithm is used to reach a blockchain transaction consensus. The server obtains the file address and obtains the ciphertext from the file address, and then obtains the file data from the Ceph cluster. The data verification module 503 performs integrity verification on the obtained ciphertext data based on the user's access data. The record tracing module 504 verifies the transaction signature through the blockchain node, and then packages the access transaction and broadcasts it to the entire network. Finally, the blockchain network uses the Pow algorithm to reach a consensus on the transaction. The Pow algorithm is specifically as follows:

[0041]

[0042] In the formula, Indicates twice Hash operation, Represents the block header information, which contains Fields, represents the target threshold difficulty, represents the maximum target value, Indicates the current difficulty value.

[0043] The block synchronization unit 6 user starts the blockchain node to access the alliance chain. During the access process, the alliance chain network will authenticate the node, and only legitimate nodes will successfully join the alliance chain. After accessing the network, the node starts the listening thread, waits for the peer nodes in the network to broadcast data, and checks whether its own block is the latest. If not, it synchronizes the block from other nodes. The error monitoring unit 8 captures the error information through the application and sends an HTTP request to the error collection interface. The error collection interface verifies the legitimacy of the request. If it is illegal, it will directly alarm, otherwise it will store the decrypted data in the message queue. The error handling script requests data from the message queue and determines whether there is a corresponding alarm strategy. If there is an alarm strategy, it will execute the alarm strategy and display the error information to the system administrator, otherwise it will display the error information directly.

[0044] When the server is offline or stops running, the remote monitoring unit 9 continuously checks whether the system is in an abnormal state. If an abnormality is detected, it attempts to start server status monitoring and application error monitoring to obtain specific monitoring information, and sends an alarm notification to the system administrator. The system sets a counter to count the number of startups. First, it checks whether the status monitoring unit 7 has successfully completed the TCP connection. If the connection is successful, it indicates normal startup and the counter is set to 0. Otherwise, the counter starts counting. When the counter is 3, an alarm message is sent. Otherwise, it continues to determine whether the counter is greater than 3. If it is not satisfied, the counter is increased by 1. Otherwise, the counter is set to 4 to lock the system and force an alarm, and the monitoring and judgment are repeated.

[0045] The log processing unit 10 includes a data recording module 1001, a data statistics module 1002 and an auxiliary analysis module 1003. The data recording module 1001 automatically records the change log of the archive and regularly searches whether there is any log missing. The data statistics module 1002 counts the number of archives according to the category of the archive, the type of file and the upload time. The auxiliary analysis module 1003 summarizes the log information of different time periods to analyze and evaluate the timeliness of the log data later, providing a reference for subsequent system maintenance.

[0046] The McEliece public key cryptography system is divided into the password generation phase, the encryption phase and the decryption phase, specifically:

[0047] Password generation phase ,

[0048] Encryption Phase ,

[0049] Decryption Phase ;

[0050] In the formula, for superior About GOPPA Code C The order generating matrix, where , is a positive integer, , , is the error correction capability of code C, for A non-singular matrix of order, for permutation matrix, and Fast decoding algorithm for codes As a private key, Published publicly as a public key, for Medium length And the weight is less than or equal to t, the plaintext , ciphertext .

[0051] Working principle: The present invention completes the query, borrowing, updating and migration operations of archives through the archive operation unit 1. When querying, fuzzy query is performed by using keywords and precise query is performed by using file numbers. The archive data is stored in the Ceph cluster in the form of files. The RESTful interface is called to obtain the data file location from the blockchain and then the target data is found from the Ceph cluster. The target data and the data queried from the local database are taken as a union and sent to the user. Borrowing archives requires completing permission authentication first. Updating archives directly replaces the updated attachments and updates the archive attributes in the local database, and the modified attachments and attributes of the archives are stored on the blockchain. When migrating archives, a new storage path is established to replace the original storage path to store data. Comparison and verification are performed to ensure that the updated data is the same as the original data. The business functions of archive management are realized through the archive management unit 2, including user permission check, archive synchronization and archive verification. Through the service configuration unit 3, the central server is used as the middle layer to communicate with the user end upward to provide the user with a Restful interface, and downward to the object gateway of the Ceph cluster and the nodes in the Ethereum network Communication, calling the interface of the object gateway to complete the data update operation, through the system setting unit 4 by setting the management archive template, management user and management RESTful interface to expand the functionality of the system, through the secure storage unit 5 to store the archive data securely, and the file address of the file stored in the Ceph cluster is distributed and stored on the blockchain node, the secure storage unit 5 includes data upload, data access, data verification and access record traceability, data upload encrypts the data through an asymmetric encryption algorithm, data access verifies the transaction signature of the user's request, and uses the Pow algorithm to reach a blockchain transaction consensus, the server obtains the file address, and obtains the ciphertext from the file address, and then obtains the file data from the Ceph cluster, the data verification performs integrity verification on the obtained ciphertext data, the access record traceability verifies the transaction signature, and the access transaction is packaged and broadcast to the entire blockchain network for coverage, and a transaction consensus is reached, and the information synchronization of each block in the blockchain is realized through the block synchronization unit 6, ensuring that when obtaining the data of the blockchain, you can arbitrarily select a block to obtain data, thereby not affecting the correctness of the data and improving the data access efficiency.

[0052] The state monitoring unit 7 uses the active reporting method to send the monitoring information in the target server to the central server, configures the public network IP for the central server, collects and summarizes the monitoring information on each edge server, and then actively establishes a TCP connection with the central server to report the monitoring information. The error monitoring unit 8 uses the HTTP interface to collect the error information of the application. When the application captures the error information, it sends an HTTP request to the error collection interface. The error collection interface verifies the legality of the request and directly alarms the illegal request. If it is legal, the corresponding alarm strategy that has been determined to exist is executed through the error handling script, and the error information is displayed to the system administrator. If the alarm strategy is judged not to exist, the alarm strategy is not directly displayed. The remote detection unit 9 continuously checks the running status of the system. When the server is offline and not working, when an abnormality is detected, the server status monitoring and application error monitoring are tried to be started to obtain specific monitoring information, and an alarm notification is sent to the system administrator. The system determines through a counter to ensure the security of the archive system. The log processing unit 10 records the archive change information and the historical access log, which provides a reference for subsequent system maintenance.

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

[0054] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A blockchain-based archive information monitoring and management system, comprising an archive operation unit (1), a system setting unit (4), a block synchronization unit (6), a remote monitoring unit (9) and a log processing unit (10), characterized in that: An archive management unit (2), the archive management unit (2) is used to implement the business function of archive management, all modifications and migrations of archives are stored on the blockchain through a RESTful interface, and for a specific archive queried, the user end needs to verify the archive in the local database and obtain the viewing authority of the archive data on the blockchain; A service configuration unit (3), wherein the service configuration unit (3) uses a central server as a service end, communicates with a user end of the archive management unit (2), and provides a RESTful interface for the user end. In addition, the service end communicates with an object gateway of the Ceph cluster and a node in the Ethereum network, and calls an interface of the object gateway to complete a data update operation; A secure storage unit (5), wherein the secure storage unit (5) stores the archive data accessed by the user end in the form of files in the Ceph cluster, stores the file location information in the blockchain, and deploys the developed smart contract on the blockchain node, and then uses the encryption algorithm and digital signature technology of the McEliece public key cryptography system to provide RESTful interface services; A status monitoring unit (7), wherein the status monitoring unit (7) sends the monitoring information in the target server to the central server in an active reporting manner, configures a public network IP for the central server, collects and aggregates the monitoring information on each edge server, and then actively establishes a TCP connection with the central server to report the monitoring information; An error monitoring unit (8), wherein the error monitoring unit (8) collects error information in the application through an HTTP interface and executes a corresponding alarm strategy. The HTTP interface records the error information and sends the alarm information to the corresponding system manager according to the alarm rules; The block synchronization unit (6) is used by a user to start a blockchain node to access the alliance chain. During the access process, the alliance chain network will authenticate the node. Only legitimate nodes can successfully join the alliance chain. After accessing the network, the node starts a listening thread, waits for the peer node in the network to broadcast data, and checks whether its own block is the latest. If not, it synchronizes blocks from other nodes. The error monitoring unit (8) captures error information through the application, sends an HTTP request to the error collection interface, and the error collection interface verifies the legitimacy of the request. If it is not legitimate, it directly issues an alarm. Otherwise, it stores the decrypted data in the message queue. The error handling script requests data from the message queue and determines whether there is a corresponding alarm strategy. If there is, the alarm strategy is executed and the error information is displayed to the system administrator. Otherwise, the error information is directly displayed. When the server is offline or stopped, the remote monitoring unit (9) continuously checks whether the system is in an abnormal state. If an abnormality is detected, it attempts to start server status monitoring and application error monitoring to obtain specific monitoring information, and sends an alarm notification to the system administrator. The system sets a counter to count the number of startups. First, it checks whether the status monitoring unit (7) successfully completes the TCP connection. If the connection is successful, it indicates normal startup and the counter is set to 0. Otherwise, the counter starts counting. When the counter is 3, an alarm message is sent. Otherwise, it continues to determine whether the counter is greater than 3. If it is not satisfied, the counter is increased by 1. Otherwise, the counter is set to 4 to lock the system and force an alarm, and the monitoring and judgment are repeated.

2. According to the blockchain-based archive information monitoring and management system of claim 1, it is characterized by: The archive operation unit (1) comprises an archive query module (101), an archive borrowing module (102), an archive update module (103) and an archive migration module (104). The archive query module (101) is divided into fuzzy query and precise query. A fuzzy query is performed on the archive by using a keyword, and a precise query is performed on the archive by using a file number. Both of them uniformly query the local database and call the RESTful interface to obtain the file storage address in the blockchain, and then obtain the archive data from the Ceph cluster, take the union of the data set obtained by the query in the local database, and send it to the user end. The archive borrowing module (102) The authority verification is performed before the file is borrowed, and the user who passes the verification authority can successfully borrow. The file update module (103) checks the file information in the update form, stores the newly added attachments to the local disk, directly replaces the updated attachments, updates the file attributes in the local database, and stores the modified attachments and attributes of the file on the blockchain. The file migration module (104) system automatically displays the original storage path configured for this part of the data. The user specifies the new storage path to perform migration. During the migration, the data under the original storage path is retained and not deleted. After the migration is completed, the migrated data is compared and verified with the original data. After confirming that the migrated data is accurate, the original data is deleted.

3. According to the blockchain-based archive information monitoring and management system of claim 1, it is characterized by: The archive management unit (2) comprises a permission checking module (201), an archive synchronization module (202) and an archive verification module (203). The permission checking module (201) obtains a user role for a logged-in user, determines whether the user's operation permissions are included in a pre-recorded permission list, and if so, allows access; otherwise, denies access. The archive synchronization module (202) makes the archive information in the local database consistent with the Ceph cluster storage information. The archive verification module (203) obtains archive attribute and attachment information, calculates a digital fingerprint for an existing attachment, and then sends the archive attribute to a RESTful interface for verification. Non-existing attachments are sent to the RESTful interface for direct verification.

4. According to the blockchain-based archive information monitoring and management system of claim 1, it is characterized by: The system setting unit (4) includes a template management module (401), a user management module (402) and a RESTful interface setting module (403). The template management module (401) is used to specify a property list of a certain type of archive. Template management includes adding, querying, deleting and updating operations on existing template properties. In addition, if there is an archive using the module, the deletion operation cannot be performed. The user management module (402) includes ordinary users, archive administrators and system administrators. The system administrator has the highest authority. According to actual needs, ordinary users are set as archive administrators and any ordinary users or archive administrator users are set as blacklist users. The RESTful interface setting module (403) is used to add and update related keys required for interface calls, and login passwords need to be verified before querying and updating keys.

5. According to the blockchain-based archive information monitoring and management system of claim 1, it is characterized by: The secure storage unit (5) comprises a data upload module (501), a data access module (502), a data verification module (503) and a record tracing module (504). The data upload module (501) encrypts the data by using an asymmetric encryption algorithm and then sends the data to the server. The server generates a file based on the received data and calculates a digital summary. The data access module (502) verifies the transaction signature of the user's request. After the verification is completed correctly, a blockchain transaction consensus is reached using the Pow algorithm. The server obtains the file address and obtains the ciphertext from the file address, and then obtains the file data from the Ceph cluster. The data verification module (503) performs integrity verification on the obtained ciphertext data based on the user's access data. The record tracing module (504) verifies the transaction signature through the blockchain node, and then packages the access transaction and broadcasts it to the entire network. Finally, the blockchain network reaches a consensus on the transaction using the Pow algorithm.

6. According to the blockchain-based archive information monitoring and management system of claim 1, it is characterized by: The log processing unit (10) comprises a data recording module (1001), a data statistics module (1002) and an auxiliary analysis module (1003). The data recording module (1001) automatically records the change log of the archive and regularly searches whether there is any log missing. The data statistics module (1002) counts the number of archives according to the category of the archive, the type of the file and the upload time. The auxiliary analysis module (1003) summarizes the log information of different time periods, so as to analyze and evaluate the timeliness of the log data later and provide a reference basis for the subsequent system maintenance.