Enhanced Data Streaming LLC v. Cisco Systems, Inc.

I'll research this case thoroughly before drafting. Let me start with parallel searches on the parties, patents, and docket.

Now let me research the plaintiff's corporate background, patent provenance (Orckit), and any PTAB proceedings.

Let me pull the technical details of each asserted patent and the accused products.

Case Overview — Enhanced Data Streaming LLC v. Cisco Systems, Inc., No. 2:25-cv-01038-JRG (E.D. Tex.)

The parties. Enhanced Data Streaming LLC ("EDS") is a patent-holding LLC — Unified Patents classifies it as an NPE/PAE — that holds a slice of the portfolio originally developed by Orckit Communications Ltd. / Orckit-Corrigent Ltd., the Tel Aviv-based telecom equipment vendor (Nasdaq: ORCT) that built the CM-4000/CM-401x packet transport switch lines, invested roughly $200 million in R&D, and sold into tier-1 carriers before entering Israeli debt-restructuring/insolvency proceedings in 2012. In April 2016, Orckit IP LLC acquired Orckit-Corrigent's patents out of those proceedings (Reel/Frame 038541/0984), and on March 20, 2017, Orckit IP sent Cisco a licensing letter enclosing a "Schedule of Orckit IP's Patent Portfolio." That letter is the linchpin of EDS's pre-suit-knowledge pleading here. USPTO assignment records show a further chain running Orckit IP → Blackbird Tech LLC (2018) → Orckit IP (2019) → Nahum Communication N.T.B. Ltd. (2021) → Orckit IP LLC (2022); I could not verify from public records the specific assignment instrument or date by which EDS itself took title, so EDS's chain of title from Orckit IP should be treated as unconfirmed — and note that Cisco has already litigated an assignment/standing fight with an affiliated Orckit entity (see below). Cisco Systems, Inc. is the Delaware-incorporated, San Jose-headquartered networking incumbent; it is a frequent defendant in this division.

The accused technology. Per the infringement contentions as summarized in the First Amended Complaint, the case targets Cisco's service-provider routing and campus/data-center switching installed base rather than a single product: principally the Cisco ASR 1000 Series Aggregation Services Router — specifically Multicast Service Reflection (multicast-to-unicast retranslation of a requested stream), IEEE 1588v2 Precision Time Protocol, and Multilink PPP over Ethernet / Link Fragmentation and Interleaving — together with switch features such as StackWise Virtual, FabricPath, and virtual port channels (vPC), which the complaint maps to redundancy, failover, and MAC-address synchronization limitations. (This mapping is drawn from a third-party element-by-element analysis of the FAC; the complaint itself is behind the PACER paywall, so the precise accused-product list should be confirmed against Dkt. 22.) EDS pleads direct infringement plus induced infringement (Cisco's configuration guides, e.g., *IP Multicast: Multicast Services Configuration Guide, Cisco IOS XE Release 3S

I'll research this case across the docket, PTAB, and legal press. Let me run several searches in parallel.

Good foundation. Now let me dig into the full docket, any PTAB activity, and the plaintiff's broader campaign.

Enhanced Data Streaming LLC v. Cisco Systems, Inc., No. 2:25-cv-01038-JRG (E.D. Tex., Marshall Div.)

Bottom line: This case is in an early, active posture. The only substantive merits ruling on the docket is Judge Gilstrap's 2026-06-02 denial of Cisco's Rule 12(b)(6) motion attacking the indirect- and willful-infringement theories. No Markman order, no summary-judgment ruling, no trial, and no identified PTAB challenge. Below is what is verifiable and, importantly, where the record is thin.

---

Chronology

---

Filing & initial pleadings

• The complaint was filed 2025-10-10 in the Marshall Division and assigned to Judge Gilstrap (Dkt. 1). Plaintiff is characterized in third-party litigation databases as a non-practicing entity (Unified Patents portal).
• One technical point worth flagging: the asserted media-distribution patent is the reissue, RE50,398, not the original '151 patent. The reissue issued only ~5½ months before suit, which is a meaningful sequencing fact — EDS pleaded the case around the reissued claim set rather than the original patent.
• Gap: I could not locate a docket entry for Cisco's answer and counterclaims (typical counterclaims would be non-infringement and invalidity, plus perhaps inequitable conduct given the reissue). The docket numbered at least 48 entries by June 2026, so an answer almost certainly exists, but its date and contents are not verified here and should be pulled from PACER.

