KR102312336B1 - Method for sharing data and apparatus thereof - Google Patents

Abstract

1 Using a storage unit that stores access right information for the first cloud storage to which the user is subscribed and access right information for the second cloud storage to which the second user is subscribed, the stored access right information for the first cloud storage, The first received from the first cloud storage in response to the request by using the communication unit for requesting the first user's data stored in the first cloud storage from the first cloud storage, and the stored second cloud storage access right information A relay server according to an embodiment including a control unit for controlling a communication unit to transmit user data to a second cloud storage is disclosed.

Description

Data sharing method and device therefor

The present invention relates to a method for sharing data or transmitting a message between a plurality of users, and an apparatus therefor.

As network technology develops, data stored in desktops, laptops, and portable devices is stored in servers on the Internet, and users can download data from the server anytime, anywhere using their account whenever necessary. In addition, the user may share his/her data stored in the server with other users. In addition, by using the messenger service, it is possible to send and receive messages with others anytime, anywhere.

However, when users share data with others, there are restrictions such as having to have an account of the same storage provider as the other person. In addition, users can utilize data only within the service provided by the storage operator in which their data is stored. In addition, even when chatting with others, users must have the same messenger operator's account as the other person.

As such, there is a problem in that users cannot use the service when the service provider they use is different from the service provider used by others.

Various embodiments of the present invention are provided for sharing data or transmitting messages between users using different cloud servers by using a relay server.

As a technical means for achieving the above-described technical problem, a first aspect of the present disclosure provides access right information for a first cloud storage to which one user is subscribed and access right information for a second cloud storage to which a second user is subscribed. A storage unit that stores the information, a communication unit that requests the first user's data stored in the first cloud storage from the first cloud storage using the access right information for the stored first cloud storage, and the stored second cloud storage It is possible to provide a relay server including a control unit for controlling the communication unit to transmit data of the first user received from the first cloud storage to the second cloud storage in response to a request by using the access right information.

In addition, the access right information for the first cloud storage includes an account of the relay server registered in the first cloud storage, and corresponding to the account of the relay server registered in the first cloud storage, the first user's data 1 A set value indicating a right to receive from the cloud storage may be set in the first cloud storage.

In addition, the setting value indicating the right to receive from the first cloud storage set in the first cloud storage is a request from the first user's device to share the data of the first user stored in the first cloud storage with the relay server. Upon reception, the first cloud storage may be configured.

In addition, the access right information for the second cloud storage includes the account of the relay server registered in the second cloud storage, and corresponds to the account of the relay server registered in the second cloud storage, in the storage space of the second user. A setting value indicating the right to store data may be set in the second cloud storage.

In addition, the setting value indicating the right to store data in the storage space of the second user set in the second cloud storage is determined by receiving a request to share the storage space of the second user with the relay server from the device of the second user. The second cloud storage may be configured.

In addition, the communication unit receives a synchronization request indicating that the data of the first user has been changed from the first cloud storage, and the control unit, in response to receiving the synchronization request, changes a copy of the data of the first user stored in the second cloud storage. The first user's data is updated, and the copy of the first user's data may be data copied from the first user's data in the first cloud storage to the second cloud storage by the relay server.

In addition, the data of the first user includes a file, the synchronization request includes location information indicating the location of the changed data in the file, and the control unit, as the synchronization request is received, based on the location information, the changed data It is determined whether the data is in the write-protected setting area, and if the changed data is not the data of the write-protected setting area, the copy of the first user's data stored in the second cloud storage is updated with the changed first user's data, and write The prohibition setting area may be an area in the copy of the first user's data set not to be changed by the relay server.

In addition, the communication unit receives, from the second cloud storage, a synchronization request indicating that the copy of the first user's data stored in the second cloud storage has been changed, and the control unit, in response to receiving the synchronization request, the first stored in the first cloud storage update the data of the 1st user with a copy of the changed data of the first user, and the copy of the data of the first user is the data in which the data of the first user in the first cloud storage is copied to the second cloud storage by the relay server can

In addition, the synchronization request includes location information indicating the location of the changed data in the copy of the file of the first user, and the control unit receives the synchronization request, based on the location information, the changed data is stored in the write-protection setting area. It is determined whether the data is data, and if the changed data is not the data of the write-protected setting area, the first user's data stored in the first cloud storage is updated with a copy of the changed first user's data, and the write-protected setting area is relayed It may be an area in the file of the first user set not to be changed by the server.

In addition, the communication unit receives, from the first device of the first user, a read prohibition request for a portion of the file among the data of the first user, and the control unit receives the read prohibition request from the first cloud storage, may be obtained, a portion of the received file for which read prohibition is requested may be deleted, and the partially deleted file may be stored in the second cloud storage.

In addition, a second aspect of the present disclosure, in a method for the relay server to share data between a plurality of devices, access right information for the first cloud storage to which the first user is subscribed and the second to which the second user is subscribed Storing access right information on the cloud storage, requesting the first user's data stored in the first cloud storage from the first cloud storage using the access right information on the first cloud storage, and the second cloud storage It is possible to provide a data relay method including transmitting the first user's data received from the first cloud storage to the second cloud storage in response to the request by using the access right information for the .

In addition, the access right information for the first cloud storage includes an account of the relay server registered in the first cloud storage, and corresponding to the account of the relay server registered in the first cloud storage, the first user's data 1 A set value indicating a right to receive from the cloud storage may be set in the first cloud storage.

In addition, the setting value indicating the right to receive from the first cloud storage set in the first cloud storage is a request from the first user's device to share the data of the first user stored in the first cloud storage with the relay server. Upon reception, the first cloud storage may be configured.

In addition, the access right information for the second cloud storage includes the account of the relay server registered in the second cloud storage, and corresponds to the account of the relay server registered in the second cloud storage, in the storage space of the second user. A setting value indicating the right to store data may be set in the second cloud storage.

In addition, the setting value indicating the right to store data in the storage space of the second user set in the second cloud storage is determined by receiving a request to share the storage space of the second user with the relay server from the device of the second user. The second cloud storage may be configured.

In addition, the data relay method includes receiving a synchronization request indicating that data of the first user has changed from the first cloud storage, and upon receiving the synchronization request, a copy of the data of the first user stored in the second cloud storage The method may further include updating the data of the first user that has been changed, and the copy of the data of the first user may be data in which the data of the first user in the first cloud storage is copied to the second cloud storage by the relay server. .

In addition, the first user's data includes a file, the synchronization request includes location information indicating a location for the changed data in the file, and a copy of the first user's data stored in the second cloud storage of the changed first user The updating with data includes, upon receiving a synchronization request, determining whether the changed data is data of the write-protection setting area based on the location information, and when the changed data is not the data of the write-protection setting area, updating the copy of the first user's data stored in the second cloud storage with the changed data of the first user, wherein the write-protection setting area is an area within the copy of the first user's data set not to be changed by the relay server can be

In addition, the data relay method includes: receiving a synchronization request indicating that a copy of the first user's data stored in the second cloud storage has been changed from the second cloud storage, and upon receiving the synchronization request, stored in the first cloud storage The method further includes updating the data of the first user with a copy of the changed data of the first user, wherein the copy of the data of the first user is configured such that the data of the first user in the first cloud storage is transferred to the second cloud by the relay server. It may be data copied to storage.

Further, the first user's data includes a file, the synchronization request includes location information indicating a location for the changed data in a copy of the first user's file, and the first user's data stored in the first cloud storage includes the changed data. The step of updating to a copy of the first user's data includes, upon receiving the synchronization request, determining whether the changed data is data of the write-protection setting area, based on the location information, and the changed data is the data of the write-protection setting area and updating the first user's data stored in the first cloud storage to a copy of the changed first user's data if it is not the data of the first user, wherein the write-protection setting area is set not to be changed by the relay server. It can be an area within the file of .

In addition, the data relay method includes receiving, from a first device of a first user, a read prohibition request for a portion of the file among the data of the first user, and upon receiving the read prohibition request, the file from the first cloud storage The method may further include the steps of obtaining, deleting a portion of the received files for which read prohibition is requested, and storing the partially deleted file in the second cloud storage.

In addition, the third aspect of the present disclosure is a storage unit that stores the authorization information of the first user on the first messenger server and the authorization information of the second user on the second messenger server, using the stored authorization information of the first user Thus, the communication unit for receiving the message of the first user from the first messenger server, and the communication unit to transmit the message of the first user received from the first messenger server to the second messenger server using the stored authority information of the second user It is possible to provide a relay server including a control unit for controlling the.

In addition, the authority information of the first user with respect to the first messenger server is information about the authority to register a third user subscribed to the first messenger server to the first messenger server as a messenger friend of the first user, The second user's authority information for the second messenger server may be information about the authority to register the fourth user who is subscribed to the second messenger server to the second messenger server as the second user's messenger friend.

In addition, the communication unit receives a registration request for registering the second user as a first messenger friend of the first user from the device of the first user, and the control unit receives the registration request, the first messenger of the second user Generate a virtual ID, register the generated first messenger virtual ID of the second user to the first messenger server, and based on the authorization information of the first user for the first messenger server, the first messenger virtual of the second user register the ID as the ID of the messenger friend of the first user in the first messenger server, and the communication unit, in response to the registration request, sets the first messenger virtual ID of the second user as the ID of the second user in the first messenger 1 Can be transmitted to the user's device.

In addition, the communication unit receives a registration request for registering the first user as a second messenger friend of the second user from the device of the second user, and the control unit receives the registration request, the second messenger of the first user Create a virtual ID, register the generated second messenger virtual ID of the first user to the second messenger server, and based on the authority information of the second user for the second messenger server, the second messenger virtual of the first user register the ID as the ID of the second user's messenger friend in the second messenger server, and the communication unit, in response to the registration request, sets the second messenger virtual ID of the first user as the ID of the first user in the second messenger 2 It can be transmitted to the user's device.

In addition, the communication unit, using the stored authorization information of the first user, registers the first messenger virtual ID of the second user in the first messenger server, using the registered first messenger virtual ID of the second user, Receives the message of the first user for the second user from the first messenger server, and the control unit registers the second messenger virtual ID of the first user to the second messenger server by using the stored authority information of the second user, The communication unit may be controlled to transmit the first user's message received from the first messenger server to the second messenger server by using the registered second messenger virtual ID of the first user.

In addition, the communication unit receives, from the device of the first user, a message transmission request for transmitting a message to the second user using the first messenger virtual ID of the second user as the ID of the recipient, and in response to the message transmission request, With the second messenger virtual ID of the first user as the sender's ID, the second messenger server may be requested to transmit the message to the second user.

1 is a diagram illustrating a method for a relay server to share data of different users stored in different cloud storages, according to an embodiment of the present invention.
2 illustrates an embodiment of a first device, a second device, a relay server, a first cloud storage, and a second cloud storage according to an embodiment of the present invention.
3 and 4 illustrate a method in which data of a first user stored in a first cloud storage through a relay server is stored in a second cloud storage as data of a second user according to an embodiment of the present invention is a drawing for
5 illustrates a method for a relay server to share data of a first user stored in a first cloud storage between a first user and a second user registered in different cloud storages, according to an embodiment of the present invention; is a flow chart that
6 is a diagram for explaining a method of registering a first user and a second user by a first cloud storage, a second cloud storage, and a relay server according to an embodiment of the present invention.
7 is a diagram for explaining a method of receiving, by a first device, an input of a first user for selecting data to be shared with a second user, according to an embodiment of the present invention.
8 is a diagram for describing a method in which a first user selects data to be shared with a second user in a first device, according to another embodiment of the present invention.
9 is a diagram for explaining a method for a first user to select data to be shared with a second user in a first device, according to another embodiment of the present invention.
10 is a diagram illustrating a method for a first device to set an access right to a relay server with respect to data selected by a first user among data of a first user stored in a first cloud storage according to an embodiment of the present invention; It is a flow chart.
11 is a diagram for describing a method for a first device to receive a first user input for setting a second user to share data of the first user, according to an embodiment of the present invention.
12 is a diagram for describing a method for a first device to receive a first user input for setting a second user to share data of the first user, according to another embodiment of the present invention.
13 is a diagram for describing a method for a first device to receive a first user input for setting a second user to share data of the first user, according to another embodiment of the present invention.
14 is a diagram in which a first device transmits data of a selected first user to a second user in response to receiving a first user's input for selecting a first user's data and a second user's data to be shared, according to an embodiment of the present invention; This is a flowchart to explain how to request a relay server to share with
15 is a diagram for explaining a database about a data provider stored in a relay server when a sharing setting between a first user and a second user for data of the first user is requested, according to an embodiment of the present invention; am.
FIG. 16 is a diagram for explaining a database related to data stored in a relay server in response to a request for sharing setting between a first user and a second user for the data of the first user, according to an embodiment of the present invention .
FIG. 17 is a diagram showing, according to an embodiment of the present invention, as sharing of the first user and the second user is set with respect to the data of the first user, the relay server stores the data of the first user set to be shared in the first cloud storage; FIG. Shows a flow chart explaining how to receive from
18 is a diagram for describing a database for a list of files or folders of a first user received from a first cloud storage according to an embodiment of the present invention.
19 is a diagram for explaining a method of granting, by a second device, an authority to store data in a storage space of a second user in a second cloud storage to a relay server, according to an embodiment of the present invention.
20 is a flowchart illustrating a method of granting, by a second device, an authority to store data in a storage space of a second user in a second cloud storage to a relay server according to an embodiment of the present invention .
21 is a diagram for describing a database stored in the relay server as the relay server receives location information indicating the location of the storage space of the second user in the second cloud storage, according to an embodiment of the present invention.
22 is a diagram illustrating a relay server to a second device when receiving a sharing request for sharing data of a first user with a second user from the first device, according to an embodiment of the present invention; It is a diagram for explaining a method of notifying a request to share the data of the first user with the second user.
23 is a diagram for explaining a method for a relay server to store a list of data of a first user received from a first cloud storage in a storage space of a second user in a second cloud storage, according to an embodiment of the present invention; It is a flow chart.
24A is a diagram illustrating a second device transferring data of a first user to a second cloud as it receives from a relay server that data of a first user is set to be shared between a first user and a second user, according to an embodiment of the present invention; It is a diagram illustrating a method of displaying a user interface for receiving a second user's selection of whether to store in storage.
24B is a flowchart illustrating a method for a relay server to store data of a first user in a second cloud storage based on a selection of a second user received from a second device, according to an embodiment of the present invention; .
25 is a diagram in which the second device receives and displays the data of the first user stored in the second cloud storage according to the sharing setting between the first user and the second user, according to an embodiment of the present invention; It is a drawing for explaining the method.
26 is a diagram in which a second device receives and displays data of a first user stored in a second cloud storage according to a sharing setting between the first user and the second user, from the second cloud storage, according to an embodiment of the present invention; It is a drawing for explaining the method.
27 is, according to another embodiment of the present invention, the first user's data stored in the second cloud storage as shared between the first user and the second user is set, and the second device receives and displays the data from the second cloud storage; It is a drawing for explaining how to do it.
28 is a flowchart illustrating a method for a second device to receive a list of data of a first user from a second cloud storage, according to an embodiment of the present invention.
29 is a diagram illustrating a second device in response to receiving an input of a second user for selecting one of a list of files of a first user shared between a first user and a second user, according to an embodiment of the present invention; It is a diagram for explaining a method of acquiring the contents of a user's file.
30 is a diagram in which, according to an embodiment of the present invention, in a state where only a list of the first user's data shared by the first user and the second user is stored in the second device, the second device transmits the data of the first user It is a flowchart to explain how to obtain it.
31 is a diagram for describing a method in which a second device sets a folder of a second user in a second cloud storage as a receiving folder in a relay server according to another embodiment of the present invention.
FIG. 32 is a diagram showing a file or folder of the first user shared between the first user and the second user is displayed on the second device as the receiving folder of the second user is set in the relay server according to an embodiment of the present invention; It is a drawing for explaining how to become.
33 is a flowchart illustrating a method for a second device to set a folder of a second user in a second cloud storage as a receiving folder in a relay server according to another embodiment of the present invention.
34 is a diagram for describing a method for a second device to receive, from a second user, an input for designating a provider, according to an embodiment of the present invention.
35 is a flowchart illustrating a method for a relay server to receive a provider setting request from a second device, according to an embodiment of the present invention.
36 illustrates a database about a second user stored in a relay server as a first user is set as a provider of a second user, according to an embodiment of the present invention.
37 is a diagram in which, according to an embodiment of the present invention, as the first user is set in the relay server as the provider of the second user, the relay server transmits the data of the first user set shared between the first user and the second user to the second user; It is a flowchart for explaining a method of saving to cloud storage.
38 is a diagram illustrating that, as data of a first user shared between a first user and a second user is stored in the second cloud storage without a request from the second user, the second cloud storage is configured according to an embodiment of the present invention; , to the second device, is a flowchart for explaining a method of transmitting the data of the first user copied from the first cloud storage.
39 is a second device as the data of the first user set to be shared between the first user and the second user is stored in the second cloud storage without the request of the second user according to another embodiment of the present invention; It is a flowchart for explaining a method of receiving the data of the first user stored in the second cloud storage.
40 is a diagram illustrating a first user stored in a relay server as data of a first user is stored in a storage space of a second user in a second cloud storage according to a sharing request of the first user, according to an embodiment of the present invention; A database of data from
41 is a diagram for explaining synchronization between a first device and a second device for data shared between a first user and a second user, according to an embodiment of the present invention.
42A is a diagram illustrating a user interface for setting synchronization provided by a first device according to an embodiment of the present invention.
42B is a diagram illustrating a user interface for setting synchronization provided by a first device or a second device according to another embodiment of the present invention.
43 illustrates a database for data of a first user stored in a relay server as information on a synchronization method is set according to another embodiment of the present invention.
44A is a diagram in which a copy of the first user's data stored in the first cloud storage and the first user's data stored in the second cloud storage is synchronized according to the request of the first user, according to an embodiment of the present invention; It is a flowchart to explain the method.
44B is a flowchart illustrating a method for a second device to set write-protection on data shared between a first user and a second user, according to an embodiment of the present invention.
45A is a diagram in which a copy of the first user's data stored in the first cloud storage and the first user's data stored in the second cloud storage is synchronized according to the request of the second user, according to an embodiment of the present invention; It is a flowchart to explain the method.
45B is a flowchart for explaining a method for a first device to set write-protection on data shared between a first user and a second user, according to an embodiment of the present invention.
46 illustrates a user interface for limiting functions for data to be shared, according to an embodiment of the present invention.
47 is a flowchart illustrating a method for a relay server to restrict use of shared data according to an embodiment of the present invention.
48 is a diagram illustrating a user interface for setting read prohibition on a part of data to be shared, according to an embodiment of the present invention.
49 is a flowchart illustrating a method of sharing data by setting read prohibition on a portion of data to be shared, according to an embodiment of the present invention.
50A and 50B are diagrams for explaining a method for a relay server to delete a read-prohibited portion.
FIG. 51 is a flowchart illustrating a method of releasing the read prohibition of data of a first user provided to a second user with a portion of which is read-protected, according to an embodiment of the present invention.
52 is a diagram illustrating data of a first user in a relay server or data of a second user in a second cloud storage when a relay server provides a cloud storage function according to an embodiment of the present invention to a first user and a second user; It is a diagram for explaining a method of sharing between each other.
53 is a diagram for explaining a method in which the relay server shares the data of the first user between the first user and the second user when the relay server provides a cloud storage function, according to an embodiment of the present invention.
54 is a diagram for describing a method in which a relay server and a second cloud storage register a first user and a second user, according to an embodiment of the present invention.
55 is a flowchart illustrating a method for a second device to register a second user's folder in a second cloud storage as a receiving folder in a relay server according to an embodiment of the present invention.
56 is a diagram illustrating a relay server transferring data of a first user in a relay server to a second in response to receiving a sharing request for sharing the data of the first user with the second user from the first device, according to an embodiment of the present invention; It is a flowchart for explaining a method of saving to a user's storage space.
57 is a diagram illustrating that, upon receiving a sharing request for sharing data of a second user in a second cloud storage between a first user and a second user from a second device, the relay server is configured to operate in the second cloud according to an embodiment of the present invention; It shows a flowchart for explaining a method of storing the data of the second user in the storage to the relay server.
58 is a diagram in which the first relay server and the second relay server convert the first user's data stored in the first cloud storage or the second user's data in the second cloud storage to the first user, according to an embodiment of the present invention; and a diagram for explaining a method of sharing between second users.
59 is a diagram illustrating a method in which a first relay server and a second relay server store data of a first user stored in a first cloud storage between a first user and a second user, according to an embodiment of the present invention is a drawing for
60 is a diagram for describing a method in which a first cloud storage and a second cloud storage register a first user and a second user, according to an embodiment of the present invention.
61 illustrates a method for the first relay server to set up sharing between the first user and the second user with respect to at least one data among the data of the first user stored in the first cloud storage, according to an embodiment of the present invention; This is a flow chart for
62 illustrates a user interface for explaining a method for a first user to transmit location information indicating a location of a file shared between a first user and a second user to a second user, according to an embodiment of the present invention; .
63 is a flowchart illustrating a method for the first relay server to transmit location information indicating the location of a file shared between a first user and a second user to a second relay server according to an embodiment of the present invention; do.
64 illustrates a user interface for the second relay server to receive the first user's data from the first cloud storage and store it in the second cloud storage, according to an embodiment of the present invention.
65 is a flowchart illustrating a method for the second relay server to receive the first user's data from the first cloud storage and store it in the second cloud storage, according to an embodiment of the present invention.
66 is a diagram illustrating a relay server that relays message transmission between users using different messenger services when the cloud server is a messenger server according to an embodiment of the present invention.
67A is a flowchart illustrating a method for a device and a relay server to register an account with a messenger server and a method for a device to register an account with a relay server, according to an embodiment of the present invention.
67B illustrates a database in which information about a user subscribed to a relay server is stored, according to an embodiment of the present invention.
68A is a flowchart illustrating a method in which the relay server acquires the authority of the first user to the first messenger server according to an embodiment of the present invention.
68B is a diagram illustrating a user interface for granting a first user's authority to a first messenger server to a relay server according to an embodiment of the present invention.
68C illustrates a database stored by a relay server upon receiving authorization information from a device, according to an embodiment of the present invention.
69A is a diagram illustrating a method in which a relay server registers a first user and a second user as mutual relay server friends, according to an embodiment of the present invention.
69B is a diagram illustrating a method in which a first device receives a first user input for setting a second user as a relay server friend with which to communicate through a relay server, according to an embodiment of the present invention.
69c is a diagram illustrating a method for a second device to receive a second user input allowing setting of a relay server friend between a first user and a second user from a second user, according to an embodiment of the present invention.
69D illustrates a database stored by a relay server when a relay server friend is established between users according to an embodiment of the present invention.
70A is a diagram illustrating a relay server registering a relay server as a second user in a first messenger server, and setting the relay server as a first messenger friend of the first user based on authority information of the first user, according to an embodiment of the present invention; This is a flow chart showing a method of registering with the first messenger server.
70B is a diagram illustrating a relay server registering a relay server as a first user in a second messenger server, and setting the relay server as a second messenger friend of a second user based on the authority information of the second user, according to an embodiment of the present invention; This is a flowchart showing a method of registering with the second messenger server.
70C is a diagram illustrating a database created in the relay server when the relay server registers virtual account information for a user in the messenger server, according to an embodiment of the present invention.
70D is a diagram for describing a method in which a first device indicates that a user having a first messenger virtual ID of a second user has been added as a first messenger friend of the first user, according to an embodiment of the present invention.
71A is a flowchart for describing a method in which a first device indicates that a second user has been added by using a contact list stored in the first device, according to an embodiment of the present invention.
71B to 71C are diagrams for explaining a method in which a first device indicates that a second user has been added by using a contact list stored in the first device, according to an embodiment of the present invention.
72A is a flowchart illustrating a method for a relay server to relay message transmission/reception between a first user and a second user based on the virtual account information of the first user and the virtual account information of the second user, according to an embodiment of the present invention; am.
72B is a diagram illustrating messages transmitted/received between the first user and the second user by the first device and the second device as the relay server relays the message transmission/reception between the first user and the second user, according to an embodiment of the present invention; It is a drawing for explaining how to do it.
73 is a diagram illustrating a relay server that relays message transmission between a user using a messenger function provided by the relay server and a user using another messenger service when the relay server performs a messenger function according to an embodiment of the present invention; It is a drawing.
74 is a flowchart illustrating a method in which a first device and a second device register an account in a relay server and a method in which a second device registers an account in a second messenger server, according to an embodiment of the present invention.
75 is a flowchart illustrating a method in which a relay server acquires a second user's authority to a second messenger server according to an embodiment of the present invention.
76A is a diagram illustrating a method of receiving, by a first device, a first user input for setting a second user as a first messenger friend to be chatted with through a relay server, according to an embodiment of the present invention.
76B is a diagram illustrating a database stored in a relay server according to an embodiment of the present invention.
77A is a diagram illustrating the relay server to the first device that the second user is the first messenger friend of the first user as the second user is registered with the relay server as the first messenger friend of the first user, according to an embodiment of the present invention; It is a flow chart showing a method of notifying that registration has been performed.
77B is a diagram illustrating a database in which a relay server stores virtual account information of users, according to an embodiment of the present invention.
78 is a flowchart illustrating a method for a relay server to transmit a message of a first user received from a first device to a second user, according to an embodiment of the present invention.
79 is a flowchart illustrating a method for a relay server to transmit a message of a second user received from a second device to a first user, according to an embodiment of the present invention.
80 is a diagram illustrating a method in which the relay server relays message transmission between users using different messenger services when the relay server performs a device function according to an embodiment of the present invention.
81 is a flowchart illustrating a method of registering a first relay server with a first messenger server and a second relay server with a second messenger server according to an embodiment of the present invention.
82A is a flowchart illustrating a method in which the first relay server acquires, from the first messenger server, the right to add another user as the first messenger friend of the first user, according to an embodiment of the present invention.
82B is a flowchart illustrating a method for the second relay server to obtain, from the second messenger server, an authority to add another user as a second messenger friend of the second user, according to an embodiment of the present invention.
83A is a diagram in which the first relay server registers the first relay server with the first messenger server and sets the first relay server to the first user's first user's first relay server based on the authority information of the first user, according to an embodiment of the present invention; It is a flowchart showing a method of registering with the first messenger server as a messenger friend.
83B is a diagram illustrating that the second relay server registers the second relay server with the second messenger server, and sets the second relay server as a messenger friend of the second user, based on the authority information of the second user, according to an embodiment of the present invention; This is a flowchart showing a method of registering with the second messenger server.
84A to 84C are diagrams illustrating a method for a first relay server to transmit a first messenger virtual ID of a second user to a second relay server according to an embodiment of the present invention.
85A is a diagram illustrating a database stored by the first relay server according to an embodiment of the present invention.
85B is a diagram illustrating a database stored by a second relay server according to an embodiment of the present invention.
86 is a flowchart illustrating a method of relaying a message transmitted from a first user to a second user by a first relay server and a second relay server according to an embodiment of the present invention.
87 is a block diagram of a relay server according to an embodiment of the present invention.
88 shows a block diagram of a first device, according to an embodiment of the present invention.
89 is a block diagram illustrating a configuration of a first device according to another embodiment of the present disclosure.

Terms used in this specification will be briefly described, and the present invention will be described in detail.

The terms used in the present invention have been selected as currently widely used general terms as possible while considering the functions in the present invention, but these may vary depending on the intention or precedent of a person skilled in the art, the emergence of new technology, and the like. In addition, in a specific case, there is a term arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description of the corresponding invention. Therefore, the term used in the present invention should be defined based on the meaning of the term and the overall content of the present invention, rather than the name of a simple term.

When a part "includes" a certain element throughout the specification, this means that other elements may be further included, rather than excluding other elements, unless otherwise stated. In addition, terms such as "...unit" and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented as hardware or software, or a combination of hardware and software. .

Throughout the specification, “cloud storage” may refer to a data storage device in which digital data is stored. In addition, the cloud storage may consist of one storage device or a plurality of storage devices.

In addition, the cloud storage may be operated by a service provider that provides a data storage service to users. For example, a service provider may provide storage space in cloud storage for a fee or free of charge to users who subscribe to a service. In addition, the cloud storage may transmit user data to the user's device through a network or receive user's data from the user's device. In addition, cloud storage may have a file system to provide file-level data access to users.

As the user subscribes to the service provided by the service provider, the user may register their own account in the cloud storage. The cloud storage may store the user's data based on the user's account registered in the cloud storage. In addition, the cloud storage may delete or change the stored user's data based on the user's account.

In addition, the cloud storage may restrict other users' access to the user's data according to the user's data access policy set by the user. For example, the cloud storage may allow access to the user's data only to the user the user has allowed access to. In addition, the cloud storage may grant access to the user's data to all users according to the user's settings.

Also, the cloud storage may be referred to as public cloud storage according to embodiments.

Throughout the specification, a storage space may refer to a logical storage space in cloud storage. For example, a storage space may include a folder, which is a file system structure in which files are stored.

Throughout the specification, location information indicating a location of data may mean a logical location of data. For example, location information indicating the location of data may include a file path and a Uniform Resource Identifier (URI).

Throughout the specification, location information indicating a location of a storage space may mean a logical location of a storage space. For example, the location information indicating the location of the storage space may include a folder path or URI.

According to an embodiment, the location information may be referred to as link information.

Throughout the specification, “messenger server” may mean a delivery device that delivers a message.

Also, the messenger server may be operated by a service provider that provides a message transmission service to users. For example, a service provider may provide a message transmission service for a fee or for free to users who have subscribed to the service.

As the user subscribes to the service provided by the service provider, the user may register the user's own account in the messenger server. The messenger server may transmit the user's message based on the user's account registered in the messenger server.

Throughout the specification, “messenger friend” may refer to a user who can communicate using a messenger service. For example, the first messenger friend of the first user may mean a user with whom the first user can communicate using the first messenger service.

Throughout the specification, "user's unique information" may mean user's unique information that can distinguish a user from other users. For example, the user's unique information may include, but is not limited to, a phone number, an email address, and a social security number.

Throughout the specification, the first device may refer to a device used by the first user. The first device may be one device or a plurality of devices. Also, the first cloud storage may be a cloud storage to which the first user is subscribed. Accordingly, the first device may store data in the first cloud storage based on the account of the first user. Also, the second device may refer to a device used by the second user. The second device may be one device or a plurality of devices. Also, the second cloud storage may be cloud storage to which the second user is subscribed. Accordingly, the second device may store data in the second cloud storage based on the account of the second user.

Depending on the embodiment, the cloud storage or messenger server may be referred to as a cloud server.

In addition, the relay server may relay data of users registered in each of the plurality of cloud storages or relay messages of users registered in each of the plurality of messenger servers, but for convenience of explanation, An embodiment for relaying users' data or relaying messages of users registered in each of two messenger servers is disclosed.

In addition, although the relay server may relay data or messages of a plurality of users, an embodiment of relaying data or messages of a first user and a second user is disclosed for convenience of description.

