Mobile Software Management Advances with Revertible Updating

As mobile operators and handset manufacturers increasingly use mobile software management to independently manage software assets on mobile devices, the technology is evolving with new innovations. One such innovation is called revertible updating, which enables operators and manufacturers to roll back software updates more quickly and efficiently.

 

Revertible updating from Red Bend Software (News - Alert), a market leader in MSM, enables the use of the same update file for both updating the device to the new version and for reverting to the previous version – without the need to download a “downgrade” file from the server. This is critical because it saves both bandwidth and time. Revertible updates enable devices to roll back to the previous version of firmware in the event that a defect is detected in the new firmware version or in case the consumer cancels the update while it is in progress.

 

Revertible updating provides new revenue opportunities for mobile operators by allowing them to offer consumers new features and applications during a specified trial period, with the software automatically removed from the phone if the consumer does not subscribe within the given time period. The feature also improves the mobile user experience by enhancing consumer control of the update process – by independently reverting the phone to a prior firmware version or canceling an update mid way.

 

Below are the main use cases for revertible updates:

 

User-initiated rollback: The consumer may roll back to the previous version as a standalone, independent operation, without having to connect to the service provider’s device management server to retrieve a reverse delta. 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. There could also be some incompatibility with the downloaded applications that the consumer is not willing to accept.

 

Operator-triggered rollback: The operator can 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.

Timer-based rollback for “try before you buy”: The operator may deploy a firmware version that has new value added features or new services to which the consumer may subscribe. If the consumers does not subscribe within a specified time period, the device will automatically roll back to the previous version without the new features.

 

Device-initiated rollback: For embedded devices, where no user is involved in the update, and a diagnostic is run after the update, it may be important to allow the device to automatically roll back to the previous version if the diagnostic test discovers a malfunction in the new version.

 

Because operators are managing multiple handset architectures, they are increasingly seeking more control over software updating to ensure a more enriching and satisfying mobile user experience. Revertible updating represents continued innovation in MSM, allowing the mobile industry and consumers to gain that control.