Patents Granted in Oman in 2016

There are three ways to acquire patent protection in Oman. You can either go to the Ministry of Commerce and Industry (MOCI) and file a patent application there, or you can go to Saudi and apply for a GCC level patent, or you can use the international system for patent registration provided by the Patent Cooperation Treaty (PCT). A few times every year, MOCI publishes in the Official Gazette the patent applications that it receives domestically or through the PCT. I took a look at these patent announcements that MOCI published in 2016 to see how many patents are filed and granted in Oman and to see how their inventors are.

Continue reading Patents Granted in Oman in 2016

The Economist Global Innovation Ranking: No Innovation from Oman

The Economist released a global innovation index sponsored by Cisco that ranks countries on the basis of the number of patents acquired by nationals of these countries at the US Patent and Trademark Office, European Patent Office, and the Japanese Patent Office.

All AGCC Countries, except Oman, made the list: Kuwait (Rank 37),  UAE (Rank 40), Saudi (Rank 42), Qatar (Rank 51),and Bahrain (60).

The list includes 82 countries and Oman is not on it. This means that no Omani individuals or companies acquired any patents at all from the US, the EU or Japan in the last three years.

This could be attributed to the general lack of innovation in the country due to education, professional training, or maybe even the work environment, it could also be caused by the lack of awareness of the patent system and the benefits of patent registration.

While nobody expects Oman to lead the list, it really sucks not to even be on it.

You can download the report PDF from this link. More info at the Economist.

[via IPKat]

Canada Software Patents – What Does MOPOP Say?

The Canadian Intellectual Property Office (CIPO) issues a Manual of Patent Office Practice (MOPOP) to guide applicants on the application procedure. The latest edition of MOPOP has a chapter dedicated to clarify the patentability of Computer Implemented Inventions. 

The first point emphasised by MOPOP is that Schlumberger, though the only authority on software patents, did not decide that computer implemented inventions are not patentable, but instead held that the introduction of a computer aspect to to the invention does not, by itself, make an invention any more or less patentable, and that a computer implemented invention would have to satisfy all the regular patentability requirements for the application to succeed and must fall within one of the invention categories mentioned in Section 2 of the Patent Act.

On issues of subject matter MOPOP makes it clear that a computer implemented process will only qualify as patentable subject matter upon the satisfaction of two conditions. The first is that the process must be an act or a series of acts performed by some physical agent, upon some physical object and produce in such an object some change either in character or condition.  The second condition is that the process must produce any essentially economic result relating to trade, industry or commerce. 

On the application of Subsection 27(8), MOPOP says that a claim to a method consisting only calculations made in accordance to certain formulae is excluded from patentability, because of its lack of any act performed by a physical agent upon some physical object and producing such a change of character or condition in such object. The same method will also not qualify because it does not produce an essentially economic result relating to trade, industry or commerce.

MOPOP states that there are three possible qualifying type of claims for which a computer implemented invention may be successfully patented:

  1. Art or Process (Method) Claims – These are claims for a process that defines a series of operations taking place when a computer program is run. A claim made in this form must satisfy the process requirements mentioned earlier.
  2. Machine (Apparatus) Claims – These are claims for a computer which has been configured with a novel compute program. The claims should be drafted as “means for” expressions and must involve the same level of functional step detail expected of the process equivalent claim for the same invention.
  3. Manufacture (Products or Computer Media Embodying Code) Claims – These are claims for computer readable memory devices that contain instructions to be executed by a processing system. The process to be executed by the ‘reader’ device must satisfy the requirement of a qualifying patent as specified earlier.

MOPOP also provides examples of how a qualifying claim would be drafted for each of these as well as examples of what would not be accepted as qualifying subject matter.

The MOPOP guidelines themselves seem to be very consistent with the case law and were updated before the more recent liberal decisions taken by BAP.

Should Software Patents Be Granted at All?

Software Patents
(Photo Credits: Leonard Low)

Software Patents introduce unique problems to the patent system. The main goals of any patent system is to create an incentive and a reward for inventors who create helpful inventions. There is no doubt that the computer software is one of the most important industries in today’s economy. However, they argument as to whether or not they should be patented at all is still hotly debated. 