Hereinafter, with reference to the accompanying drawings, embodiments of the present invention will be described in detail so that those of ordinary skill in the art can easily carry out the embodiments of the present invention. However, the present invention may be embodied in many different forms and is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

FIG. 1 is a diagram for explaining a method for a relay server 1000 to share data of different users stored in different cloud storages, according to an embodiment of the present invention.

Referring to FIG. 1 , the relay server 1000 transmits data of a first user stored in a first cloud storage 2000 or data of a second user stored in a second cloud storage 3000 between a first user and a second user. can be shared

For example, access right information for the first cloud storage 2000 may be stored in the relay server 1000 . The relay server 1000 may request the first user's data from the first cloud storage 2000 by using the stored access right information on the first cloud storage 2000 .

The access right information for the first cloud storage 2000 may refer to information about a right to acquire the first user's data from the first cloud storage 2000 .

A set value indicating the right to obtain the first user's data from the first cloud storage 2000 corresponds to the account of the relay server 1000 registered in the first cloud storage 2000, the first cloud storage ( 2000) can be set.

As the set value indicating the right to acquire the data of the first user is set in the first cloud storage 2000 in response to the account of the relay server 1000 registered in the first cloud storage 2000, the first The cloud storage 2000 may transmit data of the first user requested from the relay server 1000 to the relay server 1000 .

Upon receiving the data of the first user from the first cloud storage 2000, the relay server 1000 transfers the data of the first user to the second cloud storage ( 3000) can be transmitted. The access right information for the second cloud storage 3000 may be stored in the relay server 1000 .

The access right information for the second cloud storage 3000 may refer to information about the right to store data in the storage space of the second user in the second cloud storage 3000 .

A setting value indicating the right to store data in the storage space of the second user in the second cloud storage 3000 corresponds to the account of the relay server 1000 registered in the second cloud storage 3000 in the second cloud It may be set in the storage 3000 .

As the setting value indicating the right to store data in the storage space of the second user is set in the second cloud storage 3000 in response to the account of the relay server 1000 registered in the second cloud storage 3000, The second cloud storage 3000 may store the data of the first user transmitted from the relay server 1000 in the storage space of the second user.

2 is an embodiment of a first device 100 , a second device 200 , a relay server 1000 , a first cloud storage 2000 , and a second cloud storage 3000 according to an embodiment of the present invention. An example is shown.

Referring to FIG. 2 , the first cloud storage 2000 and the second cloud storage 3000 may be cloud storage operated by different service providers.

The first user may set an access right to the relay server 1000 with respect to the first user's data stored in the first cloud storage 2000 . For example, the first device 100 sends a request from a first user to share the data of the first user stored in the first cloud storage 2000 with the relay server 1000 to the first cloud storage 2000 . can send As the sharing relationship between the relay server 1000 and the first user is set in the first cloud storage 2000 with respect to the first user's data, the relay server 1000 stores the first data stored in the first cloud storage 2000 in the first cloud storage 2000 . 1 It is possible to obtain access to the user's data. The right to access the data of the first user may include the right to obtain the data of the first user.

Also, the second user may set an access right to the relay server 1000 for the storage space of the second user in the second cloud storage 3000 . For example, the second device 200 may transmit to the second cloud storage 3000 a request of the second user to share the storage space of the second user in the second cloud storage 3000 with the relay server 1000 . can With respect to the storage space of the second user, as the sharing relationship between the relay server 1000 and the second user is set in the second cloud storage 3000 , the relay server 1000 may 2 You can obtain access to the user's storage space. The permission to access the storage space of the second user may include permission to store data in the storage space of the second user in the second cloud storage 3000 .

The first device 100 may request the relay server 1000 to share data of the first user stored in the first cloud storage 2000 between the first user and the second user.

In response to receiving a sharing request between the first user and the second user for the data of the first user stored in the first cloud storage 2000 , the relay server 1000 transmits the data of the first user stored in the first cloud storage 2000 Based on the access right to the data, data of the first user may be received from the first cloud storage 2000 . In addition, the relay server 1000 may store the first cloud storage ( 2000) may store the data of the first user received from it.

Also, the relay server 1000 may receive a request from the second user to share the data of the second user in the second cloud storage 3000 with the first user from the second device 200 . Upon receiving the sharing request, the relay server 1000 receives the data of the second user from the second cloud storage 3000 based on the access right to the data of the second user stored in the second cloud storage 3000 . and, based on the access right to the storage space of the first user in the first cloud storage 2000, the received data of the second user may be stored in the storage space of the first user in the first cloud storage 2000 .

In addition, the relay server 1000 may synchronize a copy of the first user's data stored in the first cloud storage 2000 and the first user's data stored in the second user's storage space in the second cloud storage 3000 . have.

Also, the relay server 1000 may prohibit writing of data shared between the first user and the second user. Also, the relay server 1000 may prohibit reading of data shared between the first user and the second user.

Also, the relay server 1000 may be implemented in various forms. For example, as shown in FIG. 2 , the relay server 1000 is distinguished from the first cloud storage 2000 , the second cloud storage 3000 , the first device 100 , and the second device 200 . It may be a separate device.

Also, the relay server 1000 may be implemented in the first cloud storage 2000 or the second cloud storage 3000 . For example, the relay server 1000 may be cloud storage that provides a storage function to users based on accounts of users registered in the relay server 1000 .

Also, the relay server 1000 may be implemented in the first device 100 or the second device 200 . For example, the relay server 1000 may be a device that uploads data in the device to the first cloud storage 2000 or receives data from the first cloud storage 2000 according to a user input.

3 and 4, the first user's data stored in the first cloud storage 2000 through the relay server 1000 according to an embodiment of the present invention is the second user's data in the second cloud storage ( 3000) is a diagram for explaining a method of storing the data.

Referring to FIG. 3 , the first cloud storage 2000 may store a file of the first user.

The first cloud storage 2000 may manage files or folders of the first user by using a file system.

Data constituting the file may include content of the file and attribute information of the file. File attribute information includes file name, file format, file location, original size of file, size of data stored among the total size of file, file creation time, file modification time, file access time, file access It may include information on permissions, access range to files, and thumbnail images. Also, the attribute information of the file may be recorded in the file in the form of metadata.

A folder can be a logical storage space containing other folders or files. The data constituting the folder may include attribute information of a subfolder or file located in the folder and location information of the subfolder or file. A folder may also be referred to as a directory or a file folder, depending on the embodiment.

According to an embodiment, the structure of the folder of the first user stored in the first cloud storage 2000 includes two top-level folders having folder names of Dropbox_user1_FOLDER1 and Dropbox_user1_FOLDER2 under the root corresponding to the first user. can be a structure. Also, the Dropbox_user1_FOLDER2 folder may include two folders with folder names of Dropbox_user1_SUB_FOLDER_1 and Dropbox_user1_SUB_FOLDER_2 and one file with a file name of Dropbox_user1_FILE1.

In addition, according to an embodiment, the folder structure of the data of the second user stored in the second cloud storage 3000 is two top-level folders having folder names of Google Drive_user2_FOLDER1 and Google Drive_user2_FOLDER2 under the root corresponding to the second user. It may be a structure in which is located. Also, the Google Drive_user2_FOLDER1 folder may include one file with a file name of Google Drive_user2_FILE1.

Referring to FIG. 4 , the first user may set sharing between the first user and the second user with respect to Dropbox_user1_FOLDER2 among the data of the first user stored in the first cloud storage 2000 in the relay server 1000 . . As sharing between the first user and the second user is set for Dropbox_user1_FOLDER2, the relay server 1000 receives the Dropbox_user1_FOLDER2 folder from the first cloud storage 2000, and stores the received Dropbox_user1_FOLDER2 folder in the second cloud storage 3000. It can be stored in the storage space of the second user.

As the first user's Dropbox_user1_FOLDER2 folder stored in the first cloud storage 2000 is copied to the second user's storage space, the second cloud storage 3000 may store the Dropbox_user1_FOLDER2 folder as the second user's data.

A location where the second user's Dropbox_user1_FOLDER2 folder is stored in the storage space of the second user may be determined according to a setting of the second user. For example, when the second user sets a location where data copied from the first cloud storage 2000 is mounted as Google Drive_user2_FOLDER1, the Dropbox_user1_FOLDER2 folder of the second user may be mounted in the Google Drive_user2_FOLDER1 folder. Also, when the second user does not set a location where data copied from the first cloud storage 2000 is mounted, the Dropbox_user1_FOLDER2 folder of the second user may be mounted under a root corresponding to the second user.

As the sharing relationship between the first user and the second user is set for the first user's Dropbox_user1_FOLDER2 folder stored in the first cloud storage 2000 , all data located in the Dropbox_user1_FOLDER2 folder will be copied to the second cloud storage 3000 . can Also, only metadata of subfolders and files in the Dropbox_user1_FOLDER2 folder may be copied to the second cloud storage 3000 . For example, only attribute information of files in the Dropbox_user1_FOLDER2 folder and subfolders and hierarchical structures of files in the Dropbox_user1_FOLDER2 folder may be copied to the second cloud storage 3000 .

As the sharing relationship between the first user and the second user is established with respect to the first user's data stored in the first cloud storage 2000 , the data of the first user stored in the first cloud storage 2000 is transferred to the second cloud A method of storing data of the second user in the storage 3000 will be described in detail below with reference to FIGS. 5 to 40 .

5 is a diagram in which the relay server 1000 transmits data of a first user stored in the first cloud storage 2000 between a first user and a second user registered in different cloud storages, according to an embodiment of the present invention. It is a flow chart explaining how to share.

In step S510 , the relay server 1000 stores access right information on the first cloud storage 2000 to which the first user is subscribed and access right information on the second cloud storage 2000 to which the second user is subscribed. can

The relay server 1000 may store access right information for the first cloud storage 2000 to which the first user is subscribed.

For example, in response to receiving an input of the first user for sharing the data of the first user stored in the first cloud storage 2000 with the second user, the first device 100 is transferred from the first cloud storage 2000 A request may be made to the first cloud storage 2000 to set the authority for acquiring the first user's data to the relay server 1000 . For example, the first device 100 may request the first cloud storage 2000 to share the data of the first user stored in the first cloud storage 2000 with the relay server 1000 .

Upon receiving a request to set the right to obtain the first user's data to the relay server 1000 , the first cloud storage 2000 is the first cloud storage of the relay server 1000 registered in the first cloud storage 2000 . A setting value indicating an authority to acquire data of the first user corresponding to the account may be set. As the set value indicating the authority to acquire the first user's data is set in the first cloud storage 2000 in response to the account of the relay server 1000 , the relay server registered in the first cloud storage 2000 The account of 1000 may mean access right information for the first cloud storage 2000 .

Also, the first device 100 may request location information indicating the location of the first user's data from the first cloud storage 2000 . Upon receiving a request for location information indicating the location of the first user's data from the first device 100 , the first cloud storage 2000 transmits location information indicating the location of the first user's data to the first device ( 100) can be transmitted. The location information indicating the location of the first user's data may include a URL of the first user's data. The first device 100 may request the relay server 1000 to store location information indicating the location of the first user's data in response to the account of the first user registered in the relay server 1000 .

Also, the relay server 1000 may store access right information for the second cloud storage 2000 to which the second user is subscribed.

For example, upon receiving an input of the second user for setting the storage space of the second user in the second cloud storage 2000 as a storage space for storing data received from the relay server 1000, the second device ( 200 may request the second cloud storage 2000 to set the right to store data in the storage space of the second user to the relay server 1000 . Upon receiving a request to set the storage space of the second user in the second cloud storage 2000 to the relay server 1000 , the second cloud storage 2000 is a relay server registered in the second cloud storage 2000 ( 1000), a setting value indicating an authority to store data in the storage space of the second user may be set. As the setting value indicating the right to store data in the storage space of the second user is set in the second cloud storage 2000 in response to the account of the relay server 1000 , the value registered in the second cloud storage 2000 is The account of the relay server 1000 may mean access right information for the second cloud storage 2000 .

Also, the second device 200 may request location information indicating the location of the storage space of the second user from the second cloud storage 2000 . Upon receiving a request for location information indicating the location of the storage space of the second user from the second device 200 , the second cloud storage 2000 transmits location information indicating the location of the storage space of the second user to the second device 200 . may be transmitted to the device 200 . The location information indicating the location of the storage space of the second user may include a URL of the storage space of the second user. The second device 200 may request the relay server 1000 to store location information indicating the location of the storage space of the second user corresponding to the account of the second user registered in the relay server 1000 .

The relay server 1000 may receive a sharing request for sharing the data of the first user stored in the first cloud storage 2000 with the second user from the first device 100 .

In step S520 , upon receiving the sharing request from the first device 100 , the relay server 1000 sends the first cloud storage 2000 to the first user using the access right information on the first cloud storage 2000 . data can be requested.

For example, the relay server 1000 may request the first user's data from the first cloud story based on the account of the relay server 1000 registered in the first cloud storage 2000 . In this case, the request for data of the first user may include location information indicating the location of the data of the first user.

When the first user's data access right is set in the first cloud storage 2000 in response to the account of the relay server 1000 , the first cloud storage 2000 is the first user requested from the relay server 1000 . of data may be transmitted to the relay server 1000 .

In step S530 , the relay server 1000 transfers the data of the first user received from the first cloud storage 2000 in response to the request to the second cloud storage by using the access right information on the second cloud storage 2000 . (2000).

For example, based on the account of the relay server 1000 registered in the second cloud storage 2000 , the relay server 1000 may store the information of the first user in the storage space of the second user in the second cloud storage 2000 . You can ask to save the data. In this case, the request to store data in the storage space of the second user may include location information indicating the location of the storage space of the second user.

When the second user's access right to the storage space is set in the second cloud storage 2000 in response to the account of the relay server 1000 , the second cloud storage 2000 is the first data received from the relay server 1000 . The user's data may be stored in the storage space of the second user.

The relay server 1000 may receive, from the first device 100 , a read prohibition request for a portion of a file among the first user's data together with a sharing request for the first user's data. Also, the relay server 1000 may receive from the first device 100 a request for limiting the use of the first user's data together with the sharing request for the first user's data. Restrictions on use of data may include restrictions on copying of data, printing of data, and alteration of data.

Also, the relay server 1000 may store the first user's data in the second user's storage space only when receiving a request for the first user's data from the second cloud storage 3000 . .

Also, when the data of the first user is a file, the relay server 1000 may store only attribute information of the file except for the content of the file in the storage space of the second user.

In addition, when the relay server 1000 receives a request for prohibiting reading of a portion of the file among the data of the first user along with the sharing request from the first device 100 , the relay server 1000 transmits the first cloud storage ( 2000) of the data of the first user that is requested to be read-prohibited may be deleted, and the partially deleted file may be stored in the storage space of the second user.

Also, when the relay server 1000 receives a request for limiting the use of the first user's data together with the sharing request from the first device 100 , the relay server 1000 receives the request from the first cloud storage 2000 . A process for limiting a requested function may be performed on the data of one first user, and the data of the first user whose use limit has been processed may be stored in the storage space of the second user.

In addition, the relay server 1000 may synchronize a copy of the first user's data stored in the first cloud storage 2000 and the first user's data stored in the second user's storage space in the second cloud storage 3000 . have. The copy of the data of the first user may mean data in which the data of the first user stored in the first cloud storage 2000 is copied to the storage space of the second user according to a sharing request.

For example, the relay server 1000 may receive a synchronization request indicating that the data of the first user has changed from the first cloud storage 2000 . Upon receiving the synchronization request, the relay server 1000 may update a copy of the first user's data stored in the second cloud storage 3000 with the changed first user's data. In this case, upon receiving the synchronization request, the relay server 1000 may determine whether the changed data is write-protected data based on location information indicating the location of the changed data. Only when the changed data is not write-protected data, the relay server 1000 may update a copy of the first user's data stored in the second cloud storage 3000 with the changed first user's data. The write-protection setting may mean a setting in which a copy of the data of the first user stored in the storage space of the second user is not changed by the relay server 1000 . Also, when the changed data is a part of the file, the location information indicating the location of the changed data may include location information of the changed part in the file.

6 is a view for explaining a method of registering a first user and a second user by the first cloud storage 2000, the second cloud storage 3000, and the relay server 1000 according to an embodiment of the present invention; am.

In operation S6010 , the first cloud storage 2000 may receive a registration request for the first user from the first device 100 . The registration request for the first user may include the account of the first user to be registered in the first cloud storage 2000 . The account may include the ID and password of the first user. As the first user is registered in the first cloud based on the account of the first user, the first user may acquire a right to use the resource of the first cloud storage 2000 .

In operation S6020 , the second cloud storage 3000 may receive a registration request for the second user from the second device 200 . As the second user is registered in the second cloud based on the account of the second user, the second user may acquire a right to use the resource of the second cloud storage 3000 .

In operation S6030 , the first cloud storage 2000 may receive a registration request for the relay server 1000 from the relay server 1000 . As the relay server 1000 is registered in the first cloud storage 2000 based on the account of the relay server 1000 , the relay server 1000 is authorized to use the resource of the first cloud storage 2000 . can be obtained.

In operation S6040 , the second cloud storage 3000 may receive a registration request for the relay server 1000 from the relay server 1000 . As the relay server 1000 is registered in the second cloud storage 3000 based on the account of the relay server 1000 , the relay server 1000 is authorized to use the resource of the second cloud storage 3000 . can be obtained.

Accordingly, the relay server 1000 may be registered as a user in the first cloud storage 2000 and the second cloud storage 3000 .

On the other hand, the relay server 1000, as a third party that can use the resources of the first cloud storage 2000 or the second cloud storage 3000, the first cloud storage 2000 or the second cloud It may be registered in the storage 3000 .

For example, in the relay server 1000, a program for authentication and authorization implemented with an Open API (Application Programming Interface) provided by the first cloud storage 2000 operator or the second cloud storage 3000 operator (eg, For example, a program implemented with the OAuth standard) may be installed. And, the relay server 1000, based on the authentication and permission of the first user or the second user, the resource of the first user in the first cloud storage 2000 or the second cloud storage 3000 or the second user You can also obtain permission to use the resource.

When the relay server 1000 is previously registered in the first cloud storage 2000 and the second cloud storage 3000 , the relay server 1000 in the first cloud storage 2000 and the second cloud storage 3000 . The step of registering may be omitted.

In operation S6050 , the relay server 1000 may receive a registration request for the first user from the first device 100 . The registration request for the first user may include the account of the first user to be registered with the relay server 1000 .

In operation S6060 , the relay server 1000 may receive a registration request for the second user from the second device 200 . The registration request for the second user may include the account of the second user to be registered with the relay server 1000 .

7 is a diagram for describing a method of receiving, by the first device 100, an input of a first user for selecting data to be shared with a second user, according to an embodiment of the present invention.

Referring to FIG. 7 , the first device 100 receives the first user's input for setting sharing with the second user with respect to at least one of the first user's files or folders stored in the first cloud storage 2000 . can receive

The first device 100 may receive the first user's file or folder stored in the first cloud storage 2000 from the first cloud storage 2000 and store the received file or folder in the first device 100 . have. Also, the first device 100 may synchronize the file or folder of the first user stored in the first device 100 with the file or folder of the first user stored in the first cloud storage 2000 .

In addition, as the first user's file or folder stored in the first cloud storage 2000 is received from the first cloud storage 2000 , the first device 100 displays the list 710 of the received file or folder. can be displayed on the screen. For example, the first device 100 mounts the file or folder of the first user, received from the first cloud storage 2000, in the file system of the first device 100, and lists the files or folders ( 710) may be displayed on the screen.

When the first user right-clicks a mouse button while selecting a displayed file or folder, the first device 100 may display a menu 720 indicating a function related to the selected file or folder.

In this case, the first device 100 may determine whether the selected file or folder is a file or folder of the first user stored in the first cloud storage 2000 . Corresponding to the file or folder, information regarding whether the file or folder is a file or folder stored in the first cloud storage 2000 may be stored in the first device 100 . For example, information on whether a file or a folder is stored in the first cloud storage 2000 may be recorded in the file or folder in the form of metadata.

When the file or folder selected by the first user is the file or folder of the first user in the first cloud, the first device 100 may display an interface 730 for sharing the selected file or folder.

Upon receiving the user input for selecting the interface 730 for sharing the selected file or folder, the first device 100 may display the file or folder selected by the first user, and the first user wants to share the selected file or folder with the second user. It can be determined as a file or folder to

8 is a diagram for explaining a method for a first user to select data to be shared with a second user in the first device 100 according to another embodiment of the present invention.

Referring to FIG. 8 , the first device 100 may receive a user input for selecting at least one of the first user's files or folders stored in the first cloud storage 2000 displayed on the first device 100 . can

The first device 100 may receive a list of files or folders of the first user from the first cloud storage 2000 . In this case, the first device 100 may receive, from the first cloud storage 2000 , only attribute information of the file in the first user's folder and the hierarchical structure of the folder, among the data of the first user's file or folder. .

Upon receiving the list of files or folders of the first user from the first cloud storage 2000 , the first device 100 may display the list of files or folders of the first user on the screen.

Also, the first device 100 may display a user interface 810 for selecting at least one of the first user's files or folders on the screen. The user interface 810 for selecting at least one of the first user's files or folders includes a name of the file or folder, a check box for selecting each file or folder, and a button 820 for executing a sharing function can do.

Also, the first device 100 may display attribute information of the file together with the file name.

Upon receiving a user input of selecting at least one of the first user's files or folders and a user input of selecting a button 820 for executing a sharing function, the first device 100 is selected by the first user The file or folder may be determined as a file or folder that the first user wants to share with the second user.

9 is a diagram for explaining a method for a first user to select data to be shared with a second user in the first device 100 according to another embodiment of the present invention.

Referring to FIG. 9 , the first device 100 may receive a user input for selecting a file of the first user stored in the first cloud storage 2000 displayed on the first device 100 .

When receiving a user input for selecting a file, the first device 100 may display the content 910 of the file. Also, when the displayed file is a file stored in the cloud storage of the first user, the first device 100 may display the user interface 920 for sharing the file together with the content 910 of the file.

Upon receiving a user input for selecting the user interface 920 for sharing a file, the first device 100 may determine the displayed file as a file to be shared with the second user.

10 is a diagram in which the first device 100 provides the relay server 1000 with respect to data selected by the first user among the data of the first user stored in the first cloud storage 2000 according to an embodiment of the present invention. This is a flow chart explaining how to set access rights.

In step S1010 , the first device 100 may receive a user input instructing to share at least one of the first user's data stored in the first cloud storage 2000 with another user.

In step S1020 , the first device 100 may request the first cloud storage 2000 to grant access to the relay server 1000 to the data of the first user stored in the selected first cloud storage 2000 . have.

Upon receiving a user input for instructing sharing, the first device 100 sets up sharing between the first user and the relay server 1000 with respect to the first user's data stored in the first cloud storage 2000 . 1 A request may be made to the cloud storage 2000 .

The sharing setting request between the first user and the relay server 1000 for the first user's data stored in the first cloud storage 2000 includes the ID of the first user registered in the first cloud storage 2000, the first cloud storage ID of the relay server 1000 registered in 2000 and identification information of the first user's data stored in the selected first cloud storage 2000 may be included.

Also, the first device 100 may request location information indicating the location of the first user's data stored in the selected first cloud storage 2000 together with the access right grant request.

In operation S1030 , the first cloud storage 2000 may grant access to the relay server 1000 with respect to data selected by the first user among the data of the first user stored in the first cloud storage 2000 .

For example, the first cloud storage 2000 may set sharing between the first user and the relay server 1000 with respect to the data of the first user selected by the first user. As sharing between the first user and the relay server 1000 is set, the first cloud storage 2000 corresponds to the ID of the relay server 1000 registered in the first cloud storage 2000, and the first cloud storage Access authority information for the data of the first user stored in 2000 may be stored. Also, the first cloud storage 2000 may store the ID of the relay server 1000 in response to identification information of the first user's data stored in the first cloud storage 2000 .

In step S1040 , the first cloud storage 2000 transmits location information indicating the location of data selected by the first user among the data of the first user stored in the first cloud storage 2000 to the first device 100 . can

In FIG. 10 , as sharing of the first user's data between the first user and the relay server 1000 is set in the first cloud storage 2000 , the relay server 1000 performs the first cloud storage 2000 . Although the access authority to the data of the first user stored in You can also receive

FIG. 11 is a diagram for describing a method of receiving, by the first device 100, a first user input for setting a second user to share data of the first user, according to an embodiment of the present invention.

Referring to FIG. 11 , the first device 100 may receive a user input for setting a second user.

The first device 100 may receive a user input for setting a second user to share data selected by the first user among the data of the first user stored in the first cloud storage 2000 .

For example, as the file or folder selected by the first user is determined as data to be shared, the first device 100 may display the user interface 1110 for setting the second user.

The user interface 1110 for setting the second user may include a user interface 1120 for inputting identification information of the second user. The identification information of the second user may include the ID, name, phone number, and e-mail address of the second user registered in the relay server 1000 .

Also, the first device 100 may display a user interface 1130 for requesting the relay server 1000 to share the data of the first user with the second user. Upon receiving the input of the first user requesting the relay server 1000 to share the data of the first user with the second user, the first device 100 transmits the data of the first user selected by the first user , may be requested from the relay server 1000 to share with the second user input by the first user.

FIG. 12 is a diagram for explaining a method of receiving, by the first device 100, a first user input for setting a second user to share data of the first user, according to another embodiment of the present invention.

Referring to FIG. 12 , the first device 100 may receive a user input for setting a second user to share data of the first user stored in the first cloud storage 2000 .

With respect to the file or folder selected by the first user, the first device 100 may display a user interface 1210 for setting the second user.

The user interface 1210 for setting the second user may include a user interface 1220 for inputting identification information of the second user. The user interface 1220 for inputting the second user's identification information may be linked with the user list stored in the first device 100 .

For example, when receiving a user input of touching the user interface 1220 for inputting identification information of the second user, the first device 100 may display a list of users stored in the first device 100 . have. The user list stored in the first device 100 may include an address book 1250 .

The first device 100 may receive a user input for selecting at least one of the displayed user list. Upon receiving the user input for selecting at least one, the first device 100 may determine the name, phone number, or email address of the selected user as identification information of the second user.

Also, the first device 100 may display the user interfaces 1230 and 1240 for setting a usage limit for the data of the first user to be given to the second user. Restrictions on the use of data may include restrictions on copying of data, printing of data and alteration of data, and the like.

For example, when the first user selects the “can change” button 1230, the second user can view the first user's data as well as modify the first user's data. On the other hand, when the first user selects the “read-only” button 1240 , the second user can only view the data of the first user, and modification of the data of the first user may be restricted.

FIG. 13 is a diagram for describing a method of receiving, by the first device 100, a first user input for setting a second user to share data of the first user, according to another embodiment of the present invention.

Referring to FIG. 13 , the first device 100 may receive a user input for setting a second user to share data of the first user stored in the first cloud storage 2000 .

The first device 100 may display a user interface 1350 for setting a second user. The first device 100 may receive the user interface 1350 for setting the second user from the relay server 1000 . For example, the first device 100 may receive a web page including a user interface 1350 for setting two users from the relay server 1000 .

The user interface 1350 for inputting identification information of the second user may be linked with a user database stored in the relay server 1000 . In the user database stored in the relay server 1000 , the user's name, phone number, and e-mail address may be stored in correspondence with the ID of the user registered in the relay server 1000 .

As the first user inputs identification information of the second user through the user interface 1350 , the first device 100 may transmit the input identification information to the relay server 1000 . The relay server 1000 may determine the ID of the second user corresponding to the received identification information of the second user based on the user database.

Also, the first device 100 may display a user interface 1370 for inputting a message to be transmitted to the second user.

14 is a diagram in which the first device 100 displays data of the selected first user according to an embodiment of the present invention, as the first device 100 receives the first user's input for selecting the data of the first user to be shared and the second user. It is a flowchart for explaining a method of requesting the relay server 1000 to share with a second user.

In operation S1410 , the first device 100 may request the relay server 1000 to share the data of the first user between the first user and the second user.

Upon receiving the first user's data to be shared and the first user's input for selecting the second user, the first device 100 informs the relay server 1000 to share the selected first user's data with the second user. can be requested to

The sharing setting request between the first user and the second user for at least one of the first user's data stored in the first cloud storage 2000 includes the ID of the first user registered in the relay server 1000 and the relay server 1000 . ) may include the ID of the registered second user and identification information of the data of the first user to be shared. The identification information of the first user's data may include location information indicating a location where the first user's data is stored.

In operation S1420 , the relay server 1000 may set sharing between the first user and the second user with respect to the first user's data requested to be shared by the first device 100 .

For example, the relay server 1000 may store, as a sharer, the ID of the second user registered in the relay server 1000 in response to the sharing request of the first user. Also, the relay server 1000 may store, as an owner, the ID of the first user registered in the relay server 1000 in response to the first user's data requested to be shared. In addition, the relay server 1000 may store location information indicating the location of the storage space of the second user in the second cloud storage 3000 in response to the shared requested data of the first user.

15 is a diagram illustrating a database 1500 about a data provider stored in the relay server 1000 in response to a request for setting a sharing setting between a first user and a second user for the first user's data according to an embodiment of the present invention. ) is a diagram for explaining the

Referring to FIG. 15 , the relay server 1000 may store data-related information in response to a user providing data.

For example, the relay server 1000 may include, in response to the ID 1510 of the first user registered in the relay server 1000 , the ID 1520 of the first user registered in the first cloud storage 2000 and Information 1530 about data provided by the first user to the second user may be stored. The information 1530 about data provided by the first user to the second user may include identification information 1532 of data provided by the first user to the second user. The data identification information 1532 may include location information indicating the location of the data.

16 is a database 1600 about data stored in the relay server 1000 in response to a request for sharing setting between the first user and the second user for the first user's data, according to an embodiment of the present invention. It is a drawing for explaining.

Referring to FIG. 16 , the relay server 1000 responds to identification information 1611 of data requested to be shared between a first user and a second user, and information about the original data 1610 and information about sharing 1620 . ) can be stored.

The information 1610 about the source of the data requested to be shared includes a data name 1612, an ID 1614 of an owner, cloud storage identification information 1616 where the data is stored, and location information 1618 indicating the location of the data. can Also, the sharing information 1620 may include an ID 1622 of a recipient registered in the relay server 1000 .

17 is a diagram illustrating the relay server 1000 providing the shared data of the first user with respect to the first user's data according to an embodiment of the present invention, as the sharing of the first user and the second user is set. 1 shows a flowchart explaining a method of receiving from the cloud storage 2000 .

In step S1710 , the relay server 1000 may request the first cloud storage 2000 for a list of data of the first user shared between the first user and the second user.

With respect to the first user's data, as sharing between the first user and the second user is set, the relay server 1000 sends the first cloud storage 2000 to the first user and the first user shared between the first user and the second user. You can request a list of data from

For example, the relay server 1000 may use location information indicating the location of the first user's data and the ID of the relay server 1000 registered in the first cloud storage 2000 to store the data of the first user. You can request a list.

