UNITED STATES PATENT AND TRADEMARK OFFICE
`
`__________________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`__________________________
`
`GOOGLE LLC, MICROSOFT CORPORATION
`Petitioners
`v.
`CAROLYN W. HAFEMAN
`Patent Owner.
`__________________________
`
`IPR 2022-01190
`IPR 2022-01191
`
`U.S. Patent No. 10,789,393
`__________________________
`
`DECLARATION OF EREZ ZADOK IN SUPPORT OF PETITION FOR
`INTER PARTES REVIEW OF
`U.S. PATENT NO. 10,789,393
`
`Mail Stop PATENT BOARD
`Patent Trial and Appeal Board
`U.S. Patent & Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313–1450
`
`EX-1003
`US Patent 10,789,393
`
`

`

`TABLE OF CONTENTS
`
`Page
`
`IV.
`
`V.
`
`QUALIFICATIONS ...................................................................................... 10
`I.
`II. UNDERSTANDING OF RELEVANT LEGAL PRINCIPLES ................... 21
`III. TECHNICAL BACKGROUND ................................................................... 24
`A. General Computer Operations ............................................................. 24
`B. Authorized Remote Device Access ..................................................... 25
`THE ’393 PATENT ....................................................................................... 30
`A.
`Summary of the ’393 Patent ................................................................ 30
`B.
`Priority Date for the Challenged Claims in the ’393 Patent ............... 38
`1.
`The ’827 Application Lacks Written Description Support for
`Claims 1-7 of the ’393 patent ................................................... 42
`The ’606 Patent Lacks Written Description Support for
`Claims 1-7 of the ’393 patent ................................................... 46
`Claim Construction ............................................................................. 53
`C.
`Level of Ordinary Skill in the Art ....................................................... 57
`D.
`GROUNDS BASED ON NOVEMBER 22, 2013 PRIORITY DATE ......... 58
`A.
`INTRODUCTION ............................................................................... 58
`HAFEMAN 298/CHIU GROUND: Claims 1-7 Would Have Been
`B.
`Obvious Over the Combination of Hafeman 298 and Chiu. ............... 61
`1.
`Overview of the Combination .................................................. 61
`a.
`Hafeman 298 .................................................................. 61
`b.
`Chiu ................................................................................ 64
`c.
`Motivation to Combine Hafeman 298 and Chiu ........... 66
`Independent Claims ................................................................. 78
`a.
`Independent Claim 1 ...................................................... 78
`(i)
`Preamble [1P] ...................................................... 79
`(ii)
`“Activating” Limitation. ...................................... 80
`(a)
`Structural Limitations of Claim 1. ............. 80
`(b)
`Return/Recovery Information Display
`Limitation. .................................................. 81
`(iii) Remotely Initiating or Changing Limitation ....... 84
`
`2.
`
`2.
`
`- i -
`
`

`

`TABLE OF CONTENTS
`(continued)
`
`b.
`
`Page
`Interactive Program Limitation ........................... 91
`(iv)
`Security Prompt Limitation ................................. 95
`(v)
`(vi) User Message ...................................................... 97
`Independent Claim 4 ...................................................... 97
`(i)
`Preamble .............................................................. 98
`(ii) Structural Limitations ........................................ 100
`(iii)
`“Processor … which displays” Limitation ........ 102
`(a)
`Return/Recovery Information Display
`Limitation .................................................103
`(b) Timing Limitation ....................................103
`(iv) Remotely Initiating or Changing Limitation ..... 104
`(v)
`Interactive Program Limitation ......................... 105
`Independent Claim 7 .................................................... 106
`(i)
`Preamble ............................................................ 106
`(ii)
`“Displaying” Limitation .................................... 107
`(iii) Structural Limitations of claim 7 ...................... 108
`(a)
`Return/Recovery Information Display
`Limitation .................................................108
`(b)
`Timing and Lock Screen Limitations ......109
`(iv) Remotely Initiating or Changing ....................... 112
`(v)
`Interactive Program Limitation ......................... 112
`Dependent Claims .................................................................. 113
`a.
`Claims 2 and 5 ............................................................. 113
`b.
`Claims 3 and 6 ............................................................. 120
`HAFEMAN 670 GROUND: Claims 1-7 are Anticipated By Hafeman
`670 .....................................................................................................121
`1.
`Overview of Hafeman 670 ..................................................... 121
`2.
`Independent Claims ............................................................... 123
`a.
`Independent Claim 1 .................................................... 123
`(i)
`Preamble [1P] .................................................... 124
`(ii)
`“Activating” Limitation. .................................... 124
`Structural Limitations of Claim 1. ...........124
`(a)
`
`3.
`
`C.
`
`c.
`
`- ii -
`
`

`

