A method and system for storing project completion data

Abstract

The present invention is applicable to the field of data storage technologies, and particularly relates to a method and system for storing project completion data. The method includes: obtaining project completion data, clustering it into several categories, and performing packet encapsulation to obtain data packets; extracting the data summary and key information of each data packet, creating an authentication system, transferring all the data packets into the authentication system, using a preset hash function to hash the data summary, defining the obtained hash value as a location identifier, and establishing a correspondence relationship among the data summary, key information, and location identifier; selecting storage nodes, configuring the attributes of each storage node, and based on the attributes, dividing the storage nodes into high-speed nodes and cloud nodes. The present invention can enhance data security, prevent data abuse and leakage, greatly improve data storage efficiency, and ensure the user experience by determining the final data and target permissions.

Description

Technical Field

[0001] The present invention relates to the technical field of data storage, and particularly to a method and system for storing project completion data. Background Art

[0002] Project completion data usually includes: completion reports, completion acceptance materials, contract execution status, financial settlement data, quality inspection records, and equipment and material lists, etc.

[0003] Due to the large variety and long storage period of project completion data, which generally need to be stored for several years, even decades, or longer; to ensure that the needs of subsequent audits, compliance inspections, and data traceability can be met, project completion data is generally stored in the cloud, and cloud storage usually charges according to storage space and access frequency. Long-term storage of large-scale data may result in high storage costs, especially when project completion data needs to be kept accessible for a long time; therefore, "how to combine cloud storage with local storage" is the technical problem to be solved by the present invention. Summary of the Invention

[0004] The purpose of the present invention is to provide a method and system for storing project completion data to solve the problem of "how to combine cloud storage with local storage" proposed in the above background art.

[0005] To achieve the above purpose, the present invention provides the following technical solutions:

[0006] A method for storing project completion data, the method includes:

[0007] Obtain project completion data, cluster it into several categories, and perform packet encapsulation to obtain data packets. Extract the data summary and key information of each data packet, create an authentication system, transfer all the data packets into the authentication system, use a preset hash function to hash the data summary, define the obtained hash value as a location identifier, and establish the corresponding relationship between the data summary, key information, and location identifier;

[0008] Select storage nodes, configure the attributes of each storage node, and based on the attributes, divide the storage nodes into high-speed nodes and cloud nodes. Synchronize the location identifier, data summary, and key information to the high-speed nodes, and upload the data packets to the cloud nodes;

[0009] Collect the identity information of the user and draw up a permission comparison table, where the permission comparison table at least includes: an identity information item, a permission type item, and a data packet item. Receive the access request uploaded by the user, query the permission comparison table, locate the target packet and the target permission, define the key summary in the target packet as the target summary, use the hash function to hash the target summary to obtain a locator, compare the locator and the positioner, and determine the target node;

[0010] Based on the corresponding relationship, fill the key information into the target node to obtain the final data, connect the access request to the target node, and issue the target permission to the user.

[0011] Further, the steps of obtaining the project completion data, clustering it into several categories, and performing packet encapsulation to obtain data packets, extracting the data summary and key information of each data packet, and creating an identity authentication system include:

[0012] Configure a unique identifier for each data packet and establish a mapping between the unique identifier, the user, and the permission type;

[0013] Integrate the mapping and the identity authentication system to generate an access credential, where the access credential consists of identity information and a password.

[0014] Further, the steps of hashing the data summary and defining the obtained hash value as the positioner include:

[0015] Insert an additional information label into the data packet, where the additional information label at least includes: the data packet size, name, and modification time;

[0016] Locate the storage location of each data packet in the storage node, integrate the storage location and the corresponding relationship, and generate a query form.

[0017] Further, the steps of selecting storage nodes, configuring the attributes of each storage node, and based on the attributes, splitting the storage nodes into high-speed nodes and cloud nodes include:

[0018] Split the cloud node to obtain a cold data area and a hot data area;

[0019] Read the access logs, count the access frequency of each data packet, and determine whether the access frequency is greater than the threshold. If so, migrate the corresponding data packet to the hot data area;