When the data is a file, the list of data may include attribute information of the file. Also, when the data is a folder, the list of data may include attribute information of each file located in the folder and a hierarchical structure of the folder. Also, when the data is a folder, the list of data may further include location information indicating the location of each folder or file located in the folder.

In operation S1720 , the first cloud storage 2000 may determine whether the relay server 1000 has access to the data of the first user requested from the relay server 1000 .

The first cloud storage 2000 may determine whether the relay server 1000 has access to the requested data of the first user based on the ID of the relay server 1000 .

For example, when the first user's data requested from the relay server 1000 is set to be shared between the first user and the relay server 1000 , the first cloud storage 2000 is stored in the requested data of the first user. It may be determined that the relay server 1000 has an access right to the data.

In operation S1730 , the first cloud storage 2000 may transmit a list of data of the first user requested from the relay server 1000 to the relay server 1000 .

As the relay server 1000 determines that the relay server 1000 has access to the data of the first user requested from the relay server 1000, the first cloud storage 2000 relays the requested list of data of the first user. may be transmitted to the server 1000 .

In operation S1740, the relay server 1000 may store a list of data of the first user shared between the first user and the second user.

The relay server 1000 may store the list of data of the first user received from the first cloud storage 2000 in the relay server 1000 . For example, the relay server 1000 may store attribute information of a file in response to identification information of each file. In addition, the relay server 1000 corresponds to the identification information of the file, the owner ID of the file, the recipient ID, the time shared by the first user and the second user, the access range set by the first user, and the first cloud storage (2000) people can be stored.

18 is a diagram for explaining a database for a list of files or folders of the first user received from the first cloud storage 2000 according to an embodiment of the present invention.

Referring to FIG. 18 , the relay server 1000 may store a list of files or folders of the first user received from the first cloud storage 2000 .

The relay server 1000 may store attribute information of the file or folder 1800 received from the first cloud storage 2000 in response to identification information of each file or folder. The identification information of each file or folder may include location information indicating the location of the file or folder.

For example, in response to the file identification information, the relay server 1000 may include, in response to the file identification information, a file name, an owner ID of a file, a cloud storage name in which the file is stored, a file format, a size of a file, a file creation time, a file modification time, It is possible to store the file access point, information about the access right to the file, information about the scope of access to the file, the recipient ID of the file, and location information indicating the location of the file.

In addition, the relay server 1000 may store, in response to the identification information of the folder, the folder name, the owner ID of the folder, the folder format, information about the storage in which the folder is stored, the recipient ID of the folder, and location information indicating the location of the folder. have.

For example, the folder shared by the first user with the second user may be Dropbox_user1_FOLDER2, and the Dropbox_user1_FOLDER2 folder may include a Dropbox_user1_SUB_FOLDER_1 folder, a Dropbox_user1_SUB_FOLDER_2 folder, and a Dropbox_user1_FILE1 file.

Accordingly, the list for the Dropbox_user1_FOLDER2 folder may include a hierarchical structure of the Dropbox_user1_FOLDER2 folder, attribute information of files in the Dropbox_user1_FOLDER2 folder, and attribute information of the Dropbox_user1_FILE1 file.

19 is a diagram showing, according to an embodiment of the present invention, the second device 200 grants the relay server 1000 the right to store data in the storage space of the second user in the second cloud storage 3000 It is a drawing for explaining the method.

The right to store data in the storage space of the second user in the second cloud storage 3000 may mean the right to store data as data of the second user in the second cloud storage 3000 .

Referring to FIG. 19 , the second device 200 grants the relay server 1000 permission to store data in the storage space of the second user in the second cloud storage 3000 for the second cloud storage 3000 . ) can be requested.

For example, in the second device 200 or the relay server 1000 , software logic for granting another user the right to store data in the storage space of the second user is provided by the second cloud storage 3000 operator. It may be provided using the Open API provided by .

In response to a request from the second device 200 or the relay server 1000 to grant the relay server 1000 the right to store data in the storage space of the second user, the second cloud storage 3000 is You may be asked to authenticate as a second user. For example, the second cloud storage 3000 may transmit a user authentication page to the second device 200 .

Based on the user authentication page, the second device 200 may receive, from the second user, the account of the second user registered in the second cloud storage 3000 . Upon receiving the account of the second user registered in the second cloud storage 3000 from the second user, the second device 200 transmits the account of the second user to the second cloud storage 3000, It can be authenticated as the second user.

As the second user is authenticated, the second cloud storage 3000 grants the second user permission to the relay server 1000 to store data in the storage space of the second user to the second device. (200) can be requested. For example, the second cloud storage 3000 displays a resource use permission page 1910 for checking whether to grant the relay server 1000 the right to store data in the storage space of the second user. may be transmitted to the device 200 .

Based on the resource use permission page 1910, the second device 200 receives, from the second user, whether to grant the relay server 1000 the right to store data in the storage space of the second user. can In addition, the second device 200 may transmit to the second cloud storage 3000 whether or not to grant the relay server 1000 the right to store data in the storage space of the second user.

The second cloud storage 3000 may authorize the relay server 1000 to store data in the storage space of the second user based on a user input received from the second device 200 . For example, the second cloud storage 3000 may set the ID of the relay server 1000 registered in the second cloud storage 3000 as a third party that can use the storage space of the second user.

In addition, as the relay server 1000 is given the right to store data in the storage space of the second user, the second cloud storage 3000 provides location information indicating the location of the storage space of the second user. 2 may be transmitted to the device 200 . Upon receiving the location information indicating the location of the storage space of the second user from the second cloud storage 3000 , the second device 200 transmits the location information indicating the location of the storage space of the second user to the relay server 1000 . ) can be transmitted.

The location information indicating the location of the storage space of the second user may include location information indicating the location of the folder of the second user in the second cloud storage 3000 . Also, the location information indicating the location of the storage space of the second user may be changed according to the setting of the second user.

20 is a diagram showing, according to an embodiment of the present invention, the second device 200 granting the relay server 1000 the right to store data in the storage space of the second user in the second cloud storage 3000 . A flowchart for explaining the method is shown.

In step S2010 , the second device 200 grants the relay server 1000 permission to store data in the storage space of the second user in the second cloud storage 3000 second cloud storage 3000 . can ask for

In this case, the request for granting the relay server 1000 the right to store data in the storage space of the second user includes the ID of the relay server 1000 registered in the second cloud storage 3000 and the second cloud storage The ID of the second user registered in 3000 may be included.

Also, the second device 200 may request location information indicating the location of the storage space of the second user in the second cloud storage 3000 from the second cloud.

In step S2020 , the second cloud storage 3000 may grant the relay server 1000 the right to store data in the storage space of the second user in the second cloud storage 3000 .

For example, in response to a request to grant the relay server 1000 permission to store data in the storage space of the second user, the second cloud storage 3000 may perform authentication for the second user. have. In addition, the second cloud storage 3000 may receive, from the second device 200 , a second user's input that grants the relay server 1000 permission to store data in the storage space of the second user. .

In response to receiving an input of the second user that grants the relay server 1000 permission to store data in the storage space of the second user, the data is stored in the storage space of the second user in the second cloud storage 3000 . A right to do this may be granted to the relay server 1000 . For example, the second cloud storage 3000 may set the ID of the relay server 1000 registered in the second cloud storage 3000 as a third party that can use the storage space of the second user.

In operation S2030 , the second cloud storage 3000 may transmit location information indicating the location of the storage space of the second user in the second cloud storage 3000 to the second device 200 .

The location information indicating the location of the storage space of the second user in the second cloud storage 3000 may include a URI of the drive or folder of the second user in the second cloud storage 3000 .

Also, according to an embodiment, the second cloud storage 3000 may transmit information about the right to store data in the storage space of the second user to the second device 200 . The information on the permission to store data may include password information for authenticating the permission to store data in the storage space of the second user.

In operation S2040 , the second device 200 may transmit location information indicating the location of the storage space of the second user in the second cloud storage 3000 to the relay server 1000 .

Upon receiving the location information indicating the location of the storage space of the second user in the second cloud storage 3000 , the relay server 1000 responds to the ID of the second user registered in the relay server 1000 , It is possible to store location information indicating the location of the user's storage space.

In addition, when receiving information about the right to store data in the storage space of the second user from the second cloud storage 3000 , the second device 200 transmits the received information to the relay server 1000 . can

19 to 20 disclose a method in which the second device 200 grants the relay server 1000 permission to store data in the storage space of the second user in the second cloud storage 3000, In the same way, the first device 100 may grant the relay server 1000 access to the data of the first user in the first cloud storage 2000 .

21 is a diagram illustrating that the relay server 1000 receives location information indicating the location of the storage space of the second user in the second cloud storage 3000, and stores it in the relay server 1000 according to an embodiment of the present invention. It is a diagram for explaining the database to be used.

The relay server 1000 may store location information indicating the location of the storage space of the second user in response to the second user.

For example, the relay server 1000 may correspond to the ID 2160 of the second user registered in the relay server 1000 , the ID 2170 of the second user registered in the second cloud storage 3000 and The location information 2180 indicating the location of the storage space of the second user in which data provided to the second user from another person is to be stored may be stored. The location information 2180 indicating the location of the storage space of the second user may include a URL 2184 for the storage space of the second user.

22 is a diagram illustrating, in response to receiving a sharing request for sharing data of a first user with a second user from the first device 100, the relay server 1000, the second device, according to an embodiment of the present invention. It is a diagram for explaining a method of notifying 200 that the first user has requested to share the data of the first user with the second user.

The second device 200 may receive, from the relay server 1000 , information indicating that sharing of the first user's data has been set between the first user and the second user. The information indicating that sharing between the first user and the second user has been set includes the ID of the first user registered in the relay server 1000, a list of data of the first user that is set to be shared between the first user and the second user, and the second It may include a message of the first user to the user, and the like.

Accordingly, the second device 200 may display information indicating that sharing between the first user and the second user is set for the first user's data received from the relay server 1000 .

For example, the second device 200 may display an event message 2210 informing that sharing between the first user and the second user is set for the first user's data on the indicator bar of the screen of the second device 200 . can

23 is a diagram in which the relay server 1000 stores the list of data of the first user received from the first cloud storage 2000 in the second cloud storage 3000 according to an embodiment of the present invention. It is a flowchart to explain how to store in space.

In operation S2310 , the relay server 1000 may store, in the relay server 1000 , a list of data of the first user received from the first cloud storage in response to a sharing request from the first user.

In the list of first user's data received from the first cloud storage, the first user requests the relay server 1000 to share the first user's data stored in the first cloud storage 2000 with the second user. Accordingly, the relay server 1000 may be a list of data of the first user received from the first cloud storage 2000 .

In operation S2320 , the relay server 1000 may request the second cloud storage 3000 to store the list of the first user's data received from the first cloud storage in the storage space of the second user.

The storage request for the list of the first user's data includes the list of the first user's data, the ID of the relay server 1000 registered in the second cloud storage 3000 , and the second registered in the cloud storage 3000 . 2 may include the user's ID.

In step S2330 , the second cloud storage 3000 may determine whether the relay server 1000 has an authority to store data in the storage space of the second user in the second cloud storage 3000 .

For example, the second cloud storage 3000 is based on the ID of the second user registered in the second cloud storage 3000 and the ID of the relay server 1000 registered in the second cloud storage 3000, It may be determined whether the relay server 1000 has the right to store data in the storage space of the second user in the second cloud storage 3000 .

When the relay server 1000 has the right to store data in the storage space of the second user in the second cloud storage 3000 , in step S2340 , the second cloud storage 3000 is sent from the relay server 1000 . A list of the first user's data received. It can be stored in the storage space of the second user.

24A is a diagram illustrating that, upon receiving from the relay server 1000 that data of the first user is set to be shared between the first user and the second user, the second device 200, the first user, according to an embodiment of the present invention. It is a diagram illustrating a method of displaying a user interface for receiving a second user's selection for selecting whether to store the data in the second cloud storage 3000 .

The second device 200 may display a user interface 2420 for selecting whether to store the first user's data shared between the first user and the second user in the second cloud storage 3000 .

Also, the second device 200 may display a user interface 2430 for selecting a range of the first user's data to be stored in the second cloud storage 3000 .

The user interface 2430 for selecting a storage range may include a user interface for selecting whether to store only a list of data or even data.

The second device 200 may transmit, to the relay server 1000 , information on whether to store the first user's data in the second cloud storage 3000 and information on a storage range, received from the second user. .

The relay server 1000 may store the first user's data received from the second device 200 in the second cloud storage 3000 based on the information on the storage range and the information on whether to store the first user's data. Some or all of may be stored in the second cloud storage 3000 .

For example, when the input value of the second user is “save”, the relay server 1000 may store the list of data of the first user received from the first cloud storage 2000 or the data of the first user to the second It may be stored in the cloud storage 3000 .

In addition, when the input value of the second user is “pending”, the relay server 1000 does not store the list of data of the first user received from the first cloud storage 2000 in the second cloud storage 3000 . may not be

Also, when the input value of the second user is “rejected”, the relay server 1000 does not store the list of data of the first user received from the first cloud storage 2000 in the second cloud storage 3000 . it may not be In addition, the list of data of the first user received from the first cloud storage 2000 stored in the relay server 1000 may also be deleted.

In addition, when the second user selects to store the contents of the first user's file in the second cloud storage 3000 , the relay server 1000 sets up a list of the first user's data shared between the first user and the second user. In addition, the content of the file may be stored in the second cloud storage 3000 .

24B illustrates the relay server 1000 transferring the data of the first user to the second cloud storage 3000 based on the selection of the second user received from the second device 200, according to an embodiment of the present invention. It is a flowchart for explaining the method of saving.

In step S2410 , the relay server 1000 may store, in the relay server 1000 , a list of data of the first user received from the first cloud storage 2000 in response to a sharing request from the first user.

In step S2420 , the relay server 1000 may request the second device 200 to select whether to store the first user's data received from the first cloud storage 2000 in the second cloud storage 3000 . have.

In step S2430 , the second device 200 relays information about whether to store the first user's data in the second cloud storage 3000 and information about a storage range, received from the first cloud storage 2000 . may be transmitted to the server 1000 .

In operation S2440 , the relay server 1000 may request the second cloud storage 3000 to store the list of data of the first user received from the first cloud storage 2000 in the storage space of the second user.

The relay server 1000 stores the data of the first user received from the first cloud storage 2000 in the second cloud storage 3000 based on the input of the second user received from the second device 200 . You can decide whether or not to save it.

When the second user selects to store only the list of data of the first user in the second cloud storage 3000 , the relay server 1000 stores the list of data of the first user received from the first cloud storage 2000 . A request may be made to the second cloud storage 3000 to store in the storage space of the second user.

In addition, the data storage request transmitted to the second cloud storage 3000 includes a list of data of the first user, an ID of a second user registered in the second cloud storage 3000 , and a data storage request registered in the second cloud storage 3000 . The ID of the relay server 1000 may be included.

In operation S2450 , the second cloud storage 3000 may determine whether the relay server 1000 has an authority to store data in the storage space of the second user in the second cloud storage 3000 .

For example, the second cloud storage 3000 is based on the ID of the second user registered in the second cloud storage 3000 and the ID of the relay server 1000 registered in the second cloud storage 3000, It may be determined whether the relay server 1000 has the right to store data in the storage space of the second user in the second cloud storage 3000 .

When the relay server 1000 has the right to store data in the storage space of the second user in the second cloud storage 3000 , in step S2460 , the second cloud storage 3000 is sent from the relay server 1000 . A list of the first user's data received. It can be stored in the storage space of the second user.

25 is a diagram illustrating the data of the first user stored in the second cloud storage 3000 as shared between the first user and the second user according to an embodiment of the present invention, and the second device 200 is transferred to the second cloud. It is a diagram for explaining a method of receiving and displaying from the storage 3000 .

As the second cloud storage 3000 receives the data of the first user from the relay server 1000 and stores it as the data of the second user, the second cloud storage 3000 stores the data of the first user as the data of the second user. A copy of the user's data may be transmitted to the second device 200 .

When the copy of the first user's data is a file or folder, the second device 200 may receive only a list of files or folders from the second cloud storage 3000 . The list of files or folders may include attribute information of files and a hierarchical structure of folders.

Referring to FIG. 25 , the second device 200 may display a list 2510 of copies of the first user's data received from the second cloud storage 3000 . In this case, the second device 200 may display a list of copies of the first user's data together with a list of existing files or folders stored in the second cloud storage 3000 . Also, the second device 200 may display an image 2514 indicating that it is a copy of the first user's data by distinguishing it from an existing file or folder stored in the second cloud storage 3000 .

Also, the second device 200 may display a user interface 2512 for selecting a file or a folder. Also, the second device 200 may display a user interface 2520 for receiving the selected file or folder from the second cloud storage 3000 .

When the check box 2512 is selected and a user input of touching the download button 2520 is received, the second device 200 transfers the file or folder in which the check box 2512 is selected to the second cloud storage 3000 . can ask for..

In addition, when a user input of selecting the check box 2512 and touching the delete button 2530 is received, the second device 200 prompts the second device to delete the selected file or folder from the second cloud storage 3000 . A request may be made to the cloud storage 3000 .

26 is a diagram showing the first user's data stored in the second cloud storage 3000 as shared between the first user and the second user is set according to an embodiment of the present invention, and the second device 200 transmits the data of the second user to the second cloud. It is a diagram for explaining a method of receiving and displaying from the storage 3000 .

In FIG. 26 , as the second device 200 receives a user input for selecting the Dropbox_user1_FOLDER2 folder, the second device 200 may display a list 2620 of files and folders in the Dropbox_user1_FOLDER2.

The second device 200 may display a list of folders or files in the Dropbox_user1_FOLDER2 folder based on the hierarchical structure of the Dropbox_user1_FOLDER2 folder received from the second cloud storage 3000 .

27 is a diagram in which, according to another embodiment of the present invention, the data of the first user stored in the second cloud storage 3000 as shared between the first user and the second user is set to be shared by the second device 200 by the second device 200 . It is a diagram for explaining a method of receiving and displaying from the cloud storage 3000 .

In FIG. 27 , as the second device 200 receives a user input for selecting the Dropbox_user1_FILE1 file, the second device 200 determines whether the contents of the Dropbox_user1_FILE1 file are stored in the second device 200 . can When the content of the Dropbox_user1_FILE1 file is not stored in the second device 200 , the second device 200 may display only attribute information of the Dropbox_user1_FILE1 file.

The attribute information of the file may include a thumbnail image. Accordingly, when the selected file is an image file, the second device 200 may display the thumbnail image 2710 .

Also, the second device 200 may display the storage capacity 2720 occupied by the displayed file in the second device 200 .

Also, the second device 200 may display information 2730 indicating whether the content of the displayed file is stored in the second cloud storage 3000 .

Also, when the selected file is not stored in the second device 200 , the second device 200 may display a user interface 2740 for storing the displayed file in the second device 200 . Also, when the selected file is not stored in the second cloud storage 3000 , the second device 200 may display a user interface 2750 for storing the displayed file in the second cloud storage 3000 . have.

28 is a flowchart illustrating a method for the second device 200 to receive a list of data of the first user from the second cloud storage 3000, according to an embodiment of the present invention.

In step S2810, the second cloud storage 3000, received from the relay server 1000, the list of data of the first user set to be shared between the first user and the second user. It can be stored in the storage space of the second user.

For example, when sharing is set between the first user and the second user for the first user's data stored in the first cloud storage 2000 , the first user's data is The first cloud storage 2000 may be copied to the second cloud storage 3000 .

In operation S2820 , the second cloud storage 3000 may transmit the list of data of the first user received from the relay server 1000 to the second device 200 .

The second cloud storage 3000 may transmit a list of data of the first user to the second device 200 based on a request from the second device 200 . In addition, when synchronization is set between the data of the second user in the second cloud storage 3000 and the data of the second user in the second device 200 , the list of data of the first user is stored in the second cloud storage 3000 . As the data is stored, the second cloud storage 3000 may transmit a list of data of the first user to the second device 200 .

The list of data transmitted to the second device 200 may include data attribute information. In this case, the attribute information of the data may include information on whether the data is stored in the second cloud storage 3000 .

In operation S2830 , the second device 200 may store and display a list of data of the first user received from the second cloud storage 3000 .

The second user may access data of the first user provided by the first user through the second device 200 . That is, data of the first user stored in the first cloud storage 2000 may be shared between the first user and the second user.

29 is a second device 200 in response to receiving an input of a second user for selecting one of a list of files of the first user shared between the first user and the second user, according to an embodiment of the present invention; is a diagram for explaining a method of acquiring the contents of a file of a first user.

Referring to FIG. 29 , upon receiving a user input for selecting a file of the first user shared between the first user and the second user, the second device 200 determines whether the selected file is stored in the second device 200 . can determine whether When the selected file is not stored in the second device 200 , the second device 200 may request the selected file from the second cloud storage 3000 .

After requesting the selected file from the second cloud storage 3000 , until the requested file is received from the second cloud storage 3000 , the second device 200 displays a user interface 2910 indicating that the file is being downloaded. can be displayed. The user interface 2910 indicating that a file is being downloaded may include identification information of a cloud storage that transmits and receives a file. For example, when the file requested by the second cloud storage 3000 is not stored in the second cloud, the data of the first user in the first cloud storage 2000 is transmitted to the first The data may be transmitted from the cloud storage 2000 to the second cloud storage 3000 . Accordingly, the user interface 2910 may include identification information of the first cloud storage 2000 and the second cloud storage 3000 .

As the file selected by the second user is received from the second cloud storage 3000 via the relay server 1000 , the second device 200 may display the contents 2920 of the received file. Also, the second device 200 may display a user interface 2930 for storing the displayed file in the second device 200 .

30 is a diagram in which, according to an embodiment of the present invention, only a list of the first user's data shared by the first user and the second user is stored in the second device 200, and the second device 200 is It is a flowchart for explaining a method of acquiring data of the first user.

In step S3010, the second device 200 stores the data selected by the second user from the list of the first user's data stored in the second device as the sharing setting is set in the relay server by the first user to the second cloud storage (3000) can be requested.

The second device 200 may display a list of data of the first user received from the second cloud storage 3000 . In addition, the second device 200 may receive a user input for selecting at least one from the list of data of the first user.

Upon receiving a user input for selecting at least one of the displayed first user's data list, the second device 200 may determine whether the selected data is stored in the second device 200 . When the selected data is not stored in the second device 200 , the second device 200 may request the selected data from the second cloud storage 3000 . The data request for the second cloud storage 3000 may include the ID of the second user registered in the second cloud storage 3000 and identification information of the data.

In operation S3020 , the second cloud storage 3000 may request data requested from the second device 200 from the relay server 1000 .

Upon receiving the request for data from the second device 200 , the second cloud storage 3000 determines whether the data requested from the second device 200 is stored in the second cloud storage 3000 . can

When the data requested from the second device 200 is not stored in the second cloud storage 3000 , the second cloud storage 3000 transmits the data requested from the second device 200 to the relay server 1000 . you can request

The data request to the relay server 1000 includes identification information of data in the relay server 1000, the ID of the second user registered in the relay server 1000, and the second cloud storage ( 3000) may be included.

In step S3030 , the relay server 1000 may request data requested from the second cloud storage 3000 from the first cloud storage 2000 .

The relay server 1000 may obtain location information indicating the location of the requested data from the second cloud storage 3000 based on the identification information of the data received from the second cloud storage 3000 . The relay server 1000 may request data requested from the second cloud storage 3000 from the first cloud storage 2000 based on the obtained location information.

In operation S3040 , the first cloud storage 2000 may transmit data requested from the relay server 1000 to the relay server 1000 .

As data is requested from the relay server 1000 , the first cloud storage 2000 may determine whether the relay server 1000 has access to the requested data. When the relay server 1000 has access to the requested data, the first cloud storage 2000 may transmit the data requested from the relay server 1000 to the relay server 1000 .

In operation S3050 , the relay server 1000 may store the data received from the first cloud storage 2000 in the second cloud storage 3000 .

The relay server 1000 may obtain location information indicating the location of the storage space of the second user based on the ID of the second user registered in the relay server 1000 . In addition, the relay server 1000 may store the data received from the first cloud storage 2000 in the storage space of the second user based on the obtained location information.

In this case, the second cloud storage 3000 may determine whether the relay server 1000 has the right to store data in the storage space of the second user.

In operation S3060 , the second cloud storage 3000 may transmit data received from the relay server 1000 to the second device 200 .

As the second cloud storage 3000 receives the data requested from the second device 200 from the relay server 1000 , the second cloud storage 3000 may transmit the data requested from the second device 200 to the second device 200 . .

In operation S3070 , the second device 200 may display data selected by the second user.

As data selected by the second user is received from the second cloud storage 3000 , the second device 200 may display data selected by the second user. For example, when the selected data is a file, the second device 200 may display the contents of the selected file.

FIG. 31 is for explaining a method for the second device 200 to set a folder of a second user in the second cloud storage 3000 as a receiving folder in the relay server 1000 according to another embodiment of the present invention It is a drawing.

The reception folder may mean a folder in which data to be received from the relay server 1000 is stored.

Referring to FIG. 31 , the second device 200 may display a user interface for setting a folder in which data to be received from the relay server 1000 is stored.

For example, when the second user right-clicks a mouse button while a folder is selected, the second device 200 may display a menu 3110 indicating a function related to the selected folder. When the folder selected by the first user is the folder of the second user in the second cloud, the second device 200 selects a selection item 3120 for sharing the selected folder between the second user and the relay server 1000 from the menu. It can be displayed on (3110).

When the second device 200 receives a user input for selecting the selection item 3120 , the second device 200 grants the relay server 1000 permission to store data in the folder for the selected folder. It may request the second cloud storage 3000 to do something.

Also, the second device 200 may request location information indicating the location of the selected folder from the second cloud storage 3000 . Accordingly, the second device 200 may receive location information indicating the location of the selected folder from the second cloud storage.

Upon receiving the location information indicating the location of the selected folder, the second device 200 may request the relay server 1000 to set the selected folder as the receiving folder of the second user.

The reception folder setting request may include location information indicating the location of the folder and the ID of the second user registered in the relay server 1000 .

Upon receiving the reception folder setting request, the relay server 1000 may set the folder selected by the second user as the reception folder of the second user. For example, the relay server 1000 may store location information indicating the location of a folder in response to the ID of the second user registered in the relay server 1000 .

32 is a diagram showing a file or folder of the first user shared between the first user and the second user as the receiving folder of the second user is set in the relay server 1000 according to an embodiment of the present invention. It is a diagram for explaining a method of being displayed on the device 200 .

Referring to FIG. 32 , the second device 200 and the second cloud storage 3000 may synchronize data stored in the second device 200 and data in the second cloud storage 3000 .

Also, the second device 200 may mount the file or folder of the second user received from the second cloud storage 3000 in the file system of the second device 200 .

For example, as the first user's Dropbox_user1_FOLDER2 folder stored in the first cloud storage 2000 is set to be shared between the first user and the second user, the 2 may be copied to the cloud storage 3000 .

In this case, if the Google Drive_user2_FOLDER1 folder is set as the receiving folder of the second user in the relay server 1000 , the relay server 1000 may store the Dropbox_user1_FOLDER2 folder in the Google Drive_user2_FOLDER1 folder.

As the Dropbox_user1_FOLDER2 folder is stored in the Google Drive_user2_FOLDER1 folder, the second device 200 may receive the Dropbox_user1_FOLDER2 folder 3200 from the second cloud storage 3000 and mount it in the Google Drive_user2_FOLDER1 folder 3210 .

Also, the second device 200 may display attribute information of a file in the Dropbox_user1_FOLDER2 folder. The attribute information of the file includes the file type (3220), the file size (3230), the storage name (3240) where the original is stored, the owner's identification information (3250), the shared time (3260), and the access range (3270). may include.

33 is a flowchart illustrating a method for the second device 200 to set the second user's folder in the second cloud storage 3000 as a receiving folder in the relay server 1000 according to another embodiment of the present invention. am.

In step S3310 , the second device 200 receives a user input for selecting one of the second user's folders in the second cloud storage 3000 as a receiving folder for storing data received from the relay server 1000 . can do.

In step S3320 , the second device 200 sets the sharing setting between the second user and the relay server 1000 with respect to the selected folder among the folders of the second user in the second cloud storage 3000 to the second cloud storage 3000 . can request Also, the second device 200 may request location information indicating the location of the selected folder.

The sharing setting request between the second user and the relay server 1000 for the data of the second user in the second cloud storage 3000 is the ID of the second user registered in the second cloud storage 3000, the second cloud storage The ID of the relay server 1000 registered in 3000 and identification information of the selected folder may be included.

In operation S3330 , the second cloud storage 3000 may set sharing between the second user and the relay server 1000 for the folder selected by the second user.

For example, the second cloud storage 3000 may receive the ID of the relay server 1000 registered in the second cloud storage 3000 in response to the folder identification information received from the second device 200 . It can be saved as a sharer of As sharing between the second user and the relay server 1000 is set for the folder selected by the second user, the relay server 1000 may acquire the right to store data in the selected folder.

In operation S3340 , the second cloud storage 3000 may transmit location information indicating the location of the folder selected by the second user to the second device 200 .

The location information indicating the location of the folder may include a URL of the folder for accessing the folder.

In operation S3350 , the second device 200 may request the relay server 1000 to set the folder selected by the second user as the receiving folder of the second user.

The reception folder setting request may include location information indicating the location of the folder received from the second cloud storage 3000 and the ID of the second user registered in the relay server 1000 .

In operation S3360, the relay server 1000 may set the folder selected by the second user as the receiving folder of the second user.

For example, the relay server 1000 may store location information indicating the location of a folder in response to the ID of the second user registered in the relay server 1000 .

34 is a diagram for explaining a method of receiving, by the second device 200, an input for designating a provider from a second user, according to an embodiment of the present invention.

The provider may mean a user who can store data in the storage space of the second user without the permission of the second user. For example, the provider may mean a user who has the authority to store a file or folder as data of the second user in the second cloud storage 3000 without the permission of the second user.

Referring to FIG. 34 , the second device 200 may display a user interface 3410 for receiving an input designating a provider.

For example, when the second user long-clicks the right mouse button while selecting a folder, a user interface 3410 for designating a provider may be displayed.

The user interface 3410 for designating a provider may include a user interface 3420 for inputting user identification information. The user's identification information may include the user's name, phone number, and e-mail address. Also, the user interface 3420 for inputting user identification information may be linked with a user list stored in the device or the relay server 1000 .

Upon receiving the input of the second user inputting the provider, the second device 200 may request the relay server 1000 to set the user selected by the second user as the provider of the second user. The provider setting request may include the ID of the first user and the ID of the second user registered in the relay server 1000 .

In addition, the second device 200 may request the relay server 1000 to set the folder selected by the second user as the receiving folder, and to set the user input by the second user as a provider for the receiving folder. have. In this case, the provider setting request may include IDs of the first and second users registered in the relay server 1000 and location information indicating the location of the selected folder.

Upon receiving the provider setting request, the relay server 1000 sets the ID of the first user registered in the relay server 1000 to the second user's ID in response to the ID of the second user registered in the relay server 1000 . It can be set as a provider.

