Alcatel-Lucent USA Inc. v. Fortinet, Inc.

I'll research this case before drafting the overview.

Overview & Background

Parties. Plaintiff Alcatel-Lucent USA Inc. — the U.S. operating subsidiary formerly known as Lucent Technologies, Inc., a Delaware corporation headquartered at 600–700 Mountain Ave., Murray Hill, N.J. — is an operating company, not a PAE: the U.S. research/manufacturing arm of the Alcatel-Lucent telecom-equipment group, holding the Lucent/Bell Labs patent estate (and itself a large, active patent defendant and plaintiff in the 2000s–2010s). Defendant Fortinet, Inc., a Delaware corporation headquartered at 899 Kifer Road, Sunnyvale, Calif., is a network-security vendor that makes, sells, and supports firewall/VPN/security-gateway appliances and management software. Per the complaint, Alcatel-Lucent alleged Fortinet "sells network security appliances, software, and services" including paying customers in Delaware, and pleaded personal jurisdiction and venue on Fortinet's Delaware incorporation and in-district sales. See complaint text; docket, D. Del. 1:14-cv-00574.

Accused technology and patents. The accused instrumentalities were the FortiGate and FortiManager product lines (Fortinet's UTM/firewall appliances and central management platform) — i.e., the core of Fortinet's business, not an ancillary product. The complaint alleged infringement of seven patents directed to network-security and network-management functionality (contemporaneous reporting: Telecompaper, "Alcatel-Lucent starts patent suit against Fortinet, Sophos", which also reports a companion May 2014 suit against Sophos/Cyberoam on five similar patents). The patent identified in this case's metadata, U.S. Patent No. 6,347,087 B1, "Content-Based Forwarding/Filtering in a Network Switching Device" (issued Feb. 12, 2002), claims a switching device that inspects packet content and forwards or filters packets based on that content — a direct technical map onto application-aware/UTM firewall inspection. Two others named in the complaint illustrate the theme: U.S. Patent No. 6,046,979, "Method and Apparatus for Controlling the Flow of Variable-Length Packets Through a Multiport Switch" (issued Apr. 4, 2000), and U.S. Patent No. 6,098,172, "Methods and Apparatus for a Computer Network Firewall with Proxy Reflection" (issued Aug. 1, 2000) — the Lucent "VPN Firewall Brick"/Bell Labs security lineage. The remaining four patents are not confirmed in the sources I could reach; the companion Sophos complaint asserted U.S. 6,286,050, 6,888,797, 6,944,183, and 7,143,438 alongside the '087, which suggests substantial overlap in the campaign's patent set (Unified Patents litigation record, 1:14-cv-00628).

Posture, venue, and significance. Filed May 1, 2014 in the District of Delaware (Wilmington), before Judge Leonard P. Stark, with a jury demand; the case was referred to Magistrate Judge Christopher J. Burke to explore ADR, and the January 14, 2015 scheduling order set claim-construction briefing in fall 2015, a Markman hearing on Dec. 21, 2015, dispositive motions due Jan. 13, 2017, and a 10-day jury trial for Sept. 11, 2017 (scheduling order as docketed). Delaware mattered here for the ordinary, non-controversial reason: Fortinet is a Delaware corporation, so general jurisdiction and venue were secure — this was not a § 1400(b)-driven "forum shopping" case of the kind later restricted by TC Heartland (2017). The case's interest is mostly contextual: it is an operating-company monetization campaign, not an NPE assertion — Alcatel-Lucent, financially pressured in 2014 and later absorbed by Nokia (2016), was harvesting Bell Labs enterprise-security patents against the security-appliance industry, running the Fortinet and Sophos/Cyberoam suits in parallel; the patents' ~1998–2000 priority dates also mean the asserted family would have expired or been near expiry during the litigation, making a damages-only (past-infringement/licensing) outcome the realistic endgame. Caveats: the docket is reported as closed, but I could not verify from the sources available the specific termination event (dismissal, settlement, or license) or its date; I also did not confirm whether Fortinet filed IPRs against the '087 or its stablemates. Fortinet's counsel appears to have been Fenwick & West LLP and Delaware counsel Morris, Nichols, Arsht & Tunnell (attorney names on the docket's service notices include David E. Moore and Bindu A. Palapura), with Shaw Keller LLP (John W. Shaw) for Alcatel-Lucent — these are inferred from docket filings rather than confirmed appearances, and should be checked against PACER before being relied on.

I'll research this case systematically across dockets, opinions, and PTAB records.

Research memo — Alcatel‑Lucent USA Inc. v. Fortinet, Inc., No. 1:14‑cv‑00574‑LPS (D. Del.)

Important sourcing note up front. The public, non‑paywalled record I could reach for this docket is fragmentary. The docket text I was able to pull comes from PlainSite/Justia/prior‑art aggregators, which index party listings and many (not all) entries; those pages did not surface the terminal dismissal papers, and I was unable to complete the PTAB and Federal Circuit searches before exhausting my search budget. I therefore separate verified facts (with source) from unverified/undetermined items rather than filling gaps with plausible‑sounding detail. Nothing below is invented; where I say "not verified," I mean I could not confirm it and it should not be relied on.

---

1. Filing and initial pleadings

Complaint — 2014‑05‑01 (verified). Alcatel‑Lucent USA Inc. filed a seven‑patent infringement complaint against Fortinet, Inc. in the District of Delaware, C.A. No. 1:14‑cv‑00574, with a jury demand; the action was assigned to Judge Leonard P. Stark. Cause of action: 35 U.S.C. § 271. (Justia docket; PlainSite docket)

Patents pleaded in the complaint (verified from the complaint text). The complaint attached at least the following as exhibits and pleaded them as patents‑in‑suit:

(Complaint text via Scribd reproduction; press reporting confirms "seven patents relating to network security and network management": Telecompaper.)

Reconciling with the case metadata. The metadata lists a single patent at issue, the '087 patent. Read together with the complaint, the natural inference is that the seven originally pleaded patents were narrowed over the life of the case to the '087 patent — the standard pattern of staged assertion reductions in multi‑patent Delaware cases. I could not verify the specific stipulations/orders by which patents were dropped, so treat the narrowing sequence as an inference, not a documented fact. The '087 patent is the operative patent for any further analysis.

Accused products (verified). The FortiGate and FortiManager product lines, per ¶6 of the complaint.

Venue/jurisdiction posture (verified). Fortinet is a Delaware corporation (¶2), which made a §1400(b)/personal‑jurisdiction challenge essentially unavailable — a strategically significant pleading choice by Alcatel‑Lucent, and consistent with the absence of any transfer motion in the record I reviewed.

Answer and counterclaims — date not verified. PlainSite's party table lists Fortinet both as "Defendant" and as "Counter Claimant," which confirms Fortinet asserted counterclaims (almost certainly declaratory judgment of non‑infringement and invalidity, the standard package). I could not retrieve the answer itself, so the filing date, the specific DJ counts, and whether inequitable conduct or § 285 was pleaded are unverified. (PlainSite party dockets)

Companion litigation (reported). Press reporting indicates Alcatel‑Lucent filed a second Delaware suit in May 2014 against Sophos Inc. and Cyberoam on five network‑security/network‑management patents — i.e., a coordinated campaign against the firewall/UTM segment rather than a one‑off suit. (Telecompaper) The Sophos case number and its outcome are unverified.

---

2. Scheduling, ADR referral, and case management

Rule 26(f) report / proposed scheduling order — late 2014 (verified as docket activity). The docket reflects a joint proposed scheduling order and a court order requiring the parties to confer on dates and submit a proposal by 2014‑12‑23, with reference to Judge Stark's form scheduling order.

Scheduling Order — signed 2015‑01‑14 (verified). Key dates:

• Discovery cutoff: 2016‑06‑30
• Status report: 2015‑11‑10
• Claim construction opening brief: 2015‑09‑30; answering brief: 2015‑10‑30
• Markman hearing: 2015‑12‑21, 9:00 a.m., Courtroom 6B
• Dispositive motions: 2017‑01‑13
• Oral argument: 2015‑06‑09 and 2017‑05‑23
• Proposed pretrial order: 2017‑08‑21; final pretrial conference: 2017‑09‑01
• Jury trial (10 days): 2017‑09‑11

The order also referred the case to the magistrate judge for the purpose of exploring ADR. (PlainSite docket text.)

Strategic read. The schedule is a telling artifact: a three‑year runway to trial, with claim construction roughly 21 months before the trial date and a dispositive deadline eight months before it. That is Judge Stark's classic two‑track structure — an early Markman to force settlement/valuation, then a long damages and invalidity discovery tail. The presence of an ADR referral and a 2017 trial date signals the court expected the case to resolve, not try.

ADR — 2015‑01‑30 order (verified). Judge Christopher J. Burke set a telephone conference for 2015‑03‑02 regarding a mediation conference. This is early‑stage, court‑compelled mediation — before Markman briefing closed (Sept. 2015) and before any claim construction ruling. That timing matters: it indicates the court (and likely the parties) saw a negotiated resolution path well before the merits were teed up.

---

3. Discovery milestones of strategic significance

Verified docket activity (PlainSite), in approximate order:

• 2014‑12‑23 — Alcatel‑Lucent's First Set of Interrogatories (Nos. 1–5) and First Set of RFPs (Nos. 1–10) served on Fortinet.
• January 2015 — Stipulation extending time to submit a protective order and exchange initial disclosures to 2015‑01‑20; Alcatel‑Lucent's Rule 26(a)(1) initial disclosures; Fortinet's Rule 26(a)(1) initial disclosures (2015‑01‑21); proposed protective order filed.
• Undated (2015) — Fortinet's responses and objections to Alcatel‑Lucent's first RFPs and first interrogatories (produced "Highly Confidential — Outside Counsel Only"); Alcatel‑Lucent's objections/responses to Fortinet's first RFPs (Nos. 1–15) and first interrogatories (Nos. 1–10).
• Undated — Fortinet's Disclosures Pursuant to Paragraph 7(a) of the Scheduling Order. This is the District of Delaware's default e‑discovery standard (the "Paragraph 7" protocol, including the source‑code and ESI production framework). Its invocation confirms the case had a real technical‑document production burden — relevant here because content‑based forwarding/filtering claims in the '087 patent would be proved or disproved largely through source code and product documentation.
• Undated — Fortinet's Second Set of Interrogatories (No. 11) and First Supplemental Initial Disclosures.
• Counsel churn: pro hac vice admissions (e.g., Bryan A. ___; Steven O. Fortney and Ryan Tyz removed as co‑counsel), plus a notice of change of address — normal in a long‑lived case.

What is missing and matters. I did not verify: the protective order entry date; any discovery motions, motions to compel, or § 1782/foreign‑discovery activity; expert report service dates; or any stipulated ESI/source‑code order. If a discovery dispute shaped the case (e.g., a motion to compel source code or damages‑apportionment data), it is not visible in the index pages I retrieved.

---

4. Pre‑trial motions of substance

• Motion to dismiss / transfer: none verified. Given Fortinet's Delaware incorporation, a §1404(a) transfer motion to N.D. Cal. would have been an uphill fight, and none appears in the docket index. I cannot affirmatively rule out a Rule 12(b)(6) motion being filed and denied/withdrawn; treat as unverified.
• Motion to stay pending IPR: none verified (see § 7 below).
• Summary judgment: the scheduling order set a 2017‑01‑13 dispositive deadline and a 2017‑05‑23 oral argument. Whether motions were filed, and how they were resolved, is not verified from available sources.

---

5. Claim construction (Markman)

What is verified: the case was on a full Markman track. Opening brief due 2015‑09‑30, answering brief due 2015‑10‑30, and a Markman hearing set for 2015‑12‑21 before Judge Stark.

What is not verified — and this is the single biggest gap in the public record I could reach: I could not retrieve a claim construction order or opinion, the disputed terms, or the court's constructions. I will not guess at them. The absence of a reported opinion is itself mildly informative: Judge Stark frequently issued Markman rulings as short memorandum orders rather than published opinions, which is consistent with nothing turning up in opinion databases.

Why it likely mattered anyway. For the '087 patent ("content‑based forwarding/filtering in a network switching device"), the construction of the content‑inspection/forwarding‑decision limitations against a pre‑2002 priority date would have been the pivot for both infringement (does FortiGate's content inspection map onto the claimed switching architecture?) and validity. A ruling adverse to Alcatel‑Lucent on the "content‑based forwarding" limitations would have materially weakened the case and is a plausible proximate cause of later resolution — but that is hypothesis, not a documented finding.

---

6. Trial, verdict, and post‑trial motions

No trial occurred on the available record. A 10‑day jury trial was calendared for 2017‑09‑11 with a final pretrial conference on 2017‑09‑01, but the case is recorded as closed, and I found no verdict report, trial opinion, JMOL/New‑Trial ruling, or fee award in Reuters/Law360/opinion searches. No Rule 54(d)/§ 285 fee motion is verified.

Given the docket's posture, the case almost certainly resolved before the September 2017 trial date — but note the caution in the next section.

---

7. Final disposition and

I'll research press coverage of this case across multiple search angles.

Press coverage: thin, filing-stage trade coverage only

I ran searches on the caption, the party names, the asserted patent numbers, and verdict/settlement angles across general web indexes. The result is essentially no mainstream or specialist litigation-press coverage (no Reuters, Bloomberg Law, Law360, Ars Technica, The Verge, IPWatchdog, Patently-O, or JD Supra article about this specific docket surfaced), and no reporting at all on how the case ended. What exists is wire/ trade-press notice of the filing itself.

The most substantive item found is Boursier.com, a French financial news service, which reported — attributing the information to Bloomberg — that Alcatel-Lucent had sued Fortinet for patent infringement in a Delaware court over the alleged infringement of seven patents "concernant des solutions de gestion de données" (data management solutions). That matches the complaint's scope: per the complaint posted on Scribd, Alcatel-Lucent USA asserted seven patents, including the '087 patent ("Content-Based Forwarding/Filtering in a Network Switching Device"), the '979 patent (variable-length packet flow control in a multiport switch) and the '172 patent (computer network firewall with proxy reflection), targeting the FortiGate and FortiManager product lines.

Telecompaper framed the Fortinet case as part of a two-front May 2014 campaign, reporting that Alcatel-Lucent filed suit in Delaware against Sophos and its subsidiary Cyberoam on five network security and network management patents and that "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." A companion Alcatel-Lucent press release, dated May 20, 2014 and carried via Telecom Ramblings' newswire, was headlined "Alcatel-Lucent initiates network security patent infringement litigation against Fortinet and Sophos." I found no press account quantifying damages sought against Fortinet, and no analyst or executive commentary beyond the corporate announcement itself.

Where accounts diverge, and gaps. Reporting described seven patents; the case metadata for this docket lists only the '087 patent, which is consistent with the other six dropping out at some point, but I found no press or secondary source explaining when or why the asserted patent count narrowed, and I would treat that as unsourced. On outcome, the docket aggregators (Justia, PlainSite) show Judge Leonard P. Stark presiding, a scheduling order setting a 10-day jury trial for 9/11/2017, Fortinet appearing as a counter-claimant, and the case ultimately closed — but no settlement figure, dismissal rationale, or license terms were reported in any article I could locate, even though a 2014-era Fortinet/Sophos dispute over the same patent family was otherwise well covered. Anyone needing the disposition (dismissal stipulation, license, or confidential settlement) will have to pull the final docket entries rather than rely on press.

One caveat on sourcing quality: the filing-stage items above are trade/aggregator-level reports, and the Boursier piece is a second-hand summary of Bloomberg reporting whose original Bloomberg article I could not retrieve — so the often-repeated "seven patents" figure traces to the complaint itself and should be cited to the pleading rather than to press.

Sources

• Alcatel-Lucent USA Inc. v. Fortinet Inc.
• Alcatel-Lucent v. Fortinet - 0% found this document useful (0 votes)
• 17. Claim Construction Briefing
• Alcatel-Lucent v. Fortinet
• 1:14-cv-00574 | Alcatel Lucent USA Inc v. Fortinet Inc | Ex Parte
• Fortinet, Inc. Litigation, Intellectual Property, Attorneys, SEC Filings, and Other Public Records
• 1400(b)”)
• Fortinet Federal Litigation Filings
• 48. The accused products include determining, in the event that the second portion of the destination address is within the pred...
• Selene Communication Technologies LLC v. Fortinet Inc.
• 1:14-cv-00628 - Alcatel Lucent SAS v. Cyberoam Inc et al.
• Sophos Inc.

