Cross-Platform Application Identification with 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 the need for proprietary implementations, which can lead to compatibility issues and security vulnerabilities.

Innovation Solution

A system and method for application identification using application identifiers (IDs) and shared libraries, where applications are authenticated by an authentication server to ensure compatibility and security, involving a session manager, encrypted provisioning data, and library manifests to verify the integrity and compatibility of applications and shared libraries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are natively implemented on each device platform, then application functionality and performance are improved, but device complexity and porting requirements increase

Engineering Contradiction:
Improveapplication functionalityVSAvoidporting requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal application execution mechanism where a single application binary can run across multiple device platforms through a common runtime environment. The system uses a standardized application package format and a platform-agnostic execution layer that translates application requests into platform-specific operations, eliminating the need for separate native implementations on each device type.

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

Solution Approach 2:

The patent introduces an intermediary runtime environment and authentication server that mediates between the application and the diverse device platforms. This intermediary layer handles platform-specific adaptations, security authentication, and resource management, allowing applications to maintain consistent functionality across different devices without direct platform-specific coding.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If proprietary access information is used for device updates and services, then device security is improved, but cross-platform compatibility and interoperability decrease

Engineering Contradiction:
Improvedevice securityVSAvoidcross-platform compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an authentication server as an intermediary that manages security credentials and access information across multiple platforms. Instead of using proprietary access information embedded in each device, the system uses a centralized authentication mechanism that verifies application identities and grants access rights, maintaining security while enabling cross-platform interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal authentication and authorization framework that works across different device platforms and service types. The system uses standardized security protocols and a common credential verification mechanism that can authenticate applications on any supported platform, replacing proprietary access information with a universal security architecture.

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

3Reliability

If applications are authenticated by an authentication server, then security and control are improved, but processing time and system complexity increase

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary authentication actions where application identifiers and security credentials are verified in advance during application installation or first execution. The authentication server pre-validates application identities and establishes trust relationships before the application needs to access protected resources, reducing authentication overhead during runtime operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the authentication server provides authentication results and security policies back to the device and application. Once an application is authenticated, the system caches authentication decisions and provides rapid feedback for subsequent access requests, reducing repeated authentication delays while maintaining security control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250300972A1Systems and Methods for Application Identification
Publication Date: 2025.09.25 DIVX LLC
  • US20250300972A1 patent drawing
  • US20250300972A1 patent drawing
  • US20250300972A1 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.