Good Luck Enforcing a Payment System Patent Claimed in Abstract Form

by Dennis Crouch

Innovation Sciences, LLC v. Amazon.com, Inc. (Fed. Cir. 2019)

Eligibility: Of the three patents in suit, the district court found one ineligible under 35 U.S.C. § 101. U.S. Reissue Patent No. 46,140 (asserted claim 17).  The patent claims an use of a “payment server” in an online transaction to enhance transaction security, and the district found “securely processing a credit card transaction with a payment server” to be an unpatentable abstract idea. The key claim step includes the following limitation:

[R]eceiving credit card payment information at the payment server to buy items from a website … “wherein the credit card payment information is received after online communication of the buyer has been switched from the website listing the items to a website supported by the payment server, wherein the switching of the online communication of the buyer is after an indication from the buyer to buy the one or more of the items”

On appeal, the Federal Circuit affirmed the holding — finding that the claim “is directed to the abstract idea of securely processing a credit card transaction with a payment server.”  In reaching that conclusion, the court noted that the claim elements are written in “merely functional, result-oriented terms” — “an idea, having no particular concrete or tangible form.” (quoting Ultramercial).   Further, the recitation of “servers” limited the invention’s use to particular area of existing technology, but did not “render the claims any less
abstract.” (quoting Affinity Labs).

Regarding the wherein clause for switching from a regular server to a payment server, the court explained that the claim is merely directed to the abstract idea of switching — not any particular implementation or system improvement.

In Alice step two, the court explained “[t]here is no inventive concept in the claim’s use of a generic payment server ‘to perform well-understood, routine, and conventional activities commonly used in industry.'”

= = = = =

In the lawsuit, Innovation Services also asserted two other patents with claims that the Federal Circuit explained “are not a model of clarity and stray from the embodiments described in the specification.”

Still, with that framework, the court chose to give the claims their express meaning — broad enough to allow for infringement.  On remand though the court suggests review of the written description and enablement requirements. (“We do not express an opinion as to whether they satisfy the
requirements of § 112.”)

 

