Posts Tagged: "software patents"

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 basic law relative to § 112, ¶6 explains that a decision on whether a claim is indefinite under § 112, ¶ 6 requires a determination of whether those skilled in the art would understand what is claimed when the claim is read in light of the specification. Traditionally, claim terms are typically given their ordinary and customary meaning as understood by one of ordinary skill in the pertinent art. The question with means-plus-function claiming, however, is whether evidence from that mythical individual skilled in the art is even admissible. No structure in the specification means the person of skill in the art cannot save the disclosure by understanding. Thus, means-plus-function claims are largely valid at the mercy of a federal judge who in all certainty is not one of skill in the art and who likely has an aversion to such claiming techniques because they prefer dealing with tangible structure.

So Twitter can use the donated patents “defensively” to initiate a lawsuit if they feel threatened? If they deem it is otherwise necessary to deter a patent litigation? So Twitter can be the aggressor with the donated patents, and it seems like it is their sole discretion whether the threat or “otherwise” caveat are activated such as to allow them to go on the offensive. Incidentally, and interestingly, Twitter will have “all rights to recover damages for infringement…”

Earlier today the United States Court of Appeals for the Federal Circuit issued a decision in Noah Systems, Inc. v. Intuit, Inc. According to the Federal Circuit the specification of the ’435 patent must contain an algorithm that performs the function associated with the “access means” limitation, otherwise the limitation is indefinite and the claim invalid. Ultimately, the Federal Circuit would determine that the algorithm disclosed was incomplete. This lead the Court to explain that when the specification discloses an algorithm that only accomplishes one of multiple identifiable functions performed by a means-plus-function limitation, the specification is treated as if it disclosed no algorithm. An incomplete algorithm means no algorithm as all, which means that what one of ordinary skill in the art would understand from the disclosure is no longer relevant. This is where I would depart from the Federal Circuit and think that the law as it relates to means-plus-function claiming of computer software is all wrong. Means-plus-function claims has always been about what someone of ordinary skill in the art would appreciate (see, for example, USPTO 112 guidelines, 76 Fed. Reg. 7162 (9 February, 2011) so why is that not the case with respect to computer software?

All of this might be confusing to a Judge who is unfamiliar with computers, but that is not the test, is it? The question is supposed to be whether it would be confusing to a person of relevant skill in the relevant technology area. Indeed, disclosure sufficient for means-plus-function claiming may be implicit or inherent in the specification if it would have been clear to those skilled in the art what corresponds to the means-plus-function claim limitation. See MPEP 2181 and Atmel Corp. v. Information Storage Devices, Inc. (Fed. Cir. 1999). Indeed, the Federal Circuit in Atmel concluded that the title of the article incorporated by reference in the specification may, by itself, be sufficient to indicate to one skilled in the art the precise structure of the means for performing the recited function. So the focus is supposed to be on one of skill in the art even when interpreting whether the specification provides adequate support for means-plus-function claiming. Nowhere in the majority opinion is it stated that a person of skill in the art would not have known and would have found the claim vague or ambiguous.

When copying has occurred, much of the code may have changed by the time it’s examined due to the normal development process or to disguise the copying. For example identifiers may have been renamed, code reordered, instructions replaced with similar instructions, and so forth. However, perhaps one comment remains the same and it’s an unusual comment. Or a small sequence of critical instructions is identical. Correlation is designed to produce a relatively high value based on that comment or that sequence, to direct the detective toward that similarity. If correlation were simply a percentage of copied lines, the number could be small and thus missed entirely among the noise of normal similarities that occur in all programs.

The patent application was originally filed June 28, 2007, and as a result of delay by the Patent and Trademark Office Apple will be entitled to a patent term that is extended by 830 days. While patent term extension seems to be a growing problem due to the backlog of applications, let’s not focus on the patent term, but rather look at the core of what is being protected and how this patent was obtained. I’m not going to defend the patentability of this invention, but rather try use this as an illustration of how to read a patent and search for clue in the file history regarding how and why claims are awarded. It should also demonstrate how easy it can be to distinguish prior art references and overcome rejections if you know what you are doing or are represented by someone who does.

Listening to those who code complain about patents is nearly hysterical. They still haven’t figured out that by and large they are not innovators, but rather merely translators. Perhaps that is why they so frequently think that whatever they could have come up with themselves is hardly worthy of being patented. Maybe they are correct, but that doesn’t mean that an appropriately engineered system isn’t patentable, it just means that those who code are not nearly as likely to come up with such a system in the first place because they rarely, if ever, seem to approach a project as an engineer would. Rather, they jump right in and start coding. In the engineering world that is a recipe for disaster, and probably explains why so much software that we pay so much money for today is hardly worthy of being called a beta, much less a finished product.

President Obama reportedly asked McNealy to prepare a report on how the federal government could employ open source software, but as yet, some 26 months later there has been no mention of the report or across the board government adoption of open source software. The fact that open source software is given away to be used freely demonstrates the problem with finding a sustainable business model and may explain why the Obama Administration hasn’t yet presented the report on how the government can use open source software to decrease costs. You really have a hard time staying in business and focusing on the research, development and product advancements when the product you offer is given away to be used free, or the underlying code that makes it work can be copied and used by competitors without consequences.

In New Zealand, patents (equivalent to utility patents in the USA), registered designs (viz. US design patent) and trademarks are subject to normal substantive examination processes. Fortunately, due to smaller backlogs and a less bureaucratic system, overseas applications filed into NZ are often examined within a year of filing. Accelerated examination may also be requested with no official fee where applicants need a quicker indication as to the validity of their rights. Further, if you have a corresponding patent right granted in another major patent office, the NZ process can be accelerated assuming the NZ claims are similar to that in the corresponding right.

The gene patents issue had been simmering in Australia for some time, with a Senate Enquiry into the subject having been underway for over a year, but with the Myriad decision in the US, and the Australian litigation, it exploded into the headlines. Within the space of a few months, gene patents became the subject of numerous news articles and opinion pieces (including one by the former leader of the Opposition, and current Shadow Minister for Communications and Broadband, Malcolm Turnbull), and a major report on the Australian national broadcaster’s flagship current affairs program Four Corners. Almost all of this coverage was generally critical of ‘gene patents’, without ever providing a satisfactory definition of the term.

What do you think of my jumping buddy over there? Let’s call him “George”. George is just one example of the enormous number of inventions being made to serve our newly emerging social networking economy. George was created using a patent pending process called Evolver. He’s an avatar that can be transported to any number of different full immersion virtual world networking sites. Many new companies are forming to commercialize these new social networking innovations. They are also filing patent applications. They have many challenges ahead of them to get those patents.

As the open source movement grows Microsoft, which is always the 800 pound gorilla in the room, may consider bringing patent infringement suits. It seems that is the worry of at least one open source group who claims that it is particularly troubling that Microsoft, along with a group of tech companies that includes Apple, is seeking to purchase the Novell patent portfolio. According to the Open Source Initiative, the Microsoft coalition seeking to purchase the Novell patent portfolio has “no incentive to support open source as a competitive alternative to proprietary software.”