Untitled case

I'll verify the parties, patents, and procedural posture for this case before drafting the overview.

Case overview & background

Correction and build-out of the earlier sections. The prior "Key legal developments" section correctly flagged that the docket was unretrieved; the plaintiff and defendant sections then established the caption, and the searches run for this section now confirm and extend that record. The case is Alcatel-Lucent USA Inc. v. Fortinet, Inc., C.A. No. 1:14-cv-00574 (D. Del.), filed May 1, 2014, Wilmington office, before Judge Leonard P. Stark, nature of suit "Patent," cause of action 35 U.S.C. § 271, jury demanded by plaintiff (Justia docket; Plainsite docket). One contradiction with the case metadata must be flagged: the metadata describes this case as involving US 6,888,797 only, but the complaint as filed asserted seven patents, of which the '797 patent was Exhibit 4. The '797 patent is therefore one strand of a multi-patent assertion, not the whole case.

The parties. Both sides are operating companies — this is not an NPE/PAE case in the classic sense. Plaintiff Alcatel-Lucent USA Inc., "formerly known as Lucent Technologies, Inc.," is a Delaware corporation with its principal place of business at 600–700 Mountain Avenue, Murray Hill, New Jersey — the historic Bell Labs site — i.e., the U.S. operating/patent-holding arm of the telecommunications equipment maker Alcatel-Lucent (which completed its merger into Nokia in 2016; the U.S. entity is now Nokia of America Corporation). Defendant Fortinet, Inc. is a Delaware corporation headquartered at 899 Kifer Road, Sunnyvale, California, and, per the complaint, "sells network security appliances, software, and services" (Compl. ¶¶ 1–2, as reproduced at Scribd). So the alignment is legacy telecom/R&D patent portfolio (Lucent/Bell Labs) versus a cybersecurity vendor — a monetization assertion by a large operating company against a then-fast-growing security appliance maker, not a shell-plaintiff campaign.

The accused technology and the patents. The complaint targets Fortinet's FortiGate (firewall/VPN appliances) and FortiManager (centralized management) product lines, alleging that Fortinet "ships, distributes, offers for sale, sells, and/or advertises" them in the United States and in Delaware (Compl. ¶ 6). The asserted families cluster around packet handling, firewall/proxy architecture, policy management, and load balancing — core functions of an enterprise security appliance. The patents I could verify from the complaint text are:

The complaint recites seven patents in total; I retrieved the identities of these five and could not confirm the remaining two from the sources available, so I am not naming them. The patents' common provenance is Lucent/Bell Labs, with the '797 patent (inventors Zhirou Cao and Zheng Wang; filed May 5, 1999; issued May 3, 2005) naming Lucent Technologies as assignee of record (Google Patents).

Procedural posture and venue. The case was assigned to Judge Stark, one of Delaware's patent-heavy Article III judges, and the January 14, 2015 scheduling order set an aggressive, conventional D. Del. track: claim construction opening briefs 9/30/2015, answering briefs 10/30/2015, a Markman hearing on 12/21/2015, fact discovery closing 6/30/2016, dispositive motions 1/13/2017, final pretrial conference 9/1/2017, and a 10-day jury trial set for 9/11/2017, with the case referred to a magistrate judge (Judge Christopher J. Burke) for ADR and mediation (Plainsite docket, quoting the 1/14/2015 Scheduling Order). Fortinet counterclaimed and litigated hard on non-infringement/invalidity plus equitable defenses — its sealed motion for summary judgment of laches and implied license (D.I. 42) was filed in April 2015, with an answering brief due 4/20/2015. Fortinet's defense team is now confirmed (correcting the earlier "unattributed" names in the defendant section): Morris, Nichols, Arsht & Tunnell LLP in Wilmington (Bindu A. Palapura, David E. Moore) as Delaware counsel, with Fenwick & West LLP as national counsel (Steven O. Fortney, later removed as co-counsel "no longer with the firm," and Bryan A. Kohm, admitted pro hac vice). Delaware was the natural forum: both companies are Delaware corporations, Fortinet sells into the district, and D. Del. was the default venue for Lucent/Alcatel-Lucent portfolio assertions given the company's long-standing local-counsel relationships.

