Housing accumulation fund file management method, system, device, medium and product

Abstract

The invention discloses a housing fund archive management method, system and device, a medium and a product, and relates to the technical field of data processing.The method comprises the steps that when an archive uploading instruction input by a user is received, the archive type of an archive to be uploaded is obtained from the archive uploading instruction; outputting a file template matched with the file type of the file to be uploaded; receiving a target archive file uploaded by the user based on the archive template, and determining a dynamic identifier of the target archive file as a new identifier; verifying the target archive file based on the archive template to obtain a verification result; if the verification result shows that the target archive file is matched with the archive template, updating the dynamic identifier of the target archive file to be in auditing, and encrypting the target archive file to obtain an encrypted archive file; respectively storing the encrypted archive files into a plurality of storage spaces; wherein each storage space stores one encrypted archive file, and the archive management efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a housing provident fund archive management method, system, equipment, medium and product. Background Art

[0002] Housing provident fund is a long-term housing savings mechanism established by the state to protect the housing welfare of employees. Its purpose is to help employees solve housing problems and improve their living standards. With the rapid development of social economy and the continuous expansion of the real estate market, the role of housing provident fund has become increasingly apparent and has become an important source of housing loans for many employees. However, the management of housing provident fund involves a large number of complex files, including basic information of deposit units and employees, deposit and withdrawal records, loan application materials, and repayment progress.

[0003] In the current practice of housing provident fund management, file management has become a crucial work content. The quality of file management directly affects the efficiency and accuracy of the operation of the provident fund, and is also related to the personal rights and interests of citizens. Since housing provident fund files often contain sensitive information such as personal privacy and financial status, the standardization, security and timeliness of file management are particularly important.

[0004] At present, provident fund file management faces some practical problems. When users upload file materials, they may not be clear about the format of the uploaded file materials. When managers conduct subsequent review, they may find that there are problems with the file materials uploaded by users. At this time, users need to prepare the materials again and upload them again. This upload review method of file materials cannot timely review the correctness of the file materials, which causes users to prepare file materials repeatedly, reducing the efficiency of file management. Summary of the invention

[0005] The purpose of this application is to provide a housing provident fund archive management method, system, equipment, medium and product, which can improve the efficiency of archive management.

[0006] To achieve the above objectives, this application provides the following solutions: In a first aspect, the present application provides a housing provident fund file management method, comprising: When receiving a file upload instruction input by a user, obtaining the file type of the file to be uploaded from the file upload instruction; wherein the file type is a deposit type, a withdrawal type, a loan type, and an account change type; Outputting a file template that matches the file type of the file to be uploaded; wherein the file template at least includes the file type, file size, and file content requirements; receiving a target archive file uploaded by a user based on the archive template, and determining the dynamic identifier of the target archive file as a newly created identifier; Verifying the target archive file based on the archive template to obtain a verification result; If the verification result indicates that the target archive file matches the archive template, the dynamic identification of the target archive file is updated to "under review", and the target archive file is encrypted to obtain an encrypted archive file; and multiple storage spaces for the encrypted archive file are determined; and the encrypted archive file is stored in the multiple storage spaces respectively; wherein each storage space stores a copy of the encrypted archive file.

[0007] Optionally, verifying the target archive file based on the archive template to obtain a verification result specifically includes: Obtaining a target file type and a target file size of the target archive file; Recognize the target archive file by using OCR technology to obtain the target file content of the target archive file; Based on the file type, file size and file content requirements in the archive template, the target file type, the target file size and the target file content are respectively verified to obtain a verification result; wherein, when the target file type is the same as the file type, the target file size is less than or equal to the file size, and the target file content matches the file content requirement, the verification result is passed.

[0008] Optionally, the housing provident fund archive management method further includes: If the verification result indicates that the target archive file does not match the archive template, an upload error message of the target archive file is generated; wherein the upload error message includes at least one error type and a modification prompt corresponding to the error type; the error type is a file type error, a file size error, and a file content error; The error message is outputted so that the user can modify the target archive file based on the error message.

[0009] Optionally, the housing provident fund archive management method further includes: If the verification result indicates that the target archive file does not match the archive template, obtaining the total number of target archive files uploaded within a preset time period; Determine the number of failed target archive files and error types of failed uploads from the uploaded target archive files; Determine, from the target archive file that failed to be uploaded, a first failure number corresponding to the file type error, a second failure number corresponding to the file size error, and a third failure number corresponding to the file content error; If the ratio of the number of failures to the total number is greater than or equal to a preset threshold, determining the largest target number of failures from the first number of failures, the second number of failures, and the third number of failures; Based on the target error type corresponding to the target failure number, generating adjustment information corresponding to the target error type; Based on the adjustment information, each file template matching each file type is adjusted to obtain an adjusted file template.

[0010] Optionally, if the target failure number is the second failure number, generating adjustment information corresponding to the target error type based on the target error type corresponding to the target failure number specifically includes: Calculate an adjustment factor based on the number of failures, the total number, and a preset correction coefficient; Based on the adjustment factor and the file size, calculating and obtaining adjustment information of the file size; The adjustment information of the file size is determined as adjustment information corresponding to the target error type.

[0011] Optionally, the calculation formula of the adjustment factor is:

[0012] in, represents the adjustment factor, represents the number of failures, represents the total quantity, represents the preset correction coefficient; And, the calculation formula of the file size adjustment information is:

