Posts Tagged: "Patent Drafting Basics"

Drafting Patent Applications: Writing Method Claims

Method or process claims are relatively easy to write once you know what the core invention is and what is necessary to be included in the claim in order to overcome the prior art.  Like all claims, method or process claims must completely define the invention so that it works for the purpose you have identified AND it must be unique when compared with the prior art.  By unique I mean it must be new (i.e., not identical to the prior art, a 35 USC 102 issue) and it must be non-obvious (i.e., not a trivial or common sense variation of the prior art, a 35 USC 103 issue). Method or process claims will include active steps to achieve a certain result.  In method claims the transition is typically either “comprising” or “comprising the steps of.”  While legally there may be some distinction between these two different transitions, both are acceptable.

Turn Your Idea into an Invention with a Good Description

In reality, it is probably better to think of the description requirement as the core to patentability. If you can describe your idea with enough specificity you no longer have an idea, but rather have migrated past the idea-invention boundary, which means you have something that can be patented if it is unique. The crux of this so-called adequate description requirement is that once the first four patentability requirements are satisfied the applicant still must describe the invention with enough particularity such that those skilled in the relevant technology will be able to make, use and understand the invention that was made by the inventor. For the most part, and from a legal perspective, this requirement can be explained as consisting of three major parts. First is the enablement requirement, next is the best mode requirement and finally is the written description requirement.

Patent Drafting: What is the Patentable Feature?

Due to the laws of nature, and the reality that there are only a finite number of solutions to any particular problem, every generation invents, or re-invents, many of the same things. Thus, it is always wise to do a patent search to start the process. I guarantee a patent search will uncover inventions that you did not know were out there. With over 8.5 million utility patents having been granted in the U.S. and well over 1 million pending patent applications, and millions of other published but abandoned patent applications there is always something that can be found that at least relates in some ways. You are always better off knowing about those related inventions. This allows you to determine whether moving forward makes sense, and it also allows for a patent application to be written to accentuate the positive, and likely patentable, aspects of an invention.

Patent Claim Drafting 101: The Basics

When writing a claim it is important to describe how the various components are structured and how the various components interact and connect. First, include a claim that defines your invention in broad terms, leaving out any and all unnecessary options. Second, include another claim that defines your invention with as much specificity and with every option you can think of. It does not matter that the claims won’t be in perfect format, with appropriate being defined as the format the Patent Office will ultimately require. At the initial filing stage what matters most is that claims are present and they have appropriate scope, with some being broad and some being narrow and quite specific. By starting to write these two claims you will “bookend” your invention. By this I mean you have disclosed the very broad and generic version of your invention, as well as the highly specified version.

Writing Software Patent Applications

Collecting the information necessary to prepare a patent application covering a computer related invention can be quite challenging. Typically, most computer related inventions today relate at least in some way to software, which is at the core of the challenge. This software challenge stems from the fact that the software code is not protected by patent law, but rather how the software operates is protected. This means that the description needs to be one that can be replicated by others regardless of how they choose to write code to accomplish the necessary tasks.