Account Record Event Aggregation and Display Content Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing graphical user interfaces for web browsers and applications often require users to navigate through multiple pages to find relevant information, leading to a poor user experience, excessive resource consumption, and inefficient data access.
Innovation Solution
A system that uses a machine learning model to identify recurring non-subscription-based events in an account record, generates entity similarity scores, and compiles display content indicative of information associated with these events, allowing for more insightful and accessible information without extensive navigation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If users navigate through multiple pages to find relevant information, then they can access comprehensive data, but resource consumption increases and user experience deteriorates
Solution Approach 1:
The patent extracts relevant information about recurring non-subscription-based events from the account record and presents it directly in the event detail view. By extracting and displaying only the necessary information (event count, total amount, and link to full details) rather than requiring users to navigate through multiple pages, the system reduces resource consumption while maintaining information accessibility.
Solution Approach 2:
The system performs preliminary processing of account data to identify and aggregate recurring non-subscription-based events before the user needs to view them. The machine learning model pre-processes the account record to detect patterns and calculate metrics, so when the user views the event details, the information is already prepared and displayed immediately without requiring additional navigation or resource-intensive processing.
2Loss of information
If the system processes all events in detail, then comprehensive information is available, but processing time and resources increase
Solution Approach 1:
The patent segments events into different categories: subscription-based events and non-subscription-based events. Further, it segments non-subscription-based events into recurring and non-recurring events. By segmenting the data this way, the system can apply different processing levels to different segments - detailed processing for recurring events (which are most valuable) and summarized processing for others, thereby reducing overall processing time while maintaining information completeness.
Solution Approach 2:
The system applies local quality by providing detailed information only where needed. For recurring non-subscription-based events, it displays aggregated metrics (event count, total amount) and provides a link to full details, rather than displaying all individual event details uniformly. This localized approach to information presentation reduces processing time and resource consumption while maintaining the ability to access complete information when required.
3Loss of information
If the interface displays all event details, then users have complete information, but the interface complexity and data overload increase
Solution Approach 1:
The patent extracts only the most relevant information about recurring non-subscription-based events and presents it in a simplified format. Instead of displaying all event details, it extracts key metrics (number of events, total amount) and presents them in a clear, organized manner with a link to full details, thereby reducing interface complexity while maintaining information availability.
Solution Approach 2:
Instead of presenting all detailed information at once and requiring users to filter and sort through it, the system inverts the approach by pre-filtering and pre-aggregating the most relevant information. It presents summarized metrics first and only provides detailed information on demand through a link, thereby simplifying the interface while maintaining complete information availability.
Data Source
AI summary
In some implementations, a device may monitor the account record, wherein the account record indicates a set of events associated with an account. The device may aggregate, based on monitoring the account record, one or more events from the set of events that satisfy one or more aggregation criteria, wherein the one or more events are identified based on account data associated with the account record and event data associated with the set of events. The device may generate, based on the event data, one or more groups of events, from the one or more events, indicating events associated with respective event parameters. The device may generate, for a group of events from the one or more groups of events, display content indicative of information associated with events included in the group of events. The device may provide the display content for display.


