Systems and methods for IoT device lifecycle management
Systems and methods described herein provide for generating behavior profiles for a plurality of end devices associated with an end user; receiving, from the end user, a request for an over-the-air (OTA) update for the plurality of end devices; generating an OTA update campaign plan based on the behavior profiles responsive to the request; providing the OTA update campaign plan to the end user; receiving, from the end user, a modified request for the OTA update; and generating an OTA update campaign schedule responsive to the modified request.
1. A method comprising:
generating, by a network device, behavior profiles for a plurality of end devices associated with an end user, wherein the behavior profiles include power saving mode information for each of the end devices;
receiving, by the network device and from the end user, a request for an over-the-air (OTA) update for the plurality of end devices;
generating, by the network device, an OTA update campaign plan based on the behavior profiles responsive to the request;
determining, by the network device, a difference between a first delivery parameter identified in the request and a second delivery parameter identified in the OTA update campaign plan;
providing, by the network device and based on the difference exceeding a threshold amount, the OTA update campaign plan to the end user;
receiving, by the network device and from the end user, a modified request for the OTA update, wherein the modified request includes a change to the power saving mode information for at least one of the end devices; and
generating, by the network device, an OTA update campaign schedule responsive to the modified request.
2. The method of claim 1 , further comprising:
executing an OTA update file transfer to the plurality of end devices according to the OTA update campaign schedule.
3. The method of claim 2 , wherein the OTA update campaign schedule includes transmission information comprising an antenna beam pattern and a time of delivery for performing the transfer.
4. The method of claim 1 , wherein the OTA update campaign schedule includes a firmware OTA (FOTA) update campaign and wherein the OTA update includes a FOTA update.
5. The method of claim 1 , wherein the plurality of end devices includes a Category M (Cat-M) Internet of things (IoT) device or a narrow band IoT (NB-IoT) device.
6. The method of claim 1 , wherein the behavior profiles include a mobility location pattern for each of the end devices, and wherein the modified request indicates a change to the mobility location pattern associated with one or more of the plurality of end devices.
7. The method of claim 6 , further comprising:
modifying one or more of the behavior profiles, associated with the one or more of the plurality of end devices, based on the modified request.
8. A network device comprising:
a processor configured to:
generate behavior profiles for a plurality of end devices associated with an end user, wherein the behavior profiles include power saving mode information for each of the end devices;
receive, from the end user, a request for an over-the-air (OTA) update for the plurality of end devices;
generate an OTA update campaign plan based on the behavior profiles responsive to the request;
determine a difference between a first delivery parameter identified in the request and a second delivery parameter identified in the OTA update campaign plan;
provide, based on the difference exceeding a threshold amount, the OTA update campaign plan to the end user;
receive, from the end user, a modified request for the OTA update, wherein the modified request includes a change to the power saving mode information for at least one of the end devices; and
generate an OTA update campaign schedule responsive to the modified request.
9. The network device of claim 8 , wherein the processor is further configured to execute an OTA update file transfer to the plurality of end devices according to the OTA update campaign schedule.
10. The network device of claim 9 , wherein the OTA update campaign schedule includes transmission information comprising an antenna beam pattern and a time of delivery for performing the transfer.
11. The network device of claim 8 , wherein the OTA update campaign schedule includes a firmware OTA (FOTA) update campaign and wherein the OTA update includes a FOTA update.
12. The network device of claim 8 , wherein the plurality of end devices includes a Category M (Cat-M) Internet of things (IoT) device or a narrow band IoT (NB-IoT) device.
13. The network device of claim 8 , wherein the behavior profiles include a mobility location pattern for each of the end devices, and wherein the modified request indicates a change to the mobility location pattern associated with one or more of the plurality of end devices.
14. The network device of claim 13 , wherein the processor is further configured to:
modify one or more of the behavior profiles, associated with the one or more of the plurality of end devices, based on the modified request.
15. A non-transitory computer-readable memory device storing instructions executable by a processor of a network device that when executed cause the network device to:
generate behavior profiles for a plurality of end devices associated with an end user, wherein the behavior profiles include power saving mode information for each of the end devices;
receive, from the end user, a request for an over-the-air (OTA) update for the plurality of end devices;
generate an OTA update campaign plan based on the behavior profiles responsive to the request;
determine a difference between a first delivery parameter identified in the request and a second delivery parameter identified in the OTA update campaign plan;
provide, based on the difference exceeding a threshold amount, the OTA update campaign plan to the end user;
receive, from the end user, a modified request for the OTA update, wherein the modified request includes a change to the power saving mode information for at least one of the end devices; and
generate an OTA update campaign schedule responsive to the modified request.
16. The non-transitory computer-readable memory device of claim 15 , wherein the instructions further cause the network device to execute an OTA update file transfer to the plurality of end devices according to the OTA update campaign schedule.
17. The non-transitory computer-readable memory device of claim 15 , wherein the OTA update campaign schedule includes a firmware OTA (FOTA) update campaign and wherein the OTA update includes a FOTA update.
18. The non-transitory computer-readable memory device of claim 15 , wherein the plurality of end devices includes a Category M (Cat-M) Internet of things (IoT) device or a narrow band IoT (NB-IoT) device.
19. The non-transitory computer-readable memory device of claim 15 , wherein the behavior profiles include a mobility location pattern for each of the end devices, and wherein the modified request indicates a change to the mobility location pattern associated with one or more of the plurality of end devices.
20. The non-transitory computer-readable memory device of claim 19 , wherein the instructions further cause the network device to:
modify one or more of the behavior profiles, associated with the one or more of the plurality of end devices, based on the modified request.