Years later in litigation, who can recall when an Office was closed?

US practitioners have burned into their memory the débacle of December 22-27, 2015 when all of USPTO’s e-filing systems were broken.  For litigation purposes there will surely be cases where it will matter a lot whether a filing that got done on December 28, 2015 was or was not timely.  And any US practitioner will have no trouble remembering this very disruptive time.

But ten years from now in litigation, how will it be recalled that, for example, Monday, March 17, 2014 was a snow day at the USPTO?  (Maybe the litigants will think to check my blog article about that snow day.)

I am delighted to be able to report that for five years now, WIPO has been quietly maintaining a searchable historical database on exactly this topic.   You can go there and click on “US” and then click on “2014” and right there it lists March 17, 2014 as a day that the USPTO was closed.

This valuable resource from WIPO is the sort of database that you hope you will never need, but if you need it, it can be a lifesaver.

For inbound foreign work, who’s the client?

A thoughtful reader (I’ll call him “WW”) asks:

I have an ethics-related question that should be relevant to most U.S. patent practitioners, though I haven’t been able to find any writings about it online.

The issue is, “who is the client”, for foreign-originated patent filings in the US?

The client could possibly be either the foreign originating firm, or it could be their own ultimate client, or possibly both.

To the extent we have a choice (for example, by specifying in an engagement letter signed by all parties), which would be better? I can see benefits and detriments to either choice.

I’ll offer one or two thoughts about this, and then I’d like to invite readers to please post comments with their own points of view about all of this. Continue reading “For inbound foreign work, who’s the client?”

USPTO e-commerce systems continue to stumble

USPTO online systems continue to stumble or crash.  Much of this, I expect, is a consequence of cobbled-together temporary fixes to the massive UPS failures that happened on December 22.  Here’s a brief recap of today’s situation:

  • Newly filed patent applications and entries into the US national phase that were filed on January 5 seem to have been lost.  USPTO is trying to recover them but after more than a week they have not been recovered.  See further comments on this “January 5 problem” in a later blog post.
  • EFS-Web petitions that are supposed to be auto-granted are all broken.  We have a case that is scheduled to issue next Tuesday and we need to get it withdrawn from issue.  The auto-granting petition in EFS-Web keeps freezing and crashing.  EBC has acknowledged this as a known problem.  Hopefully USPTO will get this system repaired before next Tuesday.
  • Document display within TSDR has been on-again-off-again for the past couple of days.  As of right this moment it is on again.
  • ETAS sometimes crashes when you try to pay the recordation fee.  (EPAS does not have this problem because of course patent recordations are free of charge!)  There is a complicated workaround that involves saving the submission and taking off your shoes and putting them back on again.  (Just kidding.)
  • Visibility of recently filed documents in IFW is nonexistent.  Newly filed documents are supposed to be visible within one hour.  We are pretty consistently seeing delays of 18 hours or more before a document is visible in IFW.  This is a Big Problem.
  • EFS-Web ack receipts and fee payment pages are flaky.  This happened to many cases filed December 22 and December 27.  Even now as of January 14, USPTO has not yet provided accurate ack receipts and fee payment pages.  This is happening again now on new EFS-Web filings as of January 13.  The short-term survival steps for customers include checking the “fees” tab in PAIR and looking up the transaction in Financial Profile.

USPTO site works best in modern web browsers?

Every fiftieth visit or so to the USPTO web site triggers a pop-up Customer Satisfaction Survey.   The survey asks things like “How likely are you to return to uspto.gov?” (question 16) and “Do you intend to contact the USPTO Customer Support Centers to get information that you couldn’t find on the USPTO website?”  (question 24.3)  I have encountered this survey many dozens of times in recent months.

Today the survey popped up again for me, and I filled it out.  The question that stuck in my mind the most today was this one:

The USPTO site works best in modern web browsers. Is there a barrier that prevents you from using the most up-to-date browsers?  (question 30)

