CN112231730A - Cloud-based file storage method, system and device and storage medium thereof - Google Patents
Cloud-based file storage method, system and device and storage medium thereof Download PDFInfo
- Publication number
- CN112231730A CN112231730A CN202011150962.7A CN202011150962A CN112231730A CN 112231730 A CN112231730 A CN 112231730A CN 202011150962 A CN202011150962 A CN 202011150962A CN 112231730 A CN112231730 A CN 112231730A
- Authority
- CN
- China
- Prior art keywords
- file
- private key
- user
- client
- cloud
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
Abstract
The application relates to a file protection method and a system based on cloud storage, which comprises the following steps: a user logs in a client; the client reads a first file pointed by a local file address according to the local file address designated by a user; the client equally divides the first file into a plurality of fragment files, and names the fragment files according to a preset rule to form a sequence, wherein the sequence corresponds to the first file; and the client sends the fragment files to the cloud for storage. The data security that this application has the storage to high in the clouds can obtain the effect that improves.
Description
Technical Field
The present application relates to the field of file storage, and in particular, to a cloud-based file storage method, system, and apparatus, and a storage medium thereof.
Background
In the data era, new technologies such as artificial intelligence, cloud computing and social networking sites are gradually popularized, and data is explosively increased. On a network platform, any behavior of an individual leaves data traces, and the data brings privacy exposure problems, so that privacy protection in the information age faces new challenges.
In the related art, in a common mode of storing a file to a cloud, the file of a client is generally directly sent to a corresponding cloud storage address for storage.
In view of the above-mentioned related art, the inventor believes that there is a defect that although the related art is also provided with a user login account and a password, the method is very easy to crack, and thus the security of personal information cannot be guaranteed.
Disclosure of Invention
In order to ensure privacy of file storage and improve data security, the application provides a file storage method, a file storage system, a file storage device and a file storage medium based on a cloud.
In a first aspect, the present application provides a file storage method based on a cloud, which adopts the following technical scheme:
a file storage method based on a cloud comprises the following steps:
a user logs in a client;
the client reads a first file pointed by a local file address according to the local file address designated by a user;
the client equally divides the first file into a plurality of fragment files, and names the fragment files according to a preset rule to form a sequence, wherein the sequence corresponds to the first file;
and the client sends the fragment files to the cloud for storage.
Through adopting above-mentioned technical scheme, the file that will wait to save to the high in the clouds is smashed and is a plurality of piece files, consequently uploads a plurality of piece files to the high in the clouds according to the mode of sequence, can not be discerned by the client after the file that is smashed is downloaded alone, only when the whole piece file in this sequence is downloaded, and make up according to predetermined sequence, just can be discerned, thereby make the file be difficult to by the light and easy discernment, consequently the data security after the file is smashed and is saved to the high in the clouds again can obtain improving.
Optionally, the steps further include:
after the user logs in, generating a user private key according to an account used by the user for logging in;
the client acquires a first instruction for judging whether to use a user private key, and if the content of the first instruction is yes, the client encrypts a plurality of fragment files generated by the first file one by using the user private key and generates a plurality of corresponding encrypted fragment files;
and the client sends the encrypted fragment file to the cloud for storage.
By adopting the technical scheme, in order to further improve the security of file storage, the fragmented files after being crushed are encrypted according to the unique user secret key of the user, and even if all the fragmented files corresponding to one file are downloaded according to the sequence, the fragmented files cannot be combined to form the original file without the corresponding decryption operation, so that the privacy degree of data is further improved.
Optionally, the steps further include: and the client acquires a second instruction for selecting whether to store the user private key to the cloud, and if the content of the second instruction is yes, a private key certificate corresponding to the user private key is generated and sent to the cloud for storage.
By adopting the technical scheme, in order to prevent the user from forgetting the user key or preventing the user key stored in the client or other terminals from being lost, the file encrypted by the user key cannot be decrypted, and the user key is stored in the cloud so that the user can conveniently find back the private key certificate.
Optionally, the steps further include: the client side obtains a third instruction for selecting to store the user private key to other application sides, if the content of the third instruction is yes, a private key certificate corresponding to the user private key is generated and sent to the other application sides to be stored, and meanwhile, the private key certificate of the cloud side is completely deleted.
By adopting the technical scheme, if the user selects to store the private key certificate to other application terminals, the private key certificate stored in the cloud terminal can be completely deleted in the cloud terminal, so that other client terminals cannot easily acquire the private key certificate, and the data security is further improved.
Optionally, in the process of generating the private key certificate corresponding to the private key of the user, if the data length of the private key is not sufficient, 1, 0 or characters are used for filling.
By adopting the technical scheme, the key length is insufficient, and the key needs to be supplemented.
Optionally, the steps further include: the client acquires a specified file downloading instruction, and downloads a fragment file or an encrypted fragment file in a sequence corresponding to the specified file from the cloud;
the client judges the file types in the sequence:
if the sequence corresponds to the fragment file, the client re-merges the fragment file and generates a corresponding first original file;
if the sequence corresponds to the encrypted fragment files, the client decrypts the encrypted fragment files one by using a user private key and generates corresponding plaintext fragment files; and combining the plurality of plaintext fragments and generating a second original file.
By adopting the technical scheme, after the file is encrypted and uploaded, when the file needs to be downloaded, the fragment files in the corresponding sequence are downloaded, and then the user private keys are used for decryption one by one, so that the plaintext fragments of the corresponding sequence are generated, and then a plurality of plaintext fragments are combined into a second original file.
Optionally, in the process of encrypting/decrypting, if the encryption operation fails, the client performs a re-encryption/decryption operation.
By adopting the technical scheme, if the operation fails in the decryption or encryption process, the file needs to be repeatedly encrypted or decrypted until the encryption or decryption is correct.
In a second aspect, the application provides a file storage system based on a cloud, which adopts the following technical scheme:
a file storage system based on cloud comprises the following modules:
the file crushing module is used for reading a first file pointed by a local file address by a client according to the local file address designated by a user; the client equally divides the first file into a plurality of fragment files, names the fragment files according to a preset rule to form a sequence, and corresponds the sequence to the first file;
the private key encryption module is used for acquiring a first instruction of whether to use a private key of a user, and if the content of the first instruction is yes, the private key encryption module encrypts a plurality of fragment files generated by the first file one by using the private key of the user and generates a plurality of corresponding encrypted fragment files;
the private key decryption module acquires a specified file downloading instruction and downloads a fragment file or an encrypted fragment file in a sequence corresponding to the specified file from the cloud; the client judges the file types in the sequence: if the sequence corresponds to the fragment file, the client re-merges the fragment file and generates a corresponding first original file; if the sequence corresponds to the encrypted fragment files, the client decrypts the encrypted fragment files one by using a user private key and generates corresponding plaintext fragment files;
the file merging module is used for acquiring a merging instruction, merging the plaintext fragments and generating a second original file;
the private key storage selection module is used for acquiring a second instruction for selecting whether to store the private key of the user to the cloud, and if the content of the second instruction is yes, generating a private key certificate corresponding to the private key of the user and sending the private key certificate to the cloud for storage; acquiring a third instruction for selecting to store the user private key to other application terminals, if the content of the third instruction is yes, generating a private key certificate corresponding to the user private key, sending the private key certificate to other application terminals for storage, and completely deleting the private key certificate at the cloud end;
and the file sending/downloading module is used for sending the file of the client to the cloud according to the user instruction, or downloading the file of the corresponding sequence from the cloud to the client according to the user instruction.
By adopting the technical scheme, in the process of uploading the first file to the cloud, the first file is equally divided into a plurality of fragment files, then the fragment files are encrypted one by one, and the encrypted fragment files generated after encryption are uploaded to the cloud; when a first file needs to be downloaded and replied, after a plurality of uploaded encrypted fragment files are downloaded, the encrypted fragment files are decrypted one by using a user private key, and decrypted plaintext fragments are combined to generate a first original file, namely the first file; during uploading, firstly, crushing the file, and encrypting the crushed file by using a unique user private key of a client; in the downloading project, the unique user private key of the client is firstly used for decryption, and the crushed files are combined, so that the initial file is restored, the privacy of the file stored in the cloud is improved, and the data security is improved.
In a third aspect, the present application provides an intelligent terminal or a cloud-based file storage device, including a memory and a processor, where the memory stores a computer program that can be loaded by the processor and execute any one of the above methods of the cloud-based file storage device.
In a fourth aspect, the present application provides a computer storage medium, which adopts the following technical solutions:
a computer readable storage medium storing a computer program that can be loaded by a processor and executed to perform any of the above-described cloud-based file storage method.
The application at least comprises the following beneficial effects:
the file that will wait to save to the high in the clouds is smashed and is a plurality of piece files, consequently uploads a plurality of piece files to the high in the clouds according to the mode of sequence, can not be discerned by the client after the file that is smashed is downloaded alone, only when the whole piece file in this sequence is downloaded, and make up according to predetermined sequence, just can be discerned to make the file be difficult to by the light and easy discernment, consequently the data security after the file is smashed and is saved to the high in the clouds again can obtain improving.
Drawings
Fig. 1 is a schematic diagram illustrating steps of a cloud-based file storage method according to the present application;
FIG. 2 is a schematic flow chart of a method of the present application for cloud-based file storage;
fig. 3 is a system structure block diagram of the cloud-based file storage system according to the present application.
Reference numerals: 1. a file shredding module; 2. a private key encryption module; 3. a private key decryption module; 4. a private key storage selection module; 5. a file merging module; 6. and a file sending/downloading module.
Detailed Description
The present application is described in further detail below with reference to figures 1-3.
The embodiments of the present application will be described in further detail with reference to the drawings attached hereto.
The embodiment of the application discloses a file storage method based on a cloud end, as shown in fig. 1 and fig. 2, the file storage method comprises the following steps:
and the user logs in the client. The client may also be a user side, the device of the client may adopt an intelligent device, such as a smart phone, running with an android system or an IOS system, and the client is an APP running on the device. Be equipped with communication module such as GPS, bluetooth, WIFI and GPRS in the smart machine, still be equipped with the touch-sensitive screen that is used for showing data and receiving input in the smart machine, the transmission of data is realized to customer end accessible communication module, and the accessible touch-sensitive screen is used for showing UI and acquireing user's operation. After the user logs in, a user private key is generated according to an account used by the user for logging in, and the user private key and the account are in one-to-one correspondence and are unique. The private key of the user is also called a private key, which is different from a password used for logging in by a person. The private key is a key certificate dedicated to encrypting fragmented files, and the key certificate of each user is a globally unique binary code generated based on a UUID, and is therefore referred to as a private key. The key certificate is generated by the client code when the user first logs in.
And the client reads the first file pointed by the local file address according to the local file address designated by the user. The client displays the icon of the local file, after the user clicks the displayed icon, the clicked local file is the local file designated by the user, and the client can read the storage address of the file. The first file is a file to be stored to the cloud.
The client equally divides the first file into a plurality of fragment files, names the fragment files according to a preset rule to form a sequence, and the sequence corresponds to the first file. The first file may be equally divided into a plurality of subfiles.
The client side obtains a first instruction whether to use a user private key, and if the content of the first instruction is yes, the user private key is used for encrypting a plurality of fragment files generated by the first file one by one, and a plurality of corresponding encrypted fragment files are generated. The process of encryption and decryption uses the AES-128 bit algorithm. The AES algorithm is called "advanced encryption standard" in its entirety, translated as "advanced encryption standard", also called Rijndael encryption method, is a block encryption standard adopted by the federal government in the united states, and is the most reliable symmetric encryption algorithm at present. Using the user private key, encrypted data can not be used as well even if the data is stolen, which is a low probability event, without the user private key.
And the client sends the fragment files to the cloud for storage.
And the client sends the encrypted fragment file to the cloud for storage. The client side obtains a third instruction for selecting to store the user private key to other application sides, if the content of the third instruction is yes, a private key certificate corresponding to the user private key is generated and sent to the other application sides to be stored, and meanwhile, the private key certificate of the cloud side is completely deleted. And the client acquires a second instruction for selecting whether to store the user private key to the cloud, and if the content of the second instruction is yes, a private key certificate corresponding to the user private key is generated and sent to the cloud for storage. The user can store the user private key in the cloud, and can also select to be stored in the client by himself. When the user is selected to be stored by himself, the cloud can thoroughly delete the user private key stored in the cloud, and if the user private key is lost, all files encrypted by the user private key cannot be decrypted. And in the process of generating the private key certificate corresponding to the private key of the user, if the data length of the private key is not enough, filling the private key with 1, 0 or characters.
When a user needs to upload and download files from the cloud, the files in the cloud are checked through the client, and the sub-files in the cloud are displayed into a UI of the files before being smashed in the client. After a user clicks a UI of a file on the UI of the client, the client acquires a specified file downloading instruction, and downloads a fragment file or an encrypted fragment file in a sequence corresponding to the specified file from the cloud.
The client judges the file types in the sequence: and if the sequence corresponds to the fragment file, the client re-merges the fragment file and generates a corresponding first original file. And if the sequence corresponds to the encrypted fragment files, the client decrypts the encrypted fragment files one by using a user private key to generate corresponding plaintext fragment files, combines the plaintext fragments and generates a second original file. The first original file is a file which is not subjected to reduction on the fragmented file, and the second original file is a file which is subjected to reduction on the encrypted cheating file.
And in the process of encrypting/decrypting, if the encryption operation fails, the client carries out re-encryption/decryption operation.
The implementation principle of the file storage method based on the cloud end in the embodiment of the application is as follows: the file that will wait to save to the high in the clouds is smashed and is a plurality of piece files, consequently uploads a plurality of piece files to the high in the clouds according to the mode of sequence, can not be discerned by the client after the file that is smashed is downloaded alone, only when the whole piece file in this sequence is downloaded, and make up according to predetermined sequence, just can be discerned to make the file be difficult to by the light and easy discernment, consequently the data security after the file is smashed and is saved to the high in the clouds again can obtain improving. In order to further improve the security of file storage, the fragmented files after being crushed are encrypted according to a user key unique to a user, and even if all fragmented files corresponding to one file are downloaded according to a sequence, the fragmented files cannot be combined to form an original file without corresponding decryption operation, so that the privacy degree of data is further improved. In order to prevent the user from forgetting the user key or losing the user key stored in the client or other terminals, the file encrypted by the user key cannot be decrypted, and the user key is stored in the cloud so that the user can conveniently retrieve the private key certificate. If the user selects to store the private key certificate to other application terminals, the private key certificate stored in the cloud terminal can be completely deleted in the cloud terminal, so that other client terminals cannot easily acquire the private key certificate, and the data security is further improved. After the file is encrypted and uploaded, when the file needs to be downloaded, the fragment files in the corresponding sequence are downloaded, then the user private keys are used for decryption one by one, so that plaintext fragments of the corresponding sequence are generated, and then the plaintext fragments are combined into a second original file. If the operation fails in the process of decryption or encryption, the file needs to be encrypted or decrypted repeatedly until the encryption or decryption is correct.
The embodiment of the application further discloses a file storage system based on the cloud end, as shown in fig. 3, the file storage system comprises the following modules:
the file crushing module 1 is used for reading a first file pointed by a local file address by a client according to the local file address designated by a user; the client equally divides the first file into a plurality of fragment files, names the fragment files according to a preset rule to form a sequence, and corresponds the sequence to the first file.
And the private key encryption module 2 is used for acquiring a first instruction whether to use the private key of the user, and if the content of the first instruction is yes, encrypting the multiple fragment files generated by the first file one by using the private key of the user and generating multiple corresponding encrypted fragment files.
The private key decryption module 3 is used for acquiring a specified file downloading instruction and downloading a fragment file or an encrypted fragment file in a sequence corresponding to the specified file from the cloud; the client judges the file types in the sequence: if the sequence corresponds to the fragment file, the client re-merges the fragment file and generates a corresponding first original file; and if the sequence corresponds to the encrypted fragment files, the client decrypts the encrypted fragment files one by using the user private key and generates corresponding plaintext fragment files.
And the file merging module 5 is configured to obtain a merging instruction, merge the multiple plaintext fragments, and generate a second original file.
The private key storage selection module 4 is used for acquiring a second instruction for selecting whether to store the private key of the user to the cloud, and if the content of the second instruction is yes, generating a private key certificate corresponding to the private key of the user and sending the private key certificate to the cloud for storage; and acquiring a third instruction for selecting to store the user private key to other application terminals, if the content of the third instruction is yes, generating a private key certificate corresponding to the user private key, sending the private key certificate to other application terminals for storage, and completely deleting the private key certificate at the cloud end.
And the file sending/downloading module 6 is used for sending the file of the client to the cloud according to the user instruction, or downloading the file of the corresponding sequence from the cloud to the client according to the user instruction.
The implementation principle of the file storage system based on the cloud end in the embodiment of the application is as follows: in the process of uploading the first file to the cloud, the first file is equally divided into a plurality of fragment files, then the fragment files are encrypted one by one, and the encrypted fragment files generated after encryption are uploaded to the cloud; when a first file needs to be downloaded and replied, after a plurality of uploaded encrypted fragment files are downloaded, the encrypted fragment files are decrypted one by using a user private key, and decrypted plaintext fragments are combined to generate a first original file, namely the first file; during uploading, firstly, crushing the file, and encrypting the crushed file by using a unique user private key of a client; in the downloading project, the unique user private key of the client is firstly used for decryption, and the crushed files are combined, so that the initial file is restored, the privacy of the file stored in the cloud is improved, and the data security is improved.
The embodiment of the application further discloses a cloud-based file storage device, which comprises a memory and a processor, wherein the memory is stored with a computer program which can be loaded by the processor and can execute any one of the above cloud-based file storage device methods.
The embodiment of the present application further provides a computer-readable storage medium, which stores a computer program that can be loaded by a processor and execute the above-mentioned cloud-based file storage method.
The above embodiments are preferred embodiments of the present application, and the protection scope of the present application is not limited by the above embodiments, so: all equivalent changes made according to the structure, shape and principle of the present application shall be covered by the protection scope of the present application.
Claims (10)
1. A file storage method based on a cloud is characterized in that: the method comprises the following steps:
a user logs in a client;
the client reads a first file pointed by a local file address according to the local file address designated by a user;
the client equally divides the first file into a plurality of fragment files, and names the fragment files according to a preset rule to form a sequence, wherein the sequence corresponds to the first file;
and the client sends the fragment files to the cloud for storage.
2. The method of claim 1, wherein: the method also comprises the following steps:
after the user logs in, generating a user private key according to an account used by the user for logging in;
the client acquires a first instruction for judging whether to use a user private key, and if the content of the first instruction is yes, the client encrypts a plurality of fragment files generated by the first file one by using the user private key and generates a plurality of corresponding encrypted fragment files;
and the client sends the encrypted fragment file to the cloud for storage.
3. The method of claim 2, wherein: the method also comprises the following steps:
and the client acquires a second instruction for selecting whether to store the user private key to the cloud, and if the content of the second instruction is yes, a private key certificate corresponding to the user private key is generated and sent to the cloud for storage.
4. The method of claim 2, wherein: the method also comprises the following steps:
the client side obtains a third instruction for selecting to store the user private key to other application sides, if the content of the third instruction is yes, a private key certificate corresponding to the user private key is generated and sent to the other application sides to be stored, and meanwhile, the private key certificate of the cloud side is completely deleted.
5. The method of claim 3, wherein: in the step of equally dividing the plurality of fragmented files, the client side: and in the process of generating the private key certificate corresponding to the private key of the user, if the data length of the private key is not enough, filling the private key with 1, 0 or characters.
6. The method according to any one of claims 1 to 5, wherein: the method also comprises the following steps:
the client acquires a specified file downloading instruction, and downloads a fragment file or an encrypted fragment file in a sequence corresponding to the specified file from the cloud;
the client judges the file types in the sequence:
if the sequence corresponds to the fragment file, the client re-merges the fragment file and generates a corresponding first original file;
if the sequence corresponds to the encrypted fragment files, the client decrypts the encrypted fragment files one by using a user private key and generates corresponding plaintext fragment files; and combining the plurality of plaintext fragments and generating a second original file.
7. The method of claim 6, wherein:
and in the process of encrypting/decrypting, if the encryption operation fails, the client carries out re-encryption/decryption operation.
8. A file storage system based on high in clouds, its characterized in that: the system comprises the following modules:
the file crushing module (1) is used for reading a first file pointed by a local file address by a client according to the local file address designated by a user; the client equally divides the first file into a plurality of fragment files, names the fragment files according to a preset rule to form a sequence, and corresponds the sequence to the first file;
the private key encryption module (2) is used for acquiring a first instruction whether to use a private key of a user, and if the content of the first instruction is yes, the private key encryption module encrypts a plurality of fragment files generated by the first file one by using the private key of the user and generates a plurality of corresponding encrypted fragment files;
the private key decryption module (3) is used for acquiring a specified file downloading instruction and downloading a fragment file or an encrypted fragment file in a sequence corresponding to the specified file from the cloud; the client judges the file types in the sequence: if the sequence corresponds to the fragment file, the client re-merges the fragment file and generates a corresponding first original file; if the sequence corresponds to the encrypted fragment files, the client decrypts the encrypted fragment files one by using a user private key and generates corresponding plaintext fragment files;
the file merging module (5) is used for acquiring a merging instruction, merging the plaintext fragments and generating a second original file;
the private key storage selection module (4) is used for acquiring a second instruction for selecting whether to store the private key of the user to the cloud, and if the content of the second instruction is yes, generating a private key certificate corresponding to the private key of the user and sending the private key certificate to the cloud for storage; acquiring a third instruction for selecting to store the user private key to other application terminals, if the content of the third instruction is yes, generating a private key certificate corresponding to the user private key, sending the private key certificate to other application terminals for storage, and completely deleting the private key certificate at the cloud end;
and the file sending/downloading module (6) is used for sending the file of the client to the cloud according to the user instruction, or downloading the file of the corresponding sequence from the cloud to the client according to the user instruction.
9. The utility model provides an intelligent terminal or file storage device based on high in clouds which characterized in that: comprising a memory and a processor, said memory having stored thereon a computer program which can be loaded by the processor and which performs the method of any of claims 1 to 7.
10. A computer-readable storage medium characterized by: a computer program which can be loaded by a processor and which performs the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011150962.7A CN112231730A (en) | 2020-10-24 | 2020-10-24 | Cloud-based file storage method, system and device and storage medium thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011150962.7A CN112231730A (en) | 2020-10-24 | 2020-10-24 | Cloud-based file storage method, system and device and storage medium thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112231730A true CN112231730A (en) | 2021-01-15 |
Family
ID=74109933
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011150962.7A Pending CN112231730A (en) | 2020-10-24 | 2020-10-24 | Cloud-based file storage method, system and device and storage medium thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231730A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103346998A (en) * | 2013-05-18 | 2013-10-09 | 北京凯锐立德科技有限公司 | File breaking encryption-based file security protection method |
| US20130275695A1 (en) * | 2012-04-12 | 2013-10-17 | Qatar Foundation | Backup and storage system |
| CN104754055A (en) * | 2015-04-03 | 2015-07-01 | 易云捷讯科技（北京）有限公司 | Safety cloud storage method for use in multi-cloud environment |
| CN106294585A (en) * | 2016-07-28 | 2017-01-04 | 四川新环佳科技发展有限公司 | A kind of storage method under cloud computing platform |
| CN109451004A (en) * | 2018-10-30 | 2019-03-08 | 四川乐为科技有限公司 | Cloud storage system and method based on cloud bridge |
-
2020
- 2020-10-24 CN CN202011150962.7A patent/CN112231730A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130275695A1 (en) * | 2012-04-12 | 2013-10-17 | Qatar Foundation | Backup and storage system |
| CN103346998A (en) * | 2013-05-18 | 2013-10-09 | 北京凯锐立德科技有限公司 | File breaking encryption-based file security protection method |
| CN104754055A (en) * | 2015-04-03 | 2015-07-01 | 易云捷讯科技（北京）有限公司 | Safety cloud storage method for use in multi-cloud environment |
| CN106294585A (en) * | 2016-07-28 | 2017-01-04 | 四川新环佳科技发展有限公司 | A kind of storage method under cloud computing platform |
| CN109451004A (en) * | 2018-10-30 | 2019-03-08 | 四川乐为科技有限公司 | Cloud storage system and method based on cloud bridge |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9767299B2 (en) | Secure cloud data sharing | |
| CN104852925B (en) | Mobile intelligent terminal anti-data-leakage secure storage, backup method | |
| US8990565B2 (en) | Method and system for automatically logging in a client | |
| US8751809B2 (en) | Method and device for securely sharing images across untrusted channels | |
| CN113364760A (en) | Data encryption processing method and device, computer equipment and storage medium | |
| US20180124023A1 (en) | Method, system and apparatus for storing website private key plaintext | |
| CN111897786B (en) | Log reading method, device, computer equipment and storage medium | |
| CN104662870A (en) | Data security management system | |
| CN111143474B (en) | One-key binding changing method for mobile phone number based on block chain technology | |
| CN104283668A (en) | Method and device for obtaining application password based on mobile terminal | |
| CN107124279B (en) | Method and device for erasing terminal data | |
| CN105117635A (en) | Local data security protection system and method | |
| CN105101183A (en) | Method and system for protecting private contents at mobile terminal | |
| CN112632007B (en) | Log storage and extraction method, device, equipment and storage medium | |
| CN104615929A (en) | Security key device for secure cloud services, and system and method of providing security cloud services | |
| WO2015183783A1 (en) | Method and system for encrypting and transmitting information over unsecured communication channel | |
| CN104462998A (en) | Domestic commercial cryptography algorithm based cloud storage encryption system and implementation method thereof | |
| CN111639357A (en) | Encryption network disk system and authentication method and device thereof | |
| WO2020000765A1 (en) | Off-line data storage method and apparatus, computer device and storage medium | |
| CN113127844A (en) | Variable access method, device, system, equipment and medium | |
| CN112199730A (en) | Method and device for processing application data on terminal and electronic equipment | |
| CN111181905B (en) | File encryption method and device | |
| US10244391B2 (en) | Secure computer file storage system and method | |
| CN103516722A (en) | Subscriber stage file automatic encryption and decryption method and device | |
| CN109871698B (en) | Data processing method, data processing device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210115 |