throbber
Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 1 of 11
`
`
`
`
`
`
`
`
`
`Exhibit 3
`
`
`
`
`
`
`
`
`
`
`

`

`16 , 36 ~~ 20f2 ~ ·; VENABLE
`
`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 2 of 11
`'
`•
`
`~\_E,0
`
`.. -
`
`02/06/0,2
`~ ,'
`
`•
`
`·~ 1~
`.,-~
`tto '-'
`~ i ,
`TIIE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`iet~{\(i\O'Q'§
`
`Inre PATENT APPLICATION of
`
`Applicants
`
`Appln.No.
`
`Filed
`
`For
`
`Miki MULLOR et al.
`
`09/164,777
`
`October 1, 1998
`
`METHOD OF RESTRICTING
`S0F1W ARE OPERATION WTIHIN
`A LICENSED LIMITATION
`
`) Customer No.
`•26694*
`)
`26694
`)
`) PATENT TRADEMARK
`OFFICE
`)
`)
`)
`)
`)
`)
`
`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 CLAIMSY
`
`Please cancel claims 11, 12, 14 and 15 without prejudice to their re-entry at a later date.
`
`Please amended the claims as follows:
`
`(Amended)
`
`The method of Claim 1, wherein a pseudo-unique key is stored in
`
`the non-volatile memory of the BIOS .
`l~
`4o. (Amended)
`Received from < 202 962 8300 > at 215102 3:38:28 PM ~astern Standard Time]
`
`A method for accessing nn application software program using a
`
`!"
`
`., i
`
`ANCORA_00000433
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 3 of 11
`
`02/05/02 16:36 F~ 2 ~ ' VENABLE
`
`Amendment
`U.S. Application No.: 09/164,777
`
`•••
`
`~003
`
`pseudo-unique key stored in a first non-erasable non-volatile memory area of a coJDputer, the
`
`first non-volatile me1I1ory area being · unable to be programmntically changed, the method,
`
`comprising:
`
`loading the application software program residing in a non-volatile memory area of the
`
`co_,~ter; ~ - ·-. L: "' , \. 1 •. •• • '.~.
`• . • , 1 '- • 1 • •
`.._
`( ) • p ·· ~~ -· ; ~c~ lic~se information fro~ the so~ pro~~(- · ·
`
`. •• ·• •
`
`(_
`
`.. ' I I
`
`' ,
`
`encrypting license iDformation using the pseuderunique key stored in the first non(cid:173)
`
`volatile memory area;
`
`storing the encrypting license infonnation 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
`
`infonnation ~tored 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 1;1ow 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 Ex.amio.er.
`
`Claims 11, 12, 14 and 15 have been canceJecL 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 thjs rejection is respectfully requested.
`
`Recelild Croll< 2Gl !62 l300 > at 2lll12 3:38:28 PM tEast!m Standard TimeJ8-4
`
`2
`
`C
`
`ANCORA_00000434
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 4 of 11
`VENABLE
`
`@004
`
`••
`
`.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 al. 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 ~ 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. Toe client system ID 142 is a unique
`
`_identifier for the client computer, col 12, lines 50-51. TI1e client system IDs can be based on
`
`information collected from a computer's hardware a:od installed softwilre. 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 wrique 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,
`
`Jines 60-67. The license ID of Misra is similar to the verification structure end license
`
`information recited in claims I 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 bas a diffetent meaning and a
`
`different function :from the license information· described in Misra. Therefore, a coinbination of
`
`these references would not result in the claimed invention, as is discussed in detail below.
`3
`
`., ..
`'
`
`._I
`·'·
`
`Received from< 202 962 8300 > at 215f02 3:38:28 PM ~astern Standard Time)
`
`C
`
`ANCORA_00000435
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 5 of 11
`VENABLE
`--~2/05/0_!_ 16: 37 FAX 2~
`
`lg] 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 in.elude 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 th.e BIOS during manufacture.
`
`The identification information uniquely identifies a particular c.omputer. Therefore, according to
`
`Ewertz a "software license number" is one of a type of static data structures identifying a specific
`
`computer emd 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 ofEwertz 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 unjque 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 ~udo-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 ofEwertz is a static data structure, like the system ID of
`4
`
`Received kom < 202 962 8300 > at 215f02 3:38:28 PM ~astern Standard Time)
`
`C
`
`ANCORA_00000436
`
`

`

