A little over a month ago, Qualcomm flew me out to San Diego to talk all about cellular modem, specifically their baseband lineup, testing, and later their RF and transceiver in what would become their largest RF disclosure ever. In the past few years, we’ve made considerable headway getting SoC vendors to disclose details on the CPU and GPU side of their products, and mobile enthusiasts now are starting to become increasingly cognizant of the SoC inside devices, and in turn the blocks inside that SoC. In a short term the industry as a whole went from smartphones largely being impenetrable black boxes to devices with understandable platforms inside. The days of an OEM not disclosing what SoC was inside a device at all are largely behind us, and for the most part vendors are open to discussing what’s really inside most of their silicon quite publicly.

The last real remaining black box from my point of view is the cellular connectivity side of things. So much of what drives smartphone design and OEM choice lately is, unsurprisingly, how the device gets connected to the cellular network, and baseband remains largely a black box by design for a number of reasons. The focus of this article is specifically about Qualcomm’s newest transceiver, WTR1605L, and some more details about MDM9x25 and MDM9x15.

Cellular Radio Architecture at a High Level

Before we talk about what’s new, it bears going over cellular architecture at a high level to make things easier to understand, which is something we’ve admittedly never really done. Connecting a smartphone to a cellular network is a complicated goal, but like anything there are really only a few high level functional blocks to worry about. Understanding this architecture at a high level allows one to understand how OEMs build devices with support for multiple bands and modes, and why some designs are limited to one combination of features or another. We talk a lot about cellular baseband, but really this is just one part of the entire cellular chain on a handset. There’s of course an antenna array, and after that a switch or switches, filters for the appropriate bands, and then for receive there’s the transceiver, and finally baseband. Transmit takes much the same path, but instead of some low noise amplifiers in the transceiver, there are appropriate external power amplifiers to boost output signal to a given level for each specific transmit band.

So what role do each of those play? Antenna is pretty self explanatory — handsets have anywhere from one to four cellular antennas, each tuned for a specific band or purpose. Devices with LTE must include at least two receive chains since receive diversity is mandatory, and almost all LTE devices use a 2x1 configuration with two receive chains (in order to do 2x2 MIMO to the base station) and one transmit chain. The transmit chain usually shares the primary receive antenna, thus we see at a minimum two antennas for a normal LTE handset. Simultaneous transmission modes such as SVLTE (Simultaneous Voice and LTE) and SVDO (Simultaneous Voice and EVDO) thus far necessitate an additional dedicated transmit chain as well, bringing the total to three. Occasionally an OEM will also include an additional diversity antenna tailored for a specific band, bringing it to four. The geometry of an antenna fundamentally defines its gain and other characteristics for a given frequency band (wavelength), and is a huge part of the industrial design and form factor tradeoff for handset design. Often these are competing factors in a handset.

Switches are another fundamental part of almost every design, and are used for changing paths between the antenna and transceiver, either through the appropriate power amplifier or appropriate antenna. In TDD (Time Division Duplexing) systems, the switch is also fundamentally important since it is responsible for quickly switching between transmit and receive chains since transmit and receive are on the same band. In FDD (Frequency Division Duplexing) systems, there’s the need for a duplexer which isolates the receive and transmit bands from interfering each other.

Filters (think band pass) reject everything outside a given band and isolate a specific frequency range appropriate to whatever band class is being used. The performance of these filters is a continual subject of both scrutiny and improvement, and defines the size of guard bands in-between carriers, minimize harmonics from causing interference in other bands, and so on. In LTE for example a big concern is band 12/17 and 13 coexistence on the same band, something possible only with the latest filters.

Next in the chain is the transceiver, whose role is ultimately to downconvert the incoming signal on the receive side to I/Q data which then gets sent into the baseband (hence the name baseband, this is the complex representation of the RF signal), and on the transmit side synthesize and mix I/Q data from the baseband into RF signal for transmission. Put another way, transceiver converts from RF to baseband. There are usually a number of ports on the transceiver arranged into an arrangement of high and low bands which are tuned to work best at a given set of frequencies. If you’re not familiar with what I’m referring to when I bring up I/Q data, I encourage you to check out my Veer 4G article where I explain QAM and modulation and the I/Q plot.

