System and method for bulk transfer of digital goods

• US 20050033774A1
• Filed: 04/29/2004
• Published: 02/10/2005
• Est. Priority Date: 08/05/2003
• Status: Active Grant

• Current Assignee: Flexera Software LLC
• Original Assignee: Intraware Inc. (Flexera Software LLC)
• Inventors: Brentano, James, Pieper, Tobid, Habets, Ariane
• Granted Patent: US 7,958,163 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A system and method for transferring digital goods facilitates bulk upload of file images to a central repository. The software gets a File ID and a path to each file image to be uploaded from a list, typically an XML file, of input attributes. After successful verification, the file image is uploaded to the central repository and linked with a corresponding metadata object. Each metadata object contains attributes that describe the corresponding file image. Although file attributes may be defined when the metadata object is created, the software determines file image attributes as the file image is being uploaded and records them in the metadata object. File images are either uploaded from a server, typically an FTP server, having been placed there by the goods vendor; or the file images can be uploaded directly from a computer operated by the vendor.

Claims

1. A method of transferring digital goods, comprising steps of:

getting from a list of input parameters a File ID for at least one file image and a path to said at least one file image at a first location;

linking said at least one file image with a corresponding metadata object within a product description; and

uploading said at least one file image from said first location to a database.

2. The method of claim 1, further comprising a step of loading said at least one file image to said first location by a vendor.

3. The method of claim 2, wherein said first location comprises an FTP (file transfer protocol) server.

4. The method of claim 1, wherein said input parameters further include any of:

a vendor identifier;

a path to a vendor directory at said first location; and

means for verifying integrity of said file image.

5. The method of claim 4, wherein said means for verifying file image integrity comprises either of:

a message digest; and

a checksum.

6. The method of claim 5, wherein said message digest comprises a MD5 checksum.

7. The method of claim 1, wherein said list of input parameters comprises an XML (extensible Markup Language) file.

8. The method of claim 7, wherein said XML file contains an element corresponding to said at least one file image, and wherein said element contains said input parameters.

9. The method of claim 8, wherein said element comprises a ‘

load file image’

transaction.

10. The method of claim 9, further comprising a step of:

providing an XML Schema, wherein said Schema contains a declaration of said ‘

load file image’

transaction.

11. The method of claim 1, further comprising a step of creating said at least one corresponding metadata object.

12. The method of claim 11, wherein a vendor of said at least one file image creates said at least one metadata object.

13. The method of claim 12, wherein said at least one metadata object comprises a ‘

file’

object, wherein a ‘

file’

object includes a plurality of attributes that describe a corresponding file image.

14. The method of claim 13, further comprising a step of providing values for at least some of said attributes by said vendor.

15. The method of claim 13, further comprising a step of determining values for at least some of said attributes during uploading.

16. The method of claim 13, wherein said file image attributes include any of:

file name;

file size;

optionally, contents; and

whether or not said file image has been uploaded.

17. The method of claim 13, wherein said product description comprises a product hierarchy from a system for managing digital goods.

18. The method of claim 17, wherein said product hierarchy includes a plurality of primary objects, wherein said product hierarchy models complex product relationships involved in electronic distribution of digital goods;

and wherein said product hierarchy is based on associations among a plurality of primary objects.

19. The method of claim 18, wherein said primary object types include:

‘

entitlements;

’

‘

catalog items;

’

‘

products;

’ and

‘

files.’

20. The method of claim 17, wherein said digital goods include any of:

e-books;

digitized images;

digitized sound files; and

software products.

21. The method of claim 17, wherein said database comprises a central repository in said system for managing digital goods.

22. The method of claim 1, wherein said first location comprises a computer operated by a vendor.

23. The method of claim 1, wherein said uploading step fails if:

said at least one file image is not found;

said metadata object is not found;

or

said at least one file image fails an integrity check.

24. A computer program for transferring digital goods comprising computer-readable code means, said computer-readable code means comprising program code for executing a method for transferring digital goods, said method comprising steps of:

getting from a list of input parameters a File ID for at least one file image and a path to said at least one file image at a first location;

linking said at least one file image with a corresponding metadata object within a product description; and

uploading said at least one file image from said first location to a database.

25. The method of claim 24, further comprising a step of loading said at least one file image to said first location by a vendor.

26. The method of claim 25, wherein said first location comprises an FTP (file transfer protocol) server.

27. The method of claim 24, wherein said input parameters further include any of:

a vendor identifier;

a path to a vendor directory at said first location; and

means for verifying integrity of said file image.

28. The method of claim 27, wherein said means for verifying file image integrity comprises either of:

a message digest; and

a checksum.

29. The method of claim 28, wherein said message digest comprises a MD5 checksum.

