Posted on

T-Mobile UMA service details

I called the T-Mobile customer service line and received a clarification about the HotSpot@Home service. The charge for this service is just for unlimited calling at home and at T-Mobile hotspots. If you don’t mind using your regular service minutes in these situations, there is no need to subscribe to the @Home service – you can still use the Wi-Fi connection for better reception. So since I never seem to use more than half my minutes, I cancelled the @Home service. The phone still uses Wi-Fi when it can, so the customer service agent appears to be correct.

This makes me a lot happier with T-Mobile. When the Wi-Fi is being used to offload their network and provide better coverage, they don’t charge for it. This is as it should be. If the offload/coverage effect turns out to be a significant benefit for T-Mobile, and as the price of Wi-Fi in handsets comes down, it is conceivable that T-Mobile will find it worthwhile to add Wi-Fi to all their phones.

I remain curious about why my Nokia 6086 can’t use the Wi-Fi for web browsing.

Posted on

How does 802.11n get to 600Mbps?

802.11n incorporates all earlier amendments to 802.11, including the MAC enhancements in 802.11e for QoS and power savings.

The design goal of the 802.11n amendment is “HT” for High Throughput. The throughput it claims is high indeed: up to 600 Mbps in raw bit-rate. Let’s start with the maximum throughput of 802.11g (54 Mbps), and see what techniques 802.11n applies to boost it to 600 Mbps:

1. More subcarriers: 802.11g has 48 OFDM data subcarriers. 802.11n increases this number to 52, thereby boosting throughput from 54Mbps to 58.5 Mbps.

2. FEC: 802.11g has a maximum FEC (Forward Error Correction) coding rate of 3/4. 802.11n squeezes some redundancy out of this with a 5/6 coding rate, boosting the link rate from 58.5 Mbps to 65 Mbps.

3. Guard Interval: 802.11a has Guard Interval between transmissions of 800ns. 802.11n has an option to reduce this to 400ns, which boosts the throughput from 65 Mbps to 72.2 Mbps.

4. MIMO: thanks to the magical effect of spatial multiplexing, provided there are sufficient multi-path reflections, the throughput of a system goes up linearly with each extra antenna at both ends. Two antennas at each end double the throughput, three antennas at each end triple it, and four quadruple it. The maximum number of antennas in the receive and transmit arrays specified by 802.11n is four. This allows four simultaneous 72.2 Mbps streams, yielding a total throughput of 288.9 Mbps.

5. 40 MHz channels: all previous versions of 802.11 have a channel bandwidth of 20MHz. 802.11n has an optional mode (controversial and not usable in many circumstances) where the channel bandwidth is 40 MHz. While the channel bandwidth is doubled, the number of data subcarriers is slightly more than doubled, going from 52 to 108. This yields a total channel throughput of 150 Mbps. So again combining four channels with MIMO, we get 600 Mbps.

Lower MAC overhead
But raw throughput is not a very informative number.

The 11a/g link rate is 54 Mbps, but the higher layer throughput is only 26 Mbps; the MAC overhead is over 50%! In 11n when the link rate is 65 Mbps, the higher layer throughput is about 50 Mbps; the MAC overhead is down to 25%.

Bear mind that these numbers are the absolute top speed you can get out of the system. 802.11n has numerous modulation schemes to fall back to when the conditions are less than perfect, which is most of the time.

But to minimize these fall-backs, 11n contains additional improvements to make the effective throughput as high as possible under all circumstances. These improvements are described in the following paragraphs.

Fast MCS feedback – rate selection.
Existing equipment finds it hard to track rapid changes in the channel. Say you walk through the shadow of a pole in the building. The rate may go from 50 to 6 to 50 mbps in one step. It’s hard for conventional systems to track this, because they adapt based on transmit errors. With delay sensitive data like voice you have to be very conservative, so adapting up is much slower than down. 11n adds explicit per-packet feedback, recommending the transmission speed for the next packet. This is called Fast MCS (Modulation and Coding Scheme) Feedback.

LDPC (Low Density Partity Check) coding
LDPC is a super duper Forward Error Correction mechanism. Although it is almost 50 years old, it is the most effective error correcting code developed to date; it nears the theoretical limit of efficiency. It was little used until recently because of its high compute requirement. An interesting by-product of its antiquity is that it is relatively free of patent issues.

Transmit beam-forming
The term beam-forming conjures up images of a laser-like beam of radio waves pointing exactly at the client device, but it doesn’t really work like that. If you look at a fine-resolution map of signal intensity in a room covered by a Wi-Fi access point, it looks like the surface of a pond disturbed by a gust of wind – it is a patchwork of bumps and dips in signal intensity, some as small as a few cubic inches in volume. Transmit beam-forming adjusts the phase and transmit power at the various antennas to move one of the maxima of signal intensity to where the client device is.