Arguments Against Software Patents

There are several grounds for refusing software patents. The first one is that computer software is already protected by copyright. The protection of copyright is automatically granted without any formalities and it grants to the author of the software with the right to prohibit others from copying the way the software is expressed – i.e. the literal copying of the program code. While it is true that copyright’s protection differs from that of patent protection, in that a person can replicate the concept of the software without infringing the copyright if he does not copy the same code, any greater protection would be essence go beyond the expression and into the algorithm and idea behind the software and that should never be subject to patent or copyright protection as the free flow of ideas is necessary for any society to thrive.

Software patents do not easily fit into the patent system because they do not give society much value in return for the patent bargain. The patent system runs on the basis that an inventor would be granted protection for his novel invention upon the disclosure of the workings on the invention. The inventor gets monopoly over the invention and society gets to learn how the invention works through the disclosure. Satisfying this bargain is hard to achieve in the case of software patents because the applicant is never required to disclose the source code of the software, and even if they do, it is impossible for a patent examiner to determine whether this code is sufficient to rework the invention due the massive amount of the code.  This makes the software patent database available to the public pointless as they cannot learn anything about the invention by analysing the information provided and therefore the bargain is not really balanced.

Another problem with software patents is that they the length of a patent goes way beyond any expected market life of any software. The patent system was invented for “slow” industries for which the 20 year patent term allowed a company to generate a return on investment that covers its research and development costs. It is also likely for the patent subject to be still of commercial value even after the expiry of the term so that competitors can use it and built upon it. This could be not said about software patents as no software would have any value after a 20 years period and it would be very unlikely for society to derive any benefit from the the patent subject after the expiry of the term.

The earlier point is amplified by the fact that a patent application could taken up to 4 years for the patent office to examine it and grant a patent. This does not exceed the average market life of a software, but also subjects other software developers to the danger of unintentional patent infringement as they would not know about the existence even after the software becomes obsolete.

Many also believe that software patents are not necessarily at all to create an incentive for innovating in the software industry. This is apparent from the success of the “open source movement” and the success of a number of business institutions in creating profitable products and services built using open source software. In contrast, patented software is accused of being a cause for the lack of inoperability between different software and hardware and the emergernce of incompatible computing standards.

(Software patents are also very difficult to examine due to the unavailability of a sufficient database, complexity of software code, and the fact that source code is not submitted).

Arguments in Favour of Software Patents

As the industry changes and the world moves away from the ‘mechanical’ industries into digital industries it becomse essential for the patent system to adapt to these changes and provide incentive and reward for influential industries which are of the greatest important to society. 

TRIPS states that patent protection should be available for inventions in all fields of technology and the software industry is clearly an industry worth protecting. 

Though copyright may protect the expression of a computer code, this protection does not extend the way in which this code was applied in industry, and that is the protection granted by the patent system. Copyright is effective in protecting against consumer piracy, but it does not protect against the duplication of the invention by a competitor. As the investment in R&D in the software industry grows exponentially, it becomes vital for the state to provide those who invest in this industry of a method for protecting their investment. Trade secrecy is a viable solution only for a small number of business, but it is hard to maintain in large scale operations and in circumstances where the inner workings of the invention can be protected through reverse-engineering.

The available of patents is also helpful for small and medium enterprises who cannot compete with larger companies if their inventions could be easily duplicated without the protection of patents. The successful registration of SMEs is also used by these institutions as a marketing tool to attract capital which is necessary for their businesses to grow and expand.

I think that both sides of the debate have valid points. The software industry should have some protection, but the patent system clearly does not easily accommodate it. At times I think that the solution would be in the creation of a new sui generis type of protection for computer software that involves quicker examination, shorter protection term, and has protections and defences for third party in a manner that serves the software industry as it stands today.

Software Patents in Canada – Changing Position of CIPO (3)

