throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`DELL INC., EMC CORPORATION, HEWLETT-PACKARD
`ENTERPRISE CO., HP ENTERPRISE SERVICES, LLC, and TERADATA
`OPERATIONS, INC.
`
`Petitioners
`
`v.
`
`REALTIME DATA LLC
`Patent Owner
`____________________
`
`Case IPR2017-00176
`&
`Case IPR2017-00806
`[consolidated]
`Patent No. 7,161,506
`____________________
`
`DECLARATION OF KENNETH A. ZEGER, PH.D., IN SUPPORT OF
`PATENT OWNER’S RESPONSE
`
`Realtime 2004
`Teradata v. Realtime
`IPR2017-00806
`
`

`

`TABLE OF CONTENTS
`
`
`
`
`
`
`Introduction ........................................................................................................ 2
`A.
`Engagement ......................................................................................... 2
`B.
`Background and Qualifications ........................................................... 3
`
`
`
`I.
`
`II. Materials Considered ........................................................................................ 6
`
`III. Person Of Skill In The Art ............................................................................... 7
`
`IV. Petitioners’ Obviousness Theory As To Claim 104 Limitation C .................. 8
`
`V. Petitioners’ Obviousness Theories With Respect To Claim 105 ................... 16
`
`VI. Conclusion ..................................................................................................... 21
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`I, Kenneth A. Zeger, Ph.D., a resident of San Diego, California, declare as
`
`
`
`
`
`follows:
`
`I.
`
`Introduction
`A. Engagement
`
`I have been retained by Patent Owner Realtime Data LLC (“Realtime”
`
`or “Patent Owner”) through Zunda LLC to provide my opinions with respect to
`
`their Response to the Petitions for Inter Partes Review in IPR2017-00176 and
`
`IPR2017-00806 (the “Dell Petition” and “Teradata Petition,” respectively) as to
`
`U.S. Patent 7,161,506. Zunda LLC is being compensated for my time at the rate of
`
`$690 per hour for time spent on non-deposition tasks and for deposition time. I
`
`have no interest in the outcome of this proceeding and the payment of my fees is in
`
`no way contingent on my providing any particular opinions.
`
`
`
`As a part of this engagement, I have also been asked to provide my
`
`technical review, analysis, insights, and opinions regarding the Declarations of Dr.
`
`Charles D. Creusere (“Creusere Declaration(s),” Ex. 1002 in both proceedings)
`
`with respect to challenged claims 104 and 105, as well as the Dell and Teradata
`
`Petitions, which rely on the Creusere Declarations.
`
`
`
`The statements made herein are based on my own knowledge and
`
`opinions.
`
`
`
`
`- 2 -
`
`
`
`

`

`
`
`Background and Qualifications
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`I received a Bachelor’s degree in Electrical Engineering and
`
`B.
`
`
`Computer Science from the Massachusetts Institute of Technology in 1984.
`
`
`
`I received a Master of Science degree in Electrical Engineering and
`
`Computer Science from the Massachusetts Institute of Technology in 1984.
`
`
`
`I received a Master of Arts degree in Mathematics from the University
`
`of California, Santa Barbara, CA in 1989.
`
`
`
`I received a Ph.D. degree in Electrical and Computer Engineering
`
`from the University of California, Santa Barbara, CA in 1990.
`
`
`
`I am currently a Full Professor of Electrical and Computer
`
`Engineering at the University of California, San Diego (UCSD). I have held this
`
`position since 1998, having been promoted from Associated Professor after two
`
`years at UCSD. I have been an active member of the UCSD Center for Wireless
`
`Communications for 20 years. I teach courses full-time at UCSD in the fields of
`
`Electrical and Computer Engineering, and specifically in subfields including
`
`communications, information theory, and data compression at the undergraduate
`
`and graduate levels. Prior to my employment at UCSD, I taught and conducted
`
`research as a faculty member at the University of Illinois, Urbana-Champaign for
`
`four years, and at the University of Hawaii for two years.
`
`
`
`
`- 3 -
`
`
`
`