`TABLE OF CONTENTS
`(continued)
`
`Page
`
`b.
`
`c.
`
`(b) Return/Recovery Information Display
`Limitation. ................................................125
`(iii) Remotely Initiating or Changing Limitation ..... 125
`(iv)
`Interactive Program Limitation ......................... 128
`(v)
`Security Prompt Limitation ............................... 129
`(vi) User Message .................................................... 130
`Independent Claim 4 .................................................... 130
`(i)
`Preamble ............................................................ 131
`(ii) Structural Limitations ........................................ 131
`(a)
`“Processor … which displays” Limitation
` ..................................................................132
`(b) Return/Recovery Information Display
`Limitation .................................................133
`(c) Timing Limitation ....................................133
`(iii) Remotely Initiating or Changing Limitation ..... 133
`(iv)
`Interactive Program Limitation ......................... 134
`Independent Claim 7 .................................................... 135
`(i)
`Preamble ............................................................ 136
`(ii)
`“Displaying” Limitation .................................... 136
`(iii) Structural Limitations of claim 7 ...................... 137
`(a) Return/Recovery Information Display
`Limitation .................................................137
`(b) Timing Limitation ....................................138
`(c)
`“Lock Screen” Limitation ........................138
`(iv) Remotely Initiating or Changing ....................... 138
`(v)
`Interactive Program Limitation ......................... 139
`Dependent Claims .................................................................. 140
`a.
`Claims 2 and 5 ............................................................. 140
`b.
`Claims 3 and 6 ............................................................. 140
`VI. GROUNDS BASED ON NOVEMBER 25, 2002 PRIORITY DATE .......141
`A.
`JENNE/COHEN GROUND: Claims 1-7 Would Have Been Obvious
`Over the Combination of Jenne and Cohen ......................................141
`
`3.
`
`- iii -
`
`

`

`1.
`
`2.
`
`TABLE OF CONTENTS
`(continued)
`
`b.
`
`Page
`Overview of the Combination ................................................ 141
`a.
`Jenne ............................................................................ 141
`b.
`Cohen ........................................................................... 145
`c. Motivation to Combine Jenne and Cohen ................... 149
`Independent Claims ............................................................... 154
`a.
`Independent Claim 1 .................................................... 154
`(i)
`Preamble [1P] .................................................... 155
`(ii)
`“Activating” Limitation. .................................... 155
`(a)
`Structural Limitations of Claim 1. ...........156
`(b) Return/Recovery Information Display
`Limitation. ................................................157
`(iii) Remotely Initiating or Changing Limitation. .... 164
`(iv)
`Interactive Program Limitation. ........................ 167
`(v)
`Security Prompt Limitation ............................... 170
`(vi) User Message Limitation .................................. 175
`Independent Claim 4 .................................................... 177
`(i)
`Preamble ............................................................ 178
`(ii) Structural Limitations ........................................ 179
`(a)
`“Processor … which displays” Limitation
` ..................................................................181
`(b) Return/Recovery Information Display
`Limitation .................................................181
`(c) Timing Limitation ....................................182
`(iii) Remotely Initiating or Changing Limitation ..... 184
`(iv)
`Interactive Program Limitation ......................... 187
`Independent Claim 7 .................................................... 188
`(i)
`Preamble ............................................................ 189
`(ii)
`“Displaying” Limitation .................................... 190
`(iii) Structural Limitations of Claim 7 ..................... 191
`(a) Return/Recovery Information Display
`Limitation .................................................191
`“Lock Screen” Limitation ........................191
`(b)
`(c) Timing Limitation ....................................194
`
`c.
`
`- iv -
`
`

`