35 is a flowchart illustrating a method for the relay server 1000 to receive a provider setting request from the second device 200 according to an embodiment of the present invention.

In operation S3510 , the second device 200 may request the relay server 1000 to set the first user selected by the second user as the provider of the second user.

The provider setting request may include the ID of the first user and the ID of the second user registered in the relay server 1000 .

In operation S3520, the relay server 1000 may set the first user as a provider of the second user.

For example, the relay server 1000 may store the ID of the first user registered in the relay server 1000 as a provider of the second user in response to the ID of the second user registered in the relay server 1000 . can

FIG. 36 shows a database 2150 about a second user stored in the relay server 1000 as the first user is set as a provider of the second user, according to an embodiment of the present invention.

Referring to FIG. 36 , the relay server 1000 corresponds to the ID 2160 of the second user registered in the relay server 1000 , and serves as a provider of the second user and the first user registered in the relay server 1000 . ID 3610 of .

FIG. 37 is a first diagram in which the relay server 1000 is set to be shared between the first user and the second user as the first user is set in the relay server 1000 as a provider of the second user according to an embodiment of the present invention. It is a flowchart for explaining a method of storing user data in the second cloud storage 3000 .

In operation S3710 , the first device 100 may request the relay server 1000 to share the data of the first user between the first user and the second user.

The sharing setting request between the first user and the second user for at least one of the first user's data stored in the first cloud storage 2000 includes the ID of the first user registered in the relay server 1000 and the relay server 1000 . ) may include the ID of the registered second user and identification information of the data of the first user to be shared. The identification information of the first user's data may include location information indicating the location of the first user's data.

In operation S3720, the relay server 1000 may determine whether the first user is set as the provider of the second user.

For example, when the ID of the first user registered in the relay server 1000 is stored as the provider of the second user corresponding to the ID of the first user registered in the relay server 1000, the relay server 1000 may determine that the first user is set as the provider of the second user.

When the first user is set as the provider of the second user in step S3730, the relay server 1000 requests the first cloud storage 2000 to share data of the first user set between the first user and the second user in step S3730 can

In step S3735 , the first cloud storage 2000 may determine whether the relay server 1000 has access to the data of the first user in the first cloud storage 1000 requested from the relay server 1000 . have.

When the relay server 1000 has access to the data of the first user in step S3735 , in step S3740 , the first cloud storage 2000 relays the data of the first user requested from the relay server 1000 . may be transmitted to the server 1000 .

In operation S3750, the relay server 1000 may request the second cloud storage 3000 to store the first user's data shared between the first user and the second user in the storage space of the second user.

The relay server 1000 may request the second cloud storage 3000 to store the data of the first user received from the first cloud storage 2000 in the storage space of the second user in the second cloud storage 3000 . .

In operation S3760 , the second cloud storage 3000 may determine whether the relay server 1000 has the right to store data in the storage space of the second user in the second cloud storage 3000 .

If the relay server 1000 has the right to store data in the storage space of the second user in the second cloud storage 3000 in step S3760, in step S3770, the second cloud storage 3000 is the first user The data of the first user set to be shared between the user and the second user may be stored corresponding to the second user.

Accordingly, as the second user is set as the provider of the first user, the relay server 1000 directly transfers the data of the first user to the storage space of the second user without the request of the second user through the second cloud story. can be saved

38 is a diagram showing the second cloud storage 3000 without the request of the second user, according to an embodiment of the present invention, as data of the first user set to be shared between the first user and the second user is stored in the second cloud storage 3000; The cloud storage 3000 is a flowchart for explaining a method of transmitting the data of the first user copied from the first cloud storage 2000 to the second device 200 .

In operation S3810, the second cloud storage 3000 may store data of the first user shared between the first user and the second user.

The relay server 1000 may request the second cloud storage 3000 to store the data of the first user shared between the first user and the second user as the data of the second user, without the request of the second user. .

The second cloud storage 3000 receives the first user's data shared between the first user and the second user from the relay server 1000 and stores it in the second cloud storage 3000 as the second user's data. can

In operation S3820 , the second cloud storage 3000 may transmit the first user's data shared between the first user and the second user to the second device 200 .

For example, when the second cloud storage 3000 and the second device 200 synchronize data, as data of the first user is stored in the second cloud storage 3000 , the second cloud storage 3000 . may transmit data of the first user stored in the second cloud storage 3000 to the second device 200 .

In operation S3830 , the second device 200 may store the first user's data shared between the first user and the second user in the second device 200 .

The second device 200 may store, in the second device 200 , data of the first user that is set to be shared between the first user and the second user, received from the second cloud storage 3000 .

FIG. 39 is a diagram showing the second cloud storage 3000 without the request of the second user, according to another embodiment of the present invention, as data of the first user set to be shared between the first user and the second user is stored in the second cloud storage 3000; It is a flowchart for explaining a method in which the device 200 receives data of the first user stored in the second cloud storage 3000 .

In operation S3910 , the second cloud storage 3000 may store data of the first user shared between the first user and the second user.

The relay server 1000 may request the second cloud storage 3000 to store the data of the first user shared between the first user and the second user as the data of the second user, without the request of the second user. .

The second cloud storage 3000 receives the first user's data shared between the first user and the second user from the relay server 1000 and stores it in the second cloud storage 3000 as the second user's data. can

In operation S3920 , the second cloud storage 3000 may transmit a list of first user data shared between the first user and the second user to the second device 200 .

For example, when the second cloud storage 3000 and the second device 200 synchronize the list of data, as the first user's data is stored in the second cloud storage 3000, the second cloud storage ( The 3000 may transmit a list of data of the first user stored in the second cloud storage 3000 to the second device 200 . The list of data may include attribute information of data.

In step S3930 , the second device 200 may store in the second device 200 a list of data of the first user shared between the first user and the second user.

The second device 200 may store the list of data of the first user received from the second cloud storage 3000 in the second device 200 .

In operation S3940, the second device 200 may receive a user input for selecting at least one of the first user's data shared between the first user and the second user.

The second device 200 may display a list of data of the first user received from the second cloud storage 3000 on the screen. Also, the second device 200 may receive a user input for selecting at least one from a list of data displayed on the screen.

In operation S3950 , the second device 200 may request the data selected by the second user from the second cloud storage 3000 .

In operation S3960 , the second cloud storage 3000 may transmit data requested from the second device 200 to the second device 200 .

In operation S3970 , the second device 200 may store data received from the second cloud storage 3000 in the second device 200 .

40 is a diagram illustrating a relay server 1000 as data of a first user is stored in a storage space of a second user in the second cloud storage 3000 according to a sharing request of the first user, according to an embodiment of the present invention. ) shows a database about the data of the first user stored in .

Referring to FIG. 40 , the relay server 1000 corresponds to the data identification information of the first user in the database 1600 about the data of the first user, the recipient 1622 of the data, the cloud storage identification information to which the data is copied ( 4010) and location information 4020 indicating the location of the copied data may be recorded.

41 is a diagram for explaining synchronization between the first device 100 and the second device 200 for data shared between the first user and the second user, according to an embodiment of the present invention.

Referring to FIG. 41 , the first device 100 and the second device 200 may synchronize data shared between the first user and the second user.

For example, as the Dropbox_user1_FILE1 file stored in the first device 100 is changed, the first device 100 may synchronize the changed Dropbox_user1_FILE1 file with the first cloud storage 2000 . As the first cloud storage 2000 receives and stores the changed Dropbox_user1_FILE1 file from the first device 100 , the first cloud storage 2000 may notify the relay server 1000 that the Dropbox_user1_FILE1 file has been changed. Accordingly, the relay server 1000 may receive the changed Dropbox_user1_FILE1 file from the first cloud storage 2000 . In addition, the relay server 1000 obtains location information indicating the location of the folder of the second user in the second cloud storage 3000 to which the Dropbox_user1_FILE1 file is copied, and changes the Dropbox_user1_FILE1 file previously stored in the second cloud storage 3000 Dropbox_user1_FILE1 file can be updated. As the Dropbox_user1_FILE1 file is updated in the second user's folder in the second cloud storage 3000 , the second cloud storage 3000 may transmit the updated Dropbox_user1_FILE1 file to the second device 200 . The second device 200 may receive the updated Dropbox_user1_FILE1 file from the second cloud storage 3000 and change the Dropbox_user1_FILE1 file pre-stored in the second device 200 to the updated Dropbox_user1_FILE1 file. Accordingly, data of the first user stored in the first cloud storage 2000 shared between the first user and the second user may be synchronized between the first device 100 and the second device 200 .

Also, even when the data of the second user in the second device 200 is changed, the data of the second user in the second cloud storage 3000 shared between the first user and the second user is transferred to the first device 100 . and the second device 200 may be synchronized.

42A is a diagram illustrating a user interface for setting synchronization provided by the first device 100 according to an embodiment of the present invention.

Referring to FIG. 42A , the first device 100 may set a synchronization method for each of the first user's data shared between the first user and the second user.

The first device 100 may receive a user input for selecting at least one of the first user's data stored in the first cloud storage 2000 . Upon receiving a user input for selecting at least one of the data of the first user, the first device 100 determines whether the selected data is data shared with the second user and whether the first user is the owner of the selected data can do. Whether the data is shared with the second user and whether the first user is the owner of the selected data may be stored in the first device 100 corresponding to the data.

When the selected data is data shared with the second user and the first user is the owner of the selected data, the first device 100 may display a synchronization setting menu for the selected data. As a user input of touching the synchronization setting menu is received, the first device 100 may display a user interface 4210 for selecting a synchronization method for the selected data.

The user interface 4210 for selecting a synchronization method may include a user interface for selecting one of a method in which only the owner can synchronize the selected data and a method in which both the owner and the sharer can synchronize.

In the method that only the owner synchronizes the selected data, the changed file is updated in the files of the sharers only when the owner changes the shared data, and when the sharer changes the shared data, the changed file is transferred to the It can mean one-way sync that doesn't update files.

On the other hand, the method that both the owner and the sharer can synchronize means that the changed file is updated in the file of the owner or other sharer not only when the owner changes the shared data, but also when the sharer changes the shared data. can do.

The first device 100 may receive, from the first user, a user input for selecting one of a method in which only the owner can synchronize and a method in which both the owner and the sharer can synchronize. Also, the first device 100 may store the synchronization method set by the first user in response to the selected data in the relay server 1000 . Accordingly, when the data of the first user shared between the first user and the second user is changed, the relay server 1000 synchronizes the changed data with the second cloud storage 3000 based on the synchronization method set for the changed data. can do.

42B is a diagram illustrating a user interface for setting synchronization provided by the first device 100 or the second device 200 according to another embodiment of the present invention.

Referring to FIG. 42B , the first device 100 may display a user interface for setting or canceling synchronization.

The first device 100 may display a user interface 4220 for setting or canceling synchronization between the relay server 1000 and the second cloud storage with respect to the first user's data.

In response to receiving a user input for canceling synchronization between the relay server 1000 and other cloud storages with respect to the first user's data, the first device 100 connects the first user's data with other cloud storages. A request may be made to the relay server 1000 to release synchronization. Accordingly, the relay server 1000 may not synchronize the data of the first user with other cloud storage.

43 illustrates a database for data of the first user stored in the relay server 1000 as information on a synchronization method is set according to another embodiment of the present invention.

Referring to FIG. 43 , the relay server 1000 may receive synchronization direction information for data of the first user from the first device 100 . Upon receiving the synchronization direction information, the relay server 1000 may store the synchronization direction information 4310 received from the first device 100 in response to the identification information of the first user's data.

Also, the relay server 1000 may receive, from the first device 100 , information on whether to synchronize the relay server 1000 with another cloud storage for the first user's data. Upon receiving the synchronization information 4320 , the relay server 1000 may store synchronization information corresponding to the first user.

44A is a diagram illustrating data of the first user stored in the first cloud storage 2000 and data of the first user stored in the second cloud storage 3000 according to the request of the first user, according to an embodiment of the present invention. A flow chart to illustrate how copies of data are synchronized.

In operation S4410, the first device 100 may receive a user input for changing the file A shared between the first user and the second user.

The file A stored in the first cloud storage 2000 is the original of the file copied from the first cloud storage 2000 to the second cloud storage 3000 by the relay server 1000 according to the sharing setting of the first user. can be

When the first device 100 and the first cloud storage 2000 synchronize data, the file A may be stored in the first device 100 . Also, the first device 100 may receive a user input for changing the file A stored in the first device 100 .

In step S4415 , the first device 100 may request the update of the file A from the first cloud storage 2000 .

When the first device 100 and the first cloud storage 2000 synchronize data, as the file A is changed, the first device 100 changes the file A pre-stored in the first cloud storage 2000 to the changed file. An update to A may be requested from the first cloud storage 2000 .

When an update request for file A is requested, the first device 100 may transmit identification information of the file A and the changed file A to the first cloud storage 2000 .

In operation S4420, the first cloud storage 2000 may update the pre-stored file A to the changed file A.

The first cloud storage 2000 may obtain a storage location of the pre-stored file A based on the identification information of the file A received from the first device 100 . Based on the obtained storage location, the first cloud storage 2000 may update the pre-stored file A to the file A received from the first device 100 .

In step S4425 , the first cloud storage 2000 may transmit event information notifying that the file A of the first user has been changed to the relay server 1000 .

The event information indicating that the file A has been changed may include identification information of the file A. The identification information of the file A may be location information indicating a location where the file A is stored.

In step S4430 , the first cloud storage 2000 may request the file A from the relay server 1000 .

The request for the file A may include identification information of the file A and the ID of the relay server 1000 registered in the first cloud storage 2000 .

In operation S4435 , the first cloud storage 2000 may transmit the changed file A to the relay server 1000 .

The first cloud storage 2000 may determine whether the relay server 1000 has access to the file A based on the ID of the relay server 1000 . As the relay server 1000 determines that it has access to the file A, the first cloud storage 2000 may transmit the changed file A to the relay server 1000 .

In operation S4440 , the relay server 1000 may request an update of the file A from the second cloud storage 3000 .

Upon receiving the file A from the first cloud storage 2000, the relay server 1000 searches the storage space of users whose file A is copied from the database in the relay server 1000 based on the identification information of the file A. can As the storage space of the second user in the second cloud storage 3000 is searched for as the storage space of the users to which the file A is copied, the relay server 1000 stores the storage space of the second user in the second cloud storage 3000 . It is possible to obtain location information indicating the location.

Then, the relay server 1000 may request the second cloud storage 3000 to update the file A of the second user based on the location information indicating the location of the storage space of the second user. The update request for the file A may include identification information of the file A, the changed file A, and the ID of the relay server 1000 registered in the second cloud storage 3000 .

Upon requesting the second cloud storage 3000 to update the file A, the relay server 1000 may update information about the file A shared between the first user and the second user.

For example, the relay server 1000 may update the modification time of the file A and the identification information of the user who changed the file A, which are previously recorded in the database of the relay server 1000 , based on the identification information of the file A. .

In step S4445, the second cloud storage 3000 may update the pre-stored A to the changed file A.

The second cloud storage 3000 may determine whether the relay server 1000 has access to the storage space of the second user based on the ID of the relay server 1000 . Also, the second cloud storage 3000 may acquire a storage location of the pre-stored file A based on the identification information of the file A.

When the relay server 1000 determines that the second user has access to the storage space, the second cloud storage 3000 may update the pre-stored file A with the changed file A received from the relay server 1000 . can

In operation S4450 , the second cloud storage 3000 may request an update of the file A from the second device 200 .

In operation S4455 , the second device 200 may update the pre-stored file A to the file A received from the second cloud storage 3000 .

44B illustrates a method for the relay server 1000 to prohibit writing on data when a second user sets write prohibition on data shared between the first user and the second user, according to an embodiment of the present invention; It is a flowchart to explain.

In operation S4460, the second device 200 may request, from the relay server 1000, write-protection setting for file A among the data of the first user shared by the first user and the second user.

As the second user who is not the owner of the original file sets write-protection on the shared file, the second device 200 may request the relay server to write-protect the shared file.

The write-protection setting may refer to a setting in which a file of a user who has set a write-protection setting from being changed by a user other than a write-protected user changes a write-protected file.

Also, the write-protection setting may refer to a setting in which a file of users sharing a write-protected file is prevented from being changed by a user other than a write-protected user changing a write-protected file.

File A stored in the second cloud storage 3000 is the number of files copied from the first cloud storage 2000 to the second cloud storage 3000 by the relay server 1000 according to the sharing setting of the first user. have. When the second device 200 and the second cloud storage 3000 synchronize data, the file A may be stored in the second device 200 .

Also, the second device 200 may receive an input of a second user for setting write-protection on the file A stored in the second device 200 . The write-protection setting for the file A may be setting a partial area to be write-protected among the entire data of the file A. For example, when file A is a document, write-protection settings may be set for only some of the contents of the document. Also, when the file A is a moving picture, a write-protection setting may be set for a frame in a specific time region among frames of the moving picture. Upon receiving a user input for setting a partial area to be write-protected among all data of the file A, the second device 200 may determine the location of the set partial area within the file A.

Upon receiving the input of the second user for setting the write-protection on the file A, the second device 200 may request the relay server 1000 to set the write-protection on the file A. The write prohibition setting request for the file A may include identification information of the file A and the ID of the second user registered in the relay server 1000 .

Also, the second device 200 may request the relay server 1000 to prohibit write on a partial area of the file A. In this case, the write-protection request for the partial area of the file A includes not only the identification information of the file A, the ID of the second user registered in the relay server 1000, but also the location of the write-protected partial area within the file A. Indicative information may be further included.

In step S4462 , the relay server 1000 may set write prohibition on the file A.

Upon receiving the write prohibition setting request for the file A from the second device 200 , the relay server 1000 may set the write prohibition setting for the file A. For example, the relay server 1000 may store a write prohibition setting value in response to the identification information of the file A. Also, the relay server 1000 may store information indicating the location of a portion of the file A for which write-protection is requested, in response to the identification information of the file A. Also, in response to the identification information of the file A, the ID of the second user who requested write-protection may be stored as the user who requested write-protection.

In operation S4464, the first device 100 may receive a user input for changing the file A shared between the first user and the second user.

For example, when the file A is a document file, the first device 100 may receive a user input for changing the content in the file A.

In operation S4466 , the first device 100 may request an update of the file A from the first cloud storage 2000 .

The update request for the file A may include identification information of the file A, the ID of the first user registered in the first cloud storage 2000, and information indicating the location of the changed area in the file A.

In operation S4467, the first cloud storage 2000 may update the pre-stored file A to the changed file A.

In step S4468 , the first cloud storage 2000 may request synchronization of the file A from the relay server 1000 .

After write-protection on file A is set in the relay server 1000 in response to the second user, as the file A pre-stored in the first cloud storage 2000 is changed, the first cloud storage 2000 is the relay server A request may be made to synchronize file A indicating that file A has changed from 1000 . The synchronization request for file A may include identification information of file A. Also, the synchronization request for the file A may include information indicating the location of the changed data among the data of the file A.

In operation S4470, the relay server 1000 may determine whether the changed data in the file A is data of a write-protected area.

Upon receiving the synchronization request for the file A from the first cloud storage 2000 , the relay server 1000 may determine whether write-protection is set for the file A. For example, the relay server 1000 may determine whether a write prohibition setting value is stored in response to the identification information of the file A. When the write-protection setting value is stored in response to the identification information of the file A, the relay server 1000, based on the information indicating the location of the changed data among the data of the file A, the area where the changed data of the file A is write-protected data can be determined. For example, it may be determined whether the location of the changed data among the data of the file A is included in the location of the write-protected area.

When the changed data of the file A is data in the write-protected area, the relay server 1000 may not synchronize the changed file A in the first cloud storage 2000 with the second cloud storage 3000 .

When the changed data of the file A is not the data of the write-protected area, the relay server 1000 may synchronize the changed file A in the first cloud storage 2000 with the second cloud storage 3000 .

In step S4472 , when the changed data in the file A is data of a write-protected area, the relay server 1000 may request the file A from the second cloud storage 3000 .

When the changed data in the file A is data in the write-protected area, the relay server 1000 may request the same file A as the original file from the second cloud storage to roll back the updated file A to the first cloud storage. .

In operation S4474 , the second cloud storage 3000 may transmit the file A to the relay server 1000 .

In step S4476 , the relay server 1000 may request the first cloud storage 2000 to roll back the updated file A based on the copy of the file A received from the second cloud storage 3000 .

In step S4478, the first cloud storage 2000 may roll back the updated file A based on the received copy of the file A.

For example, the first cloud storage 2000 may delete the updated file A and store the received copy of the file A as the file A. Also, for example, the first cloud storage 2000 may roll back only the write-protected area in the updated file A to the original before the change, based on the received copy of the file A.

In step S4480 , the first cloud storage 2000 may request the first device 100 to roll back the updated file A. As the updated file A stored in the first cloud storage 2000 is rolled back, the first cloud storage 2000 may synchronize the rolled-back file A with the file A stored in the first device 100 . .

For example, the first cloud storage 2000 transmits an event indicating that the updated file A has been changed to the first device 100 , and the first device 100 receives the event and the first cloud storage 200 ) can receive the rolled back file A, and change the updated file A to the rolled back file A.

FIG. 44C is a diagram showing that, according to another embodiment of the present invention, as the second device 200 sets write prohibition on data shared between the first user and the second user, the relay server 1000 prevents writing of the data. It is a flowchart for explaining the method of prohibition.

In operation S4490, the second device 200 may request, from the relay server 1000, write-protection setting for file A among the data of the first user shared by the first user and the second user. In step S4492 , the relay server 1000 may set write prohibition on the file A. In operation S4494, the first device 100 may receive a user input for changing the file A shared between the first user and the second user. Steps S4490 to S4494 may be described with reference to steps S4460 to S4464 of FIG. 44B .

In operation S4496, the first device 100 may request the relay server 1000 to check whether the file A is write-protected.

In operation S4498, the relay server 1000 may transmit to the first device 100 that the file A is set to be write-protected.

In this case, when only a portion of the file A is write-protected, the relay server 1000 may transmit information about the location of the write-protected area to the first device 100 .

In operation S4499, the first device 100 may display the content of the file A in read-only manner.

For example, even if a user input for changing the displayed content of the file A is received, the first device 100 may not change the file A.

Also, according to an embodiment, as the file A is write-protected, the relay server 1000 may receive an event indicating that the file A is write-protected to the first device 100 . As the first device 100 receives a user input for selecting the file A, the first device 100 does not check whether the file A is write-protected to the relay server 1000, and transmits the contents of the file A based on information indicated by the received event. can be displayed.

45A is a diagram illustrating data of a first user stored in the first cloud storage 2000 and data of the first user stored in the second cloud storage 3000 according to a request of a second user, according to an embodiment of the present invention. A flow chart to illustrate how copies of data are synchronized.

In operation S4510, the second device 200 may receive a user input for changing the file A shared between the first user and the second user.

The file A stored in the second cloud storage 3000 is a copy of the file copied from the first cloud storage 2000 to the second cloud storage 3000 by the relay server 1000 according to the sharing setting of the first user. can be

When the second device 200 and the second cloud storage 3000 synchronize data, the file A may be stored in the second device 200 . Also, the second device 200 may receive a user input for changing the file A stored in the second device 200 .

In step S4515 , the second device 200 may request an update of the file A from the second cloud storage 3000 .

When the second device 200 and the second cloud storage 3000 synchronize data, as the file A is changed, the second device 200 changes the file A pre-stored in the second cloud storage 3000 to the changed file. A request may be made to the second cloud storage 3000 to update to A.

When an update request for file A is requested, the second device 200 may transmit identification information of the file A and the changed file A to the second cloud storage 3000 .

In step S4520, the second cloud storage 3000 may update the pre-stored file A to the changed file A.

The second cloud storage 3000 may acquire a storage location of the pre-stored file A based on the identification information of the file A received from the second device 200 . Based on the obtained storage location, the second cloud storage 3000 may update the pre-stored file A to the file A received from the second device 200 .

In step S4525 , the second cloud storage 3000 may transmit event information notifying that the file A of the second user has been changed to the relay server 1000 .

The event information indicating that the file A has been changed may include identification information of the file A. The identification information of the file A may be location information indicating a location where the file A is stored.

In step S4530 , the second cloud storage 3000 may request the file A from the relay server 1000 .

The request for the file A may include identification information of the file A and the ID of the relay server 1000 registered in the second cloud storage 3000 .

In step S4535 , the second cloud storage 3000 may transmit the changed file A to the relay server 1000 .

The second cloud storage 3000 may determine whether the relay server 1000 has access to the file A based on the ID of the relay server 1000 . When it is determined that the relay server 1000 has access to the file A, the second cloud storage 3000 may transmit the changed file A to the relay server 1000 .

In operation S4540, the relay server 1000 may request the first cloud storage 2000 to update the file A.

Upon receiving the file A from the second cloud storage 3000, the relay server 1000 searches the storage space of users whose file A is copied from the database in the relay server 1000 based on the identification information of the file A. can As the storage space of the first user in the first cloud storage 2000 is searched for as the storage space of the users to which the file A is copied, the relay server 1000 stores the storage space of the first user in the first cloud storage 2000. It is possible to obtain location information indicating the location.

Then, the relay server 1000 may request the first cloud storage 2000 to update the file A of the first user to the changed file A, based on the location information indicating the location of the storage space of the first user. The update request for the file A may include identification information of the file A, the changed file A, and the ID of the relay server 1000 registered in the first cloud storage 2000 .

Upon requesting the first cloud storage 2000 to update the file A, the relay server 1000 may update information about the file A shared between the first user and the second user.

For example, the relay server 1000 may update the modification time of the file A and the identification information of the user who changed the file A, which are previously recorded in the database of the relay server 1000 , based on the identification information of the file A. .

In step S4545, the first cloud storage 2000 may update the pre-stored A to the changed file A.

The first cloud storage 2000 may determine whether the relay server 1000 has access to the storage space of the first user based on the ID of the relay server 1000 . Also, the first cloud storage 2000 may obtain a storage location of the pre-stored file A based on the identification information of the file A.

When the relay server 1000 determines that the first user has access to the storage space, the first cloud storage 2000 may update the pre-stored file A with the changed file A received from the relay server 1000 . can

In operation S4550 , the first cloud storage 2000 may request an update of the file A from the first device 100 .

In step S4555 , the first device 100 may update the pre-stored file A to the file A received from the first cloud storage 2000 .

45B is a method for the relay server 1000 to prohibit writing on data when the first user sets write prohibition on data shared between the first user and the second user, according to an embodiment of the present invention; It is a flowchart to explain.

In operation S4560 , the first device 100 may request the relay server 1000 to set write-protection on file A among data of the first user shared by the first user and the second user.

As the first user who is the owner of the original file sets write-protection on the shared file, the first device 100 may request the relay server to write-protect the shared file.

The file A stored in the first cloud storage 2000 is the original of the file copied from the first cloud storage 2000 to the second cloud storage 3000 by the relay server 1000 according to the sharing setting of the first user. can be When the first device 100 and the first cloud storage 2000 synchronize data, the file A may be stored in the first device 100 .

In step S4562 , the relay server 1000 may set write prohibition on the file A. In operation S4564, the second device 200 may receive a user input for changing the file A shared between the first user and the second user. In operation S4566 , the second device 200 may request an update of the file A from the second cloud storage 3000 . In operation S4568, the first cloud storage 2000 may update the pre-stored file A to the changed file A. In step S4570 , the second cloud storage 3000 may request the relay server 1000 to synchronize the file A. In operation S4572, the relay server 1000 may determine whether the changed data in the file A is data of a write-protected area. In step S4574 , when the changed data in the file A is data of a write-protected area, the relay server 1000 may request the file A from the first cloud storage 2000 . In step S4576 , the first cloud storage 2000 may transmit the file A to the relay server 1000 . In step S4578 , the relay server 1000 may request the second cloud storage 3000 to roll back the updated file A based on the copy of the file A received from the first cloud storage 2000 . In step S4580, the second cloud storage 3000 may roll back the updated file A based on the received copy of the file A. In step S4582, the second cloud storage 3000 may request the second device 200 to roll back the updated file A. Steps S4562 to S4582 may be described with reference to steps S4462 to S4480 of FIG. 44B.

46 illustrates a user interface for limiting functions for data to be shared, according to an embodiment of the present invention.

Referring to FIG. 46 , the first device 100 may display a user interface for limiting the use of data to a person who is provided with data. Restrictions on the use of data may include restrictions on copying of data, printing of data and alteration of data, and the like.

The first device 100 may receive a user input for selecting data to be shared among the first user's data stored in the first cloud storage 2000 . Upon receiving a user input for selecting data to be shared among the data of the first user, the first device 100 limits the use of data to a person who is provided with a user interface 4610 for selecting a user to share and data may display a user interface 4620 for

When the data is a file or a folder, the user interface 4620 for limiting the use of data to a person to whom the data is provided may include a user interface for setting read-only settings and a user interface for setting prohibition of printing. The read-only setting may refer to a setting that prohibits a person providing a file from editing, copying, and pasting a shared file. In addition, the print prohibition setting may refer to a setting that prohibits a person provided with a file from printing a shared file.

After setting a read-only setting or a print prohibition setting for the Dropbox_user1_FOLDER2 folder, which is the data of the first user, upon receiving the first user input for setting sharing for group 1, the first device 100 controls the files in the Dropbox_user1_FOLDER2 folder The relay server 1000 may be requested so that the editing, copying and pasting functions or printing functions are restricted. In addition, the first device 100 may request the relay server 1000 to set the sharing setting of the file in the Dropbox_user1_FOLDER2 folder restricted in use with the group 1.

47 is a flowchart illustrating a method for limiting the use of shared data by the relay server 1000 according to an embodiment of the present invention.

In step S4710, the first device 100 receives a first user input requesting sharing between the first user and the second user by limiting the use range of at least one of the first user's data in the first cloud. can do.

In step S4720 , the first device 100 may request the first cloud storage 2000 to grant access to the relay server 1000 with respect to the selected first user's data. Also, the first device 100 may request location information indicating the location of the first user's data stored in the first cloud storage 2000 from the first cloud storage 2000 .

The relay server 1000 may acquire an access right to the data of the first user requested to be shared. Also, the first device 100 may obtain location information indicating the location of the first user's data.

In step S4730, the first device 100 limits the use range of at least one of the data of the first user in the first cloud to the relay server 1000, so that sharing between the first user and the second user is performed. you can request

The first device 100 includes the URL of the first user's data received from the first cloud storage 2000 , the ID of the first user registered in the relay server 1000 , and the second user registered in the relay server 1000 . ID and information on the usage range set by the first user may be transmitted to the relay server 1000 .

In step S4740 , the relay server 1000 may request the first cloud storage 2000 for data of the first user shared between the first user and the second user.

In operation S4730 , the first cloud storage 2000 may transmit the first user's data requested from the relay server 1000 to the relay server 1000 .

In operation S4760, the relay server 1000 may perform a process of limiting the use range of the first user's data shared between the first user and the second user.

