Local area network file management, reading, classification and query method

Abstract

The invention discloses a local area network archive management, reading, classification and query method, which comprises the following steps: sending archive data and metadata information to an archive management server, checking the received archive data through the archive management server, and carrying out classified storage according to the archive data capacity; a client needs to verify the identity of a user, if small-capacity archive data and medium-capacity archive data are read, the archive management server sends the data to the client through a local area network, if large-capacity data are read, the large-capacity data needing to be read are divided into a plurality of data blocks through the archive management server, and the data blocks are stored in the archive management server. And transmitting the plurality of data blocks to a client through a block transmission mode, and recombining the plurality of data blocks through the client to complete reading of the archive data. According to the method, idle and waste of resources can be reduced, the file storage stability is improved, the reading fluency is improved, and the retransmission data volume is remarkably reduced.

Description

Technical Field

[0001] This invention relates to a method, and more particularly, to a method for managing, reading, classifying, and querying files on a local area network. Background Technology

[0002] In local area network (LAN) environment-based record management scenarios, with the expansion of business scale of enterprises, institutions, and other organizations, the amount of record data has exploded, covering various types such as documents, drawings, videos, and audio. Moreover, the size of different records varies greatly, ranging from small text files to large engineering drawings or high-definition video files. Traditional record management methods, on the one hand, store small-capacity records on large-capacity, high-cost storage devices, resulting in resource waste; or large-capacity records are frequently migrated due to insufficient remaining storage space, increasing the risk of data corruption. On the other hand, in the record reading and transmission process, traditional methods use a uniform transmission strategy for records of different sizes, without optimizing for the transmission characteristics of large-capacity records. When reading large-capacity records, the large amount of data transmitted in a single transmission often leads to excessive LAN bandwidth consumption, affecting the transmission of other business data. Furthermore, if some data is lost or corrupted during transmission, all record data must be retransmitted, further reducing reading efficiency, and in severe cases, even causing transmission interruption.

[0003] Therefore, those skilled in the art are dedicated to providing a method for local area network file management, reading, classification, and querying that can effectively solve the above-mentioned technical problems. Summary of the Invention

[0004] To achieve the above objectives, the present invention provides a method for local area network file management, reading, classification, and querying, comprising: S1: sending file data and metadata information to a file management server, reviewing the received file data through the file management server, and classifying and storing the file data according to its capacity; S2: The client needs to verify the user's identity. Once verified, the user can retrieve the archive data. The retrieval of archive data includes retrieving small-capacity archive data, medium-capacity archive data, and large-capacity archive data. If small-capacity or medium-capacity archive data is to be retrieved, the archive management server sends it to the client via the local area network. If large-capacity data is to be retrieved, the archive management server divides the large-capacity data to be retrieved into multiple data blocks. Then, the multiple data blocks are transmitted to the client via block transmission. The client then reassembles the multiple data blocks to complete the retrieval of the archive data.

[0005] Furthermore, the process of classifying and storing archives according to their data capacity includes: Archive data capacity detection: After receiving archive data and metadata information, the archive management server starts the built-in capacity detection module to calculate the actual storage space occupied by the archive data, while excluding the storage space occupied by metadata information, and only using the capacity of the core archive data as the classification basis. The file management server dynamically generates small-capacity files, medium-capacity files, and large-capacity files based on the type of storage devices within the local area network, the percentage of remaining storage space, and historical access frequency data. The small-capacity file has a capacity less than the dynamic threshold A, where threshold A is 1% of the average remaining storage space of storage device A within the local area network. The medium-capacity file has a capacity greater than dynamic threshold A and less than dynamic threshold B, where threshold B is 5% of the average remaining storage space of storage device B within the local area network; The large-capacity file: the capacity is greater than the dynamic threshold B, and when the remaining storage space of storage device C is less than 20%, the threshold B is reduced by 10%. The reduced threshold B must not be lower than the threshold A. If it is lower than the threshold A, then the threshold B remains consistent with the threshold A. Storage device A is a small-capacity storage device, storage device B is a medium-capacity storage device, and storage device C is a large-capacity storage device.

