Nonlinear Neural Nets Smooth Wi-Fi Packets
mindless4210 writes "Smart Packets, Inc has developed the Smart WiFi Algorithm, a packet sizing technology which can predict the near future of network conditions based on the recent past. The development was originally started to enable smooth real-time data delivery for applications such as streaming video, but when tested on 802.11b networks it was shown to increase data throughput by 100%. The technology can be applied at the application level, the operating system level, or at the firmware level."
But does this improved network performance allow me to predict if I will get a first post based on my past inability to do so?
Is anyone else slightly alarmed by this news? "Neural-net" technology that shows some degree of intelligence (if you consider making fuzzy predictions intelligence). I think that checks or governing circuits should be put in place for this kind of technology so that it doesn't get out of hand by, oh I don't know, burning out transmitter circuits or something. Remember the documentary "The Terminator"? Yeah. I do. I don't want something like that to happen.
And next time, please RTFA, m'kay?
When I see the headline: "Nonlinear Neural Nets Smooth Wi-Fi Packets" and I only understand the words nets, smooth and packets...and none of them in relation to each other... - I have to be a little concerned that my geekiness is dwindling...
The anti-salmon
This technology can increase throughput 200-800% in networks of 3 Asian people and 1 doctor.
This sounds like a scam. The CEO is a furniture salesman, the CTO was a consultant to DEC with an EE from the University of South Maine.
Words I undestood in the headline:
1.Smooth
Fuck...
the technology can be executed at any of those level to be effective, not all 3 at once. So that means linux could get support for it at the kernel level... someone could write an application for windows, and palms could use an updated firmware and all 3 would effectively take advantage of the algo.
Not necessarily. This improves throughput, but as a general rule wireless always adds 20ms to your ping. so 50% of that would still be a 10ms penalty.
I'm not a network engineer, but latency is more important than bandwidth for ping times and such.
For an example pay a half-life game, open the console and type net_graph 3. That'll show you your fps, ping, and in/out bandwith used.
There would be no reason to implement the algorithms in all three. The point is that the implementation isn't so low level or complicated that it requires wireless cards to be designed for it. It can instead be implemented in firmware, hardware, or software.
Now, a speed increase sounds good to me, but as most of my wifi usage is for internet use, and I don't think i've ever been on an internet connection faster than my wifi connection, I'd like to know if it helps with range, and I'm too lazy to RTFA.
This message is encrypted with Quad ROT-13 to protect the author's copyright under the DMCA.
I'm curious as to why they are using Neural Networks for this application? In the last 10 years or so, most machine learning applications have moved away from Neural Networks to more mathematically based models such as Support Vector Machines, a generative model (e.g. Naive Bayes), or some kind of Ensemble Method (e.g. Boosting). I suspect they used NN because the Matlab toolkit made it easy or someone in research hasn't kept up. I'd look for a paper to come out soon that improves the accuracy by using SVM.
If you're a fan of women, add me to your friends list.
I know those words, but that sign doesn't make any sense.
Give me Classic Slashdot or give me death!
Umm... it isn't so simple. You are missing the basic idea of a layered architecture. This is actually really cool that it can be implemented at any layer. Sometimes there are things that can't be done at the application layer because of the constraints created by the layers below it. For instance, it is pretty worthless to do routing at the application layer if you are using IP, because it is already taken care of at the network layer.
So to say that it is all just "software" misses the fact that there is a significant difference between how these peices of software work. It is really cool that this can be done at the application layer, because it will allow applications to be developed to take advantage of it with out even changing the drivers for your wi-fi card.
This is a big deal to me, because I live in an appartment complex that offers Internet access over Wi-Fi. Because there are so many people using it the connection is pretty flaky (due to collisions). I get high download rates, but poor response times. If this provides better collision avoidance I will get a significantly better connection (lower ping times and such).
Very often the term "neural network" is used
...
just as a selling point because it sounds
like something extremely advanced and "related
to artificial intelligence".
usually the neural network is just a
very simple, possibly linear, adaptive filter
which means that really contains no more
than a few matrix multiplications
yes it has some success in approximating
things locally, but terms like "learning"
are really misused
After RTFA (the second) it actually
seems that they did try two or three
things before, but really i wouldn't
"welcome our new intelligent packet sizers overlords"
just yet.
We learn from history that we learn nothing from history - Tom Veneziano
To me, this sounds like (in the simplest form) that this is a variant on the Tit for Tat strategy that is usually applied to the Prisoner's Dilemma.
Heres a graph that I ripped out of some lecture notes. It shows how much of a problem congestion is on 802.11b networks.
.035 Mbps per host.
http://web.ics.purdue.edu/~dphillip/802.11b.gif
For a little explaination, where it says "Node 50" or "Node 100" that means that there are 50 or 100 computers on the wireless network. And the throughput numbers are for the whole network, not per host. So when 100 nodes are getting 3.5 Mbps that's
Thanks to professor Park
Why isn't there something like this for normal internet? Even the "old days" of Zmodem's big packets if it was going well, and small packets if it wasn't, is better than the fixed MTU/MRU we're stuck with now.
It's a new way of determining the optimum packet size on the fly so that collisions, errors & retransmissions are minimized, greatly boosting overall throughput.
QED
Not gonna happen. The poster was just using random random terms that have nothing to do with this article, trying to sound smart, and is probably laughing as the post gets moderated up.
Everything the poster mentione, such as Naive Bayes and Support Vector Machines are used for static tasks, like classification, not for realtime feedback situations. They learn once and predict forever. They don't learn iteratively and keep changing. Follow the Google links I just gave and peruse the first few sites that come up if you're not sure. They are used for things like text classification, handwriting recognition, voice recognition, etc., i.e., "train once use often."
There are online methods using both the techniques you mention. The theory is usually a little more involved, so you're not likely to get a good tutorial from page 1 of google results.
Try MIT's open courseware (Machine Learning course) for some better explanations of this stuff, if you can handle the maths, ughhh.
This sounds like a great improvement to 802.11x technology...now let's open-source it so we can all benefit!
Gee, let's see how many buzzwords we can cram into a technology:
.NET, Java 2 USS Enterprise Edition, and GNU/Emacs - soon to include POP, IMAP, P2P and B2B functionality for enhanced productivity.
"Introducing iFluff/XP: An XML-based Object-oriented neural networking system that will synergize the modular components of your SO/HO WAN protocols, while minimizing TCO and giving five 9's reliability by branch-predicting streaming traffic through your SAN, NAS, or ASS.
iFluff/XP allows you to commoditize and monetize the super-size networkcide as rogue packets from black hats and white hats and clue bats compete for cyber-mindshare of your Red Hat hosts.
Secure your Homeland LAN and manage your digital rights with dignitude and affordability with the help of iFluff/XP's bytecode-based embedded operating system protocols interfacing through broadband Wi-Fi connectivity and virtual presense frameworks.
A user-friendly GUI is provided through an XSLT module interfacing to leading industry applications such as Mozilla,
When you're thinking of buzzword-compliiant, ISO9001 conformant, remotely-managed turnkey security solutions, remember iFluff.... TO THE XXXTREME!"
Oh god, my brain hurts now.
I couldn't agree more. Last summer I was working with a satellite link from a third world country. Now the pipe on those guys is pretty big, we were working with 3MBps. 24Mbps. However, latency on the tcp packets from the south pacific to space and back to sunny CA is such a large problem it slowed an asynchronous transfer to about 20KBps. I had to write a special segmented upload package to be able to send video feeds sychronously and maximize the bandwidth utilization.
In other words, bandwidth will do you zero good with a traditional tcp/ip stack if your latency is too high.
perl -e '$_="\007/4`\cp%2,".chr(127);s/./"\"\\c$&\""/gees
Saying "Non-linear neural network" is like saying "Non-purple hamster". I mean, how often do you see a linear NN? Like, never.
Interesting question. I would assume that any given existing 802.11b adapter can receive packets of any size, given that there's a protocol to packets that lets the receiver know how big they should be or when they've finished. Thus you could just deploy a new access point and get a boost from it to the computers. Similarly, you could install a new NIC in a particular PC and boost the transfer rate from it to the access point. For benefits in both directions you'll have to upgrade both ends.
if it is packet-sizing, i suppose it would only have to be on the transmitting end...so you'd basically double your upstream...and if the AP or router has it implemented for ITS upstream, then you get your full speed boost.
does not suffer from intense negative feedback as does the stock market.
I think part of the ease of predictability may have a little to do with the kind of protocols used to collision detection/TDMA in congested 802.11 nets. If they are suffciently simple a single node could outmanuver the others.
Some questions...
What is the behavior of this algorithm as the number of enabled clients increases and the bandwidth demand of the clients exceeds the channel capacity? Does it degrade gracefully? Does it unfairly compete with non-enabled clients?
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
I'm pretty sure that's not the case. Besides, if the technology you're pushing boils down to 'variable-sizing', seems like someone's thought of that before.
As far as neural networks are concerned, a sufficiently complex neural network can adapt to learn reasonably complicated functions. Backpropagation networks and radial basis function networks can make good filters and make sense of noisy data. A network that doesn't adapt its structure boils down to a few matrix operations, so it's easy to script in Matlab.
With all that in mind, shouldn't they have looked at Kalman filters?
The whole point of SVMs is that they can be used to model a linear decision boundary. They were developed to find a maximum-margin hyperplane separating positive and negative training instances, and the kernel methods to allow them to work on non-linear boundaries were a later addition.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
Specifically, you want to allow a lot more packets to be outstanding then a normal TCP connection will allow. This is a bad idea on a low latency connection. It has something to do with windows, and buffering. Also, if you use advanced IP tools to ensure that ACK's get sent before anything else, you'll be much happier.
This thread on the LKML seems to have useful information on it: LKML Thread
Kirby