VideoLabs, Inc. v. Amazon.com, Inc.

I'll research this case thoroughly before drafting.

Important finding: this docket has a notable procedural history. Let me verify details.

Now let me pin down the '156 patent specifics, post-dismissal developments, and IPR activity.

Case Overview

Correction to the existing summary up front: the linkage flagged as "unverified" is now verified, and the case is not open. Civil Action No. 6:22-cv-01167-ADA is the same lawsuit as VideoLabs, Inc. v. [Amazon.com, Inc.](/litigations/by-plaintiff/Amazon.com%2C%20Inc.), No. 6:22-cv-00079-ADA (W.D. Tex., filed Jan. 21, 2022) — it is the re-docketed file after a venue round-trip, not a separate or narrowed complaint. It terminated by joint stipulation of dismissal with prejudice on Dec. 22, 2022 (Dkt. 115), after the parties filed a notice of settlement in principle and joint motion to stay on Dec. 14, 2022 (Dkt. 113), which Judge Albright granted Dec. 15, 2022 (Dkt. 114); the closing order and PTO report followed Dec. 27, 2022 (Dkts. 116–117). Patexia docket; UniCourt docket. Note also that the metadata's "patents at issue: 6880156" is a subset: the complaint asserted seven patents, and the '156 was one count among them.

Parties. VideoLabs, Inc. and its wholly owned subsidiary VL Collective IP LLC (both Delaware corporations, Palo Alto, CA) are a patent aggregation-and-licensing platform, not an operating company. VideoLabs launched publicly in late 2019 as an industry-funded "collective" — $10M in debt financing, founding members Hewlett Packard Enterprise, the Kudelski Group, Siemens Healthineers and Swisscom — built to buy high-risk video-technology patents and license them on a membership basis (Lexology/IAM, Nov. 2019). When the membership model failed to scale ("we simply didn't get enough support from the industry"), it pivoted to litigation, starting with Dell in May 2021 (Mondaq, Mar. 17, 2022). It is therefore properly characterized as a PAE/NPE — Stanford's NPE Litigation Database classifies both entities as patent asserters relying on acquired patents (Stanford NPE DB). Amazon.com, Inc. and Amazon Web Services, Inc. are the operating-company defendants. VideoLabs' campaign counsel included Courtland Reichman, Christine Lehman and Taylor Mauze; Amazon's team included J. David Hadden, Saina Shamilov, Ravi Ranganath and Johnson Kuncheria (firm affiliations not confirmed in the sources reviewed).

The accused technology and the '156 patent. The complaint grouped Amazon products by technology, and the '156 count targeted the cloud, not video: AWS Auto Scaling and Amazon EC2 Auto Scaling, accused of practicing claim 10 of U.S. Patent No. 6,880,156. Claim 10 recites a method of adapting the number of server applications within a server by "measuring a load on the server," "detecting when the load exceeds an activation threshold," and using a "system allocator" to activate an additional server application, where the threshold is based on "a ratio of a current number of connections per unit time to a past number of connections per unit time" (Compl. ¶¶325–332). VideoLabs mapped that to Auto Scaling Groups, predictive/dynamic scaling, launch templates and CloudWatch connection metrics. The patent — titled "Demand responsive method and apparatus to automatically activate spare servers" — issued in 2005 to HP inventors Steven R. Landherr and Thomas E. Turicchi, Jr., passed to Hewlett Packard Enterprise, and was assigned to VideoLabs on Sept. 5, 2019 (assignment chain, patentcut.com). The other six counts were video-centric: the Panasonic-origin H.264 entropy-coding family (7,769,238; 8,139,878; 7,970,059 — accused against Prime Video, Fire TV, Echo Show, MediaConvert/MediaLive); 8,605,794 (HLS segment ordering); 7,266,682 (WebRTC/SRTP — Echo Show, Chime, Connect); and 7,440,559 (content-flow control based on client status — Prime Video bookmarking and auto-download). Full seven-patent list at Compl. ¶11.

