Cross-Platform Application Identification With Secure Shared Libraries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Consumer electronic devices face challenges in efficiently identifying and authenticating cross-platform software applications due to resource limitations and security concerns, particularly in ensuring compatibility and preventing unauthorized access to shared libraries.

Innovation Solution

A system and method involving application identifiers (application IDs) and session managers are used to authenticate and authorize applications on user devices, utilizing encrypted provisioning data and library manifests to ensure compatibility and security, with authentication servers verifying application and shared library integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are natively implemented for each device platform, then application performance and compatibility are improved, but device complexity and development cost increase

Engineering Contradiction:
Improveapplication compatibilityVSAvoiddevelopment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal application execution platform that allows a single application to run across multiple device types (set-top boxes, personal computers, mobile devices) without native porting. The system uses a common application binary interface (ABI) and shared library mechanism that enables one application version to function universally across different hardware platforms, eliminating the need for separate native implementations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary layer consisting of shared libraries and an application platform that sits between the application and the underlying device hardware. This intermediary handles platform-specific variations, allowing applications to interact with devices through a standardized interface while the intermediary manages the complexity of device-specific implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If shared libraries are made accessible to applications, then resource efficiency is improved, but security risks and unauthorized access increase

Engineering Contradiction:
Improveresource efficiencyVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements local quality control through application-specific authorization tokens that are generated and validated for each application-library interaction. Each application receives a unique token that grants access only to the specific shared libraries it is authorized to use, with specific parameter ranges and conditions. This ensures that while shared libraries are accessible, each application's access is locally controlled and limited to its authorized scope.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements a feedback mechanism where the set-top box or authentication server continuously monitors application behavior and validates authorization tokens. When an application attempts to access shared libraries, the system provides feedback by validating the token and either granting or denying access based on pre-established authorization rules, creating a closed-loop security control system.

Inventive Principle:
Principle #23Feedback

3Reliability

If application authentication is implemented through encrypted provisioning data, then security is improved, but processing time and computational resources increase

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-generating and embedding encrypted authorization tokens within the application binary during the application creation process. The provisioning data, including encryption keys and authorization parameters, is prepared in advance and embedded into the application package. This eliminates the need for time-consuming authentication computations during application execution, as the authorization is already established beforehand.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12355736B2Systems and methods for application identification
Publication Date: 2025.07.08 DIVX LLC
  • US12355736B2 patent drawing
  • US12355736B2 patent drawing
  • US12355736B2 patent drawing

AI summary

Systems and methods for application identification in accordance with embodiments of the invention are disclosed. In one embodiment, a user device includes a processor and memory configured to store an application, a session manager, an application identifier, and at least one shared library, and the processor is configured by the session manager to communicate the application identifier and the application identifier data to an authentication server and permit the execution of the application in response to authentication of the application by the authentication server.