Alcatel-Lucent USA Inc. v. Cyberoam Inc. et al.

I'll research this case thoroughly before drafting the overview.

Let me dig into the docket, the parallel Fortinet case, and any PTAB proceedings.

Let me pull the specific docket and complaint details, plus patent titles.

Case Overview — Alcatel-Lucent USA Inc. v. Cyberoam Inc. et al., No. 1:14-cv-00628 (D. Del.)

Parties. The plaintiff is Alcatel-Lucent USA Inc., the U.S. operating subsidiary of France-based Alcatel-Lucent SA (the complaint's Rule 7.1 disclosure identifies Alcatel Lucent SA as its corporate parent). This is an operating company, not an NPE/PAE: Alcatel-Lucent was a global telecom equipment and networking vendor whose patent estate descended from Lucent Technologies and Bell Labs. The defendants are Cyberoam Inc., the U.S. arm of Cyberoam Technologies Pvt. Ltd. (Ahmedabad, India; founded 1999; a unified threat management ("UTM") and next-generation firewall vendor with roughly 550 employees and a large India/Middle East/Africa channel, per Sophos's own acquisition FAQ), and Sophos Inc., the U.S. affiliate of Sophos Ltd. (Abingdon, U.K.), a security vendor selling endpoint and network security products, with U.S. offices including Burlington, Massachusetts (where the docket shows Sophos was served via CT Corporation System). Notably, Sophos had acquired Cyberoam in early 2014 — announced in February 2014, making Cyberoam a 100%-owned Sophos entity — so by the time of suit the two defendants were affiliates, and the case is best understood as a single-front action against the combined Sophos/Cyberoam network-security business. One caveat: the Unified Patents litigation portal captions this case "Alcatel Lucent SAS v. Cyberoam Inc. et al.," whereas the docket reflects the complaint as filed by Alcatel-Lucent USA Inc. I could not resolve that naming discrepancy from the sources retrieved.

Accused technology and patents-in-suit. The complaint (D.I. 1) alleges infringement by Sophos and Cyberoam "products and services," which contemporaneous trade press (Telecompaper) characterized as network security and network management technologies — consistent with Cyberoam's UTM/firewall appliances, centralized security management, and logging/reporting platforms. The five patents reported to the Commissioner of Patents per the docket are US 6,286,050; US 6,347,087; US 6,888,797; US 6,944,183; and US 7,143,438. Verified titles (I was able to confirm these three from the parallel Alcatel-Lucent complaint against Fortinet, No. 1:14-cv-00574, filed May 1, 2014): the '087 patent, "Content-Based Forwarding/Filtering in a Network Switching Device"; the '797 patent, "Hashing-Based Network Load Balancing"; and the '183 patent, "Object Model for Network Policy Management." The Fortinet action also asserted the '087, '797, and '183 patents, showing the two suits were a coordinated May 2014 campaign against competing firewall/security vendors. I could not verify the titles or claim scope of the '050 and '438 patents from the sources I retrieved — I'm flagging that rather than guessing; the only characterization available is Telecompaper's general description of all five as network security/network management patents.