[0013] Wherein, S represents the adjustment information of the file size, Indicates the size of the file.

[0014] In the second aspect, the present application provides a housing provident fund archive management system, including: An acquisition unit, configured to acquire the file type of the file to be uploaded from the file upload instruction when receiving the file upload instruction input by the user; wherein the file type is a deposit type, a withdrawal type, a loan type, and an account change type; An output unit, used to output a file template matching the file type of the file to be uploaded; wherein the file template at least includes the file type, file size and file content requirements; A receiving unit, configured to receive a target archive file uploaded by a user based on the archive template, and determine the dynamic identifier of the target archive file as a newly created identifier; A verification unit, configured to verify the target archive file based on the archive template to obtain a verification result; A storage unit is used for updating the dynamic identification of the target archive file to "under review" if the verification result indicates that the target archive file matches the archive template, and encrypting the target archive file to obtain an encrypted archive file; and determining multiple storage spaces for the encrypted archive file; and storing the encrypted archive file in the multiple storage spaces respectively; wherein each storage space stores a copy of the encrypted archive file.

[0015] In a third aspect, the present application provides a computer device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any one of the housing provident fund archive management methods described above.

[0016] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any one of the housing provident fund archive management methods described above.

[0017] In a fifth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of any one of the housing provident fund archive management methods described above.

[0018] According to the specific embodiments provided in this application, this application discloses the following technical effects: The present application provides a housing provident fund archive management method, system, device, medium and product, which can output an archive template matching the archive type according to the archive type that the user wants to upload, so that the user can prepare the archive file to be uploaded according to the requirements in the archive template; and can perform real-time format verification on the target archive file uploaded by the user, and the target archive file can be stored only when the target archive file is consistent with the requirements of the archive template. It can be seen that in this way, the correctness of the archive data can be reviewed in time, so that the user can immediately know whether there is a problem with the uploaded archive data after uploading the archive data, and if the uploaded archive data needs to be modified, it can be modified immediately, thereby improving the efficiency of archive management. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 This is a flow chart of a housing provident fund file management method in one embodiment of the present application; Figure 2 A schematic diagram of the functional modules of a housing provident fund archive management system provided in one embodiment of the present application; Figure 3 A schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

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

[0022] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0023] In an exemplary embodiment, Figure 1 As shown, a housing provident fund file management method is provided, which is executed by a computer device, specifically, it can be executed by a computer device such as a terminal or a server alone, or it can be executed by a terminal and a server together. In the embodiment of the present application, the following steps 101 to 105 are included. Among them: Step 101: when a file upload instruction input by a user is received, the file type of the file to be uploaded is obtained from the file upload instruction.

[0024] In the embodiment of the present application, the file types are deposit type, withdrawal type, loan type and account change type; wherein: Files of deposit types: including deposit records of individuals and units, such as monthly deposit amounts and deposit ratios.

[0025] Withdrawal type files: files related to housing provident fund withdrawal, covering withdrawal application and approval information, etc.

[0026] Loan type files: files related to employee provident fund loan applications, approvals and contracts.

[0027] Files of account change type: record changes in account status, such as account mergers, transfers or settlements.

[0028] This classification structure allows archives to be queried according to different dimensions, making it easier for managers to quickly locate the information they need.

[0029] Step 102: output a file template that matches the file type of the file to be uploaded.

[0030] In the embodiment of the present application, the file template includes at least the file type, file size and file content requirements; a corresponding file template is designed for each type of file to ensure that the file meets the unified standards when entering. Each template contains the following requirements: 1. File type: clearly specify acceptable file types, such as text documents, pictures, audio and video files, etc., and file formats such as PDF, JPEG, TXT, etc. In addition, the acceptable file types must correspond to the nature of the archives. For example, PDF files are used to store contracts, approval documents, etc.; image files (such as JPEG, PNG) are used to store ID card scans and other image materials.

[0031] 2. File size: Set an upper limit on the size of a single file to prevent overly large files from taking up too much storage space, thereby improving the response speed of the management system.

[0032] 3. File content: Choose a reasonable storage path and file naming rules based on the file type and file attributes. The storage path and file naming rules can be divided according to the file type, upload date or personal information, which is convenient for quick query and file retrieval and reduces the possibility of information confusion. For example: Path format: / Provident Fund Files / Deposit Files / 2024 / Zhang San / File naming convention: Zhang San_2024_Provident Fund Payment Record.pdf Step 103: receiving a target archive file uploaded by a user based on the archive template, and determining the dynamic identifier of the target archive file as a newly created identifier.

[0033] In the embodiment of the present application, dynamic identification: In the process of file management, a status identifier is assigned to each file to indicate its current processing status. Through this identifier, the processing progress of the file can be accurately tracked, and the status of the file can be queried at any time. Common statuses include: New: The file has just been created and has not been reviewed or processed yet.

[0034] Under Review: The file has been submitted for review and is waiting for approval by the reviewer.

[0035] Archived: The file has passed the review and has been officially archived.

[0036] Completed: All processing procedures are completed, and the file status is marked as finalized and is only for reference.

[0037] These dynamic identifiers can accurately reflect the progress of each file at different time points, ensuring that managers can grasp the processing status of each file in real time and ensure that the file will not be delayed or missed in the process. Status updates can be manually triggered (by user operations) or automatically triggered (controlled by system rules).