[0020] Parallelly embed a switching mechanism into the cold data area and the hot data area.

[0021] Further, the steps of comparing the locator and the positioner and determining the target node include:

[0022] Based on the locator, determine whether there are identical items in the locator. If so, define the cloud node where the identical items are located as the target node;

[0023] If not, generate a comparison pop-up window and push the comparison pop-up window to a preset terminal.

[0024] Further, the steps of filling the key information into the target node based on the corresponding relationship to obtain the final data, accessing the retrieval request into the target node, and issuing the target permission to the user include:

[0025] Embed a location marker into the key information, and based on the location marker, supplement the key information into the target package to generate the final data;

[0026] Compare the final data with the target package to obtain an incremental update, integrate the final data and the incremental update, generate a project completion version, and construct a version update mechanism.

[0027] Further, the method further includes:

[0028] Create a synchronous update policy for the locator and the final data, and integrate the updated locator into the project completion version;

[0029] Via the comparison pop-up window, trace back the abnormal version and make corrections.

[0030] Further, establish a module for obtaining project completion data, clustering it into several categories, and performing packet encapsulation to obtain data packets. Extract the data summary and key information of each data packet, create an identity authentication system, transfer all data packets into the identity authentication system, use a preset hash function to hash the data summary, define the obtained hash value as the locator, and establish the corresponding relationship among the data summary, key information, and locator;

[0031] An upload module for selecting storage nodes, configuring the attributes of each storage node, based on the attributes, splitting the storage nodes into high-speed nodes and cloud nodes, synchronizing the locator, data summary, and key information to the high-speed nodes, and uploading the data packets to the cloud nodes;

[0032] A determination module for collecting the user's identity information, drawing a permission comparison table, where the permission comparison table at least includes: identity information items, permission type items, and data packet items, receiving the retrieval request uploaded by the user, querying the permission comparison table, locating the target package and target permission, defining the key summary in the target package as the target summary, using the hash function to hash the target summary to obtain the locator, comparing the locator with the locator, and determining the target node;

[0033] An access module, configured to fill the key information into a target node according to the corresponding relationship to obtain final data, access the retrieval request to the target node, and issue the target permission to a user.

[0034] Further, the establishment module includes:

[0035] A mapping unit, configured to configure a unique identifier for each data packet and establish a mapping among the unique identifier, user, and permission type;

[0036] A generation unit, configured to integrate the mapping and the authentication system to generate an access credential, where the access credential is composed of identity information and a password;

[0037] An insertion unit, configured to insert an additional information tag into the data packet, where the additional information tag at least includes: data packet size, name, and modification time;

[0038] A definition unit, configured to locate the storage location of each data packet in the storage node, integrate the storage location and the corresponding relationship, and generate a query form.

[0039] Further, the upload module includes:

[0040] An obtaining unit, configured to split the cloud node to obtain a cold data area and a hot data area;

[0041] A reading unit, configured to read access logs, count the access frequency of each data packet, and determine whether the access frequency is greater than a threshold. If so, migrate the corresponding data packet to the hot data area;

[0042] An embedding unit, configured to parallelly embed a swapping mechanism into the cold data area and the hot data area.

[0043] Compared with the prior art, the beneficial effects of the present invention are:

[0044] By classifying and encapsulating the project completion data, the risk of data loss or damage can be reduced, and the data management efficiency can be improved. By hashing the data digest and storing the hash value in a high-speed node, the data integrity can be ensured, and the data can be prevented from being tampered with during storage, thereby optimizing the data storage cost while enhancing the data storage security. By storing the data packet in the cloud node, the long-term storage of data can be guaranteed. By storing the key information in the high-speed node, the data privacy protection can be optimized, the data leakage risk can be further reduced, and at the same time, a data basis for disaster recovery can be provided. By determining the final data and the target permission, the data security can be enhanced, the data abuse and leakage can be prevented, the data security can be greatly improved, and the user experience can be guaranteed. Description of the Drawings

[0045] Figure 1 It is a flowchart of the project completion data storage method provided by the embodiment of the present invention;

