Tag Archives: patent law

Only Some of the Claims are Invalid

by Dennis Crouch

Hantz Software v. Sage Intacct (Fed. Cir. 2023) (non-precedential) 

The district court sided with the defendant Sage, dismissing the complaint for lack of eligibility.  In a short opinion, the Federal Circuit has largely affirmed, but made an important caveat -- that the district court held only that claims 1 and 31-33 are invalid.

[W]e agree that the operative complaint asserted infringement of only claims 1 and 31–33 of each asserted patent, and because Sage did not file any counterclaim of its own (instead, it simply moved to dismiss Hantz’s complaint), we conclude that the ineligibility judgment should apply to only claims 1 and 31–33 of the asserted patents. We therefore vacate the district court’s judgment insofar as it held any claim other than claims 1 and 31–33 of each asserted patent ineligible and affirm in all other respects.

Slip Op.  Despite the limit here, claim preclusion will prevent Hantz from reasserting any of the remaining claims against Sage. Non-mutual collateral estoppel should also apply here to to prevent Hantz from asserting any of the claims against a third party -- unless the claims are meaningfully distinct on eligibility grounds from those already adjudged to be invalid.  Normally, collateral estoppel only applies to issues actually litigated, but in the patent context, the Federal Circuit has ruled that it may also apply to non-litigated claims when the differences do not "materially alter the question of invalidity." Ohio Willow Wood Co. v. Alps South, LLC, 735 F.3d 1333, 1342 (Fed. Cir. 2013); MaxLinear, Inc. v. CF CRESPE LLC, 880 F.3d 1373, 1377-78 (Fed. Cir. 2018) (Asking “whether the remaining claims present materially different issues that alter the question of patentability”).

 


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Issue its “Mandate and Opinion”

by Dennis Crouch

The Federal Circuit regularly affirms PTAB judgments without issuing any explanatory opinion to justify the result.  Although not found in the Rules of Appellate procedure, the court has created its own local rule allowing itself to "enter a judgment of affirmance without opinion."  In a 2017 paper, I argued that these no-opinion affirmances violated both the spirit and letter of 35 U.S.C. 144, which requires the court to issue a "mandate and opinion" in cases appealed from the USPTO.  Since that time, the Federal Circuit has continued its practice, issuing hundreds of no-opinion judgments.  Throughout this time, dozens of losing parties have petitioned for en banc rehearing with the Federal Circuit or certiorari to the Supreme Court.  Up to now, both courts have remained silent and have refused to address the issue.

A new pending petition raises the issue once again. Virentem Ventures v. Google (Supreme Court 2023).  Virentem sued Google for patent infringement, and Google responded with a set of Inter Partes Review (IPR) petitions.  The PTAB eventually sided with Google and invalidated the claims of all seven challenged patents.  Virentem appealed; but the Federal Circuit affirmed the PTAB's judgement without opinion under its local Rule 36.

The new petition to the Supreme Court asks four related questions:

  1. Does the Federal Circuit’s use of Rule 36 to affirm without opinion PTAB invalidity determinations that are challenged based on pure questions of law violate a patentee’s due process rights through arbitrary or disparately applied results?
  2. Did the Federal Circuit’s use of Rule 36 to affirm without opinion PTAB invalidity determinations of Virentem’s patents violate its due process rights?
  3. Did the PTAB’s adoption, and Federal Circuit’s summary affirmance, of broad constructions of Time Scale Modification and other claim terms over Virentem’s explicit narrowing definitions, violate the Federal Circuit’s own law and precedents on claim construction in such circumstances?
  4. Does the Federal Circuit’s use of Rule 36 to affirm without opinion decisions from the PTAB violate the requirement of 35 U.S.C. § 144 that the Federal Circuit “shall issue to the Director its mandate and opinion”?

The Virentem patents relate to time-scale modification -- the speeding-up or slowing-down of media.  You may remember Alvin, Simon, and Theodore -- the Chipmunks.  That unintelligible high pitch arguably is not really time-scale modification because it is such a failure.  Rather, TSM modern impliedly requires maintaining pitch and intelligibility.  In this case though, the PTAB broadly interpreted the term to include any system that speeds-up or slows-down media.  With that broad interpretation, the tribunal then was able to find prior art rendering the claims obvious.   Virentem argued that its patents would be seen as valid under the narrower construction.  The PTAB's response: If you wanted that limitation in the claim, you should have added it to the claim.


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Eligibility for Dummies; Benson Redux

