Litigation

Realtime Adaptive Streaming LLC v. Cisco Systems, Inc.

6:17-cv-00591

Patents at issue (1)

Summary

Realtime Adaptive Streaming LLC filed suit against Cisco Systems, Inc. in the Eastern District of Texas. The action is identified as involving U.S. Patent 8,929,442.

Case overview & background

Plain-language overview of the case: parties, accused product, patents at issue, and why the suit matters.

I'll research this case thoroughly across dockets, court opinions, and IPR records.

Let me dig into the IPR proceedings and the '442 patent's technical content and outcome.

Now let me verify the case disposition, the Cisco IPR outcome, and the Paul Fallon/Realtime entity structure.

Key legal developments & outcome

Major rulings, motions, claim construction, settlements, and the present posture or final disposition.

I'll research this case systematically, starting with the docket and the asserted patent.

Let me dig into the actual docket and the Cisco IPR.

Let me pull the actual docket record.

In the news

What the press has reported about this case, summarized with links to the source articles.

I'll research press coverage of this case and the related Realtime Adaptive Streaming campaign.

Let me check the specific IPWatchdog roundups and search for broader coverage of the Realtime campaign.

Let me check the four IPWatchdog roundups directly to see whether they mention this case.

Press coverage of Realtime Adaptive Streaming v. Cisco — findings

Bottom line: I found no press article specifically reporting on this lawsuit. Searching the caption, the parties, the '442 patent number, and the Realtime campaign across the outlets you named turned up court and PTAB records (docket mirrors, JPML orders, IPR papers, complaints hosted on RPX/Justia) but no Reuters, Bloomberg Law, Law360, Ars Technica, Verge, or trade-press story about the Cisco action itself. That is consistent with the record: the case was a short-lived 2017–18 E.D. Tex. filing that was stayed and then dismissed with prejudice on the parties' joint motion in September 2018 without any reported verdict, damages award, or announced settlement terms — so there was no news event for the press to cover, and I found no reporting on what consideration, if any, accompanied the dismissal. I would not infer settlement figures from the dismissal order; nothing in what I could retrieve supports one.

On the four IPWatchdog roundups you flagged: these are weekly docket-statistics columns (tables of new PTAB and district court filings with patent numbers), not case analysis, and I could not verify that any of them discusses the Cisco action. The 2020-03-25 installment — IPWatchdog — is built around Medtronic/Axonics IPRs and a cluster of WSOU Investments complaints against Huawei; the only Cisco entry in that week's district-court table is Cisco as plaintiff against Capella Photonics on patent RE47905 (3:20-cv-01858), which is unrelated to this case. Because the Cisco–Realtime action was already dismissed by 2018, a 2020 new-filings roundup would not normally reference it at all. I could not open the 2020-04-09, 2020-04-22, or 2020-11-19 columns to check their full text, so treat their relevance to this case as unverified rather than as evidence of coverage.

The press coverage that does exist concerns the wider Realtime campaign, not Cisco. Most notably, IPWatchdog's patents archive carries a post (surfaced at IPWatchdog, though I could not open the underlying article to confirm its date or byline) reporting that the Federal Circuit issued a precedential decision affirming in part a California district court's award of attorneys' fees to Netflix for Realtime Adaptive Streaming's "improper" litigation conduct — characterizing Realtime's forum-shopping to avoid an adverse ruling as "gamesmanship" amounting to "a willful action for an improper purpose, tantamount to bad faith," in an opinion authored by Judge Chen with Judge Reyna concurring in part and dissenting in part. The related Federal Circuit fee appeal in the DISH/Sling line of cases, Realtime Adaptive Streaming L.L.C. v. Sling TV, L.L.C., likewise addresses Realtime's litigation conduct and the Board's treatment of the '535 and '610 patents rather than anything Cisco-specific. Those decisions are the real "industry reaction" story about this patent family, and they are reported as appellate fee/eligibility developments in other Realtime matters — not as coverage of 6:17-cv-00591.