[0006] Furthermore, the process of classifying and storing archives according to their data size also includes different matching and storage mechanisms for small-capacity, medium-capacity, and large-capacity archives, as follows: Small files are stored on several storage devices A, with priority given to storage devices A having the fastest read and write speeds. If storage devices A are the same, priority is given to storage devices A with the largest remaining storage space. At the same time, the storage location index of the file is recorded through the file management server. Medium-capacity files are stored across several storage devices B, with priority given to storage devices B having the largest remaining storage space. Large files are stored on several storage devices C. Before storage, the RAID array status of storage device C is checked. Only when the RAID array is in a normal redundancy state will the large file be stored in storage device C. At the same time, the file data is distributed and the file is split into different hard drives of storage device C.

[0007] Furthermore, the process of classifying and storing archives according to their data capacity also includes reviewing the storage capacity and reclassifying the archives. At preset intervals, the archive capacity is reviewed through the archive management server. If the stored archives increase in capacity due to data updates, upgrading them from small-capacity to medium-capacity or vice versa, then they are reclassified and stored, as follows: When a small file is upgraded to a medium file, a temporary copy is created on storage device B through the file management server. The file data is then transferred from storage device A to the temporary copy. After the transfer is complete and the data integrity is verified, the original data on storage device A is deleted, and the storage location index on the file management server is updated to complete the transfer. If a medium file is upgraded to a large file, the transfer is performed in the same way as if a small file were upgraded to a medium file. If a large file is downgraded to a medium or small file due to a reduction in data, the transfer is performed in reverse, following the same method as if a small file were upgraded to a medium file.

[0008] Furthermore, in S2, the reorganization of multiple data blocks by the client specifically includes: the file management server dividing the large amount of data to be read into segments, numbering the segments into data blocks, confirming the number of data blocks based on the numbers, and transmitting the numbering information to the client. After receiving the data block numbering information, the client establishes data bits corresponding to the data block numbers, and then transmits the numbered data blocks to the client. During transmission, each numbered data block corresponds to each data bit, thus achieving transmission sorting.

[0009] Furthermore, the transmission sorting implementation also includes a sorting self-check. If at least one data block is not transmitted to the corresponding data bit, resulting in the data bit being idle, the remaining transmitted data blocks remain unchanged, and the corresponding data blocks on the idle data bits are retransmitted through the file management server.

[0010] Furthermore, after the sorting self-check is completed, the method further includes grouping each numbered data block into groups of 10 data blocks each, then calculating the check value of each group of data blocks using the MD5 algorithm, and comparing it with the correct MD5 check values ​​of each group pre-stored in the file management server. If the check values ​​of a group are inconsistent, only the data blocks in that group are retransmitted, without the need to retransmit all data blocks.

[0011] Furthermore, prior to S1, the process includes the user selecting the file to be uploaded via the client, and then the file management server reviewing the file according to preset review rules. These preset review rules specifically include file format compliance review, file content security review, and file metadata integrity review. The review rules can be customized and updated by the administrator in the file management server backend. If the review is successful, the file can be uploaded; if the review fails, the reason for the failure is returned to the client.

[0012] Furthermore, when a file no longer needs to be retained, the user can submit a file deletion request through the client, explaining the reason for deletion. After receiving the request, the file management server will review it. If the review is approved, the file status will be marked as pending deletion. During the pending deletion period, if accidental deletion is found, the file status can be restored to normal through the recovery operation. A preset deletion time is set. When the file marked as pending deletion reaches the preset deletion time, the file will be completely deleted.

[0013] Furthermore, it also includes file retrieval. By setting search criteria and sending the set search criteria to the file management server, the search criteria include, but are not limited to, file name, file type, creation time range, department, and uploader's name. Clicking on a list item will display detailed metadata of the file and provide a download link. After the file management server retrieves the file information that meets the search criteria, it will send the file information to the client.

