WO2018076841A1 - Data sharing method, apparatus, storage medium and server - Google Patents

Abstract

Provided by the present invention are a data sharing method, apparatus, storage medium and server. The method comprises: acquiring a sharing request sent by a first client, the sharing request comprising identification information of user data to be shared and identity information of a second client; generating a data sharing link according to the identification information; and sending the data sharing link to the second client. Data sharing may be completed by means of a cloud server sending a data sharing link directly to a second client, thereby improving sharing efficiency.

Description

Data sharing method, device, storage medium and server

This application is required to be submitted to the Chinese Patent Office on October 25, 2016, and the application number is 201610939525.0. The priority of the Chinese patent application entitled "Data Sharing Method and Apparatus" is hereby incorporated by reference in its entirety.

Technical field

The present invention relates to the field of computer technologies, and in particular, to a data sharing method, apparatus, storage medium, and server.

Background technique

With the continuous development of network technology, the way of storing data has gradually changed from hardware storage (such as mobile hard disk, U disk) to cloud server storage. The user can store the terminal data in the cloud server anytime and anywhere through the client of the cloud server installed in the terminal, and the user can also share the terminal data in the cloud server to other users. However, in the existing sharing method, the user needs to perform multiple interactions with the cloud server, which makes the entire sharing process complicated, takes a long time, and brings inconvenience to the user.

technical problem

The embodiment of the invention provides a data sharing method, device, storage medium and server, so as to simplify the whole sharing process and improve sharing efficiency.

Technical solution

The invention provides a data sharing method, which comprises:

Obtaining a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client;

Generating a data sharing link according to the identification information, where the data sharing link is used to acquire the user data to be shared;

Sending the data sharing link to the second client according to the identity information.

The embodiment of the invention further provides a data sharing device, including:

a first obtaining unit, configured to acquire a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client;

a generating unit, configured to generate a data sharing link according to the identifier information, where the data sharing link is used to acquire the user data to be shared;

And a sending unit, configured to send the data sharing link to the second client according to the identity information.

Embodiments of the present invention also provide a storage medium storing a plurality of instructions, the plurality of instructions being adapted to cause a computer to perform a data sharing method as described above when running on a computer.

The embodiment of the invention further provides a server, comprising a processor and a memory, the memory storing a plurality of instructions, the processor loading the instructions in the memory for performing the following steps:

Obtaining a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client;

Generating a data sharing link according to the identification information, where the data sharing link is used to acquire the user data to be shared;

Sending the data sharing link to the second client according to the identity information.

Beneficial effect

The embodiment of the invention provides a data sharing method, device, storage medium and server, so as to simplify the whole sharing process and improve sharing efficiency.

DRAWINGS

FIG. 1 is a flowchart of a data sharing method according to an embodiment of the present invention.

FIG. 2 is still another flowchart of a data sharing method according to an embodiment of the present invention.

FIG. 3 is a schematic structural diagram of a data sharing apparatus according to an embodiment of the present invention.

FIG. 4 is still another schematic structural diagram of a data sharing apparatus according to an embodiment of the present invention.

FIG. 5 is a schematic diagram of a scenario of a data sharing system according to an embodiment of the present invention.

FIG. 6 is a schematic structural diagram of a server according to an embodiment of the present invention.

FIG. 7 is another schematic structural diagram of a server according to an embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The terms "first", "second", and the like in the present invention may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, a first control may be referred to as a second control, and similarly, a second control may be referred to as a first control, without departing from the scope of the present invention. Both the first control and the second control are controls, but they are not the same control. Furthermore, the terms "comprises" and "comprising" and "comprising" are intended to cover a non-exclusive inclusion.

In a first aspect, an embodiment of the present invention provides a data sharing method, where the method includes:

Obtaining a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client;

Generating a data sharing link according to the identification information, where the data sharing link is used to acquire the user data to be shared;

Sending the data sharing link to the second client according to the identity information.

In some embodiments, before the obtaining the sharing request sent by the first client, the method further includes:

Obtaining user data of the first client;

Obtaining identification information corresponding to the user data.

In some embodiments, before the generating the data sharing link according to the identifier information, the method further includes:

Determining, according to the identity information of the second client, whether the second client user is an unfamiliar user;

If it is determined that the second client user is an unfamiliar user, sending a prompt message to the first client;

Obtaining operation information that is fed back by the first client according to the prompt information;

The generating the data sharing link according to the identifier information comprises: generating a data sharing link according to the operation information and the identifier information.

In some embodiments, the determining, according to the identity information of the second client, whether the second client user is an unfamiliar user comprises:

Obtaining, according to the identity information of the second client, a history sharing record corresponding to the identity information and the first client user;

Determining, according to the history sharing record, whether the second client user is an unfamiliar user.

In some embodiments, the generating the data sharing link according to the identifier information comprises: generating a data sharing link according to the identifier information and the identity information of the second client.

In some embodiments, the sharing request further includes a preset number of accesses;

After the sending the data sharing link to the second client according to the identity information, the method further includes: acquiring a number of accesses to access the user data to be shared by using the data sharing link;

Determining whether the number of accesses is equal to the preset number of accesses;

If the number of accesses is equal to the preset number of accesses, the data sharing link is cleared.

In some embodiments, the identification information is a storage address of user data within the cloud server.

Please refer to FIG. 1. FIG. 1 is a flowchart of a data sharing method according to an embodiment of the present invention. The data sharing method is applied to the cloud server. Of course, in other embodiments, the data sharing method can also be applied to other devices, and is not specifically limited herein.

In some embodiments, the data sharing method includes the following implementation steps:

Step S101: Acquire a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client.

Step S102: Generate a data sharing link according to the identifier information, where the data sharing link is used to acquire the user data to be shared;

Step S103: Send the data sharing link to the second client according to the identity information.

