5,982,889
`[11] Patent Number:
`[19]
`Unlted States Patent
`
`DeMont
`[45] Date of Patent:
`Nov. 9, 1999
`
`U8005982889A
`
`[54] METHOD AND APPARATUS FOR
`DISTRIBUTING INFORMATION PRODUCTS
`
`[76]
`
`Inventor:
`
`Jason Paul DeMont, 244 English
`-
`-
`Place’ BaSkmg Rldge’ NJ’ 07920
`
`[21] Appl. No.: 08/845,805
`[22]
`Filed:
`Apr. 30, 1997
`
`6
`
`........................................................ H04L 9/00
`Int. Cl.
`[51]
`............................... 380/4; 380/23; 280/2864
`[52] US. Cl.
`[58] Field of Search .................................. 380/3, 4, 9, 21,
`380/23’ 44’ 45’ 49’ 59; 711/152; 395/218’
`186, 187.01, 188.01, 602, 609, 610, 612,
`71% 76% 729 725% 729> M 384-389;
`340/825'31’ 82334; 341/7849; 364/400’
`42355122237233/2/552282’652326280/22282694
`'
`'
`’
`'
`’
`'
`’
`'
`References Cited
`
`[56]
`
`U.S. PATENT DOCUMENTS
`8/1987 Applebaum et al.
`....................... 380/4
`7/1989 Francisco .............
`.. 371/53
`
`4/1992 Waite et a1
`380/4
`6/1993 Waite ...........
`380/4
`8/1994 Chou et al.
`................................. 380/4
`
`4,683,968
`4,845,715
`5,103,476
`5,222,134
`5,337,357
`
`5,343,526
`8/1994 Lassers ........................................ 380/4
`
`5,490,216
`.. 380/4
`2/1996 Richardson .
`5,553,139
`..... 380/4
`9/1996 Ross et al.
`
`
`39:23:33 fizz; 3141:1931} ~~~~~
`~ 393$;
`..............................
`,
`,
`10 e e a.
`5,636,277
`6/1997 Nagahama .................................. 380/4
`5,666,411
`9/1997 McCarty .....
`.. 380/4
`
`......... 380/4
`5,751,805
`5/1998 Otsuki et al.
`5/1998 Olsen ................................. 395/187.01
`5,758,069
`Primary Examiner—Tod R. Swann
`Assistant Examiner—Paul E. Callahan
`
`ABSTRACT
`[57]
`A method and apparatus for distributing information prod-
`t
`.
`d
`'b d th t
`.
`1 d
`th
`t
`f
`t'
`25$ lsneesifii Con :52? Eiffenniafiifiié’de831322583
`of ang’end-userZ:J idegntit
`an indicium of a firsf information
`product, and an indiciu3iil of a second information product
`With the string, R, as the key to create a launch code;
`decrypting the launch code with the string, R, to recover the
`authentlcatlon code, the lndlc1um of the end-user’s ldentlty,
`the indicium of the first information product and the indi-
`3min. (f the Second énfirmgttlfin pmd‘gi; fand “ftalhngdth‘:
`rs 1“ (”ma 10“ pro ‘1‘? an
`.6 sew“ 1“ (”ma 10“ pro “C
`onto a computer assoc1ated Wlth the end-user.
`
`4 Claims, 4 Drawing Sheets
`
`110
`______________£__________.________‘
`
`109
`F—__777‘________1’—_______—______-______"777__[’A‘|
`
`OBTAIN
`
`AUTHORIZATION
`400
`
`
`
`405
`
`
`
`
`
`
`
`
`
`INDICIUM OF
`ENCRYPT AUTHENTICATION CODE,
`END-USER’S NAME, AUTHORIZED PRODUCTS
`NAMES AND SUBSCRIPTION EXPIRATION DATES
`WITH R AS KEY TO CREATE LAUNCH CODE
`
`
`
`
`
`
`|——r-v—v->
`TRANSMIT LAUNCH CODE TO END-USER
`RECEIVE LAUNCH CODE FROM PUBLISHER
`|~f411
`
`409
`413
`I
`NOTIFY END-USER
`
`
`NO
`THAT LAUNCH CODE
`
`
`IS NOT ACCEPTABLE
`
`
`NOTIFY END-USER THAT LAUNCH CODE IS
`ACCEPTABLE AND WHICH PRODUCTS HAVE
`BEEN AUTHORIZED AND FOR HOW LONG
`
`DECRYPT LAUNCH CODE WITH R AS KEY
`
`
`
`
`Petitioner Apple - EX. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`US. Patent
`
`N0V.9,1999
`
`Sheet 1 0f4
`
`5,982,889
`
`
`END-USER
`
`RECEIVE THE PRODUCTS
`
`105
`
`FIG.
`
`1
`
`i
`
`i|
`
`I|
`|
`I
`II
`I
`
`Ill
`
`EI
`
`I
`
`I
`I
`
`
`PUBLISHER
`
`START
`
`101
`
`CREATE THE
`INFORMATION PRODUCTS
`
`102
`
`BUILD THE ANCILLARY FILES
`
`103
`
`104
`
`PREPARE FOR DISTRIBUTION
`
`DISTRIBUTE THE PRODUCTS
`
`RUN THE INSTALLER
`
`106
`
`107
`
`108
`N0
`
`
`
`
`LOCATE AND CLEANSE TOKEN
`
`DOES USER DESIRE T0
`SUBSCRIBE OR RE-SUBSCRIBE
`
`TO PRODUCTS ?
`
`1 IO
`
`PROVIDE AUTHORIZATION
`
`OBTAIN AUTHORIZATION
`
`INSTALL PRODUCTS
`
`MEMORIALIZE AUTHORIZATION
`
`1 1 I
`
`I 12
`
`Petitioner Apple - EX. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`
`
`Petitioner Apple - Ex. 1001
`
`

`

`US. Patent
`
`Nov. 9, 1999
`
`Sheet 3 0f 4
`
`5,982,889
`
`FIG. 3
`
`107
`
`: LOCATE AND CLEANSE TOKEN
`
`
`
`501
`
`303
`
`305
`
`SEARCH FOR TOKEN
`
`
`FILE LOCATED ?
`
`
`
`
`
`
`
`DECRYPT FILE
`
`
`
`
`IS THE CANDIDATE
`
`AUTHENTICATION CODE
`
`
`
`CORRECT ?
`
`
`
`HAVE ANY PRODUCT
`
`AUTHORIZATIONS EXPIRED ?
`
`
`
`NOTIFY END-USER WHICH
`
`PRODUCT AUTHORIZATIONS
`
`HAVE EXPIRED
`
`
`
`Petitioner Apple - EX. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`US. Patent
`
`Nov. 9, 1999
`
`Sheet 4 0f 4
`
`5,982,889
`
`
`
`2:\<
`
`
`
`FIIIllllllllllllllllllllllllllll
`
`zgmo
`
`
`
`22295538wm2<zmtzmmznazmWEE
`
`.3m355sz
`
`mmzmzmiE82—E15oz<m5.25:
`
`$12.5228:$85225#58“
`
`mow
`
`.._o2552—.38zo=<o=2m15<EEozm
`
`Emzuozm2o”:85E15oz<mmagma
`mango”:8501::l$.22mEmznozm
`
`
`
`2225053ESQ:
`
`
`
`
`
`WEBzoEm—mxmzoEEommzmoz<332
`
`MES52:5HES8Exm<z1:;
`
`
`
`
`
`$8558WES102255625:
`
`59:303.52a881022525
`m:mm»
`
`
`
`m.vs”582220:5154“5.3525fl
`
`E855E52
`
`Exm<mTE;3852:5#589
`
`m2N
`
`
`m><_._30:8”:
`
`
`12:3oz<39552a3852:52+:$8-02“Czoz
`
`
`
`ozo._30:m8oz<8501::25m
`
`Petitioner Apple - EX. 1001
`
`Petitioner Apple - Ex. 1001
`
`
`
`
`
`
`

`

`5,982,889
`
`1
`METHOD AND APPARATUS FOR
`DISTRIBUTING INFORMATION PRODUCTS
`
`FIELD OF THE INVENTION
`
`The present invention relates to a method and apparatus
`for distributing information products in general, and, more
`particularly, to a method and apparatus for distributing and
`installing computer programs and data.
`
`BACKGROUND OF THE INVENTION
`
`For as long as publishers have been distributing informa-
`tion products, piracy has been a concern. For the purposes of
`this specification the term “information product” includes,
`but is not limited to computer software, data, images, music,
`applets, photographs, animations, video, audio, text, hyper-
`text and multimedia works.
`
`As a practical matter, large-scale piracy committed by
`professional thieves is easier for publishers to detect and
`police because of the inherently commercial and public
`aspects of large-scale piracy. Small-scale piracy committed
`by individuals who, for example, purchase one copy of a
`computer program and install it on three or four computers
`in a small office are more insidious and, in the aggregate,
`economically more harmful to publishers.
`Several
`techniques have been used by publishers of
`information products to impede piracy. When music was
`first distributed on CDs, CD duplicating equipment were
`expensive and rare and publishers implicitly relied on
`“physical security” to impede small-scale copyright infring-
`ers. The theory underlying physical security is that
`the
`difficulty in duplicating the media containing the informa-
`tion product is sufficient to stop most small-scale infringe-
`ment.
`
`When it is difficult for the end-user to duplicate the media,
`or to transfer the information product from one computer to
`another over a network,
`the publisher can be reasonably
`assured that widespread piracy is not occurring. Of course,
`the end-user could lend, lease or sell the media embodying
`the information product to another who would install it, and
`physical security could not prevent it.
`When the technology for duplicating the media embody-
`ing an information product becomes ubiquitous, or it
`becomes easy to copy the information product from one
`computer to another over a network, publishers often
`employ “cryptographic security” to thwart copyright
`infringers.
`According to one technique, the installer accompanying
`the software will not install the software on the end-user’s
`
`computer until an acceptable password is entered by the
`end-user at the time of installation. The password is received
`by the end-user from the publisher after the end-user regis-
`ters with the publisher and the publisher is assured that the
`end-user has paid for the software. Although this technique
`is widely used, it suffers from the weakness that the end-user
`can use the media and password again to install the software
`on another computer. Furthermore, the end-user can post the
`password publicly on an electronic bulletin-board and the
`advantage of the secret password are lost.
`SUMMARY OF THE INVENTION
`
`Some embodiments of the present invention are capable
`of distributing information products without many of the
`costs and restrictions associated with techniques in the prior
`art. In particular, some embodiments of the present invention
`are capable of distributing one or more information products
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`together (e.g., either on a single CD-ROM or electronically
`over a network) while reserving to the publisher the ability
`to control which products are actually installed on an
`end-user’s computer.
`An illustrative embodiment of the present invention com-
`prises the steps of: generating a string, R; encrypting a first
`authentication code, an indicium of an end-user’s identity,
`an indicium of a first information product, and an indicium
`of a second information product with said string, R, as the
`key to create a launch code; decrypting said launch code
`with said string, R, to recover said authentication code, said
`indicium of said end-user’s identity, said indicium of said
`first information product and said indicium of said second
`information product; and installing said first information
`product and said second information product onto a com-
`puter associated with said end-user.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 depicts a flowchart of the steps associated with
`distributing information products in accordance with the
`illustrative embodiment of the present invention.
`FIG. 2 depicts a directed graph that indicates which files
`in a group of files contain hypertext links to which other
`files.
`
`FIG. 3 depicts a flowchart of the detailed steps associated
`with the step of locating and cleansing the token in FIG. 1.
`FIG. 4 depicts a flowchart of the detailed steps associated
`with the steps of providing authorization and obtaining
`information in FIG. 1.
`
`DETAILED DESCRIPTION
`
`invention
`The illustrative embodiment of the present
`facilitates the distribution of a plurality of information
`products by a publisher in such a manner that each product
`can be licensed,
`installed and used independently or in
`combination with other
`information products.
`Advantageously, this is accomplished, in part, through the
`use of a program commonly known as an “installer.” As is
`well known to those skilled in the art, an installer is program
`that is prepared by the publisher of an information product,
`that is distributed along with the information product, and
`that controls the installation of the information product onto
`the end-user’s computer. Although the installer runs on the
`end-user’s computer, it acts as remote agent of the publisher
`to control how and under what circumstances the informa-
`
`tion products are installed on the end-user’s computer.
`Each information product associated with the illustrative
`embodiment constitutes a plurality of hypertext files or “web
`pages” that are accessed by the end-user through a browser
`such as Netscape Navigator or Internet Explorer. Although
`each information product comprises hypertext files, the files
`are not intended to be accessed by the end-user via the
`Internet. Instead, all of the information products are advan-
`tageously distributed together on a single medium (e.g., a
`CD-ROM) or electronically (e.g., via the Internet) and are
`installed on the end-user’s computer, or on an intranet server
`associated with the end-user. It will be clear to those skilled
`
`in the art how to use a browser such as Netscape Navigator
`or Internet Explorer to browse through web pages that are
`stored locally in contrast to using the browser to browse web
`pages that are stored on http servers across the Internet.
`One example of an information product that can be used
`with embodiments of the present
`invention comprises a
`plurality of web pages that constitute some of the legislative,
`administrative and judicial materials associated with patent
`
`Petitioner Apple - Ex. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`5,982,889
`
`3
`law. Another example of an information product that can be
`used with embodiments of the present invention comprises
`a plurality of web pages that constitute some of the
`legislative, administrative and judicial materials associated
`with trademark law. And yet another example of an infor-
`mation product that can be used with embodiments of the
`present invention comprises a plurality of web pages that
`constitute some of the legislative, administrative and judicial
`materials associated with copyright law.
`Information products that work with embodiments of the
`present
`invention need not relate to law, or reference
`materials, or even text. Other information products could
`comprise music, video, multimedia, or data or other
`executables. It will be clear to those skilled in the art how to
`make and use the embodiments of the invention that are
`
`associated with information products that comprise other
`than hypertext files.
`Each information product associated with the illustrative
`embodiment constitutes a single issue of a periodical to
`which an end-user can subscribe and receive monthly
`updates. It will be clear to those skilled in the art that other
`embodiments of the present invention can be used to dis-
`tribute a single information product. It will also be clear to
`those skilled in the art that other embodiments of the present
`invention can be used to distribute one or more information
`
`products that are not part of a serialization or that are part of
`a serialization that issues sporadically, in contrast to peri-
`odically.
`FIG. 1 depicts a flowchart that outlines the steps associ-
`ated with distributing information products in accordance
`with the illustrative embodiment of the present invention.
`I. Create The Information Products
`
`In accordance with step 101, each information product is
`created by the publisher. To assist in describing the illustra-
`tive embodiment,
`three information products are created
`whose subject matter is related. For the purposes of this
`specification,
`the three products are named “Patent Law
`Library,” “Trademark Law Library” and “Copyright Law
`Library.” It will be clear to those skilled in the art how to
`make and use embodiments of the present invention when a
`different number of products are created, or when their
`subject matter is not related, or both.
`the
`For the purposes of the illustrative embodiment,
`Patent Law Library is a set of files that contain Title 35 of
`the United States Code as marked-up in the Hypertext
`Markup Language (“HTML”); the Trademark Law Library
`is a set of files that contain the Lanham Act as marked-up in
`HTML, and the Copyright Law Library is a set of files that
`contain Title 17 of the United States Code as marked-up in
`HTML. The files in each information product are advanta-
`geously viewed on an end-user’s computer through a
`browser such as Netscape Navigator or Internet Explorer.
`Although all three products are advantageously distrib-
`uted together, any one, two or all three of the products can
`be installed into an end-user’s computer. In other words, in
`accordance with the illustrative embodiment, one end-user
`can install just the Patent Law Library although another
`installs both Patent Law Library and Copyright Law Library.
`Because of the perishable nature of the subject matter of
`each of the illustrative products, the Patent Law Library,
`Trademark Law Library and Copyright Law Library are
`each a single issue of a periodical, which issues monthly.
`Each product advantageously comprises one or more files
`within one or more directories in a hierarchical file structure.
`
`When a product contains a large number of files, it is usually
`advantageous to arrange the files in multiple directories. It
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`will be clear to those skilled in the art how to determine
`
`when a specific information product should contain multiple
`directories. For pedagogical reasons, the files within each of
`the three illustrative information products are contained
`within a single directory.
`
`Some or all of the files in the illustrative information
`
`products advantageously contain hypertext links to items in
`other files. For example, the reference in 35 U.S.C. 42(c) to
`section 31 of the Lanham Act can be implemented as a
`hypertext link from the file containing 35 U.S.C. 42(c) in the
`Patent Law Library to the file containing section 31 in the
`Trademark Law Library.
`
`It will be clear to those skilled in the art
`
`that files
`
`associated with other embodiments of the present invention
`can contain, for example, executable programs, data and/or
`references to other files, which target files may be in the
`same or other products. It will also be clear to those skilled
`in the art that information products associated with other
`embodiments of the present
`invention need not contain
`references to other files. It will be clear to those skilled in the
`
`art how to create the files in each product.
`
`All of the files in all of the products are advantageously
`created and arranged in a file structure with the knowledge
`of the name and location in the file structure of each file it
`
`is capable of referencing, regardless of whether the files are
`part of the same information product or not.
`
`The Patent Law Library comprises five files in the hier-
`archical file structure shown in Table 1. The Trademark Law
`
`Library comprises three files in the hierarchical file structure
`shown in Table 2, and the Copyright Law Library comprises
`four files in the hierarchical file structure shown in Table 3.
`
`Advantageously, all three products are designed to install
`into the same hierarchical directory space, relative to what-
`ever the end-user defines, during installation, as the root
`directory for the product(s).
`
`TABLE 1
`
`The files that compose the Patent Law Library.
`File
`Location
`
`File 1
`File 2
`File 3
`File 4
`File 5
`
`\directory1\file1.htm
`\directory1\file2.htm
`\directory1\file3.htm
`\directory1\file4.htm
`\directory1\file5.htm
`
`TABLE 2
`
`The files that compose the Trademark Law Library.
`File
`Location
`
`File 6
`File 7
`File 8
`
`\directory2\file6.htm
`\directory2\file7.htm
`\directory2\file8.htm
`
`Petitioner Apple - Ex. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`5,982,889
`
`5
`
`TABLE 3
`
`The files that compose the Copyright Law Library.
`File
`Location
`
`File 9
`File 10
`File 11
`File 12
`
`\directory3\file9.htm
`\directory3\file10.htm
`\directory3\file11.htm
`\directory3\file12.htm
`
`For pedagogical reasons, the three information products
`in the illustrative embodiment comprise a total of 12 files. In
`commercial applications, it will be clear to those skilled in
`the art
`that a single information product can comprise
`hundreds or thousands of files. It will be clear to those
`
`skilled in the art how to make and use the files that compose
`the three products.
`The books HTML Publishing for Netscape, Stuart Harris
`& Gayle Kidder, Ventana Communications Group, Inc.,
`Research Triangle Park, NC, and HTML: The Definitive
`Guide, Chuck Musciano & Bill Kennedy, O’Reilly &
`Associates, Inc., Sebastopol, Calif., provide an excellent
`overview the creation of files using HTML and are incor-
`porated by reference.
`II. Build The Ancillary Files
`Because (1) each file can contain a hypertext link to a
`target file that may not be in the same information product,
`and (2)
`the information products can be licensed and
`installed separately, the possibility exists that a file can be
`installed on a end-user’s computer that contains a hypertext
`link to a target file that is not installed on the end-user’s
`computer. The result is a hypertext link that, when executed,
`generates a run-time error because the target file is not
`installed on the computer.
`To preclude run-time errors, the installer advantageously
`installs a “dummy” or “nominal” file into the end-user’s
`computer in the same location and with the same name as
`each file that could be referenced but is not also installed.
`
`The nominal file advantageously does not contain the same
`information as the authentic file, but contains a notice that it
`is only a nominal file and that access to the authentic file
`requires the installation of another information product.
`At step 102, ancillary files are built to enable the installer
`to know where to install the nominal files. In the illustrative
`
`embodiment, one ancillary file is built for each information
`product and the ancillary files indicates the name and
`location of each nominal file to be installed when that
`
`information product is installed.
`There are two alternative techniques that can be used by
`the installer for installing the nominal files and the authentic
`files. According to the first technique, the installer installs all
`of the authentic files for all of the information products to be
`installed, and then installs all of the nominal files into those
`locations not containing an authentic file. According to the
`
`6
`second technique, the installer installs all of the nominal files
`for all of the information products to be installed, and then
`installs all of the authentic files to be installed over the
`
`nominal files, perhaps overwriting over some or all of the
`nominal files. The choice of technique advantageously does
`not affect how the ancillary files are built. The installer
`associated with the illustrative embodiment uses the first
`
`technique, but it will be clear to those skilled in the art how
`to make and use embodiments of the present invention that
`use the second technique.
`When the total number of files in all of the information
`
`products is small, each ancillary file associated with each
`information product can exhaustively list all of the files
`associated with every other information product. In contrast,
`when the total number of files in all of the information
`
`products is large, it is advantageous for each ancillary file to
`list only those files actually needed. To determine which files
`are needed, all of the files in all of the information products
`need to be examined to determine which files reference
`which other files.
`
`FIG. 2 depicts an illustrative directed graph that repre-
`sents all of the files in the three illustrative products and
`indicates which files contain hypertext links to other files. It
`will be clear to those skilled in the art how to determine the
`
`topology of the directed graph by examining all of the files
`in all of the products associated with an embodiment of the
`present invention.
`Each file in each product is represented by a polygon
`enclosing a number. Each of the five files associated with the
`Patent Law Library are depicted by a triangle; each of the
`three files associated with the Trademark Law Library are
`depicted by a square and each of the four files associated
`with the Copyright Law Library are depicted by a pentagon.
`The number inside the polygon indicates exactly which file
`it is associated with. For example, the file “file3.htm” is
`depicted by a triangle enclosing the number 3.
`An arrow from one polygon to another indicates that the
`file associated with the first polygon contains at least one
`hypertext link to the file associated with the second polygon.
`A double-ended arrow indicates that both files contain
`
`hypertext links to each other.
`Table 4 provides the same information as does FIG. 2, but
`in tabular format. Each row in Table 4 represents a file in one
`of the three products, and an “X” in a box means that the file
`associated with the row contains a hypertext link to the file
`associated with that column. Like the directed graph in FIG.
`2, the entries in Table 4 are illustrative only. It will be clear
`to those skilled in the art how to make a similar table by
`examining all of the files in all of the information products
`associated with an embodiment of the present invention.
`Although both the directed graph of FIG. 2 and Table 4
`illustrate a tendency for files within an information product
`to reference other files within the same product, there are
`occurrence of files within one product containing references
`to files in other products.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`Petitioner Apple - Ex. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`5,982,889
`
`TABLE 4
`
`Which Files Externally Reference Which Files
`
`-
`
`-----n-nn---
`
`
`
`------ --
`------
`-------
`
`--
`--
`--
`m-
`--
`m-
`m-
`--
`
`--
`
`As both FIG. 2 and Table 4 indicate, there are three files
`(File 6, File 7 and File 11) not within the Patent Law Library
`that are referenced by files within Patent Law Library.
`Therefore, the Patent Law Library’s ancillary file is built as
`shown in Table 5. Whenever the Patent Law Library is
`installed, the files listed in the ancillary file are advanta-
`geously also installed as nominal files.
`
`TABLE 5
`
`Ancillar File assogiated with the Patent Law Libryr
`
`Ancillary File
`
`\directory2\file6.htm
`\directory2\file7.htm
`\directory3\file11.htm
`
`As both FIG. 2 and Table 4 indicate, there are four files
`(File 3, File 5, File 9 and File 10) not within the Trademark
`Law Library that are referenced by files within Trademark
`Law Library. Therefore, the Trademark Law Library’s ancil-
`lary file is built as shown in Table 6. Whenever the Trade-
`mark Law Library is installed, the files listed in the ancillary
`file are advantageously also installed as nominal files.
`
`TABLE 6
`
`Ancillary File associated with the Trademark Law Library
`
`Ancillary File
`
`\directory1\file3.htm
`\directory1\file5 .htm
`\directory3\file9.htm
`\directory3\file10.htm
`
`As both FIG. 2 and Table 4 indicate, there are four files
`(File 1, File 5, File 7 and File 8) not within the Copyright
`Law Library that are referenced by files within Copyright
`Law Library. Therefore, the Copyright Law Library’s ancil-
`lary file is built as shown in Table 7. Whenever the Copy-
`right Law Library is installed, the files listed in the ancillary
`file are advantageously also installed as nominal files.
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`TABLE 7
`
`Ancillary File associated with the Copyright Law Library
`
`Ancillary File
`
`\directory1\file1.htm
`\directory1\file5.htm
`\directory2\file7.htm
`\directory2\file8.htm
`
`III. Prepare For Distribution
`Referring again to step 103 in FIG. 1, when each infor-
`mation product and its associated ancillary file are built, the
`files are advantageously prepared for distribution. Because
`all of the information products are advantageously distrib-
`uted on the same medium (e.g., CD-ROM, DVD, diskette)
`or distributed electronically over a wide-area-network (e.g.,
`the Internet), each information product is advantageously
`compressed with a lossless compression technique and
`encrypted, in well-known fashion, with the string, S, as the
`key.
`The purpose of the compression is to reduce the amount
`of bandwidth each information product consumes during
`distribution and to reduce the entropy of the information
`products before encryption. The purpose of encryption is to
`enable the distribution of the information products without
`allowing unauthorized access to the information products
`after the information products have left
`the publisher’s
`possession. In other words, the encryption allows the pub-
`lisher to give a potential end-user a CD-ROM that contains
`all of information products but
`to retain control of the
`end-user’s access to the information products. The installer
`is advantageously knows the cryptosystem and key for
`decrypting each of the information products. How the pub-
`lisher grants access to the information products after they
`have left his or her control will be described in detail below.
`
`It will be clear to those skilled in the art how to prepare
`the information products and ancillary files for distribution.
`IV. Distribute the Information Products
`
`At step 104, the information products and ancillary files
`and the accompanying installer and its associated files are
`distributed on a single medium (e.g., a CD-ROM, DVD), on
`
`Petitioner Apple - EX. 1001
`
`Petitioner Apple - Ex. 1001
`
`

`

`9
`
`multiple media (e.g., diskettes) and/or electronically over a
`network (e.g., the Internet). It will be clear to those skilled
`in the art how to distribute the information products.
`V. Receive the Information Products
`
`At step 105, the information products and ancillary files
`and the accompanying installer and its associated files are
`received by the end-user.
`VI. Run the Installer
`
`At step 106, the end-user initiates the installation process.
`When the information products are distributed on one or
`more media, the end-user inserts the media into his or her
`computer and runs the installer in well-known fashion.
`When the information products are distributed electronically
`over a network, the end-user collects the files on his or her
`computer and then runs the installer in well-known fashion.
`VI. Locate and Cleanse the Token
`
`At step 107, the installer advantageously checks to deter-
`mine if the publisher has previously granted authorization to
`install one or more of the information products on the
`end-user’s computer. The installer determines if the pub-
`lisher has previously granted authorization by searching for
`a token on the end-user’s computer, which token would have
`been placed there by an earlier edition of the installer from
`the publisher.
`When an end-user obtains a subscription to one or more
`of the information products, the installer memorializes the
`authorization during the length of the subscription. This is
`advantageous because it relieves the publisher and the
`end-user from having to obtain explicit authorization for
`each issue during the length of the subscription.
`The token can be conceptualized as a secret, authenticated
`message from one installer to a subsequent installer that
`indicates to the subsequent
`installer that
`the end-user’s
`computer is granted access to certain of the information
`products for a given duration. How the token is created and
`placed on the end-user’s computer will be described in detail
`below.
`
`25
`
`30
`
`35
`
`the token is a file with a name and
`Advantageously,
`location that are known to the installer. The token advanta-
`
`40
`
`geously comprises a data structure comprising:
`(1) an authentication code;
`(2) an indication of the name of the end-user;
`(3) a list of the information products to which the end-user
`has been granted access; and
`(4) an indication of when the authorization for each
`information product expires.
`Furthermore, the token file is encrypted so as to impede an
`end-user from illicitly obtaining access to an information
`product by doctoring the token. The encryption is
`performed, in well-known fashion, and the installer advan-
`tageously knows the both the cryptosystem and the key, T,
`for decrypting the token. Table 8 depicts the contents of the
`illustrative token.
`
`TABLE 8
`
`Contents of the Illustrative Token
`
`Authentication code
`Indication of End-User’s Identity
`Information Product No. 1; Expiration Date
`Information Product No. 2; Expiration Date
`
`The authentication code is advantageously a 32-bit or
`longer string that is known to the installer and publisher and
`is not generally known to the public.
`
`45
`
`50
`
`55
`
`60
`
`65
`
`5,982,889
`
`10
`The indication of the name of the user can either be the
`
`actual name of the end-user or a code that represents the
`name of the end-user. When a user illicitly attempts to share
`the token with others or to post it on a bulletin board or the
`Internet, it indelibly bears an indicium of the name of the
`person to whom it was originally given. If the publisher sees
`the token posted publicly,
`the publisher can decrypt the
`token, learn the identity of the user to whom the token was
`given and then investigate whether that users is inducing
`copyright infringement of the publisher’s information prod-
`ucts.
`
`The list of information products to which the end-user has
`been authorized access can either list the products to which
`access has been authorized, or, alternatively, can list of all of
`the information products published and an indication of
`whether access has been authorized or not for each product.
`The indication of when the access for each information
`
`5
`
`10
`
`15
`
`product expires is advantageously based on the information
`products’ version numbers rather than on calendar dates.
`Each edition of the installer is told what is the version
`
`20
`
`number of the information products that accompany it.
`FIG. 3 depicts a flowchart of the illustrative steps con-
`ducted by the installer in locating and cleansing the token,
`which is step 107 in FIG. 1. At step 301,
`the installer
`searches the end-user’s computer for a file with the same
`name as the token and in the same location as expected. At
`step 303, if the installer locates a file with the same name as
`the token and in the same location as expected, then control
`passes to step 305, else the installer infers that authorization
`was not previously given. At step 305, the installer decrypts
`the found file,
`in well-known fashion, according to the
`cryptosystem and the key it knows. At step 307, the installer
`attempts to locate the candidate authentication code in the
`decrypted file and compares the candidate authentication
`code with the known authentication code, which the installer
`knows. If the installer determines that the candidate authen-
`tication code matches the known authentication code, the
`installer infers that the token is genuine and has not been
`