Client-Side Video Rendering for Real-Time Personalized Playback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Personalized videos rendered on servers are computationally expensive and introduce significant lag, making them impractical for large-scale marketing campaigns and decreasing customer interaction.
Innovation Solution
A client-side video rendering system that uses a client device's web browser to render personalized content videos in real-time by overlaying graphics on streaming videos, utilizing a client-side renderer and Canvas element, and managing graphics synchronization with video progress to avoid server-side rendering and buffering lag.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If server-side rendering is used for personalized videos, then video personalization is achieved, but computational cost becomes prohibitively expensive
Solution Approach 1:
The patent extracts the rendering function from the server and relocates it to the client device. The client-side renderer processes video frames locally using JavaScript, eliminating the need for expensive server-side rendering while maintaining personalized video output.
Solution Approach 2:
The patent creates a copy of the rendering function that runs on the client device rather than requiring the original server-based rendering system. This copied renderer produces identical personalized videos with significantly reduced computational cost.
2Productivity
If real-time rendering is used for personalized videos, then video freshness is improved, but buffering lag increases
Solution Approach 1:
The patent pre-loads video frames into memory before they are needed for display. The client-side renderer buffers video frames and graphics overlays in advance, allowing smooth real-time playback without buffering lag while maintaining video freshness.
3Adaptability or versatility
If server-side rendering is used for personalized videos, then video personalization is achieved, but rendering time delay increases
Solution Approach 1:
The patent extracts the time-consuming rendering process from the server and executes it locally on the client device. This eliminates network transmission delays and server processing time, achieving real-time personalized video rendering without time delay.
4Use of energy by stationary object
If client-side rendering is used for personalized videos, then computational cost is reduced, but rendering capability requirements increase
Solution Approach 1:
The patent replaces complex server-side rendering infrastructure with a JavaScript-based client-side renderer. This substitution uses web browser capabilities instead of dedicated rendering hardware, reducing computational cost while maintaining adequate rendering capability for video personalization.
Data Source
AI summary
A system and method for client-side video rendering uses a client device to render personalised content videos in real-time, thus avoiding the cost associated with server-side rendering. The process involves a client device's web browser loading a web page containing a client-side renderer, typically in the form of a JavaScript file. The browser is configured to play videos from a hosting source, while the client-side renderer overlays graphics on the video based on personalised content and a video timeline. The system may also stream videos from hosting to avoid local storage and buffering lag, and it accounts for network latency by synchronising graphics with the video progress. Additionally, the client-side renderer and video timeline configurations can be cached separately, minimising data downloads, and a URL service may be used to resolve URLs while preserving customer data privacy by hosting the web page internally.