KR101993309B1 - Method and program for storing service data by cloud account - Google Patents

Abstract

The present invention relates to a service internal data storing method and program using a cloud account.
A method for storing service internal data using a cloud account according to an embodiment of the present invention includes: requesting a service server to access each cloud server by a user to perform login (S400); Receiving token data from the cloud server (S600; token data receiving step); And a step (S1000) of storing the plurality of divided data generated by dividing the service internal data uploaded in the group space on-line into the cloud storage of the users included in the group (S1000: internal service data storing step).

Description

METHOD AND PROGRAM FOR STORING SERVICE DATA BY CLOUD ACCOUNT USING THE CLOUD ACCOUNT

The present invention relates to a service internal data storage method and program using a cloud account, and more particularly, to a method and a program for distributing and storing data stored in a service in a plurality of cloud accounts.

Cloud services are a mix of computing and communication services, such as virtualization, utility, and on demand computing. Typically, virtualized computer systems are used to provide users with a variety of software, security solutions, or computing resources. Means the service provided.

In particular, the cloud service can provide a wide range of data storage services to the user, allowing the user to store programs or documents individually stored in the personal computer device in an Internet-based cloud server.

And, the user can drive or browse a program or a document stored in the cloud server through various terminals such as a personal computer or a smart phone. This cloud service has the advantage of allowing the user to freely access the stored data without being affected by the place, and to utilize a richer computing resource than the user can personally provide.

In addition, various online services are provided based on the server. With the development of communication technologies such as faster communication speed, online service stores data acquired in a service operation process in a server. Accordingly, when the amount of data to be stored increases due to an increase in users during the online service operation, the server must be expanded to secure storage space.

The present invention relates to a service internal data storage method using a cloud account, in which data generated and stored in a process of providing a specific service is distributedly stored in a plurality of cloud accounts without being stored in a service server space, And programs.

The problems to be solved by the present invention are not limited to the above-mentioned problems, and other problems which are not mentioned can be clearly understood by those skilled in the art from the following description.

According to an embodiment of the present invention, there is provided a method of storing service internal data using a cloud account, the method comprising: requesting a service server to access each cloud server by a user and perform login; Receiving token data from the cloud server and storing the token data, wherein the token data is allowed to access a cloud storage space of a specific user to a service server; And a service internal data storage step of distributing and storing a plurality of divided data generated by dividing the service internal data uploaded in the group space on-line into a plurality of cloud storages.

In another embodiment, the service internal data is divided into a plurality of pieces of detailed data to perform primary encryption, and secondary data encryption is performed to compress each piece of detailed data in a specific compression method to generate a plurality of divided data pieces .

According to another embodiment of the present invention, the step of storing the service internal data includes the steps of: duplicating the service internal data to generate first internal data and second internal data; Generating the same first division data and a plurality of second division data by applying the same division method to the first service internal data and the second service internal data; And distributing the same data in the plurality of first divided data and the plurality of second divided data such that the types of users do not overlap with the types of cloud services and storing the same.

In another embodiment, the method further comprises: checking at least one cloud account information provided from the user when a specific user is excluded from the group; Checking deletion data stored in the cloud account of the user; A pair data search step of searching for pair data corresponding to the deletion data, wherein the deletion data and the pair data are identical data in the first partition data and the second partition data; And requesting transmission of the at least one pair data to the cloud account in which the pair data is stored and the cloud account in which the type of the user and the cloud service do not match in consideration of the storage location of the previously stored divided data.

According to another embodiment of the present invention, after transmitting the token data for the specific cloud service to the cloud server for storing or requesting the divided data, it is received that the token data is invalid and the user's group exclusion is confirmed do.

In another embodiment, when the directory in which the partitioned data in the cloud account is stored is deleted by a specific user, the partitioned data corresponding to the at least one deletion data is identified. A pair data search step of searching for pair data corresponding to the deletion data, wherein the deletion data and the pair data are identical data in the first partition data and the second partition data; And requesting the pair data to be transmitted to the cloud account of the user to perform directory regeneration.

Further, in another embodiment, the token data is set to be accessible only to a specific directory in which the partition data generated by the service server is stored.

According to another embodiment of the present invention, there is provided a method for managing a cloud service, comprising: checking a cloud service number and an account number for each cloud service based on a plurality of cloud account information received from a plurality of users; And dividing the service internal data based on the number of cloud services and the number of accounts per cloud service to calculate the maximum number of distributable and storable services.

