Forward Rejections - Search Playbooks

AcclaimIP strives to make sure you can build very powerful search queries as easily as possible. That's why there is the Search Playbooks tab. These Search Playbooks are designed to allow you to plug in pieces of a search without having to remember field codes, and allow the system to build the search query for you.

Generally speaking, the information from the fields here (e.g., the blocked assignee on the Record-Level Rejection section, etc.) will be listed in the Forward Rejections tab of the patents returned by the search.

Forward Rejection Query Form Breakdown

The Forward Rejection Query Form has four sections:

1) Search Options - Standard search options (see Default Search Options breakdown here: Quick View of Available Preferences)

2) Base Query

3) Record-Level Rejection Query

4) Document-Level Rejection Query

Note - you can choose as few or as many of the options available to you. In other words, you do not have to fill out the entire form. Even if you only choose to fill out only one field in the entire form, that is ok.

Base Query

1) Select the Assignee of the patents returned. For example, if I worked for CompanyX and wanted all of my patents with rejections, I would choose CompanyX from the normalized assignee dropdown here.

2) Here you can add additional field codes to restrict the search. For instance, if you only want a particular class code or a particular term in the title, you can use field codes here to add to your search.

Note - if you only use the Base Query fields assignee dropdown and do not add any other fields, the search will be exactly like using the patent owners, query builder, or quick search, and isn't limited to patents with forward rejection data. In other words, if you choose "IBM" from the assignee dropdown (1), with no other fields, it will return the entirety of IBM's portfolio.

Record-Level Rejection Query

1) Blocked Assignee - Select the assignee that has been blocked. In other words, the assignee chosen here is the one that submitted the application to the USPTO that the examiner sent an Office Action back to saying it was rejected due to a 102 or 103 rejection.

2) Rejection Type - Select the rejection type (102 or 103). Note that AcclaimIP breaks the 103 rejections down further by showing you where in the obviousness argument the patent is (e.g., if the 103 says "PatentX in view of PatentY in view of PatentZ" then PatentX is the 103.1, PatentY is the 103.2, and PatentZ is the 103.3).

3) Blocked App Status - Select the status of the app that has been blocked. This is the status of the app that is owned by the assignee chosen here in (1) on this section, the Record-Level Blocked Assignee dropdown, not the app owned by the assignee chosen in the Base Query section.

4) Rejection Date - Select the date or date range of when the rejection by the USPTO examiner occurred. Leaving this field blank will choose all date ranges (although of course this may be affected by date ranges chosen elsewhere, such as the filed date).

5) Caused Abandonment - When toggled On, this field restricts the search to only those that caused the blocked assignee to abandon their application. Note that in rare instances, an abandonment may be overcome, but would still have the abandonment on the record. So it is possible to have a granted patent that was abandoned during the application process.

6) Caused Claim Amendment - When toggled On, this field restricts the search to only those that caused the blocked assignee to have to amend their claims.

7) Caused Final Rejection - When toggled On, this field restricts the search to only those that caused the blocked assignee to receive a Final Rejection from the USPTO.

8) CPC Class of Blocked App - Select the CPC class of the blocked assignee's app. This may be different than the CPC class of the blocking document based on the Base Query. In other words, if you chose G06F9* here, the blocked app would have to have a some G06F9 class. But the blocking document that the USPTO examiner used in the 102/103 may have had some H24L9 class. Also note that you can use more than one class, but you have to separate them with the OR boolean operator (e.g., H04L65/403 OR H24L9*)

Document-Level Rejection Query

1) No. Unique Blocked Applications - Select the number or range of numbers of unique blocked applications. This is tied to the Record-Level Rejection Query assignee/search term documents, since they are the documents being blocked. Also note that this is unique applications (e.g., if the blocking document, patentX, has been used to block applicationY multiple times, applicationY would still only count once).

2) of Rejection Type - Select the rejection type(s) the number of unique blocked applications relates to. Note that these are cumulative. In other words, if you selected 2 only for the "No. Unique Blocked Applications" range, and selected both 102 and 103.1 for "of Rejection Type," the system would return documents with 2 unique blocked applications, whether they had 102 rejections, 103.1 rejections, or both.

3) Date of Most Recent Rejections - Select the date range of the most recent rejections.  Note that this is not limiting all rejections to this date range, only the most recent one. Documents may have rejections older than your date range, as well.

4) No. Unique Blocked Assignees - Select the number or range of numbers of unique blocked assignees. This is tied to the Record-Level Rejection Query assignee/search term documents, since they are the documents being blocked. Also note that this is unique applications (e.g., if the blocking document, patentX, has been used to block AssigneeY multiple times, AssigneeY would still only count once).

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.