US 7,028,009 B2Grant
Method and apparatus for distributing enforceable property rights
Issue Date:2006-04-11
•75 Claims
•5 Drawing Sheets
Abstract
An enforceable property right and a system for controlling the manner of use of an item in accordance with usage rights. The enforceable property right includes an item ticket having a security mechanism incorporated therein and specifying an item for which the item ticket can be redeemed and a license associated with the item ticket. The license includes usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking said security mechanism.
Metadata
Assignee
- ContentGuardiHoldings, Inc.
Inventors
- Xin Wang
- Bijan Tadayon
- Thomas DeMartini
- Michael Raley
- Guillermo Lao
- Eddie Chen
- Charles P. Gilliam
Application Information
Application Number:US 10/159,272
Filing Date:2002-06-03
Priority Date:2001-01-17
Art Unit:3621
Classifications
IPC:
G06F17/60
Patent Drawings (5 sheets)
Description
Related Application Data
[0001] This application claims benefit from U.S. provisional application Ser. Nos. 60/331,625 filed on Nov. 20, 2001, 60/296,117, filed on Jun. 7, 2001, 60/296,118 filed on Jun. 7, 2001, and 60/296,113 filed on Jun. 7, 2001, the disclosures of which are incorporated herein by reference. This application is a continuation-in-part of copending application Ser. No. 10/046,695 filed on Jan. 17, 2002, which claims benefit of U.S. provisional application Ser. No. 60/261,753 filed on Jan. 17, 2001, the disclosures of which are also incorporated herein by reference.
Copyright Notice
[0002] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Background
[0003] 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 disclose DRM systems addressing these issues.
[0004] For example, 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 of the content such as, viewing only, use once, distribution, and the like. Usage rights can be contingent on payment or satisfaction of other conditions and the variables.
[0005] As noted above, it is known to control the use and distribution of digital content, i.e. documents or other information that can be rendered by a computer or other device, using usage rights and conditions. This permits digital content to be distributed in a flexible manner while protecting the rights of the content owner and permitting the content owner, and others adding value to transactions, to produce a revenue stream from the distribution. However, tangible items, such as goods and services. Cannot be distributed in such a flexible manner.
[0006] It is known to utilize auctions, reverse auctions, aggregation mechanisms, and other distribution models to distribute goods and services in a more flexible manner. For example, U.S. Pat. No. 5,897,620 discloses a system for matching a destination and unspecified-time with an airline flight to permit airlines to fill otherwise empty seats. However, the system disclosed in this patent merely matches a traveler with an airline ticket and does not permit the flexible distribution of various services and goods.
[0007] U.S. Pat. No. 6,041,308 discloses a system for encouraging buyers to submit Conditional Purchase Offers (CPOs) to a CPO management system for a desired product. The CPO management system processes each received CPO to determine whether one or more sellers are willing to accept a given CPO. While this system can be applied to more diverse goods and services, the system also is merely a mechanism for matching buyers to sellers.
[0008] Notwithstanding new business models and approaches, such as those discussed above, to selling various goods and services, the sale and exchange of goods and services still relies on legal theories and relationships for enforcing behavior. For example, the parties to each transaction ultimately have to agree, either directly or indirectly, on the parameters for delivering the goods and services, such as price, quantities, the item identity and the like. Accordingly, trade of goods and services is restrained by legal and relationship issues.
Summary of the Invention
[0009] A first aspect of the invention is an enforceable property right for use within a system for controlling the manner of use of an item in accordance with usage rights. The property right comprises an item ticket specifying an item for which the item ticket can be redeemed, the ticket having a security mechanism incorporated therein and a license associated with the item ticket. The license includes usage rights specifying a manner of use for redeeming the item ticket and means for unlocking said security mechanism.
[0010] A second aspect of the invention is system for enforcing property rights in items by controlling the use of the items in accordance with usage rights. The system comprises a license device operative to associate a license with an item ticket specifying an item for which the item ticket can be redeemed and having a security mechanism incorporated therein. The license includes usage rights specifying a manner of use for redeeming the item ticket and conditions for exercising the manner of use. A security component is operative to enforce the license and unlock the security mechanism when the conditions are satisfied.
[0011] A third aspect of the invention is a method for enforcing a property right within a system for controlling the manner of use of an item in accordance with usage rights. The method comprises parsing a license associated with an item ticket specifying an item for which the item ticket can be redeemed and having a security mechanism incorporated therein. The license includes usage rights specifying a manner of use for redeeming the item ticket and conditions for exercising the manner of use. The method also comprises determining if the conditions are satisfied and unlocking the security mechanism if the conditions are satisfied.
Brief Description of the Drawing
[0012] The invention is described through a preferred embodiment, examples, and the attached drawing in which:
[0013] FIG. 1 is a block diagram of a computer architecture of the preferred embodiment of a distribution system;
[0014] FIG. 2 is a schematic illustration of a rights label in accordance with the preferred embodiment;
[0015] FIG. 3 is a schematic illustration of a license in accordance with the preferred embodiment; and
[0016] FIG. 4 is a schematic illustration of a ticket in accordance with the preferred embodiment.
Detailed Description
[0017] A rights management system can be utilized to specify and enforce property rights to specific items, such as content, goods, services, or other items. Applicants have developed the concept of an “enforceable property right”, i.e., a right to use a specified item in accordance with usage rights associated with the item. The phrase “usage rights” as used herein refers to a declarative specification of a manner of use that is identifiable and enforceable through a software mechanism. FIG. 1 illustrates system 10 that can be used in connection with the preferred embodiment. System 10 includes a user activation module, in the form of activation server 20, that issues public and private key pairs to users in a protected fashion, as is well known. During an activation process, some information is exchanged between activation server 20 and client environment 30, a computer or other device associated with a user, for example, and client component 60 is downloaded and installed in 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 any necessary engine for parsing or rendering item ticket 42. Item ticket 42 specifies a specific item as described below.
[0018] Rights label 40 is associated with item ticket 42 and specifies usage rights and possibly corresponding conditions that can be selected by an end-user. License Server 50 manages the encryption keys and issues licenses 52 for exercise of a property right in the manner set forth below. Licenses 52 embody the actual granting of usage rights to an end user based on usage rights selected from rights label 40. For example, rights label 40 may include usage rights for redeeming item ticket 42 for an item upon payment of a fee of five dollars and redeeming or distributing item ticket 42 upon payment of a fee of ten dollars. Client component 60 interprets and enforces the usage rights that have been specified in license 52.
[0019] FIG. 2 illustrates rights label 40 in accordance with the preferred embodiment. Rights label 40 includes plural rights offers 44. Each rights offer 44 includes usage rights 44a, conditions 44b, and ticket specification 44c. Ticket specification 44c can include any mechanism for referencing, calling, locating, or otherwise specifying item ticket 42 associated with rights offer 44.
[0020] FIG. 3 illustrates license 52 in accordance with the preferred embodiment. License 52 includes a unique license ID 52a and grant 52b including usage rights, a principal, conditions, state variables, and a ticket specification designating an associated ticket 42. License 52 also includes digital signature 52c including any cryptographic keys or the like for unlocking item ticket 42.
[0021] Usage rights, specify manners of use. For example, a manner of use can include the ability to use an item in a specified way for a specified period of time, to buy the item for a specified period of time, or the like. Usage rights can also be bundled. Further, usage rights can specify transfer rights, such as distribution rights and can permit granting of usage rights to others or the derivation of usage rights. Such usage rights are referred to as “meta-rights”. Meta-rights are the rights that one has to manipulate, modify, and/or derive other 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.
[0022] Often, conditions must be satisfied in order to exercise the manner of use in a specified usage 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. As will become apparent below, in the preferred embodiment, some conditions must be satisfied in order to render item ticket 42 or otherwise convert item ticket 42 into a form that is redeemable for the item. Other conditions can be expressed on ticket 42 in redeemable form. Such conditions are referred to as “post license” conditions below.
[0023] 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 or another device, based on identification mechanisms in license 52 and ticket 42. Further, the value of state variables can be used in a condition. For example, a usage right can be the right to redeem item ticket 42 for specified goods and a condition can be that the usage right can be exercised three times. Each time the usage right is exercised, the value of the state variable is incremented. In this example, when the value of the state variable is three, the condition is not longer satisfied and ticket 42 cannot be redeemed. Another example of a state variable is time. A condition of license 52 may require that item ticket 42 is redeemed within thirty days. A state variable can be used to track the expiration of thirty days. Further, the state of a usage 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.
[0024] Item ticket 42 can be prepared with document preparation application 72 installed on computer 70 associated with the distributor of an item, a content service provider, or any other party. Preparation of item ticket 42 consists of specifying the rights and any conditions or state variables values under which item ticket 42 can be redeemed. Rights label 40 is associated with item ticket 42 and item ticket 42 with is protected with some crypto algorithm or other mechanism for preventing processing or rendering of item ticket 42. A rights language such as XrML™ can be used to specify the rights and conditions in and state variables rights label 40. However, the rights and conditions can be specified in any manner. Accordingly, the process of specifying rights refers to any process for associating rights with a ticket. Rights label 40 associated with item ticket 42 and the encryption key used to encrypt item ticket 42 can be transmitted to license server 50.
[0025] Item ticket 42, with the security mechanism unlocked, can be a human readable or computer readable coupon, a code, a document, or the like. Accordingly, the phrase “item ticket” as used herein, refers to any tangible or intangible indication of an item. Ticket 42 specifies one or more items and thus usage rights and conditions can be associated with any item including, objects, classes, categories, and services, for which use, access, distribution, or execution is to be controlled, restricted, recorded, metered, charged, or monitored in some fashion. Item ticket 42 and license 52 thus define a property right. In the preferred embodiment, item ticket 42 can be linked to the item through an item reference. The term “linked” as used herein refers to any type of association, such as a description, a pointer, or the like. For example, the ticket can include a unique code associated with an item through a database record. When the code is presented to a vendor, the database is searched and the corresponding item can be delivered. Item ticket 42 can also include a human readable description of the item and any post license condition not yet satisfied. For example, if a condition in license 52 is that item ticket 42 must be redeemed at a certain location or time, that condition can be parsed and transferred to item ticket 42. As illustrated in FIG. 4 , item ticket 42 includes item reference 42a to specify the item and post license conditions 42b.
[0026] A typical workflow for DRM system 10 is described below. A user operating within client environment 30 is activated for receiving item ticket 42 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 license 52.
[0027] Usage rights, conditions, and state variables of license 52 can be stored together with item ticket 42 or otherwise associated with item ticket 42. For example item ticket 42 can include a reference to usage rights stored elsewhere. When a user wishes to obtain a specific enforceable property right to an item, the user makes a request for item ticket 42 specifying the item through item reference 42a. For example, a user might browse a Web site running on Web server of vendor 80, using a browser installed in client environment 30, and request an item corresponding to item ticket 42, i.e. an item specified in item reference 42a of item ticket 42. The user can examine rights offers 44 in rights label 40 associated with item ticket 42 and select the desired usage rights and conditions. During this process, the user may go through a series of steps possibly to satisfy conditions of the usage rights including a fee transaction 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, vendor 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 item ticket 42 and Web server 80 downloads both item ticket 42 and the license 52. As noted above, license 52 includes usage rights and conditions selected from rights label 40 of item ticket 42 and can be downloaded from computer 70 associated with a vendor, distributor, or other party. Keep in mind that item ticket 42 is secured, through encryption or another security mechanism and can only be rendered or otherwise accessed through license 52 which includes a mechanism for unlocking ticket 42. Mechanisms for controlling access to documents are well known.
[0028] Client component 60 in client environment 30 will then proceed to interpret license 52 and allow rendering or other access of item ticket 42 based on the rights and conditions specified in license 52. The interpretation and enforcement of usage rights and related systems and techniques are well known. The steps above may take place sequentially or approximately simultaneously or in various sequential order. For example, if license 52 is for purchase of an item at a price of ten dollars within one month of the issue date of item ticket 42, client component 60 could render item ticket 42a as a displayable or printable coupon for such a purchase expiring in one month the price an expiration data are post license conditions in this example. In other words, such conditions can be set forth on the rendered, or otherwise unlocked, form of item ticket 42 and can be discerned upon redemption of item ticket 42.
[0029] System 10 addresses security aspects of tickets 42. In particular, 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 license 52 can be trusted. In other words, application 60 has the capability to verify and validate signature 52c, such as a cryptographic signature, or other identifying characteristic of license 52 in a known manner. Of course, the example above is merely one way to effect a rights management system. For example, license 52 and item ticket 42 can be distributed from different entities. Clearinghouse 90 can be used to process payment transactions and verify payment prior to issuing a license. Further, various workflows can be used and various parties can be involved. Also, various devices and architectures can be used to accomplish the workflows.
[0030] As noted above, a distributor or other party associates rights label 40, with item ticket 42. Rights label 40 can be registered with clearinghouse 90 and stored in a repository, such as a memory device associated with clearinghouse 90. Item ticket 42 can be stored in a ticket repository, such as a storage device associated with the distributor. Alternatively, rights label 40 and item ticket 42 can be stored on the same device and can even be in a single common file.
[0031] The private key, or other identification information, is issued to the user upon purchase of license 52. Payment for the item is passed from the user to license server 50 or other party by way of clearinghouse 90 which collects requests from the user and from other users who wish to purchase a property right in specific items. Clearinghouse 90 can also collect payment information, such as debit transactions, credit card transactions, or other known electronic payment schemes, and forward the collected payments as a payment batch to the ultimate provider of the item. Of course, clearinghouse 90 may retain a share of the payment and the distributor may retain a portion of the batch payment from and forward a payment to the item provider. Clearinghouse 90, determines the payment made to parties in the revenue stream of the item. Clearinghouse 90 can serve as transaction aggregator which functions to aggregate plural transactions over a period of time, and charge parties in an appropriate manner to reduce the accounting overhead.
[0032] For example a user could request item ticket 42 corresponding to a desired item through Web server 80 and provide information, such as credit card and charge authorization information, personal information, or the like to permit clearinghouse 90 to satisfy conditions specified in license 52 associated with item ticket 42. Authorization identification, such as a private key, obtained from activation server 20 will also be submitted. Significantly license 52 permits item ticket 42 to be decrypted, or otherwise allows the security mechanism thereof to be unlocked, and used in accordance with the usage rights in license 52.
[0033] As noted above item ticket 42 can specify any item and, when combined with usage rights selected from rights label 40 and embodied in license 52, represents an enforceable property right that can be exercised by redeeming item ticket 42. Redemption of item ticket 42 can include presenting a rendered coupon or code to a vendor electronically or physically. However, redemption of item ticket 42 can take various forms and include various processes. Therefore, the term “redeem,” as used herein, refers to any process or mechanism by which item ticket 42 is converted to access an item. Several example of enforceable property rights are set forth below.
[0034] One example relates to a stock (or other market) exchange. For example, the property right can be the right to buy or sell a security in advance or at a threshold. Item ticket 42 can specify 1000 shares of stock of a specific company in item reference 42a. The right to by the stock between two thresholds, at a specified future time, or the like can be specified by usage rights and conditions. Item ticket 42 could also specify a margin call, the ability to change the type of stock (common/preferred), or the ability to convert stock options to regular stock. Also, there may be usage rights associated with the stock during the bankruptcy proceedings, as to who can liquidate first and in what manner. The condition of “during bankruptcy” and the status of other parties, such as creditors, can be expressed as state variables.
[0035] In an example related to real estate, a property right to real property can be expressed as, for example, joint-tenant or tenant-in-common with the option to convert to other options and with change of the percentage of the ownerships, and designation of the survivorship option. All of these ownership rights can be expressed as usage rights and the real property can be specified in item reference 42a of item ticket 42.
[0036] Further item reference 42a of item ticket 42 can specify professional services. For example, a user can buy the right to visit a specific dentists' office, or one of plural dentists' office in an association, for a period of 1 year, while paying only a fixed or variable co-payment for each visit, up to a maximum amount. Or, item ticket 42 can specify a lawyer or an accountant and usage rights and conditions can specify a period of time, a fixed number of times, or a specific project or issue to which use of the item is limited. Item reference 42a can specify the right for services offered by an organization, in advance, including the rights associated with the intellectual property, such as patents, copyright, and trademarks. This can apply to software programmers, customer service representative, training services, or other technical or non-technical services.
[0037] A user can obtain a property right and later sell that property right to a third-party, if such transfers are authorized by usage rights of license 52 associated with item ticket 42. This impacts mobility and liquidity to different types of assets, making it possible to expand the market concept to include property rights to any item. Another example of property right is where item ticket 42 defines a coupon, gift-certificate, rain-check, exchange certificate, return, authorization or the like, where rights and conditions of license 52 are associated with the redemption thereof. For example, a coupon can be rendered only after the conditions are satisfied. Alternatively, post license conditions can be expressed in the rendered coupon.
[0038] Another example relates to any type of financial account or transaction such as certificates of deposit, checking accounts, wires, e-mails, fund transfers, currency exchanges, locks on current or future interest rates, points or other fees paid for a loan, bonds, loans, secondary loans, and stocks (any of which may have one or more attributes such as maturity dates or deadlines). Item reference 42a can specify any of these items and license 52 can specify rights and conditions associated with the access to these item.
[0039] Another example includes the right for future tangible or intangible things such as books (in printed or electronic form) or music (on physical media electronic form). The usage rights and conditions of license 52 limit the right to during or after a period of time or for a predetermined number of units, such as units of CDs or books.
[0040] In another example, the property right includes the rights expressed for a will or a trust for the distribution of property or other assets, or for the provision of rights, services or benefits for persons, entities and other things that are specified by item reference 42a. Access can be restricted to certain parties, or in any other way, by usage rights and conditions.
[0041] The property right can include online services. For example, diet and vitamin calculations (customized based on an individual's characteristics and data), stock quotations, interest rate and mortgage payment calculations, credit rating, background checks, loan application and approval, on-line banking, investment advice, translation services, graphic design, advertisement services, currency conversion and exchange, and job placement can all be specified by item reference 42a of item ticket 42. In such a case, item ticket 42 can include an access code to the online service or the like that is usable only after conditions of license 52 have been satisfied.
[0042] In the preferred embodiment, a provider of items, or another specified party, specifies the conditions for access to the items. A user wishing to obtain a property right in the item has to satisfy those conditions. This concept works equally well, regardless of the direction or order in which information moves. For example, a user can supply conditions to the supplier in license 52 and the supplier has to satisfy those conditions to make a sale. Furthermore, a partial satisfaction of conditions could result in a property right or other result, which may be the same or different when compared to full satisfaction of the conditions.
[0043] The item can be access to a Web site. As a condition of access to the Web site, license 52 can include the condition that the user must be located in a specific geographical area (for example in the United States). This is useful for localization of the web site, for example, in terms of language translation, customization, or other aspects at the property right, including local customs, news, culture, hobbies, local sport news, local news makers, local industry, local merchandise, or local advertisements. For example, if the user is located in the United States, the language will be English and American versions of spelling and dialect will be used. Further advertisements can be based on American taste, season, or political climate at that moment. Localization increases the appeal of the Web site, facilitates provision of appropriate property rights and generally, improves customer satisfaction and traffic of the web site or volume of sale.
[0044] Another benefit is that the property owner may want to release a specific property right in the United States first, and three months later in Europe or another part of the world. This is common in movie industry, where the different releases in different geographical areas are restricted based on a time schedule designed to give maximum benefit to the owner or other recipient of revenue. The release dates and/or time tables can all be incorporated into a rights template, so that the assignment or modifications of the time table would be easy for the content owner, and keeping track of the various times can be done automatically, without further human intervention.
[0045] Another example is when a “Web crawler” collects data from a Web site. The Web master or other authority in control of the Web site could, as a condition of access to the Web site, require the crawler to access or request the access after midnight when the Web site traffic is at a minimum, and therefore, loads are reduced. Additionally, the web site could impose varying conditions on the ability or right of the Web crawler to access the site, such as by specifying that the access will time out after a certain period of time, if access is obtained during peak hours.
[0046] Furthermore, license 52 can specify how to gain access to a property right. For example, one can specify how a user may distribute content or other items (for example, by super-distribution). This gives more control to the content owner, as to where and by what method the distribution is conducted. The geographical location restriction is one condition. The parameters of super-distribution could also be specified by the content owner as conditions, to further limit the method of distribution for example of expiration date, the number of copies, and the people forbidden to get a copy (such as unfriendly customers, or known hackers) can be specified as conditions.
[0047] Or, one user may want to share their personal calendar with others. Access to the calendar can be the item specified in item reference 42a which can include an access code. However, as a condition of license 52, the user may require the accessing party to do a specific task. For example, a condition may require the user to open one specific file or share their own calendar. The calendar can be used and edited by all some of the others, who have the right to input, modify, or edit, as expressed in usage rights of license 52. Some of the parties may have the right to view-only, or view-and-input-only, with no modification rights. The calendar can keep track of conflict of schedules for two or more people, and automatically notify the conflicting parties or all of the parties about the conflict. The calendar can also highlight the unavailable days, when one or more parties are out of town or unavailable for other reasons. The calendar can also suggest some days or hours that the calendar is relatively empty, or for a specified parties, find the common acceptable dates or hours, based on the input by one or more users.
[0048] Another example of a property right that can be controlled is access to a print-shop service, where one can specify some policy to restrict the access of users to printing services specified by item ticket 42. In other words, access to the service is specified in item reference 42a and restrictions are expressed as usage rights and conditions of license 52. For example, the user may send a large file to be printed by the print shop, for a fee. However, as a way of managing job orders, smaller files get printed sooner, i.e., have a higher priority. The size of the files within a predetermined time frame can be compared and ordered for printing purposes. In other words, a condition of license 52 is that no smaller files are queued for printing. The status of other files qued for printing can be tracked as a state variable. However, if a job must be printed before a deadline, then the length of the printing process is estimated, and the job schedule is modified to make the deadline. This out-of-order prioritization can be signified by a flag or a variable (or set of variables/parameters), i.e., which contains the order of priority, the information about the deadline, or the like. In the case of the conflict of the schedules or having not enough time to satisfy all the deadlines, the jobs in a class with a higher priority will be handled before the other jobs. Thus, the size of a file to be printed is important only within a specific class of priority.
[0049] Further, upon payment of a fee or satisfaction of another condition, a print job might jump the queue, or color jobs and black and while jobs could be routed to different printers, or the user may specify the priority he desires based on the fee paid. For assignment of print jobs, priority assignment, class of print jobs, negotiating the prices and fees, and the moving of priorities, one can assign rights to customers and print jobs, and express those rights in license 52.
[0050] As a service provider, one can set conditions for quality in rights lable 40. For example, lower quality image can be purchased for a lower fee or a slower delivery can be granted for a lower fee. For example, the resolution can be corresponded to the price, based on a table, a formula, a function, or values on a curve. This applies to variations other than quality such as, speed or timing, and the variation could be based on conditions other than fee paid. Each of these services or items can be specified in item reference 42a.
[0051] Another possible property right is the authority to change or set the time for a computer or other system. In such an example, the condition is the identification of the person as the system administrator. Thus, the identification can be based on the role of the individual, which can be established by a smart card, ID, or the like. Such a role-based model makes it easier to effect a change in the right assignment or a change in the position of the individuals.
[0052] Further applying usage rights to items is very useful for situations in which the item provider is not the same as the item seller, such as for air fares and car rentals in which a travel agent or other party often sells the item. For example, one can buy one or more round-trip tickets between Boston and Chicago from a Web site, such as an auction site, a reverse-auction site, airline direct sales, a travel agency, an individual having the property right to transfer or resell the tickets, a clearinghouse, a reseller, or a distributor. The destination, the location, or both could be variables. For example, an item specified in item reference 42a of item ticket 42 can an airline ticket from Boston to any city in the Eastern part of the United States, any city within 2000 miles of Boston, or to any city in the continental United States. The usage rights of license 52 can include the right to exchange the ticket for another ticket within the European continent provided that condition, such a payment of a fixed or variable fee is paid. In addition, the usage rights can include the right to convert the ticket to cash, points, coupons, or the like, for purchase of merchandise or services from affiliated retailers. For busy seasons (predetermined time windows), the conditions may require an extra fee for a given property right. The predetermined times can be tracked as state variables.
[0053] As another example, item ticket 42 can specify that the user can rent a car for six days in Boston from any one of several car rental companies. The rental companies can have a contract with clearinghouse 90 to recognize item ticket 42 as valid and item reference 42a can specify the car rental. Usage rights and conditions can specify mileage limits, drop off locations, car size, car manufacturer, pick-up locations, or various equipment in the car as additional features. The item can be a rental of a car for six days within the month of August, as an example. The owner may not know exactly when or where they may be exercising the property right.
[0054] The concept of inventory of extra seats, for example, surplus tickets for movie seats, airline seats, or rental cars, in which there is not necessarily a one-to-one relationship, can also be adapted to distribution as a property right of an item with associated usage rights. For example, one can buy a property right to a movie ticket from a Web site, and exercise the property right by redeeming the corresponding item ticket 42 at a movie theater which accepts tickets 42 and has a relationship with the distributor Web site (similar to the relationship that MasterCard™ Corporation has with various issuing banks, with respect to customers and card holders, or even similar to a more centralized control, such as the one by American Express™ Cards). Thus, in general, there might be more than one type of distributors of rights, issuing entities, contract providers, or types of tickets 42, and each may have their own logos, terms, conditions, and associations, with possible reciprocal acceptances across boundaries of associations, for maximizing the acceptance areas and ease of use for customers, similar to ATM cards and banks. After honoring tickets 42, the theater owner can aggregate tickets 42 each day (for example), and obtain reimbursement.
[0055] Further, tickets or seats for events with undetermined dates or specifications can be expressed as items of property rights. Also, the item of the property right can be hotel rooms and other reserved commodities, whereby the reservations, become very liquid and exchangeable by permitting transfer of license 52 through usage rights or meta-rights.
[0056] Returning to the embodiment illustrated in FIG. 1 , clearinghouse 90 can have a contract with three car rental companies as vendors 80, from which a user rents a compact car for 6 days in August, to be used in New York City. Item ticket 42 will be redeemable, to thereby exercise the property right of the license, from any of the three car rental companies. Usage rights of license 52 associated with item ticket 42 can specify various aspects of the property right such as; any six days in August of the current year in a specific city, the ability to auction or otherwise transfer the property right, the ability to exchange the city for a fee, or the ability to use part of the property right to obtain cash.
[0057] The flexibility in trading property rights permits various item to be extended into an open market for trading or exchanging property rights (similar to the NASDAQ stock market). In such a market rights become very liquid, similar to cash, stocks, bonds, or certified checks. Property rights can be traded as commodities or objects, with certain predetermined or variable values, at the current moment or in the future. Accordingly, associating rights and conditions with items, through the mechanism of license 52 and item ticket 42, provides a completely new dimension to trading of various goods and services.
[0058] Internet and computer networks provide a very fast and convenient way for the distribution of property rights to various items. However, distribution of some items may be strictly limited as specified by the item owner or as desired by the user. One example is a property right to view or use personal or private data. It may be desirable to restrict the manner of distribution, where it is distributed, who can use it, or who should not be able to inspect, copy, distribute, or use it. All of these restrictions can be specified as conditions and usage rights in license 52.
[0059] One can treat access to private information as an item, therefore, one can use rights management solutions to safeguard the private data. For example, a user may give their private personal data to a Web site, and the Web site may sell the data to others only if the user has given such a property right to the Web site. One parameter of the property right, expressed as a condition, can be the tolerance level of the content owner, as can be quantified, and be represented by an integer, a descriptive name, or other means. This tolerance value may correspond to geographical distribution limits, a list of authorized users, a list of unauthorized people (such as known hackers or infamous web sites), pre-defined levels of trust, levels of security for different web sites, pre-defined levels of privacy for different web sites, or other parameters or conditions. The parameters can be static or dynamically determined and can be tracked as state variables.
[0060] Web sites or other distribution sites can be rated by individuals, based on votes, or can be rated by commercial or non-profit organizations which rate the sites based on surprise audits, scheduled audits, and claims or rules set on the site, compared against the criteria of a rating organization. Ratings can be accomplished in any manner. The ratings can be a condition of license 52 to determine if the party can access the information. If there is an unwanted leak of the information to the outside, the liability of the site, in terms of monetary compensations or otherwise, can be stated as a parameter for the calculation of the rating of the web site.
[0061] A condition can be an indication if the content owner is willing to sell their own personal data. For example, license 52 granting access to a network or other service can have, as a condition, the requirement that the user grants permission to sell their personal data. Other conditions can be the price (or other compensation or conditions) set on the personal data. For example, the content owner could get a percentage or a fixed fee (or other benefit such as “airline miles”) for each sale or transaction, of personal data. An aggregation of these micro-amounts can be paid at end of each month or other period, based on the usage rights parameters in the license. This can be done through one clearinghouse or multiple clearinghouses.
[0062] Personal data can be aggregated or averaged for economic, cultural, regional, national, medical or other reasons, in which the individual data for a specific person is not necessarily individually important. In such a case, the identity of individuals typically is not disclosed. The data may be used in the aggregate for any number of purposes, for example for a medical or census purposes by a non-profit or trusted organization. In these situations, conditions could specify the purpose of the collection of data, and usage rights could specify how this data is being used, such as aggregate or average only for example. Yet, another condition could specify which section or part of the collection of personal data is permitted to be used for the purpose. The specification could be done using a user interface, for example, in a template form, with flags specifying each piece of information. For example, for a medical study, permission may be granted to access the age, height, and weight of the person, but not the name, income, credit card number, credit history, or address. For a census or insurance study, the information accessible might include street address or zip codes, along with the number of the accidents in the past six months or the number of cars owned per household.
[0063] The content owner can specify that license 52 allows the data to be exchanged in a clearinghouse with another data collection entity, to average, aggregate, or simply sell or exchange the data. The content owner can verify the identity of the acquirer of the data, and the associated level of trust in the new owner, as conditions, on a case by case
[0064] Licenses and ticket redemption can be tracked as state variables. As a user, one has to enter personal data only once and then, can maintain or keep track of the data. The user or other designated party can be informed of how the data, and which part of the data, is used. The user can be notified where the data is, by a tracking means such as sending e-mail messages back to the user. The user can also receive renumeration from the sale or use of personal data.
[0065] An item consisting of personal information can be divided into different components, for which different values of privacy condition can be assigned by the owner or another authorized person. Of course, the personal information could have just one component. Privacy parameters can be on any kind of a scale. For example, the typical scale for privacy parameter can be between 0 and 1. Zero signifies “no privacy” (non-conditional access to all), and one signifies “absolute privacy” (no access under any conditions). A set of rules can define the scale for the privacy parameter. Different constraints, conditions, fees, and rights can be associated with privacy parameters and each parameter, for a given component of personal information. The owner of content, an independent trusted organization, or someone else can set a trust ratings for different entities or persons, and trust ratings can be used as conditions of access of that entity or persons to particular information associated with a given privacy parameter. Trust ratings can be based on a scale that is similar to the scale for privacy parameters. For example, persons with the highest possible trust ratings can access information with the highest privacy parameters, and those with the lowest trust ratings could access only “no privacy” information. Middle ratings could access corresponding portions of information. Thus, generally, the content has a rating and the viewer or user has a rating, and a condition to access the content is that the two ratings have to correspond. The different parts of the content can also have different ratings, for greater flexibility.
[0066] Usage rights, rights offers, tickets and licenses described herein can be expressed by any language, format, tag set, set of rules, grammar, or formulations, such as the XrML™ language. Further, the various aspects and limitations can be expressed as various combinations of items, principals, and conditions. Consider the following example. A property right that specifies that “Person A can transmit a purchase order of less than X dollars to Company C.” There are many possible ways to express the usage rights and conditions of this license to a property right. Some examples are set forth below. From these examples, it can be seen that a property right can be expressed in various ways. For example, restrictions can be set forth in the usage right, in the item, or as conditions.
- [0067] Example #1:
- [0068] Principal: Person A
- [0069] Item: Company C Purchasing Service
- [0070] Usage Right: Transmit
- [0071] Conditions: type=“Purchase Order”, cost<X
- [0072] Example #2:
- [0073] Principal: Person A
- [0074] Item: Purchase Order
- [0075] Usage Right: Transmit
- [0076] Conditions: recipient=“Company C Purchasing Service”, cost<X
- [0077] Example #3:
- [0078] Principal: Person A
- [0079] Item: Any Goods from Company C
- [0080] Usage Right: Purchase
- [0081] Conditions: cost<X
- [0082] Example #4:
- [0083] Principal: Person A
- [0084] Item: Any
- [0085] Usage Right: Purchase
- [0086] Conditions: recipient=“Company C Purchasing Service”, cost<X
- [0087] Example #5:
- [0088] Principal: Person A
- [0089] Item: Any
- [0090] Usage Right: Spend<$X
- [0091] Conditions: recipient=“Company C Purchasing Service”
- [0092] Example #6:
- [0093] Principal: Person A
- [0094] Item: Purchase Order
- [0095] Usage Right: Transmit to “Company C Purchasing Service”
- [0096] Conditions: cost<X
- [0097] Example #7:
- [0098] Principal: Person A
- [0099] Items: Purchase Order for “Company C Purchasing Service” costing less than $X total
- [0100] Usage Right: Transmit
- [0101] Conditions: none
- [0102] Example #8:
- [0103] Principal: Person A
- [0104] Item: Any
- [0105] Usage/Right: Purchase from Company C
- [0106] Conditions: cost<X
[0107] In general, one can specify how people use or access goods, services or other items through enforceable property rights. The owner item or distributor will have more control over the item and the user can have better management over what property rights are obtained and at what cost. The ability to create an enforceable property right in various items permits the items to be traded in an open market environment. While such an environment is known for commodities and stocks, it previously was not available for other goods and services. The various rights, conditions, items and other indicators can be expressed in any manner and can be stored at the same location or in different locations. For example, the ticket can be stored at one location, such as a user device, and the license can be stored at another location, such as a license server of other device. The various aspects of the preferred embodiment have individual utility and can exist separately. For example, licenses can exist separately from ticket, and each can exist outside of any specific computer architecture or system.
[0108] The system for distributing tickets and creating and enforcing licenses 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 selecting rights and granting licenses can be accomplished in the same device as that used to access and redeem item tickets. 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.
[0109] 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, an item ticket. 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.
[0110] The invention has been described through a preferred embodiment and examples. However, various modifications can be made without departing from the scope of the invention as define by the appended claims and legal equivalents.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed:
1. A computer-implemented system for enforcing an enforceable property right in an item in accordance with usage rights, the system comprising:
a device for electronically generating an item ticket specifying an item for which the item ticket can be redeemed, the item ticket having a security mechanism incorporated therein; and
a device for electronically generating a license associated with the item ticket, the license including usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking the security mechanism,
wherein the license further includes conditions that must be satisfied to activate the unlocking mechanism and exercise the manner of use,
wherein the item ticket includes a description of the item,
wherein the license further comprises usage rights specifying access to information and a condition of the access, and
wherein the condition includes a required security or trust rating for the access to the information.
2. The system of claim 1, wherein the item ticket includes an ID correlated to the item.
3. The system of claim 1, wherein the item ticket includes limitations specified by the license.
4. The system of claim 3, wherein the limitations are expressed in the conditions.
5. The system of claim 1, wherein the security mechanism is based on encryption.
6. The system of claim 1, wherein the item comprises tangible or non-tangible goods.
7. The system of claim 1, wherein the item comprises tangible or non-tangible services.
8. The system of claim 1, wherein the license includes a specification of the item ticket.
9. The system of claim 1, wherein the item comprises tangible or non-tangible information.
10. The system of claim 1, wherein the license further includes post-license conditions that do not need to be satisfied to activate the security mechanism and wherein the unlocking mechanism permits a specification of the item and the post-license conditions to be rendered.
11. The system of claim 1, wherein the license further includes state variables.
12. The system of claim 1, wherein the unlocking mechanism is operative to permit the item ticket to be rendered as a human readable description.
13. The system of claim 1, wherein the unlocking mechanism is operative to permit the item ticket to be rendered as a computer readable code.
14. The system of claim 1, wherein the usage rights include meta-rights which permit rights in the item to be granted to downstream parties.
15. The system of claim 1, wherein the item comprises a financial instrument.
16. The system of claim 1, wherein the item comprises a legal document.
17. The system of claim 1, wherein the item comprises real estate.
18. The system of claim 1, further comprising:
a license device operative to associate the license with the item ticket; and
a security component operative to enforce the license and unlock the security mechanism, if the conditions are satisfied.
19. The system of claim 18, wherein the security component comprises a client component in a user device, and an activation device for providing at least a portion of the client component.
20. The system of claim 18, further comprising a vendor device for permitting a user to select the item and the usage rights to be incorporated into the license generated by the license device.
21. The system of claim 1, further comprising:
means for parsing the license;
means for determining, if the conditions are satisfied; and
means for unlocking the security mechanism, if the conditions are satisfied.
22. The system of claim 1, wherein the security mechanism is based on encryption, and the mechanism for unlocking is based on decryption.
23. The system of claim 1, wherein the system is implemented using one or more hardware and/or software devices.
24. A computer-implemented system for enforcing an enforceable property right in an item in accordance with usage rights, the system comprising:
a device for electronically generating an item ticket specifying an item for which the item ticket can be redeemed, the item ticket having a security mechanism incorporated therein; and
a device for electronically generating a license associated with the item ticket, the license including usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking the security mechanism,
wherein the license further includes conditions that must be satisfied to activate the unlocking mechanism and exercise the manner of use,
wherein the item ticket includes a description of the item,
wherein the item comprises an online service, and
wherein the license further comprises usage rights specifying access to the online service and a condition of the access.
25. The system of claim 24, wherein the condition includes a required security or trust rating for the access to the online service.
26. A computer-implemented method for enforcing an enforceable property right in an item in accordance with usage rights, the method comprising:
electronically generating an item ticket specifying an item for which the item ticket can be redeemed, the item ticket having a security mechanism incorporated therein;
electronically generating a license; and
associating the license with the item ticket, the license including usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking the security mechanism,
wherein the license further includes conditions that must be satisfied to activate the unlocking mechanism and exercise the manner of use,
wherein the item ticket includes a description of the item,
wherein the license further comprises usage rights specifying access to information and a condition of the access, and
wherein the condition includes a required security or trust rating for the access to the information.
27. The method of claim 26, wherein the item ticket includes an ID correlated to the item.
28. The method of claim 26, wherein the item ticket includes limitations specified by the license.
29. The method of claim 28, wherein the limitations are expressed in the conditions.
30. The method of claim 26, wherein the security mechanism is based on encryption.
31. The method of claim 26, wherein the item comprises tangible or non-tangible goods.
32. The method of claim 26, wherein the item comprises tangible or non-tangible services.
33. The method of claim 26, wherein the license includes a specification of the item ticket.
34. The method of claim 26, wherein the item comprises tangible or non-tangible information.
35. The method of claim 26, wherein the license further includes post-license conditions that do not need to be satisfied to activate the security mechanism, and the method further comprises permitting via the unlocking mechanism a specification of the item and the post-license conditions to be rendered.
36. The method of claim 26, wherein the license further includes state variables.
37. The method of claim 26, further comprising permitting via the unlocking mechanism the item ticket to be rendered as a human readable description.
38. The method of claim 26, further comprising permitting via the unlocking mechanism the item ticket to be rendered as a computer readable code.
39. The method of claim 26, wherein the usage rights include meta-rights which permit rights in the item to be granted to downstream parties.
40. The method of claim 26, wherein the item comprises a financial instrument.
41. The method of claim 26, wherein the item comprises a legal document.
42. The method of claim 26, wherein the item comprises real estate.
43. The method of claim 26, further comprising:
associating via a license device the license with the item ticket; and
enforcing the license and unlocking the security mechanism via a security component, if the conditions are satisfied.
44. The method of claim 43, wherein the security component comprises a client component in a user device, and an activation device for providing at least a portion of the client component.
45. The method of claim 43, further comprising:
permitting via a vendor device a user to select the item and the usage rights to be incorporated into the license generated by the license device.
46. The method of claim 26, further comprising:
parsing the license;
determining, if the conditions are satisfied; and
unlocking the security mechanism, if the conditions are satisfied.
47. The method of claim 26, wherein the security mechanism is based on encryption, and the mechanism for unlocking is based on decryption.
48. The method of claim 26, wherein the method is implemented using one or more hardware and/or software devices.
49. The method of claim 26, wherein in the method is implemented using computer readable medium including one or more computer-readable instructions embedded therein configured to cause one or more computer processors to perform the steps of the method.
50. A computer-implemented method for enforcing an enforceable property right in an item in accordance with usage rights, the method comprising:
electronically generating an item ticket specifying an item for which the item ticket can be redeemed, the item ticket having a security mechanism incorporated therein;
electronically generating a license; and
associating the license with the item ticket, the license including usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking the security mechanism,
wherein the license further includes conditions that must be satisfied to activate the unlocking mechanism and exercise the manner of use,
wherein the item ticket includes a description of the item,
wherein the item comprises an online service, and
wherein the license further comprises usage rights specifying access to the online service and a condition of the access.
51. The method of claim 50, wherein the condition includes a required security or trust rating for the access to the online service.
52. A computer readable medium including one or more computer-readable instructions embedded therein for enforcing an enforceable property right in an item in accordance with usage rights and configured to cause one or more computer processors to perform the steps of:
electronically generating an item ticket specifying an item for which the item ticket can be redeemed, the item ticket having a security mechanism incorporated therein;
electronically generating a license; and
associating the license with the item ticket, the license including usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking the security mechanism,
wherein the license further includes conditions that must be satisfied to activate the unlocking mechanism and exercise the manner of use,
wherein the item ticket includes a description of the item,
wherein the license further comprises usage rights specifying access to information and a condition of the access, and
wherein the condition includes a required security or trust rating for the access to the information.
53. The computer readable medium of claim 52, wherein the item ticket includes an ID correlated to the item.
54. The computer readable medium of claim 52, wherein the item ticket includes limitations specified by the license.
55. The computer readable medium of claim 54, wherein the limitations are expressed in the conditions.
56. The computer readable medium of claim 52, wherein the security mechanism is based on encryption.
57. The computer readable medium of claim 52, wherein the item comprises tangible or non-tangible goods.
58. The computer readable medium of claim 52, wherein the item comprises tangible or non-tangible services.
59. The computer readable medium of claim 52, wherein the license includes a specification of the item ticket.
60. The computer readable medium of claim 52, wherein the item comprises tangible or non-tangible information.
61. The computer readable medium of claim 52, wherein the license further includes post-license conditions that do not need to be satisfied to activate the security mechanism, and further comprising computer-readable instructions configured to cause the computer processors to perform the step of permitting via the unlocking mechanism a specification of the item and the post-license conditions to be rendered.
62. The computer readable medium of claim 52, wherein the license further includes state variables.
63. The computer readable medium of claim 52, further comprising computer-readable instructions configured to cause the computer processors to perform the step of permitting via the unlocking mechanism the item ticket to be rendered as a human readable description.
64. The computer readable medium of claim 52, further comprising computer-readable instructions configured to cause the computer processors to perform the step of permitting via the unlocking mechanism the item ticket to be rendered as a computer readable code.
65. The computer readable medium of claim 52, wherein the usage rights include meta-rights which permit rights in the item to be granted to downstream parties.
66. The computer readable medium of claim 52, wherein the item comprises a financial instrument.
67. The computer readable medium of claim 52, wherein the item comprises a legal document.
68. The computer readable medium of claim 52, wherein the item comprises real estate.
69. The computer readable medium of claim 52, further comprising computer-readable instructions configured to cause the computer processors to perform the steps of:
associating via a license device the license with the item ticket; and
enforcing the license and unlocking the security mechanism via a security component, if the conditions are satisfied.
70. The computer readable medium of claim 69, wherein the security component comprises a client component in a user device, and an activation device for providing at least a portion of the client component.
71. The computer readable medium of claim 69, further comprising computer-readable instructions configured to cause the computer processors to perform the step of permitting via a vendor device a user to select the item and the usage rights to be incorporated into the license generated by the license device.
72. The computer readable medium of claim 52, further comprising computer-readable instructions configured to cause the computer processors to perform the steps of:
parsing the license;
determining, if the conditions are satisfied; and
unlocking the security mechanism, if the conditions are satisfied.
73. The computer readable medium of claim 52, wherein the security mechanism is based on encryption, and the mechanism for unlocking is based on decryption.
74. A computer readable medium including one or more computer-readable instructions embedded therein for enforcing an enforceable property right in an item in accordance with usage rights and configured to cause one or more computer processors to perform the steps of:
electronically generating an item ticket specifying an item for which the item ticket can be redeemed, the item ticket having a security mechanism incorporated therein:
electronically generating a license; and
associating the license with the item ticket, the license including usage rights specifying a manner of use for redeeming the item ticket and a mechanism for unlocking the security mechanism,
wherein the license further includes conditions that must be satisfied to activate the unlocking mechanism and exercise the manner of use,
wherein the item ticket includes a description of the item,
wherein the item comprises an online service, and
wherein the license further comprises usage rights specifying access to the online service and a condition of the access.
75. The computer readable medium of claim 74, wherein the condition includes a required security or trust rating for the access to the online service.
Patent Citations (186)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3263158(A) | 1966-07-01 | Janis | Applicant |
| US3609697(A) | 1971-09-01 | Blevins et al. | Applicant |
| US3790700(A) | 1974-02-01 | Callais et al. | Applicant |
| US3798605(A) | 1974-03-01 | Feistel | Applicant |
| US4159468(A) | 1979-06-01 | Barnes et al. | Applicant |
| US4220991(A) | 1980-09-01 | Hamano et al. | Applicant |
| US4278837(A) | 1981-07-01 | Best | Applicant |
| US4323921(A) | 1982-04-01 | Guillou | Applicant |
| US4442486(A) | 1984-04-01 | Mayer | Applicant |
| US4529870(A) | 1985-07-01 | Chaum | Applicant |
| US4558176(A) | 1985-12-01 | Arnold et al. | Applicant |
| US4593376(A) | 1986-06-01 | Volk | Applicant |
| US4614861(A) | 1986-09-01 | Pavlov et al. | Applicant |
| US4644493(A) | 1987-02-01 | Chandra et al. | Applicant |
| US4658093(A) | 1987-04-01 | Hellman | Applicant |
| US4713753(A) | 1987-12-01 | Boebert et al. | Applicant |
| US4796200(A) | 1989-01-01 | Wolfe | Applicant |
| US4817140(A) | 1989-03-01 | Chandra et al. | Applicant |
| US4827508(A) | 1989-05-01 | Shear | Applicant |
| US4868376(A) | 1989-09-01 | Lessin et al. | Applicant |
| US4891838(A) | 1990-01-01 | Faber | Applicant |
| US4924378(A) | 1990-05-01 | Hershey et al. | Applicant |
| US4932054(A) | 1990-06-01 | Chou et al. | Applicant |
| US4937863(A) | 1990-06-01 | Robert et al. | Applicant |
| US4949187(A) | 1990-08-01 | Cohen | Applicant |
| US4953209(A) | 1990-08-01 | Ryder, Sr. et al. | Applicant |
| US4961142(A) | 1990-10-01 | Elliott et al. | Applicant |
| US4975647(A) | 1990-12-01 | Downer et al. | Applicant |
| US4977594(A) | 1990-12-01 | Shear | Applicant |
| US4999806(A) | 1991-03-01 | Chernow et al. | Applicant |
| US5010571(A) | 1991-04-01 | Katznelson | Applicant |
| US5014234(A) | 1991-05-01 | Edwards, Jr. | Applicant |
| US5023907(A) | 1991-06-01 | Johnson et al. | Applicant |
| US5047928(A) | 1991-09-01 | Wiedemer | Applicant |
| US5050213(A) | 1991-09-01 | Shear | Applicant |
| US5052040(A) | 1991-09-01 | Preston et al. | Applicant |
| US5058164(A) | 1991-10-01 | Elmer et al. | Applicant |
| US5103476(A) | 1992-04-01 | Waite et al. | Applicant |
| US5113519(A) | 1992-05-01 | Johnson et al. | Applicant |
| US5136643(A) | 1992-08-01 | Fischer | Applicant |
| US5138712(A) | 1992-08-01 | Corbin | Examiner |
| US5146499(A) | 1992-09-01 | Geffrotin | Applicant |
| US5148481(A) | 1992-09-01 | Abraham et al. | Applicant |
| US5159182(A) | 1992-10-01 | Eisele | Applicant |
| US5183404(A) | 1993-02-01 | Aldous et al. | Applicant |
| US5191193(A) | 1993-03-01 | Le Roux | Applicant |
| US5204897(A) | 1993-04-01 | Wyman | Applicant |
| US5222134(A) | 1993-06-01 | Waite et al. | Applicant |
| US5235642(A) | 1993-08-01 | Wobber et al. | Applicant |
| US5247575(A) | 1993-09-01 | Sprague et al. | Applicant |
| US5255106(A) | 1993-10-01 | Castro | Applicant |
| US5260999(A) | 1993-11-01 | Wyman | Applicant |
| US5263157(A) | 1993-11-01 | Janis | Applicant |
| US5263158(A) | 1993-11-01 | Janis | Applicant |
| US5276444(A) | 1994-01-01 | McNair | Applicant |
| US5276735(A) | 1994-01-01 | Boebert et al. | Applicant |
| US5291596(A) | 1994-03-01 | Mita | Applicant |
| US5295266(A) | 1994-03-01 | Hinsley et al. | Examiner |
| US5301231(A) | 1994-04-01 | Abraham et al. | Applicant |
| US5311591(A) | 1994-05-01 | Fischer | Examiner |
| US5319705(A) | 1994-06-01 | Halter et al. | Applicant |
| US5335346(A) | 1994-08-01 | Fabbio | Examiner |
| US5337357(A) | 1994-08-01 | Chou et al. | Applicant |
| US5339091(A) | 1994-08-01 | Yamazaki et al. | Applicant |
| US5341429(A) | 1994-08-01 | Stringer et al. | Applicant |
| US5347579(A) | 1994-09-01 | Blandford | Applicant |
| US5381526(A) | 1995-01-01 | Ellson | Applicant |
| US5394469(A) | 1995-02-01 | Nagel et al. | Applicant |
| US5410598(A) | 1995-04-01 | Shear | Applicant |
| US5412717(A) | 1995-05-01 | Fischer | Applicant |
| US5428606(A) | 1995-06-01 | Moskowitz | Applicant |
| US5432849(A) | 1995-07-01 | Johnson et al. | Applicant |
| US5438508(A) | 1995-08-01 | Wyman | Applicant |
| US5444779(A) | 1995-08-01 | Daniele | Applicant |
| US5453601(A) | 1995-09-01 | Rosen | Applicant |
| US5455953(A) | 1995-10-01 | Russell | Applicant |
| US5457746(A) | 1995-10-01 | Dolphin | Applicant |
| US5473687(A) | 1995-12-01 | Lipscomb et al. | Applicant |
| US5473692(A) | 1995-12-01 | Davis | Applicant |
| US5499298(A) | 1996-03-01 | Narasimhalu et al. | Applicant |
| US5502766(A) | 1996-03-01 | Boebert et al. | Applicant |
| US5504814(A) | 1996-04-01 | Miyahara | Applicant |
| US5504818(A) | 1996-04-01 | Okano | Applicant |
| US5504837(A) | 1996-04-01 | Griffeth et al. | Applicant |
| US5509070(A) | 1996-04-01 | Schull | Applicant |
| US5530235(A) | 1996-06-01 | Stefik et al. | Applicant |
| US5532920(A) | 1996-07-01 | Hartrick et al. | Applicant |
| US5534975(A) | 1996-07-01 | Stefik et al. | Applicant |
| US5539735(A) | 1996-07-01 | Moskowitz | Applicant |
| US5563946(A) | 1996-10-01 | Cooper et al. | Applicant |
| US5568552(A) | 1996-10-01 | Davis | Applicant |
| US5621797(A) | 1997-04-01 | Rosen | Applicant |
| US5629980(A) | 1997-05-01 | Stefik et al. | Applicant |
| US5633932(A) | 1997-05-01 | Davis et al. | Applicant |
| US5634012(A) | 1997-05-01 | Stefik et al. | Applicant |
| US5638443(A) | 1997-06-01 | Stefik et al. | Applicant |
| US5649013(A) | 1997-07-01 | Stuckey et al. | Applicant |
| US5655077(A) | 1997-08-01 | Jones et al. | Applicant |
| US5673316(A) | 1997-09-01 | Auerbach et al. | Applicant |
| US5708717(A) | 1998-01-01 | Alasia | Applicant |
| US5734823(A) | 1998-03-01 | Saigh et al. | Applicant |
| US5734891(A) | 1998-03-01 | Saigh | Applicant |
| US5737413(A) | 1998-04-01 | Akiyama et al. | Applicant |
| US5737416(A) | 1998-04-01 | Cooper et al. | Applicant |
| US5745569(A) | 1998-04-01 | Moskowitz et al. | Applicant |
| US5748783(A) | 1998-05-01 | Rhoads | Applicant |
| US5757907(A) | 1998-05-01 | Cooper et al. | Applicant |
| US5761686(A) | 1998-06-01 | Bloomberg | Applicant |
| US5765152(A) | 1998-06-01 | Erickson | Applicant |
| US5768426(A) | 1998-06-01 | Rhoads | Applicant |
| US5794207(A) | 1998-08-01 | Walker et al. | Examiner |
| US5825892(A) | 1998-10-01 | Braudaway et al. | Applicant |
| US5892900(A) | 1999-04-01 | Ginter et al. | Examiner |
| US5910987(A) | 1999-06-01 | Ginter et al. | Applicant |
| US5915019(A) | 1999-06-01 | Ginter et al. | Applicant |
| US5917912(A) | 1999-06-01 | Ginter et al. | Applicant |
| US5920861(A) | 1999-07-01 | Hall et al. | Applicant |
| US5933498(A) | 1999-08-01 | Schneck et al. | Applicant |
| US5940504(A) | 1999-08-01 | Griswold | Applicant |
| US5943422(A) | 1999-08-01 | Van Wie et al. | Applicant |
| US5949876(A) | 1999-09-01 | Ginter et al. | Applicant |
| US5982891(A) | 1999-11-01 | Ginter et al. | Applicant |
| US5999949(A) | 1999-12-01 | Crandall | Applicant |
| US6006332(A) | 1999-12-01 | Rabne et al. | Applicant |
| US6009401(A) | 1999-12-01 | Horstmann | Examiner |
| US6047067(A) | 2000-04-01 | Rosen | Applicant |
| US6112181(A) | 2000-08-01 | Shear et al. | Applicant |
| US6115471(A) | 2000-09-01 | Oki et al. | Applicant |
| US6125349(A) | 2000-09-01 | Maher | Examiner |
| US6135646(A) | 2000-10-01 | Kahn et al. | Applicant |
| US6138119(A) | 2000-10-01 | Hall et al. | Applicant |
| US6141754(A) | 2000-10-01 | Choy | Applicant |
| US6157721(A) | 2000-12-01 | Shear et al. | Applicant |
| US6169976(B1) | 2001-01-01 | Colosso | Applicant |
| US6185683(B1) | 2001-02-01 | Ginter et al. | Applicant |
| US6226618(B1) | 2001-05-01 | Downs et al. | Applicant |
| US6233166(B1) | 2001-05-01 | Fontan Tarodo | Examiner |
| US6233684(B1) | 2001-05-01 | Stefik et al. | Applicant |
| US6236971(B1) | 2001-05-01 | Stefik et al. | Applicant |
| US6237786(B1) | 2001-05-01 | Ginter et al. | Applicant |
| US6240185(B1) | 2001-05-01 | Van Wie et al. | Applicant |
| US6240401(B1) | 2001-05-01 | Oren et al. | Examiner |
| US6253193(B1) | 2001-06-01 | Ginter et al. | Applicant |
| US6292569(B1) | 2001-09-01 | Shear et al. | Applicant |
| US6301660(B1) | 2001-10-01 | Benson | Applicant |
| US6327652(B1) | 2001-12-01 | England et al. | Applicant |
| US6330670(B1) | 2001-12-01 | England et al. | Applicant |
| US6345256(B1) | 2002-02-01 | Milsted et al. | Applicant |
| US6360206(B1) | 2002-03-01 | Yamashita | Examiner |
| US6363488(B1) | 2002-03-01 | Ginter et al. | Applicant |
| US6385596(B1) | 2002-05-01 | Wiser et al. | Examiner |
| US6389402(B1) | 2002-05-01 | Ginter et al. | Applicant |
| EP84441 | 1983-07-01 | Applicant | |
| EP180460 | 1986-05-01 | Applicant | |
| EP332707 | 1989-09-01 | Applicant | |
| EP651554 | 1995-05-01 | Applicant | |
| EP668695 | 1995-08-01 | Applicant | |
| EP715244(A1) | 1996-06-01 | Applicant | |
| EP725376 | 1996-08-01 | Applicant | |
| GB2136175 | 1984-09-01 | Applicant | |
| GB2236604 | 1991-04-01 | Applicant | |
| GB2316503(A) | 1998-02-01 | Applicant | |
| JP62-241061 | 1987-10-01 | Applicant | |
| JP64-068835 | 1989-03-01 | Applicant | |
| JPH03-282733 | 1990-03-01 | Examiner | |
| JP4-369068 | 1992-12-01 | Applicant | |
| JP5-268415 | 1993-10-01 | Applicant | |
| JP6-175794 | 1994-06-01 | Applicant | |
| JP6-214862 | 1994-08-01 | Applicant | |
| JP6-215010 | 1994-08-01 | Applicant | |
| JP7-084852 | 1995-03-01 | Applicant | |
| JP7-200317 | 1995-08-01 | Applicant | |
| JP7-244639 | 1995-09-01 | Applicant | |
| JP715241 | 1996-06-01 | Applicant | |
| WO92/20022 | 1992-11-01 | Applicant | |
| WO93/01550 | 1993-01-01 | Applicant | |
| WO94/01821 | 1994-01-01 | Applicant | |
| WO96/24092 | 1996-08-01 | Applicant | |
| WO97/48203 | 1997-12-01 | Applicant | |
| WO98/11690 | 1998-03-01 | Applicant | |
| WO98/42098 | 1998-09-01 | Applicant | |
| WO99/49615 | 1999-09-01 | Applicant | |
| WO/04727 | 2000-01-01 | Applicant | |
| WO/08909 | 2000-02-01 | Applicant | |
| WO/39733 | 2000-07-01 | Applicant | |
| WO1/63528 | 2001-08-01 | Applicant |
Non-Patent Literature (33)
- Weber, Robert. Digital Rights Management Technologies. Oct. 1995. Retrieved from IDS.Examiner
- “National Semiconductor and EPR Partner for Information Metering/Data Security Cards” Mar. 4, 1994, Press Release from Electronic Publishing Resources, Inc.Applicant
- Weber, R., “Digital Rights Management Technology” Oct. 1995.Applicant
- Flasche, U. et al., “Decentralized Processing of Documents”, pp. 119-131, 1986, Comput. & Graphics, vol. 10, No. 2.Applicant
- Mori, R. et al., “Superdistribution: The Concept and the Architecture”, pp. 1133-1146, 1990, The Transactions of the IEICE, vol. E 73, No. 7, Tokyo, JP.Applicant
- Weber, R., “Metering Technologies for Digital Intellectual Property”, pp. 1-29, Oct. 1994, A Report to the International Federation of Reproduction Rights Organizations.Applicant
- Clark, P.C. et al., “Bits: A Smartcard protected Operating System”, pp. 66-70 and 94, Nov. 1994, Communications of the ACM, vol. 37, No. 11.Applicant
- Ross, P.E., “Data Guard”, pp. 101, Jun. 6, 1994, Forbes.Applicant
- Saigh, W.K., “Knowledge is Sacred”, 1992, Video Pocket/Page Reader Systems, Ltd.Applicant
- Kahn, R.R., “Deposit, Registration and Recordation in an Electronic Copyright Management System”, pp. 1-19, Aug. 1992, Corporation for National Research Initiatives, Virginia.Applicant
- Hilts, P. et al., “Books While U Wait”, pp. 48-50, Jan. 3, 1994, Publishers Weekly.Applicant
- Strattner, A, “Cash Register on a Chip may Revolutionize Software Pricing and Distribution; Wave Systems Corp.”, pp. 62, Apr. 1994, Computer Shopper, vol. 14, No. 4, ISSN 0886-0556.Applicant
- O'Conner, M., “New Distribution Option for Electronic Publishers; iOpener Data Encryption and Metering System for CD-ROM use; Column”, pp. 134, Mar. 1994, CD-ROM Professional, vol. 7, No. 2, ISSN: 1409-0833.Applicant
- Willett, S., “Metered PCs: Is Your System Watching You? Wave System beta tests new technology”, pp. 84, May 2, 1994, InfoWorld.Applicant
- Linn, R., “Copyright and Information Services in the Context of the National Research and Education Network”, pp. 9-20, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Perrit, Jr., H., “Permission Headers and Contract Law”, pp. 27-48, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Upthegrove, L., “Intellectual Property Header Descriptors: A Dynamic Approach”, pp. 63-66, Jan. 1994, IMA Intellectual Property Proceedings, vol. 1, Issue 1.Applicant
- Sirbu, M., “Internet Billing Service Design and prototype Implementation”, pp. 67-80, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Simmel, S. et al., “Metering and Licensing of Resources: Kala's General Purpose Approach”, pp. 81-110, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Kahn, R., “Deposit, Registration and Recordation in an Electronic Copyright Management System”, pp. 111-120, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Tygar, J. et al., “Dyad: A System for Using Physically Secure Coprocessors”, pp. 121-152, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Griswold, G., “A Method for Protecting Copyright on Networks”, pp. 169-178, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Nelson, T., “A Publishing and Royalty Model for Networked Documents”, pp. 257-259, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
- Robinson, E., “Redefining Mobile Computing”, pp. 238-240, 247-248 and 252, Jul. 1993, PC Computing.Applicant
- Abadi, M. et al., “Authentication and Delegation with Smart-cards”, 1990, Research Report DEC Systems Research Center.Applicant
- Mark Stefik, “Letting Loose the Light: Igniting Commerce in Electronic Publication”, pp. 219-253, 1996, Internet Dreams: Archetypes, Myths, and Metaphors, IDSN 0-262-19373-6.Applicant
- Mark Stefik, “Letting Loose the Light: Igniting Commerce in Electronic Publication”, pp. 2-35, Feb. 8, 1995, Internet Dreams: Archetypes, Myths and Metaphors.Applicant
- Henry H. Perritt, Jr., “Technological Strategies for Protecting Intellectual Property in the Networked Multm dia Enviroment”, Apr. 2-3, 1993, Knowbots, Permissions Headers & Contract Law.Applicant
- International Search Report dated Sep. 6, 2002 for PCT/US02/17188.Applicant
- International Search Report Dated Feb. 11, 2004.Applicant
- International Search Report Dated Feb. 13, 2004.Applicant
- European Search Report dated Jul. 20, 2004 in EP 02 70 1056.Applicant
- International Search Report; mailed on Jun. 28, 2005 (PCT/US04/17023).Applicant