For example, when a read-only setting is requested for the first user's data shared between the first user and the second user, the relay server 1000 may store the first user's data received from the first cloud storage 2000. In contrast, the file can be encrypted to prevent a second user from editing, copying, and pasting it.

Also, the relay server 1000 may store information indicating that the read-only function is set in response to the first user's data shared between the first user and the second user.

In operation S4770 , the relay server 1000 may transmit the data of the first user whose use range is limited to the second cloud storage 3000 .

In operation S4780 , the second cloud storage 3000 may store data of the first user with a limited use range.

In operation S4790 , the second cloud storage 3000 may transmit the data of the first user whose use range is limited to the second device 200 .

Accordingly, the first user may share the data whose use range is limited with the second user. For example, when a read-only function is set for the data of the first user, the second user can only view the data of the first user in the second device 200 and change or copy the data of the first user may not be able to

48 is a diagram illustrating a user interface for setting read prohibition on a portion of data to be shared, according to an embodiment of the present invention.

Referring to FIG. 48 , the first device 100 may display the contents 4810 of the first user's file stored in the first cloud storage 2000 .

When the content 4810 of the first user's file stored in the first cloud storage 2000 is displayed, according to the first user input, the first device 100 sets read-protection on a portion of the displayed content. A menu 4820 for doing this may be displayed.

Upon receiving an input for selecting a menu 4820 for setting read prohibition for a portion of the displayed content, the first device 100 displays a user interface ( 4840) can be displayed.

The first device 100 may receive an input of the first user for selecting a portion for which read prohibition is to be set. Upon receiving the input of the first user for selecting the portion to be read-protected, the first device 100 may distinguish and display the portion selected by the first user from the unselected portion.

Also, according to the first user input, the first device 100 may display a menu 4830 for displaying a user interface for selecting a second user to share the displayed content.

Upon receiving a user input of selecting a menu 4830 for displaying a user interface for selecting a second user to share the displayed content with, the first device 100 selects a second user with whom to share the displayed content. A user interface 4850 for selection may be displayed.

A user interface 4850 for selecting a second user to share the displayed content includes an interface for selecting a second user and a user interface for selecting whether to apply read prohibition set to the content for the selected second user ( 4860).

Upon receiving the first user input for determining whether to apply the read prohibition to the second user to be shared and the second user to be shared, the first device 100 , in the relay server 1000 , provides a second You can request sharing between the first user and the second user. In this case, the first device 100 may request, from the relay server 1000 , read prohibition processing on the contents of the file for a user to which the read prohibition is applied among the second users.

49 is a flowchart illustrating a method of sharing data by setting read prohibition on a portion of data to be shared, according to an embodiment of the present invention.

In operation S4910, the first device 100 may receive a first user input requesting sharing between the first user and the second user by setting a portion of the content of the file of the first user to be read-protected.

In step S4920, the relay server 1000 may acquire an access right to the shared-requested data of the first user. In addition, the first device 100 may obtain location information indicating the location of the first user's data requested to be shared.

In step S4930, the first device 100 sets, to the relay server 1000, a portion of the contents of the first user's file to be read-prohibited, and shares the read-prohibited file between the first user and the second user. you can request

The first device 100 includes the URL for the first user file received from the first cloud storage 2000 , the ID of the first user registered in the relay server 1000 , and the second user registered in the relay server 1000 . ID and information on the location of the read-prohibited portion among the contents of the file may be transmitted to the relay server 1000 .

In operation S4940 , the relay server 1000 may request the first user's file shared between the first user and the second user from the first cloud storage 2000 .

In operation S4930 , the first cloud storage 2000 may transmit the file of the first user requested from the relay server 1000 to the relay server 1000 .

In operation S4960, the relay server 1000 may delete a portion of the content of the file of the first user that is set to be shared between the first user and the second user, which is set to be read-protected.

The relay server 1000 may delete the read-prohibited portion of the file of the first user received from the first cloud storage 2000 based on information about the location of the read-prohibited portion.

For example, as shown in FIG. 50A , the relay server 1000 may change the data value of the read-prohibited portion 5010 of the contents 5010 of the file to a predefined noise value 5020 . Also, as shown in FIG. 50B , the relay server 1000 deletes the read-prohibited portion 5010 of the contents of the file, and connects the remaining portions of the file except for the deleted portion to create one file. may be

In operation S4970 , the relay server 1000 may transmit the file of the first user from which the read-protected portion is deleted to the second cloud storage 3000 .

In operation S4980 , the second cloud storage 3000 may store the file of the first user from which a read-protected portion is deleted.

In operation S4990 , the second cloud storage 3000 may transmit the file of the first user from which the read-protected portion is deleted to the second device 200 .

Accordingly, the second user can view only a portion of the file A of the first user that is not set to be read-protected.

FIG. 51 is a flowchart illustrating a method of releasing the read prohibition of data of a first user provided to a second user with a portion of which is read-protected, according to an embodiment of the present invention.

In step S5110 , the first device 100 may request the relay server 1000 to release the read prohibition on the file A of the first user shared by the first user and the second user.

In operation S5120 , the relay server 1000 may request the first cloud storage 2000 for the file A of the first user shared by the first user and the second user.

In step S5130 , the first cloud storage 2000 server may transmit the original file A of the first user shared by the first user and the second user to the relay server 1000 .

In step S5140 , the relay server 1000 requests the second cloud storage 3000 to update the file A stored in the second cloud with the original file A received from the first cloud storage 2000 as a part of the relay server 1000 is read-protected. can

In operation S5150 , the second cloud storage 3000 may update the partially read-protected file A to the original file A received from the relay server 1000 .

In operation S5160 , the second cloud storage 3000 may request the second device 200 to update the file A, which is partially read-protected, to the original file A.

As the second device 200 updates the partially read-protected file A pre-stored in the second device 200 to the original file A, the second user can view all of the contents of the file A.

52 is a diagram illustrating data of a first user in the relay server 1000 or data of a second user in the second cloud storage 3000 when the relay server 1000 provides a cloud storage function according to an embodiment of the present invention. It is a diagram for explaining a method of sharing data between a first user and a second user.

Referring to FIG. 52 , the relay server 1000 may be a cloud storage that provides a storage function to users based on their accounts.

The relay server 1000 may operate so that the first user and the second user can share data of the first user in the relay server 1000 . For example, upon receiving a sharing request for sharing the data of the first user with the second user, the relay server 1000 transfers the data of the first user in the relay server 1000 to the data of the second user in the cloud storage 3000 . It can be stored in the storage space of the second user. Accordingly, the second user may acquire the data of the first user shared between the first user and the second user through the second cloud storage 3000 .

Also, the relay server 1000 may operate so that the first user and the second user can share data of the second user in the second cloud storage 3000 . For example, the relay server 1000 may store the data of the second user in the second cloud storage 3000 in the storage space of the first user of the relay server 1000 .

Also, the relay server 1000 may copy the first user's data and the first user's data in the relay server 1000 to synchronize the first user's copy with the storage space of the second user in the second cloud storage. For example, as the data of the first user in the relay server 1000 is changed, the relay server 1000 converts a copy of the data of the first user stored in the second cloud storage 3000 to the changed data of the first user. can be updated

Also, the relay server 1000 may set a setting that prohibits the first user or the second user from writing a file shared between the first user and the second user. Also, the relay server 1000 may set a setting that prohibits the first user or the second user from reading a file shared between the first user and the second user.

53 is a diagram illustrating a method in which the relay server 1000 shares data of a first user between a first user and a second user when the relay server 1000 provides a cloud storage function according to an embodiment of the present invention. It is a drawing for explanation.

Referring to FIG. 53 , the first user may set sharing between the first user and the second user for S Cloud_user1_FOLDER2 among the data of the first user in the relay server 1000 in the relay server 1000 . As sharing between the first user and the second user is set for S Cloud_user1_FOLDER2, the relay server 1000 stores the S Cloud_user1_FOLDER2 folder in the relay server 1000 in the second cloud storage 3000 as data of the second user. can be saved

As the first user's S Cloud_user1_FOLDER2 folder in the relay server 1000 is copied as the second user's data in the second cloud storage 3000, the second user's S Cloud_user1_FOLDER2 folder can be mounted on the second user's file system. have.

All data constituting the S Cloud_user1_FOLDER2 folder of the first user in the relay server 1000 may be copied to the second cloud storage 3000 . In addition, only the hierarchical structure of the S Cloud_user1_FOLDER2 folder of 1 user and the attribute information of the files in S Cloud_user1_FOLDER2 may be copied to the 2 cloud storage.

When sharing between the first user and the second user is set for the first user's data, the relay server 1000 stores the first user's data in the second cloud storage 3000 as the second user's data. will be described in detail below with reference to FIGS. 53 to 57 .

54 is a diagram for explaining a method of registering a first user and a second user by the relay server 1000 and the second cloud storage 3000 according to an embodiment of the present invention.

In operation S5410 , the relay server 1000 may receive a registration request for the first user from the first device 100 . The registration request for the first user may include the account of the first user to be registered with the relay server 1000 . The account may include the ID and password of the first user. Upon receiving the registration request for the first user, the relay server 1000 may grant the first user the right to use the resource of the relay server 1000 . For example, the first user may store data in the relay server 1000 based on the account of the first user.

In operation S5420 , the second cloud storage 3000 may receive a registration request for the second user from the second device 200 . Upon receiving the registration request for the second user, the second cloud storage 3000 may grant the second user the right to use the resource of the second cloud storage 3000 .

In operation S5430 , the second cloud storage 3000 may receive a registration request for the relay server 1000 from the relay server 1000 .

The relay server 1000 may be registered as a user in the second cloud storage 3000 . In addition, the relay server 1000 is to be registered in the second cloud storage 3000 as a third party that can use the resources of the second cloud storage 3000 based on the permission of the user of the second cloud storage 3000 . may be Also, when the relay server 1000 is previously registered in the second cloud storage 3000 , the step of registering the relay server 1000 in the second cloud storage 3000 may be omitted.

In operation S5440, the second device 200 may request the relay server 1000 to register the second user from the user. Upon receiving the registration request for the second user, the relay server 1000 may grant the second user the right to use the resource of the relay server 1000 .

In operation S5450 , the relay server 1000 may receive a registration request for the second cloud storage 3000 from the second cloud storage 3000 .

The second cloud storage 3000 may be registered as a user in the relay server 1000 . Also, the second cloud storage 3000 may be registered in the relay server 1000 as a third party that can use the resources of the relay server 1000 based on the permission of the user of the relay server 1000 . Also, when the second cloud storage 3000 is previously registered with the relay server 1000 , the step of registering the second cloud storage 3000 with the relay server 1000 may be omitted.

55 is a diagram for explaining a method in which the second device 200 registers a folder of a second user in the second cloud storage 3000 as a receiving folder in the relay server 1000 according to an embodiment of the present invention Show the flow chart.

The reception folder may mean a folder in which data to be received from the relay server 1000 is stored.

In operation S5510 , the second device 200 may receive a second user's input for setting one of the second user's folders in the second cloud storage 3000 as a receiving folder.

In operation S5520 , the second device 200 may request the second cloud storage 3000 to share settings between the second user and the relay server 1000 for the folder selected by the second user.

The sharing setting request includes the ID of the second user registered in the second cloud storage 3000 , the ID of the relay server 1000 registered in the second cloud storage 3000 , and identification information on the folder selected by the second user may include.

Also, the second device 200 may request location information indicating the location of the folder selected by the second user from the second cloud storage 3000 .

In operation S5530 , the second cloud storage 3000 may set sharing between the second user and the relay server 1000 for the folder selected by the second user.

For example, the second cloud storage 3000 may set the ID of the relay server 1000 registered in the second cloud storage 3000 as the ID of the sharer for the folder selected by the second user.

In operation S5540 , the second cloud storage 3000 may transmit location information indicating the location of the folder selected by the second user to the second device 200 .

The location information indicating the location of the folder may include a URL of the folder.

In operation S5550 , the second device 200 may request the relay server 1000 to set the folder selected by the second user as the receiving folder of the second user.

The reception folder setting request may include location information indicating the location of the folder and the ID of the second user registered in the relay server 1000 .

In operation S5560 , the relay server 1000 may store the folder selected by the second user as the receiving folder of the second user in the relay server 1000 .

For example, the relay server 1000 may store location information indicating the location of a folder selected by the second user as location information of the receiving folder, corresponding to the ID of the second user registered in the relay server 1000 .

56 is a diagram illustrating a relay server 1000 in response to receiving a sharing request for sharing data of a first user with a second user from the first device 100 according to an embodiment of the present invention. It is a flowchart for explaining a method of storing the data of the first user in the storage space of the second user.

In operation S5610 , the first device 100 may receive a first user input for setting sharing between the first user and the second user for at least one of the first user's data in the relay server 1000 .

In operation S5620 , the first device 100 may request the relay server 1000 to set sharing between the first user and the second user for at least one of the first user's data in the relay server 1000 .

The first device 100 may request to share at least one of the data of the first user in the relay server 1000 selected by the first user with the second user.

The sharing setting request between the first user and the second user for the data of the first user is made by the ID of the first user registered in the relay server 1000, the ID of the second user registered in the relay server 1000, and the first user. It may include identification information of the selected data of the first user in the relay server 1000 .

In operation S5630 , the relay server 1000 may set sharing between the first user and the second user for at least one of the first user's data in the relay server 1000 .

The relay server 1000 relates to at least one of the data of the first user in the relay server 1000 selected by the first user based on the identification information of the data of the first user received from the first device 100 . You can set up sharing between the first user and the second user.

In step S5640 , the relay server 1000 stores the data of the first user in the relay server 1000 shared between the first user and the second user in the storage space of the second user in the second cloud storage 3000 . may be requested from the second cloud storage 3000 .

The relay server 1000 may store location information indicating the location of the storage space of the second user corresponding to the ID of the second user registered in the relay server 1000 . For example, in the relay server 1000 , in response to the ID of the second user registered in the relay server 1000 , the folder of the second user in the second cloud storage 3000 is stored as the receiving folder of the second user. may have been

The relay server 1000 includes location information indicating the location of the storage space of the second user, the ID of the relay server 1000 registered in the second cloud storage 3000 , and the second user registered in the second cloud storage 3000 . Using the ID of , it is possible to request the second cloud storage 3000 to store the data of the first user in the storage space of the second user.

In step S5650 , the second cloud storage 3000 may store the data of the first user in the relay server 1000 shared between the first user and the second user in the storage space of the second user.

Upon receiving a storage request for storing the first user's data in the second user's storage space from the relay server 1000 , the second cloud storage 3000 has the right to store data in the second user's storage space It may be determined whether the relay server 1000 exists.

When the relay server 1000 has the authority to store data in the storage space of the second user, the second cloud storage 3000 stores the data of the first user received from the relay server 1000 by the second user. can be stored in space.

57 is a diagram showing a sharing request for sharing data of a second user in a second cloud storage 3000 between a first user and a second user is received from the second device 200 according to an embodiment of the present invention; A flowchart is shown for explaining a method in which the relay server 1000 stores the data of the second user in the second cloud storage 3000 in the relay server 1000 .

In operation S5710 , the second device 200 may receive a user input for setting sharing between the first user and the second user for at least one of the data of the second user in the second cloud storage 3000 .

In step S5720 , the second device 200 shares at least one of the second user's data in the second cloud storage 3000 to the second cloud storage 3000 between the second user and the relay server 1000 . You can send a setup request.

The second device 200 may request the second cloud storage 3000 to share data of the second user in the second cloud storage 3000 selected by the second user with the relay server 1000 .

The sharing setting request is the second user's ID registered in the cloud storage 3000, the ID of the relay server 1000 registered in the cloud storage 3000, and a second in the second cloud storage 3000 selected by the second user. It may include identification information of the user's data.

Also, the second device 200 may request location information selected by the second user indicating the location of the second user's data in the second cloud storage 3000 .

In step S5725 , the second cloud storage 3000 may set sharing between the second user and the relay server 1000 with respect to the data of the second user in the second cloud storage 3000 selected by the second user.

In step S5730 , the second cloud storage 3000 transmits location information indicating the location of the data of the second user in the second cloud storage 3000 shared between the second user and the relay server 1000 to the second device 200 . ) can be transmitted.

In step S5740 , the second device 200 transmits, to the relay server 1000 , a sharing setting request between the first user and the second user for at least one of the data of the second user in the second cloud storage 3000 . can

The second device 200 may request the relay server 1000 to share data of the second user in the second cloud storage 3000 selected by the second user between the first user and the second user.

The sharing request between the first user and the second user includes the ID of the first user registered in the relay server 1000, the ID of the second user registered in the relay server 1000, and location information indicating the location of the data of the second user. may include

In operation S5750 , the relay server 1000 may set sharing between the first user and the second user for at least one of the data of the second user in the second cloud storage 3000 .

In operation S5760 , the relay server 1000 may request data of the second user in the second cloud storage 3000 shared between the first user and the second user from the second cloud storage 3000 .

The second user's request for data includes the ID of the second user registered in the second cloud storage 3000 , the ID of the relay server 1000 registered in the second cloud storage 3000 , and the location of the data of the second user may include location information indicating

In operation S5770 , the second cloud storage 3000 may transmit, to the relay server 1000 , data of the second user in the second cloud storage 3000 set to be shared between the first user and the second user.

The second cloud storage 3000 may determine whether the relay server 1000 has access to the data of the second user requested from the relay server 1000 .

When the relay server 1000 has access to the data of the second user requested from the relay server 1000 , the second cloud storage 3000 is the relay server 1000 requested from the relay server 1000 . Data of the second user may be transmitted.

In operation S5780, the relay server 1000 may store the data of the second user in the second cloud storage 3000 set to be shared between the first user and the second user in the storage space of the first user.

The relay server 1000 may store the data of the second user received from the second cloud storage 3000 in the storage space of the first user.

58 is a view showing the first user's data stored in the first cloud storage 2000 or the second cloud storage 3000 in which the first relay server 1000a and the second relay server 1000b are stored in the first cloud storage 2000, according to an embodiment of the present invention. ) is a diagram for explaining a method of sharing the data of the second user in the first user and the second user.

Referring to FIG. 58 , the first relay server 1000a or the second relay server 1000b receives the first user's data from the first cloud storage 2000 and stores it in the second cloud storage 3000 , or , by receiving the data of the second user from the second cloud storage 3000 and storing the data in the first cloud storage 2000, the data of the first user or the data of the second user is transferred between the first user and the second user. can be shared

The first cloud storage 2000 and the second cloud storage 3000 may be storage operated by different service providers. Also, the first cloud storage 2000 and the second cloud storage 3000 may be referred to as general-purpose cloud storage according to embodiments.

59 is a diagram in which, according to an embodiment of the present invention, the first relay server 1000a and the second relay server 1000b transmit data of the first user stored in the first cloud storage 2000 to the first user and the first user. 2 It is a diagram for explaining a method of saving between users.

Referring to FIG. 59 , the first user uses the first relay server 1000a for Dropbox_user1_FOLDER2 among the data of the first user stored in the first cloud storage 2000 and in the first cloud storage 2000, Sharing between the first user and the second user can be set. As sharing between the first user and the second user is set for Dropbox_user1_FOLDER2 , the first relay server 1000a may receive location information indicating the location of the Dropbox_user1_FOLDER2 folder from the first cloud storage 2000 . Then, the first relay server 1000a may transmit location information indicating the location of the Dropbox_user1_FOLDER2 folder to the second relay server 1000b.

Upon receiving the location information indicating the location of the Dropbox_user1_FOLDER2 folder, the second relay server 1000b may receive the Dropbox_user1_FOLDER2 folder from the first cloud storage 2000 based on the location information indicating the location of the Dropbox_user1_FOLDER2 folder. In addition, the second relay server 1000b may store the Dropbox_user1_FOLDER2 folder in the second cloud storage 3000 .

By storing the first user's data stored in the first cloud storage 2000 in the storage space of the second user in the second cloud storage 3000 by the first relay server 1000a and the second relay server 1000b, the second A method of sharing data of one user between the first user and the second user will be described in detail below with reference to FIGS. 60 to 65 .

60 is a diagram for explaining a method of registering a first user and a second user by the first cloud storage 2000 and the second cloud storage 3000 according to an embodiment of the present invention.

In step S6010 , the first cloud storage 2000 may receive a registration request for the first user from the first relay server 1000a. The registration request for the first user may include the account of the first user to be registered in the first cloud storage 2000 . The account may include the ID and password of the first user. Upon receiving the registration request for the first user, the first cloud storage 2000 may grant the first user the right to use the resource of the first cloud storage 2000 .

In operation S6020 , the second cloud storage 3000 may receive a registration request for the first user from the first relay server 1000a. Upon receiving the registration request for the first user, the second cloud storage 3000 may grant the first user the right to use the resource of the second cloud storage 3000 .

In step S6025, the first relay server 1000a may request the second relay server 1000b to register the first user.

For example, the second relay server 1000b is configured to input information about the first user.

In operation S6030 , the second cloud storage 3000 may receive a registration request for the second user from the second relay server 1000b. Upon receiving the registration request for the second user, the second cloud storage 3000 may grant the second user the right to use the resource of the second cloud storage 3000 .

In operation S6040 , the first cloud storage 2000 may receive a registration request for the second user from the second relay server 1000b. . Upon receiving the registration request for the second user, the first cloud storage 2000 may grant the second user the right to use the resource of the first cloud storage 2000 .

Accordingly, the first user and the second user may be registered as users in the first cloud storage 2000 and the second cloud storage 3000 .

61 is a diagram in which the first relay server 1000a shares at least one data among the data of the first user stored in the first cloud storage 2000 between the first user and the second user according to an embodiment of the present invention. It is a flowchart to explain how to set the .

In step S6110 , the first relay server 1000a may receive a user input for setting sharing between the first user and the second user with respect to at least one of the first user's data stored in the first cloud storage 2000 . .

The first relay server 1000a may receive a user input for selecting at least one of the first user's data stored in the first cloud storage 2000 . Also, the first relay server 1000a may receive a user input for setting sharing between the first user and the second user with respect to the selected data.

In operation S6120, the first relay server 1000a may request the first cloud storage 2000 to share the data of the first user requested to be shared by the first user with the second user.

In step S6130 , the first relay server 1000a may request the first cloud storage 2000 for location information indicating the location of the first user's data requested to be shared by the first user.

The first relay server 1000a may request location information indicating the location of data selected by the first user based on the ID of the first user registered in the first cloud storage 2000 .

In operation S6140 , the first cloud storage 2000 may set sharing between the first user and the second user with respect to the first user's data requested to be shared by the first user.

In operation S6140 , the first cloud storage 2000 may transmit location information indicating the location of the first user's data requested to be shared by the first user to the first relay server 1000a.

62 illustrates a user interface for explaining a method for a first user to transmit location information indicating a location of a file shared between a first user and a second user to a second user, according to an embodiment of the present invention; .

Referring to FIG. 62 , as location information indicating the location of the first user's data stored in the first cloud storage 2000 is received from the first cloud storage 2000 , the first relay server 1000a transmits the first user The user interface 6210 for transmitting the location information indicating the location of the data of the second relay server 1000b may be displayed.

The user interface 6210 for transmitting location information indicating the location of the first user's data to the second relay server 1000b may include an icon for executing an application capable of transmitting text between users. Applications capable of transmitting text between users may include an email application, an SNS application, an SNS web application, and an address book application.

Upon receiving a user input for selecting one of the applications, the first relay server 1000a may execute the selected application. Accordingly, the first user may transmit location information indicating the location of a file shared between the first user and the second user to the second user by using the executed application.

63 is a method for the first relay server 1000a to transmit location information indicating the location of a file shared between the first user and the second user to the second relay server 1000b according to an embodiment of the present invention. A flowchart for explanation is shown.

In step S6310, the first relay server 1000a transmits location information indicating the location of the first user's data stored in the first cloud storage 2000 in which sharing between the first user and the second user is set to the second relay server 1000b ) can be transmitted.

The first user may directly transmit location information indicating the location of the first user's data to the second relay server 1000b by using an application in the first relay server 1000a.

Also, when there is a separate server connecting the first relay server 1000a and the second relay server 1000b corresponding to the first user and the second user, the first relay server 1000a is the first user's Location information indicating the location of data may be automatically transmitted to the second relay server 1000b through the server.

64 is a user interface for the second relay server 1000b to receive the first user's data from the first cloud storage 2000 and store it in the second cloud storage 3000, according to an embodiment of the present invention. shows

Referring to FIG. 64 , the second relay server 1000b transfers the data of the first user stored in the first cloud storage 2000 to the second data of the second cloud storage 3000 based on the input of the second user. You can run an application for saving in the user's storage space.

As the application is executed, the second relay server 1000b provides a user interface 6410 for receiving, from the second user, location information indicating the location of the first user's data stored in the first cloud storage 2000 . can be displayed.

As location information indicating the location of the first user's data stored in the first cloud storage 2000 is received from the second user through the user interface 6410 , the second relay server 1000b is configured to store the first cloud storage 2000 . Data of the first user stored in 2000 may be requested from the first cloud storage 2000 .

The first cloud storage 2000 may transmit the data of the first user requested from the second relay server 1000b to the second relay server 1000b. In addition, the second relay server 1000b may store the first user's data received from the first cloud storage 2000 in the second cloud storage 3000 .

65 illustrates a method for the second relay server 1000b to receive the first user's data from the first cloud storage 2000 and store it in the second cloud storage 3000 according to an embodiment of the present invention. A flow chart is shown to explain.

In step S6510, the second relay server 1000b may request, from the first cloud storage 2000, data of the first user stored in the first cloud storage 2000 shared between the first user and the second user. .

The request for data of the first user stored in the first cloud storage 2000 includes the ID of the second user registered in the first cloud storage 2000 and the data of the first user stored in the first cloud storage 2000 . It may include location information indicating the location.

In step S6520, the first cloud storage 2000 may transmit, to the first relay server 1000a, data of the first user stored in the first cloud storage 2000 shared between the first user and the second user. .

The first cloud storage 2000 may determine whether the second user has access to the data of the first user. When it is determined that the second user has access to the data of the first user, the first cloud storage 2000 may transmit the data of the first user to the second relay server 1000b.

In step S6530 , the second relay server 1000b transfers the data of the first user stored in the first cloud storage 2000 in which sharing between the first user and the second user is set to a second storage space in the second cloud storage 3000 . You can request to save it to .

The second relay server 1000b may store the first user's data received from the first cloud storage 2000 in the second relay server 1000b.

For example, the second relay server 1000b may store the received data of the first user in a folder in the second relay server 1000b that is synchronized with the folder of the second user in the second cloud storage 3000 . . As the received data of the first user is stored in the folder in the second relay server 1000b that is synchronized with the folder of the second user in the second cloud storage 3000, the received data of the first user is transferred to the second cloud It may be uploaded to the folder of the second user in the storage 3000 .

In operation S6540 , the second cloud storage 3000 may store the data of the first user stored in the first cloud storage 2000 in which sharing between the first user and the second user is set.

The second cloud storage 3000 may store data received from the second relay server 1000b in the storage space of the second user.

66 is a block diagram of a relay server 1000 according to an embodiment of the present invention.

As shown in FIG. 66 , the relay server 1000 according to an embodiment may include a control unit 1110 , a communication unit 1200 , and a storage unit 1300 . However, not all illustrated components are essential components. The relay server 1000 may be implemented by more components than the illustrated components, or the relay server 1000 may be implemented by fewer components.

The communication unit 1200 may transmit/receive data to and from an external device. For example, the communication unit 1200 may transmit/receive data to and from the first device 100 , the second device 200 , the first cloud storage 2000 , and the second cloud story.

The storage unit 1300 may store information necessary to share data between the first user and the second user. The storage unit 1300 may include a user database 1310 and a file database 1320 . The user database 1310 may store information about a user registered in the hub server. The file database 1320 may store information about a file registered in the relay server 1000 .

The controller 1110 may control the overall operation of the relay server 1000 .

For example, the controller 1110 may include location information indicating the location of the first user's data stored in the first cloud storage 2000 and location information indicating the location of the storage space of the second user in the second cloud storage 3000 . can be obtained.

Also, the controller 1110 may receive, from the device of the first user, a sharing request for the first user to share the data of the first user with the second user through the communication unit 1200 . The sharing request may be a request to store the data of the first user in the storage space of the second user.

In addition, the control unit 1110, based on the authority of the relay server 1000 to receive the data of the first user from the first cloud storage 2000 through the communication unit 1200, the first cloud storage 2000 ), the first user's data stored in the first cloud storage 2000 may be received.

In addition, the control unit 1110, through the communication unit 1200, based on the authority of the relay server 1000 to store data in the storage space of the second user in the second cloud storage 3000, the second user In the storage space, the received data of the first user may be stored.

In this case, the controller 1110 may store only the attribute information of the file among the data constituting the file of the first user in the second cloud storage 3000 .

In addition, as the controller 1110 receives a request for data of the first user stored in the first cloud storage 2000 from the second cloud storage 3000 , the control unit 1110 in the storage space of the second user 1 You can also store user data.

Also, the controller 1110 may receive, from the first cloud storage 2000 , a synchronization request indicating that the data of the first user stored in the first cloud storage 2000 has been changed.

Also, upon receiving the synchronization request, the controller 1110 may update a copy of the first user's data stored in the second cloud storage 3000 with the changed first user's data. The copy of the data of the first user may mean data in which the data of the first user in the first cloud storage is copied to the storage space of the second user according to a sharing request.

In addition, upon receiving the synchronization request, the controller 1110 determines whether the changed data is write-protected data from the first device 100 , and when the changed data is not write-protected data, the second cloud A copy of the first user's data stored in the storage may be updated with the changed first user's data. In this case, the write-protection setting may mean a setting in which a copy of the data of the first user stored in the storage space of the second user is not changed by the relay server.

Also, the controller 1110 may receive, from the first device 100 , a read prohibition request for a portion of the file among the data of the first user.

Also, in response to receiving the read prohibition request, the controller 1110 receives a read prohibition requested file from the first cloud storage, deletes a read prohibition requested portion of the received files, and stores the second user's storage Partially deleted files can be stored in space.

66 is a diagram illustrating a relay server 1000 in which the relay server 1000 relays message transmission between users using different messenger services when the cloud server is a messenger server according to an embodiment of the present invention.

Referring to FIG. 66 , the first messenger server 2000 and the second messenger server 3000 may be messenger servers operated by different service providers.

The messenger server 2000 or 3000 may transmit a message between users registered in the messenger server 2000 or 3000 to the devices 100 or 200 of the users. In this case, the messenger server 2000 or 3000 may deliver only messages between users set as messenger friends to the messenger server 2000 or 3000 .

In addition, as the messenger server 2000 or 3000 receives a request to add another user as a friend of a specific user from the device 100 or 200, the requesting device 100 or 200 sets the other user as a messenger friend of the specific user. You can check whether you have permission to add.

For example, the first messenger server 2000 may receive a request for adding a third user as a messenger friend of the first user from the relay server 1000 . In this case, the first messenger server 2000 may receive, from the relay server 1000 , permission information for adding another user as a messenger friend of the first user together with the messenger friend addition request. Upon receiving the authority information from the relay server 1000, the first messenger server 2000 determines whether the relay server 1000 has the authority to add the third user as a messenger friend of the first user based on the authority information. can determine whether

