🌐 Translate
Select your preferred language from the menu below:
Patent Claim Chart Overview
This hub presents structured claim-chart mappings for US 10,205,986 B2 and US 10,958,961 B2, evaluating how specific patent claims may align with observable workflows across X (formerly Twitter), Tesla, and SpaceX.
The purpose is to facilitate pre-suit licensing discussion. Each section below maps claim elements to product features, with supporting evidence links.
US 10,205,986 B2
US 10,958,961 B2
Target Companies
X (formerly Twitter)
✅ This section maps high-level patent workflow elements to X live video features: capture → network transmission → user selection → routing → real-time interaction.
| Patent Claim Element (Summary) | Observed Product Feature / Workflow | Evidence |
|---|---|---|
| ✅ Capture live video using a device camera | Mobile live broadcasting workflows (capture from phone camera) | X Help |
| ✅ Transmit live video over network | Internet transmission into platform ingest and distribution pipeline | X Dev |
| ✅ User selection of live content | User selects live stream from feed/search or embedded card | X Help |
| ✅ Routing/distribution to multiple viewers | Platform routes stream to many concurrent viewers | X Dev |
| ✅ Real-time interaction during streaming | Live comments / reactions / reposts / engagement layer | X Help |
Tesla
✅ Tesla integrates video workflows through vehicle cameras, the in-car display ("dash screen"), and the Tesla mobile app. These workflows support remote viewing, selectable camera perspectives, and transmission to a phone—functionally the same pipeline used for mobile live streaming: capture → transmit → select → route → display → interact/control.
| Patent Claim Element (Summary) | Observed Product Feature / Workflow | Evidence |
|---|---|---|
| ✅ Capture video from camera source | Vehicle camera system (multi-camera capture) and display | Manuals |
| ✅ Transmit video over a network | Connectivity pipeline: vehicle ↔ internet ↔ phone app | Connectivity |
| ✅ User selection of content/view | User selects which camera view/session appears (dash screen or app) | App |
| ✅ Routing to display devices | Routing to: vehicle display, mobile phone display, and other endpoints | Support |
| ✅ Interactive controls tied to stream | App-based controls and interactions that affect what is shown/when | App |
✅ Tesla workflows can present video "tiles/cards" (selectable views) where a user chooses a feed and the system routes that feed to the selected display.
✅ Subscription or paid connectivity features can gate bandwidth-heavy video workflows, tying video routing to paid access.
✅ A Tesla screen ("dash display") is effectively a dedicated client device. A phone can act as another client device. A second phone can display the live feed, or relay it onward, expanding distribution capacity.
✅ This model mirrors mass streaming platforms: one source feed → network transmission → user selection → routing to many viewers (Facebook/YouTube), or to a proprietary platform (X/Twitter).
✅ In short: Tesla's camera video is captured, transmitted, selected, and routed to endpoint devices—matching the claimed architecture.
SpaceX
✅ SpaceX distributes live video feeds (missions/operations) through network pipelines. These pipelines include capture, transmission, selectable viewing, and large-scale distribution to end-user devices.
| Patent Claim Element (Summary) | Observed Product Feature / Workflow | Evidence |
|---|---|---|
| ✅ Capture live video | Mission/operations cameras capture live video feeds | SpaceX |
| ✅ Transmit over network | Transmission across internet/satellite links | Starlink |
| ✅ User selection of stream/session | Users select which feed/session to watch (public distribution workflows) | YouTube |
| ✅ Routing to large audiences | Distribution at scale to large concurrent viewership | YouTube |
Licensing Discussion Contact
✅ For licensing discussion prior to litigation, contact the support channel below.