Firmware Content Processing
February 17, 2010
Finally a public document surface about running content processing on a chip. The story appeared in a PC Magazine Web log with the title “Kaspersky Patents Hardware Antivirus Approach.” In the azure chip search consulting world, there has been little awareness of the method of putting multiple chips on a single chip. Using this chip and onboard instructions, Kaspersky has been able to put antivirus in hardware. From my point of view, this makes clear the following trends:
- Intel showed considerable interest in content processing, search, and metatagging with its wild investment in Convera. Since that deal, Intel has been fiddling around with the idea of using hardware to handle certain types of content processing. The investment in Endeca was less about Endeca’s future in enterprise search and eCommerce and more about Intel’s gaining more insight into the computational loads of content processing in my opinion.
- A number of gizmo manufacturers, including Cisco, have been poking around in value added content processing in firmware, in devices, and in combinations. So far, not much has poked its nose from the Cisco labs, but there has been keen interest in the types of solutions that companies like Exegy have developed and for which the St Louis crowd charges big bucks.
- A number of search vendors have rolled out appliances. These include Google, Index Engines, Thunderstone, and even Autonomy. It is a a short step from a box to an engineer’s thinking about squishing text and content processing into smaller and smaller form factors.
My method in this Web log is to wait until there is a public document to which to hook my for fee research. Thanks, PC Magazine, Kaspersky, and the USPTO. More to come.
Stephen E Arnold, February 17, 2010
No one paid me to write this. Since I mentioned the USPTO, I will report non payment to this fine institution. I wish to point out that I did not comment on the news about USPTO not accepting a facsimile transmission because it was upside down. I really need a separate blog for these types of information events.