Mux – Video API – Live Streaming Developer Infringement Report

Mux – Video API – Live Streaming Developer Infringement

This report explains how Mux – Video API fits into mobile live streaming workflows, server routing, and interactive viewing systems that map onto the core claims of US 10,205,986 and US 10,958,961.

Calculating countdown…

« Back to Developer Database View Top 20 Invoiced Companies PAY END-USER LICENSE – $100 (NO REFUNDS) EMAIL GABRIEL – NEGOTIATE DEVELOPER LICENSE

For 20+ years, developers and companies like Mux – Video API have built live streaming stacks that route mobile audio/video through servers to viewers. This page summarizes how those roles intersect with the patent claim language and how licensing can resolve that exposure.

Developer Claim Chart – Core Patent Mapping

Patent / Claim	Claim Element	Evidence of Use by Mux – Video API
US 10,205,986 Claim 1 (Mobile Capture & Uplink)	Software running on a mobile device that captures audio/video and transmits it to a remote server for live distribution.	The work of Mux – Video API may include: Camera / microphone capture on phones or tablets Encoding and pushing a live stream to a server endpoint Use of RTMP, HLS, WebRTC, or proprietary uplink protocols Search: Mux – Video API live streaming mobile implementation
US 10,205,986 Claim 1 (Routing / Destination Selection)	Server-side logic that selects which viewer, channel, or group receives the live stream, including audience routing, channel mapping, or distribution policies.	Possible roles for Mux – Video API: Writing routing logic that selects which viewers / channels receive each stream Handling subscriptions, followers, or room IDs for delivery Defining server-to-client delivery rules based on metadata Search: Mux – Video API live routing developer documentation
US 10,958,961 Interactive Sessions (Comments / Reactions)	Multiple concurrent viewers interact in real time with the live stream using comments, reactions, likes, or paid messages.	Mux – Video API may: Expose APIs or UI for live chat, emoji, reactions, or gifts Synchronize viewer input with the ongoing stream Persist or log these interactions for later analytics Search: Mux – Video API live chat / interaction SDK
US 10,205,986 Archiving / VOD	Saving the live session for replay after the broadcast has ended, using the same captured content delivered to viewers.	Implementation patterns that Mux – Video API may use: Automatic recording of live streams on the server Playback endpoints / URLs for finished broadcasts Storage policies linked to user or channel accounts Search: Mux – Video API live recording / replay case studies
US 10,205,986 / 10,958,961 System-Level Coordination	Claim sets describing system-level coordination between mobile endpoints, servers, selection logic, and viewer devices including QoS, scaling, and distribution logic.	For expanded claim coverage, additional mapping may be prepared for: Load-balancing live stream traffic across nodes Coordinating multiple viewer devices per broadcast Hybrid architectures (edge servers, CDNs, or cloud routing layers) Search: Mux – Video API streaming terms / architecture overview

NOTE: This chart is expandable. Additional claims can be mapped per developer or company, depending on scope, scale, and role in deployment. Nothing on this page is legal advice; it is a technical mapping to the patent claim language for negotiation purposes.

Developer Offer Formula – How to Make an Offer

Developers and companies can propose a license by emailing support@tvknowsyou.com. A simple starting point:

Estimate how many end users / channels use your live streaming stack.
Estimate historical and projected revenue tied to live streaming features.
Propose a per-user, per-stream, or lump-sum amount that reflects your usage and risk.

You can send funds directly via payment providers, or coordinate a structured developer license through email.