REFLIB / RESEARCH & TECHNOLOGY

Patent landscapes & technology analysis

Connect sample patent records to classifications, research leads and year distributions. Traceable maps and report formats help define search scope, deduplication and analytical goals.

Service areas · Illustrative scenarios · Enterprise project enquiries
SERVICE AREA

Understand this service area

Patent-landscape research organizes searching, classification, technical relationships and trends around a defined technology question. Methods, source coverage and limitations give findings context. The examples help frame objectives and a possible report.

Conditions to assess

Assess the research question, data access, search coverage, methods and implementation capability before agreeing a report scope or any specialist assessment.

This page introduces a service area and illustrative scenarios. Organizations can email their goals, current conditions and requirements. After receiving an enquiry, we assess feasibility, implementation conditions and whether to take on the project. Any next steps require mutual agreement.

EXPLORE THE SCENARIO

Start with a concrete example

Classification
reflib
Patent landscapes & technology analysisOriginal illustrative scenario & proposal

Energy storage · Patent-map example

E

Electrochemical storage

6

P01 · P02 · P03 · P04 · P06 · P09

T

Thermal storage

4

P05 · P07 · P10 · P11

M

Mechanical storage

2

P08 · P12

Question
Which material and structural topics appear across storage approaches?
Sample scope
P01–P12; one primary technology branch per record.
Fields for an actual search
Keywords, classification codes, jurisdictions, publication dates, families and inclusion/exclusion reasons.
12 sample records
reflib
Patent landscapes & technology analysisOriginal illustrative scenario & proposal

All 12 entries are synthetic. P identifiers belong to this example; years demonstrate counting and sample-document positions demonstrate traceability.

Sample IDSample yearBranchTechnology tagRelation tagSample reference
P012022EElectrode materialMaterial–performanceSample document P01 §1
P022022EElectrolyte compositionMaterial–performanceSample document P02 §1
P032023EElectrode structureStructure–thermalSample document P03 §1
P042023EMaterial compositionMaterial–performanceSample document P04 §1
P052023TPhase-change mediumStructure–thermalSample document P05 §1
P062024EPackage heat transferStructure–thermalSample document P06 §1
P072024TThermal storage unitStructure–thermalSample document P07 §1
P082024MCompressed-air structureStructure–thermalSample document P08 §1
P092025EInterface materialMaterial–performanceSample document P09 §1
P102025THeat-exchange structureStructure–thermalSample document P10 §1
P112025TThermal storage materialMaterial–performanceSample document P11 §1
P122025MFlywheel structureStructure–thermalSample document P12 §1

On narrow screens, scroll sideways to view all columns.

Relations & evidence
reflib
Patent landscapes & technology analysisOriginal illustrative scenario & proposal

Material composition → Performance question

P01 · P02 · P04 · P09 · P11

Structural design → Thermal-management question

P03 · P05 · P06 · P07 · P08 · P10 · P12

Connections follow the relation tags and identify analytical leads. Causality, technical effects and claim scope require separate investigation.

Years & report
reflib
Patent landscapes & technology analysisOriginal illustrative scenario & proposal

Analysis-report excerpt

Counting

Group by sample year and count each record once: 12 in total. Actual projects define publication/application dates and family deduplication.

Reading the map

Inspect branch and year distributions in the sample collection, tracing each count to record identifiers.

Interpretation

The sample illustrates a method. Counts alone do not establish industry growth, maturity or patent quality.

Original illustrative scenario: parties, records and arrangements explain the service. Project scope and implementation conditions are assessed and agreed by email.

WHEN IT MATTERS

Where a conversation can help

01

Explore a technology direction

Understand the main technical approaches and their differences before exploring a field.

02

Organize an existing collection

Bring consistent labels, deduplication rules and classification levels to a list of patent records.

03

Compare changes over time

Explore the distribution of records by year, with clear explanations of search scope and its limits.

SCOPE & STRUCTURE

Possible scope and presentation

A topic classification framework

The energy-storage example separates electrochemical, thermal and mechanical branches, with explicit inclusion and exclusion criteria.

Relationships and trends

A relationship view explains connections; a trend view shows time distribution under one consistent counting rule. Each needs a source and scope.

A report structure to discuss

Questions, search rules, data preparation, visualizations, interpretation and limitations form a possible outline. Project scope is assessed after an enquiry.

BEFORE YOU GET IN TOUCH

Useful context for your first email

  • The technology question, product or application
  • Regions, languages and time period of interest
  • Existing keywords, classification codes or record lists, if available
  • Intended readers and the decision the map should inform

A short summary is enough to begin. Please leave passwords, complete sensitive datasets and confidential core technical material out of your first message.

Common questions

How can I check the example counts?

All four views reference synthetic records P01–P12. Branch and year counts are generated from those records, and relationship groups list the supporting entries for checking.

Does a landscape establish infringement or freedom to operate?

A landscape organizes technical information. Infringement, validity and freedom-to-operate questions require a defined professional assessment of claims, jurisdictions and facts. No such conclusion is provided here.

LET’S TALK ABOUT YOUR PROJECT

A focused question starts the conversation

Prepare and copy your enquiry, open your email app, then paste into the message body, review and send it yourself.

  1. 01

    Describe the need

    Email goals, context and scope from your own email application.

  2. 02

    Clarify by email

    Clarify the question and conditions, adding a summary where needed.

  3. 03

    Assess whether to proceed

    Assess feasibility, implementation and required resources.

  4. 04

    Agree any next steps

    If feasible, discuss scope, timing, cost and arrangements.

MNV LIMITED
[email protected]
+852 2661 2188