[0038] Lifecycle management: Ensure that each file has a clear management process from creation to archiving and its subsequent storage, use, update and destruction. The specific steps are as follows: (1) Archive creation and initial status allocation When a new file is entered into the system, it is automatically assigned the initial status "New", i.e., the status identifier S_1. At this time, the creation time of the file is recorded and filed in the "pending" area of ​​the database.

[0039] (2) Status Update The status of the file is updated according to its processing progress. When the file enters the next processing stage, the system automatically modifies its status identifier and records the time of the status change. For example, when the file is submitted for review, the status will be updated from "New" to "Under Review", corresponding to the status identifier S_2. This update is usually completed automatically by the system, but in some cases it may require manual operation. The status update record provides a complete historical track for file management, which is convenient for future query, audit and tracking of problem files.

[0040] (3) Audit process management During the review phase, the status change of the file is controlled by the preset state transition matrix. After the review process is completed, if the file passes the review, the status will be updated to "Archived", corresponding to the status identifier S_3. If the file fails the review, it will be returned to the "New" or "Revised" status and the relevant changes will be recorded.

[0041] (4) Archiving and Status End When all processes are completed and the file is archived, the system will mark it as "completed", corresponding to the status indicator S_4, at which point the life cycle of the file enters the termination stage. The archived file enters read-only mode, mainly for query and viewing, and can no longer be modified or otherwise operated, which can effectively prevent the file from being misoperated or illegally tampered with.

[0042] State Management Model In dynamic identification and lifecycle management, the state management model defines the rules for archive state changes through the state transition matrix. Table 1 shows how to transition from one state to the next: Table 1 State transition table

[0043] Through the above model, the change conditions and subsequent states of each state can be clearly defined, ensuring transparent and orderly archival processing.

[0044] Through dynamic identification and life cycle management, the management of housing provident fund archives can achieve process standardization, information transparency and efficient tracking, effectively improving the processing efficiency and security of archives.

[0045] Step 104: verify the target archive file based on the archive template to obtain a verification result.

[0046] In the embodiment of the present invention, after uploading the target archive file, a series of verification operations are performed when the user uploads the file to ensure that the file meets the preset requirements, which may include file format verification, file size verification and file content inspection.

[0047] File format verification: Verify the file format uploaded by the user according to the pre-defined template. Each archive file must meet the established format requirements, such as file type and structure specifications, to ensure that the file content can be correctly parsed. Specifically include: File type check: Check whether the uploaded file conforms to the specified type (such as PDF, Word, Excel, etc.). For example, provident fund business files are usually required to be uploaded in PDF format to avoid format problems when editing files.

[0048] Template structure verification: perform structure verification on the uploaded file to ensure that the file content complies with the required fields and format specifications. For example, when the provident fund file requires filling in employee information and provident fund payment records in a certain specified location, check whether these formats are correct.

[0049] If the file format does not match, the file will be automatically rejected and the user will be prompted to re-upload it in the specified format.

[0050] File size verification: Use the above formula to verify the file size. If the file exceeds the limit, the system will automatically refuse to upload it.

[0051] Strictly control the size of uploaded files, set the file size limit to Smax, and verify the file size S. When the size of the uploaded file S≦Smax, the file is allowed to proceed to the next step of processing. Otherwise, the file upload is automatically rejected and the user is prompted to adjust the file size.

[0052] File content check: After the format and size verification are passed, OCR (optical character recognition) technology is used to scan the file content and extract key fields, such as provident fund account number, employee name, ID number and payment record; then the pipe information in the file is structured to ensure that the extracted fields meet the expected format requirements. For example, the provident fund account number should be in digital format, and the ID number must comply with the 18-digit format required by the state; finally, the extracted content is compared with the information entered by the user when submitting to ensure that the input information is accurate. If the recognized content does not match the information provided by the user, the user will be automatically prompted to recheck the input content or uploaded file. For example, when the provident fund account recognition result does not match the existing account record in the system, the system will remind the user to check the archive file.

[0053] As an optional implementation, step 104 verifies the target archive file based on the archive template, and the method of obtaining the verification result may specifically include: Obtaining a target file type and a target file size of the target archive file; Recognize the target archive file by using OCR technology to obtain the target file content of the target archive file; Based on the file type, file size and file content requirements in the archive template, the target file type, the target file size and the target file content are respectively verified to obtain a verification result; wherein, when the target file type is the same as the file type, the target file size is less than or equal to the file size, and the target file content matches the file content requirement, the verification result is passed.

[0054] Among them, by implementing this implementation method, the file type, file size and file content of the target archive file can be verified respectively, so that the obtained verification result is more accurate.

[0055] Step 105: If the verification result indicates that the target archive file matches the archive template, the dynamic identification of the target archive file is updated to "under review", and the target archive file is encrypted to obtain an encrypted archive file; and multiple storage spaces for the encrypted archive file are determined; and the encrypted archive file is stored in the multiple storage spaces respectively.

[0056] In the embodiment of the present application, each storage space stores a copy of the encrypted archive file. After the archive file is uploaded, the file is automatically backed up, specifically including the following contents: 1. Automatic backup process. After the archive file is uploaded, the automatic backup process is triggered to back up the file to a safe storage location according to the established strategy. The backup process mainly includes steps such as file partitioning, multiple backups and data encryption.

