Niranjan M MFollow


Wi-Fi6 has arrived and is being fast adopted than expected and its successor low-latency Wi-Fi7 development is in progress. While these technologies have brought great features, TWT is a real boon for the success of IoT devices by enabling them to increase their battery life. This is based on the mechanism that Access Point (AP) and the IoT device will negotiate for time interval for accessing the medium. Since many IoT devices are battery driven and are meant to operate for days, weeks, months, or years, the low power consumption becomes a crucial aspect to increase the battery life. Hence AP need to keep IoT device information along with TWT details for long period to allocate the radio resource for the device to readily communicate when they wake up. But what if this information is lost on the AP due to critical scenarios such as AP crash, re-joins to another WLC, reboots due to software upgrades etc. The whole purpose of defining TWT mechanism does not serve the purpose due to these situations. The technique presented herein is to cache the IoT device TWT information on a suitable peer node in the network. So that for some reason AP loses this information, it can fetch all the details from this peer node and reconcile the information and start serving the IoT devices as and when they wake-up next time.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.