OEM Vendor App Data Sharing via Cloud Mediator

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Closed operating system variants like Windows 10 in S Mode restrict open access to APIs and data stores, making it difficult for preloaded software to share information with vendor applications, as existing solutions rely on both OEM and software vendor applications reading the same data from disk or BIOS.

Innovation Solution

Mechanisms are developed to share user-provided information between OEM and vendor applications by determining system identifiers using APIs, sending them to a vendor cloud server, and using this information to configure the vendor application, even on locked-down operating systems, allowing for customized behavior and subscription settings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If OEM and vendor applications read the same data from disk or BIOS, then information sharing between applications is enabled, but access to APIs and data stores is restricted on closed operating systems

Engineering Contradiction:

Improveinformation sharing between applicationsVSAvoidaccess to APIs and data stores

Core Design Contradiction:

Loss of informationVSEase of operation

Solution Approach 1:

The patent introduces a cloud server as an intermediary between the OEM application and the vendor application. The OEM application uploads user information and system identifier to the cloud server, which then provides this information to the vendor application. This mediator approach enables information sharing without requiring direct access between applications on the locked-down operating system.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent moves the information sharing operation from the local device dimension to the cloud dimension. Instead of applications communicating directly on the device (which is restricted), the system uses cloud-based storage and retrieval, adding a spatial dimension to the data exchange process that bypasses operating system restrictions.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If preloaded software receives information from OEM and customizes behavior, then software functionality is enhanced, but access restrictions on locked-down operating systems prevent implementation

Engineering Contradiction:

Improvesoftware behavior customizationVSAvoidaccess to APIs and data stores

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent performs preliminary actions by having the OEM application collect and upload user information and system identifiers to the cloud server before the vendor application needs this data. This advance preparation enables the vendor application to retrieve pre-configured information and customize its behavior without needing to access restricted system areas.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The cloud server acts as a mediator that receives customization parameters from the OEM application and delivers them to the vendor application. This intermediary mechanism enables software behavior customization while maintaining the locked-down state of the operating system and avoiding direct API access requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Loss of information

If separate applications access OEM-specific locations and encrypted data files, then data retrieval is possible, but security and access control are compromised

Engineering Contradiction:

Improvedata retrieval capabilityVSAvoidsecurity and access control

Core Design Contradiction:

Loss of informationVSReliability

Solution Approach 1:

The patent extracts sensitive user information and system identifiers from the locked-down operating system environment and stores them in a cloud-based location. This extraction removes the security risk associated with multiple applications accessing sensitive data on the device, while maintaining the ability to retrieve and use this information for application customization.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20240403071A1Systems, methods, and media for sharing information with vendor applications in secure environments

Publication Date: 2024.12.05 MCAFEE LLC

AI summary

Mechanisms for sharing user-provided information from an original equipment manufacturer (OEM) application and a vendor application are provided, the mechanisms including: receiving the user-provided information at the OEM application; determining a system identifier of a system on which the OEM application is executing at the OEM application using a hardware processor; providing the user-provided information and the system identifier to a vendor cloud server from the OEM application; determining the system identifier at vendor application; providing the system identifier from the vendor application to the vendor cloud server; receiving the user-provided information at the vendor application from the vendor cloud server in response to providing the system identifier to the vendor cloud server; and using the user-provided information to configure the vendor application.