Why it is notable — and what remains unverified. The case is a useful specimen of the 2013–2014 wave of operating-company patent monetization in network security: Alcatel-Lucent filed against Fortinet and, on the same day, against Sophos on the same seven patents (per Telecompaper), i.e., a coordinated campaign against security-appliance vendors rather than a one-off suit. The technology at issue — hashing-based load balancing and content-based forwarding — goes to functions (ECMP/load distribution, policy objects, proxy-reflected firewalls) that are now standard in data-center and cloud-security infrastructure, which is why the '797 patent in particular has salience beyond this case. I found no PTAB IPR/PGR on the '797 patent and no Federal Circuit appeal in the material retrieved, but those are negative results from a limited search, not confirmations. Critically, the disposition is still not verified: the docket aggregators list the case as "Closed", and nothing retrieved shows a trial or verdict, which strongly suggests resolution (settlement or dismissal) before the September 2017 trial date — but I have no dismissal order, stipulation, or settlement announcement in hand, so the earlier section's caveat on outcome should continue to stand. The fastest close-out remains pulling the terminal docket entry for 1:14-cv-00574 from PACER/RECAP, plus a check of Nokia's and Fortinet's 10-K/10-Q litigation footnotes for the 2016–2017 periods.

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

Let me dig into the patent's ownership and litigation history.

Research limitation — read first

I was unable to retrieve the actual docket for C.A. No. 1:14-cv-00574 (D. Del.). My searches surfaced the patent's identity and provenance, but not the complaint, docket entries, Markman order, verdict, or disposition for this specific case, and not any PTAB proceeding keyed to this patent. I also hit a hard cap on search steps before I could run targeted PACER/CourtListener/PTAB queries.

Per my operating rules, I will not fabricate party names, attorneys, dates, or rulings. So rather than invent a chronology, below is (A) what I could verify, (B) the requested checklist with an explicit verification status for each item, and (C) exactly where the missing pieces should be confirmed. This should be read as a correction/supplement to the earlier "Case overview & background" section, which correctly flagged that the narrative elements were unverified.

A. Verified anchor facts

• Patent: U.S. Patent No. 6,888,797 B1, "Hashing-based network load balancing." Abstract: a hashing-based router/method that computes a hash value from header data of incoming packets and routes them to permissible output links in desired loading proportions.
• Assignee of record at grant: Lucent Technologies Inc. (successor-in-interest chain runs through Alcatel-Lucent / Nokia). Inventors: Zhirou Cao and Zheng Wang. Filed 1999-05-05; granted 2005-05-03. Sources: https://patents.google.com/patent/US6888797B1/en and https://golden.com/wiki/US_Patent_6888797_Hashing-based_network_load_balancing-JKP58Y6
• Case-number inference (not confirmation): The 1:14-cv-00574 number places the filing in 2014 in the District of Delaware. That is an inference from the numbering convention only — I could not confirm the filing date from a docket entry. Note also a possible metadata mismatch: the case number format I was handed ("1:14-cv-00574") is not the format Delaware uses on its own dockets (Delaware civil numbers are typically "C.A. No. 14-574-XXX"). I flag this because it may indicate the number was normalized by an aggregator rather than taken verbatim from PACER.

B. Requested checklist — verification status

C. Where the missing pieces live (recommended verification path)