[0057] File partitioning is to partition the uploaded files according to dimensions such as file size and type for more efficient storage and backup management.

[0058] Multiple backup creates multiple backup files according to pre-set rules and distributes them in different storage media or cloud storage to ensure that the files can still be restored even if a storage node fails.

[0059] Data encryption ensures that all backup files are encrypted before storage to ensure the confidentiality and security of backup data. Common encryption methods include AES (Advanced Encryption Standard) and RSA encryption algorithms to ensure that archive information will not be leaked due to backup.

[0060] 2. Backup strategy and formula description. The total storage capacity of backup changes with the increase of archive data. The following formula is used to calculate the overall backup capacity to ensure the reasonable use and scalability of backup resources:

[0061] Among them: Bt represents the total storage capacity of all backups in the system; Bi represents the newly added backup capacity in the i-th cycle; Bin is the initial backup capacity, that is, the size of the system's first complete backup; n is the total number of backup cycles.

[0062] 3. Regular incremental backup In order to avoid repeated backups taking up a lot of storage space, an incremental backup strategy is adopted. In each backup cycle, only newly added or changed archive data (i.e. Bi) is backed up, and existing data is no longer backed up repeatedly. This can effectively reduce the waste of storage space and improve backup efficiency.

[0063] Initial backup: During the first backup, a complete backup (i.e. Bin) is performed on all uploaded archive files. This backup file saves the complete data of all archives at that time.

[0064] Incremental backup: In subsequent backup cycles, only the files that have been added or modified since the last backup are backed up (i.e., each Bi). For example, if a user uploads a batch of new files in the second backup cycle, only these new files will be backed up in the backup of this cycle.

[0065] This incremental backup strategy can significantly save storage space while ensuring that the latest archive files are backed up in a timely manner.

[0066] 4. Backup recovery and redundancy. After the backup is completed, the backup files are stored in multiple physical or cloud storage nodes at the same time to ensure data redundancy. This multi-node storage strategy improves the recoverability and security of archive data. When a node fails or becomes unavailable, it can quickly switch to other backup nodes to ensure that data is not lost.

[0067] Recovery process: In the event of data corruption or loss, data will be automatically restored from the most recent backup. During recovery, the latest change data will be extracted from the incremental backup first, and then combined with the initial backup to complete the complete file recovery process.

[0068] 5. Backup security and permission control. To prevent unauthorized access, multiple security measures are taken as follows: Access control: Only authorized users or administrators can access backup files, ensuring the security of backup data.

[0069] Logging: Every backup operation will generate detailed log records, including information such as backup time, backup size and backup status, for easy auditing and monitoring.

[0070] Data isolation: Backup files of different users are stored separately to prevent cross-access between backup data, further improving the security of backup data.

[0071] 6. Regular backup and monitoring. Not only should backup be performed regularly, but also the integrity of the backup files should be checked regularly. Through regular verification, potential storage problems can be detected and appropriate remedial measures can be taken before the problem occurs. Administrators can view the status of each backup cycle, the backup success rate, and the amount of storage used through the backup monitoring interface to ensure the smooth progress of the backup process.

[0072] As an optional implementation, if the verification result indicates that the target archive file does not match the archive template, the method may further include: Generate upload error information of the target archive file; wherein the upload error information includes at least one error type and a modification prompt corresponding to the error type; the error type is a file type error, a file size error, and a file content error; The error message is outputted so that the user can modify the target archive file based on the error message.

[0073] Among them, by implementing this implementation method, when it is determined that the target archive file does not match the archive template, an upload error message for the target archive file can be generated, and the upload error message can be output so that the user can make targeted modifications based on the upload, thereby improving the user experience.

[0074] In the embodiment of the present application, during the file upload process, the reasons for the upload failure are recorded in real time, such as file format error, size exceeding the limit, etc. Based on this information, the upload template is dynamically optimized to improve the overall upload success rate. The dynamic optimization steps include: 1. Collect failure information: During the upload process, each failed file and the reason for the upload failure are recorded in real time. The reasons for failure may include the following common situations: File format error: The file uploaded by the user does not conform to the specified file format (for example, an unsupported file type is uploaded).

[0075] File size exceeds limit: The file size exceeds the maximum allowed limit.

[0076] Content extraction failure: OCR technology fails to recognize the file content, resulting in failure to extract key fields.

[0077] Generate an error log for each failed file, recording the file name, error type, and detailed cause, and use this information for subsequent optimization analysis.

[0078] As an optional implementation, if the verification result indicates that the target archive file does not match the archive template, the method may further include: Get the total number of target archive files uploaded within a preset time period; Determine the number of failed target archive files and error types of failed uploads from the uploaded target archive files; Determine, from the target archive file that failed to be uploaded, a first failure number corresponding to the file type error, a second failure number corresponding to the file size error, and a third failure number corresponding to the file content error; If the ratio of the number of failures to the total number is greater than or equal to a preset threshold, determining the largest target number of failures from the first number of failures, the second number of failures, and the third number of failures; Based on the target error type corresponding to the target failure number, generating adjustment information corresponding to the target error type; Based on the adjustment information, each file template matching each file type is adjusted to obtain an adjusted file template.

[0079] Among them, by implementing this implementation method, corresponding adjustment information can be generated according to the error type with more errors, so as to adjust the archive template, so that the adjusted archive template can make the user upload the target archive file with a higher success rate.

