Learned upload time estimate module

• US 7,840,646 B2
• Filed: 10/08/2003
• Issued: 11/23/2010
• Est. Priority Date: 10/08/2003
• Status: Expired due to Fees

• Current Assignee: R2 Solutions LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Davis, Brockton S., Seitz, Edward F.
• Primary Examiner(s): Flynn; Nathan
• Assistant Examiner(s): Park; Jeong S
• Application Number:
  US10/682,636
• Publication Number:
  US 20050080872A1
• Time in Patent Office: 2,603 Days
• Field of Search: 709/217, 709/224
• US Class Current: 709/217
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 2201/835 Timestamp
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A learned upload time estimate is derived from historical uploading information. This involves reviewing historical uploading information for previous uploads. To determine if there is a match or likeness between information of files presently selected for uploading and the historical uploading information for any of the previous uploads, the size of these files is combined to produce an upload size. The size and timestamp of the current upload is compared against the size and timestamp of each of the previous uploads. If a match with a previous upload is found its actual time is used as the learned estimate upload time. If a match or likeness is not found, an average transfer rate is computed from the historical uploading information for the previous uploads. From the average transfer rate and upload size a learned upload time estimate is derived and provided to a client for display to a user.

Claims

1. A method for providing a learned upload time estimate, comprising:

reviewing, via a computing device, historical uploading information for more than one previous uploads, wherein for each previous upload the historical uploading information comprises a previous upload size and an upload start marker, and a number of files uploaded and a total time the previous upload actually took to complete, wherein the upload start marker is a timestamp;

determining, via the computing device, if there is a match or likeness between uploading information, including a new upload start marker, which is a new timestamp, and an upload size, in total, of one or more files presently selected for uploading, and the historical uploading information for any of the previous uploads, wherein the one or more files presently selected for uploading have an average file size, the average file size being a ratio between the upload size and number of files presently selected for upload;

if a match or likeness is found with a particular previous upload, obtaining the total time of the particular previous upload, using its historical uploading information, and using the total time as the upload time estimate for the files presently selected for uploading; and

if a match or likeness is not found, computing an average transfer rate from the historical uploading information for the one or more previous uploads, and deriving from the average transfer rate and upload size an upload time estimate for the files presently selected for uploading and providing the upload time estimate to a user, wherein computing the average transfer rate includes computing a ratio between an aggregate of the previous upload sizes and an aggregate of the total times of the previous uploads, and setting a transfer rate equal to the average transfer rate unless the average file size is smaller than the average transfer rate multiplied by one second, in which case the average transfer rate equals the average file size per second.

2. The method as in claim 1, wherein, if a match or likeness is not found, the upload time estimate is derived by computing a ratio between the upload size and the average transfer rate.

3. The method as in claim 1, wherein for each previous upload determining if there is a match or likeness includes:

determining an upload size difference between the previous upload size and the upload size, and

determining a difference between the upload start marker and the new upload start marker, the difference being a time difference between the timestamp and the new timestamp if the upload start marker and new upload start marker are the timestamp and new timestamp, respectively, new timestamps, wherein a match or likeness is found if the difference fits a predetermined event criteria and the upload size difference is within a predetermined range.

4. The method as in claim 3, wherein the predetermined event criteria is characterized by the timestamp and new timestamp being of the same-day and same-time or of the same-day but times differing by a predetermined period within which traffic load conditions are similar.

5. The method as in claim 3, wherein the predetermined event criteria is characterized by the timestamp and new timestamp being a weekend and weekday, respectively, or vise-versa, and times differing by a predetermined period within which traffic load conditions are similar.

6. The method as in claim 3, wherein the predetermined range is a percentage of the upload size.

7. The method as in claim 1, further comprising:

determining whether any previous uploads have been tracked; and

based on existence or nonexistence of historical uploading information for any previous uploads determining whether or not to provide the upload time estimate.

8. The method as in claim 1, further comprising:

