16.05.2014 Views

Patent It Yourself - PDF Archive

Patent It Yourself - PDF Archive

Patent It Yourself - PDF Archive

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

350 | <strong>Patent</strong> it YOURSELF<br />

excessive it is possible to complain to the examiner’s<br />

supervisor, but frankly supervisors usually support the<br />

examiner in these situations.<br />

34. Limitations on Number of Claims<br />

As indicated in Chapter 10, the basic filing fee entitles an<br />

applicant to submit three independent and 20 total claims.<br />

If an application is filed with or amended to have over<br />

three independent claims or over 20 total claims, the PTO<br />

requires a large fee for each extra independent claim and<br />

a medium fee for each extra total claim. However if you<br />

file more than the basic “3/20” allotment of claims, be sure<br />

that they differ significantly because examiners don’t like<br />

to examine a lot of claims, even if you pay for them. The<br />

examiner can reject excessive claims (that is, they do not<br />

differ substantially) as unduly multiplied.<br />

35. The PTO Has Been Very<br />

Difficult on Applicants<br />

In the period between 2007 through 2009, the PTO was<br />

very difficult on applicants by making numerous Whacka-Mole<br />

rejections (see <strong>It</strong>em 33, above), making far-fetched<br />

rejections, using a very high standard of patentability, being<br />

antagonistic to applicants and attorneys, and refraining<br />

from assisting applicants or making any constructive<br />

suggestions. One examiner, in an anonymous post on the<br />

Internet, said:<br />

“My view is that under [the last Commissioner] the <strong>Patent</strong><br />

Office became the <strong>Patent</strong> ‘Rejection’ Office, and instead of<br />

trying to protect IP rights (which is our purpose), USPTO<br />

management’s solution was to hire lots of people to reject<br />

out of the problem. This led to an assembly line of under<br />

trained, unknowledgeable examiners who were taught<br />

how to reject, but not how to get applications to allowance.<br />

This ‘reject, reject, reject now’ policy is encouraged by<br />

management’s policy of issuing a written warning on an<br />

examiner’s permanent file for allowance error percentage<br />

above 10%. While this may seem high, if you only allow 20<br />

cases a year it is no problem for quality to find some kind<br />

of error in your cases, especially when they aren’t experts<br />

in your art. Additionally, there is a lack of motivation<br />

to get cases allowed, because there is no incentive for the<br />

examiner to do the extra work required to arrive at claim<br />

language which can be allowed. Getting claim language<br />

to this point takes me several phone calls with attorneys<br />

and/or inventors due to the fact that disclosures typically<br />

contain multiple inventions, but claims must be limited<br />

to one and because the attorneys and not the inventors<br />

usually draft claim language which is usually broad. Add<br />

the time spent on phone calls to the lack of credit/counts<br />

given for time spent responding to amendments and the<br />

examiner is further discouraged from getting cases to<br />

allowance.” IPWatchdog.com (Blog of 2009 Mar 17).<br />

A similar view was expressed by noted patent gadfly Greg<br />

Aharonian in one of his blog entries at www.Bust<strong>Patent</strong>s.<br />

com. What’s the answer? The only recourse that I can see is<br />

to prosecute your applications as instructed in this chapter,<br />

attacking each improper rejection and appealing when<br />

necessary. Make sure your claims are in optimal condition<br />

and define your invention’s novelty over the references<br />

taken individually or in any combination. If necessary,<br />

file a continuation (use an RCE—see Chapter 14) to revise<br />

your claims after a final action. Don’t hesitate to appeal if<br />

necessary. If you appeal, be sure to try a “Pre-Appeal Brief<br />

Request for Review” (see Section J4, below). Always keep<br />

you temper and don’t attack your examiner personally since<br />

he or she is merely following instructions.<br />

Remember to always use the two-part 102 (novelty)-103<br />

(unobviousness) approach whenever you argue patentability<br />

—see Inventor’s Commandment 7 in Chapter 5.<br />

36. Avoid Fraud on the PTO<br />

In all of your statements, arguments, and representations to<br />

the PTO you should be careful to be honest and forthright<br />

and not to make any statements to the examiner by which<br />

you intend to deceive, mislead, or “snow” the examiner.<br />

This is because a court can hold your patent invalid if it<br />

ever discovers that any statement that you made to the<br />

PTO amounted to “fraud on the PTO” and you intended<br />

to deceive the PTO. E.g., if you intentionally misrepresent<br />

the operation or construction of a reference or claim<br />

false and excessive results for your invention, and your<br />

adversary discovers this later in litigation, they will bring<br />

it to the attention of the judge, who will likely hold your<br />

patent invalid. So always state the truth, the full truth, and<br />

nothing but the truth.<br />

37. Keep Your Remarks as Short as Possible<br />

There are a number of reasons to keep your remarks as<br />

short as possible. First, examiners tend to be put off and<br />

hence may not read overly long responses. Their time is<br />

limited and they are under pressure to dispose of (allow or<br />

have the applicant abandon applications). So to get your<br />

remarks read, keep them as short as possible, but include<br />

all the arguments that you feel are necessary. Second, as<br />

noted by patent attorney Michael E. Kondoudis (www.

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

Saved successfully!

Ooh no, something went wrong!