Short Summary
Microsoft challenged the Assistant Controller's decision rejecting its patent application for a network authentication system under Section 3(k) of the Patent Act, arguing that the invention provided a genuine technical solution to security problems. The Delhi High Court set aside the rejection based on the flawed interpretation of 'computer program per se,' emphasizing that an algorithm should not be automatically excluded if it offers a tangible technical contribution. Consequently, the matter was remanded back to the Controller for re-examination regarding novelty and inventive step.
Detailed Summary
When a company builds a system designed to protect networks from intruders, you'd expect the patent office to recognize the technical ingenuity behind it. But what happens when the very thing that makes the invention powerful — its algorithm — becomes the reason it's rejected? This is the story of how Microsoft Technology Licensing, LLC took on the patent establishment and forced a reckoning over what truly counts as a patentable invention in the digital age.
Microsoft Technology Licensing, LLC, the intellectual property arm of one of the world's largest technology companies, filed a patent application for a network authentication system — a solution aimed squarely at solving real-world security problems. The Assistant Controller of Patents and Designs, however, rejected the application, classifying it as a "computer program per se" and therefore excluded from patentability under Section 3(k) of the Patent Act. This provision bars inventions that are merely computer programs or algorithms from receiving patent protection. Microsoft, convinced that its invention offered far more than just code on a machine, decided to challenge the rejection before the Delhi High Court.
Microsoft argued forcefully that its network authentication system was not a mere computer program — it delivered a genuine technical solution to pressing security challenges. The company contended that the invention produced a tangible technical contribution, going well beyond simply implementing an algorithm on generic computer hardware. On the other side, the Assistant Controller stood by the rejection, treating the presence of algorithmic elements as sufficient grounds to deny patentability under Section 3(k). The core legal friction was clear: should an invention be automatically excluded just because it contains an algorithm, or should the patent office dig deeper to assess whether real technical value exists?
The Delhi High Court sided with Microsoft on the legal interpretation. The court found the rejection flawed, emphasizing that an algorithm should not be automatically excluded from patentability if it offers a tangible technical contribution. The court set aside the Assistant Controller's decision and remanded the matter back to the Controller for fresh examination — this time with proper consideration of the invention's novelty and inventive step. While Microsoft won the legal battle over how Section 3(k) should be interpreted, the patent itself remains pending, making the outcome a mixed result: a victory in principle, but with the final patent grant still uncertain.
For founders and IP professionals, this case delivers a critical lesson: software and algorithm-driven inventions are not automatically doomed under Section 3(k). The key to patent eligibility lies in demonstrating that your invention produces a real technical effect or solves a technical problem — not just that it runs on a computer. When drafting patent applications, focus on articulating the tangible technical contribution your innovation makes. Don't let a patent office's narrow reading of "computer program per se" shut the door on a genuinely technical invention.
Practitioner Note
This case demonstrates the evidentiary and procedural standards applied in patent matters before Delhi High Court. Understanding the court's reasoning in Microsoft Technology Licensing, LLC vs The Assistant Controller Of Patents And Designs is valuable context for structuring arguments or assessing risk in similar proceedings.
Related Cases
Blackberry LimitedvsAssistant Controller Of Patents And Designs
Blackberry Limited appealed an order dated July 31, 2019, wherein its application for grant of a patent was rejected. The court issued notice to the respondent and directed both parties to file written submissions within specified timelines.
Sun Patent TrustvsVivo Mobile Communication Co. Ltd.
The defendants filed an application seeking correction and interpretation of a prior court order, arguing that it implied the plaintiff had complied with FRAND obligations. The Court found that the defendants were not seeking a clerical correction but rather modification/interpretation of pending issues related to SEP compliance. Consequently, the application was dismissed as premature.
Ms Veerji Restaurant Private LimitedvsJashpal Singh Trading As Veerj Ji Malai Chaap Wale & Ors.
The Delhi High Court addressed several applications in the trademark and copyright infringement case filed by Ms Veerji Restaurant Private Limited against Jashpal Singh Trading As Veerj Ji Malai Chaap Wale. The court formally registered the plaint as a commercial suit, setting timelines for written statements and replication. Crucially, it issued notice regarding the plaintiff's application seeking permanent injunction to restrain trademark and copyright infringement and passing off of the 'VEERJI MALAI CHAAP WALE' brand.
Trutzchler Gmbh And Co Kg LimitedvsThe Controller General Of Patents
The appellant challenged the rejection of their patent application (No. 1250/KOL/2009) based on alleged lack of inventive steps. The appeal argued that the Controller reintroduced this objection suo moto, violating natural justice principles and contradicting earlier notices where the objection had been waived.
TRANS UNION, LLCvsThe Controller General of Patents, Designs & Trademarks
Trans Union, LLC challenged the refusal of its patent application (No. 4268/CHE/2012) by the Controller General of Patents, which rejected it primarily on grounds of non-patentability under Section 3(k). The appellant argued that the system and method for matching database records was inherently technical, providing a solution to data quality issues in emerging markets. The Madras High Court set aside the rejection order, finding that the invention involved technical considerations implemented by hardware, but remanded the matter to refine the claims' scope and ensure adequate enablement.
Dealing with a patent challenge?
Whether it's a Section 3(d) rejection, a post-grant opposition, or a FRAND dispute, Arctic's patent litigation team has handled it. Get a strategy call.
Disclaimer: This page contains an automated summary based on publicly available judicial records. The content is generated for informational purposes only and does not constitute legal advice. Always verify details against the original source judgment before relying on this information for any legal purpose. If you believe any information is inaccurate, please contact us.