[0014] The present invention has the following beneficial effects: 1. This invention generates dynamic thresholds A and B by using the remaining storage space ratio of different types of storage devices within a local area network and historical access frequency, accurately classifying files into three categories—small, medium, and large—and matching them with corresponding storage devices to reduce resource idleness and waste; 2. Design dedicated storage strategies for files of different capacities. For example, small-capacity files are prioritized for the fastest read / write speed on device A, medium-capacity files are prioritized for the device with the most remaining space on device B, and large-capacity files are stored only on device C of a normal RAID array and distributed storage is used to extend the lifespan of the devices and improve the stability of file storage. 4. The file capacity is rechecked at preset times. When the file capacity increases due to data updates, the file is automatically transferred. During the transfer process, a temporary copy is created first, the data integrity is verified, and then the original data is deleted to avoid storage misalignment caused by changes in file capacity. 5. When reading large files, the data is divided into multiple data blocks by the file management server and sent to the client in a block transmission manner to avoid bandwidth congestion caused by large file transfers. 6. The client establishes corresponding data bits according to the number. During transmission, the data blocks are accurately matched with the data bits to achieve automatic sorting. At the same time, through sorting self-check, if there is a case where a data block is not transmitted in place, only the missing data block is resent, without the need for a complete retransmission, reducing invalid transmission time and improving reading smoothness. 7. Group the data blocks into groups of 10, calculate the checksum of each group using the MD5 algorithm and compare it with the pre-stored value on the server. If the checksum of a group is inconsistent, only the data block of that group is retransmitted, which significantly reduces the amount of data to be retransmitted. Attached Figure Description

[0015] Figure 1This is a flowchart illustrating a specific embodiment of the present invention. Detailed Implementation

[0016] The present invention will be further described below with reference to the accompanying drawings and embodiments: In the description of this invention, it should be noted that the terms "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0017] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "setting," and "connection" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0018] like Figure 1 As shown, 1. A method for managing, reading, classifying, and querying files on a local area network, comprising: S1: Send the archive data and metadata information to the archive management server, and the archive management server reviews the received archive data and classifies and stores it according to the archive data capacity; S2: User identity verification is required through the client. In this invention, user identity verification methods include account password verification and LAN IP binding verification. The account password is created and assigned to the user in advance by the administrator on the file management server, and is simultaneously bound to the fixed LAN IP of the user's terminal device. Verification can only be successful if both the account password is correct and the terminal IP is within the bound range. If verification fails 5 times consecutively, the account will be temporarily locked. After locking, the user needs to contact the administrator to unlock it. Verified users can retrieve file data. The retrieval of file data includes retrieving small-capacity file data, medium-capacity file data, and large-capacity file data. If reading small-capacity file data and medium-capacity file data, the file management server sends the data to the client through the LAN. If reading large-capacity data, the file management server divides the large-capacity data to be read into multiple data blocks, and then transmits the multiple data blocks to the client through a block transmission method. The client then reassembles the multiple data blocks to complete the reading of the file data.

[0019] In this invention, the file management server can be used for operations such as file entry, review, update, and deletion. At the same time, the file management server can also record the file name, type, creation time, modification time, storage path, department, and uploader of each file. The client can perform operations such as uploading, downloading, and querying files.

[0020] The process of classifying and storing archives according to their data capacity includes: Archive data capacity detection: After receiving archive data and metadata information, the archive management server starts the built-in capacity detection module to calculate the actual storage space occupied by the archive data, while excluding the storage space occupied by metadata information, and only using the capacity of the core archive data as the classification basis. The file management server dynamically generates small-capacity files, medium-capacity files, and large-capacity files based on the type of storage devices within the local area network, the percentage of remaining storage space, and historical access frequency data. The small-capacity file has a capacity less than the dynamic threshold A, where threshold A is 1% of the average remaining storage space of storage device A within the local area network. The medium-capacity file has a capacity greater than dynamic threshold A and less than dynamic threshold B, where threshold B is 5% of the average remaining storage space of storage device B within the local area network; The large-capacity file: the capacity is greater than the dynamic threshold B, and when the remaining storage space of storage device C is less than 20%, the threshold B is reduced by 10%. The reduced threshold B must not be lower than the threshold A. If it is lower than the threshold A, then the threshold B remains consistent with the threshold A. Storage device A is a small-capacity storage device, storage device B is a medium-capacity storage device, and storage device C is a large-capacity storage device.