by Dennis Crouch

I've become somewhat callous toward patent eligibility jurisprudence and so was surprised when I read the Federal Circuit's decision in ADASA Inc. v. Avery Dennison Corp., 55 F.4th 900 (Fed. Cir. Dec 16, 2022). The case concluded that constructively dividing a fixed-length binary number into different sub-portions was not an abstract idea.  Now, the accused infringer has asked the Supreme Court for review.

ADASA's US Patent 9,798,967 is directed toward an RFID chip "encoded with a unique object number."  This object number as various blocks pre-allocated to identify the selling-company, product reference, and serial number as shown below.  The serial number has a unique feature of being divided into a section of "most significant bits" (MSBs) and "least significant bits" (LSBs). This division between MSBs and LSBs help in the allocation of unique serial numbers in a distributed production system.  The basic approach:

  • A product-line will be exclusively allocated a particular MSB and all possible accompanying LSBs. It will then enable RFID chips using the allocated MSB and then sequentially incrementing the LSB.
  • A separate product line might also be simultaneously enabling other other chips. To ensure no overlap in serial numbers, the second-line will be allocated a different MSB.
  • The result then is that we can guarantee that each chip has a unique serial number despite parallel production lines.

The claims do not appear to include any novel features other than this constructed division between bits in a binary number.  (Claim 1, is reproduced below). In its petition, the adjudged infringer relies heavily on the old cases of Benson and Flook to argue that the setup here lacks eligibility.

Question presented:

Radio Frequency Identification Device (RFID) tags are encoded with lengthy serial numbers that uniquely identify particular items. The patent at issue in this case designates the leading bits in a binary serial number as “the most significant bits,” and directs that all serial numbers in an allocated block begin with the same “most significant bits.”

The question presented is whether that claim, by subdividing a serial number into “most significant bits” that are assigned such that they remain identical across RFID tags, constitutes patent-eligible subject matter under 35 U.S.C. § 101.

Avery Dennison Petition.

Chief Judge Moore wrote the opinion and concluded that the claims were not directed to an abstract idea but rather provides a novel data structure within a serial number.  Here, the idea is that the patentee was able to create a new data field that was "not a mere mental process, but a hardware-based data structure focused on improvements to the technological process by which that data is encoded;" and an improvement with "important technological consequences."

An interesting feature is that the general idea presented by the patentee was already identified and discussed in the book RFID for Dummies.  If Avery Dennison loses here, then the district court will hold a trial on anticipation.  Still, the "for Dummies" label has strong rhetorical appeal -- should everything in that book title be considered an abstract idea?  The petitioner writes:

“[A]bstract ideas are not patentable.” ... It is hard to imagine a more blatant transgression of that rule than the claim in this case, which sought a patent monopoly over the simple concept of treating one long serial number as the combination of two shorter numbers, and then [requiring] blocks of RFID tags all start with the same shorter number. At bottom, that claim is no different from a direction to mentally subdivide all telephone numbers into two component parts and then assign the same leading part to an allocated block of numbers (e.g., all telephone numbers in the District of Columbia start with 202). That may be a good idea (indeed, the concept in ADASA’s patent appears in the pages of RFID for Dummies), but it is no more patentable than the other good but abstract ideas that this Court has held unpatentable for more than 150 years.

Id.  I'm confident that if the Supreme Court takes this case, it would even further expand eligibility doctrine.

= = =


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Guest Post by Profs. Masur & Ouellette: Public Use Without the Public Using

Guest post by Professors Jonathan S. Masur (Chicago Law) and Lisa Larrimore Ouellette (Stanford Law).

What is it that makes a use “public” for purposes of the public use bar? Does it matter whether the person doing the using is a member of the public, as opposed to the inventor? Or does it matter whether the use is itself in public, as opposed to taking place in secret behind closed doors? As it turns out, the answer to both questions is “yes,” but the questions are not as distinct from one another as that formulation might make it seem. Instead, the issue of who is doing the using turns out to affect where and how that use must occur if it is to be public use.

