Plain-English Summary
This page shows, in very simple steps, how live video messages work and which parts match patent claim elements. Each row has short words, easy icons, and blue links to public sources. Think of it like matching shapes: if the shapes line up, the bar fills up.
Live + Replay Model
Live voice/video now + watch again later
Server-Routed Streams
Messages hop across servers (not pure P2P)
User Selection
Tap a chat ➜ choose which stream to view
Context: Public sources describe Voxer’s live push-to-talk, video messages, storage on servers, and time-shifted playback. Recent reporting notes suits against Amazon/Twitch concerning networked video streaming systems. Links below go to those sources.
What the Patents Say (Selected Elements)
- US 10,205,986 Mobile device captures/broadcasts live video; user selects streams; controls; server transmission; recording & replay.
- US 10,958,961 Devices send live video to a network; server manages many streams; user selects; present on display; messaging integration.
What the Product Does (According to Docs)
- Live push-to-talk with voice + video; text, photo, location.
- Messages are delivered live and then stored for replay.
- Messages are kept on user devices and Voxer servers.
- Users pick chats/threads to view or replay.
Claim Chart – US 10,205,986 (Systems & Methods for Selecting and Presenting Live Video Streams)
| Claim element | Accused feature | Why it matches | Evidence |
|---|---|---|---|
| [1a] Mobile device captures & broadcasts live video | Voxer: live PTT + video messages | Mobile capture ➜ send live ➜ store |
Voxer overview Google Play features Video sharing (iOS) |
| [1b] Select one or more streams to show | Open a chat/thread; play now or later | User chooses which stream to view | Voxer overview |
| [1c] Controls: start, view, switch | PTT button; play/pause; thread nav | Meets control requirement |
Capture Mode Google Play features |
| [1d] Transmit via server infrastructure | Server-routed messages (not pure P2P) | Store-and-forward across server hops |
Voxer patent 8,782,274 UK case summary Data retention policy |
| [1e] Recording & replay | Messages stored; replay anytime | Time-shifted playback |
Google Play (recorded) Voxer overview Data retention |
Claim Chart – US 10,958,961 (Selecting & Presenting Video Streams from Multiple Sources)
| Claim element | Accused feature | Why it matches | Evidence |
|---|---|---|---|
| [2a] Devices send live video to a network | Clients encode & send voice/video | Network transmission of media |
Google Play (video) Video sharing |
| [2b] Server manages simultaneous streams | Back-end coordinates sessions/hops | Parallel handling via servers |
Voxer patent 8,782,274 UK case summary |
| [2c] Selection by user/context | Open conversation; choose stream | User-driven selection | Voxer overview |
| [2d] Present selected video to display | Playback on phone screen | Display presentation | Video sharing |
| [2e] Messaging integration | Contacts, notifications, chat history | Messaging context retained |
Voxer overview Google Play features |
Simple Picture: Do the Shapes Match?
Capture & Send Live Video
Docs show live + video messages
User Picks Which Video
Tap a chat ➜ view/replay
Server Hops (Not Pure P2P)
Stored and forwarded on servers
Record & Replay Later
Time-shifted playback
Evidence Library (Public Links)
- Voxer: What is Voxer?
- Voxer on Google Play (features, storage, live PTT, video)
- Voxer Support: Video Sharing (iOS)
- Voxer Support: Capture Mode
- Voxer: Data Retention Policy (messages stored on devices and Voxer servers)
- Voxer Patent 8,782,274 (progressive send; stored at each hop)
- Wiggin LLP analysis (live vs time-shifted; stored across servers)
- RPX Insight (2025 filings re: Amazon/Twitch streaming systems)
This page summarizes publicly available descriptions. For formal proceedings, counsel can add exhibits (screen recordings, packet traces, timestamps, API names) to each row.