Reading Korean Patent Claims: 청구항, 발명, 실시예, 효과

Core examples: 청구항, 발명, 실시예, 효과, 종래기술, 구성, 특징, 포함하는, 도면.

A patent sentence tries to define a boundary

A Korean patent claim may say:

제1항에 있어서, 상기 센서는 사용자의 움직임을 감지하도록 구성되고, 상기 제어부는 감지된 신호에 기초하여 출력을 조절하는 것을 특징으로 하는 장치.

This is not normal product description. It is legal-technical boundary writing. Every component, modifier, and relation may affect what is being claimed.

The key principle is:

Patent Korean defines scope before it explains usefulness.

This article is for language literacy, not patent advice.

청구항

청구항

means claim in a patent.

Related:

독립항 independent claim

종속항 dependent claim

제1항 claim 1 / paragraph 1, depending context, but in patent context often claim numbering

청구범위 scope of claims

A 청구항 defines the legal scope of the invention. It is usually more important than the friendly summary.

Learner action: identify whether you are reading claims or description.

발명

발명

means invention.

Related:

본 발명 the present invention

발명의 명칭 title of invention

발명의 배경 background of invention

발명의 내용 summary/content of invention

Patent prose often repeats 본 발명 to maintain precision.

실시예

실시예

means embodiment/example implementation.

Related:

일 실시예 one embodiment

다른 실시예 another embodiment

바람직한 실시예 preferred embodiment

An 실시예 explains a way the invention may be implemented. It is not always the full legal boundary.

Learner action: do not confuse 실시예 with the claim itself.

효과

효과

means effect/advantage.

Patent documents often include:

발명의 효과 effects of the invention

기술적 효과 technical effect

효과를 제공한다 provides an effect

The effect section explains why the invention matters or what problem it solves.

Learner action: 효과 is explanatory value, not claim scope by itself.

종래기술

종래기술

means prior art/conventional technology.

Related:

기존 기술 existing technology

배경기술 background technology

문제점 problem/limitation

Patents often contrast:

종래기술의 문제점 problems of prior art

with:

본 발명은 …을 해결하고자 한다 the present invention aims to solve...

Learner action: prior-art language frames the invention’s problem.

구성

구성

means configuration, composition, structure, component arrangement.

Related:

구성요소 component

구성되다 be configured/composed

포함하다 include/comprise

Patent Korean uses 구성 to define parts and relations.

Example:

장치는 센서와 제어부를 포함한다. The device includes a sensor and a control unit.

Learner action: 구성 terms are structural, not merely descriptive.

특징

특징

means feature/characteristic.

Patent phrase:

…을 특징으로 하는 장치 a device characterized by...

This phrase often appears at the end of a claim and ties the preceding limitations to the claimed object.

Learner action: 특징으로 하는 is a claim-structuring phrase.

포함하는

포함하는

means including/comprising.

Patent language uses 포함하는 to define components without necessarily limiting to only those components, depending legal context and wording.

Example:

센서와 제어부를 포함하는 장치 a device including a sensor and a control unit

Learner action: 포함하는 is a scope word. Read carefully.

도면

도면

means drawing/figure.

Related:

도 1 Figure 1

참조부호 reference numeral

도면의 간단한 설명 brief description of drawings

Patent specifications often refer to drawings:

도 1을 참조하면 referring to Figure 1

Learner action: figure references are part of the reading path.

Claim language patterns

Example claim skeleton

Original-style:

센서, 제어부 및 출력부를 포함하는 장치.

Skeleton:

장치가 있다. The device exists/is claimed.

Components:

센서 sensor

제어부 control unit

출력부 output unit

Relation:

포함하는 including

Plain reading:

A device including a sensor, a control unit, and an output unit.

Patent document sections

Common learner mistakes

Mistake 1: Reading 실시예 as the claim

Embodiments are examples, not necessarily full scope.

Mistake 2: Skipping 상기

상기

refers back to previously mentioned items. It is boring but essential.

Mistake 3: Treating 효과 as proof

효과 describes intended/claimed technical effect; it is not necessarily independent evidence.

Mistake 4: Translating 포함하는 casually

In patent context, 포함하는 is part of scope language.

Example bank walkthrough

청구항

Patent claim.

Learner action: scope-defining section.

발명

Invention.

Learner action: central technical/legal object.

실시예

Embodiment.

Learner action: example implementation, not always claim scope.

효과

Effect/advantage.

Learner action: explanatory benefit.

종래기술

Prior art.

Learner action: existing technology/problem frame.

구성

Configuration/structure/components.

Learner action: structural relation.

특징

Feature/characteristic.

Learner action: claim-ending phrase.

포함하는

Including/comprising.

Learner action: component/scope word.

도면

Drawing/figure.

Learner action: visual reference.

Patent-reading workflow

When reading Korean patent documents:

1. Identify section: claims, background, embodiment, effect, drawings?
2. For claims, find the claimed object or method.
3. List components.
4. Track 상기 references.
5. Mark 포함하는 and 구성되는 phrases.
6. Separate independent and dependent claims.
7. Read embodiments as examples.
8. Read effects as stated advantages.
9. Use drawings to confirm component relations.
10. Do not treat patent-language interpretation as legal advice.

Patent section priority table

Patent Korean should be read by section.

Claims define the boundary; embodiments explain examples.

Claim-scope chunking table

These are not filler. They are scope machinery.

Patent-reading caution

A learner should not infer legal scope from 실시예 or 효과 alone. Patent interpretation is professional work. For language study, separate: what is claimed, what is illustrated, what problem is described, and what effect is asserted.

A strong tool for this article would turn long claims into component maps.

Suggested functions:

1. Claim-number detector.
2. Independent/dependent claim labels.
3. 상기 reference tracker.
4. Component list builder.
5. 포함하는 phrase highlighter.
6. Embodiment vs claim divider.
7. Drawing-reference popovers.

Final rule

Korean patent prose is dense because it is boundary language.

청구항 defines scope. 발명 names the invention. 실시예 illustrates. 효과 explains advantage. 종래기술 frames the problem. 구성, 특징, 포함하는, and 도면 build the technical/legal map.

Read structure before translating.