Posture and why it matters. Filed in Waco before Judge Alan D. Albright, with a scheduling order (Dkt. 36) setting Markman for Oct. 13, 2022 and jury trial for Oct. 26, 2023. Amazon moved to transfer to W.D. Wash. under §1404(a) (Dkt. 39); Albright granted it in a sealed opinion on Oct. 11, 2022 (Dkt. 91), and the case opened before Judge James L. Robart as No. 2:22-cv-01451. In an unusual move, Judge Robart then transferred it back to Texas on Oct. 28, 2022 (Dkt. 110) at Judge Albright's request so Albright could decide the still-pending motions — including VideoLabs' Rule 37 sanctions motion over venue discovery (Dkt. 50) — and the case reopened as 6:22-cv-01167-ADA on Nov. 14, 2022. The local narrative also featured a technical-advisor appointment (Dkt. 83) and a magistrate referral to Judge Derek T. Gilliland. The case's significance is threefold. First, it is the clearest example of a video patent aggregator reaching into cloud infrastructure: a 2000-era HP server-provisioning patent asserted against AWS Auto Scaling, a core AWS revenue driver, framed in the complaint around live-sports streaming spikes. Second, it illustrates the VideoLabs campaign pattern — parallel suits against Dell, Netflix (D. Del.), Meta, Roku, TCL, Hisense and Starz, plus ITC Inv. No. 337-TA-1323 — with Amazon among the early exits, settling within roughly eleven months of filing. Third, the funding structure is visible in the record: VL Collective IP granted a security interest in its patents to Praetor Fund I (a sub-fund of Praetorium Fund I ICAV) in Dec. 2019, released Dec. 28, 2022, days after the Amazon dismissal (USPTO assignment data), consistent with litigation-finance-backed enforcement. Unverified: the terms of the Amazon settlement (no license or payment details are public), whether any IPR petition was filed against the '156 patent specifically (the well-documented PTAB activity — e.g., Unified Patents' IPR2023-00891 against the '794 patent — concerns other patents in the family), and whether Amazon became a VideoLabs licensee.

I'll research this case systematically, starting with the docket and party/patent basics.

Key finding: this docket appears to be a re-docketed transfer case. Let me pull the transfer orders, dismissal, and PTAB activity.

Now let me nail down the '156 patent specifically, Amazon's IPR activity, and the full docket.

Bottom line

6:22-cv-01167 is not a separate lawsuit. It is the W.D. Tex. re-docket of the original VideoLabs v. Amazon case, No. 6:22-cv-00079-ADA, after an unusual round-trip transfer to the Western District of Washington and back. The linkage the earlier summary flagged as "unverified" is now verified: Judge Robart's transfer-back order and the clerk's docket entry ("TRANSFERRED CASE opened in Western District of Texas as case 6:22-cv-01167 on 11/14/2022," Dkt. 112) confirm it, and PTAB papers uniformly caption the two numbers together as one action ("Nos. 22-00079-ADA, 22-01167-ADA (W.D. Tex.)").

Outcome: dismissed with prejudice by joint stipulation on 2022-12-22 (Dkt. 115), roughly five weeks after re-docketing. There was no Markman ruling, no summary judgment, no trial, and no verdict.

Also note a metadata caveat: the '156 patent (6,880,156) is not the only patent in this case. The complaint asserted seven patents — 6,880,156; 7,266,682; 7,440,559; 7,769,238; 7,970,059; 8,139,878; and 8,605,794 — grouped by technology (H.264/entropy coding; HLS; WebRTC/SRTP; AWS Auto Scaling; content-flow control).1 The single-patent listing in the case metadata is a docket-database artifact (the same truncation recurs in reverse in the 6:22-cv-01167 docket, whose "cause of action" field names only the '238 patent).

---

Chronology

1. Filing and initial pleadings

Substance of the '156 count (the patent in this case's metadata): VideoLabs accused AWS Auto Scaling and EC2 Auto Scaling of infringement, specifically predictive/target-tracking scaling in which an activation threshold is computed from "a ratio of a current number of connections per unit time to a past number of connections per unit time," with CloudWatch metrics and launch templates supplying the claimed allocator/server-application-resource structure. VideoLabs pleaded a notice narrative running from a 2020-03-12 licensing meeting, through delivery of a patent list "at least by 2021-08-05," to Amazon's 2021-08-31 statement that it had done an initial review and would re-engage — which VideoLabs says never happened. That paragraph is the hook for the willfulness and inducement theories.