[0046] Figure 2 It is the first sub - flowchart of the project completion data storage method provided by the embodiment of the present invention;

[0047] Figure 3 It is the second sub - flowchart of the project completion data storage method provided by the embodiment of the present invention;

[0048] Figure 4 It is the third sub - flowchart of the project completion data storage method provided by the embodiment of the present invention;

[0049] Figure 5 It is the fourth sub - flowchart of the project completion data storage method provided by the embodiment of the present invention;

[0050] Figure 6 It is the composition block diagram of the project completion data storage system provided by the embodiment of the present invention;

[0051] Figure 7 It is the composition block diagram of the establishment module in the project completion data storage system provided by the embodiment of the present invention;

[0052] Figure 8 It is the composition block diagram of the upload module in the project completion data storage system provided by the embodiment of the present invention;

[0053] Figure 9 It is the composition block diagram of the determination module in the project completion data storage system provided by the embodiment of the present invention;

[0054] Figure 10 It is the composition block diagram of the access module in the project completion data storage system provided by the embodiment of the present invention. Specific embodiments

[0055] In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0056] In Embodiment 1, Figure 1 The implementation process of the project completion data storage method provided by the embodiment of the present invention is shown, and the details are as follows:

[0057] S100: Obtain the project completion data, cluster it into several categories, and perform packet encapsulation to obtain data packets. Extract the data summary and key information of each data packet, create an authentication system, transfer all the data packets into the authentication system, use a preset hash function to hash the data summary, and define the obtained hash value as a locator. Establish the correspondence between the data summary, key information, and locator.

[0058] Collect the project completion data that needs to be stored. The project completion data includes at least: completion reports, completion acceptance materials, contract execution status, etc. Classify the project completion data into several categories according to the department or personnel to which the project completion data belongs, such as: construction category, material category, financial category, and personnel category, etc. Perform packet encapsulation on the project completion data in each category to obtain several data packets. Here, packet encapsulation is to integrate and compress. Extract the data summary and key information in each data packet. Here, the data summary is the content summary of the data packet, and the key information is an important part of the data packet, usually a numerical value.

[0059] Create an authentication system. The authentication system is mainly used to verify the user identity and the integrity of the data packet. Transfer all the data packets into the authentication system, use a preset hash function to hash the data summary. The preset hash function can be SHA-256 or MD5, etc. Define the obtained hash value as a locator. The locator is mainly used to represent the data packet and verify whether the data packet has changed. Establish the correspondence between the data summary, key information, and locator. By constructing the correspondence, the target packet can be quickly found, and the target packet can be supplemented using the key information, greatly improving the extraction efficiency of the project completion data.

[0060] S200: Select storage nodes, configure the attributes of each storage node. Based on the attributes, divide the storage nodes into high-speed nodes and cloud nodes. Synchronize the locator, data summary, and key information to the high-speed nodes, and upload the data packets to the cloud nodes.

[0061] Select storage nodes, which can be devices capable of storing project completion data, cloud storage services, virtual storage, etc.; according to the attributes of each storage node, such as processing power, storage capacity, and bandwidth, etc., divide the storage nodes into high-speed nodes and cloud nodes. As the name implies, high-speed nodes have strong processing power and low-latency network connections. They can be used for local devices or low-latency cloud storage services. High-speed nodes are suitable for storing data that needs to be accessed quickly and processed in real time (in the embodiment, in addition to storing locators, data summaries, and key information, etc., high-speed nodes can also store some project completion data according to actual needs), while cloud nodes focus on large-capacity storage and data backup, and are suitable for long-term storage and remote access; synchronize the locators, data summaries, and key information to the high-speed nodes, and upload the data packets to the cloud nodes.

[0062] S300: Collect the user's identity information, draw a permission comparison table, where the permission comparison table at least includes: identity information item, permission type item, and data packet item. Receive the access request uploaded by the user, query the permission comparison table, locate the target packet and target permission, define the key summary in the target packet as the target summary, use the hash function to hash the target summary to obtain a locator, and compare the locator with the positioner.