Pre-trial motions of substance

Only one substantive motion is confirmed: the Rule 12(b)(6) motion, denied 2026-06-02 (Dkt. 48). Its holdings are the most legally significant developments to date:

1. Pre-suit knowledge (willfulness and pre-suit indirect infringement). Cisco argued EDS pleaded no pre-suit knowledge because the March 2017 Orckit letter "does not reference any Asserted Patent." The Court rejected that, crediting EDS's allegation that the letter enclosed a portfolio schedule expressly listing the patents-in-suit and the '151 patent, and that the letter identified specific accused Cisco products. The Court applied its own Fractus, S.A. v. TCL Corp., 2021 WL 2483155, at *44 (E.D. Tex. June 2, 2021) line — notice letters listing patents and accused products suffice. Dkt. 48 at 3–4.
2. Willful blindness. The Court also sustained EDS's willful-blindness theory based on allegations that Cisco "has adopted a policy of not reviewing the patents of others," citing Motiva Pats. LLC v. Sony Corp., 408 F. Supp. 3d 833–34 (E.D. Tex. 2019), and Wooten v. McDonald Transit, 788 F.3d 490 (5th Cir. 2015). Dkt. 48 at 4 n.1.
3. Post-suit induced infringement (specific intent). The Court held EDS plausibly pleaded specific intent by citing, patent-by-patent, specific Cisco configuration guides with page numbers — e.g., IP Multicast: Multicast Services Configuration Guide, Cisco IOS XE Release 3S, pp. 16–18, instructing customers to run multicast service reflection on an ASR 1000. Dkt. 48 at 5–6 (citing Motiva, 408 F. Supp. 3d at 831, and Lifetime Indus. v. Trim-Lok, 869 F.3d 1372, 1379 (Fed. Cir. 2017)).

