A while after the iPhone 4S announcement, I posted a piece on the iPhone 4S' cellular architecture and talked about the new inclusion of HSPA+ alongside CDMA2000 1x/EVDO and some specifications. Since then, there's been some ongoing confusion about whether the device supports HSPA+, whether it's "4G," and just what all that really means. 

It's funny because this issue came up with the HP Veer 4G on AT&T a while back, and with that particular device I did a similar explanatory article in the context of a This Just In post. I wager the somewhat limited cross shopping (and commercial success of the Veer) resulted in many iOS users missing that discussion, and it's cropping up again for the iPhone 4S. The confusion is really twofold. First is a misunderstanding about 3GPP releases and what features are optional or mandatory. Second is a misunderstanding about HSDPA, HSUPA, and modulation coding schemes. Let's break it down. 

UMTS standards are defined by an organization known as the 3rd Generation Partnership Project (3GPP), which is a body comprised of partners like telecommunications companies, wireless carriers, and cellular hardware manufacturers. Standards are important, and their formation requires collaboration and discussion. Major revisions are finalized, synchronized, and become "releases." For example the first releases define GSM, release 99 defines UMTS, release 5 defines HSDPA, 6 defines HSUPA, 7 - HSPA+, 8 - LTE, and 10 - LTE Advanced.

This is a huge oversimplification, but you can see how major milestones are bundled up and become releases, and thus when baseband manufacturers like Infineon, Qualcomm, or ST-E release hardware, they're said to be compliant with a given release, and inherit the big features from releases before it. 

Where confusion arises is that you don't need to include every feature from some release to say that your hardware is compatible with a given release, and really only features from release 99 are mandatory if you're out to make some UMTS hardware. So when a baseband is "HSPA+" (which really is a colloquial name for the improvements to HSPA made in 3GPP release 7), it doesn't need to include every last feature. Features included in release 7 include things like reduced signaling, faster call setup, continuous packet connectivity, reworked RCC states (idle, DCH, FACH, e.t.c), MIMO, and higher order modulation support. On the downlink, 64QAM or MIMO gets added, and on the uplink, 16QAM gets added. 

The confusion in the case of many HSDPA 14.4 (Category 10) devices seems to center on whether it is or isn't HSPA+ if it doesn't include 64QAM support on the downlink (which starts in category 13). This is one of those few times that looking at the Wikipedia table for HSDPA UE categories can be misleading. UE categories with 64QAM are introduced in 3GPP release 7, however it's up to manufacturers to include or not include that feature when actually making hardware. It's interesting to me that all of this misinformation comes up over HSDPA UE category, and somehow HSUPA UE category never gets brought up - I haven't seen anyone claiming that some baseband isn't HSPA+ because it excludes 16QAM on the uplink, yet the overwhelming majority of devices are just using QPSK. 

Apple hasn't stated what baseband is in the iPhone 4S (and I guess we won't know absolutely for certain until it gets opened up), but it is almost without doubt MDM6600 just like the Verizon iPhone 4. The specs all line up, and while that part doesn't include 64QAM on the downlink, it does include a number of the other HSPA+ features I've mentioned, and is thus 3GPP Rel.7 and therefore "HSPA+." 

Actually using these higher orders of modulation requires favorable radio conditions, of course, and the result is that 64QAM on the downlink or 16QAM on the uplink only gets used in very well tuned systems or cell center. There have been some drive tests done which have shown that 64QAM only really gets used 10% of the time on average. In the iPhone 4S' case here in the USA, it's silly to argue about whether or not the phone can decode 64QAM if AT&T doesn't even use it. A few Samsung devices so far have been based on ST-E's Thor 5730 HSDPA 21.1/Category 14 baseband, and include an engineering menu which shows the percentage of frames encoded using QPSK, 16QAM, or 64QAM. 

Note that 64Q is 0. I have run many other tests where 16Q is 100.

