Token-Based Wallet Communication for Secure Element Memory Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing architecture of electronic wallets requires users to activate and configure multiple service provider apps separately for each transaction, leading to a poor user experience due to different user interfaces and memory constraints on secure elements, making it cumbersome for service providers to implement and manage applets for wireless radio communication.
Innovation Solution
Implementing a token-based communication method between extraneous applications and an electronic wallet using APIs for listing, selecting, and interacting with secure elements, allowing users to manage and activate services within a unified core wallet environment without leaving it, and storing tokens on a secure element for wireless radio communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple service provider apps are implemented separately for each transaction, then wireless radio communication functionality is achieved, but user interface complexity and operation difficulty increase
Solution Approach 1:
The patent merges multiple service provider apps into a single unified electronic wallet application. Instead of requiring separate apps for different wireless communication services, the invention consolidates them into one interface that manages all services through a common user experience, reducing the cognitive load and operational complexity for users.
Solution Approach 2:
The electronic wallet is designed as a universal platform that can handle multiple types of transactions and services through a single application. The system provides multi-functional capabilities including payment transactions, ticketing, and other wireless radio communication services all through one unified interface, eliminating the need for users to switch between multiple specialized apps.
2Adaptability or versatility
If multiple applets are stored on secure elements, then service functionality is enhanced, but memory constraints are exceeded
Solution Approach 1:
The invention extracts the service provider application logic from the secure element and places it in the extraneous application on the terminal. Only essential token data and minimal configuration information are stored on the secure element, while the bulk of the application code and data reside externally, thereby preserving secure element memory capacity while maintaining full service functionality.
Solution Approach 2:
The system introduces an intermediary architecture where the extraneous application acts as a mediator between the user interface and the secure element. This intermediary layer handles the complex application logic and data storage requirements, allowing the secure element to remain a compact, secure token storage device without needing to accommodate large application codebases.
3Productivity
If separate service provider apps are implemented, then specific transaction capabilities are achieved, but device complexity increases
Solution Approach 1:
The invention segments the system into distinct functional layers: the extraneous application handles user interaction and high-level transaction logic, while the secure element handles secure token storage and cryptographic operations. This segmentation allows each component to be optimized independently, reducing the overall implementation complexity while maintaining full transaction capabilities.
Solution Approach 2:
Instead of implementing multiple separate service provider apps, the system uses a single extraneous application that can dynamically load and manage multiple virtual service representations. The application uses token-based copying mechanisms where service data is represented as tokens that can be instantiated and managed without duplicating the full application code for each service type.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
This solution simplifies user interactions by allowing service providers to integrate multiple services within a unified wallet environment, reducing the need for separate applets and user interface adaptations, while enabling seamless wireless transactions without additional memory constraints or complex applet implementations.
Implementation Method 1
a secure element (e.g. in form of a SIM card/UICC or a Java card integrated in the chip set of the terminal) with Java applets that can be addressed on the one hand by applications on the terminal and on the other hand via wireless radio communication (such as NFC) by points of acceptance
Data Source
AI summary
A method for token-based communication between extraneous applications and an electronic wallet includes: (1a) selecting items for storage in the core wallet by one or more extraneous application(s); (1b) sending information on the selected items to the core wallet by the extraneous application(s); (1c) displaying the selected items on the terminal by the core wallet; (1d) waiting for activation of at least one of the displayed items based on interaction of the user with the core wallet; (1e) retrieving, for each activated item, a token associated with the item in the extraneous application from which the item originates by the core wallet; and (1f) storing the tokens retrieved in step (1e) in a wallet applet installed on a secure element that is configured for wireless radio communication.