Reading Japanese Patent Claims: 請求項, 発明, 実施例, 効果

Core examples: 請求項, 発明, 実施例, 効果, 技術分野, 課題, 解決手段, 図面, 従来技術, 構成.

The sentence is long because the boundary matters

A patent claim can look like an endless noun phrase. It repeats components, relations, conditions, and functions until the reader loses track. The reason is not bad writing. Patent language is trying to define legal-technical scope precisely.

A learner may understand words like:

発明 効果 図面 構成

but still miss what is actually claimed.

The key principle is:

In patents, separate claim scope from explanation.

The claim defines what is protected. The embodiment shows examples. The effect explains benefit. Background describes prior art. Mixing these up leads to serious misunderstanding.

This article is a language-literacy guide, not patent legal advice.

請求項: the claim

請求項

means claim.

A claim defines the legal scope of the invention. It may describe:

• an apparatus,
• a method,
• a system,
• a program,
• a composition,
• a manufacturing process.

Claims often use long noun phrases and component relations.

Example pattern:

〜を備える装置 a device comprising/equipped with X

〜する方法 a method of doing X

Learner action: identify the head noun of the claim first.

発明 and 技術分野

発明

means invention.

技術分野

means technical field.

The technical field section tells you what domain the invention belongs to:

本発明は、情報処理装置に関する。 The present invention relates to an information processing apparatus.

This does not yet define the claim. It frames the domain.

従来技術, 課題, 解決手段

Patent documents often follow a problem-solution structure.

従来技術 prior art/conventional technology

課題 problem to be solved

解決手段 means for solving the problem

This structure explains why the invention exists.

Learner action: read these sections as background and explanation, not as claim scope by themselves.

実施例: embodiment/example

実施例

means embodiment or working example.

It describes a specific way the invention may be implemented. It may include components, steps, drawings, materials, measurements, or examples.

Important:

An 実施例 is not always the full legal scope. It is an example or embodiment.

Claims may be broader than the embodiments. This is why patents are hard to translate and interpret.

効果: effect/advantage

効果

means effect, benefit, or advantage.

Examples:

本発明によれば、処理速度を向上させることができる。 According to the present invention, processing speed can be improved.

The effect section explains what the invention achieves. It may be persuasive, technical, and legal-adjacent, but it is not the same as the claim wording.

図面 and reference numerals

図面

means drawings.

Patent text often refers to figures:

図1 Figure 1

符号 reference numeral

10: 制御部 10: control unit

A drawing may clarify components, but the claim language controls scope. Do not rely only on the figure.

構成: configuration/structure

構成

means structure, configuration, composition, or arrangement depending on context.

Common phrases:

構成要素 component

〜から構成される is composed of

〜を備える comprises/includes/is equipped with

構成 is central to patent and engineering Japanese because it describes how parts relate.

Dependent claims

A patent may include claims that depend on earlier claims:

請求項1に記載の装置 the device according to claim 1

This means the later claim adds limitations or features to an earlier claim.

Learner action: track claim dependency. Claim 3 may not stand alone.

Example bank walkthrough

請求項

Claim.

Learner action: legal-technical scope.

発明

Invention.

Learner action: broad term; check whether claim or description.

実施例

Embodiment/example.

Learner action: example implementation, not necessarily full scope.

効果

Effect/advantage.

Learner action: benefit explanation.

技術分野

Technical field.

Learner action: domain framing.

課題

Problem to be solved.

Learner action: problem-solution structure.

解決手段

Means for solving.

Learner action: proposed technical solution.

図面

Drawings.

Learner action: support text, not claim by itself.

従来技術

Prior art/conventional technology.

Learner action: background.

構成

Configuration/structure.

Learner action: component relationship.

Patent-claim parse

When reading a claim:

1. Find the claim number.
2. Identify the head noun: device, method, system, program, composition?
3. Bracket component phrases.
4. Mark relationship verbs: 備える, 含む, 構成される.
5. Identify required elements.
6. Find conditions or limitations.
7. Check dependencies: 請求項1に記載の...
8. Separate claim from embodiment and effect.
9. Paraphrase the claim structure plainly.

Patent section function table

Patent documents are easier when each section is assigned a job.

This table prevents the biggest patent-reading error: treating examples as boundaries of the invention.

Claim language markers

Watch for:

〜を備える comprising/equipped with

〜を含む including

〜からなる consisting of / composed of, depending context

請求項1に記載の according to claim 1

These phrases define relationships and dependencies.

Bracket before translating

Patent claims should be bracketed structurally before English translation. Find:

1. claimed object,
2. required components,
3. relationships among components,
4. conditions,
5. dependent claim references.

If you translate before bracketing, the sentence will usually collapse into vague technical fog.

A strong tool for this article would help users collapse long patent sentences.

Suggested functions:

1. Claim-number detector.
2. Head-noun highlighter.
3. Component bracket display.
4. Dependency tracker.
5. Section classifier: claim, embodiment, effect, background.
6. Drawing-reference popovers.
7. Plain-structure summary.
8. Legal caution label.

Final rule

Patent Japanese is precision prose under legal pressure.

請求項 defines scope. 実施例 gives examples. 効果 explains advantage. 従来技術, 課題, and 解決手段 frame the problem-solution story.

Do not read patents linearly like essays. Bracket the claim.