The data sharing method in this embodiment will be described in detail below with reference to FIG. 1.

In step S101, after the first client user synchronizes the user data to the cloud server, the cloud server stores the user data to the corresponding storage area, and each user data corresponds to a storage address, and the cloud server uses the storage address as the storage address. The identification information of the user data, and the identification information is sent to the first client.

In some embodiments, the identification information of the user data is a storage address of the user data within the cloud server. Of course, in other embodiments, the identification information of the user data may be other information used to identify the user data, as long as the cloud server can find the corresponding user data according to the identification information, and no specific limitation is imposed herein.

When the first client user wants to share the user data to the second client user, the first client user logs in to the client of the cloud server through the terminal, and enters the sharing interface through the sharing portal. After the first client user selects the user data to be shared and enters the identity information of the second client, the first client obtains the identifier information of the user data to be shared and the identity information of the second client, and according to the identifier of the user data to be shared. The information and the identity information of the second client generate a sharing request and send the sharing request to the cloud server. The cloud server will get the sharing request.

It should be noted that the identity information includes the user name of the client user, the user's phone number, and/or the registered mailbox, and the specific content of the identity information is not limited herein. In addition, the identity information may include one type of information, and may also include a variety of information. For example, the identity information is the user's phone number of the client user. Of course, the identity information may also be composed of the registered email address and the user's telephone number of the client user, and no specific restrictions are imposed here.

In the steps S102 and S103, after receiving the sharing request sent by the first client, the cloud server parses the identifier information of the user data to be shared in the sharing request and the identity information of the second client. The cloud server generates a data sharing link according to the identifier information, where the data sharing link is used to obtain the user data to be shared shared by the first client user. At the same time, the cloud server sends the data sharing link to the second client according to the identity information of the second client. After the second client user clicks the data sharing link, the cloud server can obtain the user data to be shared corresponding to the identifier information in the data sharing link, and present the data to be shared to the second client user. Second, the client user can browse or download the shared user data shared by the first client user.

In some embodiments, in order to protect the security of the first client user data, avoiding the second client user inadvertently leaking the first client user data, etc., in step S102, the cloud server will be based on the user to be shared. The identification information of the data and the identity information of the second client generate a data sharing link. When other client users intercept the data sharing link or the second client user forwards the data sharing link to other client users, since the identity information of other client users is different from the identity information in the data sharing link, the other The client user cannot access the first client user data through the data sharing link. That is to say, only the second client has the right to access the user data to be shared through the data sharing link, and other client users have no right to access the user data to be shared, thereby ensuring the security of the first client user data.

In some embodiments, the sharing request sent by the first client is obtained, where the sharing request includes the identification information of the user data to be shared and the identity information of the second client; generating a data sharing link according to the identification information; The identity information sends the data sharing link to the second client. In the data sharing method, the cloud server directly sends the data sharing link to the second client, and the data sharing can be completed without the first client user performing other operations, which simplifies the entire sharing process and saves the first client user. time.

Please refer to FIG. 2. FIG. 2 is still another flowchart of a data sharing method according to an embodiment of the present invention. The data sharing method is applied to the cloud server. Of course, in other embodiments, the data sharing method can also be applied to other devices, and is not specifically limited herein.

In some embodiments, the data sharing method comprises:

Step S201: Acquire user data of the first client, and obtain identifier information corresponding to the user data.

Step S202: Acquire a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared, identity information of the second client, and preset access times.

Step S203: Determine, according to the identity information of the second client, whether the second client user is an unfamiliar user, and if it is determined that the second client user is an unfamiliar user, perform step S209, and if the second client is determined If the end user is not an unfamiliar user, step S204 is performed;

Step S204: Generate a data sharing link according to the identifier information, where the data sharing link is used to obtain the user data to be shared;

Step S205: Send the data sharing link to the second client according to the identity information.

Step S206: Acquire a number of accesses to access the user data to be shared through the data sharing link;

Step S207: determining whether the number of accesses is equal to the preset number of accesses, and if so, executing step S208, and if not, executing step S206;

Step S208: Clear the data sharing link;

Step S209: Send prompt information to the first client.

Step S210: Acquire operation information fed back by the first client according to the prompt information.

Step S211: Generate a data sharing link according to the operation information and the identification information, and return to step S205.

The above data sharing method will be described in detail below with reference to FIG.

In step S201, after the first client user logs in to the client of the cloud server, the user data in the terminal is uploaded to the cloud server through the upload button in the client. The cloud server will obtain the user data sent by the first client, and store the user data in the corresponding storage area of the cloud server. In the cloud server, each user data corresponds to a storage address. The cloud server obtains the storage address and uses the storage address as the identification information of the user data, that is, obtains the identifier information corresponding to the user data, and sends the identifier information to the first client.

Here, the identification information of the user data may be a storage address of the user data in the cloud server, and may of course be other information that plays a role of identification, as long as the cloud server can find the corresponding user data according to the identification information. No specific restrictions are made here.

In step S202, when the first client user wants to share the user data to the second client user, the first client user logs in to the sharing server through the sharing portal by logging in to the client of the cloud server through the terminal. The first client user selects the user data to be shared, and inputs the identity information of the second client and the preset number of accesses. After that, the first client obtains the identification information of the user data to be shared, the identity information of the second client, and the preset number of accesses, and according to the identification information of the user data to be shared, the identity information of the second client, and the preset access. Generate a sharing request as many times and send the sharing request to the cloud server. The cloud server will get the sharing request.

It should be noted that the identity information includes the user name of the client user, the user's phone number, and/or the registered mailbox, and the specific content of the identity information is not limited herein. In addition, the identity information may include one type of information, and may also include a variety of information. For example, the identity information is the user's phone number of the client user. Of course, the identity information may also be composed of the registered email address and the user's telephone number of the client user, and no specific restrictions are imposed here.

