{"id":150148,"date":"2026-07-16T08:22:49","date_gmt":"2026-07-16T02:52:49","guid":{"rendered":"https:\/\/www.bananaip.com\/intellepedia\/?p=150148"},"modified":"2026-07-15T00:25:13","modified_gmt":"2026-07-14T18:55:13","slug":"section-3k-technical-effect-blackberry-email-patent-computer-program-per-se","status":"publish","type":"post","link":"https:\/\/www.bananaip.com\/intellepedia\/section-3k-technical-effect-blackberry-email-patent-computer-program-per-se\/","title":{"rendered":"Colour Blind? How BlackBerry&#8217;s Messaging Patent Failed India&#8217;s Section 3(k) Technical Effect Test"},"content":{"rendered":"<h2>Background<\/h2>\n<p>BlackBerry Limited filed Patent Application No. 1976\/DEL\/2008 on 20 August 2008. The application, titled &#8216;Colour Differentiating a Portion of a Text Message Shown in a Handheld Communication Device,&#8217; addressed a practical problem: users of handheld mobile email clients rarely applied inbox filters the way they did on desktops, raising the risk of inadvertently sending a message to the wrong recipient. The invention proposed dynamically examining message addresses and colour-coding recipient names based on domain or host-name attributes so that, at a glance, a sender could distinguish internal recipients from external contacts or verify distribution lists before hitting send.<\/p>\n<p>The First Examination Report raised objections under Section 2(1)(j) for lack of inventive step and under Section 3(k) as a computer program per se. After two rounds of hearings, the Assistant Controller refused the application. BlackBerry challenged both orders before the Delhi High Court under Section 117A of the Patents Act, arguing that the invention made a genuine technical contribution distinct from the underlying software.<\/p>\n<h2>Issues Before the Court<\/h2>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li>Whether the application lacked inventive step under Section 2(1)(j) in view of prior art documents D1, D2, and D3, or whether the combination of colour-coding with domain-attribute identification constituted a non-obvious departure<\/li>\n<li>Whether the subject matter was barred from patentability under Section 3(k) as a computer program per se, on the ground that it produced no technical effect beyond the abstract execution of software instructions<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2><strong>BlackBerry&#8217;s Arguments<\/strong><\/h2>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li>The invention solved a technically distinct problem specific to handheld devices: absence of inbox filters on mobile email clients, compounded by limited screen size, constituted a hardware-context problem absent from desktop environments<\/li>\n<li>None of the prior art taught the core concept in isolation: D1 categorised received messages (not outgoing drafts) by attribute; D2 required manual per-recipient confirmation; the combination did not render the application obvious<\/li>\n<li>Applying the technical-contribution test from <em>Ferid Allani v. Union of India<\/em>, the invention reduced interaction steps and prevented inadvertent data disclosure, constituting a demonstrable technical effect; corresponding patents were granted in the USA and EU<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2><strong>Controller&#8217;s Arguments<\/strong><\/h2>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li>The problem was user-specific, not universal: signal noise affects all users equally; the risk of misdirecting a message depends on individual sender behaviour and does not arise identically for every user<\/li>\n<li>All claim limitations were software limitations; the mobile terminal device executed the colour-coding algorithm in a conventional manner without any enhancement to hardware functionality or performance<\/li>\n<li>The combination of D1, D2, and D3 rendered the approach obvious: a person skilled in the art could adapt D1&#8217;s attribute-based categorisation algorithm to produce the recipient differentiation that D2&#8217;s user-confirmation mechanism sought to achieve<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Court&#8217;s Observations and Analysis<\/h2>\n<h3><strong>Inventive Step Under Section 2(1)(j)<\/strong><\/h3>\n<p>The court noted that D1 uses message attribute characteristics in a categorisation algorithm and D2 addresses the same underlying problem of avoiding unintended recipients. Read alongside D3, which teaches visually distinguishable message formats for different users, the combination rendered the application obvious. The distinction between D1&#8217;s categorisation of incoming messages and the colour-coding of outgoing draft recipients reflected a difference in algorithm design, not a non-obvious technical departure. A person skilled in the art could readily make that adaptation. BlackBerry&#8217;s argument that D1 and D2 individually did not teach the same solution missed the point: inventive step is assessed against the combined disclosure of the prior art, not against each document in isolation.<\/p>\n<h3><strong>Technical Effect and Section 3(k): The Hardware Contribution Test<\/strong><\/h3>\n<p>The test un<strong>d<\/strong>er Section 3(k) requires the invention to improve the functioning of the system at the hardware level or address a technical problem intrinsic to the hardware, not merely enhance user convenience. The court found th<strong>a<\/strong>t the risk of sending a message to the wrong recipient was not a universal technical deficiency. Unlike hardware-level problems such as signal noise or memory overflow, which affect the device identically across all users, the misdirected-message risk depends on individual sender behaviour. Even after implementation, a user could still send to the wrong recipient if multiple recipients shared similar names or domains, confirming the solution was rooted in user-management convenience rather than device-level operation.<\/p>\n<p>The court further found that the algorithm associated colours with recipient names based on domain attributes but caused no change in hardware functionality or performance. The mobile terminal device executed the algorithm conventionally without any reduction in memory usage, acceleration of processing, or elimination of command surfaces. The court observed that the key question under Section 3(k) is not what the invention does in abstract terms, but what it contributes at the hardware level. Inventions that reduce processing overhead, improve device response times, or enable new hardware capabilities meet this test; software solutions to problems rooted in user behaviour do not. The actual contribution here lay solely in a computer program or algorithm.<\/p>\n<p>BlackBerry also argued that the grant of corresponding patents in the United States and the European Patent Office should carry persuasive weight on the question of inventive step. The court acknowledged this argument but held that foreign patent grants, while relevant as context, are not binding on Indian patent authorities. Each jurisdiction applies its own statutory framework: the United States does not have a provision equivalent to Section 3(k) of the Patents Act, and the European Patent Office applies its own &#8216;technical character&#8217; test. The existence of foreign grants did not override the specific findings made on D1, D2, and D3, nor did it dispense with the independent requirement of hardware-level technical effect under Indian law.<\/p>\n<h2>Findings<\/h2>\n<p>In view of the arguments put forward by both the Parties, the court held that:<\/p>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li>The application lacked inventive step under Section 2(1)(j): colour-coding recipient names by domain attribute was obvious from D1, D2, and D3 read together<\/li>\n<li>The subject matter constituted a &#8216;computer program per se&#8217; within Section 3(k): its contribution was a software algorithm addressing a user-convenience problem, not a hardware-level technical problem<\/li>\n<li>The mobile terminal device executed the algorithm in a conventional manner; no technical effect improving device functionality was demonstrated<\/li>\n<li>The Impugned Orders refusing the application were affirmed and the appeal was dismissed<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Case Citation:<\/strong> Blackberry Limited v. Controller of Patents and Designs, C.A.(COMM.IPD-PAT) 14\/2022, High Court of Delhi, decided on 30 April 2026. Available at <a href=\"http:\/\/indiankanoon.org\/doc\/161660179\/\" target=\"_blank\" rel=\"noopener\">http:\/\/indiankanoon.org\/doc\/161660179\/<\/a><\/p>\n<p><strong>Authored by Gaurav Mishra, Patent Attorney, BananaIP Counsels<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Delhi High Court dismissed BlackBerry&#8217;s appeal against the refusal of its patent for colour-coding email recipients on handheld devices, holding that the invention lacked inventive step and constituted a computer program per se under Section 3(k) of the Patents Act, with no technical effect at the hardware level.<\/p>\n","protected":false},"author":12,"featured_media":150150,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":10,"footnotes":""},"categories":[5495,6,14],"tags":[13082,12139,13085,576,486,83,12214,6496,13083,13084],"class_list":["post-150148","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-case-reviews","category-intellectual-property","category-patents","tag-blackberry-patent-india","tag-computer-program-per-se","tag-computer-related-invention","tag-cri-guidelines","tag-delhi-high-court","tag-inventive-step","tag-section-21j","tag-section-3k-patents-act","tag-software-patent-india","tag-technical-effect-patent"],"_links":{"self":[{"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/posts\/150148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/comments?post=150148"}],"version-history":[{"count":3,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/posts\/150148\/revisions"}],"predecessor-version":[{"id":150152,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/posts\/150148\/revisions\/150152"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/media\/150150"}],"wp:attachment":[{"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/media?parent=150148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/categories?post=150148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bananaip.com\/intellepedia\/wp-json\/wp\/v2\/tags?post=150148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}