I've shown a few other interested people how to see this menu on the Samsung Infuse 4G on AT&T, and thus far none of them has seen any 64QAM frames show up. I've never seen 64QAM pop up either, even with line of sight to the tower in the middle of the night. Those markets include my own in Tucson, AZ, and New York City, which are both AT&T "4G" markets (connoting HSPA+ with improved backhaul) on the coverage viewer. Two data points isn't enough to say conclusively that AT&T isn't using 64QAM, but I haven't seen it yet. You can also see this on video from an Infuse in NYC. Not all AT&T WCDMA "3G" markets are HSPA+, but if you're in a market that AT&T has marked with dark blue (and calls "4G") you can be pretty much assured it's HSPA+.

So the next question is when HSPA+ is and isn't real 4G, and obviously the bar right now is LTE. We've gone over all the real ITU decisions and such in our LTE piece, (whose definition does include DC-HSPA+ and LTE instead of previously just LTE Advanced) but what matters is actual throughput. There's credibility to HSPA+ being comparable to LTE speed as soon as DC-HSPA comes around which aggregates together two 5 MHz WCDMA channels. With all the same features (MIMO, 64QAM, and wider channel bandwidth), DC-HSPA+ gets you approximately to the level of theoretical maximum throughput you can get on LTE. It's easy to see how things are arguably fairly comparable when you consider Verizon uses 10 MHz FDD, and DC-HSPA+ aggregates together two 5 MHz WCDMA channels. Throw in MIMO in addition to just dual-carrier, and maximum theoretical throughput lines up pretty closely as shown in this table by Qualcomm:

That's saying nothing about network latency, however, where LTE will continue to outshine HSPA+. In that case, it does arguably make sense to associate DC-HSPA+ with real LTE and call it real 4G, but until DC-HSPA+ or at least HSPA+ with MIMO it is almost without doubt still 3G. Obviously USA carriers' attempts to pass off HSPA+ 14.4 or even 21.1 as "4G" is immediately laughable marketing, but DC-HSPA+ is arguably real 4G.

Lastly, rumor has it that AT&T and Apple are "working together" to change the 3G status indicator to "4G" for AT&T in the US, a move that would mark the first carrier intrusion into the otherwise completely carrier-untouched iOS. I don't have issue with the status indicators showing H or H+ (for HSPA and HSPA+ when appropriate), but misleading indicators do nobody justice and just serve to reinforce these kinds of misconceptions. 



