System and method for bulk transfer of digital goods

• US 7,958,163 B2
• Filed: 04/29/2004
• Issued: 06/07/2011
• 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
• Primary Examiner(s): Jalil; Neveen Abel
• Assistant Examiner(s): Syed; Farhan M
• Application Number:
  US10/835,688
• Publication Number:
  US 20050033774A1
• Time in Patent Office: 2,595 Days
• Field of Search: 707/9, 707/10, 705/26
• US Class Current: 707/805
• 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 from a vendor to a central repository, comprising steps of:

loading at least one file image from a source location by a vendor, wherein said source location comprises an FTP server;

obtaining at least one File ID parameter for said at least one file image and a source file path to said at least one file image at a computer operated by a vendor from a list of input parameters, wherein said at least one File ID parameter comprises an XML (eXtensible Markup Language) file, wherein said XML file contains an element corresponding to said at least one file image, and wherein said element contains said at least one File ID parameter;

obtaining a vendor identifier and a checksum for verifying the integrity of said file image via one or more application-specific forms available to a user through one or more web service;

linking said at least one file image with a corresponding metadata object within a product description, wherein said at least one metadata object comprises an entitlement attribute specifying at least one customer, from among a plurality of customers, entitled to download said file;

creating said at least one corresponding metadata object by the vendor of the of said at least one file image;

uploading said at least one file image from said source location to a database at said central repository, wherein said uploading 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;

generating at least one email message to notify at least one customer from a plurality of customers that said at least one file image is ready to be downloaded, wherein the step of generating said at least one email comprises generating at least one executable hyperlink that, when executed, provides said at least one customer with access to a dynamically-generated, password- protected, personalized web space configured for downloading said at least one file subject to said entitlement attribute; and

interpreting the at least one File ID parameter and the at least one additional parameter according to predefined rules for the display of the at least one file image on standardized browsers using a user-defined template.

2. The method of claim 1, wherein said element comprises a ‘

load file image’

transaction.

3. The method of claim 2, further comprising a step of:

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

load file image’

transaction.

4. The method of claim 1, 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.

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

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

7. The method of claim 4, wherein said file image attributes include any of:

file name;

file size;

optionally, contents; and

whether or not said file image has been uploaded.

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

9. The method of claim 8, 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.

10. The method of claim 9, wherein said primary object types include:

‘

entitlements;

’

‘

catalog items;

’

‘

products;

’ and

‘

file.’

11. The method of claim 8, wherein said digital goods include any of:

e-books;

digitized images;

digitized sound files; and

software products.

12. A computer-readable storage medium encoded with a computer program for transferring digital goods from a vendor to a central repository, 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:

loading at least one file image from a source location by a vendor, wherein said source location comprises an FTP server;

obtaining at least one File ID parameter for said at least one file image and a source file path to said at least one file image at a computer operated by a vendor from a list of input parameters, wherein said at least one File ID parameter comprises an XML (eXtensible Markup Language) file, wherein said XML file contains an element corresponding to said at least one file image, and wherein said element contains said at least one File ID parameter;

obtaining a vendor identifier and a checksum for verifying the integrity of said file image via one or more application-specific forms available to a user through one or more web service;

linking said at least one file image with a corresponding metadata object within a product description, wherein said at least one metadata object comprises an entitlement attribute specifying at least one customer, from among a plurality of customers, entitled to download said file;

creating said at least one corresponding metadata object by the vendor of the of said at least one file image;

uploading said at least one file image from said source location to a database at said central repository, wherein said uploading 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;

generating at least one email message to notify at least one customer from a plurality of customers that said at least one file image is ready to be downloaded, wherein the step of generating said at least one email comprises generating at least one executable hyperlink that, when executed, provides said at least one customer with access to a dynamically-generated, password-protected, personalized web space configured for downloading said at least one file subject to said entitlement attribute; and

interpreting the at least one File ID parameter and the at least one additional parameter according to predefined rules for the display of the at least one file image on standardized browsers using a user-defined template.

13. The method of claim 12, wherein said element comprises a ‘

load file image’

transaction.

14. The method of claim 13, further comprising a step of:

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

load file image’

transaction.

15. 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.

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

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

18. The method of claim 15, wherein said file image attributes include any of:

file name;

file size;

optionally, contents; and

whether or not said file image has been uploaded.

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

20. The method of claim 19, 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.

21. The method of claim 20, wherein said primary object types include:

‘

entitlements;

’

‘

catalog items;

’

‘

products;

’ and

‘

files.’

22. The method of claim 19, wherein said digital goods include any of:

e-books;

digitized images;

digitized sound files; and

software products.

23. The method of claim 12, wherein said source location comprises a computer operated by a vendor.

24. A system for transferring digital goods from a vendor to a central repository, comprising:

a source location comprising an FTP server, wherein at least one file image is stored at said source location;

processor means executing instructions, said instructions including instructions for;

loading at least one file image from a source location by a vendor;

obtaining at least one File ID parameter for said at least one file image and a source file path to said at least one file image at computer operated by a vendor from a list of input parameters, wherein said at least one File ID parameter comprises an XML (eXtensible Markup Language) file, wherein said XML file contains an element corresponding to said at least one file image, and wherein said element contains said at least one File ID parameter;

obtaining a vendor identifier and a checksum for verifying the integrity of said file image via one or more application-specific forms available to a user through one or more web service;

linking said at least one file image with a corresponding metadata object within a product description, wherein said at least one metadata object comprises an entitlement attribute specifying at least one customer, from among a plurality of customers, entitled to download said file;

creating said at least one corresponding metadata object by the vendor of the of said at least one file image;

uploading said at least one file image from said computer operated by a vendor to a database at said central repository, wherein said uploading 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;

generating at least one email message to notify at least one customer from a plurality of customers that said at least one file image is ready to be downloaded, wherein the step of generating said at least one email comprises generating at least one executable hyperlink that, when executed, provides said at least one customer with access to a dynamically-generated, password -protected, personalized web space configured for downloading said at least one file subject to said entitlement attribute; and

interpreting the at least one File ID parameter and the at least one additional parameter according to predefined rules for display of the at least one file image on standardized browsers using a user-defined template.

25. The system of claim 24, wherein said least one file image is loaded from said source computer by a vendor.

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

27. The system of claim 24, wherein said element comprises a ‘

load file image’

transaction.

28. The system of claim 27, wherein said ‘

load file image’

transaction is declared in an XML Schema.

29. The system of claim 24, 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.

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

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

32. The system of claim 29, wherein said file image attributes include any of:

file name;

file size;

contents; and

whether or not said file image has been uploaded.

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

34. The system of claim 33, 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.

35. The system of claim 34, wherein said primary object types include:

‘

entitlements;

’

‘

catalog items;

’

‘

products;

’ and

‘

files.’

36. The system of claim 33, wherein said digital goods include any of:

e-books;

digitized images;

digitized sound files; and

software products.