298
edits
No edit summary |
|||
Line 21: | Line 21: | ||
While OTA provides a great solution to the problem of updating remote devices, there are aspects that developers need to keep in mind when implementing an OTA solution. For example, if a device is being updated remotely and the connection to the network is interrupted mid update, this could leave the device in an unusable state. The more important aspects to consider are the following: | While OTA provides a great solution to the problem of updating remote devices, there are aspects that developers need to keep in mind when implementing an OTA solution. For example, if a device is being updated remotely and the connection to the network is interrupted mid update, this could leave the device in an unusable state. The more important aspects to consider are the following: | ||
<br> | |||
* Reliability: As mentioned, network interruptions during the update process can seriously affect device. Due to this, robust mechanism need to be implemented to give the system a recovery option in case of a failure during the update process. An example of this is dual-partitioning. | * Reliability: As mentioned, network interruptions during the update process can seriously affect device. Due to this, robust mechanism need to be implemented to give the system a recovery option in case of a failure during the update process. An example of this is dual-partitioning. | ||
* Security: OTA must be secure to prevent malicious updates from being applied to the system. It can be combined with other features such as secure boot and TPM to ensure only trusted updates are applied to the system. | * Security: OTA must be secure to prevent malicious updates from being applied to the system. It can be combined with other features such as secure boot and TPM to ensure only trusted updates are applied to the system. |
edits