prima facie<\/em> case of obviousness and arguing that the Examiner has not met this burden.<\/p>\nPatent attorneys have differing opinions regarding whether examiners should be called out if an Office Action is deficient in providing a factual basis establishing obviousness, or if the reasoning lacks a rational underpinning. In my practice, I am often aggressive in addressing such deficiencies, but I try to balance this based on my clients\u2019 preferred strategy and will often interview with the examiner if the circumstances suggest it would be beneficial.<\/p>\n
As practitioners, we can settle into patterns of what we do, and we are not always in tune with whether that\u2019s the most effective approach. With this in mind, I wondered if attacking a rejection from this perspective was generally hurting or helping my clients, taken as a whole. To analyze this, I used PatentAdvisor\u2019s File Wrapper search and searched responses to Office Action filed with the USPTO that used the language \u201cprima facie<\/em> case of obviousness.\u201d I assumed that if this language was mentioned, the applicant was arguing that the examiner had not established a prima facie<\/em> case of obviousness. Patent lawyers do not use this language to congratulate the examiner for establishing a prima facie<\/em> case of obviousness. No examiner has ever read, for example, \u201c[i]t is respectfully submitted that the Examiner has eloquently established a prima facie<\/em> case of obviousness.\u201d<\/p>\nAfter obtaining the results for \u201cprima facie<\/em> case of obviousness,\u201d I then narrowed the results to applications disposed (patented or abandoned) since 2019 and sorted by technology center for allowance rates and Office Actions per patent and compared these results to the average allowance rates in each technology center for disposed applications during this same time period that included an obviousness rejection.<\/p>\nThe results show that arguing the Examiner has not established a prima facie<\/em> case of obviousness is not detrimental in any of the technology centers in terms of allowance rate. In fact, it is beneficial for increasing allowance rates, especially in technology centers having the lowest allowance rates.<\/p>\n<\/p>\n
Technology centers 1600, 1700, 3600 and 3700 are the most difficult tech centers at the USPTO and arguing that the Examiner has not established a prima facie<\/em> case of obviousness results in the biggest jumps in allowance rates in these art units. In contrast, in the easier technology centers, 2100, 2400, 2600 and 2800, bringing up a prima facie<\/em> case of obviousness still appears to have a minor benefit, but not as much as the more difficult art units.<\/p>\nHowever, analytically speaking, there are downsides to arguing that the Examiner has not established a prima facie<\/em> case of obviousness. In particular, as shown below, on average, challenging the Examiner in a such a manner can lengthen prosecution to a degree. For cases including responses that mentioned \u201cprima facie<\/em> case of obviousness\u201d there was a higher number of Office Actions issued by patented case. In particular, there was an increase of between 0.5 and 0.8 Office Actions per patent, depending on the art unit.<\/p>\n<\/p>\n
This is certainly only a small glimpse of data (I hope that we soon all have much more data within our grasps), but it implies to a degree that arguing the Examiner has not established a prima facie<\/em> case of obviousness can increase the number of Office Action responses filed.<\/p>\nHowever, it says nothing about claim scope or other arguments presented. I would presume that arguing the examiner has not established a prima facie<\/em> case of obviousness results in less narrowing amendments than the average response. It shows a resistant response, and resistance logically correlates to arguing a rejection without amending the claims. In other words, it shows an applicant who genuinely believes the examiner is wrong and is not going to narrow the scope of protection to appease the Examiner.<\/p>\nIf the subject matter of a patent application is important, it certainly makes sense to spend extra resources fighting tooth and nail for claim scope. That\u2019s a no brainer. But if an application is less important, a more deferential approach can be helpful. I\u2019ve always thought that one of the most unique aspects of patent prosecution is the ability to pull out your aggressive lawyer approach selectively, balanced with a technical mind for problem solving and wordsmithing claim scope to thread the needle.<\/p>\n
When in Doubt, Interview<\/strong><\/h2>\nBut a different look at the data, as shown below, illustrates that interviews will bump your allowance rate up further. Regardless of whether or not you are arguing burden, it will pump up the allowance rate. This data also shows that there is place for calling out the examiner for not meeting the Section 103 burden AND reaching out to the examiner in a deferential manner. They are skills we all have to balance as patent attorneys. We need to figure out the limits of what the examiner will allow with a combination of technical and legal dialogue. We cannot settle for scope that is unhelpful to our clients but we also cannot waste a client\u2019s money by unnecessarily fighting over trivial language.<\/p>\n
<\/p>\n
Consider All the Angles<\/strong><\/h2>\nWhile this data is not airtight and could certainly be picked apart by a statistician, we can still gather insights from it to guide our practice. First, fighting back against difficult and\/or inexperienced examiners is not without value. Second, fighting back in the wrong cases can be unhelpful. Third, always try to interview if you think there is any chance of reaching an agreement with the examiner.<\/p>\n
Most importantly, thinking about prosecution from different angles is bound to pay off in the long run.
\n
\nImage Source: Deposit Photos
\nImage Author: Rawpixel
\nImage ID: 126977324\u00a0<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"Lawyers should always be trying to look at things from new and different angles to gain an edge. We owe it to our clients, and honestly, we should do it for ourselves, because it makes practicing more fulfilling. In an effort to spice up my patent law life, I have become especially interested in patent analytics over the past few years\u2014that\u2019s right, I just used \u201cpatent analytics\u201d and \u201cspice up\u201d in the same sentence.<\/p>\n","protected":false},"author":110941,"featured_media":151867,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":"","_links_to":"","_links_to_target":""},"categories":[5519,6998,228,3,5883,37020,41],"tags":[2742,5531,49,33,13385,40,238,74190,8727],"yst_prominent_words":[23615,65466,20122,15438,26156,23610,56856,15244,39540,16114,15341],"acf":[],"_links":{"self":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts\/151863"}],"collection":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/users\/110941"}],"replies":[{"embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/comments?post=151863"}],"version-history":[{"count":1,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts\/151863\/revisions"}],"predecessor-version":[{"id":151868,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/posts\/151863\/revisions\/151868"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/media\/151867"}],"wp:attachment":[{"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/media?parent=151863"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/categories?post=151863"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/tags?post=151863"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https:\/\/ipwatchdog.com\/wp-json\/wp\/v2\/yst_prominent_words?post=151863"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}