The Canadian Intellectual Property Office (CIPO) is the body responsible for granting patents in Canada, it also issues the Manual of Patent Office Practice (MOPOP) which is used as a guideline for examiners and applicants. Though the courts opinion regarding software patents does not signal in its favour, CIPO has made a number of recent decisions allowing software patents even though it used to also have a strict position against them in the past. The latest edition of MOPOP also has a chapter explaining the requirements for a software patent to succeed.

CIPO Software Patent Decisions

After the Schlumberger court decision, CIPO took a strict position against software patents until 1998 when the Patent Appeal Board decided in favour of two software patent applications. The first is Re Motorala Inc. Patent Application No 2, 085, 228 which involved a device and a method for evaluating exponentials. The claims in the application were originally worded in the format of method claims, later changed in the prosecution stage into apparatus claims. The ‘invention’ was made up of a special software that was coupled with a Read-Only Memory (ROM). CIPO held this to be a qualify invention because of the inclusion of the ROM as a specific part required to run the software:

[T]he Applicant has invented a device which is specifically adapted to carry out the method of solving the algorithm which the Applicant has developed. This device, while it does contain many means-plus-function statements, also includes at least one specific piece of computer hardware which is a real physical element. As a result, the Board believes that the claims of this application go beyond being directed to a mere scientific principle or abstract theorem. The Applicant is not seeking to exclude others from using the algorithm itself but is seeking to exclude others from using the specific device which is claimed.

This decision is a departure from Schlumberger as the question of where the inventiveness lies was never asked, if it were it would be clear that the inventiveness here was in the software and not the hardware nor the combination of both. While the existence of a hardware is necessary for the software to run, this piece of software is generic as any computer program will have to be stored in the ROM of a computer for it to operate, and in fact, the claims of the patent would be infringed if only the software was copied and then was used on any computer as the invention would consequently be worked that way (A5).

While this new approach might be favourable by applicants, it is a departure from case law and might as well be rejected by the court if a case was ever to reach the courts. CIPO held an identical decision also in favour of the applicant in the decision regarding the Re Motorola Inc. Patent Application No. 2,047,731 where the invention related to an apparatus for carrying out a convergence algorithm for use with selected convergence rates which gives improved efficiency on math computation of J-th roots. The software was coupled with a generic piece of hardware and consequently accepted by PAB as a qualifying subject matter that is not a “mere scientific principle or abstract theorem”. It is clear from these two decisions that ANY software could satisfy subject matter requirements by simply coupling it with a generic piece of hardware.

While the Motorala decisions show the general change at CIPO in favour of software patents, other decisions seem to also soften the impact of other cases, such as Progressive Games, which could have an impact on software patents through the exception of games, business methods, and professional skills.

The first example of these new decision is Application No. 2,298,467 which involved a system for facilitating the exchange of data between two computers for the purpose of trading diamonds. The application was rejected by the examiner of several grounds including the fact that this involved a professional skill and a business method, both of which are unpatentable subject matter. The PAB rejected both of these arguments saying that “Professional skill that falls outside the scope of patent protection involves a step in a claimed method which is carried out by a human and which relies on the intelligence and reasoning of the human to make a judgement.”

The PAB avoided discussing the issue on whether or not business methods were patentable at all but stating the the claims fell within the definition of a “machine” and not a business method. This way the other rejections made by the examiner on the grounds of business methods were rebutted.

This of course is a much narrower definition of professional skill than that described in Lawson and requires an actual participation of a human person in the process for it to be disqualified.

Another decision with a similar outcome is the one relating to patent Application No. 2,119,921 which involved an improvement to a computerised stock trading system for which one of the claims was for displaying and communicating orders to an order entry system of a stock exchange computer. The examiner rejected the application on a number of grounds and one of these was on subject matter on the basis that it was that it related to the automation of features taught by prior art. The PAB rebutted the rejections of the examiner and said that the examiner confused subject matter issues with obviousness when obviousness should not form the basis of a subject matter consideration.

The PAB has also recently showed its willingness to reject the court’s analysis in Progressive Games in the decision of Patent Application 2,220,378 in which the PAB had to decide on the patentability of an application involving systems and methods for group billing in cellular telephone plans. The examiner rejected the application on the grounds of subject matter on the basis that it did “not substantially modify the art of the billing system, nor [does it] create a new or improved billing system” and that it does not “amount to a contribution or addition to the cumulative wisdom of billing systems” – which is the same ground for refusing a process according to Progressive Games. 

