|
|
|
 |
|
|||
|
|
|
Should SCOTA Supersede FOTA?By Ilana BogomolnySr. Product Manager, Red Bend Software FOTA – Updating of Firmware Over the Air – is a successful mobile technology that is routinely used in millions of mobile phones and devices to introduce new features and provide performance improvements. In comparison, SCOTA – managing Software Components Over the Air – is a relative newcomer. SCOTA, however, has already become a common feature in operators’ requirements and device specifications, with early adopters among some of the leading device manufacturers. Red Bend customers who are implementing, or planning to implement, SCOTA on their mobile devices expect to use it as the only software management process for the entire device software stack. Therefore, the question arises 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. With FOTA, the entire firmware is updated, from the OS kernel and middleware to the top of the built-in application stack. FOTA uses the OMA DM (Open Mobile Alliance Device Management) enabler called FUMO – Firmware Update Management Object. SCOTA enables more granular and flexible management of discrete software components. With SCOTA, one or more piece of software can be changed without requiring an update to the rest of the device. SCOTA’s popularity will increase with the proliferation of app stores as there is now a need to update software components so that consumers can have access to the latest applications, without needing to replace devices. SCOTA uses the OMA DM enabler called SCOMO – Software Component Management Object. The main advantage for a single, unified mechanism on the device for managing software components, as well as for the device firmware, is that it enables dependencies to be defined between software components and the firmware version they require. When such a dependency exists and a new or updated software component requires a firmware update, it becomes possible to implement a single, holistic update operation handling both the software and firmware components by the same mechanisms. The result is a seamless update and a properly working device no matter how the consumer wants to personalize it. Merging FOTA into SCOTA also makes it simple to transition the management of some software components that are embedded in the firmware image and updated via FUMO to be handled as individual entities managed via SCOMO. Operator-branded applications packs are a good example. Of course, for devices where only FOTA is required and where component management of any kind is not planned, there is no advantage in replacing FOTA with SCOTA. For OEMs and operators that have already implemented FOTA (FUMO) and are introducing SCOTA (SCOMO) on their device, it only takes a few steps to make sure that firmware updates are managed through SCOMO. Looking toward the future, the OMA DM SCOMO standard is almost ready to handle firmware updates. There are a few enhancements that need to be made to the SCOMO standard if it is to fully supersede FUMO as the FOTA enabler. The good news is that planning has started for the next version of the SCOMO standard, so certain features will be promoted to enable the FOTA-SCOTA merger. To read more, download the Position Paper>> Labels: FOTA, FUMO, OMA DM, Red Bend Software, SCOMO, SCOTA
Device Management Is Essential for Managing a Range of Wirelessly Connected DevicesBy Yoram BerholtzSenior Product Manager, Red Bend Software The demand for constant connectivity is at an all-time high. Consumers want mobile phones that work wherever they are and whenever they need them–at home, in the office, on the road and across geographies. These demands create a big challenge for mobile operators, which want to manage all the devices in their network in a unified way, regardless of the type of device or software platform. As a result, operators globally are harnessing the Open Mobile Alliance Device Management (OMA DM) standard to meet the demands of this increasingly diverse environment and ensure a consistent and satisfying mobile user experience. Ovum recently reported that 36% of global handset shipments support OMA DM. Device management has become especially crucial to open platforms like Android, Brew Mobile Platform, Symbian and LiMo, as these platforms are feature-rich and geared to support rapidly evolving applications. Typical capabilities of DM include subscriber provisioning, connectivity configuration, firmware updating, diagnostics and monitoring, and software installation—all of which can be performed over the air (OTA). These capabilities result in lower support and maintenance costs for OEMs and operators while providing increased consumer satisfaction with their mobile device and service. With DM, operators and handset manufacturers can activate new subscribers on the network, configure parameters including preferred roaming lists, retrieve data such as billing and inventory as well as conduct “lock and wipe”—remotely shutting down the mobile phone and deleting its memory in case it’s lost or stolen. It’s not just mobile phones that require DM. Recent WiMAX deployments in the United States (Clearwire) and Japan (UQ Communications) adopted OMA DM as the main provisioning and management standard. These service providers are actively equipping their mobile devices, such as WiMAX modems and chipsets, with DM client software. By embracing the OMA DM standards, companies can ensure out-of-the-box interoperability in all the major WiMAX networks. As important as OMA DM is to the current phase of WiMAX deployment, it will be even more important as these networks evolve by being able to deliver more advanced applications and services to WiMAX consumers in the future. The prospects for WiMAX are merely up to the imaginations of the operators and their ability to offer attractive services, regardless of the device. The bandwidth capabilities anticipated in WiMAX will likely bring unprecedented access to video, movies and more, driving additional revenue streams to operators, manufacturers and ISVs as new services and applications become available. Machine-to-machine (M2M) is another wireless segment that has adopted OMA DM for two reasons: 1) the nomadic nature of some M2M segments (e.g., automotive and telematics) force the module to engage with several networks and even roam to other countries; thus, the module must be able to work in a multi-server environment, and (2) the cost of adopting standards-based DM is much less expensive than a proprietary environment because the integration with devices and the certification with networks can be quicker. With the inherent functionality that exists in OMA DM, such as provisioning, managing security and the ability to work globally, operators can benefit from lower cost of ownership by using their already deployed OMA DM infrastructure and utilizing it for M2M. Red Bend Software’s vDirect Mobile™ is the leading independent DM client. vDirect Mobile has been adopted by more than 30 manufacturers of wirelessly connected devices in the mobile, WiMAX and M2M markets, and is interoperable with any DM server supporting OMA DM standards. It also uniquely supports the WiMAX Management Object (MO) for managing mobile WiMAX devices according to specifications from the WiMAX Forum. During the next five years, mobile devices will become more advanced and have many integrated features and connectivity standards. Device management is essential for enabling manufacturers and operators to manage such a diverse installed base in a unified way. Labels: device management, FOTA, M2M, machine to machine, OMA DM, Ovum, Red Bend Software, WiMAX
|
|
|
 |
|
|
|
Copyright ® 2012 Red Bend All Rights Reserved.
Home | Solutions | Customers | Partners | Company | Terms | Contact Us | Site Map |