throbber
Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 1 of 19
`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 1 of 19
`
`
`
`UNITED STATESDISTRICT COURT
`SOUTHERN DISTRICT OF NEW YORK
`
`NETWORK-1 TECHNOLOGIES, INC.,
`
`Plaintiff,
`
`Vv.
`
`GOOGLELLC and YOUTUBE,LLC,
`
`
`
`Defendants.
`
`14 Civ. 2396 (PGG-SN)
`
`14 Civ. 9558 (PGG-SN)
`
`PLAINTIFF NETWORK-1 TECHNOLOGIES,INC.’S
`OBJECTIONS TO THE MAGISTRATE’S ORDER STRIKING PORTIONSOF ITS
`
`EXPERT’S SUPPLEMENTAL EXPERT REPORT
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 2 of 19
`
`
`TABLE OF CONTENTS
`
`I.
`INTRODUCTION .............................................................................................................. 1
`II.
`FACTUAL BACKGROUND ............................................................................................. 2
`A. Overview of Asserted Patents, Accused Products, and Google’s Initial Damages Theories
`Concerning Purported Non-Infringing Alternatives ................................................................... 2
`B. Google’s Unilateral Late Disclosure of New Contentions Related to Non-Infringing
`Alternatives Necessitated Supplemental Discovery ................................................................... 3
`C. Network-1’s Supplemental Expert Reports and Google’s Motion to Strike ...................... 5
`D. The Magistrate Judge Grants Google’s Motion to Strike ................................................... 6
`III.
`ARGUMENT ...................................................................................................................... 7
`A. The Magistrate’s Order Is Clearly Erroneous Because It Is Based on a False Factual
`Predicate ...................................................................................................................................... 7
`B. The Finding in the Magistrate’s Order that Google Is “Unduly Prejudiced” by Dr.
`Clearly Erroneous ....................................................................................................................... 9
`C. The Magistrate’s Order Is Clearly Erroneous Because It Fails to Recognize that Network-
`2021 Supplemental Discovery .................................................................................................. 10
`D. The Magistrate’s Order Is Clearly Erroneous Because It Fails to Recognize that the ’216
`Patent Analysis Relies on the Supplemental Discovery ........................................................... 13
`E. The Magistrate’s Order is Clearly Erroneous Because It Reflects a Cursory Ruling on a
`Complex Issue Via a Cursory Procedure .................................................................................. 14
`IV.
`CONCLUSION ................................................................................................................. 15
`
`Mitzenmacher’s Analysis Concerning the ’216 Patent in his Supplemental Expert Report Is
`
`1’s Expert Could Not Have Presented the ’216 Patent Analysis Prior to Receiving Google’s
`
`
`
`i
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 3 of 19
`
`
`TABLE OF AUTHORITIES
`
`Cases
`Largan Precision Co. v. Samsung Elecs. Co.,
`No. 13-cv-2740, 2015 WL 11251758 (S.D. Cal. Nov. 20, 2015) ............................................... 5
`NTP, Inc. v. Research in Motion,
`418 F.3d 1282 (Fed. Cir. 2005)............................................................................... 11, 12, 13, 14
`Smart Skins LLC v. Microsoft Corp.,
`No. 15-cv-544, 2016 WL4148091 (W.D. Wash. July 1, 2016) ................................................ 11
`SPEX Techs. v. Apricorn, Inc.,
`No. 16-cv-07349, 2020 WL 1289546 (C.D. Cal. Jan. 21, 2020) .............................................. 11
`Velocity Patent LLC v. FCA US LLC,
`319 F. Supp. 3d 950 (N.D. Ill. 2018) ........................................................................................ 11
`WhereverTV, Inc. v. Comcast Cable Commc’ns, LLC,
`No. 18-cv-529, 2022 WL 2751752 (M.D. Fla. July 14, 2022) ................................................. 11
`Rules
`Federal Rule of Civil Procedure 26(a)(1) ................................................................................... 6, 9
`Federal Rule of Civil Procedure 72(a) ............................................................................................ 1
`
`ii
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 4 of 19
`
`
`I.
`
`INTRODUCTION
`
`Pursuant to Federal Rule of Civil Procedure 72(a), Plaintiff Network-1 Technologies, Inc.
`
`objects to Dkt. No. 2831 (“Magistrate’s Order”) granting a motion to strike brought by Defendants
`
`Google LLC and YouTube LLC (collectively, “Google”). The Magistrate’s Order strikes portions
`
`of Network-1’s supplemental expert report addressing one reason why the late-proposed non-
`
`infringing alternative that Google was allowed to introduce through the supplemental discovery
`
`authorized by the Magistrate is not viable—because it would have infringed another, non-asserted
`
`Network-1 patent, U.S. Patent No. 9,538,216 (“the ’216 patent”). To avoid any confusion on this
`
`point, Network-1 is not attempting to assert the ’216 patent against Google via this supplemental
`
`report and is not seeking damages for infringement of this patent in the presently pending cases;
`
`rather, infringement of the ’216 patent by Google’s proposed alternative is simply one of many
`
`reasons why the alternative that was the subject of the supplemental discovery is not a viable non-
`
`infringing alternative to products that infringe the asserted patents. Network-1 also notes that
`
`neither the Magistrate’s Order, nor this Objection, bear on the parties’ pending motions for
`
`summary judgment, which are fully briefed.
`
`Network-1 respectfully requests this Court overrule the Magistrate’s Order in its entirety.
`
`First, the Magistrate Judge clearly erred in granting Google’s motion to strike Dr.
`
`Mitzenmacher’s analysis concerning the ’216 patent because the primary factual predicate
`
`underlying the order (that the ’216 patent was not disclosed prior to the close of the supplemental
`
`fact discovery period) is false. Rather, Google’s own expert analyzed multiple documents
`
`disclosing the ’216 patent in his initial expert report. The Magistrate’s Order should be set aside
`
`in its entirety on this basis alone.
`
`
`1 Citations to the docket are to the docket of Case No. 14 Civ. 2396 (PGG-SN).
`
`1
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 5 of 19
`
`
`The Magistrate Judge also clearly erred by finding that Google would be unduly prejudiced
`
`if the motion to strike were not granted; this finding was based on the same false factual predicate,
`
`and in any event, Google would not be prejudiced if Dr. Mitzenmacher’s analysis were not struck
`
`because its expert had ample time to respond to it.
`
`In addition, the Magistrate Judge clearly erred in striking Dr. Mitzenmacher’s ’216 patent
`
`analysis by not recognizing that (a) he could not have presented his opinions concerning the ’216
`
`patent in his initial report because he needed information disclosed in the supplemental discovery
`
`period in order to do that under the governing law, and (b) his ’216 patent analysis thus did indeed
`
`rely on information only disclosed during the supplemental discovery period.
`
`Finally, the Magistrate Judge clearly erred by deciding these complex issues via an
`
`abbreviated letter briefing process, which caused confusion of the issues and prejudiced Network-
`
`1 because it did not have ample opportunity to fully present the facts and law underlying the motion
`
`to the Court. If Google wishes to raise this issue, it needs to be addressed with full briefing, for
`
`example, at the in limine stage, as this is when Network-1 will seek to exclude Google’s late-
`
`disclosed non-infringing alternative contentions, which necessitated supplemental discovery and
`
`the portions of the supplemental expert report that Google now seeks to strike in the first place.
`
`II.
`
`FACTUAL BACKGROUND
`
`A.
`
`Overview of Asserted Patents, Accused Products, and Google’s Initial
`Damages Theories Concerning Purported Non-Infringing Alternatives
`
`A brief overview of the patents and technology involved is useful to understand the instant
`
`dispute. In the presently pending cases, Network-1 has asserted three patents against Google’s
`
`Content ID systems. As noted above, this does not include the ’216 patent. For purposes of
`
`understanding this dispute, claim 33 of U.S. Patent No. 8,205,237 (“the ’237 patent”) can serve as
`
`a representative patent claim:
`
`2
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 6 of 19
`
`
`33. A computer-implemented method comprising:
`a) obtaining, by a computer system including at least one computer, media
`work extracted features that were extracted from a media work, the media
`work uploaded from a client device;
`b) determining, by the computer system, an identification of the media work
`using the media work extracted features to perform a sublinear approximate
`nearest neighbor search of reference extracted features of reference
`identified media works; and
`c) determining, by the computer system, an action based on the determined
`identification of the media work.
`
`Dkt. No. 2 at 67. Like claim 33, all of the asserted claims are method, rather than system, claims.
`
`At a high level, Network-1 accuses two versions of Google’s Content ID systems (LSH and
`
`Siberia) of infringing the asserted patents, for example, mapping Content ID’s “fingerprinting” to
`
`claim element 33(a), Content ID’s “matching” or “Match System” to claim element 33(b), and
`
`Content ID’s “claiming” to element 33(c).
`
`
`
`During the initial fact discovery period, Google contended that damages for its
`
`infringement of Network-1’s patents should be limited in light of thirteen purported non-infringing
`
`alternatives that it listed in an interrogatory response. See Dkt. No. 268-5 at 20-23. Network-1’s
`
`technical expert Dr. Mitzenmacher addressed these enumerated alleged alternatives in his initial
`
`December 20, 2019 expert report. See Dkt. No. 226-6 ¶¶501-519. The instant discovery dispute
`
`involves just the first of these alleged non-infringing alternatives (the “offshoring” alternative),
`
`which Google only described in the initial fact discovery period as “geographically locating the
`
`servers running the Accused Instrumentalities, or a portion of the Accused Instrumentalities,
`
`outside the United States.” Dkt. No. 268-5 at 20; see also Dkt. No. 226-6 ¶505 (Dr. Mitzenmacher
`
`addressing this purported “offshoring” alternative as described by Google).
`
`B.
`
`Google’s Unilateral Late Disclosure of New Contentions Related to Non-
`Infringing Alternatives Necessitated Supplemental Discovery
`
`These cases have been pending since 2014. By the end of 2020, the initial fact and expert
`
`3
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 7 of 19
`
`
`discovery periods had long since ended, and summary judgment briefing was completed and both
`
`parties had requested oral argument on the dispositive motions. See Dkt. Nos. 201, 213, 242, 243,
`
`246. Despite the advanced stage of the case, on February 19, 2021, without leave of Court and
`
`completely out of the blue, Google served supplemental contention interrogatory responses,
`
`providing new contentions concerning the alleged “offshoring” non-infringing alternative, and
`
`produced more than 1500 pages of documents shortly thereafter. Dkt. No. 268-6 at 2-5; see also
`
`Dkt. No. 248 at 1. In short, Google expanded the single vague sentence about its “offshoring”
`
`alternative in its prior interrogatory response to three pages of text detailing, for the first time, the
`
`precise nature of its proposed alternative—a system in which only the “matching” step or “Match
`
`System” portion of the Content ID system was “offshored,” i.e., performed on servers located in
`
`Europe rather than on servers in the United States.
`
`On April 7, 2021, Network-1 sought assistance from the Court, asking the Court to find
`
`that Google had not shown good cause to unilaterally reopen discovery to amend its contentions
`
`and assert this new damages-related theory, and moved to strike the supplemental responses and
`
`production. See Dkt. No. 248 at 1-3. This Court referred this dispute to the Magistrate Judge. Dkt.
`
`No. 250. On April 23, 2021, the Magistrate Judge denied Network-1’s motion to strike,2 but found
`
`that Network-1 may conduct additional discovery even though both fact and expert discovery had
`
`long-since closed and ordered that “the scope of this limited discovery shall be determined by the
`
`parties through a meet-and-confer process.” Dkt. No. 252.
`
`
`2 At the discovery hearing on this issue, the Magistrate Judge suggested that the issue of Google’s
`unilateral reopening of discovery to assert new damages-related contentions “might be raised at a
`motion in limine at a trial.” Dkt. No. 253 at 26:8-20. Network-1 intends to move in limine, at the
`time contemplated by Your Honor’s Individual Rules of Practice X.A, X.D.1 and any subsequent
`orders from this Court, to exclude the portions of Google’s supplemental discovery responses,
`production, deposition testimony, and expert reports related to its late-disclosed non-infringing
`alternative theories. See Dkt. No. 256 ¶11; see also Ex. B at 24:17-25:5, 27:14-18.
`
`4
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 8 of 19
`
`
`In accordance with the Magistrate Judge’s order denying Network-1’s motion to strike, the
`
`parties submitted, and the Court endorsed, a Joint Stipulation for Limited Discovery After the
`
`Close of Fact Discovery, which set forth the scope of the additional fact discovery in detail. Dkt.
`
`No. 256 ¶¶1-7. The parties also reserved the right to serve supplemental expert reports related to
`
`that fact discovery. Id. ¶10. The Court subsequently granted leave for supplemental reports and set
`
`the deadline for Network-1’s supplemental expert reports for August 26, 2022, and Google’s
`
`deadline for its supplemental rebuttal expert reports for September 16, 2022. Dkt. No. 266 at 1.
`
`C.
`
`Network-1’s Supplemental Expert Reports and Google’s Motion to Strike
`
`On August 26, 2022, Network-1 served supplemental expert reports from both its technical
`
`expert Dr. Mitzenmacher as well as its damages expert Mr. Kinrich, addressing issues and
`
`information that arose in the supplemental discovery period, including that related to Google’s
`
`new alleged non-infringing alternative theory related to offshoring the “matching” portion of
`
`Content ID. Dr. Mitzenmacher included an analysis in his report detailing why Google had not
`
`shown that such offshoring was a viable non-infringing alternative. Dkt. No. 268-1 ¶¶27-146. One
`
`of the many reasons presented by Dr. Mitzenmacher was that a version of Content ID that offshores
`
`the “matching” step still infringes another Network-1 patent that is not asserted in the presently
`
`pending cases, the ’216 patent—a system patent. Id. ¶¶38-146. As noted above, to be clear,
`
`Network-1 is not attempting to assert another patent via this supplemental report and is not seeking
`
`damages for infringement of this patent, but, as Dr. Mitzenmacher explains, infringement of
`
`Network-1’s non-asserted ’216 patent by Google’s late-proposed “offshoring” alternative is
`
`simply one of many reasons why this is not a viable non-infringing alternative to the infringing
`
`Content ID systems. See generally id. at ¶¶27-43; see also, e.g., Largan Precision Co. v. Samsung
`
`Elecs. Co., No. 13-cv-2740, 2015 WL 11251758, at *7 (S.D. Cal. Nov. 20, 2015).
`
`On September 7, 2022, prior to service of its rebuttal expert reports, Google moved to
`
`5
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 9 of 19
`
`
`strike, via this Court’s joint letter brief procedure, the portions of Dr. Mitzenmacher’s report that
`
`explained why Google’s new offshoring alternative infringes the ’216 patent (paragraphs 38-146
`
`of the report). Dkt. No. 268 at 1-3. The thrust of Google’s arguments was that “[t]he opinion now
`
`offered in Dr. Mitzenmacher’s supplemental report regarding the ’216 patent could have been
`
`provided in the same form in December 2019” in his opening expert report, and that “the opinions
`
`in paragraphs 38-147 of Dr. Mitzenmacher’s supplemental report are not ‘based upon’
`
`supplemental discovery from Google.” Id. at 2-3. In the letter brief, Network-1 explained that, to
`
`the contrary, such expert opinions could not have been provided by Dr. Mitzenmacher in 2019 for
`
`the simple reason that at that time Google had not yet provided the specifics concerning what
`
`portion or portions of Content ID are “offshored” in their proposed alternative and how that
`
`offshoring would be achieved, let alone identify the Match System portion of Content ID as it did
`
`in its 2021 contentions. Id. at 4-5. Network-1 also explained how Dr. Mitzenmacher’s analysis
`
`does indeed rely on the supplemental discovery. Id. This Court again referred this dispute to the
`
`Magistrate Judge. Dkt. No. 270.
`
`D.
`
`The Magistrate Judge Grants Google’s Motion to Strike
`
`After an October 6, 2022 hearing, the Magistrate Judge granted the motion in a single-
`
`paragraph decision, stating that “Plaintiff’s failure to affirmatively identify the ‘216 patent,
`
`especially during the supplemental discovery period, violated [its] duty [under Rule 26(a)(1)].
`
`Defendants relied on Plaintiff’s silence and would be unduly prejudiced by being made to
`
`challenge the ‘216 patent without the aid of additional discovery.” Dkt. No. 283. Disclosure of the
`
`’216 patent in fact discovery was not the basis of Google’s motion to strike, and as such the parties
`
`did not address this issue in the joint letter briefing on this motion. See Dkt. No. 268. And in any
`
`event, as detailed below, the ’216 patent was in fact disclosed even before supplemental fact
`
`6
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 10 of 19
`
`
`discovery. See infra § III.A.
`
`III. ARGUMENT
`
`A.
`
`The Magistrate’s Order Is Clearly Erroneous Because It Is Based on a False
`Factual Predicate
`
`The sole basis cited in the Magistrate’s Order for granting Google’s motion to strike is that
`
`the ’216 patent was purportedly not disclosed in fact discovery (or before the conclusion of the
`
`supplemental fact discovery) and thus “Google maybe never knew about it.” Dkt. No. 283; Ex. B.
`
`at 25:12-19; see also id. at 5:11-15 (“THE COURT: . . . I further understand that the 216 patent
`
`that’s at issue in today’s dispute was never disclosed by Network-1 including during the
`
`supplemental discovery and was first raised as part of this supplemental report.”); id. at 25:9-11
`
`(“THE COURT: . . . it seems to me that this patent is something you are now relying on and you
`
`never disclosed it as part of the discovery process.”); id. at 25:12-19. In other words, the Magistrate
`
`Judge struck the portions of Dr. Mitzenmacher’s supplemental expert report addressing the ’216
`
`patent because that patent was purportedly not disclosed during either initial or supplemental fact
`
`discovery. But this is not so; rather, the ’216 patent was identified during the initial fact discovery
`
`period and Google was well aware of it.
`
`Google’s own damages expert Mr. Leonard produced and cited to a Network-1 Form 10-
`
`K that lists the ’216 patent as part of the “Cox Patent Portfolio,” the same portfolio as the three
`
`asserted patents. Ex. A3 at LEONARD_0000446 (listing the ’216 patent as well as the three
`
`asserted patents (U.S. Patent Nos. 8,101,998; 8,205,237; and 8,904,464)). In addition, Network-1
`
`produced a license agreement which designates a certain set of patents as “Network-1 Patents,”
`
`with that set listed on Exhibit B-2 and including both the application that matured into the ’216
`
`
`3 Citations to alphanumeric exhibits refer to the exhibits of the concurrently-filed Hayden
`Declaration.
`
`7
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 11 of 19
`
`
`patent (14/981,219) as well as the three asserted patents. Google’s expert Mr. Leonard analyzed
`
`this license agreement in his initial expert report, including noting in paragraph 100 that the
`
`agreement covers a certain number of issued U.S. patents and U.S. patent applications. Ex. C
`
`¶¶100-101.
`
`In addition, the basis of Google’s motion to strike was that, in its view, “[t]he opinion now
`
`offered in Dr. Mitzenmacher’s supplemental report regarding the ’216 patent could have been
`
`provided in the same form in December 2019” in his opening expert report, and that “the opinions
`
`in paragraphs 38-147 of Dr. Mitzenmacher’s supplemental report are not ‘based upon’
`
`supplemental discovery from Google.” Dkt. No. 268 at 2-3 (emphasis added); see also supra §
`
`II.C; Ex. B at 23:17-24:2. Therefore, the joint letter briefing and Network-1’s preparation for the
`
`discovery hearing focused on those issues, not the disclosure of the ’216 patent during fact
`
`discovery. See generally Dkt. No. 268; Ex. B. Until these objections, Network-1 therefore did not
`
`have a full and fair opportunity to respond to whether or not the ’216 patent was disclosed prior to
`
`or during the supplemental fact discovery period. The evidence presented with these objections
`
`demonstrates that it was, and also that Google was indeed aware of the ’216 patent.
`
`As noted above, from the face of the Magistrate’s Order, the sole basis for granting
`
`Google’s motion to strike was that the ’216 patent was purportedly not disclosed in fact discovery,
`
`but that is false. To the extent the Magistrate Judge struck certain portions of Dr. Mitzenmacher’s
`
`supplemental expert report because Network-1 did not disclose its contentions rebutting Google’s
`
`late-disclosed “offshoring” alternative during the supplemental fact discovery period rather than
`
`during the supplemental expert discovery period (see Ex. B at 9:22-10:14, 11:12-23), that was also
`
`clear error. Google did not propound any interrogatories (or any other discovery) seeking
`
`disclosure of Network-1 rebuttal contentions concerning non-infringing alternatives, either in the
`
`8
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 12 of 19
`
`
`initial or the supplemental discovery periods. And there is no requirement under Rule 26(a)(1) or
`
`any other operative rule that Network-1 do so absent a discovery request seeking that information.
`
`There was therefore no mechanism for Network-1 to disclose these contentions in advance of
`
`supplemental expert reports, which is where it did so. Indeed, Google agrees that disclosure of
`
`rebuttal non-infringing alternative contentions is the purview of expert reports, not unsolicited
`
`disclosures of contentions during fact discovery. See Dkt. No. 268 at 2.
`
`Because the ’216 patent was identified during discovery, the sole factual predicate for the
`
`Magistrate’s Order is incorrect. The entirety of the Magistrate’s Order should be set aside on this
`
`basis alone.
`
`B.
`
`The Finding in the Magistrate’s Order that Google Is “Unduly Prejudiced” by
`Dr. Mitzenmacher’s Analysis Concerning the ’216 Patent in his Supplemental
`Expert Report Is Clearly Erroneous
`
`As noted above, the Magistrate’s Order states the following basis for striking portions of
`
`Dr. Mitzenmacher’s supplemental report: “Plaintiff’s failure to affirmatively identify the ‘216
`
`patent, especially during the supplemental discovery period, violated [its] duty [under Rule
`
`26(a)(1)]. Defendants relied on Plaintiff’s silence and would be unduly prejudiced by being made
`
`to challenge the ‘216 patent without the aid of additional discovery.” Dkt. No. 283 (emphasis
`
`added). The Magistrate’s Order does not explain what undue prejudice Google would face if its
`
`motion to strike is denied; nor what additional discovery Google would need to conduct concerning
`
`the ’216 patent, particularly since Google did not identify any such discovery.
`
`First, the Magistrate’s Order’s prejudice finding is solely rooted in the same false factual
`
`predicate addressed in the preceding section—that the ’216 patent was not disclosed prior to or
`
`during supplemental fact discovery period. But as addressed above, the ’216 patent was indeed
`
`disclosed during fact discovery and Google was aware of it. See supra § III.A.
`
`9
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 13 of 19
`
`
`Second, aside from the two-page analysis addressing the impact of governing case law on
`
`the specific offshoring configuration of Google’s late-proposed alternative (Dkt. No. 268-1 ¶¶38-
`
`43), the remainder of the portion of Dr. Mitzenmacher’s report that the Magistrate’s Order strikes
`
`largely mirrors the analysis of the asserted claims presented in Dr. Mitzenmacher’s 2019 report
`
`due to the similarities in the patent claims. Dkt. No. 268 at 5; compare Dkt. No. 268-1 ¶¶44-147
`
`(analysis of system claim 1 of the ’216 patent in supplemental report) with, e.g., Dkt. No. 226-6
`
`¶¶163-259 (analysis of method claim 33 of the asserted ’237 patent). Google’s technical expert
`
`was thus able to fulsomely respond to Dr. Mitzenmacher’s supplemental opinions concerning the
`
`’216 patent with more than 35 pages of analysis. Ex. B at 26:24-27:13; see also id. at 24:3-8 (noting
`
`that Google’s expert had three weeks to prepare a response to the narrow supplemental report
`
`issued by Network-1, just shy of the default of thirty days for a rebuttal expert report addressed to
`
`all issues).
`
`Because the ’216 patent was identified during fact discovery, the sole factual predicate for
`
`the finding of “undue prejudice” in the Magistrate’s Order is incorrect. The entirety of the
`
`Magistrate’s Order should be set aside on this basis alone, and as demonstrated above, Google is
`
`not otherwise prejudiced by the portion of Dr. Mitzenmacher’s supplemental expert report it seeks
`
`to strike.
`
`C.
`
`The Magistrate’s Order Is Clearly Erroneous Because It Fails to Recognize
`that Network-1’s Expert Could Not Have Presented the ’216 Patent Analysis
`Prior to Receiving Google’s 2021 Supplemental Discovery
`
`In requesting to strike the opinions concerning why the ’216 patent rendered Google’s
`
`purported non-infringing alternative non-viable, Google argued that the opinions should have been
`
`included in Dr. Mitzenmacher’s 2019 expert report. The Magistrate Judge did not adopt this
`
`contention as a basis for granting the motion, relying instead on an argument that Google did not
`
`make and that was raised sua sponte by the Magistrate Judge at a telephonic hearing. Since Google
`
`10
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 14 of 19
`
`
`may argue that this presents an alternative basis to affirm the Magistrate Judge’s ruling, Network-
`
`1 addresses why Google’s argument fails.
`
`First, it is well-established that Google bears the burden of proof concerning the existence
`
`of non-infringing alternatives in the context of determination of a reasonable royalty for patent
`
`infringement. See, e.g., SPEX Techs. v. Apricorn, Inc., No. 16-cv-07349, 2020 WL 1289546, at *2
`
`(C.D. Cal. Jan. 21, 2020) (“The accused infringer bears the burden of proving the existence of non-
`
`infringing alternatives.”); see also Smart Skins LLC v. Microsoft Corp., No. 15-cv-544, 2016
`
`WL4148091, at *2 (W.D. Wash. July 1, 2016); WhereverTV, Inc. v. Comcast Cable Commc’ns,
`
`LLC, No. 18-cv-529, 2022 WL 2751752, at *2 (M.D. Fla. July 14, 2022); Velocity Patent LLC v.
`
`FCA US LLC, 319 F. Supp. 3d 950, 972 (N.D. Ill. 2018).
`
`Despite bearing that burden of proof, Google elected to only provide a single sentence
`
`concerning its alleged “offshoring” non-infringing alternative during the initial fact discovery
`
`period: “The first available non-infringing alternative is geographically locating the servers
`
`running the Accused Instrumentalities, or a portion of the Accused Instrumentalities, outside of
`
`the United States. See, e.g., NTP, Inc. v. Research in Motion, 418 F.3d 1282 (Fed. Cir. 2005).”
`
`Dkt. No. 268-5 at 20. This vague description does not indicate what portions or portions of Content
`
`ID Google was proposing would be moved offshore in the alternative, let alone what servers would
`
`be moved. As noted above, Content ID involves various subsystems, including the
`
`“fingerprinting,” “matching,” and “claiming” components noted above. See supra § II.A. Content
`
`ID is a complex system that also has various other components, and many of them (including the
`
`“fingerprinting,” “matching,” and “claiming” components) can be broken down into further
`
`subsystems, which may or may not run on the same servers. There are therefore at least a dozen,
`
`if not more, possible permutations of this alleged “first available non-infringing alternative” as
`
`11
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 15 of 19
`
`
`described in Google’s 2015 interrogatory response. Perhaps recognizing the errors of its ways,
`
`Google’s post-discovery 2021 supplemental response selected one of those options (offshoring
`
`only the servers that run the “matching” step), and for the first time provided further detail on that
`
`option. Dkt. No. 268-6 at 2-5. Further, although the existence of non-infringing alternatives is an
`
`issue on which Google bears the burden of proof, Google submitted no opening expert report on
`
`this issue. Its only expert articulations on the issue were in rebuttal reports,4 to which Network-1
`
`was not entitled to a further response.
`
`Google’s citation to NTP in its original interrogatory response bears explanation. As noted
`
`above, each of the asserted claims in this case is a method claim. See supra § II.A. In NTP, the
`
`Federal Circuit held that a method patent claim is not infringed unless each of the method steps is
`
`performed within the United States. 418 F.3d at 1318. Thus, “offshoring” a single step of a claimed
`
`method would evade infringement. However, NTP also held that “[t]he use of a claimed system
`
`under section 271(a) is the place at which the system as a whole is put into service, i.e., the place
`
`where control of the system is exercised and beneficial use of the system obtained.” Id. at 1317
`
`(emphasis added). In other words, in analyzing system claims like claim 1 of the ’216 patent,
`
`whether a partially offshored version of Content ID would infringe is a fact-specific inquiry that
`
`would depend on what portion or portions of Content ID is offshored—depending on the specific
`
`
`4 To the extent Google argues it provided additional detail about this proposed alternative in Rule
`30(b)(6) testimony prior to the November 2019 close of the initial fact discovery period and in its
`February 2020 initial rebuttal expert reports, that is not so; at most, that testimony and those reports
`discussed hypothetical concepts untethered to Google’s non-infringing alternative contentions in
`its interrogatory response. See Dkt. No. 268 at 5 n.5 and citations therein. In any event, if Google
`contemplated the specific “offshoring” alternative in which only the “matching” step is offshored
`before the close of the initial fact discovery, it should have amended its contention interrogatory
`response at that time, not more than a year later. But Google did not amend its contention
`interrogatory response prior to initial expert reports. Thus, while Google’s fact witness might have
`testified (in extremely vague terms) about one possible permutation of Google’s contention,
`Google never provided an interrogatory response to limit its contention to even that vague
`permutation.
`
`12
`
`

`

`Case 1:14-cv-02396-PGG-SN Document 287 Filed 11/01/22 Page 16 of 19
`
`
`configuration, a partially offshored version of Content ID may or may not have infringed the ’216
`
`patent or it may have infringed a different patent in Network-1’s portfolio.
`
`Absent analyzing every possible permutation, or somehow guessing what permutation
`
`Google was contemplating, Dr. Mitzenmacher therefore could not have conducted the analysis
`
`contemplated in NTP for the system claims of the ’216 patent (or any other patent in Network-1’s
`
`portfolio) at the time of his original report in 2019. At that time, he (and Network-1) were unaware
`
`that Google would later actually contend that the non-infringing alternative was offshoring the
`
`“matching” component, but keeping the “fingerprinting” and “claiming” components in the United
`
`States. After receiving that information, but not before, Dr. Mitzenmacher was able

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