ENGLISH 日本語中文 한국어		CUSTOMER SUPPORT SITE MAP

RESOURCES

White Papers

Product Literature

Research Reports

Standards Leadership

Red Bend Blog

   June 2007
   July 2007
   August 2007
   September 2007
   October 2007
   November 2007
   December 2007
   January 2008
   April 2008
   May 2008
   June 2008
   September 2008
   December 2008
   January 2009
   March 2009
   April 2009
   June 2009
   August 2009
   September 2009
   November 2009
   February 2010
   April 2010

Subscribe to Posts [Atom]

Should SCOTA Supersede FOTA?

By Ilana Bogomolny
Sr. 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

posted by Red Bend @ Sunday, February 7, 2010 - 10:05 PM 0 Comments

When GAAP and MSM Intersect: Business Catches up to Demand for Software Updating

By Lori Sylvia
EVP Marketing,
Red Bend Software

We envision a world where software updates occur every second of the day, improving the mobile user experience while generating additional value for mobile providers. The technology is here today to enable this vision, with OMA DM servers adopted widely by tier-1 and tier-2 operators globally and with about half of handsets already supporting over-the-air software updating.

Now, the business environment is catching up to market demand for software updates, as reflected by some recent changes to GAAP (Generally Accepted Accounting Principles).

In the old days when hardware ruled, consumer electronics manufacturers would sell a device and recognize the sale of that device in that month. Then, software got more sophisticated and more essential to the functionality of a product. If OEMs delivered software updates to the device after it was sold, it meant OEMs had to spread the revenue recognition throughout the device’s lifetime.

Years ago, we heard more than one OEM cite the accounting implications if they were to deliver FOTA updates. FOTA technology was used primarily as an insurance policy to prevent a product recall. But soon the leading OEMs and operators realized the strategic value of delivering continuous software updates. Today, FOTA is much more than fixing defects. It’s used to deliver new features as well as to improve a device’s performance. New advancements in the technology enable updating individual software components over the air (SCOTA) on-demand to support consumers personalizing their device with new applications and services. Software updating has become an important way to keep consumers satisfied with their mobile service and loyal to the experience they get from their handset maker.

Changes to the GAAP rules now allow manufacturers that are delivering software updates to recognize more revenue sooner, even if they are offering those updates free of charge (otherwise bundled in the original price), and even if the contents of the software updates are unspecified at the time the original device is sold.

One of the most vocal advocates of this change has been Apple. The company provides free software updates to iPhone users. Because some of the value of the iPhone is delivered after the product’s initial sale and because the software updates are not sold separately, the former GAAP rules forced Apple to bundle the value of the iPhone with the software updates and spread the revenue over the 24 month AT&T subscription term. Now, Apple and other manufacturers will be able to separate the value of the device from any future software updates. The product’s sales can be recognized in that quarter, while only the value of the device’s future software updates will be deferred.

Software updating is becoming increasingly commonplace in mobile phones and is spreading quickly to other wirelessly connected devices. New business models will emerge that capitalize on this powerful capability to meet the increasing demands of mobile consumers. Mobile devices are no longer static products whose functionality is set when the device ships. Mobile Software Management is the key enabler that allows mobile providers to deliver more value to their consumers throughout the entire mobile user experience.

Labels: accounting, Apple, ATT, FOTA, GAAP, iPhone, Red Bend Software, SCOTA

posted by Red Bend @ Monday, November 30, 2009 - 3:14 PM 0 Comments