http://www.techworld.com/mobility/features/index.cfm?featureid=2420&pagtype=all Cell.phone convergence - coverage versus capacity Wi-Fi has what cellphones lack. Craig Mathias, Farpoint Group April 10, 06 Dropped calls and no service are a fact of life in cellular networks. They're usually the result of problems with the propagation of radio waves, which is how the waves get from Point A to Point B and back again. This is a frightfully statistical process if there ever was one. Lots can happen between those two points, and if the signal is damaged or otherwise fades to such a low level that the receiver can't detect and use (demodulate) it, that's that. No signal, no service. Sometimes, though, dropped calls are the result of simply not having enough capacity on the cellular network, and this is usually due to having too few cells. The farther a signal goes, the less overall capacity the cell has, because there will be more users sharing the spectrum on that cell, and more range usually means less reliability regardless. We've got coverage, but not capacity. Why not just put the cells closer together, you ask? Good question. The answer is that cells are expensive, not only in terms of equipment, but also real estate costs, regulatory fees and lots of legal bills from local residents who love their cell phones but don't want to live near a cell tower. The laws of physics are at work here, too: The higher the signal is off the ground, the better it will propagate. Wi-Fi doesn't have these problems. Wireless LANs have gobs of spectrum to use - as much as 689 MHz worth in the US, plus another 50 MHz for municipalities - and they operate over relatively short distances. This means we've got capacity, but not coverage. Sure, we can deploy metro-scale Wi-Fi meshes, but we'd still have lots of little gaps in coverage to deal with and highly variable performance due to motion and the number of other active users nearby. So, cellular has coverage via big, expensive cells on licensed frequencies, and Wi-Fi has capacity on lots of little, inexpensive cells on unlicensed (free) spectrum. This, of course, begs the question: Why not merge the two into a single system and get the best of both worlds? Why not, indeed? The interim step Not so fast. There's an interim step we need to do first, and that's what's becoming known as fixed/mobile convergence (FMC). In its simplest form, FMC involves connecting the enterprise private branch exchange (PBX) to the cellular network, enabling cell phones to become extensions on the office telephone network. I expect this will ultimately happen via services offered by cellular operators, which will eventually realise that they can sell vast numbers of phones to the enterprise instead of one here and one there to consumers. Cellular operators also will be able to largely displace wireline carriers in the process. Of course, the wireline guys will fight back by becoming mobile virtual network operators (MVNOs), cellular providers that lease their capacity from the cellular network operators, and offer their own FMC systems. And the enterprise can even go the do-it-yourself route and implement FMC via customer premises equipment, which is available from a number of vendors, with more on the way. We expect the MVNO strategy to become obvious in about a year, and the cellular operators to begin to move in earnest in about 18 months. They're in no hurry; they don't need to be, and this upgrade represents a major change to their core networks and services, so caution is in fact appropriate. Key to all of these scenarios are dual-mode cellular/Wi-Fi handsets, which allow both voice and data access via both cellular and Wi-Fi services. Imagine using your cell phone as a cordless phone in the office, with unified dialing directories, calling features, a single voice-mail system (my No. 1 wish) and all of the resulting convenience. I've yet to meet an end user uninterested in this possibility. Now imagine that the handoff of voice and data connections between cellular and Wi-Fi, at both the in-building enterprise and metropolitan scales, is transparent. I've been referring to this possibility as mobile/mobile convergence (MMC), since no connection to a PBX is required or necessarily implied. Indeed, I expect the PBX to gradually disappear as its services are replaced by the IP PBX, or, more likely, services provided in the carrier's cloud and administered by the one person left in the telecommunications department via a Web interface. Regardless, with MMC, we'll be able to unify the two wireless worlds I mentioned above and gain access to both coverage and capacity in a single handset supported by what appears to be a single service - you'll get one bill, anyway. Note that one radio just can't do it all. All of this capacity, coverage and capability will eventually lead to the final step - fixed/mobile replacement (FMR). OK, I just made up that term. But think about it - if wireless can provide voice, broadband data, maybe a little video (granted, not HDTV), and can do it with the throughput and reliability of wired broadband, why won't we replace wire, just as so many have by making cell phones their only phones today? Why not, indeed? Craig Mathias is a principal with Farpoint Consulting. This article appeared in Copmuterworld
Cellular operators have a lot of incentive to implement reliable handoffs from cell to cell in order to keep their customers happy. It is challenging enough for the engineers even though they control the cells themselves. Can you imagine having reliable handoffs between a bunch of widely variable wifi systems? There are also IP routing issues, QOS issues (anyone using VOIP knows how important this is), transmission power control issues currently used extensively by cellular systems, dropped packet issues, and unpredictable latency. The article begs a lot of questions.
Wireless carriers will most likely embrace this technology in time, but most likely based only on private home or office wifi use, Other than T-mobile, there is not a reason any major wireless carrier would want to embrace this technology and leave it open to any and all wifi hotspots. It wouldn't make them any revenue to do so. As for the parts about linking with office phones etc. That has been done for quite some time, and quite well by Ascendant Telecom (a little known company that just got scooped up by RIM.) I was working with them back when they were Travlers Telecom.... Nice thing about living in Hilton Head, is I never have trouble getting vendors to come for a visit.
I guess the systems we are talking about are similar in end result, but very different in implementation, the system I was referring to is server based, and would bypass the need for building out a wifi network or an inbuilding network like Spectralink. It would tie into the PBX, and ring the wireless and desk phones at the same time and give you direct inward dialing from your regular cellphone. Since they got purchased by RIM, I would expect to see them tied into a BES purchase. Wireless carriers prefer this type of network since they can control the wireless portion as opposed to a third party. As compared to older solutions like Panasonic Business Link (1/2 cordless, 1/2 cellphone.) solutions to PBX integration. When I worked for smaller carriers, it was an easier sell to set-up a campus rate plan (unlimited usage around a property or campus.), but because of the numbers of customers and numbers of cellsites, it becomes more difficult (politically not technically) to set-up this type of system in billing. So I.T. directors will most likely be pushing for ways they can implement campus solutions without breaking the bank. With the RIM purchase and products such as Skype and Vonage becoming common place, It's only time before you see these products in prime time. My guess is that once the PBX vendors embrace it an make it their own, then you will see in the enterprise space. As for small business and SOHO customers, the push will come from wireless providers when they are ready for it...and see a good way to make money from it.
That system you're talking about sounds like the SimulRing feature in some VoIP phone services like Vonage where you can designate several phone lines that will ring at the same time when someone calls one of them. We can do this too without ever using the WiFi network but it will use cellular minutes since the call has to reach the PDA via the cellular network. The WiFi implementation obviously doesn't use minutes because it doesn't use the cellular network. This is good for some of us who don't want to carry two phones around campus, which means we can carry both our personal cell phone line and our work line in one device. Of course, the WiFi doesn't work once you step out of the buildings and it doesn't handoff to the cellular network, but that's the idea: We really don't want to be reached if we are not on duty. And because its GSM, it means we can change the SIM card anytime to a regular phone if we don't need a bulky PDA on our belts and rather carry a light and small phone when not at work.
I have a Vonage WiFi phone (F1000) which works pretty well in most hot spots. Skype has several similar phones. There are quite a few handsets with built in WiFi. These have been available for some time. WiFi phones are moving forward and will continue to do so, whether or not the wireless providers grab onto this market. Things are getting interesting.
The battery life is more or less similar to my cell phones with similar usage. It will go more than three days with usage of 30 - 60 mins/day. I have not done a real test on the battery life so my numbers are an educated guess. The battery is larger than the LiIon battery in some of my cell phone batteries. This would certainly contribute to a longer battery life. I have noticed that the F1000 will stay connected to the same ASP even when I have moved to a point where there is a stronger ASP. This leads me to believe that it does not automatically search once it has connected until it loses the original ASP connection.
I have a Verizon 6700 and use the Skype Pocket PC Client...It's usable on wifi...I don't have evdo in my area yet, but will try it on evdo next week in Florida. As for wifi around town, there are a couple of options, most of the harbours and tourist areas have pay for use wifi... as for my home network I have wifi, and a non broadcasted ssid, and encryption, my neighbor has a linksys router (fresh out of the box) and often my phone will jump onto their system. I haven't figured out who it is yet... Skype on wifi is nice, but not near enough coverage or call quality to be ready for prime time. Dedicated wifi voice on a private wifi network tied into your PBX I imagine would have better call quality?
I use the F1000 to sniff out WiFi ASPs as I travel. It finds both secure and open ASPs. Last Summer, I used my laptop with NetStumbler running as I took a train from Santa Barbara to San Luis Obispo. The number of open WiFi ASPs which I have found is amazing.