Third-Party Wallet Credential Management Through OS-Mediated NFC Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing digital credentials across multiple third-party applications on a single mobile device can lead to conflicts and inefficiencies, particularly in transactions, due to the lack of seamless integration and access to hardware features.

Innovation Solution

An operating system framework that prioritizes and manages third-party digital wallet applications, ensuring efficient credential transmission by configuring hardware components like NFC controllers based on default app settings, while maintaining security and user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple third-party digital wallet applications are installed on a single mobile device, then user choice and functionality are improved, but credential management complexity and transaction conflicts increase

Engineering Contradiction:
Improveuser choiceVSAvoidcredential management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The operating system acts as an intermediary between multiple third-party digital wallet applications and the credential management system. It provides a unified interface for credential storage, retrieval, and transmission, allowing multiple apps to coexist without direct conflicts. The OS manages app-specific credentials and coordinates hardware access (NFC controller) among competing applications, resolving conflicts centrally rather than requiring apps to manage their own credential interactions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The operating system creates a universal credential management framework that serves multiple third-party digital wallet applications simultaneously. This single system handles credentials for different merchants and payment processors, providing multi-functionality that eliminates the need for separate credential management systems for each app while maintaining secure, app-specific credential isolation.

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

2Adaptability or versatility

If third-party applications have direct access to hardware components, then application functionality is improved, but security risks and resource conflicts increase

Engineering Contradiction:
Improveapplication functionalityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The operating system serves as a security intermediary between third-party applications and hardware components. Rather than allowing direct access, the OS mediates all hardware interactions through controlled interfaces, managing permissions and resource allocation. This ensures that applications can access necessary hardware (like NFC controllers) for their intended functions while the OS maintains security oversight and prevents unauthorized or conflicting access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically manages hardware access based on application needs and transaction context. Permissions and resource allocation are not fixed but adapt in real-time based on which application is active, what hardware resources are required, and current security conditions. This dynamic control allows full functionality when needed while maintaining security through conditional access management.

Inventive Principle:
Principle #15Dynamics

3Reliability

If the operating system manages credential transmission centrally, then security and control are improved, but transmission speed and efficiency may be reduced

Engineering Contradiction:
ImprovesecurityVSAvoidcredential transmission speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The operating system performs preliminary actions by pre-configuring credential storage structures, establishing secure communication channels, and caching frequently accessed credentials. This preparation work is done in advance of actual transactions, so that when credential transmission is needed, the infrastructure is already in place and ready for rapid operation, minimizing the impact of centralized management on transmission speed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250278717A1Third-party application-based credential management
Publication Date: 2025.09.04 APPLE INC
  • US20250278717A1 patent drawing
  • US20250278717A1 patent drawing
  • US20250278717A1 patent drawing

AI summary

Aspects of the subject technology include receiving a request to perform a wireless transaction, responsive to receiving the request, determining whether an application displayed on the electronic device is configured to perform the wireless transaction, responsive to determining that the application displayed on the electronic device is configured to perform the wireless transaction, facilitating the application in conducting the wireless transaction.