determining whether historical upload information for the one of more previous uploads has been retrieved from a data structure; and

if not, retrieve the historical upload information for the one of more previous uploads.

9. The method as in claim 8, wherein the data structure is registry settings.

10. The method as in claim 1, wherein the historical uploading information is saved for up to a predetermined number of previous uploads.

11. The method as in claim 10, wherein the predetermined number of previous uploads is a parameter supplied by a server.

12. A method for tracking historical uploading information in order to provide a learned upload time estimate, comprising:

initiate uploading, via a computing device, of one or more files selected for uploading and having, in total, an upload size;

saving, via the computing device, a timestamp representing a start time of the initiated uploading;

tracking, via the computing device, the upload of the selected files and upon completion of the upload determining the stop time and the total time the upload took,

wherein the total time, timestamp, and upload size become part of historical uploading information that is used in a subsequent upload of one or more newly selected files having, in total, a new upload size an average file size, the average file size being a ratio between the upload size and number of files presently selected for upload, the subsequent upload having a new timestamp, the historical upload information of more than one previous uploads, including the just completed upload and the number of files uploaded, being used in the subsequent upload to determine if information, including the upload size and new timestamp, of the newly selected one or more files matches or nearly matches the historical uploading information such that;

upon finding a match or near match with the historical uploading information for any previous upload, the upload estimate is set to the total time of the previous upload as to which the match or near match has been found; and

upon a failure to find a match or near match with the historical uploading information for any previous upload, an average transfer rate is computed from the historical uploading information of the previous uploads, the average transfer rate and the upload size being used in providing an upload time estimate for the one or more newly selected files, wherein computing the average transfer rate includes computing a ratio between an aggregate of the previous upload sizes and an aggregate of the total times of the previous uploads, and setting a transfer rate equal to the average transfer rate unless the average file size is smaller than the average transfer rate multiplied by one second and the number of files is greater than a predetermined number, in which case the transfer rate equals the average file size per second.

13. The method as in claim 12, wherein, if a match or near match is not found, the upload time estimate is derived by computing a ratio between the upload size and the average transfer rate.

14. The method as in claim 12, wherein for each previous upload determining if there is a match or near match includes:

determining an upload size difference between the upload size of that previous upload and the new upload size, and

determining a time difference between the timestamp of that previous upload and the new timestamp, wherein a match or near match is found if the time difference fits a predetermined time criteria and the upload size difference is within a predetermined range.

15. The method as in claim 14, wherein the predetermined time criteria is characterized by the timestamp of a previous upload and the new timestamp being of the same-day and same-time or of the same-day but times differing by a predetermined period within which traffic load conditions are similar.

16. The method as in claim 14, wherein the predetermined time criteria is characterized by the timestamp of a previous upload and the new timestamp being a weekend and weekday, respectively, or vise-versa, and times differing by a predetermined period within which traffic load conditions are similar.

17. The method as in claim 14, wherein the predetermined range is a percentage of the upload size.

18. The method as in claim 12, further comprising storing the historical uploading information in a data structure.

19. The method as in claim 18, wherein the data structure is registry settings.

20. The method as in claim 12, wherein the historical uploading information is saved for up to a predetermined number of previous uploads.

21. The method as in claim 20, wherein the predetermined number of previous uploads is a parameter supplied by a server.

22. The method as in claim 12, wherein the upload time estimate is provided to a user for display.

23. A computer system for providing learned upload time estimates, comprising:

a processor; and

a memory with program code for causing the processor to perform the steps of;

reviewing, via a computing device, historical uploading information for more than one previous uploads, wherein for each previous upload the historical uploading information comprises a previous upload size and an upload start marker, and a number of files uploaded and a total time the previous upload actually took to complete, wherein the upload start marker is a timestamp;

determining, via the computing device, if there is a match or likeness between uploading information, including a new upload start marker, which is a new timestamp, and an upload size, in total, of one or more files presently selected for uploading, and the historical uploading information for any of the previous uploads, wherein the one or more files presently selected for uploading have an average file size, the average file size being a ratio between the upload size and number of files presently selected for upload;

