Realtime Adaptive Streaming LLC v. Wowza Media Systems, LLC

I'll research this case thoroughly using web search, starting with the basic docket and party information.

Let me dig into the dismissal, any IPR filings by Wowza, and the broader Realtime campaign context.

Let me check the full docket and the terms of dismissal, plus Wowza's corporate profile.

Case Overview — Realtime Adaptive Streaming LLC v. Wowza Media Systems, LLC, No. 1:18-cv-00927-MJW (D. Colo.)

The parties. Plaintiff Realtime Adaptive Streaming LLC ("RAS") is a patent-assertion entity — the video-compression-focused subsidiary of Realtime Data LLC (d/b/a IXO), one of the most prolific NPE campaigns of the past decade. By the time RAS sued Wowza, RPX reported that the Realtime Data/RAS campaign had named more than 115 defendants and asserted close to 40 patents, with RAS targeting video streaming services, cloud providers, set-top box and TV makers, and handset/tablet manufacturers (RPX Patent Risk Digest, Oct. 2018, https://www.rpxcorp.com/digest/october-2018/). Unified Patents classifies RAS as an "NPE (Patent Assertion Entity)" (https://portal.unifiedpatents.com/litigation/Colorado%20District%20Court/case/1:18-cv-00927). Defendant Wowza Media Systems, LLC is a genuine operating company — a streaming-video software and infrastructure vendor (Streaming Engine, Streaming Cloud, ClearCaster, GoCoder) headquartered at 523 Park Point Drive, Golden, Colorado, and a Delaware LLC whose corporate parent is Wowza Media Holdings, LLC (Wowza Answer, Dkt. 28, ¶ 2; Corporate Disclosure Statement). Notably, RAS's litigation counsel of record included Eric B. Fenster, Marc A. Fenster, Reza Mirzaie, Brian D. Ledahl, Jay Y. Chung, Philip X. Wang, and Paul A. Kroeger (per docket entries of May 2018); Wowza was represented by Sundeep K. Addy, Katherine L.I. Hacker, and Eric R. Olson. I have not independently verified each attorney's firm affiliation, so I flag that rather than assert it.

The technology and patents asserted. The complaint, filed April 20, 2018, accused Wowza's streaming products/services — specifically Wowza ClearCaster, Wowza Streaming Cloud, Wowza Streaming Engine, and Wowza GoCoder — of infringing five patents (Compl., Dkt. 1, ¶¶ 6–11, 13). The theory was that Wowza's standards-compliant adaptive-bitrate pipeline (H.264/AVC and HEVC/H.265, HLS delivery, a transcoder that ingests one stream and emits multiple aligned-keyframe renditions so players can switch bitrates as bandwidth rises and falls) practiced the claims. The five patents: '046 (U.S. 7,386,046, "Bandwidth Sensitive Data Compression and Decompression," issued June 10, 2008) — a compression engine that monitors throughput (e.g., pending storage access requests) and switches among compression algorithms when throughput drops below a threshold; asserted via claim 40 (see also D. Del. R&R, C.A. No. 17-1692, quoting claim 1). '535 (U.S. 8,934,535, "Systems and Methods for Video and Audio Data Storage and Distribution," issued Jan. 13, 2015) — selecting among "asymmetric compressors" based on a measured data-block parameter (representative claim 15). '477 (U.S. 9,769,477, "Video Data Compression Systems," issued Sept. 19, 2017) — multiple asymmetric encoders with different compression rates, selected based on channel-throughput parameters (claim 1). '462 (U.S. 8,634,462, "Quantization for Hybrid Video Coding," issued Jan. 21, 2014) — quantization in a hybrid video codec. '298 (U.S. 9,578,298, "Method for Decoding 2D-Compatible Stereoscopic Video Flows," issued Feb. 21, 2017) — decoding stereoscopic/3D video that remains backward-compatible with 2D players. The '046/'535/'477 are James J. Fallon-lineage Realtime Data compression patents from the same family; the '462 and '298 appear to come from different origins (the '298 claim chart in the complaint targets HEVC metadata/SEI and tile-decoding features), but I could not verify their original assignees from the sources I reviewed. One data-hygiene point: the case metadata supplied lists only the '046 as the patent at issue, whereas the complaint and Wowza's answer both confirm five patents-in-suit — the '046 is simply the lead/representative patent carried in that tracker.

Posture, venue, and significance. The case landed in the District of Colorado because Wowza's principal place of business is in Golden, making venue proper under 28 U.S.C. § 1400(b) — a point Wowza admitted (Answer ¶ 5) — and RAS deliberately clustered Colorado filings against resident or high-presence tech defendants (Apple, Polycom, Sling TV, Avaya, Broadcom, AMD, Intel, Mitel, Charter, Comcast). The case was assigned to District Judge R. Brooke Jackson, with Magistrate Judge Michael J. Watanabe handling the initial scheduling order (Dkt. entry 4/23/2018; minute order 8/1/2018 setting a 9/27/2018 scheduling conference). It never reached claim construction: Wowza answered in June 2018 denying infringement and validity (Dkt. 28), and on September 28, 2018 the parties filed a joint motion to dismiss (Dkt. 29), with termination recorded September 30/October 1, 2018 and third-party trackers labeling the disposition "Dismissed – Settled" (Unified Patents; Patexia, https://services.patexia.com/lawsuits/Realtime-Adaptive-Streaming-LLC-v-Wowza-Media-Systems-LLC-id-[112685](/patent/112685)). I could not verify from accessible records whether dismissal was with or without prejudice, or whether a license was taken — so treat the "settled" characterization as tracker-reported, not confirmed by an opinion. Context that makes this short-lived case notable: (1) it was one of twelve RAS actions in five districts that RAS tried to consolidate as MDL No. 2845; on August 1, 2018 the Judicial Panel on Multidistrict Litigation denied centralization, reasoning that although the eight asserted patents came from only three families and the accused products implement H.264/H.265, the standards contain optional features and design latitude requiring defendant-by-defendant analysis — thereby converting the campaign into dozens of parallel, one-off suits (In re Realtime Adaptive Streaming LLC Patent Litig., 326 F. Supp. 3d 1374 (J.P.M.L. 2018)). (2) It sits inside an unusually dense PTAB shadow: the '477 was challenged in IPR2018-01187 (Amazon/Hulu/Netflix, instituted in early 2019), IPR2018-01413 (Sony, terminated Jan. 2, 2019), and IPR2018-01630 (instituted Apr. 19, 2019); the '298 was the subject of IPR2018-01227 and a Google petition; the '046 drew a Google IPR petition against claims 1 and 23; and the '535 was invalidated in final written decisions dated January 10 and January 17, 2020 (per EchoStar's 10-K disclosure of the parallel Colorado Sling TV case). I found no evidence that Wowza itself filed or joined an IPR — its challenge appears to have been confined to its answer before settlement. (3) The same Colorado docket produced the campaign's most-cited cautionary outcome: after RAS's claims against Sling TV/DISH were dismissed with prejudice, Judge Jackson found the case "exceptional" and awarded attorney fees (Law.com, Sept. 20, 2022), a ruling the Federal Circuit affirmed in No. 21-2268 (May 11, 2023). Against that backdrop, the Wowza case is best read as the campaign's "small-defendant" flank — a five-patent demand letter in complaint form against a single Colorado streaming vendor, resolved in roughly five months without any merits ruling, and now useful mainly as evidence of RAS's filing-and-settle pattern and of the Colorado venue strategy that the J.P.M.L. declined to disturb.

I'll research this case systematically, starting with the docket and key rulings.

Key facts are emerging — the case appears to have been dismissed by joint motion within ~5 months. Let me dig into the docket details and the parallel IPRs.

Good progress. Now let me pin down the actual dismissal and check the docket specifics.

Realtime Adaptive Streaming LLC v. Wowza Media Systems LLC, No. 1:18-cv-00927 (D. Colo.)

Bottom line: This was a short-lived campaign case, not a litigated dispute. It went from complaint to joint dismissal in roughly five and a half months, with no Markman hearing, no dispositive motions, no discovery of significance, no trial, and no appeal. The case-metadata patent ('046) was one of five patents Realtime asserted against Wowza; Wowza's accused products were ClearCaster, Streaming Cloud, Streaming Engine, and GoCoder. The parallel PTAB activity on the '046 patent came after this case was dismissed, and it ultimately failed to knock out the '046 (though sibling patents in the same campaign did fall).

---

1. Filing & initial pleadings

The complaint asserted five patents, not just the '046: U.S. Patent Nos. 7,386,046 ("Bandwidth Sensitive Data Compression and Decompression," issued 2008-06-10), 8,934,535, 9,769,477, 8,634,462, and 9,578,298. The '046 theory rested on independent claim 40 and accused H.264/HLS adaptive-bitrate behavior — specifically the HLS client "observing effective bandwidth" and switching renditions, mapped onto the "controller for tracking throughput" limitation. Note a doctrinal soft spot visible on the face of the complaint: claim 40 expressly defines "tracking throughput" as "tracking a number of pending access requests to a storage device," whereas the infringement theory was built on network/channel bandwidth.

Sourcing caveat: Dkt. 28's full text is available (via Docket Alarm/RPX), but I could not verify from the retrieved excerpts whether Wowza pleaded declaratory-judgment counterclaims of non-infringement/invalidity, or only affirmative defenses. The answer opens by denying infringement and validity and denying entitlement to any relief; treat the counterclaim question as unconfirmed.

Counsel of record (from docket appearance entries; firm affiliations not independently confirmed here):

• Realtime: Eric Bryan Fenster, Marc Aaron Fenster, Reza Mirzaie, Jay Young Chung, Brian David Ledahl, Philip X. Wang, Paul Anthony Kroeger (the Russ August & Kabat team that later argued Realtime's side at the Federal Circuit).
• Wowza: Sundeep Kumar Addy, Katherine L.I. Hacker, Eric R. Olson.

2. Case-management / reassignment

• 2018-07-16 — initial scheduling conference set before Magistrate Judge Watanabe (later superseded).
• 2018-08-01 — Minute order by Judge R. Brooke Jackson setting a scheduling conference for 2018-09-27, indicating the case was pulled from the magistrate track and reassigned to Judge Jackson — the judge then presiding over Realtime's related Colorado actions (e.g., Realtime Adaptive Streaming v. Sling TV et al., No. 1:17-cv-02097).

3. Multidistrict consolidation attempt (affects this case indirectly)

• 2018-08-01 — The JPML denied Realtime's § 1407 motion to centralize twelve Realtime actions in five districts involving eight patents, including the '046. In re Realtime Adaptive Streaming LLC Patent Litig., 326 F. Supp. 3d 1374 (J.P.M.L. 2018). The Panel found insufficient commonality across "video streaming services, tablet computers, televisions, ... media servers," etc., and encouraged informal coordination instead. Practical effect: Wowza's case stayed on its own track in Colorado.

4. Pre-trial motions of substance

None reached decision. No motion to dismiss, no § 1402/§ 1404 transfer motion, no motion to stay pending IPR, no summary-judgment motion, and no Alice § 101 challenge was decided in this case. (The § 101 and § 103 fights that defined the Realtime campaign were litigated in the Sling/DISH, Netflix, and other actions, not here.)

5. Claim construction

None. The case was dismissed before any Markman briefing, joint claim-construction statement, or claim-construction order. No claim terms were construed in this docket.

6. Discovery milestones

None of significance. No scheduling order appears to have issued before dismissal; no discovery disputes, no expert reports, no depositions are reflected in the docket.

7. Trial, verdict, post-trial motions

None. No trial date was set; no verdict, no JMOL/Rule 50 or Rule 59 motions, and no § 285 fee motion in this case.

8. Final disposition

Present posture: Closed since September 2018. There is no appeal and no reopened proceeding. The public docket summaries do not disclose settlement terms, and I could not verify from a primary-source order whether the dismissal was with or without prejudice — the "Dismissed – Settled" status flag suggests a prejudice-bearing dismissal, but that should be confirmed against the actual order text on PACER (Dkt. entry ~87–88) before being relied on. No license or payment terms are public.

9. Parallel PTAB proceedings on the '046 patent

No IPR was filed by Wowza. The '046 challenges came from Realtime's larger campaign defendants, and all post-date this dismissal:

Federal Circuit: Comcast Cable Communications, LLC v. Realtime Adaptive Streaming LLC, No. 2020-2281 (Fed. Cir. 2022-06-15) — affirmed under Fed. Cir. R. 36 (nonprecedential; Lourie, Prost, Taranto). Philip X. Wang (Russ August & Kabat) argued for Realtime. Net effect: the '046 patent survived the IPR gauntlet, but by then Realtime had no live case against Wowza in which to exploit it.

Contrast with sibling patents (context for why the campaign collapsed):

• The '535 patent — also asserted against Wowza — was invalidated in Netflix's IPR (FWD 2020-01-10, 2020 WL 120083) and in a Google IPR (FWD 2020-02-27).
• The '477 patent — also asserted against Wowza — was subject to an IPR certificate (US 9,769,477 K1) reflecting cancellation of claims 1–29 (per secondary reporting; certificate date not verified here).
• In the related Colorado Sling TV/DISH action, the court later found the case "exceptional" under § 285 and awarded defendants attorney fees (reported 2022-09-20); on appeal the Federal Circuit confronted Realtime's double voluntary-dismissal/forum-shopping conduct. That fee litigation — not this Wowza docket — is where the real appellate law from this campaign was made.

---

Assessment

For a Wowza-specific risk read, this docket offers essentially no legal precedent and no substantive ruling — its value is (a) evidentiary, as a data point on the breadth and timing of the Realtime campaign (April 2018 filing wave, including AMD in June 2018), and (b) as confirmation that Wowza exited early and cheaply, in the same September 2018 window in which Realtime dismissed or settled several other actions (compare the E.D. Tex. and N.D. Cal. dismissals entered 2018-09-24 and 2018-10-02). Any conclusion about why Wowza settled — license, nuisance value, or the JPML's refusal to centralize — is unsourced speculation at this point.

Unverified items to confirm on PACER: (1) exact prejudice terms

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

Let me pull the full docket entry list and confirm each appearance.

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

Defendant's Counsel of Record — Wowza Media Systems, LLC

Bottom line

Wowza was represented by a single trial team out of Bartlit Beck Herman Palenchar & Scott LLP, in that firm's Denver office. Bartlit Beck is a Denver-headquartered trial boutique, so no separate "local counsel" was required in the District of Colorado — the Denver-resident Bartlit Beck lawyers served that function directly. Four attorneys entered appearances for Wowza between May 14 and mid-2018, per the docket:

Docket corroboration: the Unified Patents litigation portal docket for 1:18-cv-00927 lists, in sequence, "NOTICE of Entry of Appearance by Sundeep Kumar Addy on behalf of Wowza Media Systems, LLCAttorney Sundeep Kumar Addy added to party Wowza Media Systems, LLC(pty:dft) (Entered: 05/14/2018)," followed by notices of appearance by Katherine L.I. Hacker, Eric R. Olson, and Andrew C. Baak on Wowza's behalf. portal.unifiedpatents.com/litigation/Colorado District Court/case/1:18-cv-00927

Verification caveats — please read

• Andrew C. Baak's firm is unconfirmed. He appears on the docket as Wowza counsel, and given the composition of the team he was almost certainly a Bartlit Beck associate at the time, but I did not find a source tying him to Bartlit Beck or any later firm. Treat his firm as an open item rather than asserted fact.
• No in-house counsel appeared on the docket in the entries retrieved. Wowza is a privately held company based in Golden, Colorado (523 Park Point Drive, Suite 300); a corporate counsel may have been involved behind the scenes, but I found no appearance by any Wowza in-house lawyer and will not name one.
• No separate Colorado local counsel appeared — consistent with Bartlit Beck being a Denver firm.
• PTAB counsel should not be confused with district-court counsel. Wowza itself was not the petitioner in the Realtime Adaptive Streaming IPRs; those petitions were filed by Amazon/Hulu/Netflix (Baker Botts — Harper Batts), Google (Paul Hastings — Naveen Modi), and DISH (Fish & Richardson — Ruffin Cordell). Wowza's case is listed in those petitions only as a related co-pending litigation. Do not attribute Baker Botts, Paul Hastings, or Fish to Wowza here.

Notes that bear on the representation

• The MDL fight was the centerpiece of the defense. Realtime filed roughly two dozen suits against streaming/CDN defendants nationwide in 2017–2018, and moved to consolidate them before the Judicial Panel on Multidistrict Litigation. According to Bartlit Beck's own account, the co-defendants delegated the JPML argument to Wowza's team notwithstanding Wowza's much smaller size relative to Google, Apple, and Netflix, and the Panel declined to consolidate. Wowza then settled and exited the case within about five months of filing.
• Outcome: the docket reflects an Order of Dismissal With Prejudice by Judge R. Brooke Jackson, with a termination date of October 1, 2018 and case status "Dismissed – Settled." Patexia case summary The case had been assigned to Magistrate Judge Michael J. Watanabe at filing (case number suffix "-MJW" on the Answer) and to Judge Jackson for the scheduling conference set for 9/27/2018.
• Counsel's own bios are the best source for roles. Bartlit Beck describes Hacker as "co-lead counsel" and Addy's bio describes the representation without a title; neither firm bio uses "of counsel" or "local counsel" labels, so the role designations above for Addy and Olson are my characterizations from docket order and seniority, not quotations.

Contradiction to flag against the case metadata

The case metadata lists the patents at issue in this matter as only U.S. Patent No. 7,386,046. The operative pleadings are broader: the Complaint (Dkt. 1) and Wowza's Answer (Dkt. 28) both identify five patents-in-suit — the '046 patent, the '535 patent, the '477 patent, the '462 patent, and the '298 patent. See Wowza's Answer ("Wowza denies that it has infringed any claims of U.S. Patent Nos. 7,386,046, 8,934,535, 9,769,477, 8,634,462, and 9,578,298 (the 'patents-in-suit')"). Dkt. 28 via Docket Alarm This is consistent with the earlier sections of this case summary treating the '046 patent as merely one of several patents asserted in this and companion actions.

Sourcing note: the docket entries and firm bios above were retrieved from the Unified Patents litigation portal, Docket Alarm, and bartlit-beck.com. I ran out of search budget before I could pull the PACER docket sheet itself or the signature block of Dkt. 28, which would be the authoritative confirmation of each attorney's firm and bar status as of the 2018 filings. If you need court-certified counsel data, that signature block and the Dkt. 5–8 notices of appearance are the documents to order.