`

`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
` My twenty-plus years of industry experience includes consulting work
`
`
`
`for the United States Department of Defense as well as for private companies such
`
`as Xerox, Nokia, MITRE, ADP, and Hewlett-Packard. The topics upon which I
`
`provide consulting expertise include data communications for wireless networks,
`
`digital communications, information theory, computer software, and mathematical
`
`analyses.
`
`
`
`I have authored approximately 75 peer-reviewed journal articles, the
`
`majority of which are on the topic of communications, information theory, or
`
`signal processing. I have also authored over 110 papers at various conferences and
`
`symposia over the past thirty-plus years, such as the: IEEE International
`
`Conference on Communications; IEEE Radio and Wireless Symposium; Wireless
`
`Communications and Networking Conference; IEEE Global Telecommunications
`
`Conference; International Symposium on Network Coding; IEEE International
`
`Symposium on
`
`Information Theory; UCSD Conference on Wireless
`
`Communications; International Symposium on Information Theory and Its
`
`Applications; Conference on Advances in Communications and Control Systems;
`
`IEEE Communication Theory Workshop; Conference on Information Sciences and
`
`Systems; Allerton Conference on Communications, Control, and Computing;
`
`Information Theory and Its Applications Workshop; Asilomar Conference on
`
`
`
`
`- 4 -
`
`
`
`

`

`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`Signals, Systems, and Computers. Roughly half of those papers relate to data
`
`
`
`
`
`compression. I also am co-inventor on a US patent disclosing a memory saving
`
`technique for image compression.
`
`
`
`I was elected a Fellow of the IEEE in 2000, an honor bestowed upon
`
`only a small percentage of IEEE members. I was awarded the National Science
`
`Foundation Presidential Young Investigator Award in 1991, which included
`
`$500,000 in research funding. I received this award one year after receiving my
`
`Ph.D.
`
`
`
`I have served as an Associate Editor for the IEEE Transactions on
`
`Information Theory and have been an elected member of the IEEE Information
`
`Theory Board of Governors for three, three-year terms. I organized and have been
`
`on the technical advisory committees of numerous workshops and symposia in the
`
`areas of communications and information theory. I regularly review submitted
`
`journal manuscripts, government funding requests, conference proposals, student
`
`theses, and textbook proposals. I also have given many lectures at conferences,
`
`universities, and companies on topics in communications and information theory.
`
`
`
`I have extensive experience in electronics hardware and computer
`
`software, from academic studies, work experience, and supervising students. I
`
`
`
`
`- 5 -
`
`
`
`

