ENGLISH
 日本語 中文 한국어
|
|
CUSTOMER SUPPORT
SITE MAP
|
 |
|
|||
|
|
|
|
Will Mobile Operators Face a Capacity Crunch Soon?By Richard KinderVP of Technology and New Business for Europe Red Bend Software Mobile data has finally arrived. After years of hype, the volume of data on mobile networks is reported to have surpassed that of voice traffic. Whilst the majority of this traffic is driven by people with mobile broadband subscriptions, undoubtedly the new breed of data-intensive mobile devices contributes significantly to this rapid growth. This bandwidth consumption is stressing the edge of the network and backhaul, resulting in a potential field day for providers of optical and microwave infrastructure. I could successfully argue that the capacity crunch is already upon us. A frequently cited answer to congestion problems is to off-load mobile data from the mobile core network. Various techniques may be deployed to achieve this, such as WiFi or Femtocell offload. For the best results, both approaches rely on mobile devices being aware of their network context and acting accordingly. Unfortunately, the majority of handset software platforms have yet to acquire the necessary smarts to make best use of these whilst staying within the strict energy budgets imposed by today’s battery technologies. We should not forget that bandwidth usage is only one metric by which to measure mobile network capacity. As has been highlighted in numerous articles, blogs and elsewhere during and since Mobile World Congress 2010, today’s mobile devices also impose a greater signalling burden on the mobile network. Whilst I am yet to receive a clear explanation of exactly what signalling traffic is generated, one can hypothesise that the desire to preserve battery life results in these devices frequently establishing and tearing down PDP contexts, which in turn creates signalling traffic within the operator’s infrastructure. So what can the industry do about this? 4G standards such as LTE and WiMAX eventually will allow for future growth in mobile data usage – the key word being future! Prior to the halcyon days and unlimited bandwidth of 4G, network operators are committing significant amounts of money to enhancing their existing 3G infrastructure. As developers of device software, we too have a role to play, for example:
We cannot rely solely on network operators’ investments in infrastructure to address the capacity crunch. We have a responsibility to use what they provide as efficiently as possible. Services and platforms that can help operators manage their capacity concerns just may be more appealing to them. To misquote Scott McNealy (he of “the-network-is-the-computer fame”), one day datatone will be as important as dialtone. That day is here. Labels: 3G, bandwidth, LTE, mobile, mobile broadband, mobile data, mobile networks, mobile operators, mobile software management, mobile world congress, Red Bend Software, software, standards, WiFi, WiMAX
Nifty Way to Get an Upgrade By Yair Noam, System Architect Red Bend Software ("Nifty Way to Get an Upgrade" is inspired by the original lyrics and music from Paul Simon's "50 Ways to Leave Your Lover") "The software inside your phone is broke," she said to me The answer is FOTA, you’ll be happy, I Guarantee Please, let me help you in your struggle to fix it That must be, the nifty way to get an upgrade She said "the upgrade takes a very short interlude" Software is sent over the air, believe me it’s all true Don’t worry, it won’t brick your phone, I promise you Cause FOTA is, the nifty way to get an upgrade Nifty way to get an upgrade Don’t take the phone back, Jack Don’t get a new plan, Stan Don't need a decoy, Roy Just set yourself free Don’t throw it under the bus, Gus You don't need to wait too much Don’t use your PC, Lee FOTA will set you free Ooo don’t take the phone back, Jack Don’t get a new plan, Stan Don't need a decoy, Roy Just listen to me Don’t throw it under the bus, Gus You don't need to wait too much Don’t use your PC, Lee FOTA will set you free She said it grieves me so to see you in such pain I’ve got something new for you that’ll make you dial again I said I appreciate that and would you please explain About that nifty way She said FOTA will resolve your software plight No need to cable the phone and pray to the light And after a few minutes, I realized she was right That must be, the nifty way to get an upgrade Nifty way to get an upgrade Don’t take the phone back, Jack Don’t get a new plan, Stan Don't need a decoy, Roy Just set yourself free Don’t throw it under the bus, Gus You don't need to wait too much Don’t use your PC, Lee FOTA will set you free Ooo don’t take the phone back, Jack Don’t get a new plan, Stan Don't need a decoy, Roy Just listen to me Don’t throw it under the bus, Gus You don't need to wait too much Don’t use your PC, Lee FOTA will set you free Labels: firmware, FOTA, mobile, OMA, wireless
Reflections on 2008; Anticipation of “the Day After”Yoram SalingerCEO Red Bend Software Reflecting on 2008, unquestionably the state of the world economy had a significant impact on the mobile ecosystem. As such, mobile technology companies, especially handset manufacturers, are changing the way they conduct business. They will be cautious in the first half of 2009, reducing spending, controlling operations, and preparing to react as the economic crisis continues. They will cut the expectations of phone shipments to the market, as they did in 2008. Consumers are also changing their behavior. As a result, the replacement cycle of the phones will change; consumers will not be purchasing new mobile phone models or upgrading as often as they have. In 2008, we saw this occur in Japan when the operators abandoned their subsidies. As a result, there was about a 40 percent decline in new mobile phone purchases. Japanese operators are now faced with severe competition to retain customers and acquire new ones. In 2009, they will need to offer new services to boost their revenues and look overseas to grow their customer base. Despite the slowing pace of replacements, mobile phones are perceived to be essential parts of our lives, no longer a matter of convenience. For some consumers, their mobile phone is their only communication device. For others, it is has become a platform for commerce and socialization. While some OEMs were especially hit hard by the economy, others flourished. Take Apple and its iPhone. Apple has stayed on top despite the financial crisis. They have done this because they cultivated a great experience. And core to this great user experience is the additional applications that Apple offered. During the summer of 2008, Apple announced it had generated $30 million in one month by selling 100 million downloads from its Apple App Store for its iPhone and iPod Touch devices. The proliferation of other mobile application storefronts like Google’s Android Market, Microsoft’s Skymarket, Nokia’s Mosh and the Ovi initiative is allowing consumers to freely customize their phones with new applications and services. The expected result for these companies is noteworthy. For example, the App Store alone is expected to be a $1.2 billion business by the end of 2009, states investment firm Piper Jaffray. Even though Apple evolved as a significant player with an end-to-end proprietary system, it has several obstacles to confront. How will the iPhone reach Nokia’s level of mass market shipments? How will Apple evolve long term in the industry? Apple was not the only disruptive force in the mobile industry in 2008. Open source software changed the economics of the mobile platform in 2008. There was the Google Android launch and the birth of the Symbian Foundation. Because OEMs will build more phones on Android and Symbian, these platforms will become more community driven. But the big question is: Will the manufacturers release the code back to the industry, further driving collaboration and innovation while decreasing costs, or will they leverage it to their advantage? For 2009, both consumers and mobile companies will be careful with their money. But when consumers are ready to make that purchase, they’ll find more compelling options than ever before, specifically increasingly affordable smartphones and new kinds of innovative wireless devices to surf the Internet or read an electronic book. According to ARCchart, by 2013 non-handset devices—everything from data cards to game consoles to ebooks and M2M applications—will account for $93 billion in service revenue generated by operators. This is an exciting area of growth for our industry. Mobile software management will provide device manufacturers, mobile operators and ISVs greater flexibility and control over managing a device’s software throughout its lifecycle. They will be able to create new revenue opportunities and improve customer satisfaction through personalization. Features can be offered for a one-time fee or through a subscription service. Further on the bright side, we will see some recovery in 2009 because at the end of the day, the mobile phone is a lifestyle product. By 2010, there will be 4 billion mobile phone subscribers. Their mobile phones have become sophisticated computing devices—equipped with powerful software, enabling rich user interfaces and advanced features and applications, from streaming video to location-based services to music players. And these rich capabilities only serve to further integrate the mobile phone into our daily lives. Have you ever left the house without your phone, and not gone back to retrieve it? While there is certainly a level of fear, uncertainty and doubt, companies that prepare for “the day after” during this economic downturn will be the visionaries. The first to react will be the thought leaders because they will be able to identify opportunities through partnerships, mergers or acquisitions. These are the companies that will be proactive with feeding the market with new platforms, devices, features and services. And Red Bend Software will be one of those companies. Labels: Apple, device management, Google, mobile, mobile software management, Red Bend
SCOMO Goes Beyond FOTA and Focuses on Managing Individual Software ComponentsBy Elad GanotDirector of Standards and Alliances Red Bend Software Last month I enthusiastically purchased an advanced home entertainment system. I paid a lot of money to enjoy its high sound and picture quality, which were enabled by the cutting-edge technology that’s available in today’s market. It took me about seven years to upgrade my system even though I am a gadget fan and have a technical background. My new system is composed of an HDTV, an advanced receiver (which includes an image enhancer), a media streamer and a DVD player. You might wonder why isn’t Blu-ray part of my system—especially if I want to enjoy high definition movies. The DVD won’t help me so much as it cannot store the capacity required for HD quality. Well, as you may know, there is still doubt on whether Blu-ray will indeed become the next mainstream format for movies, so I’ve decided to wait and see. I can always upgrade separately my existing DVD to a Blu-ray (or whatever other format wins the market). Upgrading my DVD will not force me to upgrade the whole system because it is a stand-alone part with well-defined interfaces to the rest of the system. This makes it a “component.” When the time comes, I will receive an email telling me about this cool new device and for the right price I would click the “buy it now” button, and a delivery package will be on its way to my home. Going from the hardware world to the software world, things look even cooler. Here not only do components are upgradable, but also they even do so almost instantly and quite frequently. I change software components on my computer at least 100 times a year (not just once every few years). I install software, update existing software and uninstall software that I don’t use. Sometimes I just disable software for a while and re-enable it later. Yeah, I like tweaking the software on my computer, and recently I started playing with my mobile phone in the same way. My mobile phone has so many software components available for it that I even abandoned my stand-alone PDA, which had served me loyally for several years. Most users are not even aware of the fact that their mobile phone could actually be used as a personal computing platform. They probably know they can customize it in terms of a fashionable look (with wallpapers, sounds and colorful covers), but will they know how to discover a useful software component? Then be able to download it? Install it? Disable it if needed and re-enable it? Remove it? It was back in 2005 when the mobile industry saw an opportunity to improve the user experience with regard to software management and offered a service of managing the “life cycle” of software components on remote devices. To be able to realize this concept, you have to achieve a mass market, and the industry must agree on some common methods of communication—to allow for every device on every network to connect to the service, regardless of the manufacturer of the equipment (be it a managed client device or a managed server). The good news is that we NOW have a consensus with the Candidate Release of SCOMO 1.0 that was ratified by the OMA on Nov. 17. Now let us componentize the last sentence in a reversed order:
But a Candidate state also means a lot from a business perspective. Interoperability testing period typically happens in parallel to commercial deployments of the enabler. This means that Candidate Release of an enabler is a signal for businesses to start implementing commercial deployments, since the enabler is stable.
Labels: design, device management, DM, firmware, FOTA, mobile, mobile software management, Red Bend, standards
“Pizza or cell phones?” – Observations from CTIA Wireless 2008By Lori SylviaVP, Corporate Marketing Red Bend Software “Pizza or cell phones?” asked the taxi driver, when I stated that my destination was the Las Vegas Convention Center. To her, the fare was the same, but my answer would direct her taxi to one of two shows taking place at the Convention Center last week. Perhaps I should have said “pizza”… “If you're a pizzeria operator looking to improve your business or if your business provides equipment or services to the pizza industry, you've come to the right place. You'll find networking, learning, great deals, and just plain fun at International Pizza Expo® - the World's Largest and Oldest Pizza Tradeshow.” Who doesn’t like “great deals” and “fun?” Compare that with: “The convergence of more than 1,100 exhibiting companies, dozens of industries, and over 40,000 professionals from 125 countries all working toward the common goal of revolutionizing wireless. Whether in broadband convergence, enterprise, advertising, social networking or entertainment, CTIA WIRELESS 2008 is the global marketplace for connecting wireless and YOU.” It’s ironic that the show billed as “The Most Important Global Technology Event of the Year” wasn’t eventful at all. I know I’m not the only blogger to make this observation. The lack of “big news” from the operators, OEMs and Internet players last week was noticeable by all. Still, there were three things that I’ll remember from CTIA last week.
But enough of the shameless plug… back to my observations… once Yahoo! Go 2.0 was downloaded to my phone, I immediately powered it up to check it out. What was the first thing I tried? The map tool of course. I identified my location as Las Vegas, and then I could search for businesses nearby. Like pizza shops, shown in the example on Yahoo!’s promotional graphics. But I already knew where to go for that. Labels: CTIA, Handsets World, mobile, Red Bend, wireless
The “Short Blanket” Effect – Engineering Challenges in Implementing FOTABy Sharon Peleg Founder and CTO Red Bend Software Updating mobile firmware is not a simple task. Some have compared it to updating software on a PC, but there are in fact many engineering challenges that make updating mobile firmware much more difficult. While the generator running on a PC in the office can practically enjoy no resource limitations, the design of the update process on mobile devices must take into account the lack of any auxiliary data, lack of extra storage to be used as temporary buffers, lack of RAM in some cases and a much weaker CPU. Ineffective approaches could easily lead to conflicts between the various resources, and result in the “short blanket” effect – if you pull it from one side, the other side is left uncovered. When evaluating, testing and integrating FOTA on mobile devices, manufacturers and operators should consider the following: · Speed, accuracy and predictability of update generation · No spare flash memory on the device · Fault tolerance · Size of the delta file and update package · Positive user experience · Updating compressed firmware · Type of flash memory In this blog entry, I will address the first three. Speed, Accuracy and Predictability of Update Generation The update algorithm must be fast enough to generate updates at a reasonable speed and should provide sufficient feedback to allow proper understanding of the behavior of the update process on the device. Another equally important requirement is the need for the update generation to be predictable. It is not only sufficient that the generator will produce a small update when few changes are introduced to the source, it must do so consistently. No Spare Flash Memory on the Device The fact that there is no spare flash memory for building two side-by-side alternating versions when updating the new version (as some embedded devices can afford to have) leaves no option but to perform an update in-place. In-place delta-updating is challenged by limited spare flash and RAM resources to hold the new version. Fault Tolerance When updating firmware on mobile devices, it is crucial to assume that the process could be interrupted at any point in time due to a power failure. Power failure during flash re-programming not only can corrupt the written flash sector but also leave the device in a useless state. In addition to having to be both in-place and fault-tolerant, the process must run at maximum speed to minimize downtime. Fault tolerance requires writing additional data when updating in order to maintain the integrity of the persistent data at any point in time. The challenge here is to minimize writing data in order to minimize the number of re-flash operations. Learn more about implementing FOTA in our new white paper, “Principles of Updating Mobile Firmware Over-the-Air”. Labels: FOTA, mobile, software
|
|
|
 |
|
|
|
Copyright ® 2010 Red Bend All Rights Reserved.
Home | Solutions | Customers | Partners | Company | Terms | Contact Us | Site Map |