Realtime Adaptive Streaming LLC v. Intel Corporation

I'll research this case carefully, starting with the docket and party background.

Now let me dig into the docket history, outcomes, and the parallel PTAB proceedings.

Let me verify party background, the other asserted patents, and the PTAB outcomes.

Case Overview — Realtime Adaptive Streaming LLC v. Intel Corp., No. 1:18-cv-01175 (D. Colo.)

Parties. Plaintiff Realtime Adaptive Streaming LLC is a patent-holding entity — an NPE/PAE — that is an affiliate of Realtime Data LLC d/b/a IXO, the Tyler, Texas– and Bronxville, New York–based monetization vehicle for the "Fallon patents" (named for inventor James J. Fallon) covering data compression and storage acceleration. Realtime's portfolios were assembled and litigated for licensing revenue rather than products: in the related Colorado case (Realtime Adaptive Streaming v. Sling TV, No. 1:17-cv-02097-RBJ), Judge R. Brooke Jackson recorded the defendants' characterization of Realtime as a "serial litigant" that had filed roughly 145 cases and was "created by a patent attorney for the purpose of licensing and monetizing patents," while noting those facts did not bear on the merits of a particular case (Fee Order, Dkt. 326 at 3–4). Realtime later became a frequent target of § 285 fee motions and § 101 invalidity rulings in Delaware, California, and Colorado. Defendant Intel Corporation is the Delaware-incorporated, Santa Clara–headquartered semiconductor manufacturer; it conceded venue in Colorado for this case only, based on its offices in Broomfield, Englewood, Fort Collins, Longmont, and Westminster (Answer & Counterclaims, Dkt. 21 ¶ 2, 5).

Accused technology and patents. The complaint targeted Intel's QuickSync Video, the fixed-function media processing block built into Intel Core processors (the complaint's illustrative list is the 8th-generation Coffee Lake family: Core i9-8950HK, i7-8850H, i7-8750H, i5-8500B, i3-8300T), alleging that QuickSync's H.264 encoding — specifically Scalable Video Coding (Annex G) and the selection among H.264 profiles and their CAVLC/CABAC entropy coders based on bandwidth or bitrate — practices the asserted claims (Compl. Dkt. 1 ¶¶ 11–19). The complaint pleaded three patents: U.S. 7,386,046 ("Bandwidth sensitive data compression and decompression," filed Feb. 13, 2002, issued June 10, 2008, Fallon), asserted through claim 40 — a system claim requiring a controller that tracks throughput (including pending access requests to a storage device) and switches to a faster compression routine when throughput falls below a threshold; plus U.S. 8,634,462 and U.S. 8,934,535, related Fallon-family compression patents. (The case metadata lists only the '046; that is the patent the infringement analysis and the parallel PTAB proceedings centered on.) The claim-construction fault line was apparent from the pleadings: claim 40 tracks "pending access requests to a storage device," whereas the complaint mapped "throughput" to channel bandwidth/bitrate.

Procedural posture and why it matters. Filed May 15, 2018 in the District of Colorado (Denver), the case landed before Magistrate Judge Kristen L. Mix; Realtime declined consent to magistrate jurisdiction (Dkt. 24, Aug. 17, 2018), and the case was reassigned to Judge R. Brooke Jackson (Dkt. 31, Sept. 4, 2018). Intel answered on July 3, 2018 with invalidity counterclaims under §§ 101, 102, 103 and 112. The case never reached a scheduling order: Realtime filed a Notice of Settlement on September 4, 2018, the Rule 16 conference was vacated, a joint motion to dismiss followed on September 28, and Judge Jackson entered an Order of Dismissal With Prejudice on October 1, 2018 — roughly four and a half months after filing (docket via Unified Patents). No public terms, license, or payment were disclosed. The case is a specimen of Realtime's 2017–2018 blitz, in which it filed the same day against Intel, AMD (1:18-cv-01173), and Mitel (1:18-cv-01177) in Colorado, and against chipmakers, PC OEMs, and streaming services in E.D. Tex., C.D. Cal., D. Del., and D. Mass. Colorado mattered because post-TC Heartland it supplied a § 1400(b) hook (Intel's regular places of business) and, at the time, a comparatively quick docket and a receptive judge — the same judge who later awarded § 285 fees against Realtime in the Sling TV litigation. The '046 is also one of the few patents in the portfolio that survived PTAB: Netflix's IPR2019-00209 (filed Nov. 11, 2018, challenging claims 1, 4, 8, 10–11, 13–14, 16–17, 19, 21, 23–24, 26–27, 29–32, 34–35) failed on the merits, and in Google LLC v. Realtime Adaptive Streaming, IPR2019-01033, the Board's Final Written Decision of Nov. 10, 2020 held that Google/YouTube had not shown claims 1 and 23 unpatentable — in contrast to the '535 patent (claims 1–12, 14 held unpatentable in IPR2018-01169 and IPR2018-01342) and the '610 patent (invalidated under § 101 in Colorado, with fees awarded). That asymmetry — a compression-patent campaign largely dismantled by § 101 and the PTAB, yet with the '046 intact — is the main reason this short-lived, settled case remains worth citing.