The preset access times refer to the number of times the first client user wants to share user data to be accessed. For example, the first client user only wants the second client user to access the user data to be shared once. Setting the preset access times can prevent the second client user from sending the subsequently generated data sharing link to other clients and inadvertently causing the first client user data to leak.

In step S203, after the cloud server obtains the sharing request sent by the first client, the cloud server obtains the identification information of the user data to be shared, the identity information of the second client, and the preset access times by parsing the sharing request.

The cloud server determines, according to the identity information of the second client, whether the second client user is an unfamiliar user. Specifically, the cloud server determines, according to the identity information of the second client, whether the second client user has a communication interaction with the first client user, where the communication interaction includes a phone, a short message, a shared data, and the like.

In some embodiments, determining whether the second client user is an unfamiliar user according to the identity information of the second client may be implemented by: acquiring the first client corresponding to the identity information according to the identity information of the second client The history sharing record of the end user; determining whether the second client user is an unfamiliar user according to the history sharing record.

For example, when the first client user has never had a communication interaction with the second client user, the cloud server will not obtain the communication interaction with the first client user according to the identity information of the second client. At this time, the cloud The server will determine that the second client user is an unfamiliar user. If the first client user has shared its user data with the second client user, the cloud server will obtain the history sharing record with the first client user according to the identity information of the second client user, and according to the history The sharing record determines that the second client user is not an unfamiliar user.

It can be understood that, in other embodiments, the method for the cloud server to determine whether the second client user is an unfamiliar user is not limited to the foregoing, and may be determined by other methods, and is not specifically limited herein.

When the step S203 determines that the second client user is not an unfamiliar user, the cloud server generates a data sharing link according to the identifier information, where the data sharing link is used to obtain the to-be-shared user data shared by the first client user. At the same time, the cloud server sends the data sharing link to the second client according to the identity information of the second client, that is, step S204 and step S205 are performed. In this way, after the second client user clicks the data sharing link, the cloud server can obtain the to-be-shared user data corresponding to the identifier information in the data sharing link, and present the to-shared user data to the second client user. In this way, the second client user can browse or download the shared user data shared by the first client user.

In steps S206 to S208, after the client user completes accessing the data to be shared through the data sharing link, the cloud server acquires the number of accesses to access the user data to be shared through the data sharing link, and determines whether the number of accesses is Equal to the preset number of visits. If it is determined that the number of accesses is not equal to the preset number of accesses, it indicates that the number of accesses is less than the preset number of accesses. At this time, the cloud server returns to step S206, that is, each time the data sharing link is accessed through the data sharing link. After that, the cloud server performs cumulative access times. If the number of accesses is equal to the preset number of accesses, the cloud server will perform step S208 to clear the data sharing link. Thereafter, if another client user clicks on the data sharing link, the cloud server will feed back a prompt message of an invalid address link.

For example, when the first client user sets the preset access times to 2 times, if the second client user accesses the data to be shared through the data sharing link for the first time, the cloud server obtains the data to be shared by the data sharing link. The number of accesses is 1, and the cloud server will determine that the number of accesses 1 is not equal to the preset number of accesses 2, and the cloud server will wait for the next access. After the second client user accesses the data to be shared again through the data sharing link, the number of accesses obtained by the cloud server is 2, and it is determined that the number of accesses is equal to the preset number of accesses 2. At this time, the cloud server will clear the data sharing. The link makes the data sharing link invalid. If the second client user forwards the data sharing link to other client users at this time, when the other client user clicks the data sharing link again, the cloud server will feedback the prompt information of the invalid address link to other clients, thereby ensuring The security of the first client user data.

When it is determined in step S203 that the second client user is an unfamiliar user, in order to further protect the security of the first client user data, the cloud server sends a prompt message to the first client, that is, step S209 is performed. The prompt information is used to prompt the first client user whether to continue to share data with the unfamiliar user.

If the first client user chooses to continue sharing data with the unfamiliar user, the first client will obtain the operation information of the first client user, and send the operation information to the cloud server. The cloud server will obtain the operation information fed back by the first client according to the prompt information, that is, step S210 is performed. After receiving the operation information for continuing to share data with the unfamiliar user, the cloud server generates a data sharing link according to the identification information, that is, performs step S211, and returns to step S205.

If the first client user inadvertently enters the identity information of the second client user, the user will choose to cancel the sharing of data to the unfamiliar user, and then the first client will obtain the operation information for canceling the sharing of data to the unfamiliar user. And sending the operation information for canceling the data sharing to the unfamiliar user to the cloud server, so that the cloud server ends the sharing operation according to the operation information of the data sharing to the unfamiliar user. Therefore, the phenomenon that the user data is leaked due to the negligence of the first client user is effectively avoided.

In order to explain the content of the data sharing method more clearly, the following will be explained in conjunction with a specific application scenario.

After the first user logs in to the cloud server client in the mobile phone, the travel photos in the mobile phone are synchronized to the cloud server. The cloud server will store the travel photo and obtain the address information of the travel photo, and use the address information as the identification information of the travel photo. The cloud server sends the identification information of the travel photo to the first client.

When the first user wishes to share the travel photo to the second user, the first user clicks on the sharing portal of the client interface. The first user selects the travel photo in the sharing interface, and inputs the second user's phone number at the corresponding location, and sets the preset access count to 1. After the first user clicks the confirmation, the first user's client will obtain the identification information of the travel photo, the second user's phone number and the preset access times, and according to the identification information of the travel photo, the second user's phone number and the preset. The number of visits generates a sharing request and sends a sharing request to the cloud server.

The cloud server will obtain the identification information of the travel photo, the phone number of the second user, and the preset access times by parsing the sharing request, and determine whether the second user has performed data sharing with the first user according to the second user's phone number. If it is determined that the second user has never performed data sharing with the first user, the cloud server determines that the second user is an unfamiliar user, and the cloud server sends a prompt message to the first client, where the prompt information is used to prompt the first Whether a user needs to continue to share data with unfamiliar users.

