Realtime Adaptive Streaming LLC v. Mitel Networks, Inc.

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

Case Overview — Realtime Adaptive Streaming LLC v. Mitel Networks, Inc., No. 1:18-cv-01177 (D. Colo.)

Parties. Plaintiff Realtime Adaptive Streaming LLC is a patent-holding entity — a non-practicing affiliate of Realtime Data LLC (which marketed itself as "IXO"), the Fallon-family data-compression portfolio owner. The patents descend from inventor James J. Fallon of Armonk, New York, and the JPML described Realtime's parent corporation as litigating "different data compression patents" in the Northern District of California separately from this campaign. In re Realtime Adaptive Streaming LLC Patent Litig., MDL No. 2845, 326 F. Supp. 3d 1374 (J.P.M.L. Aug. 1, 2018). Realtime has no product business in the accused technology; its revenue model is licensing/litigation, so treat it as a PAE/NPE on the public record (I found no evidence it manufactures anything). Defendant Mitel Networks, Inc. is the Ottawa, Ontario–headquartered business-communications vendor whose U.S. arm sells VoIP/unified-communications and collaboration platforms (MiVoice, MiCollab, conference and video endpoints) — i.e., an operating-company defendant in the enterprise telephony/UC space. Note: I could not verify Mitel's specific accused product line from a primary document (see caveats below).

