Non-monolithic Mobile Software Architecture for Seamless Contactless Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional access device architectures, such as monolithic and multi-component architectures, face limitations in flexibility, memory consumption, and user experience due to the need for complete reconfiguration and explicit user intervention to manage different software modules for transactions.
Innovation Solution
A non-monolithic architecture for mobile devices where each software module is built and executed independently on a distinct software package, allowing for seamless selection and execution of different subsets of modules based on interaction initiation data, eliminating link dependencies and enabling seamless transaction processing without user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If a monolithic architecture is used to package all software modules together, then the system structure is simple and easy to manage, but the flexibility to update individual modules is lost and complete reconfiguration is required for any changes
Solution Approach 1:
The patent divides the software system into independent, modular components that can be individually updated and managed. Each software module is packaged separately and can be independently selected and executed based on transaction requirements, eliminating the need for complete reconfiguration while maintaining system simplicity.
2Adaptability or versatility
If multiple software modules are packaged in separate components requiring explicit user input to select the appropriate module, then module flexibility is improved, but user experience degrades due to required user intervention
Solution Approach 1:
The system automatically detects transaction initiation data and autonomously selects the appropriate software module subset without requiring explicit user input. The mobile device self-determines which modules to execute based on the transaction type, maintaining both flexibility and seamless user experience.
3Adaptability or versatility
If separate software packages are used for each software module to enable independent execution, then module independence and updateability are improved, but memory consumption increases
Solution Approach 1:
The patent extracts only the necessary software modules into separate packages based on transaction requirements, rather than loading all possible modules into memory simultaneously. The system dynamically loads and executes only the relevant subset of modules needed for each specific transaction, reducing overall memory consumption while maintaining independence.
Data Source
AI summary
A method conducted using a mobile device is disclosed. The method includes maintaining a plurality of software modules, wherein each software module of the plurality of software modules is built and executed independently of other software modules. The mobile device receives first interaction initiation data corresponding to a first transaction. In response to receiving the first interaction initiation data, a first subset of the plurality of software modules is selected via an application interface to execute the first transaction. The mobile device receives second interaction initiation data corresponding to a second transaction. In response to receiving the second interaction initiation data, a second subset of the plurality of software modules to execute the second transaction is selected via the application interface. The first subset of the plurality of software modules is different than the second subset of the plurality of software modules.