A useful RFID patent search starts with a technical question and ends with a record another researcher can repeat. Search terms, databases, dates, document types and reasons for including results matter as much as the number of hits.
This guide supports preliminary technical literature research. It helps engineers collect and organize documents; conclusions about patent validity, infringement or freedom to operate require a separate, appropriately scoped legal review. Keep the jurisdiction and date limits visible throughout the work.
Describe the technical feature before searching
Write a sentence naming the mechanism, object and problem. “RFID patents” is a broad subject. “Passive tag antenna structures intended for mounting on metal” gives the search a more useful boundary. Add what you will include and exclude: tag structure, reader processing, packaging, operating environment or a particular application.
Build groups of alternative terms. For that example, try radio-frequency identification, RFID and transponder; antenna and resonator; metal, conductive surface and on-metal. These are vocabulary leads, not a claim that every term means the same thing. Record which combination you actually enter and why you change it.
The USPTO multi-step search strategy recommends combining keyword work with classification research, reviewing relevant documents and following citations. Use a relevant result to discover additional technical vocabulary and classifications rather than assuming the first query covers the field.
Choose a database and record its coverage
USPTO Patent Public Search provides U.S. patents and published applications. Its Basic and Advanced interfaces offer different search controls. Start with Basic for a known publication or an initial term search; use Advanced when you need a repeatable combination of fields and filters. Consult the linked help for current query syntax.
Record database/interface, search date, exact query, filters and result count. Keep a screenshot or exported search record when the tool permits it. A zero-result search may reflect vocabulary, field choice or coverage; expand those assumptions before drawing a conclusion.
For international work, record the countries and publications covered by the selected service. Machine translations can help screen a document, but preserve its original-language publication and identify passages needing specialist review. The search scope should distinguish patent literature from standards, product documentation and other technical publications.
Read the document in layers
On a small screen, scroll sideways to read all columns.
| Part | Research use |
|---|---|
| Publication identity | Country, number and kind code; title; link and downloaded document reference. |
| Dates and parties | Priority, filing and publication dates kept separately; named applicants and inventors as recorded. |
| Abstract and drawings | A quick technical overview and vocabulary for deeper searching. |
| Description | Mechanism, embodiments, operating assumptions and relevant passages. |
| Claims | The actual claim text to flag for detailed review; distinguish it from descriptive examples. |
| Citations and classifications | Earlier/later references and classifications that may expand the search. |
Give each included result a short relevance note in your own words with page, figure or claim references. Also keep a brief exclusion reason for plausible-looking results. That prevents another reviewer from repeating the same screening work.
A product name in the description, a broad abstract or an old publication date is insufficient for a legal conclusion. Preserve the specific document and questions that require review. Current ownership and legal status may need additional official records for the relevant jurisdiction.
Group related publications without losing their identity
The European Patent Office explanation of patent families distinguishes simple and extended families and notes that databases can use different definitions. Record which definition you use when grouping results. A family helps organize related technical material; each publication still has its own identity and context.
Keep the family key alongside the publication number. Review relevant members for language, jurisdiction and document stage. Avoid presenting a count of publications as a count of distinct inventions without stating how related records were grouped.
Expand the search and make the handoff reproducible
Choose the strongest relevant documents and examine their classifications and citations. Search the relevant classification with a broader term set, then compare the new results with those already screened. Look for different terminology, applicants and approaches. Keep the sequence of searches so a later reviewer can see how the scope developed.
Use the USPTO quick-reference guides for supported fields and operators. Do not paste an unverified query syntax from a different database and assume it has the same meaning. Confirm the filters displayed by the tool after running the search.
Finish with the technical question, coverage, queries, inclusion rules, retained publications, family definition, strongest passages and unresolved questions. Set a reason to revisit the work, such as a design change or a later review date. Publication delays and database scope limit what a preliminary search can establish at any one time.
Store full document links and your own notes in the working log. Share the focused evidence set with the person responsible for the next technical or legal decision. A reproducible search is a useful input to that decision even when its limits remain explicit.
Keep a working record
Download the editable working record (plain text). It includes purpose, instructions, evidence fields and this guide's source links. Save a separate copy for each evaluation and record unresolved issues with their owner.
Related reading
Researched and updated September 20, 2026. Recheck source documents when equipment, software or applicable requirements change.