Accused technology and patents. The case is one of the H.264/H.265 "standard-implementation" suits: Realtime's theory across this campaign was that products which implement industry video-compression standards (H.264/AVC, H.265/HEVC and their optional features) necessarily practice the claims. The JPML recorded that defendants in the campaign included makers of "teleconferencing systems" — the category into which Mitel's UC/video products fall — while rejecting Realtime's argument that shared standards justified centralization because the standards "include purely optional features that each defendant may or may not have implemented." 326 F. Supp. 3d 1374. Although the case metadata lists only U.S. Patent No. 7,386,046, PACER-derived docket indexes tag the Mitel case with three patents: the '046 ("Bandwidth Sensitive Data Compression and Decompression," filed Feb. 13, 2002) — claims a compressor that applies a first compression routine, tracks system throughput (including "tracking a number of pending requests for data transmission"), and switches to a higher-rate second routine when throughput falls below a threshold (claim 1 quoted in the D. Del. opinion in C.A. No. 17-1692, https://www.ded.uscourts.gov/sites/ded/files/opinions/17-1692.pdf); the '535 patent; and the '477 patent ("Video data compression systems," issued Sept. 19, 2017) —

I'll research this case across multiple sources.

Realtime Adaptive Streaming LLC v. Mitel Networks, Inc., No. 1:18-cv-01177 (D. Colo.)

Bottom line up front

This is a thin-file case. It was one of roughly twenty complaints Realtime Adaptive Streaming LLC ("Realtime") filed against hardware, software, and streaming defendants in 2017–2018, asserting the James J. Fallon compression patent family. U.S. Patent No. 7,386,046 ("Bandwidth Sensitive Data Compression and Decompression," issued 2008-06-10, filed 2002-02-13) was the asserted patent here. The case is closed on the docket (PACER-derived aggregators show status "Closed"), but I was not able to retrieve the operative dismissal/settlement entry through the free sources available to me in this session. Critically, I found no evidence of a Markman order, summary-judgment ruling, trial, verdict, or appeal in this specific case — and the absence is meaningful, because the record I could verify shows the '046 patent was being litigated to judgment in other fora (the PTAB and the District of Delaware) during precisely the window in which this case went quiet.

I have flagged every unverified proposition below rather than filling gaps.

---

I. Case snapshot (verified from metadata/docket aggregators)

Sources: Justia Dockets, https://dockets.justia.com/docket/colorado/codce/1:2018cv01177/[180044](/patent/180044); Docket Alarm, https://www.docketalarm.com/search/?q=patent:(7386046); Ex Parte case page (PACER-derived), https://ai-lab.exparte.com/case/dct/cod/1:18-cv-01177/realtime-adaptive-streaming-llc-v-mitel-networks-inc.

Sourcing caveat on the cause-of-action field. Justia lists the cause as "15 U.S.C. § 1126," which is the Lanham Act. That is almost certainly a CM/ECF nature-of-suit coding artifact (Realtime's complaints uniformly plead 35 U.S.C. § 271 infringement). Nature of suit is correctly coded 830 (Patent).

Sourcing caveat on the patent count. Docket Alarm's tag set for this docket shows 7386046; 8934535; 9769477, while

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

Let me pull the docket details directly.

Counsel of Record for Plaintiff Realtime Adaptive Streaming LLC — Realtime Adaptive Streaming LLC v. Mitel Networks, Inc., No. 1:18-cv-01177-RM-MEH (D. Colo.)

Verification caveat up front: I was not able to open the raw PACER docket sheet for this case directly. My sourcing is the Justia PACER-derived docket page for this exact case, the Unified Patents litigation portal docket for the companion case, and briefing/docket materials from Realtime's parallel Colorado cases in which the same team appeared. I flag below which entries I confirmed on this docket versus inferred from the companion filings.

Confirmed on this docket (Justia's PACER extract for 1:18-cv-01177)

Highly likely but not independently confirmed on this docket

These attorneys are documented as plaintiff's counsel in Realtime's other May–June 2018 Colorado complaints (same day/near-same-day filings, same patent family) and in the related Realtime Adaptive Streaming v. Sling TV/DISH, No. 1:17-cv-02097 (D. Colo.) case, where the court's own order listed the plaintiff's full trial team:

• Marc A. Fenster (RAK, Los Angeles) — the firm's founding patent-litigation partner and the habitual "principal counsel" for Realtime entities; signed the client's Rule 7.1 certification in Realtime v. Hulu and entered appearances in the companion D. Colo. cases. If a single attorney is "lead counsel" for the campaign, it is Fenster, but I could not confirm a docket entry in 1:18-cv-01177 specifically.
• Reza Mirzaie (RAK, Los Angeles) — entered appearance in the Intel companion case (1:18-cv-01175) on 6/4/2018.
• Eric B. Fenster (Eric B. Fenster, LLC, 1522 Blake St., Denver, CO) — Colorado local counsel. He filed the complaints in the May 15, 2018 Colorado batch (e.g., 1:18-cv-01175 against Intel), which is the cleanest evidence of his role as the Colorado-admitted sponsoring attorney for this family of suits.
• Marc Aaron Fenster / Timothy T. Hsieh — also entered appearances in the companion Colorado Realtime matters; I could not confirm them on this docket.

Practical notes

• Case status: Third-party dockets list 1:18-cv-01177 as closed. Realtime's Colorado campaign against hardware/codec defendants settled quickly in this period (e.g., the related Realtime v. Computer Chip Manufacturing matter settled in October 2018), but I could not verify the specific terminating docket entry (dismissal stipulation) for Mitel and won't attribute one.
• Patent actually asserted: Docket Alarm's patent tagging for this docket lists 7,386,046, 8,934,535 and 9,769,477, broader than the single '046 patent in the case metadata — consistent with Realtime's standard three-patent Colorado complaint template.
• Counsel changes: In the PTAB track, Realtime later substituted Noroozi PC (Kayvan B. Noroozi, Joel P.N. Stonedale, William P. Rothwell) as lead PTAB counsel in 2019, with RAK remaining as back-up. I found no evidence that Noroozi PC appeared in this district court case, so I have not listed them as counsel of record here.
• Relevant outcome context for the team: The Federal Circuit vacated a D. Colo. fee award against Realtime Adaptive Streaming in the DISH/Sling litigation (opinion by Judge Albright sitting by designation) — a matter handled by this same RAK team.
• Not verified / not to be assumed: I found no in-house counsel for Realtime Adaptive Streaming (a Tyler, Texas LLC managed by Richard G. Tashjian) appearing of record, and no sealed-entry indication on this docket.

I'll research counsel of record for Mitel Networks in this D. Colo. action.

Counsel of record for Mitel Networks, Inc. — research status

Bottom line up front

I could not verify the name of any attorney who appeared for Mitel Networks, Inc. in No. 1:18-cv-01177 (D. Colo.). None of the free/PACER-derived sources reachable in this session surfaced a defense appearance, answer, corporate disclosure statement, or motion signed by Mitel's counsel. Per the operating rules, I am not going to name counsel by inference or pattern-matching from Realtime's other cases. The honest answer is: defense counsel are unverified, and there is a real possibility that no defense appearance was ever entered because the case resolved before Mitel responded — but I could not confirm that either, so treat it as a hypothesis, not a finding.

---

I. What is verified — and a warning about the Justia "Represented By" trap

Justia's docket page for this case lists a "Represented By" block reading Jay Young Chung; Eric Bryan Fenster; Marc Aaron Fenster; Brian David Ledahl; Reza Mirzaie; Philip X. [Wang]. See https://dockets.justia.com/docket/colorado/codce/1:2018cv01177/180044.

These are plaintiff-side attorneys, not Mitel's. Every one of those names is a Russ August & Kabat (Los Angeles) lawyer, and RAK — together with Noroozi PC — was Realtime Adaptive Streaming's standing litigation and PTAB team across the Fallon patent family. That is independently corroborated in the PTAB record for the sibling Realtime IPRs, where RAK's Neil A. Rubin (Reg. No. 67,030) and Kent Shum (Reg. No. 61,117) appear as Patent Owner's backup counsel (e.g., Realtime's Power of Attorney, IPR2018-01187, filed 2018-06-21, and its Updated Mandatory Notices, 2019-08-23, both available via Docket Alarm: https://www.docketalarm.com/cases/PTAB/IPR2018-01187/).

So the Justia block is plaintiff's counsel, and it should not be attributed to the defendant. Anyone reading that page quickly would make that error; I'm flagging it explicitly.

---

II. Names I affirmatively ruled out (frequently mis-attributed to this case)

Because Realtime sued ~20 defendants at once in D. Colo., counsel from sibling matters are easy to mis-assign. The following all appear in Realtime-adjacent records but are not Mitel's counsel in 1:18-cv-01177:

Sourcing: IPR2018-01187 papers (Docket Alarm links above); PTAB petitions indexing Realtime's litigation campaign (ptacts.uspto.gov); Docket Alarm doc. 75 in Realtime v. Sling TV, https://www.docketalarm.com/cases/Colorado_District_Court/1--17-cv-02097/.

I also located a CourtListener RECAP PDF (gov.uscourts.ded.48346.20.2) captioned for "MITEL NETWORKS CORPORATION and MITEL (DELAWARE), INC." — but that is a D. Del. docket, a different case and different defendant entities, and I could not read the signing firm from the snippet. Do not import that counsel into this case.

---

III. What the record shape suggests (flagged as inference, not fact)

• The case was filed 2018-05-15 and is listed "Closed" by PACER-derived aggregators (Ex Parte: https://ai-lab.exparte.com/case/dct/cod/1:18-cv-01177/realtime-adaptive-streaming-llc-v-mitel-networks-inc).
• Its immediate neighbor, Realtime v. Intel Corp., No. 1:18-cv-01175, shows a full defense response — Intel's Answer and Counterclaims filed 2018-07-03 (cited in the '417 patent prosecution/IDS history reproduced at https://patentimages.storage.googleapis.com/24/47/c6/8a11de5624c986/[US10212417](/patent/US10212417).pdf). By contrast, no analogous Mitel answer or motion surfaced for 01177 in any source I could reach.
• Inference (unverified): Mitel likely resolved or was dismissed early — plausibly before an appearance or answer — consistent with the pattern of several smaller Realtime targets. If a dismissal was filed before any appearance, then as a matter of record there simply are no "counsel of record" for Mitel, and the correct answer to the research question is "none of record."

I could not retrieve the dismissal/settlement entry either — the same gap noted in the prior section of this case summary. The two gaps are probably the same gap: whatever short docket entry ends this case (likely a Rule 41(a) notice or joint stipulation of dismissal) is the document that would confirm or refute the "no appearance" hypothesis.

---

IV. Contradictions to flag against the earlier sections

1. Case-number/filename confusion in a secondary source. The patent-images compilation at US10212417.pdf twice attributes case no. 1:18-cv-01177 to Intel ("Realtime Adaptive Streaming LLC v. Intel Networks, Inc., Case No. 1:18-cv-01177" and "v. Intel Corporation, 1:18-cv-01177"), while elsewhere correctly using 1:18-cv-01175 for Intel. Per your operating rule, I prefer the case metadata: 01177 = Mitel Networks, Inc.; 01175 = Intel. The patent-images text appears to be an OCR/compilation error.
2. The prior "Key legal developments" section is truncated mid-sentence at "Docket Alarm's tag set for this docket shows 7386046; 8934535; 9769477, while —". That list is corroborated by Docket Alarm's patent search index (https://www.docketalarm.com/search/?q=patent:(8934535) and https://ocr.docketalarm.com/search/?q=patent:(9769477)), both of which return "Docket 1:18-cv-01177, Colorado District Court (May 15, 2018), Judge Raymond P. Moore … Magistrate Judge Michael E. Hegarty." Note this conflicts with the prompt's single-patent field ('046 only); the docket tags suggest '046, '535, and '477 were all pleaded.

---

V. How to close this out (concrete next steps)

Because PACER's appearance records are behind a paywall I can't reach here, the definitive check is cheap and takes minutes:

1. Pull the full PACER docket sheet for 1:18-cv-01177 and read entries 1–20. Look specifically for CM/ECF filer names on: (a) any Notice of Appearance, (b) Corporate Disclosure Statement (Mitel Networks, Inc. is a Canadian-owned entity — a disclosure statement, if filed, will name the parent), (c) Answer/Affirmative Defenses, (d) the dismissal entry.
2. Search PACER's "Attorneys" tab for the case — this lists every attorney who has entered an appearance regardless of whether they signed a substantive paper.
3. Cross-check the D. Colo. attorney roll (https://www.cod.uscourts.gov) for local counsel; Realtime's Colorado patent cases of that vintage typically paired national IP counsel with a Denver firm.
4. Check whether Mitel filed an IPR against the '046 patent. If Mitel petitioned the PTAB, its petition's mandatory notices would name both its PTAB and its district-court counsel (as the Google/Paul Hastings and Hulu/Baker Botts notices did here) — that is the single most likely place to find the answer in free sources.

If you can supply the PACER docket text for documents 8–20, I can identify lead counsel, local counsel, and firm affiliations precisely rather than by inference.