FOTA Platform Scheduling for IoT Network Congestion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless access networks face inefficiencies when managing large numbers of IoT devices, particularly during bulk firmware updates, as they require significant bandwidth and resources, leading to network congestion and potential service disruptions.
Innovation Solution
A FOTA (Firmware Over-The-Air) platform that solicits service level parameters from customers, generates estimates for OTA updates based on network conditions, and schedules updates to minimize network impact by optimizing resource allocation and usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If bulk firmware updates are performed on a large number of IoT devices, then device functionality is improved, but network congestion and service disruptions occur
Solution Approach 1:
The patent segments the bulk firmware update process into individual device-level updates. Each device receives firmware updates independently through scheduled time slots rather than simultaneously, dividing the large-scale update into manageable portions that prevent network congestion while ensuring all devices eventually receive the update.
Solution Approach 2:
The patent implements periodic action by scheduling firmware updates at specific time intervals and using recurring time slots for different device groups. Updates are performed in periodic cycles rather than continuously or simultaneously, allowing network resources to recover between update waves and preventing sustained network congestion.
2Loss of energy
If firmware updates are scheduled to minimize network impact, then network efficiency is improved, but update completion time increases
Solution Approach 1:
The patent applies dynamics by making the update schedule adaptive rather than static. The system dynamically adjusts time slot allocations based on network conditions, device priorities, and update progress. High-priority devices can be scheduled during optimal network periods, while lower-priority devices are scheduled during off-peak times, optimizing both network efficiency and update completion.
Solution Approach 2:
The patent changes parameters such as time slot duration, scheduling intervals, and priority levels to balance network efficiency and update completion time. By adjusting these parameters dynamically based on network load and device requirements, the system can accelerate updates during high-priority periods while maintaining network efficiency during normal operations.
3Productivity
If network resources are allocated for bulk updates, then update delivery is improved, but other network services are disrupted
Solution Approach 1:
The patent implements partial action by allocating network resources for firmware updates only during scheduled time slots rather than continuously. During non-update periods, full network resources are available for other services. This partial allocation ensures update delivery while preventing excessive resource consumption that would disrupt other network services.
Solution Approach 2:
The patent maintains continuity of useful action by ensuring that network services continue uninterrupted for non-update devices while updates are being delivered to scheduled devices. The system maintains continuous network operation for normal traffic while superimposing periodic update deliveries, ensuring both update productivity and service reliability.
Data Source
AI summary
A computer device receives user parameters for an Over-The-Air (OTA) update campaign. The parameters include a number of user equipment (UE) devices to receive an OTA update, a device type to receive the OTA update, a file size of an OTA update file, and a service level agreement parameter for the OTA update campaign. The computer device generates an estimate for conducting the OTA update campaign based on the user parameters and predicted network conditions, provides the estimate to a user, and receives a request for conducting the OTA update campaign using the user parameters. The request includes identifiers for the UE devices and the OTA update file. The computer device generates, based on the request, a schedule to perform the OTA update on the UE devices in accordance with the service level agreement parameter, and instructs the UE devices to perform the OTA update based on the schedule.