IoT Notification Routing via Message Queue Prioritization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT architectures lack the ability to distinguish between different types and priorities of notifications from IoT devices, leading to network overburden, increased transmission delays, and congestion, as they route all notifications in a non-discretionary manner without considering network characteristics or customer preferences.
Innovation Solution
The proposed system uses a Service Capability Server (SCS) node to route notifications based on characteristics such as type, priority, and customer preferences, employing message queues and configuration options to selectively store and transmit notifications, allowing for prioritization and efficient distribution within the telecommunications network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If all IoT device notifications are routed in a non-discretionary manner without distinction, then the system maintains simplicity in routing logic, but network congestion and transmission delays increase
Solution Approach 1:
The patent segments notifications into different priority levels (high priority and low priority) and routes them through different message queues. High priority notifications are routed to high priority message queues while low priority notifications are routed to low priority message queues, allowing time-sensitive notifications to be processed and transmitted faster without affecting the overall system complexity
Solution Approach 2:
The Service Capability Server (SCS) acts as an intermediary between IoT devices and the network infrastructure. It introduces message queues as intermediate storage components that buffer notifications before transmission, enabling prioritization and efficient routing decisions without requiring complex routing logic at the device level
2Loss of time
If priority-based routing is implemented for IoT notifications, then transmission delays for important notifications are reduced, but system complexity increases
Solution Approach 1:
The system is segmented into distinct components: high priority message queues, low priority message queues, and corresponding service logic. Each component has a specific function, and the segmentation allows priority-based routing to be implemented through clear, maintainable code structures rather than complex algorithms
Solution Approach 2:
The system uses priority level parameters to determine routing behavior. By changing the priority parameter of a notification, the routing path automatically changes without requiring complex decision logic. This parameter-driven approach simplifies the system architecture while enabling sophisticated routing behavior
3Productivity
If message queues are used to prioritize notifications, then network resource utilization is optimized, but infrastructure complexity increases
Solution Approach 1:
The message queue infrastructure serves multiple functions: it acts as a buffer for notifications, a prioritization mechanism, a routing decision point, and a transmission scheduler. This multi-functionality reduces the need for separate components for each function, thereby optimizing network resource utilization without proportionally increasing infrastructure complexity
Solution Approach 2:
Message queues serve as intermediary components that decouple the notification generation process from the transmission process. This mediation allows the system to optimize network resource utilization by batching, prioritizing, and scheduling transmissions without requiring complex real-time coordination between devices and network infrastructure
Data Source
AI summary
A system for routing Internet-of-Things (IoT) device notifications, or a method therefore are described. For example, a system includes a processor; and computer-readable instructions that, when executed by the processor, cause the system to perform operations including receiving, from a notification customer, preferences for a selection of notifications associated with IoT devices; storing each notification of the notifications in one or more message queues, the message queues being associated with the preferences; and transmitting the selection of the notifications to the notification customer, wherein the selection of notifications comprises a subset of the notifications.