According to another embodiment, there is provided a method for receiving an in-service data transmission request from a specific user, A link address collecting step of collecting a divided data link address corresponding to the received service internal data, wherein the link address is connected to a cloud server storing each divided data to receive divided data; And an integrated link transmission step of transmitting an integrated link to the client device of the user, wherein the integrated link is linked with a plurality of link addresses for each divided data, the client device further comprising: In accordance with an operation of a user of the apparatus, receives a plurality of divided data, and merges the plurality of divided data to generate in-service data.

A service internal data storage program using a cloud account according to another embodiment of the present invention executes a method of storing service internal data using the above-mentioned cloud account in combination with hardware, and is stored in a medium.

According to the present invention as described above, the following various effects are obtained.

First, the present invention provides an effect that the capacity of the service server is not greatly expanded even if the number of service users increases and data stored in the service increases. That is, the present invention provides the effect that individual cloud storage provided by a plurality of cloud services of a user can be connected to a specific service as one large cloud storage for use.

Second, users who use the service to which the present invention is applied can expand the cloud account by adding a cloud account as needed. In addition, users can obtain the effect of not having to pay for using the server capacity of the service to be used.

Third, since the internal data of the service is divided and stored in a plurality of cloud storages, it is possible to prevent leakage of internal data of the service, thereby enhancing security. In other words, since the entire data constituting the service internal data is not stored in the specific server, it is possible to prevent the in-service data from being leaked as soon as a specific server is hacked. Also, unlike other services that directly provide cloud storage, services using embodiments of the present invention do not directly store cloud storage in the service server even if the service server is hacked, so that the hacker can not access the user's data It is effective.

Fourth, in the case where the specific cloud service used by the user is terminated or the service of the corresponding cloud service can not be used due to a service failure corresponding to the service, the service using the embodiments of the present invention does not need to transfer the data directly to another cloud storage , And the data is transferred to another story space connected to the service, and the user is provided with convenience by auto-migration. That is, when adding an account to a service using the embodiments of the present invention, the user does not need to consider whether the cloud service of the account can be continuously operated and used for storing the service internal data.

1 is a structural diagram of a service internal data storage system using a cloud account according to an embodiment of the present invention.
2 to 8 are flowcharts of a method for storing service internal data using a cloud account according to embodiments of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. To fully disclose the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

The terminology used herein is for the purpose of illustrating embodiments and is not intended to be limiting of the present invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. The terms " comprises "and / or" comprising "used in the specification do not exclude the presence or addition of one or more other elements in addition to the stated element.

In this specification, "cloud service" refers to a service that stores software and contents in a computer (data center) connected to the Internet and can read and write them whenever necessary.

As used herein, the term " cloud account " refers to an account assigned to a particular user who has subscribed to the cloud service. Each cloud account is provided with a certain amount of storage space provided by each cloud service.

In this specification, 'service internal data' means data stored by a user in a service operated by a service server. For example, in the case of a service to which a plurality of users are subscribed, such as a collaboration tool, 'service internal data' refers to data stored in a storage space of a collaboration group by a plurality of users.

Hereinafter, a service internal data storage method and program using a cloud account according to embodiments of the present invention will be described in detail with reference to the drawings.

Referring to FIG. 2, a service internal data storage method using a cloud account according to an embodiment of the present invention is a method in which a service server 100 accesses each of the cloud servers 200 by a user, Step S400; Receiving token data from the cloud server 200 (S600: token data receiving step); And a step (S1000) of storing the plurality of divided data generated by dividing the service internal data uploaded in the group space on-line into the cloud storage of the users included in the group (S1000: internal service data storing step). Hereinafter, a detailed description of each step will be described.

The service server 100 requests the user to access each of the cloud servers 200 and perform login (S400). In one embodiment, the service server 100 receives the ID and password of the cloud service directly from the user, and transmits the ID and the password to the cloud server 200 to proceed with the login. That is, if the service server 100 receives one or more cloud account information from one or more users (e.g., a plurality of users included in the group when the service is a service storing information of a specific group) The account information can be transmitted to the cloud server 200.

In another embodiment of the method of performing login to each cloud service by the user, the service server 100 displays a login page of each cloud service in response to a user's request for a cloud account login on the service application screen or the service web page screen Can be connected and provided. Then, the account information (i.e., ID and password) input by each user is directly transferred to the cloud server 200 without being stored in the service server 100. To this end, the service server 100 may include a third party client API (Application Programming Interface) that provides each cloud service accessible from other services.