The relay server 1000 may relay message transmission between users using different messenger services by connecting the messenger servers 2000 or 3000 to which users have subscribed.

For example, the relay server 1000 may receive, from the first device 100 , permission information for adding another user to the first messenger server 2000 as a messenger friend of the first user. The relay server 1000 may register the relay server 1000 with the first messenger server 2000 as a messenger friend of the first user based on the authority information received from the first device 100 .

Also, the relay server 1000 may receive, from the second device 200 , permission information for adding another user to the second messenger server 3000 as a messenger friend of the second user. The relay server 1000 may register the relay server 1000 with the second messenger server 3000 as a messenger friend of the second user based on the authority information received from the second device 200 .

The relay server 1000 may receive the message of the first user from the first messenger server 2000 as the first messenger friend of the first user. The relay server 1000 may request the second messenger server 3000 as a second messenger friend of the second user to deliver the message of the first user received from the first messenger server 2000 to the second user.

Also, the relay server 1000 may receive the message of the second user from the second messenger server 3000 as the second messenger friend of the second user. The relay server 1000 may request the first messenger server 2000 as a first messenger friend of the first user to deliver the message of the second user received from the second messenger server 3000 to the first user.

Accordingly, the relay server 1000 may relay message transmission between the first user and the second user using different messenger services.

67A is a method for registering an account in the messenger server 2000 or 3000 by the device 100 or 200 and the relay server 1000 and the device 100 or 200 using the relay server 1000 according to an embodiment of the present invention. ) is a flow chart showing how to register an account.

In step S6705 , the relay server 1000 may request the first messenger server 2000 to register the relay server 1000 .

Upon receiving the registration request from the relay server 1000 , the first messenger server 2000 may create a first messenger account of the relay server 1000 and store information about the created account. In this case, the first messenger account of the relay server 1000 may be an account as a third party, not as a user account of the first messenger server 2000 .

In step S6710 , the relay server 1000 may request the second messenger server 3000 to register the relay server 1000 .

Upon receiving the registration request from the relay server 1000 , the second messenger server 3000 may create a second messenger account of the relay server 1000 and store information about the created account. In this case, the second messenger account of the relay server 1000 may be an account as a third party, not as an account as a user of the second messenger server 3000 .

In operation S6715 , the first device 100 may transmit a registration request for the first user to the first messenger server 2000 .

For example, upon receiving the input of the first user executing the application distributed by the service provider of the first messenger server 2000, the first device 100 sends the first user to the first messenger server 2000 You can request registration for

In this case, the first device 100 may transmit the account information of the first user to be registered in the first messenger server 2000 and the address information of the first device 100 to the first messenger server 2000 . The address information of the device may include an IP address of the device or identification information of a device registered in the push server, but is not limited thereto. Also, the account information may include at least one of an ID and a password.

The first messenger server 2000 may register the first user with the first messenger server 2000 as a user subscribed to the first messenger service. In this case, address information of the first device 100 may be stored in response to the first user's account information received from the first device 100 .

In operation S6720 , the second device 200 may transmit a registration request for the second user to the second messenger server 3000 .

In this case, the second device 200 may transmit the account information of the second user to be registered in the second messenger server 3000 and address information of the second device 200 to the second messenger server 3000 .

The second messenger server 3000 may register the second user with the second messenger server 3000 as a user subscribed to the second messenger service. In this case, the second messenger server 3000 may store address information of the second device 200 in response to the account information of the second user received from the second device 200 .

In operation S6725 , the first device 100 may transmit a registration request for the first user to the relay server 1000 .

For example, upon receiving the input of the first user executing the application distributed by the services provider of the relay server 1000 , the first device 100 registers the first user with the relay server 1000 . you can request

In this case, the first device 100 may transmit account information of the first user to be registered in the relay server 1000 to the relay server 1000 .

Also, the first device 100 may transmit information about the first messenger service subscribed by the first user to the relay server 1000 . The information on the first messenger service may include identification information of the first messenger service or address information of the first messenger server 2000 .

Also, the first device 100 may transmit the first user's unique information to the relay server 1000 . The unique information of the first user may include, but is not limited to, the first user's contact information and resident number. The first user's contact information may include, but is not limited to, the first user's phone number and e-mail address.

As the first device 100 receives the first user's account information, the first messenger service information, and the first user's unique information, the relay server 1000 converts the first user to the user of the relay server 1000 . As such, it can be registered in the relay server 1000 . In this case, the relay server 1000 may store information about the first messenger service and unique information of the first user in response to the ID of the first user.

In operation S6730 , the second device 200 may transmit a registration request for the second user to the relay server 1000 .

Step S6730 may be described with reference to step S6725.

FIG. 67B shows a database in which information about a user subscribed to the relay server 1000 is stored, according to an embodiment of the present invention.

Referring to FIG. 67B , the relay server 1000 may store user account information.

In addition, the relay server 1000 receives identification information 6720 of the messenger service subscribed by the user in response to the ID 6710 of the user, the ID 6730 of the user registered in the messenger server, and the user's unique information 6740 can be saved

Also, according to an embodiment, the relay server 1000 may store contact information of people related to the user stored in the user's devices 100 and 200 .

68A is a flowchart illustrating a method in which the relay server 1000 acquires the authority of the first user to the first messenger server 2000 according to an embodiment of the present invention.

In step S6810 , the first device 100 may request the first messenger server 2000 to grant the relay server 1000 a right to add another user as the first messenger friend of the first user.

For example, as shown in FIG. 88B , the first device 100 selects whether to grant the relay server 1000 permission to add another user as the first messenger friend of the first user. A user interface can be provided for

Upon receiving the first user input selecting to grant the relay server 1000 permission to add another user as the first messenger friend of the first user, the first device 100 selects the other user as the first messenger friend. A request may be made to the first messenger server 2000 to grant the relay server 1000 an authority to add the user as a first messenger friend.

In this case, the first device 100 may transmit the first messenger account information of the first user and the first messenger ID of the relay server 1000 to the first messenger server 2000 .

In step S6820 , the first messenger server 2000 may grant the relay server 1000 the right to add another user as the first messenger friend of the first user.

The first messenger server 2000 may authenticate the first user based on the received first messenger account information of the first user. As the first user is authenticated, the first messenger server 2000 may generate authorization information indicating authorization to add another user as a messenger friend of the first user. The first messenger server 2000 may store the generated authorization information in correspondence with the first messenger ID of the first user and the first messenger ID of the relay server 1000 .

In operation S6820 , the first messenger server 2000 may transmit permission information indicating permission to add another user as the first messenger friend of the first user to the first device 100 .

In operation S6840 , the first device 100 may transmit the authorization information received from the first messenger server 2000 to the relay server 1000 to the relay server 1000 .

In this case, the first device 100 may transmit the relay server ID of the first user together with the authorization information to the relay server 1000 .

Also, although not shown, the relay server 1000 may acquire the authority of the second user with respect to the second messenger server 3000 in the same manner.

68B is a diagram illustrating a user interface for granting the first user's authority to the first messenger server 2000 to the relay server 1000 according to an embodiment of the present invention.

Referring to FIG. 68B , the first device 100 may provide a user interface for the relay server 1000 to obtain the first user's authority to the first messenger server 2000 .

As the application distributed by the service provider operating the relay server 1000 is executed, the first device 100 grants the right to add another user as the first messenger friend of the first user to the relay server 1000 A user interface for selecting whether or not to grant to the user may be displayed.

For example, upon receiving a user input for selecting to grant the relay server 1000 an authority to add another user as a messenger friend of the first user, the first device 100 may 2000) to grant permission to the relay server 1000 to add another user as the first messenger friend of the first user.

Upon receiving the authorization request, the first messenger server 2000 may request the first device 100 to authenticate the first user. As the authentication is completed, the first messenger server 2000 generates a web page 6810 for confirming whether to grant the relay server 1000 the right to add another user as a messenger friend of the first user. 1 may be transmitted to the device 100 .

Upon receiving the user input for selecting the confirmation button 6820 , the first device 100 , from the first messenger server 2000 , indicates the right to add another user as the first messenger friend of the first user The information may be received, and the received authorization information may be transmitted to the relay server 1000 .

68C illustrates a database stored by the relay server 1000 upon receiving authorization information from the device 200 or 300 according to an embodiment of the present invention.

Referring to FIG. 68C , the relay server 1000 may store authorization information 6750 indicating authorization to add another user as a user's messenger friend in response to the user's relay server ID.

For example, the relay server 1000 represents the authority to add another user as the first messenger friend of the first user, received from the first device 100 , in response to the relay server ID of the first user. Authority information 6750 may be stored.

69A is a diagram illustrating a method in which the relay server 1000 registers a first user and a second user as mutual relay server friends according to an embodiment of the present invention.

In operation S6910 , the first device 100 may receive a first user input for setting the second user as a relay server friend with which to communicate through the relay server 1000 .

For example, as shown in FIG. 69B , the first device 100 is a user interface for setting a user whose contact information is stored in the first device 100 as a relay server friend to talk to through the relay server 1000 . can provide

In operation S6920, the first device 100 may request the relay server 1000 to establish a relay server friend relationship between the first user and the second user.

For example, upon receiving the first user input for setting the second user as a relay server friend, the first device 100 sets a relay server friend relationship between the first user and the second user to the relay server 1000 . can ask for

In this case, the first device 100 may transmit the relay server ID of the first user and the unique information of the second user stored in the first device 100 to the relay server 1000 . Also, according to an embodiment, when the relay server ID of the second user is stored in the first device 100 , the first device 100 is the relay server ID of the second user together with the relay server ID of the first user. may be transmitted to the relay server 1000 .

In operation S6930, the relay server 1000 may notify the second device 200 that the first user has requested to establish a relay server friend relationship between the first user and the second user.

For example, in response to receiving a request for setting a relay server friend between the first user and the second user from the first device 100 , the relay server 1000 provides the second user's unique information received from the first device 100 . Based on the , the relay server ID of the second user may be obtained. For example, the relay server 1000 may determine a user having the same unique information as the unique information received from the first device 100 as the second user, and obtain the ID of the second user.

The relay server 1000 relays between the first user and the second user to the second device 200 based on the address information of the second device 200 stored in response to the acquired ID of the second user. It may notify that a server friend setting request has been received.

In this case, the relay server 1000 may transmit the relay server ID of the first user, the name of the first user, or unique information of the first user and identification information of the second messenger service to the second device 200 .

In step S6940 , the second device 200 may receive a second user input allowing setting of a relay server friend between the first user and the second user.

For example, as shown in FIG. 69c , upon receiving the relay server friend setting request of the first user from the relay server 1000 , the second device 200 provides the first user and the second user from the first user. A notification pop-up notifying that the relay server friend setting request has been received may be displayed. By receiving the second user input of selecting the confirmation button in the notification pop-up, the second device 200 may receive the input of the second user allowing setting of a relay server friend between the first user and the second user.

In operation S6950, the second device 200 may request the relay server 1000 to establish a relay server friend relationship between the second user and the first user.

In this case, the second device 200 may transmit the relay server ID of the first user and the relay server ID of the second user to the relay server 1000 .

In operation S6960, the relay server 1000 may register the first user as a relay server friend of the second user and the second user as a relay server friend of the second user.

The relay server 1000 may store the relay server ID of the second user as a relay server friend in response to the relay server ID of the first user. Also, the relay server 1000 may store the relay server ID of the first user as a relay server friend in response to the relay server ID of the second user.

69B is a diagram illustrating a method in which the first device 100 receives a first user input for setting a second user as a relay server friend with which to talk through the relay server 1000, according to an embodiment of the present invention. .

Referring to FIG. 69B , the first device 100 may provide a user interface for setting a user whose contact information is stored in the first device 100 as a relay server friend to talk to through the relay server 1000 .

For example, upon receiving the first user input for displaying the contact information stored in the first device 100 , the first device 100 may display a page 6910 indicating identification information of users in which the contact information is stored. . In this case, the first device 100 may display buttons 6920 and 6930 for chatting with each user together with identification information of the users in which the contact information is stored. Also, the first device 100 may display information indicating whether the users are the first messenger friends of the first user on the button for chatting with the users.

For example, if the user is not registered as the first messenger friend of the first user in the first messenger server 2000, the first device 100 may use a button 6920 for registering the selected user as a relay server friend. can be displayed. For example, a user having “Lind Kim” as identification information may not have been registered as a messenger friend of the first user in the first messenger server 2000 . In this case, the first device 100 may display a button 6920 for registering “Lind Kim” as a relay server friend of the first user in response to “Lind Kim”.

In addition, when the user is registered in the first messenger server 2000 as the first user's messenger friend, the first device 100 executes the first messenger application and displays a button 6930 for chatting with the selected user. can do.

Whether users are registered in the first messenger server 2000 as the first messenger friends may be determined by the first device 100 .

For example, the first device 100 may receive, from the first messenger server 2000 , contact information of users registered as messenger friends of the first user. The first device 100 compares the contact stored in the first device 100 with the contact received from the first messenger server 2000, and allows users who have the same contact as the contact received from the first messenger server 2000. It may be determined that the messenger friend is registered in the first messenger server 2000 .

Also, for example, when the messenger IDs of the messenger friends of the first user are stored in the first device 100 , the first device 100 is the first user's messenger friends from the first messenger server 2000 . It may be determined whether the users are registered in the first messenger server 2000 as messenger friends by receiving the registered users' messenger IDs and comparing the received IDs with stored IDs.

As the user input for selecting the button 6920 corresponding to “Lind Kim” is received, the first device 100 sends the relay server 1000 to the relay server friend between the first user and the user corresponding to “Lind Kim”. You can ask to establish a relationship.

69c is a diagram illustrating a method for the second device 200 to receive a second user input allowing setting of a relay server friend between a first user and a second user from a second user, according to an embodiment of the present invention. .

Referring to FIG. 69c , upon receiving the relay server friend setting request from the first user from the relay server 1000 , the second device 200 indicates that the relay server friend setting request between the first user and the second user has been received. A notification pop-up 6940 to notify may be displayed.

Also, the second device 200 may display a confirmation button for receiving a user input permitting setting of a relay server friend between the first user and the second user on the notification pop-up 6940 .

Upon receiving a user input for selecting a confirmation button in the notification pop-up 6940 , the second device 200 may request the relay server 1000 to set up a relay server friend between the second user and the first user.

69D illustrates a database stored by the relay server 1000 when a relay server friend is set between users according to an embodiment of the present invention.

Referring to FIG. 69D , the relay server 1000 may store the relay server ID 6950 of the user's relay server friend in response to the user's relay server ID 6710 .

For example, the relay server 1000 may store the relay server ID of the second user as a relay server friend in response to the relay server ID of the first user.

70A is a diagram illustrating that the relay server 1000 registers the relay server 1000 as a second user in the first messenger server 2000, and based on the authority information of the first user, the relay server according to an embodiment of the present invention. It is a flowchart illustrating a method of registering 1000 as a first messenger friend of the first user to the first messenger server 2000 .

In step S7010, the relay server 1000 may generate first messenger virtual account information for the second user.

As the relay server friend relationship is established between the first user and the second user, the relay server 1000 may generate first messenger virtual account information for the second user. The first messenger virtual account information for the second user may be referred to as the first messenger virtual account information of the first user.

The first messenger virtual account information for the second user may include a first messenger virtual ID for the second user and a first messenger virtual password for the second user.

For example, the relay server 1000 may generate a coined word and determine the generated coined word as a first messenger virtual ID for the second user. Also, the relay server 1000 may determine the second user's relay server ID, the second user's name, or unique information as the first messenger virtual ID for the second user.

Also, the relay server 1000 may generate a first messenger virtual password for the second user.

In step S7015 , the relay server 1000 may request the first messenger server 2000 to register the relay server 1000 as a user based on the first messenger virtual account information for the second user.

In this case, the relay server 1000 may transmit the first messenger virtual account information for the second user and the address information of the relay server 1000 to the first messenger server 2000 . The address information of the relay server 1000 may include IP address information of the relay server 1000 or identification information of the relay server 1000 registered in the push server.

Also, according to an embodiment, when the first messenger server 2000 requests to register a nickname corresponding to the account, the relay server 1000 sends the first messenger server 2000 to the first messenger server 2000 for the second user. It is possible to transmit the nickname of the second user as well as the virtual account information. The nickname of the second user may be information registered as display information of the second user to be used in a messenger service not subscribed to by the second user when the second user subscribes to the relay server 1000 .

In step S7020, the first messenger server 2000 may register the relay server 1000 as a user of the first messenger service by registering the first messenger virtual account information for the second user.

The first messenger server 2000 may register the relay server 1000 as a user of the first messenger service by registering the first messenger virtual account information for the second user received from the relay server 1000 . Also, the first messenger server 2000 may store address information of the relay server 1000 in response to the first messenger virtual account information for the second user.

In step S7025, the relay server 1000 sets the relay server 1000 as the first messenger friend of the first user based on the authority information indicating the authority to add another user as the first messenger friend of the first user. You may be asked to register.

In this case, the relay server 1000 may transmit the first messenger ID and authority information of the first user and the first messenger virtual account information of the second user to the first messenger server 2000 .

In step S7030, the first messenger server 2000 may determine, based on the received authority information, whether the relay server 1000 has the authority to register the relay server 1000 as the messenger friend of the first user. .

For example, if the received authorization information is authorization information distributed to the relay server 1000 by the first messenger server 2000 based on the input of the first user, the first messenger server 2000 may ) may be compared with the authority information stored in the first messenger server 2000 to determine that the relay server 1000 has the authority to register the messenger friend of the first user.

In addition, according to an embodiment, when the received authorization information is the first messenger ID and password of the first user, the first messenger server 2000 is based on the received first messenger ID and password of the first user. , it is possible to authenticate that the relay server 1000 is the first user.

In step S7035, when the relay server 1000 has the authority to register the relay server 1000 as a friend of the first user, the first messenger server 2000 sets the relay server 1000 as the first messenger of the first user. You can register as a friend.

The first messenger server 2000 may store the first messenger virtual ID information of the second user as the ID of the first messenger friend of the first user in response to the first messenger ID of the first user.

In operation S7040 , the first messenger server 2000 may notify the first device 100 that a user having the first messenger virtual ID information of the second user has been added as a messenger friend of the first user.

In this case, the first messenger server 2000 may transmit the first messenger virtual ID of the second user to the first device 100 . Also, according to an embodiment, the first messenger server 2000 may transmit the second user's name, the second user's unique information, and the second user's nickname to the first device 100 .

In operation S7045, the first device 100 may display that the user having the first messenger virtual ID information of the second user has been added as the first messenger friend of the first user.

The first device 100 displays the first messenger virtual ID of the second user received from the first messenger server 2000, the name of the second user, unique information of the second user, or the nickname of the second user, It may be displayed that the second user has been added as the first messenger friend of the first user.

70B is a diagram in which the relay server 1000 registers the relay server 1000 as a first user in the second messenger server 2000, and based on the authority information of the second user, the relay server according to an embodiment of the present invention. It is a flowchart illustrating a method of registering 1000 as a second messenger friend of a second user to the second messenger server 2000 .

In operation S7050, the relay server 1000 may generate second messenger virtual account information for the first user. In step S7055 , the relay server 1000 may request the second messenger server 3000 to register the relay server 1000 as a user based on the second messenger virtual account information for the first user. In step S7060, the second messenger server 3000 may register the relay server 1000 as a user of the second messenger service by registering the second messenger virtual account information for the first user. In step S7065, the relay server 1000 registers the relay server 1000 as the second messenger friend of the second user based on the authority information indicating the authority to add another user as the second user's messenger friend. you can request In step S7070, the second messenger server 3000 may determine, based on the received authority information, whether the relay server 1000 has the authority to register the relay server 1000 as a messenger friend of the second user. . In step S7075, when the relay server 1000 has the authority to register the relay server 1000 as a friend of the second user, the second messenger server 3000 sets the relay server 1000 as the second messenger of the second user. You can register as a friend. In step S7080, the second messenger server 3000 may notify the second device 200 that the user having the second messenger virtual ID information for the first user has been added as the second messenger friend of the second user. In operation S7085, the second device 200 may display that the user having the second messenger virtual ID information for the first user has been added as the second messenger friend of the second user.

Steps S7050 to S7085 may be described with reference to steps S7010 to S7045.

FIG. 70C is a diagram illustrating a database created in the relay server 1000 when the relay server 1000 registers virtual account information for a user in the messenger server, according to an embodiment of the present invention.

The relay server 1000 may store the virtual account information 7020 registered in the messenger server for the user in response to the user's relay server ID 7010 .

For example, when the virtual account information for the first user is registered in the second messenger server 3000 , the relay server 1000 corresponds to the relay server ID of the first user, and the second messenger virtual for the first user You can save your account information.

Virtual account information corresponding to one user may be different for each messenger service, or may be the same. In addition, the virtual ID may be unique information such as a user's phone number and e-mail address, or may be a coined word generated by a relay server.

70D is a diagram for explaining a method in which the first device 100 indicates that a user having a first messenger virtual ID of a second user has been added as a first messenger friend of the first user, according to an embodiment of the present invention .

Referring to FIG. 70D , the first device 100 may indicate that the user having the first messenger virtual ID of the second user has been added as the first messenger friend of the first user.

For example, the first device 100 may receive from the first messenger server 2000 that the user having the first messenger virtual ID of the second user has been added as the first messenger friend of the first user. Also, according to an embodiment, the first device 100 may receive the user's nickname having the first messenger virtual ID of the second user from the first messenger server 2000 .

Upon receiving the user input for executing the first messenger application for using the first messenger service, the first device 100 displays the first messenger virtual ID of the second user received from the first messenger server 2000 By doing so, it is possible to display that the second user has been added.

For example, upon receiving a user input for executing the first messenger application for using the first messenger service, the first device 100 may display an item 7030 indicating the first messenger ID of the first user, the first An item 7032 representing a newly added user as the user's first messenger friend and an item 7034 representing the first message friend of the first user added previously may be displayed.

When the first messenger virtual ID of the second user received from the first messenger server 2000 is “Cute_Linda@hanmail.net”, the first device 100 adds “Cute_Linda@hanmail.net” to the newly added friend. Displaying by ID may indicate that the second user has been added as a friend of the first user.

71A is a flowchart for explaining a method in which the first device 100 indicates that a second user has been added by using a contact list stored in the first device 100, according to an embodiment of the present invention.

In operation S7110 , the relay server 1000 may transmit the first messenger virtual ID information of the second user to the first device 100 .

As the first messenger virtual account information for the second user is registered in the first messenger server 2000, the relay server 1000 may transmit the first messenger virtual ID for the second user to the first device 100. have.

In operation S7120, the first device 100 may store the first messenger virtual ID for the second user as the second user's contact information.

For example, the first device 100 may store the first messenger virtual ID for the second user as the phone number of the second user.

In operation S7130 , the first messenger server 2000 may transmit information indicating that the user having the first messenger virtual ID for the second user has been added as a messenger friend of the first user to the first device 100 .

In this case, the first messenger server 2000 may transmit the first messenger virtual ID for the second user to the first device 100 . Step S7130 may correspond to step S7040 of FIG. 70A .

In operation S7140 , the first device 100 may display identification information of the second user in the contact list based on the first messenger virtual ID for the second user.

For example, the first device 100 may compare the ID received from the first messenger server 2000 with identification information of users in the contact list stored in the first device 100 . In this case, when the ID received from the first messenger server 2000 is stored as a contact, the first device 100 stores the ID received from the first messenger server 2000 as the contact information of the user. may be displayed as a user added as a messenger friend of the first user.

71B to 71C are diagrams for explaining a method in which the first device 100 indicates that a second user has been added by using a contact list stored in the first device 100, according to an embodiment of the present invention.

Referring to FIG. 71B , the first device 100 may store the first messenger virtual ID of the second user as a contact information of the second user.

The name of the second user may be stored as “Linda Kim” in the first device 100 . Also, the second device 200 may store “Cute_Linda@hanmail.net” which is the first messenger virtual ID of the second user received from the relay server 1000 as the email address of the second user.

Upon receiving “Cute_Linda@hanmail.net” as the ID of the user added as the first messenger friend of the first user from the first messenger server 2000, the second device 200 compares the received ID with the contact list. can Accordingly, the second device 200 may determine that the user added as a messenger friend of the first user is a user having identification information of “Linda Kim”.

Upon receiving the first user input for displaying the second user's contact information, the first device 100 may display a page 7110 indicating the second user's contact information. Also, the first device 100 may display “Linda Kim” 7120 as the second user's identification information and “Cute_Linda@hanmail.net” 7130 as the second user's email address.

Referring to FIG. 71C , the first device 100 may display the identification information of the second user in the contact list stored in the first device 100 as the user added as the first messenger friend of the first user.

Upon receiving a user input for executing the first messenger application for using the first messenger service, a page indicating identification information of the first messenger friends of the first user may be displayed.

In this case, the first device 100 may display that the second user having the identification information “Linda Kim” has been added as the first messenger friend of the first user. can indicate

Accordingly, the first device 100 displays the names of the users in the contact list as identification information of the first messenger friends of the first user, so that the user can easily distinguish the users on the first messenger application.

72A is a diagram illustrating a method in which the relay server 1000 relays message transmission/reception between a first user and a second user based on the virtual account information of the first user and the virtual account information of the second user, according to an embodiment of the present invention; is a flowchart showing

In operation S7210, the first device 100 may receive a first user input for transmitting a message to the second user.

For example, the first device 100 receives a first user input for executing an application distributed by the first messenger service provider, and a first user input for transmitting a message to a second user using the executed application can receive

In operation S7220 , the first device 100 may request the first messenger server 2000 to transmit a message to the second user based on the first messenger virtual ID of the second user.

In this case, the first device 100 may transmit the first messenger ID of the first user, the first messenger virtual ID of the second user, and the message to the first messenger server 2000 .

In operation S7230, the first messenger server 2000 may acquire address information about the relay server 1000 stored in correspondence to the first messenger virtual ID of the second user.

Upon receiving the message transmission request from the first device 100, the first messenger server 2000 is based on the first messenger virtual ID of the second user that is the ID of the recipient, Address information can be obtained.

In step S7240 , the first messenger server 2000 may transmit a message to the relay server 1000 .

The first messenger server 2000 may transmit a message to the relay server 1000 by using the address information of the relay server 1000 .

In this case, the first messenger server 2000 may transmit the first messenger ID of the first user as the sender's ID and the first messenger virtual ID of the second user as the receiver's ID to the relay server 1000 .

In operation S7250, the relay server 1000 may acquire information about the second user based on the first messenger virtual ID of the second user.

The relay server 1000 may acquire the relay server ID of the second user based on the first messenger virtual ID of the second user. In addition, the relay server 1000 is based on the acquired relay server ID of the second user, identification information of the messenger service used by the second user, address information of the messenger server used by the second user, and the second user's second ID. 2 You can obtain a messenger ID.

In step S7260, the relay server 1000 obtains the relay server ID of the first user based on the first messenger ID of the first user, and based on the obtained relay server ID of the first user, the first user's A second messenger virtual ID may be obtained.

In step S7270 , the relay server 1000 may request the second messenger server 3000 to transmit a message to the second user based on the second messenger virtual ID of the first user.

In this case, the relay server 1000 may transmit the message and the first user's second messenger virtual ID as the sender's ID and the second user's second messenger ID as the receiver's ID to the second messenger server 3000. have.

In step S7280 , the second messenger server 3000 may transmit a message to the second device 200 .

The second messenger server 3000 obtains the address of the second device 200 based on the second messenger ID of the second user, and uses the obtained address information to send the message to the second device 200 . can be transmitted

In this case, the second messenger server 3000 may transmit the second messenger virtual ID of the first user to the second device 200 as the sender's ID.

In operation S7290, the second device 200 may display a message.

For example, as the message is received from the second messenger server 3000 , the second device 200 may display a notification window indicating that the message has been received.

Also, as the application distributed by the second messenger service provider is executed, the second device 200 may display the received message.

In this case, the second device 200 may display the second messenger virtual ID of the first user or the name of the first user stored in the second device 200 as the sender.

72B is a diagram illustrating that the first device 100 and the second device 200 communicate with the first user as the relay server 1000 relays the message transmission/reception between the first user and the second user, according to an embodiment of the present invention. A diagram for explaining a method of displaying a message transmitted and received between second users.

Referring to FIG. 72B , as the relay server 1000 relays message transmission/reception between the first user and the second user, the first device 100 and the second device 200 transmit/receive between the first user and the second user. message can be displayed.

For example, when a first user “Alice” who uses a messenger called “KakaoTalk” and “Linda Kim”, a second user who uses a messenger called “Line” chat using the relay server 1000 , The first device 100 may display a message between “Alice” and “Linda Kim” by executing the “KakaoTalk” application. Also, the second device 200 may display a message between “Alice” and “Linda Kim” using the “Line” application.

In this case, the first device 100 displays a page 7210 indicating the transmitted/received message, and uses “Linda Kim” 7230, which is the identification information of the second user, as identification information of the other party having a conversation with the first user. can be displayed. In addition, the second device 200 displays a page 7220 indicating the transmitted/received message, and displays “Alice” 7240, which is the identification information of the first user, as identification information of the other party having a conversation with the second user. can

73 is a diagram illustrating message transmission between a user using a messenger function provided by the relay server 1000 and a user using another messenger service when the relay server 1000 performs a messenger function according to an embodiment of the present invention. It is a diagram showing the relay server 1000 that relays.

Referring to FIG. 73 , the relay server 1000 and the second messenger server 3000 may be messenger servers operated by different service providers.

The relay server 1000 may perform the function of the first messenger server 2000 described with reference to FIG. 66 .

Also, the relay server 1000 may relay message transmission between a user who uses the messenger function provided by the relay server 1000 and a user who uses another messenger service.

For example, the relay server 1000 may receive permission information for adding another user to the second messenger server 3000 as a second messenger friend of the second user from the second device 200 . The relay server 1000 may add the relay server 1000 as a second messenger friend of the second user based on the authorization information received from the second device 200 .

The relay server 1000 may receive the message of the second user from the second messenger server 3000 as the second messenger friend of the second user. The relay server 1000 may transmit the message of the second user received from the second messenger server 3000 to the first device 100 .

Also, the relay server 1000 may receive the message of the first user from the first device 100 . The relay server 1000 may request the second messenger server 3000 as the second messenger friend of the second user to deliver the message of the first user received from the first device 100 to the second user.

Accordingly, the relay server 1000 may relay message transmission between a user who uses the messenger function provided by the relay server 1000 and a user who uses another messenger service.

74 is a method of registering an account in the relay server 1000 by the first device 100 and the second device 200 and the second device 200 using the second messenger server ( 3000) is a flowchart showing how to register an account.

In step S7410 , the relay server 1000 may request the second messenger server 3000 to register the relay server 1000 .

Upon receiving the registration request from the relay server 1000 , the second messenger server 3000 may create a second messenger account of the relay server 1000 and store information about the created account. In this case, the second messenger account of the relay server 1000 may be an account as a third party, not as an account as a user of the second messenger server 3000 .