The problem with this question is its false premise.  It’s just not true that the USPTO site works best in modern web browsers.  Here are two counterexamples:

  1. Private PAIR and EFS-Web don’t work in Chrome or Microsoft Edge.
  2. If you try to do a TEAS filing in Chrome, you will find that the editing buttons (buttons for italic and bold and indenting etc.) are missing.

USPTO ought to scrap the Entrust Java applet that it uses in PAIR and EFS-Web, as I blogged in May of 2014.

USPTO does the right thing on trademark fees relating to the outage

On December 24 I blogged about things the USPTO needs to do to remediate the problems that flowed from the massive USPTO system outage December 22-27.  I wrote:

The TEAS-Plus system imposes a $50 per trademark class penalty on any filer of a “Plus” or “RF” (reduced fee) application who files a response by means other than e-filing.  USPTO needs to not impose that penalty on those who responded to a Plus or RF office action by means other than e-filing during this system crash time.

I am delighted to be able to report that now, December 31, the USPTO has addressed this problem.   Continue reading “USPTO does the right thing on trademark fees relating to the outage”

USPTO says a little more about the cause of the system crashes

Here is a statement dated December 24.  You can see the original here.

Statement of USPTO Acting Chief Communications Officer Patrick Ross

On Tuesday night, December 22, a major power disruption to the USPTO’s data center resulted in the shutdown of our public filing, searching, and payment systems, as well as the core systems our patent and trademark examiners use. Since then, dedicated teams have been working around the clock with our service providers to assess the situation and safely stabilize and restore those systems. Repair estimates remain the same—that the USPTO will be impacted at least through December 25.

Power that comes into the USPTO’s main building feeds two power filtration systems that provide steady, “filtered” power so systems don’t suffer from damaging surges or drops in power supply. A malfunction in the power supply lines feeding these two systems caused significant damage to both systems. This is what we believe caused our systems to go down on Tuesday night.

Because of their size, these large and highly complex power filtration systems cannot be easily replaced. We are working with service providers to obtain a source of uninterrupted conditioned power to the data center as soon as possible.

The USPTO will continue to provide updates, such as yesterday’s announcement of our filing deadline flexibility, through our systems status webpage (www.uspto.gov/blog/ebiz/) and Facebook account (www.facebook.com/uspto.gov (link is external)). With that information, users can make informed decisions about how best to allocate their own time and efforts while the problem is being addressed.

Our IP system is vital to our 21st century knowledge economy. Therefore, having timely and efficient public access to all of our agency’s filing, searching, and payment systems is also vital. The USPTO is mindful of our customer’s needs and appreciates the continuing patience.

So let’s try to put this into plain language.  Some years ago, USPTO spent oodles of money installing redundant “filtration systems” that are intended to protect USPTO’s e-commerce servers from problems with the electricity provided by the electric company.  On December 22, a problem happened with the electricity provided by the telephone company.  Every one of USPTO’s e-commerce servers promptly crashed.  I can’t quite put my finger on what sounds wrong about that.

 

It is now December 25.  About ¾ of USPTO’s e-commerce servers (the least mission-critical servers) are now back online.  So clearly somebody has figured out how to get power reconnected to servers.  Yet, though somebody has figured out how to get power reconnected to ¾ of the servers, still the EFS-Web and TEAS and IFW servers are broken.

The statement is not as clear as it might be, but I guess the situation is that the power that has been connected to the non-mission-critical servers is power that cannot be said to be “uninterrupted conditioned power”.  And until USPTO is able to restore “uninterrupted conditioned power”, USPTO is nervous about flipping the power switches to turn the mission-critical servers (such as EFS-Web and TEAS and IFW) back on.

Too bad that USPTO had not followed suggestions from years ago to move the “contingency” EFS-Web server to a geographically diverse location.

Anyway, “uninterrupted conditioned power” is actually quite easy to get.  USPTO could go on Amazon and place orders for two or three dozen of the biggest UPSs and they would be delivered the next day.  Or USPTO could dispatch employees to stop by all of the nearby Best Buy stores and buy all of the big UPSs.

Two or three dozen big UPSs would be more than enough to power the USPTO mission-critical systems.

USPTO current system status update

