Amazon Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Monday, 26 October 2009

HSPA in 2.6GHz?

Posted on 11:28 by Unknown
I'm wondering.....

... if LTE looks like it might be delayed, for example because of poorer-than-expected performance, difficult optimisation, continued wrangling over voice/SMS implementation, or because operators don't want to be strong-armed into IMS...

... then does it start to make sense to put HSPA/HSPA+ into the 2.6GHz bands, especially given the flurry of upcoming auctions in 2010/2011?

After all, HSPA is a "known quantity" in terms of radio deployment and operation, it's not too difficult to add another band to existing handset platforms, and it's got voice built-in out of the box.

Let's imagine a situation in markets with existing consumer use of mobile broadband, say Europe or Australia or parts of Asia. Now imagine the end of 2012 - there's a lot of 2.6GHz spectrum that's now owned by MNOs. LTE still has teething problems for whatever reason... and in any case, there's several hundred million PCs, dongles, smartphones and other gizmos running on HSPA, albeit only on existing bands like 2.1GHz. I've got to believe that a 2.1/2.6GHz HSPA+ netbook on sale for Xmas 2012 is going to be cheaper and more reliable than a 2.1GHz HSPA + 2.6GHz LTE one - and with broadly similar performance and network efficiency.

On the same theme, do any readers familiar with the innards of UMTS specifications think it might be possible to tweak R9 or R10 HSPA to support flexible channel size, from 5MHz-only to something more like LTE's range of options.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • The Number 1 problem for "seamless" models of WiFi offload / network selection
    I frequently argue against the assumption that "seamless" connection to WiFi is practical or desirable, especially for the general...
  • Mobile social networking - how I'll know when it's going mainstream....
    This falls into the category of "amusing personal anecdotes" rather than "rigorous industry analysis". But it also refle...
  • Part of Nokia's problem - making Ovi compelling
    I've got a Nokia Ovi account somewhere. Signed up for it ages ago, to play around with the Ovi Store when I had an N97 to play with, ba...
  • Putting a value on customer data with reference to offload
    There continues to be a ferocious discussion about AT&T's new data plans - and also, as I commented a couple of weeks ago, about the...
  • Android - the retail experience
    I just stopped off at my local branch of Carphone Warehouse on a whim, to have a quick look at what's being sold and how. (By coincidenc...
  • For telcos, "Monetising OTT" is about distribution partnerships & revshare, not QoS or termination fees
    A couple of years ago, I moderated a panel session at a conference on broadband business models and "traffic management". It was o...
  • BT WiFi smartphone application
    I've just seen BT's announcement of its new iPhone and Android app, offering free WiFi access at its Openzone and FON hotspots to i...
  • An update on @DApremium - the world's first paid Twitter channel. Now available with quarterly or annual subscriptions
    It's now been six weeks since I announced the launch of @DApremium , my second Twitter stream - one which is available only to paid subs...
  • The Novatel MiFi - possibilities for new mobile broadband business models
    OK, I realise that I've been a bit grumpy and critical of some things recently. But before everyone assumes I'm getting more cantank...
  • There really needs to be a "User tariff API" for developers
    Generally speaking, app developers and website owners know what device you've got, what OS, and what browser. Furthermore, they know wha...

Blog Archive

  • ►  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ►  May (5)
    • ►  April (1)
    • ►  March (3)
    • ►  February (3)
    • ►  January (5)
  • ►  2012 (46)
    • ►  December (5)
    • ►  November (4)
    • ►  October (3)
    • ►  September (2)
    • ►  August (4)
    • ►  July (3)
    • ►  June (1)
    • ►  May (6)
    • ►  April (4)
    • ►  March (1)
    • ►  February (9)
    • ►  January (4)
  • ►  2011 (73)
    • ►  December (4)
    • ►  November (10)
    • ►  October (8)
    • ►  September (6)
    • ►  August (3)
    • ►  July (5)
    • ►  June (7)
    • ►  May (9)
    • ►  April (4)
    • ►  March (7)
    • ►  February (6)
    • ►  January (4)
  • ►  2010 (130)
    • ►  December (4)
    • ►  November (10)
    • ►  October (10)
    • ►  September (6)
    • ►  August (9)
    • ►  July (7)
    • ►  June (19)
    • ►  May (19)
    • ►  April (11)
    • ►  March (18)
    • ►  February (7)
    • ►  January (10)
  • ▼  2009 (126)
    • ►  December (4)
    • ►  November (14)
    • ▼  October (9)
      • The "Social web" - does anyone actually want it?
      • Back to low-power GSM: licence exempt?
      • Sharing multiple mobile broadband connections - po...
      • HSPA in 2.6GHz?
      • New personal phone - might finally get around to g...
      • LTE needed immediately!.... er, or else what?
      • WiFi Direct - helping to break the link between SI...
      • One scenarios where femtos could be faster than WiFi
      • Amazon Kindle 2: Does this herald the arrival of "...
    • ►  September (8)
    • ►  August (9)
    • ►  July (10)
    • ►  June (21)
    • ►  May (14)
    • ►  April (2)
    • ►  March (11)
    • ►  February (15)
    • ►  January (9)
  • ►  2008 (94)
    • ►  December (24)
    • ►  November (26)
    • ►  October (25)
    • ►  September (19)
Powered by Blogger.

About Me

Unknown
View my complete profile