Untitled case

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

Let me refine with more targeted searches on the specific patent and case.

Good — I've identified the case. Let me verify the parties, patent, and outcome.

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

Parties. This is an operating-company-versus-operating-company patent suit, not an NPE/PAE case. The plaintiff, Alcatel-Lucent USA Inc., was the U.S. operating subsidiary of Alcatel-Lucent (the Franco-American telecom equipment maker); it is a telecom/network infrastructure vendor and a long-time repeat player in the District of Delaware, and its U.S. patent-holding entity was reorganized as Nokia of America Corporation after Nokia's 2016 acquisition of Alcatel-Lucent. The defendant, Fortinet, Inc., is a publicly traded cybersecurity vendor headquartered in Sunnyvale, California (best known for its FortiGate firewall/UTM product line) and appears in the docket both as defendant and as "Defendant and Counter-Plaintiff," meaning it asserted invalidity/non-infringement counterclaims. So the case pits two practicing network-technology companies against each other, with a large incumbent equipment vendor monetizing an internal patent portfolio against a security-appliance challenger — a 2014-era variant of the "incumbent vs. disruptor" assertion pattern rather than a shell-company shakedown (dockets.justia.com; plainsite).

Accused products and patents. The complaint was filed May 1, 2014 as a 35 U.S.C. § 271 action with a jury demand. Contemporary reporting (Bloomberg, as relayed by Boursier) described the suit as asserting seven patents relating to data-management solutions; the docket confirms a substantial claim-construction and discovery program consistent with a multi-patent case (Boursier/Bloomberg). The case metadata supplied for this analysis identifies only U.S. Patent No. 6,098,172 as the patent at issue, and the Google Patents "family litigation" record for that patent lists this very case — but I was not able to verify the '172 patent's title, claim scope, asserted claims, or its one-line technical sketch within this research pass. The only independent trace I found is a PTAB exhibit caption reading "U.S. Patent 6,098,172 ('Coss')," which suggests the named inventor is Coss, but that does not establish subject matter. Bloomberg's "data management" characterization applies to the asserted family as a whole and should not be treated as a verified description of the '172 patent. Treat the technical sketch as unverified — it needs to be confirmed against D.I. 1 and the patent's face before being relied on. The accused instrumentalities are likewise not verified from a primary source, though given Fortinet's product line and the complaint's reference in a related Alcatel-Lucent pleading to "the Fortinet, Inc. FortiGate series firewall products," FortiGate-family security appliances are the most plausible accused products (see the Alcatel-Lucent pleading excerpt referencing FortiGate products at insight.rpxcorp.com).

Procedural posture and venue. Filed in the Wilmington (main) office of the District of Delaware and assigned to Judge Leonard P. Stark, then one of the district's most experienced patent jurists. The scheduling order entered January 14, 2015 set a Markman hearing for 12/21/2015, fact discovery cutoff 6/30/2016, dispositive motions due 1/13/2017, final pretrial conference 9/1/2017, and a 10-day jury trial beginning 9/11/2017; the case was also referred to Magistrate Judge Christopher J. Burke for ADR/mediation in early 2015, and the docket shows completed written discovery on both sides. The docket is now closed, but I found no public opinion, trial verdict, or reported settlement/dismissal order — so the outcome (and whether it ended in license, voluntary dismissal, or judgment) remains unverified and should not be stated as known (plainsite docket). Venue matters here for the standard reasons: both parties are Delaware corporations (Fortinet is Delaware-incorporated; Alcatel-Lucent USA was its Delaware-based U.S. operating entity), making Delaware a natural forum; the District of Delaware in this period was displacing the Eastern District of Texas as the nation's busiest patent venue; and the local rules plus judges like Stark offered tight case management and deep patent experience — attractive to a well-resourced incumbent plaintiff and defensible for a defendant that could not easily transfer away.

Why it is notable. First, it is a good illustration that the 2014 patent wave was not solely NPE-driven: a major network-equipment vendor (then under financial pressure and actively monetizing its portfolio, including via a dedicated licensing operation) litigated its own R&D patents against an adjacent cybersecurity competitor. Second, it sits in the middle of the 2014–2015 D. Del. patent docket that reshaped venue statistics and set the stage for TC Heartland's later effect on where such suits are filed. Third, there is a possible later PTAB/NPE linkage worth flagging: a 2020 Unified Patents PTAB proceeding, Unified Patents, LLC v. Firenet Technologies, LLC, lists "U.S. Patent 6,098,172 ('Coss')" as Unified's Exhibit 1009 (see Patexia docket listing). I could not confirm within this research pass whether the '172 patent was itself the challenged patent, merely cited as prior art, or whether a Firenet entity acquired the Alcatel-Lucent patent — so any NPE-reincarnation narrative should be labeled speculative until the PTAB papers are pulled.