`___ o_21os102
`
`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 6 of 11
`.J.6_:_n_Ell.._~2 -
`VENABLE
`
`~006
`
`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 fimction to Misra's system ID. Therefore, eveii if Misra is
`
`combined with Ewertz, this combination does not result in the present invention. The proposed
`
`combination results in the system JD of Misra being stored in the BIOS, not the verification
`
`structure or license infonnation 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 nonnally
`
`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
`infonnation,
`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:
`
`"Toe 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 nm at the same time. Therefore, there is no teaching or
`
`suggestion to combine these programs. In fact such a combination would change the operation
`
`;. i;
`
`Received from< 202 962 8300 > at 215/02 3:38:28 PM ~astern Standard Time I
`
`5
`
`C
`
`ANCORA_00000437
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 7 of 11
`_ __ O_Z/_0_5102 16: 38 FAX 20•~ .___.
`VENABLE
`
`@007
`
`·-·
`
`Amendment
`U.S. Application No.: 09/164,777
`
`,.
`'
`
`of the programs, which is an indicia of non-obviousness. see MPEP Sec. 2 J 41.03 and re1ated
`
`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 presenre application data for
`
`at least two reasons.
`
`First, OS does not support this timctionality and is not recognized as a bard.ware 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 mediwn. Furthei:more. it is common
`
`that all peripheral devices in the PC are listed aud 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 sldlled in the art would not consider the BlOS for any operation, including
`
`writing to the BIOS.
`
`Second, no file system is associated with the B10S. Every writable device connected to
`
`the PC is associated with an OS file system to arrange and manage data structures. An example
`
`for ~ch a file system would be FAT, FAT32, NIFS, 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 215/02 3:38:28 PM !Eastern Standard Time!
`
`6
`
`C
`
`ANCORA_00000438
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 8 of 11
`VENABLE
`__ _ 02105/02 16:~8 PAX 2 ·L - - -
`
`f4J 008
`
`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 protocoP' (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
`
`~ any combination, do not fairly teach or suggest the present invention. Therefore the
`
`withdrawal ofthis 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 VeT$iOn 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 arc believed in
`
`order, and such action is earnestly solicited.
`
`Received from < 202 962 8300 > at 2/5/02 3:38:28 PM ~astern Standard TimeJ
`
`7
`
`ANCORA_00000439
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 9 of 11
`02/0S/Q2 16:38 FAX 20~2 ~ VENABLE
`
`@009
`
`· ·-
`
`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,
`
`Registration No. 26,924
`Jeffri A. Kaminski
`Registration No. 42, 709
`P.O. Box 34385
`\Vashington,D.C. 20043-9998
`Telephone 202-962-4800
`Telefax 202-962-8300
`
`RK/JAK/lrh
`#347353
`
`Received fiom < 202 962 8300 > at 215102 3:38:28 PM ~astern Standard Time)
`
`8
`
`C
`
`ANCORA_00000440
`
`

`

`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 10 of 11
`_ _ _ 0_21_05/02 16: ~8 FAX 20 . . VEr-!'.ABLE
`
`~010
`
`••
`
`Amendment
`U.S. Appln. 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.
`
`(A.mended)
`
`The method of Claim ~L wherein the--a pseudo-unique key
`
`~kules a ~seaaa l:leiE11:1e k:ey js stored in qe 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 thea application software program residing in a non-volatile memory area of the
`
`computer;
`
`extracting license information from the software program.;
`
`encrypting Jicense information using the pseudo-unique key stored in the first non(cid:173)
`
`volatile memory area;
`
`storing the encrypting - license information in a second erasable, writable, . B8ft
`
`volatilenon-yolatile memory area of the BIOS of the computer;
`
`subsequently verifying the application software program based on the encrypted license
`
`imonnati.on 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 ~astern Standard Time)
`
`I
`
`ANCORA_00000441
`
`

`

`.
`02/05/02
`---- - -·
`
`..
`Case 1:20-cv-00034-ADA Document 44-4 Filed 03/20/20 Page 11 of 11
`VENA~J,.E~---
`
`la) 001
`
`Und.crtt,., P, NIOl1t Rodualon Act of 1905. no
`
`~$C<I FTOJ$Ml1 (D!l-00)
`Amltref Docl<ct NO. ~
`Appnwe4 far U!I<! through 10,131/200Z, OMS D651-0031 "
`U.S. PSl8nt and T~demall< ome&: U.S. DEPARTMl!NT 01" J;.91',lMlii:tc'E\'
`" "ei>11e"111111 of infomi.ttil>o\ un1aa1 It contain& a v.il~
`Bttormo/;'nuriti,'ir.i\;
`
`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.
`
`7.//.'6/~· ~ 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 submitted paper.
`
`Burd&n Hour Statamont TIiis form Is esdmllled to tskl> 0.03 hout11 to complete. T,me will vary depending upon Ula needs or u,e indMdual ease. Any
`comments on Ille amoum ot Orne requirud ta complete this form &houtd be sent ID the ChiGf tn!ormation Oll1cer, U.S. Patefll and T111i:lem1111c Olftce,
`WasllinglOll, CIC 20231. 00 NOT SEND FEES OR COMPLETED FORMS TO TltlS ADDRl;SS. SEND TO: Asailllant Cammiaaioner fer Patenta,
`~ington. OC 20231.
`
`PCIOOCS:v349BSB
`
`l l t •
`
`' '
`
`I
`
`;· . .....
`. ~ ·jiJ;rl". ...... ,; ~.,.
`Received from < 202 962 8300 > at 215102 3:38:28 PM ~astern Standard Time)
`
`C
`
`ANCORA_00000442
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket