Wirevolution

Mobile Unified Communications

Subscribe!

Archive for the ‘smartphone’ Category

Samsung GT-S8500 is first with 11n, BT 3.0 certifications

Thursday, February 4th, 2010

Engadget reports that the Samsung GT-S8500 is the first phone to support Bluetooth 3.0. A look at the Wi-Fi Alliance website reveals that it was also the first feature phone to gain 802.11n certification.

The certificate is dated December 28th 2009, the same date that the first smartphone was certified for 802.11n - the LG Veri/VS750. The VS750 Wi-Fi appears to be more advanced than the Samsung, since it is certified for short guard interval and WMM Power Save.

While these are the first phones to gain Wi-Fi certification for 802.11n, they may not be the first to market.

First 802.11n handset spotted in the wild - what took so long?

Thursday, December 24th, 2009

The fall 2009 crop of ultimate smartphones looks more penultimate to me, with its lack of 11n. But a handset with 802.11n has come in under the wire for 2009. Not officially, but actually. Slashgear reports a hack that kicks the Wi-Fi chip in the HTC HD2 phone into 11n mode. And the first ultimate smartphone of 2010, the HTC Google Nexus One is also rumored to support 802.11n.

These are the drops before the deluge. Questions to chip suppliers have elicited mild surprise that there are still no Wi-Fi Alliance certifications for handsets with 802.11n. All the flagship chips from all the handset Wi-Fi chipmakers are 802.11n. Broadcom is already shipping volumes of its BCM4329 11n combo chip to Apple for the iTouch (and I would guess the new Apple tablet), though the 3GS still sports the older BCM4325.

Some fear that 802.11n is a relative power hog, and will flatten your battery. For example, a GSMArena report on the HD2 hack says:

There are several good reasons why Wi-Fi 802.11n hasn’t made its way into mobile phones hardware just yet. Increased power consumption is just not worth it if the speed will be limited by other factors such as under-powered CPU or slow-memory…

But is it true that 802.11n increases power consumption at a system level? In some cases it may be: the Slashgear report linked above says: “some users have reported significant increases in battery consumption when the higher-speed wireless is switched on.”

This reality appears to contradict the opinion of one of the most knowledgeable engineers in the Wi-Fi industry, Bill McFarland, CTO at Atheros, who says:

The important metric here is the energy-per-bit transferred, which is the average power consumption divided by the average data rate. This energy can be measured in nanojoules (nJ) per bit transferred, and is the metric to determine how long a battery will last while doing tasks such as VoIP, video transmissions, or file transfers.

For example, Table 1 shows that for 802.11g the data rate is 22 Mbps and the corresponding receive power-consumption average is around 140 mW. While actively receiving, the energy consumed in receiving each bit is about 6.4 nJ. On the transmit side, the energy is about 20.4 nJ per bit.

Looking at these same cases for 802.11n, the data rate has gone up by almost a factor of 10, while power consumption has gone up by only a factor of 5, or in the transmit case, not even a factor of 3.

Thus, the energy efficiency in terms of nJ per bit is greater for 802.11n.

Here is his table that illustrates that point:
Effect of Data Rate on Power Consumption

Source: Wireless Net DesignLine 06/03/2008

The discrepancy between this theoretical superiority of 802.11n’s power efficiency, and the complaints from the field may be explained several ways. For example, the power efficiency may actually be better and the reports wrong. Or there may be some error in the particular implementation of 802.11n in the HD2 - a problem that led HTC to disable it for the initial shipments.

Either way, 2010 will be the year for 802.11n in handsets. I expect all dual-mode handset announcements in the latter part of the year to have 802.11n.

As to why it took so long, I don’t think it did, really. The chips only started shipping this year, and there is a manufacturing lag between chip and phone. I suppose a phone could have started shipping around the same time as the latest iTouch, which was September. But 3 months is not an egregious lag.

Dual-mode technology maturing

Thursday, August 27th, 2009

The Rethink Wireless newsletter is always worth reading. An article in today’s edition says that according to ABI dual mode handset shipments are on track to double from 2008 to 2010, and more than double from 2009-2011 (144 million units to 300 million units).

Rethink’s Matt Lewis cites improved performance and usability as driving forces, plus a change in the attitudes of carriers towards hot-spots. Wireless network operators now often have captive Wi-Fi networks and can use them to offload their cellular networks.

The upshot is a prediction of 300 million dual mode handsets to ship in 2011: 100% of the smartphone market plus high end feature phones.

The attach rate of Wi-Fi will continue to grow. By 2011 the effects of Bluetooth 3.0 will be kicking in, pushing Wi-Fi attachment towards 100% in camera phones and music phones in ensuing years.

Bluetooth 3.0 arrives

Thursday, April 23rd, 2009

The Bluetooth 3.0 specification has finally been ratified.

The main new feature is the Alternate MAC/PHY (AMP), that lets Bluetooth piggyback on Wi-Fi for high speed data transfers. The way it works is that applications write to the traditional Bluetooth Profile APIs, and connections are negotiated using the traditional Bluetooth radio. But then for high-speed data transfers the system switches to a direct peer-to-peer Wi-Fi session. This enables things like bulk syncing of photos from your phone to your PC, or streaming uncompressed CD stereo audio to wireless loudspeakers.

I wrote about Bluetooth AMP before, wondering why it retained a dependency on Bluetooth radio. The answer is that in idle, listening mode waiting for activity, Bluetooth is more power efficient than Wi-Fi, while Wi-Fi is more power efficient for bulk data transfers. This makes Bluetooth’s other next big thing, LE (formerly Wibree), an interesting complement to AMP: for power efficiency Bluetooth devices will reside in two modes, very low power idle mode (LE), and Wi-Fi mode when transferring data.

The Bluetooth 3.0 specification talks about 802.11 rather than 11g or 11n, since 802.11n is not yet ratified, but some of the companies involved will be supporting draft 802.11n anyway.

From an industry point of view there are several interesting aspects to this announcement, among them:

  • Atheros’ ascendence. Atheros, a leader in Wi-Fi, only recently got into the Bluetooth market, and currently only plays in the PC Bluetooth market. It dabbled in headset Bluetooth and got out, and has not yet announced Bluetooth for handsets. So Atheros is a minor player in Bluetooth, eclipsed by CSR and Broadcom, and several others. But Kevin Hayes of Atheros was the technical editor for the 802.11 Protocol Adaptation Layer of the Bluetooth 3.0 specification, and Atheros supplied the video and the demo of AMP at the 3.0 announcement event.
  • Potential movement of Wi-Fi into feature phones. Handset makers slice the market into four main segments: ultra low cost phones, basic phones, feature phones and smart phones. Wi-Fi is now pretty much ubiquitous in new smartphones, but effectively absent in all other types of cell phone. But feature phones have music and cameras which generate exactly the data that Bluetooth 3.0 was designed to sync with PCs, so Bluetooth 3.0 provides a motivation to handset manufacturers to add Wi-Fi to their feature phones. This will vastly boost the Wi-Fi attach rate in 2010 and beyond.
  • Another nail in the coffin of UWB (Ultra Wide-Band). In its original conception, AMP was to use WiMedia’s flavor of UWB. Later Wi-Fi was added to the mix, and now UWB is absent from the spec. UWB has so far failed to meet its performance expectations, and rather than fix it the WiMedia Alliance threw in the towel in March 2009. I suppose it is possible that the few companies still toiling away on fixing UWB will eventually overcome its performance woes, and that it will get adopted into the Bluetooth specification.

AT&T to deploy Voice over Wi-Fi on iPhones

Tuesday, March 24th, 2009

Don’t get too excited by Apple’s announcement of a Voice over IP service on the iPhone 3.0. It strains credulity that AT&T would open up the iPhone to work on third party VoIP networks, so presumably the iPhone’s VoIP service will be locked down to AT&T.

AT&T has a large network of Wi-Fi hotspots where iPhone users can get free Wi-Fi service. The iPhone VoIP announcement indicates that AT&T may be rolling out voice over Wi-Fi service for the iPhone. It will probably be SIP, rather than UMA, the technology that T-Mobile uses for this type of service. It is likely to be based on some flavor of IMS, especially since AT&T has recently been rumored to be spinning up its IMS efforts for its U-verse service, which happens to include VoIP. AT&T is talking about a June launch.

An advantage of the SIP flavor of Voice over Wi-Fi is that unlike UMA it can theoretically negotiate any codec, allowing HD Voice conversations between subscribers when they are both on Wi-Fi; wouldn’t that be great? The reference to the “Voice over IP service” in the announcement is too cryptic to determine what’s involved. It may not even include seamless roaming of a call between the cellular and Wi-Fi networks (VCC).

AT&T has several Wi-Fi smartphones in addition to the iPhone. They are mostly based on Windows Mobile, so they can probably be enabled for this service with a software download. The same goes for Blackberries. Actually, RIM may be ahead of the game, since it already has FMC products in the field with T-Mobile, albeit on UMA rather than SIP, while Windows Mobile phones are generally ill-suited to VoIP.

Sharing Wi-Fi 2 - Atheros turns a cellphone into an access point

Monday, February 9th, 2009

There are several smartphone applications that allow a cell phone to act as a wireless WAN router and Wi-Fi access point, creating a wireless LAN with Internet access. For the (jailbroken) iPhone there’s PDAnet, for Windows Mobile there’s WM Wi-Fi Router and for Symbian there’s Walking HotSpot and JoikuSpot. Now Atheros has proposed to bake this functionality into their low power Wi-Fi chipset.

An idea that is as patent jargon goes “obvious to one skilled in the art,” can sometimes have obvious handicaps to one experienced in the industry. While exposing a broadband wireless data connection through a smartphone’s Wi-Fi radio is massively useful to consumers, it is unlikely to appeal to network service providers, who would prefer you to buy a wireless data card (and an additional service subscription) for your laptop rather than to simply use the wireless data connection that you are already paying for on your phone.

It will be interesting to see where this goes. I will be stunned if Atheros’ implementation appears on any phone subsidized by (or even distributed by) a wireless carrier, until they can figure out a way to charge extra for it. As Tim Wu says in his Wireless Carterfone paper (the Wireless Carterfone concept was promoted by Skype, and rejected by the FCC last April):

carriers are in a position to exercise strong control over the design of mobile equipment. They have used that power to force equipment developers to omit or cripple many consumer-friendly features.

The billing issue may not be that intractable. Closely related models already exist. You can get routers from Cisco and other vendors that have a slot for a wireless WAN card, and the service providers have subscription plans for them. More similarly, this could be viewed as a kind of “tethering” But tethering only lets one PC at a time access the wireless WAN connection - unless that PC happens to support My Wi-Fi.

Update: Marvell has announced a similar capability for its 88W8688 chip.

A not so perfect Storm

Wednesday, December 10th, 2008

The Verizon Storm may be heading for failure in more than one way. A raft of reviewers, led by David Pogue of the New York Times are trashing its usability. This means that even with the marketing might of Verizon behind it it may not fulfill its goal of being a bulwark against the iPhone in the enterprise.

But the Storm was an experiment in another way by Verizon. The other three major American mobile network operators have capitulated to Wi-Fi in smartphones. Against the new conventional wisdom, Verizon decided to launch a new flagship smartphone without Wi-Fi. The Storm looks like a trial balloon to see whether Wi-Fi is optional in modern smartphones. If the Storm is a success, it will demonstrate that it is possible to have credible business smartphones without Wi-Fi. But if it turns out to be a flop because of other factors, it will not be a proof point for Wi-Fi either way.

But Wi-Fi is a closed issue by now for all the network operators, perhaps even including Verizon. Phones have lead times of the order of a year or so, and controversies active back then may now be resolved. Verizon covered its bets by launching three other smartphones around the same time as the Storm, all with Wi-Fi (HTC Touch Pro, Samsung Omnia, Samsung Saga).

Before its launch, AT&T hoped that the iPhone would stimulate use of the cellular data network. It succeeded in this, so far beyond AT&T’s hopes that it revealed a potential problem with the concept of 3G (and 4G) data. The network slows to a crawl if enough subscribers use data intensively in small areas like airports and conferences. Mobile network operators used to fear that if phones had Wi-Fi subscribers would use it instead of the cellular data network, causing a revenue leak. AT&T solved that problem with the iPhone by making a subscription to the data service obligatory. T-Mobile followed suit with the Google phone. So no revenue leak. With the data subscription in hand, Wi-Fi is a good thing for the network operators because it offloads the 3G network. In residences and businesses all the data that goes through Wi-Fi is a reduction in the potential load on the network. In other words, a savings in infrastructure investment, which translates to profit. This may be some of the thinking behind AT&T’s recent acquisition of Wayport. The bandwidth acquired with Wayport offloads the AT&T network relatively cheaply. AT&T’s enthusiasm for Wi-Fi is such that it is selling some new Wi-Fi phones without requiring a data subscription.

The enterprise market is one that mobile network operators have long neglected. It is small relative to the consumer market, and harder to fit into a one-size-fits-all model. Even so, in these times of scraping for revenue in every corner, and with the steady rise of the Blackberry, the network operators are taking a serious look at the enterprise market.

The device manufacturers are way ahead of the network operators on this issue: the iPhone now comes with a lot of enterprise readiness Kool-Aid; Windows Mobile makes manageability representations, as does Nokia with its Eseries handsets. RIM, the current king of the enterprise smartphone vendors also pitches its IT-friendliness.

Wi-Fi in smartphones has benefits and drawbacks for enterprises. One benefit is that you have another smart device on the corporate LAN to enhance productivity. A drawback is that you have another smart device on the corporate LAN ripe for viruses and other security breaches. But that issue is mitigated to some extent if smartphones don’t have Wi-Fi. So it’s arguable that the Storm may be more enterprise-friendly as a result of its lack of Wi-Fi. Again, if the Storm becomes a hit in enterprises that argument will turn out to hold water. If the Storm is a flop for other reasons, we still won’t know, and it will have failed as a trial balloon for Wi-Fi-less enterprise smartphones.

DiVitas Test Drive

Tuesday, October 28th, 2008

Divitas loaned me a Nokia E71 to try out with their mobile unified communications solution hosted by Sawtel. It’s a very nice phone - looks good, feels good in the hand. It’s also the best-sounding cell phone experience I have ever had, and that’s thanks to DiVitas. All cellular service providers use technology that sacrifices sound quality for increased carrying capacity. By squeezing down the bandwidth used by a call they can fit more calls into each cell, and get by with fewer cell towers, saving money. The standard codec around most of the world is GSM, and it’s the reason that cell calls can never sound as good as landline calls.

But DiVitas uses a Wi-Fi connection for your calls, and they have chosen to use the standard land-line codec, G.711. The effect is startling - a little disorienting even; we are so used to the horrible GSM codec that when a cell phone sounds as good as a land-line the subjective illusion is that it sounds much better.

This is one of the reasons that the type of voice over Wi-Fi solution offered by DiVitas is way better than the one offered by the telco industry, called UMA. UMA uses the GSM codec even over Wi-Fi connections.

But DiVitas didn’t stop with the sound quality. DiVitas has done an excellent job in several other technical areas. The fundamental technology of fixed mobile convergence is the ability to hand off a call in progress from the cellular network to the Wi-Fi network and vice versa.

This is very challenging, and it is an area where DiVitas claims to lead. So the first thing I did after turning on the phone was to make a call to check it out. I didn’t need to look at the on-screen indicator to know that the call was running over my office Wi-Fi network. The sound quality (did I mention this before?) was superb. So I walked out of range of the WLAN and sure enough the call handed over to the cellular network without dropping. There was a brief interlude of music and the call continued. Going back into the WLAN coverage area the handoff was completely seamless, perceptible only by the improvement in call quality as it moved from the cellular to the WLAN network.

Superior sound quality and seamless handover, while impressive to an engineer who knows what’s entailed, are not really sexy to regular users - it’s just a phone behaving like you would expect. DiVitas takes it to the next level by overcoming another technical challenge, delivering a polished, well thought-through, feature rich and well integrated user interface on the phone.

Actually, the DiVitas software client for the handset overcomes two challenges. The technical challenge of integration with the phone’s native software environment, and the design challenges of usability and usefulness. User interfaces are a matter of personal taste; the best are those that don’t get in the way of doing what you want. I disappointed the people at DiVitas by discarding their carefully written instructions and forging ahead by trial and error. Considering the potential consequences of this behavior I got away lightly. Everything worked the way I expected it to, and there were some nice touches, including Skype-like presence icons by the names in the directory.
While we’re on the topic of the directory, one thing that jumps out is the four digit phone numbers.

This is an indicator of yet another set of technical challenges that DiVitas has overcome to deliver their solution, namely integration with the corporate PBX, and presentation of the PBX features through the cell-phone user interface. DiVitas users will actually get a superior experience of the PBX through their cell phone compared to their desk phone. This is because the DiVitas software has a computer industry heritage rather than a telco heritage; it takes advantage of the nice big color screen with features like the presence icons and voice mail presented in an on-screen list like on the iPhone.

So the big news here is that a product has finally caught up with the hype around enterprise Mobile Unified Communications. All my criticisms (DiVitas got an earful) are nitpicking. For me the system worked as advertised, and that’s saying a lot.