[0080] In the embodiment of the present application, the current upload template is optimized and adjusted, and the user is notified to re-upload. Common optimization directions include adjusting the upper limit of the file size, optimizing the format requirements, and improving the extraction method.

[0081] Adjust the upper file size limit: If a large number of upload failures are detected due to file size exceeding the limit, the upper file size limit may be adjusted appropriately based on the actual situation (i.e., allowing users to upload larger files). The specific size adjustment can be determined based on the adjustment factor.

[0082] Optimize format requirements: When upload failures are mainly due to file format issues, consider relaxing or increasing the supported file types. For example, archive files that originally only allow PDF format can be expanded to support Word or image formats to accommodate more upload requirements. At the same time, format prompts can be provided in real time when users upload files to reduce failures caused by format inconsistencies.

[0083] Improve extraction methods: If the frequency of OCR content extraction failure is high, the OCR technology can be upgraded and optimized based on the failure logs. For example, a more accurate recognition algorithm can be used, or users can be allowed to manually adjust key fields that failed to be automatically recognized.

[0084] Notification and feedback: After optimizing the upload conditions, users will be notified of these improvements in a variety of ways to ensure that they understand the new upload standards and guide them to re-upload files according to the optimized templates. Notification methods include: directly prompting users with new file requirements during the upload process, such as file size or format adjustments, or sending emails to users, detailing the optimization content and suggesting that users re-submit archive files that meet the new standards.

[0085] Continuous dynamic optimization: The dynamic optimization process is a cyclic operation. As time goes by and data continues to accumulate, the upload failure situation is regularly evaluated, and the upload template is continuously optimized to make it more adaptable to the actual needs of users and reduce obstacles in the upload process.

[0086] Optionally, if the target failure number is the second failure number, based on the target error type corresponding to the target failure number, a method of generating adjustment information corresponding to the target error type may specifically include: Calculate an adjustment factor based on the number of failures, the total number, and a preset correction coefficient; Based on the adjustment factor and the file size, calculating and obtaining adjustment information of the file size; The adjustment information of the file size is determined as adjustment information corresponding to the target error type.

[0087] In the embodiment of the present application, the calculation formula of the adjustment factor is:

[0088] in, represents the adjustment factor, represents the number of failures, represents the total quantity, Indicates the preset correction factor; the correction factor is used to control the adjustment range and is configured according to different situations. By calculating the adjustment factor, the proportion of upload failures can be accurately evaluated, and based on this, it can be determined whether the upload template needs to be optimized.

[0089] And, the calculation formula of the file size adjustment information is:

[0090] Wherein, S represents the adjustment information of the file size, Indicates the size of the file.

[0091] For example, suppose that the total number of files uploaded during a certain period of time is 200, and 50 files fail to upload. Based on the preset correction coefficient Rc=0.5, the calculated adjustment factor is:

[0092] This adjustment factor will be used as a reference value for template optimization, and related conditions will be further optimized based on the type of failure (such as file size problem, format problem, etc.).

[0093] In addition, you can also assign permissions and manage files for users and managers, specifically: 1. Permission control: Based on the user permission level and archive file category, each user's access rights are dynamically calculated and divided into the following: User permission level (U_level): Assign corresponding permission levels to users according to their roles and responsibilities, such as administrator, senior auditor, and ordinary user, etc. Each level corresponds to different access rights.

[0094] Archive file category (D_type): Archive files are classified according to their sensitivity or department, such as general archives, confidential archives, etc. Different categories of archives have different access permission requirements.

[0095] 2. Dynamic permission allocation The following formula is used to dynamically calculate each user's access rights to a certain type of file:

[0096] Among them, Pa represents the user's access rights to a certain type of archive, which determines whether the user can view, edit or delete the archive; Ul represents the user's permission level, and different user levels determine their operating permissions in the system; Dt represents the category of archive files, and different categories of archives may require higher permission levels to access.

[0097] The function of the above formula is to dynamically calculate the specific permission value based on the user permission level and archive file category. This formula ensures that the allocation of permissions is flexible and scalable, and can adapt to the security needs of different users and archive types.

[0098] For example: Ordinary users (low-level permissions) can only view ordinary archive files of their own department and cannot access confidential archive files; Senior auditors (high-level permissions) can not only view, but also edit and delete certain sensitive files; System administrators have the highest authority and can fully manage all types of files, including adding, deleting, modifying and checking.

[0099] 3. The process of authority allocation: including user login verification, file category determination, authority matching and verification, and operation log recording.

[0100] User login verification: When a user logs into the system, the corresponding permission level Ul is retrieved based on the user's identity authentication information.

[0101] File category determination: When a user tries to access a file, the system determines the file's category Dt based on the file's metadata.

[0102] Permission matching and verification: calling the permission calculation function , to determine whether the current user has sufficient permissions to access the file. If the user's permissions meet the requirements, the corresponding operation is allowed; otherwise, access is denied and a prompt is displayed indicating insufficient permissions.

[0103] Operation log recording: Log every file access, edit or delete operation to ensure the traceability of the operation. The log content includes user ID, operation type, file category, timestamp and other information for subsequent audit and analysis.

