Multi-View Live-Stream Rendering on Resource-Constrained Mobile Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face resource and energy constraints, limiting their ability to efficiently render multiple live-streams simultaneously, which is particularly challenging for applications like live-streaming video or audio content.
Innovation Solution
The solution involves close communication between the streaming backend, audio and video streaming client-side processors, and the user-facing frontend layer, considering user interactions to provide low-latency multi-view live-streaming with minimal energy and resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple live-streams are rendered simultaneously on mobile devices, then user experience is enhanced with detailed views of multiple live events, but resource consumption (processing power, memory, energy) increases significantly
Solution Approach 1:
The patent segments the rendering process by dividing the mobile device's display into multiple zones, each dedicated to a specific live-stream feed. This allows simultaneous rendering of multiple streams by spatial segmentation rather than temporal multiplexing, enabling multi-view capability while optimizing resource allocation for each segment independently.
Solution Approach 2:
The patent implements periodic refresh rates for different live-stream segments based on their importance and user interaction patterns. Frequently viewed or critical streams are refreshed at higher rates, while less critical streams use lower refresh rates, reducing overall processing power and energy consumption while maintaining acceptable user experience.
2Adaptability or versatility
If multiple live-streams are rendered simultaneously on mobile devices, then user experience is enhanced with detailed views of multiple live events, but processing power requirements exceed available resources
Solution Approach 1:
The patent applies local quality optimization by rendering different live-stream segments at different resolutions and quality levels. High-priority or user-selected streams receive higher resolution and processing resources, while background or less important streams are rendered at lower quality, optimizing the overall processing power distribution across multiple simultaneous streams.
Solution Approach 2:
The patent implements partial rendering by pre-processing and pre-buffering portions of live-stream data that are likely to be viewed, while deferring full-resolution rendering of less critical segments until needed. This allows the system to maintain multiple stream connections and prepare data in advance without fully rendering all streams simultaneously, reducing peak processing power requirements.
3Adaptability or versatility
If multiple live-streams are rendered simultaneously on mobile devices, then detailed glances at multiple live events are provided, but memory constraints prevent efficient rendering
Solution Approach 1:
The patent implements preliminary action by pre-buffering and pre-processing live-stream data in memory before it needs to be rendered. Data is fetched and prepared in advance during idle periods or when resources are available, reducing peak memory requirements during active multi-view rendering by having data ready in an optimized format rather than loading everything simultaneously.
Solution Approach 2:
The patent applies nesting by organizing live-stream data structures in a hierarchical manner, where commonly accessed data is stored in faster, higher-memory segments while less frequently accessed data is stored in slower, lower-memory segments. This nested memory organization allows efficient access to critical stream data while minimizing overall memory footprint for multiple simultaneous streams.
Data Source
AI summary
The present document describes devices and methods for rendering multiple live-streams on a user interface (UI) with minimal resources. The UI is activated, having a first set of remote sensors loaded for rendering. The first set of remote sensors receive a first activation signal and begin streaming first data, which the UI renders. Respondent to an action changing the set of remote sensors to be rendered on the UI, a second set of remote sensors are loaded for rendering. The second set of remote sensors receive a second activation signal and begin streaming second data, which the UI renders while the first set of remote sensors continue streaming the first data. The first data is no longer streamed after a threshold time is reached.