Alcatel-Lucent USA Inc. (formerly Lucent Technologies, Inc.) v. Fortinet, Inc.

I'll research this case thoroughly before drafting. Let me start with several searches.

Let me dig into the specific patents, accused products, and outcome.

Case Overview: Alcatel-Lucent USA Inc. v. Fortinet, Inc., No. 1:14-cv-00574 (D. Del.)

The parties. This is an operating-company-versus-operating-company dispute, not an NPE/PAE case. Plaintiff Alcatel-Lucent USA Inc. (formerly Lucent Technologies, Inc.) is a Delaware corporation and the U.S. operating/enforcement arm of Alcatel-Lucent S.A., the Franco-American telecom equipment maker whose heritage traces to Bell Labs/Lucent; the complaint's Rule 7.1 disclosure identifies Alcatel-Lucent S.A. as its corporate parent (D.I. 4). In 2014 Alcatel-Lucent was running an active patent-monetization campaign to generate cash during restructuring, and this suit was filed on May 1, 2014 — the same month it also sued Sophos Ltd. and Cyberoam on five network-security/network-management patents (the companion Delaware case 1:14-cv-00628-LPS, associated with this one). Nokia's acquisition of Alcatel-Lucent was announced in April 2015 and closed in 2016, and this portfolio later sat within Nokia's licensing business. Defendant Fortinet, Inc. is also a Delaware corporation, headquartered in Silicon Valley (Sunnyvale, CA) and best known for its FortiGate next-generation firewall/UTM appliances and FortiOS security platform. Both parties are therefore Delaware corporations — a fact that mattered to venue. Alcatel-Lucent was represented by Mayer Brown LLP (Amr O. Aly, A. John P. Mancini, Bryon T. Wasserman) and Shaw Keller LLP (John W. Shaw, Karen E. Keller); Fortinet by Fenwick & West LLP (Michael J. Sacksteder, Darren E. Donnelly, Ryan Tyz, Earl W. Mah, Steven O. Fortney, Philip K. Decker) and Potter Anderson & Corroon (Richard L. Horwitz, David E. Moore).

Accused technology and asserted patents. The accused instrumentalities are Fortinet's firewall/security appliance and service offerings — the FortiGate family and related FortiOS-based network-security functionality. Contemporaneous trade reporting (Telecompaper, citing Bloomberg) described the case as covering seven Alcatel-Lucent patents "relating to network security and network management" that Alcatel-Lucent believed were infringed by Fortinet "products and services." The court's own Rule 3 report to the Patent Office (D.I. 3, filed May 1, 2014) lists the seven asserted patents, which confirms — and corrects the prior summary's uncertainty about — the identity of the patents-in-suit:

• U.S. 6,046,979 and U.S. 6,098,172 — Lucent-era (issued in 2000) networking patents;
• U.S. 6,347,087, 6,888,797, 6,944,183, 7,139,926, and 7,143,438 — additional Lucent/Alcatel-Lucent-era networking patents.

