Codec Management Using Local Tokens and Cloud Provisioning

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing information handling systems face challenges in efficiently managing codecs for media file encoding and decoding, particularly when specific codecs are not initially enabled, leading to potential encoding or decoding failures.

Innovation Solution

A method involving a driver accessing a local token store to identify enabled codecs, requesting a unique token from a cloud codec management service when a required codec is not enabled, storing the token, and restarting the driver to enable the codec for media file processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If codecs are initially disabled at the information handling system, then system security and control are improved, but media processing functionality is worsened when codecs are needed

Engineering Contradiction:

Improvecodec enablement controlVSAvoidmedia processing capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary checks of the local token store before media processing operations. The driver proactively verifies available codecs against the media file requirements, and pre-fetches tokens from the cloud codec management service when needed, rather than waiting for processing failures to occur

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

A cloud codec management service acts as an intermediary between the information handling system and codec licensing authorities. This service provides tokens that enable codecs without requiring direct system configuration changes, maintaining security while enabling functionality

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the driver restarts after receiving a token, then codec enablement is improved, but system operational continuity is worsened

Engineering Contradiction:

Improvecodec enablementVSAvoiddriver restart time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically determines whether a driver restart is necessary based on the specific codec enablement scenario. The driver monitors its own state and the success of token application, restarting only when required to properly load the enabled codec, rather than following a fixed restart protocol

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the driver monitors codec enablement success and media processing outcomes. This feedback loop allows the system to learn from past operations and optimize future driver restart decisions, reducing unnecessary restarts while ensuring proper codec loading when needed

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12407515B2Codec management at an information handling system

Publication Date: 2025.09.02 DELL PROD LP

AI summary

Enabling codecs at an IHS including: accessing a local token store that stores tokens, each token associated with a codec; identifying codecs enabled at the IHS based on the tokens; receiving a request to encode or decode a media file, the media file associated with a particular codec for encoding or decoding of the media file; determining that the particular codec is not enabled at the IHS based on the previously identified enabled codecs, and in response, transmitting a request to a cloud codec management service; receiving the particular token, the particular token signed and unique to the IHS, and in response, storing the particular token at the local token store; restarting the driver, and in response, accessing the local token store; obtaining from the local token store, the particular token, and in response, enabling the particular codec for the media file.