EP 0 679 977 A1
`
`mow.
`
`:w
`
`mm
`
`0E
`
`
`
`mhhwmeQ>w¥.EOmxw
`
`New
`
`mun“.DHwzHIO<Z
`
`mun“.DHmzHIO<z
`
`
`
`mHDmHELkwhkwyma
`
`1:3QmeEozw
`
`>wv_
`
`
`
`$5232meDJQZH
`
`
`
`0mm:mhmOmZH“.0
`
`zOE<0ECzwDH
`
`wzHIQ<Z
`
`
`
`VmeOHmDo
`
`onh<zmomzH
`
`
`
`wthEHH<zwhm>m
`
`IE3QmeEozw
`
`>wv_
`
`
`
`wzHIo<ZmwQDJozH
`
`45.9.
`
`ow30.j<momwmzoz
`
`
`
`noH2300mwQDJQZH
`
`m._.m0mxw
`
`29.256qu
`
`MwZOHmDo
`
`
`
`wHDmHEL/xwkhwyma
`
`It}thm>mozw
`
`>w¥
`
`
`
`wHDmECkzwhm>m
`
`
`
`1.53Qwhnimozw
`
`>wv_
`
`mam
`
`
`
`mun”.>wv_
`
`61:”.>m§
`
`Sm
`
`mam
`
`45
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3001
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3001
`
`
`

`

`EP 0 679 977 A1
`
`mH
`m
`
`m
`
`8
`
`So
`
`mm.OE
`
`.EOmxw
`kamHEF/xzwhmkwkamHth‘whhwxwa
`
`
`
`wHDmHmHCxzwkmhwwhamHmHS.whhwyma
`
`
`
`moHm:mwODJQZHIt}wh<0n5
`
`
`1:3owhmEozm1:3awhmEoZm
`1.53owhnimozw1:3DmeEozw
`
`wzHIo<z.EOmzH0mHm0m<k
`
`“mus”.DHwzHIo<z"mus”.DHwzHIo<z
`
`.muzm>mv_.EOmzH.wuzu>mv_
`
`
`
`.>wx>wv_
`
`meOHmDomeDwhmomZH
`
`>m§>mv_
`m9.9mzHIQ<Z
`
`wbkwmeQ>w¥
`
`20:535qu
`
`moH2300Dz<
`
`3m
`
`mam
`
`:m
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3002
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3002
`
`