Finally we have the baseband, which effectively functions as the controller for power amplifiers, switches, and transceiver and handles all the demodulation of received I/Q data and modulation for transmission. In addition the baseband worries about the layers above physical required to get the phone online, for example signaling required for the particular air interface. I’ve seen people refer to this as digital baseband, baseband processor, and modem interchangeably, it’s the same part they’re referring to. It’s this baseband which, at the end of the day, converts that RF signal into bits for the AP (Application Processor) to deal with. For cellular basebands, this is also where things like voice encoding and increasingly GNSS (Global Navigation Satellite System) reside, as these tasks just end up being yet another process running on what usually boils down to an ARM CPU and some DSP running a realtime OS of some kind. At some level the modem really just is another AP running a different workload with very specific DSP onboard.

In the case of a lot of Qualcomm SoCs (MSMs), the baseband processor sits alongside AP onboard the SoC, but the same design may also be reused and exist in a discrete part as well. For example the baseband IP block onboard MSM8960 is shared with MDM9x15, and there will be another SoC which is analogous with MDM9x25.

The transceiver and baseband combination fundamentally define the air interfaces that a device will or can support, and the number and configuration of bands as well. OEMs can always add support for more bands with a switch outside, but of course switches have their own insertion losses and thus affect link budget.

So that’s a very high level overview of cellular radios today, a subject whose complexity is further increasing with the addition of more and more radios, modes, and bands for even more connectivity on mobile devices. It’s the combination of all of these components that contribute to a given device being able to connect to, say, LTE versus just a flavor of WCDMA, or one band versus another.

WTR1605 - 7 Primary Rx Ports
Comments Locked


