298
edits
RidgeRun Platform Security Manual/Platform Security/OTA: Difference between revisions
RidgeRun Platform Security Manual/Platform Security/OTA (view source)
Revision as of 18:32, 28 January 2025
, 28 Januaryno edit summary
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
OTA allows for providers to update several software components of the system that can range from small updates to certain configurations or bigger updates to the root file system or the device firmware. This technique can be specially relevant to embedded systems sin in a lot of cases they might be installed in locations that are hard to access to or if a product has already been shipped, it is not practical to recall all of the devices to apply the updates through a physical connection. | OTA allows for providers to update several software components of the system that can range from small updates to certain configurations or bigger updates to the root file system or the device firmware. This technique can be specially relevant to embedded systems sin in a lot of cases they might be installed in locations that are hard to access to or if a product has already been shipped, it is not practical to recall all of the devices to apply the updates through a physical connection. | ||
<br> | |||
[[File:Ota industry examples.png|650px|thumb|center|Fig 1. Industries that benefit from OTA. Extracted from [https://www.cavliwireless.com/blog/nerdiest-of-things/fota-why-update-firmware-over-the-air.html link]]] | [[File:Ota industry examples.png|650px|thumb|center|Fig 1. Industries that benefit from OTA. Extracted from [https://www.cavliwireless.com/blog/nerdiest-of-things/fota-why-update-firmware-over-the-air.html link]]] | ||
| Line 30: | Line 32: | ||
* Resource Constraints: As embedded systems system often have limited resources, OTA implementations need be lightweight to ensure that updates can be applied without affecting system performance. | * Resource Constraints: As embedded systems system often have limited resources, OTA implementations need be lightweight to ensure that updates can be applied without affecting system performance. | ||
* Version Compatibility: If there are different versions of the hardware each version must get an adequate update. Update management tools can help in handling this. | * Version Compatibility: If there are different versions of the hardware each version must get an adequate update. Update management tools can help in handling this. | ||
<br> | |||
OTA works by posting the update to a remote server to which embedded OTA enabled devices can connect, and the server provides a mechanism for devices to check if updates are available. The connected devices will periodically check for updates, or when the action is triggered by actions such as getting connection to the network, and when an update is available the package will be downloaded by the device. After that, the package is verified to ensure the integrity of the update and if package is determined to be trustable the update is applied. | |||
[[File:Over-the-air-update-process.png|650px|thumb|center|Fig 2. OTA process illustration. Extracted from [https://www.cavliwireless.com/blog/nerdiest-of-things/fota-why-update-firmware-over-the-air.html link]]] | |||
<noinclude> | <noinclude> | ||