If the first user selects "Yes" at this time, the first client will send "Yes" operation information to the cloud server. After receiving the operation information of the “Yes”, the cloud server generates a data sharing link of the travel photo according to the identifier information, and sends the data sharing link to the second client corresponding to the phone number of the second user. In this way, the second user can click on the data sharing link to access the first user's travel photos.

After the second user completes accessing the travel photos of the first user, the cloud server acquires the number of accesses currently accessing the data to be shared through the data sharing link, and determines whether the current number of accesses is equal to the preset number of accesses 1. If the cloud server determines that the current number of accesses is equal to the preset number of accesses 1, the cloud server will clear the data sharing link.

Thereafter, when the second user or other users want to access through the data sharing link, they will receive the prompt information of the invalid address fed back by the cloud server.

The above application scenario is only for further explaining the content in the data sharing method embodiment, and cannot be used to limit the scope of application of the data sharing method.

In some embodiments, determining whether the second client user is an unfamiliar user according to the identity information of the second client, and when determining that the user is an unfamiliar user, sending a prompt message to the first client user to notify the first client user For strange users. If the first client user wants to continue to share with the second client user, the cloud server generates a data sharing link according to the identifier information sent by the first client, and sends the data sharing link to the second client, so that the second The client user can access the user data to be shared by the first client. In addition, in order to protect the security of the first client user data, the first client user sets a preset number of accesses, and when the number of accesses to access the shared user data through the data sharing link reaches a preset number of accesses, the data sharing is cleared. Links that make it impossible for others to gain unauthorized access through the data sharing link. In the data sharing method, the cloud server directly sends the data sharing link to the second client, and the data sharing can be completed without the first client user performing other operations, which simplifies the entire sharing process and saves the time of the first client user. . At the same time, by preset the number of accesses, it is possible to further avoid the occurrence of data leakage of the first client user and improve the security of data sharing.

In a second aspect, an embodiment of the present invention provides a data sharing apparatus, including:

a first obtaining unit, configured to acquire a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client;

a generating unit, configured to generate a data sharing link according to the identifier information, where the data sharing link is used to acquire the user data to be shared;

And a sending unit, configured to send the data sharing link to the second client according to the identity information.

In some embodiments, the data sharing apparatus further includes a second obtaining unit, configured to acquire user data of the first client, and acquire identification information corresponding to the user data.

In some embodiments, the data sharing apparatus further includes a determining unit, the determining unit further includes a first determining subunit, a prompting subunit, and an obtaining prompting subunit;

The first determining subunit is configured to determine, according to the identity information of the second client, whether the second client user is an unfamiliar user;

The prompting subunit is configured to send prompt information to the first client if it is determined that the second client user is an unfamiliar user;

The obtaining prompt subunit is configured to obtain operation information that is fed back by the first client according to the prompt information;

The generating unit is configured to generate a data sharing link according to the operation information and the identification information.

In some embodiments, the generating unit is configured to generate a data sharing link according to the identifier information and the identity information of the second client.

In some embodiments, the sharing request further includes a preset access number; the data sharing device further includes: an obtaining determining unit, where the obtaining determining unit includes an obtaining subunit, a second determining subunit, and a clearing subunit;

The obtaining subunit is configured to acquire the number of accesses to access the user data to be shared through the data sharing link;

The second determining subunit is configured to determine whether the number of accesses is equal to the preset number of accesses;

The clearing subunit is configured to clear the data sharing link if the number of accesses is equal to the preset number of accesses.

Please refer to FIG. 3. FIG. 3 is a schematic structural diagram of a data sharing apparatus according to an embodiment of the present invention. The data sharing device 300 is applied to the cloud server. Of course, in other embodiments, the data sharing device 300 can also be applied to other devices, and is not specifically limited herein.

In some embodiments, the data sharing device 300 includes a first obtaining unit 310, a generating unit 320, and a transmitting unit 330. The first obtaining unit 310 is configured to acquire the sharing request sent by the first client, where the sharing request includes the identifier information of the user data to be shared and the identity information of the second client. The generating unit 320 is configured to use the identifier information according to the identifier information. Generating a data sharing link, wherein the data sharing link is used to obtain the user data to be shared; and the sending unit 330 is configured to send the data sharing link to the second client according to the identity information.

The data sharing device 300 will be described in detail below with reference to FIG.

When the first client user wants to share the user data to the second client user, the first client user logs in to the client of the cloud server through the terminal, and enters the sharing interface through the sharing portal. After the first client user selects the user data to be shared and enters the identity information of the second client, the first client obtains the identifier information of the user data to be shared and the identity information of the second client, and according to the identifier of the user data to be shared. The information and the identity information of the second client generate a sharing request, and send the sharing request to the data sharing device 300 of the cloud server. The first obtaining unit 310 in the data sharing device 300 will acquire the sharing request.

It should be noted that the identity information includes the user name of the client user, the user's phone number, and/or the registered mailbox, and the specific content of the identity information is not limited herein. In addition, the identity information may include one type of information, and may also include a variety of information. For example, the identity information is the user's phone number of the client user. Of course, the identity information may also be composed of the registered email address and the user's telephone number of the client user, and no specific restrictions are imposed here.

In some embodiments, the identification information of the user data is a storage address of the user data within the cloud server. Of course, in other embodiments, the identification information of the user data may be other information used to identify the user data, as long as the cloud server can find the corresponding user data according to the identification information, and no specific limitation is imposed herein.

