I stated that this was particularly because operators will want to exploit greater spectral efficiencies for packet voice, that become possible in later versions of 3.5G. I also argued that because LTE, WiMAX and UMB are all-IP, it was inevitable that we would ultimately end up with full mobile VoIP, and that the question was then about the timelines and roadmap. Moreover, I said that I thought that VoIPo3G (or VoIPo4G if that’s how LTE etc become defined) would quickly overtake VoWLAN in prevalence.
It’s fair to say that I came in for some criticism. Some commentators thought that VoWLAN would grow much more rapidly than I expect pointing to growing availability of dual-mode phones. Others pointed out that using 3G networks for VoIP ran into barriers of power consumption, operators blocking 3rd-party VoIP traffic, or the potential need for IMS or other IP-based core networks.
My view has been that the 3GPP operator “fully standardised” version of mobile VoIP would be slow in arriving, partly because it was expected to be tied to IMS, and partly because of the lack of a defined “plain vanilla VoIP” services in 3GPP or OMA standards. Yes, there’s MMTel (IMS Multimedia Telephony), but that’s not “just VoIP” and in my view is part of the problem rather than the solution, because it bundles in useless and unwanted fripperies like video sharing, rather than just focusing on voice (or web services mashups).
Instead, I expected two things to happen instead – growing use of non-IMS operator VoIP (based on softswitches) extended to the mobile domain, using “naked SIP” handset clients, or possibly standalone VoIP app servers on top of "IMS lite" implementations. And secondly, I anticipated the growing use of fully “over the top” Internet or corporate VoIP applications using 3.5G data channels and flatrate tariffs.
Because I saw standardised “vanilla VoIP” as so slow in arriving, I’ve been exhorting operators who’ve bought the report, or spoken to me personally, to instead consider partnering with the Internet VoIP players – who will inevitably exploit flatrate data and smartphones/3G-connected PCs anyway. Basically, my view is that operators should either work with Skype, Truphone, fring et al – or compete head-to-head with them using their own pre-standard mobile VoIP implementations.
I still believe this is a good route to VoIPo3G, especially for operators that are already moving to VoIP in their fixed networks, or which are early deployers of IMS or other IP-NGN architectures. (This is also relevant for CDMA operators, which seem more IP/IMS friendly at present). Blocking VoIP it not a viable option in competitive markets - as evidenced by the increasing trend towards openness that's been seen in recent weeks.
But interestingly, another ‘flavour’ of mobile VoIPo3G is now emerging as an alternative for mobile operators – Circuit Switched Voice over HSPA, as an early specification within 3GPP’s Release 8 generation of standards. This was just starting to evolve seriously when I published the report in November, and is mentioned in the comments on this post of mine. And it now seems to be moving fast. In the last week, two of the largest ‘'movers and shakers' in mobile technology - from both handset and network sides - have talked up this approach to me unprompted. And I’m in agreement that it’s undoubtedly going to be important.
Basically, CS voice over HSPA takes the ordinary mobile circuit voice service, using ordinary diallers on the phone, and circuit core switches in the network... and tunnels it over an underlying IP bearer. So the application isn't VoIP, but ordinary circuit telephony, but the wireless transport (down in the guts of the phone) is IP.
In other words, it's "Mobile Circuit Telephony over IP"
In fact, we've all heard this concept before. It is an almost direct HSPA equivalent of UMA’s voice over WiFi. In both cases, there are benefits for operator voice calls, derived from the nature of the radio IP bearer: cost in WiFi’s case as it’s unlicenced spectrum, and the efficiencies of new packet transmission techniques in HSUPA and beyond. And in both cases, it’s not necessary for the operator to have already deployed IMS, VCC and so forth – they can reuse their existing core networks, and get away with less messing-around at the handset application layer. [I’m not sure yet whether the IP tunnel uses a similar IPsec approach to UMA, and could use a similar gateway, or if it’s entirely new]. The downside is that this isn’t a next-gen IP voice service in terms of application capability – it’s voice 1.0 transported over network 3.5.
There are also various reasons why I'm more positive on CS over HSPA than I am about WiFi-UMA.
It's a matter of semantics (and your company's point of view) whether you treat CS Voice over HSPA and UMA as 'true' wireless VoIP. Both are using classic circuit signalling, rather than SIP or proprietary protocols like Skype. Neither are as easy to use as "full VoIP" as the basis of innovative applications like voice mashups.
The interesting thing to me is that the industry is starting to polarise into different points of view on this issue. Ericsson remains a staunch MMTel advocate, driven by its desire to push IMS as the main future application layer. But other major players seem to be edging towards a CS over HS worldview, albeit with a hedge around naked-SIP VoIP.
So… taken together, the various types of VoIPo3G are going to be:
- Over-the-top independent VoIP (Skype, Truphone, IP-PBX etc) with a dedicated client on the handset or PC
- CS voice over HSPA, using the ordinary circuit voice app plus some lower-level IP ‘plumbing’.
- IMS MMTel – needing a full IMS client on the device
- Other IMS or standards-based voice apps like PoC or perhaps a standalone SIP VoIP server plugged into the IMS application layer
- Standalone operator softswitch-based VoIP connecting to a (probably) SIP client on the handset.
- Partnerships or mashups of the above.
But the bottom line is that with the addition of CS Voice over HSPA, my top-level VoIPo3G predictions are still looking feasible, although some of the fancier web- or application-based VoIP capabilities will be trickier to exploit by the operators choosing that approach.
Purchasers of the Disruptive Analysis VoIPo3G report will get ongoing support & commentary about these developments. Please contact information AT disruptive-analysis for details.
These are very interesting explications. Again I have learned a lot from you.
The most important point is that these technologies should be usable like normal cell phone calls. The user shouldn't notice and just dial his numbers or use his phone book. A software on the handset should automatically decide how to connect the call: VoIPo3G, VoIPoWifi, callthrough or whatever. No numerous callthrough keystrokes before the real phone number, no waiting time for Truphone to find a Wifi network, no frustration because my Skype buddy isn't online, no weird Rebtel numbers which are every time different for the same callee.
That's where the independent VoIP providers still have work ahead. The user should have the certainty that no cell phone call costs more than a local call. Technically that's already possible, as we learnt from Mobilemax.
Since we're talking about R8 here, and devices that won't be in peoples' pockets until 2010/1 so the issue of 'requiring a full SIP client' in the handset should hardly be an issue. SIP will open up other smart features that CSoHSPA will not.
I personally question if VOIP on mobiles will actually live that long.
Even post-R7 extensions are needed for VOIP to be more spectrally efficient than CS, so where precisely is the hook for the operators: CS voice that is a central portion of a 3GPP network, in HW and SW, or VOIP that requires several radio network features (QoS, RoHC, VOIPoHSPA) that will all have a vendor cost and will yield worse system capacity, and for the user, worse Voice Quality. All this 2 years after AMR-WB will hit the networks, with CS-based voice quality that exceeds peoples fixed-line experience?
Perhaps Ericsson and others' reticence over CSoHSPA is that they have yet another 'standard' to support, that no-one might actually use.
I am not as optimistic on CS Over PS for R8. At the last Plenary held in Cancun, The report (TR 23.879) from technical committee regarding CSoPS was only noted. The schedule is tight, if not at risk for the release. Sixteen of the operators held an impromptu side meeting and ranked their priorities for the release (TS-070909) - CSoPS was at the bottom, while VCC/ICS was at the top. I would presume that most operators see VCC/ICS as their legacy preservation strategy.
From the : There was consensus in [plenary] that the solution for CS support in EPS in the Release 8 time frame will be CS Fallback (page in 4G to go to 3G). [Technical Committee] are left to decide how to document this in the CS over PS Study. A new [work item] needs to be produced for the normative CS over EPS fallback work.
IMHO, LTE could leave a huge stranded investment of perfectly functioning, packet capable (R4) voice servers deployed in 3G. Unless someone has a modified UMA trick up their sleeve, I can't be as optimistic.
Thanks to the various posters here. I'm not directly involved in the standards process, so I'm a little divorced from the nitty-gritty of the politics.
I suspect that we'll end up with a situation (similar to that with WiFi voice), where there are 4 or 5 possible architectures ranging from "full IMS" right through to "Internet VoIP over the top" (which works OK already in small numbers of users). CS over HSPA will be somewhere in the middle.
There will be a bewildering set of decision criteria for any given operator - legacy core networks, ease of upgrade of radio elements, frequency, local competition, regulation of VoIP, IMS/Internet philosophy, device strategy and so on. No easy answers.
I'm certainly not saying that CS over HSPA is going to take over the world - but it's just been interesting that it's suddenly ballooned in public profile in recent weeks. I wanted to add it to the debate on this blog, given my focus on VoIPo3G.
It seems particularly popular with vendors pitching HSPA+ as a hedging strategy vs. delays or problems with LTE. A lot may depend on 2.5Ghz spectrum auctions - will anyone actually get the 10MHz or 20MHz needed to make LTE really worthwhile? Also maybe 3G deployments in refarmed 900MHz spectrum might be a good candidate for some of the new R7/R8 extensions.
CS over HSPA is part of the 3GPP Release 8 content. But terminals according Release 7 can support the feature w/o problems. I.e. terminals can be considered sooner available.
The use of the HSPA radio bearer will allow to use all the power saving features which has come with HSPA. This will improve user experience compared to the R99 DCH.
IMS is hopefully providing more than just voice, therefore I consider CS voice over HSPA an improvement on the voice service, but no competition to IMS and mult-media
The main driver behind CSoHSPA is providing better talk times (and better radio capacity). Voice over HSPA offers significant power saving incentives. If this voice is CS voice you get all this with impact to radio network only. And as HSPA radio is there already this is just a matter of routing CS voice over non-CS radio.
Sure, you'd get the same benefits for true IMS voice + more, but CSoHSPA gives these things with a small tweak to the radio network only ==> Only a small investment assuming you already had HSPA in your network. And let's face it, the major drag of 3G terminals is the need to always have the charger with you - something you didn't need to do any more in the late nineties for a GSM phone.
Post a Comment