Shared CVM Applet for Mobile Payment Cardlets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing smartphone-based payment systems lack flexibility and convenience in cardholder verification methods, particularly when managing multiple payment cardlets, as they often require different PINs for each cardlet and do not easily accommodate upgrades or changes in verification methods.
Innovation Solution
A shared CVM applet stored in the secure element of a smartphone validates user input and issues a CVM token, which is verified by the selected payment cardlet, allowing for flexible CVM methods such as PIN or biometric verification, and supports multiple or time-limited authorizations without requiring changes to the payment cardlets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a standard shared CVM applet is used to manage PIN entry for all payment cardlets, then a single PIN can be used to unlock any cardlet, but the system lacks flexibility for upgrading or changing verification methods
Solution Approach 1:
The system separates the CVM verification logic into a dedicated shared CVM applet that is independent of individual payment cardlets. This segmentation allows the verification method to be updated or changed in the shared applet without modifying any cardlet code, thereby providing both ease of operation with a single PIN and adaptability for upgrading verification methods.
Solution Approach 2:
The shared CVM applet can dynamically update its verification logic and supported methods over time. The system allows for dynamic changes in CVM requirements and verification methods without requiring changes to the payment cardlets themselves, enabling the system to adapt to new security requirements while maintaining operational simplicity.
2Reliability
If different PINs are required for each payment cardlet, then security is maintained per cardlet, but user convenience and system flexibility are reduced
Solution Approach 1:
The system merges the CVM verification functionality across all payment cardlets into a single shared CVM applet. This allows a single PIN or biometric credential to verify access to multiple cardlets while maintaining security, as the shared applet centrally manages verification for all cardlets rather than requiring separate verification for each.
Solution Approach 2:
The shared CVM applet provides universal verification service for multiple payment cardlets, making it multi-functional. A single verification credential can unlock any cardlet in the system, providing both security and convenience by eliminating the need for multiple different PINs while maintaining per-cardlet security through centralized verification management.
3Reliability
If CVM verification logic is embedded in each payment cardlet, then each cardlet is self-sufficient, but system flexibility for upgrades is reduced
Solution Approach 1:
The CVM verification logic is extracted from individual payment cardlets and placed in a separate shared CVM applet. This extraction allows each cardlet to remain simple and self-sufficient for its payment functions, while the verification logic resides in a separate component that can be independently updated or upgraded without affecting the cardlets themselves.
Solution Approach 2:
The shared CVM applet acts as an intermediary between the user and multiple payment cardlets. It mediates the verification process by receiving verification credentials and determining access rights across multiple cardlets, allowing upgrades to verification methods in the intermediary without requiring changes to the individual cardlets.
4Adaptability or versatility
If multiple CVM verification methods are supported, then user convenience is improved, but system complexity increases
Solution Approach 1:
The shared CVM applet is designed with multi-functionality to support multiple verification methods including PIN, biometric, and other CVM approaches. By consolidating support for multiple methods in a single shared component rather than having separate verification logic for each method, the system achieves versatility without proportionally increasing complexity.
Solution Approach 2:
The system uses a unified shared CVM applet structure that handles all verification methods through a common framework. This homogeneous approach to managing diverse verification methods reduces complexity by providing a consistent interface and management mechanism for all CVM types, rather than requiring separate handling for each verification method.
Data Source
AI summary
In a payment-enabled smartphone, a shared cardholder verification method (CVM) applet serves a number of mobile payment cardlets. The shared CVM applet validates CVM information input by a user of the smartphone and in response issues a CVM token. The CVM token is passed to a particular one of the mobile payment cardlets that is selected for a current transaction. The selected mobile payment cardlet submits the CVM token back to the shared CVM applet for verification. Upon verifying the CVM token, the shared CVM applet enables the selected mobile payment cardlet to perform the current transaction.