A patent application can survive a novelty challenge and still fail where it matters most: in the telling. Arti Srivastava filed patent application no. 1774\/DEL\/2006, titled “Method and System for Detecting Counterfeit Products,” before the Indian Patent Office on 03 August 2006. The invention addressed a genuine and commercially significant problem: the inability of ordinary consumers to verify whether a product they were purchasing was genuine.<\/p>\n
The proposed solution was a dual-code label system. Each product would carry two alphanumeric codes \u2014 one visible to the buyer, and a second concealed beneath a scratchable coating. A consumer suspecting a fake could transmit both codes to a central data centre (via telephone, fax, SMS, email, or internet), which would then verify the codes against its records and communicate the result back to the user. The data centre would also log repeated enquiries against the same codes, enabling manufacturers to track potential counterfeiting activity.<\/p>\n
The application moved through the Patent Office without urgency. After the First Examination Report was issued in June 2011, Srivastava filed her response in May 2012 and attended a hearing in July 2013, submitting post-hearing written submissions in December 2013. The Assistant Controller of Patents (Controller) rejected the application on 31 January 2014 on two grounds: lack of inventive step under Section 2(1)(ja) of the Patents Act, 1970 (Act), relying on prior art documents D1 and D5, and insufficient disclosure under Section 10(4)(a). Aggrieved by the Controller’s decision, Srivastava appealed to the Delhi High Court.<\/p>\n
The court noted at the outset that the Controller’s inventive step rejection rested primarily on prior art document D1, titled “Method and System for Deterring Product Counterfeiting, Diversion and Piracy.” On examining the dates, the court found that D1 was published on 10 August 2006, seven days after Srivastava filed her application on 03 August 2006. The court held that a document published after the filing date cannot validly be cited as prior art. Since D1 was the primary prior art underpinning the Section 2(1)(ja) rejection, and the respondent itself chose not to sustain that objection before the High Court, the inventive step ground did not survive.<\/p>\n
The court observed that Section 10(4)(a) requires a complete specification to fully and particularly describe the invention, its operation or use, and the method by which it is to be performed. The court noted that this is not a mere formality: a patent is granted for an invention capable of practical use, and the specification must deliver enough information for a PSITA to work the invention without conducting further research or making further inventions of their own.<\/p>\n
Referring to the Bombay High Court’s decision in Farbwerke Hoechst vs Unichem Laboratories<\/em>, the court noted that insufficiency of description has two branches: the specification must describe an embodiment of each claimed invention in enough detail for those in the relevant industry to implement it without further inventions, and the description must not be unnecessarily difficult to follow. The court also drew on its own earlier decision in Titan Umreifungstechnik GMBH and Co. KG v. Assistant Controller of Patents and Designs<\/em>, which affirmed that the applicant must disclose the best known method of performing the invention clearly enough for a PSITA to reproduce it.<\/p>\n The court found that the complete specification left several critical elements of the claimed system unexplained. While the figures and flow charts described the modes of transmitting the dual codes to the data centre, the specification did not disclose how the data centre would digitally process the received codes, what protocols, security standards, or error-handling mechanisms were involved in the transmission, or how the outcome of the comparison would be converted from digital form into a voice message, SMS, or email for delivery back to the user. The court further observed that the specification also failed to address how the data centre would generate the visible and hidden codes in the first instance, including the generation logic, metadata linkage, and encryption safeguards.<\/p>\n The court observed that these were not peripheral details that could safely be left to the PSITA’s common knowledge. They were essential components of the claimed system. In the court’s view, leaving these elements for the PSITA to work out independently crossed the line from enabling disclosure into requiring further independent research or invention, precisely what Section 10(4)(a) prohibits.<\/p>\n Going beyond the grounds upheld by the Controller, the court found an additional infirmity. Claim 1 of the subject application claims a “processor” to verify and match the received product code and a “transmitter” to report results back to the user. The court observed that the complete specification contained no corresponding disclosure of how either component actually functioned. Citing the Madras High Court’s analysis in Caleb Suresh Motupalli vs Controller of Patents<\/em>, the court noted that Section 10(5) requires claims to be fairly based on the matter disclosed in the specification, and that a claim covering an unimplementable or unworkable embodiment cannot meet that standard. The court held that claim 1 failed this test.<\/p>\n In view of the observations and the arguments presented by both the parties, the court held that:<\/p>\nWhere the Specification Failed<\/h3>\n
The Fair Basing Requirement Under Section 10(5)<\/h3>\n
Findings<\/h2>\n
\n
\n
\n