View All Comments

  • miusuario - Sunday, October 16, 2011 - link

    There are many features that define an UE as HSPA+. Still, the main driver of UTRAN evolution is throughput.

    Then, saying that the iPhone 4S is HSPA+ is wrong. According to the table above, the MDM6600 is HSPA+ as it implements HSPA+ WCDMA Air interfaces. If it's so, how come the most basic feature of HSPA+ air interface, 64QAM is left behind?

    The perspective of this analysis, and the fact that it's even considering a future 4G tag for such "HSPA+" goes beyond wrong, seems to be even manipulated. HSPA+ minimum requirement in Air interface is 64QAM, but, that's not it. Multi-Cell Carrier implementation and MIMO, are supposed to take throughputs (theoretical peak) to 84 Mbps, 168 Mbps, even beyond (NSN just show 336 Mbps). In this analysis 14.4Mbps are enough, because there is implementation of CPC. This is totally wrong. IMO.
  • nasula - Monday, December 12, 2011 - link

    While Anand is correct that HSPA+ doesn't necessarily mean any speed increase (CPC, Voice over HSPA, FDPCH or any other new features would also do), I didn't see any real proof that it is an HSPA+ device. I could have also missed it in the article (ready for bed).

    I know that the qualcomm feature chart claims this, but where's the proof? What HSPA+ features does the iP4 have? It would be VERY interesting to know if it supports for example CPC or better yet, standardised Fast Dormancy instead of the network breaking implementation found in iP3GS and iP4. Any data on this?
  • Remingtonh - Thursday, March 08, 2012 - link

    It is even more relevant today! Reply
  • Rizi - Tuesday, July 17, 2012 - link

    The iPhone 4S is part of an interesting tale. It was the device thought to come in addition to a new iPhone 5. The 4S was supposed to incrementally increase the specs found on the iPhone 4 and offer a lower price point, while the iPhone 5 would provide a huge jump in design and power. When Apple unveiled the iPhone 4S with no iPhone 5, it was clear that for at least the next ten or twelve months, it would be considered Apple’s flagship phone. While many were disappointed, the iPhone 4S has gone on to be one of the best selling phones of all time in just a few weeks. But with more choices than ever for smartphone shoppers, does the iPhone 4S still have a place as a premium device? Unboxing the iPhone 4S is no different than unboxing an iPhone 4. You get the same accessories (a wall charger, USB cable, and white ear buds) in virtually the same box. The only point of differentiation is the “S” branding (reused from the days of the iPhone 3GS) plus an iCloud logo. The <a href="http://cellocean.com/iphone-4s-specifications-2210... 4s</a> is powered by the A5 dual-core 1GHz chip found in the iPad 2, though our guess is that the chip might not run at the full peak 1GHz speed, and instead probably cap out at 800MHz. Apple claims that the A5 provides 2x the CPU speed and 7x the graphics prowess than the iPhone 4 (take a look at our comparison video below to see whether this is true). Beyond that, the iPhone 4S has 512MB of RAM, 16/32/64GB of storage, 802.11 b/g/n, Bluetooth 4.0, a digital compass, gyroscope, cellular data provided by HSPA+, HSDPA, or EVDO Rev-A (depending on whether you version you choose). The screen is unchanged–it is 3.5? with 960×640 resolution, providing a 326ppi pixel density, which is still unrivaled by any other phone on the market right now. Powering everything is a battery that is slightly larger than the iPhone 4, providing 8 hours talk time. More on battery life later. From day one, the iPhone 4S is available in white, unlike the iPhone 4 where it took many months for the white version to start shipping. Why choose white over black? It’s a matter of personal preference, but white does a better job at hiding finger prints. While the iPhone 4S has the same design as the iPhone of last year, it’s still a handsome device thanks to colored glass that opposes the metal bands of the antenna configuration. New to the iPhone 4S is an improved dual-antenna system: no more “grip of death”. Apple says the camera optics of the 4S are vastly improved over the 4. We agree. It has a larger f/2.4 apperature to allow more light into the sensor, providing improved performance in low light situations. The iPhone 4S ships with iOS 5, which brings forth a lot of new features. Chief among them is a new notification system, iCloud, Siri, iMessage, Reminders, improvements to the photo app, and some other goodies. Let’s dissect each of these new features in more detail. Previously, notifications in iOS were very disruptive. They’d come in as pop-ups that would interrupt you from what you were doing. Now, notifications have three ways of being customized. First, you can choose whether a notification pops in as a banner, a pop up, or you can turn them off completely for a given app. The banners are great except that they obscure UI elements when they appear as shown above. And because you can’t “wipe” them away like in Windows Phone 7, you have to wait until they disappear, which takes several seconds. As you can see in the screenshot above, the notification is covering up the “Messages” back button. Very annoying. Update: after some experimentation, we found a way to dismiss banner notifications in iOS 5. Second, you can utilize the Android-like Notification Center to manage all of your notifications which is accessible if you swipe down from the top. The trouble with this is that you cannot selectively remove notifications. Rather, you can only clear entire categories of notifications with the tiny X button. I didn’t find the notification center particularly useful, so I left it turned off by selectively entering the Notification setting for each program, and turning Notification Center to off. Third, you can have notifications appear on your lockscreen. Not only that, but the program’s icon becomes a slider so that you can instantly enter the program that has sent you a notification. This is very useful, but if you’re streaming a lot of notifications, this area might become cluttered. Reply

Log in

Don't have an account? Sign up now