[0021] The process of classifying and storing archives according to their data size also includes different matching and storage mechanisms for small-capacity, medium-capacity, and large-capacity archives, as follows: Small files are stored on several storage devices A, with priority given to storage devices A having the fastest read and write speeds. If storage devices A are the same, priority is given to storage devices A with the largest remaining storage space. At the same time, the storage location index of the file is recorded through the file management server. Medium-capacity files are stored across several storage devices B, with priority given to storage devices B having the largest remaining storage space. Large files are stored on several storage devices C. Before storage, the RAID array status of storage device C is checked. Only when the RAID array is in a normal redundancy state will the large file be stored in storage device C. At the same time, the file data is distributed and the file is split into different hard drives of storage device C.

[0022] The process of classifying and storing archives based on their data capacity also includes reviewing the storage capacity and reclassifying the archives. Archive capacity is reviewed at a preset time via the archive management server. This preset time can be set to 2:00 AM every Monday, and can be adjusted by the administrator in the archive management server backend based on the local area network load. During each review, the archive management server automatically iterates through all stored archives, recalculates the core data capacity of the archives, and compares it with the currently effective dynamic thresholds A and B to determine whether reclassification is necessary. If the stored archives increase in capacity due to data updates, upgrading them from small-capacity to medium-capacity or vice versa, then reclassification and storage are performed, as detailed below: When a small file is upgraded to a medium file, a temporary copy is created on storage device B through the file management server. The file data is then transferred from storage device A to the temporary copy. After the transfer is complete and the data integrity is verified, the original data on storage device A is deleted, and the storage location index on the file management server is updated to complete the transfer. If a medium file is upgraded to a large file, the transfer is performed in the same way as if a small file were upgraded to a medium file. If a large file is downgraded to a medium or small file due to a reduction in data, the transfer is performed in reverse, following the same method as if a small file were upgraded to a medium file.

[0023] In step S2, the reorganization of multiple data blocks by the client specifically includes: the file management server dividing the large amount of data to be read into segments, numbering the segments, confirming the number of data blocks based on the numbers, and transmitting the numbering information to the client. Upon receiving the data block numbering information, the client establishes data bits corresponding to the data block numbers, and then transmits the numbered data blocks to the client. During transmission, each numbered data block corresponds to its respective data bit, achieving transmission sorting. This invention, through this setup, effectively improves efficiency, eliminating the need to wait until all data blocks have been transmitted before sorting.

[0024] The transmission sorting implementation also includes a sorting self-check. If at least one data block is not transmitted to its corresponding data bit, resulting in an idle data bit, the remaining transmitted data blocks remain unchanged, and the corresponding data blocks on the idle data bits are retransmitted through the file management server. This invention effectively avoids the problem of data transmission interruption and retransmission due to partial data loss during overall transmission.

[0025] After the sorting self-check is completed, the method further includes grouping each numbered data block into groups of 10 data blocks each. Then, the checksum of each group of data blocks is calculated using the MD5 algorithm and compared with the correct MD5 checksums of each group stored in the file management server. If the checksums of a group are inconsistent, only the data blocks in that group are retransmitted, and it is not necessary to retransmit all the data blocks.

[0026] Before S1, the process also includes the user selecting the file to be uploaded via the client, and then the file management server reviewing the file according to preset review rules. These preset review rules specifically include file format compliance review (e.g., whether it conforms to preset allowed formats such as PDF, DOC, and TXT), file content security review (e.g., whether it contains malicious code or illegal sensitive information), and file metadata integrity review (e.g., whether required metadata fields such as file name, department, and uploader are filled in). The review rules can be customized and updated by the administrator in the file management server backend. If the review is successful, the upload can proceed; if the review fails, the reason for the failure is returned to the client.