Posture, venue, and significance. Filed May 20, 2014 in the District of Delaware with a jury demand on all triable issues, and with the standard magistrate-judge consent/referral notice; summonses issued that same day to Cyberoam Inc. and to Sophos Inc. The presiding judge is not confirmed in the materials I retrieved (the companion Fortinet case was assigned to then-Chief Judge Leonard P. Stark, but I have no sourced basis for assigning this case to a particular judge). Delaware mattered here for the usual reasons — a small, patent-experienced bench, well-developed local patent rules, fast time-to-trial, and the fact that both defendants are U.S.-registered entities with national distribution into the district — and it was a natural forum for a serial filer like Alcatel-Lucent. The case is notable on several axes: it is a rare incumbent-vs-incumbent assertion (telecom vendor against security-appliance vendors) rather than a classic PAE campaign, drawing on Bell Labs firewall and traffic-management patents; it was one of two suits Alcatel-Lucent filed within three weeks in May 2014 (Fortinet on May 1, Sophos/Cyberoam on May 20), indicating a deliberate licensing-and-enforcement push; it landed immediately on the heels of Sophos's acquisition of Cyberoam, which may have consolidated the infringement target and changed the defendants' incentives to settle; and its market context is the fast-growing UTM/next-gen firewall segment (IDC sized UTM at roughly $2.5B growing ~20%/year in Sophos's own 2014 materials). The final disposition is not confirmed: I found no public settlement, dismissal order, judgment, or merits opinion in the sources I retrieved, and I found no PTAB IPR/PGR proceedings on these five patents. Given that the case is now over a decade old with no reported outcome, the most probable resolutions are a confidential license/settlement or dismissal, but that is inference, not a sourced fact.

I'll research this case systematically, starting with docket-level and outcome information.

Let me dig into the docket details, disposition, and any PTAB proceedings.

Key Legal Developments — Alcatel-Lucent USA Inc. v. Cyberoam Inc. et al., No. 1:14-cv-00628 (D. Del.)

Important caveat up front, and it matters for how you should use this: I was able to verify the filing-stage docket records for this case, but I was not able to retrieve the later docket sheet (answers, motion practice, Markman, trial, or the terminating event), and I found no public record of any PTAB proceeding against the five asserted patents. Rather than paper over those gaps with plausible-sounding narrative, I've separated verified facts from inferences and from unverified/unknown items. Several items on your checklist appear to have no accessible public record at all.

---

1. Verified: filing and initial pleadings (2014)

Two caption/bookkeeping notes worth flagging:

• The docket as indexed by Unified Patents is captioned Alcatel Lucent SAS v. Cyberoam Inc. et al., while the complaint itself was filed by Alcatel-Lucent USA Inc. The case metadata you supplied (plaintiff = Alcatel-Lucent USA Inc.) matches the filing party; the "SAS" in the docket title appears to reflect the French parent identified in the Rule 7.1 statement. This type of caption discrepancy is common in the Alcatel-Lucent/Nokia docket family.
• The case was filed with the Magistrate Judge consent/referral forms, meaning the parties were given the option to consent to magistrate jurisdiction — a routine D. Del. filing-stage notice.

Corporate context that shaped the defense: Sophos announced its acquisition of Cyberoam Technologies in February 2014 ("Cyberoam is now 100% owned by Sophos"), i.e., roughly three months before this suit was filed (Sophos press FAQ, "Sophos Acquires Cyberoam," news.sophos.com). That ownership relationship is why Cyberoam and Sophos were sued together and appears in the docket caption as a parent/subsidiary pair.

Companion/parallel filing: Alcatel-Lucent filed a related Delaware action against Fortinet, Inc. on 2014-05-01, Alcatel-Lucent USA Inc. v. Fortinet Inc., 1:14-cv-00574 (D. Del.) — making the Cyberoam/Sophos suit the second of Alcatel-Lucent's May 2014 network-security assertions, per Telecompaper ("Alcatel-Lucent starts patent suit against Fortinet, Sophos," telecompaper.com). Telecompaper characterizes the asserted technology as "network security and network management." I did not verify whether the Fortinet and Cyberoam/Sophos cases asserted the identical patent set or were coordinated for discovery/Markman — worth checking, as claim construction in one Delaware Alcatel-Lucent case could have been leveraged in the other.

---

2. Items on your checklist for which I found no verifiable public record

I want to be direct rather than fill these in speculatively:

• Answer and counterclaims (Civ. R. 12/13). No answer, counterclaim, or Rule 12 motion is reflected in the docket material I retrieved. Given the Sophos/Cyberoam parent-subsidiary posture, counterclaims for declaratory judgment of invalidity/non-infringement would be expected, but I cannot confirm they were filed.
• Motion to dismiss / transfer / stay. None located.
• Motion to stay pending IPR. None located — and see the PTAB point below.
• Markman / claim construction. No claim-construction opinion or order in this case was located. In D. Del. this typically surfaces as a Markman order or an opinion by the assigned judge; I found neither, which is consistent with (but does not prove) early resolution.
• Summary judgment. None located.
• Discovery milestones of strategic significance. None located.
• Trial, verdict, JMOL/new-trial/fee motions. None located. There is no public indication this case was tried.
• Final disposition / appeal. Not confirmed. No stipulated dismissal order, settlement announcement, final judgment, or Federal Circuit appeal for No. 1:14-cv-00628 surfaced in my searches.

---

3. Parallel PTAB proceedings — none located

I searched specifically for IPR/PGR activity on the five asserted patents (US 6,286,050; 6,347,087; 6,888,797; 6,944,183; 7,143,438) and found no IPR or PGR naming any of them as the challenged patent. This is a meaningful negative for your chronology: if accurate, there was no PTAB-forum parallel attack in this case, which distinguishes it from the many 2014–2016 network-security assertions that were stayed pending IPR. Because I could not search the PTAB portal directly by patent number within the available steps, treat this as strongly suggestive but not conclusively verified.

Two related threads I surfaced that you should chase, because they may bear on the asserted family's chain of title:

• A Patent Purchase Agreement among Nokia Technologies Oy, Nokia Solutions and Networks B.V., Alcatel Lucent SAS, and Provenance Asset Group LLC appeared as an exhibit in a PTAB proceeding (recorded at Reel 043877). This reflects the post-2016 Nokia-era monetization of portions of the Alcatel-Lucent portfolio. I could not confirm whether the five asserted patents were among the transferred assets — and if they were, ownership/s standing issues would be a key development here.
• Nokia's acquisition of Alcatel-Lucent closed in 2016, with the full squeeze-out implemented 2016-11-02 (Nokia interim report / AMF timetable). Any Alcatel-Lucent patent litigation still pending after that date would have been prosecuted in the Nokia era, and any damages/licensing outcome would flow to Nokia.

---

4. Related (but distinct) litigation against the same defendants — useful context, not this case

Do not conflate this with Verifire Network Solutions, LLC v. Cyberoam Inc. et al., No. 2:15-cv-00931 (E.D. Tex.), filed 2015-06-03 before Judge Rodney Gilstrap and Magistrate Judge Roy S. Payne. That is a different plaintiff asserting different patents against the same Sophos/Cyberoam defendants, and it was dismissed with prejudice by order of 2015-09-30 (per UniCourt case record). It is relevant only as evidence of the defendants' contemporaneous exposure in the same technology space; it is not a development in this Delaware case.

---

5. What the record most likely shows (clearly labeled inference, not fact)

The combination of (a) filing in May 2014, (b) no accessible Markman opinion, (c) no PTAB proceeding, and (d) no trial or appellate record produces two plausible endings, and I cannot yet distinguish between them:

1. Early confidential settlement and stipulated dismissal — common in D. Del. patent cases resolved before claim construction; the order would typically be a short "So Ordered" stipulation that generates little press.
2. Voluntary dismissal without prejudice after the Fortinet and Cyberoam/Sophos matters were folded into a broader Alcatel-Lucent network-security licensing program.

Neither end state is verified. I have not found a dismissal order, judgment, or settlement report, and I will not assert one.

---

6. Where to close the gaps (recommended next searches)

To convert the above into a complete chronology, the following are the highest-yield sources, in order:

1. PACER docket for 1:14-cv-00628 (D. Del.) — pull the full docket sheet and the terminating entry. This single document resolves items 2 through 4 above. CourtListener's RECAP docket for this case number returned no free copy in my search.
2. PTAB Patent Trial & Appeal Board / USPTO Patent Public Search — run each of the five patent numbers through the PTAB "Patent Trial" search and the USPTO assignment database (assignment.uspto.gov) to confirm (a) no IPR/PGR and (b) whether the patents were assigned to Provenance Asset Group LLC or another entity.
3. The Fortinet companion docket, 1:14-cv-00574 — for shared Markman scheduling and any coordinated stay, and to see how the common patent set was resolved.
4. Nokia/Alcatel-Lucent licensing disclosures (2016–2019 20-F filings) — for any reference to settlement or licensing revenue tied to the network-security portfolio.

Because I hit my search-step limit before reaching a definitive disposition, please treat "not confirmed" literally for the answer, motions, Markman, trial, and disposition sections — not as shorthand for "no such events occurred."

I'll research the docket and counsel of record for the plaintiff in this case.

Bottom line up front

I could not verify counsel of record for the plaintiff from the sources I was able to reach. The public docket text I retrieved for Alcatel-Lucent USA Inc. v. Cyberoam Inc. et al., No. 1:14-cv-00628 (D. Del.) confirms the plaintiff and the filing but does not surface attorney names in the retrievable snippets, and I was cut off before I could pull the complaint's signature block (D.I. 1) or the pro hac vice motions. Per the operating rules, I am not going to name attorneys I could not tie to a docket entry — so the honest answer is: unconfirmed as of this research pass, with a precise roadmap below for closing the gap.

What the record does confirm

From the Unified Patents litigation portal entry for the case (portal.unifiedpatents.com):

• Caption variance worth flagging: the portal styles the case as "Alcatel Lucent SAS v. Cyberoam Inc et al.", while your metadata and the complaint text say the filer is Alcatel-Lucent USA Inc. The docket itself shows that on 5/20/2014 a "COMPLAINT FOR PATENT INFRINGEMENT ... filed by Alcatel-Lucent USA Inc." with five exhibits, and the Rule 7.1 disclosure "identifying Corporate Parent Alcatel Lucent SA for Alcatel-Lucent USA Inc." This matters for your counsel question: if a parent/subsidiary entity was added or substituted, the attorney appearing on a later entry may be counsel to a different Alcatel-Lucent entity than the original filer.
• Summons issued 5/20/2014 as to Cyberoam Inc. and Sophos Inc. (both via CT Corporation System and the Burlington, MA address). Service on Delaware counsel for defendants is the trigger for the appearance entries (D.I. 7–9 typically).
• Patents reported to the PTO: US 6,286,050 B1; 6,347,087 B1; 6,888,797 B1; 6,944,183 B1; 7,143,438 B1 — consistent with your case metadata.
• A subsequent dated entry appears on the portal at 4/8/2015, but the snippet does not identify its type or the filing attorney.

Press coverage (Telecompaper, "Alcatel-Lucent starts patent suit against Fortinet, Sophos") confirms the May 2014 filing campaign against Sophos/Cyberoam over five network-security/network-management patents, and notes a parallel 5/1/2014 Delaware suit against Fortinet on seven patents. That companion case is a useful cross-reference: Alcatel-Lucent commonly used the same local Delaware counsel across its 2014 Delaware campaign, so the Fortinet docket (1:14-cv-00581) is a high-yield place to confirm the Delaware local-counsel relationship. I did not verify that relationship in this pass.

Plaintiff-side counsel: status by category

I am deliberately leaving these blank rather than filling them with plausible-sounding names. I did not find any filing in this case that was returned to me as sealed, and I have no basis to say whether any document was filed under seal; the gap is a research limitation on my end, not a sealing issue I can confirm.

Exact docket entries that will answer this

To definitively identify counsel, pull these from PACER (D. Del.) or CourtListener's RECAP docket for 1:14-cv-00628:

1. D.I. 1 — Complaint for Patent Infringement. The signature block names plaintiff's filing attorney(s), typically Delaware local counsel, and the certificate of service/CM-ECF header lists the full service list.
2. D.I. 5–6-ish — Rule 7.1 Disclosure Statement (Alcatel-Lucent USA Inc.), which carries the filing attorney's name, email, and firm.
3. D.I. 7–12 — Motions for Leave to Appear Pro Hac Vice on behalf of plaintiff, with the accompanying declarations listing each out-of-state lead/backup attorney, their firm, office address, and bar admissions. This is where you get lead vs. backup roles.
4. Order(s) granting pro hac vice — confirms which attorneys were actually admitted.
5. Subsequent substantive entries (claim construction briefing, IPR-related stays, stipulations of dismissal) — these carry the current appearance roster, and any substitution of counsel would appear as a withdrawal/appearance pair.
6. If there is a Terminated/Settled entry, the stipulation of dismissal signature blocks confirm who was still counsel at the end.

Also worth running: the Rule 7.1 and pro hac vice dockets of the companion Fortinet case, and the D. Del. CM/ECF "Attorney Appearance" filter, which lists every attorney appearing for each party with firm and address.

One caveat on the case status

Your metadata shows status "not confirmed," and the summary says final disposition is unconfirmed. The portal shows an April 2015 entry but I could not characterize it. Before relying on any counsel list, confirm whether this case was dismissed, settled, transferred, or consolidated with the Fortinet action — because the operative counsel roster is the one on the last substantive entry, not on the 2014 complaint.

If you can grant another search pass, I'll pull the complaint signature block and the pro hac vice filings directly and return a named, role-tagged table with citations.

I'll research defense counsel for both Cyberoam and Sophos in this Delaware case.

Let me try to pull the actual docket sheet and any appearances.

Let me try to access the RECAP docket directly and search for Sophos's Delaware litigation counsel.

Defense counsel of record — research result

Bottom line: I could not verify any attorney as counsel of record for Cyberoam Inc. or Sophos Inc. in No. 1:14-cv-00628 (D. Del.). The public docket text I could reach confirms the case, the parties, and the filing-stage papers, but it does not surface appearance entries, pro hac vice motions, or signature blocks — the entries where defense counsel names appear. Per the operating rules, I am not going to fill this table with plausible-sounding names. The honest state of the record, with the one cross-case lead I found, is below.

1. What the retrievable docket does and does not show

From the Unified Patents litigation portal docket for this case (portal.unifiedpatents.com), the entries I could actually read are all plaintiff-side or clerk-side, dated 5/20/2014:

• Complaint for Patent Infringement, jury demand, against Cyberoam Inc. and Sophos Inc., filed by Alcatel-Lucent USA Inc. (D.I. 1).
• Rule 7.1 disclosure identifying Alcatel Lucent SA as parent.
• AO-120 Report to the Commissioner listing the five patents.
• Summonses issued as to Cyberoam Inc. and Sophos Inc. (the latter via c/o CT Corporation System and c/o 3 Van de Graaff Drive, Burlington, MA) — both on 5/20/2014.
• Magistrate consent/referral notices.

The portal text also shows a later entry dated 4/8/2015 ("CIVIL DOCKET"), but the snippet does not identify what was filed or by whom. No appearance, answer, Rule 12 motion, pro hac vice motion, or stipulation of dismissal was recoverable in my searches. A targeted CourtListener RECAP search for the docket sheet similarly returned no free copy of the later docket.

Caveat on completeness: this is a research gap on my end, not evidence of absence. I could not reach PACER, and I found no indication that any specific filing in this case was sealed. Whether defense counsel ever appeared — and who they were — is simply not resolved by the sources I could retrieve.

2. Defense counsel table — status by category

Because Sophos had acquired Cyberoam in February 2014 (100% ownership; Sophos press release, 2/10/2014), the two defendants most likely shared a single defense team — but that is inference from the corporate relationship, not a verified fact about appearances in this case.

3. One cross-case lead (flagged as unverified for this case)

The only concrete defense-side attorney information I surfaced comes from a different case against the same defendant: SoftVault Systems, Inc. v. Sophos Inc., No. 5:14-cv-03222-LHK (N.D. Cal.). A January 14, 2015 joint settlement status report in that case lists Sophos's counsel:

• Corby R. Vowell (admitted pro hac vice)
• Jonathan T. Suder (PHV to be filed)
• Todd Blumenfeld (admitted pro hac vice)

These three names are characteristic of Friedman, Suder & Cooke (Fort Worth, Texas), a firm with a substantial patent-defense practice; the filing also references a counsel phone number in the 202 (Washington, D.C.) area code for defendant Sophos, suggesting additional counsel from a D.C. firm. I could not verify the firm affiliations from the snippet, and — critically — I have no evidence these attorneys appeared in the Delaware Cyberoam/Sophos action. Treat this strictly as a research lead: Sophos's outside patent-defense roster circa 2014–15 is the place to start when checking this docket.

4. Exact docket entries that will answer this

To name defense counsel with citations, these are the entries to pull from PACER (D. Del.) or the RECAP docket for 1:14-cv-00628:

1. Defendants' Rule 12 answer or motion — the first defense-side substantive filing; its signature block and ECF header list lead and local counsel.
2. Motions for Leave to Appear Pro Hac Vice (typically filed soon after the answer) — the accompanying declarations give each out-of-state attorney's firm, office, and bar admissions, and distinguish lead from backup.
3. Order(s) granting pro hac vice — confirms who was actually admitted.
4. Notice of Appearance / Withdrawal entries — establishes the operative roster and any substitution (relevant here because Sophos's 2014–15 cybersecurity M&A activity and the Cyberoam integration could have changed counsel).
5. Any stipulation of dismissal or settlement order — the signature blocks confirm who remained counsel at the end; given the case's age and the previously noted absence of a merits ruling, this is likely where the record terminates.
6. *The companion Fortinet docket, Alcatel-Lucent USA Inc. v. Fortinet Inc., No. 1:14-cv-00574 (D. Del.)* — a useful control for the plaintiff-side roster, not the defense roster; the defendants there are unrelated to Sophos, so this will not reveal Cyberoam/Sophos counsel, contrary to any suggestion that the two May 2014 cases shared a defense team.

Also worth running: the D. Del. CM/ECF "Attorney Appearance" filter for this case number, which lists every attorney appearing for each party with firm and address, and the USPTO assignment records for the five patents (which bear on ownership/s standing rather than counsel).

5. Consistency check against the earlier sections

This result is consistent with the previously generated sections, which already noted that no answer, counterclaim, or Rule 12 motion was confirmed and that the case's disposition is "not confirmed." No contradiction with the case metadata arose: the filer is Alcatel-Lucent USA Inc., and the docket-title variant "Alcatel Lucent SAS" noted earlier persists in the Unified Patents indexing. I did not find new information displacing the earlier sections' characterization of the case as unresolved on the public record.

If I'm given another search pass, the highest-yield next step is a direct PACER pull of the docket sheet for 1:14-cv-00628 (or the CourtListener RECAP copy), which would resolve the defense roster in one document.