30. The method of claim 24, wherein said list of input parameters comprises an XML (extensible Markup Language) file.

31. The method of claim 30, wherein said XML file contains an element corresponding to said at least one file image, and wherein said element contains said input parameters.

32. The method of claim 31, wherein said element comprises a ‘

load file image’

transaction.

33. The method of claim 32, further comprising a step of:

providing an XML Schema, wherein said Schema contains a declaration of said ‘

load file image’

transaction.

34. The method of claim 24, further comprising a step of creating said at least one corresponding metadata object.

35. The method of claim 34, wherein a vendor of said at least one file image creates said at least one metadata object.

36. The method of claim 35, wherein said at least one metadata object comprises a ‘

file’

object, wherein a ‘

file’

object includes a plurality of attributes that describe a corresponding file image.

37. The method of claim 36, further comprising a step of providing values for at least some of said attributes by said vendor.

38. The method of claim 36, further comprising a step of determining values for at least some of said attributes during uploading.

39. The method of claim 36, wherein said file image attributes include any of:

file name;

file size;

optionally, contents; and

whether or not said file image has been uploaded.

40. The method of claim 36, wherein said product description comprises a product hierarchy from a system for managing digital goods.

41. The method of claim 40, wherein said product hierarchy includes a plurality of primary objects, wherein said product hierarchy models complex product relationships involved in electronic distribution of digital goods;

and wherein said product hierarchy is based on associations among a plurality of primary objects.

42. The method of claim 41, wherein said primary object types include:

‘

entitlements;

’

‘

catalog items;

’

‘

products;

’ and

‘

files.’

43. The method of claim 40, wherein said digital goods include any of:

e-books;

digitized images;

digitized sound files; and

software products.

44. The method of claim 40, wherein said database comprises a central repository in said system for managing digital goods.

45. The method of claim 24, wherein said first location comprises a computer operated by a vendor.

46. The method of claim 24, wherein said uploading step fails if:

said at least one file image is not found;

said metadata object is not found;

or

said at least one file image fails an integrity check.

47. A system for transferring digital goods comprising:

a first computer, wherein at least one file image is stored at said first computer;

processor means executing instructions, said instructions including instructions for;

getting from a list of input parameters a File ID for said at least one file image and a path to said at least one file image at said first computer;

linking said at least one file image with a corresponding metadata object within a product description; and

uploading said at least one file image from said first computer to a database.

48. The system of claim 47, wherein said least one file image is loaded to said first computer by a vendor.

49. The system of claim 48, wherein said first location comprises an FTP (file transfer protocol) server.

50. The system of claim 47, wherein said input parameters further include any of:

a vendor identifier;

a path to a vendor directory at said first location; and

means for verifying integrity of said file image.

51. The system of claim 50, wherein said means for verifying file image integrity comprises either of:

a message digest; and

a checksum.

52. The system of claim 51, wherein said message digest comprises a MD5 checksum.

53. The system of claim 47, wherein said list of input parameters comprises an XML (extensible Markup Language) file.

54. The system of claim 53, wherein said XML file contains an element corresponding to said at least one file image, and wherein said element contains said input parameters.

55. The system of claim 54, wherein said element comprises a ‘

load file image’

transaction.

56. The system of claim 55, wherein said ‘

load file image’

transaction is declared in an XML Schema.

57. The system of claim 47, wherein a vendor of said at least one file image creates said at least one metadata object.

58. The system of claim 57, wherein said at least one metadata object comprises a ‘

file’

object, wherein a ‘

file’

object includes a plurality of attributes that describe a corresponding file image.

59. The system of claim 58, wherein values for at least some of said attributes are specified by said vendor.

60. The system of claim 58, said instructions further comprising instructions for determining values for at least some of said attributes during uploading.

61. The system of claim 58, wherein said file image attributes include any of:

file name;

file size;

contents; and

whether or not said file image has been uploaded.

62. The system of claim 58, wherein said product description comprises a product hierarchy from a system for managing digital goods.

63. The system of claim 62, wherein said product hierarchy includes a plurality of primary objects, wherein said product hierarchy models complex product relationships involved in electronic distribution of digital goods;

and wherein said product hierarchy is based on associations among a plurality of primary objects.

64. The system of claim 63, wherein said primary object types include:

‘

entitlements;

’

‘

catalog items;

’

‘

products;

’ and

‘

files.’

65. The system of claim 62, wherein said digital goods include any of:

e-books;

digitized images;

digitized sound files; and

software products.

66. The system of claim 62, wherein said database comprises a central repository in said system for managing digital goods.

67. The system of claim 63, wherein said first location comprises a computer operated by a vendor.

68. The system of claim 47, wherein said uploading step fails if:

said at least one file image is not found;

said metadata object is not found;

or

said at least one file image fails an integrity check.