NB-IoT Device Management via Non-IP to IP Mode Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current NB-IoT device management protocols, such as OMA LWM2M, do not support device management communication using non-IP standards, leading to increased energy and processing overheads due to the requirement of IP data packet headers, which reduces the operational endurance of resource-constrained NB-IoT devices.
Innovation Solution
Implementing a system that allows NB-IoT devices to switch between non-IP and IP communication modes, with a Service Capability Server (SCS) in the wireless carrier network managing the transition to enable device management functions, thereby minimizing battery consumption and extending device longevity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If IP communication is used for NB-IoT device management, then device management functionality is enabled, but energy consumption and processing overhead increase
Solution Approach 1:
The system dynamically switches between IP and non-IP communication modes based on operational requirements. The NB-IoT device operates in non-IP mode during normal data transmission to conserve energy, and transitions to IP mode only when device management functions are required, thereby resolving the contradiction between management capability and energy consumption.
Solution Approach 2:
The communication protocol parameter is changed from IP-based to non-IP-based for routine operations, and reverted when management functions are needed. This parameter switching allows the system to optimize energy consumption while maintaining the ability to perform device management when necessary.
2Reliability
If IP data packet headers are used, then communication standards are met, but data processing overhead increases
Solution Approach 1:
The communication process is segmented into two distinct modes: non-IP mode for routine data transmission and IP mode for device management. This segmentation allows the system to avoid IP header processing overhead during normal operations while maintaining IP compliance when management functions are required.
Solution Approach 2:
The IP header structure is extracted and removed from the communication stream during normal data transmission. Only the essential management functions require IP headers, allowing the system to eliminate unnecessary processing overhead while maintaining standard compliance for critical operations.
3Use of energy by moving object
If non-IP communication is used, then energy consumption is reduced, but device management communication is not supported
Solution Approach 1:
The system employs periodic switching between communication modes. Non-IP communication is used for the majority of the operational周期 to conserve energy, with periodic transitions to IP mode when device management functions need to be executed, thus balancing energy efficiency with management capability.
Solution Approach 2:
The system uses an intermediary mechanism that allows non-IP communication to serve as the primary mode while providing a gateway to IP mode when management functions are required. This intermediary approach enables the system to benefit from low-energy non-IP communication while maintaining access to IP-based management capabilities.
Data Source
AI summary
A NarrowBand-Internet of Things (NB-IoT) device is transitioned from using non-Internet Protocol (IP) communication to using IP communication for device management. A service capability server (SCS) of a core network may receive data from an NB-IoT device via non-IP communication. The SCS may send a command to the NB-IoT device via the non-IP communication to trigger the NB-IoT device to transition to using IP communication to communicate with the SCS. Subsequently, the SCS may command the NB-IoT device to perform one or more device management functions via the IP communication.