The service server 100 may be provided with a plurality of cloud accounts of a specific user or may receive one or more cloud accounts of each user from a plurality of users. In one embodiment, when a service is operated for each user, a specific user provides his or her own multiple cloud accounts. That is, the service server 100 may provide a plurality of different cloud service accounts by sequentially providing the cloud service login page selected by the user.

In another embodiment, when a plurality of users use a service as a group, the service server 100 receives one or more cloud accounts held by each user from a plurality of users. For example, in the case of providing a collaboration service between a plurality of users, in order to form a storage space for storing group data to be shared by a plurality of users or data input in the service, One or more cloud accounts may be provided from the user. As will be described later, the storage spaces of a plurality of cloud accounts provided by the respective users are combined and used as a space for storing information at the time of providing a service.

In addition, when the service server 100 needs new storage to replace the storage of a user excluded from the service (for example, a user excluded from the group in the collaboration service) as described below, , A new account for a specific cloud service can be input and added by the user.

The service server 100 receives and stores the token data from the cloud server 200 (S600: token data receiving step). The token data allows the service server 100 to access the cloud storage space of a specific user. The service server 100 accesses the storage space corresponding to each account in the cloud server 200 without storing account information of each cloud account by receiving and storing the token data corresponding to the account information of each user . Thus, the service server 100 stores token data corresponding to the number of connected cloud accounts.

The token data provided in the cloud server 200 may be authorized to access the entire directory of accounts provided to the service server 100, in one embodiment. Further, in another embodiment, it may be authorized to access only the directory where data of a specific service is stored. For example, the token data may be set to be accessible only to a specific directory in which the partition data generated by the service server 100 is stored, as described later. The range of account storage space accessible by the token data may be determined according to the cloud service settings or user settings.

The service server 100 divides and stores the plurality of divided data generated by dividing the service internal data uploaded on-line into the cloud storage of the users included in the group (S1000: service internal data storage step). The service server 100 transmits the divided data to each user's cloud account based on the token data for the plurality of cloud accounts. For example, when a plurality of users, such as a collaboration service, uploads service internal data (for example, a file or a post to be shared among a plurality of users) to a group space provided on-line, the service server 100 The service internal data uploaded in the group space can be divided into a plurality of divided data and distributed to each of the cloud accounts and stored.

The service server 100 may divide the service internal data in various ways and transmit the divided internal data to the storage space corresponding to each account. In one embodiment of the method of dividing the service internal data, the service server 100 transmits a plurality of detailed data (for example, data in which one internal service data is divided into equal size data ), And compress the respective detailed data for secondary encryption to generate divided data to be distributedly stored in each of the cloud storages.

Further, in another embodiment, the service server 100 may compress (i.e., divide-and-compress) a specific service internal data after it is compressed. Specifically, the service server 100 performs a primary encryption by compressing the service internal data, and performs a secondary encryption that divides the service internal data into a specific number of files to generate a plurality of divided data. This makes it impossible to confirm the information contained in the service internal data even if the divided data stored in the cloud account of a specific user is leaked by hacking or the like.

In addition, as shown in FIG. 3, when only one partition data for a specific service internal data is generated in the service internal data storage step (S1000), the partition data included in a specific cloud account is lost The service server 100 generates the same divided data in a redundant manner and stores the data in a distributed manner. Specifically, a step (S1010) of duplicating the service internal data and generating the first service internal data and the second service internal data is performed (S1010). A step (S1020) of generating a plurality of first divided data and a plurality of second divided data by applying the same division method to the first service internal data and the second service internal data; And distributing and storing the same data in the plurality of first divided data and the plurality of second divided data so that the types of users or cloud services do not overlap (S1030).

The service server 100 duplicates the service internal data and generates the first service internal data and the second service internal data (S1010). That is, the service server 100 duplicates specific service internal data uploaded by the user and generates two copies. For example, the service server 100 may set the original data uploaded by the user as internal data of the first service, and generate the duplicated data replicated with the original data as the internal data of the second service.

Thereafter, the service server 100 generates a plurality of first divided data and a plurality of second divided data by applying the same division method to the first service internal data and the second service internal data (S1020) . That is, the service server 100 applies the same partitioning scheme (for example, dividing the same data size and the same compression scheme) so that the first partitioned data and the second partitioned data form a specific pair. Accordingly, even if one of the first divided data and the second divided data constituting a pair is lost, it can be restored using the pair data (divided data constituting a pair).

