A common error companies make in their patent strategy is filing patents after the product is completed. By then, the prior art has often accumulated, and the window for strong claims has narrowed. IP teams that sit in on R&D reviews early catch inventions while they are still protectable. Portfolio audits matter too. A patent that no longer maps to any product line is just an annuity bill. For companies filing across jurisdictions, PCT and Paris Convention filings need to be planned together. Managing them as separate tracks is how priority dates quietly slip.

Smart devices have several things worth protecting, and each needs a different instrument. How the device works internally, the architecture, the protocols, and the processing logic are patent territory. How it looks goes through a registered design. The brand name and logo are trademark matters. The practical problem is timing. Counterfeit versions of popular products appear fast, sometimes within weeks of launch. Registrations filed during development, before the product is public, give rights holders something to act on. Filing after a fake product has already reached the market puts companies on the back foot immediately.

People often confuse the two because both involve products, but they protect completely different things. A registered design under the Designs Act 2000 covers appearance, shape, pattern, ornamentation, and configuration. It has nothing to say about how the product functions. A patent under the Patents Act, 1970, covers a technical invention. Appearance is irrelevant to the patent examiner. Design registration lasts ten years, with a five-year renewal available. A patent runs for twenty years from the filing date. A product that is both technically inventive and visually distinctive can carry both, and often should.

Patents do not file themselves, and most inventions that go unprotected are lost simply because the engineer did not know the idea was worth protecting. That is the problem workshops fix. When R&D teams understand the basics of what makes something patentable, they will start documenting work differently, and they will stop assuming someone else will catch it. A conference paper published before filing, or a product shown to a customer too early, can end a case before it starts. Disclosure forms and internal recognition programmes help sustain the habit. Training without follow-through tends to fade quickly.

Computer-related invention applications in India are rejected mostly by the provisions of section 3(k). It excludes computer programs per se. Examiners use it broadly often against applications where hardware is not clearly involved. The objection is not always fair, but it is consistent. Arguing back requires moving away from what the software does and toward what the system achieves in concrete technical terms. A measurable drop in power consumption, a documented improvement in processing speed, a specific security outcome, etc. An argument that stays at the level of the algorithm rarely does.

Infringement in smartphone patents can be brought before a High Court in India. The range of relief available includes injunctions, damages, account of profits, and delivery up of infringing stock. The Delhi High Court has a track record in these cases and will move fast when the situation calls for it, including before the other side is notified, in cases where urgency is clear. Before any of that is possible, a claim chart needs to exist. This is a document that takes each element of the relevant patent claims and maps it against what the competitor's product actually does. Courts require it. Without one, the case has no foundation.