Strategic significance: the 2017 Orckit letter is now the load-bearing fact for both enhanced damages and pre-suit inducement/contributory infringement. It converts a 2025 complaint into a case with a 2017 notice narrative and shifts Cisco's burden to attack the letter's actual contents (the schedule was not attached to the FAC — the Court took the allegation as true, so Cisco's best early target is the letter and its enclosures on the merits or in a summary-judgment motion).

• No motion to transfer, no motion to stay, and no summary-judgment motion are confirmed. Given Cisco's headquarters and EDS's NPE status, a § 1404(a) transfer motion would be a conventional defense step; I found no evidence one was filed. Do not assume it was.

Claim construction (Markman)

Not reached / not confirmed. No Markman order, claim-construction opinion, or O2 Micro / Gilstrap "Model Order" scheduling order appears in any source I could reach. With the pleadings not closed until mid-2026, Markman was almost certainly still ahead as of 2026-10-25. This is the next materially case-shifting event to watch, particularly on the '398 reissue claims (limitations reciting delay "to reduce zap-time" determined "at least partly based on a timing parameter of the request," and the multicast-to-unicast conversion "in response to" a request — both are ripe indefiniteness/§ 112 and infringement disputes).

Discovery milestones

No discovery orders, motion-to-compel rulings, or protective-order disputes are verifiable in the sources available. The practical milestone is that discovery opened in earnest after the 2026-06-02 order (the press noted the case "will proceed to discovery"). Given the 2017 knowledge theory, the highest-value discovery items will be: Cisco's patent-review policies (willful blindness), the custodian files for the March 2017 letter, and Cisco documentation for multicast service reflection as configured on the ASR 1000.

Trial, verdict, post-trial motions

None. No trial setting, verdict, JMOL, new-trial, or fee motion is confirmed. The case has not reached trial.

Final disposition / present posture

Pending and active as of 2026-10-25. Docket status is "Open," no termination date (Unified Patents portal). The 2026-06-02 order terminated Dkt. 26 only; it did not narrow the patents or the accused products. An interlocutory appeal of a Rule 12(b)(6) denial is not available, so the ruling is not appealable now — the realistic appeal path is a post-judgment appeal to the Federal Circuit.

Parallel PTAB proceedings

No IPR, PGR, or reissue/reexam challenge to the asserted patents by Cisco is confirmed. I searched for PTAB petitions naming EDS, Cisco, and the five patents and found nothing. Two caveats:

• A petition filed in late 2025 or 2026 would fall in the 6-month window before institution, so absence of press coverage is weak evidence. The authoritative check is PTAB Patent Trial and Appeal Board Endpoint / P-TACTS by patent number (RE50,398; 6,891,855; 7,336,605; 7,660,234; 7,032,135).
• Because the '398 reissue issued in April 2025, the § 315(b) one-year IPR bar for Cisco runs from service of the 2025 complaint — i.e., a Cisco petition would need to be filed by roughly October 2026. That deadline is the single most consequential near-term date on this case: a petition now would likely draw a § 315(a)/stay fight before Judge Gilstrap, who has stayed cases pending IPR when the PTAB institutes.

What is not established (do not treat as fact)

• Cisco's answer/counterclaim date and theories.
• Any transfer, stay, or summary-judgment motion.
• Any Markman hearing date or order.
• Any IPR/PGR number or institution decision.
• Case-specific counsel of record for either side (not verified in these sources).

Primary citations: Enhanced Data Streaming LLC v. Cisco Systems, Inc., No. 2:25-cv-01038-JRG, Dkt. 48 (E.D. Tex. June 2, 2026), https://www.govinfo.gov/content/pkg/USCOURTS-txed-2_25-cv-01038/pdf/USCOURTS-txed-2_25-cv-01038-0.pdf; 2026 BL 206667; Justia docket, https://law.justia.com/cases/federal/district-courts/texas/txedce/2:2025cv01038/[241096](/patent/241096)/48/; Unified Patents case portal, https://portal.unifiedpatents.com/litigation/Texas%20Eastern%20District%20Court/case/2%3A25-cv-01038.

I'll search from several angles to locate actual press coverage of this case.

Let me search additional angles, including specific patent numbers and trade press.

Bottom line: I found essentially no press coverage of this case. After searching the case caption, the party names, the docket number, the asserted patent numbers (including RE50,398), and the June 2026 ruling, the only "news" items surfaced were a Bloomberg Law docket note and one algorithmic financial-analysis post. There is no Reuters, Bloomberg Law feature story, Law360 article, Ars Technica, The Verge, IPWatchdog, Patently-O, EFF, JD Supra, or mainstream coverage I could locate for Enhanced Data Streaming LLC v. Cisco Systems, Inc., No. 2:25-cv-01038-JRG.

The closest thing to trade-press reporting is a Bloomberg Law docket item, which I only encountered second-hand through an aggregated IP news feed rather than on bloomberglaw.com itself: Bloomberg Law (cited as 2026 BL 206667) summarized that Judge Rodney Gilstrap denied Cisco's motion to dismiss Enhanced Data Streaming's indirect and willful infringement claims because EDS "sufficiently pleaded pre-suit knowledge and specific intent for post-suit induced infringement." That is a one-paragraph docket digest, not an analytical piece — I could not verify it directly on the Bloomberg Law site, and it adds no numbers, no damages theory, and no industry reaction.

Beyond that, the coverage is either primary-source material or machine-generated. SecBot, an automated court-ruling-to-ticker service, filed a June 3, 2026 note framing the ruling as a procedural "LOSS" for Cisco that "allows the case to proceed to discovery, but no damages or injunctive relief were awarded at this stage, and the financial exposure remains unquantified." It also flags the two factual predicates of the ruling — a March 2017 letter from prior owner Orckit IP, and Cisco configuration guides as evidence of induced-infringement intent — and rates appeal and precedent risk as low. That is an analyst-style take on the docket, not reporting: it explicitly states it is "based on 1 court opinion from CourtListener," and its "will it be appealed / precedent risk" characterizations go beyond anything in the court record. Docket-aggregator listings from Unified Patents tag EDS as an NPE and confirm the case remains open before Judge Gilstrap, and the opinion itself is available via Justia and govinfo — but those are court records, not press.

On the specific questions you asked: no outlet has reported a damages figure, settlement, verdict, or market impact, and I found no executive statements, analyst commentary, or industry reaction in the press. Note also that the case is early — filed October 10, 2025, still at the pleadings stage as of the June 2, 2026 ruling — which explains the thin coverage; NPE suits against large defendants in Marshall routinely draw no press unless they reach claim construction, summary judgment, or trial. If coverage emerges, the likely triggers will be a Markman order, an IPR petition on the '398 or '605 patents, or a trial setting.

Sources

• IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF TEXAS MARSHALL DIVISION
• Enhanced Data Streaming LLC v. Cisco Systems, Inc.
• Complaint analysis | 2:25-cv-01038 | Enhanced Data Streaming LLC v. Cisco Systems Inc | Ex Parte
• Patent Cases, Dockets and Filings in Texas
• Intellectual Property Cases filed in Texas
• 2:25-cv-01038 | Enhanced Data Streaming LLC v. Cisco Systems Inc | Ex Parte
• Enhanced Data Streaming LLC v. Cisco Systems, Inc., No. 2:25-cv-01038 (E.D. Tex. June 2, 2026) — Memorandum Opinion and Order (Dkt. 48) — Patent Case Watch
• Cisco State Court Decisions
• IP In the News - IP In the News from Research and Information Services on Inoreader
• Case 2:25-cv-01038-AH Document 113-1 Filed 05/15/26 Page 10 of 51 Page ID #:4198
• 4. Attached as Exhibit D is a copy of U

I'll research the counsel of record for Enhanced Data Streaming LLC in this case.

I have the case documents but need the specific counsel. Let me dig into the docket and complaint signature blocks.

Let me look for the CourtListener RECAP docket, which typically lists counsel, and check for related EDS lawsuits.

Bottom line

I was unable to verify the names of plaintiff's counsel of record from the sources I could reach. Rather than guess, I'm reporting what the record confirms, what is missing, and exactly where to confirm it. No attorney should be attributed to Enhanced Data Streaming LLC in this case on the basis of this memo — the signature blocks and the ECF attorney list are the only reliable sources, and the publicly indexed text of the two plaintiff-side filings I located (the Complaint, Dkt. 1, and the First Amended Complaint, Dkt. 22) does not expose them.

What is confirmed about the plaintiff's side of the docket

Sources: the opinion itself, Enhanced Data Streaming LLC v. Cisco Systems, Inc., No. 2:25-cv-01038-JRG (E.D. Tex. June 2, 2026) (Dkt. 48), available at govinfo and Justia; see also 2026 BL 206667 (Bloomberg Law report of the June 2, 2026 ruling).

What that establishes about counsel: plaintiff's counsel have appeared and are actively litigating — EDS filed the Complaint, amended as of right after the first motion to dismiss, and successfully opposed the renewed motion to dismiss. So this is not a case where counsel has not yet appeared, and the docket shows no indication that the pleadings or the motion papers were filed under seal (the June 2 opinion is public and quotes the FAC's substantive allegations, e.g., the 2017 notice letter and the Cisco configuration guides relied on for pre-suit knowledge and specific intent).

