Five IP Offices statistic tools

The Five IP Offices (IP5) is the name given to a forum of the five largest intellectual property offices in the world that is being set up to improve the efficiency of the examination process for patents worldwide. The members of IP5 are:

• the European Patent Office (EPO),

• the Japan Patent Office (JPO),

• the Korean Intellectual Property Office (KIPO),

• the State Intellectual Property Office of the People's Republic of China (SIPO),  

• and the United States Patent and Trademark Office (USPTO).

The IP5 Offices account for 90% of all patent applications filed worldwide and for 93% of all work carried out under the Patent Cooperation Treaty (PCT).
The vision of the IP5 Offices is global co-operation, which has been defined as "the elimination of unnecessary duplication of work among the IP5 Offices, the enhancement of patent examination efficiency and quality and guarantee of the stability of patent right". The objective is to address the ever-increasing backlog at the world's five biggest intellectual property offices. As the world sees economic barriers between nations fade away, innovators want their intellectual creations protected concurrently in multiple major markets. Hence, applications for the same technology are filed at more than one patent office. The solution to the backlog problem is to reduce, to the maximum extent possible, the duplication of work which takes place at each office for a family of patent applications.

in its website aside from a lot of useful statistics and data reports (http://www.fiveipoffices.org/stats.html) it is possible to find also a very useful tool displaying for a given patent the full pentadic family data and also the timeline of all priorities and family members:

http://ccd.fiveipoffices.org/CCD-2.0/



 

Crios Patstat Online DB update

updated version (data oct. 2013) of Crios Patstat db (formerly Kites patstat db) is availale at address:

db.crios.unibocconi.it

or

http://ricercaweb.unibocconi.it/criospatstatdb/

(please note previous address db.kites.unibocconi.it is no more available)

This is the full list of available reports:

Patent count by inventor country / year
Patent count by applicant country / year
Patent count by inventor region / year
Patent count by applicant region / year
Patent count by inventor nuts3 / year
Patent count by applicant nuts3 / year
Patent count by applicant name / year
Patent count by main IPC - first 4 digits
Patent count by main IPC class reclassified on OST30
Patent count by applicant, year, OST30
Patent count by applicant country, county, region, OST30, year
Citations count by applicant name, year
Citations count by applicant country, year
Citations count by inventor country, year
Copatenting by inventor country, year
Copatenting by applicant country, year
Applicants by IPC - first 4 digits
Inventors by IPC - first 4 digits

Fixing duplicated persons in TLS207

Due to a bug in original data in DOCDB, a percentage of person ids appear twice for the same application.

I pubblish here a code for MySql but easily adaptable to other platforms, for fixing the issue.


The following code creates starting from a list of application ids (XX_appln_id usually I have all EPO applications in it); it must be broken into 3 parts cause in case of duplicates I take the minimum seq_nr (both for applicant and inventor) but in order to avoid cases where we have the same person id as inventor and applicant (so where the min would be 0) in a support table and for the final table I take the max seq_nr.



use newpatstat;

drop table if exists TLS207_pers_appln;
drop table if exists TLS207_pers_appln0;


create table TLS207_pers_appln0
SELECT  e.person_id, e.APPLN_ID, min(e.applt_seq_nr) as applt_seq_nr, invt_seq_nr 
from  patstat.TLS207_pers_appln e
inner join XX_appln_id t on t.appln_id = e .appln_id
where e.invt_seq_nr =0
group by e.person_id, e.APPLN_ID, e.invt_seq_nr ;


insert into TLS207_pers_appln0
SELECT  e.person_id, e.APPLN_ID, e.applt_seq_nr, min(e.invt_seq_nr ) as invt_seq_nr
from  patstat.TLS207_pers_appln e
inner join XX_appln_id t on t.appln_id = e .appln_id
where e.applt_seq_nr =0
group by e.person_id, e.APPLN_ID, e.applt_seq_nr ;

insert into TLS207_pers_appln0
SELECT  e.person_id, e.APPLN_ID, min(e.applt_seq_nr) as applt_seq_nr, min(e.invt_seq_nr) as invt_seq_nr 
from  patstat.TLS207_pers_appln e
inner join XX_appln_id t on t.appln_id = e .appln_id
group by e.person_id, e.APPLN_ID;


create table TLS207_pers_appln
SELECT  e.person_id, e.APPLN_ID, max(e.applt_seq_nr) as applt_seq_nr, max(e.invt_seq_nr ) as invt_seq_nr 
from  TLS207_pers_appln0 e
group by e.person_id, e.APPLN_ID;


CREATE INDEX IDX207_PERSON ON TLS207_PERS_APPLN(PERSON_ID);
CREATE INDEX IDX207_APPLN ON TLS207_PERS_APPLN(APPLN_ID);


drop table if exists tls207_chk01;
drop table if exists tls207_chk02;


-- two check tables should be empty

create table tls207_chk01
SELECT t.APPLN_ID, t.person_id, invt_seq_nr, Count(t.APPLN_ID) AS cc
FROM tls207_pers_appln t
GROUP BY t.APPLN_ID, t.person_id, invt_seq_nr
HAVING cc >  '1';

create table tls207_chk02
SELECT t.APPLN_ID, t.person_id, applt_seq_nr, Count(t.APPLN_ID) AS cc
FROM tls207_pers_appln t
GROUP BY t.APPLN_ID, t.person_id , applt_seq_nr
HAVING cc >  '1';



drop table if exists TLS207_pers_appln0;

European Patent Register for PATSTAT

As previously annonced EPO has released EP register data as plug and play extension of patstat.

This new dataset, linkable by appln_id to the other tables, contains the full track of events the application goes across (the legal events table TLS221 may be considered as a subset of this dataset) as well as legal rappresentative and aother useful pieces of info.

An example of the data contained (for EP1.000.000):

https://register.epo.org/application?number=EP99203729&tab=main

here the full EPO letter announcing the releaase:




It is our pleasure to announce that we now have the “European Patent Register for PATSTAT” database ready for sale.  

What is the European Patent Register for PATSTAT ?

The European Patent Register for PATSTAT is a data base extracted from the European Patent Register.  In this database, the European Patent Office stores all the publicly available information it has on European patent applications (inclusive Euro-PCT) as they pass through the grant procedure.  The main purpose of the data base is to allow patent information users in companies, research institutes and public institutions to carry out in-depth statistical or business intelligence analysis of European patent applications.

What can the register do for you ?

Possible areas of research:

§        Broad analysis of the European patent system
§        Applicant filing behaviour at the EPO
§        Technology developments
§        Speed an quality of the granting process
§        Competition matters

Typical questions that can be answered with this data base:

§        In what stage of the procedure do we find European patent applications:  published, refused, withdrawn, granted, opposed, revoked, amended,...  ?
§        Oppositions to a European patents: who is opposing who, in what technological areas (IPC-based) is opposition custom, how long do the various procedural steps take, ... ?
§        How do you find professional representatives active in a certain technological area?
§        What are the success rates of opposition and appeal proceedings?
§        How wide is the scope of the cited prior art? What is the impact of non-patent literature?

How does this new data base relate to PATSTAT ?

The “European Patent Register for PATSTAT” can be used as a standalone database or can be linked to PATSTAT via the application identification (appln_id) .  There are sufficient bibliographical attributes to carry out a broad range of analysis on European patent applications without the need of having PATSTAT.  But it speaks for itself that linking PATSTAT to the “European Patent Register for PATSTAT” opens a whole new range of analysis which was previously not easy possible.



Where do you start ?

If you are interested in “European Patent Register for PATSTAT”, we would advise you to first download a sample data set so that you can check for yourself it the data base contains the necessary attributes for your purpose.  
This sample is available in MS ACCESS format via this link: https://publication.epo.org/raw-data/product?productId=1
We also strongly recommend you to consult the Register Data Catalog if you want to learn about the details of the various tables and attributes.  Here is the link: http://documents.epo.org/projects/babylon/eponet.nsf/0/2A7D990B3A6ADDCCC1257C4000559878/$File/data_catalog_register_v1-1-2_en.pdf

For pricing, we kindly refer you to this document : http://documents.epo.org/projects/babylon/eponet.nsf/0/2A7D990B3A6ADDCCC1257C4000559878/$File/patstat_family_products_pricelist_en.pdf
You will see that we have made a very competitive package price for users who want to order the 3 products together:

ü        PATSTAT
ü        European Patent Register for PATSTAT
ü        EPO worldwide legal status database for PATSTAT

If you have any further questions, don't hesitate to contact us via patstat@epo.org .

MySQL upload scripts for EEE-PPAT october 2013

EEE-PPAT table is an extension of the PERSON TABLE (TLS206) produced by ECOOM (Catholic University of Leuven) and Eurostat (see here). The extension concerns sector allocation and name harmonization of applicants.



October 2013 ediction contains 44730405 records, but it has standardized names and sectors for 15.291.352 legal person (not for individuals).

It can be required at no cost by contacting technoinfo@ecoom.be

MySql script I created for uploading the table can be downloaded here

Missing addresses in patstat ediction oct. 2013

Aside from an already announced by epo lack of data in ipc table (see here) there is another issue, this time involving address data.

The check has been run against EPO data (thanks to Xiaoyan Song from ECOOM for rising the issue)

Select
  patstat.tls207_pers_appln.PERSON_ID,
  patstat.tls207_pers_appln.APPLN_ID,
  patstat.tls207_pers_appln.APPLT_SEQ_NR,
  patstat.tls207_pers_appln.INVT_SEQ_NR,
  patstat.tls211_pat_publn.PUBLN_AUTH,
  patstat.tls206_person.PERSON_NAME,
  patstat.tls206_person.PERSON_ADDRESS,
  patstat.tls206_person.DOC_STD_NAME_ID
From
  patstat.tls206_person Inner Join
  patstat.tls207_pers_appln On patstat.tls207_pers_appln.PERSON_ID =
    patstat.tls206_person.PERSON_ID Inner Join
  patstat.tls211_pat_publn On patstat.tls211_pat_publn.APPLN_ID =
    patstat.tls207_pers_appln.APPLN_ID
Where
  patstat.tls211_pat_publn.PUBLN_AUTH = 'EP' And
  patstat.tls206_person.PERSON_ADDRESS = ""

We find that 292110 application/person have no address vs a total of 16.866.000 (about 2%).

This means many person_ids that in previous edictions had an address now have lost it.

For instance appln_id 57746196 had in oct 2012 applicant 4473356 Canon Kabushiki Kaisha with address 30-2 Shimomaruko 3-chome  Ohta-ku Tokyo.

Now appln_id 57746196 has as applicant person_id 5216598 that is still Canon Kabushiki Kaisha has no address.

In total we have 188107 person_id that suffer from this issue.

Some of them, counting by appln_id, are big players.

person_id	count(appln_id)
263	7208
5355192	1547
5238080	1333
5235181	1014
5217811	612
5818520	459
5213673	386
6156118	344
5262071	288

Person_id 263 (empty name and address) in reality has been also added in many cases where previous versions of patstat reported no applicant / inventor for a given application.

IPCs missing in october 2013 ediction

this year patstat ediction came with some deficiency in table TLS209. EPO itself send a letter to all users...


Dear PATSTAT users,

It does not happen often, but we have to notify you about a deficiency in the current PATSTAT version. We have observed that about 4.5 per cent of the applications in the PATSTAT October 2013 release have their IPC codes missing. 99 % of the missing IPC codes belong to Japanese applications filed before the year 2000.

If you do not use IPC codes for your analyses, then you don’t need to take any action.

We have looked at various options to solve the observed problem, and offer the following remedies:

1) Users who have the APRIL 2013 edition installed on their server can with a small script merge the missing IPC codes from the tls209_appln_ipc (APRIL 2013 edition) into the October 2013 edition.  This process takes about 10 minutes.

The script needs be adapted to your own environment, e.g. by changing the data base name and/or table names.

2) User who do not have the APRIL 2013 edition will need to download new source files with the missing IPC codes.  There are 2 options: You can download and install the APRIL 2013 edition of tls209_appln_ipc files and proceed as above, or alternatively, you can download a newly created CSV file that contains the full ready-made merged file.


Don’t hesitate to contact us via patstat@epo.org if you need any further information.

Geert Boedt & Christian Soltmann
Business use of patent information
PATSTAT promotion & customer support