VQDL.
`
`llllllllllllllllllll
`Z0/90/90
`
`UTILITY
`
`PATENT APPLICATION
`TRANSMITTAL
`(Onlyfor new nonprovisional applications under 3 7 CFR 1.53(b))
`
`APPLICATION ELEMENTS
`
`2.‘
`
`I]
`
`See MPEI’ chapter 600 concerning utility patent application contents.
`1. D Fee Transmittal Form (e.g., PTO/SB/l7)
`(Submit an original and a duplicateforfee proc1.'.:'.\ing)
`Applicant claims small entity status.
`See 37 CFR 127.
`IE Specification
`[Total Pages 23]
`(preferred arrangement set forth below)
`Descriptive title of the invention
`‘
`Cross Reference to Related Applications (ifapplicable)
`Statement Regarding Fed sponsored R & D (ifapplicable)
`Reference to sequence listing, a table,
`or a computer program listing appendix fifapplicablc)
`Background of the Invention
`Brief Summary of the Invention
`Brief Description of the Drawings (iffiled)
`Detailed Description
`Claim(s)
`Abstract of the Disclosure
`[El Drawing(s) (35 U.S.C. 113)
`[ Total Sheets 07]
`Oath or Declaration
`S
`[ Total Pages U ]
`a.» El Newly executed (original or copy)
`b. El Copy from a prior application (37 CFR 1.63(d))
`(for continuation/divisional with Box 18 completed)
`i. Cl
` lN,¥ENTV0R.(S,)
`Signed statement attached deleting inventor(s)
`named in the prior application, see 37 CFR
`1.63(d)(2) and 1.33(b)
`D Application Data Sheet. See 37 CFR 1.76
`
`Prior application infomtationz
`
`
`
`Illllll|||||IHIIIllllllllllllllllllllas/us/02
`
`PTO/SB/O5 (O3—0l)
`Approved for use through 10/31/2002. OMB 0651-0032
`
`First Inventor
`
`Xin Wang et al.
`
`Method And Apparatus Managing The
`Transfer OfRights
`Express Mail Label No.
`
`ADDRESS TO:
`
`Commissioner for Patents
`Box Patent Application
`Washington, DC 20231
`7. El CD-ROM or CD-R in duplicate, large table or
`Computer Program (Appendix)
`8. Nucleotide and/or Amino Acid Sequence Submission
`applicable, all necessary)
`a. U Computer Readable Form (CRF)
`b. Specification Sequence Listing on:
`i. I] CD—ROM orCD—R (2 copies; or
`ii. D paper
`c. D Statements verifying identity of above copies
`ACCOMPANYING APPLICATION PARTS
`
`Assignment Papers (cover sheet & document(s))
`37 CFR 3.73(b) Statement
`El
`Power of
`(when there is an assignee)
`Attomey
`English Translation Document (if applicable)
`Information Disclosure
`D Copies oflDS
`Statement (IDS)/PTO-1449
`Citations
`Preliminary Amendment
`Retum Receipt Postcard (MPEP 503)
`(Should be specifically itemized)
`Certified Copy of Priority Document(s)
`(ifforeign priority is claimed)
`Nonpublication request under 35 U.S.C.
`122(b)(2)(B)(i). Applicant must attach form
`PTO/SB/35 or its equivalent.
`Other:
`
`tiooigiooooo
`
`If a CONTINUING APPLICATION, check appropriate box, and supply the requisite information below and in a preliminaly amendment,
`I 8.
`or in an Application Data Sheet under 37 CFR 1.76:
`El Divisional
`D Continuation
`D Continuation-in-part (CIP)
`Examiner
`
`of prior application No.:
`Group / Art Unit:
`
`/
`
`For CONTINUATION OR DIVISIONAL APPS only: The entire disclosure of the prior application, from which an oath or declaration is supplied under
`Box Sh, is considered a part of the disclosure of the accompanying continuation or divisional application and is hereby incorporated by reference. Thc
`incorporation can only be relied upon when a portion has been inadvertently omitted from the submitted application parts.
` I9. CORRESPONDENCE ADDRESS
`
`IZI Customer Number or Bar Code Label
`
`El Correspondence address below
`
`Name
`
`Marc S. Kaufman
`
`Address
`City
`— Telephone
`
`Registration No. (Attomey/Agent)
`June 6, 2002
`
`NVA228768.l
`
`Petitioner Apple Inc. — Exhibit 1024, p. l
`
`Petitioner Apple Inc. - Exhibit 1024, p. 1
`
`

`
`ii
`
`I
`
`,
`
`.
`
`I
`
`..
`
`/~ —-
`
`I
`
`‘
`
`.
`
`1‘
`
`*
`
`Attorney Docketga 1 1 1325-1 13
`
`
`
`METHOD AND APPARATUS MANAGING
`THE TRANSFER OF RIGHTS
`
`RELATED APPLICATION DATA
`
`[0001]
`
`This application claims benefit from U.S. provisional applications
`
`Ser. Nos. 60/331,624, 60/331,623, and 60/331,621 ‘filed on November 20,
`
`2001, the disclosures of which are incorporated herein by reference. This
`
`application also claims benefit of U.S. provisional applications Ser. Nos.
`
`60/296,113, 60/296,117, and 60/296,118 filed on June 7, 2001,
`
`the
`
`disclosures of which are 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 othen/vise 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 “lntel|ectua| Property
`
`Rights Management" (“lPRM"), “Digital Property Rights Management"
`
`(“DPRM”),
`
`“|nte|lectua|
`
`Property Management”
`
`(“lPM”),
`
`“Rights
`
`Management" (“RM”), and “Electronic Copyright Management" (“ECM”),
`
`collectively referred to as “Digital Rights Management
`
`(DRM)” herein.
`
`NVA22809I .1
`
`Petitioner Apple Inc. — Exhibit 1024, p. 2
`
`Petitioner Apple Inc. - Exhibit 1024, p. 2
`
`

