throbber
Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 1 of 8 PageID #: 18696
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`HUAWEI DEVICE USA INC. ET AL.,
`
`
`Defendants.
`
`APPLE, INC.,
`
`
`Defendant.
`















`
`
`
`Case No. 2:17-CV-0513-JRG
`(LEAD CASE)
`
`
`JURY TRIAL DEMANDED
`
`
`Case No. 2:17-CV-0516-JRG
`(CONSOLIDATED CASE)
`
`JURY TRIAL DEMANDED
`
`
`PLAINTIFF AGIS SOFTWARE DEVELOPMENT LLC’S REPLY
`IN SUPPORT OF ITS OPPOSED MOTION TO STRIKE PORTIONS
`OF THE EXPERT REPORT OF NEIL SIEGEL RELATING TO
`THE UNDISCLOSED INVALIDITY THEORY
`BASED ON “DYNAMICALLY ELECTING SERVERS” (DKT. 233)
`
`
`
`
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 2 of 8 PageID #: 18697
`
`I.
`
`ARGUMENT
`
`A.
`
`Apple’s Invalidity Contentions Were Limited to a Central Server Theory
`From Which The New Dynamically Electing Server Theory Was Not
`Apparent
`
`
`
`Dr. Siegel’s new theory of invalidity is essentially that “hundreds” of vehicle-mounted
`
`FBCB2 devices “could become servers,” as opposed to the centralized “Command Center
`
`Servers” and satellites disclosed in Apple’s invalidity contentions. Compare Ex. H at 196:3-8
`
`with Ex. I at 4. For the proposition that this theory was present in Apple’s invalidity contentions,
`
`Apple relies on disclosures that do not mention “dynamically electing servers” in which it did
`
`not contend that FBCB2 user devices constitute servers. See Dkt. 257 at 6-7. In the alternative,
`
`Apple argues that the dynamically electing server theory was “describe[d] using different
`
`words,” but Apple cites to disclosures which neither used the word “server,” nor plausibly
`
`described FBCB2 user devices as servers. See Dkt. 257 at 7. These disclosures are far more
`
`plausibly directed to a centralized server theory, acknowledged as distinct from the dynamically
`
`electing server theory by Dr. Siegel. See Ex. J (Siegel Transcript) at 102:2-103:7; 202:8-16;
`
`Dkt. 233 at 5. Because Apple’s invalidity contentions did not put AGIS on notice of Dr. Siegel’s
`
`new dynamically electing server theory, AGIS respectfully requests that the Court strike the new
`
`theories.
`
`1.
`
`Apple’s assertion that it “explained” dynamically electing servers is
`based on parts of its invalidity contentions not pertaining to any
`server limitation
`
`
`
`Invalidity contentions serve to put the party alleging infringement on notice of the alleged
`
`infringer’s arguments as to “[w]hether each item of prior art anticipates each asserted claim or
`
`renders it obvious.” P.R. 3-3. AGIS does not “flail for procedural protection,” as Apple suggests
`
`[Dkt. 257 at 2]; rather, AGIS seeks enforcement of P.R. 3-3 in accord with its purpose to “further
`
`the goal of full, timely, discovery and provide all parties with adequate notice and information
`
`
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 3 of 8 PageID #: 18698
`
`with which to litigate their cases.” Cummins–Allison Corp. v. SBM Co., No. 9:07–cv–196, 2009
`
`WL 763926, at *1 (E.D.Tex. March 19, 2009). To satisfy the P.R. 3-3(4) requirement of “a chart
`
`identifying where specifically in each alleged item of prior art each element of each asserted
`
`claim is found,” defendants must “provide notice of how each claim element is met.” Id. at 4
`
`(holding that “failure to provide the specific reference that allegedly reads on a claim
`
`limitation . . .does not place plaintiff on notice”); see also Realtime Data, LLC v. Packeteer, Inc.,
`
`Civil No. 6:08–cv–144–LED–JDL, 2009 WL 4782062, at *2 (E.D. Tex., December 8, 2009).
`
`
`
`Apple bases its argument on disclosures that are insufficient to put AGIS on notice of its
`
`allegedly disclosed theory under this standard, because the proffered disclosures do not address
`
`any claim limitation that recites a “server.”1 Moreover, this failure to put AGIS on notice with
`
`regard to the ‘838 Patent is representative of Apple’s invalidity contentions for each of the
`
`patents-in-suit. See e.g. Ex. I at 4. Further, Apple’s charts never contended that FBCB2 user
`
`devices constituted servers at all, let alone “dynamically electing servers”; the only quotes that it
`
`purports to show otherwise actually suggest the opposite.2 Thus, because AGIS was not on
`
`notice of any application of the quoted ‘559 Patent or 1999 Siegel Presentation disclosures to a
`
`“server” limitation, and further not on notice of any theory in which FBCB2 user devices became
`
`servers, these items do not support Dr. Siegel’s new dynamically electing server theory.
`
`
`1 Apple alleges that a set of block quotes to the Siegel ‘559 Patent and a 1999 presentation by Dr. Siegel specifically
`explain dynamically electing servers. See Dkt. 257 at 6-7. But Apple points to no language that would put AGIS on
`notice that these quotes relate to any server limitation, or that suggests they relate to a server limitation at all. See
`Dkt. 257-3 at 4-22. Rather, throughout the patents-in-suit, Apple only recited these quotations where claim
`limitations concerned “joining a group” or “joining a network.” See e.g. Dkt. 257-3 at 4.
`2 Apple suggests that the ‘599 Patent explains FBCB2 user devices acting as “hosts,” “servers,” and “routers,” but
`the complete sentence containing the terms Apple quoted in its opposition states that, “Other computers function as
`servers, and distribute requested data to network users with host computers.” Dkt. 257 at 6; 257-6 at 1:21-30.
`Similarly, Apple draws the term “dynamic ‘server’ structure” from a table in Dr. Siegel’s 1999 presentation which
`more completely states that “Units moving away from/out-of-LoS-of their nominal “data supplier” . . . Need a
`dynamic “server” for key data.” Dkt. 257-3 at 19. The singular use of “a” suggests the presentation contemplated a
`single centralized “server,” i.e. a satellite that could not be blocked by losing line-of-sight, a conclusion supported
`by the disclosure of a satellite link which “breaks-the-line of sight barrier” in the charted cell for the same claim
`element. Dkt. 257-3 at 6. Moreover, in describing such a server, the chart refers to “needed battlefield dynamics”
`and “implied technical requirements,” suggesting that such a server did not exist. Id. at 19.
`
`2
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 4 of 8 PageID #: 18699
`
`2.
`
`Apple’s relevant invalidity contentions disclosed only centralized
`server systems from which the dynamically electing server theory is
`not apparent
`
`
`
`The words “dynamically electing server” do not appear in Apple’s invalidity contentions,
`
`nor are the properties of a dynamically electing server described. Apple’s charts do not describe
`
`hundreds of vehicles in a group acting as independent servers, nor do they describe how radio
`
`“transceivers bolted to the tops of vehicles” transform into servers. Dkt. 257-3 at 23. Instead,
`
`Apple’s charts describe satellites and “Command Center Servers,” in a “’hub and spoke’
`
`configuration” with a number of FBCB2 user devices. Id. Dr. Siegel confirmed, and Apple’s
`
`opposition does not dispute, that the “dynamically electing server’s” implementation is radically
`
`different from a centralized server and, instead, involves multiple units acting as servers which
`
`change server status over time. See Ex. J at 102:2-103:7; 202:8-16; Dkt. 233 at 5. Apple’s
`
`contentions described only the latter, and did not put AGIS on notice of the former.
`
`
`
`Apple’s Opposition argues that AGIS should have derived its new theory from a first
`
`block quote noting the capability of an FBCB2 “Applique” systems to “gather and distribute
`
`critical combat information to soldiers,” through use of the “Tactical Internet,” and a second
`
`block quote contrasting satellite implemented “FBCB2-BFT” with “terrestrial based” “FBCB2-
`
`EPLRS.” Dkt. 257-3 at 24-25 and 28-29. Apple provided no supporting argument of any kind to
`
`explain the relevance of each block quote, for example, that it contended these systems
`
`constituted servers, or that such servers were “dynamically electing.” Id. Instead, Apple now
`
`alleges that describing a device which can “gather” and “distribute” information, and describing
`
`FBCB2-EPLRS in the absence of a satellite were each sufficient to put AGIS on notice that
`
`Apple considered every FBCB2 device capable to transforming into a server that met the claimed
`
`limitations. Dkt. 257 at 7. But the quotes Apple cited do nothing of the sort – moreover, if it had
`
`been Apple’s intention for its charts to put AGIS on notice of the dynamically electing server
`
`3
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 5 of 8 PageID #: 18700
`
`theory, it could have simply described its theory rather than copy-pasting block quotes without
`
`further explanation. Without such explanation, AGIS had no reason to take notice that Apple’s
`
`contentions meant anything other than what was identified by its charted quotes.
`
`
`
`Furthermore, Apple’s allegedly explanatory block quotes were not provided in a vacuum;
`
`Apple’s invalidity charts included quotes describing a centralized “Command Center Server”
`
`installed at a headquarters and a “satellite hub” for virtually every claim element reciting a
`
`server, and for every claim element alleged to be anticipated by dynamically electing servers in
`
`the Siegel Report. Compare Dkt. 233-4 (Siegel Expert Report) at ¶¶100, 104, 164, 183, 219, 235,
`
`243, 265, 273, 418, and 470 with e.g. Dkt. 233-2. For one claim element with “server”
`
`limitations identified in the Siegel report, Apple’s invalidity contentions only disclosed the
`
`above-referenced “Command Center Server” and “satellite hub” quote. See e.g. Ex. C at 4-5;
`
`Dkt. 233-4 at ¶¶83. This block quote represented the only reference to a “server” in Apple’s
`
`charts for the claims identified in the Siegel Report. Apple does not dispute that this disclosure
`
`does not support its dynamically electing server theory. See Dkt. 257 at 10. Apple’s apparent
`
`willingness to use the word “server” with respect to the central server theory suggests that if it
`
`intended to put AGIS on notice of its “dynamically electing server” theory, it would have at the
`
`very least made use of the word “server” in the charted claim elements that it now alleges
`
`anticipated by that theory to anticipate. Apple’s failure to do so further suggests that Dr. Siegel’s
`
`“dynamically electing servers” represent a new theory, not present in Apple’s invalidity
`
`contentions.
`
`4
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 6 of 8 PageID #: 18701
`
`B.
`
`AGIS Was Prejudiced
`
`
`
`AGIS has been prejudiced by Apple’s new theory of invalidity; at the very least, AGIS
`
`has missed additional document discovery on FBCB2 user devices and transceivers that it would
`
`have sought had it been timely informed regarding the distinctions Apple now draws between
`
`“user devices,” “transceivers,” and “Command Center Servers” comprising FBCB2.
`
`Further, Apple misrepresents that “AGIS conducted its fact discovery regarding FBCB2
`
`after Dr. Siegel served his expert report.” Dkt. 257 at 12. By “fact discovery,” Apple is
`
`apparently referring to Dr. Siegel’s November 14, 2018 deposition, as fact discovery closed on
`
`October 26, 2018 – four days prior to service of Dr. Siegel’s expert report on October 30, 2018.
`
`Dkt. 217 at 3. But AGIS and Apple explicitly agreed through counsel that Dr. Siegel’s deposition
`
`was conducted pursuant to expert discovery, not fact discovery.3
`
`II.
`
`CONCLUSION
`
`
`
`For the foregoing reasons and those provided in AGIS’ Opening Brief, AGIS respectfully
`
`requests that this Court strike the new theories in Dr. Siegel’s Invalidity Expert Report.
`
`Dated: January 11, 2019
`
`
`
`
`
`
`
`Respectfully submitted,
`
`BROWN RUDNICK LLP
`
` /s/ Alfred R. Fabricant
`
`Alfred R. Fabricant
`NY Bar No. 2219392
`Email: afabricant@brownrudnick.com
`Lawrence C. Drucker
`NY Bar No. 2303089
`Email: ldrucker@brownrudnick.com
`
`
`3 AGIS and Apple agreed that Dr. Siegel’s deposition would be pursuant to expert discovery via meet-and-confer on
`November 13, 2018, the undisputed confirmation of which stated “Thank you for confirming our discussion. As you
`pointed out, we served our subpoena before we knew that Dr. Siegel would be submitting an expert report. You
`further pointed out that you saw this issue as an expert issue, hence the seven hour limit. In view of our discussions,
`we hereby withdraw out subpoena on Dr. Siegel and we agree to proceed with Dr. Siegel’s deposition pursuant to
`expert discovery. . .” Ex. K at 1 and 9.
`
`5
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 7 of 8 PageID #: 18702
`
`Peter Lambrianakos
`NY Bar No. 2894392
`Email: plambrianakos@brownrudnick.com
`Vincent J. Rubino, III
`NY Bar No. 4557435
`Email: vrubino@brownrudnick.com
`Alessandra C. Messing
`NY Bar No. 5040019
`Email: amessing@brownrudnick.com
`Shahar Harel
`NY Bar No. 4573192
`Email: sharel@brownrudnick.com
`John A. Rubino
`NY Bar No. 5020797
`Email: jrubino@brownrudnick.com
`Enrique W. Iturralde
`NY Bar No. 5526280
`Email: eiturralde@brownrudnick.com
`Daniel J. Shea, Jr.
`NY Bar No. 5430558
`Email: dshea@brownrudnick.com
`Justine Minseon Park
`NY Bar No. 5604483
`Email: apark@brownrudnick.com
`BROWN RUDNICK LLP
`7 Times Square
`New York, NY 10036
`Telephone: 212-209-4800
`Facsimile: 212-209-4801
`
`Samuel F. Baxter
`Texas Bar No. 01938000
`Email: sbaxter@mckoolsmith.com
`Jennifer L. Truelove
`Texas State Bar No. 24012906
`Email: jtruelove@mckoolsmith.com
`McKOOL SMITH, P.C.
`104 East Houston Street, Suite 300
`Marshall, Texas 75670
`Telephone: 903-923-9000
`Facsimile: 903-923-9099
`
`ATTORNEYS FOR PLAINTIFF, AGIS
`SOFTWARE DEVELOPMENT LL
`
`6
`
`

`

`Case 2:17-cv-00513-JRG Document 280 Filed 01/11/19 Page 8 of 8 PageID #: 18703
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that, on January 11, 2019, all counsel of record who are
`
`deemed to have consented to electronic service are being served with a copy of this document via
`
`the Court’s CM/ECF system per Local Rule CV-5(a)(3).
`
`
`
`
`
` /s/ Alfred R. Fabricant
` Alfred R. Fabricant
`
`
`
`

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