Media Fling Caching for Low-Latency TV Playback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current media flinging solutions, such as DLNA and AirPlay, suffer from latency, inconsistent quality, and complex setup processes, leading to poor user experiences when transferring content from mobile devices to TVs, with issues like buffering, freezing, and detection failures.

Innovation Solution

A media fling platform that caches content at a rendering device based on user history and current viewing behavior, allowing seamless transfer and prioritizing fling requests over caching, with automatic device selection and optimized network management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If media content is transmitted over network from mobile device to TV using DLNA or AirPlay, then content can be displayed on larger screen, but latency increases to 2-4 seconds and user experience deteriorates

Engineering Contradiction:
ImprovelatencyVSAvoiduser experience consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system pre-loads and caches media content on the TV device before the user actually requests to play it. When a user browses media on their mobile device, the system detects this browsing activity and proactively transfers and caches the media files to the TV's local storage in advance. This preliminary action eliminates the 2-4 second latency that normally occurs during actual playback, as the content is already available locally on the TV when needed.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If DLNA protocol is used for media transfer, then interoperability between devices is achieved, but device complexity increases due to multiple configuration steps and network setup requirements

Engineering Contradiction:
Improvedevice interoperabilityVSAvoidsetup complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system automatically detects when a mobile device is browsing media content and initiates the content transfer to the TV without requiring manual user configuration. The TV device autonomously monitors the network for media browsing activities, automatically requests and caches the relevant content, and manages the entire workflow without user intervention. This self-service approach eliminates the complex multi-step DLNA configuration process while maintaining broad device compatibility.

Inventive Principle:
Principle #25Self-service

3Loss of time

If media content is cached on rendering device before user selection, then playback latency is reduced, but network bandwidth is consumed during caching process

Engineering Contradiction:
Improveplayback latencyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The system implements intelligent caching that selectively transfers only the media content that the user is actively browsing or likely to play next, rather than caching all available media. The system monitors user browsing behavior and caches content in advance based on predicted playback intent, using approximately 3MB of network bandwidth for pre-loading. This partial action approach reduces latency for anticipated content while avoiding unnecessary network consumption for content the user never plays.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20260019664A1Caching Media in a Media Fling System
Publication Date: 2026.01.15 COMCAST CABLE COMM LLC
  • US20260019664A1 patent drawing
  • US20260019664A1 patent drawing
  • US20260019664A1 patent drawing

AI summary

Aspects of the disclosure relate to a content (e.g., media) transfer or fling platform system and method. In a media fling platform system, media items may be cached at a rendering device prior to any selection of media items to fling. The determination of which media to cache may be based on a variety of factors including a user fling history, a currently viewed media item, and a navigation point in the media files. A fling request may take priority over caching, and the fling request may interrupt any caching processes.