`TABLE OF CONTENTS
`(continued)
`
`3.
`
`2.
`
`Page
`(iv) Remotely Initiating or Changing Limitation ..... 195
`(v)
`Interactive Program Limitation ......................... 196
`Dependent Claims .................................................................. 197
`a.
`Claims 2 and 5 ............................................................. 197
`b.
`Claims 3 and 6 ............................................................. 199
`B. ANGELO/HELLE GROUND: Claims 1, 4, and 7 Would Have Been
`Obvious Over the Combination of Angelo and Helle .......................203
`1.
`Overview of the Combination ................................................ 203
`a.
`Angelo .......................................................................... 203
`b.
`Helle ............................................................................. 209
`c. Motivation to Combine Angelo and Helle .................. 217
`Independent Claims ............................................................... 232
`a.
`Independent Claim 1 .................................................... 232
`(i)
`Preamble [1P] .................................................... 233
`(ii)
`“Activating” Limitation ..................................... 234
`(a)
`Structural Limitations of Claim 1 ............235
`(b) Return/Recovery Information Display
`Limitation .................................................236
`(iii) Remotely Initiating or Changing Limitation ..... 244
`(iv)
`Interactive Program Limitation ......................... 250
`(v)
`Security Prompt Limitation ............................... 254
`(vi) User Message .................................................... 257
`Independent Claim 4 .................................................... 259
`(i)
`Preamble ............................................................ 260
`(ii) Structural Limitations ........................................ 261
`(a)
`“Processor … which displays” Limitation
` ..................................................................262
`(b) Return/Recovery Information Display
`Limitation .................................................263
`(c) Timing Limitation ....................................263
`(iii) Remotely Initiating or Changing Limitation ..... 264
`(iv)
`Interactive Program Limitation ......................... 265
`Independent Claim 7 .................................................... 266
`
`b.
`
`c.
`
`- v -
`
`

`

`TABLE OF CONTENTS
`(continued)
`
`Page
`Preamble ............................................................ 267
`(i)
`“Displaying” Limitation .................................... 268
`(ii)
`(iii) Structural Limitations of Claim 7 ..................... 269
`(a) Return/Recovery Information Display
`Limitation .................................................269
`(b) Timing and Lock Screen Limitations ......270
`(iv) Remotely Initiating or Changing ....................... 273
`(v)
`Interactive Program Limitation ......................... 274
`VII. CONCLUSION ............................................................................................276
`
`
`- vi -
`
`

`

`
`
`I, Erez Zadok, declare as follows:
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`1.
`
`I have been engaged by Perkins Coie LLP on behalf of Google LLC
`
`and by Faegre Drinker Biddle & Reath on behalf of Microsoft Corporation
`
`(collectively “Petitioners”) to provide this Declaration concerning technical subject
`
`matter relevant to the petition for Inter Partes Review (“Petition”) of U.S. Patent
`
`No. 10,789,393 to Carolyn W. Hafeman (“the ’393 patent”).
`
`2.
`
`I am over 18 years of age. I have personal knowledge of the facts stated
`
`in this Declaration and could testify competently to them if asked to do so.
`
`3.
`
`I have reviewed and am familiar with the specification and the claims
`
`of the ’393 patent. In general, I will cite to the specification of a United States patent
`
`using the following formats: (Patent No., Col:Line Number(s)) or (Patent No.,
`
`Paragraph Number(s)). For example, the citation (’393 patent, 1:1-10) points to
`
`the ’393 patent specification at column 1, lines 1-10. Also, for convenience, I use
`
`italics to denote limitations from the challenged claims.
`
`4.
`
`All of the opinions contained in this Declaration are based on the
`
`documents I reviewed and my knowledge and professional judgment. In forming
`
`the opinions expressed in this Declaration, I reviewed the following documents:
`
`• U.S. Patent 10,789,393 to Carolyn W. Hafeman (“the ’393 patent”; EX-
`1001)
`• File History of U.S. Patent 10,789,393 (“’393 FH”; EX-1002)
`
`
`
`- 7 -
`
`

`

