Doc Ruby writes "Electronics Weekly is reporting that Intel has developed a new prototype chip for software defined radio. The new chip will be able to handle WiFi, WiMAX and DVB-H digital TV all on the same chip. 'This kind of chip would allow equipment to access the WiFi network in the home, automatically handover to a WiMAX network when you leave the house and also access digital TV on the move, all through one chip.' It's also a proof that the entire class of SW radios that could possibly converge CDMA, GSM and various other radio networks for opportunistic handoffs by a single device, a 'universal radio' that could use content formerly locked into a single radio type."
And presumably the drivers for this will be closed source because of that dumb FCC rule that end-users shouldn't be able to tinker with wi-fi chips because they are a dangerous radio device.
I should point out that I'm almost positive that there is no rule that says this. The companies take that position then try to back it up that way ("well the FCC might pull the device's license if..."). There are valid reasons for this (it would be easy to cause interference for only the purpose of being annoying) and good reasons against (my device means my responsibility, it's an unlicensed part of the spectrum).
However that only applies to transmitting. The is no valid reason why there would be a problem letting you configure the thing however you wanted to receive things. There are a few little bands that you aren't supposed to listen to, but if the analog part was designed correctly that would be impossible (I don't know if any of those bands are that high up). It would be simple to make it so that it's impossible (without modification of the physical circuits) to get RF though the amplifier unless it is within a little frequency set that the device is allowed in.
It IS illegal to make a device in such a way that it can be easily modified to transmit on other frequencies (seen with CBs) and I think it may be illegal for receiving too (like to listen into cell frequencies). Note that there is no solid definition on this as far as I know. You can't make it so it's "cut jumper B3 and you're set", but you don't have to go all the way to "install 12 wires, a chip, flash the firmware, hold the radio upside-down and...". Someone who is more familiar with this rules will surely point out the specifics.
I refer everyone else to section B of FCC regulations. If you can't Google it, then you don't belong here.:) In short, a device may not cause interference, but it must accept any interference it may receive due to natural or other issues that interfere with/tie into the operation of an EM-based device.
To put it short, you can receive and listen in to anything you choose to, but to transmit may be a different story. End of simple statement.
A plane is not getting it's "GPS location" from Air Traffic control, it will work it out from GPS satellites.
Perhaps there are other navigation aids you might be able to interfere with.
Not to mention that air pressure is the standard way of measuring altitude. You'll need a fairly powerful radio transmitter to interfere with that system.
I'm curious to see how long that policy lasts if the Google-backed "any device, any app" proposal wins. The market seems to be headed in that direction with the recent announcements from Verizon and AT&T.
The Google proposal is limited to the 700 MHz spectrum being auctioned off. There's not going to be any "any device, any app" going on in GSM/CDMA/FM/Ham/CB or any other licensed bands policy more than there is today.
Just like today, nobody is going to stop you from building your own or tinkering with pre-built tools as long as you're not selling them and aren't causing any interference. If you are, the FCC is just as probable to come around and "talk" as they are now.
It has nothing to do with "win"modems or reverse engineering ability. The difference between a good old hardware modem and a "win"modem is that one follows a standard and the other doesn't. An external hardware modem is a serial device (standard) that obeys the AT command set (standard). An internal hardware modem behaves like a serial port card (standard) with an attached device that obeys the AT command set (standard).
The only problem with "win"modems is that there's no baseline standard for talking to an
Instead of making 100s of different NICs that all behaved differently and required their own software drivers, NIC makers all constructed their hardware so that it would behave like a NE2000 ethernet card.
That's almost how it happened. Novell used National Semiconductors sample design for how a bare minimum card based on it's 8390 ethernet controller could be constructed. Then everyone else copied it too. I don't think it was done for compatibility reasons, it just saved you doing design work. It was also p
And you can use both at the same time? I just want to be clear on that point. Because a cellphone that can switch from GSM to CDMA etc would be useful... and it doesn't need to do both at once... but I'd sort of expect to do wifi and use my mouse at the same time...
Did you see 2.4ghz? Bluetooth works within roughly the same channel grouping as 802.11b/g. It uses frequency hopping, and in many implementations is good for about 10m so it's somewhat impractical for what they're trying to do. There are other Bluetooth classes that both have a larger range, and also a slightly better data rate. But you don't want them, so I wouldn't worry about the lack of an implementation. Worse: Bluetooth is low-power (hence the short range, incl standby modes, etc) and must be bonded w
Actually, Winmodems aren't a bad idea per se. They are cheaper to make than full modems, and you don't need to update the hardware much when new modulation standards appear since they are basically a soundcard. Microsoft basically worked out they could make something that hardware manufacturers would like because it was cheap. And rival OS vendors would hate it since the specification wasn't published.
There are still a few stages in the receiving chain that have to be analog.
In particular the first few stages of input filtering, RF amplification, and mixing all HAVE to be analog, and delicate, tricky analog at that.
Someday we may have 5Gig sample/second 32-bit floating-point A/D converters with microvolt sensitivity, but until then radio receivers can't be quite as flexible as the term "software defined radio" implies.
I thought we already did, just not a price point, size or power consumption that is anywhere remotely practical for everyday electronic items.
Sure if you have a couple million dollars to blow on your next particle detector that you are going to stick in front of your billion dollar accelerator, and can take a couple of U's up in a rack that is not going to be a problem. Back in the everyday world it is still a pipe dream.
With a resounding cry of "Ahhhhh crap." from carriers relying on clients using only their devices.
"You need to replace your phone? well then you can sign a new contract for a discount on our new..."
"I already have a device to use for it right here....picked it up online, and its not part of your expected sell/refurb/resell cycles. I believe you know what you can do with your contract..."
Course there will still be the "But don't you want 6 months of unlimited local talking and a discounted rate plan?!", still cuts out a lock in technique though.
An integrated 3-protocol chip, if produced for a reasonable price, could be just the thing to spark a new age of computing. Let's compare most "movie-future" computers to this: Easy wireless access almost anywhere you go, plus reception of live digital TV broadcasts. Sounds like the movies to me!! Granted -- the chip doesn't appear to be a ATSC decoder (I could be wrong) so current US broadcasters won't have their digital signals accessible by this chip. Additionally, wireless access in most municipalities is not existent, and most of those implementations just plain suck. At any rate, we need the hardware base to exist before the demand for "quality" municipal WiFi will grow.
Continue this development, and you may reach the point of having essentially a HTPC on a card, with TV tuning and wireless internet built in. With the new FCC mandates to open up the cable box market, Intel may open the door for competition that isn't a TiVO. And...even if no new companies step up, TiVO would probably be interested in providing Internet and TV via the same box -- something most cable boxes cannot do.
I also LONG for the day where WiFi chips/cards begin coming standard on motherboards; I prefer a desktop to a laptop any day. That, and I am tired of running CAT5 throughout my house to my multiple boxes.
Except it is an absolute pain to run Linux or any other non-MS OS on them, save freeBSD and *buntu, but other then that, its a total pain to work with wi-fi and with the devices being non F/OSS, most distros won't include them. The curse of the winmodem in the modern age.
LinuxMCE [slashdot.org] already does what TiVo does, and a lot more, by integrating MythTV with home automation, telephony, and all kinds of other stuff.
I agree with you there, but the FCC's intent was not to push LinuxMCE. Rather, the separable security directive was intended to open the market for third-party customer premises equipment (cable boxes). After 6 months, no other company has even started marketing a similar device for cable subscribers on the mass market. If this chip and a SDK were released to the public, I can see it finding a home in such a device. The integrated WiFi and WiMax capability adds a feature not available in today's CPE, namely
This device doesn't do the DSP or any other transcoding in software. It decomposes the 3 bands' different transcoder HW into components, factors out the redundant ones, then uses SW to just glue together the required signal paths. The work is done by HW. Should work quite well.
You still have a fundamental problem with radio communications - how to tune the antenna for multiple frequency bands [wirelessne...gnline.com] in a small package. Not an easy task.
You don't. You put 3 antennas in the device and switch between them. This would be problematic for other things, but in high frequencies the antennas aren't that big. If all three things use nearby pieces of spectrum (say different parts of 2.4 GHz) then you can tune the antenna for the center and put up with the losses for frequencies near the edges.
by Anonymous Coward
on Wednesday December 12 2007, @05:41PM (#21677637)
I don't know a lot about them, but I've read that Mid-Tex Cellular uses software defined radios from Vanu, Inc. From what I've read they updated from TDMA (using conventional hardware) to GSM (using quite unconventional hardware) in early 2005. Instead of installing GSM hardware at each site, they installed this software defined radio hardware. So, now they've decided to add in CDMA also for roamers; instead of having to add expensive and specialized CDMA base station hardware to each site, they just add software to the control computers (and, possibly add an extra computer to a site if it needs more processing power.)
This sounds like something Alltel could use, given in the west they run AMPS, TDMA, GSM, CDMA, and EVDO. (Western Wireless, which Alltel bought, provides the only coverage in a lot of the rural desert, and so they found the more standards they supported, the more roaming money they made... since it's desert, they didn't have problems with network congestion or whatever, so they just decided to run all standards 8-) They run CDMA + EVDO for themselves, and the rest for roamers.)
DVH-H, like most mobile targeted digital video systems afaik, is not an always-on signal. It's divided into time slices, and only uses something like one in ten slices for any particular channel. This is primarily to allow power savings by leaving the receiver powered off 90% of the time, but it might also allow you to use the same radio for TV and WiFI/WIMAX effectively at the same time.
This provides all the digital signal processing and forward error correction for these three protocols and the area is still comparable to three fixed function Asics
This isn't really software-defined radio. Software-defined implies that the protocol level processing (i.e. DSP, FEC, etc.) are performed in software or firmware rather than in silicon (and hence changeable on the fly). While it is a pretty neat chip that has the potential to ease the convergence of these wireless standards, software radio it's not.
"Software Defined Radio" isn't a precise term. It means "the least HW processing, the most SW processing" designed for flexibility in tuning multiple frequency bands and other (mostly protocol) features. This device is defined by SW running on it which band and protocol it's working in. It's a few steps beyond the trivial case of just switching among a few dedicated all-HW radios with a config signal. It decomposes the 3 band/protocol radios into components, factors out the redundant ones, and glues them to
Closed drivers (Score:5, Interesting)
Re:Closed drivers (Score:5, Informative)
No worries, mate. I'm a ham radio op... and a programmer... I'll have an open source control program along shortly.
Alternatively, I could write support into GNU Radio. [gnu.org]
Parent
Re: (Score:2)
http://www.flex-radio.com/ [flex-radio.com]
Icom also has a neat receiver-only radio: http://icomamerica.com/en/products/receivers/pc/pcr2500/default.aspx [icomamerica.com]
Re: (Score:2)
Re:Closed drivers (Score:5, Informative)
I should point out that I'm almost positive that there is no rule that says this. The companies take that position then try to back it up that way ("well the FCC might pull the device's license if..."). There are valid reasons for this (it would be easy to cause interference for only the purpose of being annoying) and good reasons against (my device means my responsibility, it's an unlicensed part of the spectrum).
However that only applies to transmitting. The is no valid reason why there would be a problem letting you configure the thing however you wanted to receive things. There are a few little bands that you aren't supposed to listen to, but if the analog part was designed correctly that would be impossible (I don't know if any of those bands are that high up). It would be simple to make it so that it's impossible (without modification of the physical circuits) to get RF though the amplifier unless it is within a little frequency set that the device is allowed in.
It IS illegal to make a device in such a way that it can be easily modified to transmit on other frequencies (seen with CBs) and I think it may be illegal for receiving too (like to listen into cell frequencies). Note that there is no solid definition on this as far as I know. You can't make it so it's "cut jumper B3 and you're set", but you don't have to go all the way to "install 12 wires, a chip, flash the firmware, hold the radio upside-down and...". Someone who is more familiar with this rules will surely point out the specifics.
Parent
To help clarify your statement.... (Score:3, Informative)
To put it short, you can receive and listen in to anything you choose to, but to transmit may be a different story. End of simple statement.
Re: (Score:2)
Re: (Score:3, Funny)
Excellent! (Score:4, Funny)
But the real question is, can I change software modes and nuke a burrito with my wireless card?
Or, even better, my roommate?
Re:Excellent! (Score:5, Funny)
Parent
Re:Excellent! (Score:5, Funny)
Parent
Re: (Score:2)
Default? No. Not enough power.
However, we could add a (highly illegal and dangerous) external amplifier on the output and do it that way.
I wonder what the resonant frequency of a burrito is....
Re: (Score:2)
Re: (Score:3, Funny)
Cool (Score:2)
Re: (Score:3, Informative)
To get FCC approval these devices will have to be not "modifiable" by the end user.
Re: (Score:2)
Re: (Score:2)
Just like today, nobody is going to stop you from building your own or tinkering with pre-built tools as long as you're not selling them and aren't causing any interference. If you are, the FCC is just as probable to come around and "talk" as they are now.
Winmodem? (Score:5, Insightful)
They sound much more interesting than Winmodems (Score:4, Insightful)
Parent
the craziness does not have to continue! (Score:2)
An external hardware modem is a serial device (standard) that obeys the AT command set (standard). An internal hardware modem behaves like a serial port card (standard) with an attached device that obeys the AT command set (standard).
The only problem with "win"modems is that there's no baseline standard for talking to an
Re: (Score:3, Informative)
That's almost how it happened. Novell used National Semiconductors sample design for how a bare minimum card based on it's 8390 ethernet controller could be constructed. Then everyone else copied it too. I don't think it was done for compatibility reasons, it just saved you doing design work. It was also p
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2, Insightful)
Uh, not quite (Score:5, Informative)
There are still a few stages in the receiving chain that have to be analog.
In particular the first few stages of input filtering, RF amplification, and mixing all HAVE to be analog, and delicate, tricky analog at that.
Someday we may have 5Gig sample/second 32-bit floating-point A/D converters with microvolt sensitivity, but until then radio receivers can't be quite as flexible as the term "software defined radio" implies.
Re: (Score:2)
Sure if you have a couple million dollars to blow on your next particle detector that you are going to stick in front of your billion dollar accelerator, and can take a couple of U's up in a rack that is not going to be a problem. Back in the everyday world it is still a pipe dream.
Cell Companies (Score:4, Insightful)
"You need to replace your phone? well then you can sign a new contract for a discount on our new..."
"I already have a device to use for it right here....picked it up online, and its not part of your expected sell/refurb/resell cycles. I believe you know what you can do with your contract..."
Course there will still be the "But don't you want 6 months of unlimited local talking and a discounted rate plan?!", still cuts out a lock in technique though.
awesome! (Score:4, Funny)
Potential in many markets for this integration (Score:3, Informative)
Continue this development, and you may reach the point of having essentially a HTPC on a card, with TV tuning and wireless internet built in. With the new FCC mandates to open up the cable box market, Intel may open the door for competition that isn't a TiVO. And...even if no new companies step up, TiVO would probably be interested in providing Internet and TV via the same box -- something most cable boxes cannot do.
I also LONG for the day where WiFi chips/cards begin coming standard on motherboards; I prefer a desktop to a laptop any day. That, and I am tired of running CAT5 throughout my house to my multiple boxes.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
This is a great idea! (Score:2)
Re: (Score:2)
Sounds great but... (Score:4, Interesting)
Re:Sounds great but... (Score:5, Informative)
Parent
Re: (Score:2)
Mid-tex cellular uses software defined radios (Score:4, Informative)
This sounds like something Alltel could use, given in the west they run AMPS, TDMA, GSM, CDMA, and EVDO. (Western Wireless, which Alltel bought, provides the only coverage in a lot of the rural desert, and so they found the more standards they supported, the more roaming money they made... since it's desert, they didn't have problems with network congestion or whatever, so they just decided to run all standards 8-) They run CDMA + EVDO for themselves, and the rest for roamers.)
Multi-tasking ? (Score:3, Funny)
Re: (Score:2)
q.v. onechiptorulethemall (Score:5, Funny)
There. It's been a while since I made a stupid joke here. Quota fulfilled for the next couple of months I guess :)
Not Really Software-Defined (Score:5, Informative)
Re: (Score:2)
Re: (Score:2)
Stupid Marketing (Score:2)
This is the real need.
Re: (Score:2, Insightful)
Re:ettus USRP (Score:4, Insightful)
Parent