`

`R9298959
`
`\/\momoom
`
`>mx
`
`
`
`mmumzé89mmszoo
`
`€0sz
`
`50m:
`
`OHKoo
`
`5.0sz
`
`<H0wz
`
`zopm>mozm
`
`zOHH<mwmo
`
`zomeomo
`
`zOC<mmmo
`
`mnzn.my
`
`
`
`>wxmmZOPmDo:
`
`
`
`myPQDDOE..
`
`EP 0 679 977 A1
`
`€0sz
`
`Sow:
`
`
`
`onk<mmmOHmOmxm
`
`.Vm.OHu
`
`OF$00
`
`5.52m:
`
`50m:
`
`zopm>mozw
`
`onH<mmmo
`
`zOHEEowD
`
`onk<mmmo
`
`mzHIo<z
`
`onk<oHquzmoH
`
`89£299:12:-
`
`
`
`...<>mm._.zH123:.n
`
`<._.<D
`
` mdu
`
`Ev.mmg
`
`
`
`
`
`EomxmE80:9899.5%:«(m6-
`
`mwmngt.
`
`
`
`6:58445$sz.35-
`
`<k<o
`
`
`
`mwkzbookm0mxm..
`
`47
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3003
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3003
`
`
`
`
`
`
`
`
`
`
`

`

`EP 0 679 977 A1
`
`mab
`
`mmkszoo
`
`
`
`mnzn.>wv_
`
`
`
`
`
`>w¥«wZOHwDou
`
`
`
`
`
`>m§HQDQONE..
`
`mag
`
`zomeon
`
`202.5.me
`
`
`
`Hwomi.(/35Amo—
`
`zopnimowo
`
`2055*me
`
`zomuKoo
`
`
`
`Sow:Eozmz
`
`me
`
`Hwomdc.Koo
`
`o._.9mzHIo<z
`
`
`
`Sow:.Eozmz
`
`
`
`mwkzDoo.EOmxw:
`
`fig$3“
`
`mwhamzoo
`
`
`
`wzHIo<zz<w.._o.
`
`e92msmHEwm£9
`
`#395is:-Bog:9male;9mzioé-93%
`
`<20$528Gog:1:3
`
`Sow:
`
`
`
`
`
`mamzofiéwmozofiémmoEozwz
`
`
`
`
`
`29:83:59onEEozmonEEomo20EKoo
`
`
`
`wzHIQ<ZwomDOm..
`
`DH
`
`szo<z
`
`mam:
`
`
`
`mzmeCkzwknmzoo
`
`:585mmOK89zotéwmoEon:
`
`
`
`m:wzHIo<z
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3004
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3004
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`0 “W“ “m“
`
`EUROPEAN SEARCH REPORT
`-
`
`Wm"
`EP 95 10 5400
`
`DOCUMENTS CONSIDERED TO BE RELEVANT
`
`X
`
`H0-A-94 07204 (UNILOC)
`' abstract; figures 41,2.8 '
`line 5 '
`* page 6.
`line 11 - page 9,
`' page 10,
`line 3 - line 10 '
`' page 12,
`line 7 - page 17.
`
`line 13 '
`
`APPUCATION (lanai)
`
`1,9
`
`GO6F1/00
`GO6F12/14
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` GB-A-Z 136 175 (ATALLA)
`' the whole document '
`
`line 1 '
`line 50 '
`
`
`claims 2,9 '
`
`
`EP-A-0 268 139 (IBM)
`' column 1,
`line 1 - column 3,
`' column 6,
`line 7 - column 7,
`column 9,
`line 20 - line 29 '
`column 19,
`line 9 - line 50 '
`column 21,
`line 6 - line 18 '
`
`I'f
`
`i'
`
`
`
`EP-A-0 561 685 (FUJITSU)
`'
`'
`TED-[NICALl-‘IDDS
`
`..... m
`G06F
`
`
`
`
`mmmchrwmhsheuhwnupfudldins
`
`
`
`
`
`
`mum
`_
`mumumm
`Exi-
`
`
`
`THE HAGUE
`3
`25 July 1995
`Powell, D
`
`umonvorumo oowmxls
`E
`Imam-yuphduzummym
`
`
`X-puflcnlul Ida-3111mm
`a
`hip
`and
`[:11'l3m‘fi'13h‘3m
`Y2wflafllfl§rdmmflqnhdiifimha
`g
`Dzmtdtuhm
`
`
`E Altmanglmnmmqq
`umudtuhoaam
`
`
`OEFm—Iriladbdme
`2
`t:nahadl|¢n-¢mhlfly.mmdhg
`H
`
`
`szndhelmm
`2
`.
`
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3005
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3005
`
`

`

`Europfiiechee Patentamt
`
`European Patent Office3 Office européen des brevets
`
`llllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllll
`
`(11)
`
`EP 0 715 243 A1
`
`(12)
`
`EUROPEAN PATENT APPLICATION
`
`(43) Date 01 publication:
`05.06.1996 Bulletin 1996/23
`
`(51) Int 0162 G06F 1/00, G06F 17/60
`
`(21) Application number: 953084142
`
`(22) Date of filing: 23.11.1995
`
`(84) Designated Contracting States:
`DE FR GB
`
`(30) Priority: 23.11.1994 US 344773
`
`(71) Applicant: XEROX CORPORATION
`Rochester New York 14644 (US)
`
`(72) inventors:
`0 Steflk, Mark J.
`Woodstde, California 94062 (US)
`
`- Plrolll, Peter L.T.
`El Cerrrlto, California 94530 (US)
`- Merkle, Ralph C.
`Sunnyvale, California 94087 (US)
`
`(74) Representative: Goode, Ian Roy et al
`Rank Xerox Ltd
`Patent Department
`Parkway
`Marlow Bucklnghamshlre SL7 1YL (GB)
`
`-
`
`
`
`(54)
`
`System for controlling the distribution and use of digital works having a tee reporting
`mechanism
`
`A fee accounting mechanism tor reporting fees
`(57)
`associated with the distribution and use of digital works.
`Usage rights and fees are attached to digital works. The
`usage rights define how the digital work may be used or
`further distributed. Usage fees are specified as part of
`a usage right. The digital works and their usage rights
`and fees are stored in repositories (201 ). The repositor—
`
`ies control access to the digital works, Upon determina-
`tion that the exercise of a usage right requires a tee, the
`repository generates a tee reporting transaction (302).
`Fee reporting is done to a credit server (301 ). The credit
`server collects the fee information and periodically
`transmits it to a billing clearinghouse (303).
`
`Repository
`
`1
`-
`5
`Billing
`:
`l Clearinghouse -
`l
`303
`E
`
`Fig. 3
`
`
`Pr’med byJowe. 75M! PARIS (FR)
`
`EP0715243A1
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3006
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3006
`
`

`

`Description
`
`EP 0 715 243 A1
`
`The present invention relates to the field of distribution and usage rights enforcement for digitally encoded works.
`A fundamental issue facing the publishing and information industries as they consider electronic publishing is how
`to prevent the unauthorized and unaccounted distribution or usage of electronically published materials. Electronically
`published materials are typically distributed in a digital form and recreated on a computer based system having the
`capability to recreate the materials. Audio and video recordings, software, books and multimedia works are all being
`electronically published. Companies in these industries receive royalties for each accounted for delivery of the mate-
`rials, eg. the sale of an audio CD at a retail outlet. Any unaccounted distribution of a work results in an unpaid royalty
`(e.g. copying the audio recording CD to another digital medium.)
`The ease in which electronically published works can be 'perfectly' reproduced and distributed is a major concern.
`The transmission of digital works over networks is commonplace. One such widely used network is the Internet. The
`Internet is a widespread network facility by which computer users in many universities. corporations and government
`entities communicate and trade ideas and information. Computer bulletin boards found on the Internet and commercial
`networks such as CompuServ and Prodigy allow for the posting and retrieving of digital information. lnforrnation services
`such as Dialog and LEXIS/NEXIS provide databases of current information on a wide variety of topics. Another factor
`which will exacerbate the situation is the development and expansion of the National lnforrnation Infrastructure (the
`NH). It is anticipated that, as the NH grows, the transmission of digital works over networks will increase many times
`over. It would be desirable to utilize the NH for distribution of digital works without the fear of widespread unauthorized
`copying.
`
`The most straightforward way to curb unaccounted distribution is to prevent unauthorized copying and transmis-
`sion. For existing materials that are distributed in digital form, various safeguards are used. in the case of software,
`copy protection schemes which limit the number of copies that can be made or which corrupt the output when copying
`is detected have been employed. Another scheme causes software to become disabled after a predetermined period
`of time has lapsed. A technique used for workstation based software is to require that a special hardware device must
`be present on the workstation in order for the software to run, e.g., see USA—4,932,054 entitled 'Method and Apparatus
`for Protecting Computer Software Utilizing Coded Filter Network in Conjunction with an Active Coded Hardware Device.
`' Such devices are provided with the software and are commonly referred to as dongles.
`Yet another scheme is to distribute software, but which requires a "key' to enable its use. This is employed in
`distribution schemes where 'demos' of the software are provided on a medium along with the entire product. The
`demos can be freely used, but in order to use the actual product, the key must be purchased. These schemes do not
`hinder copying of the software once the key is initially purchased.
`It is an object of the present invention to provide an improved system and method for controlling the use and
`distribution of digital works.
`The invention accordingly provides a system and method as claimed in the accompanying claims.
`In a system for the control of distribution and use of digital works, a fee reporting mechanism for reporting fees
`associated with such distribution and use is disclosed. The system includes a means for attaching usage rights to a
`digital work. The usage rights define how the digital work may be used or further distributed by a possessor of the
`digital work. Usage fees are specified as part of a usage right. The ability to report usage fees may be a condition to
`the exercise of a usage right. Further, different fees may be assigned to different usage rights.
`The present invention enables various usage fee scenarios to be used. Fees may be assessed on a per use basis.
`on a metered basis or based on a predetermined schedule. Fees may also be discounted on a predetermined schedule,
`or they can be marked-up a predetermined percentage (e.g. as a distributor tee). Fee reporting may also be deferred
`to a later time, to accommodate special deals, rebates or some other external information not yet available.
`The present invention supports usage fees in an additive fashion. Usage fees may be reported for a composite
`digital work, Le. a digital work comprised of a plurality of discrete digital works each having their own usage rights, and
`for distributors of digital works. Accordingly, fees to multiple revenue owners can be reported.
`Usage fee reporting is done to a credit server. The credit server collects the fee information and periodically trans-
`mits it to a billing clearinghouse. Alternatively, the credit server may have a pre-allocated credit which is decremented
`as fees are incurred. in this alternative embodiment, the credit server would have to be periodically reallocated with
`credits to enable further use.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`50
`
`A system and method in accordance with the invention will now be described, by way of example, with reference
`to the accompanying drawings, in which:-
`.
`
`55
`
`is a flowchart illustrating a simple instantiation of the operation of the currently preferred embodiment of
`Figure 1
`the present invention.
`
`Figure 2 is a block diagram illustrating the various repository types and the repository transaction flow between
`them in the currently preferred embodiment of the present invention.
`Figure 3 is a block diagram of a repository coupled with a credit server in the currently preferred embodiment of
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3007
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3007
`
`

`

`EP 0 715 243 A1
`
`the present invention.
`Figures 4a and 4b are examples of rendering systems as may be utilized in the currently preferred embodiment
`of the present invention.
`Figure 5 illustrates a contents file layout for a digital work as may be utilized in the currently preferred embodiment
`of the present invention.
`Figure 6 illustrates a contents file layout for an individual digital work of the digital work of Figure 5 as may be
`utilized in the currently preferred embodiment of the present invention.
`Figure 7 illustrates the components of a description block of the currently preferred embodiment of the present
`invention.
`
`Figure 8 illustrates a description tree for the contents file layout of the digital work illustrated in Figure 5.
`Figure 9 illustrates a portion of a description tree corresponding to the individual digital work illustrated in Figure 6.
`Figure 10 illustrates a layout for the rights portion of a description block as may be utilized in the currently preferred
`embodiment of the present invention.
`Figure 11 is a description tree wherein certain d—blocks have PRINT usage rights and is used to illustrate 'strict'
`and 'lenient' rules for resolving usage rights conflicts.
`'
`Figure 12 is a block diagram of the hardware components of a repository as are utilized in the currently preferred
`embodiment of the present invention.
`Figure 13 is a block diagram of the functional (logical) components of a repository as are utilized in the currently
`preferred embodiment of the present invention.
`Figure 14 is diagram illustrating the basic components of a usage right in the currently preferred embodiment of
`the present invention.
`Figure 15 lists the usage rights grammar of the currently preferred embodiment of the present invention.
`Figure 16 is a flowchart illustrating the steps of certificate delivery, hotlist checking and performance testing as
`performed in a registration transaction as may be performed in the currently preferred embodiment of the present
`invention.
`
`Figure 17 is a flowchart illustrating the steps of session information exchange and clock synchronization as may
`be perlormed in the currently preferred embodiment of the present invention, after each repository in the registration
`transaction has successfully completed the steps described in Figure 16.
`Figure 18 is a flowchart illustrating the basic flow for a usage transaction, including the common opening and
`closing step, as may be performed in the currently preferred embodiment of the present invention.
`Figure 19 is a state diagram of server and client repositories in accordance with a transport protocol followed when
`moving a digital workfrom the server to the client repositories, as may be perlormed in the currently preferred embod-
`iment of the present invention.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`OVERVIEW
`
`40
`
`A system for controlling use and distribution of digital works is disclosed. The present invention is directed to
`supporting commercial transactions involving digital works.
`Herein the terms 'digital work', 'work' and 'content' refer to any work that has been reduced to a digital repre-
`sentation. This would include any audio, video, text, or multimedia work and any accompanying interpreter (e.g. soft-
`ware) that may be required for recreating the work. The term composite work refers to a digital work comprised of a
`collection of other digital works. The term 'usage rights' or "rights' is a term which refers to rights granted to a recipient
`of a digital work. Generally, these rights define how a digital work can be used and if it can be further distributed. Each
`usage right may have one or more specified conditions which must be satisfied before the right may be exercised.
`Figure 1 is a high level flowchart omitting various details but which demonstrates the basic operation of the present
`invention. Referring to Figure 1, a creator creates a digital work, step 101. The creator will then determine appropriate
`usage rights and fees, attach them to the digital work, and store them in Repository 1, step 102. The determination of
`appropriate usage rights and fees will depend on various economic factors. The digital work remains securely in Re—
`pository 1 until a request for access is received. The request for access begins with a session initiation by another
`repository. Here a Repository 2 initiates a session with Repository 1, step 103. As will be described in greater detail
`below, this session initiation includes steps which helps to insure that the respective repositories are trustworthy As-
`suming that a session can be established, Repository 2 may then request access to the Digital Work for a stated
`purpose, step 104. The purpose may be, for example, to print the digital work or to obtain a copy of the digital work.
`The purpose will correspond to a specific usage right. In any event, Repository 1 checks the usage rights associated
`with the digital work to determine if the access to the digital work may be granted, step 105. The check of the usage
`rights essentially involves a determination of whether a right associated with the access request has been attached to
`the digital work and if all conditions associated with the right are satisfied. If the access is denied, repository 1 terminates
`the session with an error message, step 106. If access is granted, repository 1 transmits the digital work to repository
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3008
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3008
`
`

`

`EP 0 715 243 A1
`
`2, step 107. Once the digital work has been transmitted to repository 2, repository 1 and 2 each generate billing infor-
`mation for the access which is transmitted to a credit server, step 108. Such double billing reporting is done to insure
`against attempts to circumvent the billing process.
`Figure 2 illustrates the basic interactions between repository types in the present invention. As will become apparent
`from Figure 2, the various repository types will'serve different functions. It is fundamental that repositories will share
`a core set of functionality which will enable secure and trusted communications. Referring to Figure 2, a repository
`201 represents the general instance of a repository. The repository 201 has two modes of operation; a server mode
`and a requester mode. When in the server mode, the repository will be receiving and processing access requests to
`digital works. When in the requester mode. the repository will be initiating requests to access digital works. Repository
`201 is general in the sense that its primary purpose is as an exchange medium for digital works. During the course of
`operation, the repository 201 may communicate with a plurality of other repositories, namely authorization repository
`202, rendering repository 203 and master repository 204. Communication between repositories occurs utilizing a re-
`pository transaction protocol 205.
`Communication with an authorization repository 202 may occur when a digital work being accessed has a condition
`requiring an authorization. Conceptually, an authorization is a digital certificate such that possession of the certificate
`is required to gain access to the digital work. An authorization is itself a digital work that can be moved between
`repositories and subjected to fees and usage rights conditions. An authorization may be required by both repositories
`involved in an access to a digital work.
`Communication with a rendering repository 203 occurs in connection with the rendering of a digital work. As will
`be described in greater detail below, a rendering repository is coupled with a rendering device (e.g. a printer device)
`to comprise a rendering system.
`Communication with a master repository 205 occurs in connection with obtaining an identification certificate. lden-
`tification certificates are the means by which a repository is identified as 'trustworthy'. The use of identification certif-
`icates is described below with respect to the registration transaction.
`Figure 3 illustrates the repository 201 coupled to a credit server 301. The credit server 301 is a device which
`accumulates billing information for the repository 201. The credit server 301 communicates with repository 201 via
`billing transactions 302 to record billing transactions. Billing transactions are reported to a billing clearinghouse 303
`by the credit server 301 on a periodic basis. The credit server 301 communicates to the billing clearinghouse 303 via
`clearinghouse transactions 304. The clearinghouse transactions 304 enable a secure and encrypted transmission of
`information to the billing clearinghouse 303.
`
`RENDERING SYSTEMS
`
`A rendering system is generally defined as a system comprising a repository and a rendering device which can
`render a digital work into its desired form, Examples of a rendering system may be a computer system, a digital audio
`system, or a printer. A rendering system has the same security features as a repository. The coupling of a rendering
`repository with the rendering device may occur in a manner suitable for the type of rendering device.
`Figure 4a illustrates a printer as an example of a rendering system. Referring to Figure 4, printer system 401 has
`contained therein a printer repository 402 and a print device 403. It should be noted that the the dashed line defining
`printer system 401 defines a secure system boundary. Communications within the boundary are assumed to be secure.
`Depending on the security level, the boundary also represents a barrier intended to provide physical integrity. The
`printer repository 402 is an instantiation of the rendering repository 205 of Figure 2, The printer repository 402 will in
`some instances contain an ephemeral copy of a digital work which remains until it is printed out by the print engine
`403. In other instances, the printer repository 402 may contain digital works such as fonts, which will remain and can
`be billed based on use. This design assures that all communication lines between printers and printing devices are
`encrypted, unless they are within a physically secure boundary. This design feature eliminates a potential 'fault' point
`through which the digital work could be improperly obtained. The printer device 403 represents the printer components
`used to create the printed output.
`
`Also illustrated in Figure 4a is the repository 404. The repository 404 is coupled to the printer repository 402. The
`repository 404 represents an external repository which contains digital works.
`Figure 4b is an example of a computer system as a rendering system. A computer system may constitute a 'multi-
`function' device since it may execute digital works (e.g. software programs) and display digital works (e.g. a digitized
`photograph). Logically, each rendering device can be viewed as having its own repository, although only one physical
`repository is needed. Referring to Figure 4b, a computer system 410 has contained therein a display/execution repos-
`itory 411. The display/execution repository 411 is coupled to display device. 412 and execution device 413. The dashed
`box surrounding the computer system 410 represents a security boundary within which communications are assumed
`to be secure. The display/execution repository 411 is further coupled to a credit server 414 to report any fees to be
`billed for access to a digital work and a repository 415 for accessing digital works stored therein.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`50
`
`55
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3009
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3009
`
`