The PAB rebutted the rejection of the examiner stating that subject matter should be examined on its own without taking into consideration issues of novelty, obviousness, and utility and that examination should only decide on whether or not the invention can fall within one of the patentable categories of section 2, namely an art, a process, a machine, a manufacture, or a composition of matter.

This is a very logical explanation of what should be done by CIPO, but CIPO does not have the legal authority to overrule a court decision, which in this instance was clearly disregarded.  It is clear that CIPO is now more willing that ever to allow a software patent to successfully pass on the grounds of subject matter, but that does not meant the court will have the same opinion as CIPO in matters in which the court previously held otherwise.

Software Patents in Canada – The Position of the Courts (2)

In addition to the possibility of having an software patent application rejected on the grounds that it was a mere mathematical formula or abstract theorem in accordance with Section 27(8) and Schlumberger, the application might also be rejected for failing to satisfy the subject matter requirements for not being ‘art’ in accordance with section 2.

A computer program could be in essence one relating to a business method or a game, both of which have been rejected by the courts in Canada as qualifying subject matter. A business method or a game could theoretically fall under the definition of the term ‘art’ mentioned as a type of invention in section 2 of the act. In the case of Shell Oil Co v Commissioner of Patents 67 CPR (2d) 1 the court held that the “word “art” in the context of the definition must be given its general connotation of “learning or knowledge” as commonly used in expressions such as “the state of the art” or the “prior art”“.

This definition had been restricted by the courts in previous decisions to state that the term ‘art’ that do not include “professional skills”. In Lawson v Commissioner of Patents (190). 62 CPR 101 (Ex. Ct.) the court held that a method of describing and laying out parcels of land in a unique shape was not patentable as failing within the skill of a solicitor and conveyancer and that of a planning consultant and surveyor. It therefore rejected the application on the grounds that it involved a professional field and that did not fall within the meaning of section 2.

The case of Tennessee Eastman Co. v Commissioner of Patents (1970) 62  CPR 117 (Ex. Ct.) also had a decision similar to Lawson in that the court held that methods of medical or surgical treatment were also excluded because they were essentially professional skills.

It is worth noting that Lawson also defined “art”:

An art or operation is an act or series of acts performed by some physical agent upon some physical object and producing in such object some change either of character or of condition. It is abstract in that, it is capable of contemplation of the mind. It is concrete in that it consists in the application of physical agents to physical objects and is then apparent to the senses in connection with some tangible object or instrument.

The definition makes it clear that the definition of “art” requires the existence of “physical” tangible aspects for it to qualify which may sound like a very restrictive definition, however, the court later said in the case of Shell Oil Co v Commissioner of Patents (1983) 67 CPR (2d) 1 (SCC) that “‘art’ was a word of very wide connotation and was not to be confined to new processes or products or manufacturing techniques but extended as well to new and innovative methods of applying skill or knowledge provided they produced effects or results commercially useful to the public”. 

The Shell definition is a much wider one than that of Lawson, but because of the way it was worded, it was understood by the court in the case of Progressive Games, Inc v Commissioner of Patents (1999) 3 CPR (4th) 517 (FCTD) to mean that for a process to be considered an ‘art’ it must:

  1. not be a disembodied idea but has a method of practical application;
  2. be a new and innovative method of applying skill or knowledge; and
  3. have a result or effect that is commercially useful.

The case of Progressive Games involved a patent application for a modified version of a poker game which the court held not to be an “art” when applying the Shell Oil test as the game did not amount to “a contribution or addition to the cumulative wisdom on the subject of games” and “do not substantially modify the poker game as it exists nor do they create a new game”.

Progressive Games is another block facing the successful application of software patents as many of them are games or business methods. The new interpretation of Shell Oil in this case makes the satisfaction of subject matter issues a complex matter than requires examining novelty, non-obvious and utility at the same time. This cannot be right because it will give a patent examiner to have a “second kick at the can” for attacking the application based on these separate elements (A6). Some of the steps in the Shell Oil test also create a great level of uncertainty, as they are unlike the real separate stand alone elements, do not have established and clear tests for satisfying each of these steps (A6).