[0063] Use the user's identity information to draw a permission comparison table, where the permission comparison table at least includes: identity information item, permission type item, and data packet item; for example, the existing identity information items: financial personnel, construction personnel, and warehouse management personnel; data packet items: construction data packet, material data packet, financial data packet, and personnel data packet, and construct the following permission comparison table:

[0064]

[0065] In the above permission comparison table, the specific permission type should be formulated by project management personnel. In actual operation, the permission comparison table can also be refined to specific individuals.

[0066] When the user needs to access a certain data packet, define the data packet corresponding to the access request as the target packet, and define the permission type corresponding to the target packet as the target permission, define the key summary corresponding to the target packet as the target summary, and define the storage location of the target packet as the target node.

[0067] Continuing with the above permission comparison table as an example, if a construction worker A wants to query the time taken to complete the initial draft of the building design during the project design phase, define the construction data packet as the target packet, find the storage location of the construction data packet in the cloud node, and define this storage location as the target node, extract the target packet, continue to extract the data summary in the target packet, use the hash function to hash this data summary, and define the obtained hash value as the locator.

[0068] In the high-speed node, find the corresponding locator, compare the locator with the position. If the two are the same, it indicates that the construction data packet has not been tampered with during the storage process.

[0069] S400: Based on the corresponding relationship, fill the key information into the target node to obtain the final data, access the retrieval request to the target node, and issue the target permission to the user.

[0070] If the locator and the positioner are the same, then according to the corresponding relationship, fill the key information corresponding to the positioner into the target node to obtain the final data. The advantage of doing this is that it can detect whether the project completion data has been tampered with; in addition, storing the data digest, key information, and positioner in the high-speed node and storing the data packet in the cloud can also ensure the normal retrieval of the project completion data while reducing the storage cost.

[0071] In Embodiment 2, Figure 2 The implementation process of the project completion data storage method provided by the embodiment of the present invention is shown. The steps of obtaining the project completion data, clustering it into several categories, encapsulating it to obtain a data packet, extracting the data digest and key information of each data packet, and creating an authentication architecture are described in detail as follows:

[0072] S101: Configure a unique identifier for each data packet, and establish a mapping between the unique identifier, the user, and the permission type.

[0073] Set a unique identifier for each data packet, where the unique identifier can be a string or a number; use this unique identifier to establish a mapping relationship between the user and the permission type.

[0074] S102: Integrate the mapping and the authentication architecture to generate an access credential, where the access credential consists of identity information and a password.

[0075] When accessing the data packet, the user identity should also be verified using the access credential and the authentication system.

[0076] In Embodiment 3, Figure 2 The implementation process of the project completion data storage method provided by the embodiment of the present invention is shown. The step of hashing the data digest and defining the obtained hash value as the locator is described in detail as follows:

[0077] S103: Insert an additional information label into the data packet, where the additional information label at least includes: the data packet size, name, and modification time.

[0078] Insert additional information tags into each data packet. For example, the additional information tags corresponding to the personnel data packet can be the specific name of the person, the person's name and job type, etc.

[0079] S104: Locate the storage location of each data packet in the storage node, integrate the storage location and the corresponding relationship, and generate a query form.

[0080] Find out the storage location of each data packet; specifically, the data packets are stored in the cloud nodes, and the cloud nodes are composed of several storage nodes. Therefore, by determining the storage location of each data packet, the calling efficiency of the data packets can be further improved; supplement the storage location into the corresponding relationship to construct a query form. In other words, the query form should include: data packet, storage location of the data packet, data summary, key information, location symbol, etc.

[0081] In Embodiment 4, Figure 3 The implementation process of the project completion data storage method provided by the embodiment of the present invention is shown. The following details the steps of selecting the storage node, configuring the attributes of each storage node, and based on the attributes, splitting the storage node into a high-speed node and a cloud node, as follows:

[0082] S201: Split the cloud node to obtain a cold data area and a hot data area.