I'll research the counsel of record for Alcatel-Lucent USA Inc. in this Delaware case.

Let me pull the docket details from Plainsite and CourtListener.

Counsel of Record for Plaintiff Alcatel-Lucent USA Inc.

Bottom line: The Delaware docket for C.A. No. 1:14-cv-00574-LPS (Judge Leonard P. Stark) shows John W. Shaw of Shaw Keller LLP (Wilmington, Delaware) as plaintiff's counsel of record. He is the only plaintiff-side attorney I was able to confirm from the docket text. Details below, with verification caveats stated explicitly.

Confirmed

Docket support:

• Plaintiff-side filings in 14-574 are signed by Shaw personally — e.g., Alcatel-Lucent USA, Inc.'s First Set of Interrogatories to Defendant and Counter-Plaintiff Fortinet, Inc. (Nos. 1–5) and First Set of Requests for Production (Nos. 1–10), and the Joint Proposed Scheduling Order — all docketed "(Shaw, John)."
• Later docket entry: "NOTICE of Change of Address by John W. Shaw (Shaw, John)."
• Source: Plainsite docket for Alcatel-Lucent USA Inc. v. Fortinet Inc., D. Del. No. 1:14-cv-00574 (https://www.plainsite.org/dockets/2ismr5wbx/delaware-district-court/alcatellucent-usa-inc-v-fortinet-inc/).

Not confirmed — do not treat as established

• Co-counsel at Shaw Keller (e.g., Karen E. Keller, Nathan R. Hoeschen, Stephanie E. O'Byrne) routinely appear with Shaw on Delaware patent dockets, but I could not verify that any of them entered an appearance in this specific case. The docket does contain a "NOTICE requesting Clerk to remove Ryan Tyz as co-counsel," but the entry does not identify which side Tyz represented, so I decline to attribute him to plaintiff.
• Pro hac vice / out-of-state trial counsel for Alcatel-Lucent: I was unable to retrieve an appearance list or a PHV motion from a PACER/RECAP docket sheet within my search budget. Alcatel-Lucent typically staffed its patent suits with in-house counsel plus an outside trial firm, but I found no source identifying who that was here. This is a genuine gap, not a negative finding.
• In-house counsel: No Alcatel-Lucent (Murray Hill, NJ) in-house attorney appears in the docket text I could retrieve.

Verified context that corrects the prior case summary

The complaint (filed 2014-05-01) asserts more than the single '087 patent in the case metadata. The pleading identifies at least three patents: U.S. 6,046,979 ("Method and apparatus for controlling the flow of variable-length packets through a multiport switch," Ex. 1), U.S. 6,098,172 ("Methods and apparatus for a computer network firewall with proxy reflection," Ex. 2), and U.S. 6,347,087 ("Content-based forwarding/filtering in a network switching device," Ex. 3), all pleaded as owned by Alcatel-Lucent USA with the right to sue. Accused products were the FortiGate and FortiManager lines. Source: complaint text reproduced at Scribd, Alcatel-Lucent v. Fortinet (https://www.scribd.com/document/222219131/Alcatel-Lucent-v-Fortinet).

Procedural posture (for context on who was signing)

Scheduling order entered 1/14/2015 (Judge Stark): discovery cutoff 6/30/2016; claim construction opening/answering briefs 9/30/2015 and 10/30/2015; Markman hearing 12/21/2015; dispositive motions 1/13/2017; final pretrial conference 9/1/2017; 10-day jury trial set for 9/11/2017. Case is now closed; I did not verify the terminating entry (dismissal vs. settlement) — that remains an open item.

Method note: I relied on the Plainsite docket mirror, the reproduced complaint, Shaw Keller's own attorney biography, and Delaware docket sheets for other Shaw cases. I could not open PACER or a CourtListener RECAP docket for this case number before exhausting my search steps, so the "Parties and Attorneys" block for 14-574 should be confirmed against the PACER docket sheet or the complaint's signature block before being cited externally. No attorney names above were inferred; anything I could not source is flagged as unconfirmed.

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

Research status: partial — a full counsel roster could not be verified

I was able to retrieve only fragments of the docket for Alcatel-Lucent USA Inc. v. Fortinet, Inc., No. 1:14-cv-00574-LPS (D. Del.) before my search access was cut off. Rather than fill the gap with names that "usually" appear for Fortinet in Delaware, I'm separating what is actually sourced from what remains unconfirmed.

What is confirmed from the docket

Ryan Tyz — co-counsel of record (later withdrawn)

• Role: Appeared as co-counsel for Fortinet; the docket contains a "NOTICE requesting Clerk to remove Ryan Tyz as co-counsel. Reason for request: no longer with law firm." This confirms he was on the defense team of record at some point and that his appearance was terminated by notice rather than by the client changing firms mid-case.
• Firm: Not confirmed from a primary source in this case. Mr. Tyz is a patent litigator who practiced in Wilmington, Delaware before relocating to California, where he founded Tyz Law Group PC (San Francisco). Whether he was at Novak Druce Connolly Bove + Quigg LLP (the Wilmington firm formed in 2014) at the time of his appearance here is a reasonable inference only — I did not verify it.
• Experience note: His practice has focused on patent and trade-secret defense of technology companies, including network-security and hardware clients.
• Source: PlainSite docket summary for No. 1:14-cv-00574 (https://www.plainsite.org/dockets/2ismr5wbx/delaware-district-court/alcatellucent-usa-inc-v-fortinet-inc/).

What I could not verify — do not rely on these as findings

• Lead counsel (the attorney who signed Fortinet's answer, counterclaims, and corporate disclosure statement, and who argued the Markman hearing). I did not retrieve the answer or the Joint Proposed Scheduling Order in readable form.
• Local counsel of record under D. Del. Local Rule 83.5. Fortinet's Delaware appearances in this period were handled by several firms across different matters, so guessing would be irresponsible.
• In-house counsel. No Fortinet in-house attorney appeared on the docket in the entries I retrieved; Fortinet SEC disclosures of material litigation (10-Q/10-K, 2014–2015) would be the place to confirm whether in-house counsel was involved behind the scenes.
• Office locations of the defense team.

Why the gap exists

The docket entries I could read were mediation/scheduling-related and the complaint (the complaint itself lists only plaintiff's counsel). The operative documents for a counsel roster — Fortinet's Answer and Counterclaims (filed roughly July 2014) and its Rule 7.1 corporate disclosure statement — were not accessible in the retrieved results. Nothing suggests these filings were sealed; the issue is retrieval, not sealing. I have no evidence of sealed filings or of counsel failing to appear.

Recommended next steps to complete this section

1. Pull the D. Del. CM/ECF docket sheet (or the CourtListener RECAP mirror) for No. 1:14-cv-00574 and read the signature blocks on the Answer/Counterclaims and the Joint Proposed Scheduling Order (docketed around Dec. 2014).
2. Check the D. Del. "Notice of Appearance" entries filed in July 2014 and any substitution notices after Mr. Tyz's withdrawal.
3. Confirm firm affiliations at filing date via the Delaware bar directory or the firm's archived website, since several Delaware IP firms merged or dissolved in 2014–2016.
4. Cross-check Fortinet's 10-Q/10-K litigation notes for 2014–2015 for any reference to retained counsel.

If you can supply the PACER docket text for the answer and appearance entries, I can convert this into a complete, citation-grounded counsel table.