Thereafter, the service server 100 distributes the same data in the plurality of first divided data and the plurality of second divided data so that the types of users or cloud services do not overlap (S1030). If the user or the divided data pair that is paired with the account having the same cloud service type is stored, the pair data can be lost simultaneously due to the departure / withdrawal of the user or the service termination / server down of the cloud service. Accordingly, the first divided data and the second divided data are distributed and stored in an account in which the types of users or cloud services do not overlap.

In an exemplary embodiment, when the service is used by a specific user, the service server 100 may receive a plurality of cloud accounts for each cloud service possessed by the user. At this time, the service server 100 controls not to store the first divided data and the second divided data, which are pair data, in the account of the same cloud service. In addition, in another embodiment, when the storage space of a service is formed by a plurality of cloud accounts provided from a plurality of users, the service server 100 stores first divided data paired with accounts in different cloud services of different users, So that the second divided data is distributed and stored.

Also, in an embodiment of the present invention, instead of generating the first service internal data and the second service internal data and then generating the plurality of first divided data and the plurality of second divided data through the same encryption method, It is possible to generate a plurality of first divided data and a plurality of second divided data by duplicating all the plurality of divided data after generating the plurality of divided data with the specific encryption method. Thereafter, the service server distributes a plurality of first divided data and a plurality of second divided data in the same manner.

In addition, as shown in FIG. 4, another embodiment of the present invention further includes a step (S1200) of restoring specific segmented data that the service server 100 has lost. For example, when specific divided data is lost, a specific user is excluded when account information is provided from a plurality of users, and the divided data stored in a specific cloud server 200 can not be provided (for example, For example, a cloud service is down, or a particular cloud service no longer supports a service to which a storage method according to an embodiment of the present invention is applied), or the user may delete the partitioned data storage directory in the account have.

In one embodiment, as shown in FIG. 5, if a specific user is excluded from the group, step (S1210) of checking at least one cloud account information provided from the user; Confirming deletion data stored in the cloud account of the user (S1220); A pair data search step (S1230) of searching for pair data corresponding to the deletion data, wherein the deletion data and the pair data are data in the first partition data and the second partition data; And requesting transmission of the at least one pair data to the cloud account in which the pair data is stored and the cloud account in which the type of the user and the cloud service do not coincide with each other, in consideration of the storage location of the previously stored divided data at operation S1240.

First, the service server 100 confirms at least one cloud account information provided from the user (S1210). That is, the service server 100 confirms the excluded cloud account in the service storage space as the user is excluded from the group.

The service server 100 can confirm whether or not a specific user has left the service in various ways. For example, the service server 100 manages the connection relationship between the user and the account included in the group, so that the service server 100 determines that the entire cloud account of the user is excluded if a specific user is excluded from the provided service . In another example, after the service server 100 transmits the token data for accessing the cloud account for a specific user to the specific cloud server 200, the access server 200 receives the inaccessibility result from the cloud server 200, Of cloud accounts are excluded from the storage space of the provided services. That is, the service server 100 transmits the token data for the specific cloud service to the cloud server 200 for storing or requesting the divided data, receives the token data is invalid and confirms the group exclusion of the user do.

Thereafter, the service server 100 confirms the deletion data stored in the cloud account of the user excluded from the provided service (S1220). The deletion data is deleted data from the paired partition data. For example, the service server 100 stores the identification code of each divided data and the identification code of each cloud account, stores the identification code of each divided data, and stores the storage location of each divided data (that is, If the user is excluded from the providing service, the user can confirm the divided data (i.e., deletion data) matched to the cloud account provided by the user.

 Thereafter, the service server 100 searches the pair data corresponding to the deletion data (S1230; pair data search step). The erasure data and the pair data are data in the first divided data and the second divided data. After that, the service server 100 requests to transmit the one or more pair data to the cloud account in which the pair data is stored and the cloud account in which the type of the user and the cloud service do not match S1240).

6, when the directory in which the partitioned data in the cloud account is stored is deleted by a specific user, the service server 100 deletes the pair of deleted data in the deleted partitioned data directory Search the data and re-direct the directory to the deleted cloud account to regenerate the partitioned data directory. Specifically, checking (S1250) one or more pieces of deletion data in the deleted directory; Searching for pair data corresponding to the deletion data (S1260; pair data searching step); And requesting the pair data to be transmitted to the cloud account of the user (i.e., the cloud account from which the partitioned data directory has been deleted) to perform directory regeneration (S127). The erasure data and the pair data are data in the first divided data and the second divided data.

