IoT Device Awake State Detection via Status Tracking Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for detecting the awake state of IoT devices in wireless access networks are unreliable, as they rely on HSS or SCEF registration status, which may not accurately reflect the device's connectivity status, especially for IoT devices using NB-IoT connections that only utilize the control plane.
Innovation Solution
A device status tracking server is implemented to detect IoT device awake states without requiring specific network connections, maintaining a database of device statuses and notifying registered application servers when an IoT device enters an awake state, allowing for communication across various wireless and wired connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If HSS or SCEF registration status is used to detect IoT device awake states, then the detection method is simple, but the reliability of device status detection deteriorates
Solution Approach 1:
The patent introduces an intermediary component (network device or location management function) that acts as a mediator between the application server and the IoT device. This intermediary receives registration status information from the HSS or SCEF and forwards relevant awake state notifications to the application server, thereby improving detection reliability without significantly increasing system complexity.
Solution Approach 2:
The patent segments the device status detection function into separate modular components: the HSS/SCEF for registration management, the network device or location management function for status tracking, and the application server for service delivery. This segmentation allows each component to specialize in specific tasks, improving overall system reliability while maintaining manageable complexity.
2Use of energy by moving object
If NB-IoT connections are used for IoT devices, then energy consumption is reduced, but the accuracy of awake state detection deteriorates
Solution Approach 1:
The patent implements a feedback mechanism where the network device or location management function continuously monitors registration status changes and sends notifications back to the application server when the IoT device transitions to an awake state. This feedback loop ensures accurate detection of NB-IoT device states without requiring the device to remain continuously connected, thus preserving low energy consumption while improving detection accuracy.
3Loss of energy
If application servers wait for scheduled active periods to communicate with IoT devices, then network resource usage is optimized, but real-time communication capability deteriorates
Solution Approach 1:
The patent enables preliminary action by allowing application servers to register their communication requirements in advance with the network device or location management function. When an IoT device enters an awake state, the system proactively notifies registered application servers, enabling them to initiate communication immediately rather than waiting for scheduled periods. This maintains network resource optimization while enabling real-time communication capability.
Data Source
AI summary
A device may include a memory storing instructions and processor configured to execute the instructions to maintain an Internet of Things (IoT) device database that stores, for an IoT device in the IoT device database, an application server device list that includes one or more application server devices that are to be notified when the IoT device is determined to be in an awake state. The processor may be further configured to receive a first indication from a first application server device that the IoT device is in an awake state; access the IoT device database to identify a second application server device associated with the IoT device; and send a second indication to the second application server device that the IoT device is in the awake state based on the received first indication from the first application server device.