STBC
In a phone the chances are that there will only be one Wi-Fi antenna, so there will be only one spatial channel. Even so, the MIMO technique of STBC (Space-Time Block Coding) enables the handset to take advantage of the multiple antennas on the Access Point to improve range, both rate-at-range and limiting range.

Incidentally, to receive 802.11n certification by the Wi-Fi Alliance, all devices must have two or more antennas except handsets which can optionally have a single antenna. Several considerations went into allowing this concession to handsets, mainly size and power constraints. STBC is particularly useful to handsets. It yields the robustness of MIMO without a second radio, which saves all the power the second radio would burn. This power saving is compounded with another: because of the greater rate-at-range the radio is on for less time while transmitting a given quantity of data. STBC is optional in 802.11n, though it should always be implemented for systems that support 802.11n handsets.

Hardware assistance
Many of these features impose a considerable compute load. LDPC and STBC fall into this category. This is an issue for handsets, since computation costs battery life. Fortunately these features are amenable to hardware implementation. With dedicated hardware the computation happens rapidly and with little cost in power.

Posted on

CSR pitches better sound quality, battery life in Bluetooth headsets

CSR announced their Bluecore 6 chip today. It will ship in production volumes in January 2008. CSR claims a more robust connection – with increased transmit power and receive sensitivity. CSR also claims a breakthrough in sound quality, achieved by going from a Continuous Variable Slope Delta (CVSD) codec to Adaptive Differential Pulse Code Modulation (ADPCM). This enables packet retransmission and a halving of transmission bandwidth. The reduced bandwidth requirement results in a reduction in power consumption, and the ADPCM codec yields a MOS of 4.14 compared with a maximum of 2.41 for CVSD.

This is a welcome change, but doesn’t really go far enough. What’s needed is a wideband codec like AMR-WB to yield better-than-toll quality sound. While this would be redundant in a regular cell phone – ADPCM is more than adequate to carry a signal that has been encoded in GSM – it would make a huge difference in dual-mode phones carrying Voice over Wi-Fi.

Posted on

Muni Wi-Fi on the ropes?

Wired has a story about the struggles of several municipal Wi-Fi deployments. Turns out that good coverage requires double the number of access points than planned, and that consumer subscriptons were an order of magnitude less than anticipated (1-2% instead of 10-25%).

The article holds out a few rays of hope: 802.11s for mesh deployments in residential areas, concentrate on high-traffic areas rather than trying to replace fixed broadband access, get the cities to become “anchor tenants.”

On the other hand, there still seem to be plenty of lower profile metro Wi-Fi deployments that are doing OK.

Posted on

Bluetooth headset for the iPhone

I went to an Apple store today, to buy an iPhone Bluetooth headset. I asked the clerk how the iPhone is selling, and he said “Steady, to both business users and consumers.” I came back to my desk to find a press release from iSuppli saying that the iPhone was the best selling smartphone in the US in July, with 1.8% of the overall cell phone market.

The iPhone Bluetooth headset comes in a box about the same size as the iPhone’s box. As usual with Apple, the box and all its contents are seductively designed, a pleasure to unpack and examine. The headset itself is tiny, but it comes with two USB connectors, one a nice docking station for the phone plus the headset, and one a traveling cable for both the phone and the headset.

One benefit of these dual connectors is pairing. To pair the devices simply plug them both in at the same time. That’s all. It worked for me. Another nice touch is the charging progress indicator that appears on the screen of the iPhone. It shows the battery status of both the headset and the phone.

The headset comes pre-charged; it was only plugged in to the dock for a couple of minutes before the light went green. Even plugging it in brought a little lift of the spirit, as I discovered that it uses the same magnetic engagement technology as the MacBook power connector.

What a disappointment when I made a call, though! There was a lot of static and a sound like running water at both ends of the connection. This is par for the course in my experience of Bluetooth headsets (there are half a dozen discards in my desk drawer), but still not acceptable. The headset was about 3 feet from the phone. There are several Wi-Fi transmitters in my office, but Bluetooth is supposed to be immune from this kind of interference due to its adaptive frequency hopping, which is supposed to learn which frequencies are conflicting and avoid them. ** Update: on subsequent calls I didn’t experience the same degree of impairment, so this initial experience may have been anomalous. The call quality on most calls appears to be acceptable. Even better, this is the first in-ear headset I have used that is so comfortable that I forget I am wearing it. This is a breakthrough. But now that it’s in my ear all the time I am beginning to be concerned about battery life. **

About a billion cell phones were sold in 2006, of which about 50% had Bluetooth capability. About 100 million bluetooth headsets were sold in 2006. Although 100 million of anything is a lot, it is only a 10% attach rate for headsets to phones. I believe the attach rate would be higher if the comfort, sound quality and ease of use were improved.