Corrections to the prior summary: the parties are now identified (Alcatel-Lucent USA Inc. v. Fortinet, Inc.), the court/division is the District of Delaware, Wilmington, before Judge Stark, and the patent at issue is US 6,098,172 — but the outcome and the accused products/patent scope remain unverified and should not be asserted as established.

I'll research this case systematically. Let me start with several searches in parallel.

The initial searches were off-target. Let me identify the patent and case directly.

Case 1:14-cv-00574 appears to be Alcatel-Lucent USA Inc. v. Fortinet Inc. Let me confirm and tie it to US 6,098,172.

Bottom line up front

On the case-metadata supplied, D. Del. No. 1:14-cv-00574 is Alcatel-Lucent USA Inc. v. Fortinet Inc. — a patent infringement action filed 2014-05-01 before Judge Leonard P. Stark in Wilmington (35 U.S.C. § 271; jury demand by plaintiff; docket aggregators list the case as closed). I was able to verify the identity of the case, the judge, the filing date, the pleadings/discovery/scheduling events and the case's closed status, but I was not able to retrieve a final judgment, verdict, settlement document, or appeal notice from the sources returned, and I could not independently confirm that U.S. Patent No. 6,098,172 was one of the asserted patents. I flag each of those gaps explicitly below rather than guess.

---

1. Filing and initial pleadings

Caveat on the patent-in-suit: the case metadata (Google Patents "family litigation" linkage for US 6,098,172) ties the '172 patent to this case number. I could not retrieve the complaint or a docket entry listing the asserted patents, so I cannot confirm from a primary source that '172 was among them. For context only: US 6,098,172 (inventor "Coss") appears in the network-security/firewall art — it was used as prior art, Exhibit 1009, in Unified Patents, LLC v. Firenet Technologies, LLC (exhibit dated 2020-03-13) — which is at least consistent with an Alcatel-Lucent v. Fortinet firewall/VPN patent family, but is not proof of assertion in this case. Unverified.

2. Scheduling order and pre-trial framework (verified)

A Scheduling Order was entered 2015-01-14 (D.I. entry signed by Judge Stark), setting:

• Claim Construction Opening Brief — due 2015-09-30
• Claim Construction Answering Brief — due 2015-10-30
• Markman Hearing — set 2015-12-21, 9:00 a.m., Courtroom 6B, before Judge Stark
• Oral Argument — set 2015-06-09, 11:00 a.m.
• Fact discovery cutoff — 2016-06-30
• Status Report — due 2015-11-10
• Case referred to the Magistrate Judge for ADR; a mediation teleconference was set for 2015-03-02 at 10:45 a.m. before Judge Christopher J. Burke (order entered 2015-01-30)
• Dispositive motions — due 2017-01-13
• Oral Argument — set 2017-05-23
• Proposed Pretrial Order — due 2017-08-21; Final Pretrial Conference — 2017-09-01
• 10-day jury trial — set for 2017-09-11, 9:00 a.m.

Source: PlainSite docket text for 1:14-cv-00574 (D. Del. Jan. 14, 2015) — verified.

No motion to dismiss, transfer, or stay-pending-IPR appears in the docket text I retrieved. I cannot affirmatively state that none was filed; I simply did not find one. Treat as not verified either way.

3. Claim construction (Markman)

• A Markman hearing was docketed for 2015-12-21 before Judge Stark (verified above).
• I could not locate a claim construction opinion or order from this case, and no Markman ruling in Alcatel-Lucent v. Fortinet surfaced in my searches. Outcome unverified. This is the single most important gap to close on PACER, because the construction of the '172 claims would have driven any summary-judgment or trial outcome.

4. Discovery milestones of strategic significance (verified, with limited detail)

• 2015-03-02 — court-ordered mediation teleconference before Magistrate Judge Burke (ADR referral), an early signal the parties (or the court) treated settlement as viable.
• 2015-11-10 — status report due mid-discovery.
• 2016-06-30 — fact discovery closed (approximately 25 months after filing — a long runway typical of a multi-patent, multi-accused-product case).
• 2017-01-13 — dispositive motion deadline; whether any SJ motion was in fact filed is unverified.