`

`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`personally program computers on an almost daily basis and have fluency in many
`
`
`
`
`
`different computer languages.
`
` My curriculum vitae, attached to this declaration as Exhibit A,
`
`(“Zeger Curriculum Vitae”), lists my publication record in archival journals,
`
`international conferences, and workshops.
`
`II. Materials Considered
`
`I have been asked to provide a technical review, analysis, insights, and
`
`opinions. My technical review, analysis, insights, and opinions are based on almost
`
`35 years of education, research, and experience, as well as my study of relevant
`
`materials.
`
`
`
`I have reviewed and am familiar with the ’506 Patent specification
`
`and claims. My understanding of the claims is based on the plain and ordinary
`
`meaning of the claims as would be understood by a person of ordinary skill in the
`
`art, unless the inventor has provided a special meaning for a term. My opinions set
`
`forth herein do not rest on a disagreement with Dr. Creusere as to the meaning of
`
`any claim term or limitation.
`
`
`
`I have reviewed and am familiar with the Petitions for Inter Partes
`
`Review, Patent Owner Preliminary Responses, and the Board’s Decisions to
`
`Institute in these proceedings.
`
`
`
`
`- 6 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`
`
`I have reviewed the Declarations of Dr. Charles D. Creusere in both
`
`proceedings. I have also reviewed the Franaszek, Hsu, and Sebastian references
`
`submitted by Petitioners in these proceedings, and am familiar with those
`
`references. In addition, I have reviewed Dr. Creusere’s deposition testimony in
`
`these proceedings. Based on my review of the materials identified in this paragraph
`
`and paragraph 17 above, I did not identify any differences between the Petitions
`
`and the Creusere Declarations across the Dell and Teradata proceedings that are
`
`material to my opinions herein. The opinions I present here apply equally to both
`
`sets of Petitions and Declarations, and were formed on that basis.
`
` This declaration represents only opinions I have formed to date. I may
`
`consider additional documents as they become available or other documents that
`
`are necessary to form my opinions. I reserve the right to revise, supplement, or
`
`amend my opinions based on new information and on my continuing analysis.
`
`III. Person Of Skill In The Art
`
`I am familiar with the concept of the person of ordinary skill in the art
`
`(“POSA”), and have reviewed Dr. Creusere and Petitioners’ views on the
`
`definition and qualifications of the POSA for purposes of these proceedings. I do
`
`not disagree with those views, and have applied the same understandings in
`
`forming my opinions set forth herein.
`
`
`
`
`- 7 -
`
`
`
`