[0104] 4. Dynamic adjustment of authority allocation In order to adapt to user changes or responsibilities in the system, dynamic adjustment of permissions is supported. Administrators can modify the user's permission level Ul according to needs, or reclassify the category Dt of archive files. After adjustment, the system will automatically reallocate access rights according to the newly configured permission rules to ensure the flexibility and dynamism of the permission system.

[0105] 5. Archives management and security Based on the authority allocation system, the access and operation of each archive file are recorded in detail, and audit reports are generated regularly. Administrators can monitor the user's archive operation behavior through audit reports, find abnormal access or abuse of authority, and take timely measures; at the same time, in order to avoid erroneous modification or deletion, a version control function is provided for each archive file. After each edit, the historical version of the file is automatically saved, and users can restore to the previous version at any time to avoid data loss or misoperation. Through the above means, comprehensive security management functions are provided for archive files to ensure the security and controllability of archives throughout their life cycle.

[0106] 6. Security policies for rights management. In order to enhance the security of rights management, a series of security policies are designed as follows: Multi-factor authentication: For high-privilege users, multi-factor authentication (such as password + SMS verification code or fingerprint recognition) is required to further ensure the authenticity of the user's identity.

[0107] Principle of least privilege: Follow the principle of least privilege, that is, users can only obtain the minimum permissions required to complete their work, preventing unnecessary permission exposure.

[0108] Regular permission review: Administrators regularly review the permission configuration of all users to ensure the rationality of permission allocation and adjust permissions in a timely manner to prevent permission abuse.

[0109] In order to provide users with efficient file extraction functions, users can retrieve the required provident fund files according to keywords, file categories, dates and other conditions. Corresponding statistical reports can also be generated for daily management and decision support. Specifically including: 1. Efficient file retrieval function To help users quickly find the archive files they need, users can search through the following main methods: Keyword search: Users can conduct precise or fuzzy searches based on key fields of the archives, such as provident fund account number, name, ID number, etc., to quickly locate relevant archive files.

[0110] File category filtering: Provide classification filtering function according to different categories of files (such as personal files, unit files, deposit records, etc.). Users can quickly narrow the search scope by selecting a certain type of file to reduce the interference of irrelevant information.

[0111] Date range search: Users can also search by selecting the creation or update date range of archives. For example, query all archived files within a certain period of time or view audit records at a specific point in time.

[0112] Advanced search: It provides a combined search function, where users can use multiple conditions for advanced search at the same time. By entering multiple parameters, such as name + provident fund account + date range, you can further accurately lock the target file.

[0113] 2. Search results and file extraction After the user submits the search criteria, the archives are quickly matched based on the index in the database, and a list of archives that meet the criteria is presented. For the search results, operation options such as viewing archive details, downloading archive files, and batch operations are provided.

[0114] View file details: Users can click on a record to view detailed information of the file, including provident fund account, payment record and review status.

[0115] Download archive files: Supports the download function of archive files. Users can download electronic archive files to local computers as needed for subsequent use. When downloading, the system will convert the file format to ensure compatibility and ease of use.

[0116] Batch operation: allows users to perform batch operations on multiple archive files, including batch downloading, batch archiving, etc., greatly improving work efficiency.

[0117] 3. Archive statistical report generation In order to assist in daily management and decision support, users are provided with the function of generating archive statistical reports. Users can generate reports in various formats according to different needs. The reports cover deposit statistics, archive review status statistics and historical archive records, etc.: Contribution statistics: Generate housing provident fund contribution statistics report based on the specified time period, covering key indicators such as total contribution amount and number of contributors.

[0118] Archive review status statistics: Generate statistical reports on the archive review status to help managers understand the current archive processing progress, such as how many files are under review and how many have been archived.

[0119] Historical archive records: Supports the generation of a historical record table of all archived files within a certain period of time for archive management and tracking of historical data.

[0120] These reports can be exported to Excel, PDF and other formats to facilitate users to further process or archive data.

[0121] 4. Security and authority control in the use of archives During the process of file extraction and use, strictly abide by the authority management strategy to ensure the safe use of files. The user's search scope and extraction operations are subject to their authority level. Specific measures include: Display search results by permissions: Users can only retrieve files that match their permission level. For example, ordinary users can only search for their own files or the files of their departments, while administrators can retrieve all files.

[0122] Logging and monitoring: The system generates an operation log for each retrieval and extraction operation, including detailed information such as operation time, user ID, extracted files, etc., for subsequent auditing and monitoring.

[0123] Sensitive data masking: For users with lower permissions, the system will mask some sensitive data in the file, such as ID number, salary information, etc., to ensure data security.

[0124] 5. Data Visualization and Analysis In order to better assist management in decision-making, by extracting and analyzing a large amount of archival data (including trend analysis and efficiency analysis), visual charts such as pie charts, bar charts and line charts are generated to intuitively display the provident fund contribution trends, archival processing progress, etc.

[0125] Trend analysis: Managers can use charts to visually view the historical trends of provident fund contributions, identify abnormal fluctuations, and adjust strategies.

[0126] Efficiency analysis: By analyzing the file review and processing process, management can evaluate the current file processing efficiency, identify process bottlenecks, and optimize business operations.

[0127] By implementing the above-mentioned steps 101 to 105, the correctness of the archival materials can be audited in time, so that the user can immediately know whether there is a problem with the uploaded archival materials after uploading the archival materials, and can immediately modify the uploaded archival materials if necessary, thereby improving the efficiency of archive management. In addition, the application can also make the obtained verification result more accurate. In addition, the application can also improve the user experience. In addition, the application can also make the obtained adjusted archive template enable the user to upload the target archive file with a higher success rate.