5. Trial, verdict, post-trial motions

• A 10-day jury trial was calendared for 2017-09-11 (verified).
• I found no record of the trial occurring, no verdict, and no JMOL/new-trial/§ 285 fee motions. Docket aggregators nonetheless list the case as "Closed." That combination is most consistent with resolution before the 2017-09-11 trial date (settlement or voluntary dismissal) — but I want to be explicit that this is an inference, not a verified fact.

6. Final disposition / present posture

• Aggregator status: Closed (AI Lab district-court case record for 1:14-cv-00574: "Alcatel Lucent USA Inc v. Fortinet Inc.", patent owner = operating company, Status: Closed). Verified as to status field only.
• The specific terminating event — settlement, stipulated dismissal, consent judgment, or judgment after trial — is not verified. No Federal Circuit appeal docket for this case appeared in my searches; given the volume of Alcatel-Lucent/Nokia appellate activity, absence of evidence here is weak evidence, not proof.

7. Parallel PTAB (IPR/PGR) proceedings on the asserted patents

• I found no IPR, PGR, or CBM petition challenging US 6,098,172 in my searches. In particular, the PTAB matter that references the '172 patent — Unified Patents, LLC v. Firenet Technologies, LLC — used US 6,098,172 as prior art (Exhibit 1009, 2020-03-13), i.e., '172 was the reference, not the challenged patent. Do not conflate the two. Verified as to the exhibit; "no IPR on '172" is a negative finding.
• Beware a false-positive risk in case-number searching: IPR2018-00574 (ARRIS International PLC v. ChanBond, LLC, involving US 8,984,565) is an unrelated proceeding that shares the "574" digits and has nothing to do with this case.

---

What is verified vs. what you should confirm on PACER

Verified: case identity (Alcatel-Lucent USA Inc. v. Fortinet Inc.), court, case number, judge (Stark), filing date (2014-05-01), § 271/jury demand, seven-patents-asserted (press report only), Fortinet's counterclaims, the full 2015-01-14 scheduling order terms, the 2015-03-02 ADR/mediation referral, and closed status.

Not verified (highest-value PACER pulls):

1. The complaint (D.I. 1) and any amended complaint — to confirm whether US 6,098,172 was in fact asserted and to capture the accused products.
2. Fortinet's answer and counterclaims (invalidity/non-infringement counts; any inequitable-conduct or § 101 challenge).
3. Any motion to dismiss / transfer / stay — none surfaced, but the docket text I retrieved was partial.
4. The Markman transcript/order around 2015-12-21 and the claim construction opinion.
5. The terminating docket entry (settlement order, stipulation of dismissal, or judgment) and any Federal Circuit notice of appeal.
6. A PTAB search on the specific asserted patent numbers once identified.

If you can pull the PACER docket for 1:14-cv-00574 or confirm which of the seven asserted patents is the '172 patent, I can complete the claim-construction, trial, and disposition sections with docket-entry-level citations.

I'll research the plaintiff-side counsel of record for this case.

Now let me find the complaint signature block and any appearances for plaintiff's counsel.

Let me identify the individual attorneys and firms on the plaintiff side.

Research note: my session was cut off mid-search (the search tool returned a step limit), so this section reflects what I could verify plus clearly-labeled open leads. I have not filled any gap with an invented name, firm, or appearance.

Plaintiff representatives — Alcatel-Lucent USA Inc. v. Fortinet Inc., C.A. No. 1:14-cv-00574 (D. Del.)

Sole plaintiff: Alcatel-Lucent USA Inc. (the U.S. operating/patent-holding subsidiary; the complaint pleads that it was "formerly known as Lucent Technologies, Inc.," with a principal place of business at 600–700 Mountain Avenue, Murray Hill, NJ) (complaint text, Scribd copy of D.I. 1).

1. Delaware counsel of record — verified from docket text

2. Additional names on the case's "Represented By" list — aggregator-sourced; side attribution NOT verified

Justia's docket page for this case shows a single blended "Represented By" block — A. John Mancini; Amr O. Aly; Andrew Russell; John W. Shaw; Bryon T. Wasserman; and a truncated "James L. ___" (Justia docket). Because Shaw is confirmed plaintiff-side, and because Fortinet's confirmed local counsel is Bindu Palapura of Potter Anderson (per the same docket), the following are leads toward plaintiff's out-of-state team — but the aggregator block does not separate the parties, so I decline to state these as plaintiff's counsel of record:

