So we've seen the new iPhone, and had a chance to briefly play with it at the demo room, but as I've learned in the past so many times you only really know a handset after you've taken a look at the FCC test reports or spent a few days with it yourself. On my flights home, I typed up our iPod and EarBud impressions piece, but also pored over those FCC test reports for the iPhone 5, and it became immediately obvious the iPhone 5 doesn't support simultaneous voice and data on CDMA2000 carriers such as Sprint and Verizon in the US. 

The reasons, as always, are somewhat technical but at a high level pretty simple. Suffice it to say that at a high level this is a design decision which makes the phone as small and light as it is (it really is light, almost alarmingly so) and enables it to support a wide number of LTE bands, rather than some major oversight like I've seen it portrayed. 

First, a bit of overview. At the Apple event there were two physical hardware models for the iPhone 5 announced: A1428 and A1429, with three different provisioning configurations. There are hardware differences between the two models, and what provisioning boils down to is both how the phone is initially provisioned, and likely what AMSS (Advanced Mobile Subscriber Software - Qualcomm's software package that runs on the baseband) gets loaded at boot. This is analogous to how with iPhone 4S there was a single hardware model, but two different configurations for CDMA and GSM. 

For the most part, the two hardware models are identical, and to most users the two models will be indistinguishable, but there are physical differences to accommodate a number of different LTE bands between the two. The Apple iPhone 5 specs page lists this at a high level, and there's an even more explicit LTE specific page with a list of what LTE bands work for what carriers. Of course, what ultimately really matters is what's in the FCC docs and in the hardware, and looking at those there are a few more bands supported than listed for LTE.

Why this is the case is interesting and a function of transceiver and Apple's implementation – with Qualcomm's transceivers (specifically RTR8600 in the iPhone 5, but this applies to others as well), each "port" is created equal, and can handle WCDMA or LTE equally. If your design includes the right power amplifiers (PA), filters, and antenna tuning, you're good to go, which is why we see LTE testing reports for bands that aren't listed otherwise. I saw this same behavior with Apple's test reports for the iPad 3 with LTE as well, there were many more tested configurations than what any carrier in the USA will run, but remember Apple's approach is about covering as many possible configurations as possible with the fewest number of SKUs.

I've made a table of what the cellular band support breakdown is for the three iPhone 5 configurations:

Apple iPhone 5 Models
iPhone 5 Model GSM/EDGE Bands WCDMA Bands CDMA 1x/EVDO Rev.A/B Bands LTE Bands (FCC+Apple)
A1428 "GSM" 850/900/1800/1900 MHz 850/900/1900/2100 MHz N/A 2/4/5/17
A1429 "CDMA" 850/900/1800/1900 MHz 850/900/1900/2100 MHz 800/1900/2100 MHz 1/3/5/13/25
A1429 "GSM" 850/900/1800/1900 MHz 850/900/1900/2100 MHz NA 1/3/5 (13/25 unused)

Note that we now have both quad band GSM/EDGE and WCDMA across all three models. All three configurations support WCDMA with up to HSDPA Category 24 (DC-HSPA+ with 64QAM for 42 Mbps downlink) and HSUPA Category 6 (5.76 Mbps uplink) as far as I'm aware. Only the A1429 "CDMA" configuration supports CDMA2000 1x and EVDO, and interestingly enough even supports EVDO Rev.B which includes carrier aggregation, though no carrier in the USA will ever run it.  In addition the FCC reports include 1xAdvanced testing and certification for CDMA Band Classes 0 (800 MHz), 1 (1900 MHz), and 10 (Secondary 800 MHz), so I have no idea why Sprint is saying it won't work with their "HD Voice" (really 1xAdvanced) deployment, but I'm digressing yet again... 

Looking at just the LTE band numbers is hard unless you have them internalized, so I made yet another table which focuses just on that aspect:

Apple iPhone LTE Band Coverage
E-UTRA (LTE) Band Number Applicable iPhone Model Commonly Known Frequency (MHz) Bandwidths Supported (MHz)
1 A1429 2100 20, 15, 10, 5  (?)
2 A1428 1900 20, 15, 10, 5, 3, 1.4
3 A1429 1800 20, 15, 10, 5, 3, 1.4 (?)
4 A1428 1700/2100 20, 15, 10, 5, 3, 1.4
5 A1428, A1429 850 10, 5, 3, 1.4
13 A1429 700 Upper C 10, 5
17 A1428 700 Lower B/C 10, 5
25 A1429 1900 20, 15, 10, 5, 3, 1.4

So you can see how with two different hardware models, Apple is able to support no fewer than 8 LTE bands with largely the same hardware – the same display, chassis, battery, form factor, and PCB outline (different power amplifiers and filters are required), and roughly the same exterior antennas (gain is different on the primary bottom antenna between the two models, no doubt they're tuned differently). Previously most handsets I've seen have been destined to work only on a single carrier, and thus implement at most one or two LTE bands. 

If you look at Apple's iPhone lineup historically, there's this obvious two year cadence which jumps out at you, and it applies even to cellular. I've removed the CPU and GPU parts so this table doesn't get too huge, but historically Apple has been very careful about engineering a platform that will last for a while. 

Apple iPhone - Cellular Trends
  Release Year Industrial Design Cellular Baseband Cellular Antennas
iPhone 2007 1st gen Infineon S-Gold 2 1
iPhone 3G 2008 2nd gen Infineon X-Gold 608 1
iPhone 3GS 2009 2nd gen Infineon X-Gold 608 1
iPhone 4 (GSM/UMTS) 2010 3rd gen Infineon X-Gold 618 1
iPhone 4 (CDMA) 2011 3rd gen Qualcomm MDM6600 2
(Rx diversity, No Tx diversity)
iPhone 4S 2011 3rd gen Qualcomm MDM6610 (MDM6600 w/ ext. trans) 2
(2 Rx/1 Tx diversity)
iPhone 5 2012 4th gen Qualcomm MDM9615 w/RTR8600 ext. trans 2
(2 Rx/1 Tx diversity)

It was touched on in the keynote, but the iPhone 5 likewise inherits the two-antenna cellular design that was touted from the 4S. This is the original mitigation for iPhone 4 "deathgrip" which was introduced somewhat quietly in the iPhone 4 (CDMA), and carried over to the 4S with one additional improvement – the phone included a double pole, double throw switch which allowed it to change which antenna was used for transmit as well to completely quash any remaining unwarranted attenuation. While receive diversity was a great extra for the 4S that drastically improved cellular performance at cell edges, in LTE 2-antenna receive diversity is now thankfully mandatory, leaving the base LTE antenna configuration a two-antenna setup (two Rx, one shared for Tx). Thankfully, Apple already had that antenna architecture worked out with the 4S, and carried it over to the iPhone 5. 

So now that we're done with all that, where the heck does simultaneous voice and data fit into the picture? Again, it comes down to antennas, design decisions, and band support.

First a bit of history: first generation LTE phones on Verizon used a combination of two cellular architectures to deliver both LTE and CDMA1x/EVDO capabilities. Quite literally there were two basebands, two transmit chains, and at least three antennas: a two-antenna setup for LTE, and 1 transmit for CDMA 1x/EVDO duties. Usually this boiled down to a shared diversity receive antenna for LTE and CDMA 1x/EVDO, and discrete transmit antennas for LTE and CDMA1x/EVDO.

Samsung Galaxy S 3 for VZW (SCH-I535) antennas (3 for cellular)

Modernizations from Qualcomm have since reduced the number of digital basebands required to just one (with MSM8960 and MDM9x15) which helped improve battery life, but the end implementation still requires the same three-antenna solution. This configuration enables both SVLTE (simultaneous voice and LTE) and SVDO (simultaneous voice and EVDO) with one modem but still requires those two transmit RF chains to work for CDMA phones. I should mention that these methods are all in place to accommodate the fact that as of yet almost no CDMA networks implement VoLTE (Voice over LTE or Voice over IMS), except MetroPCS. To make this single radio simultaneous LTE and CDMA architecture work requires making another RF path. 

On WCDMA/GSM carriers, the path forward until we get to VoLTE is what's called circuit-switched fallback (CS-FB). This quite literally means you drop from 4G LTE to 3G WCDMA (where voice and data are already multiplexed) for the call, then hand back up to LTE when you're finished. This is the way that voice works at the moment for all GSM/WCDMA carriers, and on all those handsets with LTE to date.

From iPhone 5's FCC Test Reports

So onto the iPhone – we know definitively that the iPhone 5 definitely doesn't support either SVDO or SVLTE. It's as simple as looking at the FCC documents and the appropriate sections in the allowed and tested simultaneous transmitters section for SAR (Specific Absorption Rate) testing. There, it's spelled out that only one air interface can be active at a time, and that only one antenna can be selected for transmit at a time. There's also an explicitly called out mention to VoLTE not being supported at present. I didn't replicate the entire table of simultaneous transmission combinations which need to be tested (it is a huge table) there are no entries with CDMA Voice being active at the same time as any data mode save WiFi. This has been confirmed as well by later statements by the carriers and Apple. 

From Apple's perspective, no doubt the iPhone 5 not supporting simultaneous voice and data on CDMA carriers isn't the end of the world. After all, iPhone 4 and 4S customers have ostensibly been using their phones without that functionality just fine for some time now – this is just a logical extension. At the same time, LTE handsets on Verizon and Sprint which currently support both SVDO and SVLTE will have a differentiator, and from what I've been told the inclusion of SVDO is more of a "delighter" than core feature. 

What it really boils down to is that by using this single Tx chain, Apple is able to support a ton of LTE bands (more space for PAs and fewer transceiver ports used on SVLTE for CDMA networks) and also do it without making the iPhone very large. Moving to an architecture that works with SVDO and SVLTE would require an additional transmit path and antenna, and incur a size and weight penalty. The other reality is that CS-FB is the way voice coexists with LTE in the vast majority of cases globally, and thus engineering all that just for CDMA networks is at odds with Apple's ultimate desire to deliver as few models as possible. 

In the future all of this overhead to implement voice with legacy 3G and 2G networks will largely go away and exist only as a handover option for when LTE service isn't available. Voice over LTE is indeed coming soon. 

Update: The other LTE related iPhone 5 thing to explain is why LTE support for 800 MHz and 2.6 GHz isn't present. This article originally started as an explanation for why SVLTE and SVDO support are not absent, I think there's even more discussion necessary about what the likely plan of attack from Apple is for including both more LTE bands and that TD-SCDMA phone for China. I plan to address that in our upcoming review. 

Comments Locked


View All Comments

  • ananduser - Saturday, September 15, 2012 - link

    Get over yourself. RS2 didn't blast Anand's at all. He just expressed a pretty viable point, IMO. Where the heck do you get the impression that you need to butt in and send him to some other sites ? If you're doing that, try to send a large part of the audience the AppleInsider way while you're at it.
  • ltcommanderdata - Friday, September 14, 2012 - link

    One thing you should test in your CDMA iPhone 5 review is what happens if you take a phone call (hopefully hands-free) while driving with turn-by-turn directions? Does iOS 6 cache enough map data/turn-by-turn data to last through an arbitrary length phone call? I'm not expecting hours here, but certainly 10s of minutes. Or does turn-by-turn directions simply cut-off which could lead the driver to miss a turn and stay on the same road oblivious? That would be a major problem.
  • En1gma - Friday, September 14, 2012 - link

    there are 3G on AWS?
    or no 3G in t-mo network?
  • KPOM - Friday, September 14, 2012 - link

    T-Mobile uses AWS for 3G, but the iPhone 5 doesn't support it. T-Mobile is re-farming some of their 1900MHz spectrum to run 3G, which the iPhone 5 supports, and plans to run LTE on AWS, which the iPhone 5 supports.
  • jb510 - Friday, September 14, 2012 - link

    Well drat... I thought I'd made a decision to switch from AT&T (iPhone 4) to Verizon because the Verizon iPhone 5 offered better global LTE roaming... but this throws a another factor into the decision and no I'm uncertain again.

    Simultaneous Voice/Data is moderately important to me. Global compatibility (Thailand, India, China) is also moderate important to me. I'm thinking simultaneous V/D will win out and I'll accept slower data speeds overseas, but it's all still a bit cloudy.
  • drdave25 - Friday, September 14, 2012 - link

    Thanks for this comprehensive article.
    1. While you were doing the research, did you find the FCC SAR levels for the iPhone 5? I can't find it anywhere on the net.

    2. I wonder if one iPhone 5 has an advantage over the other when traveling in the EU or even in (say) Turkey or Asia...with AT&T I guess one doesn't have to bother changing a sim card?
  • drdave25 - Friday, September 14, 2012 - link

    I guess the VZ version could be a disadvantage when using a GPS app and talking to someone simultaneously.
  • SignalPST - Saturday, September 15, 2012 - link

    Hi Brian and Anand,

    With your upcoming full review on the iPhone 5, it would be awesome if you could address the following points that I've been itching to find out.

    1. confirm that the new EarPods can be used to trigger Siri

    2. confirm if Bluetooth Message Access Profile is indeed implemented in iOS 6. (Pebble watch)

    3. how close does the silver tone on the white iPhone 5 model match the silver on Apple's Macbooks?

    4. rumors about airplay direct (airplay without an AP)

    5. rumors about airdrop (since now it has dual band wifi)

    6. rumors about the Lightning connector being able to host USB devices

    7. any word if Google will launch a separate Maps app for iOS 6? Street view has been almost indispensable for many people.

    8. how likely do you think will Apple be able to enable VoLTE for the iPhone 5 with just a firmware update in the future when carriers switch it on? I'm hoping for simultaneous voice and data on Sprint/Verizon as well as HD Voice.

    Also, I'm really looking forward to your test results on the brightness of the display and how close it comes to matching Apple's claim of covering the entire sRGB color space. It would be totally awesome if the specs match the new iPad's display.

  • drdave25 - Saturday, September 15, 2012 - link

    Great questions. Thanks for asking.

    I also wonder about the SAR for the 5. These values are quite low for the Samsung. I wonder if Apple's new design affected the SAR.
  • lancedal - Saturday, September 15, 2012 - link

    I was about to pre-order an iPhone5 for my wife on Verizon network yesterday before I read about this issue. I decided not to do it. Here is the reason why. She needs the navigation/google-search feature for driving/finding places. However, with this limitation, she can't take call while do that simultaneously.

    For me, I absolutely needs this ability. I find myself constantly on the phone while search for address/location. Additionally, without it, I can even tether my laptop for online meeting while joining conference call.

    It's not that you won't survive without it. It's that if I pay big-buck for it, I don't want to maximize its usability.

    One option for me is to go with AT&T, but that would put me back on their HSPA+ instead of LTE while doing data+voice. Then why do I pay for LTE then?

    I'm waiting for the Lumia 920 to see if it has this limitation or not. It's a bit big for my linking.

Log in

Don't have an account? Sign up now