Personalized digital media access system—PDMAS part II
DC CAFCFirst Claim
1. A method for authorizing access to digital content using a cloud system, the cloud system comprising connected modules in operation as one or more of a cloud computing or a cloud storage in connection with devices and users, wherein the digital content is at least one of encrypted or not encrypted, the method facilitating access rights between a plurality of data processing devices, the method comprising:
- receiving a digital content access request from at least one communications console of the plurality of data processing devices, the access request being a read or write request of metadata of the digital content, wherein the read or write request of metadata is performed in connection with a combination of at least one device and the cloud system, the request comprising a verification token provided by a first user corresponding to the digital content, wherein the verification token is one or more of a password, e-mail address, payment system, credit card, authorize ready device, rights token, or one or more redeemable instruments of trade;
authenticating the verification token;
establishing a connection with the at least one communications console, wherein the communications console is a combination of a graphic user interface (GUI) and an Application Programmable Interface (API) wherein the API is obtained from a verified web service, the web service capable of facilitating a two way data exchange to complete a verification process wherein the data exchange session comprises at least one identification reference;
requesting the at least one identification reference from the at least one communications console, wherein the identification reference comprises one or more of a verified web service account identifier, letter, number, rights token, e-mail, password, access time, serial number, address, manufacturer identification, checksum, operating system version, browser version, credential, cookie, or key;
receiving the at least one identification reference from the at least one communications console; and
writing at least one of the verification token or the reference into the metadata.
3 Assignments
Litigations
5 Petitions
Accused Products
Abstract
The invention is an apparatus that facilitates access to a data source to accept verification and authentication from an enabler using at least one token and at least one reference. The at least one reference could be a device serial number, a networking MAC address, or a membership ID reference from a web service. Access to the data source is also managed with a plurality of secondary enablers.
328 Citations
30 Claims
-
1. A method for authorizing access to digital content using a cloud system, the cloud system comprising connected modules in operation as one or more of a cloud computing or a cloud storage in connection with devices and users, wherein the digital content is at least one of encrypted or not encrypted, the method facilitating access rights between a plurality of data processing devices, the method comprising:
-
receiving a digital content access request from at least one communications console of the plurality of data processing devices, the access request being a read or write request of metadata of the digital content, wherein the read or write request of metadata is performed in connection with a combination of at least one device and the cloud system, the request comprising a verification token provided by a first user corresponding to the digital content, wherein the verification token is one or more of a password, e-mail address, payment system, credit card, authorize ready device, rights token, or one or more redeemable instruments of trade; authenticating the verification token; establishing a connection with the at least one communications console, wherein the communications console is a combination of a graphic user interface (GUI) and an Application Programmable Interface (API) wherein the API is obtained from a verified web service, the web service capable of facilitating a two way data exchange to complete a verification process wherein the data exchange session comprises at least one identification reference; requesting the at least one identification reference from the at least one communications console, wherein the identification reference comprises one or more of a verified web service account identifier, letter, number, rights token, e-mail, password, access time, serial number, address, manufacturer identification, checksum, operating system version, browser version, credential, cookie, or key; receiving the at least one identification reference from the at least one communications console; and writing at least one of the verification token or the reference into the metadata. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A system for authorizing access to digital content using a worldwide cloud system infrastructure, the worldwide cloud system infrastructure comprising connected modules in operation as computing and storage, the computing and storage comprising a server, a database, devices and users, wherein the digital content is at least one of encrypted or not encrypted, the system facilitating access rights between a plurality of data processing devices, the system working as a front-end agent for access rights authentication between the plurality of data processing devices, the system further comprising:
-
a first receipt module, the first receipt module receiving a digital content access request from at least one communications console of the plurality of data processing devices, the access request being a read or write request of metadata of the digital content, wherein the read or write request of metadata is performed in connection with a combination of a device, the server, the database and the cloud system, the metadata further comprises one or more of a software or contents of a web page, the request comprising a verification token provided by a user corresponding to the digital content, wherein the verification token is one or more of a password, e-mail address, payment system, credit card, authorize ready device, rights token, or one or more redeemable instruments of trade; an authentication module, the authentication module authenticating the verification token; a connection module, the connection module establishing a connection with the at least one communications console, wherein the communications console is a combination of a graphic user interface (GUI) and an Application Programmable Interface (API) wherein the API is obtained from a verified web service, the web service capable of facilitating a two way data exchange to complete a verification process wherein the data exchange session comprises at least one identification reference; a request module, the request module requesting the at least one identification reference from the at least one communications console, wherein the identification reference comprises one or more of a verified web service account identifier, letter, number, rights token, e-mail, password, access time, serial number, address, manufacturer identification, checksum, operating system version, browser version, credential, cookie, or key; a secondary receipt module, the secondary receipt module receiving the at least one identification reference from the at least one communications console; and a branding module, the branding module writing at least one of the verification token or the identification reference into the metadata. - View Dependent Claims (10)
-
-
11. A non-transitory computer medium comprising a program code, the program code being a part of an operating system software or downloaded in sections from a web server, the operating system software program coupled with a user executing a method for authorizing access to digital content wherein the program code, when executed in a processor for facilitating access rights between a plurality of data processing devices, performs the following steps of:
-
receiving a digital content request from at least one communications console of the plurality of data processing devices, the access request being a read or write request of metadata of the digital content, wherein the read or write request of metadata is performed in connection with a combination of the operating system software program and a cloud system, the request comprising a verification token provided by the user corresponding to the digital content, wherein the verification token is one or more of a password, e-mail address, payment system, credit card, authorize ready device, rights token, key, file, or one or more redeemable instruments of trade; authenticating the verification token; establishing a connection with the at least one communications console, wherein the communications console is a combination of a graphic user interface (GUI) and an Applications Programmable Interface (API) wherein the API is obtained from a verified web service, the web service capable of facilitating a two way data exchange to complete a verification process wherein the data exchange session comprises at least one identification reference; requesting the at least one identification reference from the at least one communications console, wherein the identification reference is one or more of a verified web service account identifier, letter, number, rights token, e-mail, password, access time, serial number, address, manufacturer identification, checksum, operating system version, browser version, credential, cookie, or key; receiving the at least one identification reference from the at least one communications console; and writing at least one of the verification token or the identification reference into the metadata. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. A computer product comprising a memory, a CPU, a communications console and a non-transitory computer usable medium, the computer usable medium having an operating system stored therein, the computer product further comprising a customization module, the computer product authorizing access to digital content, wherein the digital content is at least one of an application, a video, or a video game, wherein the digital content is at least one of encrypted or not encrypted, the computer product configured to perform the steps of:
-
receiving the digital content access request from the communications console, the access request being a read or write request of metadata of the digital content, the metadata of the digital content being one or more of a database or storage in connection to the computer product, the request comprising a verification token corresponding to the digital content, the verification token is handled by the user as a redeemable instrument, wherein the verification token comprises at least one of a purchase permission, a rental permission, or a membership permission, wherein the at least one of purchase permission, rental permission, or membership permission being represented by one or more of a tag, a letter, a number, a combination of letters and numbers, a successful payment, a rights token, a phrase, a name, a membership credential, an image, a logo, a service name, an authorization, a list, an interface button, a downloadable program, or the redeemable instrument; authenticating the verification token; establishing a connection with the communications console, wherein the communications console is a combination of a graphic user interface (GUI) and an Applications Programmable Interface (API) wherein the API is obtained from a verified web service, the web service capable of facilitating a two way data exchange to complete a verification process wherein the data exchange session comprises at least one identification reference; requesting the at least one identification reference from the at least one communications console, wherein the identification reference comprises one or more of a verified web service account identifier, letter, number, rights token, e-mail, password, access time, serial number, address, manufacturer identification, checksum, operating system version, browser version, credential, cookie, or key, or ID; receiving the at least one identification reference from the communications console; and writing at least one of the verification token or the identification reference into the said metadata. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29, 30)
-
Specification