`
`
`
`.
`
`Attorney Dockehma 111325-1 13
`
`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.
`
`patents 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.
`
`[0004]
`
`Two basic DRM schemes have been employed,
`
`secure
`
`A “secure container” (or simply an
`containers and trusted systems.
`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 CRYPTOLOPESTM
`
`and DIGIBOXESTM 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.
`
`[0005]
`
`In
`
`the
`
`“trusted system" approach,
`
`the entire
`
`system is
`
`responsible for preventing unauthorized use and distribution of
`
`the
`
`Building a trusted system usually entails introducing new
`document.
`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
`
`NVA228091.1
`
`Petitioner Apple Inc. — Exhibit 1024, p. 3
`
`Petitioner Apple Inc. - Exhibit 1024, p. 3
`
`

`
`-
`
`Attorney Dockego. 1 11325-113
`
`
`
`
`
`operating systems (e.g., Windows“, LinuxT"", 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.
`
`[0006]
`
`As an example, U.S. patent 5,634,012, the disclosure of which is
`
`incorporated herein by reference, 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.
`
`Usage. rights define one or more manners of use of the associated
`document content and 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
`
`A
`
`other conditions. Further, a party may grant usage rights to others that are
`
`a subset of usage rights possessed by the party.
`
`[0007]
`
`DRM systems have facilitated distribution of digital content by
`
`permitting the content owner to control use of the content. However,
`
`known business models for creating, distributing, and using digital content
`
`and other items involve a plurality of parties.
`
`For example, a content
`
`creator may sell content to a publisher who then authorizes a distributor to
`
`distribute content to an on—line storefront who then sells content to end-
`
`users. Further, the end users may desire to share or further distribute the
`
`content.
`
`In such a business model, usage rights can be given to each
`
`party in accordance with their role in the distribution chain. However, the
`
`parties do not have control over downstream parties unless they are privy
`
`to any transaction with the downstream parties in some way.
`
`For
`
`to the
`example, once the publisher noted above provides content
`distributor,
`the publisher cannot
`readily control
`rights granted to
`
`downstream parties, such as the first or subsequent users unless the
`/
`
`NVA228091 . I
`
`Petitioner Apple Inc. — Exhibit 1024, p. 4
`
`Petitioner Apple Inc. - Exhibit 1024, p. 4
`
`

`
`.
`
`Attorney Dockeg 111325-113
`
`publisher remains a party to the downstream transaction. This loss of
`
`control combined with the ever increasing complexity of distribution chains
`
`results in a situation, which hinders the distribution of digital content and
`
`other items. Further, the publisher may want to prohibit the distributor
`
`and/or the storefront from viewing or printing content while allowing an end
`
`user receiving a license from the storefront to view and print. Accordingly,
`
`the concept of simply granting rights to others that are a subset of
`
`possessed rights is not adequate for multi-party, i.e. multi-tier, distribution
`
`models.
`
`SUMMARY OF THE INVENTION
`
`[0008]
`
`A first aspect of the invention is a method for transferring rights
`
`adapted to be associated with items from a rights supplier to a rights
`
`consumer. The method comprises obtaining a set of rights associated
`
`with an item, said set of rights including meta-rights specifying derivable
`
`rights that can be derived therefrom by the rights consumer, and
`
`determining whether the rights consumer is entitled to derive the derivable
`
`rights specified by the meta-rights, and at
`
`least one of deriving the
`
`derivable rights, and generating a license including the derived rights with
`
`the rights consumer designated as a principal
`
`if the rights consumer is
`
`entitled to derive the derivable rights specified by the meta-rights.
`
`[0009]
`
`A second aspect of the invention is a license associated with an
`
`item and adapted to be used within a system for managing the transfer of
`
`rights to the item from a rights supplier to a rights consumer. The license
`
`comprises a set of rights including meta-rights specifying derivable rights
`
`that can be derived therefrom by the rights consumer, a
`
`principal
`
`designating at
`
`least one rights consumer who is authorized to derive the
`
`derivable rights, and a mechanism for providing access to the item in
`
`accordance with the set of rights.
`
`NVA22309l .1
`
`Petitioner Apple Inc. — Exhibit 1024, p. 5
`
`Petitioner Apple Inc. - Exhibit 1024, p. 5
`
`

`
`.
`
`»
`
`Attorney Docketga 1 1 1325-1 13
`
`[0010]
`
`A third aspect of the invention is a method for deriving rights
`
`adapted to be associated with items from meta-rights.
`
`The method
`
`comprises obtaining a set of rights associated with an item, said set of
`
`rights including meta-rights specifying derivable rights that can be derived
`
`therefrom by the rights consumer, and generating a license associated
`
`with said item and including the derived rights.
`
`BRIEF DESCRIPTION OF THE DRAWING
`
`[0011]
`
`The invention will be described through a preferred embodiment
`
`and the attached drawing in which:
`
`[0012]
`
`Fig. 1
`
`is a schematic illustration of a rights management system
`
`in accordance with the preferred embodiment;
`
`[0013]
`
`Fig. 2 is a block diagram of an example distribution chain
`
`showing the derivation of rights from meta-rights;
`
`[0014]
`
`Fig. 3 is a schematic illustration of a license in accordance with
`
`the preferred embodiment;
`
`[0015]
`
`Fig. 4 is an example of a license expressed with an XML based
`
`rights language in accordance with the preferred embodiment;
`
`[0016]
`
`Fig. 5 is a block diagram of the license server of the system of
`
`Fig. 1;
`
`[0017]
`
`Fig. 6 is a block diagram of a rights label in accordance with the
`
`preferred embodiment; and
`
`[0018]
`
`Fig. 7 is a flow chart of the procedure for transferring and
`
`deriving rights in accordance with the preferred embodiment.
`
`DETAILED DESCRIPTION
`
`
`
`NVA22809 I . I
`
`Petitioner Apple Inc. — Exhibit 1024, p. 6
`
`Petitioner Apple Inc. - Exhibit 1024, p. 6
`
`

`
`
`
`‘i
`
`.
`
`4
`
`C?‘
`
`‘
`
`Attorney Dockeg. 111325-113
`
`[0019]
`
`A DRM system can be utilized to specify and enforce usage
`
`rights for specific content, services, or other items. Fig. 1
`
`illustrates DRM
`
`System 10 that can be used in connection with the preferred embodiment.
`
`DRM System 10 includes a user activation component,
`
`in the form of
`
`activation server 20, that issues public and private key pairs to content
`
`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
`
`content recipient, 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 component necessary for
`
`rendering content 42.
`
`[0020]
`
`Rights label 40 is associated with content 42 and specifies
`
`usage rights and possibly corresponding conditions that can be selected
`
`by a content recipient. License Server 50 manages the encryption keys
`
`and issues licenses for protected content. These licenses embody the
`
`actual granting of usage rights to an end user. For example, rights label
`
`40 may include usage rights permitting a recipient to view content for a fee
`
`of five dollars and view and print content for a fee of ten dollars. License
`
`52 can be issued for the view right when the five dollar fee has been paid,
`
`for example. Client component 60 interprets and enforces the rights that
`
`have been specified in license 52.
`
`[0021]
`
`Fig. 6 illustrates rights label 40 in accordance with the preferred
`
`embodiment.
`
`Rights label 40 includes plural
`
`rights offers 44 each
`
`including usage rights 44a, conditions 44b, and content specification 44c.
`
`Content
`
`specification 44c can include any mechanism for calling,
`
`referencing, locating, linking or othen/vise specifying content 42 associated
`
`with offer 44. 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
`
`NVA22809l .1
`
`Petitioner Apple Inc. — Exhibit 1024, p. 7
`
`Petitioner Apple Inc. - Exhibit 1024, p. 7
`
`

`
`.
`
`Attorney Docketga 1 11325-113 .
`
`
`
`Eng
`
`other party. Preparation of content consists of specifying the rights and
`
`conditions under which content 42 can be used, associating rights label 40
`
`with content 42 and protecting content 42 with some crypto algorithm. A
`
`rights language such as XrMLTM can be used to specify the rights and
`conditions. However, the 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. As discussed in detail
`
`below, rights 44a can include usage rights, which specify a manner of use,
`
`and meta-rights, which permit other rights to be derived.
`
`[0022]
`
`In some case,
`
`license 52 includes conditions that must be
`
`satisfied in order to exercise 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
`
`In other words, the condition is that the user is a
`members of a book club.
`particular person or member of a particular group. Rights and conditions
`
`A
`
`can exist as separate entities or can be combined.
`
`[0023]
`
`Labels, offers, usage rights, and conditions can be stored
`
`together with content 42 or otherwise associated with content 42 through
`
`content specification 44c or any other mechanism. A rights language such
`
`as XrMLTM can be used to specify the rights and conditions. However, the
`
`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
`
`content 42.
`
`[0024]
`
`A typical workflow for DRM system 10 is described below. A
`
`recipient operating within client environment 30 is activated for receiving
`
`NVA228091.l
`
`Petitioner Apple Inc. — Exhibit 1024, p. 8
`
`Petitioner Apple Inc. - Exhibit 1024, p. 8
`
`

`
`.
`
`Attorney Dockeg. 111325-113
`
`content 42 by activation sewer 20. This results in a public-private key pair
`
`(and possibly 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.
`
`[0025] When a recipient wishes to obtain specific content 42,
`
`the
`
`recipient makes a request for content 42. For example, a user, as a
`
`recipient, might browse a Web site running on Web server 80, using a
`
`browser installed in client environment 30, and request 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 content 42 and Web server 80 causes both the content and license 52
`
`to be downloaded. License 52 includes the appropriate rights, such as
`
`usage rights and/or meta-rights, and can be downloaded from license
`
`server 50 or an associated device. Content 42 can be downloaded from
`
`computer 70 associated with a vendor, distributor, or other party.
`
`[0026]
`
`Client component 60 in client environment 30-will then proceed
`
`to interpret license 52 and allow use of content 42 based on the usage
`
`rights and conditions specified in license 52. The interpretation and
`
`enforcement of usage rights are well known generally and described in the
`
`patents referenced above,
`
`for example. The steps described. above may
`
`take place sequentially or approximately simultaneously or in various
`
`orders.
`
`[0027]
`
`I DRM system 10 addresses security aspects of content 42.
`
`In
`
`particular, DRM system 10 may authenticate license 52 that has been
`
`
`
`NVA22809l.l
`
`Petitioner Apple Inc. — Exhibit 1024, p. 9
`
`Petitioner Apple Inc. - Exhibit 1024, p. 9
`
`

`
`.
`
`Attorney Docketgo. 1 11325-113
`
`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 the
`cryptographicsignature, or other identifying characteristic of license 52.
`
`Of course, the example above is merely one way to effect a DRM system.
`
`For example, license 52 and content 42 can be distributed from different
`
`entities. Clearinghouse 90 can be used to process payment transactions
`
`and verify payment prior to issuing a license.
`
`[0028]
`
`As noted above, typical business models for distributing digital
`
`content include plural parties, such as owners, publishers, distributors, and
`
`users. Each of these parties can act as a supplier granting rights to a
`
`consumer downstream in
`
`the distribution channel.
`
`The preferred
`
`embodiment extends the known concepts of usage rights, such as the
`
`usage rights and related systems disclosed in U.S. patents 5,629,980,
`5,534,012, 5,638,443, 5,715,403 and 5,530,235,
`to incorporate the
`
`
`
`concept of “meta-rights.” Meta-rights are the rights that one has to
`
`generate, manipulate, modify, dispose of or othenrvise derive other rights.
`
` meta-rights). This concept will become clear based on the description
`
`Meta-rights can be thought of as usage rights to usage rights (or other
`
`below.
`
`[0029] Meta-rights can include derivable rights to offer rights, grant
`
`rights, negotiate rights, obtain rights,
`
`transfer rights, delegate rights,
`
`expose rights, archive rights, compile rights, track rights, surrender rights,
`
`exchange rights, and revoke 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. Meta-rights can be hierarchical and can be
`
`structured as objects within objects. For example, a distributor may have
`
`a meta-right permitting the distributor to grant a meta—right to a retailer
`
`which permits the retailer to grant users rights to view content.
`
`Just as
`
`NVA22809l .1
`
`Petitioner Apple Inc. — Exhibit 1024, p. 10
`
`Petitioner Apple Inc. - Exhibit 1024, p. 10
`
`

`
`.
`
`Attorney Dockeg 1 1 1325-1 13
`
`rights can have conditions, meta-rights can also have conditions. Meta-
`
`rights can also be associated with other meta-rights.
`
`A [0030]
`
`The concept of meta-rights can be particularly useful because
`
`distribution models may include entities that are not creators or owners of
`
`digital content, but are in
`
`the business of manipulating the rights
`
`associated with the content. For example, as noted above, in a multi-tier
`
`content distribution model, intermediate entities (e.g., distributors) typically
`
`will not create or use the content but will be given the right to issue rights
`
`for the content they distribute.
`
`In other words, the distributor or reseller will
`
`need to obtain rights (meta-rights) to issue rights. For the sake of clarity,
`
`the party granting usage rights or meta-rights is referred to as “supplier”
`
`and the party receiving and/or exercising such rights is referred to as
`
`“consumer” herein.
`
`It will become clear that any party can be a supplier or
`
`a consumer depending on their relationship with the adjacent party in the
`
`distribution chain. Note that a consumer “consumes” , i.e. exercises, rights
`
`and does not necessarily consume, i.e. use, the associated content.
`
`[0031]
`
`Fig. 2 schematically illustrates an example of a multi-tier
`
`distribution model 200. Publisher 210 publishes content for distribution, by
`
`distributor 220 for example. Distributor 220 distributes content to retailers,
`
`such as retailer 230 and retailer 230 sells content to users, such as user
`
`240.
`
`In model 200, publisher 210 could negotiate business relationships
`
`with distributor 220 and
`
`distributor 220 could negotiate business
`
`relationships with retailer 230. Also, retailer 230 may desire usage rights
`
`that are beyond usage rights granted to distributor 220. However, keep in
`
`mind that, in a distribution chain that utilizes a DRM system to control use
`
`and distribution of content or other items, content can travel from publisher
`
`210 to user 240 through any digital communication channel, such a
`
`network or transfer of physical media. When user 240 wishes to use
`
`content, a license is obtained, in the manner described above for example.
`
`Accordingly,
`
`the negotiated relationships can become difficult,
`
`if not
`
`impossible, to manage.
`
`
`
`NVA22809l .1
`
`10
`
`Petitioner Apple Inc. — Exhibit 1024, p. 11
`
`Petitioner Apple Inc. - Exhibit 1024, p. 11
`
`

`
`
`
`
`.
`
`Attorney Docket!o. 11 1325-113
`
`[0032]
`In model 200 of Fig. 2, retailer 230 will only grant rights to user
`240 that have been predetermined and authorized by the distributor 220,
`
`publisher 210 and potentially other parties upstream of the transaction,
`
`such as the content creator or owner. The rights are predetermined
`
`through, and derived from, meta-rights granted to retailer 230 by distributor
`
`220. Of course, there can be any number of parties in the distribution
`
`chain. For example, distributor 220 may sell directly to the public in which
`
`case retailer 230 is not necessary. Also, there may be additional parties.
`
`For example user 240 can distribute to other users.
`
`[0033]
`
`In model 200 publisher grants to distributor 220 usage rights 212
`
`permitting distribution of content, and meta-rights 214. Meta-rights 214
`
`permit distributor 220 to grant to retailer 230 the usage right 214’ (derived
`
`from meta-rights 214) to distribute or possibly sell content and meta-rights
`
`216 which permit retailer 230 to grant user 240 the right to use content.
`
`For example, publisher 210 may specify, through meta-rights 214,
`
`that
`
`meta-right 216 granted to retailer 230 permits retailer 230 to grant only 500
`
`licenses and usage rights 216’ that retailer 230 can grant to a user can
`
`only be “view” and “print-once".
`
`In other words, distributor 220 has
`
`granted meta-rights to retailer 230. Similarly, publisher 210 issues meta-
`
`rights 214 to the distributor that will govern what type, and how many ,
`
`rights distributor 220 can grant to retailer 230. Note that these entities
`
`could be divisions, units or persons that are part of a larger enterprise,
`
`which also has other roles.
`
`For example, an enterprise might create,
`
`distribute, and sell content and carry out those activities using \different
`
`personnel or different business units within the enterprise. The principles
`
`of meta-rights can be applied to an enterprise to determine content usage
`
`within that enterprise. Also, retailer 230 could grant meta-rights 218 to
`
`user 240 permitting user 240 to share rights or grant usage rights to
`
`achieve a super-distribution model.
`
`It can be seen that meta-rights of a
`
`party are derived from meta-rights granted by an upstream party in the
`
`distribution chain.
`
`NVA228091.1
`
`11
`
`Petitioner Apple Inc. — Exhibit 1024, p. 12
`
`Petitioner Apple Inc. - Exhibit 1024, p. 12
`
`

`
`.
`
`Attorney Dockewo. 111325-1 13
`
`[0034]
`
`For example, a person’s medical records can be in digital form
`
`managed by a first hospital as publisher 230.
`
`In this scenario, the person,~
`
`as supplier, grants usage rights to the hospital, as consumer, to access
`
`and update the medical records. Should that person require treatment at a
`
`second hospital and desires to transfer their records to the second
`
`hospital, the person can grant to the first hospital the right to transfer the
`
`access rights to the new hospital through meta-rights.
`
`In other words, the
`
`person has specified meta-rights and granted the meta-rights to the first
`
`hospital. The meta-rights permit the first hospital to grant rights, as a
`
`supplier, to the second hospital, as a consumer.
`
`In another example, a
`
`person’s last will and testament can be in digital form and managed by a
`
`law firm as publisher 210.
`
`If the person wishes to allow a third party to
`
`review the will. The person can grant meta-rights to the law firm permitting
`
`the law firm to grant access rights to this third party.
`
`[0035]
`
`At a high level the process of enforcing and exercising meta-
`
`rights are the same as for usage rights. However, the difference between
`
`usage rights and meta-rights are the result from exercising the rights.
`
`When exercising usage rights, actions to content result.
`
`For example
`
`usage rights can be for viewing, printing, or copying digital content. When
`
`meta-rights are exercised, new rights are created from the meta-rights or
`
`existing rights are disposed as the result of exercising the meta-rights.
`
`The recipient of the new rights may be the same principal (same person,
`
`entity, or machine, etc), who exercises the meta-rights. Alternatively, the
`
`recipient of meta-rights can be a new principal. The principals who receive
`
`the derived
`rights may be
`authenticated and
`authorized
`before
`receiving/storing the derived rights. Thus, the mechanism for exercising
`
`and enforcing a meta-right can be the same as that for a usage right. For
`example, the mechanism disclosed in U.S. Patent 5,634,012 can be used.
`
`[0036] Meta-rights can be expressed by use of a grammar or rights
`
`language including data structures, symbols, elements, or sets of rules.
`
`For example, the XrMLT"" rights language can be used. As illustrated in
`
`
`
`
`NVA22809l .1
`
`12
`
`Petitioner Apple Inc. — Exhibit 1024, p. 13 g
`
`Petitioner Apple Inc. - Exhibit 1024, p. 13
`
`

`
`I
`
`Attorney Docket lo. 111325-113
`
`Fig. 3, the structure of license 52 can consist of one or more grants 300
`
`and one or more digital signatures 310. Each grant 300 includes specific
`
`granted meta-rights 302 such as rights to offer usage rights, grant usage
`
`rights, obtain usage rights, transfer usage rights, exchange usage rights,
`
`transport usage rights, surrender usage rights, revoke usage rights, reuse
`
`usage rights, or management meta-rights such as the rights to backup
`
`rights, restore rights, recover rights, reissue rights, or escrow the rights for
`
`management of meta-rights and the like.
`
`[0037]
`
`Grant 300 can also specify one or more principals 304 to whom
`
`the specified meta-rights are granted. Also grants 300 can include
`conditions 306 and state variables 308. Like usage rights, access and
`exercise of
`the granted meta-rights are controlled by any related
`conditions 306 and state variables 308. The integrity of license 52
`is
`ensured by the use of digital signature 310, or another identification .
`mechanism.
`Signature 310 can include a crypto-algorithm, a key, or
`
`another mechanism for providing access to content 42 in a known manner.
`
`The structure of digital signature 310 includes the signature itself,
`
`the
`
`method of how the code is computed, the key information needed to verify
`
`the code and issuer identification.
`
`[0038]
`
`State variables track potentially dynamic states conditions.
`
`State variables are variables having values that represent status of rights,
`
`or other dynamic conditions.
`
`State variables can be tracked, by
`
`clearinghouse 90 or 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
`
`for 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 no 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
`
`Eu;
`
`W
`
`
`
`NVA228091 .1
`
`13
`
`Petitioner Apple Inc. — Exhibit 1024, p. 14
`
`Petitioner Apple Inc. - Exhibit 1024, p. 14
`
`

`
`.
`
`Attorney DocketIo. 111325-113
`
`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.
`
`[0039]
`
`Fig. 4 is an example of license 52 encoded in XrMLT“'. The
`
`provider grants the distributor a meta right to issue a usage right (i.e., play)
`
`to the content (i.e., a book) to any end user. With this meta right, the
`
`distributor may issue the right to play the book within the U.S. region and
`