After receiving the sharing request sent by the first client, the first obtaining unit 310 obtains the identification information of the user data to be shared in the sharing request and the identity information of the second client by parsing, and identifies the information of the user data to be shared. The identity information of the second client and the second client are sent to the generating unit 320. The generating unit 320 generates a data sharing link according to the identification information, and the generating unit 320 sends the generated data sharing link and the identity information of the second client to the sending unit 330, wherein the data sharing link is used to acquire the user data to be shared. The sending unit 330 sends the data sharing link to the second client according to the identity information. After the second client user clicks the data sharing link, the cloud server can obtain the user data to be shared corresponding to the identifier information in the data sharing link, and present the data to be shared to the second client user. Second, the client user can browse or download the shared user data shared by the first client user. .

In some embodiments, in order to protect the security of the first client user data, avoiding the second client user inadvertently leaking the first client user data, etc., the generating unit 320 will identify the information according to the user data to be shared. A data sharing link is generated with the identity information of the second client. When other client users intercept the data sharing link or the second client user forwards the data sharing link to other client users, since the identity information of other client users is different from the identity information in the data sharing link, the other The client user cannot access the first client user data through the data sharing link. That is to say, only the second client has the right to access the user data to be shared through the data sharing link, and other client users have no right to access the user data to be shared, thereby ensuring the security of the first client user data.

In some embodiments, the data sharing device 300 acquires the sharing request sent by the first client by using the first obtaining unit 310, where the sharing request includes the identification information of the user data to be shared and the identity information of the second client; the generating unit 320 Generating a data sharing link according to the identification information; the sending unit 330 sends the data sharing link to the second client according to the identity information. The data sharing device 300 can directly send the data sharing link to the second client, and the data sharing can be completed without the first client user performing other operations, which simplifies the entire sharing process and saves the time of the first client user.

Please refer to FIG. 4. FIG. 4 is still another schematic structural diagram of a data sharing apparatus according to an embodiment of the present invention. The data sharing device 400 is applied to the cloud server. Of course, in other embodiments, the data sharing device 400 can also be applied to other devices, and is not specifically limited herein.

In some embodiments, the data sharing apparatus 400 includes a second obtaining unit 410, a first obtaining unit 420, a determining unit 430, a generating unit 440, a sending unit 450, and an obtaining determining unit 460, wherein the determining unit 430 includes a first determining unit. The unit 431, the prompting subunit 432, and the acquisition prompt subunit 433; the acquisition judging unit 460 includes an acquisition subunit 461, a second judging subunit 462, and a clearing subunit 463.

The above data sharing device 400 will be described in detail below with reference to FIG.

After the first client user logs in to the client of the cloud server, the user data in the terminal is uploaded to the data sharing device 400 of the cloud server through the upload button in the client. The second obtaining unit 410 in the data sharing device 400 will acquire the user data sent by the first client, and store the user data in a corresponding storage area of the cloud server. In the cloud server, each user data corresponds to a storage address. The second obtaining unit 410 will acquire the storage address, and use the storage address as the identification information of the user data, that is, obtain the identification information corresponding to the user data, and send the identification information to the first client.

Here, the identification information of the user data may be a storage address of the user data in the cloud server, and may of course be other information that plays a role of identification, as long as the cloud server can find the corresponding user data according to the identification information. No specific restrictions are made here.

When the first client user wants to share the user data to the second client user, the first client user logs in to the client of the cloud server through the terminal, and enters the sharing interface through the sharing portal. The first client user selects the user data to be shared, and inputs the identity information of the second client and the preset access times. After that, the first client obtains the identifier information of the user data to be shared and the identity information of the second client. And the preset access times, and generating a sharing request according to the identification information of the user data to be shared, the identity information of the second client, and the preset access times, and sending the sharing request to the data sharing device 400. The first obtaining unit 420 will acquire the sharing request.

It should be noted that the identity information includes the user name of the client user, the user's phone number, and/or the registered mailbox, and the specific content of the identity information is not limited herein. In addition, the identity information may include one type of information, and may also include a variety of information. For example, the identity information is the user's phone number of the client user. Of course, the identity information may also be composed of the registered email address and the user's telephone number of the client user, and no specific restrictions are imposed here.

The preset access times refer to the number of times the first client user wants to share user data to be accessed. For example, the first client user only wants the second client user to access the user data to be shared once. Setting the preset access times can prevent the second client user from sending the subsequently generated data sharing link to other clients and inadvertently causing the first client user data to leak.

After obtaining the sharing request sent by the first client, the first obtaining unit 420 obtains the identification information of the user data to be shared, the identity information of the second client, and the preset access times by parsing the sharing request, and the user data to be shared is to be shared. The identification information, the identity information of the second client, and the preset number of accesses are sent to the determining unit 430.

The first determining sub-unit 431 in the determining unit 430 determines whether the second client user is an unfamiliar user according to the identity information of the second client. Specifically, the first determining sub-unit 431 determines, according to the identity information of the second client, whether the second client user has a communication interaction with the first client user, where the communication interaction includes a phone, a short message, sharing data, and the like.

For example, when the first client user has never had a communication interaction with the second client user, the first determining sub-unit 431 will not obtain the communication interaction with the first client user according to the identity information of the second client. At this point, the cloud server will determine that the second client user is an unfamiliar user. If the first client user has shared its user data with the second client user, the first determining sub-unit 431 will obtain a history sharing record with the first client user according to the identity information of the second client user. And determining, according to the historical sharing record, that the second client user is not an unfamiliar user.

It is to be understood that, in other embodiments, the method for determining whether the second client user is an unfamiliar user is not limited to the foregoing, and may be determined by other methods, and is not specifically limited herein.