[0128] The present application also provides an application scenario, which applies the above-mentioned housing provident fund archive management method. Specifically: the housing provident fund archive management method provided in this embodiment can be applied in the scenario where the user uploads the housing provident fund archive. When the user chooses to handle housing provident fund related business, he needs to upload the corresponding housing provident fund archive file, and the department that manages the housing provident fund needs to manage the archive files submitted by the user. The housing provident fund archive management method provided in this embodiment belongs to the link of managing the archive files submitted by the user.

[0129] Based on the same inventive concept, the embodiment of the present application also provides a housing provident fund archive management system for implementing the housing provident fund archive management method involved above. The implementation scheme for solving the problem provided by the system is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more housing provident fund archive management system embodiments provided below can refer to the limitations of the housing provident fund archive management method above, and will not be repeated here.

[0130] In an exemplary embodiment, Figure 2 As shown, a housing provident fund archive management system is provided, including: The acquisition unit 201 is used to acquire the file type of the file to be uploaded from the file upload instruction when receiving the file upload instruction input by the user; wherein the file type is a deposit type, a withdrawal type, a loan type, and an account change type; The output unit 202 is used to output a file template that matches the file type of the file to be uploaded; wherein the file template at least includes the file type, file size and file content requirements; The receiving unit 203 is used to receive a target archive file uploaded by a user based on the archive template, and determine the dynamic identifier of the target archive file as a newly created identifier; A verification unit 204, configured to verify the target archive file based on the archive template to obtain a verification result; The storage unit 205 is used to update the dynamic identification of the target archive file to "under review" if the verification result indicates that the target archive file matches the archive template, and encrypt the target archive file to obtain an encrypted archive file; and determine multiple storage spaces for the encrypted archive file; and store the encrypted archive file in the multiple storage spaces respectively; wherein each storage space stores a copy of the encrypted archive file.

[0131] As an optional implementation, the verification unit 204 verifies the target archive file based on the archive template, and obtains the verification result in the following manner: Obtaining a target file type and a target file size of the target archive file; Recognize the target archive file by using OCR technology to obtain the target file content of the target archive file; Based on the file type, file size and file content requirements in the archive template, the target file type, the target file size and the target file content are respectively verified to obtain a verification result; wherein, when the target file type is the same as the file type, the target file size is less than or equal to the file size, and the target file content matches the file content requirement, the verification result is passed.

[0132] Among them, by implementing this implementation method, the file type, file size and file content of the target archive file can be verified respectively, so that the obtained verification result is more accurate.

[0133] As an optional implementation manner, the verification unit 204 is further configured to: If the verification result indicates that the target archive file does not match the archive template, an upload error message of the target archive file is generated; wherein the upload error message includes at least one error type and a modification prompt corresponding to the error type; the error type is a file type error, a file size error, and a file content error; The error message is outputted so that the user can modify the target archive file based on the error message.

[0134] Among them, by implementing this implementation method, when it is determined that the target archive file does not match the archive template, an upload error message for the target archive file can be generated, and the upload error message can be output so that the user can make targeted modifications based on the upload, thereby improving the user experience.

[0135] As an optional implementation manner, the verification unit 204 is further configured to: If the verification result indicates that the target archive file does not match the archive template, obtaining the total number of target archive files uploaded within a preset time period; Determine the number of failed target archive files and error types of failed uploads from the uploaded target archive files; Determine, from the target archive file that failed to be uploaded, a first failure number corresponding to the file type error, a second failure number corresponding to the file size error, and a third failure number corresponding to the file content error; If the ratio of the number of failures to the total number is greater than or equal to a preset threshold, determining the largest target number of failures from the first number of failures, the second number of failures, and the third number of failures; Based on the target error type corresponding to the target failure number, generating adjustment information corresponding to the target error type; Based on the adjustment information, each file template matching each file type is adjusted to obtain an adjusted file template.

[0136] Among them, by implementing this implementation method, corresponding adjustment information can be generated according to the error type with more errors, so as to adjust the archive template, so that the adjusted archive template can make the user upload the target archive file with a higher success rate.

[0137] As an optional implementation manner, if the target failure number is the second failure number, the verification unit 204 generates the adjustment information corresponding to the target error type based on the target error type corresponding to the target failure number in a manner that specifically can be: Calculate an adjustment factor based on the number of failures, the total number, and a preset correction coefficient; Based on the adjustment factor and the file size, calculating and obtaining adjustment information of the file size; The adjustment information of the file size is determined as adjustment information corresponding to the target error type.

[0138] In the embodiment of the present application, the calculation formula of the adjustment factor is:

[0139] in, represents the adjustment factor, represents the number of failures, represents the total quantity, represents the preset correction coefficient; And, the calculation formula of the file size adjustment information is:

[0140] Wherein, S represents the adjustment information of the file size, Indicates the size of the file.

[0141] By implementing the above-mentioned implementation mode, the correctness of the archival materials can be audited in time, so that the user can immediately know whether there is a problem with the uploaded archival materials after uploading the archival materials, and can immediately modify the uploaded archival materials if necessary, thereby improving the efficiency of archive management. In addition, the present application can also make the obtained verification result more accurate. In addition, the present application can also improve the user experience. In addition, the present application can also make the obtained adjusted archive template enable the user to upload the target archive file with a higher success rate.

