llllllllllllllllllllllllllllll OldST}NW
`
`PTO/SB/05 (03-01)
`A mved for use thmuh I0/31/2002. OMB 0651-0032
`
`.
`
`111325035000
`
`UTILITY
`PATENT APPLICATION
`
`TRANSMITTAL
`(Onlyfor new nonprovisional applications under 3 7 CFR I.53(b))
`
`svsrr-:1v1 AND METHOD FOR RIGHTS
`OFFERING AND GRANTING USING
`SHARED STATE VARIABLES
`
`
`
`APPLICATION ELEMENTS
`
`
`
`
`
`alert! a lication contents.
`See MPEP chater 600 concerrrin utili
`
` 7. El CD-ROM or CD-R in duplicate, large table or
`1.
`IE Fee Transmittal Form (e.g., PTO/SB/l 7)
`,\
`
`(Submit an original and a duplicateforfeeprocessing)
`to
`Computer Program (Appendix)
`
`2. U Applicant claims small entity status.
`8. Nucleotide and/or Amino Acid Sequence Submission
`8
`See 37 CFR 1.27.
`
`*1‘
`(ifapplicable, all necessary)
`a. C] Computer Readable Form (CRF)
`
`b. Specification Sequence Listing on:
`
`i. E] CD-ROM or CD-R (2 copies; or
`
`ii. D paper
`c. U Statements verifying identity of above co ies
`ACCOMPANYING APPLICATION PARTS
`
`
`
`3.
`
`
`
`
`
`
`
`
`
`
`
`lllllllllllllllllllllll
`
`
`
`[Total Pages 43]
`lg Specification
`(pref:-red 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 (ifapplicable)
`Background of the Invention
`-
`- Brief Summary of the Invention
`- Brief Description of the Drawings (rffiled)
`- Detailed Description
`-
`Claim(s)
`- Abstract of the Disclosure
`
`
`
`
`
`9. El Assignment Papers (cover sheet & document(s))
`10. Cl 37 CFR 3.73(b) Statement
`CI
`Power of
`(when there is an assignee)
`Attorney
`1 l. B English Translation Document (ifapplicable)
`12. U Infomration Disclosure
`CI Copies of IDS
`Statement (IDS)/PT0- l 449
`Citations
`13. D Preliminary Amendment
`14. El Return Receipt Postcard (MPEP 503)
`(Should be specifically itemized)
`15. D Certified Copy of Priority Document(s)
`(tfforeign priority is claimed)
`16. D Nonpublication request under 35 U.S.C.
`I22(b)(2)(B)(i). Applicant must attach form
`PTO/SB/35 or its equivalent.
`17. C] Other.
`
`
`
`lg Drawing(s) (35 U.S.C. 113) 23 Figgres [ Total SheeLr I7]
`4.
`5. Oath or Declaration
`[ Total Pages 0 ]
`a. CI Newly executed (original or copy)
`b.
`I21 Copy from a prior application (37 CFR l.63(d))
`(for continuation/divisional with Box I8 completed)
`i. D DELETION OF lNVENTOR(S)
`Signed statement attached deleting inventor(s)
`named in the prior application, see 37 CFR
`1.63(d)(2) and l.33(b)
`6. E Application Data Sheet. see 37 CFR 1.76
`
`
`
`
`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 1. 76:
`
`D Continuation
`E Continuation-in-part (CIP) of prior application No: 10/162 2l2
`
`
`Examiner NotYetAssigr_1ed
`Group/ArtUnit: 3621
`Prior application infomiationz
`
`For CONTINUATION OR DIVISIONAL APPS only: The entire disclosure of the prior application, from which an oath or declaration is supplied under
`
`Box 5b, 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
`
`»( ~'
`p
`or D Correspondence address below
`
`
`
`
`
`
`—i——
`
`—‘t
`
`
`
`
`
`
`43,224
`
`Date
`
`October 4, 2004
`
`W326635.l
`
`Petitioner Apple Inc. — Exhibit 1006, p. 1
`
`Petitioner Apple Inc. - Exhibit 1006, p. 1
`
`

`
`Patentfees are subject to annual revision.
`
`APPli¢8li0n Number
`Filing Date
`First Named Inventor
`Examiner Name
`A" Uni‘
`
`Cnmlerei Known
`
`Not Yet Assi r ed
`October 4’
`Maj NGUYEN, e; g[_
`Not Yet Assigned
`Not Yet Assigned
`
`Attorney Docket No-
`
`I I
`
`METHOD OF PAYMENT check all that a Iv
`
`FEE CALCULATION continued
`
`D Check D CreditCard D Money D Other D None
`Order
`
`3’ ADDITIONAL FEES
`
`[3 Dep0ShAcc0um:
`Deposit
`Account
`I 9-23 80
`Number
`
`Large Entity
`
`Small Entity
`Fee
`Fee
`Code
`(5)
`2051
`65
`2052
`25
`
`Deposit
`Account
`Name
`
`_
`Nixon Peabody LLP
`
`_
`_
`The Commissioner is authorized to: (check all that apply)
`
`El Credit any overpaymenis
`
`charge fee(S) indicated below
`[21
`E Charge any additional fee(s)
`D Charge fee(s) indicated below, except for the filing fee
`‘° ‘'‘° "b°"°"d°“‘ifi°" “°P°S" "°°°““‘
`FEE CALCULATION
`1, BASIC FILING FEE
`Large Entity
`Small Entity
`F
`F
`F
`F
`Cffde
`(Se;
`C3;
`(Se;
`
`F D
`ee
`
`'
`'
`escnptlon
`
`Fee Paid
`
`790.00
`
`EXTRA CLAIM FEES FOR UTILITY AND REISSUE
`Fee from
`below
`
`Extra Claims
`x
`
`-20‘-=
`
`Fee Paid
`$342.00
`
`Fee Dacrlption
`
`Surcharge — late filing fee or oath
`Surcharge - late provisional filing fee or cover
`sheet
`
`Non—English specification
`.
`.
`.
`For filing a request for ex parre reexanunation
`Requesting publication of SIR prior to Examiner
`action
`BC on
`R°;l“°5‘5"S P“"“°"‘i°“ °f Sm 3”" E"““i"°'
`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 fifi.h month
`Notice of Appeal
`
`Filing a brief in support of an 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)
`Desi?“ 155"‘ f“
`Plant issue fee
`
`Petitions to the Commissioner
`Processing fee under 37 CFR l.l7(q)
`5UbmiSSi0n 0f1l'|f0l'|'nflli0|'| DISCIOSUN SUN
`Recording each patent assignment per property
`(times number of properties)
`Filingasubmission aster final rejection
`(37 CFR l.l29(a))
`For each additional invention to be examined
`(37 CFR l.l29(b))
`
`Request for Continued Examination (RCE)
`Request for expedited examination of a design
`application
`
`130
`2,520
`920’
`
`‘>340’
`55
`215
`
`1053
`1812
`1804
`
`1305
`2251
`2252
`2253
`2254
`2255
`2401
`
`2402
`2403
`
`1451
`2452
`2453
`2501
`25”
`2503
`
`1460
`1807
`1305
`8021
`
`2809
`
`2810
`?
`2801
`1802
`
`Other fee (specify)
`
`[00]
`1002
`1003
`1004
`1005
`
`2.
`
`Total Claims
`
`Independent
`Claims
`
`Multiple Dependent
`Large Entity
`Fee
`Fee
`
`Code (S)
`1202
`18
`
`1201
`1203
`
`1204
`
`88
`300
`
`38
`18
`
`2001
`2002
`2003
`2004
`2005
`
`395
`Us
`275
`395
`so
`
`Utility flung fee
`Design filing fee
`Plant filing fee
`Reissue filing fee
`Provisional filing fee
`
`SUBTOTAL (I)
`
`$79030
`
`-3"‘ = :] X Z
`
`x :1
`
`Fee Description
`
`Claims in excess of 20
`
`Small Entity
`Fee
`Fee
`
`Code
`2202
`
`(S)
`9
`
`2201
`2203
`
`2204
`2205
`
`44
`150
`
`44
`9
`
`Independent claims in excess of?»
`Multiple dependentclaim,il'not paid
`
`‘Reduced by Basic Filing Fee Paid
`
`SUBTOTAL (3)
`
`
`
`;:i;:;515::t;';‘:°P°“d°“‘ °'‘'““5 °‘’"
`" Reissue clain1s in excess of20 and
`over original patent
`
`CERTIFICATE or MAILING OR TRANSMISSION [37 CFR l.8(a)]
`I h°'°'>Y “"55? “W “"5 °°"“°5P°"de"°° ‘-5 b°i"8=
`deposited with the United States Postal Service on the date shown below with sufficient
`El
`
`SUB-I-0-I-AL 2
`$342 00
`( )
`“or number previously paid, if greater, For Reissues, see above
`
`postage as first class mail in an envelope addressed to: Mail Stop j___,
`Commissioner for Patents, P. O. Box 1450, Alexandna, VA 22313-1450
`transmitted by facsimile on the date shown below to the United States Patent and
`Trademark Office at (703)
`-
`
`Date
`
`Signature
`
`1- d or rinted name
`
`
`
`Comlete i a licable
`‘2°2’5"5'”°“
`“3’”“
`"W 1‘ ““a‘“*“ A
`—.IlIlIIIl % October 4, 2004
`
`
`‘-
`v V "
`SEND TO: Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`SUBMITTED BY
`
`
`
`
`
`W326643.1
`
`
`
`Petitioner Apple Inc. — Exhibit 1006, p. 2
`
`Petitioner Apple Inc. - Exhibit 1006, p. 2
`
`

`
`.':l'
`l‘.
`
`Attorney Docket No. 111325-235000
`
`SYSTEM AND METHOD FOR RIGHTS OFFERING AND GRANTING
`
`USING SHARED STATE VARIABLES
`
`RELATED APPLICATION DATA
`
`[0001]
`
`This application is a continuation-in-part application of co-pending
`
`application Ser. No. 10/162,212 filed on June 5, 2002, which is a continuation-
`
`in-part application of application Ser. No. 09/867,745 filed on May 31, 2001,
`
`and which claims benefit
`
`from U.S. provisional
`
`application Ser.
`
`No.
`
`60/296,113, filed in June 7, 2001, U.S. provisional application, Serial No.
`
`60/331,625 filed in November 20, 2001, and U.S. provisional application Ser.
`
`No. 60/331,624 filed on November 20, 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 offering and granting of
`
`rights and more particularly to a method, system and device for offering and
`
`granting of rights using shared state variables.
`
`BACKGROUND OF THE INVENTION
`
`[0003]
`
`The digital age has greatly increased concerns about ownership,
`
`access, and control of copyrighted information,
`
`restricted services and
`
`valuable resources. Rapid evolution and wide deployment has occurred for
`
`computers, and other electronic devices such as cellular phones, pagers,
`
`PDAs, and e-book readers, and these devices are interconnected through
`
`communication links including the Internet,
`
`intranets and other networks.
`
`These interconnected devices are especially conducive to publication of
`
`content, offering of services and availability of resources electronically.
`
`[ooo4]
`
`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
`
`NVA303631.1
`
`Petitioner Apple Inc. — Exhibit 1006, p. 3
`
`Petitioner Apple Inc. - Exhibit 1006, p. 3
`
`

`
`Attorney Docket No. 11 1325-235000
`
`owners during the distribution and use of digital works. Efforts to resolve this
`
`problem have been termed "lntellectual Property Rights Management"
`
`(“lPRM"),
`
`“Digital Property Rights Management" (“DPRM"),
`
`“lnte|lectual
`
`Property Management” (“lPM”), "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
`
`5,629,980,
`
`the disclosures of which are incorporated herein by reference,
`
`disclose DRM systems addressing these issues.
`
`[0005]
`
`Two basic DRM schemes have been employed, secure containers
`
`and trusted systems. A “secure container” (or simply an encrypted document)
`
`offers a way to keep document contents encrypted until a set of authorization
`
`conditions are met and some copyright terms are honored (e.g., payment for
`
`use). After the various conditions and terms are verified with the document
`
`provider, the document is released to the user in clear form. Commercial
`
`products such as Cryptolopes and Digiboxes fall into this category. Clearly,
`
`the secure container approach provides a solution to protecting the document
`
`during delivery over insecure channels, but does not provide any mechanism
`
`to prevent legitimate users from obtaining the clear document and then using
`
`and redistributing it in violation of content owners’ intellectual property.
`
`[0006]
`
`In the “trusted system" approach, the entire system is responsible
`
`for preventing unauthorized use and distribution of the document. Building a
`
`trusted system usually entails introducing new hardware such as a secure
`
`processor, secure storage and secure rendering devices. This also requires
`
`that all software applications that run on tmsted systems be certified to be
`
`trusted. While building tamper-proof trusted systems is a real challenge to
`
`NVA303631.1
`
`2
`
`Petitioner Apple Inc. — Exhibit 1006, p. 4
`
`Petitioner Apple Inc. - Exhibit 1006, p. 4
`
`

`
`Attorney Docket No. 111325-235000
`
`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 (eg, 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.
`
`[0007]
`
`Some DRM systems allow content owners to specify usage rights
`
`and conditions, and associate them with content. These usage rights control
`
`how the recipient thereof can use the content. Usually after a content
`
`distributor or consumer has completed selecting and ordering specific content,
`
`the content is delivered either electronically from some content repository or
`
`via a conventional distribution channel to the recipient, such as tangible media
`
`sent via a common carrier. Corresponding DRM systems used by the
`
`recipient, for example the distributor or consumer, will then interpret the rights
`
`and conditions associated with the content, and use them to control how the
`
`content is distributed and/or used. Examples of usage rights include view,
`
`print and extract the content, and distribute, repackage and loan content.
`
`Associated conditions may include any term upon which the rights may be
`
`contingent such as payment, identification, time period, or the like.
`
`[0008]
`
`U.S. patent 5,634,012, discloses a system for controlling the
`
`distribution of digital documents. Each rendering device has a repository
`
`associated therewith. A predetermined set of usage transaction steps define
`
`a protocol used by the repositories for enforcing usage rights associated with
`
`a document. Usage rights persist with the document content. The usage
`
`rights can permit various manners of use such as, viewing only, use once,
`
`NVA303631.1
`
`3
`
`Petitioner Apple Inc. — Exhibit 1006, p, 5
`
`Petitioner Apple Inc. - Exhibit 1006, p. 5
`
`

`
`distribution, and the like. Usage rights can be contingent on payment or other
`
`conditions.
`
`Attorney Docket No. 11 1325-235000
`
`[0009]
`
`However, there are limitations associated with the above-mentioned
`
`paradigms wherein only usage rights and conditions associated with content
`
`are specified by content owners or other grantors of rights. Once purchased
`
`by an end user, a consumer, or a distributor, of content along with its
`
`associated usage rights and conditions has no means to be legally passed on
`
`to a next recipient in a distribution chain. Further the associated usage rights
`
`have no provision for specifying rights to derive other rights,
`
`i.e. rights to
`
`modify,
`
`transfer, offer, grant, obtain,
`
`transfer, delegate,
`
`track, surrender,
`
`exchange,
`
`transport, exercise,
`
`revoke, or
`
`the like.
`
`Common content
`
`distribution models often include a multi-tier distribution and usage chain.
`
`Known DRM systems do not facilitate the ability to prescribe rights and
`
`conditions for all participants along a content distribution and usage chain.
`Therefore,
`it is difficult for a content owner to commercially exploit content
`
`unless the owner has a relationship with each party in the distribution chain.
`
`SUMMARY OF THE INVENTION
`
`[0010]
`
`Exemplary aspects of the present
`
`invention include a method,
`
`system and device for sharing rights adapted to be associated with items, the
`
`method and system including generating at least one of usage rights and
`
`meta-rights for the items; defining, via the usage rights, a manner of use for
`
`the items; and defining, via the meta-rights, a manner of rights transfer for the
`
`items. The device including receiving at least one of usage rights and meta-
`
`rights for the items; interpreting, via the usage rights, a manner of use for the
`
`items; and interpreting, via the meta-rights, a manner of rights transfer for the
`
`items. The usage rights or the meta-rights include at least one state variable
`
`that is shared by one or more rights.
`
`[0011]
`
`Still other aspects,
`
`features, and advantages of
`
`the present
`
`invention are readily apparent from the following detailed description, simply
`
`NVA303631 .1
`
`4
`
`Petitioner Apple Inc. — Exhibit 1006, p. 6
`
`Petitioner Apple Inc. - Exhibit 1006, p. 6
`
`

`
`Attorney Docket No. 111325—235000
`
`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
`
`[0012]
`
`Exemplary embodiments of this invention will be described in detail,
`
`with reference to the attached drawings in which:
`
`[0013]
`
`Fig.
`
`1
`
`is a schematic diagram of a three-tier model for content
`
`distribution;
`
`[0014]
`
`Fig. 2 is a schematic diagram illustrating rights offering and granting
`
`processes in the model of Fig. 1;
`
`[0015]
`
`Fig. 3(a) is a schematic diagram of a simple supplier-consumer
`
`push model for rights generating, issuing and exercising;
`
`[0016]
`
`Fig. 3(b) is a schematic diagram of a simple supplier-consumer pull
`
`model for rights generating, issuing and exercising;
`
`[0017]
`
`Fig. 4 is a block diagram of a rights offering-granting architecture in
`
`accordance with the preferred embodiment;
`
`[0018]
`
`Figs. 5a and 5b are workflow diagrams for examples of offering and
`
`granting rights between a rights supplier and a rights consumer with a push
`
`and pull model respectively;
`
`[0019]
`
`Fig. 6 is a flow chart of a rights offer generation process in
`
`accordance with the preferred embodiment;
`
`[0020]
`
`Fig. 7 is a flow chart of a rights offer consideration process in
`
`accordance with the preferred embodiment;
`
`NVA303631.1
`
`5
`
`Petitioner Apple Inc. — Exhibit 1006, p. 7
`
`Petitioner Apple Inc. - Exhibit 1006, p. 7
`
`

`
`Attorney Docket No. 11 1325-235000
`
`[0021]
`
`Fig. 8 is a flow chart of a rights offer customization process in
`
`accordance with the preferred embodiment;
`
`[0022]
`
`Fig. 9 is block diagram of a DRM system that may be utilized in
`
`connection with the preferred embodiment;
`
`[0023]
`
`Fig. 10 is a block diagram of an exemplary structure of a license
`
`containing usage rights and meta-rights of the preferred embodiment;
`
`[0024]
`
`Fig. 11 is a schematic illustration of a rights label of the preferred
`
`embodiment;
`
`[0025]
`
`Fig. 12 illustrates an exemplary system including a state-of-rights
`
`server;
`
`[0026]
`
`Fig. 13 illustrates employing of a state variable in deriving exclusive
`
`usage rights;
`
`p
`
`[0027]
`
`Fig. 14 illustrates employing of a state variable in deriving inherited
`
`usage rights;
`
`[0028]
`
`Fig. 15 illustrates employing of a state variable in deriving rights that
`
`are shared among a known set of rights recipients;
`
`[0029]
`
`Fig. 16 illustrates employing of a state variable in deriving rights that
`
`are shared among a dynamic set of rights recipients;
`
`[0030]
`
`Fig. 17 illustrates employing of a state variable in maintaining a
`
`state shared by multiple rights;
`
`[0031]
`
`Fig. 18 illustrates employing of multiple state variables to represent
`
`one state of rights;
`
`[0032]
`
`Fig. 19 illustrates a case where not all rights are associated with
`
`states;
`
`[0033]
`
`Fig. 20 illustrates a case where not all rights which are associated
`
`with states are shared or inherited; and
`
`[0034]
`
`Fig. 21 illustrates a case of rights sharing based on an offer which
`
`does not explicitly include meta-rights.
`
`NVA303631 .1
`
`6
`
`Petitioner Apple Inc. — Exhibit 1006, p. 8
`
`Petitioner Apple Inc. - Exhibit 1006, p. 8
`
`

`
`Attorney Docket No. 111325—235000
`
`DETAILED DESCRIPTION
`
`[0035]
`
`Prior to providing detailed description of the apparatus and method
`
`for offering and granting rights, a description of a DRM system that can be
`
`utilized to specify and enforce usage rights and meta-rights for specific
`
`content, services, or other items is first described below.
`
`[0036]
`
`Fig. 9 illustrates DRM System 10 that includes a user activation
`
`component, in the form of activation server 20, that issues public and private
`
`key pairs, or other identification mechanisms, to content users in a protected
`
`fashion, as is well known. Typically, when a user uses DRM system 10 for
`
`the first
`
`time,
`
`the user installs software that works with, or includes, a
`
`rendering application for a particular content format. The software is installed
`
`in client environment 30, a computer associated with the content recipient, for
`
`example. The software is part of DRM 10 system and is used to enforce
`usage rights for protected content. During the activation process, some
`
`information is exchanged between activation server 20 and client environment
`
`30. Client component 60 preferably is tamper resistant and contains the set
`
`of public and private keys issued by activation server 20 as well as other
`
`components, such as rendering components for example.
`
`[0037]
`
`Rights label 40 is associated with content 42 and specifies usage
`
`rights and meta-rights that are available to a recipient,
`
`i.e. a consumer of
`
`rights, when corresponding conditions are satisfied.
`
`License Server 50
`
`manages the encryption keys and issues licenses 52 for protected content 42.
`
`Licenses 52 embody the actual granting of rights, including usage rights and
`
`meta-rights, to an end user. For example, rights offer 40 may pennit a user to
`
`view content for a fee of five dollars and print content for a fee of ten dollars,
`
`or it may permit a user to offer rights to another user, for example, by utilizing
`
`the concept of meta-rights described below. License ‘52 can be issued for the
`
`view right when the five dollar fee has been paid. Client component 60
`
`interprets and enforces the rights, including usage rights and meta-rights, that .
`
`NVA303631 .1
`
`p
`
`7
`
`Petitioner Apple Inc. — Exhibit 1006, p. 9
`
`Petitioner Apple Inc. - Exhibit 1006, p. 9
`
`

`
`Attorney Docket No. 111325-235000
`
`have been specified in the license. Rights label 40 and license 52 are
`
`described in detail below.
`
`[0038]
`
`Fig. 11 illustrates rights label 40 in accordance with the preferred
`
`embodiment. Rights label 40 includes plural rights options 44. Each rights
`
`option 44 includes usage rights 44a, conditions 44b, and content specification
`
`44c. Content specification 44c can include any mechanism for referencing,
`
`calling,
`
`locating, or otherwise specifying content 42 associated with rights
`
`offer 44.
`
`[0039]
`
`As shown in Fig. 10, license 52 includes license 52a, grant 52b, and
`
`digital signature 52c. Grant 52b includes granted usage rights and/or meta-
`
`rights selected from label. The structure of the grant also includes one or
`
`more principals, to whom the specified usage rights and/or meta-rights are
`
`granted, a list of conditions, and state variables required to enforce the
`
`license. Like usage rights, access and exercise of the granted meta-rights are
`
`controlled by the condition list and state variables as described below.
`
`[0040]
`
`Clear
`
`(unprotected) content can be prepared with document
`
`preparation application 72 installed on computer 70 associated with a content
`
`publisher, a content distributor, a content service provider, or any other party.
`
`Preparation of content consists of specifying the usage rights, meta-rights,
`
`and conditions under which content 42 can be used and distributed,
`
`associating rights label 40 with content 42 and protecting content 42 with
`
`some crypto algorithm. A rights language such as XrML can be used to
`
`specify the rights and conditions. However, the usage rights and meta-rights
`
`can be specified in any manner. Also, the rights can be in the form of a pre-
`
`defined specification or template that is merely associated with the content.
`
`Accordingly,
`
`the process of specifying rights refers to any process for
`
`associating rights with content. Rights label 40 associated with content 42
`
`and the encryption key used to encrypt the content can be transmitted to
`
`license server 50.
`
`NVA303631 .1
`
`8
`
`Petitioner Apple Inc. — Exhibit 1006, p. 10
`
`Petitioner Apple Inc. - Exhibit 1006, p. 10
`
`

`
`Attorney Docket No. 1 11325-235000
`
`[0041]
`
`Rights can specify transfer rights, such as distribution rights, and
`
`can permit granting of rights to others or the derivation of rights. Such rights
`
`are referred to as “meta—rights". Meta-rights are the rights that one has to
`
`manipulate, modify, or otherwise derive other meta-rights or usage rights.
`
`Meta-rights can be thought of as usage rights to usage rights. Meta-rights
`
`can include rights to offer, grant, obtain, transfer, delegate, track, surrender,
`
`exchange, and revoke usage rights to/from others. Meta-rights can include the
`
`rights to modify any of the conditions associated with other rights. For
`example, a meta-right may be the right to extend or reduce the scope of a
`
`particular right. A meta-right may also be the right to extend or reduce the
`
`validation period of a right.
`
`[0042]
`
`Often, conditions must be satisfied in order to exercise the manner
`
`of use in a specified right. For, example a condition may be the payment of a
`
`fee, submission of personal data, or any other requirement desired before
`
`permitting exercise of a manner of use. Conditions can also be “access
`
`conditions" for example, access conditions can apply to a particular group of
`
`users, say students in a university, or members of a book club.
`
`In other
`
`words, the condition is that the user is a particular person or member of a
`
`particular group. Rights and conditions can exist as separate entities or can
`
`be combined.
`
`[0043]
`
`State variables track potentially dynamic states conditions. State
`
`variables are variables having values that represent status of an item, usage
`
`rights, license or other dynamic conditions. State variables can be tracked,
`
`by clearinghouse 90 license or server 30 another device, based on
`
`identification mechanisms in license 52. Further, the value of state variables
`
`can be used in a condition. For example, a usage right can be the right to
`
`print content 42 three times. Each time the usage right is exercised, the value
`
`of the state variable “number of prints” is incremented.
`
`In this example, when
`
`the value of the state variable is three, the condition is not longer satisfied and
`
`content 42 cannot be printed. Another example of a state variable is time. A
`
`NVA303631.1
`
`9
`
`Petitioner Apple Inc. — Exhibit 1006, p. 11
`
`Petitioner Apple Inc. - Exhibit 1006, p. 11
`
`

`
`Attorney Docket No. 111325-235000
`
`condition of license 52 may require that content 42 is printed within thirty
`
`days. A state variable can be used to track the expiration of thirty days.
`
`Further, the state of a right can be tracked as a collection of state variables.
`
`The collection of the change is the state of a usage right represents the usage
`
`history of that right.
`
`[0044]
`
`A typical workflow for DRM system 10 is described below. A
`
`recipient, such as a user, operating within client environment 30 is activated
`
`for receiving content by activation server 20. This results in a public—private
`
`key pair (and some user/machine specific information) being downloaded to
`
`client environment 30 in the form of client software component 60 in a known
`
`manner. This activation process can be accomplished at any time prior to the
`
`issuing of a license.
`
`[0045] When a user wishes to use protected content 42, the user makes a
`
`request for the content 42. For example, a user might browse a Web site
`
`running on Web server 80 associated with a grantor of rights such as a
`
`content distributor, using a browser installed in client environment 30, and
`
`attempt to download protected content 42. During this process, the user may
`
`go through a series of steps possibly including a fee transaction (as in the
`
`sale of content) or other transactions (such as collection of information).
`
`When the appropriate conditions and other prerequisites, such as the
`
`collection of a fee and verification that the user has been activated, are
`
`satisfied, Web server 80 contacts license server 50 through a secure
`
`communications channel, such as a channel using a Secure Sockets Layer
`
`(SSL). License server 50 then generates license 52 for the content and Web
`
`server 80 causes both protected content 42 and license 52 to be downloaded.
`
`License 52 can be downloaded from license server 50 or an associated
`
`device. Content 42 can be downloaded from computer 70 associated with a
`
`publisher, distributor, or other party.
`
`[0046]
`
`Client component 60 in client environment 30 will then proceed to
`
`interpret license 52 and allow use of content 42 based on the rights and
`
`NVA303631.1
`
`1 0
`
`Petitioner Apple Inc. — Exhibit 1006, p. 12
`
`Petitioner Apple Inc. - Exhibit 1006, p. 12
`
`

`
`Attorney Docket No. 111325-235000
`
`conditions specified in license 52. The interpretation and enforcement of
`
`usage rights are well known generally. The steps above may take place
`
`sequentially or approximately simultaneously or in various order.
`
`[0047]
`
`DRM system 10 addresses security aspects of protecting content
`
`42.
`
`In particular, DRM system 10 may authenticate license 52 that has been
`
`issued by license server 50. One way to accomplish such authentication is for
`
`application 60 to determine if the licenses can be trusted.
`
`In other words,
`
`application 60 has the capability to verify and validate the cryptographic
`
`signature of digital signature 52c, or other identifying characteristic of the
`
`license. During the activation step described above, both client environment
`
`30 and license server 50 receive a set of keys in a tamper-resistant software
`
`“package" that also includes other components, such as the necessary
`
`components for activated client environment 30 to verify signature 52 of
`
`license 52 in a known manner. Of course, the example above is merely one
`
`way to effect a DRM system. For example, the license and content can be
`distributed from different entities. Also, rights offer 40 can be associated with
`
`content by a party other than the party preparing the content.
`
`Also,
`
`clearinghouse 90 can be used to process payment transactions and verify
`
`payment prior to issuing a license.
`
`[0048]
`
`For any set of rights, there are two kinds of entities involved, the
`
`’’supplier’’ and the "consumer”. The function of the supplier is to offer , and
`
`possibly grant, the rights, and the function of the consumer is to select, and
`
`possibly exercise the rights. Both the supplier and consumer may actually
`
`represent two or more entities.
`
`In general, multiple entities may collectively
`
`make an offer and grant rights to multiple entities. The supplier and consumer
`
`represent any two entities in the content value chain that have a direct
`
`relationship with each other regarding the granting of rights. At the beginning
`
`of the value chain, the supplier and consumer may be author and publisher.
`
`Going down along the value chain, the supplier and consumer may be a
`
`publisher and another publisher (for content aggregation), a publisher and
`
`NVA303631.1
`
`1 1
`
`Petitioner Apple Inc. — Exhibit 1006, p. 13
`
`Petitioner Apple Inc. - Exhibit 1006, p. 13
`
`

`
`Attorney Docket No. 111325-235000
`
`distributor (for content distribution), a distributor and another distributor (for
`
`multi-tier content distribution), a distributor and a retailer (for content retailing),
`
`a retailer and a consumer (for content consumption), and a consumer and
`
`another consumer (for content supper—distribution or personal lending).
`
`[0049]
`
`An “offer of rights" or “rights offer” expresses how a consumer (e.g.
`
`a content distributor or user) can acquire a particular instance of content
`
`together with its associated usage rights and/or meta—rights. An offer may or
`
`may not contain financial terms. An offer is an expression of mere willingness
`
`to commerce negotiation and also an expression of willingness to grant on
`terms stated. An offer may be expressed in the form of a rights label. A
`
`“consideration of rights” is a process as part of the rights granting in which the
`
`rights consumer has examined the rights being offered and possibly
`
`bargained them and associated terms and conditions. A “choice of rights" is a
`
`selection of rights and their associated tenns and conditions from a rights
`
`offer.
`
`It indicates the intent of the consumer to accept these rights and the
`
`corresponding tenns and conditions. For example, selection can comprise
`
`selecting one option 44 from label 40. “Customization of rights” is a process
`
`as part of the rights g