`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 1 of 11
`
`EXHIBIT 8
`EXHIBIT 8
`
`
`
`
`
`
`02/06/0
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 2 of 11
`-,
`.2
`16:36 FAiii 20
`..
`VENABLE
`
`1/0
`
`lw
`
`r, v,
`
`cd CiactO it 63
`7-
`iedooko
`THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`In re PATENT APPLICATION of
`
`Applicants
`
`Appin. No.
`
`Flied
`
`For
`
`I"
`
`Miki M1JLLOR et al.
`
`: 09/164,777
`
`October 1, 1998
`
`Customer No.
`*26694*
`26694
`PATENT TRADEMARK
`OFFICE
`
`METHOD OF RESTRICTING
`SOFTWARE OPERATION WITHIN
`A LICENSED LIMITATION
`
`Group Art Unit
`Examiner
`
`2161
`C. Hewitt
`
`Atty. Dkt.
`
`39636-176166
`
`Assistant Commissioner for Patents
`Washington, D.C. 22031
`
`Sir:
`
`AMENDMENT
`
`Responsive to the Office Action dated January 15, 2002, please amend the application as
`
`follows:
`
`IN THE CLAIMS:
`
`Please cancel claims 11, 12, 14 and 15 without prejudice to their re-entry at a later date.
`
`Please arriended the claims as follows:
`
`Cf.\
`
`.
`
`(Amended) The method of Claim 1, wherein a pseudo-unique key is stored in
`
`the non-volatile memory of the BIOS.
`
`(Amended) A method for accessing an application software program using a
`
`Received from < 202 962 8300 > at V5102 3:38:28 PM [Eastern Standard Time]
`
`ANCORA_00000433
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 3 of 11
`02/05/02 16:36 VIA.
`VENABLE
`
`ta 003
`
`Amendment
`U.S. Application No.; 09/164,777
`
`C/ 3"
`VI p(
`
`(3 -
`ti
`
`pseudo-unique key stored in a first non-erasable non-volatile memory area of a computer, the
`
`first non-volatile memory area being unable to be programmatically changed, the method,
`
`comprising:
`
`loading the application software program residing in a non-volatile memory area of the
`
`comp4ter;
`1,0/acting license information from the software program;
`
`encrypting license information using the pseudo-unique key stored in the first non-
`
`volatile memory area;
`
`storing the encrypting license information in a second erasable, writable, non-volatile
`
`memory area of the BIOS of the computer;
`
`subsequently verifying the application software program based on the encrypted license
`
`information stored in the second erasable, writable, non-volatile memory area of the BIOS; and
`
`acting on the application software program based on the verification.
`
`REMARKS
`
`Claims 1-10, 13 and 16-23 are now pending • in this application. Each of the pending
`
`claims is believed to define an invention which is novel and unobvious over the cited references.
`
`Favorable reconsideration of this case is respectfully requested.
`
`Claims 16 and 20 have been amended to correct the informalities noted by the Examiner.
`
`Claims 11, 12, 14 and 15 have been canceled. In view of these amendments, it is respectfully
`
`submitted that all pending claims are now in all aspects in compliance with 35 U.S.C. 112,
`
`second paragraph. Therefore, the withdrawal of this rejection is respectfully requested.
`
`Received from < 202 962 8300 > at 2/5102 138:28 PM [Eastern Standard Time'
`
`9-
`
`2 4
`
`ANCORA_00000434
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 4 of 11
`02/05/Q2 16:37 FAI 20
`• VENABLE
`2 "
`1111
` --1
`
`
`11)
`
`•
`
`0004
`
`Amendment
`U.S. Application No.: 09/164,777
`
`Claims 1-23 have been rejected under 35 U.S.C. 103(a) as being unpatentable over Misra
`
`et al. in view of U.S. Patent No. 5,684,951 to Goldman et at and U.S. Patent No. 5,479,639
`
`Ewertz et al.
`
`The cited references do not render the present invention obvious as they do not teach or
`
`suggest, among other things, storing a verification structure, such as a software license
`
`information, in the BIOS of a computer as is recited in the present claims.
`
`Misra et al. is cited as the primary reference against the present claims. Misra relates to a
`
`system and method for enforcing software licenses. The system of Misra generates unique
`
`identifiers for servers and clients, col 12, lines 41-42. The client system ID 142 is a unique
`
`identifier for the client computer, col 12, lines 50-51. The client system IDs can be based on
`
`information collected fives, a computer's hardware and installed software. For example, hard disk
`
`volume numbers, registered software, video cards, and some microprocessors contain unique
`
`identifiers. This information can be combined to uniquely identify a particular PC. Thus, the
`
`client system ID of Misra, is similar to the pseudo-unique key recited in claims 1 and 20.
`
`Misra also describes a license ID, which is a unique identifier assigned to a software
`
`license when the software license is issued to a client device, col. 11, lines 9-12. The license ID
`
`may be a digital certificate indicating the right to use the particular software at issue, col. 10,
`
`lines 60-67. The license ID of Misra is similar to the verification structure and license
`
`information recited in claims 1 and 20, respectively.
`
`Misra fails to teach using the BIOS of a computer to store the license ID, as noted in
`
`Section 7, Page 6 of the Office Action. Ewertz is cited as supplementing Misra to teach this
`
`feature. However, the license information described in Ewertz has a different meaning and a
`
`different function from the license information described in Misra. Therefore, a combination of
`
`these references would not result in the claimed invention, as is discussed in detail below.
`3
`•
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Time'
`
`ANCORA_00000435
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 5 of 11
`•
` 02/05/02 16:37 FAX 204,11110
`VERABLE
`
`• 411
`
`005
`
`Amendment
`U.S. Application No.: 09/164,777
`
`In Ewertz, a "software license number" is described as one type of identification
`
`information, col. 3, lines 20-22. This identification information may also include an Ethernet
`
`address or system serial numbers, col 3, lines 20-22. The identification information is a unique
`
`identification value stored in a non-writable, non-erasable area of the BIOS during manufacture.
`
`The identification information uniquely identifies a particular computer. Therefore, according to
`
`Ewertz a "software license number" is one of a type of static data structures identifying a specific
`
`computer and the static data structure is stored such that it cannot be modified. Accordingly, the
`
`software license number of Ewertz is simply identification for the operating system of a
`
`particular computer.
`
`For example, col. 2, lines 47-49 of Ewertz disclose that the memory storing the
`
`identification information may be electronically locked to prevent erasure or modification of its
`
`contents once installed. Moreover, in teaching a preferred embodiment, col. 11, line 23 - col. 12,
`
`line 14 of Ewertz describe that several types of identification information must be retained for
`
`individual computer systems. One type of identification number, as mentioned above, is an
`
`Ethernet address. The Ethernet address is stored in a protected area 306 in static page 2 of the
`
`flash memory of Ewertz and cannot be erased or altered once the device is installed. Thus the
`
`identification number cannot be destroyed. Ewertz also teaches other computer system
`
`identification numbers, such as unique serial number, printed board assembly (PBA) numbers or
`
`operating system license numbers may be stored in the locked memory.
`
`Consequently, Ewertz teaches storing identification information for the computer in a
`
`non-writable, non-erasable non-volatile memory. This identification information of Ewertz
`
`corresponds to the pseudo-unique key stored in the first non-erasable, non-volatile memory as
`
`recited in claims 1 and 20 and does not correspond to the license information recited in these
`
`claims. The identification information of Ewertz is a static data structure, like the system ID of
`4
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Time'
`
`ANCORA_00000436
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 6 of 11
`02/05/02 16:37 FAX 204102 4111, . VENABLE
`
`• 1)
`
`Amendment
`U.S. Application No.: 09/164,777
`
`Misra, that uniquely identifies a computer and simply does not correspond the license ID of
`
`Misra or the license information of the present invention as defined by claims 1 and 20.
`
`From the above discussion, it is clear that the "software license number" according to
`
`Ewertz is equivalent in definition and function to Misra's system ID. Therefore, everi if Misra is
`
`combined with Ewertz, this combination does not result in the present invention. The proposed
`
`combination results in the system ID of Misra being stored in the BIOS, not the verification
`
`structure or license information being stored in the BIOS as is required by the present claims.
`
`Furthermore, there is no suggestion or motivation to combine Misra and Ewertz in the
`
`manner suggested in the Office Action. .BIOS is a configuration utility. Software license
`
`management applications, such as the one of the present invention, are operating system (OS)
`
`level programs. Therefore, BIOS programs and software licensing management applications do
`
`not ordinarily interact or communicate because when BIOS is running, the computer is in a
`
`configuration mode, hence OS is not running Thus, BIOS and. OS level programs are normally
`
`mutually exclusive.
`
`Ewertz teaches that writing to the BIOS area is performed by the BIOS routines:
`
`"Referring to Fig. 8, processing logic for updating the flash memory
`device with configuration data, such as EISA information, is
`illustrated... The processing logic shown in Fig. 8 resides in the system
`BIOS of the preferred embodiment" Col 10, lines 20-28
`Misra teaches a licensing system that is OS level based:
`
`"The license generator 26, license server 28 and intermediate server 32
`are preferably implemented as computer servers, such as Windows NT
`servers that run Windows NT server operating systems from Microsoft
`corporation or UNIX-based servers" Col 5, lines 3-7
`Thus, the systems described in Misra and Ewertz are an OS program and a BIOS
`
`program, respectively, that cannot run at the same time. Therefore, there is no teaching or
`
`suggestion to combine these programs. In fact such a combination would change the operation
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Time'
`
`5
`
`ANCORA_00000437
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 7 of 11
`02/05/02 16:38 FAX 2041102
`... VENABLE
`0
`
`lb*
`
`a007
`
`Amendment
`U.S. Application No.: 09/164,777
`
`of the programs, which is an indicia of non-obviousness, see MPEP Sec. 2141_03 and related
`
`case law.
`
`Moreover, the present invention proceeds against conventional wisdom in the art. Using
`
`BIOS to store application data such as that stored in Misra's local cache for licenses is not
`
`obvious. The BIOS area is not considered a storage area for computer applications. An ordinary
`
`skilled artisan would not consider the BIOS as a storage medium to preserve application data for
`
`at least two reasons.
`
`First, OS does not support this functionality and is not recognized as a hardware device
`
`like other peripherals. Every OS provides a set of application program interfaces (APIs) for
`
`applications to access storage devices such as hard drives, removable devices, etc. An ordinary
`
`person skilled in the art makes use of OS features to write date to storage mediums. There is no
`
`OS support whatsoever to write data to the system BIOS. Therefore, an ordinary person skilled
`
`in the art would not consider the BIOS as a possible storage medium. Furthermore, it is common
`
`that all peripheral devices in the PC are listed and recognized by the OS except for the BIOS.
`
`This supports the fact that the BIOS is not considered a peripheral device. Accordingly, an
`
`ordinary person skilled in the art would not consider the BIOS for any operation, including
`
`writing to the BIOS.
`
`Second, no file system is associated with the BIOS. Every writable device connected to
`
`the PC is associated with an OS file system to arrange and manage data structures. An example
`
`for such a file system would be FAT, FAT32, NTFS, HPFS, etc. that suggests writing data to the
`
`writable device. No such file system is associated with the BIOS. This is further evidence that
`
`OS level application programmers would not consider the BIOS as a storage medium for license
`
`data.
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Timel
`
`6
`
`ANCORA_00000438
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 8 of 11
`411___
`02/05/02 16:38 FAX
`VENABLE
`
`Amendment
`U.S. Application No.: 09/164,777
`
`Additionally, Misra teaches away from using the BIOS as a storage area by making a
`
`statement about client computers that do not have a persistent non-volatile area
`
`"The license cache 136 is kept in persisted (non-volatile) storage. Clients
`that do not have persistent storage can be issued licenses as long as they
`can generate a unique client ID and can respond to the client platform
`challenge protocol" (Misra, Col. 12, lines 15-18)
`
`Since all computers must have a BIOS, it is clear Misra teaches away from using the
`
`BIOS as a local storage area for licenses.
`
`Goldman et al. do not supplement Misra and Ewertz to teach or suggest the present
`
`invention_
`
`Thus, in view of the above discussion, it is clear that the cited references, taken alone or
`
`in any combination, do not fairly teach or suggest the present invention. Therefore the
`
`withdrawal of this rejection is respectfully requested. Favorable reconsideration of this case and
`
`early issuance of a Notice of Allowance is respectfully requested
`
`Attached hereto is a marked-up version of the changes made to the specification and
`
`claims by the current amendment. The attached page is captioned "Version with markings to
`
`show changes made."
`
`In view of the foregoing, reconsideration and allowance of this application are believed in
`
`order, and such action is earnestly solicited.
`
`.4
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Time'
`
`7
`
`ANCORA_00000439
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 9 of 11
`02/05/02 16:38 FAX 20
`i 411
`' VENABLE
`
`0009
`
`Amendment
`U.S. Application No.: 09/164,777
`
`The Commissioner is authorized to charge any fee necessitated by this Amendment to our
`
`Deposit Account No. 22-0261.
`
`Respectfully submitted,
`
`berg
`Registration No. 26,924
`Jeffri A. Kaminski
`Registration No. 42, 709
`P.O. Box 34385
`Washington, D.C_ 20043-9998
`Telephone 202-962-4800
`Telefax 202-962-8300
`
`RK/JAK/lrh
`0347353
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Time)
`
`8
`
`ANCORA_00000440
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 10 of 11
`02/05/02 16:38 FAX 20
`2 4116
`' VENABLE
`
`0 •
`
`la 010
`
`Amendment
`U.S. Appin. No.: 09/164,777
`
`VERSION WITH MARKINGS TO SHOW CHANGES MADE
`
`IN THE CLAIMS:
`
`Please cancel claims 11, 12, 14 and 15 without prejudice to their re-entry at a later date.
`
`Please amended the claims as follows:
`
`16.
`
`(Amended) The method of Claim 2-a, wherein the—a pseudo-unique key
`
`inGloEles-a-pseaele-unkfae-key is stored in the non-volatile memory of the BIOS.
`
`20.
`
`(Amended)
`
`A method for accessing an application software program using a
`
`pseudo-unique key stored in a first non-erasable non-volatile memory area of a computer, the
`
`first non-volatile memory area being unable to be programmatically changed, the method,
`
`comprising:
`
`loading they application software program residing in a non-volatile memory area of the
`
`computer,
`
`extracting license information from the software program;
`
`encrypting license information using the pseudo-unique key stored in the first non-
`
`volatile memory area;
`
`storing the encrypting —license information in a second erasable, writable, nen
`
`velatilenon-volatile memory area of the BIOS of the computer;
`
`subsequently verifying the application software program based on the encrypted license
`
`information stored in the second erasable, writable, non-volatile memory area of the BIOS; and
`
`acting on the application software program based on the verification.
`
`Received from < 202 962 8300 > at 215102 3:38:28 PM [Eastern Standard Time'
`
`ANCORA_00000441
`
`
`
`Case 1:20-cv-00034-ADA Document 45-10 Filed 03/20/20 Page 11 of 11
`
` •
`02/05/02 16:36 FAX 20
`
`VENABLE • •
`
`a 001
`
`Revised PTOISSNI7 (la-00)
`Attorney Docket NO.
`Approved Tor use through 10/31/2002. mai oEsi-0031
`U.S. Patent and Trademark 0Mca; U.S. DEPARTMENT OPSOM2IFF.teE\
`Undcr tho Paperwork Reduction Art art 005. no persons are required to respond tea easection of infamotion unieas It contains a valid 0 1506treimurnbir.L
`
`Certificate of Transmission under 37 CFR 1.8
`
`The undersigned certifies that the attached Amendment is being
`facsimile filed to the Examiner C. Hewitt (703) 746-7239) on
`February 5, 2002.
`
`Signature
`
`Typed or printed name of person signing Certificate
`
`Note: Each paper must have its own certificate of transmission, or this
`certificate must identify each submifted paper.
`
`Burden Hour Statement: This form Is estimated to take 0.03 hours to complete. Time will vary depending upon the needs of the individual case. Any
`Comments on the amount of time required to complete this form should be sent to the Chief information 01TICer. U.S. Patent and Trademark Office,
`Washington, DC 20231. DO NOT SEND FEES OR COMPLETED FORMS TO 11113 ADDRESS. SEND TO: Assistant Commissioner for Patents,
`Washington, DC 20231.
`
`PCJDOCS21349asa
`
`Received from < 202 962 8300 > at 215102 1308 PM [Eastern Standard Time]
`
`ANCORA_00000442
`
`