if a match or likeness is found with a particular previous upload, obtaining the total time of the particular previous upload, using its historical uploading information, and using the total time as the upload time estimate for the files presently selected for uploading; and

if a match or likeness is not found, computing an average transfer rate from the historical uploading information for the one or more previous uploads, and deriving from the average transfer rate and upload size an upload time estimate for the files presently selected for uploading and providing the upload time estimate to a user, wherein computing the average transfer rate includes computing a ratio between an aggregate of the previous upload sizes and an aggregate of the total times of the previous uploads, and setting a transfer rate equal to the average transfer rate unless the average file size is smaller than the average transfer rate multiplied by one second, in which case the average transfer rate equals the average file size per second.

24. The computer system as in claim 23, wherein the computer system is operative to establish communications with the client via the Internet.

25. The computer system as in claim 24, wherein the program code for causing the processor to determine if there is a match or likeness includes further program code for causing the processor to perform, for each previous upload, the steps of:

determining an upload size difference between the previous upload size and the upload size, and

determining a difference between the upload start marker and new upload start marker, the difference being a time difference between the timestamp and the new timestamp if the upload start and new upload start markers are the timestamp and new timestamp, respectively, wherein a match or likeness is found if the time difference fits a predetermined event criteria and the upload size difference is within a predetermined range.

26. The computer system as in claim 25, wherein the predetermined event criteria is characterized by the timestamp and new timestamp being of the same-day and same-time or of the same-day but times differing by a predetermined period within which traffic load conditions are similar.

27. The computer system as in claim 25, wherein the predetermined event criteria is characterized by the timestamp and new timestamp being a weekend and weekday, respectively, or vise-versa, and times differing by a predetermined period within which traffic load conditions are similar.

28. The computer system as in claim 25, wherein the predetermined range is a percentage of the upload size.

29. The computer system as in claim 23, operative to provide the upload time estimate to the client for display to an end user.

30. The computer system as in claim 23, wherein, if a match or likeness is not found, the program code causes the processor to derive the upload time estimate by computing a ratio between the upload size and the average transfer rate.

31. The computer system as in claim 23, wherein the program code causes the processor to perform the further steps of:

determining whether any previous uploads have been tracked; and

based on existence or nonexistence of historical uploading information for any previous uploads determining whether or not to provide the upload time estimate.

32. The computer system as in claim 23, wherein the memory contains a data structure, and wherein the program code causes the processor to perform the further steps of:

determining whether historical upload information for the one of more previous uploads has been retrieved from the data structure; and

if not, retrieve the historical upload information for the one of more previous uploads.

33. The computer system as in claim 32, wherein the data structure is registry settings.

34. The computer system as in claim 23, operative to save the historical uploading information for up to a predetermined number of previous uploads.

35. The computer system as in claim 34, wherein the system includes a server operative to supply a parameter specifying the predetermined number of previous uploads.

36. The computer system as in claim 23, in which the one or more files are self-extracting executable (.exe) files or files including JPEG (Joint Photographic Experts Group) JPEG (Joint Photographic Experts Group), GIF (Graphic Interchange Format), PNG (Portable Network Graphics) or BMP (bit mapped) formatted files.

37. The computer system as in claim 23, further comprising:

a host server; and

an upload server, both the host and upload servers in communications with the client via a network.

38. The computer system as in claim 37, wherein the host server is operative to send html (hypertext markup language) pages to the client, wherein the client is operative to upload the one or more files to the upload server, and wherein the upload server is operative to indicate failure or success of file uploads.

39. The computer system as in claim 37, wherein the html pages contain features of a file uploader tool, including file selection, via browsing and drag-drop operations, and wherein the upload time estimate changes along with additional selections of files before they are uploaded to the upload server.

40. The compute system as in claim 39, wherein the files contain image data of photos and wherein further features of the uploader tool include photo preview.