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.

ChaPter 13 | GETTING the Pto to DELIVER | 349<br />

associated with a rejection). In addition, anyone can follow<br />

the prosecution of your application (that is, see your Office<br />

Actions and amendments) on the PTO’s “Private PAIR” site.<br />

29. When Submitting Arguments,<br />

Rely on Statutes, Rules, and the<br />

MPEP, Rather Than Case Law<br />

When drafting the remarks portion of an amendment, it’s<br />

helpful to cite authority for any rule of law or requirement<br />

that you rely upon. I’ve tried to provide most of the rules<br />

and main arguments in this chapter, but there are many<br />

more that I do not have room to include. If you need to find<br />

an authority for your position, look in the MPEP, which<br />

is available online at the PTO’s site. The MPEP has a full<br />

online index and its Chapter 2100 on patentability is very<br />

helpful. If and when you do cite any authority, keep in mind<br />

that examiners consider the patent statutes (35 USC), the<br />

Rules of Practice (37 CFR), and the MPEP to be the most<br />

meaningful authorities. Examiners are strictly bound to<br />

follow these authorities. There are thousands of patent cases<br />

available also, but examiners find these far less persuasive<br />

and less useful. (One reason is that it’s difficult and timeconsuming<br />

for an examiner to look up and analyze a case.)<br />

In fact, when I was employed as an examiner, my supervisor<br />

told me never to cite a case since the attorney for the<br />

applicant could always rebut me by citing a different case<br />

with a contrary holding!<br />

30. Don’t Wait Until the Last Minute<br />

I find that most inventors who receive an Office Action<br />

tend to wait until near the end of the three-month period,<br />

or even later, to draft their response. The reason for this<br />

procrastination is usually due to fear of tackling a new task.<br />

However I strongly advise you grit your teeth and do the<br />

job as soon as possible so that you will have enough time,<br />

you won’t be rushed, you can ramp-up to the nuances and<br />

intricacies of the process, and you’ll have time to review<br />

and polish your work.<br />

31. <strong>Patent</strong>s and Published <strong>Patent</strong> Applications<br />

Are Prior Art as of Their Filing Date<br />

as Well as Their Publication Date<br />

As discussed in Chapter 5, patents and published patent<br />

applications (PubPAs), unlike other publications, are<br />

effective as of their filing date, in addition to their<br />

publication date. So if the examiner rejects your claims on<br />

a patent or PubPA, you may have to consider both dates<br />

when formulating your response. If the patent or PubPA<br />

was published over a year before your filing date, it’s a<br />

statutory bar (Section 102(b)) so you can’t swear behind it<br />

(see Section D3 below) and thus only the publication date<br />

is relevant. If the patent or PubPA was published less than a<br />

year before your filing date, it’s prior art as of its publication<br />

date (Section 102(a)) and as of its filing date (Section 102(e)).<br />

You must swear behind the earlier (filing) date by proving<br />

an earlier date of invention—see Section D3, below, and<br />

also review Chapter 5, Section E1b. Check the date of all<br />

prior art cited against your application, since examiners<br />

sometimes make mistakes—for example, after the PTO<br />

published an application of Nokia’s, an examiner examined<br />

the application and mistakenly cited the published patent<br />

application against itself!<br />

32. <strong>Patent</strong> Examiners Overwhelmed<br />

An article on WashingtonPost.com (2007 Oct 8) noted that<br />

examiner turnover and the PTO’s backlog are very high<br />

due to production quotas, difficulty of searching, and the<br />

cost of living in the DC area. In other words, the quality of<br />

examination has been declining and the delay in receiving<br />

an Office Action has been increasing, a situation that could<br />

be harmful to U.S. competitiveness. For this reason you<br />

may have to wait a long time before you receive a first Office<br />

Action. You can check the status of cases in your examining<br />

division to ascertain approximately when you will hear<br />

from the PTO. To do so, first find out the examining<br />

division or Group Art Unit from your Filing Receipt. Then,<br />

go to the PTO’s home page (www.uspto.gov), click <strong>Patent</strong>s,<br />

then Search Aids, then OG (Official Gazette) regular and<br />

special notices, then Browse [current year], and finally<br />

click the latest issue. Click <strong>Patent</strong> Technology Centers and<br />

find your Group Art Unit. In the right-hand column find<br />

the average filing date that your GAU is working on now.<br />

Compute the time from this date to the present date and<br />

add this time to your filing date to find the approximate<br />

date they will reach your case.<br />

33. Beware of “Whack-a-Mole” Rejections<br />

Examiners have been increasingly making subsequent<br />

rejections on a different ground than a previously rebutted<br />

rejection, even though the subsequent rejection could have<br />

been made when the previous rejection was made. Some<br />

patent attorneys have termed this practice, “Whack-a-<br />

Mole Rejecting.” (<strong>It</strong> is also called piecemeal prosecution<br />

and condemned in the MPEP.) There is no good solution<br />

except to be aware in advance that it may occur and to take<br />

it philosophically if it does occur and patiently respond<br />

to each new rejection in the usual manner. If it becomes

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

Saved successfully!

Ooh no, something went wrong!