[0142] In an exemplary embodiment, a computer device is provided. The computer device may be a server or a terminal. The internal structure diagram thereof may be as follows: Figure 3As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store video tag processing data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a housing provident fund file management method is implemented.

[0143] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0144] In an exemplary embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0145] In an exemplary embodiment, a computer-readable storage medium is provided, storing a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0146] In an exemplary embodiment, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0147] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0148] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).

[0149] The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. The non-relational database may include a distributed database based on blockchain, etc., but is not limited thereto. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but is not limited thereto.

[0150] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0151] This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only used to help understand the method and core ideas of this application. At the same time, for those skilled in the art, according to the ideas of this application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A housing provident fund file management method, It is characterized in that The housing provident fund archive management method comprises: When receiving a file upload instruction input by a user, obtaining the file type of the file to be uploaded from the file upload instruction; wherein the file type is a deposit type, a withdrawal type, a loan type, and an account change type; Outputting a file template that matches the file type of the file to be uploaded; wherein the file template at least includes the file type, file size, and file content requirements; receiving a target archive file uploaded by a user based on the archive template, and determining the dynamic identifier of the target archive file as a newly created identifier; Verifying the target archive file based on the archive template to obtain a verification result; If the verification result indicates that the target archive file matches the archive template, the dynamic identification of the target archive file is updated to "under review", and the target archive file is encrypted to obtain an encrypted archive file; and multiple storage spaces for the encrypted archive file are determined; and the encrypted archive file is stored in the multiple storage spaces respectively; wherein each storage space stores a copy of the encrypted archive file.

2. The housing provident fund file management method according to claim 1, It is characterized in that The verifying the target archive file based on the archive template to obtain a verification result specifically includes: Obtaining a target file type and a target file size of the target archive file; Recognize the target archive file by using OCR technology to obtain the target file content of the target archive file; Based on the file type, file size and file content requirements in the archive template, the target file type, the target file size and the target file content are respectively verified to obtain a verification result; wherein, when the target file type is the same as the file type, the target file size is less than or equal to the file size, and the target file content matches the file content requirement, the verification result is passed.

3. The housing provident fund file management method according to claim 1, It is characterized in that The housing provident fund archive management method also includes: If the verification result indicates that the target archive file does not match the archive template, an upload error message of the target archive file is generated; wherein the upload error message includes at least one error type and a modification prompt corresponding to the error type; the error type is a file type error, a file size error, and a file content error; The error message is outputted so that the user can modify the target archive file based on the error message.

4. The housing provident fund file management method according to claim 2, It is characterized in that The housing provident fund archive management method also includes: If the verification result indicates that the target archive file does not match the archive template, obtaining the total number of target archive files uploaded within a preset time period; Determine the number of failed target archive files and error types of failed uploads from the uploaded target archive files; Determine, from the target archive file that failed to be uploaded, a first failure number corresponding to the file type error, a second failure number corresponding to the file size error, and a third failure number corresponding to the file content error; If the ratio of the number of failures to the total number is greater than or equal to a preset threshold, determining the largest target number of failures from the first number of failures, the second number of failures, and the third number of failures; Based on the target error type corresponding to the target failure number, generating adjustment information corresponding to the target error type; Based on the adjustment information, each file template matching each file type is adjusted to obtain an adjusted file template.

5. The housing provident fund file management method according to claim 4, It is characterized in that If the target failure number is the second failure number, generating adjustment information corresponding to the target error type based on the target failure number specifically includes: Calculate an adjustment factor based on the number of failures, the total number, and a preset correction coefficient; Based on the adjustment factor and the file size, calculating and obtaining adjustment information of the file size; The adjustment information of the file size is determined as adjustment information corresponding to the target error type.

6. The housing provident fund file management method according to claim 5, It is characterized in that The calculation formula of the adjustment factor is: ； in, represents the adjustment factor, represents the number of failures, represents the total quantity, represents the preset correction coefficient; And, the calculation formula of the file size adjustment information is: ； Wherein, S represents the adjustment information of the file size, Indicates the size of the file.

7. A housing provident fund archive management system, It is characterized in that The housing provident fund archive management system includes: An acquisition unit, configured to acquire the file type of the file to be uploaded from the file upload instruction when receiving the file upload instruction input by the user; wherein the file type is a deposit type, a withdrawal type, a loan type, and an account change type; An output unit, used to output a file template matching the file type of the file to be uploaded; wherein the file template at least includes the file type, file size and file content requirements; A receiving unit, configured to receive a target archive file uploaded by a user based on the archive template, and determine the dynamic identifier of the target archive file as a newly created identifier; A verification unit, configured to verify the target archive file based on the archive template to obtain a verification result; A storage unit is used for updating the dynamic identification of the target archive file to "under review" if the verification result indicates that the target archive file matches the archive template, and encrypting the target archive file to obtain an encrypted archive file; and determining multiple storage spaces for the encrypted archive file; and storing the encrypted archive file in the multiple storage spaces respectively; wherein each storage space stores a copy of the encrypted archive file.

8. A computer device, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the housing provident fund archive management method described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the housing provident fund archive management method described in any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the steps of the housing provident fund archive management method described in any one of claims 1 to 6 are implemented.

Images