When the first determining sub-unit 431 determines that the second client user is not an unfamiliar user, the first determining sub-unit 431 sends the first signal, the identification information of the user data to be shared, and the identity of the second client to the generating unit 440. The information and the preset access times are such that the generating unit 440 generates a data sharing link according to the identification information after obtaining the first signal, and sends the generated data sharing link, the identity information of the second client, and the preset access times to the sending unit 450. , wherein the data sharing link is used to obtain user data to be shared. The sending unit 450 sends the data sharing link to the second client according to the identity information of the second client, and sends the preset access times to the acquisition determining unit 460. After the second client receives the data sharing link, after the second client user clicks the data sharing link, the cloud server may obtain the user data to be shared corresponding to the identifier information in the data sharing link, and the The shared user data is presented to the second client user, so that the second client user can browse or download the shared user data shared by the first client user.

After the client user completes the data to be shared by the data sharing link, the obtaining sub-unit 461 in the obtaining determining unit 460 acquires the number of accesses to access the user data to be shared through the data sharing link, and acquires the obtained data. The number of accesses is passed to the second judging subunit 462. The second determining sub-unit 462 will determine whether the current number of accesses is equal to the preset number of accesses.

If the second determining sub-unit 462 determines that the current number of accesses is not equal to the preset number of accesses, the current number of accesses is less than the preset number of accesses, and the second determining sub-unit 462 sends a second signal to the obtaining sub-unit 461. After the receiving the second signal, the obtaining sub-unit 461 re-acquires the number of accesses to access the user data to be shared through the data sharing link.

If the second determining sub-unit 462 determines that the current access times are equal to the preset access times, the second determining sub-unit 462 sends a third signal to the clearing sub-unit 463, so that the clearing sub-unit 463 clears the data sharing link according to the third signal. . Thereafter, the client user can no longer access the data to be shared through the data sharing link.

For example, when the first client user sets the preset access times to 2 times, if the second client user accesses the data to be shared through the data sharing link for the first time, the obtaining sub-unit 461 will obtain access to be shared through the data sharing link. The number of accesses of the user data is 1, and the second determining sub-unit 462 determines that the number of accesses 1 is not equal to the preset number of accesses 2, and the obtaining sub-unit 461 will wait for the next access. After the second client user accesses the data to be shared again through the data sharing link, the number of accesses acquired by the obtaining subunit 461 is 2, and the second determining subunit 462 determines that the number of accesses is equal to the preset number of accesses 2. At this point, the clear sub-unit 463 will clear the data sharing link, making the data sharing link invalid.

When the first determining sub-unit 431 determines that the second client user is an unfamiliar user, in order to further protect the security of the first client user data, the first determining sub-unit 431 will send a fourth signal to the prompting sub-unit 432. The prompting sub-unit 432 sends the prompt information to the first client according to the fourth signal. The prompt information is used to prompt the first client user whether to continue to share data with the unfamiliar user.

If the first client user chooses to continue sharing data with the unfamiliar user, the first client will obtain the operation information of the first client user, and send the operation information to the data sharing device 400. The obtaining prompt sub-unit 433 will obtain the operation information fed back by the first client according to the prompt information, and the operation information for continuing to share data with the unfamiliar user, the identification information of the user data to be shared, the identity information of the second client, and the preset. The number of accesses is sent to the generating unit 440. After the generating unit 440 obtains the operation information for continuing to share data with the unfamiliar user, the data sharing link is generated according to the identification information, and the data sharing link, the second client identity information, and the preset access are generated. The number of times is sent to the transmitting unit 450. The transmitting unit 450 and the acquisition judging unit 460 are caused to perform the aforementioned operational procedures.

If the first client user inadvertently enters the identity information of the second client user, the user will choose to cancel the sharing of data to the unfamiliar user, and then the first client will obtain the operation information for canceling the sharing of data to the unfamiliar user. The operation information for canceling the sharing of data to the unfamiliar user is sent to the acquisition prompt sub-unit 433, so that the acquisition prompt sub-unit 433 ends the sharing operation according to the operation information for canceling the sharing of data to the unfamiliar user. Therefore, the phenomenon that the user data is leaked due to the negligence of the first client user is effectively avoided.

In some embodiments, the data sharing device 400 determines, by the first determining sub-unit 431, whether the second client user is an unfamiliar user according to the identity information of the second client. When determining that the user is an unfamiliar user, the prompting sub-unit 432 is first. The client user sends a prompt message to inform the first client that the user is an unfamiliar user. If the first client user wants to continue to share with the second client, the generating unit 440 generates a data sharing link according to the identifier information sent by the first client, and the sending unit 450 sends the data sharing link to the second client. In this way, the second client user can access the user data to be shared of the first client. In addition, in order to protect the security of the first client user data, the first client user sets a preset access times, and when the number of accesses to access the shared user data through the data sharing link reaches a preset access times, the clearing sub-unit 463 Clear the data sharing link so that others can't access it illegally through the data sharing link. The data sharing device 400 can directly send the data sharing link to the second client, and the data sharing can be completed without the first client user performing other operations, which simplifies the entire sharing process and saves the time of the first client user. At the same time, by preset the number of accesses, it is possible to further avoid the occurrence of data leakage of the first client user and improve the security of data sharing.

The data sharing system provided by the embodiment of the present invention mainly includes a terminal and a cloud server, and the cloud server and the terminal can be connected through a wired or wireless network.

Please refer to FIG. 5. FIG. 5 is a schematic diagram of a scenario of a data sharing system provided by the present invention. The data sharing system includes a cloud server and a terminal, wherein the cloud server integrates the data sharing device provided by the present invention, and the cloud server stores a large number of user data and corresponding identification information. The first client and the second client in the present invention are installed in the terminal, where the terminal may be a server such as a mobile phone or a tablet computer.

When the first client user wants to share data with the second client user, the first client sends a sharing request to the cloud server. The cloud server obtains the sharing request sent by the first client, where the sharing request includes the identification information of the user data to be shared and the identity information of the second client; the cloud server obtains the identification information of the user data to be shared by parsing the sharing request and The identity information of the second client is generated, and the data sharing link is generated according to the identifier information, and the data sharing link is sent to the second client according to the identity information, where the data sharing link is used to obtain the user data to be shared. In this way, the second client user can browse or download the shared user data shared by the first client user by clicking the data sharing link.

