llllllllllliiuiilhlllllll Id'S'fll9Z€l
`
`PTO/SB/05 (03-01)
`l0/31/2002. OMB 0651-0032
`
`111325-291300
`.
`Attorney Docket No.
`Ma‘ “G” “ EN’ '3‘ ‘*1’
`First Inventor
`0
`SYSTEM AND METHOD FOR
`MANAGING TRANSFER OF RIGHTS'o‘_.v—
`USING SHARED STATE VARIABLES’). (‘:1
`0
`
`
`
`
`
`
`
`UTILITY
`PATENT APPLICATION
`TRANSMITTAL
`
`(Onlyfor new nonpravisianal applications under 37 CFR I.53(b))
`
`
`
`APPLICATION ELENIEN-rs
`
`0) C
`Commissioner for Patents
`ADDRESS T0:
`Box Patent Application
`,'i’ .-
`atent a lication contents.
`e
`Washin on, DC 20231
`7‘
`See MPEP chater 600 concernin utili
`
`7. U CD-ROM or CD-R in duplicate, large table or
`1.
`Fee Transmittal Forln (e.g., PTO/SB/17)
`
`(Submit an original and a duplicateforfee processing)
`Computer Program (Appendix)
`Applicant claims small entity status.
`8. Nucleotide and/or Amino Acid Sequence Submission
`See 37 CFR 1.27.
`
`(ifapplicable, all necessary)
`a. El Computer Readable Fonn (CRF)
`
`b. Specification Sequence Listing on:
`i.
`III CD-ROM or CD-R (2 copies; or
`
`ii. El paper
`c. El Statements verifying identity of above copies
`ACCOMPANYING APPLICATION PARTS
`
`[Total Pages 33]
`Specification
`(preferred arrangunuxt 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 (ifapplicable)
`Background of the Invention
`-
`Brief Summary of the Invention
`-
`Brief Descxiption of the Drawings (iffi/ed)
`-
`- Detailed Description
`:
`of the Disclosure
`I2! Drawing(s) (35 U.S.C. 113) 17 Figures [ Total Sheets 14] ‘
`4.
`5. Oath or Declaration
`[ Total Pages 5 ]
`a‘
`'3 Newly executed (original or copy)
`b.
`[3 Copy from a prior application (37 CFR l.63(d))
`(for continuation/divisional with Box 18 completed)
`i. El DELEFION OF INVENTOR(S1
`.
`signed [emerit mach.ed[.ie1efing mvemods)
`'l'“g§:;‘X“$)“;:§’l"’3’3‘2f’§"‘°a“°“’ 5“ 37 CF“
`_
`_ ‘
`'
`IE Application Data Sheet. See 37 CFR 1.76
`
`6.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`. El Assignment Papers (cover sheet & document(s))
`10. El 37 CFR 3.73(b) Statement
`E!
`Power of
`(when there is an assignee)
`Attomey
`11. El English Translation Document (ifapplicable)
`12' D
`449
`'3 (駒t::f:n°S“DS
`13 D Preliminary Amendment
`14. El Retum Receipt Postcard (MPEP 503)
`‘
`(S,,o,,,d be spec,-fica,,y ,-,,_,,,,,-,e,,)
`15_ U Certified Copy of Prion-ty Document“)
`(ifforeign priority is claimed)
`16. El Nonpublication request under 35 U.S.C.
`l22(b)(2)(B)(i). Applicant must attach form
`PTO/SB/35 or its equivalent.
`17» D Omen
`
`
`
`
`
`
`
`
`
`
`
`
`If a CONTINUING APPLICATION, check appropriate box, and supply the requisite information below and in a preliminary amendment,
` 18.
`
`or in an Application Data Sheet under 37 CFR I. 76:
`
`D Continuation
`E Continuation-in-part (CIP) of prior application No: 10/ 162,791
`
`
`
`
`
`
`Group / Art Unit: 2122
`Examiner Not Yet Assigned
`2 ‘Prior application information:
`For CONTINUATION OR DIVISIONAL APPS only: The entire disclosure of the prior application, from which an oath or declaration is supplied under
`Box Sb, is considered a part of the disclosure of the accompanying continuation or divisional application and is hereby incorporated by reference. The
`incorporation can only be relied upon when a portion has been inadvertently omitted from the submitted application parts.
`19. CORRESPONDENCE ADDRESS
`
`
` E Customer Number or Bar Code Label
`
`or U Correspondence address below
`
`
`
`
`
`
`
` ‘
`
`
`
`———
`———
`
`Name (Print/Type)
`Ca;-[05 R_ Villam, egistration No. (Attomey/Agent)
`
`\
`
`
`October 4, 2004
`
`1.
`
`W326658.l
`
`Petitioner Apple Inc. - Exhibit 1002, p. 1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 1
`
`

`
`Com letei Known
`
`Not Yet Assi ed
`October 4, 2004
`Mai NGUYEN, et al.
`Not Yet Assigned
`Not Yet Assigned
`111325-291300
`
` Application Number
`
`Filing Date
`
`First Named Inventor
`
` Examiner Name
`
`Art Unit
`
`
`
`
`Attorney Docket No.
`
`t70T700l
`
`FEE TRANSMITTAL
`
`FOR FY 2004
`Pateritfees are subject to annual revision.
`
`__“ plicant claims small entity status. See 37 CFR 1.27
`$1 078.00
`
`METHOD OF PAYMENT (check all that a u
`
`D Check D Credit Card D Money D Other D None
`
`Order
`
`E Deposit Account:
`Deposit
`Account
`19-2380
`Number
`
`
`
`
`3. ADDITIONAL FEES
`
`
`
`
`
`
`
`
`
`
`
`
`_
`Deposit
`Nlxon Peabody LLP
`gzrfgmt
`_
`_
`_
`_
`The Comirussioner IS authorized to: (check all that apply)
`E Chmgc feds) indicated below
`E Credit any ovcrpaymcms
`E Charge any additional fee(s)
`D Charge fee(s) indicated below, except for the filing fee
`‘° ‘*'° 3b°V°"“°“‘ifi“' “°P°5" "’°°°"“L
`FEE CALCULATION
`1, BASIC FILING FEE
`Large Entity
`Small Entity
`F
`F
`F
`F
`Czede
`(Se;
`Czze
`(Se:
`
`F D
`ee
`
`ti
`‘
`escnp on
`
`Fee Paid
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`FEE CALCULATION continued
`
`Fee Description
`
`V
`
`Surcharge — late filing fee or oath
`Surcharge - late provisional filing fee or cover
`sheet
`
`Non-English specification
`For filing a request for ex parte reexamination
`Requesting publication of SIR prior to Exarriiner
`anion
`:R::::sting publication of SIR after Examiner
`Extension for reply within first month
`Extension for reply within second month
`Extension for reply within third month
`Extension for reply within fourth month
`Extension for reply within fifili month
`Notice of Appeal
`,
`,
`,
`,
`Filing a bnefin support ofan appeal
`Request for oral hearing
`
`Petition to institute a public use proceeding
`Petition to revive — unavoidable
`Petition to revive — unintentional
`Utility issue fee (Or reissue)
`9°99“ ‘55“‘’ f”
`Plant issue fee
`
`Petitions to the Commissioner
`Processing fee under 37 CFR 1.17(q)
`Submission of Infomiation Disclosure Stmt
`Recording each patent assignment per property
`(times number of properties)
`Filing a submission afier final rejection
`(37 CFR1.129(a))
`For each additional invention to be examined
`(37 CFR 1.l29(b))
`
`Request for Continued Examination (RCE)
`Request for expedited examination of a design
`application
`
`to
`
`Small Entity
`
`Large Entity
`
`
`Code
`(5)
`2051
`65
`2052
`25
`
`
`
`
`
`
`1053
`1812
`1804
`
`1805
`2251
`2252
`2253
`2254
`2255
`2401
`
`2402
`2403
`
`1460
`1807
`1806
`8021
`
`2309
`
`2810
`
`2801
`1802
`
`130
`2,520
`920'
`
`1,840‘
`55
`215
`490
`765
`‘ 1,040
`170
`
`170
`150
`
`1,510
`55
`685
`535
`245
`330
`
`130
`50
`180
`40
`
`395
`
`395
`
`395
`900
`
`
`
`395
`2001
`790
`1001
`1451
`790_00 .
`Uu-my filing fee
`
`
`175
`2002
`350
`1002
`Design filing fee _ 2452
`
`
`
`
`275
`2003
`550
`mam filing fee - 2453
`J003
`
`
`1004
`790
`2004
`395
`Reissue filing fee _ 2501
`Provisional filing fee ’ 2502
`I005
`150
`2005
`so
`
`2503
`
`
`SUBTOTAL (1)
`$790 00
`
`
`
`EXTRA CLAIM FEES FOR UTILITY AND REISSUE
`Fee from
`below
`18.00
`
`Total Claims
`
`Extra Clnirris
`x
`
`-20" =
`
`=
`
`
`
`
`
`
`
`
`Fee Paid
`
`
`$288.00
`
`
`Independent [:] -3" = |:| x :| = [E]
`Claims
`
`
`
`Multiple Dependent
`X [:l = I
`Large Entity
`Small Entity
`
`Fee
`Fee
`Fee
`Fee
`Fee Dgseripfign
`
`
`
`
`Other fee (specify)
`Code
`(5)
`Code
`(S)
`1202
`18
`2202
`Claims in excess of20
`
`
`1201
`88
`2201
`Independent claims in excess of 3
`
`
`1203
`300
`2203
`150
`Multiple dependent claim, ifnot paid
`
`‘Reduced by Basic Filing Fee Paid
`
`
`
`1204
`1205
`
`33
`18
`
`22°‘
`2205
`
`44
`9
`
`T1
`;'.;:;Sl‘::':“‘:°P°“‘°“' °“’i"‘5 °"°’
`“ Reissue claims in excess of 20 and
`over original patent
`SUBTOTAL (2)
`$288.00
`"or number previously paid, if greater, For Reissues, see above
`
`
`
`
`
`
`
`
`
`
`
`
`
`CERTIFICATE or MAILING OR TRANSMISSION [37 CFR l.8(a)]
`I hemby cenify ‘hm mis °°"°5p°“d°“°e is bemg:
`deposited with the United States Postal Service on the date shown below with sufficient
`El
`postage as first class mail in an envelope addressed to: Mail Stop
`,
`Commissioner for Patents, P. O. Box 1450, Alexandria, VA 22313-1450
`transmitted by facsimile on the date shown below to the United States Patent and
`Trademark Office at (703)
`
`El
`
`Date
`
`Signature
`
`Ted or rinted narne
`
`
`
`Comlete i a licable
`0°” 5“5"‘2°“
`°“‘°“‘*“"“‘““ ‘*-°’’”‘‘
`——flltfll October 4, 2004
`
`
`W’ ' 1
`SEND TO: Cornmissioner for Patents
`PO. Box 1450
`Alexandria, VA 22313-1450
`
`SUBMITTED BY
`
`W326666.l
`
`Petitioner Apple Inc. - Exhibit 1002, p. 2
`
`Petitioner Apple Inc. - Exhibit 1002, p. 2
`
`

`
`SYSTEM AND METHOD FOR MANAGING TRANSFER OF RIGHTS USING
`
`Attorney Docket No. 11 1325-291300
`
`SHARED STATE VARIABLES
`
`RELATED APPLICATION DATA
`
`[0001]
`
`This application is a continuation-in-part application of co-pending
`
`application Ser. No. 10/162,701 filed on June 6, 2002, which claims benefit
`
`from U.S. provisional applications Ser. Nos. 60/331,624, 60/331,623, and
`
`60/331,621 filed on November 20, 2001, and U.S. provisional applications
`
`Ser. Nos. 60/296,113, 60/296,117, and 60/296,118 filed on June 7, 2001, the
`
`entire disclosures of all of which are hereby incorporated by reference herein.
`
`FIELD OF THE INVENTION
`
`[0002]
`
`The present invention generally relates to rights transfer and more
`
`particularly to a method, system and device for managing transfer of rights
`
`using shared state variables.
`
`BACKGROUND OF THE INVENTION
`
`[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 "|nte||ectua| Property Rights Management"
`
`(“IPRM”),
`
`“Digital Property Rights Management” (“DPRM”), “|nte||ectua|
`
`Property Management” (“|PM"), “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. patents 5,530,235, 5,634,012, 5,715,403, 5,638,443, and
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3
`
`

`
`5,629,980, the disclosures of which are incorporated herein by reference,
`
`disclose DRM systems addressing these issues.
`
`Attorney Docket No. 11 1325-291300
`
`[0004]
`
`Two basic DRM schemes have been employed, secure containers
`
`and trusted systems. A "secure container” (or simply an encrypted document)
`
`offers a way to keep document contents encrypted until a set of authorization
`
`conditions are met and some copyright terms are honored (e.g., payment for
`
`use). After the various conditions and terms are verified with the document
`
`provider, the document is released to the user in clear form. Commercial
`
`products
`
`such as CRYPTOLOPEST“ 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 document. Building a
`
`trusted system usually entails introducing new hardware such as a secure
`
`processor, secure storageand secure rendering devices. This also requires
`
`that all software applications that run on trusted systems be certified to be
`
`trusted. While building tamper-proof trusted systems is a real challenge to
`
`existing technologies, current market trends suggest that open and untrusted
`
`systems, such as PC’s and workstations using browsers to access the Web,
`
`will be the dominant systems used to access digital works.
`
`in this sense,
`
`existing computing environments such as PC’s and workstations equipped
`
`with popular operating systems (e.g., Windows“’', Linux”, and UNIX) and
`
`rendering applications, such as browsers, are not trusted systems and cannot
`
`be made trusted without significantly altering their architectures. Of course,
`
`alteration of the architecture defeats a primary purpose of the Web,
`
`i.e.
`
`flexibility and compatibility.
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 4
`
`Petitioner Apple Inc. - Exhibit 1002, p. 4
`
`

`
`Attorney Docket No. 1 11325-291300
`
`[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 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 example, once the publisher noted
`
`above provides content to the distributor, the publisher cannot readily control
`
`rights granted to downstream parties, such as the first or subsequent users
`
`unless the 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
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 5
`
`Petitioner Apple Inc. - Exhibit 1002, p. 5
`
`

`
`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.
`
`Attorney Docket No. 111325-291300
`
`SUMMARY OF THE INVENTION
`
`[0008]
`
`The exemplary embodiments of the present invention are directed
`
`to a method, system and device for
`
`transferring rights adapted to be
`
`associated with items from a rights supplier to a rights consumer, including
`
`obtaining a set of rights associated with an item, the set of rights including
`
`meta-rights specifying derivable rights that can be derived from the meta-;
`
`determining whether the rights consumer is entitled to the derivable rights
`
`specified by the meta-rights; and deriving at least one right from the derivable
`
`rights, if the rights consumer is entitled to the derivable rights specified by the
`
`meta-rights, wherein the derived right includes at least one state variable
`
`based on the set of rights and used for determining a state of the derived
`
`right.
`
`[0009]
`
`Still other aspects,
`
`features, and advantages of
`
`the present
`
`invention are readily apparent from the following detailed description, simply
`
`by illustrating a number of exemplary embodiments and implementations,
`
`including the best mode contemplated for carrying out the present invention.
`
`The present invention is also capable of other and different embodiments, and
`
`its several details can be modified in various respects, all without departing
`
`from the spirit and scope of the present invention. Accordingly, the drawings
`
`and descriptions are to be regarded as illustrative in nature, and not as
`
`restrictive.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0010]
`
`Exemplary embodiments of this invention will be described in detail,
`
`with reference to the attached drawings in which:
`
`[0011]
`
`Fig. 1 is a schematic illustration of a rights management system in
`
`accordance with the preferred embodiment;
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 6
`
`Petitioner Apple Inc. - Exhibit 1002, p. 6
`
`

`
`Attorney Docket No. 111325-291300
`
`[0012]
`
`Fig. 2 is a block diagram of an example distribution chain showing
`
`the derivation of rights from meta—rights;
`
`[0013]
`
`1 Fig. 3 is a schematic illustration of a license in accordance with the
`
`preferred embodiment;
`
`[0014]
`
`Fig. 4 is an example of a license expressed with an XML based
`
`rights language in accordance with the preferred embodiment;
`
`[0015]
`
`Fig. 5 is a block diagram of the license server of the system of
`
`Fig. 1;
`
`[0016]
`
`Fig. 6 is a block diagram of a rights label in accordance with the
`
`preferred embodiment;
`
`[0017]
`
`Fig. 7 is a flow chart of the procedure for transferring and deriving
`
`rights in accordance with the preferred embodiment;
`
`[0018]
`
`Fig. 8 illustrates an exemplary system including a state-of-rights
`
`server;
`
`[0019]
`
`Fig. 9 illustrates employing of a state variable in deriving exclusive
`
`usage rights;
`
`[0020]
`
`Fig. 10 illustrates employing of a state variable in deriving inherited
`
`usage rights;
`
`[0021]
`
`Fig. 11 illustrates employing of a state variable in deriving rights that
`
`are shared among a known set of rights recipients;
`
`[0022]
`
`Fig. 12 illustrates employing of a state variable in deriving rights that
`
`are shared among a dynamic set of rights recipients;
`
`[0023]
`
`Fig. 13 illustrates employing of a state variable in maintaining a
`
`state shared by multiple rights;
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 7
`
`Petitioner Apple Inc. - Exhibit 1002, p. 7
`
`

`
`[0024]
`
`Fig. 14 illustrates employing of multiple state variables to represent
`
`one state of rights;
`
`Attorney Docket No. 1 1 1325—291300
`
`' [0025]
`
`Fig. 15 illustrates a case where not all rights are associated with
`
`states;
`
`[0026]
`
`Fig. 16 illustrates a caseiwhere not all rights which are associated
`
`with states are shared or inherited; and
`
`[0027]
`
`Fig. 17 illustrates a case of rights sharing based on an offer which
`
`does not explicitly include meta-rights.
`
`DETAILED DESCRIPTION
`
`[0028]
`
`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.
`
`[0029]
`
`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
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 8
`
`Petitioner Apple Inc. - Exhibit 1002, p. 8
`
`

`
`Attorney Docket No. 1 11325-291300
`
`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.
`
`[0030]
`
`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 otherwise 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 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 XrML 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.
`
`[0031]
`
`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 members of a book
`
`club.
`
`In other words, the condition is that the user is a particular person or
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 9
`
`Petitioner Apple Inc. - Exhibit 1002, p. 9
`
`

`
`member of a particular group. Rights and conditions can exist as separate
`
`entities or can be combined.
`
`Attorney Docket No. 11 1325—29130O
`
`[0032]
`
`Labels, offers, usage rights, and conditions can be stored together
`
`with content 42 or othewvise associated with content 42 through content
`
`specification 44c or any other mechanism. A rights language such as XrML
`
`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.
`
`[0033]
`
`A typical workflow for DRM system 10 is described below. A
`
`recipient operating within client environment 30 is activated for receiving
`
`content 42 by activation server 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.
`
`[0034] 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.
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 10
`
`Petitioner Apple Inc. - Exhibit 1002, p. 10
`
`

`
`Content 42 can be downloaded from computer 70 associated with a vendor,
`
`distributor, or other party.
`
`Attorney Docket No. 11 1325-291300
`
`[0035]
`
`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.
`
`[0036]
`
`DRM system 10 addresses security aspects of content 42.
`
`In
`
`particular, DRM system 10 may authenticate license 52 that has been issued
`
`by license server 50. One way to accomplish such authentication is for
`
`application 60 to determine if license 52 can be trusted.
`
`In other words,
`
`application 60 has the capability to verify and validate the cryptographic
`
`signature, or other identifying characteristic oflicense 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.
`
`[0037]
`
`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,634,012, 5,638,443,
`
`5,715,403 and 5,630,235, to incorporate the concept of “meta—rights.” Meta-
`
`rights are the rights that one has to generate, manipulate, modify, dispose of
`
`or otherwise derive other rights. Meta-rights can be thought of as usage
`
`rights to usage rights (or other meta—rights). This concept will become clear
`
`based on the description below.
`
`NVA303632.1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 11
`
`Petitioner Apple Inc. - Exhibit 1002, p. 11
`
`

`
`Attorney Docket No. 11 1325-291300
`
`[0038] 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 rights can have conditions, meta-rights
`
`can also have conditions. Meta-rights can also be associated with other
`
`meta-rights.
`
`[0039]
`
`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.
`
`[0040]
`
`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
`
`NVA303632.1
`
`10
`
`Petitioner Apple Inc. - Exhibit 1002, p. 12
`
`Petitioner Apple Inc. - Exhibit 1002, p. 12
`
`

`
`Attorney Docket No. 1 11325-291300
`
`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.
`
`[0041]
`
`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.
`
`[0042]
`
`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
`
`NVA303632.1
`
`1 1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 13
`
`Petitioner Apple Inc. - Exhibit 1002, p. 13
`
`

`
`Attorney Docket No. 1 11325-291300
`
`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 cany 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 detennine 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—distr1'bution 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.
`
`[0043]
`
`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 righ