`

`STRUCTURE OF DIGITAL WORKS
`
`EP 0 715 243 A1
`
`Usage rights are attached directly to digital works. Thus, it is important to understand the structure of a digital work.
`The structure of a digital work, in particular composite digital works, may be naturally organized into an acyclic structure
`such as a hierarchy. For example, a magazine has various articles and photographs which may have been created
`and are owned by diflerent persons. Each of the articles and photographs may represent a node in a hierarchical
`structure. Consequently, controls, i.e. usage rights, may be placed on each node by the creator. By enabling control
`and fee billing to be associated with each node, a creator of a work can be assured that the rights and fees are not
`circumvented.
`
`In the currently preferred embodiment, the file information for a digital work is divided into two files: a 'contents'
`file and a 'description tree' file. From the perspective of a repository, the 'contents' file is a stream of addressable
`bytes whose format depends completely on the interpreter used to play. display or print the digital work. The description
`tree file makes it possible to examine the rights and fees for a work without reference to the content of the digital work.
`It should be noted that the term description tree as used herein refers to any type of acyclic structure used to represent
`the relationship between the various components of a digital work.
`Figure 5 illustrates the layout of a contents file. Referring to Figure 5, a digital work is comprised of story A 510,
`advertisement 511, story B 512 and story C 513.
`It is assumed that the digital work is stored starting at a relative
`address of 0. Each of the parts of the digital work are stored linearly so that story A 510 is stored at approximately
`addresses 0-30.000, advertisement 511 at addresses 30.001-40,000, story B 512 at addresses 40,001-60,000 and
`story C 513 at addresses 60,001-85K. The detail of story A 510 is illustrated in Figure 6. Referring to Figure 6, the
`story A 510 is funher broken down to show text 614 stored at address 0-1500, soldier photo 615 at addresses
`1501-10,000, graphics 616 stored at addresses 10,001 -25,000 and sidebar 617 stored address 25,001 -30,000. Note
`that the data in the contents file may be compressed (for saving storage) or encrypted (for security).
`From Figures 5 and 6 it is readily observed that a digital work can be represented by its component parts as a
`hierarchy. The description tree for a digital work is comprised of a set of related descriptor blocks (d-blocks). The
`contents of each d—block is described with respect to Figure 7. Referring to Figure 7, a d~block 700 includes an identifier
`701 which is a unique identifier for the work in the repository, a staning address 702 providing the start address of the
`first byte of the work, a length 703 giving the number of bytes in the work, a rights ponion 704 wherein the granted
`usage rights and their status data are maintained, a parent pointer 705 for pointing to a parent d~block and child pointers
`706 for pointing to the child d~blocks. In the currently preferred embodiment, the identifier 701 has two parts. The first
`part is a unique number assigned to the repository upon manufacture. The second part is a unique number assigned
`to the work upon creation. The rights portion 704 will contain a data structure, such as a look-up table, wherein the
`various information associated with a right is maintained. The information required by the respective usage rights is
`described in more detail below. D-blocks form a strict hierarchy. The top d-block of a work has no parent; all other d-
`blocks have one parent. The relationship of usage rights between parent and child d~blocks and how conflicts are
`resolved is described below.
`
`A special type of d~block is a 'shell' d-block. A shell d-block adds no new content beyond the content of its parts.
`A shell d-block is used to add rights and fee information, typically by distributors of digital works.
`Figure 8 illustrates a description tree for the digital work of Figure 5. Referring to Figure 8. a top d~b|ock 820 for
`the digital work points to the various stories and advertisements contained therein. Here, the top d~block 820 points to
`d-block 821 (representing story A 510), d-block 822 (representing the advertisement 511), d—block 823 (representing
`story B 512) and and d-block 824 (representing story C 513).
`The portion of the description tree for Story A 510 is illustrated in Figure 9. D~block 925 represents text 614, d-
`block 926 represents photo 615, d-block 927 represents graphics 616 by and d-block 928 represents sidebar 617.
`The rights portion 704 of a descriptor block is further illustrated in Figure 10. Figure 10 illustrates a structure which
`is repeated in the rights portion 704 for each right. Referring to Figure 10, each right will have a right code field 1050
`and status information field 1052. The right code field 1050 will contain a unique code assigned to a right. The status
`information field 1052 will contain information relating to the state of a right and the digital work. Such information is
`indicated below in Table 1. The rights as stored in the rights portion 704 may typically be in numerical order based on
`the right code.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`40
`
`50
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3010
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3010
`
`

`

