Smart Card Time Manager Decouples Application Layer From Protocol Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Smart card communication protocols face challenges in managing time constraints, particularly in open operating systems like JavaCard, where the application layer is not designed to handle time-related aspects, leading to restrictive and non-portable time management solutions.
Innovation Solution
A time manager entity is introduced within the smart card, interfacing with the protocol layer to periodically construct and transmit waiting time extension requests, decoupling the application layer from time management and relying on the protocol layer for timing, using a dedicated timer and protocol parameters to avoid conflicts and ensure efficient communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the application layer manages waiting time extension requests directly, then time management can be performed at the application level, but the solution becomes non-portable and restrictive across different operating systems
Solution Approach 1:
The patent introduces a time manager as an intermediary component between the application layer and protocol layer. This time manager handles waiting time extension requests independently, allowing the application layer to remain time-independent while still enabling time management functionality. The time manager acts as a mediator that translates application-level time requirements into protocol-compliant waiting time extension requests, ensuring portability across different operating systems including open systems like JavaCard.
2Adaptability or versatility
If the application layer is designed to be independent of time aspects, then portability is improved, but time management becomes restrictive and difficult to implement
Solution Approach 1:
The time manager serves as an intermediary that bridges the gap between the time-independent application layer and the time-sensitive communication protocol. It provides time management functionality without requiring the application layer to be time-aware, thus maintaining portability while enabling effective time management through waiting time extension requests.
Solution Approach 2:
The patent extracts time management functionality from the application layer and places it in a separate time manager component. This extraction allows the application layer to remain independent of time aspects, ensuring portability, while the time manager handles all time-related operations including waiting time extension requests, maintaining ease of time management.
3Device complexity
If waiting time extension requests are managed by the protocol layer, then time management is simplified, but the application layer cannot handle long processing processes effectively
Solution Approach 1:
The time manager as an intermediary enables the application layer to handle long processing processes by managing waiting time extension requests independently. It monitors processing duration and sends appropriate WTX requests to extend the waiting time at the protocol layer, allowing long processes to complete without timeout errors while keeping protocol layer complexity low.
4Ease of operation
If empirical time counting is used in the application layer, then time management can be implemented, but it becomes restrictive for short waiting times and complex cryptography algorithms
Solution Approach 1:
The time manager provides a standardized interface for time management that adapts to different processing durations automatically. It handles both short waiting times and long cryptographic processing by managing waiting time extension requests appropriately, eliminating the restrictiveness of empirical time counting while maintaining ease of operation through a unified time management mechanism.
Data Source
AI summary
An entity of the smart card type has an application layer linked to a communication protocol layer. A time manager containing a timer interfaces with the protocol layer. The time manager substantially periodically constructs waiting time extension requests transmitted to a terminal through the protocol layer as long as data are being processed in the application layer. The application layer is thus freed from any time constraint.