1. The docket itself. Pull 1:14-cv-00574 from PACER or CourtListener/RECAP (courtlistener.com/?q=…, filter D. Del.). The full docket sheet will give the complaint date, all motion entries (D.I. numbers), the Markman order, and the terminal entry (dismissal/stipulation/judgment), which is the fastest way to fill the entire table above.
2. Google Patents "Litigation" / "Similar Documents" trail. The case number in the case metadata evidently originated from the Google Patents record for US6888797B1. The Google Patents litigation tab (and its underlying source, often Unified Patents' "Portal" or RPX/Insulex data) will name the plaintiff/defendant pair; cross-check those names against the PACER docket rather than trusting the aggregator.
3. PTAB. Search the USPTO Patent Trial and Appeal Board end-to-end review system (developer.uspto.gov / PTAB API) for the '797 patent number and for the case caption once the parties are known. Because the '797 patent issued in 2005 and this case was filed in 2014, an IPR would have been possible (IPR became available 2012-09-16); a pre-AIA inter partes reexamination is also possible and should be checked in the patent's file wrapper and in the Google Patents "Also published as / Legal events" panel.
4. Counsel and outcome. Once the caption is confirmed, D. Del. opinions are on courtlistener.com and often summarized by Law360 / IPWatchdog / Patently-O; check the Federal Circuit site for any appeal.

What I can responsibly conclude

There is a real, identifiable patent behind this case (Lucent's '797 hashing/load-balancing patent), and the case number points to a 2014 Delaware filing — but I cannot state a single date, ruling, party name, or outcome for C.A. No. 1:14-cv-00574 without a docket source, and I have not found one. I recommend the previous section's caveat stand, and that this section be updated once the PACER/CourtListener docket and the PTAB record are pulled. If you can supply the docket text or the party caption, I can build the full chronological treatment (pleadings → motions → Markman → trial/post-trial → disposition, plus any parallel IPR) immediately.

I'll research this case and its counsel. Let me start with several searches.

Now I have the case identity. Let me find the docket and counsel.

Let me get the full docket sheet and identify the plaintiff's counsel of record.

Counsel of Record — Plaintiff Alcatel-Lucent USA Inc.

First, the case identity (resolving the earlier "unverified" narrative): C.A. No. 1:14-cv-00574 (D. Del.) is Alcatel-Lucent USA Inc. v. Fortinet, Inc., filed May 1, 2014, assigned to Judge Leonard P. Stark, nature of suit = Patent, cause of action 35 U.S.C. § 271, jury demanded by plaintiff. That is consistent with the Google Patents link to the '797 patent (U.S. 6,888,797, "Hashing-based network load balancing"), which was among the patents asserted. The complaint itself as filed recited at least U.S. 6,046,979 and 6,098,172 (and reporting at the time said Alcatel-Lucent asserted seven patents against Fortinet). So the prior summary's "parties… could not be verified" should be corrected: plaintiff = Alcatel-Lucent USA Inc. (now Nokia of America Corporation); defendant = Fortinet, Inc. These should be treated as authoritative per the case metadata.

Plaintiff's counsel

Grounding: The Plainsite docket for this case shows plaintiff-side filings signed "(Shaw, John)" — e.g., Alcatel-Lucent USA, Inc.'s First Set of Interrogatories to Defendant and Counter-Plaintiff Fortinet, Inc. (Nos. 1–5) and the corresponding First Set of Requests for Production "filed by Alcatel-Lucent USA Inc..(Shaw, John)," together with the plaintiff's proposed protective order and joint proposed scheduling order. Justice/Justia's case page for 1:2014cv00574 likewise lists counsel including "John W…" among those appearing. Young Conaway's Wilmington address and Shaw's Bar No. 3362 are corroborated by his signature blocks in the related Lucent/Telcordia Delaware dockets (e.g., 1:04-cv-00875 and D. Del. 1:04-cv-00907-cases, D.I. 238, D.I. 297).

Counsel whose party affiliation I could NOT confirm (flagging explicitly)

The Plainsite docket also reflects two "NOTICE requesting Clerk to remove [X] as co-counsel" entries — one for Steven O. Fortney and one for Ryan Tyz. The snippets I retrieved do not state which side they appeared for, and I could not confirm whether they were plaintiff's or Fortinet's counsel. Do not treat these as plaintiff's counsel without checking the docket images.

The Justia party page for this case lists a set of names under "Represented By" (A. John Mancini; Amr O. Aly; Andrew Russell; Bryon T. Wasserman; a "James L.___"), but that page does not cleanly attribute the list to plaintiff versus defendant, and the list looks like the defense side (Fish & Richardson–associated names such as Amr Aly/Andrew Russell regularly represented Fortinet). I am not asserting any of them as plaintiff's counsel.

What I could not verify

• No non-Delaware / pro hac vice plaintiff's counsel could be confirmed. In Alcatel-Lucent's patent suits of this era the company typically used its in-house IP litigation group plus a national firm admitted pro hac vice alongside Delaware local counsel. I could not retrieve the pro hac vice motions (which would name any national counsel) or the complaint's signature block within my search budget, so I will not name any such attorney.
• In-house counsel: Alcatel-Lucent maintained an in-house IP litigation team (the company is now Nokia of America Corp., and in later PTAB matters its in-house signatory of record was Margaret G. Yulos, Secretary). Whether in-house counsel entered an appearance in this case is not confirmed.

Recommended next step to close the gaps

Pull the full docket from PACER/RECAP (D. Del. 1:14-cv-00574) and check: (1) the complaint signature block (D.I. 1), (2) any motions for leave to appear pro hac vice and the accompanying pro hac vice orders (these name national counsel), and (3) the two "notice requesting Clerk to remove co-counsel" entries to confirm which party Fortney and Tyz represented. The case is closed (Judge Stark; scheduling order set discovery to 6/30/2016 and a 9/11/2017 trial date), so the docket should be complete.

Bottom line: The only plaintiff's counsel I can confirm by name from the sources retrieved is John W. Shaw of Young Conaway Stargatt & Taylor LLP (Wilmington, DE) as lead Delaware counsel of record for Alcatel-Lucent USA Inc. Additional plaintiff-side counsel (pro hac vice or in-house) are likely but unverified, and I have not invented any names to fill that gap.

I'll research this case to identify the defendant's counsel of record.

Let me search more specifically.

Let me identify the patent and search patent-focused sources.

Counsel of Record for Defendant(s) — Unable to Verify

I was unable to identify the defendant(s) or their counsel of record for this case with the searches available, and I will not guess at attorney names. Here is a candid accounting.

What I searched

• Case-number lookups: "1:14-cv-00574" Delaware and 1:14-cv-00574 District of Delaware patent 6888797
• Patent lookups: US6888797B1 patent title assignee, "6,888,797" patent, patent 6888797 B1 "D. Del." complaint
• Nothing returned the docket sheet, complaint, or any filing for this specific case.

What the searches actually returned

The results were unrelated D. Del. matters whose documents happen to cite other Delaware case numbers, e.g. dates/counsel from Ingenus Pharmaceuticals v. Hetero (C.A. 24-1025-JLH) and the Pfizer/FoldRx/Aurobindo matters (C.A. 23-879). None of these are this case, and none identify the parties or counsel for 1:14-cv-00574. I deliberately did not carry any of those attorney names over, because there is no evidence tying them to this case.

Contradiction / gap to flag

The case metadata here is thin and, as the earlier-generated overview already noted, the parties themselves could not be verified. That is the root problem:

• The caption is listed only as "Untitled case."
• I could not confirm the assignee/owner of US 6,888,797 B1, which is normally the fastest way to identify the plaintiff and thus the likely defendant set.
• Without a party name, there is no reliable path to the complaint's caption, the defendant's answer, or the attorneys' appearances, and therefore no basis to name any counsel as "lead," "local," "of counsel," or "in-house."

What cannot be asserted

• No counsel of record can be confirmed for any defendant in 1:14-cv-00574 (D. Del.). I cannot say whether pleadings or appearances are sealed; I simply have no source confirming any appearance at all.
• I have no firm, office location, or experience note to report, because I have no verified attorney identities.

Recommended verification steps (to run against primary sources)

1. CourtListener / RECAP — fetch the docket directly: https://www.courtlistener.com/docket/?q=1:14-cv-00574 (D. Del. docket page), then open the complaint (D.I. 1) and any "Notice of Appearance"/"Disclosure Statement" entries.
2. PACER for the District of Delaware, Docket Report for 1:14-cv-00574 — read the caption and the "Attorneys" block, which lists lead and local counsel per party.
3. USPTO Patent Assignment / PAIR for US 6,888,797 B1 — confirm the assignee to pin down the plaintiff, which in turn identifies the defendant group.
4. Firm press releases / Law360 / Reuters Legal for the plaintiff named in step 3 against "Delaware" and "2014."

If you can supply the party names (or the patent's assignee), I can immediately pull the Delaware local-counsel firm and the defendant's lead trial counsel and give you the role/firm/experience detail requested. Until then, the accurate answer is: counsel of record for the defendant(s) is unverified from available sources — no attorney names are provided to avoid fabrication.