What it does not establish: the identity of any attorney. Third-party case trackers I checked — Unified Patents' litigation portal (2:25-cv-01038) and the Ex Parte AI Lab docket page (link) — both carry an "Attorney" field for this case, but the field did not render in the indexed text I could retrieve. I also could not retrieve a CourtListener/RECAP docket sheet for this case (no result), and it is not in the Justia dockets listing beyond a caption entry. I found no Law360 or Reuters counsel-line coverage of the appearance.

One substantive caution about inference

EDS is docketed as a patent assertion entity (Unified Patents classifies it as an NPE), and the complaint's pedigree — a 2025 reissue (RE50,398, reissued Apr. 22, 2025 from U.S. Patent No. 9,185,151) plus four 1990s–2000s networking patents ('855, '605, '234, '135) — is consistent with a monetization program that may use a high-volume Texas plaintiff's firm. But that is pattern-matching, not evidence, and I will not translate it into names. Likewise, the Cisco defense side is well documented in E.D. Tex. (e.g., Brian Rosenthal of Gibson, Dunn & Crutcher has served as Cisco's lead trial counsel in several E.D. Tex. networking-patent cases, per his firm bio), and Cisco's fee/sanctions litigation against William Ramey and Ramey LLP in the W.D. Tex. mCom line of cases is well known — none of that identifies EDS's counsel here, and neither name should be imported into this case without a docket confirmation.

How to confirm (recommended before publication)

1. PACER docket sheet for 2:25-cv-01038-JRG — the ECF "Attorneys" tab lists every attorney with a bar number, firm, address, phone, and email, and flags lead vs. appearing-pro-hac-vice counsel.
2. Dkt. 1 and Dkt. 22 signature blocks — for E.D. Tex. Local Rule 11 compliance these carry the lead attorney's name, State Bar No., firm, and full address; the FAC (Dkt. 22) is the more current of the two.
3. Dkt. 30-ish response to Dkt. 26 — the opposition brief's signature block and certificate of service should list all counsel who have appeared, including any local E.D. Tex. counsel retained to satisfy Local Rule 83.1 / Judge Gilstrap's practice requirements.
4. Pro hac vice orders, if any — neither briefing to date suggests a contested admission fight, but any PHV order would name out-of-state counsel and the local sponsoring attorney.
5. Corporate disclosure statement (Fed. R. Civ. P. 7.1) — in an NPE case this often reveals the parent/affiliate entity and sometimes the same counsel handling the portfolio's other suits, which is a fast cross-check against any other EDS filings.

If you can pull the docket sheet or the Dkt. 22 PDF, I'll build the full counsel table (name, role, firm/office, bar number, and verified patent-litigation track record from their other E.D. Tex. appearances) against it.

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

Let me pull the docket sheet and any filings that list counsel.

Bottom line on counsel of record

I was not able to retrieve a PACER docket sheet for 2:25-cv-01038-JRG that lists counsel of record, and I could not verify the signature blocks on Cisco's filings in this case (e.g., Dkt. 17, Dkt. 26, Cisco's answer). Everything I can confirm about Cisco's defense team comes from a companion Cisco case in the same court before the same judge, so the names below should be treated as a strong indication, not a verified list for this docket.