Regardless of the method for reaching the outcome of the case, it is clear from all previous court decisions that the court is not in favor of software and similar patents that do not involve a tangible element as it has never allowed them in all the instances that actually reached the court, even in the last decision of Progressive Games which was decided in 1999.

This dislike of software patents is not shared by CIPO. It will be seen from the upcoming post that CIPO has decided to use its own interpretation to allow some recent software patents to succeed even though they would have been rejected if the same court tests were applied.

Software Patents in Canada – The Position of the Courts (1)

Software Patents in Canada

The position of the software patents in Canada is not a straightforward one. There is no explicit prohibitions on the patentability of software patents (or business methods) in the Canadian Patent Act, but the only software patent case that ever reached the court decided that software inventions are not patentable. This case was decided in 1981 and the computer and internet revolution has changed the face of Earth since then and there seems to be a general preference for having patents for software in the Canadian Intellectual Property Office  – which indicates in its Manual of Patent Office Practice that a qualify software may be granted a patent. The CIPO did not stop there as it has already allowed the successful application of a number of software patents. CIPO decisions and MOPOP has no legal authority, so the fact that they are granting software patents does not mean that the court will hold them valid if ever challenged.

I will examine in this post the position of the courts and various grounds for which a software patent may be rejected and then will follow that with how CIPO has changed its position over time.

Requirements Under the Patent Act

For a patent application to succeed in Canada it must satisfy the invention subject matter requirements (Section 2), novelty (s28(2)), non-obviousness (s28(3)) and utility (s2).

For application to satisfy the subject matter requirements it must fall within the definition of “invention” in Section 2 of the Act which states that it must be an “art, process, machine or composition of matter, or any new and useful improvement in any art, process, machine, manufacture or composition of matter”. This definition is subject to sub-section 27(8) which prohibits the grant of a patent for “any mere scientific principle or abstract theorem”.

Novelty is a quantitative criteria of “newness” that requires the invention not to be part of the state of the art at the of filling.  (MOPOP S15.01.01) This basically means that the invention must not have been built, or described in a single document that contained sufficient information to allow another person to make the invention, before the application for the invention was filed.

Non-obviousness is a qualitative criteria of “inventiveness” that requires the invention not to have been obvious to a person of skill in the art at the time of filling. The test of obviousness is whether or not an unimaginative skilled technician would, in the light of the state of the art and common general knowledge at the time of filling date, be led directly and without difficulty to the invention covered by the claim. (MOPOP S15.01.02)

Utility is a requirement for the invention to be “useful” for the purpose for which it was designed. (MOPOP S15 + Progressive Games v COP)

Software patents are usually rejected on subject matter grounds and not on novelty, non-obviousness, or utility, which do not create any software specific problems to the patent application.

General Position of Software Patents – The Schlumberger Case

The only software patent case that reached the courts in Canada is the Schlumberger case (Schlumberger Canada Ltd. v. Commissioner of Patents (1981) 56 C.P.R. (2d) 204 (FCA)). The application in this case involved a computer system for the analysis of soil characteristics data for the purpose oil and gas exploration. CIPO rejected the application on the grounds that it was merely a computer program which did not fall under the definition of invention under section 2 of the Patent Act.

The application reached the Federal Court of Appeal which used a two step test to decide whether or not the application should be allowed:

  1. What has been discovered according to the patent application?
  2. Is that discovery patentable regardless of whether a computer is or should be used to implement discovery?

In applying this test the court held that “[w]has is new here is the discovery of the various calculations to be made and of the mathematical formulae to be used in making those calculations. If those calculations were not to be effected by computers but by men, the subject-matter of the application would clearly be mathematical formulae and a series of purely mental operations; as such, in my view, it would not be patentable,” and consequently rejected the application on the grounds of Section 28(3) against the patentability of a “mere scientific principle or abstract theorem”. 

