IoT Event Management with Criticality-Based Notification Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT systems lack an effective method to manage and notify users about missed events in a routine schedule, often providing notifications at inappropriate times, which can be annoying or lead to security issues if critical events are not addressed promptly.
Innovation Solution
A method and device that identify critical events in a schedule, monitor their execution, and provide notifications before or after the execution of critical events, allowing for timely reminders and potential re-execution of missed activities, while modifying the schedule based on frequency and order of events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If notifications are provided immediately when an event is missed, then user awareness is improved, but user annoyance increases due to inappropriate timing
Solution Approach 1:
The system performs preliminary identification of critical events in the schedule and prepares notification strategies in advance. By analyzing the schedule structure and event criticality before missed events occur, the system can determine appropriate notification timing windows that balance user awareness with annoyance reduction.
Solution Approach 2:
The notification timing is made dynamic based on the criticality level of missed events and the current schedule state. The system adjusts notification strategies in real-time based on whether events are critical or non-critical, and whether subsequent events have been executed, creating an adaptive notification system that reduces annoyance while maintaining reliability.
2Ease of operation
If notifications are delayed until after critical events are executed, then user annoyance is reduced, but security risks increase due to delayed awareness
Solution Approach 1:
The system applies different notification strategies to different events based on their criticality. Critical events trigger immediate or early notifications to ensure security awareness, while non-critical events can have delayed notifications that reduce user annoyance. This localized differentiation resolves the contradiction between timely awareness and annoyance reduction.
Solution Approach 2:
The system preliminarily identifies which events are critical and prepares appropriate notification timing for each event type. By pre-classifying events based on their security implications, the system can ensure that critical events receive timely notifications while non-critical events follow delayed notification strategies.
3Measurement precision
If the system monitors all events to determine criticality, then notification accuracy is improved, but system complexity increases
Solution Approach 1:
The system segments the schedule into parts based on critical event identification. By dividing the schedule into segments separated by critical events, the system can monitor and manage events more efficiently without requiring complex analysis of all events simultaneously. This segmentation reduces system complexity while maintaining notification accuracy.
Solution Approach 2:
The system uses feedback from event execution monitoring to refine its criticality determination. By observing which events are actually executed and which are missed, the system can adjust its criticality classification and notification strategies, improving accuracy over time without requiring overly complex initial analysis.
4Productivity
If the schedule is modified based on event frequency and order, then notification timing optimization is improved, but schedule management complexity increases
Solution Approach 1:
The schedule management becomes dynamic through continuous monitoring of event frequency and execution order. The system automatically adjusts notification strategies based on observed patterns, optimizing timing without requiring manual schedule management. This dynamic adaptation improves productivity while keeping management complexity manageable through automation.
Data Source
Figure 1~2
Figure 3A~3B
Figure 4A~4B
AI summary
A method for managing a missed event in an Internet of Things (IoT) environment and an apparatus therefor are provided. The method includes determining a sequence of events executed by a user, identifying a first event among the sequence of events as a critical event, detecting a missed event among the sequence of events, determining a significance weight of the missed event and performing the missed event based on at least one of the significance weight of the missed event or the critical event.