`

`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
` Throughout my declaration, even if I discuss my analysis in the
`
`
`
`present tense, I am always making my determinations based on what a POSA
`
`would have known at the time of the invention.
`
`IV. Petitioners’ Obviousness Theory As To Claim 104 Limitation C
`
`I understand that at his deposition, Dr. Creusere testified that a POSA
`
`combining Franaszek with Hsu would always use Hsu to identify a data type and
`
`three redundancy metrics for each of Franaszek’s data blocks.
`
`Q. Okay. Now, with respect to how Franaszek’s system once
`modified by Hsu would actually make use of Hsu’s data type and
`compression metrics, where in the Franaszek flow process would
`Hsu’s data type and compression metrics analysis occur and -- well,
`just – let’s start there.
`[A.] Well, I mean, a person of ordinary skill in the art, of course,
`would have to -- would have to consider their application what they
`are trying to application [sic]. My own personal feeling on this as a
`person of ordinary skill in the art would be that you would do this in --
`around the same flight in block 4A -- in [Franaszek’s] figure 4A, that
`first block, where it says, at the moment data type available and it
`makes that first split.
`My own opinion is that this is where you would add the Hsu concepts,
`so you -- if you had the data type, then you could use that to guide
`Hsu into making a better situation, into making better or to looking at
`fewer possibilities. If you didn't have the data type, you could then
`
`
`
`
`- 8 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`apply Hsu to finding data type and then follow the path to the right
`in figure 4A, where it says, yes, and move -- and move on.
`
`Id. at 131:13-132:15 (emphasis added).
`
` While I do not agree that a POSA would be motivated to combine
`
`Franaszek with Hsu at all, I do agree with Dr. Creusere that if a POSA were to
`
`make such a combination, the POSA would rely on Hsu’s powerful data type
`
`recognition and compressibility analysis approach to identify a data type and three
`
`redundancy metrics for each of Franaszek’s data blocks.
`
`
`
`I understand Dr. Creusere’s explanation of how a POSA would
`
`combine Hsu into Franaszek’s Figure 4A to be visually depicted by annotated
`
`figure below.
`
`
`
`
`- 9 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`
`
`
`
`
`
`I also understand that Dr. Creusere testified that using Hsu’s approach
`
`will always yield a result for a block’s data type, and I agree with Dr. Creusere in
`
`that particular regard.
`
`Q. And in Hsu’s approach, of those four pieces of information that
`the data type and the three redundancy metrics [sic], it will always be
`
`- 10 -
`
`
`
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`the case that at least one, and likely more of those will be identified
`for a given data block, right?
`A. As regards the three redundancy metrics, those are basically
`statistical analysis calculations, and those can always be calculated for
`any data block. As far as the – as the data type information as output
`by Hsu’s new file routine, that, that’s – that will – that should in my,
`in my opinion, as a person of ordinary skill in the art, my best estimate
`is that will always output something. It will always give you
`something. Now exactly what it outputs under certain circumstances,
`I’m not totally sure of.
`Ex. 2003 at 21:13-22:6 (emphasis added).
`
` Based on my review of Dr. Creusere’s testimony, I recognize that Dr.
`
`Creusere attempted to qualify the above testimony through additional testimony on
`
`re-direct from counsel for Petitioners. Specifically, I am aware that Dr. Creusere
`
`testified that Hsu’s approach to data type recognition uses “the UNIX file
`
`command,” that “[t]he UNIX file command . . . will return an indication of data for
`
`any kind of unrecognized file type,” and that there is therefore “a possibility” that
`
`Hsu would in fact fail to determine a data type and simply return “data.” Ex. 2003
`
`at 146:15-148:1.
`
`
`
`I disagree with Dr. Creusere’s testimony and opinions in that regard.
`
`To the contrary, it is my opinion that a POSA would understand Hsu to teach an
`
`
`
`
`- 11 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`approach that will always recognize a data type for each data block, and would not
`
`conclude that Hsu’s reference to UNIX file command indicates otherwise.
`
` Hsu describes a system that avoids any content independent
`
`compression and that instead uses an entirely content-dependent approach. Hsu
`
`teaches the identification of a “block type” (i.e., data type) for each data block
`
`using a “new-file” procedure. Ex. 1005 at 1103-1104. Hsu’s “new-file” procedure
`
`analyzes three 512-byte segments within the block: 512 bytes in the beginning, 512
`
`bytes in the middle, and 512 bytes in the end. Ex. 1005 at 1103-1104. During that
`
`analysis, Hsu’s method looks for “the pattern of data contained” in each 512 byte
`
`segment. Ex. 1005 at 1103-1104. Hsu compares each segment to a collection of
`
`known data patterns from Unix and other operating systems. Ex. 1005 at 1103-
`
`1104.
`
` Correlating with known patterns, Hsu identifies the data type of the
`
`block as one of the ten possible classifications shown in Table I, reproduced below.
`
`Ex. 1005 at 1103, 1107. In the event that two of the tested segments point to one
`
`data type and the third to another, Hsu uses a “majority vote” to reconcile the
`
`discrepancy. Ex. 1005 at 1104. Where each of the three segments points to
`
`different data types, Hsu uses “the first data type detected.” Ex. 1005 at 1104.
`
`
`
`
`- 12 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`
`
`Ex. 1005 at 1107.
`
` Table I makes clear that Hsu’s list of ten possible data types does not
`
`include “data,” or any other indication of an unrecognized data type. Accordingly,
`
`the teachings of Hsu itself foreclose the possibility that its approach will fail to
`
`recognize a data type for a data block. Indeed, Hsu specifically explains that its
`
`“new-file” approach “compares not only the first 512 bytes of a data set, but also
`
`512 bytes in the middle of the set and the 512 bytes at the end (if they exist)” in
`
`order to “provide a better indication of the primary data type of a file. . . .” Ex.
`
`1005 at 1104 (emphasis original). Hsu also explains that its approach compares
`
`those patterns to a larger set of known patterns than previous versions of UNIX.
`
`Ex. 1005 at 1104. Both of those teachings would lead a POSA to conclude that Hsu
`
`
`
`
`- 13 -
`
`
`
`

`