In operation S7420 , the first device 100 may transmit a registration request for the first user to the relay server 1000 .

For example, upon receiving the input of the first user to install the application distributed by the service provider of the relay server 1000 , the first device 100 registers the first user with the relay server 1000 . you can request

In this case, the first device 100 may transmit relay server account information of the first user to be registered with the relay server 1000 and address information of the first device 100 to the relay server 1000 . The address information of the device may include an IP address of the device or identification information of a device registered in the push server, but is not limited thereto. Also, the account information may include at least one of an ID and a password.

Also, the first device 100 may transmit the first user's unique information to the relay server 1000 . The unique information of the first user may include, but is not limited to, the first user's contact information and resident number. The first user's contact information may include, but is not limited to, the first user's phone number and e-mail address.

The relay server 1000 may store address information of the first device 100 and unique information of the first user in response to the first user's relay server 1000 account information received from the first device 100 .

In operation S7430 , the second device 200 may transmit a registration request for the second user to the second messenger server 3000 .

In this case, the second device 200 transmits the second messenger account information of the second user to be registered in the second messenger server 3000 and the address information of the second device 200 to the second messenger server 3000 . can

The second messenger server 3000 may store address information of the second device 200 in response to the second messenger account information of the second user received from the second device 200 .

In operation S7440 , the second device 200 may transmit a registration request for the second user to the relay server 1000 .

For example, upon receiving the input of the second user to install the application distributed by the service provider of the relay server 1000 , the second device 200 registers the second user with the relay server 1000 . you can request

In this case, the second device 200 may transmit the relay server 1000 account information of the second user to be registered with the relay server 1000 to the relay server 1000 .

Also, the second device 200 may transmit information about the second messenger service subscribed by the second user to the relay server 1000 . The information on the second messenger service may include identification information of the second messenger service or address information of the second messenger server 3000 .

Also, the second device 200 may transmit the second user's unique information to the relay server 1000 . The unique information of the second user may include, but is not limited to, the second user's contact information and resident number. The second user's contact information may include, but is not limited to, the second user's phone number and e-mail address.

As the second device 200 receives the second user's relay server 1000 account information, the second messenger service information, and the second user's unique information, the relay server 1000 is the second user's relay server Information about the second messenger service and unique information of the second user may be stored in correspondence with the ID.

75 is a flowchart illustrating a method in which the relay server 1000 acquires the authority of the second user to the second messenger server 3000 according to an embodiment of the present invention.

In step S7510 , the second device 200 may request the second messenger server 3000 to grant the relay server 1000 a right to add another user as a second messenger friend of the second user.

In this case, the second device 200 may transmit the second messenger account information of the second user and the second messenger identification information of the relay server 1000 to the second messenger server 3000 .

In step S7520 , the second messenger server 3000 may grant the relay server 1000 a right to add another user as a messenger friend of the second user.

The second messenger server 3000 may authenticate the second user based on the received account information of the second user. As the second user is authenticated, the second messenger server 3000 may generate authorization information indicating authorization to add another user as a messenger friend of the second user. The second messenger server 3000 may store the generated authorization information in response to the second messenger ID of the second user and the second messenger identification information of the relay server 1000 .

In step S7530 , the second messenger server 3000 may transmit authority information indicating the authority to add another user as a messenger friend of the second user to the second device 200 .

In operation S7540 , the second device 200 may transmit the authorization information received from the second messenger server 3000 to the relay server 1000 .

In this case, the second device 200 may transmit the relay server ID of the second user together with the authorization information to the relay server 1000 .

Accordingly, the relay server 1000 may acquire the right to add another user to the second messenger server 3000 as the second user's messenger friend.

76A is a diagram illustrating a method in which the first device 100 receives a first user input for setting a second user as a first messenger friend to be chatted with through the relay server 1000 according to an embodiment of the present invention; FIG. am.

Referring to FIG. 76A , the first device 100 receives a list of users subscribed to the relay server 1000 from the relay server 1000, and selects a user selected from the received list of users as a first messenger friend. A user interface can be provided.

For example, as the relay server 1000 receives a first user input for executing the distributed messenger application, the first device 100 receives from the relay server 1000 among users subscribed to the relay server 1000 . A list of users not set as the first user and the first messenger friend may be received. In this case, the relay server 1000 may transmit to the first device 100 a list of users related to the first user among users who are not set as the first user and the first messenger friend.

The users related to the first user may be, for example, a user who stores the contact information of the first user in the device or a user in which the first user stores the contact information in the first device 100 , but is not limited thereto. To this end, the relay server 1000 may receive the contact stored in the first device 100 from the first device 100 , and receive and store the contact stored in the second device 200 from the second device 200 . have.

Upon receiving the first user input for selecting one of the first user and the list of users not set as the first messenger friend, the first device 100 sends the second user to the relay server 1000 as the first user's friend. You can request to be set as the first messenger friend.

As the first device 100 receives a list of users related to the first user among users who are not set as the first user and the first messenger friend from the relay server 1000, the first device 100 displays a page 7620 indicating the received users. can be displayed.

Upon receiving a user input for selecting a second user from among the displayed users, the first device 100 may request the relay server 1000 to establish a first messenger friend relationship between the first user and the second user. .

Upon receiving the first messenger friend setting request from the first device 100 , the relay server 1000 sends a first messenger friend setting request from the first user to the second device 200 between the first user and the second user. You can notify that it has been received.

69c, the second device 200 displays a notification window informing that the first messenger friend setting request has been received between the first user and the second user, and based on the selection of the second user, the relay server ( 1000) to set up a first messenger friend between the first user and the second user.

76B is a diagram illustrating a database stored in the relay server 1000 according to an embodiment of the present invention.

Referring to FIG. 76B , the relay server 1000 may store information about a user.

The relay server 1000 may store identification information 7620 of the messenger service subscribed by the user in response 7610 to the relay server ID of the user, the messenger server ID 7630 of the user, and unique information 7640 of the user. .

Also, the relay server 1000 may store authorization information 7650 indicating the authority to add another user as the user's messenger friend in response to the user's relay server ID 7610 .

For example, the relay server 1000 may store authorization information indicating the authority to add another user as a messenger friend of the second user to the second messenger server 3000 in response to the second user relay server ID. have.

Also, the relay server 1000 may store the relay server ID 7660 of the user set as the first messenger friend in response to the relay server ID 7610 of the user. For example, the relay server 1000 may set the second user as the first messenger friend in response to the relay server ID of the first user. A first messenger friend setting between users may be described with reference to FIGS. 69A to 69C .

77A is a diagram showing that, as a second user is registered in the relay server 1000 as a first messenger friend of the first user, the relay server 1000 sends the first device 100 to the second user according to an embodiment of the present invention. It is a flowchart illustrating a method of notifying that the user is registered as the first messenger friend of the first user.

In operation S7710, the relay server 1000 may set up a first messenger friend between the second user and the first user.

Upon receiving a request for setting a first messenger friend between the first user and the second user from the first device 100 and the second device 200 , the relay server 1000 establishes a first messenger between the second user and the first user. You can set up friends.

In operation S7720, the relay server 1000 may notify the first device 100 that the second user has been added as the first messenger friend of the first user.

In this case, the relay server 1000 may transmit the relay server ID of the second user and the relay server ID of the first user to the first device 100 . According to an embodiment, the relay server 1000 may transmit the second user's unique information or name to the first device 100 .

In operation S7730, the first device 100 may display that the second user has been added as the first messenger friend of the first user.

As the relay server 1000 receives the input of the first user executing the distributed messenger application, the first device 100 may display that the second user has been added as the first messenger friend of the first user.

In this case, the first device 100 may display the relay server ID, name, or unique information of the second user as the display information of the second user. Also, as shown in FIG. 71C , the first device 100 may display the identification information of the second user in the contact list stored in the first device 100 as the display information of the second user.

In addition, as shown in FIG. 70B , the relay server 1000 generates second messenger virtual account information for the first user, and based on the generated second messenger virtual account information for the first user, the second Based on the authority information indicating the authority to register the relay server 1000 in the messenger server 3000 as a user of the second messenger service and add another user as the second messenger friend of the second user, the relay server ( 1000) as the second user's second messenger friend, the second device 200 can also display that the user with the second messenger virtual ID information for the first user has been added as a friend of the second user. have.

77B is a diagram illustrating a database 7700 in which the relay server 1000 stores virtual account information of users, according to an embodiment of the present invention.

Referring to FIG. 77B , the relay server 1000 may store virtual account information 7720 for each messenger server corresponding to the relay server ID 7710 of users.

78 is a flowchart illustrating a method for the relay server 1000 to transmit a message of a first user received from the first device 100 to a second user according to an embodiment of the present invention.

In operation S7810, the first device 100 may receive a first user input for transmitting a message to the second user.

In operation S7820, the first device 100 may request the relay server 1000 to transmit a message to the second user based on the relay server ID of the second user.

In this case, the first device 100 may transmit the relay server ID of the first user, the relay server ID of the second user, and the message to the relay server 1000 .

In operation S7830, the relay server 1000 may acquire information about the second user stored in response to the relay server ID of the second user.

The information about the second user may include identification information of the messenger server used by the second user, address information of the messenger server, and the second messenger ID of the second user.

In operation S7840, the relay server 1000 may acquire the second messenger virtual ID of the first user based on the relay server ID of the first user.

In operation S7850, the relay server 1000 may request the second messenger server 3000 to transmit a message to the second user based on the second messenger virtual ID of the first user.

In this case, the relay server 1000 may transmit the message, the first user's second messenger virtual ID as the sender's ID, and the second user's second messenger ID as the receiver's ID, to the second messenger server 3000 . have.

In operation S7860 , the second messenger server 3000 may transmit a message to the second device 200 .

The second messenger server 3000 obtains the address of the second device 200 based on the second messenger ID of the second user, and uses the obtained address information to send the message to the second device 200 . can be transmitted

In this case, the second messenger server 3000 may transmit the second messenger virtual ID of the first user to the second device 200 as the sender's ID.

In step S7190, the second device 200 may display a message.

In this case, the second device 200 may display the second messenger virtual ID of the first user or the name of the first user stored in the second device 200 as the sender.

79 is a flowchart illustrating a method for the relay server 1000 to transmit a message of a second user received from the second device 200 to a first user, according to an embodiment of the present invention.

In operation S7910, the second device 200 may receive a second user input for transmitting a message to the first user.

In operation S7920 , the second device 200 may request the second messenger server 3000 to transmit a message to the first user based on the second messenger virtual ID of the first user.

In this case, the second device 200 may transmit the second messenger ID of the second user, the second messenger virtual ID of the first user, and the message to the second messenger server 3000 .

In operation S7930, the second messenger server 3000 may acquire address information about the relay server 1000 stored in correspondence to the second messenger virtual ID of the first user.

Upon receiving the message transmission request from the first device 100, the first messenger server 2000 is based on the first messenger virtual ID of the second user that is the ID of the recipient, Address information can be obtained.

In step S7940 , the second messenger server 3000 may transmit a message to the relay server 1000 .

The second messenger server 3000 may transmit a message to the relay server 1000 by using the address information of the relay server 1000 .

In this case, the second messenger server 3000 may transmit the second messenger ID of the second user as the sender ID and the second messenger virtual ID of the first user as the receiver ID to the relay server 1000 .

In operation S7950, the relay server 1000 may acquire the relay server ID of the second user based on the second messenger ID of the second user.

In operation S7960, the relay server 1000 may acquire the relay server ID of the first user based on the second messenger virtual ID of the first user.

In operation S7970 , the relay server 1000 may transmit a message to the first device 100 .

The relay server 1000 may acquire the stored address information of the first device 100 corresponding to the relay server ID of the first user. The relay server 1000 may transmit the message received from the first messenger server 2000 to the first device 100 using the obtained address information of the first device 100 .

In step S7980, the first device 100 may display a message.

In this case, the first device 100 may display the relay server ID of the second user or the name of the second user stored in the first device 100 as display information of the sender.

80 is a diagram illustrating that when the relay server 1000 performs the functions of the devices 100 and 200, the relay server 1000 relays message transmission between users using different messenger services according to an embodiment of the present invention. A drawing showing the method.

Referring to FIG. 80 , the first relay server 1000a may be a device of a first user. Also, the second relay server 1000b may be a device of the second user.

The first messenger application distributed by the first messenger service provider may be installed in the first relay server 1000a. Also, the second messenger application distributed by the second messenger service provider may be installed in the second relay server 1000b.

The first relay server 1000a and the second relay server 1000b may relay message transmission/reception between the first user and the second user using different messenger services.

For example, the first relay server 1000a may receive, from the first messenger server 2000, permission information for adding another user to the first messenger server 2000 as a messenger friend of the first user. Also, the first relay server 1000a may add the first relay server 1000a as the first messenger friend of the first user to the first messenger server 2000 based on the received authorization information.

Also, the second relay server 1000b may receive from the second messenger server 3000 permission information for adding another user to the second messenger server 3000 as a messenger friend of the second user. Also, the second relay server 1000b may add the second relay server 1000b to the second messenger server 3000 as a messenger friend of the second user based on the received authorization information.

The first relay server 1000a may receive, from the first messenger server 2000, a message transmitted by the first user to the second user as a friend of the first user. Also, the first relay server 1000a may request the second messenger server 3000 to transmit the received message to the second user. Upon receiving the message transmission request from the first relay server 1000a, the second messenger server 3000 may transmit the received message to the second relay server 1000b.

Accordingly, the first relay server 1000a and the second relay server 1000b may relay message transmission/reception between the first user and the second user using different messenger services.

81 is a diagram illustrating a method in which the first relay server 1000a registers with the first messenger server 2000 and the second relay server 1000b registers with the second messenger server 3000, according to an embodiment of the present invention. It is a flow chart.

In step S8110 , the first relay server 1000a may request the first messenger server 2000 to register the first user.

For example, upon receiving the input of the first user who installs the application distributed by the service provider of the first messenger server 2000, the first relay server 1000a sends the first message to the first messenger server 2000. You can request registration for a user.

In this case, the first relay server 1000a may transmit the account information of the first user to be registered with the first messenger server 2000 and the address information of the first relay server 1000a to the first messenger server 2000 . have. The address information of the device may include an IP address of the device or identification information of a device registered in the push server, but is not limited thereto. Also, the account information may include at least one of an ID and a password.

The first messenger server 2000 may store address information of the first relay server 1000a in response to the first user's account information received from the first relay server 1000a.

In step S8120 , the second relay server 1000b may request the second messenger server 3000 to register the second user.

In this case, the second relay server 1000b may transmit the account information of the second user to be registered in the second messenger server 3000 and address information of the second device 200 to the second messenger server 3000 . .

The second messenger server 3000 may store address information of the second relay server 1000b in response to the account information of the second user received from the second relay server 1000b.

In step S8130 , the first relay server 1000a may request the first messenger server 2000 to register the first relay server 1000a.

Upon receiving the registration request from the first relay server 1000a, the first messenger server 2000 creates an account of the first relay server 1000a in the first messenger server 2000, and relates to the created account. information can be stored. In this case, the account of the first relay server 1000a in the first messenger server 2000 may not be an account as a user of the first messenger server 2000 but as a third party account.

Also, the first relay server 1000a may transmit address information of the first relay server 1000a to the first messenger server 2000 . The first messenger server 2000 may store address information of the first relay server 1000a in response to account information of the first relay server 1000a.

In operation S8140, the second relay server 1000b may request the second messenger server 3000 to register the second relay server 1000b.

Upon receiving the registration request from the second relay server 1000b, the second messenger server 3000 creates an account of the second relay server 1000b in the second messenger server 3000, and relates to the created account. information can be stored. In this case, the account of the second relay server 1000b in the second messenger server 3000 may be an account as a third party, not as an account as a user of the second messenger server 3000 .

Also, the second relay server 1000b may transmit address information of the second relay server 1000b to the second messenger server 3000 . The second messenger server 3000 may store address information of the second relay server 1000b in response to account information of the second relay server 1000b.

82A shows a method for the first relay server 1000a to obtain, from the first messenger server 2000, the right to add another user as the first messenger friend of the first user according to an embodiment of the present invention. It is a flow chart showing

In step S8210 , the first relay server 1000a may request to grant the authority to add another user as the first user's messenger friend to the first relay server 1000a.

For example, as shown in FIG. 69B , the first relay server 1000a grants the first relay server 1000a the right to add another user as the first messenger friend of the first user. A user interface may be provided for selecting .

Upon receiving the first user input selecting to grant the first relay server 1000a the authority to add another user as the first messenger friend of the first user, the first relay server 1000a sends the other user A request may be made to the first messenger server 2000 to grant the first relay server 1000a the right to add the user as the first messenger friend of the first user.

In this case, the first relay server 1000a may transmit the first messenger account information of the first user and the first messenger account information of the first relay server 1000a to the first messenger server 2000 .

In step S8220 , the first messenger server 2000 may grant the first relay server 1000a the right to add another user as the first messenger friend of the first user.

The first messenger server 2000 may authenticate the first user based on the received first messenger account information of the first user. As the first user is authenticated, the first messenger server 2000 may generate authorization information indicating authorization to add another user as the first messenger friend of the first user. The first messenger server 2000 may store the generated authorization information in correspondence with the first messenger ID of the first user and the first messenger ID of the first relay server 1000a.

In step S8230 , the first messenger server 2000 may transmit authority information indicating the authority to add another user as the first messenger friend of the first user to the first relay server 1000a.

In step S8240 , the first relay server 1000a may store the authority information received from the first messenger server 2000 . .

82b is a method for the second relay server 1000b to obtain, from the second messenger server 3000, the right to add another user as a second messenger friend of the second user, according to an embodiment of the present invention. It is a flow chart showing

In step S8250 , the second relay server 1000b may request to grant the second relay server 1000b an authority to add another user as the second messenger friend of the second user. In step S8260 , the second messenger server 3000 may grant the second relay server 1000b the right to add another user as the second messenger friend of the second user. In operation S8270, the second messenger server 3000 may transmit authority information indicating the authority to add another user as the second messenger friend of the second user to the second relay server 1000b. In step S8280 , the second relay server 1000b may store the authority information received from the second messenger server 3000 .

Steps S8250 to S8280 may be described with reference to steps S8210 to S8240 of FIG. 82A.

83A is a diagram in which the first relay server 1000a registers the first relay server 1000a with the first messenger server 2000, and based on the authority information of the first user, the first relay server 1000a according to an embodiment of the present invention It is a flowchart showing a method of registering the relay server 1000a with the first messenger server 2000 as the first messenger friend of the first user.

In operation S8305, the first relay server 1000a may receive a first user input for setting the second user as a relay server friend.

For example, as shown in FIG. 84A, the first relay server 1000a selects a user from the contact list and provides a user interface for setting the selected user as the first relay server friend of the first user. can The first relay server friend of the first user may refer to a user who does not use the first messenger but can send and receive messages to and from the first user using the first relay server 1000a.

In operation S8310, the first relay server 1000a may generate first messenger virtual account information for the second user.

As the second user is selected as the first relay server friend, the first relay server 1000a may generate first messenger virtual account information for the second user.

The first messenger virtual account information for the second user may include a first messenger virtual ID for the second user and a first messenger virtual password for the second user.

For example, the first relay server 1000a may generate a coined word and determine the generated coined word as a first messenger virtual ID for the second user. Also, the first relay server 1000a may determine the ID of the first relay server 1000a of the second user, the name of the second user, or unique information as the first messenger virtual ID for the second user.

Also, the first relay server 1000a may generate a first messenger virtual password for the second user.

In step S8315, the first relay server 1000a may request the first messenger server 2000 to register the first relay server 1000a as a user based on the first messenger virtual account information for the second user. have.

In this case, the first relay server 1000a may transmit the first messenger virtual account information for the second user and the address information of the first relay server 1000a to the first messenger server 2000 . The address information of the first relay server 1000a may include IP address information of the first relay server 1000a or identification information of the first relay server 1000a registered in the push server.

In step S8320 , the first messenger server 2000 may register the first relay server 1000a as a user of the first messenger service by registering the first messenger virtual account information for the second user.

The first messenger server 2000 registers the first messenger virtual account information for the second user received from the first relay server 1000a, thereby registering the first relay server 1000a as a user of the first messenger service. can Also, the first messenger server 2000 may store address information of the first relay server 1000a corresponding to the first messenger virtual account information for the second user.

In step S8325, the first relay server 1000a assigns the first relay server 1000a to the first messenger of the first user based on the authority information indicating the authority to add another user as the first user's messenger friend. You can request to register as a friend.

In this case, the first relay server 1000a may transmit the first messenger ID and authority information of the first user and the first messenger virtual account information for the second user to the first messenger server 2000 .

In step S8330, the first messenger server 2000 determines whether the first relay server 1000a has the authority to register the first relay server 1000a as the first messenger friend of the first user, based on the received authorization information. can determine whether

For example, if the received authorization information is the first messenger ID and password of the first user, the first messenger server 2000 is based on the received first messenger ID and password of the first user, the first It is possible to authenticate that the relay server 1000a is the first user.

In addition, according to an embodiment, when the received authorization information is authorization information distributed by the first messenger server 2000 to the first relay server 1000a based on the input of the first user, the first messenger server 2000 compares the authority information distributed to the first relay server 1000a with the authority information stored in the first messenger server 2000, and indicates that the first relay server 1000a has the authority to register the messenger friend of the first user. can judge

In step S8335, the first messenger server 2000 sends the first relay server 1000a to the first relay server 1000a when the first relay server 1000a has the authority to register the first relay server 1000a as a friend of the first user. 1 You can register as a user's first messenger friend.

The first messenger server 2000 may store the first messenger virtual ID information for the second user as a messenger friend of the first user in response to the ID of the first user.

In step S8340, the first messenger server 2000 may notify the first relay server 1000a that the user having the first messenger virtual ID information for the second user has been added as the first messenger friend of the first user. .

In this case, the first messenger server 2000 may transmit the first messenger virtual ID for the second user to the first relay server 1000a.

In operation S8345 , the first relay server 1000a may transmit the first messenger virtual ID for the second user to the second relay server 1000b.

In this case, the first relay server 1000a may transmit the first messenger ID of the first user together with the first messenger virtual ID for the second user to the second relay server 1000b.

For example, as shown in FIG. 84B , upon receiving the first messenger virtual ID for the two users from the first messenger server 2000, the first relay server 1000a provides the second user with the A user interface for transmitting the first messenger virtual ID and the first messenger ID of the first user using a text message may be provided.

As shown in FIG. 84c , upon receiving the text message from the first relay server 1000a, the second relay server 1000b receives the first messenger virtual ID of the second user and the first user's virtual ID included in the text message. A second user input for setting the first messenger ID to the second relay server 1000b may be received.

In addition, according to an embodiment, the first relay server 1000a transmits the first messenger virtual ID of the second user and the first messenger ID of the first user to a separate server to which the first user and the second user are subscribed to the second user. You can request it to be sent to Upon receiving the first messenger virtual ID of the second user and the first messenger ID of the first user from the server, the second relay server 1000b receives the received first messenger virtual ID of the second user and the first virtual ID of the first user 1 You can save the messenger ID.

83B is a diagram illustrating that the second relay server 1000b registers the second relay server 1000b with the second messenger server 3000, and based on the authority information of the second user, the second relay server 1000b according to an embodiment of the present invention. It is a flowchart showing a method of registering the relay server 1000b to the second messenger server 3000 as a messenger friend of the second user.

In operation S8350, the second relay server 1000b may receive a second user input for setting the first user as a relay server friend. In operation S8355, the second relay server 1000b may generate second messenger virtual account information for the first user. In step S8360, the second relay server 1000b may request the second messenger server 3000 to register the second relay server 1000b as a user based on the second messenger virtual account information for the first user. have. In operation S8365, the second messenger server 3000 may register the second relay server 1000b as a user of the second messenger service by registering the second messenger virtual account information for the first user. In step S8370, the second relay server 1000b uses the second relay server 1000b as the second user's messenger friend based on the authority information indicating the authority to add another user as the second user's messenger friend. You may be asked to register. In step S8375, the second messenger server 3000 determines whether the second relay server 1000b has the authority to register the second relay server 1000b as a messenger friend of the second user, based on the received authorization information. can judge In step S8380, the second messenger server 3000 sends the second relay server 1000b to the second relay server 1000b when the second relay server 1000b has the authority to register the second relay server 1000b as a friend of the second user. 2 You can register as a user's friend. In step S8385, the second messenger server 3000 may notify the second relay server 1000b that the user having the second messenger virtual ID information for the first user has been added as a messenger friend of the second user. In operation S8390, the second relay server 1000b may transmit the second messenger virtual ID for the first user to the first relay server 1000a.

Steps S8350 to S8390 may be described with reference to steps S8305 to S8345 of FIG. 83A.

84A to 84C are diagrams illustrating a method in which the first relay server 1000a transmits the first messenger virtual ID of the second user to the second relay server 1000b according to an embodiment of the present invention.

Referring to FIG. 84A , the first relay server 1000a may transmit the first messenger virtual ID for the second user and the first messenger ID of the first user to the second relay server 1000b.

For example, upon receiving the first user's input for selecting the second user's contact information stored in the first device 100 , the first device 100 generates a first messenger virtual ID of the second user. A user interface can be provided.

For example, upon receiving an input of “Alice” for selecting a contact of “Linda Kim” stored in the device 1000a of “Alice,” which is the first relay server 1000a, the device 1000a of “Alice” is Identification information 8420 of “Linda Kim” and a button 8430 for generating a virtual ID of “Linda Kim” for “KakaoTalk,” which is a messenger service to which “Alice” is subscribed, may be displayed.

Upon receiving the input of “Alice” for selecting the button 8430, the device 1000a of “Alice” creates a virtual account of “Linda Kim”, and the virtual account created in the “KakaoTalk” server 2000 may be requested to register. Also, the device 1000a of “Alice” may store the created account information as a virtual account of “Linda Kim”.

Referring to FIG. 84B , the first relay server 1000a may transmit the first messenger virtual ID for the second user and the first messenger ID of the first user to the second relay server 1000b.

For example, upon receiving the virtual account from the “KakaoTalk” server, the device 1000a of “Alice” displays a pop-up window 8440 for transmitting the KakaoTalk virtual ID of “Linda Kim” to “Linda Kim”. can be displayed.

The pop-up window 8440 may be a window for sending the KakaoTalk virtual ID of “Linda Kim” to “Linda Kim” in the form of a text message, and “Linda Kim” to a separate server to which “Alice” and “Linda Kim” are subscribed. It may be a window to request that “Linda Kim” transmit the KakaoTalk virtual ID of ”.

Upon receiving the input of “Alice” for selecting the confirmation button in the message window, the device 1000a of “Alice” may transmit the KakaoTalk virtual ID of “Linda Kim” in text form or to a separate server. In this case, the device 1000a of “Alice” may transmit the KakaoTalk ID of “Alice” together.

Referring to FIG. 84C , the second relay server 1000b may receive the first messenger virtual ID for the second user and the first messenger ID of the first user from the first relay server 1000a.

The device 1000b of “Linda Kim” as the second relay server 1000b may receive the KakaoTalk virtual ID of “Linda Kim” and the KakaoTalk ID of “Alice” in the form of a text message or from a separate server.

When receiving in the form of a text message, the device 1000b of “Linda Kim” receives the input of “Linda Kim”, which inputs the KakaoTalk virtual ID of “Linda Kim” and the KakaoTalk ID of “Alice”, Information may be stored in correspondence with the identification information of “Alice”. In addition, when receiving from a separate server, the device 1000b of “Linda Kim” may store the KakaoTalk virtual ID of “Linda Kim” and the KakaoTalk ID of “Alice” corresponding to the identification information of “Alice”. .

Accordingly, upon receiving the input of “Linda Kim” for selecting the contact of “Alice”, the device 1000b of “Linda Kim” stores the information of “Linda Kim” corresponding to the identification information 8460 of “Alice”. The KakaoTalk virtual ID 8480 and the KakaoTalk ID 8470 of “Alice” may be displayed.

Also, the device 1000b of “Linda Kim” may display a button 8490 for generating a virtual ID of “Alice” for “Line,” which is a messenger service to which “Linda Kim” is subscribed.

85A is a diagram illustrating a database stored by the first relay server 1000a according to an embodiment of the present invention.

Referring to FIG. 85A , the first relay server 1000a may store information 8510 of a first user and information 8520 of a second user.

For example, the first relay server 1000a stores the first messenger account information 8514 of the first user received from the first user or from the first messenger server 2000 in correspondence to the messenger identification information 8512 . can In addition, the first relay server 1000a transmits authority information 8516 indicating the authority to add another user received from the first messenger server 2000 as a messenger friend of the first user to the messenger identification information 8512. can be saved in response.

Also, the first relay server 1000a may store information 8520 about users stored as friends of the first relay server. For example, the first relay server 1000a corresponds to the second user's identification information 8521, the second user's first messenger virtual account information 8522 8523, the second user's messenger identification information 8524, The second messenger ID 8525 of the second user and the contact information 8526 of the second user may be stored.

85B is a diagram illustrating a database stored by the second relay server 1000b according to an embodiment of the present invention.

Referring to FIG. 85B , the second relay server 1000b may store the second user's information 8530 and the first user's information 8540 .

The second user information 8530 and the first user information 8540 stored by the second relay server 1000b may be described with reference to FIG. 85B .

86 is a flowchart illustrating a method of relaying a message transmitted from a first user to a second user by the first relay server 1000a and the second relay server 1000b according to an embodiment of the present invention.

In operation S8610, the first relay server 1000a may receive a first user input for transmitting a message to a second user.

For example, an application distributed by the first messenger service provider may be executed, and a first user input for transmitting a message to a second user using the executed application may be received.

In step S8620, the first relay server 1000a may request the second user to transmit a message based on the first messenger virtual ID of the second user.

Upon receiving the first user input for transmitting the message to the second user, the first relay server 1000a first instructs the second user to transmit the message to the second user based on the first messenger virtual ID of the second user. A request may be made to the messenger server 2000 .

In this case, the first relay server 1000a transmits the message, the first messenger ID of the first user as the sender ID, and the first messenger virtual ID of the second user as the receiver ID to the first messenger server 2000 . can

In operation S8630, the first messenger server 2000 may acquire address information of the relay server 1000 stored in correspondence to the first messenger virtual ID of the second user.

The first messenger server 2000 may acquire address information of the relay server 1000 stored in correspondence with the first messenger virtual ID of the second user, which is the ID of the receiver.

In operation S8640, the first messenger server 2000 may transmit a message to the first relay server 1000a.

The first messenger server 2000 may transmit the message received from the first relay server to the relay server 1000 which is the device of the receiver.

The first relay server 1000a may transmit the message, the first messenger ID of the first user as the sender's ID, and the first messenger virtual ID of the second user as the receiver's ID, to the first messenger server 2000 .

In operation S8650, the first relay server 1000a may acquire the second messenger ID of the second user based on the first messenger virtual ID of the second user.

The first relay server 1000a may acquire the stored second messenger ID of the second user corresponding to the first messenger virtual ID of the second user received from the first messenger server 2000 .

