Top three requirements for OTA software updates for IoT

栏目: IT技术 · 发布时间: 4年前

内容简介:Updating your device software, whether its system or application level, may seem an easy task to do when you first start your IoT project but then you realize what’s involved is more than just overwriting some files with new copies. What if the power goes

Updating your device software, whether its system or application level, may seem an easy task to do when you first start your IoT project but then you realize what’s involved is more than just overwriting some files with new copies. What if the power goes out while the device is updating? What if the connectivity is lost due to poor network quality? What if a third party sends a fake update? What if a portion of your devices in the field require updates?

As more of these ‘what if’ scenarios pile up, you’d soon realize that building an end-to-end software update mechanism for connected embedded systems requires more competency than just overwriting some files with new copies!!

At the very least the software update mechanism must be:

  • Robust
  • Secure
  • Scalable

Robust

One of the most important characteristics of an OTA solution is to ensure the update process is robust. This has many elements to ensure the resiliency of the embedded systems. One of the worst possible scenarios is to have devices remotely deployed and then due to an interruption during an update become unusable and bricked. The resiliency and reliability of the update process should be a central concern given the potential consequences. The key word is atomicity and it requires that in the update process there is no part of the system left behind that is not updated. There must be a single continuous, uninterrupted change to the system software that toggles to the new version of software. There are a few ways to achieve this, one being symmetric image update, orA/B image update.

Secure

When designing and implementing an update mechanism you need to have a reliable method to install security patches, new features and fix bugs. However, the same mechanism may be used by others to install unapproved software packages. The biggest weakness is that of a fake remote update and in order to avoid this you need to authenticate the update server before starting to download the software. You will also need a secure transfer channel, such as HTTPS protocol. There is also the authenticity of updates you need to check for and one way is to use a digital signature in the bootloader. If the kernel image is signed at the manufacturing plant with a digital key, the bootloader can check the key before it loads the kernel and refuses so if the keys do not match. Therefore, as long as the keys are kept private by the manufacturer, it will not be possible to load an authorized kernel image.

Scalable

An update mechanism should have the ability to manage the entire fleet of devices. Many client-only solutions exist. But manual one-by-one updating of devices should be a remnant of the past, even with smaller fleets of just 10 devices. Fleet management requirements can be extensive and have many different requirements depending on the specific scenario and environment. One of the more complicated aspects of an OTA solution is the fleet management capabilities of the management server.

Learn more from a whitepaper on Hidden Costs of Homegrown Updaters .

Download a comprehensive list of OTA requirements checklist here .


以上所述就是小编给大家介绍的《Top three requirements for OTA software updates for IoT》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!

查看所有标签

猜你喜欢:

本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们

超级用户

超级用户

[美] 艾迪•尹 / 王喆,余宁 / 中信出版集团 / 2017-9 / 49.00

《超级用户》是一本可以让你和你的公司实现超常规增长的神奇的书。 多数人只有一个订书机,但有一天,全球著名市场调研公司尼尔森的高管艾迪•尹在和办公用品供应商的合作中发现,订书机的“死忠粉”们,平均每人有8个订书机。令人意想不到的是,相比那些需要更换订书机或遗失订书机的“普通”用户,他们的需求更强,购买第九个订书机的可能性更大。 有些人无肉不欢,有些人爱做手工,有些人痴迷于美国女孩玩偶。这......一起来看看 《超级用户》 这本书的介绍吧!

在线进制转换器
在线进制转换器

各进制数互转换器

URL 编码/解码
URL 编码/解码

URL 编码/解码

html转js在线工具
html转js在线工具

html转js在线工具