IoT Subscription Proxy for Mismatched Notification Intervals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IoT systems face challenges in efficiently managing power consumption and ensuring timely event notifications between devices with mismatched notification intervals, leading to failed subscriptions.
Innovation Solution
Implementing a method that determines and adjusts time intervals for event notifications using an agent to bridge the gap between the requester's expected interval and the target's capable interval, ensuring notifications are delivered according to the requester's schedule.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If the target device operates in a longer notification interval to save power, then power consumption is reduced, but the requester cannot receive timely notifications
Solution Approach 1:
The patent introduces a server as an intermediary component that receives event notifications from the target device at its optimal long interval and forwards them to the requester at the requester's required short interval. This mediator resolves the time interval mismatch without requiring either the target or requester to compromise their optimal operating parameters, thus maintaining both power efficiency and notification timeliness.
Solution Approach 2:
The notification delivery process is segmented into two distinct stages: first, the target device sends notifications to the server at extended intervals optimized for power saving; second, the server independently manages forwarding these notifications to the requester at shorter intervals. This segmentation allows each component to operate at its optimal interval without direct coupling constraints.
2Reliability
If the requester requires frequent notifications, then notification timeliness is improved, but power consumption increases
Solution Approach 1:
The server acts as a mediator that absorbs the burden of frequent notification forwarding. The requester can maintain its short interval requirement without directly interacting with the target device, thus avoiding the power consumption penalty that would result from the requester actively polling or maintaining continuous connectivity.
Solution Approach 2:
The server autonomously manages the notification forwarding process, determining when to poll the target and when to forward to the requester based on各自 optimal intervals. This self-service mechanism eliminates the need for the requester to actively manage the notification retrieval process, reducing its power consumption.
3Device complexity
If direct subscription is used between requester and target, then system complexity is reduced, but subscription fails when time intervals mismatch
Solution Approach 1:
The server serves as a subscription intermediary that decouples the requester and target device. Instead of direct subscription that fails due to interval mismatch, the requester subscribes to the server and the server independently subscribes to the target, creating two independent successful subscriptions that work around the timing conflict.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
The present disclosure relates to a subscription notification method in an Internet of Things system, a proxy in an Internet of Things system, an electronic device, and a non-static computer readable medium. An Internet of Things system comprises a requester, a target party, and a proxy. The method comprises: determining a first time interval and a second time interval, wherein the first time interval is a time interval at which the requester expects to receive event notifications from the target party, and the second time intervals is a time interval at which the target party can send the event notifications (S301); determining whether the second time interval exceeds the first time interval (S302); and in response to determining that the second time interval exceeds the first time interval, the proxy receiving the event notifications from the target party at the second time interval and notifying the requester at the first time interval (S303).