This court decision made it clear that the mere addition of a computer in a patent application will not change the subject matter of the discovery so as to rescue what is originally unpatentable. A mathematical formula was not allowed to be patentable just because it is processed by a computer.

Though Schlumberger is the only case involving software patents and it was clearly not in favour of allowing software patents, the decision did not prohibit patenting ANY software related invention, but merely one in which “what was discovered” would not be considered as a qualifying subject matter if a computer is or should be used to implement it.

CIPO interpreted this a consequent decision (Application No. 96284) to mean the following:

  1. Claims to a computer program per se are not patentable;
  2. Claims o a new method of programming a computer are not patentable;
  3. Claims to a computer program in a novel manner where the novelty lies solely in the program or algorithm are not patentable;
  4. Claims to a computing apparatus programmed in a novel manner, where the patentable advance in the apparatus itself, are patentable; and
  5. Claims to a method or process carries out with a specific novel apparatus devised to implement newly discovered idea are patentable. 

This summary corresponds with the Schlumberger case as a pure computer program or an invention in which the novelty is in the program are not patentable, while an invention that uses a computer program and has its novel aspect outside the computer program would be patentable.

This position was justified at its time as the software industry was still in its early days and computer hardware was a bigger industry in which innovation was rapidly changing. Research and Development could have been easily protected by the patent system with the Schlumberger decision as the decision allows computer related inventions to be patentable where the innovation is in the apparatus (the hardware) and that adequately protects and promotes this industry.

However, this position is changed now as software is clearly one of the most important industries in world economy and there is a great need to protect and promote the investment in this field. This change in important in software is reflected in more recet CIPO decisions, which are not binding and can be overturned by any court if ever challenged.

But before we turn to the CIPO decision, we should talk in the second post about other more recent additional obstacles that face software patent application as became apparent from business method patent applications, which face a very similar objects at CIPO.

Software Patents (EU, US, and Japan)

Software Patents
(Photo Credits: Leonard Low)

A patent is a powerful tool that grants monopoly over an invention you make. The scope of its protection differs from copyright. In the context of software, copyright will only protect literal copying of the code, but it will not protect against the recreation of the same program using original code – even if the new application has program or even identical functions to your program. A patent on the other hand grants protection for the application of the ideas of the program regardless of how that application happened, so even if your program was written using a new completely different code, if that program carries out a process or creates a product similar to what you have your patent application, then you would have the right to stop them from using that program or you can claim damages for their infringing use.

The problem with computer programs (and business methods as well) is that they are generally considered as subject matter which is unprotectable by patents. Each jurisdiction has a different reason behind this ban of software patents and also provides a way to go patent your software “around” the allowed subject matter.

In Europe, patents are granted by the European Patent Office which governs its patent grant procedure through the European Patent Convention 2000.  According to Article 52(2) of the EPC computer “programs for comoputers” are not to be regarded as inventions as such. The keyword here is “as such”. The EPC has been interpreted by the EPO in a way that excludes only computer programs when they are claimed to be “the invention” itself as that would be a claim to an excluded subject matter “as such”.

EPO decisions were inconsistent and unclear as to their legal grounds for granting this protection and it suggests that a computer program will not be excluded if the program includes a ‘technical character’, but there is not definition as to what ‘technical character’ means. In mid 80s decision of Viacom (T-208/84), the EPO held that the invention in question made a “technical contribution to the known art” and was therefore patentable. This decision was followed by that of IBM (T-22/85) in which the patent application was refused on the ground that it the invention lacked a “technical character” as it did not “provide a technical contribution to the art”.

The principle shifted for a “contribution” of this vague “technical contribution” element to the need for the presence of this “technical character” element in the invention itself. In the decision of Hitachi (T/258/03) it was stated that “What matters having regard to the concept of invention within the meaning of Art.52(1) EPC is the presence of technical character which may be implied by the physical features of an entity or the nature of an activity, or may be conferred to a non-technical activity by the use of technical means”. No definition was given as to what “technical effect” meant, and instead the EPO admitted in PBS Partnership (T-931/95) that “the meaning of the term “technical” or
technical character” is not particularly clear.”