A strange omission in the iPhone Bluetooth headset is the apparent lack of support for playing iPod content through it. While it may make sense to think that music listeners must have stereo, not every MP3 is music. I play a lot of saved NPR clips through my iPhone, and the headset wires are constantly getting tangled up. Balanced against this inconvenience I would be quite satisfied with monaural playback of this content through a Bluetooth headset. It seems high-handed to deny this option to those who might find it useful. Perhaps this design decision has something to do with battery life.

Posted on

Femtocells, FMC, Wi-Fi

There’s an interesting article on femtocells in EETimes. It mentions the Femto Forum. It is a thoughtful look at the prospects for femtocells, a welcome counterbalance to the hype. The most telling quote is from the CTO of Ubiquisys:

We—that is, the femtocell ecosystem—probably have a two-year window to make our mark, ensure we come up with standard interfaces, and, above all, avoid fragmentation.

The two year comment is about beating Wi-Fi dual mode phones to the punch. But currently the primary driver for Wi-Fi in cell phones is feature inflation in high-end handsets, not FMC. In other words, there are really two dynamics driving Wi-Fi into handsets, FMC is the minor one and feature inflation is the major one; femtocells don’t affect the latter.

So if femtocells overcome their numerous challenges, FMC services for consumers will come mainly through femtocells. Femtocells will not impact Wi-Fi attach rate much, since Wi-Fi is becoming a checklist feature on high end phones. How useful the Wi-Fi in these handsets will be depends on how successful the phone makers are at keeping them open.

Posted on

iPhone activation experience

I sat down with my iPhone and my MacBook, turned on the iPhone and tapped on the screen where it said “Activate iPhone.” The screen went black. Not a good sign.
Then I remembered that the iPhone needs to be plugged in to the PC physically to activate it. This is weird, because one of the things I like best about my MacBook is the way I can just put my Mororola Razr on the desk near it and download photos without any fuss.
So I plugged in the iPhone to the USB and fired up iTunes to do the activation.
Some of the questions were intrusive. It forced me to enter my social security number, also a credit card number for iTunes. I would have preferred to wait until I was ready to buy something from iTunes before giving it credit card info.
The minimum billing I could find was $59.99 a month plus a $36 activation fee for an obligatory 2 years.
This is a $1,536 commitment; add in the $600 for the phone and this toy costs over $2,000.
iTunes showed me my new phone number, and the phone screen said:
“Waiting for AT&T activation. This may take some time.”
This sounded ominous, but within a minute the phone said it was activated.
I made a phone call. Sounded OK.

Posted on

New York Times tells it like it is

David Pogue, the gadget-maven at the New York Times, went to a cell phone conference in Italy last week, and learned a few home truths.

On Independence Day he wrote a column that lambasted the US cellular carriers for their conservatism, and the following day he eulogized T-Mobile for deploying UMA. The UMA writeup is a PR flack’s dream. All true, too.

In the column on the calcification of the US cellular carriers, he indulged in a bit of wishful thinking:

If the iPhone becomes a hit, then, it could wind up loosening the carriers’ stranglehold on innovation.

Seasoned denizens of this industry may scoff, but it must be possible. And while UMA strives to exploit the VoIP genie while still keeping it in the bottle, at least its another step in the right direction. In the column on UMA, Pogue made a prediction that I happen to agree with:

But hard to believe though it may be, T-Mobile did make an announcement last week. And even harder to believe, its new product may be as game-changing as Apple’s.

The Wall Street Journal has already made the observation that the network operators don’t necessarily have their subscribers best interests at heart. But these two events in the same week may mark some kind of a turning point. I hope they do.

Posted on

OpenMoko ships Neo 1973

Lost in the iPhone brouhaha was a June 27th announcement about a phone that may turn out to be more revolutionary:

In our factory in China, 400 Neos are waiting… Starting July 9th, we will launch openmoko.com and start taking orders.

400 units sounds laughable compared to the iPhone’s initial run of 6 million. But it is the seed of something that could turn out to be insanely great. Steve Jobs will remember that the initial production run of the Apple I was only 220 units.

The Neo 1973 looks somewhat similar to the iPhone. It has a similar multi-touch screen that has twice the resolution (640×480) of the iPhone, though it is physically smaller.

What is revolutionary is the software business model. The iPhone isn’t even technically a Smart Phone, since it doesn’t support third party applications. The Neo 1973 is Linux-based, it is open source, and you are welcome to modify it to suit your needs.

This is huge for small, vertically oriented ISVs all over the world. While Motorola and other phone makers have already delivered Linux phones, they are notoriously secretive about the APIs, and make it almost impossible to develop tightly integrated applications. With the Neo 1973, ISVs will finally be free to customize a phone for a particular application or vertical market.

The first version shipping in early July will not support Wi-Fi. A revision in October will. This will be a breakthrough device, selling only to enthusiasts and early adopters in 2007, but gaining sales through 2008 as more applications are developed, and as hardware improvements (like faster CPU, larger screen, 802.11n, NFC, more memory, improved battery life, thinner) are made.