A Comparative Analysis Of Patenting Software Related Inventions

Introduction

The dispute over software patents focuses on two issues: first, whether computer software is patentable, and if so, what should be the boundaries of patent protection. There are variances on both of these fronts, but in the interim, major patent offices throughout the world have granted several software patents, leading to the development of various examination guidelines and case laws, which has led to a variety of standards of protection. Despite the fact that there is no accepted meaning of the term “software patent.” A software patent, according to one definition put out by the Foundation for a Free Information Infrastructure, is a patent on any computer performance achieved by procedures for a computer programme. Software designs and concepts are protected by software patents. Software subsequently incorporates these concepts. A particular patent may prevent others from developing software that performs a function in a specific way or from using a certain set of computations.

[Image Sources : Shutterstock]

Patent law

The rapid development of software from a scientific and mathematical calculator to a pervasive product that has permeated practically every element of contemporary technology and living is the cause of the complexity and confusion surrounding software patents. Software has long since been seen as a sticky situation in terms of patent law. The software is a theoretical innovation, as many have noted, but original ideas are not eligible for protection. By conducting a comparative analysis between the USA and India, this paper investigates what that means, the enforceability of software patenting, and judicial approach towards software patenting.

The Patent Amendment Act of 2005 intended to establish software patents in India. The Patent Amendment Act of 2005 proposed a change to clause 3 (k) to include “a computer programme per se other than its technical application to industry or a combination with hardware; a mathematical approach or a business method or algorithm.” However, the Indian Parliament rejected this revision and opted to keep section 3(k) in its original form. The ordinance’s requested modifications were retracted. As stated explicitly in the Patent Act, computer software as a whole is not patentable. It could also be argued that the provision stating that software itself is not patentable means that only software that is a component of a larger invention, of which it is a part, could be taken into consideration for a patent as a whole, provided that it satisfies the Act’s requirements for a patent.

This demonstrates that under Indian law, software “standing alone” is not patentable. A software programme does not become an invention simply by being equipped with ordinary data processing machinery. The innovation can only be patented as a whole if the software application is a component of a sizable system and the system as a whole is patentable. The requirement that computer programmes are “per se” not patentable is found in Section 3 (k). What does “per se” actually imply here? In accordance with the Joint Committee’s 1999 report on the Patent (Second Amendment) Bill, “The addition of “per se” was suggested since occasionally the computer programme may incorporate other items that are related to or built upon it. If they are inventions, there is no desire to deny them a patent. However, it is not designed to give patents for computer programmes as a whole. The change was suggested to make the goal more clear.” Following the stance taken by courts in the EU and the UK, the Delhi High Court’s ruling in the Ericsson v. Intex case made it apparent that computer-related inventions with a technical contribution or technical effect are patentable in India.

Until 2015, there was no consistency among India’s four patent offices (Kolkata, Mumbai, Delhi, and Chennai) on the topic of granting software patents. This was also underlined by the Intellectual Property Appellate Board (IPAB) in the case, Yahoo v. Controller. It was discovered that, in the  absence of any regulations on the subject of patents on computer-related inventions (CRI), some patent offices were inclined to grant software patents while others were not . The Controller of Patents published CRI recommendations in order to eliminate irregularities in the award of software patents in India. Reviewers may depend on the following three-stage test for evaluating CRI applications, according the CRI Guidelines of 2016: If the contribution is only a mathematical, business, or algorithmic method, the claim should be properly construed and rejected. If the contribution is a computer programme, the claim should be checked to see if it is being made in conjunction with any novel hardware before moving on to other steps to determine the patentability of the invention. A computer programme cannot ever be patentable in and of itself. Deny the claim if the only contribution is made by the computer programme. Continue to the next steps in the patentability process if the contribution is found in both the computer programme and the hardware. 2016 criticisms prompted the creation of revised CRI standards for 2017. The elimination of the prior guidelines’ three-step examination method is the most significant aspect of the most recent guideline. Recent documentation makes no mention of novel hardware for patent awarding. Even subtle or implied references to hardware have been deleted as a result of the thorough rewriting process. The 2017 rules simply provide clarification to the patent office’s prior recommendations, according to the official viewpoint of the Indian Patent Office as stated by PTI. There has been no change in the policy of patenting CRIs.

To begin with, US courts viewed software patenting with suspicion and have repeatedly ruled that it is not patentable under US law because it is simply a mathematical formula. The Court later altered its mind, stating that the innovation should be viewed as a whole and that patent protection shouldn’t be withheld only because it involves mathematical formulae as a result of Diamond v. Diehr. But there were still two exceptions: the first was the exception for mathematical algorithms, and the second was the exception for business methods. In Diamond v. Diehr, the patent application described a better way to cure rubber by employing a computer to repeatedly recalculate the ideal curing time using a predetermined formula. It was decided that the patent claim did not attempt to anticipate the use of mathematical calculations and instead described a method for curing rubber, which was obviously an industrial process covered by the Patent Act. The Court concluded that the subject matter was not non-statutory simply because a computer programme and a mathematical equation were present. In order for software to qualify for patenting, it must perform a practical application and be more than just a manipulation of an abstract idea, as is clear from case law.

Conclusion

The degree, mechanism, and extent of software protection vary greatly around the globe. Despite the fact that TRIPS protects computer software with copyrights, it has been contended that it implicitly also protects patents. The law relating to software patenting has mostly been formed by local courts and legislators, which in turn have been heavily impacted by their own interests, as a result of international processes’ inability to harmonise it. Through this article, we can clearly observe the conflicting viewpoints that exist in the US and India, which have had a significant impact on the entire world. The United States, on the other hand, appears to give patents to “anything under the sun invented by man.” India, on the other hand, has traditionally maintained a stringent stance. The preceding section shows that the scope of software patentability varies. As a result, although India places a strong focus on “technological advancement,” the US has taken a more lax stance and expressly permits the use of a formula.

Author: Tanya Saraswat, in case of any queries please contact/write back to us via email to chhavi@khuranaandkhurana.com or at Khurana & Khurana, Advocates and IP Attorney.

References

  • Ravindra Chingale and Srikrishna Deva Rao, “Software Patent in India: A Comparative Judicial and Emperical Overview”, 20 Journal of Intellectual Property Rights, July 2015
  • Terrell on the Law of Patents, 18th Edition, Sweet & Maxwell (Thomson Reuters), 2016

Leave a Reply

Categories

Archives

  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • February 2011
  • January 2011
  • December 2010
  • September 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010