Smart Card Event Listener API for Secure Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Smart Card systems lack efficient mechanisms to manage events related to Smart Card-accessing devices and ensure secure access control, leading to potential unauthorized access and missed events due to polling limitations.
Innovation Solution
A customized API is introduced that allows applications to listen for specific events using the 'addEventListener' method, associating user sessions with Smart Card-accessing devices to prevent unauthorized access and execute functions in response to events, regardless of the application's busy state.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If polling is used to detect Smart Card events, then the application can detect events, but the application code becomes complex and events may be missed when the application is busy
Solution Approach 1:
The patent introduces an intermediary event listener mechanism that sits between the Smart Card device and the application. Instead of the application directly polling for events, the event listener continuously monitors the device and automatically invokes the application's callback function when events occur. This mediator eliminates the need for complex polling logic in the application while ensuring reliable event detection, as the listener operates independently of the application's busy state.
Solution Approach 2:
The event listener system performs self-service by autonomously monitoring the Smart Card device and automatically triggering application responses. The system registers the application's callback function once, then independently manages continuous event detection and automatic invocation without requiring the application to repeatedly poll or check for events. This self-managing mechanism simplifies application code while maintaining reliable event detection.
2Adaptability or versatility
If multiple users can access multiple Smart Card devices, then system versatility increases, but unauthorized access between users becomes possible
Solution Approach 1:
The patent segments the Smart Card device into multiple isolated access contexts, one for each user session. Each user session is associated with a specific device context that includes separate event listeners, callback functions, and communication channels. This segmentation ensures that User A's event listeners can only receive events from User A's device context, preventing unauthorized access to User B's Smart Card while maintaining versatile multi-user support.
Solution Approach 2:
The patent applies local quality by giving each user session its own isolated event listener instance with device-specific parameters and callback functions. Instead of a single shared event listener that could access any device, each user has a locally-configured listener that is bound to their specific device context. This localized configuration ensures that event detection and response mechanisms are inherently restricted to the authorized user's device, preventing cross-user access while maintaining system versatility.
3Reliability
If the application must poll the Smart Card device continuously, then events are detected reliably, but the application cannot efficiently perform other tasks
Solution Approach 1:
The event listener acts as an intermediary that handles continuous event monitoring independently of the application's main execution thread. The listener runs as a separate mechanism that continuously watches for events on the Smart Card device, while the application can simultaneously perform other tasks. When events occur, the listener automatically invokes the application's callback function, ensuring reliable event detection without preventing the application from efficiently executing other operations.
Data Source
AI summary
A mechanism is disclosed for allowing an application to perform specified operations in response to occurrences of a specified event relative to a specified Smart Card-accessing device. A customized API is exposed to the application. The application invokes an “addEventListener” method of the API. The invocation of the method specifies, as parameters of the method, at least a Smart Card-accessing device, a type of event, and a function. The server computer executing the application detects the invocation of the “addEventListener” method. In response to detecting the invocation, the server determines the type of the event specified by the invocation, and starts a mechanism that executes the specified function each time that an event of the specified type occurs relative to the specified Smart Card-accessing device. Consequently, the application does not need to be programmed to poll the specified Smart Card-accessing device at specific times during the application's execution.


