How do you draft software patents that survive Section 3(k) and §101?
Most software and AI applications fail in the same two places: Section 3(k) of the Indian Patents Act, 1970 at the IPO and 35 USC §101 / MPEP §2106 at the USPTO. Both can be addressed at the drafting stage. Here is how Sitabience IP approaches each.
Drafting around Section 3(k) of the Indian Patents Act
Section 3(k) is not a surprise it is a predictable test the IPO will apply to every software claim, set out in the Patents Act, 1970 and elaborated in the IPO's Computer-Related Inventions (CRI) Guidelines, 2017. Treat it as part of the drafting brief, not as something to argue about later.
Examiners apply Section 3(k) to most software-related applications. A claim drafted as a pure computer programme, mathematical method or business method is refused as a matter of routine.
Claim a technical method with a defined technical effect. Anchor the description in the hardware that is actually involved. Make the inventive technical contribution visible inside the independent claim, not buried in the specification.
Independent claim, dependent claims and description are written together. If the technical effect cannot be pointed to in the original specification, it cannot be relied on later so it is put in at the start.
Drafting around 35 USC §101 and the Alice test
Alice rejections under Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014) applied through the USPTO's two-step test in MPEP §2106 are one of the most common reasons strong software and AI inventions stall at the USPTO. The patent that gets through is the one that took §101 seriously at the drafting table.
Following Alice Corp. v. CLS Bank International (2014), the USPTO uses a two-step test under §101. Many software and AI applications get classified as directed to an abstract idea and refused.
Claims are framed around a specific technical improvement to a computer or to another technology. The inventive concept that adds significantly more is identified and is given real weight inside the independent claim.
Description carries the technical detail an examiner needs to see. Eligibility, novelty and non-obviousness are addressed together at drafting, so prosecution does not turn into a rebuilding exercise.
Software patent eligibility: IPO vs USPTO vs EPO
The same invention often needs differently shaped claims for each office. This is the short version.
| Office | Governing rule | What examiners look for | Drafting move |
|---|---|---|---|
| Indian Patent Office (IPO) | Section 3(k), Indian Patents Act, 1970 + IPO CRI Guidelines, 2017 | A defined technical effect tied to specific hardware, not a computer programme per se. | Claim a technical method or system; anchor the description in hardware interaction. |
| USPTO | 35 USC §101 + Alice/Mayo two-step test (MPEP §2106) | A specific technical improvement plus an inventive concept that adds significantly more. | Frame claims around the technical improvement; put the inventive concept inside the independent claim. |
| EPO | Article 52(2)(c) and 52(3) EPC + Comvik approach (T 641/00) | A further technical effect beyond the normal interaction of program and computer. | Identify the technical features that contribute to the technical character; carry inventive step on those features alone. |
Sources: Indian Patents Act, 1970 (§3(k)); IPO Computer-Related Inventions (CRI) Guidelines, 2017; 35 USC §101 and USPTO MPEP §2106; Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014); European Patent Convention, Art. 52; EPO Boards of Appeal, T 641/00 (Comvik).