[0027] When a file no longer needs to be retained, the user can submit a file deletion request through the client, explaining the reason for deletion. After receiving the request, the file management server reviews it. If the review is approved, the file status is marked as pending deletion. During the pending deletion period, if accidental deletion is discovered, the file status can be restored to normal through a recovery operation. A preset deletion time is set; when a file marked as pending deletion reaches the preset deletion time, the file is completely deleted. In this invention, the specific preset deletion time can be set according to actual needs. When a file is marked as pending deletion, the file management server will display a message indicating that the file is pending deletion and has several days remaining on the client interface and in the file list. During the pending deletion period, only the file uploader and administrator can initiate a recovery operation. After recovery, the file status is restored to normal. When the preset deletion time is reached, the file management server will completely erase the data of the file in the storage device and delete the corresponding storage location index, which is irreversible.

[0028] This invention also includes a file query function. By setting query conditions, the query conditions are sent to the file management server. The query conditions include, but are not limited to, file name, file type, creation time range, department, and uploader's name. Clicking on a list item allows users to view detailed metadata and download links for the file. After the file management server retrieves the data, it sends the file information that meets the query conditions to the client.

[0029] The optimal method for local area network file management, reading, classification, and querying in this invention is as follows: Users select the files to upload through the client, triggering the upload process. The file management server conducts a comprehensive review of the files according to preset review rules. These rules can be customized and updated by the administrator in the server backend. Specifically, the rules include checking whether the files conform to preset allowed formats such as PDF, DOC, and TXT. If the format does not conform, the review will fail. The rules also include checking whether the files contain malicious code or illegal sensitive information. If there is a security risk, the review will fail. Finally, the rules verify whether the file metadata is complete, such as the file name, department, and uploader. If any required information is missing, the review will fail. Files that pass the review proceed to the subsequent upload and storage process; if a file fails the review, the server returns a clear reason for the failure to the client, allowing the user to modify and re-upload; after receiving the file data and metadata information, the file management server activates the built-in capacity detection module to calculate the actual storage space occupied by the file data, excluding the space occupied by metadata information, and using only the core data capacity of the file as the classification basis; the server combines the storage device types in the local area network (storage device A: small capacity storage device, storage device B: medium capacity storage device, storage device C: large capacity storage device), the percentage of remaining storage space, and historical access frequency data to generate dynamic thresholds A and B. Threshold A is 1% of the average remaining storage space of all storage devices A in the local area network; threshold B is initially 5% of the average remaining storage space of all storage devices B in the local area network; when the remaining storage space of storage device C is lower than 20%, threshold B is reduced by 10%, and the reduced value must not be lower than threshold A; if it is lower, it remains consistent with threshold A; For files stored on multiple storage devices A, the device with the fastest read / write speed is selected first. If multiple storage devices A have the same read / write speed, the device with the largest remaining storage space is selected first. The file management server records the storage location index of the file. For medium-capacity files (threshold A < capacity < threshold B), the storage device B with the largest remaining storage space is selected first. For large-capacity files (capacity > threshold B), the storage device C is selected first. Before storage, the RAID array status of storage device C is checked. Only when the RAID array is in a normal redundancy state will the large-capacity file be stored on that device. During storage, the file data is distributed and split across different hard drives on storage device C. According to a preset time (default 2 AM every Monday, which can be adjusted by the administrator based on the local area network load), the file management server automatically traverses all stored files, recalculates the core data capacity of the files, and compares it with the currently effective dynamic thresholds A and B to determine whether reclassification is necessary. The server creates a temporary copy in storage device B and transfers the file data from storage device A to the temporary copy. After the transfer is completed, the data integrity is verified. Once confirmed to be correct, the original data in storage device A is deleted, and the storage location index in the server is updated to complete the transfer. Upgrading a medium-capacity file to a large-capacity file: the transfer method for upgrading a small-capacity file to a medium-capacity file is followed. If a large-capacity file is downgraded to a medium-capacity or small-capacity file due to a reduction in data, the reverse logic of the upgrade transfer is followed: first, a temporary copy is created on the target storage device, the data is transferred, the integrity is verified, and then the original storage device data is deleted and the index is updated. The system employs a dual authentication method, combining account and password with LAN IP binding. The account and password are pre-created and assigned to users by the administrator on the file management server, and are simultaneously bound to the user's terminal device's fixed LAN IP address. Users must have both the correct account and password and the terminal IP address within the bound range to pass the authentication. If an authentication fails five times consecutively, the account will be temporarily locked, and the user must contact the administrator to unlock it. After successful authentication, the file management server directly sends the file data to the client via the LAN, which the user can then access directly. The archive management server divides large amounts of data into multiple data blocks, assigns a number to each block, determines the total number of blocks, and transmits the numbering information to the client. Upon receiving the numbering information, the client creates an empty data bit corresponding to each block number. The server then transmits the numbered data blocks to the client, with each block corresponding to a data bit, achieving automatic sorting during transmission. A sorting self-check is performed during transmission. If a data block is not transmitted to its corresponding data bit, resulting in an idle data bit, the transmitted data blocks remain unchanged, and the server only retransmits the missing data block corresponding to the idle data bit. After the self-check, the numbered data blocks are grouped into groups of 10. A checksum is calculated for each group using the MD5 algorithm and compared with the pre-stored correct MD5 checksums of each group on the server. If the checksums of a group are inconsistent, only the data blocks within that group are retransmitted; there is no need to retransmit all data blocks. The client reassembles all data blocks to complete the reading process. Users set query criteria on the client, including but not limited to file name, file type, creation time range, department, and uploader's name. The client sends the query criteria to the file management server, which retrieves the matching files and sends them back to the client. Users can click on the query results list item to view detailed file metadata and download links. Users can submit file deletion requests through the client, explaining the reason for deletion. The file management server receives and reviews the requests. If approved, the file status is marked as pending deletion, and the client interface and file list will indicate the pending deletion status and the remaining retention days. During the pending deletion period, only the file uploader and administrator can initiate a recovery operation. After recovery, the file status returns to normal. When a file marked as pending deletion reaches the preset deletion time, the file management server completely erases the file's data from the storage device, deletes the corresponding storage location index, and the deletion is irreversible.

