07.03.2013 Views

Guide to STN Patent Databases – Basic Version - Paton - TU Ilmenau

Guide to STN Patent Databases – Basic Version - Paton - TU Ilmenau

Guide to STN Patent Databases – Basic Version - Paton - TU Ilmenau

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Types of search<br />

Document type SEARCH DISPLAY (<strong>STN</strong> format)<br />

A- and T-documents<br />

S JP06011796/PN JP 06011796 A<br />

(before 2000):<br />

S JPEENNNNNN/PN JP EENNNNNN A<br />

A- and T-documents<br />

S JP2002012345/PN JP 2002012345 A<br />

(from 2000):<br />

S JP20YYNNNNNN/PN JP 20YYNNNNNN A<br />

B-documents<br />

S JP06011796B/PN JP 06011796 B<br />

(published examined application, until March 1996) S JPEENNNNNNB/PN JP EENNNNNN B<br />

C-documents<br />

S JP2139594/PN JP 2139594 C<br />

(Granted patents, until March 1996)<br />

S JPNNNNNNN/PN JP NNNNNNN C<br />

B-documents<br />

S JP2763879B/PN JP 2763879 B2<br />

(published registered patent specification,<br />

from May 1996)<br />

S JPNNNNNNNB/PN JP NNNNNNN B2<br />

B1-documents<br />

S JP2852740B/PN JP 2852740 B1<br />

(published registered patent specification<br />

without previous A2 publication)<br />

S JPNNNNNNNB/PN JP NNNNNNN B1<br />

Utility model S JP07039349U/PN JP 07039349U U2<br />

S JPNNNNNNNNU/PN JP NNNNNNNNU U2<br />

Utility model, published after examination S JP2585094U/PN JP 2585094 Y1<br />

S JPNNNNNNNU/PN JP NNNNNNN Y1<br />

Utility model, examined, 2nd publication S JP2604277/PN JP 2604277 Y2<br />

S JPNNNNNNN/PN JP NNNNNNN Y2<br />

All kinds of documents can be searched with truncation, e.g.:<br />

=> S JP06011796?/PN<br />

Usually EXPAND is recommended.<br />

The numbering of publications is done separately for each document type. This means that:<br />

Documents of different publication levels, although being members of the same patent family, are likely <strong>to</strong><br />

have different publication numbers and<br />

Documents of different publication levels having the same publication number are rather unlikely <strong>to</strong><br />

belong <strong>to</strong> the same patent family.<br />

For a clear distinction of document types the document kind code must be specified in addition <strong>to</strong> the publication<br />

number.<br />

Due <strong>to</strong> the publication system having changed from a publication of the examined application (with a three<br />

- ost-grant opposition<br />

period) numbering has been changed for these documents <strong>to</strong> consecutive numbers starting from 2 500 001 with<br />

the publication kind code B from May 1996.<br />

JAPIO only contains unexamined applications. In World <strong>Patent</strong>s Index all publications of the national patent family<br />

are included in the PI field. The ADT field gives information on which publication relates <strong>to</strong> which application<br />

number. In INPADOCDB the members of the national family are entered in<strong>to</strong> new publication segments. The<br />

application number can also be used <strong>to</strong> identify documents based on the same application.<br />

JP documents show the publication number (as illustrated in the above format) and the publication date (including<br />

Emperor and Western years, in Roman characters), B documents show the relevant data of an earlier publication<br />

additionally (code A, T).<br />

21.5.3 Note on KR document numbers<br />

Current Korean publication and patent numbers on the printed documents include a code for the type of<br />

publication (10 = patent, 20 = utility model, 30 = design); this code is not included in the document number format<br />

on <strong>STN</strong>. The number of digits is different, <strong>to</strong>o.<br />

Example:<br />

Printed Korean number: 10- 2004- 0009844<br />

<strong>STN</strong> publication number: KR 2004009844 A<br />

139

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!