The embodiment of the present invention further provides a server. Referring to FIG. 6, a schematic structural diagram of a server according to an embodiment of the present invention is shown. The server 500 includes a processor 501 and a memory 502, where:

In some embodiments, the processor 501 in the server 500 loads the executable file corresponding to the process of one or more applications into the memory 502 according to the following instructions, and is executed by the processor 501 to be stored in the memory. The instruction in 502 is used to perform the following steps:

Obtaining a sharing request sent by the first client, where the sharing request includes the identification information of the user data to be shared and the identity information of the second client, and generating a data sharing link of the user data to be shared according to the identification information, where The data sharing link is used to obtain the user data to be shared; and the data sharing link is sent to the second client according to the identity information.

The processor 501 also runs instructions stored in the memory 502 for performing the steps of: acquiring user data of the first client; and obtaining identification information corresponding to the user data.

The memory 502 stores user data of the first client acquired by the processor 501. After the memory 502 stores the user data of the first client, the processor 501 acquires the identification information corresponding to the user data from the memory 502.

After the processor 501 sends the message to the second client, the second client user can click, and the processor 501 reads the user data of the corresponding first client from the memory 502 and presents the data to the second client. The client user, so that the second client user can browse or download the user data to be shared that the first client user wants to share.

The processor 501 further executes the following steps before executing the data sharing link according to the identifier information, to perform the following steps: determining, according to the identity information of the second client, whether the second client user is an unfamiliar user; Sending the prompt information to the first client, and acquiring the operation information fed back by the first client according to the prompt information; and generating a data sharing link according to the identifier information Specifically, the method includes: generating a data sharing link according to the operation information and the identification information.

The processor 501 is further configured to: obtain, according to the identity information of the second client, a history sharing record corresponding to the first client user corresponding to the identity information; and determine, according to the history sharing record, Whether the second client user is an unfamiliar user.

The processor 501, when executing the data sharing link according to the identifier information, specifically executes the following instructions to perform the following steps: generating a data sharing link according to the identifier information and the identity information of the second client.

The processor 501 also runs instructions stored in the memory 502 to perform the steps of: the sharing request further includes a preset number of accesses; and transmitting the data sharing link to the second client according to the identity information After the method, the method further includes: obtaining a number of accesses to access the user data to be shared by using the data sharing link; determining whether the number of accesses is equal to the preset number of accesses; and if the number of accesses is equal to the preset number of accesses, Then clear the data sharing link.

The embodiment of the present invention further provides a server 500, wherein any of the data backup devices provided in the above embodiments may be integrated. Referring to FIG. 7, another structure diagram of the server 500 according to the embodiment of the present invention is shown. Specifically:

The server 500 can include one or more processors 501 of processing cores, a memory 502 of one or more computer readable storage media, a communication unit 503, a power source 504, an input unit 505, and a display unit 506.

It will be understood by those skilled in the art that the server structure illustrated in FIG. 6 does not constitute a limitation to the server, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements. among them:

Processor 501 is the control center of the server, connecting various portions of the server with various interfaces and lines, by running or executing software programs and/or modules stored in memory 502, and recalling data stored in memory 502, Execute the server's various functions and process data to monitor the server as a whole.

Optionally, the processor 501 may include one or more processing cores; the processor 501 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, etc., and a modulation solution The processor mainly handles wireless communication. It can be understood that the above modem processor may not be integrated into the processor 501.

The memory 502 can be used to store software programs and modules, and the processor 501 executes various functional applications and data processing by running software programs and modules stored in the memory 502.

The communication unit 503 can be used for receiving and transmitting signals during transceiving information. In particular, the communication unit 503 receives signals transmitted by the terminal and hands the signals to one or more processors 501 for processing. At the same time, the communication unit 503 transmits the feedback signal sent by the processor 501 to the terminal.

The server 500 also includes a power source 504 (such as a battery) that supplies power to various components. The power source can be logically coupled to the processor 501 through a power management system to manage functions such as charging, discharging, and power management through the power management system. The power supply 504 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.

The server 500 can also include an input unit 505 that can be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

The server 500 can also include a display unit 506 that can be used to display information entered by the user or information provided to the user and various graphical user interfaces of the server, which can be represented by graphics, text, icons, videos. And any combination of them to constitute. The display unit 508 can include a display panel, and optionally, a liquid crystal display can be used. (LCD, Liquid Crystal Display), Organic Light Emitting Diode (OLED, Organic Light-Emitting) Diode) and other forms to configure the display panel.

In the foregoing embodiments, the descriptions of the various embodiments are different, and the detailed descriptions of the data sharing methods are not described herein.

The data sharing device provided by the embodiment of the present invention is in the same concept as the data sharing method in the embodiment of the present invention, and any method provided in the data sharing method embodiment may be run on the data sharing device. For details of the implementation process, refer to the data sharing method embodiment, which is not described here.

It should be noted that, in the data sharing method of the present invention, a common tester in the art can understand all or part of the process of implementing the data sharing method in the embodiment of the present invention, which can be completed by controlling a related hardware through a computer program. The computer program may be stored in a computer readable storage medium, such as in a memory of the terminal, and executed by at least one processor in the terminal, and may include a method of data sharing as described in the execution process. The flow of an embodiment. Wherein, the storage medium may be a magnetic disk, an optical disk, a read only memory (ROM, Read) Only Memory), random access memory (RAM, Random Access Memory), etc.

For the data sharing device of the embodiment of the present invention, each functional module may be integrated into one processing chip, or each module may exist physically separately, or two or more modules may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated module, if implemented in the form of a software functional module and sold or used as a standalone product, may also be stored in a computer readable storage medium, such as a read only memory, a magnetic disk or an optical disk, etc. .

