Secure Element Credential Provisioning Across Multiple Wallet TSMs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing credentials for multiple first- and third-party digital wallet applications on a single mobile device is challenging due to lack of vertical integration and potential conflicts in secure element resource allocation.

Innovation Solution

A system that allows third-party and non-native applications to interface with a secure element, utilizing multiple Trusted Service Managers (TSMs) for credential provisioning, including onboarding, domain creation, and applet management, ensuring secure and efficient transmission of payment credentials.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple digital wallet applications are installed on a single mobile device, then user convenience and payment options are improved, but resource conflicts and security management complexity increase

Engineering Contradiction:
Improvepayment optionsVSAvoidcredential management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments credential management by introducing multiple independent Trusted Service Managers (TSMs), each responsible for specific wallet applications. This segmentation allows different wallet apps to have dedicated credential provisioning and management channels, reducing conflicts while maintaining multiple payment options.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces TSMs as intermediary components between wallet applications and the secure element. These intermediaries manage credential provisioning, domain creation, and applet management, thereby simplifying the overall system complexity while enabling multiple wallet applications to coexist securely.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If third-party applications interface with the secure element, then application versatility is improved, but security risks and resource allocation conflicts increase

Engineering Contradiction:
Improveapplication interface capabilityVSAvoidsecure element security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary security setup by having TSMs provision credentials, create domains, and install applets before third-party applications access the secure element. This preliminary configuration ensures that proper security contexts and access controls are established in advance, reducing security risks while enabling application versatility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements local quality by creating separate domains within the secure element for different wallet applications. Each domain has its own security context and credentials managed by specific TSMs, allowing third-party applications to interface with the secure element while maintaining isolated security boundaries that prevent resource allocation conflicts and security breaches.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250380136A1Multi-trusted services manager (TSM) credential management
Publication Date: 2025.12.11 APPLE INC
  • US20250380136A1 patent drawing
  • US20250380136A1 patent drawing
  • US20250380136A1 patent drawing

AI summary

Aspects of the subject technology include receiving a selection of a digital credential at a user interface associated with the non-native application process, providing to a first server associated with the first entity a first request for provisioning a domain on a secure element of the user device, receiving an indication that a first script was provided to the secure element for the secure element to provision the domain on the secure element according to the first script, providing to a second server associated with a second entity a second request to provision the digital credential in the provisioned domain on the secure element, receiving from the second server a second script for provisioning the digital credential in the provisioned domain on the secure element, and causing the secure element to provision the digital credential in the provisioned domain on the secure element according to the second script.