System and method for distributed data storage and transmission using blockchain
Through blockchain technology, the files are split and encrypted and hash values are generated for verification, solving the security and usage tracking of existing data storage and transmission systems, achieving secure, fast and economical data transmission and storage.
Patent Information
- Application Number
- CN201980075138.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-08-30
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2039-08-30
AI Technical Summary
Existing data storage and delivery systems are vulnerable to hackers and lack effective security and usage tracking mechanisms to provide high-level security, compliance and transparency.
Data storage and transmission are carried out using blockchain technology. By splitting files into group files and encrypting them with encryption keys, hash values are generated for storage and verification, ensuring the security and integrity of files, and using blockchain Provides tamper-proof transaction history and usage tracking.
It enables secure file transfer and storage, enhances the speed, cost-effectiveness and security of cloud storage, and provides tamper-proof transaction history and high-level usage tracking capabilities.
Smart Images

Figure CN113196702B_ABST
Abstract
Description
[0001] In one aspect, the present disclosure relates to systems and methods for data storage and transfer, and in particular, secure, distributed data storage and transfer systems and methods using blockchain. Other aspects are also described. Background Art
[0002] Current data storage and transmission systems can be highly vulnerable to hacking, tampering, etc., and also do not effectively provide adequate methods to track participant or customer usage. Therefore, there is a need for systems and methods for secure, distributed data storage and transmission. Blockchain technology provides an environment that provides the highest level of security, compliance, transparency, and trust between participants. Blockchain technology provides trust and security by applying cryptographic techniques to ensure the security of transactions. Transaction history can further be made available almost instantly. Therefore, the present disclosure solves the aforementioned and other related and unrelated problems / problems in the art. Summary of the invention
[0003] In one aspect, the present disclosure relates to a system for data storage and transfer using blockchain. The system may include a website, an application, a mobile application, a file transfer program ("FTP") such as a secure file transfer program ("SFTP"), etc., which can be accessed by a participant to store and transfer data files. For example, a participant can access the website, application, mobile application, FTP / SFTP, etc. by providing authentication credentials (e.g., authentication credentials selected by the participant, such as a username, password, etc.), or using other suitable multi-factor authentication methods. The participant can upload one or more files to the system using an interface (e.g., a GUI or other suitable interface) of the website, application, mobile application, FTP / SFTP, etc.
[0004] The system further includes one or more components or modules configured to split the uploaded file into smaller constituent files. The system may also include one or more modules or components configured to generate a hash or hash value of the original file and the smaller constituent files (e.g., by applying a hash function such as a SHA256 or RIPEMD function to the electronic information of the smaller constituent files). By adjusting the number of constituent files into which the original file is broken and the locations where the constituent files are stored, the competing goals of security, cost, and performance can be balanced.
[0005] The system may also include an encryption component or other suitable component or module configured to encrypt smaller constituent files using an encryption key supplied or otherwise selected by a participant. When encrypting constituent files, the system may provide the encrypted constituent files to one or more storage locations. In one variation, the system may provide the encrypted constituent files to multiple storage locations (e.g., two or more cloud-based storage systems, such as Amazon Web Services (AWS), InterPlanetary File System (IPFS), etc.) for redundancy. The system may also identify or locate the encrypted constituent files in the storage location based on the hash values of the generated constituent files.
[0006] The system further generates one or more transactions including transaction information related to the uploaded file (e.g., including a transaction identifier, file type, participant information, status information, time information, a hash value of the file, location information of the file, or other suitable transaction information). In one variation, the transaction identifier may include a generated hash or hash value of the original uploaded file. The transaction information may be provided to the current block in the blockchain.
[0007] Other additional participants or participants who uploaded the file(s) may access the uploaded and stored file(s) through an application, mobile application, website, FTP / SFTP, etc. For example, a participant may authenticate with their credentials or using other suitable multi-factor authentication or other authentication methods (e.g., providing biometric information such as fingerprint, facial scan, etc.) and access the system's website, application, mobile application, FTP, etc. After the participant has accessed the website, application, mobile application, FTP, etc., they may request to retrieve a specific file that was previously uploaded. The system may then retrieve the corresponding encrypted constituent files associated with the requested file, for example by referencing the hash values of the constituent files or the hash values of the original files stored in the blockchain.
[0008] In addition, the system may include one or more decryption components or modules that use an encryption key supplied or otherwise selected by the participant to decrypt the encrypted constituent files. The system also includes one or more components or modules that hash or generate hash values for the decrypted constituent files or reassembled files (e.g., by applying a hash function such as SHA256 or RIPEMD function to the electronic information of the file).
[0009] The system may compare the hash value of the decrypted file with the hash values of the corresponding smaller constituent files stored in the blockchain, for example, to determine whether the file has been corrupted, tampered with, or otherwise altered. If the hash values match, the decrypted files may be combined (e.g., using one or more components configured to combine files) to form a file corresponding to the originally uploaded file. If one or more of the hash values of the decrypted file differs from (i.e., does not match) the values of the smaller constituent files stored in the blockchain, however, the system may generate an error, alarm, or other notification alert and provide a notification to the participant indicating that the file may have been tampered with or altered.
[0010] When the constituent files are reassembled, the reassembled files may be transmitted to a website, application, mobile application, etc., or other desired location, or may otherwise be made available for access by requesting participants.
[0011] In addition, or in an alternative embodiment, the system may compare the hash value of the original file with the hash value of the reassembled file stored in the blockchain (and, if appropriate, first decrypt the hash value stored in the blockchain), for example, to determine whether the reassembled file has been tampered with or otherwise altered. If the hash values match, the reassembled file may be transmitted to a website, application, mobile application, etc., or other desired location, or may otherwise be made available for access by the requesting participant. If the hash value of the reassembled file is different from (i.e., does not match) the value of the original file stored in the blockchain, however, the system may generate an error, alarm, or other notification alert and provide a notification to the participant indicating that the file may have been tampered with or altered.
[0012] The system may further generate transaction information related to the retrieved file and the original file to be stored in the blockchain (e.g., including a transaction identifier, file type, participant information, state information, time information, a hash value of the file, location information of the file, or other suitable transaction information). In one variation, the transaction identifier may include a hash value of the generated reassembled file.
[0013] Thus, the system can help facilitate secure file transfer and storage, and further help provide a security guard against tampering of stored files using file checks (e.g., hash comparisons) during file retrieval. The system according to the present disclosure can also help increase the speed, cost-effectiveness, and security of cloud or IPFS storage. Additionally, the system can provide a substantially tamper-proof transaction history using information stored in the blockchain, and in one variation, provide a high-level dashboard that tracks participant usage.
[0014] In one aspect, a method for secure, distributed data storage and transmission may be provided. For example, an original file may be received from a participant. A hash value of the received original file may be generated. Then, the received original file may be split into a plurality of smaller constituent files, and a hash value of each file in the smaller constituent files may be generated (e.g., by applying a hash function to the electronic data of the smaller constituent files). Each file in the plurality of smaller constituent files may also be encrypted using one or more predetermined or user-selected encryption keys to generate a plurality of encrypted constituent files. Then, each file in the plurality of encrypted constituent files is stored in at least one storage location. In one variation, the plurality of encrypted files may be stored in two or more cloud-based storage locations, such as AWS, IPFS, etc., for redundancy. Transaction information may also be generated and provided to the current block in the blockchain. The hash value of each file in the plurality of constituent files and the original file may also be provided to the current block in the blockchain (e.g., as part of the transaction information) where appropriate.
[0015] When a file retrieval request is received from (one or more) additional participants (or participants providing original files) among the plurality of participants, the plurality of encrypted constituent files may be retrieved from the (one or more) storage locations, for example by reference to hash values for the constituent files and for the original files stored in the blockchain. Thereafter, each of the plurality of encrypted constituent files may be decrypted, for example using one or more predetermined or user-selected encryption keys, to generate a plurality of decrypted constituent files (e.g., which should correspond to smaller constituent files). A hash value for each of the decrypted constituent files may then be generated and compared to a hash value for the corresponding smaller constituent file stored in the current block of the blockchain, for example to determine whether the file has been tampered with or otherwise altered.
[0016] If the hash value of the decrypted constituent file matches the corresponding hash value of the smaller constituent file stored in the blockchain, then the multiple decrypted files can be combined to generate a file related to the original file. However, if one or more hash values of each file in the multiple decrypted files do not match the hash value of one or more files in the corresponding smaller constituent files (e.g., indicating damage, tampering, change, etc., or failure in transmission, storage, decryption or retrieval), an alarm, warning or other suitable notification can be generated and provided to the participants. Additional transaction information can also be generated and provided to the current block in the blockchain.
[0017] When the constituent files are reassembled, the reassembled files may be transmitted to a website, application, mobile application, etc., or other desired location, or may otherwise be made available for access by the requesting participant. Additional transaction information may also be generated and provided to the current block in the blockchain.
[0018] Additionally, or in an alternative embodiment, a hash value of the reassembled file may be generated and compared to a hash value of the original file stored in the current block of the blockchain, for example, to determine whether the file has been tampered with or otherwise altered. If the hash value of the reassembled file matches the corresponding hash value of the original file stored in the blockchain, the reassembled file may be transmitted to a website, application, mobile application, etc., or other desired location, or may otherwise be made available for access by the requesting participant. However, if the hash value of the reassembled file does not match the hash value of the original file (e.g., indicating damage, tampering, change, etc., or a failure in transmission, storage, retrieval, decryption, or reassembly), an alarm, warning, or other suitable notification may be generated and provided to the participant. Additional transaction information may also be generated and provided to the current block in the blockchain.
[0019] The above summary does not include an exhaustive list of all aspects of the present disclosure. It is contemplated that the present disclosure includes all systems and methods that can be practiced from all suitable combinations of the various aspects outlined above, as well as those systems and methods described in the following detailed description and specifically pointed out in the claims filed with the present application. Such combinations have specific advantages not specifically described in the above summary. The various objects, features and advantages of the present disclosure will become further apparent to those skilled in the art when consulting the following detailed description considered in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] It will be appreciated that for simplicity and clarity of illustration, the elements illustrated in the various figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements. Embodiments incorporating the teachings of the present disclosure are shown and described with reference to the drawings herein, in which:
[0021] Figure 1 A system for secure data storage and transfer using blockchain according to one aspect of the present disclosure is illustrated.
[0022] Figure 2A and Figure 2B A flow chart of a method or process for secure data storage and transfer using blockchain according to one aspect of the present disclosure is provided.
[0023] Figure 3A flow chart of a method or process for secure data storage and transfer using blockchain according to one aspect of the present disclosure is provided.
[0024] The use of the same reference symbols in different drawings indicates similar or identical items. DETAILED DESCRIPTION
[0025] The following description is provided in conjunction with the figures to help understand the teachings disclosed herein. The description focuses on specific implementations and embodiments of the teachings and is provided to help describe the teachings. This focus should not be interpreted as a limitation on the scope or applicability of the teachings.
[0026] Several aspects of the present disclosure are now explained with reference to the drawings. Whenever the shapes, relative positions and other aspects of the described components are not clearly defined, the scope of the present invention is not limited to the components shown, which are meant for illustration purposes only.
[0027] Figure 1 1 shows a data storage and transmission system 10 according to one aspect of the present disclosure. Figure 1 As shown in , the system 10 includes a website, an application, a mobile application, a file transfer program such as a secure file transfer program ("SFTP") or other suitable computer program product, a platform file transfer program ("FTP"), etc. 12, which can be accessed by a participant to upload and retrieve files. For example, using user-selected credentials / authentication information (e.g., username, password, answers to challenge response questions, etc.) or other suitable multi-factor authentication or authentication methods (e.g., by providing biometric information such as fingerprints, facial scans, etc.), the participant can access the website, application, mobile application, FTP / SFTP, etc. 12. The system 10 (e.g., website, application, mobile application, FTP / SFTP, etc. 12) can further include one or more interfaces that allow participants to upload files (e.g., participants can browse and select specific files to upload, can drag specific files to an area where upload is allowed, etc.).
[0028] If additionally in Figure 1As shown in , the system 10 includes one or more components or modules 14, which are configured to split the uploaded file into multiple smaller constituent files. One or more modules or components 14 can also be configured to hash the original file and the smaller constituent files or generate hash values thereof. For example, (one or more) modules / (one or more) components 14 can apply hash functions such as SHA 256 function, RIPEMD function, etc. to the electronic information of the original file and the smaller constituent files or electronic information otherwise related thereto, such as converting any input length into an output of a fixed length. The hash values of the smaller constituent files (or original files) can be provided and stored in a table or other suitable list, index, grouping, spreadsheet, database, etc. The table, list, grouping, etc. including / storing hash values can be stored in any suitable storage location, such as cloud-based storage (e.g., Amazon Web Services ("AWS"), Interplanetary File System ("IPFS"), etc.), or other suitable storage location. It will be further understood that although Figure 1 The same component / module 14 may be shown performing the splitting and hashing operations, but any number of components or modules (eg, two or more separate components / modules) may perform the splitting and hashing operations.
[0029] The system 10 may further include an encryption component 16 or other suitable module or component that encrypts the smaller constituent files split from the uploaded file using an encryption key supplied or otherwise selected by one or more participants to generate an encrypted file 17. For example, the encryptor 16 may apply an encryption function (such as an AES function, such as an AES256 function, an RSA function, a DES function, etc.) to the electronic data / information of each file of the plurality of smaller constituent files or otherwise related thereto. The system 10 may provide the encrypted constituent files 17 to one or more storage locations 18. In one example, the system 10 may provide the encrypted constituent files 17 to multiple storage locations (e.g., two or more cloud-based storage locations 18, such as AWS, IPFS, etc.) for redundancy.
[0030] The system 10 may further create transaction information associated with the uploaded file and provide the transaction information together with the hash value 20 and the location information of the file to the blockchain 22. In one variation, the transaction information may include a transaction identifier, file type, participant information, state information, time information, hash values of the original file and smaller component files, location information of the file, or other suitable transaction information associated with the original file, smaller component files, encrypted and stored files, etc. In one embodiment, the transaction identifier may include a generated hash value of the original uploaded file.
[0031] The attached participant (or the participant who uploaded the file(s)) may access the uploaded files through a website, application, mobile application, FTP / SFTP, etc. 12. For example, a participant accessing a website, application, mobile application, FTP / SFTP (e.g., upon authentication) may initiate a request to retrieve a specific file previously uploaded to the system. The system 10 may then retrieve all corresponding encrypted constituent files 17, e.g., by referencing hash values of the constituent files and the original file stored in the blockchain, and may further provide the files 17 to one or more components or modules 24, which decrypt the encrypted constituent files associated with the requested file using an encryption key supplied or otherwise selected by the participant.
[0032] One or more components / modules 26 additionally hash the decrypted file or generate a hash value for the decrypted file (e.g., by applying a hash function such as a SHA 256 function, a RIPEMD function, etc. to the electronic information of the decrypted file or otherwise associated with the decrypted file), and compare the hash value of the retrieved file with the hash value of the corresponding smaller component file stored in the blockchain 22, for example, to determine whether the file has been tampered with, altered, or otherwise differs from the corresponding smaller component file. If the hash value of the retrieved decrypted file corresponds to the hash value of the corresponding component file stored in the blockchain 22, the decrypted component files can be combined, for example, by the component / module 26, to generate a reassembled file corresponding to the original uploaded file. If the hash values are different (i.e., do not match or correspond), however, the system 10 can generate an error, warning, or other suitable notification and provide it to the participant (e.g., the error notification can be provided to the participant via an SMA text, email, etc.). Furthermore, if the hash value of the retrieved decrypted file corresponds to the hash value of the corresponding constituent file stored in the blockchain 22, the reassembled file may be transmitted to an application, mobile application, website, FTP / SFTP, etc. interface, or other desired location to allow the participant to access the file.
[0033] Alternatively, for additional verification, if the hash value of the decrypted file matches the hash value of the constituent files stored in the blockchain 22, one or more components / modules 26 may additionally hash or generate a hash value of the reassembled file (e.g., by applying a hash function such as a SHA 256 function, a RIPEMD function, etc. to the electronic information of the reassembled file or otherwise associated with the reassembled file), and compare the hash value of the reassembled file with the hash value of the original file stored in the blockchain 22, for example, to determine whether the reassembled file has been corrupted, tampered with, altered, etc., or otherwise different from the original uploaded file. If the hash value of the reassembled file corresponds to the hash value of the corresponding original file stored in the blockchain 22, the reassembled file may be transmitted to an application, mobile application, website, FTP / SFTP, etc. interface, or other desired location to allow the participant to access the file. If the hash values are different (i.e., do not match or correspond), however, the system 10 may generate an error, warning, or other suitable notification and provide it to the participant (e.g., an error notification may be provided to the participant via an SMA text, email, etc.).
[0034] Although Figure 1 The same component / module 26 is shown performing operations such as hashing, comparing, combining, etc., but any number of components or modules (e.g., two or more separate components / modules) may perform these operations without departing from the scope of the present disclosure. One of ordinary skill in the art will further understand that, although multiple components / modules are shown to perform various operations of the system 10, a single component / module or any other suitable number or combination of components or modules may perform the operations of the system without departing from the scope of the present disclosure.
[0035] The system 10 may further generate additional transaction information related to the file retrieval and store the information in the blockchain 22. In one variation, the additional transaction information may include a transaction identifier, a file type, participant information, status information, time information, a hash value of a file, location information of a file, or other suitable transaction information related to the retrieved file, the decrypted file, the combined file, etc. In one embodiment, the transaction identifier may include a hash or hash value of the reassembled file. Thus, the system may help provide a substantially tamper-proof transaction history using blockchain, and may also increase the speed, cost-effectiveness, and security of cloud-based storage or transactions / databases.
[0036] Additionally, the system can provide a substantially tamper-proof transaction history using information stored in the blockchain. In one variation, the system can provide a high-level dashboard (e.g., on its interface, GUI, etc.) that includes information stored in the blockchain to track participant usage.
[0037] The system 10 may further include a server 30 or other suitable computing device, for example, at a data or control center managed by a data service provider or other suitable entity, the server / computing device 30 may have one or more processors 32 and one or more memories 34, the one or more memories 34 being configured to store instructions executed by the one or more processors. The various components / modules of the above-mentioned data storage system 10 may include workflows, program instructions, etc. stored in one or more memories 34 and executed by the processor 32. Additionally or alternatively, one or more components of the system 10 may be network-based or cloud-based and may be stored and accessed from one or more memories or storage devices of a computing device (such as a server) that is part of a data management center managed by a network or cloud service provider or other suitable entity. Additionally or alternatively, one or more components of the system may reside on or be accessed by a computing device 40 managed by a participant (described below).
[0038] For example, participants can use their managed computing devices 40 to access websites, FTP / SFTP, applications, mobile applications, etc. 12, and their managed computing devices 40 can communicate with the system 10 through a network. The device 40 managed by the participant may include, but is not limited to, a handheld mobile device, such as a mobile phone 42, a smart phone, a tablet device, a PAD, or other suitable mobile computing device; a personal computing device, such as a laptop computer 44, a desktop computer, a workstation, etc.; or any other suitable computing device. The managed computing device 40 may have one or more processors and one or more memories. The computing device 40 may be configured to access one or more networks, such as the Internet, a peer-to-peer network, or any other suitable private or public network or combination thereof, to enable the participant to access websites, applications, mobile applications, FTP, etc. to upload, access, retrieve, etc. files. These devices may be connected via a wired connection, such as an Ethernet cable, or via, for example, Wi-Fi, Bluetooth, etc. ® The network is accessed through a wireless connection, a cellular connection such as 3G, 4G, LTE, 5G, etc., or a combination thereof.
[0039] The processor of the computing device 30, 40 may include a central processing unit (CPU) or hardware or software control logic, ROM and / or other types of non-volatile memory, and the memory may include random access memory (RAM) or (ROM). The computing device 30, 40 may further include one or more ports for communicating with external devices and various input and output (I / O) devices such as a keyboard, mouse, touch screen and / or video display. However, the computing device 30, 40 may include any suitable computing component that is operable to calculate, compute, determine, classify, process, transmit, receive, retrieve, initiate, switch, store, display, communicate, visualize, detect, record, reproduce, dispose of or utilize any form of information or data for any suitable purpose.
[0040] Figure 2A and Figure 2B A flow chart for secure data storage and transmission using blockchain according to one aspect of the present disclosure is shown. Figure 2A As shown in , at 102, a participant (e.g., a first participant) can launch a data storage system, and, for example, at 104, the participant can log into a website, application, mobile application, secure file transfer program ("SFTP") or other suitable file transfer program ("FTP") to access a document service provider. The participant can provide a request to upload a file at 106, for example, by selecting / clicking one or more icons, selectable objects, etc., and then the participant can upload the selected (one or more) files at 108.
[0041] Thereafter, at 110, the data storage system generates a hash value for the uploaded file, splits the uploaded file into smaller constituent files, and also generates a hash value for each of the smaller constituent files (e.g., by applying a hash function such as a SHA256 function, a RIPEMD function, etc. to the electronic information of the smaller constituent files or otherwise associated therewith). The system then encrypts each of the smaller constituent files at 112 (e.g., using an encryption function such as an AES256 function). At 114, the data storage system provides and stores the encrypted constituent files in at least two locations (e.g., AWS or IPFS) for redundancy, and at 116, the system notifies the participant or other participants (e.g., via SMS message, email, etc.) that the file has been uploaded / saved, typically as described above. Figure 2A as shown in .
[0042] In addition, at 118, Figure 2AThe data storage system is shown generating a transaction and storing the transaction in the current block 50 of the blockchain 22. For example, the transaction may include transaction information, including a transaction ID, which may include a hash value of the original file, a file type (e.g., PDF, word document, GIF, JPEG, WAV, MP3, etc.), participant information, transaction status, and time information such as a timestamp, which is provided to the current block 50 in the blockchain 22 ( Figure 2A ).
[0043] Afterwards, if Figure 2B As shown in , another participant (or the same participant) can access the uploaded and stored files. For example, a participant (e.g., a second participant or a first participant) can launch a data storage system at 120. For example, the participant can log into a website, application, mobile application, FTP, etc. at 122, and can generate a file retrieval request at 124 to access the uploaded and stored files (e.g., by selecting one or more icons or other commands) ( Figure 2B ).
[0044] Upon receiving the file retrieval request, at 126, the data storage system may retrieve and decrypt each of the encrypted constituent files corresponding to the requested file (e.g., with reference to the hash values of the constituent files). At 128, the data storage system may additionally calculate a hash value for each of the decrypted constituent files and compare the hash values of the decrypted files with the hash values of the corresponding constituent files stored in the blockchain (i.e., at 130, the data storage system determines whether the hash values correspond or match), typically as described in Figure 2B as shown in .
[0045] If the hash value of the decrypted file matches the hash values of the constituent files stored in the blockchain, the data storage system combines the files to create a file related to the originally uploaded file. If the hash value does not match the hash value stored in the blockchain at 128, the data storage system may send an alert to one or more of the participants (e.g., to the first and second participants) at 134 to indicate that the file may have been tampered with or otherwise altered.
[0046] In addition, if the hash value of the decrypted file matches the hash value of the constituent files stored in the blockchain, the data storage system can provide the reassembled file to the user, and also create a transaction with transaction information, and provide the transaction information to the current block 52 in the blockchain 22. The transaction information includes, but is not limited to, a transaction ID, which in some embodiments may include a hash of the reassembled file; a file type (e.g., PDF, word document, GIF, JPEG, WAV, MP3, etc.); information about the participants; the status of the transaction; time information; etc., typically as Figure 2B as shown in .
[0047] Alternatively, for additional verification, if the hash value of the decrypted file matches the hash values of the constituent files stored in the blockchain, then at 128 the data storage system may compare the hash value of the reassembled file with the hash value of the original file stored in the blockchain (i.e., at 130 the data storage system determines whether the hash values correspond or match), typically as described in Figure 2B If the hash value of the reassembled file matches the hash value of the original file stored in the blockchain, the data storage system provides the reassembled file to the requesting participant and also creates a transaction with transaction information and provides the transaction information to the current block 52 in the blockchain 22. The transaction information includes, but is not limited to, a transaction ID, a file type, information about the participants, a transaction status, time information, etc., typically as Figure 2B as shown in .
[0048] Figure 3 A flow chart of a method or process for secure data storage and transmission according to one aspect of the present disclosure is shown. Figure 3 As shown in , at 202, an original file may be received from one of a plurality of participants. At 204, a hash value of the received original file may be generated, and at 206, the received original file may be split into a plurality of smaller constituent files. In some embodiments, a hash value of each file in the smaller constituent files may also be generated.
[0049] Then, at 208, each of the plurality of smaller constituent files is encrypted using one or more predetermined encryption keys to generate a plurality of encrypted files. At 210, the plurality of encrypted files are stored in at least one storage location. In one variation, the plurality of encrypted files may be stored in a plurality of cloud-based storage locations, such as AWS, IPFS, etc., for redundancy. In some embodiments, the hash values of the smaller constituent files may facilitate the location of the encrypted files in the storage location(s).
[0050] At 212, transaction information may be generated and provided to the current block in the blockchain. In one variation, a hash value of each of the plurality of constituent files or the original file may also be provided to the current block in the blockchain, for example, as part of the transaction information.
[0051] Additionally, at 214, a file retrieval request may be received from one of the plurality of participants (e.g., the participant that uploaded the file or another participant). Upon receiving the file retrieval request, at 216, a plurality of encrypted files may be retrieved from the storage location(s). Then, at 218, each of the plurality of decrypted files may be decrypted using one or more predetermined encryption keys to generate a plurality of decrypted files. At 220, the plurality of decrypted files may be combined to generate a reassembled file associated with the original file, and at 222, a hash value of the reassembled file may be generated.
[0052] If the hash value of the reassembled file as determined at 224 matches the hash value of the original file, then the reassembled file may be provided to or otherwise made available to the requesting participant at 226. However, if the hash value of the reassembled file does not match the hash value of the original file, then an alert, warning, notification, etc. may be generated and provided to the participant at 228, for example to indicate that the file is corrupted, tampered with, or otherwise altered. Additionally, at 230, additional transaction information may be generated and provided to the current block in the blockchain.
[0053] Those skilled in the art will understand that Figure 3 One or more of the steps or actions shown in (e.g., 202 to 230) may be omitted or rearranged without departing from the scope of the present disclosure. For example, if the hash value of the reassembled file does not match the hash value of the original file, a hash value of the decrypted file may be generated and compared to the hash values of the constituent files originally provided to the storage location, for example to determine which specific files in the constituent files have been corrupted, tampered with, or otherwise changed. In addition, the storage location or the device / system that manages the storage location may be restored or reset to a restore point, a previous configuration, etc., where the hash values of the constituent files match the hash values of the constituent files originally provided to the storage location (e.g., to a point / configuration prior to corruption, tampering, change, etc.) to provide a reassembled file corresponding to the original uploaded file.
[0054] The foregoing description generally illustrates and describes various embodiments of the present disclosure. However, it will be understood by those skilled in the art that various changes and modifications may be made to the above-discussed construction of the present disclosure without departing from the spirit and scope of the present disclosure as disclosed herein, and it is intended that all contents contained in the above description or shown in the accompanying drawings should be interpreted as illustrative and not to be understood in a restrictive sense. In addition, the scope of the present disclosure should be interpreted as covering various modifications, combinations, additions, changes, etc. of the above and the above-described embodiments, which should be considered to be within the scope of the present disclosure. Therefore, the various characteristics and features of the present disclosure as discussed herein may be selectively interchangeable and applied to other illustrated and unexplained embodiments of the present disclosure, and may be further subjected to various modifications, modifications, and additions without departing from the spirit and scope of the present invention as set forth in the appended claims.
Claims
1. A method for secure data storage and transmission, comprising: Receive files uploaded by users and generate hash values for the uploaded files; Splitting the uploaded file into multiple component files; and Generate a hash value for each of the plurality of constituent files; encrypting each of the plurality of constituent files using one or more predetermined or user-selected encryption keys to generate a plurality of encrypted files, and storing the plurality of encrypted files in at least one storage location; Generate transaction information including at least a hash value of the uploaded file and hash values of the plurality of constituent files and provide the transaction information to a current block in the blockchain; upon receiving a file retrieval request from the user or another user, retrieving the plurality of encrypted files from the at least one storage location by referring to the hash values of the plurality of constituent files stored in the blockchain, and decrypting each of the plurality of encrypted files using the one or more predetermined or user-selected encryption keys to generate a plurality of decrypted files; generating a hash value for each of the plurality of decrypted files and determining whether the hash values of the plurality of decrypted files match the hash values of the plurality of constituent files; If the hash values of the plurality of decrypted files match the hash values of the plurality of constituent files, combining the plurality of decrypted files to generate a reassembled file; generating a hash value of the reassembled file and determining whether the hash value of the reassembled file matches the hash value of the uploaded file; and If the hash value of the reassembled file matches the hash value of the uploaded file, the reassembled file is provided to the user or other users, additional transaction information including at least the hash value of the reassembled file is generated, and the additional transaction information is provided to the current block in the blockchain.
2. The method according to claim 1, further comprising: If the hash value of the reassembled file or the hash value of each file in the plurality of decrypted files does not match the hash value of the uploaded file or the hash value of each corresponding file in the plurality of constituent files, an alert, warning or notification is generated. 3 . The method of claim 1 , wherein each file in the plurality of constituent files is stored in at least two cloud-based storage locations. The method of claim 1 , wherein each of the plurality of constituent files is smaller than an original file.
5. The method of claim 1, wherein encrypting each file in the plurality of constituent files comprises applying an encryption function to electronic data of each file in the plurality of constituent files, and wherein the encryption function comprises an AES256 function.
6. The method according to claim 1, wherein the transaction information relates to the uploaded file, component file or encrypted file, and includes a transaction identifier, a transaction type, participant information, status information and time information.
7. The method of claim 6, wherein the transaction identifier comprises a hash value of the uploaded file.
8. The method of claim 1, wherein the additional transaction information relates to reassembling a file, encrypting a file, or decrypting a file, and includes a transaction identifier, a transaction type, participant information, status information, and time information.
9. The method of claim 1, wherein generating a hash value of the uploaded file or each file in the constituent files comprises applying a hash function to the electronic data of the uploaded file or each file in the constituent files, wherein the hash function comprises a SHA256 or RIPEMD function.
10. A system for secure data storage and transmission, comprising: one or more processors; and One or more non-transitory computer-readable storage media having stored therein instructions that, when executed by one or more processors, cause the system to: Receiving an uploaded file and generating a hash value for the uploaded file; Splitting the uploaded file into multiple component files; generating a hash value for each of the plurality of constituent files; encrypting each of the plurality of constituent files using one or more predetermined or user-selected encryption keys to generate a plurality of encrypted files, and storing the plurality of encrypted files in at least one storage location; Generate transaction information including at least a hash value of the uploaded file and hash values of the plurality of constituent files and provide the transaction information to a current block in the blockchain; upon receiving a file retrieval request, retrieving the plurality of encrypted files from the at least one storage location by referring to the hash values of the plurality of constituent files stored in the blockchain, and decrypting each of the plurality of encrypted files using the one or more predetermined or user-selected encryption keys to generate a plurality of decrypted files; generating a hash value for each of the plurality of decrypted files and determining whether the hash values of the plurality of decrypted files match the hash values of the plurality of constituent files; If the hash values of the plurality of decrypted files match the hash values of the plurality of constituent files, combining the plurality of decrypted files to generate a reassembled file related to the uploaded file; generating a hash value of the reassembled file and determining whether the hash value of the reassembled file matches the hash value of the uploaded file; and If the hash value of the reassembled file matches the hash value of the uploaded file, access to the reassembled file is allowed, Additional transaction information including at least a hash value of the reassembled file is generated and provided to a current block in the blockchain.
11. The system according to claim 10, wherein: If the hash value of the reassembled file does not match the hash value of the uploaded file, the system generates an alert, warning, or notification.
12. The system of claim 10, wherein each file in the plurality of constituent files is stored in at least two cloud-based storage locations.
13. The system of claim 10, wherein each file of the plurality of constituent files is smaller than the uploaded file.
14. The system of claim 10, wherein an encryption function is applied to the electronic data of each file in the plurality of constituent files to encrypt each file in the plurality of constituent files, wherein the encryption function comprises an AES256 function.
15. A system according to claim 10, wherein the transaction information relates to the uploaded file, composed file or encrypted file, and includes a transaction identifier, transaction type, participant information, status information and time information, and wherein the additional transaction information relates to a reassembled file, encrypted file or decrypted file, and includes a transaction identifier, transaction type, participant information, status information and time information.
16. A method for secure data storage and transmission, comprising: Receives an uploaded file and splits it into its constituent files; Generate a hash value of the uploaded file and a hash value of each of the plurality of constituent files; encrypting each of the plurality of constituent files using one or more predetermined or user-selected encryption keys to generate a plurality of encrypted files, and storing the plurality of encrypted files in a plurality of storage locations; and Generate transaction information including a hash value of the uploaded file and provide it to a current block in the blockchain, wherein the hash value of each file in the plurality of constituent files can be used to identify or locate the corresponding encrypted file in the storage location; upon receiving a file retrieval request from one or more users, retrieving the plurality of encrypted files from at least one of the plurality of storage locations by referring to the hash values of the plurality of constituent files stored in the blockchain, and decrypting each of the plurality of encrypted files using the one or more predetermined or user-selected encryption keys to generate a plurality of decrypted files; generating a hash value for each file in the plurality of decrypted files, and determining whether the hash value for each file in the plurality of decrypted files matches the hash value for each corresponding file in the plurality of constituent files; If the hash value of each file of the plurality of decrypted files matches the hash value of each corresponding file of the plurality of component files, combining the plurality of decrypted files to generate a reassembled file related to the uploaded file; generating a hash value of the reassembled file and determining whether the hash value of the reassembled file matches the hash value of the uploaded file; and If the hash value of the reassembled file does not match the hash value of the uploaded file, the one or more users are notified.
17. The method according to claim 16, further comprising: If the hash value of each file in the plurality of decrypted files does not match the hash value of each corresponding file in the plurality of constituent files, an alert, warning, or notification is generated.
18. A method for secure data storage and transmission, comprising: receiving document retrieval requests from participants; When a file retrieval request is received, retrieving a plurality of encrypted files corresponding to the plurality of constituent files split from the original file from the plurality of storage locations by referring to the hash values of the plurality of constituent files stored in the blockchain; decrypting each file in the plurality of encrypted files using one or more predetermined or user-selected encryption keys to generate a plurality of decrypted files; determining whether a hash value of each file of the plurality of decrypted files matches a hash value of each corresponding file of the plurality of constituent files; If the hash value of each file of the plurality of decrypted files matches the hash value of each corresponding file of the plurality of component files, combining the plurality of decrypted files to generate a reassembled file related to the original file; Verifying that the reassembled file corresponds to the original value by comparing the hash value of the reassembled file with the hash value of the original file; and Generate transaction information and provide it to the current block in the blockchain.
19. The method according to claim 18, further comprising: If the hash value of the reassembled file does not match the hash value of the original file, an alert, warning, or notification is generated.
20. The method of claim 18, further comprising: If the hash value of each file in the plurality of decrypted files does not match the hash value of a corresponding file in the plurality of constituent files, an alert, warning, or notification is generated.
Citation Information
Patent Citations
Local data security protection system and method
CN105117635A
Block-chain based P2P network cloud storage method in big data environment
CN107360156A