`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`teaches an approach that will not only always recognize and output some data type,
`
`
`
`
`
`but will also be more likely to correctly recognize the data type.
`
`
`
`I have continuously used UNIX, on an almost weekly basis, since the
`
`1980s. Based on my personal experience, I am aware that there were numerous
`
`versions of UNIX’s file command during the 1980s and 1990s. Those versions
`
`were not necessarily consistent. Moreover, while some POSAs may have been
`
`familiar with UNIX and its file command as of the 1995 publication date of Hsu or
`
`the 2001 priority date of the ’506 patent, a POSA would almost certainly not have
`
`been familiar with how any particular version of UNIX’s file command actually
`
`worked. A POSA reading Hsu would neither know which particular version of
`
`UNIX’s file command Hsu had utilized, nor would he or she have reason to
`
`conclude that Hsu may fail to recognize data types because of its teachings
`
`regarding UNIX. And a POSA would appreciate that Hsu does not state that its
`
`approach is necessarily identical to any particular version of UNIX’s file
`
`command, but rather states that “new-file works in similar fashion.” Ex. 1005 at
`
`1104. In addition, I am not aware of evidence that a POSA reading Hsu would
`
`have had access to either the source code underlying Hsu’s system or the source
`
`code for the specific version of UNIX on which Hsu had relied (if any).
`
`Accordingly, a POSA would have no reason to look past Hsu’s own teachings—
`
`
`
`
`- 14 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`which demonstrate that Hsu will always identify a data type for each data block—
`
`to conclude that Hsu may sometimes fail to identify a data type simply because it
`
`was based on some unknown version of UNIX with unknown modifications. Hsu
`
`gives neither an explicit nor an implicit suggestion that it will not identify a data
`
`type, nor even a clue about how such a (nonexistent, in my opinion) situation
`
`would or could be handled. A POSA would not interpret that silence as an
`
`indication that Hsu has a problem that it does not address. Rather, the POSA would
`
`understand that Hsu simply does not have such a problem.
`
` Turning to limitation 104[c], which recites “performing data
`
`compression with a single data compression encoder, if a data type of the data
`
`block is not identified,” it is my opinion that limitation 104[c] can only be met
`
`where a data type of the data block is not identified. Indeed, that is the express
`
`language of the limitation.
`
` Because a POSA combining Franaszek with Hsu would always use
`
`Hsu to identify a block’s data type, Ex. 2003 at 131:13-132:15, and because Hsu
`
`will always identify a data type for any data block (as explained above), it follows
`
`that the alleged combination of Franaszek and Hsu will always identify a data type
`
`for each data block.
`
`
`
`
`- 15 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`
`
`I understand that Petitioners have an alternative theory in which
`
`Franaszek would be modified based on Sebastian. Under that theory, Sebastian’s
`
`generic filter would be used when Franaszek does not have a data type. That theory
`
`does not affect my opinion with respect to limitation 104[c], however, because (as
`
`explained above) Hsu would always identify a data type for each block in
`
`Franaszek’s system, and thus Sebastian’s generic filter would never be used.
`
`V.
`
`Petitioners’ Obviousness Theories With Respect To Claim 105
` Like Claim 104, Claim 105 expressly requires analyzing the data to
`
`identify one or more data types where the analysis is not “based only on a
`
`descriptor” (steps [b] and [e]). Claim 105 further recites, at step [d], “[1] if one or
`
`more encoders are associated to said type, compressing said data block with at
`
`least one of said one or more encoders, [2] otherwise compressing said data block
`
`with a default data compression encoder[.]”
`
`
`
`I understand that Petitioners’ theory with respect to claim 105 also
`
`proposes adapting the descriptor-based system of Franaszek based on the teachings
`
`of Hsu. See IPR2017-00176, Pet. at 43-44; IPR2017-00806, Pet. at 46.
`
` Based on my review of Franaszek, a POSA would understand
`
`Franaszek to teach that Franaszek’s system will always have “one or more
`
`encoders [ ] associated to” an identified data type, and that a data block with an
`
`
`
`
`- 16 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`identified data type will always be compressed “with at least one of said one or
`
`more encoders.”
`
` Since Hsu’s approach would always be used, Ex. 2003 at 131:13-
`
`132:15, and will always recognize a data type, it follows that the ensuing
`
`combination of Franazek and Hsu will always recognize a data type of a data
`
`block, will always have one or more encoders associated with each data block, and
`
`will ultimately always compress that data block using those one or more associated
`
`encoders. In other words, the combined system of Franaszek and Hsu would never
`
`use or perform Franaszek’s step 407.
`
`
`
`I understand that Petitioners and Dr. Creusere have proposed that a
`
`POSA could have modified Franaszek such that—when “a data type has been
`
`included in the ‘type’ field, but is not associated with a particular encoder”—
`
`Franaszek would use a default encoder, as purportedly taught by Sebastian.
`
`IPR2017-00176, Pet. at 42-43; IPR2017-00806, Pet. at 44-45.
`
`
`
`I am not aware of any evidence that a POSA would have a reason to
`
`believe that Franaszek’s system would fail to associate at least one encoder with an
`
`identified data type. Rather, based on Franaszek’s teachings, a POSA would
`
`conclude based on Franaszek’s teachings that that scenario would not occur within
`
`
`
`
`- 17 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`Franaszek’s system. Dr. Creusere testified to the same effect, and appears to agree
`
`with me on this point.
`
`Q. Okay. So your point is simply that Franaszek will have in some
`fashion a list of algorithms that have been predetermined to be the
`appropriate set for a particular data block given the data type
`information that has been provided for that data block?
`A. Yes. Franaszek will have a list of algorithms associated with a
`given type of data, assuming that, assuming that it knows that type of
`data. Franaszek doesn’t address the situation directly, where, where it
`doesn’t know – where there might be type description data. It doesn’t
`know it. But assuming it knows that data, it will have some sort of a
`list associated with that data of possible compression algorithms and it
`will select, it will go through the same process of selecting one of
`those compression algorithms to apply to encode the block.
`Q.
`And to your point just a second ago, Franaszek does not
`contemplate a situation in which it is provided with data type
`information but does not have a list of compression techniques
`associated with that data type. True?
`A.
`From the preferred embodiment of Franaszek, I don’t recall
`any indication that Franaszek contemplates that scenario.
`Ex. 2003 at 14:21-16:1 (emphasis added).
`
` A POSA thus would not have been motivated to modify Franaszek
`
`based on the alleged teachings of Sebastian to solve a problem Franaszek did not
`
`have.
`
`
`
`
`- 18 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`
`
`I also understand that Petitioners assert that “Sebastian makes a
`
`decision about whether a ‘filter’ is associated with the data type, and if not, it
`
`compresses the data using the generic filter.” IPR2017-00176, Pet. at 42; IPR2017-
`
`00806, Pet. at 44 (emphasis added).
`
`
`
`I disagree with that characterization of Sebastian’s teachings, and a
`
`POSA would not have understood such a teaching from Sebastian. To the contrary,
`
`a POSA would understand that Sebastian teaches that there is always an encoder
`
`associated with each of Sebastian’s data types, but that that encoder may not
`
`always be installed, which is why a default filter exists. Ex. 1030 at 1:55-60, 4:9-
`
`15 (explaining that the generic filter is used when a filter matching the format of
`
`the data is not installed). Sebastian does not contain a teaching as to a scenario in
`
`which its generic filter will be used when a data type for a data block is not
`
`available to it. Indeed, Sebastian does not even contemplate a scenario in which a
`
`data type is not available to its system. Dr. Creusere appears to have acknowledged
`
`the same during his deposition.
`
`So Sebastian does not have any discussion of a scenario in
`Q.
`which the data type for a data block is not available to it and what it
`would do in that scenario. True?
`A. Not to my recollection. Sebastian is a long patent. To be able to
`say that definitively, I would have to through line by line. But to my
`
`
`
`
`- 19 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`recollection, that is not something that is – that is covered by
`Sebastian.
`Q. And column 4 in that same section you were looking at, and
`throughout Sebastian, the only scenario in which Sebastian teaches
`using its generic filter is when its system does not already have the
`desired or appropriate compression technique for a particular data
`type. True?
`A.
`Sebastian specifically states that if it doesn’t have a filter that
`matches the source’s data format, then it will use a generic filter. So
`that is as far as it goes on the subject. It doesn’t, to my recollection,
`state other scenarios.
`Ex. 2003 at 27:19-28:16 (emphasis added).
`
` Accordingly, I do not believe that Sebastian’s teachings would have
`
`motivated a POSA to use a generic encoder where Franaszek had a data type that is
`
`not recognized by its system. While I understand that a POSA is not limited to
`
`bodily incorporating one prior art reference into another, it is my opinion that a
`
`POSA reading Sebastian would simply not have any basis for arriving at the idea
`
`of using Sebastian’s generic filter to compress blocks with unrecognized data
`
`types. Again, that is not a scenario Sebastian contemplates, and I have not seen any
`
`other teaching or evidence in the Petitions or Dr. Creusere’s declarations to
`
`indicate that a POSA would have arrived upon that idea.
`
`
`
`
`- 20 -
`
`
`
`

`