The data sharing method, device and system provided by the embodiments of the present invention are described in detail. The principles and implementation manners of the present invention are described in the specific examples. The description of the above embodiments is only used to help understanding. The method of the present invention and its core idea; at the same time, those skilled in the art, according to the idea of the present invention, there are some changes in the specific implementation manner and application scope. In summary, the content of the present specification should not be understood. To limit the invention.

In the above, the present invention has been disclosed in the above embodiments, but the above embodiments are not intended to limit the present invention, and those skilled in the art can make various changes without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the claims.

Claims (20)

A data sharing method, including: Obtaining a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client; Generating a data sharing link according to the identification information, where the data sharing link is used to acquire the user data to be shared; Sending the data sharing link to the second client according to the identity information. The data sharing method according to claim 1, wherein before the obtaining the sharing request sent by the first client, the method further comprises: Obtaining user data of the first client; Obtaining identification information corresponding to the user data. The data sharing method according to claim 1, wherein before the generating the data sharing link according to the identification information, the method further comprises: Determining, according to the identity information of the second client, whether the second client user is an unfamiliar user; If it is determined that the second client user is an unfamiliar user, sending a prompt message to the first client; Obtaining operation information that is fed back by the first client according to the prompt information; The generating the data sharing link according to the identifier information comprises: generating a data sharing link according to the operation information and the identifier information. The data sharing method according to claim 3, wherein the determining, according to the identity information of the second client, whether the second client user is an unfamiliar user comprises: Obtaining, according to the identity information of the second client, a history sharing record corresponding to the identity information and the first client user; Determining, according to the history sharing record, whether the second client user is an unfamiliar user. The data sharing method according to claim 1, wherein the generating the data sharing link according to the identification information comprises: generating a data sharing link according to the identification information and the identity information of the second client. The data sharing method according to claim 1, wherein the sharing request further comprises a preset number of accesses; After the sending the data sharing link to the second client according to the identity information, the method further includes: acquiring a number of accesses to access the user data to be shared by using the data sharing link; Determining whether the number of accesses is equal to the preset number of accesses; If the number of accesses is equal to the preset number of accesses, the data sharing link is cleared. The data sharing method according to any one of claims 1 to 6, wherein the identification information is a storage address of the user data in the cloud server. A data sharing device, comprising: a first obtaining unit, configured to acquire a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client; a generating unit, configured to generate a data sharing link according to the identifier information, where the data sharing link is used to acquire the user data to be shared; And a sending unit, configured to send the data sharing link to the second client according to the identity information. The data sharing device of claim 8, wherein the data sharing device further comprises a second obtaining unit, wherein the second obtaining unit is configured to acquire user data of the first client; and acquire corresponding to the user data Identification information. The data sharing device of claim 8, wherein the data sharing device further comprises a determining unit, the determining unit further comprising a first determining subunit, a prompting subunit, and an obtaining prompting subunit; The first determining subunit is configured to determine, according to the identity information of the second client, whether the second client user is an unfamiliar user; The prompting subunit is configured to send prompt information to the first client if it is determined that the second client user is an unfamiliar user; The obtaining prompt subunit is configured to obtain operation information that is fed back by the first client according to the prompt information; The generating unit is configured to generate a data sharing link according to the operation information and the identification information. The data sharing device according to claim 8, wherein the generating unit is configured to generate a data sharing link according to the identification information and the identity information of the second client. The data sharing device of claim 8, wherein the sharing request further comprises a preset number of accesses; the data sharing device further comprises: an acquisition determining unit, wherein the obtaining determining unit comprises an obtaining subunit and a second determining Unit and clear subunit; The obtaining subunit is configured to acquire the number of accesses to access the user data to be shared through the data sharing link; The second determining subunit is configured to determine whether the number of accesses is equal to the preset number of accesses; The clearing subunit is configured to clear the data sharing link if the number of accesses is equal to the preset number of accesses. A storage medium, wherein the storage medium stores a plurality of instructions, the plurality of instructions being adapted to cause the computer to perform the data sharing method of claims 1-7 when run on a computer. A server, comprising a processor and a memory, the memory storing a plurality of instructions, the processor loading the instructions in the memory for performing the following steps: Obtaining a sharing request sent by the first client, where the sharing request includes identifier information of the user data to be shared and identity information of the second client; Generating a data sharing link according to the identification information, where the data sharing link is used to acquire the user data to be shared; Sending the data sharing link to the second client according to the identity information. The server of claim 14, wherein the processor is further configured to perform the following steps: Obtaining user data of the first client; Obtaining identification information corresponding to the user data. The server of claim 14, wherein the processor is further configured to perform the following steps: Determining, according to the identity information of the second client, whether the second client user is an unfamiliar user; If it is determined that the second client user is an unfamiliar user, sending a prompt message to the first client; Obtaining operation information that is fed back by the first client according to the prompt information; The generating the data sharing link according to the identifier information comprises: generating a data sharing link according to the operation information and the identifier information. The server of claim 14, wherein the processor is further configured to perform the following steps: Obtaining, according to the identity information of the second client, a history sharing record corresponding to the identity information and the first client user; Determining, according to the history sharing record, whether the second client user is an unfamiliar user. The server of claim 14, wherein the processor is further configured to perform the following steps: Generating a data sharing link according to the identification information and the identity information of the second client. The server of claim 14, wherein the processor is further configured to perform the following steps: After the sending the data sharing link to the second client according to the identity information, the method further includes: acquiring a number of accesses to access the user data to be shared by using the data sharing link; Determining whether the number of accesses is equal to the preset number of accesses; If the number of accesses is equal to the preset number of accesses, the data sharing link is cleared. The server according to claim 14, wherein the identification information is a storage address of user data in the cloud server.