Begin with the question of who is doing the using. Most cases of “public use” have involved use by at least one member of the public—“a person other than the inventor who is under no limitation, restriction or obligation of secrecy to the inventor.” And when an invention is in use by a member of the public (rather than the inventor), it is blackletter law that the use can be “public use” even if it takes place entirely in secret, behind closed doors. In addition, it is also blackletter law that the use need not enable the invention to constitute prior art. No member of the public needs to see all the details of the invention or be able to reproduce it—it is enough that at least one person has come to rely on the availability of the invention free from any patent-based restriction.

But as we explain in a forthcoming article, a small line of cases suggests there is a second route to public use: even if no member of the public uses the invention, an invention can be placed in public use if it is used by the inventor, but only if it is displayed to the public in such a way that the relevant public could have understood the invention. That is, there can be public use without the public using, but only if that use is out in the open and with something like an enablement requirement. See Real-World Prior Art, 76 Stan. L. Rev. (forthcoming 2024). These cases appear to rely on an idea of constructive public knowledge: just as a conference poster can be invalidating printed publication prior art if a researcher could have learned about the invention by reading it, an inventor’s demonstration of an invention can be an invalidating public use if someone could have learned about the invention from observing the demonstration. Likewise, the Federal Circuit has held that display of an invention is not public use “if members of the public are not informed of, and cannot readily discern, the claimed features of the invention.” The only exception to these rules has come when the inventor is engaged in secret commercial use of the invention. Some courts have held that this puts the invention into public use. But more recently, the Federal Circuit has instead begun to hold that this places the invention on sale, because the whole point of the use is to exploit the invention commercially. We agree with the Federal Circuit panels that have held that the on sale bar is a better fit in these situations.

The upshot from these two lines of precedent is that the question of whether an invention is in public use depends intimately on who is doing the using. If the user is someone other than the inventor, then there is public use (a) even if the use is taking place in secret, and (b) irrespective of whether the user can figure out how the invention works (enablement). But if the inventor herself is the one doing the using, then (a) the use must be taking place in public, and (b) the use must be enabling.

As one might predict, the grouping of these two approaches under the single heading of “public use” has led to confusion among litigants and, in some cases, courts. Two new Federal Circuit decisions this month add to this “public use without the public using” line of cases and demonstrate the pitfalls of failing to keep the interlocking public use rules straight. In Minerva v. Hologic, the court held that display and demonstration of a medical device at a gynecological trade show constituted public use. The patentee, perhaps misunderstanding this line of doctrine, argued that it could not be public use because no member of the public used the invention. But the court held that “public use may also occur where, as here, the inventor used the device such that at least one member of the public without any secrecy obligations understood the invention.” Similarly, In re Wingen held that display of an inventive “Cherry Star” flowering plant at a private Home Depot event placed the plant into public use. The patentee argued that the display did not disclose the claimed genetics of the plant—which could have been a successful argument given the enablement-like inquiry imposed on other similar cases—but the court held that this argument was forfeited because it was not raised in proceedings below. It seems likely that the lawyers who argued the case before the PTAB had not thought to make this argument because they did not realize that use by the inventor requires enablement. Our article includes numerous examples of district courts that were similarly confused by the rules that vary depending on who’s doing the using.

As we explain in our article, treating enabling demonstrations by the inventor as prior art makes sense as a matter of patent policy. But lumping these cases under the “public use” umbrella has created confusion and mistakes among the lower courts. Going forward, we think the Federal Circuit should be explicit that there are two distinct routes to public use: (1) use by a member of the public—someone under no obligation of confidentiality to the inventor—which can take place in secret and need not be enabling, and (2) use by the inventor, which must take place in public and enable the invention.

Alternatively, and perhaps even better, the Federal Circuit could decide that the inventor-use category of activities instead implicates the “otherwise available to the public” prong of § 102. An enabling demonstration, where the public learns about the invention but cannot use it, could be the paradigmatic example of an activity that makes an invention available to the public without creating any other type of prior art. This is not a full solution given all the pre-AIA patents still in force, and in light of the strong policy reasons for barring pre-AIA patents that were displayed publicly we can see why courts have tried to fit these cases within the “public use” category. Regardless, for patentees and their attorneys, Minerva v. Hologic and In re Wingen serve as a reminder to avoid disclosing the details of an invention before they are ready to file a patent application—and if a disclosure does occur, they should remember to preserve the argument that it wasn’t actually enabling!