Sourcing notes / open items. The docket events above are grounded in the court's own docket text as mirrored by Unified Patents and Docket Alarm; the dismissed case has no published opinion. I did not verify the exact titles of the '462 and '535 patents in the sources reviewed, and I could not confirm any settlement consideration. Claim 40 (asserted in the complaint) was not among the claims tested in the Google IPR (claims 1 and 23) or expressly listed in the Netflix petition excerpt I reviewed, so claim 40's validity remains untested at the PTAB. Attorney appearances (Realtime: Eric Fenster, Marc Fenster, Reza Mirzaie, Brian Ledahl, Philip Wang, Jay Chung; Intel: Kourtney Merrill, Thomas Millikan, David Burman, Ryan McBrayer) are from the docket; I did not independently confirm their firms.

I'll research this case systematically, starting with the docket and any opinions.

Now let me get the actual docket and track the case's disposition.

The D. Colo. case was short-lived. Let me confirm the docket details and then dig into the parallel PTAB proceedings on the '046 patent.

Case Snapshot

Realtime Adaptive Streaming LLC v. Intel Corporation, No. 1:18-cv-01175 (D. Colo.), filed 2018-05-15 before Magistrate Judge Kristen L. Mix (later reassigned to Judge R. Brooke Jackson, No. 1:18-cv-01175-RBJ). Final disposition: dismissed with prejudice on 2018-10-01, roughly 4½ months after filing, pursuant to a settlement. The case never reached claim construction, discovery, dispositive motions, or trial, and there was no appeal. (Unified Patents docket; Justia docket)

Scope note / metadata discrepancy. The case metadata lists only the '046 patent. The complaint actually asserted three patents — U.S. Patent Nos. 7,386,046 (Ex. A), 8,934,535 (Ex. B), and 9,769,477 (Ex. C) — all from the Fallon "bandwidth sensitive data compression" family. Intel's answer confirms three patents were pleaded. My chronology below tracks all three, with emphasis on the '046.

---

1. Filing and Initial Pleadings

2018-05-15 — Complaint filed (Dkt. 1), jury demand.

• Accused instrumentalities: Intel processors implementing Intel QuickSync Video, including the Core i9-8950HK, i7-8850H, i7-8750H, i5-8500B, and i3-8300T.
• Infringement theory: Intel's H.264 codecs (including Annex G Scalable Video Coding) select among compression routines (e.g., CAVLC vs. CABAC entropy coders / different H.264 profiles) based on bitrate or resolution, allegedly meeting the "controller for tracking throughput … selecting a compression routine" limitations.
• Against Intel, Realtime asserted claim 40 of the '046 patent (a system claim reciting a controller that tracks "a number of pending access requests to a storage device" and switches to a faster compression routine when throughput falls below a threshold). (Complaint text; complaint analysis)
• A structural vulnerability was apparent on the face of the pleading: claim 40 requires tracking pending storage-device access requests, while the complaint mapped that limitation to channel bandwidth / SVC bitrate adaptation — a mismatch that likely would have driven claim construction. Id.

2018-05-21 — Intel served. (Summons returned executed; original answer deadline 2018-06-11.)