7, the service server 100 may check the number of cloud services and the number of accounts per cloud service based on a plurality of cloud account information received from a plurality of users (S700 ); And calculating (S800) a maximum number of distributable and storable services by dividing the service internal data based on the number of cloud services and the number of accounts per cloud service. That is, the service server can determine the number of divided data to be generated by encrypting the service internal data based on the number of cloud accounts and the number of cloud services currently connected to the service server.

In addition, when receiving a request for sharing a particular service internal data (for example, a request for transmission to another user subscribed to the provided service), the service server 100 transmits service internal data in various manners. In one embodiment, the service server 100 receives the partition data for the service internal data requested to be shared, restores the service internal data with a plurality of divided data, and transmits the divided data to the client device of the other party (i.e., the second user) do.

In another embodiment, the service server 100 merges the divided data into the service internal data after receiving the divided data from the client device. Specifically, as shown in FIG. 8, a step S1300 of receiving a service internal data transmission request from a specific first user (i.e., the first user client 300) by the service server 100; Collecting a segmented data link address corresponding to the received service internal data (S1400; link address gathering step); And transmitting the integrated link to the client device of the second user (S1500; integrated link transmission step).

The service server 100 receives a service internal data transmission request from a specific user (S1300). For example, in the service internal data list displayed in the first user client 300, specific internal service data is selected from the first user.

Thereafter, the service server 100 collects a divided data link address corresponding to the received service internal data (S1400; link address gathering step). The link address may be provided to the cloud server 200 in which the divided data is stored, and the divided data may be provided. That is, the service server 100 obtains the link address of the account in which the divided data for the specific service internal data is stored.

Thereafter, the service server 100 transmits the integrated link to the second client device 400 of the second user (S1500; integrated link transmission step). The integrated link is linked with a plurality of link addresses for each divided data. The second client device 400 receives a plurality of divided data in accordance with a user's operation on the unified link, and merges the plurality of divided data to generate in-service data.

Specifically, the service server 100 provides an integrated link in which a link address for a plurality of divided data is integrated into a client of a second user, and a user client of the second user (i.e., a second user client) As the integrated link connection is performed, the storage space for each cloud account is accessed through each link address included in the integrated link, and each divided data is received. Thereafter, the second user client merges the plurality of divided data received through each link address internally to restore the service internal data.

As described above, the service internal data storing method using the cloud account according to an embodiment of the present invention may be implemented as a program (or application) to be executed in combination with a hardware computer and stored in the medium.

The above-described program may be stored in a computer-readable medium such as C, C ++, JAVA, machine language, or the like that can be read by the processor (CPU) of the computer through the device interface of the computer, And may include a code encoded in a computer language of the computer. Such code may include a functional code related to a function or the like that defines necessary functions for executing the above methods, and includes a control code related to an execution procedure necessary for the processor of the computer to execute the functions in a predetermined procedure can do. Further, such code may further include memory reference related code as to whether the additional information or media needed to cause the processor of the computer to execute the functions should be referred to at any location (address) of the internal or external memory of the computer have. Also, when the processor of the computer needs to communicate with any other computer or server that is remote to execute the functions, the code may be communicated to any other computer or server remotely using the communication module of the computer A communication-related code for determining whether to communicate, what information or media should be transmitted or received during communication, and the like.

The medium to be stored is not a medium for storing data for a short time such as a register, a cache, a memory, etc., but means a medium that semi-permanently stores data and is capable of being read by a device. Specifically, examples of the medium to be stored include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, but are not limited thereto. That is, the program may be stored in various recording media on various servers to which the computer can access, or on various recording media on the user's computer. In addition, the medium may be distributed to a network-connected computer system so that computer-readable codes may be stored in a distributed manner.

According to the present invention as described above, the following various effects are obtained.

First, the present invention provides an effect that the capacity of the service server is not greatly expanded even if the number of service users increases and data stored in the service increases. That is, the present invention provides the effect that individual cloud storage provided by a plurality of cloud services of a user can be connected to a specific service as one large cloud storage for use.

Second, users who use the service to which the present invention is applied can expand the cloud account by adding a cloud account as needed. In addition, users can obtain the effect of not having to pay for using the server capacity of the service to be used.