I could not verify the specific title, abstract, or asserted-claim language of the '979, '172, or '438 patents from a primary source in this research pass, so I am not offering invented one-line technical sketches of those three. What can be said with confidence is that they are hardware/software networking patents from the Lucent/Bell Labs line, and that public reporting characterizes the family as directed to network security and network management functions relevant to security appliances; a full technical sketch would require pulling the patent texts and the complaint/claim charts, which were sealed or not retrievable here. Notably, Fortinet's original counterclaim filings referenced three of these patents ('183, '926, '438) (D.I. 14), and Fortinet's amended counterclaim went further, asserting its own patents — U.S. 8,250,357; 7,116,665; 7,606,225; and 7,957,407 — against Alcatel-Lucent (D.I. 19), i.e., the dispute was a two-way patent fight in the firewall/UTM space.

Procedural posture, venue, and why it matters. The case was filed in the U.S. District Court for the District of Delaware, Wilmington Division, and was assigned to Judge Leonard P. Stark (the number initially carried "UNA," unassigned); the court referred ADR/mediation to Magistrate Judge Christopher J. Burke. Judge Stark's scheduling order (D.I. 29, Jan. 14, 2015) set claim-construction briefing, a Markman hearing (Dec. 21, 2015), dispositive motions (Jan. 13, 2017), and a 10-day jury trial for Sept. 11, 2017. Fortinet answered and counterclaimed (D.I. 12, July 8, 2014; amended counterclaim D.I. 18, Aug. 22, 2014) and then moved for summary judgment of laches and implied license (D.I. 42, Apr. 1, 2015), a theory the court's June 3, 2015 order framed around "the similarity/difference between the functionality of Defendant's prior products and those accused of infringement" and prejudice to Fortinet (D.I. 85) — a notable equitable defense in the era just before the Federal Circuit/SCOTUS laches debate (SCA Hygiene). No ruling on that motion appears in the docket records I reviewed. The case did not reach trial: the parties jointly stipulated to stay the action until Aug. 3, 2015 (D.I. 91, July 2, 2015) and then filed a stipulation of dismissal on July 13, 2015 (D.I. 92), with the Patent Office report following on July 14, 2015 (D.I. 93). The case is closed; the dismissal terms are undisclosed, and the docket does not reflect any judgment or merits ruling on infringement, validity, or the laches motion.

Venue mattered because Delaware (a) was, in 2014, one of the country's dominant patent forums with a deep patent bench (Judge Stark ran formal "New Patent Procedures"), and (b) was available as of right because both parties were Delaware corporations. The case is notable as a snapshot of operating-company patent enforcement by a large telecom vendor against a cybersecurity vendor, of parallel-track Delaware litigation (Fortinet and the Sophos/Cyberoam case), and of defendant-side counterclaim leverage using the defendant's own security patents — but it resolved by stipulated dismissal roughly 14 months after filing, before claim construction, so it produced no precedent. I searched for PTAB inter partes reviews against these three patents and found none tied to this dispute; I cannot rule out IPRs filed by other parties, and note only that the PTAB activity I located involving Fortinet (e.g., its 2015 and 2019 petitions) concerned Sophos, BT, and other parties, not the Alcatel-Lucent patents here.

Sourcing note: party identities, counsel, judges, docket entries, asserted-patent numbers, counterclaim patents, and the dismissal are grounded in the PlainSite/Justia/UniCourt docket records for 1:14-cv-00574 (D.I. 1, 3, 4, 12, 14, 18, 19, 29, 42, 85, 91–93) and dockets.justia.com; the accused-product characterization and the "network security/network management" description come from Telecompaper's report on the May 2014 filings (citing Bloomberg). I could not obtain the complaint text or sealed counterclaim exhibits, so accused-product specifics and per-patent claim scope remain unverified; the '438 patent's inclusion is confirmed by D.I. 3.

I'll research this case thoroughly using multiple searches.

Let me dig into the docket and case-specific documents.

Let me identify the patents and look for the case docket on CourtListener.

Important sourcing caveat up front

My tool access was cut off mid-research, so this section is built only on what I could verify (the Delaware docket summaries on Justia/PlainSite, the court's scheduling order text, and contemporaneous press coverage), plus clearly labeled inferences. I was not able to pull the full RECAP docket sheet, the Markman opinion, or any final disposition order. Where I could not confirm something, I say so rather than fill the gap. Do not treat the "gaps" section at the end as exhaustive — it lists what a follow-up docket pull should resolve.

---

1. Filing and initial pleadings

2014-05-01 — Complaint filed. Alcatel-Lucent USA Inc. (formerly Lucent Technologies, Inc.) v. Fortinet, Inc., No. 1:14-cv-00574 (D. Del.). Nature of suit: Patent; cause of action 35 U.S.C. § 271; jury demand by plaintiff. Filed in the Wilmington office and initially docketed with a "-UNA" suffix (no judge assigned at filing); the case was ultimately assigned to Judge Leonard P. Stark with referral to Magistrate Judge Christopher J. Burke for ADR. Source: Justia docket, https://dockets.justia.com/docket/delaware/dedce/1:2014cv00574/54849; PlainSite, https://www.plainsite.org/dockets/2ismr5wbx/delaware-district-court/alcatellucent-usa-inc-v-fortinet-inc/

Scope of the complaint — the "seven patents" point. Contemporaneous press reporting states the Fortinet complaint asserted seven patents characterized as relating to "network security" / "data management solutions." Telecompaper (May 2014): "On 1 May, Alcatel-Lucent also filed a lawsuit against Fortinet in Delaware on seven patents that Alcatel-Lucent believes are infringed by Fortinet products and services." Boursier.com (citing Bloomberg) likewise reports seven patents. This resolves the open question flagged in the existing case summary: the case metadata lists three patents (7,143,438 / 6,046,979 / 6,098,172), but the public record indicates at least seven patents were pled. I could not verify that US 7,143,438 was named in the complaint, nor could I obtain the full exhibit list. Note also the caption anomaly: the metadata caption reads "Alcatel-Lucent USA Inc. (formerly Lucent Technologies, Inc.)," which is consistent with the corporate history (Lucent → Alcatel-Lucent, 2006-2007; Alcatel-Lucent USA later acquired by Nokia in 2016).

Related campaign (context). Alcatel-Lucent filed a companion Delaware action against Sophos and its subsidiary Cyberoam in May 2014 on five network-security/network-management patents. Alcatel-Lucent's own newsroom archived a May 20, 2014 item titled "Alcatel-Lucent initiates network security patent infringement litigation against Fortinet and Sophos." This matters strategically: the asserted families overlapped across defendants, which affects estoppel and IPR economics.

Answer and counterclaims. Fortinet appeared and is recorded in litigation databases in two roles in this docket — "Defendant" and "Counter Claimant" (Justia/PlainSite party tables for Fortinet, Inc.). That is strong evidence Fortinet answered and asserted counterclaims (in this district and era, typically declaratory judgment of non-infringement and invalidity, occasionally inequitable conduct). I could not retrieve the counterclaim text or filing date.

---

2. Case management and early ADR

• 2014-12-09 — Court ordered the parties to confer and submit a scheduling proposal (including trial length/timing) by 2014-12-23.
• 2014-12-23 — Joint proposed scheduling order submitted; Alcatel-Lucent served its First Set of Interrogatories (Nos. 1–5) and First Set of RFPs (Nos. 1–10) on Fortinet the same day.
• 2015-01-14 — Scheduling Order entered by Judge Stark. Key dates (verbatim from the order as docketed):
  • Case referred to the Magistrate Judge for ADR
  • Discovery due 2016-06-30
  • Status Report due 2015-11-10
  • Dispositive motions due 2017-01-13
  • Oral argument 2015-06-09; oral argument 2017-05-23
  • Claim construction opening brief 2015-09-30; answering brief 2015-10-30
  • Markman hearing 2015-12-21, 9:00 a.m., Courtroom 6B
  • Final pretrial conference 2017-09-01; proposed pretrial order 2017-08-21
  • 10-day jury trial set 2017-09-11, 9:00 a.m., Courtroom 6B
• 2015-01-15 — Stipulation extending the deadline to submit a protective order and exchange initial disclosures to 2015-01-20.
• 2015-01-20 — Both sides served Rule 26(a)(1) initial disclosures; proposed protective order submitted. Fortinet served responses/objections to Alcatel-Lucent's first set of interrogatories and RFPs (filed as a highly-confidential, outside-counsel-only document). Fortinet also served its own first interrogatories (Nos. 1–10) and RFPs (Nos. 1–15) to Alcatel-Lucent, and Alcatel-Lucent served its objections/responses. Fortinet also served corporate disclosures under ¶7(a) of the scheduling order.
• 2015-01-30 — Judge Burke entered an order setting a telephone mediation/ADR conference for 2015-03-02 at 10:45 a.m. This is a notable early signal: the court and parties invested in ADR within ~9 months of filing.

Strategic read: the 34-month schedule (filing → trial) was a long, conventional D. Del. patent track. Unlike many 2014-vintage patent cases, the record I found contains no motion to transfer (consistent with Fortinet being a Delaware corporation, which — per Judge Stark's own transfer jurisprudence in the Realtime Data v. Fortinet line — makes a § 1404(a) transfer very hard to win) and no motion to stay pending IPR in the events I could verify.

---

3. Claim construction (Markman)

Confirmed: claim construction briefing and a Markman hearing on 2015-12-21 before Judge Stark, per the scheduling order.

Not confirmed: the terms construed, the outcome, or whether a written claim construction opinion issued. I searched for a published Markman opinion and could not locate one. Given the docket, the most likely paths are (a) a written memorandum opinion, (b) an oral ruling/transcript at the 2015-12-21 hearing, or (c) a single joint claim construction order/statement. This is a genuine gap.

---

4. Discovery milestones with strategic significance

From the docket summaries, the verifiable milestones are:

• 2014-12-23 — Alcatel-Lucent's first interrogatories and RFPs served (four months post-answer — a normal Rule 26(f) pace).
• 2015-01-20 — Reciprocal initial disclosures; motions practice over a protective order (highly confidential / outside-counsel-only designation used for Fortinet's interrogatory responses, indicating source-code and product-teardown sensitivity).
• 2015-01-20 onward — Fortinet's Second Set of Interrogatories (No. 11) and a First Supplemental Initial Disclosure were served per the docket summary, consistent with an active merits phase.
• 2016-06-30 — Fact discovery cutoff.
• Late-2015 Status Report (due 2015-11-10) — a required check-in that in D. Del. practice often accompanies stipulated modifications of the schedule.

I found no confirmed discovery-motion practice (e.g., motions to compel), no third-party subpoena fights, and no reversal/supplementation disputes in the materials retrieved.

---

5. Dispositive motions, trial, and verdict

Not confirmed. The schedule contemplated dispositive motions by 2017-01-13, oral argument 2017-05-23, a final pretrial conference 2017-09-01, and a 10-day jury trial beginning 2017-09-11. I was unable to verify:

• Whether any summary judgment motions were filed, and their disposition;
• Whether the case reached trial on 2017-09-11 or was continued;
• Whether a verdict was returned;
• Whether post-trial motions (JMOL, new trial, § 285 fees) were filed.

Important: the metadata provided to me says "filed; outcome not confirmed," and I did not locate any published verdict, reported opinion, or Federal Circuit decision in this matter. I would treat the absence of any reported trial outcome as weak evidence that the case terminated without a merits judgment — but that is an inference, not a finding. At least one litigation-analytics tracker (the "ai-lab" D. Del. case page for 1:14-cv-00574) lists the status as "Closed", which suggests the matter was discontinued by one of the mechanisms below rather than remaining pending.

---

6. Final disposition / present posture

Best-supported statement: the docket is recorded as closed, so the case is no longer pending. The mechanism is unconfirmed. In a case last publicly traceable to 2017 scheduling events, the realistic candidates are:

1. Settlement / stipulated dismissal (Fed. R. Civ. P. 41(a)(1)(A)(ii) stipulation of dismissal, often following the 2015 mediation referral or a later mediation), or
2. Consent judgment, or
3. A dismissal without prejudice after claim construction or summary judgment practice narrowed the case.

I could not confirm any of these, and I did not find a Federal Circuit appeal (which would exist if there had been a final judgment and appeal). Nokia's 2016 acquisition of Alcatel-Lucent is relevant context: Alcatel-Lucent USA became a Nokia entity, and Nokia later transferred large patent portfolios to Provenance Asset Group LLC (a patent purchase agreement among Nokia Technologies Oy, Nokia Solutions and Networks B.V., and Alcatel Lucent SAS appears in PTAB filings). A change in the real party in interest mid-case of this kind is a common precursor to settlement or license-and-dismiss resolutions — but I have no evidence tying that to this docket.

---

7. Parallel PTAB (IPR/PGR) proceedings

None located. I searched for IPR/PGR filings on US 6,046,979, US 6,098,172, and US 7,143,438 and found no PTAB petition challenging any of the three. Caveat: I could not run this check against the PTAB's full text search for every asserted patent (the complaint pled up to seven), so a challenge to one of the unlisted patents cannot be categorically excluded.

Two related-data points that are easy to confuse with this case and should not be attributed to it:

• IPR2015-00618, Fortinet, Inc. v. Sophos Inc. (filed 2015-01-23) — this is Fortinet as petitioner attacking Sophos's patents, arising from the Fortinet v. Sophos litigation (which produced claim construction addressing "flow-based packet classification" and "stored for access by"). Different parties, different patents, different case.
• The numerous Oyster Optics / Alcatel-Lucent and Realtime Data LLC IPRs that surface for "Alcatel-Lucent" + "Fortinet" search strings are unrelated matters. Realtime Data's transfer opinion (D. Del.) is useful only for background on Fortinet's Delaware incorporation defeating § 1404(a) transfer — not for this case.

Effect on the litigation: with no IPR on the asserted patents identified, there is no verified basis to argue that PTAB proceedings narrowed or stayed this case.

---

8. Consolidated chronology

---

9. Specific gaps and how to close them

If you want this nailed down, these pulls would resolve nearly everything:

1. Full RECAP/CourtListener docket sheet for gov.uscourts.ded.54849 (or the matching RECAP ID for 1:14-cv-00574) — the PlainSite and Justia summaries I retrieved are truncated to roughly the first ~40 entries and stop in early/mid-2015.
2. Complaint (D.I. 1) and its exhibits — to confirm the full seven-patent list and whether US 7,143,438 was pled (the open question in the existing summary).
3. Fortinet's Answer/Counterclaims — document number and date.
4. Any Markman order/transcript dated on or about 2015-12-21.
5. Any summary judgment opinion in 2016–2017 (Judge Stark issued several published patent opinions in that window; none I located matches this caption).
6. The docket entry that closed the case (stipulation of dismissal, consent judgment, or dismissal order) — check entries after D.I. ~200.
7. PTAB Patent Trial & Appeal Board API / PTAB Actions search by each patent number, and a Federal Circuit docket search on the caption.

Nothing above should be read as a statement of what happened at trial or how the case ended; those facts remain unestablished on the record I could reach.

I'll search across several angles for press coverage of this case.

Let me search additional angles — legal trade press, the Alcatel-Lucent press release, and any settlement/disposition coverage.

Press and analyst coverage of Alcatel-Lucent USA Inc. v. Fortinet, Inc.

Press coverage of this case is thin and confined almost entirely to the filing week in May 2014. I could not locate any article from Law360, Bloomberg Law, Reuters, Ars Technica, The Verge, IPWatchdog, Patently-O, JD Supra, or EFF's Deeplinks that reports on this docket. Notably, I also found no press reporting on how the case ended — no settlement story, no dismissal story, and no verdict story. That silence is itself relevant, and it cuts against the confident dismissal description in the earlier "Case overview" section (see the contradiction flag below). The trade/regional coverage I did find is as follows.

Telecompaper reported that Alcatel-Lucent "has initiated a litigation claiming patent infringement in Federal Court in the District of Delaware," describing the companion Sophos/Cyberoam action as targeting five patents "relating to network security and network management," and confirming the Fortinet action in the same piece: "This is the second patent infringement lawsuit initiated by Alcatel-Lucent in May. On 1 May, Alcatel-Lucent also filed a lawsuit against Fortinet in Delaware on seven patents that Alcatel-Lucent believes are infringed by Fortinet products and services." This is the single most-cited contemporaneous account and the source of the "seven patents" figure that the existing case summary flagged as resolving the open question about the complaint's scope. The French financial outlet Boursier.com carried a same-period item attributing its information to Bloomberg, reporting that "Alcatel-Lucent a assigné Fortinet en violation de brevets" before a Delaware court over "sept brevets concernant des solutions de gestion de données" — i.e., seven patents concerning data-management solutions. The two accounts agree on the count (seven) and the court (D. Del.) but diverge in framing: Telecompaper frames the patents as "network security and network management" while Boursier/Bloomberg frames them as "data management solutions," a discrepancy that likely reflects the mixed networking portfolio (firewall, packet-switching, and network-management patents) rather than a real conflict. Both are brief news-brief items with no technical or claim-level analysis.

The only party-side statement I located is Alcatel-Lucent's own announcement, archived on the Telecom Ramblings newswire under the headline "Alcatel-Lucent initiates network security patent infringement litigation against Fortinet and Sophos," dated May 20, 2014. This is a corporate press release rather than independent journalism, and it is the closest thing to an executive statement of intent — it frames the two May 2014 suits as a coordinated "network security" enforcement initiative, which is consistent with the operating-company, portfolio-licensing posture described in the earlier sections. Beyond this, the only substantive public characterization of the matter I could verify is a law-firm bio, not news coverage: the Jenner & Block attorney profile for Amr O. Aly (retrieved and described in the earlier "Defendant representatives" section) states he "served as lead counsel for Alcatel-Lucent in a 24-patent infringement litigation involving patents directed to network security" that "precipitated settlement on very favorable terms." That bio is a self-interested marketing description, and its "24-patent" figure conflicts with the seven-patent figure reported by Telecompaper and Boursier — so it should be treated as an attorney's characterization of an engagement (possibly spanning multiple suits or a broader campaign) rather than a verified case fact.

Where reporting goes beyond or diverges from the court record — and a contradiction to flag. No outlet I found reported any damages figure sought or awarded, any settlement amount, any license terms, or any market/financial impact. Fortinet's SEC disclosures are generic: its 10-Q and 10-K risk-factor and legal-proceedings sections discuss IP litigation risk and other named matters (Trend Micro, Enhanced Security Research, Network Protection Sciences) but, in the filings I retrieved, do not name Alcatel-Lucent as a pending matter or as a settlement — meaning there is no public financial disclosure tying this case to a payment. Critically, the earlier "Case overview & background" section asserts that "the parties jointly stipulated to stay the action until Aug. 3, 2015 (D.I. 91)" and "filed a stipulation of dismissal on July 13, 2015 (D.I. 92)," while the separate "Key legal developments" section states the disposition mechanism is unconfirmed and treats the case as running toward the scheduled Sept. 11, 2017 trial. These two prior sections are in direct conflict, and the press record does not resolve it: not one news outlet reported a July 2015 dismissal, which is surprising if a stipulated dismissal of a seven-patent, operating-company suit had occurred (such resolutions are, however, routinely undisclosed and unreported). Given the absence of any primary-source or press confirmation, I would treat the "July 2015 stipulated dismissal" as unverified and the trial-schedule-vs.-closure question as still open. Net assessment: the case is lightly reported at the filing stage and effectively uncovered thereafter, with no damages, settlement, or industry-reaction reporting located in any outlet.

Sources

• Alcatel-Lucent USA Inc. v. Fortinet Inc.
• Fortinet Federal Litigation Filings
• Alcatel-Lucent USA Inc. v. Fortinet Inc. :: Delaware District Court :: Federal Civil Lawsuit No. 1:14-cv-00574, Judge Leonard P. Stark presiding
• Fortinet, Inc. Litigation, Intellectual Property, Attorneys, SEC Filings, and Other Public Records
• Alcatel-Lucent v. Fortinet - 0% found this document useful (0 votes)
• Alcatel-Lucent v. Fortinet
• IN THE UNITED STATES DISTRICT COURT
• ● | On September 9, 2016, litigation against Fortinet Inc
• 1:14-cv-00628 - Alcatel Lucent SAS v. Cyberoam Inc et al.
• In addition to our headquarters, we lease approximately 14,000 square feet of data center space and a total of approximately 72,...
• Methodologies For Calculating FRAND Damages: Part 1 - Law360
• Fortinet, Inc. Litigation, Intellectual Property, Attorneys, SEC Filings, and Other Public Records

I'll research this docket. Let me run several searches in parallel.

Let me pull the docket pages directly and search for the specific attorneys.

Bottom line

I could confirm the plaintiff's Delaware/local counsel of record from the docket activity in Alcatel-Lucent USA Inc. v. Fortinet Inc., No. 1:14-cv-00574-UNA (D. Del.) — Young Conaway Stargatt & Taylor LLP. I could not confirm the identity of Alcatel-Lucent's pro hac vice/lead trial counsel from the sources I was able to retrieve. The public mirrors of the docket I could reach (Justia, PlainSite, the Stanford NPE database, RPX Insight) expose only truncated attorney strings, and I was unable to open the PACER docket sheet itself. I am therefore flagging one confirmed name, one probable additional local name, and a set of names I cannot responsibly attribute. I have not invented anyone.

---

Plaintiff: Alcatel-Lucent USA Inc. (now Nokia of America Corp.)

Docket grounding for John W. Shaw (plaintiff-side filings signed (Shaw, John)):

• Plaintiff's Rule 26(a)(1) initial disclosures (served Jan. 2015).
• Alcatel-Lucent's First Set of Interrogatories (Nos. 1–5) and First Set of Requests for Production (Nos. 1–10) directed to Fortinet.
• Proposed Protective Order submitted by Alcatel-Lucent.
• Joint Proposed Scheduling Order / letter enclosing scheduling order (Dec. 2014), preceding the Jan. 14, 2015 Scheduling Order (Judge Leonard P. Stark: Markman set 12/21/2015; 10-day jury trial set 9/11/2017).

Sources: PlainSite docket mirror (https://www.plainsite.org/dockets/2ismr5wbx/delaware-district-court/alcatellucent-usa-inc-v-fortinet-inc/) and the Justia docket summary (https://dockets.justia.com/docket/delaware/dedce/1:2014cv00574/54849).

---

Attorney-index entries I could not reliably attribute

The Justia attorney index for this docket renders as a truncated list — including, in the snippet I retrieved: "A. John Mancini," "Amr O. ___," "Andrew Russell," "Bryon T. Wasserman," "James L. ___," plus a separate Fortinet-side block. Justia's page format mixes counsel for all parties, and the surnames were cut off in retrieval. So:

• I can say these names appear somewhere in the case's attorney index.
• I cannot say which of them represented Alcatel-Lucent versus Fortinet, or which were lead vs. local, without the PACER docket sheet or the signature blocks of D.I. 1 and the Rule 7.1 disclosure.
• Do not treat any of these as confirmed plaintiff's counsel on my account.

For context only (and not confirmation): Alcatel-Lucent's large patent enforcement campaigns of that era — the Lucent–Gateway and Lucent–Microsoft litigations in S.D. Cal. — were handled principally by Kirkland & Ellis LLP as lead trial counsel, with Delaware counsel used for D. Del. venues. I could not verify that Kirkland (or any specific Kirkland partner) appeared in this Fortinet matter.

---

Defendant-side context (for completeness, so the attorney index isn't misread)

• Bindu A. Palapura (Potter Anderson & Corroon LLP, Wilmington, DE) — signed Fortinet's discovery notices and initial disclosures; effectively Fortinet's local Delaware counsel at the outset.
• A docket entry requesting the Clerk to remove Ryan Tyz as co-counsel appears on this docket; Ryan A. Tyz was a Fenwick & West patent litigator named in Fortinet's outside-counsel records, so this appears to be defense-side counsel rotation. I did not confirm which party he had appeared for in this case.

---

Gaps and caveats (explicit)

1. No sealed-filing issue found. Nothing in the retrievable docket summaries suggests the appearances were sealed; my limitation is retrieval, not sealing.
2. PACER not directly accessible to me. D. Del. 1:14-cv-00574 is a closed/terminated docket (Stanford NPE database lists it as closed; the case was set for trial 9/11/2017, consistent with resolution before or shortly after that date). The attorney list would be complete and definitive on the PACER docket report or in the complaint's signature block.
3. Party naming. Plaintiff is "Alcatel-Lucent USA Inc. (formerly Lucent Technologies, Inc.)"; after the Nokia acquisition the entity is commonly referenced as Nokia of America Corporation. Whether in-house Nokia/Alcatel-Lucent IP counsel appeared on the docket (e.g., as "of counsel") I could not determine.
4. Patent count discrepancy. Press coverage of the May 1, 2014 filing (Telecompaper, Boursier) describes seven patents asserted against Fortinet concerning data-management/network-security technology; your case summary lists three (’438, ’979, ’172). The complaint text (D.I. 1) would resolve this.

Recommended verification steps (all one-step on PACER/CM-ECF): pull the D.I. 1 signature block and the "Attorneys" section of the docket report for 1:14-cv-00574-UNA; also check D.I. 1-1 (Rule 7.1 corporate disclosure) and any pro hac vice motions, which name lead counsel and their firms precisely.

I'll research the docket and counsel appearances for this case.

Let me pull the full docket party/attorney listings.

Let me dig into the docket party listings and specific attorney names.

Bottom line

I could only partially verify counsel for this case. What is well-sourced is the plaintiff side (Alcatel-Lucent), which I confirmed through firm bios and docket entries. For Fortinet's defense team, I was not able to retrieve a document that ties a named attorney to Fortinet in this docket (1:14-cv-00574-UNA). Below I separate what is confirmed from what is unverified, and I flag one attorney whose appearance notice appears on the docket but whose party affiliation I could not resolve.

---

Defendant: Fortinet, Inc.

No defense counsel is confirmed by a source I could verify. Specifically:

• The public aggregator docket pages (Justia, PlainSite, CourtListener) for 1:14-cv-00574 return only fragments of the party/attorney block. The Justia page shows a truncated "Represented By" list of roughly six names — readable fragments are initials/surnames such as "A. ___," "Amr O. ___," "Andrew Russell ___," "John W. ___," "Bryon T. ___," and "James L. ___" (dockets.justia.com/docket/delaware/dedce/1:2014cv00574/54849). The snippet does not preserve which party each name is attached to, so I cannot assign any of these to Fortinet without guessing. I am not naming these attorneys as Fortinet's counsel.

• PlainSite's docket index for the case surfaces one counsel-related event: a "NOTICE requesting Clerk to remove Ryan Tyz as co-counsel" (reason given on the docket image: "no longer with law firm") — https://www.plainsite.org/dockets/2ismr5wbx/delaware-district-court/alcatellucent-usa-inc-v-fortinet-inc/. I could not confirm from the available text whether Mr. Tyz appeared for Alcatel-Lucent or Fortinet, and I could not confirm his firm at the time of appearance. Treat this as a lead only, not a finding.

• I found no notice of appearance, answer, counterclaim signature block, or Rule 7.1 disclosure for Fortinet in this case in any searchable source.

Unverified context (do not treat as confirmed for this docket): Fortinet's Delaware-local patent counsel in its other D. Del. matters has been Morris, Nichols, Arsht & Tunnell LLP (Wilmington, DE) — e.g., Jack B. Blumenfeld and Brian P. Egan appeared for Fortinet in Realtime Data LLC v. Fortinet, Inc., No. 17-1635-CFC (consolidated at No. 17-0800-CFC), as reflected in the court's May 4, 2021 memorandum opinion (https://cases.justia.com/federal/district-courts/delaware/dedce/1:2017cv00800/62386/41/0.pdf). That is a different case, different years, different patents, and I have no evidence it applies to 1:14-cv-00574.

Also worth noting for completeness: Fortinet's current outside patent litigation team (visible in 2025 filings in Skysong Innovations, Inc. v. Fortinet, Inc., No. 2:25-cv-00098-JRG, E.D. Tex.) includes Melissa Richards Smith (Gilliam & Smith LLP, Marshall, TX), with pro hac vice counsel including Lindsay Cooper Hayman, Ryan Iwahashi, John M. Neukom, Andrew Dale Gish, Josef Bryks Schenker, and Christopher Gerson (PTAB/docket reproductions at ptacts.uspto.gov petitions 1558328/1558329). This is a 2025 team and cannot be assumed to be the 2014 team.

---

Plaintiff: Alcatel-Lucent USA Inc. (for contrast, since the docket fragments intermix both sides)

These are the only counsel I could tie to the case with a specific source:

Two honest caveats on the above:

1. The Jenner bio's "24-patent" characterization conflicts with contemporaneous press reporting that the May 1, 2014 Delaware suit asserted seven patents (Telecompaper, "Alcatel-Lucent starts patent suit against Fortinet, Sophos" — https://www.telecompaper.com/news/alcatel-lucent-starts-patent-suit-against-fortinet-sophos--[1015028](/patent/1015028)). The bio may describe a broader or later Alcatel-Lucent/Fortinet engagement, or Aly's current firm may have inherited the description. I did not resolve the discrepancy, and I also could not confirm where Aly practiced in 2014.
2. Whether Shaw was at Young Conaway or already at Shaw Keller in May 2014 is based on my general knowledge of the 2015 founding of Shaw Keller, not on a document from this docket.

Case status note: one aggregator lists 1:14-cv-00574 as "Closed" and confirms it was assigned to Judge Leonard P. Stark (https://ai-lab-cl-prod.azurewebsites.net/case/dct/ded/1:14-cv-00574/alcatel-lucent-usa-inc-v-fortinet-inc), and the Jenner bio indicates a favorable settlement for Alcatel-Lucent. I could not independently confirm the disposition (no opinion or judgment citation surfaced), consistent with the case summary's "outcome not confirmed."

---

What I did not find / what would close the gap

• No Fortinet appearance, answer, or counterclaim document text was retrievable in my searches. The complaint was filed 5/1/2014; the docket shows Fortinet entered the case and filed a stipulation (extension to exchange protective order/initial disclosures) and served initial disclosures as counter-plaintiff (per PlainSite entries), which means a defense team did appear — but the signature blocks are not in any indexable source I reached.
• Sealed or image-only filings are a real possibility; several Delaware filings in this era are PDFs behind PACER's paywall and are not OCR-indexed by the free aggregators.

Recommended next retrieval (definitive): pull from PACER for 1:14-cv-00574 the docket entries for (a) the notice of appearance for defendant Fortinet, Inc., (b) Fortinet's answer/counterclaim, (c) the Rule 7.1 disclosure statement, and (d) D.I. 744-style certificates of service. Those four documents will name Fortinet's lead, local, and any pro hac vice counsel and their firms with certainty. Until then, I decline to name any attorney as Fortinet's counsel of record in this case.