2018-06-04 — Deadline extended to 2018-07-11 (Minute Order granting Intel's unopposed extension motion, Dkt. 10).

2018-07-03 — Intel's Answer and Counterclaims (Dkt. 21).

• Denied infringement and denied that any of the three patents was "duly and properly issued," alleging invalidity under 35 U.S.C. §§ 101, 102, 103, and 112 as to each.
• Asserted declaratory-judgment counterclaims of non-infringement and invalidity, with a jury demand.
• Admitted venue was proper under § 1400(b) but expressly reserved the right to move to transfer under § 1404 — a live threat that never ripened. (Dkt. 21 text)

2018-07-20 — Realtime's Reply to Counterclaims (Dkt. 22).

2018-08-30 to 2018-09-04 — Jurisdictional shuffle. Realtime filed a consent/non-consent form indicating the parties did not consent to magistrate-judge jurisdiction. Magistrate Judge Mix ordered reassignment under D.C.COLO.LCivR 40.1 (2018-08-30); Judge Wiley Y. Daniel issued a Memorandum Returning Case (Dkt. 31); and the case was randomly reassigned to Judge R. Brooke Jackson (text entry, 2018-09-04), becoming No. 18-cv-01175-RBJ.

---

2. Pre-Trial Motions of Substance

None. No motion to dismiss, no § 1404 transfer motion (despite Intel's reservation), no motion to stay pending IPR, and no summary-judgment motion was ever filed. The case was resolved before the first scheduling conference.

---

3. Claim Construction (Markman)

No Markman proceeding occurred. No scheduling order was entered and no claim-construction briefing or hearing took place. (For context on what would have been contested, the parties' dispute would almost certainly have centered on "throughput"/"pending access requests" and whether bandwidth-based profile selection reads on a storage-access-request limitation.)

---

4. Discovery Milestones

**None of record

I'll search for press coverage of this case from multiple angles.

Mostly primary sources so far. Let me search specifically for press coverage.

Let me try trade press and legal-industry outlets specifically.

Press & Media Coverage

*Bottom line: I found no news coverage of Realtime Adaptive Streaming LLC v. Intel Corp., No. 1:18-cv-01175 (D. Colo.).* Across searches on the caption, the case number, the plaintiff/defendant pairing, the '046 patent number, the accused QuickSync Video technology, and Realtime's broader 2018 Colorado filing spree, the results were entirely docket mirrors, court filings, and databases — not journalism. Specifically, no article from Reuters, Bloomberg Law, Law360, Ars Technica, The Verge, IPWatchdog, Patently-O, JD Supra, IAM, or any mainstream or trade outlet discussing this case was located. Nothing reported a damages demand, a settlement figure, or any industry reaction, which is consistent with the record: the case was dismissed with prejudice roughly 4½ months after filing, before a scheduling order, and no consideration was disclosed. The closest items surfaced were non-journalistic: the Unified Patents litigation portal and Justia dockets (docket mirrors), Docket Alarm (a court-records search engine whose '046 query lists this case among the Fallon-patent suits), RPX Insight (a document repository hosting the complaint), and an automated complaint-analysis page at Ex Parte — the last of which is algorithmic rather than reported, and reads the claim-40 "pending access requests to a storage device" limitation against the complaint's channel-bandwidth theory exactly as our own claim-construction note did.

The only quasi-editorial litigation write-up I encountered concerns a different Realtime case: PatSnap's litigation blog has a case-record page on Realtime Adaptive Streaming v. Sling TV (Fed. Cir. No. 21-2268), listing 14 asserted patents and their validity-challenge histories. It does not mention the Intel action and contains no narrative analysis, so it cannot be used to characterize this case. The same database pages do, however, corroborate case metadata that is useful for cross-checking: Docket Alarm's '046 and '535 searches list this case's three patents as 7,386,046; 8,934,535; 9,769,477 under Judge R. Brooke Jackson, confirming the three-patent scope noted in the prior sections and again putting the single-patent case metadata in tension with the record.

Flag — apparent tension with the earlier "the '046 survived / remained intact" framing. No press account exists to complicate that statement, but the judicial record does. In the parallel Delaware campaign, the District of Delaware issued Report and Recommendation opinions analyzing the Fallon patents under Alice step two, and the opinion in No. 17-1692 (Realtime v. Netflix) recommends finding that "the '046 patent fails under step two of Alice," reasoning that "tracking is abstract and can be performed manually" and that the specification's statement that the invention may be implemented in "various forms of hardware, software, firmware, special purpose processors, or a combination thereof" signaled well-known, conventional technology; a companion opinion in No. 17-1520 reaches the same recommendation as to the '046. Those analyses addressed claim 1, not asserted claim 40. And Sony's § 101 motion in No. 17-1693 confirms the '046 (Count I) was under simultaneous § 101 attack in Delaware, this District, C.D. Cal., and E.D. Tex. So the accurate statement is narrower than "intact": the '046 survived the PTAB (the Google IPR2019-01033 and Netflix IPR2019-00209 outcomes) while being recommended for § 101 invalidity in Delaware on claim 1 — an asymmetry worth preserving rather than flattening.

Sourcing caveat. My search was bounded — I exhausted the available search budget after four query batches (caption; case number; plaintiff/defendant plus QuickSync/SVC terms; and trade-press/NPE-tracker angles). Law360, Bloomberg Law, and IAM content is largely paywalled and often not surfaced by open web search, so a docket-blurb item in one of those outlets cannot be ruled out; but on the open record reviewed, the press silence is itself the finding, and it is unsurprising for a four-month, quietly settled NPE suit against a single chipmaker that never produced a motion, a ruling, or a disclosed payment.

Sources

• Complaint for Patent Infringement, filed in Realtime Adaptive Streaming LLC v
• Realtime Adaptive Streaming LLC v
• Search court records on patent:(7386046)
• IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLORADO
• IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLORADO
• separate litigations against other defendants across the country: Realtime Adaptive Streaming LLC v
• Case 1:17-cv-02869-MSK-STV Document 32 Filed 03/05/18 USDC Colorado Page 1 of 23
• patentability
• 1:18-cv-01175 - Realtime Adaptive Streaming LLC v. Intel Corp - Text
• Search court records on patent:(9769477)
• 1:18-cv-01175 | Realtime Adaptive Streaming LLC v. Intel Corp | Ex Parte
• Systems and methods for data compression - Defendant Egnyte, Inc

I'll research the plaintiff's counsel of record from the docket and firm sources.

Let me pull the docket's counsel listing and the complaint's signature block.

Let me confirm the complaint's signature block and whether Ledahl/Chung formally appeared.

Plaintiff's Counsel of Record — Realtime Adaptive Streaming LLC

Bottom line. Realtime was represented by a two-firm team: Russ August & Kabat (Los Angeles) as lead patent counsel, and Denver solo practitioner Eric B. Fenster as Colorado local counsel — the same structure Realtime used across its 2017–2018 Colorado campaign (Apple, AMD, Charter, Sling TV). [5 attorneys] appear in the record; PACER itself is paywalled, so the roster below is reconstructed from the Justia and Unified Patents docket mirrors, the Docket Alarm document images, and PTAB filings in the parallel IPRs.

Table of counsel

Notes and caveats

• No in-house counsel appeared. Realtime Adaptive Streaming is a licensing vehicle with no litigation staff of record; all appearances were outside counsel.
• Who did the work vs. who signed on. The docket shows a deliberate division: Fenster (Denver) opened the case and handled local-court mechanics (complaint, AO 120, case-association notice, corporate disclosure); RAK then entered appearances within three weeks for the substantive patent work, and Chung signed the papers that closed the case. No Colorado counsel other than Eric Fenster appeared for plaintiff.
• Unconfirmed / excluded names. Paul A. Kroeger (RAK) appears in Realtime signature blocks in contemporaneous sister cases and the Netflix appeal, but I found no filing or appearance by him in this docket and have not listed him as counsel of record. Kyle Paul Seedorf appears on Realtime's counsel list in v. Charter (D. Colo. 1:18-cv-01345) but not here. No attorney should be attributed to this case on the basis of sister-case appearances alone.
• Identity caveat on local counsel. Public business-directory profiles for "Eric B. Fenster LLC" (Denver) describe a criminal-defense/personal-injury practice, which is unusual for patent local counsel; I cannot verify from those profiles whether the directory listing refers to the same practitioner, so I rest the identification solely on the court filings themselves (CO Atty Reg. #33264; eric@fensterlaw.net; address of record). I also did not confirm any family or firm relationship between Eric B. Fenster and Marc A. Fenster, and the record does not suggest one — the two operated as separate firms.
• Cross-reference to earlier sections. The case-overview section listed these same six names but flagged that firms were unverified; this section supplies the firm, bar-number, address, appearance-date, and role detail. Note one internal inconsistency between the two prior sections (the overview says the complaint also pleaded the '462 and '535; the "Key legal developments" section says '535 and '477) — that discrepancy is in the patent roster, not counsel, but affects how the pleadings should be cited.

Sources: Justia docket, No. 1:18-cv-01175 (counsel list: Eric Bryan Fenster, Marc Aaron Fenster, Brian David Ledahl, Reza Mirzaie, Philip X. Wang); Unified Patents docket mirror (entry-of-appearance and filing text for Fenster, Wang, Marc Fenster, Mirzaie, Chung); Docket Alarm images of Dkt. 21 (Intel's Answer) and of Realtime's Colorado filings in 1:17-cv-02869 (Fenster/RAK signature blocks); USPTO PTACTS power of attorney and petition papers in the Realtime IPRs (Wang as lead, Chung/Mirzaie/Shum/Rubin backup; RAK address); Federal Circuit No. 21-2268 order of 5/11/2023 and Realtime's Netflix principal brief (counsel roster).

I'll research Intel's counsel of record in this case, using the docket and firm sources.

Docket entries identified. Now let me verify firms and roles for each Intel attorney.

Now let me confirm firm affiliations and check for any additional appearances (including pro hac vice filings and local counsel).

Defendant's Counsel of Record — Intel Corporation

All four of Intel's appearances came from a single firm: Perkins Coie LLP. Intel used Perkins Coie's Denver office for the Colorado-licensed filing attorney and its Seattle/San Diego IP litigation partners for substantive work. Intel filed no pro hac vice motions and had no in-house counsel enter an appearance on the mirrored docket.

Correction / upgrade to prior sections. The "Case overview" section listed these four Intel attorneys from docket text while noting "I did not independently confirm their firms." That open item is now closed: all four were Perkins Coie in 2018. No other Intel appearance appears on the docket.

Table of appearances

Role analysis and caveats

• No formal "lead counsel" designation exists. D. Colo. practice does not require a lead-counsel designation on the docket, and the CM/ECF text contains none. The role assignments above are inferential: Merrill is the Colorado-admitted attorney who signed the answer and counterclaims and the scheduling-order submission; Millikan and Burman are the out-of-state IP partners whose notices of appearance were filed the same day (6/26/2018), i.e., the pattern of a national IP team associating Colorado local counsel.
• No pro hac vice motions appear. Because D.C.COLO.LAttyR 2 requires local counsel for PHV admission, and no PHV motion appears in the mirrored docket, the out-of-state attorneys (Millikan, Burman, McBrayer) either were already admitted to the D. Colo. bar or their admissions were handled without a docketed motion. I could not verify individual bar admissions from a primary source; treat this as an open item. The docket mirrors I relied on are Unified Patents and Justia.
• No in-house Intel attorney appeared. Intel Corporation's legal department did not enter an appearance; Intel's only appearances were outside counsel.
• Do not confuse with Intel's PTAB counsel. In parallel USPTO proceedings involving the Realtime/Fallon patents and expressly cross-referencing this D. Colo. case, Intel was represented by Paul Hastings LLP — lead counsel Naveen Modi (Reg. No. 46,224), backup Joseph E. Palys (Reg. No. 46,508), Phillip W. Citroën (Reg. No. 66,541), and Howard Herr (PHV to be requested), at Paul Hastings' Washington, D.C. office, 875 15th St. NW (PTAB petition papers). None of the Paul Hastings attorneys appeared in the district court case. Likewise, Baker Botts LLP (Harper Batts, Eliot Williams, Chris Ponder, Jennifer Nall) appears in IPR2018-01187 on the '477 patent as counsel for a different petitioner that cited the Intel case as a related matter — not as Intel's counsel (mandatory notices).
• Not verified in this pass: Ryan J. McBrayer's exact 2018 office and current firm (my verification search was cut off); his inclusion in the 2020 Intel PHV motion in Delaware supports the Perkins Coie/Intel relationship but I did not confirm his present affiliation. I also did not retrieve the actual signature blocks of Dkt. 21 to see which attorneys signed the counterclaims.