IP Library Granted Patent US 8,135,756
Granted Patent B2
US 8,135,756 · App. 11/608,201 · Granted Mar 13, 2012

Method and system for managing 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 8,135,756
App. No.
11/608,201
Granted
Mar 13, 2012
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 (39)

1. A computer-implemented method of transferring digital goods from one or more vendors to a central network repository, comprising steps of:

assigning each vendor from among said one or more vendors a unique e-commerce server space directory, wherein the unique e-commerce server space directory includes a unique URL that allows vendors access to their own dynamically generated and password-protected web site;

loading one or more versions of a plurality of software files from a source location by a vendor, wherein said source location comprises an FTP server;

obtaining at least one File ID parameter for each version of each software file among the plurality of software files and a source file pathname identifying the actual e-commerce server space directory location of each version of each software file in said plurality of software files at one or more computers operated by said one or more vendors, wherein said at least one File ID parameter is selected 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 each version of each software file in said plurality of software files, and wherein said element contains said at least one File ID parameter;

obtaining, for each software file in said plurality of software files, a vendor identifier and a checksum for verifying the integrity of each version of each software file in said plurality of software files via one or more application-specific forms available to a user through one or more web service, wherein said checksum is configured for tracking multiple versions of said plurality of software files;

linking each version of each software file in said plurality of software files with a corresponding metadata object within a product description;

creating said at least one corresponding metadata object by the vendor of each version of each software file in said plurality of software files;

uploading each version of each software file in said plurality of software files from said source location to said unique e-commerce server space directory, wherein said uploading fails when:

said at least one file image is not found;

said metadata object is not found; or

said software file in said plurality of software files fails an integrity check; and

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

2. A non-transitory computer-readable storage medium encoded with a computer program for transferring digital goods from one or more vendors to a central network 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:

assigning each vendor from among said one or more vendors a unique e-commerce server space directory, wherein the unique e-commerce server space directory includes a unique URL that allows vendors access to their own dynamically generated and password-protected web site;

loading one or more versions of a plurality of software files from a source location by a vendor, wherein said source location comprises an FTP server;

obtaining at least one File ID parameter for each version of each software file among the plurality of software files and a source file pathname identifying the actual e-commerce server space directory location of each version of each software file in said plurality of software files at one or more computers operated by said one or more vendors, wherein said at least one File ID parameter is selected 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 each version of each software file in said plurality of software files, and wherein said element contains said at least one File ID parameter;

obtaining, for each software file in said plurality of software files, a vendor identifier and a checksum for verifying the integrity of each version of each software file in said plurality of software files via one or more application-specific forms available to a user through one or more web service, wherein said checksum is configured for tracking multiple versions of said plurality of software files;

linking each version of each software file in said plurality of software files with a corresponding metadata object within a product description;

creating said at least one corresponding metadata object by the vendor of each version of each software file in said plurality of software files;

uploading each version of each software file in said plurality of software files from said source location to said unique e-commerce server space directory, wherein said uploading fails when:

said at least one file image is not found;

said metadata object is not found; or

said software file in said plurality of software files fails an integrity check; and

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

3. A system for transferring digital goods from one or more vendors to a central network repository, comprising steps of:

a source location comprising a server, wherein one or more versions of a plurality of software files is stored at said location;

memory;

processor means for executing instructions in memory, said instructions including instructions for:

assigning each vendor from among said one or more vendors a unique e-commerce server space directory, wherein the unique e-commerce server space directory includes a unique URL that allows vendors access to their own dynamically generated and password-protected web site;

loading one or more versions of a plurality of software files from a source location by a vendor, wherein said source location comprises an FTP server;

obtaining at least one File ID parameter for each version of each software file among the plurality of software files and a source file pathname identifying the actual e-commerce server space directory location of each version of each software file in said plurality of software files at one or more computers operated by said one or more vendors, wherein said at least one File ID parameter is selected 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 each version of each software file in said plurality of software files, and wherein said element contains said at least one File ID parameter;

obtaining, for each software file in said plurality of software files, a vendor identifier and a checksum for verifying the integrity of each version of each software file in said plurality of software files via one or more application-specific forms available to a user through one or more web service, wherein said checksum is configured for tracking multiple versions of said plurality of software files;

linking each version of each software file in said plurality of software files with a corresponding metadata object within a product description;

creating said at least one corresponding metadata object by the vendor of each version of each software file in said plurality of software files;

uploading each version of each software file in said plurality of software files from said source location to said unique e-commerce server space directory, wherein said uploading fails when:

said at least one file image is not found;

said metadata object is not found; or

said software file in said plurality of software files fails an integrity check; and

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

Assignments (11)
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 →
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 →
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 →
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 →
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2014
From: BANK OF MONTREAL
To: FLEXERA SOFTWARE LLC
Reel/Frame 032581/0652 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Apr 2, 2014
From: FLEXERA SOFTWARE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 032590/0617 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Apr 2, 2014
From: FLEXERA SOFTWARE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 032590/0805 →