This white paper is for manufacturers of mobile phones, tablets, automotive vehicles, consumer electronics and other wirelessly connected devices (in the paper, described as “mobile devices”) that are interested in using their hardware products as platforms from which to deliver value-added services.
The paper describes how Mobile Software Management (MSM) can be used to achieve this strategy. With MSM, manufacturers can leverage a range of over-the-air technologies—firmware updating, application management, device analytics, policy management and Type-1 virtualization—both as differentiating features that can strengthen their offerings and as services to their customers. Readers will learn from case studies of how to successfully use MSM to deliver new integrated services.
This whitepaper is intended for Android device manufacturers interested in offering an OTA software updating service to continually delight customers with the latest features and performance improvements. It describes the importance of delivering software updates and explains how it has become an integral part of a manufacturer’s go-to-market strategy. The paper discusses the technology, expertise and service infrastructure needed to ensure reliable and efficient software updates to devices used both by consumers and enterprises. By reading this white paper, Android OEMs will learn how to easily offer an OTA software updating service and gain a competitive edge in the crowded consumer electronics market.
FOTA – Firmware Over the Air, the means of updating the software of mobile devices over the mobile network, is a successful mobile technology that is being routinely used on millions of cellular phones and devices to introduce new features and fix defects. SCOTA, updating Software Components Over the Air, is a relative newcomer, but has already become a common feature in operators’ requirements and device specifications, with early adopters among some of the leading device manufacturers. This article focuses on the management of FOTA and SCOTA according to the OMA DM standard, defined by the Open Mobile Alliance (OMA), the organization responsible for mobile Device Management standards being deployed worldwide by major network operators. This article explores whether devices that support SCOTA should still use FOTA to update firmware, or whether SCOTA can and should absorb FOTA functionality, making SCOTA the sole software-managing mechanism on these devices.
Today's consumers are demanding the latest software version, pushing OEMs and operators to improve their FOTA update strategies, especially considering the growing problem of Android fragmentation. Planning a winning FOTA system starts first by analyzing customers' requirements, proper dimensioning, deciding which technology to use, and finalizing the business logic that will determine the user experience. In this white paper, Red Bend Software describes five steps for successful FOTA implementation, leveraging Red Bend’s vast experience in providing the FOTA technology used in nearly 1,500 different device models over the last 10 years. To create this white paper, Red Bend has analyzed the best practice FOTA processes of its leading customers. By reading this paper, OEMs and operators in any market -- Mobile to M2M to Automotive -- can understand how to deliver continuously better mobile devices and services using FOTA.
Tens of millions of FOTA updates are performed each year in all geographies, not just to fix software defects, but to deliver valuable new features and applications to the consumer. The frequency of updates continues to rise sharply, with OS providers like Apple, Android and Microsoft publishing at least two major releases every year and as many minor updates each month. With software updates becoming more frequent, not just on mobile phones but on all the connected devices around us, it’s time to consider a FOTA update process that does not interrupt a consumer’s use of the device. The solution is to perform FOTA updates in the background.
This white paper presents how Mobile Software Management revenue and business models can evolve, and highlights the business scenarios where participants in the mobile value chain can benefit from MSM.The paper introduces Mobile Software Management and describes the main market needs and use cases as well as discusses how MSM relates to similar technologies. A simple business case is then demonstrated in order to quantify the core benefits of MSM. Finally, potential MSM service models towards consumers and value chain scenarios for realistic MSM deployment are described.
A new firmware update technology is being evolved to enable manufacturers and operators to manage individual software components over-the-air (SCOTA). SCOTA allows deployment of discrete software components, either updated or new, to the embedded firmware of a mobile device. A modification or feature change in a software component requires only a single updated version of the component to be deployed to all relevant handset configurations in the field. A completely new feature can be deployed and installed to applicable handsets, and previously installed features can be removed to make space for other features. With SCOTA, operators can maintain the reliability and security of tightly integrated firmware, but they gain more flexibility to efficiently update devices post-sale.