Network Triggered Reporting Notification for IoT Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face inefficiencies in signaling and bandwidth usage when delivering network triggered report notifications to IoT devices, as they require the transmission of IP packets that include significant overhead, making it resource-intensive.
Innovation Solution
The solution involves a 3GPP Core Network node (e.g., GGSN) determining the purpose of an IP packet received from an external node to notify an IoT device for network triggered reporting, allowing alternative mechanisms to deliver the notification more efficiently, such as using UDP port information to identify network triggered reports and reducing the need for IP packet delivery, thereby leveraging control plane messages or NAS signaling to convey the necessary information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IP packets are used to deliver network triggered report notifications to IoT devices, then the notification can be transmitted with standard IP protocol support, but the signaling overhead and bandwidth requirements become excessively high
Solution Approach 1:
The patent extracts the essential notification function from the full IP packet structure. Instead of transmitting complete IP packets with their standard headers and protocols, the system uses simplified control plane messages and NAS signaling that carry only the necessary trigger information, thereby removing unnecessary overhead while preserving the core notification functionality.
Solution Approach 2:
The notification delivery mechanism is segmented into different components: control plane messages for trigger indication, NAS signaling for device-specific parameters, and simplified packet structure for actual data transmission. This segmentation allows each component to be optimized independently, reducing overall signaling overhead while maintaining reliability.
2Adaptability or versatility
If IP packets with standard overhead are transmitted to trigger IoT devices, then protocol compatibility is maintained, but bandwidth requirements increase significantly
Solution Approach 1:
The system changes the parameters of packet transmission by switching from standard IP packet mode to a simplified notification mode. The packet structure is modified to include minimal overhead elements while maintaining essential protocol compatibility features, allowing the same infrastructure to support both traditional and optimized notification modes.
Solution Approach 2:
Instead of transmitting the full IP packet with all its overhead (excessive action), the system transmits only the necessary trigger information and essential headers (partial action). This partial transmission approach maintains protocol compatibility for the essential functions while eliminating unnecessary bandwidth consumption.
3Loss of information
If full IP packet delivery is used for network triggered reporting, then complete data can be transmitted, but signaling complexity and processing requirements increase
Solution Approach 1:
The essential notification function is extracted from the complex IP packet processing chain. The system identifies and separates the core trigger indication function from the surrounding IP protocol overhead, allowing simplified processing that maintains data completeness for the actual payload while reducing signaling complexity in the network core.
Solution Approach 2:
Control plane messages and NAS signaling act as intermediaries between the network server and the IP packet delivery mechanism. These intermediary layers carry the trigger information and device-specific parameters, simplifying the overall signaling complexity by providing a structured interface that decouples the simple trigger function from the complex packet delivery infrastructure.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A first Core Network (CN) node (e.g., Gateway GPRS Support Node), a second CN node (e.g., Serving GPRS Support Node) and a wireless access node (e.g., Base Station Subsystem) are described herein that are configured to efficiently deliver a network triggered report notification to a wireless device (e.g., Internet of Things device).