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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

216<br />

<strong>Guide</strong> <strong>to</strong> <strong>STN</strong> <strong>Patent</strong> <strong>Databases</strong><br />

- Gaming and prize redemption system.<br />

- Prize redemption system for games executed over a wide area network.<br />

- Progressive-type prize awarding scheme.<br />

28.8.4 Moni<strong>to</strong>ring patent families in INPADOCDB/INPAFAMDB Family SDI<br />

In INPADOCDB/INPAFAMDB it is possible <strong>to</strong> moni<strong>to</strong>r patent families (manually or au<strong>to</strong>matically). The fields for this<br />

see in the table above. Any event occurring <strong>to</strong> the patent family can be found this way, from the first entry of a<br />

family member <strong>to</strong> changes <strong>to</strong> the legal status. Here are some notes on the update fields:<br />

If certain update fields are set the same date will au<strong>to</strong>matically be entered in other update fields (INPADOCDB):<br />

EDF UPFD, UPFP, UPFB, UPFE, UPFA<br />

UPFD UPFP, UPFB, UPFE, UPFA<br />

UPFP UPFB, UPFE, UPFA<br />

UPFB UPFA<br />

Using DISPLAY UPALL the table of updates can be displayed for every document.<br />

Thanks <strong>to</strong> the database structure of INPAFAMDB it is easy <strong>to</strong> moni<strong>to</strong>r patent families in this database. All update<br />

codes in this database relate <strong>to</strong> the patent family.<br />

In INPADOCDB both record-based and family-based moni<strong>to</strong>ring can be done. The following table shows the<br />

relevant fields:<br />

Record (INPADOCDB) Family (INPADOCDB<br />

New family (new family number FN) - EDF<br />

Merged or split families - UPFC<br />

New record (member) EDP UPFD<br />

New document ED UPFP<br />

Update of BIB + IND UP UPFB<br />

Update of BIB UPBB UPBB<br />

Update of IND UPCC UPCC<br />

Update of the legal status (LS) UPLS UPFL<br />

New document or LS EDLS UPFE<br />

All updates / changes UPM UPFA<br />

formats, i.e. you will be charged only for data that actually appear in the display.<br />

FFAMUP All BIB and/or LSUP of family members updated with the current update, weekly SDI<br />

FFAMUP4 All BIB and/or LSUP of family members updated with the current update, monthly SDI<br />

FFAMUP.PC Country specific FFAMUP, e.g. FFAMUP.EP<br />

(only for these countries:<br />

PC=AT AU BE CA CH DE DK EP ES FI FR GB GR IE IL IT JP HU NL NO SE US WO)<br />

FFAMED New publications and/or LSUP of a patent family, weekly SDI<br />

FFAMED4 New publications and/or LSUP of a patent family, monthly SDI<br />

FFAMED.PC Country specific FFAMED, e.g. FFAMED.US<br />

(only for these countries:<br />

PC=AT AU BE CA CH DE DK EP ES FI FR GB GR IE IL IT JP HU NL NO SE US WO)<br />

LFAMUP PI (Publication Information) and LSUP (legal status changed) of the current update week of a patent family,<br />

weekly SDI<br />

LFAMUP4 PI (Publication Information) and LSUP (legal status changed) of the current update week of a patent family,<br />

monthly SDI<br />

LFAMUP.PC Country specific LFAMUP, e.g. LFAMUP.FR<br />

(only for these countries:<br />

PC= AT AU BE CA CH DE DK EP ES FI FR GB NL NO SE US WO)<br />

UPALL Table of update dates<br />

The update fields needed for a Family SDI are available if any update has occurred <strong>to</strong> the patent family since the<br />

introduction of this feature (9/2004). (This may be important in a retrospective search if you wish <strong>to</strong> use any of the<br />

UP fields.)<br />

=> D BIB UPALL<br />

AN 53039753 INPADOCDB ED 20070505 EW 200718 UP 20070505 UW 200718

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

Saved successfully!

Ooh no, something went wrong!