---

What is confirmed about this case (docket facts)

Nothing in what I retrieved shows a sealed appearance, a pro hac vice order, or a disqualification in this case — the record simply was not accessible to me at the counsel level.

---

Cisco's likely defense team (inferred from the related docket — verify before relying)

Cisco is defending a separate E.D. Tex. patent case before Judge Gilstrap, Lionra Technologies Ltd. v. Cisco Systems, Inc., No. 2:24-cv-00097-JRG. The joint motion at Dkt. 40 in that case carries Cisco's full signature block (CourtListener RECAP PDF):

Important caveat: I have not seen a filing in 2:25-cv-01038 bearing these names. Cisco sometimes staffs different matters with different outside counsel, and the Dallas/New York mix above is case-specific to Lionra. Do not cite this table as "counsel of record in EDS v. Cisco" without checking the docket.

---

What I could not verify (and would flag in a memo)

• Lead counsel designation in this case — no Rule 11 / signature-block confirmation obtained. Cisco's answer to the FAC and the Dkt. 26 motion would both carry it.
• Pro hac vice admissions — if Gibson Dunn attorneys are appearing, the E.D. Tex. pro hac vice orders (typically entered within 30 days of first appearance) would name them and reveal whether the Lionra roster carried over.
• In-house counsel — no Cisco legal-department attorney appeared on the Lionra docket; corporate counsel (Cisco Legal, San Jose) would not normally enter an appearance. Nothing indicates otherwise here.
• Whether any appearance was sealed — possible in principle but no evidence of it.

---

Suggested verification path

1. PACER → E.D. Tex. 2:25-cv-01038-JRG, run the "Attorneys" / "Parties" tab (or the docket report header, which lists all counsel with bar numbers and firm addresses).
2. Pull Dkt. 17 (first MTD, 12/19/2025) and Dkt. 26 (second MTD, 1/30/2026) — the signature blocks are the authoritative counsel list as of early 2026.
3. Check the pro hac vice orders docketed between Oct. 2025 and Feb. 2026.
4. Cross-check PTAB — if Cisco filed IPRs against the '605, '855, '234, '135 or RE50,398 patents, the mandatory notices there list litigation counsel and confirm the team.

If you want, I can next attempt to pull the Dkt. 26 signature block or check for parallel Cisco IPR petitions on these five patents.