Also, the first relay server 1000a may acquire the stored second messenger service identification information and address information of the second messenger server 3000 in response to the second user's first messenger virtual ID.

In operation S8660, the first relay server 1000a may acquire the second messenger virtual ID of the first user based on the first messenger ID of the first user.

The first relay server 1000a may acquire the stored second messenger virtual ID of the first user corresponding to the first messenger virtual ID of the first user received from the first messenger server 2000 .

In step S8670, the first relay server 1000a may request the second messenger server 3000 to transmit a message to the second user based on the second messenger virtual ID of the first user.

The first relay server 1000a uses the address information of the second messenger server 3000 to use the message and the second messenger virtual ID of the first user as the sender's ID, and the second user's ID as the receiver's ID. 2 may be transmitted to the messenger server 3000 .

In operation S8680, the second messenger server 3000 may transmit a message to the second relay server 1000b.

The second messenger server 3000 may acquire the stored address information of the second relay server 1000b corresponding to the second messenger ID of the second user. In addition, the second messenger server 3000 uses the address information of the second relay server 1000b to send the second messenger virtual ID of the first user to the second relay server 1000b as the sender's ID, and the second user The second messenger ID of , as the ID of the receiver, may be transmitted to the second relay server 1000b.

In step S8690, the second relay server 1000b may display a message.

Upon receiving the message from the second messenger server 3000 , the second relay server 1000b may display the received message.

For example, a notification window indicating that a message has been received from the second user may be displayed. Also, for example, upon receiving a second user input for executing an application provided by the second messenger service provider, the second relay server 1000b may display an image indicating that a message has been received from the second user. have.

87 is a block diagram of a relay server 1000 according to an embodiment of the present invention.

87 , the relay server 1000 according to an embodiment may include a controller 1100 , a communication unit 1200 , and a storage unit 1300 . However, not all illustrated components are essential components. The relay server 1000 may be implemented by more components than the illustrated components, or the relay server 1000 may be implemented by fewer components.

The communication unit 1200 may communicate with various types of external devices according to various types of communication methods. For example, the communication unit 1200 may transmit/receive data to and from the devices 100 and 200 or the cloud servers 2000 and 3000 .

Also, the communication unit 1200 may include a communication port (not shown). The communication unit 1200 may receive a user's input from the devices 100 and 200 through a communication port, and may transmit/receive information about files or files to and from the devices 100 and 200 or the cloud servers 2000 and 3000 . Also, the communication unit 1200 may transmit/receive messages and message-related information to/from the devices 100 and 200 or the messenger servers 2000 and 3000 .

Communication ports may include, but are not limited to, 100BASE-TX ports, 1000BASE-T ports, 10 GBASE-T ports, Wi-Fi antennas, Bluetooth antennas, cellular antennas, and the like.

Also, the communication unit 1200 may include a network processor (not shown). The network processor may identify a packet received through the communication port and transmit the identified packet to the controller 1100 . Also, the communication unit 1200 may transmit the generated packet to a network through a communication port. Also, the communication unit 1200 may transmit/receive data according to various protocols. For example, the communication unit 1200 may transmit and receive data according to TCP/IP, UDP, FTP, or SMTP, but is not limited thereto.

Also, according to an embodiment, the communication unit 1200 may include a Wi-Fi chip, a Bluetooth chip, or a wireless communication chip.

The storage unit 1300 may store data or information.

Also, the storage unit 1300 may include at least one of an internal memory (not shown) and an external memory (not shown).

The internal memory includes a volatile memory (eg, dynamic RAM (DRAM), static RAM (SRAM), synchronous dynamic RAM (SDRAM), etc.), non-volatile memory (eg, one time programmable ROM (OTPROM), programmable memory (PROM)). ROM), Erasable and Programmable ROM (EPROM), Electrically Erasable and Programmable ROM (EEPROM), Mask ROM, Flash ROM, etc.), a hard disk drive (HDD), or a solid state drive (SSD). The external memory includes, for example, at least one of CF (Compact Flash), SD (Secure Digital), Micro-SD (Micro Secure Digital), Mini-SD (Mini Secure Digital), xD (extreme Digital), and Memory Stick. may include

Also, the storage unit 1300 may include a user database 1310 and a file database 1320 .

The user database 1310 may be a computer-readable and writable storage medium. The user database 1310 may store information about a user registered in the relay server 1000 . For example, the user database 1310 may store user's relay server account information, each user's device identification information, each user's file list, and information about each user's cloud server.

The file database 1320 may also be a computer-readable and writable storage medium. The file database 1320 may store information about a file to be relayed. The file may include, but is not limited to, a text file, an image file, an audio file, a video file, a spreadsheet, a presentation data file, an HTML file, and the like.

The file database 1320 may also store attribute information of each file. The property information of the file includes the file name, file format, location where the original file is stored, the original size of the file, the size of the copied data among the total size of the file, when the file is created, when the file is modified, when the file is accessed, when the file is accessed. It may include, but is not limited to, information about the access right to the file, the access range to the file, and a thumbnail image.

The controller 1100 may control the overall operation of the relay server 1000 .

When the cloud server is cloud storage, the storage unit 1300 includes access right information for the first cloud storage 2000 to which the first user is subscribed and access right to the second cloud storage 3000 to which the second user is subscribed. Information may be stored.

When the communication unit 1200 requests the data of the first user stored in the first cloud storage 2000 from the first cloud storage 2000 by using the access right information on the stored first cloud storage 2000, The controller 1100 transfers the first user's data received from the first cloud storage 2000 to the second cloud storage 3000 in response to a request by using the stored access right information on the second cloud storage 3000 . It is possible to control the communication unit to be transmitted.

In addition, when the communication unit 1200 receives a synchronization request indicating that the data of the first user has been changed from the first cloud storage 2000, the controller 1100, upon receiving the synchronization request, the second cloud storage ( 3000) may be updated with the changed data of the first user.

When the synchronization request includes location information indicating the location of the changed data in the file, the controller 1100, upon receiving the synchronization request, determines whether the changed data is data in the write-protection setting area based on the location information It is determined, and when the changed data is not the data of the write-protection setting area, a copy of the first user's data stored in the second cloud storage 3000 may be updated with the changed first user's data.

When the communication unit 1200 receives a synchronization request indicating that the copy of the first user's data stored in the second cloud storage 3000 has been changed from the second cloud storage 3000, the control unit 1100 receives the synchronization request Accordingly, the first user's data stored in the first cloud storage 2000 may be updated with a copy of the changed first user's data.

In addition, when the synchronization request includes location information indicating the location of the changed data in the copy of the file of the first user, the controller 1100, upon receiving the synchronization request, writes the changed data based on the location information It is determined whether the data is in the prohibit setting area, and if the changed data is not the data in the write protection setting area, the first user's data stored in the first cloud storage 2000 is updated with a copy of the changed first user's data. can

In addition, when the communication unit 1300 receives a read prohibition request for a part of the file among the data of the first user from the first device 100 of the first user, the control unit 1100 receives the read prohibition request. Accordingly, it is possible to obtain a file from the first cloud storage 2000 , delete a portion of the received file for which read prohibition is requested, and store the partially deleted file in the second cloud storage 3000 .

In addition, when the cloud server is a messenger server, the storage unit 1300 may store the authorization information of the first user on the first messenger server 2000 and the authorization information of the second user on the second messenger server 3000 . have.

When the communication unit 1300 receives the message of the first user from the first messenger server 2000 using the stored authority information of the first user, the control unit 1100 uses the stored authority information of the second user, The communication unit 1300 may be controlled to transmit the first user's message received from the first messenger server 2000 to the second messenger server 3000 .

In addition, when the communication unit 1300 receives a registration request for registering the second user as the first messenger friend of the first user from the device of the first user, the control unit 1300, as receiving the registration request, Create a first messenger virtual ID of 2 users, register the generated first messenger virtual ID of the second user in the first messenger server 2000, and authority information of the first user for the first messenger server 2000 Based on , the first messenger virtual ID of the second user may be registered in the first messenger server 2000 as the ID of the first user's messenger friend.

Also, in response to the registration request, the communication unit 1300 may transmit the first messenger virtual ID of the second user to the device of the first user as the ID of the second user in the first messenger.

In addition, when the communication unit 1300 receives a registration request for registering the first user as a second messenger friend of the second user from the second user's device, the control unit 1100 receives the registration request, The second user's authority to the second messenger server 3000 is generated, the second messenger virtual ID of the first user is generated, and the second messenger virtual ID of the first user is registered in the second messenger server 3000 Based on the information, the second messenger virtual ID of the first user may be registered in the second messenger server 3000 as the ID of the second user's messenger friend.

Also, in response to the registration request, the communication unit 1300 may transmit the second messenger virtual ID of the first user to the device of the second user as the ID of the first user in the second messenger.

In addition, the communication unit 1300 registers the first messenger virtual ID of the second user to the first messenger server 2000 by using the stored authorization information of the first user, and the registered second user's first messenger virtual ID Using the ID, a message of the first user for the second user may be received from the first messenger server 2000 .

In this case, the controller 1100 registers the second messenger virtual ID of the first user in the second messenger server 3000 using the stored authority information of the second user, and the registered second messenger virtual ID of the first user Using the ID, the communication unit may be controlled to transmit the message of the first user received from the first messenger server 2000 to the second messenger server 3000 .

In addition, the communication unit 1300 receives, from the device of the first user, a message transmission request for transmitting a message to the second user using the first messenger virtual ID of the second user as the ID of the receiver, and responds to the message transmission request Thus, the second messenger server 3000 may be requested to transmit the message to the second user by using the second messenger virtual ID of the first user as the sender's ID.

88 is a block diagram of the first device 100 according to an embodiment of the present invention. The device configuration of the second device 200 may include the device configuration of the first device 100 .

88 , the first device 100 according to an embodiment may include a control unit 170 , a communication unit 130 , a user input unit 145 , and a display unit 110 . However, not all illustrated components are essential components. The first device 100 may be implemented by more elements than the illustrated elements, and the first device 100 may be implemented by fewer elements than the illustrated elements.

The communication unit 130 may transmit/receive data to and from an external device. For example, the communication unit 130 may transmit/receive data to and from the second device 200 , the cloud servers 2000 and 3000 , or the relay server 1000 .

The user input unit 145 may receive a user input for sharing data from the first user. Also, the user input unit 145 may receive a user input for transmitting a message from the first user.

The display 110 may display an image or data for sharing data. Also, the display unit 110 may display an image or data for transmitting and receiving a message.

The controller 170 may control the overall operation of the device 100 .

For example, the controller 170 may request the first cloud storage 2000 to set the authority to obtain the first user's data from the first cloud storage 2000 to the relay server 1000 . For example, the controller 170 may request the second cloud storage 3000 to share the folder of the second user stored in the second cloud storage 3000 between the second user and the relay server 1000 . have.

Also, the controller 170 may transmit a sharing request for sharing the data of the first user between the first user and the second user to the relay server 1000 based on the input of the first user. In this case, the sharing request is, the relay server receives the data of the first user from the first cloud storage, based on the authority to obtain the data of the first user from the first cloud storage, and the received first user It may mean a request to store the data of the second user in a storage space in which the data of the second user is stored in the second cloud storage.

In addition, when the first device 100 operates as the second device 200 , the controller 170 stores data in the storage space of the second user in which the data of the second user in the second cloud storage 3000 is stored. The second cloud storage 3000 may be requested to set the storage authority to the relay server 1000 .

Also, the controller 170 may receive, from the second cloud storage 3000 , data of the second user stored in the storage space of the second user.

Also, the display 110 may display a list of data of the second user received from the second cloud storage 3000 . In this case, as the first user shares at least one of the data of the second user with the second user with respect to the data of the first user stored in the first cloud storage 2000, the relay server 1000 The user's file may be received from the first cloud storage 2000, and the received file may include data stored in the storage space of the second user based on the authority to store the data in the storage space of the second user. .

89 is a block diagram illustrating the configuration of the first device 100 according to another embodiment of the present disclosure. The device configuration of the second device 200 may include the device configuration of the first device 100 .

89, the configuration of the first device 100 is, for example, a mobile phone, a tablet PC, a PDA, an MP3 player, a kiosk, an electronic picture frame, a navigation device, a digital TV, a wrist watch, or It can be applied to various types of devices, such as a wearable device such as a head-mounted display (HMD).

89 , the first device 100 includes a display unit 110 , a control unit 170 , a memory 120 , a GPS chip 125 , a communication unit 130 , a video processor 135 , and an audio processor 140 . , a user input unit 145 , a microphone unit 150 , an imaging unit 155 , a speaker unit 160 , and at least one of a motion sensing unit 165 .

The display unit 110 may include a display panel 111 and a controller (not shown) for controlling the display panel 111 . The display panel 111 includes various types of displays such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display, an active-matrix organic light-emitting diode (AM-OLED), and a plasma display panel (PDP). can be The display panel 111 may be implemented to be flexible, transparent, or wearable. The display unit 110 may be provided as a touch screen (not shown) by being coupled to the touch panel 147 of the user input unit 145 . For example, the touch screen (not shown) may include an integrated module in which the display panel 111 and the touch panel 147 are coupled in a stacked structure.

The memory 120 may include at least one of an internal memory (not shown) and an external memory (not shown).

The built-in memory includes, for example, a volatile memory (eg, Dynamic RAM (DRAM), Static RAM (SRAM), Synchronous Dynamic RAM (SDRAM), etc.), a non-volatile memory (eg, One Time Programmable ROM (OTPROM)). ), Programmable ROM (PROM), Erasable and Programmable ROM (EPROM), Electrically Erasable and Programmable ROM (EEPROM), Mask ROM, Flash ROM, etc.), hard disk drive (HDD), or solid state drive (SSD). may include According to an embodiment, the controller 170 may load a command or data received from at least one of the non-volatile memory or other components into the volatile memory and process it. Also, the controller 170 may store data received or generated from other components in a non-volatile memory.

The external memory includes, for example, at least one of CF (Compact Flash), SD (Secure Digital), Micro-SD (Micro Secure Digital), Mini-SD (Mini Secure Digital), xD (extreme Digital), and Memory Stick. may include

The controller 170 may control the display 110 so that a part of the content stored in the memory 120 is displayed on the display 110 . In other words, the controller 170 may display a part of the content stored in the memory 120 on the display 110 . Alternatively, when a user gesture is made in one area of the display unit 110 , the controller 170 may perform a control operation corresponding to the user's gesture.

The controller 170 may include at least one of a RAM 171 , a ROM 172 , a CPU 173 , a graphic processing unit (GPU) 174 , and a bus 175 . RAM 171 , ROM 172 , CPU 173 , GPU 174 , and the like may be connected to each other through a bus 175 .

The CPU 173 accesses the memory 120 and performs booting using the O/S stored in the memory 120 . In addition, various operations are performed using various programs, contents, data, etc. stored in the memory 120 .

The ROM 172 stores an instruction set for system booting and the like. For example, in the mobile terminal 100, when a turn-on command is input and power is supplied, the CPU 173 copies the O/S stored in the memory 120 to the RAM 171 according to the command stored in the ROM 172, You can boot the system by running O/S. When booting is completed, the CPU 173 copies various programs stored in the memory 120 to the RAM 171 , and executes the programs copied to the RAM 171 to perform various operations. When the booting of the first device 100 is completed, the GPU 174 displays the UI screen on the area of the display 110 . Specifically, the GPU 174 may generate a screen on which an electronic document including various objects such as content, icons, and menus is displayed. The GPU 174 calculates attribute values such as coordinate values, shape, size, color, etc., at which each object is to be displayed according to the layout of the screen. In addition, the GPU 174 may generate screens of various layouts including objects based on the calculated attribute values. The screen generated by the GPU 174 may be provided to the display unit 110 and displayed on each area of the display unit 110 .

The GPS chip 125 may receive a GPS signal from a Global Positioning System (GPS) satellite and calculate the current location of the first device 100 . The controller 170 may calculate the user's location using the GPS chip 125 when using a navigation program or when the user's current location is required.

The communication unit 130 may communicate with various types of external devices according to various types of communication methods. The communication unit 130 may include at least one of a Wi-Fi chip 131 , a Bluetooth chip 132 , a wireless communication chip 133 , and an NFC chip 134 . The control unit 170 may communicate with various external devices using the communication unit 130 .

The Wi-Fi chip 131 and the Bluetooth chip 132 may perform communication using a WiFi method and a Bluetooth method, respectively. In the case of using the Wi-Fi chip 131 or the Bluetooth chip 132, various types of connection information such as an SSID and a session key may be first transmitted and received, and then various types of information may be transmitted/received after communication connection using this. The wireless communication chip 133 refers to a chip that performs communication according to various communication standards such as IEEE, ZigBee, 3rd Generation (3G), 3rd Generation Partnership Project (3GPP), and Long Term Evoloution (LTE). The NFC chip 134 refers to a chip operating in a Near Field Communication (NFC) method using a 13.56 MHz band among various RF-ID frequency bands such as 135 kHz, 13.56 MHz, 433 MHz, 860 to 960 MHz, and 2.45 GHz.

The video processor 135 may process video data included in content received through the communication unit 130 or content stored in the memory 120 . The video processor 135 may perform various image processing, such as decoding, scaling, noise filtering, frame rate conversion, and resolution conversion, on video data.

The audio processor 140 may process audio data included in the content received through the communication unit 130 or the content stored in the memory 120 . In the audio processor 140 , various processes such as decoding, amplification, and noise filtering on audio data may be performed.

When a playback program for multimedia content is executed, the controller 170 drives the video processor 135 and the audio processor 140 to play the corresponding content. The speaker unit 160 may output audio data generated by the audio processor 140 .

The user input unit 145 may receive various commands from the user. The user input unit 145 may include at least one of a key 146 , a touch panel 147 , and a pen recognition panel 148 .

The key 146 may include various types of keys, such as mechanical buttons and wheels, which are formed in various areas such as the front, side, or rear of the main body of the first device 100 .

The touch panel 147 may detect a user's touch input and output a touch event value corresponding to the sensed touch signal. When the touch panel 147 is combined with the display panel 111 to form a touch screen (not shown), the touch screen may be implemented with various types of touch sensors such as capacitive type, pressure sensitive type, and piezoelectric type. The capacitive type is a method of calculating touch coordinates by sensing micro-electricity generated by the user's body when a part of the user's body is touched on the touch screen surface using a dielectric coated on the touch screen surface. The decompression type includes two electrode plates embedded in the touch screen, and when the user touches the screen, the touch coordinates are calculated by detecting that the upper and lower plates of the touched point come into contact and current flows. A touch event occurring on a touch screen may be mainly generated by a human finger, but may also be generated by an object made of a conductive material capable of applying a change in capacitance.

The pen recognition panel 148 detects a pen proximity input or a touch input according to the operation of the user's touch pen (eg, a stylus pen, a digitizer pen), and detects a pen proximity event or pen A touch event can be output. The pen recognition panel 148 may be implemented by, for example, an EMR method, and may detect a touch or proximity input according to the proximity of the pen or a change in the intensity of an electromagnetic field due to the touch. In detail, the pen recognition panel 148 includes an electromagnetic induction coil sensor (not shown) having a grid structure and an electronic signal processing unit (not shown) that sequentially provides an AC signal having a predetermined frequency to each loop coil of the electromagnetic induction coil sensor. ) may be included. When a pen having a built-in resonance circuit exists near the loop coil of the pen recognition panel 148, a magnetic field transmitted from the loop coil generates a current based on mutual electromagnetic induction in the resonance circuit in the pen. Based on this current, an induced magnetic field is generated from the coil constituting the resonance circuit in the pen, and the pen recognition panel 148 detects the induced magnetic field from the loop coil in the signal receiving state, so that the pen approaching position or A touch position may be sensed. The pen recognition panel 148 may be provided with a predetermined area under the display panel 111 , for example, an area capable of covering the display area of the display panel 111 .

The microphone unit 150 may receive a user's voice or other sound and convert it into audio data. The controller 170 may use the user's voice input through the microphone unit 150 in a call operation, or convert it into audio data and store it in the memory 120 .

The imaging unit 155 may capture a still image or a moving image according to a user's control. The imaging unit 155 may be implemented in plurality, such as a front camera or a rear camera.

When the imaging unit 155 and the microphone unit 150 are provided, the control unit 170 performs a control operation according to a user voice input through the microphone unit 150 or a user motion recognized by the imaging unit 155 . may be For example, the first device 100 may operate in a motion control mode or a voice control mode. When operating in the motion control mode, the controller 170 may activate the imaging unit 155 to capture an image of the user, track a change in the user's motion, and perform a corresponding control operation. When operating in the voice control mode, the controller 170 may operate in a voice recognition mode in which a user voice input through the microphone unit 150 is analyzed and a control operation is performed according to the analyzed user voice.

The motion detection unit 165 may detect a movement of the body of the first device 100 . The first device 100 may be rotated or inclined in various directions. In this case, the motion detecting unit 165 may detect motion characteristics such as a rotation direction, an angle, and a tilt using at least one of various sensors such as a geomagnetic sensor, a gyro sensor, and an acceleration sensor.

In addition, although not shown in FIG. 89, in the embodiment, a USB port to which a USB connector can be connected in the first device 100, a headset, a mouse, various external input ports for connecting with various external terminals such as LAN, It may further include a DMB chip for receiving and processing a Digital Multimedia Broadcasting (DMB) signal, various sensors, and the like.

Names of components of the above-described first device 100 may vary. In addition, the first device 100 according to the present disclosure may be configured to include at least one of the above-described components, and some components may be omitted or may further include additional other components.

An embodiment of the present invention may also be implemented in the form of a recording medium including instructions executable by a computer, such as a program module executed by a computer. Computer-readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. Also, computer-readable media may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism, and includes any information delivery media.

The above description of the present invention is for illustration, and those of ordinary skill in the art to which the present invention pertains can understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a dispersed form, and likewise components described as distributed may be implemented in a combined form.

The scope of the present invention is indicated by the following claims rather than the above detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention. do.

Claims (26)

a storage unit for storing access right information for the first cloud storage to which the first user is subscribed and access right information for the second cloud storage to which the second user is subscribed;
a communication unit for requesting data of the first user stored in the first cloud storage from the first cloud storage by using the stored access right information on the first cloud storage; and
and a control unit for controlling the communication unit to transmit the data of the first user received from the first cloud storage to the second cloud storage in response to the request by using the stored access right information for the second cloud storage do,
The communication unit,
receiving, from the first device of the first user, a read prohibition request for a portion of the file among the data of the first user;
The control unit is
Upon receiving the read prohibition request, the file is obtained from the first cloud storage, the read prohibition requested portion of the obtained files is deleted, and the partially deleted file is stored in the second cloud storage. Stored, relay server.
The method of claim 1,
The access right information for the first cloud storage includes an account of the relay server registered in the first cloud storage,
In response to the account of the relay server registered in the first cloud storage, a setting value indicating the right to receive the data of the first user from the first cloud storage is set in the first cloud storage, relay server.
3. The method of claim 2,
A setting value indicating a right to receive from the first cloud storage set in the first cloud storage is,
In response to receiving a request from the first user's device to share the data of the first user stored in the first cloud storage with the relay server, the first cloud storage is configured.
The method of claim 1,
The access right information for the second cloud storage includes an account of the relay server registered in the second cloud storage,
In response to the account of the relay server registered in the second cloud storage, a setting value indicating the right to store data in the storage space of the second user is set in the second cloud storage.
5. The method of claim 4,
A setting value indicating the right to store data in the storage space of the second user set in the second cloud storage is,
The second cloud storage is configured in response to receiving a request from the second user's device to share the storage space of the second user with the relay server.
The method of claim 1,
The communication unit,
receiving a synchronization request indicating that the data of the first user has been changed from the first cloud storage;
The control unit is
Upon receiving the synchronization request, updating a copy of the first user's data stored in the second cloud storage with the changed first user's data,
The copy of the first user's data is data copied from the first user's data in the first cloud storage to the second cloud storage by the relay server.
7. The method of claim 6,
The first user's data includes a file,
The synchronization request includes location information indicating the location of the changed data in the file,
The control unit is
Upon receiving the synchronization request, based on the location information, it is determined whether the changed data is data of a write-protection setting area, and when the changed data is not data of a write-protection setting area, the second cloud storage update a copy of the first user's data stored in the changed data of the first user,
and the write-protection setting area is an area in the copy of the first user's data set not to be changed by the relay server.
The method of claim 1,
The communication unit,
receiving a synchronization request from the second cloud storage indicating that a copy of the first user's data stored in the second cloud storage has changed;
The control unit is
Upon receiving the synchronization request, updating the first user's data stored in the first cloud storage to a copy of the changed first user's data,
The copy of the first user's data is data copied from the first user's data in the first cloud storage to the second cloud storage by the relay server.
9. The method of claim 8,
The first user's data includes a file,
the synchronization request includes location information indicating the location of the changed data in the copy of the file of the first user;
The control unit is
Upon receiving the synchronization request, based on the location information, it is determined whether the changed data is data of a write-protection setting area, and when the changed data is not data of a write-protection setting area, the first cloud storage update the first user's data stored in the to a copy of the changed first user's data,
and the write-protection setting area is an area in the file of the first user set not to be changed by the relay server.
delete A method for a relay server to share data between a plurality of devices, the method comprising:
storing access right information for the first cloud storage to which the first user is subscribed and access right information for the second cloud storage to which the second user is subscribed;
requesting the first user's data stored in the first cloud storage from the first cloud storage by using the access right information on the first cloud storage; and
Transmitting the data of the first user received from the first cloud storage to the second cloud storage in response to the request by using the access right information for the second cloud storage,
receiving, from the first device of the first user, a read prohibition request for a portion of the file among the data of the first user;
obtaining the file from the first cloud storage in response to receiving the read prohibit request;
deleting the read-prohibited portion of the acquired file; and
The data relay method further comprising the step of storing the partially deleted file in the second cloud storage.
12. The method of claim 11,
The access right information for the first cloud storage includes an account of the relay server registered in the first cloud storage,
In response to the account of the relay server registered in the first cloud storage, a setting value indicating the right to receive the data of the first user from the first cloud storage is set in the first cloud storage, data relay method.
13. The method of claim 12,
A setting value indicating a right to receive from the first cloud storage set in the first cloud storage is,
In response to receiving a request from the device of the first user to share the data of the first user stored in the first cloud storage with the relay server, the first cloud storage is configured.
12. The method of claim 11,
The access right information for the second cloud storage includes an account of the relay server registered in the second cloud storage,
In response to the account of the relay server registered in the second cloud storage, a setting value indicating the right to store data in the storage space of the second user is set in the second cloud storage.
15. The method of claim 14,
A setting value indicating the right to store data in the storage space of the second user set in the second cloud storage is,
The method of claim 1, wherein the second cloud storage is set in response to receiving a request to share the storage space of the second user with the relay server from the device of the second user.
12. The method of claim 11,
The data relay method is
receiving a synchronization request indicating that the data of the first user has changed from the first cloud storage; and
In response to receiving the synchronization request, the method further comprising: updating a copy of the first user's data stored in the second cloud storage with the changed first user's data;
The copy of the first user's data is data that the first user's data in the first cloud storage is copied to the second cloud storage by the relay server.
17. The method of claim 16,
The first user's data includes a file,
The synchronization request includes location information indicating the location of the changed data in the file,
The step of updating a copy of the first user's data stored in the second cloud storage with the changed data of the first user,
upon receiving the synchronization request, determining whether the changed data is data of a write-protection setting area based on the location information; and
When the changed data is not the data of the write-protection setting area, updating a copy of the first user's data stored in the second cloud storage with the changed first user's data;
and the write-protection setting area is an area within the copy of the first user's data set not to be changed by the relay server.
12. The method of claim 11,
The data relay method is
receiving, from the second cloud storage, a synchronization request indicating that a copy of the first user's data stored in the second cloud storage has been changed; and
In response to receiving the synchronization request, the method further comprising: updating the first user's data stored in the first cloud storage to a copy of the changed first user's data;
The copy of the first user's data is data that the first user's data in the first cloud storage is copied to the second cloud storage by the relay server.
19. The method of claim 18,
The first user's data includes a file,
the synchronization request includes location information indicating the location of the changed data in the copy of the file of the first user;
The step of updating the first user's data stored in the first cloud storage to a copy of the changed first user's data includes:
upon receiving the synchronization request, determining whether the changed data is data of a write-protection setting area based on the location information; and
When the changed data is not the data of the write-protection setting area, updating the first user's data stored in the first cloud storage to a copy of the changed first user's data;
and the write-protection setting area is an area in the file of the first user set not to be changed by the relay server.
delete a storage unit for storing the first user's authority information for the first messenger server and the second user's authority information for the second messenger server;
a communication unit configured to receive a message of the first user from a first messenger server by using the stored authority information of the first user; and
a control unit controlling the communication unit to transmit the message of the first user received from the first messenger server to the second messenger server by using the stored authority information of the second user;
including,
The first user's authority information for the first messenger server is information about the authority to register a third user who is subscribed to the first messenger server to the first messenger server as a messenger friend of the first user, ,
The second user's authority information for the second messenger server is information about the authority to register a fourth user who is subscribed to the second messenger server to the second messenger server as a messenger friend of the second user. relay server.
delete 22. The method of claim 21,
The communication unit,
receiving a registration request for registering the second user as a first messenger friend of the first user from the device of the first user;
The control unit is
Upon receiving the registration request, a first messenger virtual ID of the second user is generated, and the generated first messenger virtual ID of the second user is registered in a first messenger server, and Registering the first messenger virtual ID of the second user in the first messenger server as the ID of the messenger friend of the first user based on the authorization information of the first user;
The communication unit, in response to the registration request, transmits the first messenger virtual ID of the second user to the device of the first user as the ID of the second user in the first messenger.
22. The method of claim 21,
The communication unit,
receiving a registration request for registering the first user as a second messenger friend of a second user from the device of the second user;
The control unit is
Upon receiving the registration request, a second messenger virtual ID of the first user is generated, and the generated second messenger virtual ID of the first user is registered in a second messenger server, and Registering the second messenger virtual ID of the first user in the second messenger server as the ID of the messenger friend of the second user based on the authority information of the second user;
The communication unit, in response to the registration request, transmits the second messenger virtual ID of the first user to the device of the second user as the ID of the first user in the second messenger.
22. The method of claim 21,
The communication unit,
Registering the first messenger virtual ID of the second user to the first messenger server using the stored authority information of the first user, and using the registered first messenger virtual ID of the second user, the second user Receive a message of the first user for the second user from a first messenger server,
The control unit is
Registering the second messenger virtual ID of the first user in the second messenger server using the stored authority information of the second user, and using the registered second messenger virtual ID of the first user, A relay server for controlling the communication unit to transmit the message of the first user received from the first messenger server to the second messenger server.
26. The method of claim 25,
The communication unit,
receiving, from the device of the first user, a message transmission request for transmitting a message to the second user using the first messenger virtual ID of the second user as an ID of a recipient;
in response to the message transmission request, requesting the second messenger server to transmit the message to the second user by using the second messenger virtual ID of the first user as an ID of a sender.

Images