Clicking around in various USPTO e-commerce systems, I see no progress from yesterday.

  • IFW is still broken.
  • EFS-Web is still broken, both the main server and the contingency server.
  • TEAS is still broken.
  • ESTTA is still broken.

If you see progress with any of the systems, please post a comment here.  Thanks.

USPTO “deeming” several days to be federal holidays

Every external-facing system at the USPTO crashed two days ago on December 22, 2015.  As of today, December 24, most of the systems are still broken.  (In another blog post I review the status of the various systems up to the present time.  I also describe the administrative steps the USPTO still needs to do to remediate the crash.  I also discuss the redundancy measures that USPTO should have taken years ago but did not do, and now needs urgently to do.)

In the past, when a USPTO e-filing system failed, the rather brusque advice to the would-be filer of a patent application was that the customer could go to the post office instead of e-filing.  The customer was further told that the $400 penalty for failing to e-file would not be waived.  Translated into plain language, the would-be filer of a patent application was being told to pound sand.

In the aftermath of the May 14, 2014 massive crash, in which both EFS-Web servers crashed for some eighteen hours, thousands of customers who went to the post office were dinged with the $400 penalty.  We at Oppedahl Patent Law Firm LLC were dinged for that penalty for the one urgent patent application that we filed at the post office on the evening of May 14.  Pound sand indeed.

The most recent system crash that knocked out both of the EFS-Web servers (the main one and the “contingency” server that USPTO promises will always be working even if the main one crashes) happened on the afternoon of Tuesday, December 22, 2015.  Just over twenty-four hours later, after the close of business on Wednesday, December 23, 2015, the USPTO made an announcement that was (I expect) intended to be much more customer-friendly than the previous “pound sand” policy.  Here is what the USPTO announced yesterday evening:

In light of this emergency situation, the USPTO will consider each day from Tuesday, December 22, 2015, through Thursday, December 24, 2015, to be a “Federal holiday within the District of Columbia” in accordance with the description and regulations in this official notice posted here: https://www.uspto.gov/blog/ebiz/.

At first blush, this looks like a really smart and customer-friendly way to address the massive server crash.  The practical consequence, as I blogged yesterday, was that filers would get a free pass on anything that needed to be filed on the 22nd or 23rd or 24th, and anything that was due to be filed that day (or on the 25th or 26th or 27th) could be postponed until the 28th.  Nobody would have to scramble around trying to find a post office that was open late.  Nobody would have to pay the $400 penalty for failing to e-file.  The problem had been remediated.

But several alert members of the patent practitioner listserv clued me in that I was wrong to think that this action by the USPTO would remediate the problem.  Mere minutes after USPTO’s announcement that it would “deem” these three days to be federal holidays in the District of Columbia, alert list member David Boundy wrote:

Does the statute give the PTO authority to “consider” a day to be a holiday?  No.   That declaration has to come from either the President or Congress.

35 U.S.C. § 21(a) gives the Director the authority to “consider” a paper to be timely filed if it is timely mailed, but § 21(b) on holidays has no such grant of authority.

Maybe the PTO can “consider” papers that are actually filed late to be timely, but I don’t know where a court would find similar authority when an issued patent is tested.  The PTO has the authority to waive regulations (and thus can allow extension fees to be tolled for two days), but they don’t have the authority to define “holiday” for purposes of statute.

This sure looks to me like the PTO taking a bad situation and making it worse — give a promise that they can’t deliver on, and invite detrimental reliance.

(What?  You don’t belong to the the patent practitioner listserv?  Time to join!)

USPTO is going to have to go to the Hill to get a special bill passed, deeming December 22-24 to have been a federal holiday in the District of Columbia at least for the purposes of the USPTO.  If USPTO fails to do this, there will be later litigations in which infringers argue (and might well successfully argue) that the USPTO only had the power to waive rules, and did not have the power to waive the statute.

While the USPTO is visiting at the Hill asking for a special bill to fix this December 22-24 problem retroactively, USPTO might as well ask that Congress undo the $400 penalty for failing to e-file that came into effect with the America Invents Act.  Or at least ask that Congress give the USPTO the power to waive that penalty when needed.