I'll start by identifying the case and parties, then dig into counsel.

Let me confirm the patent and pull the docket details.

Confirmed the case: Alcatel-Lucent USA Inc. v. Fortinet Inc., D. Del. No. 1:14-cv-00574 (Judge Stark). Now let me nail down the patent and the defense-side counsel.

Bottom line

Case identified: Despite the "Untitled case" caption in the metadata, docket aggregators confirm that D. Del. No. 1:14-cv-00574 is Alcatel-Lucent USA Inc. v. Fortinet Inc., filed May 1, 2014, assigned to Judge Leonard P. Stark, nature of suit "Patent," and now closed. (dockets.justia.com; plainsite.org)

The only defendant is Fortinet Inc. (single-defendant case; Fortinet also appeared as a counterclaim plaintiff). (plainsite Fortinet profile)

With that said, I have to be candid about verification limits, because this is an older closed case and I could not reach the actual PACER docket sheet or the proof-of-service/notice-of-appearance filings in this session. Below I separate what is docket-sourced from what is name-only/aggregator-sourced.

---

Defense side — Fortinet Inc.

The last five names come from the truncated "Represented By" block on the Justia docket page for this case (dockets.justia.com). Important caveat: that aggregator block does not cleanly separate the two sides. I was able to confirm that at least one name in the same listing — John W. Shaw (Young Conaway Stargatt & Taylor, Wilmington) — is plaintiff-side counsel, because he is the filer of record on "Alcatel-Lucent USA, Inc.'s First Set of Interrogatories … filed by Alcatel-Lucent USA Inc. (Shaw, John)." That means the Justia list is a blended list, and I therefore decline to attribute Mancini, Wasserman, Aly, Russell or "James L." to Fortinet. I am flagging them as leads to verify against PACER, not as findings.

In-house counsel: No indication in anything I retrieved that Fortinet in-house counsel entered an appearance of record. I also cannot rule it out.

---

Plaintiff side (for contrast / to avoid misattribution)

• John W. Shaw — Young Conaway Stargatt & Taylor LLP, Wilmington, DE — plaintiff-side filer of record (plainsite docket).
• Alcatel-Lucent USA Inc. was the sole plaintiff.

---

Case context that bears on counsel identification

• Filed May 1, 2014 against Fortinet on seven patents; a companion suit was filed the same month against Sophos/Cyberoam on five patents, all described as network-security and network/data-management patents. (Telecompaper; Boursier)
• The scheduling order set Markman for 12/21/2015, fact discovery to 6/30/2016, dispositive motions to 1/13/2017, and a 10-day jury trial for 9/11/2017 — the case closed before trial. (plainsite docket)
• Patent 6,098,172 caveat: I could not verify from the pleadings that U.S. 6,098,172 was among the seven patents asserted in this action. The only occurrence of that patent number I could retrieve in connection with this period is as a prior-art exhibit in an unrelated PTAB matter (Exhibit 1009, "U.S. Patent 6,098,172 ('Coss')," in Unified Patents IPR2020-00471), which does not establish it as a patent-in-suit here. Given the metadata instruction, I am treating 6,098,172 as the patent of record for this case, but that identification should be confirmed against the complaint (D.I. 1) before it is relied on.

---

What I could not do, and why it matters

1. PACER was not directly accessible in this session, and the case is old enough that the free RECAP/CourtListener docket for 1:14-cv-00574 did not surface the notice-of-appearance, pro hac vice motions, or the proof of service / Rule 7.1 disclosure that would authoritatively list each side's full team.
2. Because of that, the lead counsel identity and the out-of-state firm for Fortinet are not established here. The reliable, citable Fortinet-side fact I have is Bindu A. Palapura appearing for Fortinet in Delaware, plus the later withdrawal of Ryan Tyz as co-counsel.
3. If you need the definitive roster, the documents to pull are: the notice of appearance / pro hac vice motions for Fortinet, Fortinet's Answer and Counterclaims signature block, the Rule 26(a)(1) disclosures and Rule 7.1 corporate disclosure, and the protective order signature blocks — all of which will name lead and local counsel with firms and addresses. I have not fabricated any attorney, firm or address to fill those gaps.