Skip to main content
 
 
 
IN THIS SECTION
7 posts
Hegedus
Last seen: 02/04/2024 - 19:23
Joined: 10/24/2018 - 20:10
CPC clarification

I am new to this so be gentle.  I am trying to understand the differences within the cpc fields.

I am working on some simple cases to get acclimated to api_wrapper.  I am looking at one of my patents,8,674,214, and I would like to search on similar cpc classified patents.  The classification is H01L 31/0735 (20130101); Y02E 10/544 (20130101) and let's start with the first. How is  H01L 31/0735 parsed with respect to the different fields?  I looked at the CPC web site and they do not use the same taxonomies. Specifically I would like to set the input type.

cpc_category

cpc_group_id

cpc_section_id

cpc_subgroup_id

cpc_subsection_id

 

Thanks in advance.

Andy

Hegedus
Last seen: 02/04/2024 - 19:23
Joined: 10/24/2018 - 20:10
The cfg file I am using

This returns no results.  What should it look like?

The CPC_Test.txt file has a single line of

H01L

#
#
#   PatentsView-APIWrapper Configuration File
#   American Institutes for Research


#   See the accompanying README.md file for instructions 
#   to modify this configuration file

#  


[QUERYFred2]
entity = "patents"
input_file = "CPC_Test.txt"
directory = "/Users/andreashegedus/PatentsView-APIWrapper" 
input_type = "cpc_category"
fields = ["patent_number", "patent_title","assignee_organization"]
sort = [{"patent_number":"asc"}]

Russ
Last seen: 03/21/2024 - 09:05
Joined: 11/14/2017 - 22:15
the easy way

Andy,

The easiest thing to do would be to hit the patents endpoint asking for your patent and specifying that you want those cpc fields and see what comes back. Here's the link that will do that: http://www.patentsview.org/api/patents/query?q={"patent_number":"8674214"}&f=["cpc_category","cpc_group_id","cpc_section_id","cpc_subgroup_id","cpc_subsection_id","cpc_sequence"].  The output isn't meant for humans though.  Copy and paste it into http://jsbeautifier.org/  

I'm trying to get patentsview to adopt swagger which makes playing with an api simple.  Check out http://patentsview.historicip.com/swagger/ You can hit the various endpoints without having to write a single line of code and you won't need jsbeautifier.

Looking at the output I think the patentsview field you want is cpc_subgroup_id.  You can then use the api_wrapper to go after those cpc_subgroup_ids.

[QUERY2]
entity = "patents"
input_file = "sample_subgroup_ids.txt"
directory = "/Users/Russ/mygit/PatentsView-APIWrapper"
input_type = "cpc_subgroup_id"
fields = ["patent_number", "patent_title","assignee_organization"]
sort = [{"patent_number":"asc"}]

type sample_subgroup_ids.txt
H01L31/0735
Y02E 10/544

Russ

 

Russ
Last seen: 03/21/2024 - 09:05
Joined: 11/14/2017 - 22:15
correction

Oops, there shouldn't have been a space in the second subgroup_id

type sample_subgroup_ids.txt
H01L31/0735
Y02E10/544

Hegedus
Last seen: 02/04/2024 - 19:23
Joined: 10/24/2018 - 20:10
USPTO Nomenclature for CPC

Hi,

 

Thanks for your thoughts they did help me out.

On a related note, when I look at the USPTO nomenclature for CPC it is different that the fields used in the API.

For example: I looked up H01L (https://www.uspto.gov/web/patents/classification/cpc/html/cpc-H01L.html#H01L)

and they use specific terms

The top level is called section (H)

The next level is class (H01) 

and finally

Subclass (H01L).

Why not use the terms such as class and subclass to relate to the CPC taxonomy?  It would make it more clear. 

Andy

PVTeam
Role: moderator
Last seen: 04/26/2024 - 10:39
Joined: 10/17/2017 - 10:47
Re: Response to USPTO NOMENCLATURE FOR CPC

Hi, 

We are looking into this issue regarding the USPTO Nomenclature for CPC and we will get back to you with an answer soon.

Thank you,

PVTeam

PVTeam
Role: moderator
Last seen: 04/26/2024 - 10:39
Joined: 10/17/2017 - 10:47
Re: Response to USPTO NOMENCLATURE FOR CPC

Hi Andy,

The CPC files that we parse to obtain CPC classifications are set up with the current fields: section, subsection, group, and subgroup. The fields cannot be changed at this time, but we will add this change to the suggested features list.

 Thank you,

 PVTeam