throbber
Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 1 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 1 of 20
`
`IN THE UNITED STATES DISTRICT COURT
`
`FOR THE WESTERN DISTRICT OF TEXAS
`
`WACODIVISION
`
`FLYPSI, INC. (D/B/A FLYP),
`
`Plaintiff,
`
`vs.
`
`GOOGLE LLC,
`
`Defendant.
`
`Civil Action No. 6:22-cv-31-ADA
`
`JURY TRIAL DEMANDED
`
`es
`
`
`
`BURNER, OBVIOUSNESS AND GOOGLE’S35 U.S.C.§112 ARGUMENTS
`
`FLYP’S MOTION FOR PARTIAL SUMMARY JUDGMENT CONCERNING
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 2 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 2 of 20
`
`TABLE OF CONTENTS
`
`T.
`
`ARGUMENT 0... eecccecccccceccceccesceescesceesceseeseeseesaeessesecaecsaeesecaecsseeseeeaeseaeeseeeaeesaeeeeeaeeeseeseeeaes 1
`
`A._The Asserted Patents are Not Anticipated nor Rendered Obvious by Burnet................. 1
`
`1.
`
`2.
`
`3.
`
`Burmer’s Operation ..............cccecceecceecceesceeseeeseceseeesseceseeesaecesceeeeeeseeeaeceaeeeseeeeseeesseeeeeees 2
`
`Outbound Patents ............ cee cee ceecceceeeccesseceseecsaeeesceesseceseeceseceseeseseeeseeceaeeeseeeeseeeseeeeseees 2
`
`Inbound Patents 22.0.2... ....ceecccecceecceecceesccesceeeeceseecsaecesceesaeceseceseeceseeeeeceaecesseeeeeeseeeeseees 5
`
`B.
`
`Google Has NotIdentified Any Motivation to Combine.....................:cccccceeeeeeseeeeeeeeeeees 7
`
`Google Has Not Shown that a POSITA Would be Motivated to Modify Any Single
`C.
`Reference to Render the Asserted Patents ODVIOUS...................:ccccesceeceeseeeseeeeceseeeseeeeeseenseeneeeaes 9
`
`There is No Dispute of Material Fact that the Asserted Patents Possess Adequate
`D.
`Written Description and Enablement.................0...cccecceeccesceeeceeeseeeseeceseeeseeceseeeseeceseeeseeeeseeesees 10
`
`TT. CONCLUSION.00..eececccccececccescceseesceeseeseeeeeseesseseesseseeesecaeesseeseeeseeeseseeaeeseeeeeeseenseeseeeseess 14
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 3 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 3 of 20
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`CASES
`
`ALZA Corp. v. Andrx Pharm., LLC,
`603 F.3d 935 (Fed. Cir. 2010)... cccccccecccccesccescceseeeseeesscesecessecesecesseceseceseeceseeesseenseeesseeess 11
`
`Andersonv. Liberty Lobby, Inc.,
`ATT U.S. 242 (1986)... ccccccccccccccecccceseceseeesseeesecesseesecessecsecessecesecessecesseesseeeseeesaeeeseeeseceeseeesaes 1
`
`Ariad Pharms., Inc. v. Eli Lilly & Co.,
`598 F.3d 1336 (Fed. Cir. 2010). 2.0... ..ccccecccccccesccescceeseeeseeeeseeeseeesecesseesseceseeeesecesseesseeeseeeees 11
`
`Celotex Corp. v. Catrett,
`ATT U.S. 317 (1986)... ccccccecccccecceseccsseceseeesseceseeesseeesecessecesecessecseeesseceaeeeseecesecesseeeseeeseeeeseeesees 1
`
`Eli Lilly and Co. v. Zenith Goldline Pharmaceuticals, Inc.,
`471 F.3d 1369 (Fed. Cir. 2006).........00ccccccccccccccesceeseeeesecesecessecesecesseceseeeseeceseeeeeceseeesecesseeesees 7
`
`Forest Laboratories, LLC v. SigmapharmLaboratories, LLC,
`918 F.3d 928 (Fed. Cir. 2019).......0cccccccccecccccescceeseceseeeeseceseecacceseeesseeeseeseseeeseeceseeesesenseeesees 7
`
`SIBIA Neurosciences, Inc. v. Cadus Pharm. Corp.,
`225 F.3d 1349 (Fed. Cir. 2000)... ...0cccccccccccecccescceesseceesseceessceesssecesseceesseecesseecesseseesseeees 9,10
`
`Smiths Indus. Med. Sys., Inc. v. Vital Signs, Inc.,
`183 F.3d 1347 (Fed. Cir. 1999)... occ ccccccccccccccsceesccesseeesseesscesecessecesecesseeesecesseeesesesseeeeeenaee 7
`
`Tec Air, Inc. v. Denso Mfg. MichiganInc.,
`192 F.3d 1353, 52 U.S.P.Q.2d 1294 (Fed. Cir. 1999) .......cccccccecceccceseeseceseeeeeeseeeseenseeeeesees 8
`
`VLSI Tech. LLC v. Intel Corp.,
`2021 WL 2773013 (W.D. Tex. Apr. 12, 2021).......0ccccccceccecccecceecceseceseeseteseeeeeseseaeenseeseeesees 1
`
`STATUTES
`
`35 U.S.C. § VQ ooeccccccccccccccescescceseeseeesecseesscsecseeesecsecsaescsecssecsasesecsaeessesseceseceatesseeseesseeeeeaeesaseesaes 1
`
`OTHER AUTHORITIES
`
`Fed. R. Civ. P. 56(a) ......cecccccccccccceccceescceseeeseeceseecseecsecesaeceseecsseceseecsaeeeseeceaeeeseeceseeeeeeeseesseeesseeeseeenes 1
`
`i
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 4 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 4 of 20
`
`TABLE OF EXHIBITS!
`
`No.
`
`Brief Description
`
`AdHoc_000104
`
`AdHoc_000054
`
`Expert Report of Dr. Oded Gottesman on Invalidity (dated September 12, 2023)
`
` 12
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`AdHoc000097
`
`AdHoc_000114
`
`AdHoc_000106
`
`U.S. Patent No. 9,332,128 (“Backhaus”)
`
`AdHoc_000018
`
`GOOG-FLYP-PA-00004636
`
`Deposition Transcript ofFo (dated August 15, 2023)
`
`Deposition Transcript of Oded Gottesman, Day 2 (dated October 31, 2023)
`
`Claim Construction Hearing Transcript (dated November 22, 2022)
`
`' The undersigned herebystates that true and correctcopies of the exhibits noted here are attached
`to this Motion.
`
`ill
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 5 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 5 of 20
`
`One of the two primary references advanced by Google—the Bumer phone system
`
`(“Burmer”’)—fails to invalidate the Asserted Patents under any standard of proof, muchless a clear
`
`and convincing one. Flyp is thus entitled to summary judgementas to validity over the Burner
`
`phonesystem. In addition, for all proposed obviousness combinations, Google has failed to show
`
`sufficient motivation to combine any reference with any other reference. And for single reference
`
`obviousness, Google has not shown sufficient motivation for a person of ordinary skill in the art
`
`(“POSITA”) to modify any single reference. Finally, Google’s arguments for invalidity under 35
`
`U.S.C. § 112 either attempt to advance arguments that this Court rejected during claim construction
`
`or its expert disavowed during his deposition.
`
`As the Court is familiar with general summary judgment standards and related legal
`
`precedents, Flyp will refrain from reciting them here. See VLSI Tech. LLC v. Intel Corp., Case
`
`No. 6:21-CV-299-ADA, 2021 WL 2773013 at *2 (W.D. Tex. Apr. 12, 2021) (citing, interalia,
`
`Fed. R. Civ. Pro. 56(a), Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 248 (1986), and Celotex
`
`Corp. v. Catrett, 477 U.S. 317, 322-23 (1986)). Rather, Flyp will focus on the legal precedents
`
`specific to this Motion.
`
`L
`
`ARGUMENT
`
`A.
`
`The Asserted Patents are Not Anticipated nor Rendered Obvious by Burner
`
`The Asserted Patents are neither anticipated nor rendered obvious by the Burner system.
`
`Google’s expert, Dr. Gottesman, bases his conclusion that Burner invalidates the asserted claims
`
`on a severe misunderstanding of Burner.
`
`In the ’094, ’554, and ’585 Patents (the “Outbound
`
`Patents”), Google can poit to no analog in Burnerto the claim elements “bridge or access
`
`telephone number.” Additionally, nowhere does Google produce any evidence—in Dr.
`
`Gottesman’s report, in his testimony, or otherwise—that Burnerpracticed a server associated with
`
`a switch that (1) stores an association of primary and secondary number, (2) stores an association
`
`1
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 6 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 6 of 20
`
`of a bridge or access number with a secondary number, or (3) stores an association ofa pair primary
`
`numberand bridge number with a pair of secondary number and contact number.
`
`Similarly, the °770 and °105 Patents (the “Inbound Patents”) require that the pre-call
`
`information be transmitted over the data channel to the handset, but the BurnerPo
`
`1.
`
`Burner’s Operation
`
`Ad Hoc Labsreleased the Burnerapplication on August 8, 2012. Ex. 1, AdHoc000104.
`
`In its initial press release, the company described the application as one that “issues disposable
`
`phone numbersat the touch of a button.” Jd. Ad Hoc Labs’ CEO, Greg Cohn, explained that the
`
`application was targeted to those who value their privacy. Jd. The Burnerapplication allowed
`
`users to provision temporary numbers that they could use for phone calls and text messages and
`
`then “burn” when they were ready to deactivate the number. Jd. These temporary numbers are
`
`referred to as “Burner Numbers.” See id. According to the press release, for outgoing calls, the
`
`user’s Burner Number would showasthe caller ID whena userplaced the call. See id.; see also
`
`ee
`
`2.
`
`Outbound Patents
`
`Google fundamentally misunderstands Burner,
`
`the patent claims, or both, when it
`
`incorrectly applies the term “proxy calling”in relation to the OutboundPatents.
`
`In Dr. Gottesman’s opening report, he opines that Ad Hochl
`RE©. 3, oresRep. at $113(iting Bx. 4
`
`AdHoc_000097at 98). However, this cannot be the case, and the same evidencethat he cites for
`
`this proposition makes that clear. The email Dr. Gottesman cites describes a conference-calling
`
`2
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 7 of 20
`
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 7 of 20
`
`Ex. 4 at 98.
`
`In this conference-calling approach, a userwould
`
`The Bummer conference calling solution is distinct from the invention claimed in the
`
`Outbound Patents. The ’094 Patentis illustrative. The ’094 Patent recites four distinct telephone
`
`numbers: primary telephone numbers (e.g., the carrier-assigned handset number); secondary
`
`telephone numbers(e.g., the Google Voice number, or analogously, the “Burner” number); bridge
`
`or access telephone numbers (e.g., the proxy number or shadow numberin Google Voice); and
`
`contact telephone numbers(i.e., the intended destination for the outgoing call). See ’094 Patent at
`
`claim 1; see also ’554 Patent at claim 1 (reciting the same elements).
`
`These numbers perform specific and distinct roles in the claimed invention. For instance,
`
`in the asserted independent claims from both Outbound Patents, the primary and secondary
`
`numbers must be associated with the handset, while it is the bridge or access telephone number
`
`(i.e., the proxy number) that must receive the outgoing call from the mobile device. See ’094
`
`Patent at claim 1 (“receiving, at a switch associated with the server, an outgoing call from the
`
`3
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 8 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 8 of 20
`
`handset to the bridge or access telephone number via a second channel”); see also °554 Patent at
`
`claim | (“receiving, at the switch associated with the server, an outgoing call from the mobile
`
`device to the access telephone number via a second channel”).
`
`In his deposition, Dr. Gottesman identifiedTe
`
`I 1. otesion iceniica
`
`ee). However, he was unable to point to any other
`
`component of Burner that would serve as the bridge or access telephone numberother than the
`
`Burner numberagain. See id. at 314:25-318:25. When pressed, he stated thai
`
`Dr. Gottesman could not point to an example of bridge telephone number from Bummerfor
`
`the simple fact that the Burner conference calling solution has no analog to the bridge or access
`
`ae). This mostclosely aligns to the secondary telephone numberin the claims. See,
`
`e.g., 094 claim 1 (“identify a telephone numberfrom whichthe outgoingcall is being madeas the
`
`secondary telephone number”). Accordingly, in the Duneit
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 9 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 9 of 20
`
`ee
`
`ee
`es
`
`Separately and independently, Google has produced no evidence regarding the backend
`
`structure of Bumer. Google has offered no evidence regarding a “switch” in Burner. Also absent
`
`is any evidence regarding a server associated with such a switch that (1) stores an association of
`
`primary and secondary number, (2) stores an association of a bridge or access number with a
`
`secondary number, or (3) stores an association of a pair primary numberand bridge numberwith
`
`a pair of secondary numberand contact number.
`
`Therefore, there is no genuine dispute of material fact as to whether Burner discloses a
`
`bridge or access telephone number. Accordingly, on either of these bases, Flyp is entitled to
`
`summary judgmentof validity of the Outbound patents over Burner.
`
`3.
`
`InboundPatents
`
`Further, Burner’sPo does not anticipate the asserted claims in the
`
`Inbound Patents because it omits the recited pre-call information and accordingly routes the call
`
`in a distinct way. The ’770 Patentis illustrative. Independent claim 1 from the ’770 Patent requires
`
`“transmitting pre-call information to the handset overthe at least one data channel,” with the pre-
`
`call information including the bridge telephone numberand the handset-associated telephone
`
`number, such that the handset is “capable of displaying the handset-associated telephone number
`
`to a user and, based on user input, accepting the incoming call by connecting with the switch over
`
`the at least one voice channel using the bridge telephone number.”
`
`Whereas the claims require that the pre-call information transmitted over the data channel
`
`includesa bridge telephone numberthat the handset can use to connect with the switch, the Burner
`
`5
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 10 of 20
`
`ee. Thus, while the claims require sending a bridge
`
`telephone numberovera data channel that makes the handset capable of connecting with the server
`
`Exhibit 5 (AdHoc_000114) is an April 2013 email fromP| confirming that a
`
`6 2:01s:
`
`a T
`
`his further confirms that Burner was not using the inventions described in the InboundPatents.
`
`8 6 (2500000106) is
`November2015 email fomi. Onthis chain is another November2015 email from
`contr
`
`
`
`Nowhere has Google produced any evidence to the contrary on this point. Consequently,
`
`Flyp is entitled to summary judgment onthe validity of the Inbound Patents over Burner.
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 11 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 11 of 20
`
`B.
`
`Google Has Not Identified Any Motivation to Combine
`
`Google has only produced the most conclusory evidence that any motivation to combine
`
`existed. The only evidence Google could muster is Dr. Gottesman’s opinionin his report that it is
`
`the “natural evolution of systems is to integrate more and more networks, in order to offer more
`
`versatile features and seamless overall internetwork solutions, especially when there are already
`
`pre-existing standards and competitive markets. Such a natural progression provides a POSITA
`
`with further motivation to combine the prior art GV and the systems disclosed in Backhaus and
`
`Saksena. Therefore POSITA [sic] would be motivated and would find it trivial and obvious to
`
`combine them.” Gottesman Rep. at §§ 103-04. This contravenes the law for two reasons and
`
`ignores the facts for two other reasons.
`
`First, this is not the proper legal inquiry. “An invention is not obvious simply becauseall
`
`of the claimed limitations were known in the priorart at the tume of the invention. Instead, we ask
`
`‘whetherthere is a reason, suggestion, or motivation in the priorart that would lead one of ordinary
`
`skill in the art to combine the references, and that would also suggest a reasonable likelihood of
`
`success.’” Forest Laby’s, LLC v. Sigmapharm Laby’s, LLC, 918 F.3d 928, 934 (Fed. Cir. 2019)
`
`(citing and quoting Smiths Indus. Med. Sys., Inc. v. Vital Signs, Inc., 183 F.3d 1347, 1356 (Fed.
`
`Cir. 1999)). And the inquiry also requires an accused infringer to show why a POSITA would
`
`select specific references and combine those together. See Eli Lilly and Co. v. Zenith Goldline
`
`Pharms., Inc., 471 F.3d 1369, 1379, (Fed. Cir. 2006) (“the law requires a motivation to select the
`
`references and to combine them in the particular claimed mannerto reach the claimed invention.”).
`
`Dr. Gottesman does not specifically identify why a POSITA would be motivated to combine
`
`Burneror prior art Google Voice with any of the other referenceshelisted.
`
`Second, allowing Google to argue that a motivation to combine exists becauseit is the
`
`“natural evolution” of telephony systems to include more systems and more features would
`
`7
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 12 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 12 of 20
`
`swallow the law and be a holding that a motivation to combine a/waysexists in this technical field.
`
`Google has offered no legal authority on that position, nor offered any testimony from its fact
`
`witnesses that this could even betrue.
`
`Additional facts show that such a motivation to combine wasa factual impossibility. For
`
`instance, asa tic! facta ar,a
`
`at (65). If it was not actually available to a POSITAasofthe priority date of the patent, it would
`
`not as a practical matter be on the “table” of prior art references for a POSITA to choose from
`
`whendeciding whichpriorart references to combine together. Therefore, as a practical and factual
`
`matter, a POSITA could not have been motivated to combinePY Also
`for this same reason, a POSITA would not have been motivated to combineii
`a.
`
`Further, Burner taught away from such a combination. The point of Burnerwasthat the
`
`numbers it created were meant to beee
`GE.. See Ex. 8 AdHoc000018 at 24Gs
`DEES20.0000:
`ES 9. c006-Fv"-
`
`PA-00004636 at 4638 (“““The person who has burmedthe numberis not reachable on that number,’
`
`Cohn added. ‘We think ofit as a temporary social network. You’re just giving them a path to you
`
`that works for nght now. When you burn that number, that path dissolves. As well, we wipe the
`
`history from your phone.’”; id. at 4637 (“Get a burner numbervalid for 7 days or 20 talk minutes
`
`or 60 texts”). References that teach away cannot be combined. See Tec Air, Inc. v. Denso Mfg.
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 13 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 13 of 20
`
`MichiganInc., 192 F.3d 1353, 1360, 52 U.S.P.Q.2d 1294 (Fed. Cir. 1999) (citations omitted—
`
`affirming jury verdict that patent was not invalid and denial of JMOL of invalidity because jury
`
`could reasonably have foundthat prior art patent that taught placing adjustable screwsin the non-
`
`cavity side of a mold taught away from the claimed invention of placing the screws in the cavity
`
`side ofthe mold as the conventional wisdomasofthe application filing date was that screws placed
`
`in the cavity side of the mold would inevitably fill up with plastic and be moperative for their
`
`intended purpose).
`
`Accordingly, Flyp is entitled to summary judgmentthat Google has not demonstrated any
`
`motivation to combine any reference with any other.
`
`Google Has Not Shown that a POSITA Would be Motivated to Modify Any
`Cc.
`Single Reference to Render the Asserted Patents Obvious
`
`Google offers insufficient evidence or explanation as to how or why a POSITA would be
`
`motivated to modify the teachings of either Google Voice or Bummerto render the Asserted Claims
`
`obvious overeither one of those references individually. While “[i]n appropriate circumstances,
`
`a single prior art reference can render a claim obvious,” there must however “be a showing of a
`
`suggestion or motivation to modify the teachings of that reference to the claimed invention in order
`
`to support the obviousness conclusion.” SJBIA Neurosciences, Inc. v. Cadus Pharm. Corp., 225
`
`F.3d 1349, 1356 (Fed. Cir. 2000) (emphasis added).
`
`Google has not offered any evidenceas to this motivation to modify the teachings of either
`
`Google Voice or Burner except Dr. Gottesman’s expert report and testimony. In his expert report,
`
`Dr. Gottesman relies on only vague and conclusory statements such as stating that it would be
`
`ee
`ee
`GRE” Gottesman Opening Rep.at #¥ 196, 200, 205.
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 14 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 14 of 20
`
`For example, Dr. Gottesmanstatesthat:
`
`
`
`Id. at 205.
`
`This conclusory appeal to “common sense” has been explicitly rejected by the Federal
`
`Cireuit. See, e.g., SIBIA, 225 F.3d at 1356 (reversing a finding of unpatentability for obviousness
`
`because the Board erred in relying on “common sense” to supply a claim limitation that was
`
`missing from the oneprior art reference relied on to show obviousness).
`
`Further, even if this explanation were adequate,
`
`it
`
`is unsupported except by Dr.
`
`Gottesman’s ipse dixit testimony. Google’s own corporate designee contradicts Dr. Gottesman.
`
`Modifying the purported prior-art Google Voice in the manner Dr. Gottesman suggests would have
`
`been unduly complex and would not have had a reasonable expectation of success. At the relevant
`
`5,
`PE. See, c.c., Ex. 10,J Dep.Tr. at 34:21-363
`ee
`eee
`ee. Consequently, Google has not
`
`shown the requisite suggestion or motivation to modify either single reference, and Flyp is entitled
`
`to summary judgmentonthis issue.
`
`There is No Dispute of Material Fact that the Asserted Patents Possess
`D.
`Adequate Written Description and Enablement
`
`The Asserted Patents have adequate written description because the specification
`
`reasonably conveys “to those skilled in the art that the inventor had possession of the claimed
`
`10
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 15 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 15 of 20
`
`invention as ofthe filling date.” Ariad Pharms., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed.
`
`Cir. 2010). Further, the specification is enabling becauseit teaches “those in the art to make and
`
`use the full scope of the claimed invention without undue experimentation.” ALZA Corp. v. Andrx
`
`Pharm., LLC, 603 F.3d 935, 940 (Fed. Cir. 2010). There is no dispute of material fact on this issue
`
`because Google’s invalidity expert, Dr. Gottesman, admitted in his deposition that he wasable to
`
`understand,in light of the specification, each of the claim terms Google contends is invalid under
`
`section 112.
`
`Google contends that four sets of terms are invalid due to a lack of written description
`
`and/or enablement. First, Google argues that the claim terms “primary” and “secondary”telephone
`
`numbersare invalid under section 112. In his opening report on invalidity, Dr. Gottesman opines
`
`that “[a]ny two numbers within a phone handset or a phoneservice can be picked and labeled
`
`primary or secondary numbers. The specification provides no clear guidance to a POSITAasto
`
`what characterizes such numbers as being primary or secondary, and what would distinguish
`
`them.” Gottesman Inv. Rep. at para. 231. However, in Dr. Gottesman’s deposition, when asked
`
`how he applied the term “primary” telephone number in his invalidity report, the following
`
`exchangetookplace:
`
`Q. What about primary telephone number, how have you applied
`that in your invalidity analysis?
`
`A. The primary telephone numberis used basically in the patent
`primarily to associate certain elements in the database.- And I
`believe, you know,that a telephone number such as a SIM telephone
`numberthat is described in the claim in the specification is such a
`telephone number.
`
`Ex. 9, Gottesman Oct. 31 Dep. at 279:14-23.
`
`When describing Burner, Dr. Gottesman also stated he had no difficulty understanding the terms
`
`“primary” and “secondary telephone number”in light of the patent and the specific system at issue:
`
`11
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 16 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 16 of 20
`
`Id. at 314:11-19.
`
`Not only does Dr. Gottesman admit that he understands the term “primary telephone
`
`number”in light of the specification and by virtue ofits relationship to the system and whatset of
`
`tules applies to it, but this is exactly the understanding that Dr. Conte opines upon in his report.
`
`See Conte Rep. at para. 76 (“The specification and claims do not use the words “primary” and
`
`“secondary” in a subjective sense, but rather to distinguish between two telephone numbers that
`
`follow a specific set of rules.”). Further, Google’s argument regarding these terms is simply
`
`patroting its failed claim construction argument regarding indefiniteness of the same terms, which
`
`this Court rejected. See Ex. 12, Nov. 22, 2022 MarkmanTr. at 5-6, 8, 13 (Google arguing that the
`
`terms are indefinite, and the Court rejecting that argument, stating “This isn’t a tiny little thing in
`
`something like I usually get, where it’s, you know,[. .
`
`.] wherein the node will do X, and you don’t
`
`know maybewhich nodeitis. I get that. But this is theje ne sais quoi ofthe patent.” (emphasis added)).
`
`Second, Dr. Gottesman admitted that a POSITA would have been familiar with VoIP at
`
`the time the patents werefiled:
`
`Q. Wediscussed quite a bit today VoIP, and I believe I understand
`your opinion to be that well before the earliest prior dates of these
`patents VoIP was well known in theart; is that fair?
`
`A. Yes.
`
`Ex. 11, Gottesman Oct. 31 Dep. Tr. at 497:5-10.
`
`12
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 17 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 17 of 20
`
`Third, Dr. Gottesman admitted that a voice channel and a data channel may be transmitted
`
`overIP.
`
`Q. And the question I'm asking youis: In paragraph 151, right in
`the middle of paragraph 150 where you're talking about
`the
`specification and the rest of paragraph 151, where you're talking
`about the understandings you're going to adopt in the report, you
`say, “Both voice channel and data channel may be using IP, so IP is
`not a useful way to distinguish between them.” Do youagree with
`that statement or disagree? That's all I'm asking.
`
`in
`A. Generally speaking — generally speaking, voice channel
`general and data channel in general may be transmitted in general
`over IP. And whenthey are transmitted over IP, they are transmitted
`in the same way.
`
`Id. at 434:19-435:9.
`
`Fourth andfinally, the Asserted Patents possess adequate written description for the terms
`
`“switch” and “server,” including as those terms relate to VoIP in the patent. Dr. Gottesman admits
`
`that a POSITA would have understood how the term “switch” operated with regards to VoIP in
`
`2013:
`
`Q.Is it correct that a person ofordinary skill in the art in 2013 would
`have known about these VoIP software switches?
`
`A. Yes.
`
`Td. at 283:22-25.
`
`He likewise admits that it could have run on a server:
`
`Q. Could it run on a server, for instance?
`
`A. Yes.
`
`Id. at 286:15-17.
`
`Therefore, there is no dispute of material fact regarding whether the Asserted Patents
`
`possess adequate written description and enablement for each of these terms. Alternatively, Flyp
`
`is concurrently moving to strike Dr. Gottesman’s opinions and testimony regarding written
`
`13
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 18 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 18 of 20
`
`description and enablementin a separately filed Motion to Strike. If such motionis granted, then
`
`no dispute of material fact exists because Google has produced no other evidencein its favor.
`
`Therefore, under either basis, Flyp is entitled to summary judgmenton this issue in its favor.
`
`I.
`
`CONCLUSION
`
`For the reasons stated above,there is no dispute of material fact regarding: (1) the Asserted
`
`Claim’s validity over Burner; (2) that there is no motivation to combine any of the references
`
`Google relies upon; (3) there is no adequate motivation to modify any single reference to render
`
`obvious the Asserted Claims; and (4) that the Asserted Patents possess adequate written description
`
`and enablement under 35 U.S.C. §112. Therefore, Flyp respectfully requests summary judgment
`
`in its favor on these issues.
`
`14
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 19 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 19 of 20
`
`DATED: November 14, 2023
`
`Respectfully submitted,
`
`/s/ Thomas M. Melsheimer
`Thomas M. Melsheimer
`
`Texas Bar No. 13922550
`tmelsheimer@winston.com
`M.Brett Johnson
`
`Texas Bar No. 00790975
`mbjohnson@winston.com
`Michael A. Bittner
`Texas Bar No. 24064905
`mbittner@winston.com
`C. Charles Liu
`Texas Bar No. 24100410
`ccliu@winston.com
`Steven R. Laxton
`
`Texas Bar No. 24120639
`slaxton@winston.com
`WINSTON & STRAWN LLP
`2121 North Pearl Street, Suite 900
`Dallas, TX 75201
`Telephone: (214) 453-6500
`
`Matthew R. McCullough
`California Bar No. 301330
`mrecullough@winston.com
`WINSTON & STRAWN LLP
`275 Middlefield Road, Suite 205
`Menlo Park, CA 94025
`Telephone: (650) 858-6500
`
`William M. Logan
`Texas Bar No. 24106214
`wlogan@winston.com
`Evan D. Lewis
`Texas Bar No. 24116670
`edlewis@winston.com
`WINSTON & STRAWN LLP
`800 Capitol Street, Suite 2400
`Houston, TX 77002
`Telephone: (713) 651-2766
`
`ATTORNEYS FOR PLAINTIFF
`
`15
`
`

`

`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 20 of 20
`Case 6:22-cv-00031-ADA Document 165 Filed 11/21/23 Page 20 of 20
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on November 14, 2023, a true and correct copy of the foregoing
`documentwasfiled electronically with the Clerk of Court using the CM/ECFsystem. As ofthis
`date, all counsel of record have consented to electronic service and are being served with a copy
`of this document through the Court’s CM/ECF system and by email. Administrative Policies and
`Procedures for Electronic Filing in Civil and Criminal Cases, Western District of Texas,
`Section 14.
`
`/s/ Michael A. Bittner
`Michael A. Bittner
`
`16
`
`

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