CNIPA.AI
CNIPA.AI
Back to Blog
TutorialThu Apr 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time)13 min read

Patent Drafting Strategy by Technical Domain: Software, Mechanical, Chemical, Biotech, and Electronics

CNIPA.AI Team

Tech Blog

A seasoned patent attorney can tell within three paragraphs whether a draft was written for the right technical domain. Software patents use step sequences; mechanical patents use structural part lists; chemistry patents use Markush groups and numerical ranges; biotech patents revolve around sequence listings and dosing; electronics patents mix circuits and signal flows. Picking the wrong drafting pattern is a quality catastrophe no amount of polish can fix.

Software and Mechanical Patents — Fundamentally Different Claim Shapes

Software claims under CNIPA Examination Guidelines Part II Chapter 9 typically follow the four-part suite: method claim (S1/S2/S3 steps) → apparatus claim (mapped modules) → device claim (processor + memory) → storage medium claim. Algorithm features must have a technical interaction with a technical feature to clear subject matter eligibility. Specifications rely on flowcharts, architecture diagrams, data flows, and pseudocode. Mechanical patents, by contrast, drive toward product claims describing parts and their structural/functional connections ('XXX包括A、B和C,其中A通过铰链连接到B'). Dependent claims refine dimensions, materials, angles. Drawings are front/side views, cross-sections, exploded assemblies. A template optimized for software — full of S1/S2 steps — will produce incoherent mechanical drafts; conversely a mechanical template produces software drafts missing the required technical-algorithm interaction.

Chemical and Biotech — Where Data Supplants Description

Chemistry patents under CNIPA Examination Guidelines Part II Chapter 10 pivot on composition claims, Markush groups (covering multiple chemically related variants), process claims, and use claims. Numerical ranges (content, temperature, pressure, pH) are core, not optional. Sufficient disclosure requires actual experimental data — you cannot argue effect from theory alone. Typical specification: raw materials, preparation steps, comparative example tables, effect verification. Biotech goes further: sequence listings in ST.26 XML format, SEQ ID NO references throughout the claims, in vitro/in vivo data, dose-response curves, toxicology summaries. Markush structures dominate small molecule patents; antibody patents often use CDR-based functional claims. Drawings may be minimal (chemical structures, reaction schemes) or heavy (spectra, cell images, sequence alignments). A software-style AI template applied to a chemistry invention will produce Markush-less, data-less claims that will be rejected for lack of enablement.

Electronics and the Case for Domain-Specialized AI

Electronic/communications patents blend software and hardware: circuit topology, timing diagrams, signal flow, modulation schemes. Independent claims often describe a system with transmitter/receiver/processor blocks, while dependent claims specify modulation schemes or frequency bands. Drawings are heavy on circuit schematics and timing charts. Domain boundaries are not always clean — an automotive patent might combine mechanical parts (chassis, steering) with electronic control units (ECUs) and software (autonomous driving algorithms), requiring all three drafting patterns in one application. The takeaway for AI tool selection: domain specialization matters more than surface multi-jurisdiction support. A tool that correctly handles Markush expansion, sequence references, circuit descriptions, and mechanical part hierarchies will deliver higher quality drafts than one that 'supports' six jurisdictions but treats every invention as a software patent.

Get Started with CNIPA.AI

Sign up now and experience AI-powered patent search and writing

Sign Up Free