Moving Forward in Advanced FOTA Features With Revertible Updates

• User-initiated version rollback: The consumer will be able to roll back to the previous version even after completing the update without having to retrieve a reverse delta from the device management (DM) server. This is often done because of user preference. Sometimes the consumer prefers the same features and functions that were on the original handset and does not want to learn the enhancements. Or there may be some incompatibility with the downloaded applications that the customer is not willing to put up with.
• Update cancel: The consumer may choose to cancel the update during a FOTA maintenance update and revert back to the source version. In this instance, perhaps the consumer remembers he needs to make an important phone call, and wants to postpone the FOTA update operation to a later, more convenient time. (By the way, this is another reason to adopt background updates!)
• Operator-triggered rollback: The operator will be able to revert all device updates back to the source version without sending a reverse delta. There are many reasons why operators may need to implement a revertible update. Sometimes this is done due to a defect in the target firmware. Sometimes it is because the new version of the firmware may not be compatible with the current data on the handset. For instance, operators will send a FOTA update but may discover that certain field entries of an email application are incompatible with the new version. Sometimes there are security breaches in the handsets’ operating systems and a rollback is necessary. Because operators are managing multiple handset architectures, they are increasingly seeking more control of the specifications for FOTA updates to ensure a more enriching and satisfying mobile user experience.

Besides handset manufacturers, revertible updates are also valuable for machine-to-machine (M2M) manufacturers and service providers. FOTA is being used to keep the M2M module software up-to-date with changing standards and customer requirements, and to remotely perform software updates in a fast and reliable manner. With M2M modules growing in complexity, FOTA enables manufacturers to perform software improvements over the air, without needing to send a field technician on site. It is also important to mitigate risk if a defect is detected in the new firmware version. With revertible updating, the M2M manufacturer can perform a server-initiated rollback to the previous firmware version on all or select modules. In the case of the defect affecting the cellular stack, the module can initiate a self-update triggered by a watchdog to revert back to the previous version. This revertible update can occur without any contact with the server.

Revertible updates and background updates are two features available from Red Bend since version 5 of vCurrent® Mobile, which is now called vRapid Mobile FOTA. Red Bend is committed to continuing to deliver new advancements in mobile software management (MSM) to deliver an enriching user experience that also enables our customers to reduce support costs and increase service revenues.

Labels: firmware, FOTA, mobile software management, Red Bend

<< Home