ADDING LINKS IS TEMPORARILY BLOCKED - if you want to add a link, just put a space in it so that it doesn't work. The admin will then fix the link for you very quickly. This will be fixed as soon as I have the new spam blocking system in place.

SitemapCountriesWhy abolish?Law proposalsStudiesCase lawPatent office case lawLawsuits

Technical solutions not technical problems

Jump to: navigation, search

Some authors suggest that the criteria for patentability should be applied to problems rather than solutions. For example, if a patent application has to be "technical", then they say that solving a technical problem is sufficient.

This is incorrect, and it's important to avoid the confusion.

Consider a company that holds meetings on the fourth floor of a building. They install a new lift, but there's a technical problem: the lift doesn't stop at even floors. Possible solutions:

  1. Modify the hardware of the lift, enabling it to stop at the fourth floor.
  2. Hold meetings on the third or fifth floor.

The first solution is technical, the second isn't.

If patent offices make the mistake of granting patents for solutions to technical problems, they will effectively eliminate the requirement for patent applications to be technical.

And then, of course, there must be a clarification that software ideas are not considered technical (in terms of the patent law).

[edit] Related pages on

This wiki is part of the End Software Patents (ESP) campaign (donate). For more information, see:
>> (Main ESP website) <<
>> (News) <<

This wiki is publicly editable. (See: It's a pool of information, not a statement of ESP's views or policies, so no permission is required. Add your knowledge! (See: Help:How to make a good contribution)