Unsourced / not verified: I could not retrieve the answer and counterclaims (date, declaratory-judgment counts, invalidity theories). An answer and likely DJ counterclaims would have been filed in spring 2022 (Amazon's first substantive filing I can confirm is the transfer motion, Dkt. 39, in June 2022). Treat the answer's contents as an open item — see verification list below.

2. Pre-trial motions of substance

Motion to transfer venue (the dispositive procedural fight). Amazon filed an Opposed Motion to Transfer Venue under 28 U.S.C. § 1404(a) on 2022-06-08 (Dkt. 39). This triggered full-blown venue discovery against the Waco Division's local-activity theory:

• 2022-06-20 — VideoLabs serves 30(b)(6) notice on Amazon; 2022-08-14 — notice to depose Juan Lopez, manager of the Waco fulfillment center.
• 2022-08-17 — venue discovery closes.
• 2022-08-23/24 — Amazon seeks a protective order on four 30(b)(6) topics; Magistrate Judge Derek T. Gilliland holds a Zoom discovery hearing on 2022-08-24.
• 2022-09-01 — Dkt. 62, Order Regarding Venue Discovery Dispute: Amazon's protective order granted as to topics 1, 4, 11, 12, 13 (historical development testimony), topic 3 (Waco-specific sales/revenue/profits) and topic 10 (document-retention policies); denied as to the Lopez deposition, and Amazon was ordered to produce him for 90 minutes. The order expressly reserved VideoLabs's sanctions motion.2

VideoLabs's Rule 37 sanctions motion (Dkt. 50) — an opposed, sealed motion for sanctions against Amazon over discovery conduct, briefed in parallel with venue discovery: opposition and the Ravi Ranganath declaration filed 2022-09-06 (Dkt. 65), reply with 12 exhibits filed 2022-09-20 (Dkt. 73), and VideoLabs moved to expedite briefing on it (Dkt. 51, 2022-08-22). Outcome not verified — I could not locate an order granting or denying Dkt. 50; it was very likely mooted by the transfer and dismissal, but I cannot state that as fact.

Transfer granted — then reversed on a jurisdictional technicality.

• 2022-10-11 — Judge Albright grants the § 1404(a) motion by sealed Memorandum Opinion and Order (Dkt. 91).3 (Sealed; whether a redacted version ever issued is unverified.)
• 2022-10-13 — transfer perfected; case docketed as W.D. Wash. No. 2:22-cv-01451-JLR before Judge James L. Robart.
• 2022-10-13 — VideoLabs files, back in W.D. Tex., a motion to stay the transfer and a motion for clarification/reconsideration (Dkt. 94).
• 2022-10-28 — Judge Robart, VideoLabs, Inc. v. Amazon.com, Inc., No. C22-1451JLR (W.D. Wash.), orders the case transferred back to W.D. Tex. because the W.D. Tex. motions were filed after jurisdiction had already passed to Washington (citing NBS Imaging Sys. and In re Red Barn Motors), and "Judge Albright has requested that the case be transferred back to the Western District of Texas so that he may consider the pending motions."4
• 2022-11-14 — case re-docketed in W.D. Tex. as 6:22-cv-01167 (Dkt. 112).

No motion to dismiss, no stay pending IPR, and no summary-judgment motion appears on the docket. Notably, Amazon did not seek a § 101 dismissal or an IPR-based stay in this case.

3. Claim construction

The case got materially into Markman briefing but never reached a construction ruling or a Markman hearing on the public record:

• Scheduling Order at D.I. 36 (cited in the Joint Claim Construction Statement and later as an IPR exhibit).
• Joint Claim Construction Statement — disputed terms across the '238, '878, '059, '794 and '682 patents; agreed constructions included "output/outputting" ("transmitted, stored together, or passed on to a processing unit"), limiting preambles for the '794 patent, the "assignment rule" terms (requiring assignment without exact timing/timestamp information), and "application layer" ("layers above the transport layer (layers above 4)").5
• Amazon's Opening Claim Construction Brief (ECF 48) and VideoLabs's Responsive Claim Construction Brief. The central fight was validity-flavored: Amazon argued that "an audio processing unit configured to…" ('238 cl. 1) and "an audio coding unit configured to code an audio signal" ('059) were **§ 112(f) means-plus-function terms with no corresponding structure — hence

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

Initial searches surfaced docket/pleading material but little press. Let me search more targeted angles.

Good — I've confirmed the docket arc. Now let me hunt specifically for press/analysis coverage.

Press and analysis coverage

My searches were truncated before I could exhaust every outlet listed, so treat the "no coverage" findings below as provisional rather than exhaustive.

The only contemporaneous write-up of the filing itself that I located is a trade/law-firm piece on Mondaq dated 2022‑03‑17, headlined "Patent Collective Turned Plaintiff VideoLabs Expands Campaign, Sues Amazon." It reported that VideoLabs, Inc. and subsidiary VL Collective IP, LLC sued Amazon in the Western District of Texas (6:22‑cv‑00079) asserting seven patents over "streaming systems and services, smart home devices, software, tablets, and TVs," and framed the theories functionally: "support of the H.264 and HLS streaming protocols, auto scaling, WebRTC and SRTP standards, and content flow control." That "auto scaling" theory is the AWS Auto Scaling/'156 Patent theory your case metadata isolates. The piece is useful mainly for business context: it recounts, quoting reporting by IAM and VideoLabs SVP Ira Blumberg, that VideoLabs was built as a membership model ("companies would pay an annual fee and would be licensed to VideoLabs' growing portfolio which now stretches to more than 100 assets") and that Blumberg told IAM the model failed to attract industry support — "not the least of which was covid, we simply didn't get enough support from the industry for the membership model." That is an executive statement, not a court record fact.

On the resolution, I found no press account of settlement terms, and no reported dollar figure anywhere. What exists is a company announcement — VideoLabs posted a December 2022 item titled "Amazon licenses VideoLabs' patent portfolio, ends litigation," and its licensee page lists Amazon among "more than 30 companies" licensed. The docket corroborates the sequence but not the economics: a joint motion to stay and notice of settlement in principle (Dkt. 113, 2022‑12‑14), the stay order (Dkt. 114, 2022‑12‑15), a joint stipulation of dismissal with prejudice (Dkt. 115, 2022‑12‑22), and a further order (Dkt. 116, 2022‑12‑27), per the Justia docket. Separately, VideoLabs' 2022‑12‑27 demand letter to Hisense — filed as an exhibit in a later PTAB proceeding and available via Docket Alarm — states that "[m]ost recently, Amazon entered into a portfolio license agreement with VideoLabs," which is the closest thing to a public confirmation of a portfolio-wide license rather than a single-patent settlement.

The only sustained third-party analysis came from the defensive aggregator Unified Patents, which on 2022‑12‑20 reported that the PTAB had instituted trial on all challenged claims of U.S. Patent 8,605,794 and noted the patent "has been asserted against Starz Entertainment and Amazon"; Unified later reported that on 2023‑12‑18 the Board found claims 1, 3, 5, 9, 12, 13 and 15 of the '794 patent unpatentable. That framing is advocacy-adjacent (Unified is the petitioner and situates VideoLabs in its "SEP Video Codec Zone"), so it goes beyond the court record. I also saw an IAM headline, dated 2025‑05‑07, describing HP's license as "the 20th licensee for VideoLabs"; I could only see the headline/snippet on IAM's Amazon organisation page, not the article body, so I cannot confirm it discusses this docket.

Where accounts differ: they largely don't, because almost nothing was written. The one real divergence is between the parties' framing and the docket — VideoLabs publicly characterized December 2022 as a portfolio license "ending litigation," while the court record shows only a settlement in principle and voluntary dismissal with prejudice, with no findings on validity, infringement, or damages. On the venue history, the docket resolves the open question flagged in the earlier case summary: the Western District of Washington case (2:22‑cv‑01451) was transferred back to W.D. Tex. at Judge Albright's request (Dkt. 110, 2022‑10‑28) and re-docketed as 6:22‑cv‑01167 on 2022‑11‑14 (Dkt. 112), so the two dockets are the same case. Beyond that, no mainstream or legal-trade coverage of this specific action surfaced in my searches, which is unsurprising for an NPE campaign docket that settled roughly five months after service and never reached a Markman ruling, trial, or verdict. If the case file needs an authoritative press record, the missing pieces are Law360/Bloomberg Law docket alerts and any IAM article on the Amazon license — I was unable to reach those before my search budget ran out.

Sources

• UNITED STATES DISTRICT COURT WESTERN DISTRICT OF TEXAS WACO DIVISION
• UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF TEXAS WACO DIVISION
• Complaint analysis | 2:22-cv-01451 | VideoLabs Inc v. Amazon.com Inc | Ex Parte
• UNITED STATES DISTRICT COURT WESTERN DISTRICT OF TEXAS WACO DIVISION
• UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF TEXAS WACO DIVISION
• VideoLabs, Inc. et al v. Amazon.Com, Inc. et al
• IN THE UNITED STATES DISTRICT COURT FOR THE WESTERN DISTRICT OF TEXAS WACO DIVISION
• Amended Complaint | 2:22-cv-01451 | VideoLabs Inc v. Amazon.com Inc | Ex Parte
• VideoLabs, Inc.
• petitions—IPR2024-01023, IPR2024-01024, and IPR2024-01025 challenging the ’236 patent, and
• The '794 patent describes improved techniques for synchronizing audio and video data segments when streaming content
• 316. Amazon also indirectly infringes the '682 Patent by inducing others to infringe and contributing to the infringement of oth...

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

Let me get the actual docket sheet for 6:22-cv-01167.

Good — I have the full docket. Now let me pin down each plaintiff attorney's firm and role.

I'll research the defendant's counsel of record through docket sources and firm records.

Counsel of Record — Defendants Amazon.com, Inc. and Amazon Web Services, Inc.

Posture caveat first: this action is closed (stipulated dismissal with prejudice, Dkt. 115, Dec. 22, 2022), so what follows is the final roster of counsel of record, not a live appearance list. The docket does not formally designate "lead" versus "of counsel" status; every Fenwick attorney below is listed simply as "Attorneys for Defendants AMAZON.COM, INC. and AMAZON WEB SERVICES, INC." Role characterizations are my inferences from signature-block order, seniority, and who actually signed substantive papers. Both Amazon entities were represented by the same team throughout — no separate AWS-only counsel appeared.

National/trial counsel — Fenwick & West LLP (Silicon Valley Center, 801 California Street, Mountain View, CA 94041; Tel. 650-988-8500)

Local / Texas counsel

W.D. Wash. phase (No. 2:22-cv-01451-JLR)

In-house counsel

No Amazon in-house attorney appears on the docket as counsel of record in either the Texas or Washington file, and I found no corporate disclosure or notice of appearance identifying one. Unverified: the identity of Amazon's internal legal/paralegal contacts; none is public in the records reviewed.

Sourcing and what I could not confirm

• Grounded in: the Jan. 31, 2022 and Mar. 29, 2022 Notices of Attorney Appearance (Dkts. 20, 22–26) as mirrored on Justia (6:22-cv-01167), Justia (6:22-cv-00079), Docket Alarm, and UniCourt; the Oct. 3, 2022 Joint Claim Construction Statement signature block in No. 6:22-cv-00079-ADA-DTG (hosted at PTAB/PTActs); and the Dkt. 65 Ranganath declaration and Dkt. 29 Rule 7 disclosure listed on Patexia.
• Bar numbers and addresses are taken verbatim from the signed filings, not from firm websites, so they reflect counsel's status as of late 2022. Firm affiliations for Hadden, Shamilov, Ranganath, Kuncheria, Long and Kaempf at Fenwick are confirmed by the filings themselves; note that some of these lawyers may have since changed firms or been promoted (Kaempf is now a partner), and I did not re-verify each individual's current status.
• No pro hac vice motion by any Fenwick attorney appears in the entries I reviewed — consistent with the "Admitted W.D. Tex." annotations, but I did not search the full docket for PHV orders, so I cannot rule out that one was filed and granted.
• Nothing sealed: the counsel roster itself is not under seal; it was the venue-transfer opinion (Dkt. 91) and the sanctions papers that were sealed, not the appearances.