IoT Reachability Translation for Power-Saving Message Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Power-constrained IoT devices under 3GPP NB-IoT 5G standards face inefficiencies in power consumption and connectivity due to the disconnect between power saving mode (PSM) and Lightweight Machine-to-Machine (LwM2M) standards, particularly in the use of LwM2M messages which require more power than 3GPP defined messages.
Innovation Solution
A translation application within the core network translates 3GPP sleep and wake messages into LwM2M messages to manage message queuing and release, using 3GPP UE Reachability Notification and LwM2M Reachability Indication messages to efficiently handle IoT device connectivity and message delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If LwM2M messages are used for device management and data communication, then device management capability is improved, but power consumption increases
Solution Approach 1:
The system segments communication into two distinct modes: LwM2M protocol for device management functions (registration, software updates, configuration) and 3GPP-defined messages for simple data delivery and reachability notifications. This segmentation allows the device to use the lower-power 3GPP protocol for routine communications while maintaining LwM2M capability when management functions are needed, thus reducing overall power consumption while preserving device management capability.
2Reliability
If LwM2M Registration Update messages are sent to signal active state, then message delivery is ensured, but power consumption increases due to DTLS/TLS handshake and RESTful CoAP communication
Solution Approach 1:
The patent extracts the heavy DTLS/TLS handshake and RESTful CoAP communication requirements from the simple reachability notification function. Instead, the device sends lightweight 3GPP-defined messages (such as UE reachability notifications) that do not require establishing full LwM2M sessions or performing cryptographic handshakes. The LwM2M protocol is retained only for actual device management operations, separating the low-power reachability signaling from the higher-power management communication.
3Loss of information
If LwM2M server polling is performed, then message queuing status is checked, but power is wasted when no messages are queued
Solution Approach 1:
Instead of continuous or frequent polling of the LwM2M server, the system implements periodic action where the device polls only at intervals aligned with its wake-up schedule from power-saving mode. The device uses 3GPP-defined reachability notifications to signal its active state, and the network infrastructure tracks message queuing status on behalf of the device. This eliminates unnecessary polling transmissions when no messages are queued, reducing power consumption while maintaining awareness of message delivery status.
4Ease of operation
If 3GPP PSM and LwM2M wake-up operations are disconnected, then power saving mode operation is simplified, but message delivery reliability deteriorates
Solution Approach 1:
The patent introduces the 3GPP network infrastructure (specifically the Mobility Management Entity and Serving Gateway) as an intermediary that bridges PSM and LwM2M wake-up operations. When a device wakes from PSM, it sends a 3GPP-defined reachability notification through the network. The network infrastructure then translates this into LwM2M Registration Update messages to the LwM2M server, ensuring queued messages are delivered. This intermediary approach maintains simple power-saving operations while ensuring reliable message delivery through automated translation and coordination.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A 3rd Generation Partnership Project (3GPP) notification message may be received at a translation application at a core network of a wireless carrier network. The 3GPP notification message may include an indication of a loss of connectivity or a communication failure for an Internet-of-Things (IoT) device. The 3GPP notification message is translated by the translation application into a logically equivalent non-3GPP reachability status communication that indicates the IoT device is unreachable. The non-3GPP reachability status communication is sent by the translation application to a server of the wireless carrier network to trigger the server to queue one or more communication messages that are destined for the IoT device in a server queue. Likewise, another 3GPP notification message may be translated into an additional non-3GPP reachability status communication that causes the release of the one or more communication messages to the IoT device.