Caveat and next step. I am reporting a genuine absence of coverage, not a search failure I can fully rule out: my access here was through general web search, and paywalled databases (Law360, Bloomberg Law, Docket Navigator's litigation news feed, Lex Machina) are not indexed in a way that surfaced here. If your client needs a defensible "no press" conclusion for this docket, a LexisNexis/News+ or Law360 name search on "Realtime Adaptive Streaming" paired with "Cisco" is the right confirmation step; on the open web, the accurate summary is that the Cisco suit generated no substantive press attention of its own.

Sources

Plaintiff representatives

Counsel of record for the plaintiff(s): attorneys, firms, and roles (lead counsel, of counsel, local counsel).

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

Defendant representatives

Counsel of record for the defendant(s): attorneys, firms, and roles (lead counsel, of counsel, local counsel).

I'll research the docket and firm records for Cisco's counsel in this action.

UniCourt lists a single defendant attorney. Let me verify against the docket and the actual filings.

Let me pull the docket mirrors that list party counsel, and check the JPML docket.

Counsel of record for Cisco Systems, Inc. — 6:17-cv-00591

Bottom line

The docket mirrors for this action identify exactly one attorney as counsel for Cisco: Michael E. Jones of Potter Minton, P.C. (Tyler, Texas). He appears to have served as Cisco's local counsel — the role Potter Minton plays for Cisco in essentially every E.D. Tex. matter — and no lead/pro hac vice counsel from a national firm is reflected in the public docket data I could reach. I could not verify a national-firm lead counsel, and I will not guess at one.

Attorney Role Firm / office Note on experience
Michael E. Jones (Tex. Bar No. 10929400; mikejones@potterminton.com) Local counsel — the only defendant attorney listed on the docket Potter Minton, P.C., 110 N. College Ave. (Suite 500 at the time; firm now lists Suite 900), Tyler, TX 75702; (903) 597-8311 Potter Minton shareholder and Cisco's long-standing East Texas local counsel: VirnetX v. Cisco, No. 6:10-cv-417 (E.D. Tex.) (with Desmarais LLP as national counsel); ESN, LLC v. Cisco, No. 5:08-cv-20 (E.D. Tex.); Monarch Networking Solutions v. Cisco, No. 2:20-cv-15 (E.D. Tex.); Paltalk Holdings v. Cisco, No. 6:21-cv-757 (W.D. Tex.).
No confirmed lead / national counsel — — See caveat below.

Sourcing and what it does and does not prove

  • UniCourt's docket summary for 6:17-cv-00591, last refreshed from the district court data on 2018-03-29, lists seven plaintiff-side attorneys (Claire Abernathy Henry, Thomas John Ward Jr., C. Jay Chung, Brian D. Ledahl, Reza Mirzaie, Timothy T. Hsieh, Philip X. Wang — the Ward Smith & Hill / Russ August & Kabat teams) and, under "Defendant Attorney," Michael E Jones alone: UniCourt docket.
  • The PlainSite docket mirror confirms Cisco actively litigated (corporate disclosure statement; letter brief; motion to dismiss the first amended complaint at Dkt. 39) but its public party/counsel summary does not add attorneys beyond the above: PlainSite docket.
  • Jones's signature block and Cisco-local-counsel role are documented in numerous Cisco filings, e.g. his notice of appearance for Cisco in Paltalk Holdings, Inc. v. Cisco Systems, Inc., No. 6:21-cv-757 (W.D. Tex.), Dkt. 47, and the VirnetX-era E.D. Tex. joint filings listing him alongside Desmarais LLP as "OF COUNSEL" for Cisco, Dkt. 683.

Caveats the client should know

  1. No PACER verification. I do not have direct PACER/CM-ECF access here; the identification of Jones rests on two independent docket aggregators (UniCourt and PlainSite) and on his documented pattern of appearing for Cisco in Texas. The filings themselves (the Dkt. 39 motion to dismiss, Cisco's answer, the Dkt. 88 joint motion to dismiss) are the authoritative source for the full signature block, and I could not retrieve them.
  2. Likely unlisted pro hac vice counsel. Cisco's consistent practice in Texas patent cases is a two-tier team: Potter Minton as local counsel plus a national firm (Desmarais LLP in VirnetX and Monarch; Quinn Emanuel in the 2008–09 ESN matter). It is therefore probable that one or more out-of-state attorneys appeared pro hac vice alongside Jones in this case, but no public docket data I found names them. Since the case was dismissed with prejudice on a joint motion (Dkt. 88, 2018-09-24) — as reflected in the PTAB exhibit materials discussed in the "In the news" section — counsel's appearances would have terminated less than a year after filing, which likely explains the sparse public attorney record.
  3. PTAB counsel is a separate question. In the parallel inter partes reviews against Realtime's compression patents, the petitioner-side papers in the record I reviewed designate Baker Botts L.L.P. counsel — Jennifer Nall (Reg. No. 57,053) as lead, with Eliot Williams, Andrew Wilson and Michelle Eber as backup (PTAB petition papers). I could not confirm that Baker Botts was appearing for Cisco specifically in IPR2018-01384, nor that any of those attorneys entered an appearance in the district court case. Do not treat Baker Botts as district-court counsel of record on this record.
  4. No in-house counsel identified. Cisco filed a corporate disclosure statement (per PlainSite), but no Cisco legal-department attorney appears in the public docket data.

What would close the gaps

A PACER docket-sheet pull (the "Attorneys" tab) or the PDFs of Dkt. 39 and Dkt. 88 would definitively resolve the lead/local split and any pro hac vice admissions, at roughly $0.10/page. Lex Machina or Docket Navigator would surface the same data plus damages/outcome fields without a PACER account. If the client needs this for a conflicts check, PACER is the only reliable source — aggregator counsel lists for short-lived 2017–18 E.D. Tex. cases are frequently incomplete, as the single-name defendant listing here suggests.