Client-Side Content Encoding for Server Load Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Social media and content distribution platforms face computationally intensive decode/re-encode processes due to varying encoding quality of user-uploaded content, leading to reduced content quality and lack of efficient client-side encoding solutions.

Innovation Solution

Implementing client-side encoding methods where user devices receive encoding instructions and parameters, enabling them to encode content according to recipient requirements, with embedded identifiers for validation, thereby ensuring proper encoding and reducing server-side transcoding needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server decodes and re-encodes uploaded content to ensure proper encoding format, then the content encoding reliability is improved, but the computational cost and processing time increase significantly

Engineering Contradiction:
Improvecontent encoding reliabilityVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The patent applies preliminary action by performing encoding operations on the client device before content is uploaded to the server. The client receives encoding instructions and parameters from the server, then encodes the content locally according to these instructions. This preliminary encoding action shifts the computational burden from the server to the client, allowing the server to receive pre-encoded content that requires minimal processing, thus improving encoding reliability while reducing server computational cost.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If the server performs decode/re-encode process to ensure proper encoding, then the content quality is maintained, but the processing time and server resources are consumed

Engineering Contradiction:
Improvecontent qualityVSAvoidprocessing time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent extracts the encoding operation from the server-side processing pipeline and relocates it to the client device. The server provides encoding instructions and parameters, then the client device performs the actual encoding operation locally. This extraction removes the time-consuming decode/re-encode process from server processing, allowing the server to simply receive and store the already-encoded content, thereby maintaining content quality while significantly reducing processing time and server resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

3Power

If client-side encoding is implemented to reduce server computational burden, then server resources are saved, but the complexity of the upload system increases

Engineering Contradiction:
Improveserver computational resourcesVSAvoidupload system complexity
Core Design Contradiction:
PowerVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism in the form of encoding instructions and parameters that are transmitted from the server to the client. These instructions serve as a mediator that guides the client device through the encoding process without requiring the client to have complex encoding capabilities built-in. The server sends encoded format specifications, and the client simply needs to apply these instructions, which simplifies the overall system architecture compared to having the server perform all encoding operations while maintaining client-side encoding functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8166132B1Systems and methods for client-side encoding of user-generated content
Publication Date: 2012.04.24 ADOBE INC
  • US8166132B1 patent drawing
  • US8166132B1 patent drawing
  • US8166132B1 patent drawing

AI summary

Methods and systems are disclosed that facilitate client-side encoding of content. Certain embodiments involve sending a user's client device items for encoding content that will be uploaded to an upload recipient. In some cases, a client-device may receive an encoding application or application component for performing the encoding. In some cases, a client device may receive upload parameter information for the upload. The embedded content may include an identifier that allows confirmation that it was encoded according to the parameters. Embodiments provide various mechanisms for an upload recipient to guarantee or otherwise trust that uploaded content has been appropriately encoded and/or encrypted by a user. Items and instructions for uploading can be provided from the upload recipient or from a provider who is trusted by the client and the recipient with respect to encoding the content.