[0083] Split the cloud node into multiple partitions, such as a hot data area, a buffer area, and a cold data area; among them, the cloud node corresponding to the hot data area should have high availability, low latency, and high concurrency processing capabilities. The hot data area is mainly used to store the frequently accessed project completion data, and the buffer area is used to store the project completion data that has not been classified yet.

[0084] S202: Read the access log, count the access frequency of each data packet, and determine whether the access frequency is greater than the threshold. If so, migrate the corresponding data packet to the hot data area.

[0085] According to the access log of the data packet, record the access frequency of each data packet, migrate the data packet with an access frequency greater than the threshold to the hot data area, and migrate the data packet with an access frequency less than or equal to the threshold to the cold data area.

[0086] S203: Embed a swap mechanism into the cold data area and the hot data area in parallel.

[0087] Update the access frequency of the data packet in real time, and at the same time embed a swap mechanism into the cold data area and the hot data area. The swap mechanism is the specific method for adjusting the cold and hot attributes of the data packet; for example, transfer the data packet from the hot data area to the cold data area, or transfer the data packet from the cold data area to the hot data area.

[0088] In Embodiment 5, Figure 4 The implementation process of the project completion data storage method provided by the embodiment of the present invention is shown. The following details the step of comparing the locator and the positioner to determine the target node, as follows:

[0089] S301: Based on the locator, determine whether there are identical items in the positioner. If so, define the cloud node where the identical items are located as the target node. If not, generate a comparison pop-up window.

[0090] Determine whether the locator corresponding to the target summary is the same as the positioner. If they are the same, it means that the data packet has not changed during the storage process. At this time, use the locator to find the cloud node corresponding to the data packet and define it as the target node. In other words, by comparing the locator and the positioner, it is possible to detect whether the data packet has changed during the storage process and at the same time locate the storage location of the data packet.

[0091] S302: Push the comparison pop-up window to a preset terminal.

[0092] If the locator and the positioner are different, it means that the data packet has changed during the storage process. At this time, generate a comparison pop-up window using the data packet in the target node and the data summary corresponding to the locator, and push the comparison pop-up window to a preset terminal. The preset terminal is the terminal of the project management personnel, and the project management personnel judge the specific differences between the data packet and the data summary.

[0093] In Embodiment 6, Figure 5 The implementation process of the project completion data storage method provided by the embodiment of the present invention is shown. The following details the steps of filling the key information into the target node based on the corresponding relationship to obtain the final data, accessing the retrieval request to the target node, and issuing the target permission to the user, as follows:

[0094] S401: Embed a position marker into the key information, and based on the position marker, supplement the key information into the target packet to generate the final data.

[0095] Determine the data packet corresponding to each key information, and generate a position marker for the key information using the storage location corresponding to the data packet. When the target packet is determined and the positioner corresponding to the target packet is the same as the locator, write the key information corresponding to the positioner into the target packet via the position marker to obtain the final data, where the final data is the complete project completion data.

[0096] S402: Compare the final data and the target packet to obtain an incremental update, integrate the final data and the incremental update, generate a version update mechanism, and construct a version update mechanism.

[0097] If the permission types corresponding to the user include modification, deletion, etc., record the changed part of the final data, define the changed part as incremental update, generate the completed project version using the incremental update and the final data, and record the generation time, version number, modifying personnel, etc. of each completed project version at the same time; use the version update mechanism to record and update the completed project version, where the version update mechanism is to use the version number as a marker to perform version control on the final data; by setting the version update mechanism, the change process of the completed project version can be tracked and managed.

[0098] In Embodiment 7, different from Embodiment 1, in the embodiment of the present invention, the method further includes:

[0099] Create a synchronization update policy for the locator and the final data, and integrate the updated locator into the completed project version;

[0100] Via the comparison pop-up window, trace back the abnormal version and make corrections.

[0101] If the final data changes, that is, the completed project data in the data packet is modified, then use the synchronization update policy to modify the locator; where the synchronization update policy is to modify the corresponding locator via the corresponding relationship; integrate the modified locator into the completed project version, so as to realize the recording of the locator.

