Beyond 'Per Se': Computer-Related Inventions under Section 3(k) after Ferid Allani — India, EPO and US

This bundle plans and structures an LL.M. dissertation in Intellectual Property Law on one of the most litigated questions in Indian patent practice: when does a software-implemented invention escape the exclusion in section 3(k) of the Patents Act, 1970? Section 3(k) excludes "a mathematical or business method or a computer programme per se or algorithms" from patentability. For two decades Indian examiners read the words per se narrowly, often demanding novel hardware, until the Delhi High Court in Ferid Allani v. Union of India (2019) held that an invention showing a technical effect or technical contribution is not a computer programme per se, and directed examination under the 2017 Guidelines for Computer-Related Inventions (CRIs).

The dissertation asks whether that shift has produced a coherent, predictable test. It uses three methods: a doctrinal study of section 3(k), its legislative history (the 2002 amendment, the 2004 Ordinance and its lapse in 2005) and the CRI Guidelines; a comparative study of the European Patent Office's "as such" and technical-character approach (EPC Article 52, COMVIK, G 1/19) and the US Alice framework under 35 U.S.C. § 101; and a content analysis of a sample of Controllers' decisions and High Court appeals to see how the test is applied in practice. The outcome is a 100–130-page dissertation with proposed examination criteria that the board of examiners can test against real decisions.

Abstract

India's software and digital-services sector files a large and growing share of patent applications, but section 3(k) of the Patents Act, 1970 excludes computer programmes per se, algorithms and business methods. After Ferid Allani v. Union of India (Delhi High Court, 2019), the Patent Office and High Courts have moved towards a technical-effect test, yet applicants and examiners still disagree about what counts as a technical effect. This dissertation examines the provision's text and history, compares the Indian position with the European and US approaches, and analyses a sample of decisions to propose clearer examination criteria.

Introduction

The words per se were added by the Patents (Amendment) Act, 2002. The Joint Parliamentary Committee explained that computer programmes with other things ancillary to them or developed on them may be patentable. The Patents (Amendment) Ordinance, 2004 tried to widen the provision to programmes with technical application to industry or combined with hardware, but the Patents (Amendment) Act, 2005 dropped that language. The Patent Office issued guidelines on CRIs in 2015, 2016 and 2017, and Ferid Allani read the provision in light of the 2017 Guidelines. The Supreme Court's purposive reading of another section 3 exclusion in Novartis AG v. Union of India (2013) 6 SCC 1 shows how the legislative history of section 3 is used in interpretation.

Literature gap

• Commentary on section 3(k) largely predates or only summarises Ferid Allani.
• Comparative work cites the EPO and Alice but seldom tests whether Indian decisions actually apply either approach.
• There is little systematic analysis of Controllers' reasoning in CRI refusals and grants.

Research design

Doctrinal and comparative, supported by a qualitative content analysis of decisions; eight chapters; Bluebook citation.

Feasibility

Statutes, guidelines, Controllers' decisions and judgments are publicly available from IP India, India Code, the Delhi and Madras High Court websites, the EPO and the USPTO. No human participants are involved.

Section 3(k) of the Patents Act, 1970 excludes computer programmes per se, algorithms, mathematical methods and business methods from patentability. Since Ferid Allani v. Union of India (2019), Indian law recognises that an invention demonstrating a technical effect or technical contribution is not excluded merely because it is implemented in software. However, the statute does not define technical effect, the Guidelines have been revised several times, and different Controllers and benches appear to apply different tests: some look for improvement in the functioning of the computer itself, some for any effect outside the computer, and some still ask for novel hardware.

This uncertainty affects applicants deciding whether to file in India, examiners writing refusal orders, and courts hearing appeals after the abolition of the Intellectual Property Appellate Board in 2021. The dissertation asks what test Indian law now applies, how it compares with the European technical-character approach and the US Alice framework, and whether clearer criteria can be stated without rewriting the statute.

In scope

• Section 3(k) and related definitions in sections 2(1)(j) (invention) and 2(1)(ja) (inventive step) of the Patents Act, 1970.
• Patent Office CRI Guidelines (2015, 2016, 2017 and any later revision in force when you write).
• Ferid Allani and subsequent Delhi and Madras High Court decisions on CRIs, located and read in full by the researcher.
• EPO: EPC Article 52(2)–(3), T 641/00 (COMVIK), T 1173/97, G 1/19.
• US: 35 U.S.C. § 101, Diamond v. Diehr, Mayo v. Prometheus, Alice Corp. v. CLS Bank.

Out of scope

• Copyright protection of software and trade secrets, except where needed for context.
• Section 3(d) pharmaceutical issues, cited only as an interpretive analogy.
• Standard-essential patents and FRAND licensing.

Research design

A doctrinal and comparative study with a supporting qualitative content analysis of decisions.

Research questions

1. What does per se in section 3(k) mean in light of its legislative history and the CRI Guidelines?
2. What test did Ferid Allani adopt, and how have later High Court decisions and Controllers applied it?
3. How do the EPO's technical-character approach and the US Alice framework resolve the same question, and what can India borrow?
4. Can a clearer set of examination criteria be stated within the existing statute?

Hypotheses

• H1: After Ferid Allani, Indian decisions increasingly apply a technical-effect test, but the meaning of technical effect varies between decisions.
• H2: A requirement of novel hardware still appears in some refusals despite its removal from the 2017 Guidelines.
• H3: The Indian approach is closer to the EPO's technical-character reasoning than to the US Alice framework.

Sources, in order of authority: Patents Act and Rules → Supreme Court → High Courts (and earlier IPAB decisions) → Controllers' decisions → Patent Office guidelines and manual → foreign statutes, EPO Boards of Appeal and US Supreme Court (persuasive) → books and peer-reviewed articles.

Content analysis: draw a sample of Controllers' decisions involving section 3(k) from the IP India decisions database over a defined period; code each for the test applied (per se only, technical effect, hardware requirement, business-method finding), claim type and outcome; re-code 20% after a week to check consistency; present descriptive tables with the sampling frame stated.

Timeline (24 weeks): weeks 1–3 proposal; 4–7 Indian doctrinal chapters; 8–11 EPO and US chapters; 12–15 content analysis; 16–18 comparative analysis; 19–20 conclusions; 21 similarity check; 22–23 revisions; 24 binding and viva preparation.

Citation and integrity: Bluebook (21st ed.) or ILI uniform style, used consistently; Zotero; similarity check under the UGC Regulations, 2018.