Although the EPO has granted many patents for computer programs, the grounds for doing so do not seem to be clear at all at the term “technical character” was never defined. However, the key to getting a European patent from the EPO for a computer program would be not to claim the invention as a computer program and instead attempt to claim it as invention for doing something using a computer program. Claims in the patent application must also be carefully drafted to make sure that they do not fall under any other exceptions under 52(2) for abstract ideas or business methods.

In the US, the Patent Law (Title 35 USC) does not include a statutory bar on computer programs or business methods, however, this exception was developed through case law as it was established that “laws of nature, physical phenomena and abstract ideas” are not patentable subject matter (Case:�Diamond v. Diehr (1981)). The application for many computer program patents failed on the grounds that there were mere abstract ideas as all they were constituted of mathematical formulas.

This position changed in the year 1998 where the court held in the case of State Street Bank v. Signature Financial Group (1998) that a business method will not not be considered an abstract idea if it produced “a useful, concrete and tangible result”. The same principle was then applied to many computer applications as, for example, the production of computer data that resembles a real life solution (e.g. stockmarket prices) produces a useful, concret, and tangible result. One of the most famous business method patents granted in the US is Amazon’s 1-click patent.

However, in the very recent case of Re Bilski (2008) the court rejected the principle of the mere need of “a useful, concrete and tangible result” of State Street as the ultimate saviour of business method patents stating that it was “inadequate”. The court held in this case the right to test to use was a “machine or transform” test which requires the business method to be attached to a specific machine for it to qualify as an invention OR for the business method to transform a particular article into a different state or thing.

Re Bilski is a very recent case and the exact impact of it on the scope of computer programs is still unknown, but it has surely reduced its scope significantly as no longer the fact that the program produces ‘a useful, concret and tangible result’ is sufficient for it to qualify as an invention, but it must be attached to a specific machine or must be a transformative process.

In Japan, the law requires an invention to be “a creation of technical ideas utilizing a law of nature”. This has meant for Japan that pure software patents will not qualify as they do not are not ‘technical’ in nature (even Software as a subject matter is explicity considered as patentable subject matter), however, the JPO Guidlines states that this requirement can be satisfied by simply “realising the program using hardware resources” – and that apparently provides the technical element needed for escaping the requirement. (Check JPG Guidelines for Computer Software Related Inventions – Warning PDF).

Software patents will not automatically succeed if they prove that they are not included in any of the exceptions found in various patent laws, each of these jurisdictions require a patent to be novel, non-obvious, and be capable of industrial application (or useful in the US).

Invention Patents in Europe

(Photo credits: telethon)

Patents are monopoly rights for a certain period of time given by a state to those who create qualifying inventions in return of their disclosure to the public of the details of their inventions. 

This means that if you make an invention which you would like to sell and at the same time make sure that nobody else copies this invention you made, you will have to apply for a patent. The patent will usually grant you a maximum of 20 years to stop others from copying your invention. After these 20 years your patent will become public domain and anyone will be able to manufacture it without paying you any royalties or licensing fees. 

Patents grant a monopoly right only in the jurisdiction in which the patent was registered in. You will have to register in each country on its own if you wish to execrise your monopoly right in that country. This post will only talk about the patent system in Europe as the law differs from one jurisdiction to the other. I will talk about the US and Japan in later posts. (Oman’s law is very similar to American law, so I will talk about it in that post).

In the field of technology you can get a patent for a product, a manufacturing method, or a method to create a specific product. It is also possible to get a patent in certain circumates for a computer program.

There are currently two methods for getting a patent in Europe, the first is by going to each country on its own and registering for a national patent, the second is by going to the European Patent Office (EPO) and apply for a bundle of patents for all the member countries of the European Patent Convention. It is worth mentioning that this is NOT an EU intiative and it goes beyond the members of the EU. Getting your patent from the EPO is cheaper than going to all the European countries. An EPO patent is not a *super* European Patent, but a bundle of national patents from all the members. This means that once you patent is issued, if a national court decides that your patent is invalid for any reason then you patent will be invalid in that one country by itself and will not affect the validity of the patent in other places. This is pretty messed up, but because of the lack of a higher court of appeal to take care of European Patent, the industy will like to keep the current system as it is less risky than one which has a super European patent.

