TI Announces WiLink 8 Family - WiFi, GNSS, NFC, BT, and FM Combo Chipby Brian Klug on February 13, 2012 9:00 AM EST
It goes without saying that connectivity is a hugely important part of smartphones. After all, without some sort of network connection, you've basically just got an expensive PDA or PMP. Today, TI is making formal the WiLink 8 family, the newest member of its popular WiLink series of WLAN combo chips, which is built on a 45nm process. WiLink 8 adds support for GNSS (Global Navigation Satellite System - GPS + GLONASS) and NFC in addition to WiFi, Bluetooth, and FM receive/transmit like we've seen in WiLink 7 in a number of devices.
The WiLink 8 family includes 15 different discrete solution options, and TI has provided a feature comparison for those parts. The configuration options basically afford OEMs the ability to choose whether they want GNSS (which they might not if the baseband or SoC provides it), NFC (possibly for low-end devices), and a simplified WLAN-only option.
|TI WiLink 8 Series Comparison|
|Technology Option||WL189x solutions||WL187x solutions||WL185x solutions||WL183x solutions||WL180x solutions|
|Dual-band 2x2 MIMO||WL1897||WL1877||WL1857||WL1837||WL1807|
|Wi-Fi 802.11 a/b/g/n||WL1893||WL1873||WL1853||WL1833||WL1803|
|Wi-Fi 802.11 b/g/n||WL1891||WL1871||WL1851||WL1831||WL1801|
|Wi-Fi SS 40MHz (HT40)||Y||Y||Y||Y||Y|
|Bluetooth low energy||Y||Y||Y||Y|
WiLink 8 WiFi support builds on WiLink 7 by also adding both 2.4 and 5 GHz radio support, and most interestingly the option to connect using either dual-band 2x2:2 MIMO with a 20 MHz WiFi channel, or single spatial stream (1x1:1) on a 40 MHz wide channel. This is an interesting and unique feature that we haven't seen before from the other combo chip players, and I'm eager to see if OEMs opt to go for the 2x2:2 solution. Tablets are probably the most logical place for 2x2:2 considering that a larger device means better chances of getting two decently uncorrelated streams. The WiLink 8 series also includes an integrated NFC controller with support for all of the NFC forum use cases and modes, and TI tells us they've already partnered with a number of Secure Element (SE) providers (TI names Infineon and NXP in its release) as well for support.
Integrated GNSS support is also very interesting, as for a while now Qualcomm has been the only player I've seen offering smartphone-tailored GNSS receiver with support for GPS and Russia's GLONASS constellation in newer SoCs and basebands. TI tells me they also have a different approach to managing use and prioritization of GPS/GLONASS than Qualcomm, whose solution right now only uses GLONASS when GPS SNR is low. We'll see products with WiLink 8 inside in the second half of 2012.
Source: Texas Instruments
Post Your CommentPlease log in or sign up to comment.
View All Comments
Kobaljov - Monday, February 13, 2012 - linkThe "Bluetooth technology" is not too informative from technical view, so which version exactly?
RU482 - Monday, February 13, 2012 - linkWell, considering it also says Bluetooth Low Energy Technology, I'd say Bluetooth 4.0.
Kobaljov - Monday, February 13, 2012 - linkYes, but the Bluetooth High Speed is not mentioned, so maybe it's not a full 4.0 implementation just the Bluetooth Classic and the Bluetooth Low Energy integration
Kobaljov - Monday, February 13, 2012 - link4.0, in the source's detailed spec it is written (but why just there?)
Brian Klug - Monday, February 13, 2012 - linkIt's Bluetooth 4.0
Conficio - Monday, February 13, 2012 - linkI'm wondering if anybody is working/researching the use of the headphones as a second antenna?
I know that some phones use the headphone's cable as an antenna for FM reception. I wonder what would keep them from doing the same with the Wifi antenna configuration.
I'd also think that some ear piece or an additional antenna I could wear in my clothing and communicates over some distinct channel with the phone could be an interesting alternative for a second antenna to a cell phone. I would not mind having a thick check card sized secondary device in my pocket, that contains a battery and a smart antenna doubling my streams.
Feel free to educate me why those things are ludicrous ;-)
Gorgonesh - Monday, February 13, 2012 - linkThe wavelength difference between frequencies used for WiFi versus FM is why you won't see headphone wires being used for antennas. This and matching different types of headphone wires/lengths back to WiFi chip would create quite the challenge.
AndreMalm - Monday, February 13, 2012 - linkBroadcom already ships several SoCs with GLONASS support that are used in smartphones. ST-Ericsson also has a chip that should be in production by now.
name99 - Monday, February 13, 2012 - linkHi Brian,
In future when you review (or even mention) WiFi equipment, can you give details on what OPTIONAL parts of the spec are supported.
40MHz and the number of spatial streams are the headline numbers, but just as amateurs argue tactics while professionals argue logistics, so people who really understand WiFi know that what really determines your performance is the MAC features --- the PHY numbers mean nothing without MAC support.
Since (for reasons I do not understand) most of the various features that are essential to make an 802.11n device give goodput higher than 802.11g are optional, this is not a small matter. Things like:
- EDCA (is that still optional, or is it, in practical terms, everywhere?)
- Block acknowledge (ideally without delay).
- Aggregation at both the MAC and PHY levels to the maximum allowed size.
Even beyond that it would be nice to know something about how well the various "algorithmic" parts of the spec are supported by various vendors.
- Do they make a considered decision (based on recent traffic levels and the size of data to send) whether to use RTS/CTS or do they just always do it?
- How do they determine when to change modulation+coding?
- Do they intelligently switch between spatial multiplexing and ST-diversity for stations that are at the very edge of the base station's range?
- What intelligence are they using to decide between MAC aggregation, PHY aggregation, or both?
Right now basically what we learn from these announcements is:
Woohoo we support some spec (where by "support" is possibly meant we do the absolute bare minimum necessary to function on such a network and not damn thing more).
The alternative is we get reviews giving something like goodput numbers. But it is never clear from such reviews if numbers are bad because one or other side of the connection (the mobile device or the base station) simply doesn't support large parts of the spec, or supports it in a half-assed fashion. In other words, if the laptop has worked really hard to support aggregation well (rather than going for something flashier but probably of less value in real life, like 3x3:3) but is paired with a crappy base station than does the bare minimum to support aggregating clients and not a damn thing more, that is unfair in some sense to the laptop.
The only way I see around this sort of issue --- it's not ideal but it's better than nothing --- is for journalists like yourselves to be a lot more hardass about asking vendors EXACTLY which optional parts of the spec they do and don't support, and about the performance of the algorithms they are using. This is especially true (and especially shameful) in the case of aggregation where, as far as I can tell it is simultaneously true that
- this is an essential part of the n spec (and the ac spec) to get decent goodput,
- yet it is also commonly handled very poorly by many devices,
- and no reviewer event comments on it or understand that it is the reason so many devices behave like crap under 802.11n, not some random "wireless sucks and you can't trust the iEEE"
Brian Klug - Thursday, June 14, 2012 - linkThis is a really really good point, and especially with 802.11ac combo chips and as we start talking more with the combo vendors, I intend to ask those kinds of questions. Absolutely :)