[0030] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A method for managing, reading, classifying, and querying files on a local area network, characterized in that: include: S1: Send the archive data and metadata information to the archive management server, and the archive management server reviews the received archive data and classifies and stores it according to the archive data capacity; S2: The client needs to verify the user's identity. Once verified, the user can retrieve the archive data. The retrieval of archive data includes retrieving small-capacity archive data, medium-capacity archive data, and large-capacity archive data. If small-capacity or medium-capacity archive data is to be retrieved, the archive management server sends it to the client via the local area network. If large-capacity data is to be retrieved, the archive management server divides the large-capacity data to be retrieved into multiple data blocks. Then, the multiple data blocks are transmitted to the client via block transmission. The client then reassembles the multiple data blocks to complete the retrieval of the archive data.

2. The method for managing, reading, classifying, and querying files on a local area network as described in claim 1, characterized in that, The process of classifying and storing archives according to their data capacity includes: Archive data capacity detection: After receiving archive data and metadata information, the archive management server starts the built-in capacity detection module to calculate the actual storage space occupied by the archive data, while excluding the storage space occupied by metadata information, and only using the capacity of the core archive data as the classification basis. The file management server dynamically generates small-capacity files, medium-capacity files, and large-capacity files based on the type of storage devices within the local area network, the percentage of remaining storage space, and historical access frequency data. The small-capacity file has a capacity less than the dynamic threshold A, where threshold A is 1% of the average remaining storage space of storage device A within the local area network. The medium-capacity file has a capacity greater than dynamic threshold A and less than dynamic threshold B, where threshold B is 5% of the average remaining storage space of storage device B within the local area network; The large-capacity file: the capacity is greater than the dynamic threshold B, and when the remaining storage space of storage device C is less than 20%, the threshold B is reduced by 10%. The reduced threshold B must not be lower than the threshold A. If it is lower than the threshold A, then the threshold B remains consistent with the threshold A. Storage device A is a small-capacity storage device, storage device B is a medium-capacity storage device, and storage device C is a large-capacity storage device.

