The Delhi High Court has
dismissed BlackBerry's long-pending patent appeal, holding that an invention
for colour-coding email recipients based on domain names does not constitute a
patentable "technical effect" and falls squarely within the exclusion
for computer programmes per se under Section 3(k) of the Patents Act,
1970. The Court also upheld the Controller's finding of lack of inventive
step in view of three prior art documents.
I. Background and the
Invention
BlackBerry Limited, the Canadian
multinational known for its enterprise software and smartphones, filed Indian
Patent Application No. 1976/DEL/2008 on 20 August 2008, claiming priority from
European Patent Application No. 07117003.9 filed on 21 September 2007. The
application was titled "Colour Differentiating a Portion of a Text
Message Shown in a Listing on a Handheld Communication Device."
The invention addressed a
practical problem familiar to smartphone users: on a handheld device with a
small screen, it is difficult to quickly identify intended recipients of an
outgoing email — particularly to distinguish internal recipients (same domain)
from external ones. The proposed solution was to dynamically colour-code
recipient names in the address field of an outgoing message based on the
host name or domain name of each recipient's email address, enabling the sender
to instantly spot any unintended external recipients before sending.
The invention claimed a method by
which: (i) a message address is examined to extract the host/domain name; (ii)
recipient names are displayed in a colour differentiated by their respective
domain affiliation; and (iii) this colour-coding occurs in real-time as the
user composes the message — not merely after receipt.
II. Procedural History
The journey of this application
through the Indian patent system spans 18 years:
- 2008: Application filed
at the Delhi Patent Office
- 2009: Published under
Section 11A
- 2014: First Examination
Report — objections under Sections 2(1)(j) and 3(k)
- 2015: Response filed by
BlackBerry's agent
- August 2019: Hearing;
oral Section 3(k) objections; post-hearing submissions filed
- October 2019: Impugned
Order I — application refused
- November 2019: Review
Petition filed under Sections 77(1)(f) and 15
- March 2020: Impugned
Order II — Review dismissed
- 2022: Appeal filed
before the Delhi HC under Section 117A
- 30 April 2026: Delhi HC
dismisses the appeal
III. The Prior Art — D1, D2,
and D3
D1 — EP1767008A1
("Message Recognition and Display System"): Applies visual
identifying styles to *received* messages on mobile devices,
categorising them (urgent, family, professional) using message attributes. The
Controller held that modifying D1's algorithm to use domain-based recipient
categorisation for *outgoing* messages was obvious to a PSITA.
D2 — US6671718B1
("Email Client Application Incorporating an Active Transmit Authorisation
Request"): A system alerting users before sending, displaying all
recipients for confirmation. Shared the same underlying problem as the Subject
Application — preventing messages being sent to unintended recipients.
D3 — US2003/0084109A
("Efficient Message Notification System"): Discloses visually
distinguishable formats — including colour differentiation — corresponding to
different individual users. Cited in the original Hearing Notice, relied upon
by the Controller in HC proceedings.
IV. BlackBerry's Arguments
BlackBerry advanced four
principal lines of argument:
(a) Technical problem and
technical solution: The invention solves a genuine technical problem — the
inability of handheld devices with limited screen size to allow users to
implement desktop-style filters. The solution (real-time domain-based colour
coding) is a technical solution to a device-level constraint. Reliance was
placed on *Ferid Allani v. Union of India* (2019) for the
"technical contribution" test.
(b) Inventive step: D1
applies colour coding to *received* messages by content attributes; the
Subject Application applies colour coding to *recipients* of *outgoing*
messages by *domain names* — a substantively different approach. The
Controller's conclusion was criticised as impermissible hindsight reasoning.
Reliance was placed on *Enercon v. Aloys Wobben* (Order 123/2013):
"most inventions are built with prior known puzzle-pieces" and
hindsight deduction is unacceptable.
(c) Technical effect: The
invention provides improved reliability and security at the device level,
reduces user-device interaction steps, and prevents inadvertent disclosure —
none of which are merely administrative outcomes.
(d) International grants:
Corresponding patents had been granted in the US (US8682394B2) and EU
(EP2275980B1). BlackBerry also highlighted two successful earlier appeals
before this Court: 2025:DHC:3100 and 2024:DHC:6572.
V. The
Controller's Grounds for Refusal
Ground 1 — Lack of inventive
step (Section 2(1)(j)):
The difference between D1 (colour
coding of received messages by message attributes) and the Subject Application
(colour coding of outgoing recipients by domain name) was held to be a
"superficial" algorithmic distinction obvious to a PSITA combining
the teachings of D1 and D2.
Ground 2 — Section 3(k):
The invention's contribution lies
entirely in a software algorithm. It does not affect hardware performance or
modify how the device processor operates. The "technical problem" of
sending to the wrong person was characterised as a human/administrative error,
not a universal technical problem. The Impugned Order stated:
"A
technical problem is universal in nature and technicality is not varied person
to person. For example noise in a communication system. Here every person faces
the same noise problem... But an error in sending a message with respect to
recipient cannot be considered a technical problem because it depends on the
person sending the message."*
VI. The Delhi High Court's
Analysis
Justice Tejas Karia dismissed the
appeal on both grounds.
On inventive step: The
Court accepted the Controller's analysis. D1, D2, and D3 read together rendered
the Subject Application obvious. The algorithmic difference between D1's
categorisation (urgent/family/professional) and the Subject Application's
categorisation (by domain name) was a straightforward modification for a PSITA.
This was legitimate mosaicking — not impermissible hindsight.
On Section 3(k): The Court
applied the "technical effect / technical contribution" test from *Ferid
Allani*, *Microsoft Technology Licensing* (Madras HC 2024), and the
CRI Guidelines, holding:
"The
algorithm in the present invention is only related to colour coding on the
basis of message characteristic and is not enhancing the system's
functionality. The present invention relates to CRI, but does not result in a
'technical effect' that improves the system's functionality and efficacy at the
hardware level."
The Court observed that even
after implementation, the user could still send a message to the wrong person
(e.g., where multiple recipients share the same domain and different colours
are assigned). The sole hardware element — the wireless communication device —
executed the algorithm "in the same conventional manner it executes any
other algorithm."
VII. Critical Legal Analysis
The "universal technical
problem" test: The judgment endorses a universality criterion — a
technical problem must affect all users of a system uniformly (like signal
noise). A problem that varies by user behaviour is administrative, not
technical. This is stricter than the European problem-solution approach.
Hardware performance as the
primary metric: The Court applies a hardware-centric test — the invention
must improve the performance or functionality of the hardware itself. A
software layer operating on unchanged hardware, regardless of practical
utility, does not satisfy this test.
International grants not
decisive: US and EU grants carried no weight. Indian patentability
standards — particularly Section 3(k) — are distinct from other jurisdictions.
Tension with prior BlackBerry
wins: The distinction from 2025:DHC:3100 and 2024:DHC:6572 (where
BlackBerry succeeded) appears to be that in those cases, the technical effect
was demonstrably linked to hardware-level improvements, whereas here the effect
remained confined to the display/UI layer without affecting device performance.
VIII. Practical Implications
1. Claim drafting: For
UI-related computer-implemented inventions, claims must articulate a
hardware-level technical effect — not merely improved user convenience.
Describe how the invention modifies processor operation, memory use, or
communication subsystems.
2. Specification strategy:
Where the Background section describes the problem in human/administrative
terms, it undermines the argument for a technical solution. Frame the technical
problem in device-constraint terms from the outset.
3. Prior art strategy:
Distinguish prior art on the inventive concept, not just at which stage of a
workflow a known technique is applied (send vs. receive). Demonstrate why the
combination would not have occurred to a PSITA without knowledge of the
invention.
4. Alternative protection:
Where Section 3(k) is likely, consider:
- Design registration for
the GUI (particularly following *NEC Corporation v. Controller*,
Calcutta HC, March 2026)
- Copyright for the
underlying software as a literary work
- Trade secrets for the
algorithm itself
5. Section 3(k) objections are
not formalities. This judgment confirms that the Delhi HC will uphold
reasoned Controller findings on the absence of hardware-level technical effect.
Engage Section 3(k) objections substantively from the FER stage.
IX. Consistency with
Precedents
Consistent with (upholding
Section 3(k) refusals):
- *Blackberry Limited v.
Assistant Controller of Patents & Designs* (2024:DHC:6571)
- *Microsoft Technology
Licensing LLC One
Microsoft Way v. Assistant Controller of Patents, Patent Office * (Madras
HC, 2024 SCC OnLine Mad 2785)
In tension with (Section 3(k)
grants):
- *Blackberry Limited v.
Assistant Controller of Patents & Designs * (2025:DHC:3100 and
2024:DHC:6572)
- *Ferid Allani v. Union of
India* (2019)
- *Comviva Technologies v.
Assistant Controller of Patents & Designs * (2024:DHC:8990)
The distinguishing factor in the
successful cases appears to be whether the invention modified hardware
behaviour or merely operated as a software layer on unchanged hardware.
X. Significance and Conclusion
Three points make this judgment
significant:
First, it applies Section
3(k) to a real-world commercial invention from a major global technology
company — brand recognition provides no shelter from patentability exclusions.
Second, it crystallises a
two-pronged test: (i) does the invention solve a *universal* technical
problem (not a variable human/administrative one), and (ii) does it produce a
technical effect at the *hardware performance level*?
Third, it underscores
India's divergence from global standards for software-implemented inventions —
US and EU grants for corresponding applications were given no weight.
For practitioners, this judgment
reinforces the importance of patent specification drafting that front-loads
technical effect language, frames problems in device-constraint terms, and
identifies concrete hardware-level outcomes. For businesses relying on
software-implemented inventions, a multi-layered IP strategy — combining
patents (where technically framed), design registrations, copyright, and trade
secrets — remains the most resilient approach in India.
The appeal was dismissed with no order as to costs.