Third, since the internal data of the service is divided and stored in a plurality of cloud storages, it is possible to prevent leakage of internal data of the service, thereby enhancing security. In other words, since the entire data constituting the service internal data is not stored in the specific server, it is possible to prevent the in-service data from being leaked as soon as a specific server is hacked. Also, unlike other services that directly provide cloud storage, services using embodiments of the present invention do not directly store cloud storage in the service server even if the service server is hacked, so that the hacker can not access the user's data It is effective.

Fourth, in the case where the specific cloud service used by the user is terminated or the service of the corresponding cloud service can not be used due to a service failure corresponding to the service, the service using the embodiments of the present invention does not need to transfer the data directly to another cloud storage , And the data is transferred to another story space connected to the service, and the user is provided with convenience by auto-migration. That is, when adding an account to a service using the embodiments of the present invention, the user does not need to consider whether the cloud service of the account can be continuously operated and used for storing the service internal data.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. Therefore, it should be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

100: service server (100) 200: cloud server (200)
300: first user client 400: second user client

Claims (10)

Requesting the service server to perform login by receiving cloud account information held by each user from a plurality of users included in one group and transmitting the received cloud account information to the cloud server;
The service server receives and stores the token data corresponding to the cloud account information held by each user from the cloud server, and the token data is permitted to access the storage space of the cloud account corresponding to the token data Token data receiving step;
Wherein the service server stores a plurality of divided data generated by dividing service internal data uploaded in a group space on-line into a storage space of each cloud account held by the plurality of users included in the one group based on the token data And a service internal data storing step of distributing and storing the service internal data,
Wherein the group space is a space in which storage spaces of respective cloud accounts held by the plurality of users included in the one group are combined,
Wherein the service internal data is group data shared by the plurality of users included in the one group. The method according to claim 1,
The service internal data storage step includes:
Characterized in that a plurality of divided data is generated by performing secondary encryption by dividing the service internal data into a plurality of detailed data and performing primary encryption and compressing each of the detailed data by a specific compression method, A method for storing service internal data using. The method according to claim 1,
The service internal data storage step includes:
Generating the first service internal data and the second service internal data by duplicating the service internal data;
Generating the same first division data and a plurality of second division data by applying the same division method to the first service internal data and the second service internal data; And
And distributing and storing the same data in the plurality of first divided data and the plurality of second divided data so that the types of users do not overlap with the types of cloud services. The method of claim 3,
If a particular user is excluded from the group,
Identifying at least one cloud account information provided from the user;
Checking deletion data stored in the cloud account of the user;
A pair data search step of searching for pair data corresponding to the deletion data, wherein the deletion data and the pair data are identical data in the first partition data and the second partition data; And
And requesting transmission of the at least one pair data to the cloud account in which the pair data is stored and the cloud account in which the type of the user and the cloud service do not match in consideration of the storage location of the previously stored divided data. Service internal data storage method. 5. The method of claim 4,
The method comprising: transmitting to a cloud server a token data for a specific cloud service for storing or requesting division data; and receiving a notification that the token data is invalid to confirm the group exclusion of the user. How to store data. The method of claim 3,
When the directory in which the partitioned data in the cloud account is stored by a specific user is deleted,
Identifying divided data corresponding to at least one erasure data;
A pair data search step of searching for pair data corresponding to the deletion data, wherein the deletion data and the pair data are identical data in the first partition data and the second partition data; And
And requesting the pair data to be transmitted to the user's cloud account to perform directory regeneration. The method according to claim 1,
The token data,
Wherein the service data is set to be accessible only to a specific directory in which the partition data generated by the service server is stored. The method according to claim 1,
Checking a number of cloud services and an account number per cloud service based on a plurality of cloud account information received from a plurality of users; And
And dividing the service internal data and calculating a maximum number that can be distributed and stored based on the number of cloud services and the number of accounts per cloud service. The method according to claim 1,
Receiving a service internal data transmission request from a specific user;
A link address collecting step of collecting a divided data link address corresponding to the received service internal data, wherein the link address is connected to a cloud server storing each divided data to receive divided data; And
Further comprising transmitting an aggregate link to the client device of the user, wherein the aggregate link is linked to a plurality of link addresses for each partitioned data,
The client device comprising:
In accordance with an operation of the user with respect to the integrated link,
Wherein the service internal data is generated by merging the plurality of divided data. 9. A service internal data store program using a cloud account stored in a medium for executing the method of any one of claims 1 to 9 in combination with a computer which is hardware.

Images