3. The method for managing, reading, classifying, and querying files on a local area network as described in claim 2, characterized in that, The process of classifying and storing archives according to their data size also includes different matching and storage mechanisms for small-capacity, medium-capacity, and large-capacity archives, as follows: Small files are stored on several storage devices A, with priority given to storage devices A having the fastest read and write speeds. If storage devices A are the same, priority is given to storage devices A with the largest remaining storage space. At the same time, the storage location index of the file is recorded through the file management server. Medium-capacity files are stored across several storage devices B, with priority given to storage devices B having the largest remaining storage space. Large files are stored on several storage devices C. Before storage, the RAID array status of storage device C is checked. Only when the RAID array is in a normal redundancy state will the large file be stored in storage device C. At the same time, the file data is distributed and the file is split into different hard drives of storage device C.

4. The method for managing, reading, classifying, and querying files on a local area network as described in claim 3, characterized in that, The process of classifying and storing archives according to their data capacity also includes reviewing the storage capacity and reclassifying them. At preset intervals, the archive capacity is reviewed through the archive management server. If the stored archives increase in capacity due to data updates, upgrading them from small-capacity to medium-capacity or vice versa, then they are reclassified and stored, as follows: When a small file is upgraded to a medium file, a temporary copy is created in storage device B through the file management server. The file data is then transferred from storage device A to the temporary copy. After the transfer is completed and the data integrity is verified, the original data in storage device A is deleted. At the same time, the storage location index in the file management server is updated to complete the transfer. If a medium-sized file is upgraded to a large-sized file, it will be transferred in the same way as a small-sized file upgraded to a medium-sized file; if a large-sized file is reduced to a medium-sized or small-sized file due to data reduction, it will be transferred in the reverse way as a small-sized file upgraded to a medium-sized file.

5. The method for managing, reading, classifying, and querying files on a local area network as described in claim 4, characterized in that, In step S2, the reorganization of multiple data blocks by the client specifically includes: the file management server dividing the large amount of data to be read into segments, numbering the segments into data blocks, confirming the number of data blocks based on the numbers, and transmitting the numbering information to the client. After receiving the data block numbering information, the client establishes data bits corresponding to the data block numbers, and then transmits the numbered data blocks to the client. During transmission, each numbered data block corresponds to each data bit, thus achieving transmission sorting.

6. The method for managing, reading, classifying, and querying files on a local area network as described in claim 5, characterized in that, The transmission sorting also includes sorting self-check. If at least one data block is not transmitted to the corresponding data bit, resulting in the data bit being idle, the remaining transmitted data blocks remain unchanged, and the corresponding data blocks on the idle data bits are resent through the file management server.

7. The method for managing, reading, classifying, and querying files on a local area network as described in claim 5, characterized in that... After the sorting self-check is completed, the method further includes grouping each numbered data block into groups of 10 data blocks each. Then, the check value of each group of data blocks is calculated using the MD5 algorithm and compared with the correct MD5 check values ​​of each group pre-stored in the file management server. If the check values ​​of a group are inconsistent, only the data blocks in that group are retransmitted, and it is not necessary to retransmit all data blocks.

8. The method for managing, reading, classifying, and querying files on a local area network as described in claim 7, characterized in that, Before S1, the process also includes the user selecting the file to be uploaded through the client, and then the file management server reviewing the file according to preset review rules. The preset review rules specifically include file format compliance review, file content security review, and file metadata integrity review. The review rules can be customized and updated by the administrator in the background of the file management server. If the review is successful, the file can be uploaded. If the review fails, the reason for the failure is returned to the client.

9. The method for managing, reading, classifying, and querying files on a local area network as described in claim 7, characterized in that, When a file no longer needs to be retained, the user can submit a file deletion request through the client, explaining the reason for deletion. After receiving the request, the file management server will review it. Once the review is approved, the file status will be marked as pending deletion. During the pending deletion period, if accidental deletion is found, the file status can be restored to normal through the recovery operation. The preset deletion time will be used to completely delete files marked for deletion.

10. The method for managing, reading, classifying, and querying files on a local area network as described in claim 7, characterized in that, It also includes file retrieval. By setting search criteria, the client can send the set search criteria to the file management server. Search criteria include, but are not limited to, file name, file type, creation time range, department, and uploader's name. Clicking on a list item will display detailed metadata of the file and provide a download link. After the file management server retrieves the file information that matches the search criteria, it will send the file information to the client.

Images