IP Library Granted Patent US 7,958,163
Granted Patent B2
US 7,958,163 · App. 10/835,688 · Granted Jun 7, 2011

System and method for bulk transfer of digital goods

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,958,163
App. No.
10/835,688
Granted
Jun 7, 2011
Kind
B2
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 (112)

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.

Assignments (22)
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENTS - REEL/FRAME 045441/ 0499 Recorded Aug 25, 2025
From: JEFFERIES FINANCE LLC
To: FLEXERA SOFTWARE LLC; PALAMIDA, INC.; BDNA CORPORATION
Reel/Frame 072552/0558 →
SECURITY INTEREST Recorded Aug 15, 2025
From: FLEXERA SOFTWARE LLC
To: KKR LOAN ADMINISTRATION SERVICES LLC, AS COLLATERAL GENT
Reel/Frame 072460/0828 →
RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS Recorded Apr 18, 2024
From: JEFFERIES FINANCE LLC
To: BDNA CORPORATION; FLEXERA SOFTWARE LLC; PALAMIDA, INC.; RIGHTSCALE, INC.; RISC NETWORKS, LLC; REVULYTICS, INC.
Reel/Frame 067636/0534 →
SECOND LIEN SECURITY AGREEMENT Recorded Mar 3, 2021
From: BDNA CORPORATION; FLEXERA SOFTWARE LLC; PALAMIDA, INC.; RIGHTSCALE, INC.; RISC NETWORKS, LLC; REVULYTICS, INC.
To: JEFFERIES FINANCE LLC
Reel/Frame 055487/0354 →
RELEASE OF SECOND LIEN SECURITY INTEREST Recorded Feb 28, 2020
From: JEFFERIES FINANCE LLC
To: FLEXERA SOFTWARE LLC; PALAMIDA, INC.; BDNA CORPORATION; RIGHTSCALE, INC.; RISC NETWORKS, LLC
Reel/Frame 052049/0560 →
SECOND LIEN SECURITY AGREEMENT Recorded Feb 27, 2018
From: FLEXERA SOFTWARE LLC; PALAMIDA, INC.; BDNA CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 045451/0499 →
TERMINATION OF 2ND LIEN SECURITY INTEREST RECORDED AT REEL/FRAME 032590/0805 Recorded Feb 26, 2018
From: JEFFERIES FINANCE LLC
To: FLEXERA SOFTWARE LLC
Reel/Frame 045447/0842 →
TERMINATION OF 1ST LIEN SECURITY INTEREST RECORDED AT REEL/FRAME 032590/0617 Recorded Feb 26, 2018
From: JEFFERIES FINANCE LLC
To: FLEXERA SOFTWARE LLC
Reel/Frame 045447/0894 →
FIRST LIEN SECURITY AGREEMENT Recorded Feb 26, 2018
From: FLEXERA SOFTWARE LLC; PALAMIDA, INC.; BDNA CORPORATION
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 045441/0499 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Apr 2, 2014
From: FLEXERA SOFTWARE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 032590/0617 →
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2014
From: BANK OF MONTREAL
To: FLEXERA SOFTWARE LLC
Reel/Frame 032581/0652 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Apr 2, 2014
From: FLEXERA SOFTWARE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 032590/0805 →
AMENDED AND RESTATED PATENT SECURITY AGREEMENT Recorded Mar 28, 2013
From: FLEXERA SOFTWARE LLC
To: BANK OF MONTREAL, AS COLLATERAL AGENT
Reel/Frame 030111/0362 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 027022/0216 Recorded Mar 25, 2013
From: BANK OF MONTREAL, AS COLLATERAL AGENT
To: FLEXERA SOFTWARE LLC
Reel/Frame 030081/0178 →
MERGER Recorded Feb 25, 2013
From: INTRAWARE, INC.
To: FLEXERA SOFTWARE LLC
Reel/Frame 029867/0462 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Oct 5, 2011
From: INTRAWARE, INC.
To: BANK OF MONTREAL, AS COLLATERAL AGENT
Reel/Frame 027021/0068 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Oct 5, 2011
From: INTRAWARE, INC.
To: BANK OF MONTREAL, AS COLLATERAL AGENT
Reel/Frame 027022/0216 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Oct 3, 2011
From: BARCLAYS BANK PLC, AS ADMINISTRATIVE AGENT
To: INTRAWARE, INC.
Reel/Frame 027005/0201 →
SECURITY AGREEMENT Recorded Jan 21, 2011
From: INTRAWARE, INC.
To: BARCLAYS BANK PLC, AS ADMINISTRATIVE AGENT
Reel/Frame 025675/0817 →
RELEASE OF SECURITY INTEREST Recorded Jan 20, 2011
From: BANK OF MONTREAL, AS AGENT
To: INTRAWARE, INC.
Reel/Frame 025667/0309 →
SECURITY AGREEMENT Recorded Jan 21, 2009
From: INTRAWARE, INC.
To: BANK OF MONTREAL, AS AGENT
Reel/Frame 022117/0931 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2004
From: BRENTANO, JAMES; PIEPER, TOBID; HABETS, ARIANE
To: INTRAWARE, INC.
Reel/Frame 015294/0827 →