Kernel Controller for Dynamic Payment Processing Offload
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing payment readers often struggle to meet the processing demands of modern transactions due to hardware limitations, power constraints, or outdated software, leading to inefficiencies and security risks.
Innovation Solution
Implementing a kernel controller that dynamically selects the appropriate kernel for processing, allowing payment readers to offload resource-intensive tasks to external devices with GEN 2 kernels, such as mobile devices or remote servers, to optimize resource utilization and enhance security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If payment readers use existing hardware with limited processing capabilities, then device complexity and cost are reduced, but processing speed and capability deteriorate when handling modern payment transactions
Solution Approach 1:
The patent introduces a kernel controller as an intermediary component that manages and coordinates multiple kernels (processing units) within the payment reader. This kernel controller dynamically selects and activates appropriate kernels based on transaction requirements, enabling the system to handle complex modern payment transactions without requiring complete hardware replacement. The kernel controller acts as a mediator between the transaction processing demands and the available processing resources.
Solution Approach 2:
The payment reader's processing system is segmented into multiple independent kernels with different processing capabilities and resource requirements. Instead of relying on a single monolithic processing unit, the system divides processing functions across multiple kernels (e.g., first kernel, second kernel, third kernel), each optimized for specific types of transactions. This segmentation allows the system to handle diverse payment scenarios by activating only the necessary kernel for each transaction type.
2Speed
If payment readers process all transactions locally, then processing speed is maintained, but power consumption increases and security risks arise from processing sensitive data on potentially compromised devices
Solution Approach 1:
The patent implements dynamic kernel selection where the system adaptively chooses which kernel to activate based on real-time transaction requirements, device state, and security conditions. The kernel controller dynamically adjusts processing architecture by selecting between local kernel processing and external device processing, optimizing the balance between processing speed, power consumption, and security for each specific transaction scenario.
Solution Approach 2:
The system changes processing parameters by dynamically selecting different kernels based on transaction characteristics, device resources, and security requirements. When power consumption needs to be reduced or security concerns arise, the system can shift from local processing to external device processing, effectively changing the processing location parameter while maintaining transaction integrity.
3Reliability
If payment readers use outdated software versions to maintain compatibility with existing hardware, then hardware obsolescence is delayed, but security vulnerabilities increase and modern payment functionalities cannot be supported
Solution Approach 1:
The patent creates a universal processing architecture where multiple kernels with different software versions and capabilities can coexist within a single payment reader device. The kernel controller selects the appropriate kernel based on the specific transaction type and security requirements, enabling the system to handle both legacy transactions requiring older software versions and modern transactions requiring updated security protocols and functionalities.
Solution Approach 2:
The system creates virtual copies of different kernel environments within the same physical device, allowing multiple software versions to run simultaneously in isolated contexts. This enables the payment reader to maintain compatibility with legacy hardware while also supporting modern secure processing capabilities through copied or emulated kernel environments.
4Productivity
If payment readers are upgraded with newer hardware to meet modern processing demands, then processing capability improves, but cost increases and existing deployed systems become obsolete
Solution Approach 1:
Instead of replacing entire payment reader devices, the patent segments the processing functionality into multiple kernels that can be independently activated. This allows existing deployed payment readers to gain enhanced processing capabilities by activating additional or different kernels without requiring complete hardware replacement, thereby reducing deployment costs while improving productivity.
Solution Approach 2:
The system dynamically adapts its processing architecture by selecting from available kernels based on transaction requirements. This dynamic capability allows existing hardware to effectively evolve and meet modern processing demands through software-based kernel selection rather than requiring physical hardware upgrades, reducing the total cost of ownership.
Data Source
AI summary
A payment reader can have one or more kernels capable of performing certain payment processing functions but not capable of performing certain, more processing-intensive payment processing functions. The payment reader may be designed to selectively assign processing tasks to application layer kernels located on a mobile device and/or a cloud-based device external to the payment reader, the mobile device having more or different processing resources than the payment reader. The selective assignment may be made dynamically based on the measurement of a condition of the reader or an occurrence of an event, such as a determination that the payment reader cannot process a transaction, that the payment reader does not have sufficient battery strength to process the transaction, or that there has been a tampering attempt at the payment reader. The payment reader also has a physical layer module, which module maintains its processing on the payment reader. By these means, the processing related to a payment transaction is conducted on a hybrid system, using resources both local to and remote from the payment reader.