[0102] If the same hash value as the locator cannot be found in the locator, it means that the data packet may be abnormally modified; according to the comparison result of the project management personnel, find the abnormal version, and there are many reasons for the appearance of the abnormal version, for example, the completed project version is tampered with, or the version data is chaotic, etc.; at this time, according to the locator and the key information, the project management personnel correct the completed project version to restore the original data.

[0103] Figure 6 The composition structure block diagram of the completed project data storage system provided by the embodiment of the present invention is shown. The completed project data storage system 1 includes:

[0104] A establishment module 11, configured to obtain the completed project data, cluster it into several categories, and perform packetization to obtain data packets, extract the data summary and key information of each data packet, create an authentication architecture, transfer all the data packets into the authentication architecture, use a preset hash function to hash the data summary, define the obtained hash value as a locator, and establish the corresponding relationship between the data summary, the key information and the locator;

[0105] An upload module 12 is used to select storage nodes, configure the attributes of each storage node, based on the attributes, split the storage nodes into high-speed nodes and cloud nodes, synchronize location markers, data digests, and key information to the high-speed nodes, and upload the data packets to the cloud nodes;

[0106] A determination module 13 is used to collect the identity information of users, draw a permission comparison table, where the permission comparison table at least includes: identity information items, permission type items, and data packet items, receive the access request uploaded by the user, query the permission comparison table, locate the target packet and target permission, define the key digest in the target packet as the target digest, use the hash function to hash the target digest to obtain a locator, compare the locator and the location marker, and determine the target node;

[0107] An access module 14 is used to fill the key information into the target node according to the corresponding relationship to obtain the final data, access the access request to the target node, and issue the target permission to the user.

[0108] Figure 7 The composition structure block diagram of the project completion data storage system provided by the embodiment of the present invention is shown. The establishment module 11 includes:

[0109] A mapping unit 111 is used to configure a unique identifier for each data packet and establish a mapping between the unique identifier, the user, and the permission type;

[0110] A generation unit 112 is used to integrate the mapping and the authentication architecture to generate an access credential, where the access credential consists of identity information and a password;

[0111] An insertion unit 113 is used to insert an additional information tag into the data packet, where the additional information tag at least includes: data packet size, name, and modification time;

[0112] A definition unit 114 is used to define the storage location of each data packet in the storage node, integrate the storage location and the corresponding relationship, and generate a query form.

[0113] Figure 8 The composition structure block diagram of the project completion data storage system provided by the embodiment of the present invention is shown. The upload module 12 includes:

[0114] A obtaining unit 121 is used to split the cloud node to obtain a cold data area and a hot data area;

[0115] A reading unit 122 is used to read the access logs, count the access frequency of each data packet, determine whether the access frequency is greater than the threshold, and if so, migrate the corresponding data packet to the hot data area;

[0116] An embedding unit 123 for parallelly embedding a switching mechanism into the cold data area and the hot data area.

[0117] Figure 9 The composition structure block diagram of the project completion data storage system provided by the embodiment of the present invention is shown. The determination module 13 includes:

[0118] A judgment unit 131 for judging, based on the locator, whether there are identical items in the position symbol. If so, defining the cloud node where the identical items are located as the target node. If not, generating a comparison pop-up window;

[0119] A push unit 132 for pushing the comparison pop-up window to a preset terminal.

[0120] Figure 10 The composition structure block diagram of the project completion data storage system provided by the embodiment of the present invention is shown. The access module 14 includes:

[0121] A filling unit 141 for embedding a position mark into the key information, and based on the position mark, filling the key information into the target packet to generate final data;

[0122] A construction unit 142 for comparing the final data and the target packet to obtain an incremental update, integrating the final data and the incremental update to generate a version update mechanism, and constructing the version update mechanism.

[0123] Among them, the establishment module 11 is mainly used to complete step S100, the upload module 12 is mainly used to complete step S200, the determination module 13 is mainly used to complete step S300, and the access module 14 is mainly used to complete step S400;

[0124] The mapping unit 111 is mainly used to complete step S101, the generation unit 112 is mainly used to complete step S102, the insertion unit 113 is mainly used to complete step S103, and the definition unit 114 is mainly used to complete step S104;