View All Comments

  • name99 - Saturday, January 5, 2013 - link

    "The last real remaining black box from my point of view is the cellular connectivity side of things."

    There is the 4GAmerica's site which has a large number of very up-to-date and extraordinarily good white papers on the technical details of past and future GSM releases. That's one way to keep up but, like you say, it doesn't tell us what the chip vendors (or the telcos) are doing.

    I expect Qualcomm would not answer this, but is their willingness to start being a little more open a fear of Rosepoint in the future? Intel is presumably headed for their turf, and that must scare the bejesus out of them...
    I wouldn't be surprised if, as Rosepoint becomes more real, Qualcomm starts becoming a lot more flexible about just how it's willing to sell off its IP, allowing you, if you want, to buy blocks you can stick on your SOC (rather than Qualcomm branded chips), and even designing custom such blocks for you if you provide the specs on exactly what you want.
  • SydneyBlue120d - Sunday, January 6, 2013 - link

    I second the question: What Qualcomm thinks of Intel full digital radio approach?
    Another question, they added Beidou support, what about European Galileo system?
  • DanNeely - Sunday, January 6, 2013 - link

    Beidou has been operational in China since 2011, and across the asia pacific region since last month; Galileo isn't expected to reach initial operating capacity until the middle of the decade. Until last October there weren't even enough sats in orbit to begin testing it; so while Qualcom is probably working on something they couldn't've put something known to work in the current silicon. Presumably when it's closer to IOC in a year or three they'll add support for it. Until then it'd be a waste of silicon for devices that will largely be retired before it's usable.
  • toyotabedzrock - Saturday, January 5, 2013 - link

    The WTR1605 looks like a baby step that didn't really move anything forward, unless you want to get into the Chinese market a little bit.

    It really has no advantage for the US market with the single mid band diversity port since the major carriers use both the low and mid bands, while the small carriers have only mid band spectrum.
  • ishbuggy - Saturday, January 5, 2013 - link

    This is way off topic I think, but does anyone know what they use for staking on that board? The layer looks to be perfectly around each SMT component near the chip, and I am curious what they use.
  • dealcorn - Sunday, January 6, 2013 - link

    After reading the article I have a better understanding of why Anand hired you. I am not surprised that Qualcomm wants to service multiple markets with a single chip so incremental improvements to increase the number of markets the chip may address is typical market leader behavior. I do not know whether a sidebar or pod cast is the best vehicle, but a rant providing some compare and contrast between the Qualcomm baseband strategy vs the Intel strategy would be helpful. Also, it would be a good place to incorporate your preliminary read on how the digital radio stuff Intel recently demonstrated may affect the marketplace and the block diagrams.

    You must go into the weeds to establish credibility. However, once you got it, few care about the weeds. Everybody wants more red meat in the ARM vs Intel thing and this is a lovely opportunity to serve some up. Kindly share the benefit of your insight.
  • iwod - Sunday, January 6, 2013 - link

    Interesting, i was late to the article and there is only 10 comments, compared to 3 page on ARM vs Atom. People not interested in LTE / Baseband at all??

    Anyway, so do LTE UE 4 offer better bandwidth efficiency then UE 3? Since both only required 20Mhz, but UE 4 gives up to 150Mbps.

    Apart from Beidou and TDS-CDMA, WTR1605 seems like a small step, no size reduction?

    Are there any power improvement with 9x25? LTE seems to be draining battery a lot.

    So i gathered all current Qualcomm already support VoLTE, we are only waiting for carrier to support it, right? And may be off topic, why aren't carrier doing it / Faster?

    I am not sure if i am right, the more port there are, the more supported band / wireless spec there will be. It seems to be one of the reason iPhone 5 could not come with world wide LTE supported. So wouldn't ditching GSM help? ( 4G is here.... time to ditch 2G right? )

    How do WiFi and Bluetooth fits into the scenario? They are all wireless tech, why do they requires another chip? Couldn't Qualcomm fits those in?

    I remembered there was a article about Intel Digital Radio. I admit i still do not understand much of it. Any relation to this? Or is Digital Radio more on the antenna side of things.
  • DanNeely - Sunday, January 6, 2013 - link

    VoLTE increases the load on their 4g networks by reducing the load on 2g/3g; since 4g is only going to get more crowded with time while 2g is becoming a ghost town and 3g will become one in the next few years as LTE deployments are completed, VoLTE does nothing beneficial for the carriers in the short term.

    Long term it's needed to let them shut down their legacy networks; but that's at least 4-5 years out according to occasional talking points they make (and if Sprint/iDEN is any indication even farther out in the real world) which makes it not worth enabling for handsets that will probably be junked well before it happens.
  • thm82 - Monday, January 7, 2013 - link

    You forgot one point: Efficiency also matters for Voice, as long as the network is robust enough.
    In terms of efficiency: LTE is by far more spectral efficient than 2G. GSM for example needs 5 to 7 frequencies to operate one network, UMTS and LTE only 1. The carrier modulation and coding of LTE is 1.5 to 2 times more efficient than UMTS.
    In terms of robustness: LTE is as robust as GSM from a modulation and coding point of view (something UMTS is not).
    That means the same bandwidth voice codec can run on much less spectrum on an LTE network compared to GSM, while still being almost as robust against interference. In consequence, VoLTE should be very desirable for the carriers. Even in the short term. They should be able to re-farm some of their 2G frequencies even faster in case the speed up the VoLTE introduction.
  • jhh - Tuesday, January 8, 2013 - link

    Carriers have the harder part of implementing VoLTE. Since no carrier has a strictly 4G network, and generally have a larger 3G footprint than 4G, the voice traffic has to be able to be dynamically switched between the 3G and 4G networks. While this is happening for data, voice handovers are less forgiving. While the equipment to do this is all available now, to integrate it into the existing network with the same level of service requires integration testing and bug fixing.

Log in

Don't have an account? Sign up now