Mobile Transaction Platform Life Occurrence Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile transaction systems lack an integrated solution to provide a user-centric experience that seamlessly integrates user transactions with their lifestyle, increasing complexity and failing to fully utilize available information for simplifying mobile experiences.
Innovation Solution
A method and system that derive a multi-dimensional context from user transactions to determine life occurrences, generating trigger-events and resolution paths using fuzzy logic, neural networks, and rule engines, which are executed on mobile devices to facilitate user-directed actions and transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mobile transaction systems collect and analyze multiple data sources to provide user-centric experience, then the quality of service and personalization improve, but the system complexity and computational burden increase
Solution Approach 1:
The system segments the complex transaction analysis by separating life occurrence detection from resolution path generation. The life occurrence container on the mobile device handles local context analysis, while the rules engine on the server handles complex resolution logic, distributing computational burden across multiple components.
Solution Approach 2:
The patent introduces a rules engine as an intermediary component that mediates between the mobile transaction platform and the life occurrence detection system. This rules engine processes complex business logic and resolution paths centrally, reducing the computational burden on mobile devices while maintaining personalized service quality.
2Productivity
If the system provides real-time context-aware alerts and automatic resolutions, then user convenience and transaction efficiency improve, but the processing time and computational resources increase
Solution Approach 1:
The system performs preliminary actions by pre-defining resolution paths and rules in the rules engine before transactions occur. When life occurrences are detected, the system can quickly match them to pre-established resolution paths, avoiding real-time complex computations and reducing processing time.
Solution Approach 2:
The life occurrence container on the mobile device performs self-service by locally detecting life occurrences and triggering appropriate resolution paths without requiring constant server communication. This autonomous operation reduces both processing time and computational resource usage while maintaining transaction efficiency.
3Measurement precision
If the system integrates multiple data sources and analytics to determine life occurrences, then the accuracy of event detection improves, but the data processing load and system resources increase
Solution Approach 1:
The patent segments data processing between the mobile device's life occurrence container and the server's rules engine. The container handles local data filtering and basic pattern recognition, while the rules engine processes aggregated data for complex life occurrence determination, distributing the data processing load effectively.
Solution Approach 2:
The system extracts only the essential data elements needed for life occurrence detection from the broader transaction data set. The life occurrence container focuses on extracting specific patterns and contexts relevant to life events, filtering out unnecessary data to reduce processing load while maintaining detection accuracy.
Data Source
AI summary
A method is disclosed herein in accordance with an embodiment of the present invention. The method may include deriving at a mobile transaction platform a multi-dimensional context from one or more user transactions and determining at least one life occurrence based, at least in part, on the multi-dimensional context. The one or more user transactions may be conducted through the mobile transaction platform. The one or more user transactions may be stored on a third-party source. In an aspect, the at least one life occurrence has yet to occur. In another aspect of the invention, the life occurrence has already occurred. The multi-dimensional context may include at least one of user location information and life occurrence location information. The multi-dimensional context may include at least one of a time of life occurrence and a current time.