Posts Tagged: "enablement"

One thing that many individuals and professional inventors employed by corporations (i.e., “kept inventors”) have in common is that they frequently do not perceive what they have come up with as worth patenting. So many have the idea that a patent is something that gets awarded to breakthrough innovations, when in fact it is far more common to have a patent awarded to an improvement on an existing product. If you can improve upon something , there is already a market in existence for the underlying product and consumers will perceive your improvement as worth paying for then you very well may have a winning invention. Certainly, you are much farther along the path to success with that trifecta.

In my view, both the majority opinion, as well as Judge Dyk’s dissent, miss the real “written description” problem in Crown Packaging which has nothing to do with whether the common patent specification illustrates both solutions to the prior art problem. Instead, it relates to the follow description (see column 1, line 62 to column 2, line 5 of the ‘826 patent) at the end of the sentence stating how the claimed invention solved the problem of using less metal in the can end: “characterized [or “characterised” depending on which version of the ‘826 patent you use] in that, the chuck wall is inclined to an axis perpendicular to the exterior of the central panel at an angle between 30o and 60o and the concave [i.e., the reinforcing] bead narrower than 1.5 mm (0.060”).”

The back bone, however, is made up of many smaller bones. For example, there are seven cervical vertebrae in the necks of all mammals, and these bones together make up a portion of the back bone. Therefore, a more complete description of the backbone would point out that the neck is a part of the backbone. An even more complete description might include saying cervical vertebrae 1 (i.e., C1, which is a part of the neck) is connected to cervical vertebrae 2 (i.e., C2) and so on. The point is that the more description you provide the better, but you absolutely must have at least the big picture overview of how everything fits together, and how to make and use the invention. Therefore, be sure that you have disclosed with as much detail as possible how all the pieces of your invention connect, work together, function and interrelate.

In order to have a patentable business method it is necessary for the invention to accomplish some practical application. In other words, in order for a business method to be patentable it must produce a “useful, concrete and tangible result.” Although the United States Supreme Court did away with that test when it issued its decision in Bilski v. Kappos, it is still nevertheless illustrative and the best test that is out there. If you really understand what Judge Rich meant by “useful, concrete and tangible result” you come to the inescapable conclusion that it is the appropriate test and if you really target the description of the invention to satisfy the test you will have something that is patentable under the Supreme Court Bilski v. Kappos test and the USPTO guidelines that have followed.

Last week the United States Court of Appeals for the Federal Circuit issued a ruling in Goeddel v. Sugano, which might be one of a dying breed should patent reform actually pass. The case dealt with an appeal from an interference proceeding where the Board awarded priority based on a Japanese application. The Federal Circuit, per Judge Newman, explained that it was inappropriate to say that the Japanese application demonstrated a constructive reduction to practice because the application merely would allow the skilled reader to “envision” the invention covered in the interference count. If patent reform passes (and yes that could really happen) cases like Goeddel would become a thing of the past, although priority determinations like this one in Goeddel will certainly not go away.

Software is now and will remain patentable in the United States. Software patents have been vilified by many, but they have been granted by the United States Patent and Trademark Office and upheld in federal courts across the United States. The much anticipated Bilski v. Kappos decision at the Supreme Court did nothing to slow down the patentability of software, and in fact even the original Federal Circuit decision wound up, as applied by the USPTO, to make it more likely that adequately written software patent applications would be granted and transformed into issued patents. What has changed over the last several years, however, is the amount of detail that must go into a software patent application in order to satisfy the adequate description requirements under US patent law. So don’t listen to anyone who tells you software cannot be patents in the United States; it certainly can, but it isn’t quite as easy as it used to be.

Coming as no surprise, a majority of the en banc Federal Circuit just ruled in Ariad Pharmaceuticals v. Eli Lilly &Co. that there is there is a separate and distinct “written description” requirement in the first paragraph of 35 U.S.C. § 112. Also not surprisingly, there were multiple concurring (and dissenting) opinions. Judge Lourie (writing the majority opinion) has now won the on-going debate that has raged between him and Judge Rader (who has strenuously argued there is no written description requirement separate and distinct from the “enablement” requirement) since the 1997 case of Regents of the University of California v. Eli Lilly & Co.

In probably the most significant case since In re Bilski, the en banc Federal Circuit in Ariad Pharmaceuticals v. Eli Lilly is about to ponder two questions:  (1) is there a separate and distinct “written description” requirement in the first paragraph of 35 U.S.C. § 112?; and (2) if there is, what does it mean?  My answer to the first…

The Redmond Giant, Microsoft Corporation, had US Patent Application 20090265604 publish, which seeks to protect a method for displaying a graphical representation of the vitality of a social network. This patent application was filed on April 21, 2008, and is one of many related to social networking that Microsoft has pending presently.