`EP 0 715 243 A1
`
`TABLE 1
`
`DIGITAL WOFIK STATE INFORMATION
`
`
`a...
`
`
`
`
`
`A counter of the number of copies of a work that are in use. Incremented when
`another copy is used; decremented when use is completed.
`
`OUT
`
`Indicator of the maximum number of time-units that a document can be loaned
`
`Indicator that the current work is a loaned out copy of an authorized digital work.
`Indicator of the remaining time of use on a metered document right.
`A string containing various identifying information about a document. The exact
`format of this is not specified, but it can include information such as a publisher
`name, author name, ISBN number. and so on.
`
`A handle identifying a revenue owner for a digital work. This is used reporting
`usage fees.
`
`The date that the digital work was published.
`
`A list of events recording the repostories and dates for operations that copy,
`transfer, backup, or restore a digital work.
`
`Copies-in-Use
`
`Loan—Period
`
`Leaner-Copy
`
`Ftemaining~TIme
`
`Document-Descr
`
`String
`
`Revenue-Owner
`
`Publication-Date
`
`History-list
`
`History-Rec
`
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`50
`
`55
`
`The approach for representing digtal works by separating description data from content assumes that parts of a
`file are contiguous but takes no position on the actual representation of content. In particular, it is neutral to the question
`of whether content representation may take an object oriented approach. It would be natural to represent content as
`objects. In principle, it may be convenient to have content objects that include the billing structure and rights Information
`that is represented in the d-blocks. Such variations in the design of the representation are possible and are viable
`alternatives but may introduce processing overhead, e.g. the interpretation of the objects.
`Digital works are stored in a repository as part of a hierarchical file system. Folders (also termed directories and
`sub—directories) contain the digital works as well as other folders. Digital works and folders in a folder are ordered in
`alphabetical order. The digital works are typed to reflect how the files are used. Usage rights can be attached to folders
`so that the folder itself is treated as a digital work. Access to the folder would then be handled in the same fashion as
`any other digital work As will be described in more detail below, the contents of the folder are subject to their own rights.
`Moreover, file management rights may be attached to the folder which define how folder contents can be managed.
`
`ATTACHING USAGE RIGHTS TO A DIGITAL WOFIK
`
`It is fundamental to the present invention that the usage rights are treated as part of the digital work As the digital
`work is distributed, the scope of the granted usage rights will remain the same or may be narrowed. For example, when
`a digital work is transferred from a document server to a repository, the usage rights may include the right to loan a
`copy for a predetermined period of time (called the original rights). When the repository loans out a copy of the digital
`work, the usage rights in the leaner copy (called the next set of rights) could be set to prohibit any further rights to loan
`out the copy. The basic idea is that one cannot grant more rights than they have.
`The attachment of usage rights into a digital work may occur in a variety of ways. If the usage rights will be the
`same for an entire digital work, they could be attached when the digital work is processed for deposit in the digital work
`sewer. In the case of a digital work having different usage rights for the various components, this can be done as the
`digital work is being created. An authoring tool or digital work assembling tool could be utilized which provides for an
`automated process of attaching the usage rights.
`_
`As will be described below, when a digital work is copied, transferred or loaned, a 'next set of rights' can be
`specified. The'next set of rights" will be attached to the digital work as it is transported.
`
`Resolving Conflicting Rights
`
`Because each part of a digital work may have its own usage rights. there will be instances where the rights of a
`'contained part' are different from its parent or container part. As a result, conflict rules must be established to dictate
`when and how a right may be exercised. The hierarchical structure of a digital work facilitates the enforcement of such
`rules. A 'strict' rule would be as follows: a right for a part in a digital work is sanctioned if and only if it is sanctioned
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3011
`
`Petitioner Apple Inc. - Exhibit 1002, p. 3011
`
`

`

`EP 0 715 243 A1
`
`for the part, for ancestor d-blocks c