88 thoughts on “Good Luck Enforcing a Payment System Patent Claimed in Abstract Form

  1. 11

    Transferred here because of the silly comment limit Dennis has in place:

    GregDL, definitely “confused”: it is not crazy for the patent system to award me my 20 years of statutory exclusivity for tests employing that law of nature, even if the mechanisms for measuring the correlation are old in the art

    Please try to be clear, Greg, and avoid further muddying the waters. I know it’s difficult for you because if you are clear you are liable to run smack into your own silly arguments but still … try harder.

    “Correlations” aren’t “measured”, Greg. They are “made”. They are also ineligible for patenting because they are abstractions. More specifically, they are facts.

    Section 101 does not present a per se bar to obtaining so-called “diagnostic method” claims, or claims to kits for practicing such methods. Nobody is saying otherwise.

    And, yes, it absolutely is “crazy” to hand out patents that recite only prior art “mechanisms” for gathering data followed by a step of “determining” what the gathered data “means” based on … an un-ownable fact that was printed in a patent specification or in a research article. It’s not only “crazy” but it’s unconstitutional. And it’s remarkable to hear an attorney argue otherwise. Then again, you’re not the only self-interested patent attorney willing to make the worst arguments ever so … enjoy looking like a f-0-0-l, my naïve and confused brother.

    it only makes policy sense to exclude such diagnostic technologies from patent eligibility if one thinks that it is not particularly valuable for scientists to invest the time and material resources necessary to make such discoveries

    LOL! Wow, you really have been immersing yourself in the holy texts of patent maximalism! News flash: handing out patents on correlations is hardly the only means of promoting “progress” in correlations. Patents just happen to be the worst of all such means (or among the worst) for reasons that are pretty easy for most normal people to understand. Last time I checked, people — all kinds of people — make new correlations based on observed data all the time. They do this not because they are interested in filing patents but because … as logical entities, we can’t help but do so. Handing out patents (LOL) on correlations does not “promote” better correlations. It promotes patenting, and litigation. Period.

    The Prometheus decision has done literally nothing to impede or stall progress in “better correlations.” I would wager that more correlations, including medical correlations, have been made in the wake of the Mayo v. Prometheus than in any other time in the history of the country. There is simply no reason to believe that progress in correlations will be improved in any manner whatsoever by making doctors (and their patients, in many instances) infringers for twenty years because they understand what it means when, e.g., they have Gene X and hair color Y.

    Your silly “argument” (such as it is) for taking the extreme radical step you are proposing could be used to justify handing out patents that turn people into infringers for contemplating literally any new fact, in any recited prior art context. After all, if you don’t support Greg’s idea that facts should be patented, then (according to Greg) you “must believe” that determining facts is just a total waste of time and money and not worth investing in. Sure, Greg. Seems a tad circular to me but, hey, you’re a very serious person.

    The deal is that if you (like me) believe that determining facts is valuable, the patent system’s “answer” to that belief is that we should hand out patents that promote progress in new non-obvious non-abstract tools for obtaining discoveries and not patents on the facts and natural phenomenon themselves. Handing out patents on the latter minimizes the value of patents on the former because patents on the latter turn the use of the former into a liability. It’s like trying to encourage better methods of extracting oil by handing out patents on the oil itself, where the only difference between the new oil and the old oil is the location from which the oil was drilled. That makes no sense at all, at least from a patent perspective. And it’s one of the reasons why the patent system doesn’t permit that kind of claim.

    1. 11.1

      Another carry over:

      §101 is the only statutory section capable of dealing with the (real and legitimate) problem that he is discussing

      In your own words, what is the “real and legitimate problem” with using subject matter eligibility to forestall the use of patents to protect non-obvious correlations? How did this problem arise and what solution do you propose? Assume for the sake of answering this question that the use of the non-obvious correlation is enabled and that the applicant was in possession of the specifically recited correlation as of the filing date of the application.

    2. 11.2

      Transferred here because of the silly comment limit Dennis has in place

      Hmm, you only have seven comments – typically your “count” limit is appreciably higher.

    3. 11.3

      More carryover:

      BP Alice was not new 101 law, it was an application of Mayo. A targeted solution to Mayo will impact Alice. The piecemeal analysis of Mayo needs to go.

      The “piecemeal analysis” of Mayo is just the application of logic to the issue being dealt with, i.e., a patent claim which consists of words, in a system where the applicant is not required to set forth what subject matter in the claim is in the prior art, and which limitations are new. In other words, you can’t get rid of the so-called “piecemeal analysis” (by which I assume you are referring to so-called “claim dissection”) without literally kneecapping the subject matter eligibility analysis so that it becomes totally meaningless. You say that my claim can’t be “totally in the mind”? Okay, I will recite a step requiring that the practice of the method of thinking also breathes air. Done! Your statute is satisfied. See how that works? This inherent and unavoidable issue is why the sloppy and fake “holding” in Diehr was d.o.a. the moment it was held up and cherished by a tiny class of patent practitioners, and this is why that “holding” was completely obliterated by subsequent events. The only holding that remains of Diehr is the one I’m communicating to you now: you can’t decide subject matter eligibility merely by spot-checking a claim for the presence or absence of a certain type of subject matter. The analysis has to be more complicated than the simpleton’s version of Diehr (i.e., “no claim dissection!” or “no piecemeal”!) because of the unlimited freedom the US system provides to claim drafters. Most patent attorneys can handle a very slightly more complicated analysis (at least, most of the ones I work with can handle it — but as we all know the online patent community is a special breed of s-t-0-0-p-it).

      Hard to believe that a “targeted solution” to Mayo would not extend to other types of medical diagnostics and the so-called “information-based inventions”.

      Not sure exactly what you’re driving at but nothing in the Supreme Court’s Mayo decision suggests that the principle underlying the holding is limited to “medically relevant correlations”. Getting rid of Mayo and forbidding the most basic kind of textual analysis of patent claims imaginable is a disaster for the patent system, which has been punished enough already by the demands put on it by those who insist that otherwise ineligible logic should be eligible for patenting simply because the logic is performed by an instructable logic-executing machine. Methods of solving math problems using a slide rule anyone? Why weren’t there a zillion such patents on those methods back in the good old days? Or methods of solving math problems using a calculator? Were lawyers just less creative then? Golly gee I wonder what happened.

      1. 11.3.1

        For all of your whining, YOUR treatment of the Diehr case does NOT even hold up to your own assertion of:

        The only holding that remains of Diehr is the one I’m communicating to you now: you can’t decide subject matter eligibility merely by spot-checking a claim for the presence or absence of a certain type of subject matter.

        As you do NOT take “the claim as a whole,” ALL that you are doing is that very same “spot-checking a claim for the presence or absence of a certain type of subject matter.

        That you seem unable (or unwilling) the plain logic of your own view is merely Malcolm being Malcolm.

        1. 11.3.1.1

          As you do NOT take “the claim as a whole,” ALL that you are doing is that very same “spot-checking a claim for the presence or absence of a certain type of subject matter.”

          There is no “spot checking.” The claim is first analyzed for the existence of ineligible abstractions that would not be eligible for patent protection on their own terms (e.g., mental steps, “printed matter,” facts, correlations, descriptions of data content, logic, prices, legal status, ownership status, privacy status, etc). If there are no such abstractions, then the claim is analyzed for steps involving the detection of natural phenomenon. If neither of those things exist, then there is no subject matter eligibility issue.

          If those issues are present, then the next step of the analysis is to determine if there are other elements in the claim that rescue the claim from ineligibility. Specifically, the claim is analyzed for the existence of new and non-obvious eligible subject matter, described in objective structural terms that distinguish that subject matter from the prior art or (in the case of a method) terms that describe a non-obvious physical transformation of matter.

          None of this is “confusing” or difficult for most of us. You can, of course, pretend that it’s confusing by acting like a f–ked in the head id-I-0-t which seems to be a specialty of certain folks around here (you especially).

          1. 11.3.1.1.1

            You are STILL parsing and not taking the claim as a whole.

            What do you think that “spot-checking” entails?

            You “spot check” and then act differently based on the “spot-checking.”

            F
            A
            I
            L

            1. 11.3.1.1.1.1

              You are STILL parsing and not taking the claim as a whole.

              None of the elements in the claim are being ignored, nor is the relationship of any of those elements to each other being ignored. Simultaneously, no element on it own is capable of rendering the claim is ineligible.

              Beyond that, “taking the claim as a whole” is an utterly meaningless phrase. So please do everyone a favor and shove up it as far up your f–king @ h0le as humanly possible, okay? Thanks, Bildo.

              1. 11.3.1.1.1.1.1

                Except for the fact that you are not doing anything remotely close to that paragraph of yours (not the last, as that appears to be more in line with your usual Accuse Others meme).

    4. 11.4

      BP: why is Damadian missing from the MRI Nobel? Because he enforced his patent claims

      LOL Who told you that? And what on earth does the Nobel Prize have to do with subject matter eligibility?

      his patent claims … would not exist because they would be ineligible under Mayo

      Oh, LOL, let’s see them! And let’s see your “analysis.” I’m sure you’ve thought in great depth about it, and about the prior art, too. You’re a very serious person! Would love to hear how Kary Mullis fits into this deep thesis as well.

      1. 11.4.1

        Would love to hear how Kary Mullis fits into this deep thesis as well.

        Interesting guy, this Mullis:

        link to en.wikipedia.org

        Of course, Malcolm’s retort here is merely replete with rhetorical fallacies, and goes deep into the weeds AWAY FROM what BP is actually talking about.

  2. 9

    This blog’s tolerance of some people has really diminished much of its positive value.

    I’m quite surprised by Dennis’ tolerance for it.

    It seems to resemble the first two weeks of first years crying about what they want the law to be…

    A few have turned most away from providing meaningful comments.

    It’s a shame.

    1. 9.1

      If you prefer a heavily moderated hugbox you can easily find it elsewhere among the patent related blogs.

      Personally, the effort it takes skip over comments from certain posters is worth it to not be posting under viewpoint partial moderation.

        1. 9.1.1.1

          that has nothing to do with my comment.

          Sure it doesn’t, snowflake. Let’s hear your “meaningful comments”! You are a very serious person and totally aren’t looking for that special place where you can simply express your feelings about how “bad” a Supreme Court or CAFC case without any reasoning whatsoever except that your favorite kind of patent claim got tanked and oh by golly it’s all so unfair when that happens to Joe Everyday Person (like you).

          1. 9.1.1.1.1

            Brush aside the mindless ad hominem, and yet another post by Malcolm that says nothing and that adds nothing.

            It is easy to see here that Malcolm’s feelings are pr1cked, and that he is merely responding based on his lack of control of those feelings.

      1. 9.1.2

        Ben appears to have a certain blog in mind, but without more (particularly, exactly which blog), it is not really possible to give any weight at all to Ben’s comment.

        Further, this blog is moderated, although the “moderation rules” are certainly not evenly or objectively applied (AND notwithstanding that slant, a certain singular person remains the most expunged and biggest blight on the boards — hint: in the DISQUS day’s, this was the person that Ben “upvoted” on the most consistent basis).

        Tell us Ben, which blog is it that you consider to be a “heavily moderated hugbox.”

        1. 9.1.2.2

          biggest blight

          Says the path 0l 0gical li @r with extreme narcissist personality disorder.

          1. 9.1.2.2.2

            Tell me Malcolm, which poster has had the most posts removed for being inappropriate?

            More posts than anyone else.
            More posts than everyone else combined.

            And — as I have challenged you before (and you have always NOT delivered), show me a single L I E that I have made. This post of yours is nothing more than YOUR number one meme of Accuse Others Of That Which Malcolm Is – in your own inimical Trump style.

      2. 9.1.3

        If you prefer a heavily moderated hugbox you can easily find it elsewhere among the patent related blogs.

        Come Ben, where did you run off to? Why not be specific about which blog it is that you feel is a “heavily moderated hugbox”…?

        So while I certainly agree*** that “the effort it takes skip over comments from certain posters is worth it to not be posting under viewpoint partial moderation” — your PREMISE remains unestablished.

        *** and note here, that the agreement is in merely the ease of effort and NOT that actually skipping over comments from certain posters is AT ALL a wise move. THAT type of attitude is sure to engender just as much of a group-think, LACK OF CRITICAL THINKING mode that you appear to want to denigrate.

    2. 9.2

      A few have turned most away from providing meaningful comments.

      Have you provided a meaningful comment here, snowflake?

      Here’s an idea: go to Big Jeans Echo Chamber and both of you whining crybabies can s-ck Big Jeans off together. It’ll be a meaningful experience for all three of you, since you plainly have a lot in common. Ask me if you need more explanation.

      1. 9.2.1

        That would be you and Bildo, snowflake. Just in case you were “confused” about that (“confusion” seems to be the most shared characteristic among today’s oh-so-serious and concerned patent attorneys).

  3. 8

    SCOTUS says:

    “First, we determine whether the claims (ALL the claims) at issue are directed to” a (one) patent-ineligible concept (singular — one again).”

    Yet, the CAFC; claiming to follow SCOTUS; says:

    “the abstract idea of securely processing a credit card transaction with a payment server.”

    and

    “the idea of switching to a more secure server for payment processing.”

    Meaning the CAFC (this panel) incorrectly posited not the required — and expressly limited to one — TWO alleged abstract ideas / concepts.

    With a hat tip to Britney … they did it again:

    link to youtube.com

    Congress can’t stop this innovation, job-and-company killing foolishness soon enough.

  4. 7

    “In Alice step two, the court explained “[t]here is no inventive concept in the claim’s use of a generic payment server ‘to perform well-understood, routine, and conventional activities commonly used in industry.'”

    Hey lookie! Its abstract because its old, again.

  5. 6

    the recitation of “servers” limited the invention’s use to particular area of existing technology, but did not “render the claims any less abstract”, quoting Affinity Labs

    Note that in a logical world — one without special ad hoc judicial activist exceptions created solely to satisfy an industry group and its whining entitled attorneys — this straightforward reasoning leads directly to the correct and desirable result: ineligibility of all methods/apparatus that rely on existing programmable computers to carry out logical operations on data.

  6. 5

    Good Luck Enforcing a Payment System Patent Claimed in Abstract Form

    No doubt.

    For more 101 laughs, see the hilarious claims at issue in the Symantec case that the CAFC wrote about today.

    The Beaver: “Gee whiz, Wally, how should we check whether a file contains some “harmful” code in it?”

    Wally: “I dunno, Beav. I guess you use a file scanner to scan the file and a harmful code determiner to determine if there is harmful code.”

    The Beaver: [writes down claim 1, as Wally describes it] “Golly, Wally! You’re swell!” [runs to patent office]

    Wally: [shakes head and smiles]

    1. 5.1

      MM how do you write a claim in abstract form? So a claim that is enabled and satisfies the WD is abstract. Makes no sense. No real engineer would say such a thing and no real attorney would say such a thing.

      1. 5.1.1

        And try to remember if you attempt to formulate an answer that being enabled means that anyone skilled in the art can make an apparatus.

        So there is a machine that reads on the claims. The machine was built by anyone skilled in the art. But somehow that machine is abstract. Or is it the claims that are abstract. So words that enable anyone skilled in the art to build the machine are abstract. OK. Total gibberish from Alice and a bunch f’ing wan kers. Thanks Lemley and Obama.

        1. 5.1.1.1

          If “being enabled means that anyone skilled in the art can make an apparatus” was true – fully satisfying 112 and its case law – a claim with no unconventional elements would not require any patent specification or drawings at all! Just a one sentence statement that “anyone skilled in the art can make this.” It would be an unusual looking patent, and save lots of work for patent attorneys.

          1. 5.1.1.1.1

            Cheap shot Paul. That may apply to only a element of the claim and additionally more likely what happens is that all those embodiments known to the anyone skilled in the art is added on to the embodiments that are enabled by the specification.

      2. 5.1.2

        a claim that is enabled and satisfies the WD is abstract. Makes no sense. No real engineer would say such a thing and no real attorney would say such a thing.

        Are you still high from last night?

        being enabled means that anyone skilled in the art can make an apparatus

        An apparatus … like an apparatus that holds sheets of paper with printed text on them, such that the paper can be lifted and “turned” with a finger, thereby allowing the text to be read and understood by a human or machine. Stay with me, grasshopper! This is going to get real deep for you real fast.

        somehow that machine is abstract. Or is it the claims that are abstract.

        It’s the allegedly inventive subject matter that is abstract. For example, the apparatus we call a “book” is in the prior art but if you were the first person to conceive of and reduce to practice that invention (constructively or “actually”) you could get a patent on it. But you can’t get a patent on a “new” book based entirely on, e.g., the “non-obviousness” of the text that you print on the book’s pages. And it doesn’t matter how useful that text is, and it doesn’t matter what level of detail with respect to that text is recited in the claim.

        This isn’t difficult stuff. Sure, courts sometimes are sloppy when they right their opinions but the fundamental principle is pretty easy to understand (and is true throughout the world, in every country’s patent system). Heck, even Dennis understands it. Although he’s definitely stopped talking about it, presumably because there is a conflict of interest he is forced to struggle with.

        1. 5.1.2.1

          MM>>>It’s the allegedly inventive subject matter that is abstract.

          Show me a cite for that. There is no mention of this in Alice. And you have just made this up.

          1. 5.1.2.1.1

            That is just Malcolm attempting his age old parsing of a claim and applying eligibility at a piece part level only.

            (Cue the Big Box of Protons, Neutrons and Electrons put-down)

      3. 5.1.3

        Night Writer asks:

        how do you write a claim in abstract form

        Let’s pause a moment and reflect on the question.

        The question (heavily) implies that there may be a mere “form” of a claim that itself is “abstract.”

        Is that even a real patent law question?

        Does it not smack if the very “vice” that the Supreme Court has used as an excuse for their scrivining? (as the Court sua sponte decides that claims in a particular form nominatively meet the legal requirements as set out by the Constitutionally designated branch of the government, but are deemed — by the officious Court — to be “merely of form”)…

        (I am also surprised to have not yet seen our pals Marty and Random make any comments, as this fanciful frolic sounds along Marty’s partition/insertion of yet another (undefined) use of the word “abstract” — without regard to the patent law notion of “ladders of abstraction” – as typically blundered by Random)

  7. 4

    >Good Luck Enforcing a Payment System Patent Claimed in Abstract Form

    Claim in abstract form. We have reached new levels of new speak. There is no meaning to these words. An abstract is something like build a machine with fewer parts that operates the same otherwise. That is abstract.

    >>Claims that are enabled and satisfy the WD requirement cannot possible be abstract.<<

    Psychotic nonsense from anti-patent lowlife.

    1. 4.1

      Claims that are enabled and satisfy the WD requirement cannot possibly be abstract

      Is this your proposition, Night Wiper? So if I claim

      “A method comprising the step of adding two numbers, wherein the numbers are 8,533.398 and 10,324.094.”

      does that fail enablement or written description?

      How about the claim “A correlation, wherein said correlation is determined using a correlation determination means, wherein said correlation is a correlation between the presence of a mutation in the gene encoding ArxIV and the likelihood of armpit cancer.”

      Assume the “means” is described in great detail in the specification. Does this fail enablement or written description?

      Explain your answers. I’m sure you’ve thought a lot about this already. You’re a very serious person!

      1. 4.1.1

        MM >“A method comprising the step of adding two numbers, wherein the numbers are 8,533.398 and 10,324.094.”
        >does that fail enablement or written description?

        You tell us MM what you think. Make your own arguments.

        1. 4.1.1.1

          It doesn’t fail either enablement or written description. But it is surely an abstraction.

          Oh but wait! “Adding two numbers is the essence of electronic structure”! So totally not an abstraction. At least that’s what we were told by a judge who resigned in disgrace on the famous day when he teamed up with a mentally incompetent high-on-his-own-supply d 0 0 fus by the name of Giles Rich.

          1. 4.1.1.1.1

            That’s a pretty strawman there, Malcolm.

            Are you really trying to say that there is zero tie to admittedly different functional capability to an exact same configuration of the system (and your attempted parsing OUT of that system of the design-optional “ware” of software?

            1. 4.1.1.1.1.1

              Are you really trying to say that there is zero tie to admittedly different functional capability to an exact same configuration of the system (and your attempted parsing OUT of that system of the design-optional “ware” of software?

              I believe he’s trying to counter the absolutely insane categorical statement that “Claims that are enabled and satisfy the WD requirement cannot possibly be abstract”

              That’s a pretty strawman there, Malcolm.

              It only appears to be a strawman because the actual argument Night made is so ridiculous. He didn’t generate a crazy situation, Night claimed a crazy situation. Obviously your mind is capable of doing things (i.e. it would meet 112a for a non-zero amount of methods) and obviously things performed in your mind are abstract, so categorically stating that meeting 112a inherently means no abstraction is clearly wrong.

              1. 4.1.1.1.1.1.1

                I believe he’s trying to counter the…

                Really? If so, he [George Carlin filtered word for “opposite of succeed] in spectacular fashion. – That this particular word draws the “will not post filter” is a truly bizarre editor’s mechanism.

                It only appears to be a strawman because..”

                Wrong.

                There is NO “appears because,” as Malcolm IS using a strawman.

                He may be attempting to use the strawman to counter something, but that does not change the fact that he IS using a strawman.

                Obviously your mind is capable of doing things (i.e. it would meet 112a for a non-zero amount of methods) and obviously things performed in your mind are abstract,…”

                You confuse and conflate things here — think “anthropomorphication” and claim as a whole.

                Just because a claim MAY have a corollary that absent some claim element may be moved (as in, goalpost moving) to reflect a situation in which the corollary may be performed in the mind, does NOT make the original to be “abstract” (even as the Court has refused to actually bother defining that term as they use it).

  8. 3

    The irony. “The Current Wars” by 101 Studios. A film about Thomas Edison and Nickolas Tesla both of whom would not be able to get patents today and both of whom would be categorized as patent trolls by the lowly likes of Lemley.

  9. 2

    Innovation Sciences, LLC v. Amazon.com, Inc. (Fed. Cir. 2019)
    Finally, 101 remand instructions for the district court to also consider 112 enablement requirements, especially for “merely functional, result-oriented” claim elements. But will they now finally really encourage and sustain S.J. on that issue on a regular basis? Especially since it should be the judge, not a jury, reading and interpreting the claim elements vis a vis their patent specification enablement, if any, per Markman.

    1. 2.1

      However, that 112 issue may never get decided since the part of the lengthy decision below requiring remand was “we vacate the judgment of noninfringement as to claims 35–60 because the stipulation does not specify whether our affirmance of all but one of the appealed [claim] constructions is dispositive.”
      BTW, in view of the obvious large attorney fee expenditures here, why was a CBM proceeding not filed?

    2. 2.2

      Paul >>>“merely functional, result-oriented”

      Except in reality all of us that have been real engineers and all of us that work with real engineers on real inventions know that there is no such thing. That a person of ordinary skill in the art (or anyone) would view functional language as representing the set of all known solutions in view of the specification.

      The propaganda machine against patents is in full swing.

      1. 2.2.1

        What does being a “real engineer” have to do with proper claiming? If someone wants to state a claim limitation in functional language “representing the set of all known solutions in view of the specification,” they should use 112(f) and identify “all known solutions.” It it not permissible to delegate to a POSITA (or anyone) the task of researching “all known solutions” in order to interpret claim limitations.

        1. 2.2.1.1

          It is not permissible to delegate to a POSITA (or anyone) the task of researching “all known solutions” in order to interpret claim limitations.

          Your anti-patent bias is tiresome.

          /Bildo off

        2. 2.2.1.2

          Non Sequitur II >>s to state a claim limitation in functional language “representing the set of all known solutions in view of the specification,” they should use 112(f) and identify “all known solutions.”

          This just isn’t possible. There are too many ways to solve the problems. I have given concrete examples of this, e.g., a voltage differentiator circuit, and have quoted from textbooks that are used at MIT that say expressly that functional language is used to represent all known solutions.

          You simply are not dealing with how a POSIT or an anyone skilled in the art would interpret a functional claim element.

          1. 2.2.1.2.1

            I have given concrete examples of this, e.g., a voltage differentiator circuit, and have quoted from textbooks that are used at MIT that say expressly that functional language is used to represent all known solutions.

            The alleged novelty of the claim is the function. There is no known solutions other than those specifically identified in the spec, which is none.

            Regardless, even if there was a known solution, that doesn’t change the fact that known solutions is not the same scope as all solutions. That was the entire point of Morse – He invented on basic means of communicating information but his claim to the function would have read on the modern computer.

        3. 2.2.1.3

          >It is not permissible to delegate to a POSITA (or anyone) the task of researching “all known solutions” in order to interpret claim limitations.

          This is a red herring. The POSITA understands the scope of the claims. The POSITA knows all these solutions or knows that if they think of a solution to build a product that it is a known way. Your argument is against the reality of what a POSIT is.

          I’ve written real claims to real electronic devices that have been licensed for of millions of dollars to the top international corporations. That will not pay if they can design around.

          A patent application that included all the known ways of solving a function would get to be over 1,000 pages. Probably realistically it would have to be 5,000 pages.

          Plus—your argument is that a claim scope should be less than the scope of enablement, which means by definition that there are embodiments that are enabled but not included in the scope. So trivial to avoid infringement.

          1. 2.2.1.3.1

            NW:

            To be clear, this is a hypothetical, and I am not saying this IS the law.

            What would you say to a system where the scope of the claim was limited by what was obvious in view of the prior art and the filed specification at the effective filing date?

                1. I did not take you to intend a slight toward NW. I thought that you meant a slight toward the patent system. I was saying “ouch” on behalf of the existing regime.

                  In a sane patent system, the scope of the grant should depend on “what was obvious in view of the prior art and the filed specification at the effective filing date.” If—as you say—such is not the law, but merely a hypothetical, that is a rather damning characterization of the actually existing U.S. patent system.

                  Did I misunderstand the upshot of your 2.2.1.3.1?

                2. I don’t think so, but I am kinda surprised that you’d agree with the idea. So perhaps I am not being clear.

                  I’m basically imagining there being an infringement defense of the-patent-and-prior-art-didn’t-make-obvious-my-product-at-the-time-of-filing.

                  As far as I’m aware this is far from the current law, and the last time I brought it up the patent practicioners in the discussion recoiled. Some posters here seem to even cherish the ‘principle’ that the gun inventor is beholden to the bow inventor for the term of a projectile-shooting-device patent.

                3. I am kinda surprised that you’d agree with the idea.

                  You are surprised that I would agree with an aggressive use of §112(a) to police over-broad claiming? I cannot imagine why.

                  I have said ~1000 times on these boards that I think that the courts should be much less aggressive in their use of §101 and much more aggressive in their use of §112 to address exactly the problems that are currently policed with §101. I know that you have seen me make these arguments.

                  Some posters here seem to even cherish the ‘principle’ that the gun inventor is beholden to the bow inventor for the term of a projectile-shooting-device patent.

                  Yes. Les, in particular, is noted on these boards for making that argument. I have taken issue with that argument. I am certainly not on board with the idea that the bow inventor should get royalties from the gun market.

                4. Fair enough. I meant no offense, and I don’t remember that specific dialog with Les. But there is a difference between what I’m suggesting a thorough application of 112(a).

                  112(a) never asks obvious-in-view-of-spec.-and-prior-art. It asks “is it enabled?” and “would a PHOSITA recognize inventor as possessing?”. These questions are decoupled from obviousness and we are not nearly so comfortable resolving them as we are obviousness.

                5. No offense taken. My apologies if my response read as if I were miffed. Two further thoughts:

                  1) I think that the distinction that you are positing between “obvious” and “enabled” is thinner than you suppose. An “obvious” variant on the disclosed embodiments is (by legal definition of “obvious”) a variant that requires no more than ordinary skill to effect. That is to say, it is a variant that does not require “undue experimentation” to effect. In other words, truly non-obvious variants are—by definition—not enabled by the spec, and conversely, all variants that are enabled by the spec are—by definition—obvious variants. As such, if a claim reads on subject matter that is not obvious in view of the disclosure and the state of the art at the time of filing, then the claim necessarily extends beyond the scope of enablement.

                  2) I think that the defense to infringement that you are describing is known in the case law as the reverse doctrine of equivalents. DePuy Spine v. Medtronic Sofamor Danek, 567 F.3d 1314, 1338 (Fed. Cir. 2009). This doctrine almost never gets invoked anymore, and to my mind this is all to the good. The reason why almost no one ever invokes reverse DoE is that a claim that can be evaded by rDoE is invalid (see #1 above) on written description and/or enablement grounds. Better just to tank such a claim, rather than give one individual defendant a pass on non-infringement grounds, but leave the claim enforceable in future suits against future defendants.

                6. I have said ~1000 times on these boards that I think that the courts should be much less aggressive in their use of §101 and much more aggressive in their use of §112 to address exactly the problems that are currently policed with §101. I know that you have seen me make these arguments.

                  I too am a fan of 112, but when a pure-112a stance gets interrogated it turns out you need a 101 logical jump regardless of whether you call it 101 or not..

                  Enablement/WD of an overbroad scope largely depends on post-hoc counter-invention. My gun fits within your claim scope but isn’t described or enabled by your spec pertaining to bow construction, so my gun proves your functional claim is overbroad. Remove the gun from that equation and the argument falls apart.

                  The more important issue is the *threat that the gun could be developed in a pre-gun world*. In other words, if I am an inventor and I know of the functional claim scope, I won’t seek to develop the gun, because I know that selling the gun invites an infringement suit I might lose. 112a needs to work proactively rather than retroactively. A given disclosure (“here is how you build my bow”) can only invite a scope of a certain breadth before it can be rejected purely by being too dangerously large for the given disclosure. Is a picture claim necessary? No. But every limitation one strips makes it more and more likely that there exists some totally different and unposited means that fits within the claim scope. The final result of this is the mere functional scope.

                  It is impossible to set a real line about “how far is too far” in a proactive manner. It necessarily requires someone’s judgement to just be “nah, you’ve gone too far.” Whether you go to far because you’ve gone “abstract without significantly more” or you go too far because “one of ordinary skill would not believe you to be in possession of the full scope of the claim” or “failing to prove the full scope of the claim can be practiced without undue experimentation” it’s really just a statement that we are uncomfortable with your scope chilling future research.

                  Does a bow disclosure mean that undue experimentation is needed to generate a gun? Sure. Does it mean that one of skill would not believe one to possess a gun? Sure. Does it mean that the function of firing a projectile is abstract? Sure. But they’re all terms that mean the same thing – You’ve got a bow, and (looking forward from the patenting of the bow in a gun-less world) we need to protect the desire to research other projectile-firing inventions that you have not invented and have not disclosed from the chilling effect of an overbroad scope.

                  Virtually every 101 rejection can be rephrased as “Given that science is inductive and you are only in possession of one/a few means of achieving a result, how is it anything more than mere speculation that you possess all the means of achieving a result such that we can reward you with that scope?” If you put the burden on the applicant to prove at the time of filing (which is where it should be) that their means fills the scope claimed, you’re essentially engaging in a 101 analysis, whether you call it a 112a rejection or not. The difference, of course, is that (and here I will only speak to what I know since I know we have disagreed before) *some parts* of the office merely accept the statement that the applicant possesses every means of achieving the result, when simple logic would say that’s extremely unlikely to be true.

                7. If you put the burden on the applicant to prove at the time of filing (which is where it should be) that their means fills the scope claimed, you’re essentially engaging in a 101 analysis, whether you call it a 112a rejection or not.

                  I think that I know what you are trying to say, and I think that I even (broadly) agree with it. I also think, however, that you are using some confused terminology, and that the confusion in terminology is covering over a weakness in your argument that merits exploration. In particular, I think that it is not helpful to speak of “§112 analysis” and “§101 analysis.” It would be more helpful to speak of “written description analysis,” “enablement analysis,” “clarity analysis,” subject matter eligibility analysis,” and “utility analysis.” These various separate and distinct analyses can be canvassed under the sloppy short-hands of “§112 analysis” and “§101 analysis” but the conflation of meaningfully distinct legal requirements that occur when one uses those short-hands can lead one down wrong holes.

                  When one says that an overly abstract claim to (e.g.) a “processor configured to intermediate an escrow exchange” fails §112(a), it is straightforward enough to understand how and why the over-abstraction runs afoul of §112(a). Section 112(a) requires a “written description” of the invention. To the extent that one claims “a processor configured to…,” the claim reads on all possible configurations. Therefore, if one has not described all possible configurations, then it is intuitively fair when the judge (or the PTAB) tells you that your claim does not conform to the statutory requirements.

                  By contrast, when one says that such a claim does not survive the “§101 analysis,” the intuitive justice of this assertion is far less clear. Section 101 sets out three substantive requirements: (1) the claimed invention must be “new”; (2) it must be “useful”; and (3) it must fit into one of four statutory categories. It is not intuitively clear how “a processor configured to…” fails any one of those three (assuming that the [X] it is configured to do is genuinely novel when done on a computer). Rather, in order to say that such a claim “fails §101,” it is first necessary to read into §101 a host of requirements that never actually appear in §101, the exact contours of which have never been entirely clear, and never will be.

                  As it happens, U.S. law is such that we all know (for reasons that are not at all clear) that the Supreme Court has chosen to read these (so-called) subject matter eligibilty exceptions (including the so-called “abstract idea” exception) into §101. For all that, though, the Court could have just as meaningfully read the exceptions into §100, or §102, or §111, come to that. Once one starts inventing requirements untethered to any actual statutory text, it is somewhat arbitrary into what chunk of the text one chooses to pretend that they have been inserted.

                  In other words, when you say that “you’re essentially engaging in a 101 analysis, whether you call it a 112a rejection or not,” what you really mean is “you’re essentially engaging in a 101subject matter eligibility analysis, whether you call it a 112awritten description rejection or not… .” I suppose that, within the constraints of current legal categories, that is true as far as it goes. The problem is, as I mention above, this analysis is intuitively unjust. It may well be absolutely necessary (we both agree that one cannot go around handing out claims that cover the gun to the man who has only invented the bow) to have a legal mechanism to effect this check on claim scope, but the way one goes about effecting this check is not clear to the intelligent inventor who reads the statute in good faith.

                  Therefore, when this good faith inventor finds his or her claim being tanked supposedly under §101 as “abstract”—when §101 does not say a dashed thing about—the inventor has a legitimate reason to feel slighted and wronged. It is counterproductive to a patent system for the outcome of patent disputes to appear unfair and arbitrary to intelligent inventors who read the statutes in good faith.

                  It would, therefore, be much better if we purported to locate the statutory ground for this denial in a part of the statute that has some logical textual basis (“shall contain a written description”) to support such a denial, rather than one that lacks any textual connection whatever to the rejection being made. We really should call this a §112 rejection, even if historically we have (for mysterious reasons) been wont to treat it as a §101 issue.

                8. it turns out you need a 101 logical jump regardless of whether you call it 101 or not..

                  LOL – that “need” is ONLY if you are trying to arrive at your desired ENDS without regard to the actual law as written (and intended) by Congress.

                  Hence, as typical, Random gets MULTIPLE sections of law wrong in order to arrive at his “needs” being fulfilled.

                  Also, as typical, inte11ectual coward Greg would rather play patty-cake with someone so obviously wrong on the law in order to arrive at Greg’s “desired Ends.”

                9. In particular, I think that it is not helpful to speak of “§112 analysis” and “§101 analysis.” It would be more helpful to speak of “written description analysis,” “enablement analysis,” “clarity analysis,” subject matter eligibility analysis,” and “utility analysis.”

                  Yes and no. See an analysis entirely changes based on who is prosecuting and who is arguing in rejection, rather than the objective scope, which is a problem.

                  For example, if one comes up with the structure of a bow, but claims a machine that fires projectiles, one may argue that this is a 112b violation, since a machine that fires projectiles fails to point out and particularly claim the bow with reasonable clarity. But that attack has an iron-clad defense – “I am not seeking to claim the bow, but the function.”

                  It requires some knowledge of the genesis of the law – prior to 52 the “I’ve invented one thing within a much larger claimed scope” situation was taken care of with a combination of 112b (Perkin’s Glue, Wabash) and 101 judicial exception (Morse). Enablement wasn’t invoked and WD hadn’t been “invented” yet. Post-52 the CCPA and CAFC essentially neutered 112b and ignored judicial exceptions, which required them to invent WD in order to prevent runaway claim scopes.

                  I use 112 to invoke the evidence-required burden-on-the-challenger approach of enablement and WD (typified by say Lizardtech), and 101 to invoke the de novo four-corners logic analysis of the spec (typified by Morse). Notably, the supreme court has never endorsed WD as a test at all, let alone as THE standard for overbreadth. Instead, they seem to conceive of overbreadth being subject to the Morse logic test, which is why the Alice standard is so different (and so reviled) from WD.

                  To the extent that one claims “a processor configured to…,” the claim reads on all possible configurations. Therefore, if one has not described all possible configurations, then it is intuitively fair when the judge (or the PTAB) tells you that your claim does not conform to the statutory requirements.

                  See there is nothing wrong with this argument (forgive me) in the abstract, but when it comes time to actually practically apply this test, it is insufficient. That is because Examiners (I am an Examiner) lack the ability to prove the scope of “all possible configurations” which makes an analysis like WD, which requires comparison of disclosed embodiments to see if they are “representative” of the full scope, impossible. The only way to prove the specification does not have representative embodiments is to counter-invent within the claim scope: You claim a machine that fires projectiles, you show me a bow, behold the gun which proves your lack of representativeness. Remove the gun and the argument cannot be made. Thus the claim issues, and it can be used to prevent opposing R&D and is cloaked in a presumption of validity, which (while not being impossible to overcome, as 112a invalidations exist) is the issue regardless of whether a court eventually sets the record straight.

                  The problem is, as I mention above, this analysis is intuitively unjust.

                  It’s really not though, and you should go back and reread Morse. Morse makes an undeniably clear argument – Placing the burden on the public to reject an overbroad scope is an unjust enrichment of the applicant because it chills the very evidence that is necessary for the public to defend itself.

                  A just rule would be that “You get the embodiment you disclose with particularity, and then any abstraction taken from that embodiment can only be sustained when the four corners of the document prove that the embodiment is representative of the enlarged scope.” In other words, a person disclosing a bow can claim the function of a machine that fires projectiles ONLY WHEN they prove that a gun, or any other device performing the function, CAN NOT EXIST. As a practical matter, science is inductive, and therefore cannot prove a negative, and therefore as a general matter a function cannot be claimed. Therefore a just rule would be that functions are *generally invalid* (rather than being valid until the public lodges an evidence-based attack against them) absent special circumstances that prove that the functional scope is entirely possessed. (You’ll notice that this reduces to “A claim to functionality is only valid when it is equivilently coextensive with a claim to the structure of the spec” which, unsurprisingly, is the exact logic of 112f-style claiming).

                  Placing the burden on the public to supply evidence when the very existence of the overbroad claim scope impedes the public creation and disclosure of that evidence is inherently unjust. Once one makes that jump – that the burden lies on the claimant to claim correctly and not artificially inflate their scope – one is doing the thing that upsets the inventor, because it allows for tanking a claim absent evidence. The patent bar would not be more happy if Alice stated that this was a possession analysis that could be tanked based on a judge’s “subjective” logical judgement without evidence.

                  Let me give one example that is important: Suppose A invents a bow, but claims all machines that fire a projectile. A gun would certainly invalidate A’s claim under either prong of 112. However, prior to the gun’s existence, someone invents the catapault. The catapault clearly falls under the overbroad claim scope, and may be different enough in kind that it triggers a 112a invalidation just like the gun does. But the catapault salesman should not be forced to defend on the much closer issue of “Is the bow representative of a scope that extends to include the catapault” but should be allowed to defend on the much stronger issue of “Is the bow representative of a scope that extends to include the gun.” The second argument is inherently not evidenced based, as there is no gun yet, there is merely the threat that the gun could, one day, be invented. And yet had the patentee just provided an accurate scope, perhaps the catapault inventor could have designed around the claim scope (perhaps with a trebuchet). The question isn’t whether the defendant in Lizardtech used a different means (although the particular claim scopes in that case are wonderful for illuminating the issue) – the question is whether the patentee should be allowed to profit from an infringement action when they were the master of their claims and intentionally drew their claims larger than what they had invented. That is the point of using functional language – the goal is to encompass means not disclosed in the spec. For some reason you’re arguing that that tactic for that goal is just and should be protected. It should not.

                  Regardless, of the above, there are separate reasons for locating the issue in 101 which largely have to do with separation of powers and federalism. To locate the issue as a form of 112 would suggest that Congress could make certain things eligible for patenting when they could not no matter how possessed they are (i.e. there is subject matter for which the “significantly more” limitations to make it eligible simply do not exist). One example I like to give here is a claim to using a drilling rig to drill for oil in a particular spot previously unknown to contain oil (“I discovered a new oil deposit”). It is extremely clear to me at least that despite that claim being properly sized to the discovery, being clear and being non-obvious, Congress lacks the jurisdiction to issue a patent for that. Congress was specifically shackled against invading property rights, especially land rights where the state also has an interest, in this manner. Morse, although one could conceive of an argument against him that sounds in both branches of 112a, is another example – or to use the Court’s more basic example: Einstein could not have patented e=mc^2.

                10. It requires some knowledge of the genesis of the law – prior to 52 the “I’ve invented one thing within a much larger claimed scope” situation was taken care of with a combination of 112b (Perkin’s Glue, Wabash) and 101 judicial exception (Morse). Enablement wasn’t invoked and WD hadn’t been “invented” yet. [emphasis added]

                  This seems backward to me. The WD analysis had been “invented” before 1952. The WD analysis was the brainchild of the Morse court. It is your grafting of the Morse analysis onto §101 that is the anachronism. In vain will you search through Morse for a mention of §101, because §101 had not been “invented” yet.

                  It was Funk Bros. v. Kalo Co., 333 U.S. 127, 132 (1948) that grafted the Morse analysis retroactively onto 35 U.S.C. §31 (the predecessor statute section to the 1952 §101). Justice Frankfurter concurred in Funk Bros. (Id. at 133) to point out that the concern that the Court expressed with Funk’s claim would be much better solved with 35 U.S.C. §33 (the predecessor statute section to the 1952 §112).

                  Justice Frankfurter had the better of this one. The good news is that it is not too late to correct Funk Bros.’s error. Indeed, it looks like the Congress is moving slowly toward that salutary development.

                  Morse makes an undeniably clear argument – Placing the burden on the public to reject an overbroad scope is an unjust enrichment of the applicant because it chills the very evidence that is necessary for the public to defend itself.

                  Right. I agree with this. No argument here.

                  That is the point of using functional language – the goal is to encompass means not disclosed in the spec. For some reason you’re arguing that that tactic for that goal is just and should be protected.

                  No, I am definitely not arguing that. I would be fine with a rule that said that functional claim terms are invalid per se under §112(b). I am equally well content with a compromise (as embodied in §112(f)) to the effect that functional claim terms are simply converted by application of law into a species of structural terms (or else tanked under §112(b)). I certainly do not wish to take up the mantle to defend functional claim terms whose purpose and intent is to be construed as functional.

                  The problem is, as I mention above, this analysis is intuitively unjust.

                  It’s really not though, and you should go back and reread Morse.

                  Forgive me, but we are talking past each other. The fault is my own, for a lack of clarity. You are certainly correct that the rule you are advancing is not unjust in its ultimate outcome. It is—as it were—fair to the public, and that is good. A rule of law system, however, cannot be content merely to know that its ultimate outcomes are fair. The processes by which one reaches these outcomes must also be fair.

                  Imagine that X (an inventor) discovers the bow and then claims “a device capable of generating a force to move a projectile through a linear acceleration.” The examiner rejects X’s claim on the grounds that “§112 requires a ‘written description… in such full, clear, concise, and exact
                  terms as to enable any person skilled in the art… to make’ the invention, but X has not described how to make every device capable of such acceleration, so the claim does not conform to the statutory requirements.” X may feel sore about this, but W, Y, & Z (other inventors) will look at this incident and say “that is fair. The statute required something that X did not supply, so it is only fair that X does not get a patent under this statute.”

                  Now imagine that the examiner, instead, rejects the claim on the ground that “X’s claim is drawn to an ‘abstract idea’ of accelerating a projectile and is therefore rejected under §101.” Now not only X is sore. W, Y, & Z also look at the rejection with indignation. After all, §101 has only three requirements (new, useful, and category), and X’s claim satisfies all three of those (X’s invention is new, it is useful, and it is a “machine” or a “manufacture,” which are each among the listed categories). Meanwhile, §101 says nothing at all about “abstract ideas.” In other words, instead of a rejection that every fair minded observer can admit to be outside of the statutory requirements, the examiner has not predicated the rejection on a putative statutory basis that has no tie whatever to the actual statutory language. The outcome might well be fair to the public, but the process by which the outcome is obtained is also intuitively to the community of disinterested inventors when it is decided under §112, but not when it is decided under §101. It only kind-of-sort-of becomes intuitively fair if (as you say) one has “some knowledge of the genesis of the law.” Even then, however, it does not really make sense (why do we exclude claims to “processors” or “computers” as “abstract ideas,” when everyone has a computer sitting on their desk that hurts when you drop it on your foot in precisely the way that an abstraction does not hurt?).

                  Section 112 is just much the better basis to achieve the right outcome here.

                11. Yet again, the “over-politeness” of Greg is not helpful here.

                  I fully “get” why Greg is being overly polite.

                  He sees a common “End” and wants to get to that same common End, but instead of through 101, Greg wants to get there through 112.

                  The problem with the “politeness” is that Random just will not see how wrong Random is in BOTH 101 and 112, and that the path Greg wants through 112 just is not there so the Ends that Greg thinks is in common CANNOT BE ACHIEVED no matter how polite Greg is.

                  BOTH are wrong.

                  Each in different ways, and Random is far deeper into the weeds than Greg is.

          2. 2.2.1.3.2

            A patent application that included all the known ways of solving a function would get to be over 1,000 pages.

            Oh noes! So many pages. It makes the “real engineer” weep.

            Golly, if only there were a way to submit that kind of information in a uniform standard manner to reduce the number of pages and allow each of those “known ways” to be searchable by the USPTO.

            But, alas, such things are not possible in our third world country. Surely it is the fault of Latinos!

          3. 2.2.1.3.3

            The POSITA knows all these solutions or knows that if they think of a solution to build a product that it is a known way.

            Hahahahaha. “This term is definite because a POSITA knows everything” isn’t even remotely close to “informing with reasonable certainty.” By the way, if the absolute state of the art is such a well known thing, how come so many prior art rejections happen?

            I’ve written real claims to real electronic devices that have been licensed for of millions of dollars to the top international corporations. That will not pay if they can design around.

            Just think of how well they’d have done if they’d have gotten a better lawyer.

            A patent application that included all the known ways of solving a function would get to be over 1,000 pages. Probably realistically it would have to be 5,000 pages.

            It’s almost as if nobody living in an inductive world could prove definitively that they invented the entirety of the abstract function! Ludicrous.

            Plus—your argument is that a claim scope should be less than the scope of enablement, which means by definition that there are embodiments that are enabled but not included in the scope. So trivial to avoid infringement.

            If an inventor discovers something that has many uses, but personally only understands some subset of the uses, then the inventor does not get all of the uses. That is, again, literally what Morse argued for – I discovered this principle, and I claim every possible use of this principle, regardless of if I posit it or disclose it or not. By your logic, Bernoulli has invented every airplane that has ever existed and will ever exist, because all flight is enabled by lift.

            In short your argument, while adorable, has nothing to do with the actual law.

            1. 2.2.1.3.3.1

              If an inventor discovers something that has many uses, but personally only understands some subset of the uses, then the inventor does not get all of the uses.

              A most odd statement.

              A claim to the thing is a claim to thing — regardless of the uses that thing may be put to.

              THIS statement of yours actually works AGAINST your desired Ends, Random. See 35 USC 100(b).

            2. 2.2.1.3.3.2

              In short your argument, while adorable, has nothing to do with the actual law.

              LOL – says the guy who is clue1ess about actual law (and this is reflected in the FACT that the Ladders of Abstraction have more than the two rungs that Random’s “examples” always boil down to).

        4. 2.2.1.4

          NS II asks:

          What does being a “real engineer” have to do with proper claiming?

          … and falls to the same mistake that Greg jumped on awhile back now when Night Writer explains how “functional language” is understood by a Person Having Ordinary Skill In The Art (albeit using engineering rather than legal terms).

          NS II, please tell me that you are aware of the legal version of “Ladders of Abstraction” (see Klusky on claim drafting, if necessary).

      2. 2.2.2

        real engineers

        LOL

        How come these “real engineers” always seem to be the dullest sticks in the bunch when it comes to patent law? It’s been a running joke here for the past 15 years.

      3. 2.2.3

        The propaganda machine against rampant patent maximalist id-i0cy is in full swing.

        Fixed for accuracy. Also, get used to it.

      4. 2.2.4

        Patents are for inventions, not for just claiming a desired result without both claiming and enabling one or more actual solutions for that result.
        There are all kinds of possible purely functional, result-oriented claims. E.g., “I claim a method of killing flies with a beam of nuclear radiation.”

        1. 2.2.4.1

          Does the method use artificial intelligence or machine learning? If so, my benefactor is extremely interested.

          Sincerely,

          Silly Con Valley Bro

        2. 2.2.4.2

          Patents are for inventions, not for just claiming a desired result without both claiming and enabling one or more actual solutions for that result.

          And even then, a claim to all ways of achieving a result when the specification only provides “one or more actual solutions” is overbroad. One might have an invention, but it is not the invention of the function.

          One generally cannot prove the full scope of all solutions, so one generally cannot prove they possess all solutions. They can only prove that they possess the solution they have. People can invent means of achieving a result. People cannot invent the result. String tension certainly seems like the only manner of propelling a projectile until someone unmasks contained chemical explosion. The person who invented the bow invented the bow, they didn’t invent the function of firing a projectile, as that set of solutions includes the gun, which they didn’t have.

    3. 2.3

      “But will they now finally really encourage and sustain S.J. on that issue on a regular basis?”

      No.

  10. 1

    “In Alice step two, the court explained “[t]here is no inventive concept in the claim’s use of a generic payment server ‘to perform well-understood, routine, and conventional activities commonly used in industry.’””

    Seems to me in Alice step two, the court explained the claim is abstract (its the Alice test after all) because they it recites something old.

    Unless the claims predate Ebay and Paypal, I tend to agree the element discussed is old. Of course THAT DOES NOT MAKE IT ABSTRACT!!!!

Comments are closed.