`
`
`
`
`IPR2017-00176
`IPR2017-00806
`ZEGER DECLARATION
`
`
`VI. Conclusion
`
`In signing this declaration, I understand that the Declaration will be
`
`filed as evidence in contested cases before the Patent Trial and Appeal Board of
`
`the United States Patent and Trademark Office. I acknowledge that I may be
`
`subject to cross-examination in these cases and that cross examination will take
`
`place within the United States. If cross examination is required of me, I will appear
`
`for cross examination within the United States during the time allotted for cross
`
`examination.
`
`
`
`I declare that all statements made herein of my own knowledge are
`
`true and that all statements made on information and belief are believed to be true;
`
`and further that these statements were made with the knowledge that willful false
`
`statements and the like so made are punishable by fine or imprisonment, or both,
`
`under Section 1001 of Title 18 of the United States Code, and that such willful
`
`false statements may jeopardize the validity of the ʼ506 Patent.
`
`
`
`
`
`
`
`
`Executed on September 22, 2017 in San Diego, California.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`
`
`Kenneth A. Zeger, Ph.D.
`- 21 -
`
`
`
`

`

`
`
`
`
`
`EXHIBIT A
`EXHIBIT A
`
`

`

`Kenneth A. Zeger
`
`- Professor and consultant -
`
`January 8, 2017
`
`Personal Data
`
`Email: zeger@ZundaLLC.com
`Web: http://ZundaLLC.com (company)
`http://zeger.us (university)
`Citizenship: USA
`
`Academic Degrees
`
`Ph.D (ECE):
`University of California, Santa Barbara (1990)
`M.A. (Mathematics): University of California, Santa Barbara (1989)
`S.M. (EECS):
`Massachusetts Institute of Technology (1984)
`S.B.
`(EECS):
`Massachusetts Institute of Technology (1984)
`
`Faculty Positions
`
`University of California, San Diego
`
`Professor of Electrical Engineering (1998-present)
`-
`- Associate Professor of Electrical Engineering (1996-1998)
`
`University of Illinois, Urbana-Champaign - Associate Professor of Electrical Engineering (1995-1996)
`- Assistant Professor of Electrical Engineering (1992-1995)
`
`University of Hawaii
`
`- Assistant Professor of Electrical Engineering (1990-1992)
`
`Honors and Awards
`
`• IEEE Fellow (2000)
`• NSF Presidential Young Investigator Award (1991)
`• United States Mathematical Olympiad (1980)
`
`Page 1 of 21
`
`CV of K. Zeger
`
`

