US20110247077A1 - System and Method for Rights Offering and Granting Using Shared State Variables - Google Patents

System and Method for Rights Offering and Granting Using Shared State Variables Download PDF

Info

Publication number
US20110247077A1
US20110247077A1 US13/162,826 US201113162826A US2011247077A1 US 20110247077 A1 US20110247077 A1 US 20110247077A1 US 201113162826 A US201113162826 A US 201113162826A US 2011247077 A1 US2011247077 A1 US 2011247077A1
Authority
US
United States
Prior art keywords
rights
meta
state variable
offer
item
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/162,826
Inventor
Mai Nguyen
Xin Wang
Eddie J. Chen
Bijan Tadayon
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Contentguard Holdings Inc
Original Assignee
Contentguard Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=25350385&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US20110247077(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Priority claimed from US10/162,212 external-priority patent/US7774279B2/en
Priority claimed from US10/956,070 external-priority patent/US8001053B2/en
Application filed by Contentguard Holdings Inc filed Critical Contentguard Holdings Inc
Priority to US13/162,826 priority Critical patent/US20110247077A1/en
Assigned to CONTENTGUARD HOLDINGS, INC. reassignment CONTENTGUARD HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TADAYON, BIJAN, CHEN, EDDIE J., NGUYEN, MAI, WANG, XIN
Publication of US20110247077A1 publication Critical patent/US20110247077A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/18Legal services; Handling legal documents
    • G06Q50/184Intellectual property management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • G06Q20/123Shopping for digital content
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • G06Q20/123Shopping for digital content
    • G06Q20/1235Shopping for digital content with control of digital rights management [DRM]
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F17/00Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/16Coin-freed apparatus for hiring articles; Coin-freed facilities or services for devices exhibiting advertisements, announcements, pictures or the like

Definitions

  • the present invention generally relates to offering and granting of rights and more particularly to a method, system and device for offering and granting of rights using shared state variables.
  • the digital age has greatly increased concerns about ownership, access, and control of copyrighted information, restricted services and valuable resources. Rapid evolution and wide deployment has occurred for computers, and other electronic devices such as cellular phones, pagers, PDAs, and e-book readers, and these devices are interconnected through communication links including the Internet, intranets and other networks. These interconnected devices are especially conducive to publication of content, offering of services and availability of resources electronically.
  • IPRM Intelligent Property Rights Management
  • DPRM Digital Property Rights Management
  • IPM Intelligent Property Management
  • RM Remote Lights Management
  • ECM Electronic Copyright Management
  • a “secure container” (or simply an encrypted document) offers a way to keep document contents encrypted until a set of authorization conditions are met and some copyright terms are honored (e.g., payment for use). After the various conditions and terms are verified with the document provider, the document is released to the user in clear form. Commercial products such as Cryptolopes and Digiboxes fall into this category.
  • the secure container approach provides a solution to protecting the document during delivery over insecure channels, but does not provide any mechanism to prevent legitimate users from obtaining the clear document and then using and redistributing it in violation of content owners' intellectual property.
  • trusted system In the “trusted system” approach, the entire system is responsible for preventing unauthorized use and distribution of the document. Building a trusted system usually entails introducing new hardware such as a secure processor, secure storage and secure rendering devices. This also requires that all software applications that run on trusted systems be certified to be trusted. While building tamper-proof trusted systems is a real challenge to existing technologies, current market trends suggest that open and untrusted systems, such as PC's and workstations using browsers to access the Web, will be the dominant systems used to access digital works.
  • Some DRM systems allow content owners to specify usage rights and conditions, and associate them with content. These usage rights control how the recipient thereof can use the content. Usually after a content distributor or consumer has completed selecting and ordering specific content, the content is delivered either electronically from some content repository or via a conventional distribution channel to the recipient, such as tangible media sent via a common carrier. Corresponding DRM systems used by the recipient, for example the distributor or consumer, will then interpret the rights and conditions associated with the content, and use them to control how the content is distributed and/or used. Examples of usage rights include view, print and extract the content, and distribute, repackage and loan content. Associated conditions may include any term upon which the rights may be contingent such as payment, identification, time period, or the like.
  • U.S. Pat. No. 5,634,012 discloses a system for controlling the distribution of digital documents. Each rendering device has a repository associated therewith. A predetermined set of usage transaction steps define a protocol used by the repositories for enforcing usage rights associated with a document. Usage rights persist with the document content. The usage rights can permit various manners of use such as, viewing only, use once, distribution, and the like. Usage rights can be contingent on payment or other conditions.
  • Exemplary aspects of the present invention include a method, system and device for sharing rights adapted to be associated with items, the method and system including generating at least one of usage rights and meta-rights for the items; defining, via the usage rights, a manner of use for the items; and defining, via the meta-rights, a manner of rights transfer for the items.
  • the device including receiving at least one of usage rights and meta-rights for the items; interpreting, via the usage rights, a manner of use for the items; and interpreting, via the meta-rights, a manner of rights transfer for the items.
  • the usage rights or the meta-rights include at least one state variable that is shared by one or more rights.
  • FIG. 1 is a schematic diagram of a three-tier model for content distribution
  • FIG. 2 is a schematic diagram illustrating rights offering and granting processes in the model of FIG. 1 ;
  • FIG. 3( a ) is a schematic diagram of a simple supplier-consumer push model for rights generating, issuing and exercising;
  • FIG. 3( b ) is a schematic diagram of a simple supplier-consumer pull model for rights generating, issuing and exercising;
  • FIG. 4 is a block diagram of a rights offering-granting architecture in accordance with the preferred embodiment
  • FIGS. 5 a and 5 b are workflow diagrams for examples of offering and granting rights between a rights supplier and a rights consumer with a push and pull model respectively;
  • FIG. 6 is a flow chart of a rights offer generation process in accordance with the preferred embodiment
  • FIG. 7 is a flow chart of a rights offer consideration process in accordance with the preferred embodiment.
  • FIG. 8 is a flow chart of a rights offer customization process in accordance with the preferred embodiment.
  • FIG. 9 is block diagram of a DRM system that may be utilized in connection with the preferred embodiment.
  • FIG. 10 is a block diagram of an exemplary structure of a license containing usage rights and meta-rights of the preferred embodiment
  • FIG. 11 is a schematic illustration of a rights label of the preferred embodiment
  • FIG. 12 illustrates an exemplary system including a state-of-rights server
  • FIG. 13 illustrates employing of a state variable in deriving exclusive usage rights
  • FIG. 14 illustrates employing of a state variable in deriving inherited usage rights
  • FIG. 15 illustrates employing of a state variable in deriving rights that are shared among a known set of rights recipients
  • FIG. 16 illustrates employing of a state variable in deriving rights that are shared among a dynamic set of rights recipients
  • FIG. 17 illustrates employing of a state variable in maintaining a state shared by multiple rights
  • FIG. 18 illustrates employing of multiple state variables to represent one state of rights
  • FIG. 19 illustrates a case where not all rights are associated with states
  • FIG. 20 illustrates a case where not all rights which are associated with states are shared or inherited.
  • FIG. 21 illustrates a case of rights sharing based on an offer which does not explicitly include meta-rights.
  • FIG. 9 illustrates DRM System 10 that includes a user activation component, in the form of activation server 20 , that issues public and private key pairs, or other identification mechanisms, to content users in a protected fashion, as is well known.
  • a user activation component in the form of activation server 20
  • the user installs software that works with, or includes, a rendering application for a particular content format.
  • the software is installed in client environment 30 , a computer associated with the content recipient, for example.
  • the software is part of DRM 10 system and is used to enforce usage rights for protected content.
  • Client component 60 preferably is tamper resistant and contains the set of public and private keys issued by activation server 20 as well as other components, such as rendering components for example.
  • Rights label 40 is associated with content 42 and specifies usage rights and meta-rights that are available to a recipient, i.e. a consumer of rights, when corresponding conditions are satisfied.
  • License Server 50 manages the encryption keys and issues licenses 52 for protected content 42 .
  • Licenses 52 embody the actual granting of rights, including usage rights and meta-rights, to an end user.
  • rights offer 40 may permit a user to view content for a fee of five dollars and print content for a fee of ten dollars, or it may permit a user to offer rights to another user, for example, by utilizing the concept of meta-rights described below. License 52 can be issued for the view right when the five dollar fee has been paid.
  • Client component 60 interprets and enforces the rights, including usage rights and meta-rights, that have been specified in the license. Rights label 40 and license 52 are described in detail below.
  • FIG. 11 illustrates rights label 40 in accordance with the preferred embodiment.
  • Rights label 40 includes plural rights options 44 .
  • Each rights option 44 includes usage rights 44 a , conditions 44 b , and content specification 44 c .
  • Content specification 44 c can include any mechanism for referencing, calling, locating, or otherwise specifying content 42 associated with rights offer 44 .
  • license 52 includes license 52 a , grant 52 b , and digital signature 52 c .
  • Grant 52 b includes granted usage rights and/or meta-rights selected from label.
  • the structure of the grant also includes one or more principals, to whom the specified usage rights and/or meta-rights are granted, a list of conditions, and state variables required to enforce the license.
  • Like usage rights, access and exercise of the granted meta-rights are controlled by the condition list and state variables as described below.
  • Clear (unprotected) content can be prepared with document preparation application 72 installed on computer 70 associated with a content publisher, a content distributor, a content service provider, or any other party.
  • Preparation of content consists of specifying the usage rights, meta-rights, and conditions under which content 42 can be used and distributed, associating rights label 40 with content 42 and protecting content 42 with some crypto algorithm.
  • a rights language such as XrML can be used to specify the rights and conditions.
  • the usage rights and meta-rights can be specified in any manner.
  • the rights can be in the form of a pre-defined specification or template that is merely associated with the content. Accordingly, the process of specifying rights refers to any process for associating rights with content.
  • Rights label 40 associated with content 42 and the encryption key used to encrypt the content can be transmitted to license server 50 .
  • Rights can specify transfer rights, such as distribution rights, and can permit granting of rights to others or the derivation of rights. Such rights are referred to as “meta-rights”. Meta-rights are the rights that one has to manipulate, modify, or otherwise derive other meta-rights or usage rights. Meta-rights can be thought of as usage rights to usage rights. Meta-rights can include rights to offer, grant, obtain, transfer, delegate, track, surrender, exchange, and revoke usage rights to/from others. Meta-rights can include the rights to modify any of the conditions associated with other rights. For example, a meta-right may be the right to extend or reduce the scope of a particular right. A meta-right may also be the right to extend or reduce the validation period of a right.
  • Conditions must be satisfied in order to exercise the manner of use in a specified right.
  • a condition may be the payment of a fee, submission of personal data, or any other requirement desired before permitting exercise of a manner of use.
  • Conditions can also be “access conditions” for example, access conditions can apply to a particular group of users, say students in a university, or members of a book club. In other words, the condition is that the user is a particular person or member of a particular group. Rights and conditions can exist as separate entities or can be combined.
  • State variables track potentially dynamic states conditions.
  • State variables are variables having values that represent status of an item, usage rights, license or other dynamic conditions. State variables can be tracked, by clearinghouse 90 license or server 30 another device, based on identification mechanisms in license 52 . Further, the value of state variables can be used in a condition. For example, a usage right can be the right to print content 42 three times. Each time the usage right is exercised, the value of the state variable “number of prints” is incremented. In this example, when the value of the state variable is three, the condition is not longer satisfied and content 42 cannot be printed. Another example of a state variable is time. A condition of license 52 may require that content 42 is printed within thirty days. A state variable can be used to track the expiration of thirty days. Further, the state of a right can be tracked as a collection of state variables. The collection of the change is the state of a usage right represents the usage history of that right.
  • a typical workflow for DRM system 10 is described below.
  • a recipient such as a user, operating within client environment 30 is activated for receiving content by activation server 20 .
  • This activation process can be accomplished at any time prior to the issuing of a license.
  • a user When a user wishes to use protected content 42 , the user makes a request for the content 42 .
  • a user might browse a Web site running on Web server 80 associated with a grantor of rights such as a content distributor, using a browser installed in client environment 30 , and attempt to download protected content 42 .
  • the user may go through a series of steps possibly including a fee transaction (as in the sale of content) or other transactions (such as collection of information).
  • Web server 80 contacts license server 50 through a secure communications channel, such as a channel using a Secure Sockets Layer (SSL).
  • License server 50 then generates license 52 for the content and Web server 80 causes both protected content 42 and license 52 to be downloaded.
  • License 52 can be downloaded from license server 50 or an associated device.
  • Content 42 can be downloaded from computer 70 associated with a publisher, distributor, or other party.
  • Client component 60 in client environment 30 will then proceed to interpret license 52 and allow use of content 42 based on the rights and conditions specified in license 52 .
  • the interpretation and enforcement of usage rights are well known generally. The steps above may take place sequentially or approximately simultaneously or in various order.
  • DRM system 10 addresses security aspects of protecting content 42 .
  • DRM system 10 may authenticate license 52 that has been issued by license server 50 .
  • One way to accomplish such authentication is for application 60 to determine if the licenses can be trusted.
  • application 60 has the capability to verify and validate the cryptographic signature of digital signature 52 c , or other identifying characteristic of the license.
  • both client environment 30 and license server 50 receive a set of keys in a tamper-resistant software “package” that also includes other components, such as the necessary components for activated client environment 30 to verify signature 52 of license 52 in a known manner.
  • the example above is merely one way to effect a DRM system.
  • the license and content can be distributed from different entities.
  • rights offer 40 can be associated with content by a party other than the party preparing the content.
  • clearinghouse 90 can be used to process payment transactions and verify payment prior to issuing a license.
  • the function of the supplier is to offer, and possibly grant, the rights, and the function of the consumer is to select, and possibly exercise the rights. Both the supplier and consumer may actually represent two or more entities. In general, multiple entities may collectively make an offer and grant rights to multiple entities.
  • the supplier and consumer represent any two entities in the content value chain that have a direct relationship with each other regarding the granting of rights. At the beginning of the value chain, the supplier and consumer may be author and publisher.
  • the supplier and consumer may be a publisher and another publisher (for content aggregation), a publisher and distributor (for content distribution), a distributor and another distributor (for multi-tier content distribution), a distributor and a retailer (for content retailing), a retailer and a consumer (for content consumption), and a consumer and another consumer (for content supper-distribution or personal lending).
  • An “offer of rights” or “rights offer” expresses how a consumer (e.g. a content distributor or user) can acquire a particular instance of content together with its associated usage rights and/or meta-rights.
  • An offer may or may not contain financial terms.
  • An offer is an expression of mere willingness to commerce negotiation and also an expression of willingness to grant on terms stated.
  • An offer may be expressed in the form of a rights label.
  • a “consideration of rights” is a process as part of the rights granting in which the rights consumer has examined the rights being offered and possibly bargained them and associated terms and conditions.
  • a “choice of rights” is a selection of rights and their associated terms and conditions from a rights offer. It indicates the intent of the consumer to accept these rights and the corresponding terms and conditions.
  • selection can comprise selecting one option 44 from label 40 .
  • Customerization of rights is a process as part of the rights granting in which the rights supplier assembles rights and terms and conditions based on a choice of the rights consumer. The output of this process can be a draft license to be accepted by the rights consumer.
  • a “license of rights” is an expression of rights and possibly conditions accepted and agreed upon by the rights supplier and consumer. It is the output of the rights offering and granting process.
  • a license is a grant to exercise the rights that govern the usage (possibly including further distribution) of content or other items.
  • a rights label such as rights label 40
  • the accepted rights may include a right to present offers to others or make selections of offers.
  • FIG. 1 An example of a distribution chain model is illustrated in FIG. 1 .
  • the distribution chain includes a content provider 100 , distributor 110 , and end user 120 .
  • content may be prepared in the manner described above. It is assumed that the content has already been prepared in the model of FIG. 1 .
  • FIG. 1 is directed to the transfer of content and shows that, in this example, provider 100 may publish content to distributor 110 or receive content for reuse from distributor 110 .
  • Distributor 110 may in turn distribute content to user 120 or receive returned content form user 120 .
  • User 100 can use content.
  • provider 100 can aggregate content from others, distributor 110 , can receive content from other distributors for redistribution, and user 120 can share content with the other users. It is clear that there are plural stages in the content life cycle and plural relationships between the various parties. A precise and consistent specification of rights at the different stages of the life cycle and relationships is important and crucial to persistent protection of content in multi-tier distribution and usage.
  • FIG. 2 illustrates the flow of rights in the same model, including rights generating, aggregating, issuing, relinquishing, driving, granting, surrendering, delegating and exercising.
  • the model of FIG. 2 includes the same entities, provider 100 , distributor 110 , and user 120 . It can be seen that, with respect to the flow of rights, each party can grant and accept rights. User 120 can grant and accept rights from other users, a process called “delegation”, in this example.
  • the model of FIG. 2 covers many specific content publishing, distribution and use relationships. Other models can be derived from on this model by a different consolidation or segregation of the parties. For example, every provider can be a distributor. This is “direct publishing”, which allows individual authors to distribute/sell their content without any intermediate publisher. Further, every consumer can be a potential distributor. This allows consumers to pass content to each other. This includes supper-distribution, gifting, and personal lending. In a “Web community” and everyone is able to publish, distribute and consume content. “Content aggregation” allows publishers to compose content from other publishers into composite works. Site license and enterprise use allows sharing content among consumers.
  • FIG. 3( a ) shows a “push” model
  • FIG. 3( b ) shows a “pull” model.
  • rights supplier 200 initiates the rights offering and granting process by generating an offer and granting the rights to the rights consumer 210 .
  • rights consumer 210 initiates the process by requesting an offer and accepting the rights from the rights supplier 200 .
  • Architecture 400 can be implemented as a combination of computer hardware and software and includes rights supplier component 402 , rights consumer component 438 and communication channel 422 linking these two components.
  • communication channel 42 can be Internet, a direct computer to computer connection, a LAN, a wireless connection or the like.
  • Supplier component 402 is associated with the supplier, i.e. the entity making rights available to a consumer who is the entity going to exercise, i.e., consume the rights.
  • the supplier could be the content owner or provider, or could be a distributor or any “middle-man,” such as a retailer or operator of a web site.
  • Consumer component 438 is associated with the consumer who could be the ultimate user (i.e., content consumer) or a “middle-man,” such as a retailer, whole-seller, or reseller. Keep in mind that the consumer consumes rights and does not necessarily use (i.e. consume) the content.
  • Both supplier component 402 and consumer component 438 can embody any type of hardware devices, and or software modules, such as a personal computer, a handheld computer, a mobile phone a server, a network, or any combination of the same.
  • Supplier component 402 generates rights label 40 as offers, presents draft licenses and grants license 52 to the consumer.
  • Consumer component 438 issues requests, select choices of options 44 from rights labels 40 , generates counter offers, and accepts licenses 52 .
  • Supplier component 402 and consumer component 438 can be embodied in the same device(s) and communication channel 422 can be an internal channel.
  • Supplier component 402 contains user interface module 404 , communication interface module 420 identity module 406 repository 412 for supplier's rights (e.g., in the form of issued licenses) and database 414 for management related information.
  • User interface 404 accomplishes presentation to the user of the component functions and acceptance of user interactions in a known manner.
  • Communication interface 422 provides the proper formatting and protocols for messages between supplier component 402 and consumer component 438 .
  • Identity module 406 ensures that the identity of supplier component 402 can be authenticated by consumer component 438 and may contain authentication information like a password, cryptographic keys or biometric information of the user of supplier component 402 .
  • Rights repository 412 stores rights granted to the user of supplier component 402 and may include functions for indexing, searching and updating the rights stored within.
  • Management database 414 is used to archive information generated during the rights offering and granting processes. Such information includes information related to initial offers, consumer choices, possible counter-offers, agreements and final licenses.
  • Consumer component 438 includes user interface module 428 , communication interface module 424 , identity module 426 , repository 434 for consumer's rights (e.g., in the form of issued licenses), and database 436 for management related information.
  • User interface 424 deals handles presentation to the user of the component and acceptance of user interactions.
  • Communication interface 422 provides the proper formatting and protocols for rights offering and granting messages between supplier component 402 and consumer component 438 .
  • Identity module 426 ensures that the identity of the consumer component 438 can be authenticated by supplier component 402 and may contain authentication information like a password, cryptographic keys or biometric information of the user.
  • Rights repository 434 stores rights granted to the user of consumer component 438 and may include functions for indexing, searching and updating the rights stored within.
  • Management database 436 is used to archive information generated during the rights offering and granting process.
  • the information includes that related to offers 44 , consumer choices, possible counter-offers, agreements and licenses 52 .
  • database 436 can store information that is the same as or different from database 414 because the parties may interact with other parties and thus have different archived information.
  • Supplier component 402 also includes offer generator module 408 for generating offers, rights composer module 410 for composing licenses, offer templates module 418 for providing templates for generating offers based on previous transactions and common formality of offers, and consumer profiles module 416 for customizing and granting rights based on past consumer characteristics and relationships.
  • Consumer component 438 also includes offer analyzer module 430 for understanding rights and their terms and conditions presented within offers, a choice maker module 432 for selecting favorable options specified in offers, a supplier preference module 438 for describing any preferred suppliers based on past and existing supplier characteristics and relationships, and choice patterns module 440 for providing patterns and interests in selection options in offers.
  • the choice pattern module 440 may include a list of preferred suppliers or a list of lowest prices for the item of interest to the consumer.
  • Offer analyzer module 430 and choice maker module 432 may be combined into one module.
  • the process of offering and granting rights within architecture 400 is based on protocols followed by supplier component 402 and consumer component 438 .
  • These protocols generally consist of an offer and acceptance of that offer.
  • the protocols include an offering of rights by one party to another and acceptance of that offer by the person to whom it is made.
  • An offer, once made, may be styled so that it may revoked before acceptance or the offeror could styled it so that it cannot be revoked at all or only under certain circumstances definable by the offeror.
  • An offer can also expire in various way, for example if a deadline for acceptance passes. If there is no specified deadline, then the offer could expire in a predetermined reasonable time, depending on the subject matter of the offer.
  • a reasonable time could be accord to the period of the content publication, for example.
  • a reasonable time could be any time before the availability of the content.
  • the rights supplier can dictate other terms of the acceptance, to which the rights consumer is bound. For example, the offer may require acceptance in sending back in a certain form via an email or through a certain web page interface.
  • FIG. 5( a ) illustrates the workflow of protocol 500 of a push model for rights granting.
  • Supplier component 402 generates an offer of rights in the form of rights label 40 for example, with possibly many options 44 , and sends it to consumer component 438 ( 510 ).
  • Consumer component 438 considers the offer and its possible options, and responds to supplier component 402 with a choice of any of the optional rights offer 44 ( 512 ).
  • Supplier component 402 customizes rights according to the consumer's response, and issues the rights the user of consumer component 432 ( 514 ) in the form of a draft license.
  • Consumer component 438 then accepts the draft license if it corresponds to the choice made and is otherwise acceptable ( 516 ).
  • supplier component 402 Upon acceptance, supplier component 402 generates license 52 and transmits license 52 to consumer component ( 518 ).
  • grant 52 b of license 52 can include usage rights and/or meta-rights. Therefore license 52 can permit the user of consumer component 438 to grant rights to others in a similar fashion. However, the derivable rights are controlled by upstream parties through the use of meta-rights.
  • the protocol can include steps where supplier component 402 requests to make payment through a credit card of the user of consumer component 438 , and the user component 402 provides the information and authorizes the charge. Both supplier component 402 and consumer component 438 can generate status reports on success or failure of the process. Further, parties can authenticate each other during the process and maintain authentication through the process.
  • FIG. 5( b ) shows a protocol of pull model for rights granting.
  • consumer component 438 sends a request to supplier component 402 to indicate an interest in obtaining certain rights in content ( 520 ).
  • Supplier component 402 then responds with an offer, in the form of label 40 having plural offer options 44 , covering the rights requested by consumer component 438 , and sends the offer to consumer component 438 ( 522 ).
  • Consumer component 438 then considers the offer and its options, and responds to supplier component 402 with a choice of one of the offer options ( 524 ).
  • Supplier component 402 customizes rights according to the response, and grant the rights to the consumer in the form of a draft license ( 526 ).
  • Consumer component 438 then accepts the draft license ( 528 ) and supplier component 402 issues license 52 granting rights to consumer component 438 ( 530 ).
  • the rights can include meta-rights.
  • FIG. 6 illustrates the offer generation process 600 performed by offer generator module 408 in supplier component 402 .
  • available rights are first collected in block 602 . Rights may be available from a previous supplier by being derived from meta-rights granted to the supplier or may be originally created rights.
  • step 604 it is determined whether supplier has a right to make an offer to the consumer. For example, if the consumer is known to be a minor and the content is restricted to an adult consumer or if the consumer is on a list of those prohibited from receiving content, the supplier may not make an offer. In such case, the offer generation process terminates in step 606 .
  • the process determines all the rights that can be offered to the consumer in step 608 by parsing the rights collected in step 602 .
  • the process determines whether the consumer has requested any specific rights. If a request has been received, the process further filters the determined rights that can be offered, taking the received consumer requested rights into consideration and comparing them to the available rights. Then, the process determines whether an offer template needs to be applied in steps 614 .
  • the consumer might be offered standard rights included in the template, such as printing right, archiving right, etc. of the content.
  • the offer template is then applied in steps 616 .
  • human intervention may be provided to further make adjustments to the offer template or to any of the rights that are available for offering thus far in the process.
  • restrictions can be applied, through conditions and/or state variables. For example, a time restriction may be place on certain rights in step 620 .
  • a digital signature or other authentication is provided with the collection of rights to be offered in step 622 and an authenticated offer, in the form of rights label 40 is made in step 624 and presented to consumer component 438 in step 624 .
  • FIG. 8 illustrates rights customization process 800 which is performed by rights composer module 410 in supplier component 402 .
  • consumer's choices are received in step 802 .
  • Choices are rights and conditions of an option 44 selected label 40 of step 624 ( FIG. 6 ).
  • the process determines if supplier component 402 has the right to grant rights to consumer component 438 in step 804 . For example, if the consumer fails to meet a certain requirement, such as minimum age or proof of residence in a locale where content may be licensed, for example, granting a license may not be proper, and the rights customization process 800 terminates in step 806 . Otherwise, consumer selected choices are analyzed in step 808 to ascertain if they are an discernible by supplier component 402 . For example, the choices can be parsed to see if they are understandable.
  • step 810 determines if consumer information is available in step 810 .
  • consumer profiles may be stored in database 414 ( FIG. 4 ). If available, the consumer information is taken into consideration in step 812 for further analysis of consumer choices.
  • dynamic information can also considered as described below.
  • the profile may include a trust rating or address of the consumer that renders it desirable of undesirable to provide certain rights.
  • the process determines if the choices are reasonable in step 814 . This determination may be carried out, for example, computationally or with human intervention. If the customer's choices are deemed unreasonable, re-negotiation of the customer's choices is then performed in block 816 .
  • the customer is presented with a new proposed offer based on the previously analyzed choices, the customer is given an opportunity to submit new choices offered, and the right customization process 800 begins again in step 802 . Otherwise, a license including the selected rights is created in step 818 .
  • step 820 After a license is created, if consumer acceptance is necessary (step 820 ), it is presented to the consumer for review in step 822 . If the consumer does not agree with the terms in the license in step 824 , re-negotiation is then initiated in step 816 , which re-starts the rights customization process 800 again in step 802 . In step 820 , if a review by the consumer is not required, then the license is authenticated in step 826 to create a completed license 52 in step 828 which is to be issued and associated with content 42 .
  • FIG. 7 illustrates offer consideration process 700 which is performed by offer analyzer module 430 and choice maker module 432 of consumer component 438 .
  • Available offers are first collected in step 702 .
  • process 700 determines whether it has a right to accept offers from the supplier. For example, if the consumer certain restrictions on the purchase of content, such as an age restriction or a restriction against accepting content from outside an enterprise, the consumer may not accept an offer. In such a case, the offer consideration process terminates in step 706 . If the consumer has the right to accept offers from the supplier, the offers are then analyzed in step 708 to ascertain if they are discernible. If it is determined that supplier preferences are available in step 710 , the offers are filtered in step 712 based on the preferences.
  • step 714 determines if consumer preferences are available and, if so, they are applied in step 716 to the offers. Once all the offers are analyzed, by applying the logic of steps 708 - 714 and any other desired logic, the consumer then selects options in block 718 and specifies contingencies in block 720 . The selection of options can be done automatically. If human intervention is desired, the customer can intervene and further specify additional choices or conditions desired. Any preferences, rules, or other logic can be used to analyze offers.
  • the consumer sends a request, and then a license is constructed.
  • the request is a subset of an offer and the offer has one or more options.
  • the supplier makes the offer available to the consumer sending the request (and to other consumers if that is the desire), and the consumer (including other consumers, if applicable) makes choices. Then, the supplier analyzes the choices, and constructs the license (i.e. a grant of rights). Note that the request can also be rejected, or a counter proposal could be made and the same process could then repeat for the counter proposal.
  • the analysis may be done automatically, or with human intervention.
  • the choice or acceptance may be done automatically, or with human intervention.
  • Either the offer or a license, or both, may be generated based on the dynamic information, the consumer's information, and the consumer's request, such as described above.
  • the dynamic information may include many kinds of information including information related to pricing, status of the network, the traffic of a web site at each moment of time, discounts given, coupons given, the habits of the consumer, how many times the content has been used, for how long the content was used, where it was used, or the like.
  • the dynamic information can be tracked as state variables and the values of the state variables can be checked and updated as necessary.
  • Dynamic information is information capable of being (although, it need not actually be) changed or created by or by reference to a non-static element.
  • the dynamic information can be obtained based on a formula, database, curve, predetermined table, percentage of a value, a function, reference to other data, such as the prime rate of interest or the change in a stock market index, and/or by a human intervention of the user or distributor, and/or consumer's input.
  • the consumer's information may include information such as the age of the consumer, the credit history of the consumer, the credit limit of the consumer, income of the consumer, what kind of rights or licenses obtained, the password of the consumer, the key assigned to the consumer, club membership for access or discount, the class of the consumer based on a predetermined criteria, or any other data, identification characteristics and information.
  • the supplier's information may include some or all of the subjects of information as the consumer's information, and may also include, for example, available options or variations, suppliers, shipping information, and other information.
  • the system and processes disclosed in this invention support multi-tier and super distributions of content.
  • the following is a use case that shows how this can be modeled and supported. It illustrates the process of offering and granting rights by showing the process of transforming offered rights to a rights supplier (the content distributor in this case) to granted rights to a rights consumer (the end user in this case). It specifically shows how an offer is generated from an existing license, how this offer is considered with a choice, and how a final license is issued. Meta-rights provide a mechanism for permitting the transfer of rights from one party to the next party in a content distribution chain.
  • a content provider P of some content C wants to specify that a distributor D may sell, to any end user within the region of the United States (US), the “play” right at a flat rate of $1 and the “print” right at a cost of $4 per copy (both are paid by D to P).
  • the provider also allows the content distributor to add its own conditions to the “play” and “print” rights it issues to end users.
  • a license from the content provider to the distributor may resemble the following using the XrML rights language.
  • the distributor may make an offer to the end user based on the rights it has as expressed in the license above. Note that usage rights and conditions of each option are set forth as XML elements between ⁇ grant> tags. In the following offer, note that the distributor adds a fee condition for getting the “play” right, charging the end user $2 ($1 more than it pays to the provider), and another fee condition for the “print” right, charging the end user $6 per print copy ($1 more than it pays to the provider). The distributor also limits the offer to an acceptance time period (up to Dec. 31, 2002). Meta rights granted to the distributor permit the distributor to modify the grant in the license, as described above, and make the offer.
  • the end user may choose to get only the right to “play” for the flat fee of $2 and responds to the distributor with a choice set forth as an XML element between ⁇ choice> tags as follows.
  • a response can also be constructed as a counter offer for rights not originally offered by the distributor.
  • the distributor receives the choice from the end user, it then issues a license to the user as shown below.
  • the issuers may choose to digitally sign the documents using some digital signature algorithms.
  • the recipients of these documents have options to verify the validity of these documents by checking the validity of the attached digital signatures.
  • Access to the various documents, and elements thereof, can be controlled using known techniques.
  • derived rights obtained as a result of meta-rights, may inherit and/or share the state variable values associated with the rights. For example, when one is granted with the right to print 5 times and make 4 copies of some document, all new copies may have the same set of rights but share the state (or remaining rights) with the original. After the original has been printed 2 times and a new copy was then made, the copy and original can all together print 3 times and make 2 more new copies.
  • the exemplary embodiments include a method for transferring usage rights adapted to be associated with items.
  • the method includes generating, by a supplier, at least one first offer containing usage rights and meta-rights for the item, the usage rights defining a manner of use for the items, the meta-rights specifying rights to derive usage rights or other meta-rights, presenting the offer to a first consumer, receiving a selection from the first consumer indicating desired usage rights and meta-rights, and generating a first license granting the desired usage rights and meta-rights to the first consumer.
  • the exemplary embodiments further include a system for transferring usage rights adapted to be associated with an item to be licensed in multi-tier channels of distribution with downstream rights and conditions assigned at least one level.
  • the system includes a supplier component, comprising a supplier user interface module, an offer generator module for generating an offer containing at least usage rights and of meta-rights, a rights composer module for composing a draft license, and a repository for supplier's rights, a supplier management database.
  • the system further includes a consumer component comprising a consumer user interface module, an offer-consideration module configured to analyze the offers generated by the supplier component and select offers based on the analysis, and a repository for consumer's rights, a consumer management database.
  • the exemplary embodiments still further include a method for generating a license to digital content to be used within a system for at least one of managing use and distribution of the digital content.
  • the method includes presenting a consumer with an offer including meta-rights, receiving a selection by the consumer of at least one meta-right in the offer, generating a license based on the selection, wherein the license permits the consumer to exercise the at least one meta-right and permits the consumer to offer at least one derived right derived from the at least one meta-right and generate a license including the at least one derived right.
  • FIG. 12 illustrates an exemplary system including a common state-of-rights server, according to the present invention.
  • the exemplary system can include a common state-of-rights server of the system 1201 , including a state-of-rights manager 1209 , and one or more state-of-rights repositories 1214 , and one or more license servers 1200 , including a meta-rights manager 1210 , a usage rights manager 1212 , an authorization component 1208 , a condition validator 1206 , a state-of-rights manager 1204 , one or more state-of-rights repositories 1216 , a license manager 1203 , a license interpreter 1202 , and one or more license repositories 1218 .
  • the common state-of-rights server 1201 can be configured as a remote server connected with one or more of the license servers 1200 .
  • the common state-of-rights server 1201 provides comparable services as the state-of-rights manager 1204 in the license servers 1200 via the state-of-rights manager 1209 .
  • the services provided by the state-of-rights server 1201 are accessible and states that the server 1201 manages can be shared by one or more rights suppliers and rights consumers (not shown).
  • the state-of-rights server 1201 can be configured as a remote server connected with one or more of the license servers 1200 via one or more communication links 1220 , and the like.
  • the services provided by the state-of-rights server 1201 also can be integrated within one or more of the license server 1200 and such services can be accessible by other rights suppliers, rights consumers, and the like.
  • the license manager 1203 derives new rights based on an offer, which can include any suitable machine-readable expression, and optionally including meta-rights. While deriving rights, the license manager 1203 can create new state variables to be associated with derived rights.
  • the creation of state variables and their scopes can be prescribed in the offer or by some other function in the system.
  • the state variables can be created in one or more instances, for example, prior to rights derivation, during rights derivation, upon fulfillment of conditions, during a first exercise of rights associated with the state variables, and the like.
  • the state variables can be designated exclusively for a specific rights consumer, can be shared among rights consumers, and can be shared among rights consumers and other entities, such as rights suppliers, and the like.
  • the license manager 1203 can interact with the state-of-rights manager 1204 to associate new state variables with physical addresses in one or more of the state-of-rights repositories 1216 .
  • the state-of-rights manager 1204 can access the one or more state-of-rights repositories 1216 and can interact with the state-of-rights server 1201 to access shared state variables from one or more of the state-of-rights repositories 1214 .
  • Designated state variables can be used to support a license that grants a recipient of the license a right to print content 5 times
  • shared state variables can be used to support a site license that grants a group of authorized users a right to print content an aggregated total of 100 times, and the like.
  • a designated state variable can be updated when the corresponding right is exercised, whereas a shared state variable can be updated when an authorized user exercises the corresponding right.
  • a shared state variable can include a data variable that is updated in response to actions by a plurality of users and which is globally applied to each of the users.
  • state variables can be local, and solely confined to a recipient or can be global, and shared by a predetermined group of recipients.
  • a global state variable can be shared by a group of recipients not determined when derived rights are issued, but to be specified later, perhaps based on certain rules defined in the license or based on other means.
  • a global state variable can be shared between one or more rights suppliers, predetermined recipients, un-specified recipients, and the like.
  • state variables can be created at different stages of the value chain.
  • a state variable can be unspecified in meta-rights, which means the identifier and value of the state variable are yet to be determined by the meta-rights manager module 1210 and included in the derived right. If a distinct state variable is assigned to each derived right, the scope of the state variable in the derived right is typically exclusive to the recipient.
  • FIG. 13 is used to illustrate employing of a state variable in deriving exclusive usage rights, according to the present invention.
  • rights 1302 and 1303 derived from an offer 1301 are exclusive to each respective consumer.
  • the offer 1301 is a type of meta-right of which the recipients have the rights to obtain specific derivative rights when the conditions for obtaining such rights are satisfied.
  • the exemplary offer 1301 has an unspecified state variable 1304 .
  • specific state variable 1305 and 1306 each with uniquely assigned identifications (IDs) are included in the derived rights 1302 and 1303 .
  • the derived state variables 1305 and 1306 are bound to their associated derived rights, e.g., “AlicePlayEbook” (i.e., Alice has the right to play Ebook) is bound to derived right 1302 , and “BobPlayEbook” (i.e., Bob has the right to play Ebook) is bound to derived right 1303
  • “AlicePlayEbook” variable can be updated when Alice exercises her play right
  • the “BobPlayEbook” variable can be updated when Bob exercises his play right.
  • a right can transfer from an entity to a recipient.
  • the governing of the associated state variable is also transferred to the recipient.
  • the source principal typically can no longer exercise the right, whereas the recipient can exercise the right.
  • the license server governing the exercising of a right of a recipient assumes the responsibility for state management. If, however, the state variables are managed by the common state of right server 1201 , the state of right server 1201 needs to be informed of the transfer of right. Specifically, the state variable can be managed in the context of the recipient after the transfer of right.
  • a right When a right is to be shared between the source principal and the recipient, the associated state variable is referenced in the derived right. If the same right is shared with multiple recipients, then typically all of the recipients share the same state variables with the source principal. In this case, a shared state can be managed by an entity that is accessible by all sharing principals.
  • FIG. 14 is used to illustrate employing of a state variable in deriving inherited usage rights, according to the present invention.
  • a derived right can inherit a state variable from meta-rights.
  • a personal computer (PC) of a user Alice
  • a personal data assistant (PDA) of Alice also can obtain a right to play the e-book according to offer 1401 , if the PC and PDA share the same state variables 1404 and 1405 , e.g., “AlicePlayEbook.”
  • a derived right 1402 allows Alice also to play the e-book on her PDA as long as the PDA and the PC share a same count limit 1406 of 5 times.
  • a state variable for tracking a corresponding usage right can be specified in a meta-right using a same state variable identification for all recipients. During a process of exercising the meta-right, the same state variable identification is included in every derived right.
  • FIG. 15 illustrates the use of state variable in deriving rights that are shared among a known set of rights recipients, according to the present invention.
  • a site license 1501 is issued to FooU university.
  • a librarian is granted a right to issue rights that allow FooU students to play, view, and the like, corresponding content, such as e-books and the like, as long as such usage is tracked by a state variable 1504 , e.g., “www.foou.edu.”
  • rights 1502 and 1503 derived from the site license 1501 include state variables 1505 and 1506 , “www.foou.edu,” which can be updated when corresponding students, Alice and Bob, play the e-book.
  • the state variable can stay unspecified in the usage right.
  • a state variable can be specified using some identification unique to the known recipients and can be included within a derived right.
  • FIG. 16 is used to illustrate employing of a state variable in deriving rights that are shared among a dynamic set of rights recipients, according to the present invention.
  • an offer 1601 specifies that a distributor can issue site licenses to affiliated clubs, allowing 5 members of each club to concurrently view, play, and the like, content, such as an e-book.
  • a corresponding state variable 1607 associated with such a right can be unspecified in the offer 1601 .
  • the corresponding club identities are used to specify state variables 1608 and 1609 in the issued rights.
  • the offers 1602 and 1603 are meta-rights derived from the offer 1601 , with offer being assigned the distinct state variables 1608 and 1609 .
  • Further rights 1604 - 1606 can be derived from the offers 1602 and 1603 to be shared among members of each respective club.
  • the licenses 1604 and 1605 are examples of rights derived from the offer 1602 , and which inherit the state variable 1608 , e.g., “urn:acme:club,” whereas the license 1606 inherits the state variable 1609 , e.g., “urn:foo:club.”
  • FIG. 17 is used to illustrate employing of a state variable for maintaining a state shared by multiple rights, according to the present invention.
  • a same state variable 1703 is associated to both a right to print 1702 and the right to play 1701 , so that the total number of playing, printing, and the like, can be tracked together.
  • FIG. 18 is used to illustrate employing of multiple state variables to represent one state of rights, according to the present invention.
  • the example described with respect to FIG. 18 builds upon the example described with respect to FIG. 16 .
  • a usage right can be tracked by employing multiple state variables 1807 and 1808 in an offer 1801 .
  • the state variable 1808 for example, representing a priority level, can stay unspecified in the corresponding offers 1802 and 1803 (e.g., site licenses).
  • the corresponding state variables 1809 - 1811 for example, used for setting a priority, can be assigned to each member in the corresponding licenses 1804 , 1805 and 1806 .
  • the corresponding right to view, play, and the like can now be dependent on two state variables, effectively restricting 5 simultaneous views, plays, and the like, per priority level.
  • One state variable can represent a collection of states.
  • a unique identification can be used to represent a state variable, and an appropriate mechanism can be employed to map such unique id to a database of multiple variables, where each variable represents a distinct state.
  • state variables can be used to determine entities by which the state variables can be managed. For example, for a local state variable, usage tracking of associated rights thereof can be managed solely by a trusted agent embedded within a rights consumption environment, such as a media player, and the like. In addition, such usage tracking can be conducted by a trusted remote service, such as the common state-of-rights server 1201 . Further, shared global state variables can be made accessible by multiple trusted agents. To avoid privacy issues, security issues, trust issues, rights issues, and the like, associated with accessing content, such as data, and the like, included within a peer rights consumption environment, managing of such shared global state variables can be performed by a remote service, such as the state-of-rights server 1201 .
  • a counter is a common form of state variable usage.
  • state sharing can include counter sharing where a state represents a number of times a right has been exercised, an event has occurred, and the like.
  • Such counter sharing can be manifested in various forms and occur in many contexts, such as: tracking a number of simultaneous uses, tracking a number of sequential uses, sequencing (e.g., a commercial must be viewed before free content can be accessed), a one-time use constraint, a transaction count, a delegation control level, a super-distribution level, dependency on at least one or more services or devices, and the like.
  • state variables can be incarnated in a wide variety of forms.
  • a state variable can be used to track specific time slots within a period of time, such as used by a movie studio to transfer syndication rights to a specific TV station, to transfer syndication rights shared by a group of stations, to transfer syndication rights assigned through a bidding process, and the like.
  • State variables also can be employed, for example, with regional selling or distribution rights, in a statement from a financial clearing house to acknowledge that an appropriate fee has been paid, as a status of whether a commercial has been watched before free content can be accessed, and the like.
  • FIG. 19 is used to illustrate a case where not all rights are associated with states, according to the present invention.
  • an offer 1901 allows a user, Alice, to grant an unlimited play right, view right, and the like, to her PDA. Such a play right need not be associated with any state.
  • derived right 1902 also has an unlimited play right to the content, as well as the right 1903 for her PC.
  • FIG. 20 is used to illustrate a case where not all rights which are associated with states are shared or inherited, according to the present invention.
  • a play right 2003 of a user, Alice, a play right 2002 of a PDA of Alice, and a play right 2003 of a PC of Alice specify a same state variable identification 2004 , a same state need not be shared since each device can track a state thereof locally.
  • such an implementation would allow the PC and the PDA to each play the corresponding content up to 5 times.
  • FIG. 21 illustrates a form of an offer which does not explicitly include meta-rights.
  • an offer 2101 is configured as a site license written in English. Licenses 2102 and 2103 are instances derived from the offer 2101 .
  • variables 2104 and 2105 can be created based on interpretation of the offer 2101 , for example, by the system of FIG. 12 .
  • the preferred embodiment can utilize various devices, such as a personal computers, servers, workstations, PDA's, thin clients, and the like.
  • the client environment can be a handheld device such as a mobile phone or a PDA.
  • Various channels for communication can be used.
  • the various functions can be integrated in one device.
  • the license server function can be accomplished by software within the client environment.
  • the function of the license server or other modules for making offers, selecting rights and granting licenses can be accomplished in the same device.
  • the disclosed functional modules are segregated by function for clarity. However, the various functions can be combined or segregated as hardware and/or software modules in any manner. The various functions can be useful separately or in combination.
  • a license can be stored together with, or separate from, content. Further, the various elements of a license can be stored on separate devices.
  • the values of state variables can be stored in a state variable repository of a system that tracks the current value of state variables.
  • Various links, references, specifications, and the like can be used to associate the elements.

Abstract

A method, system and device for sharing rights adapted to be associated with items, the method and system including generating at least one of usage rights and meta-rights for the items; defining, via the usage rights, a manner of use for the items; and defining, via the meta-rights, a manner of rights transfer for the items. The device including receiving at least one of usage rights and meta-rights for the items; interpreting, via the usage rights, a manner of use for the items; and interpreting, via the meta-rights, a manner of rights transfer for the items. The usage rights or the meta-rights include at least one state variable that is shared by one or more rights.

Description

    RELATED APPLICATION DATA
  • This application is a continuation of U.S. patent application Ser. No. 10/956,070, filed Oct. 4, 2004, now allowed, which is a continuation-in-part of U.S. patent application Ser. No. 10/162,212, filed Jun. 5, 2002, now U.S. Pat. No. 7,774,279, issued Aug. 10, 2010, which is a continuation-in-part of U.S. patent application Ser. No. 09/867,745, filed May 31, 2001, now U.S. Pat. No. 6,754,642, issued Jun. 22, 2004, and which claims benefit from U.S. Provisional Patent Application No. 60/296,113, filed Jun. 7, 2001, U.S. Provisional Patent Application No. 60/331,625, filed Nov. 20, 2001, and U.S. Provisional Patent Application No. 60/331,624, filed Nov. 20, 2001, the entire disclosures of all of which are hereby incorporated by reference herein.
  • FIELD OF THE INVENTION
  • The present invention generally relates to offering and granting of rights and more particularly to a method, system and device for offering and granting of rights using shared state variables.
  • BACKGROUND OF THE INVENTION
  • The digital age has greatly increased concerns about ownership, access, and control of copyrighted information, restricted services and valuable resources. Rapid evolution and wide deployment has occurred for computers, and other electronic devices such as cellular phones, pagers, PDAs, and e-book readers, and these devices are interconnected through communication links including the Internet, intranets and other networks. These interconnected devices are especially conducive to publication of content, offering of services and availability of resources electronically.
  • One of the most important issues impeding the widespread distribution of digital works (i.e. documents or other content in forms readable by computers), via electronic means, and the Internet in particular, is the current lack of ability to enforce the intellectual property rights of content owners during the distribution and use of digital works. Efforts to resolve this problem have been termed “Intellectual Property Rights Management” (“IPRM”), “Digital Property Rights Management” (“DPRM”), “Intellectual Property Management” (“IPM”), “Rights Management” (“RM”), and “Electronic Copyright Management” (“ECM”), collectively referred to as “Digital Rights Management (DRM)” herein. There are a number of issues to be considered in effecting a DRM System. For example, authentication, authorization, accounting, payment and financial clearing, rights specification, rights verification, rights enforcement, and document protection issues should be addressed. U.S. Pat. Nos. 5,530,235, 5,634,012, 5,715,403, 5,638,443, and 5,629,980, the disclosures of which are incorporated herein by reference, disclose DRM systems addressing these issues.
  • Two basic DRM schemes have been employed, secure containers and trusted systems. A “secure container” (or simply an encrypted document) offers a way to keep document contents encrypted until a set of authorization conditions are met and some copyright terms are honored (e.g., payment for use). After the various conditions and terms are verified with the document provider, the document is released to the user in clear form. Commercial products such as Cryptolopes and Digiboxes fall into this category. Clearly, the secure container approach provides a solution to protecting the document during delivery over insecure channels, but does not provide any mechanism to prevent legitimate users from obtaining the clear document and then using and redistributing it in violation of content owners' intellectual property.
  • In the “trusted system” approach, the entire system is responsible for preventing unauthorized use and distribution of the document. Building a trusted system usually entails introducing new hardware such as a secure processor, secure storage and secure rendering devices. This also requires that all software applications that run on trusted systems be certified to be trusted. While building tamper-proof trusted systems is a real challenge to existing technologies, current market trends suggest that open and untrusted systems, such as PC's and workstations using browsers to access the Web, will be the dominant systems used to access digital works. In this sense, existing computing environments such as PC's and workstations equipped with popular operating systems (e.g., Windows, Linux, and UNIX) and rendering applications, such as browsers, are not trusted systems and cannot be made trusted without significantly altering their architectures. Of course, alteration of the architecture defeats a primary purpose of the Web, i.e. flexibility and compatibility.
  • Some DRM systems allow content owners to specify usage rights and conditions, and associate them with content. These usage rights control how the recipient thereof can use the content. Usually after a content distributor or consumer has completed selecting and ordering specific content, the content is delivered either electronically from some content repository or via a conventional distribution channel to the recipient, such as tangible media sent via a common carrier. Corresponding DRM systems used by the recipient, for example the distributor or consumer, will then interpret the rights and conditions associated with the content, and use them to control how the content is distributed and/or used. Examples of usage rights include view, print and extract the content, and distribute, repackage and loan content. Associated conditions may include any term upon which the rights may be contingent such as payment, identification, time period, or the like.
  • U.S. Pat. No. 5,634,012, discloses a system for controlling the distribution of digital documents. Each rendering device has a repository associated therewith. A predetermined set of usage transaction steps define a protocol used by the repositories for enforcing usage rights associated with a document. Usage rights persist with the document content. The usage rights can permit various manners of use such as, viewing only, use once, distribution, and the like. Usage rights can be contingent on payment or other conditions.
  • However, there are limitations associated with the above-mentioned paradigms wherein only usage rights and conditions associated with content are specified by content owners or other grantors of rights. Once purchased by an end user, a consumer, or a distributor, of content along with its associated usage rights and conditions has no means to be legally passed on to a next recipient in a distribution chain. Further the associated usage rights have no provision for specifying rights to derive other rights, i.e. rights to modify, transfer, offer, grant, obtain, transfer, delegate, track, surrender, exchange, transport, exercise, revoke, or the like. Common content distribution models often include a multi-tier distribution and usage chain. Known DRM systems do not facilitate the ability to prescribe rights and conditions for all participants along a content distribution and usage chain. Therefore, it is difficult for a content owner to commercially exploit content unless the owner has a relationship with each party in the distribution chain.
  • SUMMARY OF THE INVENTION
  • Exemplary aspects of the present invention include a method, system and device for sharing rights adapted to be associated with items, the method and system including generating at least one of usage rights and meta-rights for the items; defining, via the usage rights, a manner of use for the items; and defining, via the meta-rights, a manner of rights transfer for the items. The device including receiving at least one of usage rights and meta-rights for the items; interpreting, via the usage rights, a manner of use for the items; and interpreting, via the meta-rights, a manner of rights transfer for the items. The usage rights or the meta-rights include at least one state variable that is shared by one or more rights.
  • Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, simply by illustrating a number of exemplary embodiments and implementations, including the best mode contemplated for carrying out the present invention. The present invention is also capable of other and different embodiments, and its several details can be modified in various respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Exemplary embodiments of this invention will be described in detail, with reference to the attached drawings in which:
  • FIG. 1 is a schematic diagram of a three-tier model for content distribution;
  • FIG. 2 is a schematic diagram illustrating rights offering and granting processes in the model of FIG. 1;
  • FIG. 3( a) is a schematic diagram of a simple supplier-consumer push model for rights generating, issuing and exercising;
  • FIG. 3( b) is a schematic diagram of a simple supplier-consumer pull model for rights generating, issuing and exercising;
  • FIG. 4 is a block diagram of a rights offering-granting architecture in accordance with the preferred embodiment;
  • FIGS. 5 a and 5 b are workflow diagrams for examples of offering and granting rights between a rights supplier and a rights consumer with a push and pull model respectively;
  • FIG. 6 is a flow chart of a rights offer generation process in accordance with the preferred embodiment;
  • FIG. 7 is a flow chart of a rights offer consideration process in accordance with the preferred embodiment;
  • FIG. 8 is a flow chart of a rights offer customization process in accordance with the preferred embodiment;
  • FIG. 9 is block diagram of a DRM system that may be utilized in connection with the preferred embodiment;
  • FIG. 10 is a block diagram of an exemplary structure of a license containing usage rights and meta-rights of the preferred embodiment;
  • FIG. 11 is a schematic illustration of a rights label of the preferred embodiment;
  • FIG. 12 illustrates an exemplary system including a state-of-rights server;
  • FIG. 13 illustrates employing of a state variable in deriving exclusive usage rights;
  • FIG. 14 illustrates employing of a state variable in deriving inherited usage rights;
  • FIG. 15 illustrates employing of a state variable in deriving rights that are shared among a known set of rights recipients;
  • FIG. 16 illustrates employing of a state variable in deriving rights that are shared among a dynamic set of rights recipients;
  • FIG. 17 illustrates employing of a state variable in maintaining a state shared by multiple rights;
  • FIG. 18 illustrates employing of multiple state variables to represent one state of rights;
  • FIG. 19 illustrates a case where not all rights are associated with states;
  • FIG. 20 illustrates a case where not all rights which are associated with states are shared or inherited; and
  • FIG. 21 illustrates a case of rights sharing based on an offer which does not explicitly include meta-rights.
  • DETAILED DESCRIPTION
  • Prior to providing detailed description of the apparatus and method for offering and granting rights, a description of a DRM system that can be utilized to specify and enforce usage rights and meta-rights for specific content, services, or other items is first described below.
  • FIG. 9 illustrates DRM System 10 that includes a user activation component, in the form of activation server 20, that issues public and private key pairs, or other identification mechanisms, to content users in a protected fashion, as is well known. Typically, when a user uses DRM system 10 for the first time, the user installs software that works with, or includes, a rendering application for a particular content format. The software is installed in client environment 30, a computer associated with the content recipient, for example. The software is part of DRM 10 system and is used to enforce usage rights for protected content. During the activation process, some information is exchanged between activation server 20 and client environment 30. Client component 60 preferably is tamper resistant and contains the set of public and private keys issued by activation server 20 as well as other components, such as rendering components for example.
  • Rights label 40 is associated with content 42 and specifies usage rights and meta-rights that are available to a recipient, i.e. a consumer of rights, when corresponding conditions are satisfied. License Server 50 manages the encryption keys and issues licenses 52 for protected content 42. Licenses 52 embody the actual granting of rights, including usage rights and meta-rights, to an end user. For example, rights offer 40 may permit a user to view content for a fee of five dollars and print content for a fee of ten dollars, or it may permit a user to offer rights to another user, for example, by utilizing the concept of meta-rights described below. License 52 can be issued for the view right when the five dollar fee has been paid. Client component 60 interprets and enforces the rights, including usage rights and meta-rights, that have been specified in the license. Rights label 40 and license 52 are described in detail below.
  • FIG. 11 illustrates rights label 40 in accordance with the preferred embodiment. Rights label 40 includes plural rights options 44. Each rights option 44 includes usage rights 44 a, conditions 44 b, and content specification 44 c. Content specification 44 c can include any mechanism for referencing, calling, locating, or otherwise specifying content 42 associated with rights offer 44.
  • As shown in FIG. 10, license 52 includes license 52 a, grant 52 b, and digital signature 52 c. Grant 52 b includes granted usage rights and/or meta-rights selected from label. The structure of the grant also includes one or more principals, to whom the specified usage rights and/or meta-rights are granted, a list of conditions, and state variables required to enforce the license. Like usage rights, access and exercise of the granted meta-rights are controlled by the condition list and state variables as described below.
  • Clear (unprotected) content can be prepared with document preparation application 72 installed on computer 70 associated with a content publisher, a content distributor, a content service provider, or any other party. Preparation of content consists of specifying the usage rights, meta-rights, and conditions under which content 42 can be used and distributed, associating rights label 40 with content 42 and protecting content 42 with some crypto algorithm. A rights language such as XrML can be used to specify the rights and conditions. However, the usage rights and meta-rights can be specified in any manner. Also, the rights can be in the form of a pre-defined specification or template that is merely associated with the content. Accordingly, the process of specifying rights refers to any process for associating rights with content. Rights label 40 associated with content 42 and the encryption key used to encrypt the content can be transmitted to license server 50.
  • Rights can specify transfer rights, such as distribution rights, and can permit granting of rights to others or the derivation of rights. Such rights are referred to as “meta-rights”. Meta-rights are the rights that one has to manipulate, modify, or otherwise derive other meta-rights or usage rights. Meta-rights can be thought of as usage rights to usage rights. Meta-rights can include rights to offer, grant, obtain, transfer, delegate, track, surrender, exchange, and revoke usage rights to/from others. Meta-rights can include the rights to modify any of the conditions associated with other rights. For example, a meta-right may be the right to extend or reduce the scope of a particular right. A meta-right may also be the right to extend or reduce the validation period of a right.
  • Often, conditions must be satisfied in order to exercise the manner of use in a specified right. For, example a condition may be the payment of a fee, submission of personal data, or any other requirement desired before permitting exercise of a manner of use. Conditions can also be “access conditions” for example, access conditions can apply to a particular group of users, say students in a university, or members of a book club. In other words, the condition is that the user is a particular person or member of a particular group. Rights and conditions can exist as separate entities or can be combined.
  • State variables track potentially dynamic states conditions. State variables are variables having values that represent status of an item, usage rights, license or other dynamic conditions. State variables can be tracked, by clearinghouse 90 license or server 30 another device, based on identification mechanisms in license 52. Further, the value of state variables can be used in a condition. For example, a usage right can be the right to print content 42 three times. Each time the usage right is exercised, the value of the state variable “number of prints” is incremented. In this example, when the value of the state variable is three, the condition is not longer satisfied and content 42 cannot be printed. Another example of a state variable is time. A condition of license 52 may require that content 42 is printed within thirty days. A state variable can be used to track the expiration of thirty days. Further, the state of a right can be tracked as a collection of state variables. The collection of the change is the state of a usage right represents the usage history of that right.
  • A typical workflow for DRM system 10 is described below. A recipient, such as a user, operating within client environment 30 is activated for receiving content by activation server 20. This results in a public-private key pair (and some user/machine specific information) being downloaded to client environment 30 in the form of client software component 60 in a known manner. This activation process can be accomplished at any time prior to the issuing of a license.
  • When a user wishes to use protected content 42, the user makes a request for the content 42. For example, a user might browse a Web site running on Web server 80 associated with a grantor of rights such as a content distributor, using a browser installed in client environment 30, and attempt to download protected content 42. During this process, the user may go through a series of steps possibly including a fee transaction (as in the sale of content) or other transactions (such as collection of information). When the appropriate conditions and other prerequisites, such as the collection of a fee and verification that the user has been activated, are satisfied, Web server 80 contacts license server 50 through a secure communications channel, such as a channel using a Secure Sockets Layer (SSL). License server 50 then generates license 52 for the content and Web server 80 causes both protected content 42 and license 52 to be downloaded. License 52 can be downloaded from license server 50 or an associated device. Content 42 can be downloaded from computer 70 associated with a publisher, distributor, or other party.
  • Client component 60 in client environment 30 will then proceed to interpret license 52 and allow use of content 42 based on the rights and conditions specified in license 52. The interpretation and enforcement of usage rights are well known generally. The steps above may take place sequentially or approximately simultaneously or in various order.
  • DRM system 10 addresses security aspects of protecting content 42. In particular, DRM system 10 may authenticate license 52 that has been issued by license server 50. One way to accomplish such authentication is for application 60 to determine if the licenses can be trusted. In other words, application 60 has the capability to verify and validate the cryptographic signature of digital signature 52 c, or other identifying characteristic of the license. During the activation step described above, both client environment 30 and license server 50 receive a set of keys in a tamper-resistant software “package” that also includes other components, such as the necessary components for activated client environment 30 to verify signature 52 of license 52 in a known manner. Of course, the example above is merely one way to effect a DRM system. For example, the license and content can be distributed from different entities. Also, rights offer 40 can be associated with content by a party other than the party preparing the content. Also, clearinghouse 90 can be used to process payment transactions and verify payment prior to issuing a license.
  • For any set of rights, there are two kinds of entities involved, the “supplier” and the “consumer”. The function of the supplier is to offer, and possibly grant, the rights, and the function of the consumer is to select, and possibly exercise the rights. Both the supplier and consumer may actually represent two or more entities. In general, multiple entities may collectively make an offer and grant rights to multiple entities. The supplier and consumer represent any two entities in the content value chain that have a direct relationship with each other regarding the granting of rights. At the beginning of the value chain, the supplier and consumer may be author and publisher. Going down along the value chain, the supplier and consumer may be a publisher and another publisher (for content aggregation), a publisher and distributor (for content distribution), a distributor and another distributor (for multi-tier content distribution), a distributor and a retailer (for content retailing), a retailer and a consumer (for content consumption), and a consumer and another consumer (for content supper-distribution or personal lending).
  • An “offer of rights” or “rights offer” expresses how a consumer (e.g. a content distributor or user) can acquire a particular instance of content together with its associated usage rights and/or meta-rights. An offer may or may not contain financial terms. An offer is an expression of mere willingness to commerce negotiation and also an expression of willingness to grant on terms stated. An offer may be expressed in the form of a rights label. A “consideration of rights” is a process as part of the rights granting in which the rights consumer has examined the rights being offered and possibly bargained them and associated terms and conditions. A “choice of rights” is a selection of rights and their associated terms and conditions from a rights offer. It indicates the intent of the consumer to accept these rights and the corresponding terms and conditions. For example, selection can comprise selecting one option 44 from label 40. “Customization of rights” is a process as part of the rights granting in which the rights supplier assembles rights and terms and conditions based on a choice of the rights consumer. The output of this process can be a draft license to be accepted by the rights consumer. A “license of rights” is an expression of rights and possibly conditions accepted and agreed upon by the rights supplier and consumer. It is the output of the rights offering and granting process. A license is a grant to exercise the rights that govern the usage (possibly including further distribution) of content or other items.
  • As described above, a rights label, such as rights label 40, may contain a number of options 44 allowing the consumer to make a selection and conduct negotiation (if permitted), while license 52 contains rights the consumer has selected and accepted. Note that the accepted rights may include a right to present offers to others or make selections of offers.
  • An example of a distribution chain model is illustrated in FIG. 1. The distribution chain includes a content provider 100, distributor 110, and end user 120. Of course content may be prepared in the manner described above. It is assumed that the content has already been prepared in the model of FIG. 1. FIG. 1 is directed to the transfer of content and shows that, in this example, provider 100 may publish content to distributor 110 or receive content for reuse from distributor 110. Distributor 110 may in turn distribute content to user 120 or receive returned content form user 120. User 100 can use content. To further illustrate the potential complexities of multi-tier distribution chains provider 100 can aggregate content from others, distributor 110, can receive content from other distributors for redistribution, and user 120 can share content with the other users. It is clear that there are plural stages in the content life cycle and plural relationships between the various parties. A precise and consistent specification of rights at the different stages of the life cycle and relationships is important and crucial to persistent protection of content in multi-tier distribution and usage.
  • FIG. 2 illustrates the flow of rights in the same model, including rights generating, aggregating, issuing, relinquishing, driving, granting, surrendering, delegating and exercising. The model of FIG. 2 includes the same entities, provider 100, distributor 110, and user 120. It can be seen that, with respect to the flow of rights, each party can grant and accept rights. User 120 can grant and accept rights from other users, a process called “delegation”, in this example.
  • The model of FIG. 2 covers many specific content publishing, distribution and use relationships. Other models can be derived from on this model by a different consolidation or segregation of the parties. For example, every provider can be a distributor. This is “direct publishing”, which allows individual authors to distribute/sell their content without any intermediate publisher. Further, every consumer can be a potential distributor. This allows consumers to pass content to each other. This includes supper-distribution, gifting, and personal lending. In a “Web community” and everyone is able to publish, distribute and consume content. “Content aggregation” allows publishers to compose content from other publishers into composite works. Site license and enterprise use allows sharing content among consumers.
  • In general, all the rights relationships shown in FIG. 2 can be captured by two generic supplier-consumer models, as shown in FIGS. 3( a) and 3(b). FIG. 3( a) shows a “push” model and FIG. 3( b) shows a “pull” model. In the push model shown in FIG. 3( a), rights supplier 200 initiates the rights offering and granting process by generating an offer and granting the rights to the rights consumer 210. In the pull model shown in FIG. 3( b), rights consumer 210 initiates the process by requesting an offer and accepting the rights from the rights supplier 200.
  • An architecture of the preferred embodiment for rights offering and granting is shown in FIG. 4. Architecture 400 can be implemented as a combination of computer hardware and software and includes rights supplier component 402, rights consumer component 438 and communication channel 422 linking these two components. For example, communication channel 42 can be Internet, a direct computer to computer connection, a LAN, a wireless connection or the like. Supplier component 402 is associated with the supplier, i.e. the entity making rights available to a consumer who is the entity going to exercise, i.e., consume the rights. The supplier could be the content owner or provider, or could be a distributor or any “middle-man,” such as a retailer or operator of a web site. Consumer component 438 is associated with the consumer who could be the ultimate user (i.e., content consumer) or a “middle-man,” such as a retailer, whole-seller, or reseller. Keep in mind that the consumer consumes rights and does not necessarily use (i.e. consume) the content. Both supplier component 402 and consumer component 438 can embody any type of hardware devices, and or software modules, such as a personal computer, a handheld computer, a mobile phone a server, a network, or any combination of the same. Supplier component 402 generates rights label 40 as offers, presents draft licenses and grants license 52 to the consumer. Consumer component 438 issues requests, select choices of options 44 from rights labels 40, generates counter offers, and accepts licenses 52. Supplier component 402 and consumer component 438 can be embodied in the same device(s) and communication channel 422 can be an internal channel.
  • Supplier component 402 contains user interface module 404, communication interface module 420 identity module 406 repository 412 for supplier's rights (e.g., in the form of issued licenses) and database 414 for management related information. User interface 404 accomplishes presentation to the user of the component functions and acceptance of user interactions in a known manner. Communication interface 422 provides the proper formatting and protocols for messages between supplier component 402 and consumer component 438. Identity module 406 ensures that the identity of supplier component 402 can be authenticated by consumer component 438 and may contain authentication information like a password, cryptographic keys or biometric information of the user of supplier component 402. Rights repository 412 stores rights granted to the user of supplier component 402 and may include functions for indexing, searching and updating the rights stored within. Management database 414 is used to archive information generated during the rights offering and granting processes. Such information includes information related to initial offers, consumer choices, possible counter-offers, agreements and final licenses.
  • Consumer component 438 includes user interface module 428, communication interface module 424, identity module 426, repository 434 for consumer's rights (e.g., in the form of issued licenses), and database 436 for management related information. User interface 424 deals handles presentation to the user of the component and acceptance of user interactions. Communication interface 422 provides the proper formatting and protocols for rights offering and granting messages between supplier component 402 and consumer component 438. Identity module 426 ensures that the identity of the consumer component 438 can be authenticated by supplier component 402 and may contain authentication information like a password, cryptographic keys or biometric information of the user. Rights repository 434 stores rights granted to the user of consumer component 438 and may include functions for indexing, searching and updating the rights stored within. Management database 436 is used to archive information generated during the rights offering and granting process. The information includes that related to offers 44, consumer choices, possible counter-offers, agreements and licenses 52. Note that database 436 can store information that is the same as or different from database 414 because the parties may interact with other parties and thus have different archived information.
  • Supplier component 402 also includes offer generator module 408 for generating offers, rights composer module 410 for composing licenses, offer templates module 418 for providing templates for generating offers based on previous transactions and common formality of offers, and consumer profiles module 416 for customizing and granting rights based on past consumer characteristics and relationships.
  • Consumer component 438 also includes offer analyzer module 430 for understanding rights and their terms and conditions presented within offers, a choice maker module 432 for selecting favorable options specified in offers, a supplier preference module 438 for describing any preferred suppliers based on past and existing supplier characteristics and relationships, and choice patterns module 440 for providing patterns and interests in selection options in offers. For example, the choice pattern module 440 may include a list of preferred suppliers or a list of lowest prices for the item of interest to the consumer. Offer analyzer module 430 and choice maker module 432, respectively, may be combined into one module.
  • The process of offering and granting rights within architecture 400 is based on protocols followed by supplier component 402 and consumer component 438. These protocols generally consist of an offer and acceptance of that offer. Specifically, the protocols include an offering of rights by one party to another and acceptance of that offer by the person to whom it is made. An offer, once made, may be styled so that it may revoked before acceptance or the offeror could styled it so that it cannot be revoked at all or only under certain circumstances definable by the offeror. An offer can also expire in various way, for example if a deadline for acceptance passes. If there is no specified deadline, then the offer could expire in a predetermined reasonable time, depending on the subject matter of the offer. For periodically available content such as magazines, journals, and even newspapers, a reasonable time could be accord to the period of the content publication, for example. For dynamically generated or provided content such as streaming content, a reasonable time could be any time before the availability of the content. The rights supplier can dictate other terms of the acceptance, to which the rights consumer is bound. For example, the offer may require acceptance in sending back in a certain form via an email or through a certain web page interface.
  • FIG. 5( a) illustrates the workflow of protocol 500 of a push model for rights granting. Supplier component 402 generates an offer of rights in the form of rights label 40 for example, with possibly many options 44, and sends it to consumer component 438 (510). Consumer component 438 considers the offer and its possible options, and responds to supplier component 402 with a choice of any of the optional rights offer 44 (512). Supplier component 402 customizes rights according to the consumer's response, and issues the rights the user of consumer component 432 (514) in the form of a draft license.
  • Consumer component 438 then accepts the draft license if it corresponds to the choice made and is otherwise acceptable (516). Upon acceptance, supplier component 402 generates license 52 and transmits license 52 to consumer component (518). Keep in mind that grant 52 b of license 52 can include usage rights and/or meta-rights. Therefore license 52 can permit the user of consumer component 438 to grant rights to others in a similar fashion. However, the derivable rights are controlled by upstream parties through the use of meta-rights. Additionally, the protocol can include steps where supplier component 402 requests to make payment through a credit card of the user of consumer component 438, and the user component 402 provides the information and authorizes the charge. Both supplier component 402 and consumer component 438 can generate status reports on success or failure of the process. Further, parties can authenticate each other during the process and maintain authentication through the process.
  • FIG. 5( b) shows a protocol of pull model for rights granting. First, consumer component 438 sends a request to supplier component 402 to indicate an interest in obtaining certain rights in content (520). Supplier component 402 then responds with an offer, in the form of label 40 having plural offer options 44, covering the rights requested by consumer component 438, and sends the offer to consumer component 438 (522).
  • Consumer component 438 then considers the offer and its options, and responds to supplier component 402 with a choice of one of the offer options (524). Supplier component 402 customizes rights according to the response, and grant the rights to the consumer in the form of a draft license (526). Consumer component 438 then accepts the draft license (528) and supplier component 402 issues license 52 granting rights to consumer component 438 (530). Once again the rights can include meta-rights.
  • FIG. 6 illustrates the offer generation process 600 performed by offer generator module 408 in supplier component 402. In offer generation process 600, available rights are first collected in block 602. Rights may be available from a previous supplier by being derived from meta-rights granted to the supplier or may be originally created rights. In step 604 it is determined whether supplier has a right to make an offer to the consumer. For example, if the consumer is known to be a minor and the content is restricted to an adult consumer or if the consumer is on a list of those prohibited from receiving content, the supplier may not make an offer. In such case, the offer generation process terminates in step 606. If the supplier has the right to make an offer, the process then determines all the rights that can be offered to the consumer in step 608 by parsing the rights collected in step 602. Next, in step 610, the process determines whether the consumer has requested any specific rights. If a request has been received, the process further filters the determined rights that can be offered, taking the received consumer requested rights into consideration and comparing them to the available rights. Then, the process determines whether an offer template needs to be applied in steps 614.
  • For example, the consumer might be offered standard rights included in the template, such as printing right, archiving right, etc. of the content. If an offer template is available and needed, the offer template is then applied in steps 616. In steps 618, human intervention may be provided to further make adjustments to the offer template or to any of the rights that are available for offering thus far in the process. Next, restrictions can be applied, through conditions and/or state variables. For example, a time restriction may be place on certain rights in step 620. Finally, a digital signature or other authentication is provided with the collection of rights to be offered in step 622 and an authenticated offer, in the form of rights label 40 is made in step 624 and presented to consumer component 438 in step 624.
  • FIG. 8 illustrates rights customization process 800 which is performed by rights composer module 410 in supplier component 402. Initially, consumer's choices are received in step 802. Choices are rights and conditions of an option 44 selected label 40 of step 624 (FIG. 6). The process then determines if supplier component 402 has the right to grant rights to consumer component 438 in step 804. For example, if the consumer fails to meet a certain requirement, such as minimum age or proof of residence in a locale where content may be licensed, for example, granting a license may not be proper, and the rights customization process 800 terminates in step 806. Otherwise, consumer selected choices are analyzed in step 808 to ascertain if they are an discernible by supplier component 402. For example, the choices can be parsed to see if they are understandable.
  • Next, the process determines if consumer information is available in step 810. For example, consumer profiles may be stored in database 414 (FIG. 4). If available, the consumer information is taken into consideration in step 812 for further analysis of consumer choices. In step 812, dynamic information can also considered as described below. For example, the profile may include a trust rating or address of the consumer that renders it desirable of undesirable to provide certain rights. The process then determines if the choices are reasonable in step 814. This determination may be carried out, for example, computationally or with human intervention. If the customer's choices are deemed unreasonable, re-negotiation of the customer's choices is then performed in block 816. In this re-negotiation process, the customer is presented with a new proposed offer based on the previously analyzed choices, the customer is given an opportunity to submit new choices offered, and the right customization process 800 begins again in step 802. Otherwise, a license including the selected rights is created in step 818.
  • After a license is created, if consumer acceptance is necessary (step 820), it is presented to the consumer for review in step 822. If the consumer does not agree with the terms in the license in step 824, re-negotiation is then initiated in step 816, which re-starts the rights customization process 800 again in step 802. In step 820, if a review by the consumer is not required, then the license is authenticated in step 826 to create a completed license 52 in step 828 which is to be issued and associated with content 42.
  • FIG. 7 illustrates offer consideration process 700 which is performed by offer analyzer module 430 and choice maker module 432 of consumer component 438. Available offers are first collected in step 702. In step 704, process 700 determines whether it has a right to accept offers from the supplier. For example, if the consumer certain restrictions on the purchase of content, such as an age restriction or a restriction against accepting content from outside an enterprise, the consumer may not accept an offer. In such a case, the offer consideration process terminates in step 706. If the consumer has the right to accept offers from the supplier, the offers are then analyzed in step 708 to ascertain if they are discernible. If it is determined that supplier preferences are available in step 710, the offers are filtered in step 712 based on the preferences. For example, the consumer may trust a specific supplier, or otherwise prefer transactions with that supplier, more that other suppliers. Next, step 714 determines if consumer preferences are available and, if so, they are applied in step 716 to the offers. Once all the offers are analyzed, by applying the logic of steps 708-714 and any other desired logic, the consumer then selects options in block 718 and specifies contingencies in block 720. The selection of options can be done automatically. If human intervention is desired, the customer can intervene and further specify additional choices or conditions desired. Any preferences, rules, or other logic can be used to analyze offers.
  • Overall, as can be seen in the description of FIGS. 6, 7, and 8 above, the consumer sends a request, and then a license is constructed. Either the supplier or the consumer could draft the content of the license, but in the example above the supplier does so. The request is a subset of an offer and the offer has one or more options. The supplier makes the offer available to the consumer sending the request (and to other consumers if that is the desire), and the consumer (including other consumers, if applicable) makes choices. Then, the supplier analyzes the choices, and constructs the license (i.e. a grant of rights). Note that the request can also be rejected, or a counter proposal could be made and the same process could then repeat for the counter proposal.
  • Also, when the supplier analyzes the request, the analysis may be done automatically, or with human intervention. When the consumer considers the offer, the choice or acceptance may be done automatically, or with human intervention. Either the offer or a license, or both, may be generated based on the dynamic information, the consumer's information, and the consumer's request, such as described above.
  • The dynamic information may include many kinds of information including information related to pricing, status of the network, the traffic of a web site at each moment of time, discounts given, coupons given, the habits of the consumer, how many times the content has been used, for how long the content was used, where it was used, or the like. The dynamic information can be tracked as state variables and the values of the state variables can be checked and updated as necessary.
  • Dynamic information is information capable of being (although, it need not actually be) changed or created by or by reference to a non-static element. For example, the dynamic information can be obtained based on a formula, database, curve, predetermined table, percentage of a value, a function, reference to other data, such as the prime rate of interest or the change in a stock market index, and/or by a human intervention of the user or distributor, and/or consumer's input.
  • The consumer's information may include information such as the age of the consumer, the credit history of the consumer, the credit limit of the consumer, income of the consumer, what kind of rights or licenses obtained, the password of the consumer, the key assigned to the consumer, club membership for access or discount, the class of the consumer based on a predetermined criteria, or any other data, identification characteristics and information. The supplier's information may include some or all of the subjects of information as the consumer's information, and may also include, for example, available options or variations, suppliers, shipping information, and other information.
  • The system and processes disclosed in this invention support multi-tier and super distributions of content. The following is a use case that shows how this can be modeled and supported. It illustrates the process of offering and granting rights by showing the process of transforming offered rights to a rights supplier (the content distributor in this case) to granted rights to a rights consumer (the end user in this case). It specifically shows how an offer is generated from an existing license, how this offer is considered with a choice, and how a final license is issued. Meta-rights provide a mechanism for permitting the transfer of rights from one party to the next party in a content distribution chain.
  • Suppose that a content provider P of some content C wants to specify that a distributor D may sell, to any end user within the region of the United States (US), the “play” right at a flat rate of $1 and the “print” right at a cost of $4 per copy (both are paid by D to P). The provider also allows the content distributor to add its own conditions to the “play” and “print” rights it issues to end users.
  • A license from the content provider to the distributor may resemble the following using the XrML rights language.
  • <license>
     <grant>
      <forAll varName=“user”/>
      <forAll varName=“distributorConditionForPlay”/>
      <principal id=“distributor”/>
      <issue/>
      <grant>
       <principal varRef=”user”/>
       <play/>
       <digitalResource licensePartId=“book”/>
       <allCondition>
        <region regionCode=“US”/>
        <condition varRef=“distributorConditionForPlay”/>
       </allCondition>
      </grant>
      <fee>
       <flat currencycode=“USD”>1</flat>
       <to licensePartid=“provider”/>
      </fee>
     </grant>
     <grant>
      <forAll varName=“user”/>
      <forAll varName=“distributorConditionForPrint”/>
      <principal id=“distributor”/>
      <issue/>
      <grant>
       <principal varRef=“user”/>
       <play/>
       <digitalResource licensePartId=“book”/>
       <allCondition>
        <region regionCode=“US”/>
        <condition varRef=“distributorConditionForPrint”/>
       </allCondition>
      </grant>
      <fee>
       <perUse regionCode=“USD”>5</perUse>
       <to licensePartId=“provider”/>
      </fee>
     </grant>
     <issuer id=“provider”/>
    </license>
  • The distributor may make an offer to the end user based on the rights it has as expressed in the license above. Note that usage rights and conditions of each option are set forth as XML elements between <grant> tags. In the following offer, note that the distributor adds a fee condition for getting the “play” right, charging the end user $2 ($1 more than it pays to the provider), and another fee condition for the “print” right, charging the end user $6 per print copy ($1 more than it pays to the provider). The distributor also limits the offer to an acceptance time period (up to Dec. 31, 2002). Meta rights granted to the distributor permit the distributor to modify the grant in the license, as described above, and make the offer.
  • <offer>
     <grant>
      <forAll varName=“user”/>
      <principal varRef=“user”/>
      <obtain/>
      <grant>
       <principal varRef=“user”/>
       <play/>
       <digitalResource licensePartId=“book”/>
       <region regionCode=“US”/>
      </grant>
       <fee>
        <flat currencyCode=“USD”>2</flat>
        <to licensePartId=“distributor”/>
       </fee>
     </grant>
     <grant>
      <forAll varName=“user”/>
      <principal varRef=“user”/>
      <obtain/>
      <grant>
       <principal varRef=“user”/>
       <print/>
       <digitalResource licensePartId=“book”/>
       <allCondition>
        <region regionCode=“US”/>
        <fee>
         <perUse currencyCode=“USD”>6</perUse>
         <to licensePartId=“distributor”/>
        </fee>
       </allCondition>
      </grant>
     </grant>
     <issuer id=“distributor”>
      <validityInterval>
       <until>2002:12:31</until>
      </validityInterval>
     </issuer>
    </offer>
  • When the offer is presented to an end user, the end user may choose to get only the right to “play” for the flat fee of $2 and responds to the distributor with a choice set forth as an XML element between <choice> tags as follows.
  • <choice>
     <grant>
      <principal id=“anEndUser”/>
      <obtain/>
      <grant>
       <principal id=“anEndUser”/>
       <play/>
       <digitalResource licensePartId=“book”/>
       <region regionCode=“US”/>
      </grant>
       <fee>
        <flat currencyCode=“USD”>2</flat>
        <to licensePartId=“distributor”/>
       </fee>
     </grant>
     <issuer id=“anEndUser”/>
      <validityInterval>
       <until>2002:12:31</until>
      </validityInterval>
     </issuer>
    </choice>
  • Note that the request can also be rejected. Note also that a response can also be constructed as a counter offer for rights not originally offered by the distributor. When the distributor receives the choice from the end user, it then issues a license to the user as shown below.
  • <license>
     <grant>
      <principal id=“anEndUser”/>
      <obtain/>
      <grant>
       <principal id=“anEndUser”/>
       <play/>
       <digitalResource licensePartId=“book”/>
       <region regionCode=“US”/>
      </grant>
       <fee>
        <flat currencyCode=“USD”>2</flat>
        <to licensePartId=“distributor”/>
       </fee>
     </grant>
     <issuer id=“distributor”>
      <issuedTime>
       2002:05:06
      </issuedTime>
     </issuer>
    </license>
  • Note that in all the XML documents above, the issuers may choose to digitally sign the documents using some digital signature algorithms. The recipients of these documents have options to verify the validity of these documents by checking the validity of the attached digital signatures. Access to the various documents, and elements thereof, can be controlled using known techniques.
  • In some situations offering and granting result in a license with a fresh state for content usage. As one starts to exercise the rights, derived rights, obtained as a result of meta-rights, may inherit and/or share the state variable values associated with the rights. For example, when one is granted with the right to print 5 times and make 4 copies of some document, all new copies may have the same set of rights but share the state (or remaining rights) with the original. After the original has been printed 2 times and a new copy was then made, the copy and original can all together print 3 times and make 2 more new copies.
  • Thus, the exemplary embodiments include a method for transferring usage rights adapted to be associated with items. The method includes generating, by a supplier, at least one first offer containing usage rights and meta-rights for the item, the usage rights defining a manner of use for the items, the meta-rights specifying rights to derive usage rights or other meta-rights, presenting the offer to a first consumer, receiving a selection from the first consumer indicating desired usage rights and meta-rights, and generating a first license granting the desired usage rights and meta-rights to the first consumer. The exemplary embodiments further include a system for transferring usage rights adapted to be associated with an item to be licensed in multi-tier channels of distribution with downstream rights and conditions assigned at least one level. The system includes a supplier component, comprising a supplier user interface module, an offer generator module for generating an offer containing at least usage rights and of meta-rights, a rights composer module for composing a draft license, and a repository for supplier's rights, a supplier management database. The system further includes a consumer component comprising a consumer user interface module, an offer-consideration module configured to analyze the offers generated by the supplier component and select offers based on the analysis, and a repository for consumer's rights, a consumer management database. The exemplary embodiments still further include a method for generating a license to digital content to be used within a system for at least one of managing use and distribution of the digital content. The method includes presenting a consumer with an offer including meta-rights, receiving a selection by the consumer of at least one meta-right in the offer, generating a license based on the selection, wherein the license permits the consumer to exercise the at least one meta-right and permits the consumer to offer at least one derived right derived from the at least one meta-right and generate a license including the at least one derived right.
  • FIG. 12 illustrates an exemplary system including a common state-of-rights server, according to the present invention. In FIG. 12, the exemplary system can include a common state-of-rights server of the system 1201, including a state-of-rights manager 1209, and one or more state-of-rights repositories 1214, and one or more license servers 1200, including a meta-rights manager 1210, a usage rights manager 1212, an authorization component 1208, a condition validator 1206, a state-of-rights manager 1204, one or more state-of-rights repositories 1216, a license manager 1203, a license interpreter 1202, and one or more license repositories 1218.
  • The common state-of-rights server 1201 can be configured as a remote server connected with one or more of the license servers 1200. The common state-of-rights server 1201 provides comparable services as the state-of-rights manager 1204 in the license servers 1200 via the state-of-rights manager 1209. The services provided by the state-of-rights server 1201 are accessible and states that the server 1201 manages can be shared by one or more rights suppliers and rights consumers (not shown).
  • The state-of-rights server 1201 can be configured as a remote server connected with one or more of the license servers 1200 via one or more communication links 1220, and the like. The services provided by the state-of-rights server 1201 also can be integrated within one or more of the license server 1200 and such services can be accessible by other rights suppliers, rights consumers, and the like.
  • The license manager 1203 derives new rights based on an offer, which can include any suitable machine-readable expression, and optionally including meta-rights. While deriving rights, the license manager 1203 can create new state variables to be associated with derived rights. The creation of state variables and their scopes can be prescribed in the offer or by some other function in the system. The state variables can be created in one or more instances, for example, prior to rights derivation, during rights derivation, upon fulfillment of conditions, during a first exercise of rights associated with the state variables, and the like. The state variables can be designated exclusively for a specific rights consumer, can be shared among rights consumers, and can be shared among rights consumers and other entities, such as rights suppliers, and the like. The license manager 1203 can interact with the state-of-rights manager 1204 to associate new state variables with physical addresses in one or more of the state-of-rights repositories 1216. The state-of-rights manager 1204 can access the one or more state-of-rights repositories 1216 and can interact with the state-of-rights server 1201 to access shared state variables from one or more of the state-of-rights repositories 1214.
  • Designated state variables can be used to support a license that grants a recipient of the license a right to print content 5 times, shared state variables can be used to support a site license that grants a group of authorized users a right to print content an aggregated total of 100 times, and the like. A designated state variable can be updated when the corresponding right is exercised, whereas a shared state variable can be updated when an authorized user exercises the corresponding right. In other words, a shared state variable can include a data variable that is updated in response to actions by a plurality of users and which is globally applied to each of the users.
  • There are multiple ways to specify the scope of state variables, each of which can affect whether the derivative state variables can be shared, how the derivative state variables can be shared, and the like. For example, a state variable can be local, and solely confined to a recipient or can be global, and shared by a predetermined group of recipients. A global state variable can be shared by a group of recipients not determined when derived rights are issued, but to be specified later, perhaps based on certain rules defined in the license or based on other means. A global state variable can be shared between one or more rights suppliers, predetermined recipients, un-specified recipients, and the like. Advantageously, depending on the sharing employed with a given a business model and the rights granted in the meta-rights, state variables can be created at different stages of the value chain.
  • A set of non-exhaustive exemplary usages of state variables will now be described. For example, a state variable can be unspecified in meta-rights, which means the identifier and value of the state variable are yet to be determined by the meta-rights manager module 1210 and included in the derived right. If a distinct state variable is assigned to each derived right, the scope of the state variable in the derived right is typically exclusive to the recipient.
  • FIG. 13 is used to illustrate employing of a state variable in deriving exclusive usage rights, according to the present invention. In FIG. 13, rights 1302 and 1303 derived from an offer 1301 are exclusive to each respective consumer. The offer 1301 is a type of meta-right of which the recipients have the rights to obtain specific derivative rights when the conditions for obtaining such rights are satisfied. Accordingly, the exemplary offer 1301 has an unspecified state variable 1304. However, specific state variable 1305 and 1306, each with uniquely assigned identifications (IDs) are included in the derived rights 1302 and 1303. The derived state variables 1305 and 1306 are bound to their associated derived rights, e.g., “AlicePlayEbook” (i.e., Alice has the right to play Ebook) is bound to derived right 1302, and “BobPlayEbook” (i.e., Bob has the right to play Ebook) is bound to derived right 1303 The “AlicePlayEbook” variable can be updated when Alice exercises her play right, whereas the “BobPlayEbook” variable can be updated when Bob exercises his play right.
  • Other than deriving rights from an offer, a right can transfer from an entity to a recipient. When a right is transferred, the governing of the associated state variable is also transferred to the recipient. After a right is transferred, the source principal typically can no longer exercise the right, whereas the recipient can exercise the right. The license server governing the exercising of a right of a recipient assumes the responsibility for state management. If, however, the state variables are managed by the common state of right server 1201, the state of right server 1201 needs to be informed of the transfer of right. Specifically, the state variable can be managed in the context of the recipient after the transfer of right.
  • When a right is to be shared between the source principal and the recipient, the associated state variable is referenced in the derived right. If the same right is shared with multiple recipients, then typically all of the recipients share the same state variables with the source principal. In this case, a shared state can be managed by an entity that is accessible by all sharing principals.
  • FIG. 14 is used to illustrate employing of a state variable in deriving inherited usage rights, according to the present invention. In FIG. 14, a derived right can inherit a state variable from meta-rights. For example, a personal computer (PC) of a user, Alice, can be configured to play an e-book according to a license 1403. A personal data assistant (PDA) of Alice also can obtain a right to play the e-book according to offer 1401, if the PC and PDA share the same state variables 1404 and 1405, e.g., “AlicePlayEbook.” A derived right 1402 allows Alice also to play the e-book on her PDA as long as the PDA and the PC share a same count limit 1406 of 5 times.
  • When a usage right is to be shared among a predetermined set of recipients, a state variable for tracking a corresponding usage right can be specified in a meta-right using a same state variable identification for all recipients. During a process of exercising the meta-right, the same state variable identification is included in every derived right.
  • FIG. 15 illustrates the use of state variable in deriving rights that are shared among a known set of rights recipients, according to the present invention. In FIG. 15, a site license 1501 is issued to FooU university. For example, via the site license 1501, a librarian is granted a right to issue rights that allow FooU students to play, view, and the like, corresponding content, such as e-books and the like, as long as such usage is tracked by a state variable 1504, e.g., “www.foou.edu.” Accordingly, rights 1502 and 1503 derived from the site license 1501 include state variables 1505 and 1506, “www.foou.edu,” which can be updated when corresponding students, Alice and Bob, play the e-book.
  • When a usage right is to be shared among a dynamic set of recipients, the state variable can stay unspecified in the usage right. When exercising a meta-right and a set of recipients is known, a state variable can be specified using some identification unique to the known recipients and can be included within a derived right.
  • FIG. 16 is used to illustrate employing of a state variable in deriving rights that are shared among a dynamic set of rights recipients, according to the present invention. In FIG. 16, an offer 1601 specifies that a distributor can issue site licenses to affiliated clubs, allowing 5 members of each club to concurrently view, play, and the like, content, such as an e-book. A corresponding state variable 1607 associated with such a right can be unspecified in the offer 1601. When corresponding rights 1602 and 1603 are issued to affiliated clubs, the corresponding club identities are used to specify state variables 1608 and 1609 in the issued rights. The offers 1602 and 1603 are meta-rights derived from the offer 1601, with offer being assigned the distinct state variables 1608 and 1609. Further rights 1604-1606 can be derived from the offers 1602 and 1603 to be shared among members of each respective club. The licenses 1604 and 1605 are examples of rights derived from the offer 1602, and which inherit the state variable 1608, e.g., “urn:acme:club,” whereas the license 1606 inherits the state variable 1609, e.g., “urn:foo:club.”
  • Not only can state variables be shared among principals, such as rights suppliers, consumers, and the like, a state variable can be shared among multiple exercisable rights. FIG. 17 is used to illustrate employing of a state variable for maintaining a state shared by multiple rights, according to the present invention. In FIG. 17, a same state variable 1703 is associated to both a right to print 1702 and the right to play 1701, so that the total number of playing, printing, and the like, can be tracked together.
  • The state of rights can depend on more than one state variable. FIG. 18 is used to illustrate employing of multiple state variables to represent one state of rights, according to the present invention. The example described with respect to FIG. 18 builds upon the example described with respect to FIG. 16. In FIG. 18, a usage right can be tracked by employing multiple state variables 1807 and 1808 in an offer 1801. The state variable 1808, for example, representing a priority level, can stay unspecified in the corresponding offers 1802 and 1803 (e.g., site licenses). The corresponding state variables 1809-1811, for example, used for setting a priority, can be assigned to each member in the corresponding licenses 1804, 1805 and 1806. The corresponding right to view, play, and the like, can now be dependent on two state variables, effectively restricting 5 simultaneous views, plays, and the like, per priority level.
  • One state variable can represent a collection of states. For example, a unique identification can be used to represent a state variable, and an appropriate mechanism can be employed to map such unique id to a database of multiple variables, where each variable represents a distinct state.
  • The scope of state variables can be used to determine entities by which the state variables can be managed. For example, for a local state variable, usage tracking of associated rights thereof can be managed solely by a trusted agent embedded within a rights consumption environment, such as a media player, and the like. In addition, such usage tracking can be conducted by a trusted remote service, such as the common state-of-rights server 1201. Further, shared global state variables can be made accessible by multiple trusted agents. To avoid privacy issues, security issues, trust issues, rights issues, and the like, associated with accessing content, such as data, and the like, included within a peer rights consumption environment, managing of such shared global state variables can be performed by a remote service, such as the state-of-rights server 1201.
  • A counter is a common form of state variable usage. For example, such state sharing can include counter sharing where a state represents a number of times a right has been exercised, an event has occurred, and the like. Such counter sharing can be manifested in various forms and occur in many contexts, such as: tracking a number of simultaneous uses, tracking a number of sequential uses, sequencing (e.g., a commercial must be viewed before free content can be accessed), a one-time use constraint, a transaction count, a delegation control level, a super-distribution level, dependency on at least one or more services or devices, and the like.
  • In addition, state variables can be incarnated in a wide variety of forms. For example, a state variable can be used to track specific time slots within a period of time, such as used by a movie studio to transfer syndication rights to a specific TV station, to transfer syndication rights shared by a group of stations, to transfer syndication rights assigned through a bidding process, and the like.
  • State variables also can be employed, for example, with regional selling or distribution rights, in a statement from a financial clearing house to acknowledge that an appropriate fee has been paid, as a status of whether a commercial has been watched before free content can be accessed, and the like.
  • Not all rights need be associated with states. FIG. 19 is used to illustrate a case where not all rights are associated with states, according to the present invention. In FIG. 19, an offer 1901 allows a user, Alice, to grant an unlimited play right, view right, and the like, to her PDA. Such a play right need not be associated with any state. Accordingly, derived right 1902 also has an unlimited play right to the content, as well as the right 1903 for her PC.
  • Not all rights which are associated with states are shared or inherited. For example, some rights are meant for off-line usage, can be transferred in whole to another device, and hence are not shared with other devices. FIG. 20 is used to illustrate a case where not all rights which are associated with states are shared or inherited, according to the present invention. In FIG. 20, even though a play right 2003 of a user, Alice, a play right 2002 of a PDA of Alice, and a play right 2003 of a PC of Alice specify a same state variable identification 2004, a same state need not be shared since each device can track a state thereof locally. Advantageously, such an implementation would allow the PC and the PDA to each play the corresponding content up to 5 times.
  • FIG. 21 illustrates a form of an offer which does not explicitly include meta-rights. In FIG. 21, an offer 2101 is configured as a site license written in English. Licenses 2102 and 2103 are instances derived from the offer 2101. In an exemplary embodiment, variables 2104 and 2105 can be created based on interpretation of the offer 2101, for example, by the system of FIG. 12.
  • The preferred embodiment can utilize various devices, such as a personal computers, servers, workstations, PDA's, thin clients, and the like. For example, the client environment can be a handheld device such as a mobile phone or a PDA. Various channels for communication can be used. Further, the various functions can be integrated in one device. For example, the license server function can be accomplished by software within the client environment. Further, the function of the license server or other modules for making offers, selecting rights and granting licenses can be accomplished in the same device. The disclosed functional modules are segregated by function for clarity. However, the various functions can be combined or segregated as hardware and/or software modules in any manner. The various functions can be useful separately or in combination.
  • The various elements and portions thereof can be stored on the same device or on different devices. For example, a license can be stored together with, or separate from, content. Further, the various elements of a license can be stored on separate devices. For example the values of state variables can be stored in a state variable repository of a system that tracks the current value of state variables. Various links, references, specifications, and the like can be used to associate the elements.
  • The invention has been described through exemplary embodiments and examples. However, various modifications can be made without departing from the scope of the invention as defined by the appended claims and legal equivalents.

Claims (44)

1. A method for sharing rights associated with an item between a plurality of devices, the method comprising:
associating a first meta-right with the item, wherein the first meta-right is enforceable by a computing device, and wherein the first meta-right permits a first device of the plurality of devices to generate at least one of a second meta-right and a usage right for the item;
associating a state variable with the first meta-right, wherein the state variable is assigned an identification unique to the first device, and wherein the state variable is managed by a license server;
storing the first meta-right and the item on the first device;
receiving, by the first device, a request to transfer the item to a second device of the plurality of devices;
generating, by the first device, a derived right that is at least one of a second meta-right and a usage right, wherein the derived right is generated in accordance with the first meta-right;
informing, by the first device, the license server that governing of the state variable is transferred to the second device; and
managing, by the license server, the state variable to associate the derived right with the second device.
2. The method of claim 1, wherein the state variable indicates which device is permitted to generate the derived right.
3. The method of claim 1, wherein the state variable indicates how many devices are permitted to share rights.
4. The method of claim 1, wherein the license server is configured to map the identification to a database of multiple variables, where each variable represents a distinct state.
5. The method of claim 1, wherein the first meta-right is derived from an offer, the offer is used to derive a plurality of meta-rights, wherein each of the plurality of meta-rights is associated with a distinct state variable.
6. The method of claim 5, wherein the offer does not explicitly include meta-rights and the distinct state variable is created based on interpretation of the offer.
7. The method of claim 1, wherein the state variable is shared among multiple exercisable rights.
8. The method of claim 7, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
9. The method of claim 1, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
10. The method of claim 1, further comprising transferring, by the first device, the item to the second device.
11. The method of claim 1, further comprising transferring, by the first device, the derived right to the second device.
12. A system for sharing rights associated with an item between a plurality of devices, the system comprising:
a computing device configured to associate a first meta-right with the item, wherein the first meta-right is enforceable by a computing device, and wherein the first meta-right permits a first device of the plurality of devices to generate at least one of a second meta-right and a usage right for the item;
a computing device configured to associate a state variable with the first meta-right, wherein the state variable is assigned an identification unique to the first device, and wherein the state variable is managed by a license server;
a first device comprising:
a computing device configured to store the first meta-right and the item on the first device;
a computing device configured to receive a request to transfer the item to a second device of the plurality of devices;
a computing device configured to generate a derived right that is at least one of a second meta-right and a usage right, wherein the derived right is generated in accordance with the first meta-right; and
a computing device configured to inform the license server that governing of the state variable is transferred to the second device; and
a license server configured to manage the state variable to associate the derived right with the second device.
13. The system of claim 12, wherein the state variable indicates which device is permitted to generate the derived right.
14. The system of claim 12, wherein the state variable indicates how many devices are permitted to share rights.
15. The system of claim 12, wherein the license server is configured to map the identification to a database of multiple variables, where each variable represents a distinct state.
16. The system of claim 12, wherein the first meta-right is derived from an offer, the offer is used to derive a plurality of meta-rights, wherein each of the plurality of meta-rights is associated with a distinct state variable.
17. The system of claim 16, wherein the offer does not explicitly include meta-rights and the distinct state variable is created based on interpretation of the offer.
18. The system of claim 12, wherein the state variable is shared among multiple exercisable rights.
19. The system of claim 18, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
20. The system of claim 12, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
21. The system of claim 12, wherein the first device further comprises a computing device configured to transfer the item to the second device.
22. The system of claim 12, wherein the first device further comprises a computing device configured to transfer the derived right to the second device.
23. A method for sharing rights associated with an item between a plurality of devices, the method comprising:
receiving, at a first device of the plurality of devices, the item and a first meta-right associated with the item, wherein the first meta-right is enforceable by a computing device, wherein the first meta-right is associated with a state variable, the state variable being assigned an identification unique to the first device and being managed by a license server, and wherein the first meta-right permits the first device to generate at least one of a second meta-right and a usage right for the item;
storing the first meta-right and the item on the first device;
receiving, by the first device, a request to transfer the item to a second device of the plurality of devices;
generating, by the first device, a derived right that is at least one of a second meta-right and a usage right, wherein the derived right is generated in accordance with the first meta-right; and
informing, by the first device, the license server that governing of the state variable is transferred to the second device to thereby notify the license server that the state variable should be managed to associate the derived right with the second device.
24. The method of claim 23, wherein the state variable indicates which device is permitted to generate the derived right.
25. The method of claim 23, wherein the state variable indicates how many devices are permitted to share rights.
26. The method of claim 23, wherein the license server is configured to map the identification to a database of multiple variables, where each variable represents a distinct state.
27. The method of claim 23, wherein the first meta-right is derived from an offer, the offer is used to derive a plurality of meta-rights, wherein each of the plurality of meta-rights is associated with a distinct state variable.
28. The method of claim 27, wherein the offer does not explicitly include meta-rights and the distinct state variable is created based on interpretation of the offer.
29. The method of claim 23, wherein the state variable is shared among multiple exercisable rights.
30. The method of claim 29, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
31. The method of claim 23, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
32. The method of claim 23, further comprising transferring, by the first device, the item to the second device.
33. The method of claim 23, further comprising transferring, by the first device, the derived right to the second device.
34. A device for sharing rights associated with an item between a plurality of devices, the device being a first device of the plurality of devices, the device comprising:
a component configured to receive the item and a first meta-right associated with the item, wherein the first meta-right is enforceable by a computing device, wherein the first meta-right is associated with a state variable, the state variable being assigned an identification unique to the first device and being managed by a license server, and wherein the first meta-right permits the first device to generate at least one of a second meta-right and a usage right for the item;
a component configured to store the first meta-right and the item;
a component configured to receive a request to transfer the item to a second device of the plurality of devices;
a processor configured to generate a derived right that is at least one of a second meta-right and a usage right, wherein the derived right is generated in accordance with the first meta-right; and
a processor configured to inform the license server that governing of the state variable is transferred to the second device to thereby notify the license server that the state variable should be managed to associate the derived right with the second device.
35. The device of claim 34, wherein the state variable indicates which device is permitted to generate the derived right.
36. The device of claim 34, wherein the state variable indicates how many devices are permitted to share rights.
37. The device of claim 34, wherein the license server is configured to map the identification to a database of multiple variables, where each variable represents a distinct state.
38. The device of claim 34, wherein the first meta-right is derived from an offer, the offer is used to derive a plurality of meta-rights, wherein each of the plurality of meta-rights is associated with a distinct state variable.
39. The device of claim 38, wherein the offer does not explicitly include meta-rights and the distinct state variable is created based on interpretation of the offer.
40. The device of claim 34, wherein the state variable is shared among multiple exercisable rights.
41. The device of claim 40, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
42. The device of claim 34, wherein the state variable represents a plurality of states, wherein at least one of the states is managed by one of the devices and at least one of the states is managed by the license server.
43. The device of claim 34, further comprising a processor configured to transfer the item to the second device.
44. The device of claim 34, further comprising a processor configured to transfer the derived right to the second device.
US13/162,826 2001-05-31 2011-06-17 System and Method for Rights Offering and Granting Using Shared State Variables Abandoned US20110247077A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/162,826 US20110247077A1 (en) 2001-05-31 2011-06-17 System and Method for Rights Offering and Granting Using Shared State Variables

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US09/867,745 US6754642B2 (en) 2001-05-31 2001-05-31 Method and apparatus for dynamically assigning usage rights to digital works
US10/162,212 US7774279B2 (en) 2001-05-31 2002-06-05 Rights offering and granting
US10/956,070 US8001053B2 (en) 2001-05-31 2004-10-04 System and method for rights offering and granting using shared state variables
US13/162,826 US20110247077A1 (en) 2001-05-31 2011-06-17 System and Method for Rights Offering and Granting Using Shared State Variables

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/956,070 Continuation US8001053B2 (en) 2001-05-31 2004-10-04 System and method for rights offering and granting using shared state variables

Publications (1)

Publication Number Publication Date
US20110247077A1 true US20110247077A1 (en) 2011-10-06

Family

ID=25350385

Family Applications (4)

Application Number Title Priority Date Filing Date
US09/867,745 Expired - Lifetime US6754642B2 (en) 2001-01-17 2001-05-31 Method and apparatus for dynamically assigning usage rights to digital works
US10/777,044 Abandoned US20040162784A1 (en) 2001-05-31 2004-02-13 Method and apparatus for dynamically assigning usage rights to digital works
US13/162,826 Abandoned US20110247077A1 (en) 2001-05-31 2011-06-17 System and Method for Rights Offering and Granting Using Shared State Variables
US14/315,309 Abandoned US20150088768A1 (en) 2001-05-31 2014-06-25 Method and apparatus for dynamically assigning usage rights to digital works

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US09/867,745 Expired - Lifetime US6754642B2 (en) 2001-01-17 2001-05-31 Method and apparatus for dynamically assigning usage rights to digital works
US10/777,044 Abandoned US20040162784A1 (en) 2001-05-31 2004-02-13 Method and apparatus for dynamically assigning usage rights to digital works

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/315,309 Abandoned US20150088768A1 (en) 2001-05-31 2014-06-25 Method and apparatus for dynamically assigning usage rights to digital works

Country Status (9)

Country Link
US (4) US6754642B2 (en)
EP (1) EP1346307B1 (en)
JP (1) JP2004528661A (en)
KR (1) KR100702788B1 (en)
AT (1) ATE312382T1 (en)
DE (1) DE60207812T2 (en)
ES (1) ES2254682T3 (en)
MX (1) MXPA03011044A (en)
WO (1) WO2002098041A2 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080313270A1 (en) * 2007-06-18 2008-12-18 Microsoft Corporation Decoupled mechanism for managed copy client applications and e-commerce servers to interoperate in a heterogeneous environment
US20110271116A1 (en) * 2005-10-10 2011-11-03 Ronald Martinez Set of metadata for association with a composite media item and tool for creating such set of metadata
US20130042296A1 (en) * 2011-08-09 2013-02-14 Ryan L. Hastings Physical interaction with virtual objects for drm
US20130179984A1 (en) * 2010-05-21 2013-07-11 Pratyush Kumar method for controlling the execution of an application on a computer system
US20130218729A1 (en) * 2010-01-11 2013-08-22 Apple Inc. Electronic text manipulation and display
US20150269360A1 (en) * 2014-03-18 2015-09-24 Fujitsu Limited Control method and system
US10019500B2 (en) 2005-02-28 2018-07-10 Huawei Technologies Co., Ltd. Method for sharing and searching playlists
US11379562B2 (en) * 2019-09-09 2022-07-05 Servicenow, Inc. Remote software usage monitoring and entitlement analysis

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0880840A4 (en) * 1996-01-11 2002-10-23 Mrj Inc System for controlling access and distribution of digital property
US7861312B2 (en) 2000-01-06 2010-12-28 Super Talent Electronics, Inc. MP3 player with digital rights management
GB2371636A (en) * 2000-12-21 2002-07-31 Nokia Oyj Content Distribution System
MXPA04004681A (en) 2001-11-20 2004-09-10 Contentguard Holdings Inc An extensible rights expression processing system.
FR2833446B1 (en) * 2001-12-12 2004-04-09 Viaccess Sa PROTOCOL FOR CONTROLLING THE MODE OF ACCESSING DATA TRANSMITTED IN POINT TO POINT OR POINT MULTI-POINT MODE
US20030128229A1 (en) * 2002-01-08 2003-07-10 International Business Machines Corporation Allowing a user to determine whether to view web content based on cost
US20040006544A1 (en) * 2002-07-03 2004-01-08 Michael Gulett Integrated licensing, design, and supply system, method, and article of manufacture for semiconductor chips
TW200407799A (en) * 2002-11-05 2004-05-16 Ind Tech Res Inst Texture partition and transmission method for network progressive transmission and real-time rendering by using the wavelet coding algorithm
US7603717B2 (en) * 2002-11-18 2009-10-13 Microsoft Corporation Digital licenses that include universally quantified variables
WO2004070584A2 (en) * 2003-02-04 2004-08-19 Canonline Global Media, Inc. Method and apparatus for converting objects between weakly and strongly typed programming frameworks
US10063523B2 (en) * 2005-09-14 2018-08-28 Oracle International Corporation Crafted identities
US10275723B2 (en) 2005-09-14 2019-04-30 Oracle International Corporation Policy enforcement via attestations
US9781154B1 (en) 2003-04-01 2017-10-03 Oracle International Corporation Systems and methods for supporting information security and sub-system operational protocol conformance
US7949877B2 (en) * 2003-06-30 2011-05-24 Realnetworks, Inc. Rights enforcement and usage reporting on a client device
US8082563B2 (en) * 2003-07-25 2011-12-20 Home Box Office, Inc. System and method for content access control through default profiles and metadata pointers
US7090128B2 (en) * 2003-09-08 2006-08-15 Systems And Software Enterprises, Inc. Mobile electronic newsstand
US8641424B2 (en) * 2003-10-23 2014-02-04 Monvini Limited Method of publication and distribution of instructional materials
US9665876B2 (en) * 2003-10-23 2017-05-30 Monvini Limited System of publication and distribution of instructional materials and method therefor
JP4321334B2 (en) * 2004-04-09 2009-08-26 ソニー株式会社 License creation device, license creation method, and computer program
US7765404B2 (en) * 2004-06-29 2010-07-27 Nokia Corporation Providing content in a communication system
US20060085348A1 (en) * 2004-07-16 2006-04-20 Ns8 Corporation Method and system for managing the use of electronic works
KR100739176B1 (en) * 2004-11-09 2007-07-13 엘지전자 주식회사 System and method for protecting unprotected digital contents
TWI250435B (en) * 2004-12-24 2006-03-01 Ind Tech Res Inst Method of copyright publication and trade for stepwise digital content
US20070011165A1 (en) * 2005-07-05 2007-01-11 Xerox Corporation. Retracting rights to digital works
US20070056042A1 (en) * 2005-09-08 2007-03-08 Bahman Qawami Mobile memory system for secure storage and delivery of media content
US7720767B2 (en) * 2005-10-24 2010-05-18 Contentguard Holdings, Inc. Method and system to support dynamic rights and resources sharing
RU2008127501A (en) * 2006-01-13 2010-02-20 Вайет (Us) SULFONIL-SUBSTITUTED 1H-INDOLES AS LIGANDS OF 5-HYDROXYTRIPTAMINE RECEPTORS
US8533846B2 (en) * 2006-11-08 2013-09-10 Citrix Systems, Inc. Method and system for dynamically associating access rights with a resource
DE102007008948B4 (en) * 2007-02-21 2018-02-22 Dspace Digital Signal Processing And Control Engineering Gmbh Method and system for providing digital content
US20090037808A1 (en) * 2007-08-01 2009-02-05 Thibodeau Barbara L System, Method and Computer Program Product for Producing and Managing Certain Documents
US20090089883A1 (en) * 2007-09-29 2009-04-02 Sympact Technologies Llc Method and apparatus for controlling media content distribution
US8706638B2 (en) * 2008-01-11 2014-04-22 Apple Inc. Method for on demand video and other content rental
US20150220894A1 (en) * 2014-02-05 2015-08-06 Andrew Dale Jouffray Software marketing and trade
US10909255B2 (en) * 2017-08-24 2021-02-02 Data Republic Pty Ltd Systems and methods to control data access and usage
JP7267571B2 (en) * 2018-11-30 2023-05-02 株式会社コナミアミューズメント Service system and computer program used for it
US20210383008A1 (en) * 2020-06-04 2021-12-09 i2Chain, Inc. Methods and systems for altering access rights set on digital documents based on temporal events

Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4937863A (en) * 1988-03-07 1990-06-26 Digital Equipment Corporation Software licensing management system
US5765152A (en) * 1995-10-13 1998-06-09 Trustees Of Dartmouth College System and method for managing copyrighted electronic media
US5892900A (en) * 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US6006332A (en) * 1996-10-21 1999-12-21 Case Western Reserve University Rights management system for digital media
US6044466A (en) * 1997-11-25 2000-03-28 International Business Machines Corp. Flexible and dynamic derivation of permissions
US6189146B1 (en) * 1998-03-18 2001-02-13 Microsoft Corporation System and method for software licensing
US6226618B1 (en) * 1998-08-13 2001-05-01 International Business Machines Corporation Electronic content delivery system
US20020048369A1 (en) * 1995-02-13 2002-04-25 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US20020052933A1 (en) * 2000-01-14 2002-05-02 Gerd Leonhard Method and apparatus for licensing media over a network
US6385596B1 (en) * 1998-02-06 2002-05-07 Liquid Audio, Inc. Secure online music distribution system
US20020077986A1 (en) * 2000-07-14 2002-06-20 Hiroshi Kobata Controlling and managing digital assets
US20020191764A1 (en) * 1999-12-06 2002-12-19 Yoshihiro Hori Data distribution system and recording device for use therein
US20030144869A1 (en) * 2001-11-20 2003-07-31 Contentguard Holdings, Inc. Extensible rights expression processing system
US20040039916A1 (en) * 2002-05-10 2004-02-26 David Aldis System and method for multi-tiered license management and distribution using networked clearinghouses
US20040044779A1 (en) * 2000-06-05 2004-03-04 Lambert Martin R. Digital rights management
US20040098580A1 (en) * 2002-11-15 2004-05-20 Microsoft Corporation State reference
US20040117784A1 (en) * 2002-10-15 2004-06-17 Canon Kabushiki Kaisha Management apparatus, management method, and control program therefor
US20050060569A1 (en) * 2003-09-12 2005-03-17 Konica Minolta Photo Imaging, Inc. Method of managing the information on the release of restriction on use
US20050071280A1 (en) * 2003-09-25 2005-03-31 Convergys Information Management Group, Inc. System and method for federated rights management
US6918113B2 (en) * 2000-11-06 2005-07-12 Endeavors Technology, Inc. Client installation and execution system for streamed applications
US20050289072A1 (en) * 2004-06-29 2005-12-29 Vinay Sabharwal System for automatic, secure and large scale software license management over any computer network
US20060155620A1 (en) * 2003-06-10 2006-07-13 Ken Tsurubayashi License distribution method
US20070073626A1 (en) * 2000-12-28 2007-03-29 Reeder Russell P Integrated media management and rights distribution apparatus

Family Cites Families (207)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3263158A (en) 1963-08-15 1966-07-26 Motorola Inc Saturable reactor voltage control circuit
US3609697A (en) 1968-10-21 1971-09-28 Ibm Program security device
US3798605A (en) 1971-06-30 1974-03-19 Ibm Centralized verification system
US3790700A (en) 1971-12-17 1974-02-05 Hughes Aircraft Co Catv program control system
CH624877A5 (en) * 1977-05-13 1981-08-31 Idc Chemie Ag
DE2840980C3 (en) 1977-10-08 1982-05-06 Tokyo Electric Co., Ltd., Tokyo Electronic cash register and electronic cash register system
US4278837A (en) 1977-10-31 1981-07-14 Best Robert M Crypto microprocessor for executing enciphered programs
US4159468A (en) 1977-11-17 1979-06-26 Burroughs Corporation Communications line authentication device
FR2448825A1 (en) 1979-02-06 1980-09-05 Telediffusion Fse SYSTEM FOR TRANSMITTING INFORMATION BETWEEN A TRANSMISSION CENTER AND RECEIVING STATIONS, WHICH IS PROVIDED WITH A MEANS OF CONTROLLING ACCESS TO THE INFORMATION TRANSMITTED
US4361851A (en) * 1980-01-04 1982-11-30 Asip William F System for remote monitoring and data transmission over non-dedicated telephone lines
US4529870A (en) 1980-03-10 1985-07-16 David Chaum Cryptographic identification, financial transaction, and credential device
US4442486A (en) 1981-11-25 1984-04-10 U.S. Philips Corporation Protected programmable apparatus
US4429385A (en) * 1981-12-31 1984-01-31 American Newspaper Publishers Association Method and apparatus for digital serial scanning with hierarchical and relational access
EP0084441A3 (en) 1982-01-19 1984-08-22 Tabs Limited Method and apparatus for the protection of proprietary computer software
US4558176A (en) 1982-09-20 1985-12-10 Arnold Mark G Computer systems to inhibit unauthorized copying, unauthorized usage, and automated cracking of protected software
US4588991A (en) 1983-03-07 1986-05-13 Atalla Corporation File access security method and means
US4593376A (en) 1983-04-21 1986-06-03 Volk Larry N System for vending program cartridges which have circuitry for inhibiting program usage after preset time interval expires
EP0148235B1 (en) * 1983-06-30 1988-10-05 Independent Broadcasting Authority Encrypted broadcast television system
US4658093A (en) 1983-07-11 1987-04-14 Hellman Martin E Software distribution system
US4740890A (en) * 1983-12-22 1988-04-26 Software Concepts, Inc. Software protection system with trial period usage code and unlimited use unlocking code both recorded on program storage media
US4644493A (en) 1984-09-14 1987-02-17 International Business Machines Corporation Implementing a shared higher level of privilege on personal computers for copy protection of software
EP0180460B1 (en) 1984-10-31 1990-09-19 Sony Corporation Decoders for pay television systems
US4614861A (en) 1984-11-15 1986-09-30 Intellicard International, Inc. Unitary, self-contained card verification and validation system and method
US4713753A (en) 1985-02-21 1987-12-15 Honeywell Inc. Secure data processing system architecture with format control
US4891838A (en) 1985-11-04 1990-01-02 Dental Data Service, Inc. Computer accessing system
LU86203A1 (en) * 1985-12-11 1987-07-24 Cen Centre Energie Nucleaire METHOD AND APPARATUS FOR VERIFYING THE AUTHENTICITY OF DOCUMENTS LINKED TO A PERSON AND THE IDENTITY OF THEIR CARRIERS
DE3787583T2 (en) 1986-07-07 1994-02-03 Semiconductor Energy Lab Portable book without paper.
US5014234A (en) 1986-08-25 1991-05-07 Ncr Corporation System with software usage timer and counter for allowing limited use but preventing continued unauthorized use of protected software
US5010571A (en) 1986-09-10 1991-04-23 Titan Linkabit Corporation Metering retrieval of encrypted data stored in customer data retrieval terminal
US4827508A (en) 1986-10-14 1989-05-02 Personal Library Software, Inc. Database usage metering and protection system and method
US4977594A (en) 1986-10-14 1990-12-11 Electronic Publishing Resources, Inc. Database usage metering and protection system and method
US5050213A (en) 1986-10-14 1991-09-17 Electronic Publishing Resources, Inc. Database usage metering and protection system and method
US5047928A (en) 1986-10-24 1991-09-10 Wiedemer John D Billing system for computer software
US4817140A (en) 1986-11-05 1989-03-28 International Business Machines Corp. Software protection system using a single-key cryptosystem, a hardware-based authorization system and a secure coprocessor
US4796220A (en) 1986-12-15 1989-01-03 Pride Software Development Corp. Method of controlling the copying of software
US4868376A (en) 1987-05-15 1989-09-19 Smartcard International Inc. Intelligent portable interactive personal data system
US4975647A (en) 1987-06-01 1990-12-04 Nova Biomedical Corporation Controlling machine operation with respect to consumable accessory units
DE3856404T2 (en) 1987-08-28 2000-10-19 Honda Motor Co Ltd Data management system
US4999806A (en) 1987-09-04 1991-03-12 Fred Chernow Software distribution system
US5390297A (en) * 1987-11-10 1995-02-14 Auto-Trol Technology Corporation System for controlling the number of concurrent copies of a program in a network based on the number of available licenses
US4924378A (en) 1988-06-13 1990-05-08 Prime Computer, Inc. License mangagement system and license storage key
US4961142A (en) 1988-06-29 1990-10-02 Mastercard International, Inc. Multi-issuer transaction device with individual identification verification plug-in application modules for each issuer
US5247575A (en) 1988-08-16 1993-09-21 Sprague Peter J Information distribution system
US4932054A (en) 1988-09-16 1990-06-05 Chou Wayne W Method and apparatus for protecting computer software utilizing coded filter network in conjunction with an active coded hardware device
US5023907A (en) 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server
US4953209A (en) 1988-10-31 1990-08-28 International Business Machines Corp. Self-verifying receipt and acceptance system for electronically delivered data objects
DE3903454A1 (en) 1988-12-12 1990-06-13 Raymund H Eisele ELEMENT INSERTABLE IN IT FACILITIES
US4949187A (en) 1988-12-16 1990-08-14 Cohen Jason M Video communications system having a remotely controlled central source of video and audio data
US5113519A (en) 1989-05-15 1992-05-12 International Business Machines Corporation Maintenance of file attributes in a distributed data processing system
US5129083A (en) * 1989-06-29 1992-07-07 Digital Equipment Corporation Conditional object creating system having different object pointers for accessing a set of data structure objects
US5347579A (en) 1989-07-05 1994-09-13 Blandford Robert R Personal computer diary
US5138712A (en) 1989-10-02 1992-08-11 Sun Microsystems, Inc. Apparatus and method for licensing software on a network of computers
US5148481A (en) 1989-10-06 1992-09-15 International Business Machines Corporation Transaction system security method and apparatus
FR2653248B1 (en) 1989-10-13 1991-12-20 Gemolus Card International PAYMENT OR INFORMATION TRANSFER SYSTEM BY ELECTRONIC MEMORY CARD.
US5136643A (en) 1989-10-13 1992-08-04 Fischer Addison M Public/key date-time notary facility
FR2653914A1 (en) 1989-10-27 1991-05-03 Trt Telecom Radio Electr SYSTEM FOR AUTHENTICATING A MICROCIRCUIT CARD BY A PERSONAL MICROCOMPUTER, AND METHOD FOR ITS IMPLEMENTATION
US5263157A (en) 1990-02-15 1993-11-16 International Business Machines Corporation Method and system for providing user access control within a distributed data processing system by the exchange of access control profiles
US5263158A (en) 1990-02-15 1993-11-16 International Business Machines Corporation Method and system for variable authority level user access control in a distributed data processing system having multiple resource manager
GB9004901D0 (en) * 1990-03-05 1990-05-02 Space Communications Sat Tel L Television scrambler
US5058164A (en) 1990-05-03 1991-10-15 National Semiconductor Corp. Encryption of streams of addressed information to be used for program code protection
US5052040A (en) 1990-05-25 1991-09-24 Micronyx, Inc. Multiple user stored data cryptographic labeling system and method
JP2689998B2 (en) 1990-08-22 1997-12-10 インターナショナル・ビジネス・マシーンズ・コーポレイション Device for cryptographic operation
JPH05134957A (en) 1990-10-10 1993-06-01 Fuji Xerox Co Ltd Data management system
US5222134A (en) 1990-11-07 1993-06-22 Tau Systems Corporation Secure system for activating personal computer software at remote locations
US5103476A (en) 1990-11-07 1992-04-07 Waite David P Secure system for activating personal computer software at remote locations
DE4042094C2 (en) * 1990-12-28 1999-02-25 Peter Eiba System for operating one or more entertainment, in particular money, gaming device (s)
US5255106A (en) 1991-02-05 1993-10-19 International Integrated Communications, Ltd. Method and apparatus for delivering secured hard-copy facsimile documents
US5504818A (en) 1991-04-19 1996-04-02 Okano; Hirokazu Information processing system using error-correcting codes and cryptography
DE69228350T2 (en) * 1991-05-08 1999-09-23 Digital Equipment Corp ADMINISTRATIVE INTERFACE AND FORMAT FOR LICENSE MANAGEMENT SYSTEM
WO1992020021A1 (en) * 1991-05-08 1992-11-12 Digital Equipment Corporation License management system
US5438508A (en) 1991-06-28 1995-08-01 Digital Equipment Corporation License document interchange format for license management system
US5260999A (en) 1991-06-28 1993-11-09 Digital Equipment Corporation Filters in license management system
US5204897A (en) 1991-06-28 1993-04-20 Digital Equipment Corporation Management interface for license management system
US5940504A (en) 1991-07-01 1999-08-17 Infologic Software, Inc. Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site
US5504814A (en) 1991-07-10 1996-04-02 Hughes Aircraft Company Efficient security kernel for the 80960 extended architecture
US5276444A (en) 1991-09-23 1994-01-04 At&T Bell Laboratories Centralized security control system
US5734823A (en) 1991-11-04 1998-03-31 Microtome, Inc. Systems and apparatus for electronic communication and storage of information
WO1993009490A1 (en) 1991-11-04 1993-05-13 Vpr Systems Ltd. Lap-top computer for retrieving and displaying text and graphic information encoded on personal library cd-rom
US5557518A (en) 1994-04-28 1996-09-17 Citibank, N.A. Trusted agents for open electronic commerce
US5453601A (en) 1991-11-15 1995-09-26 Citibank, N.A. Electronic-monetary system
DE69333787T2 (en) * 1992-01-08 2006-02-02 Broadband Innovations, Inc., San Diego Method and device for generating a multi-channel signal
US5301231A (en) 1992-02-12 1994-04-05 International Business Machines Corporation User defined function facility
US5183404A (en) 1992-04-08 1993-02-02 Megahertz Corporation Systems for connection of physical/electrical media connectors to computer communications cards
US5276735A (en) 1992-04-17 1994-01-04 Secure Computing Corporation Data enclave and trusted path system
US5440631A (en) 1992-04-24 1995-08-08 Fijitsu Limited Information distribution system wherein storage medium storing ciphered information is distributed
JP2659896B2 (en) 1992-04-29 1997-09-30 インターナショナル・ビジネス・マシーンズ・コーポレイション Structured document copy management method and structured document copy management device
US5412717A (en) 1992-05-15 1995-05-02 Fischer; Addison M. Computer system security method and apparatus having program authorization information data structures
US5235642A (en) 1992-07-21 1993-08-10 Digital Equipment Corporation Access control subsystem and method for distributed computer system using locally cached authentication credentials
US5287408A (en) * 1992-08-31 1994-02-15 Autodesk, Inc. Apparatus and method for serializing and validating copies of computer software
US5381526A (en) 1992-09-11 1995-01-10 Eastman Kodak Company Method and apparatus for storing and retrieving generalized image data
US5293422A (en) * 1992-09-23 1994-03-08 Dynatek, Inc. Usage control system for computer software
JP3358627B2 (en) * 1992-10-16 2002-12-24 ソニー株式会社 Information recording / reproducing device
US5319705A (en) 1992-10-21 1994-06-07 International Business Machines Corporation Method and system for multimedia access control enablement
US5414852A (en) * 1992-10-30 1995-05-09 International Business Machines Corporation Method for protecting data in a computer system
US5341429A (en) 1992-12-04 1994-08-23 Testdrive Corporation Transformation of ephemeral material
US5509070A (en) 1992-12-15 1996-04-16 Softlock Services Inc. Method for encouraging purchase of executable and non-executable software
US5504837A (en) 1993-05-10 1996-04-02 Bell Communications Research, Inc. Method for resolving conflicts among distributed entities through the generation of counter proposals by transversing a goal hierarchy with acceptable, unacceptable, and indeterminate nodes
US5337357A (en) 1993-06-17 1994-08-09 Software Security, Inc. Method of software distribution protection
US5428606A (en) 1993-06-30 1995-06-27 Moskowitz; Scott A. Digital information commodities exchange
US5386369A (en) * 1993-07-12 1995-01-31 Globetrotter Software Inc. License metering system for software applications
IL110891A (en) 1993-09-14 1999-03-12 Spyrus System and method for data access control
CA2129075C (en) 1993-10-18 1999-04-20 Joseph J. Daniele Electronic copyright royalty accounting system using glyphs
US6135646A (en) * 1993-10-22 2000-10-24 Corporation For National Research Initiatives System for uniquely and persistently identifying, managing, and tracking digital objects
JPH07212712A (en) 1993-10-29 1995-08-11 Eastman Kodak Co Method and equipment for adding and deleting digital watermark in hierarchical picture memory and fetch system
US5455953A (en) 1993-11-03 1995-10-03 Wang Laboratories, Inc. Authorization system for obtaining in single step both identification and access rights of client to server directly from encrypted authorization ticket
US5625690A (en) * 1993-11-15 1997-04-29 Lucent Technologies Inc. Software pay per use system
US5768426A (en) 1993-11-18 1998-06-16 Digimarc Corporation Graphics processing system employing embedded code signals
US5748783A (en) 1995-05-08 1998-05-05 Digimarc Corporation Method and apparatus for robust information coding
US5495411A (en) * 1993-12-22 1996-02-27 Ananda; Mohan Secure software rental system using continuous asynchronous password verification
US5473687A (en) 1993-12-29 1995-12-05 Infosafe Systems, Inc. Method for retrieving secure information from a database
US5504816A (en) * 1994-02-02 1996-04-02 Gi Corporation Method and apparatus for controlling access to digital signals
US5553143A (en) * 1994-02-04 1996-09-03 Novell, Inc. Method and apparatus for electronic licensing
US5394469A (en) 1994-02-18 1995-02-28 Infosafe Systems, Inc. Method and apparatus for retrieving secure information from mass storage media
JP2853727B2 (en) 1994-02-22 1999-02-03 日本ビクター株式会社 Reproduction protection method and protection reproduction device
US5787172A (en) * 1994-02-24 1998-07-28 The Merdan Group, Inc. Apparatus and method for establishing a cryptographic link between elements of a system
US5499298A (en) 1994-03-17 1996-03-12 National University Of Singapore Controlled dissemination of digital information
US5757907A (en) 1994-04-25 1998-05-26 International Business Machines Corporation Method and apparatus for enabling trial period use of software products: method and apparatus for generating a machine-dependent identification
CA2143874C (en) 1994-04-25 2000-06-20 Thomas Edward Cooper Method and apparatus for enabling trial period use of software products: method and apparatus for utilizing a decryption stub
US5563946A (en) 1994-04-25 1996-10-08 International Business Machines Corporation Method and apparatus for enabling trial period use of software products: method and apparatus for passing encrypted files between data processing systems
US5799087A (en) 1994-04-28 1998-08-25 Citibank, N.A. Electronic-monetary system
US5636346A (en) * 1994-05-09 1997-06-03 The Electronic Address, Inc. Method and system for selectively targeting advertisements and programming
US5564038A (en) * 1994-05-20 1996-10-08 International Business Machines Corporation Method and apparatus for providing a trial period for a software license product using a date stamp and designated test period
US5694546A (en) * 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US5473692A (en) 1994-09-07 1995-12-05 Intel Corporation Roving software license for a hardware agent
US5535276A (en) * 1994-11-09 1996-07-09 Bell Atlantic Network Services, Inc. Yaksha, an improved system and method for securing communications using split private key asymmetric cryptography
US5557678A (en) * 1994-07-18 1996-09-17 Bell Atlantic Network Services, Inc. System and method for centralized session key distribution, privacy enhanced messaging and information distribution using a split private key public cryptosystem
US6189037B1 (en) * 1994-09-30 2001-02-13 Intel Corporation Broadband data interface
US5727065A (en) * 1994-11-14 1998-03-10 Hughes Electronics Deferred billing, broadcast, electronic document distribution system and method
JPH08263438A (en) * 1994-11-23 1996-10-11 Xerox Corp Distribution and use control system of digital work and access control method to digital work
US5715403A (en) * 1994-11-23 1998-02-03 Xerox Corporation System for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar
US5634012A (en) 1994-11-23 1997-05-27 Xerox Corporation System for controlling the distribution and use of digital works having a fee reporting mechanism
US5638443A (en) 1994-11-23 1997-06-10 Xerox Corporation System for controlling the distribution and use of composite digital works
US5629980A (en) 1994-11-23 1997-05-13 Xerox Corporation System for controlling the distribution and use of digital works
US5655077A (en) 1994-12-13 1997-08-05 Microsoft Corporation Method and system for authenticating access to heterogeneous computing services
US5485577A (en) * 1994-12-16 1996-01-16 General Instrument Corporation Of Delaware Method and apparatus for incremental delivery of access rights
US5649013A (en) 1994-12-23 1997-07-15 Compuserve Incorporated Royalty tracking method and apparatus
US5745569A (en) 1996-01-17 1998-04-28 The Dice Company Method for stega-cipher protection of computer code
JPH08214281A (en) 1995-02-06 1996-08-20 Sony Corp Charging method and system
DE69637799D1 (en) 1995-02-13 2009-02-12 Intertrust Tech Corp Systems and procedures for secure transaction management and electronic legal protection
US6157721A (en) 1996-08-12 2000-12-05 Intertrust Technologies Corp. Systems and methods using cryptography to protect secure computing environments
US5943422A (en) 1996-08-12 1999-08-24 Intertrust Technologies Corp. Steganographic techniques for securely delivering electronic digital rights management control information over insecure communication channels
US5530235A (en) 1995-02-16 1996-06-25 Xerox Corporation Interactive contents revealing storage device
US6424717B1 (en) * 1995-04-03 2002-07-23 Scientific-Atlanta, Inc. Encryption devices for use in a conditional access system
US6246767B1 (en) * 1995-04-03 2001-06-12 Scientific-Atlanta, Inc. Source authentication of download information in a conditional access system
US5534975A (en) 1995-05-26 1996-07-09 Xerox Corporation Document processing system utilizing document service cards to provide document processing services
US5790677A (en) * 1995-06-29 1998-08-04 Microsoft Corporation System and method for secure electronic commerce transactions
FR2736783B1 (en) * 1995-07-13 1997-08-14 Thomson Multimedia Sa METHOD AND APPARATUS FOR RECORDING AND PLAYBACK WITH LARGE CAPACITY RECORDING MEDIUM
US5764807A (en) * 1995-09-14 1998-06-09 Primacomp, Inc. Data compression using set partitioning in hierarchical trees
EP0766468B1 (en) * 1995-09-28 2006-05-03 Nec Corporation Method and system for inserting a spread spectrum watermark into multimedia data
US5896176A (en) 1995-10-27 1999-04-20 Texas Instruments Incorporated Content-based video compression
US5708717A (en) 1995-11-29 1998-01-13 Alasia; Alfred Digital anti-counterfeiting software method and apparatus
US5825876A (en) * 1995-12-04 1998-10-20 Northern Telecom Time based availability to content of a storage medium
US5708709A (en) * 1995-12-08 1998-01-13 Sun Microsystems, Inc. System and method for managing try-and-buy usage of application programs
US5633932A (en) 1995-12-19 1997-05-27 Intel Corporation Apparatus and method for preventing disclosure through user-authentication at a printing node
EP0880840A4 (en) 1996-01-11 2002-10-23 Mrj Inc System for controlling access and distribution of digital property
DE69703074T2 (en) * 1996-03-18 2001-05-03 News Datacom Ltd CHIP CARD COUPLING FOR PAY-TV SYSTEMS
US5761686A (en) 1996-06-27 1998-06-02 Xerox Corporation Embedding encoded information in an iconic version of a text image
FR2752655B1 (en) * 1996-08-20 1998-09-18 France Telecom METHOD AND EQUIPMENT FOR ALLOCATING A COMPLEMENTARY CONDITIONAL ACCESS TO A TELEVISION PROGRAM ALREADY WITH CONDITIONAL ACCESS
US5991306A (en) * 1996-08-26 1999-11-23 Microsoft Corporation Pull based, intelligent caching system and method for delivering data over a network
US5812664A (en) * 1996-09-06 1998-09-22 Pitney Bowes Inc. Key distribution system
US5825879A (en) * 1996-09-30 1998-10-20 Intel Corporation System and method for copy-protecting distributed video content
US5825892A (en) 1996-10-28 1998-10-20 International Business Machines Corporation Protecting images with an image watermark
US6115471A (en) 1996-11-28 2000-09-05 Fujitsu Limited Member-exclusive service system and method through internet
US6076166A (en) 1997-01-17 2000-06-13 Philips Electronics North America Corporation Personalizing hospital intranet web sites
EP0906700B1 (en) * 1997-01-27 2002-09-11 Koninklijke Philips Electronics N.V. Method and system for transferring content information and supplemental information relating thereto
GB9703193D0 (en) * 1997-02-15 1997-04-02 Philips Electronics Nv Television
US5920861A (en) 1997-02-25 1999-07-06 Intertrust Technologies Corp. Techniques for defining using and manipulating rights management data structures
US6233684B1 (en) 1997-02-28 2001-05-15 Contenaguard Holdings, Inc. System for controlling the distribution and use of rendered digital works through watermaking
US5999949A (en) 1997-03-14 1999-12-07 Crandall; Gary E. Text file compression system utilizing word terminators
JP3613929B2 (en) * 1997-05-07 2005-01-26 富士ゼロックス株式会社 Access credential authentication apparatus and method
AU7475798A (en) * 1997-05-07 1998-11-27 Neomedia Technologies, Inc. Scanner enhanced remote control unit and system for automatically linking to on-line resources
US6195646B1 (en) * 1997-05-13 2001-02-27 Data Junction Corp System and method for facilitating the valuation and purchase of information
US6112239A (en) * 1997-06-18 2000-08-29 Intervu, Inc System and method for server-side optimization of data delivery on a distributed computer network
GB9714227D0 (en) * 1997-07-04 1997-09-10 British Telecomm A method of scheduling calls
JP3613936B2 (en) * 1997-07-07 2005-01-26 富士ゼロックス株式会社 Access qualification authentication device
DE69724947T2 (en) 1997-07-31 2004-05-19 Siemens Ag Computer system and method for backing up a file
JP3671611B2 (en) * 1997-08-05 2005-07-13 富士ゼロックス株式会社 Access credential authentication apparatus and method
JP3622433B2 (en) * 1997-08-05 2005-02-23 富士ゼロックス株式会社 Access credential authentication apparatus and method
US6523745B1 (en) * 1997-08-05 2003-02-25 Enix Corporation Electronic transaction system including a fingerprint identification encoding
US6091777A (en) 1997-09-18 2000-07-18 Cubic Video Technologies, Inc. Continuously adaptive digital video compression system and method for a web streamer
IL121862A (en) * 1997-09-29 2005-07-25 Nds Ltd West Drayton Distributed ird system for pay television systems
US6038563A (en) 1997-10-31 2000-03-14 Sun Microsystems, Inc. System and method for restricting database access to managed object information using a permissions table that specifies access rights corresponding to user access rights to the managed objects
US6112181A (en) 1997-11-06 2000-08-29 Intertrust Technologies Corporation Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information
US6141754A (en) * 1997-11-28 2000-10-31 International Business Machines Corporation Integrated method and system for controlling information access and distribution
FR2772486B1 (en) 1997-12-15 2000-01-07 Elf Exploration Prod METHOD FOR THE AUTOMATIC DETECTION OF PLANAR HETEROGENEITIES INTERRUPTING THE LAMINATION OF A MEDIUM
JP4113274B2 (en) * 1998-02-05 2008-07-09 富士ゼロックス株式会社 Authentication apparatus and method
US6216112B1 (en) * 1998-05-27 2001-04-10 William H. Fuller Method for software distribution and compensation with replenishable advertisements
US6219652B1 (en) * 1998-06-01 2001-04-17 Novell, Inc. Network license authentication
US6169976B1 (en) * 1998-07-02 2001-01-02 Encommerce, Inc. Method and apparatus for regulating the use of licensed products
US6397333B1 (en) * 1998-10-07 2002-05-28 Infineon Technologies Ag Copy protection system and method
US6330670B1 (en) 1998-10-26 2001-12-11 Microsoft Corporation Digital rights management operating system
US6327652B1 (en) 1998-10-26 2001-12-04 Microsoft Corporation Loading and identifying a digital rights management operating system
US6158010A (en) 1998-10-28 2000-12-05 Crosslogix, Inc. System and method for maintaining security in a distributed computer network
JP3816689B2 (en) * 1999-03-31 2006-08-30 株式会社東芝 Information distribution apparatus, information reception apparatus, and communication method
WO2000073922A2 (en) * 1999-06-01 2000-12-07 Cacheflow, Inc. Content delivery system
FR2796183B1 (en) * 1999-07-07 2001-09-28 A S K CONTACTLESS ACCESS TICKET AND MANUFACTURING METHOD THEREOF
US6796555B1 (en) * 1999-07-19 2004-09-28 Lucent Technologies Inc. Centralized video controller for controlling distribution of video signals
US20020056118A1 (en) * 1999-08-27 2002-05-09 Hunter Charles Eric Video and music distribution system
US6289455B1 (en) * 1999-09-02 2001-09-11 Crypotography Research, Inc. Method and apparatus for preventing piracy of digital content
WO2001024530A2 (en) * 1999-09-29 2001-04-05 Loudeye Technologies, Inc. Streaming media encoding agent for temporal modifications
US6401211B1 (en) * 1999-10-19 2002-06-04 Microsoft Corporation System and method of user logon in combination with user authentication for network access
US6738901B1 (en) * 1999-12-15 2004-05-18 3M Innovative Properties Company Smart card controlled internet access
US7792745B2 (en) * 2000-02-25 2010-09-07 Ipass Inc. Method and system to facilitate financial settlement of service access transactions between multiple parties
JP2001338117A (en) * 2000-05-25 2001-12-07 Internatl Business Mach Corp <Ibm> Server, information communication terminal, method for managing sales of commodity, storage medium and program transmission device
US7103668B1 (en) * 2000-08-29 2006-09-05 Inetcam, Inc. Method and apparatus for distributing multimedia to remote clients
US7225231B2 (en) * 2000-09-20 2007-05-29 Visto Corporation System and method for transmitting workspace elements across a network
US20020143952A1 (en) * 2001-03-30 2002-10-03 Sugiarto Basuki Afandi Multimedia download timer system and method

Patent Citations (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4937863A (en) * 1988-03-07 1990-06-26 Digital Equipment Corporation Software licensing management system
US20020048369A1 (en) * 1995-02-13 2002-04-25 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US5765152A (en) * 1995-10-13 1998-06-09 Trustees Of Dartmouth College System and method for managing copyrighted electronic media
US5892900A (en) * 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US6006332A (en) * 1996-10-21 1999-12-21 Case Western Reserve University Rights management system for digital media
US6044466A (en) * 1997-11-25 2000-03-28 International Business Machines Corp. Flexible and dynamic derivation of permissions
US6385596B1 (en) * 1998-02-06 2002-05-07 Liquid Audio, Inc. Secure online music distribution system
US6189146B1 (en) * 1998-03-18 2001-02-13 Microsoft Corporation System and method for software licensing
US6226618B1 (en) * 1998-08-13 2001-05-01 International Business Machines Corporation Electronic content delivery system
US20020191764A1 (en) * 1999-12-06 2002-12-19 Yoshihiro Hori Data distribution system and recording device for use therein
US20020052933A1 (en) * 2000-01-14 2002-05-02 Gerd Leonhard Method and apparatus for licensing media over a network
US20040044779A1 (en) * 2000-06-05 2004-03-04 Lambert Martin R. Digital rights management
US20020077986A1 (en) * 2000-07-14 2002-06-20 Hiroshi Kobata Controlling and managing digital assets
US6918113B2 (en) * 2000-11-06 2005-07-12 Endeavors Technology, Inc. Client installation and execution system for streamed applications
US20070073626A1 (en) * 2000-12-28 2007-03-29 Reeder Russell P Integrated media management and rights distribution apparatus
US20030144869A1 (en) * 2001-11-20 2003-07-31 Contentguard Holdings, Inc. Extensible rights expression processing system
US20040039916A1 (en) * 2002-05-10 2004-02-26 David Aldis System and method for multi-tiered license management and distribution using networked clearinghouses
US20040117784A1 (en) * 2002-10-15 2004-06-17 Canon Kabushiki Kaisha Management apparatus, management method, and control program therefor
US20040098580A1 (en) * 2002-11-15 2004-05-20 Microsoft Corporation State reference
US20060155620A1 (en) * 2003-06-10 2006-07-13 Ken Tsurubayashi License distribution method
US20050060569A1 (en) * 2003-09-12 2005-03-17 Konica Minolta Photo Imaging, Inc. Method of managing the information on the release of restriction on use
US20050071280A1 (en) * 2003-09-25 2005-03-31 Convergys Information Management Group, Inc. System and method for federated rights management
US20050289072A1 (en) * 2004-06-29 2005-12-29 Vinay Sabharwal System for automatic, secure and large scale software license management over any computer network

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10521452B2 (en) 2005-02-28 2019-12-31 Huawei Technologies Co., Ltd. Method and system for exploring similarities
US11789975B2 (en) 2005-02-28 2023-10-17 Huawei Technologies Co., Ltd. Method and system for exploring similarities
US11709865B2 (en) 2005-02-28 2023-07-25 Huawei Technologies Co., Ltd. Method for sharing and searching playlists
US11573979B2 (en) 2005-02-28 2023-02-07 Huawei Technologies Co., Ltd. Method for sharing and searching playlists
US11468092B2 (en) 2005-02-28 2022-10-11 Huawei Technologies Co., Ltd. Method and system for exploring similarities
US11048724B2 (en) 2005-02-28 2021-06-29 Huawei Technologies Co., Ltd. Method and system for exploring similarities
US10860611B2 (en) 2005-02-28 2020-12-08 Huawei Technologies Co., Ltd. Method for sharing and searching playlists
US10614097B2 (en) 2005-02-28 2020-04-07 Huawei Technologies Co., Ltd. Method for sharing a media collection in a network environment
US10019500B2 (en) 2005-02-28 2018-07-10 Huawei Technologies Co., Ltd. Method for sharing and searching playlists
US20110271116A1 (en) * 2005-10-10 2011-11-03 Ronald Martinez Set of metadata for association with a composite media item and tool for creating such set of metadata
US8965950B2 (en) * 2007-06-18 2015-02-24 Microsoft Corporation Decoupled mechanism for managed copy client applications and e-commerce servers to interoperate in a heterogeneous environment
US20080313270A1 (en) * 2007-06-18 2008-12-18 Microsoft Corporation Decoupled mechanism for managed copy client applications and e-commerce servers to interoperate in a heterogeneous environment
US10824322B2 (en) 2010-01-11 2020-11-03 Apple Inc. Electronic text manipulation and display
US20130218729A1 (en) * 2010-01-11 2013-08-22 Apple Inc. Electronic text manipulation and display
US20130179984A1 (en) * 2010-05-21 2013-07-11 Pratyush Kumar method for controlling the execution of an application on a computer system
US9767524B2 (en) 2011-08-09 2017-09-19 Microsoft Technology Licensing, Llc Interaction with virtual objects causing change of legal status
US9038127B2 (en) * 2011-08-09 2015-05-19 Microsoft Technology Licensing, Llc Physical interaction with virtual objects for DRM
US20130042296A1 (en) * 2011-08-09 2013-02-14 Ryan L. Hastings Physical interaction with virtual objects for drm
US20150269360A1 (en) * 2014-03-18 2015-09-24 Fujitsu Limited Control method and system
US11379562B2 (en) * 2019-09-09 2022-07-05 Servicenow, Inc. Remote software usage monitoring and entitlement analysis
US20220350864A1 (en) * 2019-09-09 2022-11-03 Servicenow, Inc. Remote software usage monitoring and entitlement analysis
US11693930B2 (en) * 2019-09-09 2023-07-04 Servicenow, Inc. Remote software usage monitoring and entitlement analysis

Also Published As

Publication number Publication date
MXPA03011044A (en) 2004-06-25
ES2254682T3 (en) 2006-06-16
KR20040006004A (en) 2004-01-16
US20150088768A1 (en) 2015-03-26
US20020184155A1 (en) 2002-12-05
US6754642B2 (en) 2004-06-22
WO2002098041A3 (en) 2003-06-26
US20040162784A1 (en) 2004-08-19
EP1346307A4 (en) 2004-07-28
JP2004528661A (en) 2004-09-16
EP1346307B1 (en) 2005-12-07
DE60207812T2 (en) 2006-07-20
KR100702788B1 (en) 2007-04-03
ATE312382T1 (en) 2005-12-15
DE60207812D1 (en) 2006-01-12
EP1346307A2 (en) 2003-09-24
WO2002098041A2 (en) 2002-12-05

Similar Documents

Publication Publication Date Title
US8001053B2 (en) System and method for rights offering and granting using shared state variables
US8447697B2 (en) Rights offering and granting
US20110247077A1 (en) System and Method for Rights Offering and Granting Using Shared State Variables
US8078542B2 (en) System and method for managing transfer of rights using shared state variables
US7206765B2 (en) System and method for supplying and managing usage rights based on rules
US20100275270A1 (en) Method and apparatus for managing the transfer of rights
US20040039704A1 (en) System and method for supplying and managing usage rights of users and suppliers of items
AU2002312351A1 (en) Method and apparatus managing the transfer of rights
WO2004109450A2 (en) System and method for supplying and managing usage rights associated with an item repository
JP2016129052A (en) Function determination device
KR100626969B1 (en) Rights offering and granting
WO2006041462A2 (en) System and method for rights offering and granting using shared state variables
TWI232392B (en) Rights offering and granting
JP4932058B2 (en) Method and apparatus for transferring rights associated with content
JP4898966B2 (en) Method for offering and granting rights using shared state variables
AU2002305819A1 (en) Rights offering and granting
WO2006041461A1 (en) System and method for managing transfer of rights using shared state variables

Legal Events

Date Code Title Description
AS Assignment

Owner name: CONTENTGUARD HOLDINGS, INC., DELAWARE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NGUYEN, MAI;WANG, XIN;CHEN, EDDIE J.;AND OTHERS;SIGNING DATES FROM 20050207 TO 20070202;REEL/FRAME:026501/0500

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION