Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

LSI Patents the Doubly-Linked List 328

An anonymous reader writes "Back in April, LSI was granted patent number 7028023. This is a patent on a stunning new technique in data structures ... the concept that a linked list can in fact have multiple orderings. Of course, this has been used since the beginning of (computer) time in the form of doubly-linked lists. Even if LSI wants to (somehow) claim that the doubly-linked list doesn't count as prior art, maintaining linked lists of graphical objects sorted by both x and y co-ordinates for collision detection has been done since "graphical objects" meant ASCII characters on a green-on-black screen, and has probably been widespread in databases for probably even longer."
This discussion has been archived. No new comments can be posted.

LSI Patents the Doubly-Linked List

Comments Filter:
  • Not exactly (Score:5, Informative)

    by Reality Master 101 ( 179095 ) <<moc.liamg> <ta> <101retsaMytilaeR>> on Thursday November 23, 2006 @01:07PM (#16965162) Homepage Journal

    A double linked list implies reverse pointers allowing forward and backward traversal of a list. The patent in question is more broad than that. It is talking about multiple links allowing different orderings at the same time for the same elements. So you could have a list of, say, files with links giving alphabetical order, and links giving size order, and thirdly links giving file types without having to resort the list. You might use this in a file-list screen.

    The patent is still absurd, but the summary is (as usual) inaccurate.

  • by Doug Dante ( 22218 ) on Thursday November 23, 2006 @01:23PM (#16965300)
    The macro implementation of linked lists in the Linux kernel supports multiple linked lists per structure. It probably goes back to the late 1990s.

    See Linux Kernel Linked List Explained. Note on the page where it says "You can have multiple lists!". That was baked into the kernel by good, smart engineers.

  • Re:Prior art (Score:3, Informative)

    by gmack ( 197796 ) <gmack@@@innerfire...net> on Thursday November 23, 2006 @01:29PM (#16965336) Homepage Journal
    Not quite. The patent is for objects that are indexed on multiple lists rather a double linked list as most programmers know it. It's still a common contstruct.
  • USPTO is a joke... (Score:5, Informative)

    by gustgr ( 695173 ) <gustgrNO@SPAMgmail.com> on Thursday November 23, 2006 @01:31PM (#16965366)
    This very same examiner (John Breene [patentstorm.us]) has also granted patents #6944634 [patentstorm.us] (file caching) and #6745181 [patentstorm.us] (query based search).
  • by brunes69 ( 86786 ) <[slashdot] [at] [keirstead.org]> on Thursday November 23, 2006 @01:46PM (#16965504)
    If the submitter and editor had bothered to RTFP (read the f*cking patent), they would see it is covering avery specific implementation of a linked list. The patent covers the idea of having a linked list of pointers with *two ancillary linkakges*. What this allows essentially, is for you to have a list sorted in two totally different orders at the same time... if you traverse linkage A, you get one order, if you traverse linkage B, you get the other.

    Now, I don't know if there's prior art on this, and the idea seems pretty obvious to me, but it is certainly *NOT* a simple doubly-linked-list.

  • by kansas1051 ( 720008 ) on Thursday November 23, 2006 @02:26PM (#16965814)

    I agree that this examiner is awful. The face of the patent lists all the prior art that he considered. In this case the examiner only found 13 issued patents that were relevant to the claimed invention. Importantly, the examiner did not search for or locate any non-patent prior art (such as the dozens of examples posted on this thread). This is a hallmark of crappy patent examination.

    Even more astounding, this application was allowed after only one rejection by the USPTO, which means LSI didn't really even have to argue about the prior art (software applications are typically rejected at least two times).

  • by Great_Geek ( 237841 ) on Thursday November 23, 2006 @03:02PM (#16966054)
    It looks like no one has bothered to read the patent (even the original poster who kindly included a link to it).

    The patent is NOT for a "doubly linked list". It is for multiple links to access the list in multiple orders. Note that a doubly linked list allows you to traverse the list forwards and backwards; whilc this patent claims to allow multiple different orders.

    This is a non-trivial problem that comes up frequently enough that a general solution would be useful. I have not read the patent in enough to see how they handle insertions and deletions, so I have no way to know if it actually works, and is fast, etc.
  • by DamnStupidElf ( 649844 ) <Fingolfin@linuxmail.org> on Thursday November 23, 2006 @03:59PM (#16966406)
    Give the man a cookie. Finally, someone who actually understands the purpose of patents. The whole deal, here, is that, in the past, people just kept their inventions secret if they could. The end result? Techniques could die with their inventor (read about Damascus steel for a great example of this). And, as you say, meanwhile people have to duplicate the effort.

    I don't know about that. Most of the most famous inventions were generally unprotected by patents or heavily overpatented. Printing presses, screw propellers (reference [rochester.edu]), internal combustion engines, transistors (existing patents from 1930 were very similar to the ones made at Bell [pbs.org]), and plenty of others. That's not to say that a lot of people didn't obtain or try to obtain patents, just that the general industry was able to work around the patents. Additionally, very few inventors have actually made much money for their patents. Most often, individual inventors have been crushed by rich corporations who stole their ideas, filed their own patents, and tied the inventors up in court for years. In general, big discoveries are created by the big thinkers who simply publish their ideas, and it's left up to industry to create practical implementations of these ideas. Patents can push industry to develop working implementations, but only if they are overbroad. The physical world allows a near infinite number of solutions to most classes of problems, so once a working device is patented it usually gives competitors enough information to build a similar device anyway. In reality, all that patents can do is prevent exact copying of a design. In that sense, it's very similar to copyright.

    As for software patents, I have no problem with them on the surface (well, except for those that are obvious, but that's a problem with the patent office, not patents in general). However, I think software patents should have a more limited lifespan. After all, 20 years is a *very* long time in the world of computing (just think how different things were in 1986). Something like 4 or 5 years makes far more sense.

    The reason software patents are bad is that copyright already covers the same concepts for software that patents do for hardware and machines, namely preventing the exact duplication of an invention. There is no need for softare patents because copyright law prevents competitors from exactly copying an existing solution and selling it themselves. However, there should be nothing wrong with understanding the underlying problem that needs to be solved, examining all the existing approaches, selecting the best approach, and reimplementing a working solution. In some cases, there are what can be called optimal solutions to problems in computer science, and in this case the copyright office recognizes that re-implementations of an optimal algorithm to solve the same problem may in fact be very similar, if not exactly so. The key is that they were produced from first principles and existing research and not directly copied from an existing copyrighted work. Patents work the same way (but in practice patent owners pretend they don't and file lawsuits contrary to this fact), and for instance patents on creating chemicals or medicines are merely a patent on a specific process of creating the end product, or in essence a patent on a machine (considering the entire process as a whole) that produces the end product. Someone who can build a machine to do the same thing in a slightly different way won't infringe the patent.

    Any other concept of patents (or copyrights) requires that some entity can own an idea or class of ideas, and not merely a physical representation of a particular idea. I agree with you that patent terms should be shortened (along with copyright terms) to 5 to 10 years. The rate of progress is increasing, and there's no reason to pretend otherwise by having even longer terms th
  • You're right (Score:3, Informative)

    by taniwha ( 70410 ) on Thursday November 23, 2006 @05:14PM (#16967094) Homepage Journal
    as I read the patent it's simply a patent for list elements that are in more than one list at the same time - prior art up the wazoo of course (Unix V6 from the late '70s for a start)
  • All I can say is... (Score:4, Informative)

    by mavenguy ( 126559 ) on Thursday November 23, 2006 @05:21PM (#16967164)
    ..holy sh*t, this is incredible (Well, sadly not). For convenience, here's [uspto.gov] the PTO's version of the patent, better to use because it has links to some of the cited prior art patents. Additionally, consider looking at the prosecution of the application [uspto.gov]. You can download a pdf of the "image file wrapper" which includes the examiner's action and applicant's response.

    There was a nominal rejection under 35 USC 101 [cornell.edu] as covering non-statutory subject matter, which applicant easily overcame by typical claim redrafting used in software patents. There was also a rejection under 35 USC 102 [cornell.edu] as being anticipated by the patent to Schwartz [uspto.gov]. The latter patent discloses a singly linked list and an separate array of pointers to individual items (kind of like an index?). Clearly, this is not the same as the doubly linked list of the application, and the applicant responded by pointing this out. The application was then allowed and issued.

    What was clearly missed here was the patent to Porter [uspto.gov] which discloses a "...doubly-linked list search and management method ..." Now Porter goes on to add an auxiliary array of pointers (but for a more refined use than just an index) but the basic concept of a doubly linked list is here. Even the examiner very briefly acknowledged in passing that Porter showed a doubly linked list, but obviously failed to recognize that this fully meets claim 1 (including the redrafted version); she obviously did not understand what the applicant was showing. If there are any doubts about what arrangement of data are being disclosed and claimed here then just look a Figure one in the drawings (You have to use the "Images" link at the top which will take you to a clumsy page that displays the sheets of the actual patent specification using some specific tiff format, so your browser must be capable of displaying these images).

    I'm sure there are lots of other prior art showing this plus the use of more than two lists (like Fig. 3). In any event I can't see claim 1 surviving even a cursory challenge. Anyone have $ 2,520.00 free to file a reexamination request?
  • by DerekTomes ( 1024783 ) on Thursday November 23, 2006 @11:39PM (#16970300)
    just like Coca Cola makes sure no one finds out about the "secret formula".


    Coca Cola Recipe

    Ingredients

    1 oz. Citrate Caffein
    3 oz. Citric Acid
    1 oz. Ext. Vanilla
    1 Qt. Lime Juice
    2 1/2 oz. Flavoring
    30 lbs. Sugar
    4 oz. F.E. Coco
    Caramel sufficient
    2 1/2 gal. Water


    Flavoring

    80 Oil Orange
    40 Oil Cinnamon
    120 Oil Lemon
    20 Oil Coriander
    40 Oil Nutmeg
    40 Oil Neroli
    1 Qt. Alcohol


    Directions

    Mix Caffeine Acid and Lime Juice
    1 Qt. Boiling water add vanilla and flavoring when cool.
    Let stand for 24 hours.
    :)

"Engineering without management is art." -- Jeff Johnson

Working...