Posts Tagged: "patent software"

EPO ready for the first Unitary Patent as soon as the ratification requirements are met

One of the great aspects of the Unitary Patent is that it follows the normal EPO procedure up to grant. And indeed, the search and the examination processes will be precisely the same as those you’ve been used to with the current EP and PCT procedures, and will be performed by the same examiners. One of the strengths of the EPO is that we allocate examiners to applications according to their technical expertise, regardless of the filing route through which applications arrive. It will only be at the end of the procedure, when the application proceeds to grant, that applicants will have to indicate if they want to have a single Unitary Patent instead of a bundle of patents for individual member states, as is the case for the European patent. So it’s extremely straightforward, cost effective, and much simpler to administer post grant than the current European patent. My impression is that many U.S. applicants already understand the logic and advantages of this very well, sometimes even a little better than European applicants, as the geographical size and the GDP of the market covered by the Unitary Patent is very similar to that of the U.S. patent.

Exclusive with Grant Philpott: Patenting Computer Implemented Inventions in Europe

We try to be precise and stick to CII because “software” in itself is a term which lacks precision. It can refer to a high level program, a machine level program, or it can be an executable program. But if we speak about a computer-implemented invention the core of the discussion is rather on the technology. We have a general purpose computer and we program it, and when it runs it executes the instructions and performs certain functions. So the essence of our approach is to ask what the software does. Software of course can do a variety of things, many of which can be totally out of the patentable area if they’re purely abstract or purely business oriented. But when software solves a technical problem you are definitely in the area where a patent is possible. That is the core element of our approach.

PTAB cites Enfish, refuses to institute Covered Business Method Review on Mirror World patent

Earlier today the Patent Trial and Appeal Board (PTAB) of the United States Patent and Trademark Office (USPTO) declined to institute a covered business method (CBM) review of U.S. Patent No. 6,006,227, which is owned by Mirror World Technologies, LLC. The decision is significant not only because the PTAB refused to institute a covered business method review, but because the panel — Administrative Patent Judges Thomas Giannetti, David McKone, and Barbara Parvis — cited the Federal Circuit’s recent decision in Enfish v. Microsoft when they found that the challenged claims of the ‘227 patent were not abstract.

Twilight Zone: The Solicitor General’s Brief in Alice v. CLS Bank

… in order to handle the messy reality that the system claims, illustrated above, are clearly not abstract under any intellectually honest definition, they merely say that if the method and computer readable medium claims are not patent eligible neither are the system claims because… well just because. It seems inventions rise and fall based on what the applicant really wants to protect, not the claims… Assuming you have snapped back from the Twilight Zone yourself you may be hearing in your head the clanking of coconuts as several Monty Python players exit stage left in search for the holy grail! Of course, regardless of whether the coconuts migrate, those coconuts are are obviously abstract and not tangible, clearly not patent eligible and a fiction of your imagination. Therefore, you really can’t be hearing the coconut clanking noise because imaginary non-migratory coconuts that don’t exist can’t be banged together to make a sound.

Software Patent Basics: What Level of Description is Required?

The key to any software patent application is to describe the invention with enough technical detail, system specifics and process information so that a computer programmer could take the disclosure and code the software without having to make any independent, creative decisions. Essentially, you want your patent application to be a design document. This is critical because it is the design of the software — the architecture of the system, how the algorithms are strung together, the rules, calculations and manipulations — that are patentable. Software code is not patentable. You can and should get a copyright on the software code as written, but the invention does not reside in the code. The computer programmer is merely a translator that takes your invention and writes it into code that the computer can execute.

USPTO: No Change to Software Patentability Evaluation

In a one-page memorandum to the Patent Examining Corps dated May 13, 2013, Deputy Commissioner for Patent Examination Policy Drew Hirshfeld had a simple message to respond to the Federal Circuit’s en banc non-decision in CLS Bank v. Alice Corp. The message was this: “there is no change in examination procedure for evaluating subject matter eligibility.”

A Guide to Patenting Software: Getting Started

Any good patent application that covers a software related invention will need to put forth three specific pieces of information. First, you need to describe the overall computer architecture of the system within which the software will exist. Second, you need to prepare a single flowchart that depicts the overall working of the software. Third, you need to prepare a series of flow charts that show with painstaking detail the various routines and subroutines that together connect to create and deliver the complete functionality of the computer system as enabled by the software.

Building Better Software Patent Applications: Embracing Means-Plus-Function Disclosure Requirements in the Algorithm Cases

The disclosure requirements for these types of patent applications has been a moving target for years, which means that whatever the most stringent disclosure requirements are should become the target regardless of the types of claims you file. To ensure your software patent application has appropriate disclosure of the invention you should accept — even embrace — the requirements for having an appropriate means-plus-function disclosure. By meeting the strict standards set forth in the mean-plus-function algorithm cases you will file more detailed applications that have better disclosure and which will undoubtedly support more claims, thus making the resulting patent or patents more valuable.

The Information Needed to Avoid Writing Bad Software Patents

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.

Business of Software: How to Develop Tools for Patent Lawyers

If you ever thought of starting a patent software company, I have some good news for you. Unlike the general software markets for, say, antivirus or mp3 software, the legal software market is just not very saturated. A lot of the existing software for patent lawyers is outdated, ridiculously expensive, and frankly, not that good. There is definitely room for…