`
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`• U.S. Patent Publication 2003/0122864 to Jenne, et al (“Jenne”; EX-1005)
`• European Patent Publication EP0687968A2 to Cohen (“Cohen”; EX-
`1006)
`• U.S. Patent Publication 2003/0065934 to Angelo, et al (“Angelo”; EX-
`1007)
`• U.S. Patent 6,662,023 to Helle (“Helle”; EX-1008)
`• U.S. Patent Publication 2004/0103298 to Hafeman (“Hafeman 298”; EX-
`1009)
`• U.S. Patent Publication 2003/0088633 to Chiu, et al (“Chiu”; EX-1010)
`• U.S. Patent Publication 2005/0071670 to Hafeman (“Hafeman 670”; EX-
`1011)
`• File Histories of the following applications and patents to Hafeman:
`• U.S. Patent No. 8,601,606 (“the ’606 FH”; EX-1012)
`• U.S. Patent No. 10,325,122 (“the ’122 FH”; EX-1013)
`• U.S. Patent No. 9,892,287 (“the ’287 FH”; EX-1014
`• EPO App. No. 05791717 (International Application No.
`PCT/US05/30171) (“the 717 EP FH”; EX-1017)
`• EPO App. No. 18188741 (International Application No.
`PCT/US05/30171) (a divisional of EPO App. No.
`05791717) (“the 741 EP FH”; EX-1026)
`
`I have also reviewed and am familiar with the other materials referred to in this
`
`Declaration.
`
`5.
`
`I have been asked to provide my technical opinions regarding how a
`
`person of ordinary skill in the art would have understood the claims of the ’393
`
`
`
`- 8 -
`
`

`

`
`patent at the time of the alleged invention. I understand that there is a dispute about
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`the priority date (i.e., the date of the alleged invention) for the ’393 patent: the
`
`Petitioners assert that the priority date is no earlier than November 22, 2013 as I
`
`discuss in § IV.B and the Patent Owner will (likely) assert that the priority date is at
`
`least as early as November 25, 2002 (the filing date for the first application in a chain
`
`of applications related to the ’393 patent). For purposes of whether the teachings of
`
`the prior art render the claims of the ’393 patent obvious, I have assumed the date of
`
`November 22, 2013 although my opinions regarding the combination of Jenne and
`
`Cohen (§ VI.A below) and the combination of Angelo and Helle (§VI.B below)
`
`would not change even if the November 25, 2002 date is assumed in this case. I note
`
`that the prior art relied on in § V, with the exception of Hafeman 298 and Hafeman
`
`670, predate the Patent Owner’s asserted priority date of November 25, 2002.
`
`6.
`
`I have also been asked to provide my technical opinions on how
`
`concepts in the ’393 patent specification relate to claim limitations of the ’393 patent.
`
`In reaching the opinions provided herein, I have considered the ’393 patent, its
`
`prosecution history, and the references cited above and have drawn as appropriate
`
`on my own education, training, research, knowledge, and personal and professional
`
`experience.
`
`
`
`
`
`- 9 -
`
`

`

`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`
`I. QUALIFICATIONS
`7.
`In formulating my opinions, I have relied on my knowledge, training,
`
`and experience in the relevant field, which I will summarize briefly. A more detailed
`
`summary of my background, education, experience, and publications is set forth in
`
`my curriculum vitae (CV), which is submitted as EX-1004.
`
`8.
`
`I have personal knowledge of the facts and opinions set forth in this
`
`declaration and believe them to be true. If called upon to do so, I would testify
`
`competently thereto. I have been warned that willful false statements and the like
`
`are punishable by fine or imprisonment, or both.
`
`9.
`
`My consulting company, Zadoks Consulting, LLC,
`
`is being
`
`compensated for my time at my current standard consulting rate. I am also being
`
`reimbursed for expenses that I may incur during the course of this work. My
`
`compensation is not contingent upon the results of my study and analysis, the
`
`substance of my opinions, or the outcome of any proceeding involving the
`
`Challenged Claims. I have no financial interest in the outcome of this matter or in
`
`any litigation involving the ’393 patent.
`
`10.
`
`I am a Professor in the Computer Science Department at Stony Brook
`
`University (part of the State University of New York (“SUNY”) system). I direct
`
`the File-systems and Storage Lab (FSL) at Stony Brook’s Computer Science
`
`
`
`- 10 -
`
`

`

`
`Department. My research interests include file systems and storage systems,
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`operating systems, information technology and system administration, security and
`
`information assurance, networking, energy efficiency, performance and
`
`benchmarking, virtualization, cloud systems, compilers, applied machine learning,
`
`and software engineering.
`
`11.
`
`I studied at a professional high school in Israel, focusing on electrical
`
`engineering (“EE”), and graduated in 1982. I spent one more year at the high
`
`school’s college division, receiving a special Certified Technician’s degree in EE. I
`
`then went on to serve in the Israeli Defense Forces for three years (1983-1986). I
`
`received my Bachelor of Science degree in computer science (“CS”) in 1991, my
`
`Master’s degree in CS in 1994, and my PhD in CS in 2001—all from Columbia
`
`University in New York.
`
`12. When I began my undergraduate studies at Columbia University, I also
`
`started working as a student assistant in the various campus-wide computer labs,
`
`eventually becoming an assistant to the head labs manager, who was managing all
`
`public computer labs on campus. During that time, I also became more involved
`
`with research within the CS Department at Columbia University, conducting
`
`research on operating systems, file and storage systems, distributed and networked
`
`systems, security, and other topics. I also assisted the CS department’s computer
`
`
`
`- 11 -
`
`

`

`
`administrators in managing the department’s computers, which included storage, IT,
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`networking, and cyber-security related duties.
`
`13.
`
`In 1991, I joined Columbia University’s CS department as a full-time
`
`systems administrator, studying towards my MS degree part-time. My MS thesis
`
`topic related to file system reliability, fault tolerance, replication, and failover in
`
`mobile networked storage systems using file virtualization. My main duties as a
`
`systems administrator involved installing, configuring, and managing many
`
`networked servers, proxies, and desktops running several operating systems, as well
`
`as network devices setup; this included many hardware upgrades, device upgrades,
`
`and BIOS firmware/chipset updates/upgrades. My duties also included ensuring
`
`reliable, secure, authenticated access to networked systems/storage and licensed
`
`software, as well as software updates, security and bug fixes. Examples of servers
`
`and their protocols included email (SMTP), file transfer (FTP), domain names
`
`(DNS), network file systems (NFS), network news systems (NNTP), and Web
`
`(HTTP).
`
`14.
`
`In 1994, I left my systems administrator position to pursue my doctoral
`
`studies at Columbia University. My PhD thesis topic was on versatile file system
`
`development using stackable (virtualized) file systems, with examples in the fields
`
`of security and encryption, efficiency, reliability, and failover. I continued to work
`
`
`
`- 12 -
`
`

`

`
`part-time as a systems administrator at the CS department, and eventually I was
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`asked to serve as manager to the entire information technology (“IT”) staff. From
`
`1991 to 2001, I was also a member of the faculty-level Facilities Committee that
`
`oversaw all IT operations at the CS department.
`
`15.
`
`As part of my PhD studies at Columbia, I collaborated on projects to
`
`develop advanced AI-like techniques to detect previously unknown viruses (a.k.a.
`
`“zero-day malware”), using data mining and rule-based detection. This work led to
`
`several highly cited papers (over 1,400 citations for one of the papers alone), and
`
`two patents. I also became a Teaching Assistant (TA) for a first-ever Computer
`
`Security course given at Columbia University’s CS department with Dr. Matt Blaze
`
`as instructor.
`
`16.
`
`From 1990 to 1998, I consulted for SOS Corporation and HydraWEB
`
`Technologies, as a systems administrator and programmer, managing data storage
`
`use and backup/restore duties, as well as information assurance and cyber-security
`
`(e.g., malware protection, software licensing). From 1994 to 2000, I led projects at
`
`HydraWEB Technologies, and then became the Director of Software Development-
`
`overseeing the development of several products and appliances such as stateful
`
`firewalls and HTTP load-balancers, utilizing network-virtualization and high-
`
`availability techniques. Since 2009, I have consulted for Packet General Networks,
`
`
`
`- 13 -
`
`

`

`
`a startup specializing in secure, virtualized, network storage and applications’ data
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`security in the cloud.
`
`17.
`
`In 2001, I joined the faculty of Stony Brook University, a position I
`
`have held since that time. In 2002, I joined the Operations Committee, which
`
`oversees the IT operations of the CS department at Stony Brook University. From
`
`2006 to 2010, I was the Director of IT Operations of the CS department; my day-to-
`
`day duties included setting policies regarding computing, hiring and training new
`
`staff, assisting any staff with topics of my specialty, defining requirements for new
`
`software/hardware, and purchasing. From 2010 to 2015, I have served as the Co-
`
`Chair to the Operations Committee. From 2016 to 2019, I oversaw the IT Operations
`
`as the Chair of the Operations Committee. A significant component of these duties
`
`included defining and helping implement policies for data management, so as to
`
`ensure the security of users and their data, and data reliability and availability, while
`
`minimizing the inconvenience and performance impact to users. I personally helped
`
`setup and maintain an initial virtual-host infrastructure in the department. Since late
`
`2019, I’ve been a member of the department’s Executive Committee that also
`
`oversees all IT operations.
`
`18.
`
`In 2017, I became the department’s Graduate Academic Adviser,
`
`advising all Master students (over 400 annually on average) and many other graduate
`
`
`
`- 14 -
`
`

`

`
`students on an assortment of academic matters.
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`19.
`
`Since 2001, I personally configured and managed my own research
`
`lab’s network. This includes setting up and configuring multiple storage systems
`
`(e.g., NFS, CIFS/SMB, NAS), virtual and physical environments, applications such
`
`as database and mail servers, user access control (e.g., NIS, LDAP), backups and
`
`restores, snapshot policies, and more. I’ve personally installed, configured, changed,
`
`replaced parts, and upgraded components in numerous devices including mobile
`
`devices, laptops, desktops, and servers, both physical and virtual.
`
`20.
`
`Since 1995, I have taught courses on operating systems, storage and file
`
`systems, advanced systems programming in Unix/C, systems administration, data
`
`structures, data/software security, and more. My courses often use storage, file
`
`systems, distributed systems, and system/network security as key teaching principles
`
`and practical examples for assignments and projects. I have taught these concepts
`
`and techniques to my students, both to my direct advisees as well as in my courses.
`
`For example, in my graduate Operating Systems course, I often cover Linux’s kernel
`
`mechanisms to protect users, applications, and data files, virtual file systems, as well
`
`as distributed storage systems (e.g., NFS). And in the System Administration
`
`undergraduate course, I covered many topics such as networking, storage, backups,
`
`and configuring complex applications such as mail, web, and database servers.
`
`
`
`- 15 -
`
`

`

`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`21. My research often investigates computer systems from many angles:
`
`
`
`security, efficiency, energy use, scalability, reliability, portability, survivability,
`
`usability, ease-of-use, versatility, flexibility, and more. My research gives special
`
`attention to balancing five often-conflicting aspects of computer systems:
`
`performance, reliability, energy use, security, and ease-of-use.
`
`22.
`
`Since joining Stony Brook University in 2001, my group in the File-
`
`systems and Storage Lab (FSL) has developed many file systems and operating
`
`system extensions; examples include a highly-secure cryptographic file system, a
`
`portable copy-on-write (COW) versioning file system, a tracing file system useful
`
`to detect intrusions, a replaying file system useful for forensics, a snapshotting and
`
`sandboxing file system, a namespace unification file system (that uses stackable,
`
`virtualized, file-based COW), an anti-virus file system, an integrity-checking file
`
`system, a load balancing and replication/mirroring file system, network file system
`
`extensions for security and performance, distributed secure cloud-based storage
`
`systems, transactional key-value stores and file systems, OS-level embedded
`
`databases, a compiler to convert user-level C code to in-kernel efficient yet safe
`
`code, GCC plugins, stackable file system templates, and a Web-based backup
`
`system. Many of these projects used one form of virtualization or another (storage,
`
`network, host, etc.). I continue to maintain and release newer versions of some of
`
`
`
`- 16 -
`
`

`

`
`these file systems and software.
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`23.
`
`I have published over 120 refereed publications (in ACM, IEEE,
`
`USENIX, and more). To date, my publications have been cited more than 8,900
`
`times (as per Google Scholar as of June 21, 2022). My papers cover a wide range
`
`of related technologies such as file systems, storage systems, transactional systems,
`
`security, clouds and virtualization, performance benchmarking and optimization,
`
`energy efficiency, system administration, and more. I also published a book titled
`
`“Linux NFS and Automounter Administration” (Sybex, 2001), covering systems
`
`administration topics related to network storage and data security.
`
`24.
`
`Some of my research has led to public software releases that have been
`
`used worldwide. I have publicly maintained the Amd Berkeley Automounter in a
`
`package called “am-utils” since 1992; this software helps administrators manage the
`
`multitude of file system mounts on dozens of different Unix systems, especially
`
`helping to automate access to multiple NFS/NAS storage volumes. Since 1997, I
`
`have maintained and released several stackable (virtualized) file system software
`
`projects for Linux, FreeBSD, and/or Solaris, in a package called FiST. One of my
`
`stackable file system encryption projects, called Cryptfs, became the basis for IBM’s
`
`public release of eCryptfs, now part of Linux. Packet General Networks, for whom
`
`I have provided consulting services since 2009, licensed another encryption file
`
`
`
`- 17 -
`
`

`

`
`system called Ncryptfs. Another popular file system released in 2003, called
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`Unionfs, offers virtual namespace unification, transparent shadow copying (a.k.a.
`
`copy-on-write or COW), file system snapshotting (e.g., useful for forensics and
`
`disaster recovery), and the ability to save disk space by sharing a read-only copy of
`
`data among several computers, among other features.
`
`25. My research and teaching make extensive use of data security features.
`
`For example, each time I taught the graduate operating system course, the first
`
`homework assignment includes the creation of a new system call that performs new
`
`or added functionality, often for encrypting a file or verifying its integrity; many of
`
`my other assignments cover topics of user/process access control, anti-virus filtering,
`
`and more. Since 2001, over 1,000 graduate students were exposed to these simple
`
`principles directly through my teaching and research at Stony Brook University.
`
`26. Moreover, in an undergraduate course titled “Advanced Systems
`
`Programming in Unix/C,” I cover many topics of system security and vulnerabilities,
`
`such as the structure of UNIX processes, and memory segments such as the heap and
`
`stack. This course covers details of several hundred Linux system calls. Often, the
`
`first assignment for this course is to develop a tool to encrypt/decrypt files using
`
`advanced ciphers, use digital signatures to certify the cipher keys used, and reliably
`
`recover files in case of failures. Since 2001, several hundred undergraduate students
`
`
`
`- 18 -
`
`

`

`
`were exposed to these principles directly through my teaching and research at Stony
`
`IPR 2022-01190
`IPR 2022-01191
`U.S. Patent No. 10,789,393
`
`Brook University.
`
`27.
`
`In another undergraduate course, System Administration, I taught
`
`network configuration, security, and storage configuration and reliability. In a
`
`special topics course on Storage Systems, I covered many topics such as data
`
`deduplication, RAID, transactional storage, storage hardware including modern
`
`Flash based ones, virtual storage, backup/restore, snapshots and continuous data
`
`protection (CDP), NAS and SAN, and NFS.
`
`28.
`
`Overall, in addition to the aforementioned experience, my technical
`
`experience relevant to the challenged patent(s) at the time of the alleged invention(s)
`
`included the following: set up remote access to an assortment of computer hosts;
`
`accessed such hosts remotely and/or interactively, both as a user as well as an
`
`administrator; administered remote hosts (e.g., updates and upgrades) by remote
`
`login using various techniques (e.g., telnet, rlogin, rsh, ssh, rdist, rsync); set up
`
`computers for users to use while administered said computers remotely, including
`
`changing users’ passwords, locking out