Red Bend Software: Optimizing the User Experience with Over-the-Air Updates
Download as PPTX, PDF4 likes4,234 views
This document discusses best practices for optimizing the user experience with over-the-air (OTA) updates. It outlines Red Bend's OTA updating service, including planning an OTA system, testing updates, operating update campaigns, and measuring the impact of OTA updates. Red Bend has delivered over 1.75 billion OTA updates across many brands and can help OEMs provide reliable, easy-to-use OTA updating as a cloud-based software as a service.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Red Bend Software: Optimizing the User Experience with Over-the-Air Updates (20)
Ad
Recently uploaded (20)
Red Bend Software: Optimizing the User Experience with Over-the-Air Updates
- 1. Optimizing the User Experience with Over-the-Air (OTA) Updates Yoram Berholtz, Director of Market Adoption Sep 2013
- 2. Introduction Stay Competitive with Updating Software OTA Overview of an OTA Updating System Best Practices in Delivering Software Updates OTA ▪ Planning an OTA Updating System ▪ Testing the OTA Updates ▪ Operating an Update Campaign ▪ Optimizing the User Experience ▪ Measuring the Impact of OTA Updating Red Bend’s OTA Updating Service Summary and Recommendation for OEMs Agenda 2
- 3. Red Bend Software, the Leader in Mobile Software Update 33 1.75 billion devices1,200+ models
- 4. Big Brands Provide OTA Updating 4 Over-the-air update is the best approach to get the highest Adoption
- 5. Why Update Software OTA? 5 Fixing SW defects Time to marketSafer and secure Android raceIP Contamination More functionality
- 6. Consumers expect OS to be up- to-date, no matter the device price, brand or retail channel Commitment to provide OTA updates influences buying decision and builds brand loyalty Selling thin-margin, mass-market devices mandates a service that’s easy to use, highly reliable and requires minimal customer support Consumers Demand Latest OS 6
- 7. All major OEMs and operators are committed to FOTA Hundreds of millions of OTA software updates are performed every year on smartphones and tablets The bandwidth consumed by software updates is increasing constantly Global Adoption and Trends 7*Red Bend data
- 8. When an OEM or an operator wants to start a FOTA service, they should consider a broad range of factors Red Bend based on its vast experience has gathered those factors into a guide for successful FOTA implementation Best Practice in Delivering Software Updates Over the Air 8 Back-end management system Mobile device Connectivity
- 9. 9 FOTA Best Practices White Paper www.redbend.com/en/downloads/white- papers
- 10. Backend Consideration 1. Planning an OTA Updating System 10 Service area Trigger methodTransport technologyDevice dependencies Campaign parametersFirmware Size
- 11. Client Consideration 1. Planning an OTA Updating System 11 Communication 100% reliabilityFirmware GrowthDelta technology Time to marketEase of integration
- 12. 2. Testing the OTA Updates 12 Trigger for a new version OEM creates a new version and the associated delta packages OEM tests the new version with FOTA OEM/Operator performs the FOTA campaign
- 13. Suggested Functionality Verification 2. Testing the OTA Updates 13 Silent Download Ability to manage large FOTA update packages Server notification during a phone call Corrupted update package Postpone/Accept/Reject update Battery removal during the update process Mobile originated a voice call during the update process
- 14. From the user perspective it should be an easy and secured process The time of the update should be minimized Background update Vs. download in the background 3. Optimizing the User Experience 14
- 15. Test and QA are done The IMEI/IMSI in the database Generation of the delta packages Impact estimation Campaign definition Monitoring and feedbacks 4. Operating an Update Campaign 15
- 16. 4. Operating an Update Campaign 16 Live View From Software Management Server
- 17. From a consumer’s point of view, OTA Updates are no longer a special feature of only the highest end devices “OTA Update reputation” of the OEM can impact a consumer’s next buying decision and loyalty From the perspective of the OEM, it is important to control the update process 5. Measuring the Impact of OTA Updates 17 *
- 18. Recommendation for Android OEMs 18 Trusted solutionFast IntegrationWeb-based ScalabilityAll type of SWUpdates OTA
- 19. Premier OTA solution in easy to implement software as a service model (SaaS) Suitable for any Android device including tablets and M2M No hardware investment, no operational expertise, no maintenance fees, unlimited updates Introducing Red Bend’s OTA Updating Service for Android 19 Easy Reliable Economical
- 20. How the Service Works 20 Red Bend Cloud Infrastructure Source Image Target Image Update Generator extracts only the essential differences between versions to create the smallest delta Update Installer applies the delta to the existing firmware to create an updated version Red Bend Software Management Center is used to plan, perform, optimize and monitor the update campaign
- 21. 21 Swift on- device client integration Proven & patented delta- update technology over cellular or Wi-Fi 100% update success in 1.75 billion phones, tablets & wireless devices Easy-to- use web UI to update devices anywhere, anytime Highly available cloud service with expert local support Red Bend Advantages
- 22. The value that consumers see in updating their mobile devices with FOTA is increasing substantially OTA updates are a must-have feature in Android devices FOTA is a competitive edge and increases the customer loyalty Red Bend’s OTA Updating Service for Android is the most suitable solution for OEM Red Bend’s OTA Updating Service for Android provides affordable service with an optimize price point Summary 22 Red Bend Software makes mobile devices and services continuously better in a rapidly changing world.
Editor's Notes
- #14: This slide provides a partial list of suggested test guidelines for evaluating FOTA updating solutions, for example :Silent download – Verifies that the device supports Silent Download capability and not only the download approved by the consumerAbility to manage large FOTA update packages – Verifies that the device is able to process a large FOTA update packageServer notification during a phone call – Verifies the device behavior when it receives an update notification during a voice call.Corrupted update package – Checks the device successfully detects an incorrect or corrupt update package before proceeding with the update process. The device should gracefully manage it and notify both the user and the back-end management system.Postpone/Accept/Reject update – Verifies that the device allows the user to postpone, accept, or ignore the software update. In case of postpone, it should be able to set a reminder when to activate it again. In case of accept, it should start the update process. And in case of ignore, it should cancel the process.Battery removal during the update process – Verifies that the FOTA client can handle battery removal during the update process, simulating a loss of power due to battery drain-age or battery falling out. This test can be performed a few times during the update process, for example every 10-20% of the elapsed update time.Mobile originated a voice call during the update process – Verifies the behavior of the device when a voice call is originated by the user during the update process.
- #15: The Third stage is optimizing the user experience,One of the important factors in a successful device update strategy is to understand how to make this process as easy and quick as possible for the users. In the case of getting a software update by a push method, meaning that the back-end management system is initiating the FOTA update campaign. The user has the flexibility to decide when to perform the update and, if the decision is to apply the update now, it means that if it was planned correctly in only two clicks the device will have a new version. Since some mobile subscribers are hesitant to install new versions, the way to remove this barrier is to ensure that the update message comes from a trusted source, such as the operator or the OEM. In this message, it is important to provide customers with a brief explanation of the content of the update, the benefits to the user for performing the update, and how much time it is expected to take.One of the methods to improve the user experience is by reducing the time needed to perform the updates, because during this time mobile subscribers cannot use their device.The proposed method is updating the device firmware in the background while the device is fully operational.In this approach, all of the software on the device must be available for the user, while in parallel the FOTA client updates the software on flash memory.