So what do you have to do to get a European patent from the EPO?  You simply have to fill a patent application and submit it to the EPO. However, for your patent to be granted, your creation must satisfy the requirements of the European Patent Convention (EPC), namely:

  1. It must be an invention.
  2. It must be novel.
  3. It must have required an inventive step to make.
  4. It must be industrially applicable.

We will go through these one by one:

Your creation must be an invention: The EPC does not define an invention but says that a patent may be granted for any invention in all fields of technology. However, explicity exludes inventions such as absolute theories, mathematical methods, aesthetic creations, mental acts, and mere presentation of information. The EPC also excludes inventions that contravene the public order, methods for treating the humn or animal body (methods – not products), and plan or animal varieties.

The requirement for an invention is usually not problematic, except for the fact that one of the exceptions under Art 52(2) is computer programs. The stance of the law in Europe regarding this is not clear, but I personally understand it as follows, if an invention is a pure computer application that has no novel tangible aspect then it will not be patented, however, if a computer program has some tangible aspect that extends beyound the code, then it will be patented. For example, a word processing application does not create by itself have a tangible aspect, but a program that affects the brightness of the screen depending on the time of the day has that tangible aspect. DO NOT CITE ME ON THIS, THIS IS MY PERSONAL OPINION AND I CANNOT BE BOTHERED TO DIG UP THE CASES/DECISIONS THAT SUPPORT MY OPINION AT THIS MOMENT.

The second requirement for the patent is to be novel. This is a quantitative absolute test that requires the patent to be a new. Art 54 of the EPC says that an invention is considered new if it does not form part of the state of the art.  This simply means that your invention is not like anything we have seen before the date the priority date (first filing date). This is an important because it requires the inventor NOT to disclose the functional details of his invention to the public before he files his patent application, if the information is already in the public, then the patent application will fail.

The novel will not be satisfied if a single disclosure in the relevant industry field (the fact that people from an irrelvent industyr know about it does not invalidate it) has a clear and unmistakable disclosure (the fact that it had to be *figured* out does not invalidate it) his made available  (it will be invalidated by making it available, no need to actually be seen or read) to a skilled a person (if the only person who heard or saw it did not understand what you were talking about then that will not invalidate it). 

The EPC provides an exception when the information was disclosed through an act of breach of confidence, or if the information was disclosed in an official international exhibition, if any of these two happen, the inveotor has six months from that date to make his application for that action not to invalidate his patent.

The requirement for an inventive step: This is a qualitative test. I think of it as the “It must be good enough to be protected” test. The patent will only be granted for inventiosn which are not obvious to a person skilled in the specific industry. If the invention is new, but it was an obvious progression from existing technology then it will not be protected.

Deciding whether an invention involved an inventive step requires the analysis of this step at the priority date, this is problematic because the patent examiner usaully looks at a patent months or even years after the patent was actually filed. So he must disregard all technological advancements that took place throughout that time and decide where there was an inventive step at the priority date. It is usually very easy to say in hindsight that any invention was obvious, so the EPO attempts to use a test called the ‘Problem and Solution Test”, which tries to envision the problem the invention tries to solve and see if this solution has an inventive step.

The problem and solution test consists of the following:

  1.  Indetifying the closest prior art.
  2. Determining the objective technical problem (the technical problem which the invention attempts to solve).
  3. examining whether or not the claimed solution to the problem is obvious for a skilled person in view of the state of the art.
An examiner will also look at secondary considerations IF he is not sure about the answer to the question 3 of the problem and solution test. These secondary considerations include a ‘long felt need’, ‘commercial success’, and ‘unexpected technical effect’. Secondary considerations will not rescue an invention that is obvious, but will be useful in close cases and those in doubt.

The invention must be industrially applicable: This is a requirement that is never unsatisfied because industry is defined as any industry (including agriculture – which is apparently not considered as an industry in France). But anyway, the requirement will only fail for inventions which are impossible to make.