[0125] The obtaining unit 121 is mainly used to complete step S201, the reading unit 122 is mainly used to complete step S202, and the embedding unit 123 is mainly used to complete step S203;

[0126] The judgment unit 131 is mainly used to complete step S301, and the push unit 132 is mainly used to complete step S302;

[0127] The filling unit 141 is mainly used to complete step S401, and the construction unit 142 is mainly used to complete step S402.

[0128] The technical features of the above-described embodiments can be combined arbitrarily. For the sake of brevity of description, 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, it should be considered as falling within the scope described in this specification.

[0129] The above-described embodiments merely represent several implementation manners of the present invention. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the patent for the present invention. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present invention, several modifications and improvements can still be made, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the patent for the present invention shall be subject to the appended claims.

[0130] The above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent replacements, and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A method for storing project completion data, characterized in that: The method comprises: Acquire project completion data, cluster them into several categories, and package them to obtain data packets, extract the data summary and key information of each data packet, create an identity authentication system, transfer all data packets to the identity authentication system, use a preset hash function to hash the data summary, define the obtained hash value as a location symbol, and establish the corresponding relationship between the data summary, key information and location symbol; Selecting storage nodes, configuring the attributes of each storage node, dividing the storage nodes into high-speed nodes and cloud nodes based on the attributes, synchronizing the location identifier, data summary and key information to the high-speed nodes, and uploading the data packet to the cloud node; Collecting the identity information of the user, drawing a permission comparison table, wherein the permission comparison table at least includes: an identity information item, a permission type item, and a data package item, receiving a request for access uploaded by the user, querying the permission comparison table, locating the target package and the target permission, defining the key summary in the target package as the target summary, using the hash function to hash the target summary to obtain a locator, comparing the locator with the position symbol, and determining the target node; Based on the corresponding relationship, the key information is filled into the target node to obtain the final data, the access request is connected to the target node, and the target authority is issued to the user; The steps of obtaining the project completion data, clustering it into several categories, and packaging it to obtain data packets, extracting the data summary and key information of each data packet, and creating an identity authentication system include: Configure a unique identifier for each data packet and establish a mapping between the unique identifier, user, and permission type; integrating the mapping and identity authentication systems to generate access credentials, wherein the access credentials consist of identity information and a password; The step of hashing the data digest and defining the obtained hash value as a location symbol comprises: Inserting an additional information tag into the data packet, wherein the additional information tag includes at least: data packet size, name and modification time; Locate the storage location of each data packet in the storage node, integrate the storage location and the corresponding relationship, and generate a query form; The step of selecting storage nodes, configuring the attributes of each storage node, and dividing the storage nodes into high-speed nodes and cloud nodes based on the attributes includes: Splitting the cloud node to obtain a cold data area and a hot data area; Read the access log, count the access frequency of each data packet, and determine whether the access frequency is greater than a threshold. If so, migrate the corresponding data packet to the hot data area; A swap mechanism is embedded in the cold data area and the hot data area in parallel.

2. The project completion data storage method according to claim 1, characterized in that: The step of comparing the locator and the positioner to determine the target node comprises: Based on the locator, determine whether there is an identical item in the locator, and if so, define the cloud node where the identical item is located as a target node; If not, a comparison pop-up window is generated and pushed to a preset terminal.

3. The project completion data storage method according to claim 1, characterized in that: The steps of filling the key information into the target node based on the corresponding relationship to obtain final data, connecting the access request to the target node, and issuing the target permission to the user include: embedding a position mark into the key information, and based on the position mark, adding the key information into the target package to generate final data; The final data and the target package are compared to obtain an incremental update, the final data and the incremental update are integrated to generate a completed version of the project, and a version update mechanism is constructed.

4. The project completion data storage method according to claim 2, characterized in that: The method further comprises: Creating a synchronization update strategy for the location symbol and the final data, and integrating the updated location symbol into the completed version of the project; Through the comparison pop-up window, the abnormal version is traced back and corrected.

Images