`
`
`
`
`
`
`
`
`
`
`
`
`Patent Owner’s Response and Notice of Supplemental
`Evidence in Response to Petitioner’s Objections to Patent
`Owner’s Evidence Dated October 30, 2019
`
`
`
`
`
`
`
`
`
`
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 1
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________
`
`
`AMERICAN NATIONAL MANUFACTURING INC.,
`Petitioner,
`
`v.
`
`SLEEP NUMBER CORPORATION
`f/k/a SELECT COMFORT CORPORATION,
`Patent Owner.
`____________
`
`Case No. IPR2019-00500
`Patent No. 9,737,154 B2
`____________
`
`
`
`
`
`
`SUPPLEMENTAL DECLARATION OF GEORGE EDWARDS
`IN SUPPORT OF PATENT OWNER’S RESPONSE
`
`
`
`
`
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 2
`
`
`
`
`
`TABLE OF CONTENTS
`
`i
`
`
`
`
`
`I, George Edwards, declare as follows:
`
`1.
`
`I am over the age of 21 years and am fully competent to make this
`
`Supplemental Declaration. I make the following statements based on personal
`
`knowledge and, if called to testify to them, could and would do so.
`
`2.
`
`I have been retained on behalf of Sleep Number Corporation (“Sleep
`
`Number”). My fee is not contingent on the outcome of any matter or on any of the
`
`positions I have or will take in any matter. I have no financial interest in Sleep
`
`Number.
`
`1
`
`
`
`
`
`5.
`
`I attended graduate school at the University of Southern California,
`
`where I was a USC Viterbi School of Engineering Dean's Doctoral Fellow and
`
`Annenberg Graduate Fellow. I received an MS in computer science in 2006 and a
`
`PhD in computer science in 2010 from USC. My MS research focused on
`
`distributed, real-time, and embedded systems. My PhD research focused on the
`
`analysis of distributed systems and their architecture, with an emphasis on mobile
`
`applications and embedded systems. My research was funded by several government
`
`agencies, such as the Department of Defense and the NSA, and large companies,
`
`such as Bosch and InfoSys. I presented my work at numerous conferences and in
`
`academic journals, industry magazines, and other publications. In 2008, I received
`
`the USC Computer Science Department’s award for outstanding graduate student
`
`research.
`
`6.
`
`I am the founder of Quandary Peak Research, Inc., where I hold the
`
`titles of President and Computer Scientist. Quandary Peak Research is a software
`
`analysis company with twelve employees located in Los Angeles, Nashville, and
`
`Washington, D.C. Quandary Peak Research’s software analysis services fall into
`
`three areas: (1) audits and compliance in highly regulated industries; (2) technical
`
`due diligence in mergers and acquisitions; and (3) litigation and intellectual property.
`
`In all three areas, Quandary Peak analyzes software and computer systems to answer
`
`questions about the development, structure, behavior, and quality of those systems.
`
`2
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 5
`
`
`
`
`
`7.
`
`In my role as President, I manage the company’s business affairs. In
`
`my role as Computer Scientist, I perform software analysis on behalf of clients. I
`
`have analyzed a broad variety of complex, real-world software systems, including
`
`many embedded software systems, mobile devices, and web and Internet
`
`applications. I have reverse-engineered the hardware and software designs of dozens
`
`of distributed systems. I have conducted many investigations of the design and
`
`implementation of these systems with respect to specific patent claims and other
`
`intellectual property considerations, such as copyright infringement and trade secret
`
`theft.
`
`8.
`
`I was formerly employed as a Lecturer of Computer Science at the
`
`University of Southern California. In that capacity, I taught Requirements
`
`Engineering (CSCI 568), a graduate-level software engineering class, and Data
`
`Structures and Algorithms (CSCI 102), an undergraduate-level software design and
`
`programming class.
`
`9.
`
`I also formerly worked as a research scientist and software engineer at
`
`Blue Cell Software LLC, Intelligent Systems Technology, Inc., IBM, and The
`
`Boeing Company. During my time with Blue Cell, I built a simulation-based
`
`software design and modeling environment. While at IBM, I conducted research on
`
`next-generation mobile architectures, such as large-scale mobile device provisioning
`
`3
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 6
`
`
`
`
`
`systems. At Boeing, I helped to design software for collecting and processing sensor
`
`data and geo-location data from military vehicles.
`
`10.
`
`I have authored over thirty scholarly journal articles, magazine articles,
`
`conference papers, and book chapters on varied topics related to software
`
`engineering and distributed systems. I have co-authored many peer-reviewed papers
`
`specifically related to embedded systems and software control systems, such as
`
`“Integrating Publisher/Subscriber Services
`
`in Component Middleware
`
`for
`
`Distributed Real-time and Embedded Systems,”1 “Engineering Heterogeneous
`
`Robotics Systems: A Software Architecture-Based Approach,”2 and “A Middleware
`
`
`1 George Edwards, Douglas C. Schmidt, Aniruddha Gokhale, and Bala Natarajan.
`
`“Integrating Publisher/Subscriber Services
`
`in Component Middleware
`
`for
`
`Distributed Real-time and Embedded Systems.” Proceedings of the 42nd Annual
`
`ACM Southeast Conference (ACMSE), April 2004.
`
`2 Nenad Medvidovic, Hossein Tajalli, Joshua Garcia, Yuriy Brun, Ivo Krka, and
`
`George Edwards. “Engineering Heterogeneous Robotics Systems: A Software
`
`Architecture-Based Approach.” IEEE Computer, 2011.
`
`4
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 7
`
`
`
`
`
`Platform for Providing Mobile and Embedded Computing Instruction to Software
`
`Engineering Students,”3 among others.
`
`11.
`
`I have delivered numerous invited lectures, seminars, and technology
`
`demonstrations related to software design and analysis for university courses,
`
`research symposia, conferences, workshops, and industry events in the field of
`
`computer science. I have also served as a reviewer, committee member, or panelist
`
`for over a dozen computer science journals, magazines, and conferences.
`
`12.
`
`I am also a member of the Association for Computer Machinery (ACM)
`
`and the IEEE Computer Society.
`
`5
`
`
`
`
`
`and methods that are implemented and executed to a large degree in software that
`
`runs on a microprocessor. For example, the ‘154 and ‘747 Patents teach that the
`
`invention includes a “control device” and “control logic”:
`
`“The control device includes control logic that is capable of calculating
`
`a manifold pressure target based upon the desired pressure setpoint
`
`and a pressure adjustment factor, monitoring pressure within the pump
`
`manifold, adjusting pressure within the air chamber until the sensed
`
`manifold pressure is within an acceptable pressure target error range
`
`of the manifold pressure target, comparing an actual chamber pressure
`
`to the desired pressure setpoint to quantify an adjustment factor error,
`
`and calculating an updated pressure adjustment factor based upon the
`
`adjustment factor error.”4
`
`14. Based upon my training and experience as a computer scientist, I know
`
`that this disclosed “control logic” would naturally be implemented in software. The
`
`control logic is explicitly recited in the system claims of the ‘154 and ‘747 Patents.
`
`(See ‘154 Patent, claim 20, reciting “a control device operably connected to the input
`
`device and to the pressure sensing means, the control device having control logic…”
`
`See also ‘747 Patent, claim 16, reciting, “a control device operably connected to the
`
`
`4 154 Patent at 2:50-60; 747 Patent at 2:40-50.
`
`6
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 9
`
`
`
`
`
`input device and to the pressure sensing means, the control device having control
`
`logic…”) Also, the disclosed capabilities of the control logic include the steps
`
`recited in the method claims of the ‘154 and ‘747 Patents. (See, e.g., ‘154 Patent,
`
`claim 1, reciting, inter alia, “calculating a pressure target for the pump housing,
`
`wherein the pressure target for the pump housing is calculated based upon the desired
`
`pressure setpoint for the air chamber and a pressure adjustment factor;” “adjusting
`
`pressure within the air chamber until a pressure sensed within the pump housing is
`
`substantially equal to the pressure target;” “comparing the actual chamber pressure
`
`to the desired pressure setpoint to determine an adjustment factor error;” and
`
`“modifying the pressure adjustment factor based upon the adjustment factor error.”
`
`See also ‘747 Patent, claim 1, reciting, inter alia, “calculating a pressure target based
`
`upon the desired pressure setpoint and a pressure adjustment factor…”; “adjusting
`
`pressure within the air chamber until a sensed pressure within the pump housing is
`
`substantially equal to the calculated pressure target;” “comparing the actual chamber
`
`pressure to the desired pressure setpoint to determine an adjustment factor error;”
`
`and “modifying the pressure adjustment factor based upon the adjustment factor
`
`error.”)
`
`15. The ‘172 Patent also claims systems that include software and methods
`
`that are performed partly in software. For example, the ‘172 Patent teaches that the
`
`invention includes “a processor for providing commands to the improved valve
`
`7
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 10
`
`
`
`
`
`enclosure assembly during an inflate/deflate cycle.”5 This processor would
`
`necessarily need to execute a software program to provide commands during an
`
`inflate/deflate cycle.
`
`16. Therefore, I am qualified to provide expert opinions regarding the
`
`aspects of the Patents-at-Issue that relate to software.
`
`17.
`
`I am also familiar with certain versions of source code produced by
`
`Petitioner American National Manufacturing, Inc. (“ANM”) and Real-Party-in-
`
`Interest Sizewise Rentals, LLC (“Sizewise”). I was retained by Sleep Number to
`
`conduct source code inspections in the underlying district court cases: Sleep Number
`
`Corporation v. American National Manufacturing,
`
`Inc., No. 5:18-cv-
`
`00357AB(SPx) (C.D. Cal. 2018) and Sleep Number Corporation v. Sizewise Rentals,
`
`LLC, No. 5:18-cv-00356AB(SPx) (C.D. Cal.) (“District Court Cases”). I was also
`
`previously retained by Select Comfort Corporation to conduct source code
`
`inspections in connection with Certain Air Mattress Systems, Components Thereof,
`
`and Methods of Using the Same, US ITC Inv. No. 337-TA-971.
`
`18. During my inspection of ANM’s source code in the District Court
`
`Cases, I analyzed what I identified as Version 1.8, Version 1.9, Version 1.92,
`
`Version 1.97, and Version 2.0 of ANM’s source code. I also helped print certain
`
`
`5 172 Patent at 2:59-61.
`
`8
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 11
`
`
`
`
`
`pages of the source code for Sleep Number’s counsel. My inspection included an
`
`analysis of the source code in comparison to the claims of the Patents-at-Issue. My
`
`methodology for this inspection is discussed below in paragraphs 25-28. While I
`
`inspected and analyzed other versions of source code from ANM and Sizewise and
`
`compared them to the claims of the Patents-at-Issue, I do not discuss that analysis
`
`herein.
`
`19.
`
`It is my understanding from the Contentions defined below that, in the
`
`District Court Cases, Sleep Number has accused various of ANM’s consumer and
`
`medical air bed products that use the source code identified above of infringing the
`
`Patents-at-Issue. It is my understanding that ANM petitioned the United States
`
`Patent and Trademark Office for IPR on each of the Patents-at-Issue. It is also my
`
`understanding that an IPR has been instituted on each patent.
`
`20.
`
`In my declaration, I rely on Sleep Number’s Amended Disclosure of
`
`Asserted Claims and Infringement Contentions against ANM, which is Exhibit
`
`2044; the ‘172 Patent claim chart against ANM, which is Exhibit 2046; the ‘154
`
`Patent claim chart against ANM, which is Exhibit 2048; and the ‘747 Patent claim
`
`chart against ANM, which is Exhibit 2049 (collectively herein “Contentions”). The
`
`Contentions contain reference to source code line numbers and variable and method
`
`names that I helped compile, but I understand those references have been redacted
`
`and are not being provided to the Board at this time. I also understand from Sleep
`
`9
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 12
`
`
`
`
`
`Number’s counsel that neither ANM’s source code nor Sleep Number’s code has yet
`
`been provided to the Board, even though experts and counsel for ANM and Sleep
`
`Number have inspected each other’s code in the District Court Cases. Consequently,
`
`I have been instructed that I am permitted to use the information I learned through
`
`my inspection of the ANM and Sleep Number code in forming the opinions given in
`
`this declaration, but I am not permitted to identify or describe specific portions of
`
`code in detail at this time. Nevertheless, all the code I rely on for this declaration
`
`was either provided by ANM (ANM’s code) or provided to ANM (Sleep Number’s
`
`code) for inspection in the District Court Cases, and I am available to be cross-
`
`examined by ANM’s counsel related to each party’s code. I understand from Sleep
`
`Number’s counsel that if Sleep Number is allowed to use ANM’s source code,
`
`additional briefing on the subject will be discussed with the Board and that Sleep
`
`Number may then provide the source code to the Board. I believe that the Board
`
`would be better able to evaluate my opinions on ANM’s and Sleep Number’s source
`
`code if both parties’ source code and Sleep Number’s unredacted Contentions were
`
`provided under seal to the Board. In the context of this declaration, I do not think it
`
`would be helpful to the Board to see Sleep Number’s source code in isolation (i.e.
`
`without ANM’s source code) because my opinions are related to similarities between
`
`Sleep Number’s code and ANM’s code.
`
`10
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 13
`
`
`
`
`
`21.
`
`I incorporate the Contentions defined above by reference. I do not
`
`provide any opinions on infringement in this declaration, as I understand
`
`infringement is not at issue in this IPR proceeding. However, I understand based
`
`upon my knowledge of IPR proceedings that issues like copying and commercial
`
`success are relevant in this proceeding. I further understand that a connection
`
`between any copying or commercial success and the claimed subject matter is
`
`relevant. My opinions enumerated below regarding the extent to which ANM’s and
`
`Sleep Number’s source code practices the claims of the Patents-at-Issue relate to
`
`those issues, not infringement.
`
`22. As mentioned above, I also reviewed source code related to Sleep
`
`Number’s products. The Sleep Number source code was organized in folders named
`
`“Logic PD\Base_5k_Realtime,” “Sleep Number,” “Sleep Number & SleepIQ,” and
`
`“Winland board documentation.” My methodology for this inspection is discussed
`
`below in paragraphs 25-28. I understand from Sleep Number’s counsel that Sleep
`
`Number located and provided those same folders of source code for inspection to
`
`ANM’s counsel and experts in the District Court Cases. In other words, the Sleep
`
`Number source code that I opine about in this declaration was inspected by ANM’s
`
`counsel and experts. I also understand that during this inspection, ANM’s counsel
`
`and experts printed portions of Sleep Number’s source code, which was then
`
`produced to ANM by Sleep Number. I was provided with a copy of the Sleep
`
`11
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 14
`
`
`
`
`
`Number code printed by ANM’s counsel and experts. Thus, I understand that both
`
`parties have inspected the other’s source code and printed certain pages. I further
`
`understand based upon reviewing Exhibit 2044 that Sleep Number has disclosed in
`
`its Contentions which air controllers sold with its consumer air mattress systems
`
`practice the claims of the Patents-at-Issue.
`
`23.
`
`I understand the source code provided for inspection by ANM and
`
`Sizewise in the District Court Cases is governed by protective orders under which
`
`the source code is marked “HIGHLY CONFIDENTIAL SOURCE CODE –
`
`OUTSIDE COUNSEL ONLY.” I take my obligations under the District Court
`
`Cases’ protective orders very seriously and have maintained the confidentiality of
`
`ANM’s and Sizewise’s source code.
`
`24.
`
`I have also reviewed a document produced by ANM in the District
`
`Court Cases with the Bates number ANMI00133414–22, which I understand is
`
`Exhibit 2052, and a document produced by Sleep Number in the District Court Cases
`
`with a Bates number SN_0021013–33, which I understand is Exhibit 2058. Based
`
`upon my review, I understand that these documents provide a history of the air
`
`controllers sold respectively by ANM and Sleep Number. I rely upon these
`
`documents for certain of my opinions below.
`
`12
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 15
`
`
`
`
`
`13
`
`
`
`
`
`analysis is routinely employed by companies, government agencies, and other
`
`organizations that engage in software engineering. I have personally performed
`
`static program analysis numerous times individually and as part of a team, in both
`
`laboratory and industrial settings, and I taught static program analysis techniques to
`
`software engineering graduate students at the University of Southern California.
`
`27. Static program analysis was an appropriate method to use in this matter
`
`because (1) it provides information highly relevant to the questions that I was asked,
`
`and (2) it only requires access to the source code, and does not require access to a
`
`running instance of the software. Static analysis was therefore an appropriate
`
`approach, given that the form of the software production and restrictions delineated
`
`in the Protective Order did not allow for deployment and execution of the software.
`
`28. Numerous static program analysis tools exist which analyze different
`
`aspects of the code and provide different perspectives on its structure and behavior.
`
`In my analysis of the ANM, Sizewise, and Sleep Number source code, I used
`
`14
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 17
`
`
`
`
`
`Notepad++7, Eclipse8, and MPLAB X9 for viewing and printing the source code files.
`
`I used PowerGREP10 for searching the source code files. I used Beyond Compare11
`
`for comparing source code files and folders.
`
`15
`
`
`
`
`
`• ANM’s products that use Version 1.8, Version 1.97, and Version 2.0 of
`
`ANM’s source code each practice every element of the claims of the ‘154
`
`and ‘747 Patents that are identified in Sleep Number’s Contentions.
`
`• With respect to the software-based control functions recited in claims 12
`
`and 16 of the ‘172 Patent, ANM’s Version 1.8, Version 1.9, Version 1.92,
`
`Version 1.97, and Version 2.0 software is substantially similar to the Sleep
`
`Number software that post-dates the patent filing and issuance and that was
`
`provided for inspection.
`
`• With respect to the software-based control functions recited in the ‘154
`
`Patent, the ‘747 Patent, and claims 2, 6, and 20 of the ‘172 Patent, ANM’s
`
`Version 1.8, Version 1.97, and Version 2.0 software is substantially similar
`
`to the Sleep Number software that post-dates the patent filing and that was
`
`provided for inspection.
`
`• The similarity between ANM’s and Sleep Number’s products and the
`
`release of the relevant ANM products after Sleep Number’s products are
`
`evidence that ANM copied the functionality claimed in the ‘172, ‘154, and
`
`‘747 Patents from the Sleep Number products.
`
`• ANM’s changes in moving from Version 1.8 to Version 1.9 of its source
`
`code and subsequent reversion of those changes in Version 1.97 and
`
`Version 2.0 demonstrate the technical value of the inventions disclosed in
`
`16
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 19
`
`
`
`
`
`the ‘154 and ‘747 Patents and are evidence that these inventions
`
`substantially improved the software-based control of inflation and
`
`deflation in ANM’s products.
`
`17
`
`
`
`
`
`31. Based on my review of the source code, it is my opinion that in both
`
`the ANM and Sleep Number products, the software embedded in the microcontroller
`
`implements control functions for inflation and deflation, including responding to
`
`user inputs to change the pressure in the bed, obtaining readings of the current
`
`pressure in the bed, sending commands to valves and pumps, and displaying
`
`messages on a user interface. Therefore, the software is a critical component of the
`
`ANM and Sleep Number products and understanding the design and function of
`
`these products requires an understanding of the software.
`
`32. By implementing inflation and deflation control functions in software,
`
`it is possible to program sophisticated behaviors into the system. For example, based
`
`upon my review of ANM’s source code, it is my opinion that in certain ANM
`
`products, inflation and deflation control functions are partly regulated by parameters
`
`stored in the memory of the microcontroller. These parameters are updated using
`
`pressure readings that are taken both during and after inflation and deflation. By
`
`dynamically updating these parameters during operation, the software may change
`
`its inflation and deflation behavior based on usage conditions. For example, the ‘154
`
`and ‘747 Patents explain: “Furthermore, when microprocessor 36 detects subsequent
`
`increases or decreases in the desired pressure setpoint after the default constants have
`
`been replaced, the customized default constants may continue to be updated and
`
`replaced in step 114 to maintain the highest degree of accuracy when performing
`
`18
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 21
`
`
`
`
`
`pressure adjustments and to take into account changes in the user such as, for
`
`example, an increase or decrease in the weight of the user.” (‘154 Patent at 11:1-8;
`
`‘747 Patent at 10:39-47.) I confirmed in a discussion with Dr. Abraham that these
`
`parameters would change depending on the weight of the user. In this way, the
`
`inflate/deflate behavior of the ANM products is customized for a user’s weight – a
`
`capability made possible through the use of software-based control.
`
`19
`
`
`
`
`
`a/k/a Pegasus, FCS a/k/a Corolla (including the Performance FCS, Innovation FCS,
`
`& 2012/Current/Corolla Firmness Control System), Q10, ADAT, SleepIQ, and 360.
`
`34. The results of my analysis of Sleep Number’s source code are
`
`consistent with this information. My inspection found that the Sleep Number code
`
`included some code, the “Winland board documentation,” that contains programmer
`
`notes that document the dates of revisions (“Winland code”). The recorded revisions
`
`of the Winland code indicate that the code was developed prior to 2005, and many
`
`revisions are dated between 2001-2004. It appears to me that the Winland code was
`
`used in at least Sleep Number’s Pegasus pump (a/k/a the 5000/6000 series FCS)
`
`because (1) according to Exhibit 2058, Sleep Number began selling the Pegasus air
`
`controller in May 2004; (2) the Winland code includes software elements of the ‘172
`
`Patent and Sleep Number disclosed in Exhibit 2044 that the Pegasus pump practiced
`
`the ‘172 Patent; and (3) there was a document titled “Select Pegasus software matrix
`
`022205.xls” within the “Winland board documentation” folder structure. As
`
`mentioned above, the Winland code includes software elements of the ‘172 Patent.
`
`This code also implements what ANM refers to in Exhibit 2052 as a “Target
`
`pressure”/“Target system” controller, which ANM implemented in its air controllers
`
`starting in 2012 (see Exhibit 2052 at ANMI00133420), by which I mean that the
`
`user first sets a desired pressure, and then, without additional user input, the system
`
`adjusts the pressure to achieve that target pressure. Other than the Winland code, all
`
`20
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 23
`
`
`
`
`
`the other Sleep Number code provided
`
`for
`
`inspection,
`
`the “Logic
`
`PD\Base_5k_Realtime,” “Sleep Number,” and “Sleep Number & SleepIQ,” includes
`
`software elements of the ‘747 and ‘154 Patents in addition to the ‘172 Patent. This
`
`other Sleep Number code implements an improved “Target pressure”/“Target
`
`system” controller, which ANM implemented in its air controllers starting in 2014
`
`(see Exhibit 2052 at ANMI00133421–22), by which I mean that the controller uses
`
`an adjustment factor as taught in the ‘747 and ‘154 Patents. I am willing and able to
`
`further explain the operation of the Sleep Number code in detail and identify the
`
`specific portions of code that implement claim elements of the Patents-at-Issue if
`
`instructed to do so.
`
` ‘172 Patent Against ANM
`
`35.
`
`It is my opinion based upon the methodology described above and the
`
`inspections I have conducted that at least Version 1.8, Version 1.97, and Version 2.0
`
`of ANM’s source code implement the software elements of claims 2, 6, 12, 16, 20,
`
`22, and 24 of the ‘172 Patent, and at least Version 1.9 and Version 1.92 of ANM’s
`
`source code implement the software elements of claims 12 and 16 of the ‘172 Patent.
`
`Portions of these versions of source code demonstrate how to monitor pressure and
`
`provide commands during an inflate/deflate cycle as required by the claims of the
`
`‘172 Patent. Table 1 indicates the specific claim elements of the ‘172 Patent that are
`
`implemented in ANM’s source code. I am willing and able to further explain the
`
`21
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 24
`
`
`
`
`
`operation of the ANM source code in detail and identify the specific portions of code
`
`that implement claim elements of the ‘172 Patent if allowed to do so.
`
`36.
`
`It is also my opinion based upon the methodology described above and
`
`the inspections I have conducted that the Contentions, in Exhibit 2046 (on the ‘172
`
`Patent against ANM), accurately and specifically identify the source code files, lines,
`
`functions, and variables in ANM’s source code that read on the claims of the ‘172
`
`Patent. I understand that reference in the Contentions to the source code line
`
`numbers and variable and method names have been redacted and are not being
`
`provided to the Board at this time. I can attest that the redacted text specifically
`
`identifies the parts of the source code that implement each claim element listed. I am
`
`willing and able to further explain how each version of source code operates if
`
`allowed to do so.
`
`37.
`
`I have reviewed the Declaration of John Abraham (Exhibit 2027) that I
`
`understand is being submitted by Sleep Number contemporaneously with this
`
`declaration. I understand that Dr. Abraham opines that ANM’s products read on the
`
`claimed mechanical-related elements of (i.e. structural components of) the ‘172
`
`Patent. (See, e.g., Exhibit 2027, paragraphs 34-35.) I rely upon that opinion and do
`
`not provide any opinions on mechanical-related elements myself.
`
`38. Therefore, based upon my review of the ‘172 Patent’s claims and
`
`specification, the Declaration of John Abraham (and discussions with Dr. Abraham),
`
`22
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 25
`
`
`
`
`
`and the inspections I conducted of ANM’s source code using the methodology
`
`described above, it is my opinion that ANM’s products that use Version 1.8, Version
`
`1.9, Version 1.92, Version 1.97, and Version 2.0 of ANM’s source code (see Exhibit
`
`2052 at ANMI00133414, 21–22) can provide further evidence of practicing the
`
`claims of the ‘172 Patent that are identified in Sleep Number’s Contentions.
`
`39.
`
`It is also my opinion based upon the methodology described above and
`
`reviewing Sleep Number’s source code that ANM’s Version 1.8, Version 1.97, and
`
`Version 2.0 software is substantially similar to the inspected Sleep Number software
`
`that post-dates patent issuance with respect to the software-based control functions
`
`that are claimed in the ‘172 Patent. Further, it is my understanding based upon
`
`reviewing the Contentions (Exhibits 2044, 2046), SN_0021013–33 (Exhibit 2058),
`
`ANMI00133414–22 (Exhibit 2052), and Dr. Abraham’s Declaration (Exhibit 2027)
`
`that each of these versions of software were released after Sleep Number’s similar
`
`software had been put into products being offered for sale. I also understand from
`
`reviewing the Contentions (Exhibit 2046), SN_0021013–33 (Exhibit 2058),
`
`ANMI00133414–22 (Exhibit 2052), and Dr. Abraham’s Declaration (Exhibit 2027)
`
`that ANM’s air mattress systems and air controllers are similar to Sleep Number’s
`
`air mattress systems and air controllers in terms of the mechanical, i.e., structural,
`
`components.
`
`23
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 26
`
`
`
`
`
`40. Therefore, it is my opinion that the similarity between ANM’s and
`
`Sleep Number’s software (established by my analysis), the similarity between
`
`ANM’s and Sleep Number’s mechanical components (established by Dr. Abraham),
`
`and the release of the relevant ANM products after Sleep Number’s products are
`
`evidence that ANM copied the functionality claimed in the ‘172 Patent from the
`
`Sleep Number products.
`
` ‘154 and ‘747 Patents Against ANM
`
`41.
`
`It is my opinion based upon the methodology described above and the
`
`inspections I have conducted that at least Version 1.8, Version 1.97, and Version 2.0
`
`of ANM’s source code read on the software-related limitations of claims 1-19 of the
`
`‘154 Patent and claims 1-18 of the ‘747 Patent. The source code shows how the
`
`software receives a selection of a desired pressure setpoint, calculates a pressure
`
`target based upon the desired pressure setpoint and an adjustment factor, adjusts
`
`pressure within the air chamber of the air bed until a sensed pressure in a pump
`
`manifold is substantially equal to the pressure target, determines an actual pressure
`
`within the air chamber which is used to determine an adjustment factor error, and
`
`subsequently modifies the pressure adjustment factor based upon the adjustment
`
`factor error. Each version of the source code reads on other claimed elements,
`
`including but not limited to using an additive adjustment factor for inflation and a
`
`multiplicative adjustment factor for deflation, storing the modified/updated pressure
`
`24
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 27
`
`
`
`
`
`adjustment factor, and using the modified pressure adjustment factor to calculate a
`
`modified/updated pressure target that is used in a subsequent pressure adjustment. I
`
`prepared Table 2 and Table 3, which indicate the specific claim elements of the ‘154
`
`and ‘747 Patent that are implemented in ANM’s source code. I am willing and able
`
`to further explain the operation of the ANM source code in detail and identify the
`
`specific portions of code that implement claim elements of the ‘154 and ‘747 Patents
`
`if allowed to do so.
`
`42.
`
`It is also my opinion based upon the methodology described above and
`
`the inspections I have conducted that the Contentions, in Exhibit 2048 (on the ‘154
`
`Patent against ANM) and Exhibit 2049 (on the ‘747 Patent against ANM), accurately
`
`and specifically identify the source code files, lines, functions, and variables in
`
`Version 1.8, Version 1.97, and Version 2.0 of ANM’s source code that read on the
`
`claims of the ‘154 and ‘747 Patents. I understand that reference in the Contentions
`
`to the source code lines numbers and variable and method names have been redacted
`
`and are not being provided to the Board at this time. I can attest that the redacted
`
`text specifically identifies the parts of each version of the source code that implement
`
`each claim limitation, and I would be willing and able to further explain how each
`
`version of source code operates, if allowed to do so.
`
`43. As stated above, I have reviewed the Declaration of John Abraham
`
`(Exhibit 2027) that is being submitted by Sleep Number contemporaneously with
`
`25
`
`Sleep Number Corp.
`SUPPLEMENTAL EXHIBIT 2029
`IPR2019-00500
`Page 28
`
`
`
`
`
`this declaration. I understand that Dr. Abraham opines that the mechanical structures
`
`of ANM’s products read on the claimed mechanical-related elements of (i.e.
`
`