Slashdot Mirror


Micron Lands Broad "Slide To Unlock" Patent

Zordak writes "Micron has recently landed U.S. Patent 8,352,745, which claims priority back to a February 2000 application---well before Apple's 2004 slide-to-unlock application. While claim construction is a highly technical art, the claims here are (for once) almost as broad as they sound, and may cover the bulk of touch screen smart phones on the market today. Dennis Crouch's Patently-O has a discussion."

34 of 211 comments (clear)

  1. The USPTO is holding roundtables by ciaran_o_riordan · · Score: 5, Informative

    The USPTO is holding roundtables with software developers to ask for suggestions. If anyone can add to what's there already, I've some suggestions on this wiki:

    http://en.swpat.org/wiki/Suggestions_for_the_USPTO_in_2013

    (But remember, the patent office has only a small role in patent policy. Most substantial changes will have to come from Congress or the Supreme Court.)

    1. Re:The USPTO is holding roundtables by h4rr4r · · Score: 5, Insightful

      Here is a simple suggestion.

      MATH IS NOT FUCKING PATENTABLE YOU IDIOTS! STOP ALLOWING SOFTWARE PATENTS SINCE THEY ARE JUST MATH.

      This should be pretty simple, but they would never accept that.

      Slashdot admins; The caps are supposed to be yelling, that is why I used them. Sometimes yelling is needed.

    2. Re:The USPTO is holding roundtables by logjon · · Score: 5, Informative

      Alternatively, since they have to follow court rulings, we could try: OBVIOUSNESS TEST FOR SOFTWARE PATENTS SHOULD BE DONE BY SOMEONE WHOSE EXPERTISE IN THE FIELD INVOLVES MORE THAN SENDING E-MAIL IN OUTLOOK. Seriously, where do they find these people? If it's software to do X, it should be examined by someone with expertise in the field of software AND the field of X.

      --
      The stories and info posted here are artistic works of fiction and falsehood.
      Only fools would take it as fact.
    3. Re:The USPTO is holding roundtables by Antipater · · Score: 2

      Is physics patentable? I mean, my new catapult design is just physics.

      --
      Everything is better with chainsaws.
    4. Re:The USPTO is holding roundtables by Theaetetus · · Score: 4, Insightful

      Here is a simple suggestion.

      MATH IS NOT FUCKING PATENTABLE YOU IDIOTS! STOP ALLOWING SOFTWARE PATENTS SINCE THEY ARE JUST MATH.

      Software patents that are just math are not allowed. You'll see that this one involves hardware, which is not just math*.

      *unless you're saying that all hardware can be abstracted as mathematical relationships, and are therefore arguing that all machines are unpatentable too?

    5. Re:The USPTO is holding roundtables by msauve · · Score: 2

      "What part of software is not math?"

      The parts you have to hire sweaty bags of meat to write.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    6. Re:The USPTO is holding roundtables by gstoddart · · Score: 2

      All computing has a foundation in math, but not all patents relate to mathematical things. They relate to trying to map physical analogs to digital things.

      Swipe to unlock? Pretty much no math there except the graphics libraries. It's a concept, but there's not exactly some mathematical formula for swipe to unlock.

      I've never subscribed to the argument that all computing is math, because as much as it affects how efficient your algorithms are, software is not mathematics.

      The problem with patents is they seem to be patenting the idea, and it takes so long for the USPTO to process the claims that by the time to they do it's an industry standard practice.

      --
      Lost at C:>. Found at C.
    7. Re:The USPTO is holding roundtables by Dr_Barnowl · · Score: 5, Insightful

      The very first test should be - ask a bunch of software guys - "If you had to do X in software, how would you do it?"

      If ANY of them gets even close the patent should be thrown out.

      That said, there shouldn't be any software patents. Asking how to improve the process of patenting software is like asking how to improve the process of circumcision. Just because you do it now, and lots of tribal elders say it's a great idea, doesn't mean it's true.

    8. Re:The USPTO is holding roundtables by AwesomeMcgee · · Score: 3, Insightful

      I think you hit the nail on the head but have the wrong idea. Yes, hardware is patentable; the way in which your hardware did something may be patented by all means. If it's something stupidly simple there will be a million ways to do it so good luck having a patent that matters. The thing you're doing being just math should be unpatentable, but the way you do it in the physical world should be.

      Think about it like this, if nvidia comes up with some phenomenal new shader technique in the hardware that blows everything else away, they should be able to patent that hardware technique, chances are if it was easy to come up with ATI would have done it so this patent is worthwhile. ATI can surely do the same thing less efficiently or in software, but the patent gives advantage how it should while not stifling completition because ATI's software that does the same shader technique less efficiently wouldn't land them in court, even a less efficient hardware design (or a more efficient hardware design, which ATI should then patent!). As soon as you take the die apart and find the identical circuit implementation in both chips you have a patent violation.

    9. Re:The USPTO is holding roundtables by Grond · · Score: 2

      MATH IS NOT FUCKING PATENTABLE YOU IDIOTS! STOP ALLOWING SOFTWARE PATENTS SINCE THEY ARE JUST MATH.

      Well let's look at claim 1 of this patent. "A system comprising: a touch screen upon which a user is to enter, by drawing, a geometric pattern in a specified direction to gain access to the system; and a processing circuit coupled to the touch screen to compare the user entered geometric pattern to a predefined geometric pattern stored in a memory."

      Certainly some parts of this can be reduced to mathematics. The geometric pattern, obviously, as well as whatever algorithm is used for comparing the input with the pattern. But no amount of math is going to cause a touch screen to appear out of thin air. And if I sit in front of a locked phone with a piece of paper and a pencil, I can do math all day and that phone will remain locked. That's because the patent is not a patent on math. It's a patent on an electronic device that happens to use some mathematical principles in order to function in a certain way.

      It's no different from a patent on the design of an airplane wing that defines the shape of the wing in terms of a mathematical function. You can analyze that function, write proofs about it, etc all day and never create an airplane wing because the math is fundamentally separable from the invention that uses it.

    10. Re:The USPTO is holding roundtables by Dr_Barnowl · · Score: 4, Interesting

      Indeed.

      Swipe to unlock for doors == a bolt.

      Swipe to unlock for GUI == ?

      Patenting GUI analogs of physical devices is an oxymoron - you're copying a user interface that already exists. The very reason you made that analog in a piece of software is because it ISN'T a new and innovative idea. It's familiar and obvious to people or there would be no point.

      If you want to patent UI metaphors, you should first demonstrate that no-one understands how to use it without first reading the manual.

    11. Re:The USPTO is holding roundtables by ColdWetDog · · Score: 3, Insightful

      Asking how to improve the process of patenting software is like asking how to improve the process of circumcision. Just because you do it now, and lots of tribal elders say it's a great idea, doesn't mean it's true.

      I was going to nominate you for some sort of award, but I am puzzled as to exactly how to proceed. Non sequitur of the month? Most inappropriate Off Topic rant of the week?

      Were you trying for anything in specific or was this a toss-it-against a Library of Congress to see if it was saluted?

      --
      Faster! Faster! Faster would be better!
    12. Re:The USPTO is holding roundtables by gstoddart · · Score: 2

      You know, my degree is in math and comp. sci, and while it's all expressable as math, writing software is in most ways nothing at all like math.

      I've known several mathematicians who couldn't ever grasp the basics of programming, and I've known more than a few guys with Master's degrees in comp. sci who didn't know much more -- because all they learned was math for theoretical stuff.

      Knowing which libraries to use, writing readable code, release management, configuration management, debugging, and dozens of other things involved in writing code takes it beyond being "just math".

      You can't separate it from math, but I disagree that it all boils down to math.

      --
      Lost at C:>. Found at C.
    13. Re:The USPTO is holding roundtables by v1 · · Score: 2

      The problem is that there is no clear line on what is hardware and software, and both can implement the same thing.

      I would disagree. Hardware that executes instructions is a physical design, and should be obvious to be patentable.

      Hardware CAN have firmware. For the purpose of comparison, the firmware should be classified as software.

      With that settled.... software is a list of instructions. It's a process, in written form. Processes can be patented.

      The question then becomes "how far do you need to deviate from a patented process or hardware design to be considered non infringing? THAT is the big problem here. "broad patents" try to define the breadth of their coverage, and frequently come down to "anything that's even remotely similar to this is ours".

      For both hardware and software, the exact implementation is obviously protected. On the other end of the spectrum, you clearly don't have a patent over the result. (unless the result is another physical, separately patentable object, such as chemicals/pharmaceuticals) You can patent a car but not transportation. Therefore you can't simply claim rights because someone else has arrived at the same result as your process. And that's what they're trying to do. It'd be like inventing a calculator and then trying to patent anything that adds. You should be able to patent HOW it's done, but not WHAT it does. Look at the wording at the start of most patents of this type.... "This defines a method and process for ...." That's how they have to word it because the law doesn't explicitly protect results. But then they always go on to explain the results in the patent. ("and by doing A, B, and C, it results in X and Y") and then they try to enforce someone else arriving at the X and the Y by a different method or process.

      But the current state of patent interpretation and enforcement is allowing results of processes to be enforced. And there's the problem.

      --
      I work for the Department of Redundancy Department.
    14. Re:The USPTO is holding roundtables by cozziewozzie · · Score: 2

      Knowing which libraries to use, writing readable code, release management, configuration management, debugging, and dozens of other things involved in writing code takes it beyond being "just math".

      Yet these are not the parts which get patented.

      What gets patented is math.

    15. Re:The USPTO is holding roundtables by gutnor · · Score: 2

      Right after graduating, the USPTO equivalent here was trying to get people to go work there without much success.

      Simply put, it is a boring job. Even worse, it is still a government job (although extremely well paid, it was like double the starting salary of the other well paid job), with all the office politic, policies and general slowness. What they would need is to hire successful professionals, people that have had to actively solve problems, that are continuously learning, ... i.e. the exact same people that everybody wants to hire. (and if the salary is huge for a new starter, the difference is inverted later in your career, as with most government job)

    16. Re:The USPTO is holding roundtables by bill_mcgonigle · · Score: 2

      Meanwhile, if between the time it is filed and granted, anyone else either files for or implements the patent, it is presumed insufficiently non-obvious.

      Flag down. Bringing logic and reason into an argument about imaginary property. 20 year penalty.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    17. Re:The USPTO is holding roundtables by msclrhd · · Score: 2

      But you will be able to look at the patent which explains how the device works in detail so someone skilled in the art can reproduce it. If it does not, it should not be granted. Part of the problem is that software patents are obscurely worded and deliberately ambiguous to apply to more than what the patent was originally about.

    18. Re:The USPTO is holding roundtables by fredprado · · Score: 2

      Patenting ideas is not allowed (at least theoretically) even in US. Ideas are not patentable, only specific implementations.

    19. Re:The USPTO is holding roundtables by mobets · · Score: 2

      Could probably reword to:
      If any of them infringe on the pattent, it should be thrown out.

      --

      It was me, I did it, I moved your cheese
  2. Everyone is screwed... by StrangeBrew · · Score: 3, Funny

    once my twist to open patent is approved.

  3. processing circuit by stevejf · · Score: 3, Interesting

    The claim still requires a 'processing circuit coupled to the touchscreen.' The disclosure also talks about a 'compare circuit.' I would think that a software implementation would not be covered by at least claim 1 of this patent. They may be able to argue software implementations are covered under doctrine of equivalents, but personally, I would think that dedicated hardware does not function in 'essentially the same way.'

    1. Re:processing circuit by Zordak · · Score: 2

      The CPU is a "processing circuit." It doesn't matter that the specification includes a "compare circuit," because it's not part of the claim. You can't just read stuff from the specification into the claims (except when you can).

      --

      Today's Sesame Street was brought to you by the number e.
  4. Android slide-to-unlock not covered by this patent by pv2b · · Score: 5, Informative

    I'm not a patent expert, although I did once watch a very informative video about how patents work. This makes me eminently qualified on the subject by slashdot standards.

    Looking at the independent claims, it looks like at least the lock screen as implemented by Samsung (starting at the unlock button, drag a certain distance in any direction to unlock) and possibly other Android phones out there is safe from this patent.

    1. A system comprising:

    a touch screen upon which a user is to enter, by drawing, a geometric pattern in a specified direction to gain access to the system; and

    a processing circuit coupled to the touch screen to compare the user entered geometric pattern to a predefined geometric pattern stored in a memory.

    Since the system on Samsung phones works no matter which direction you drag, it looks like the "slide to unlock" implementation in Samsung phones is clear.

    However, I think this patent may very well be applicable to the "pattern lock" of android phones.

  5. just wondering -- Win8 ? by cellocgw · · Score: 2

    Disclaimer: I have never come within 1.6 km of a machine running Win8. But I've seen the slick TV commercials showing people logging on by drawing shapes on the screen. If this patent in fact covers "slid[ing] in any direction" does it cover Win8 ?

    --
    https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
  6. Just hold software patents to the same standards. by Immerman · · Score: 3, Interesting

    Actually yes, it does. You can patent the *specific* hardware implementation of a task. Someone else could then do the exact same task with a different implementation and bypass your patent.

    Honestly I'd have no problem with software patents if they just followed the same rules as hardware - you patent the implementation, not the effect. Of course the versatility of software means that would render almost all software patents trivially easy to bypass, but I don't see a problem with that. Let's take real world "slide to unlock" functionality - I can think of a half-dozen different deadbolt and related designs offhand, and I bet all of the modern implementations are/were patented, and none of them violated the patents of the others.

    Would that mean you can't meaningfully patent your brilliant software idea? Almost certainly, but then ideas are *explicitly* denied patent protection to begin with.

    --
    --- Most topics have many sides worth arguing, allow me to take one opposite you.
  7. Re:They need to go by jd659 · · Score: 3, Insightful

    The problem with the software patents (or the current interpretation) is that it's not the code that gets patented, but rather the problem. In the old days, when the inventors had to submit the prototypes, there were hundreds of mouse trap patents issued. In the current "patent the problem" world we would see the wording for a mouse trap to be something close to "a device that stops a creature from free movement by using physical, mechanical, electromagnetic force in a restrain device".

    --
    There's no such thing as "illegal download"
  8. Re:Just hold software patents to the same standard by fahrbot-bot · · Score: 4, Informative

    Actually yes, it does. You can patent the *specific* hardware implementation of a task. Someone else could then do the exact same task with a different implementation and bypass your patent.

    For example, Setuid was patented by Dennis Ritchie in 1972/1979 (applied/granted) based on the hardware implementation, as shown in the patent abstract.

    --
    It must have been something you assimilated. . . .
  9. Zero value by Qzukk · · Score: 3, Insightful

    The patent has no informative properties at all. It does not explain any process or algorithms used to ie detect that a finger is moving on the screen, which direction its moving in, what shape it draws, whether the shape is "close enough" to the shape in memory etc (though to be fair claim #1 doesn't even check the shape, only that a shape was drawn, claim #2 is to check the shape and deny access if it's wrong). If all of the above is obvious to someone of regular skill in the art, then the claims should be invalid as obvious. If it is not obvious to someone of regular skill in the art, then the patent fails to live up to the Constitutional mandate to advance the sciences and arts by not disclosing how these claims are to be achieved, and if current patent law does not make the patent invalid on this basis, then patent law should be changed to comply with the Consitution.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  10. Re:Just hold software patents to the same standard by Shagg · · Score: 2

    There is already protection for the specific implementation of software... it's called copyright.

    "Software patents" are purely about protecting the generic effect, which should be invalid.

    --
    Unix is user friendly, it's just selective about who its friends are.
  11. Similar filings should trigger obviousness failure by MCRocker · · Score: 4, Informative

    First to invent vs. file conflicts could be used to raise the bar on obviousness.

    Obviousness is surprisingly difficult to determine because some of the best and most brilliant ideas are also very simple ideas that seem obvious only in retrospect. So the patent office is deliberately reluctant to interpret the obviousness constraint too rigorously.

    Recently, the US has switched from awarding priority of similar patents to the first one to be filed instead of the first to be invented. Since there is often a very long delay from filing to patent award, during which filers must not publicly disclose their idea, priority becomes an issue more frequently than one might expect.

    It seems obvious to me that instead of struggling with who has priority, the patent office should simply look at two similar patents being filed at about the same time as a failure of the obviousness test because, clearly, two different practitioners of the art came up with similar solutions to a problem. So both patents and any similar future filings should be rejected as obvious.

    This doctrine would have disallowed a lot of patents in the past including the light bulb and telephone, which, while revolutionary were being investigated by several inventors who came up with similar solutions and even filed within hours of each other!

    --
    Signatures are a waste of bandwi (buffering...)
  12. Re:Just hold software patents to the same standard by mabhatter654 · · Score: 2

    The best example by far is the Mouse Trap. There are literally thousands of patents on various devices to catch a pesky mouse in your house. You can look them all up and develop your OWN physical design that might catch a mouse too.

    Software patents are effectively a closed box with a blinky light that "catches a mouse" using various mechanisms and sensors that we don't have to fully explain or even show you. Any "box with a mouse-sized hole" can potentially be infringing.

  13. Re:Just hold software patents to the same standard by Belial6 · · Score: 2

    Honestly I'd have no problem with software patents if they just followed the same rules as hardware - you patent the implementation, not the effect.

    We already have laws protecting the specific implementation of software.In software that would be called copyright.

    Software patents are double dipping. At the very least, software developers should have to choose. Patent or Copyright. If we choose patent, then the source code should be required to be published with the patent, and receive no copyright protection. If copyright is chosen, then it is the specific recorded form that is receiving the protection and there should be no protection for implementing the same thing using original 'art'.