`

`Consulting Experience
`
`January 8, 2017
`
`Clients:
`
`• Automatic Data Processing Co.
`• Hewlett-Packard Laboratories
`• U.S. Department of Defense
`• MITRE Co.
`• Nokia Telecommunications Inc.
`• Prominent Communications Inc. (Chair of Technical Advisory Board)
`• ViaSat Inc.
`• Xerox Co. Palo Alto Research Center
`• Zeger-Abrams Inc.
`• Zunda LLC (President)
`• Expert Witness in numerous patent infringement and trade secret litigations.
`
`Topics:
`
`• Image, fax, video, vision, television coding.
`• Speech coding and recognition, audio coding, telephony.
`• Electronic hardware devices: cell phones, printers, cameras, TV, computers, dongles, etc.
`• Protocols, networks, Internet, security, GPS.
`• Digital and wireless communications.
`• Error correcting codes.
`• Communication protocols.
`• Software: C, C++, C#, BASIC, Lisp, Fortran, Cobol, Algol, Pascal, Assembler, TMS320, Java,
`DSP, Verilog, HTML, JavaScript, Perl, Visual Basic, VHDL.
`• National security topics.
`
`Page 2 of 21
`
`CV of K. Zeger
`
`

`

`Professional Activities
`
`January 8, 2017
`
`• Board of Governors of IEEE Information Theory Society (1998-2000, 2005-2007, and 2008-
`2010)
`• Associate Editor At-Large of IEEE Transactions on Information Theory (1995-1998).
`• Steering Committee member of Fourth Workshop on Network Coding, Theory, and Applications
`(2007).
`• Co-organizer of: Third Workshop on Network Coding, Theory, and Applications, San Diego
`(2007).
`• Co-organizer of NSF Workshop on Joint Source-Channel Coding, San Diego, California. (1999)
`• Co-organizer of IEEE Information Theory Workshop, San Diego, California. (1998)
`• Co-organizer of Allerton Conference on Communication, Control, and Computing (1995)
`• Co-organizer of IEEE Communication Theory Workshop, Ojai, California. (1990)
`• International Advisory Committee of International Symposium on Spread Spectrum Techniques
`and Applications (ISSTA) (Taichung, Taiwan 2010)
`• Program Committee of Information Theory Workshop (ITW) (Jerusalem, Israel, 2015)
`• Program Committee member of International Symposium on Network Coding (NetCod) (Sydney,
`Australia, 2015)
`• Program Committee member of International Symposium on Network Coding (NetCod) (Bei-
`jing, China, 2011)
`• Program Committee member of Workshop on Network Coding, Theory, and Applications (Net-
`Cod) (Lausanne, Switzerland, 2009)
`• Program Committee member of Workshop on Network Coding, Theory, and Applications (Net-
`Cod) (Hong Kong, 2008)
`• Program Committee member of Workshop on Network Coding, Theory, and Applications (Net-
`Cod) (Boston, 2006)
`• Program Committee member of International Symposium on Information Theory (ISIT) (Toronto,
`Canada 2008)
`• Program Committee member of International Symposium on Information Theory (ISIT) (Ade-
`laide, Australia 2005)
`• Program Committee member of International Conference on Image Processing (ICIP) (Atlanta,
`Georgia, September 2006).
`• Program Committee member of International Conference on Image Processing (ICIP) (Genova,
`Italy, 2005)
`• Program Committee member of International Conference on Image Processing (ICIP) (Singapore
`2004)
`• Program Committee member of International Conference on Image Processing (ICIP) (Barcelona,
`Spain, 2003)
`• Program Committee member of International Symposium on Information Theory and its Appli-
`cations (Monterey, California 2016)
`• Program Committee member of International Symposium on Information Theory and its Appli-
`cations (Melbourne, Australia 2014)
`
`Page 3 of 21
`
`CV of K. Zeger
`
`

`

`January 8, 2017
`
`• Program Committee member of International Symposium on Information Theory and its Appli-
`catio

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