File Upload Method And System

• US 20150215400A1
• Filed: 04/10/2015
• Published: 07/30/2015
• Est. Priority Date: 10/12/2012
• Status: Active Grant

• Current Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Inventors: LIU, Gang
• Granted Patent: US 10,681,127 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A first client performs fragmentation on a to-be-uploaded file, to obtain multiple file fragments, and calculates check information of the file fragments. The first client uploads a file fragment to a second server according to an address of the second server obtained from a first server. When the first client uploads the file fragment, the first server sends a file identifier of the file to a third server; the third server determines, according to the file identifier of the file, a second client that saves at least one file fragment. According to file upload information separately sent by the third server to the first client and the second client, the first client and the second client separately upload a corresponding file fragment

Claims

1. A file upload method, comprising:

performing, by a first client, fragmentation on a to-be-uploaded file, to obtain multiple file fragments;

uploading, by the first client, at least one of the file fragments to a second server according to an address of the second server obtained from a first server;

sending, by the first server, a file identifier of the file to a third server when the first client uploads the at least one of the file fragments;

determining, by the third server according to the file identifier of the file, a second client that saves at least one of the file fragments;

uploading, by the first client when receiving first file upload information sent by the third server, to the second server a first file fragment corresponding to a file fragment identifier carried in the first file upload information; and

uploading, by the second client when receiving second file upload information sent by the third server, to the second server a second file fragment corresponding to a file fragment identifier carried in the second file upload information.

2. The method according to claim 1, further comprising:

sending, by the second client, query information to the third server; and

forwarding, by the third server, the query information to a fourth server, wherein the query information comprises the file identifier;

querying, by the fourth server according to the query information, for a node that completes download of the file or is downloading the file;

sending, by the fourth server when the node is found, information of the node to the second client by using the third server; and

downloading, by the second client, the file from the node.

3. The method according to claim 1, wherein the determining a second client that saves the at least one of the file fragments comprises:

receiving, by the third server, a file identifier being reported by means of heartbeat and being of a shareable file; and

determining, when the file identifier of the shareable file is the same as the file identifier of the file being uploaded, that a client that reports the file identifier of the shareable file is the second client;

or

determining, by the third server, when finding a client that completes download of the file or is downloading the file, that the found client is the second client.

4. The method according to claim 1, further comprising:

checking, by the second server, the first file fragment when the first file fragment is uploaded;

writing the first file fragment into a fifth server when the check for the first file fragment is successful;

sending, by the second server to the first client and the second client, a message indicating that the first file fragment is uploaded; and

writing the file identifier of the file, a size of the file, and a name of the file into a sixth server;

checking, by the second server, the second file fragment when the second file fragment is uploaded;

writing the second file fragment into the fifth server when the check for the second file fragment is successful;

sending, by the second server to the first client and the second client, a message indicating that the second file fragment is uploaded; and

writing the file identifier of the file, the size of the file, and the name of the file into the sixth server.

5. The method according to claim 4, further comprising:

sending, by the third server to the first client when the check for the first file fragment or the check for the second fragment is unsuccessful, the first file upload information that carries the file fragment identifier of the first file fragment when the check for the first file fragment is unsuccessful or carries the file fragment identifier of the second file fragment when the check for the second fragment is unsuccessful;

or

sending, by the third server to the second client when the check for the first file fragment or the check for the second fragment is unsuccessful, the second file upload information that carries the file fragment identifier of the first file fragment when the check for the first file fragment is unsuccessful or carries the file fragment identifier of the second file fragment when the check for the second fragment is unsuccessful.

6. A file upload method, comprising:

performing, by a first client, fragmentation on a to-be-uploaded file, to obtain multiple file fragments, and calculating check information of the file fragments;

uploading, by the first client, at least one file fragment in the multiple file fragments to a second server according to an address of the second server found from a first server;

sending, by the first server, a file identifier of the file to a third server when the first client uploads the at least one file fragment; and

uploading, by the second client when receiving file upload information sent by the third server, to the second server a file fragment corresponding to a file fragment identifier carried in the file upload information.

7. The method according to claim 6, further comprising:

reporting, by the second client to the third server by means of heartbeat, a file identifier of a shareable file.

8. The method according to claim 6, further comprising:

checking, by the second server, when a file fragment in the at least one file fragment is uploaded, the uploaded file fragment;

writing the uploaded file fragment into a fifth server when the check is successful;

sending, to the first client and the second client, a message indicating that the file fragment is uploaded; and

writing the file identifier of the file, a size of the file, and a name of the file into a sixth server.

9. The method according to claim 8, further comprising:

sending, by the third server, the file upload information to the first client or the second client when the check is unsuccessful, so that the first client or the second client uploads the file fragment according to the file upload information.

10. The method according to claim 6, wherein the file upload information comprises a file fragment identifier of at least one file fragment that is in the multiple file fragments and needs to be uploaded by the first client or the second client.

11. A file upload system, comprising:

a first client, configured to perform fragmentation on a to-be-uploaded file, to obtain multiple file fragments, and calculate check information of the file fragments; and

upload at least one file fragment in the multiple file fragments to a second server according to an address of the second server found from a first server;

the first server, configured to send a file identifier of the file to a third server when the first client uploads the at least one file fragment;

the third server, configured to receive the file identifier of the file sent by the first server, and send, to a second client, file upload information for uploading the file;

the second client, configured to upload, to the second server according to the file upload information when receiving the file upload information sent by the third server, at least one file fragment that is in the multiple file fragments of the file and needs to be uploaded by the second client; and

the second server, configured to receive at least one file fragment that is in the multiple file fragments and sent by the first client and/or the second client.

12. The system according to claim 11, wherein

the third server is further configured to receive a file identifier of a shareable file, wherein the file identifier is reported by the second client by means of heartbeat.

13. The system according to claim 11, wherein the second server is further configured to:

check, when a file fragment in the at least one file fragment is uploaded, the uploaded file fragment;

write the uploaded file fragment into a fifth server when the check is successful;

send, to the first client and the second client, a message indicating that the file fragment is uploaded; and

write the file identifier of the file, a size of the file, and a name of the file into a sixth server.

14. The system according to claim 13, wherein

the third server is further configured to send the file upload information to the first client or the second client when the check is unsuccessful, so that the first client or the second client re-uploads the file fragment according to the file upload information.

15. The system according to claim 11, wherein the file upload information comprises a file fragment identifier of at least one file fragment that is in the multiple file fragments and needs to be uploaded by the first client or the second client.