decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Oracle is not Happy; Asks Judge to Reconsider Order Reducing Claims
Monday, May 09 2011 @ 03:21 PM EDT

The parties have each responded to the judge's order reducing the number of Oracle's claims in Oracle v. Google from 132 to 3. And each has provided requested input to the judge on his tentative order on claim construction. If you recall, the judge asked for their input.

Here is Oracle's response to the order reducing the claims. After a respectful introduction acknowledging the Hon. William Alsup's "experience with complex trials", Oracle says it thinks he needs to modify the order:

The Court’s proposal to limit Oracle to only three asserted claims, however, will prejudice Oracle in the upcoming trial. That prejudice will be seen in both Oracle’s damages and liability case. Moreover, the Court’s requirement that Oracle surrender untried claims will deny Oracle due process and its right to a jury trial. The Court’s proposal, moreover, will place additional pressure on motions for summary judgment. Oracle recommends that the Court decide the number of claims to be tried closer to trial.
When a lawyer tells a judge that his client will be "prejudiced" by an order, it's kind of fighting words. Not in a bad way, but that word has weight. It is a word that lets the judge know that the party believes an error has been made that is fundamental to a fair trial. Of course Google has a shorter response:
Google agrees with the Court’s three-step process in its entirety.
If Google had just written, "Yay!" it couldn't be more clear that Google is delighted with the order.

I think that Oracle has made some valid points, however, and I think the judge may well agree, and while he may not go all the way to Oracle's suggested numbers, I think he may modify his order somewhat. And Google makes some strong points regarding the reexamination of Oracle's patents. It seems Google has made some progress already at the USPTO.

Meanwhile, we can use this document to learn how Morrison & Foerster's Michael A. Jacobs, who signed it, deals with a situation where a judge has issued an order that the lawyer now hopes to persuade the judge to modify. Jacobs is a master at this sort of thing, so law students everywhere can learn a great deal from this skillful filing. The rest of us can just enjoy the display. I confess, I absolutely love watching this guy work.

Do you remember when IBM got hit with a discovery order [PDF] they thought was unfair in SCO v. IBM back in 2005? David Marriott of Cravath was able to get the judge to modify the order. So we have seen a talented lawyer do this once before. And it can work. Judges don't always see all the issues as clearly as the lawyers do, at the beginning of a trial especially. How could they? The lawyers have been thinking deeply about all the detailed aspects of the case for a while in a more focused way than the judge has yet done or ever will.

Judges are aware of that, by the way. That's why this judge asked the parties for their reactions to his tentative order on claims construction. He's open to hearing from them if they think he's missed something. And when the magistrate judge in the IBM case modified her order, she said frankly that there were things she had not considered when making her original order.

So Jacobs here offers the judge his counter proposal, mentioning details he thinks the judge didn't think about, and notice that his tone is reasonable, respectful, but rather clear as to why he believes the order went too far, the unfair results he anticipates if the order is not modified, how he would suggest it be modified, and finally what Oracle will have to do if there is no modification:

We understand the Court’s desire to limit each side to a manageable number of claims and prior art references. Oracle believes, however, that the number should be larger – three claims per patent. Just as important, the ultimate decision on the number of claims should be made closer to trial – after summary judgment and after the Court has heard from the parties on the distinctions among the remaining claims for trial, consistent with Katz. This added procedure would not add significant cost or time and would reduce the risk of error in depriving Oracle of its valuable rights.

The limitations should also be imposed after Google refines its invalidity defenses. Although the order imposes limits on Google’s triable prior art references, it imposes no limits on Google’s other invalidity defenses. This could result in considerable unfairness: Google can maintain a highly elastic defense strategy and present multiple invalidity defenses against Oracle’s excessively narrowed claim set target. Limits on Oracle’s triable claims should be accompanied by limits on Google’s triable defenses in toto, not merely those based on prior art.

We raise this issue now to prevent surprising the Court regarding the scope of these motions. These will be technical motions with technical evidence in the form of expert declarations and deposition testimony. They will be as brief as the content allows. But they will require time to resolve. We think it better for both the Court and the parties to balance summary judgment and trial, and not to impose such severe limits on trial presentation that summary judgment is artificially inflated.

If I were the judge, I wouldn't be moved by the part about Google's defenses. But did you see the threat of summary judgments up to the judge's eyeballs? That should do it. Kidding, sort of, but it's a way of saying to the judge that if his unfair order, as Oracle views it, stands, there have to be consequences, because Oracle's lawyers can't just let their client be prejudiced. They will have to do something to get Oracle a more fair playing field. And it strengthens Oracle's suggestion that the final number be decided by the judge closer to trial, after summary judgment.

We watched this judge in the Apple v. Psystar case, and he can't be bullied. He isn't a fan of large corporate law firm fancy dancing either. But that is exactly why Jacobs is the very best lawyer to approach him with this request. We never saw Jacobs in the SCO v. Novell litigation, where he represented Novell, do anything tricky or underhanded, did we? He never stretched the truth. He always showed respect not just to the judge's face but to the very concept of the rule of law, where lawyers fight hard on the issues but with dignity, honesty and a sense fair play. Jacobs is always pleasant in tone and manner. Despite all the tricks that others might have come up with, he steadfastly stayed true to his own values. And still he won, did he not?

If you think about it, those are very similar to the values I associate with the FOSS community, where programmers and projects compete on skill and merit, not with backstabbing or FUD or dirty anticompetitive tricks.

This is, after all, a case between two companies who each care about and benefit from Linux. The community does expect it to be possible to get into a dispute inside the family, so to speak, and still handle it fairly. If someone has made a mistake, they can correct it, make the other whole, and then get back to cooperating again. It's a community, and this litigation is like a pimple on its nose. Everyone, I think, would like it to be resolved in a way that distinguishes it from the mean, bare-knuckle viciousness of the proprietary software style. At least I continue to hope for that. As Jacobs has already demonstrated, you can do that and still prevail. Here are all the filings:

05/06/2011 - 132 - RESPONSE to re 128 Order Oracle's response to Court's Tentative Claim Construction Order and Request for Critique by Oracle America, Inc.. (Peters, Marc) (Filed on 5/6/2011) (Entered: 05/06/2011)

05/06/2011 - 133 - RESPONSE to re 131 Order Re Schedule for Narrowing Issues for Trial by Oracle America, Inc.. (Jacobs, Michael) (Filed on 5/6/2011) (Entered: 05/06/2011)

05/06/2011 - 134 - Statement in Response to the Court's Order Re Schedule For Narrowing Issues For Trial by Google Inc.. (Sabnis, Cheryl) (Filed on 5/6/2011) (Entered: 05/06/2011)

05/06/2011 - 135 - Statement on the Court's Tentative Claim Construction Order by Google Inc.. (Sabnis, Cheryl) (Filed on 5/6/2011) (Entered: 05/06/2011)

There are some details about the inter partes reexamination of Oracle's patents that Google initiated that I didn't know before and you might find interesting:
Responding (briefly) to the Court’s questions:

Only two patents are in inter partes reexamination, the '205 and '720 patents. The PTO disagreed with Google about six of the eight grounds Google asserted against the '205 patent and limited the scope of that reexamination accordingly. The PTO agreed with Google with respect to arguments made against the '720 patent and has issued rejections based on those arguments, to which Oracle will be responding shortly. The extent to which – several years from now – the final results in the reexamination could moot the need for a trial here on those patents depends, of course, on the outcome in reexamination. The remaining patents are subject to ex parte reexamination. According to current PTO statistics, the average number of months between an ex parte reexamination request and the issuance of a reexamination certificate is 31.8 months.

I don't know about you, but I read that to be saying that Google has made some progress with the PTO already. This issue may well tip things toward Google in significant ways, because no judge wants to have the financial burden and effort of a trial, only to discover that the patents aren't valid in the first place. On the other side, it's quite common to request reexaminations when being sued, and not all are successful, so he will have to balance that out. Judges didn't just fall off a turnip truck. Oracle is stressing the length of any delay, but Google is stressing how unfair or pointless it would be to award damages on patents that it believes will not survive the invalidity challenge. And this isn't coming up deep into the litigation but at the start.

Here's what Google tells the judge:

II. If Trial Were Postponed, To What Extent Would The Results Of The Inter Partes Reexaminations Possibly Moot Need For Trial

Postponing the trial until after the completion of the inter partes reexaminations would most likely moot the need for a trial. It is very unlikely that the presently asserted patent claims will survive the reexamination process. And, even in the unlikely event that claims were to survive the reexamination process in their current form, their scope would likely be diminished based on the argumentation and evidentiary support entered into the administrative record to gain their allowance, which are key considerations in interpreting claim scope. As a result of claim cancellation or amendment, Oracle will not be entitled to past damages, and ongoing damages will be limited by the limited remaining terms of most of the patents-in-suit. This may impact the value of the case to Oracle, which in turn may moot the need for a trial.

The probability of any asserted claims surviving unchanged is quite low, based on the most recent reexamination statics. Oracle has suggested that “some decisions will favor Oracle [and] some will favor Google.” However, the most recent U.S. Patent and Trademark Office (“PTO”) statistics show that claims are cancelled or amended in 88% of inter partes reexaminations and in 76% of ex parte reexaminations. Cancelled claims cannot be infringed and amended claims are subject to absolute and equitable intervening rights. 35 U.S.C. §§ 307(b), 252; Seattle Box Co., Inc. v. Indust. Crating & Packing, Inc., 731 F.2d 818, 830 (Fed. Cir. 1984). Based on these statistics, the outcome of the reexaminations is not simply an even coin-toss, as implied by Oracle, but is likely a narrowed claim scope. Unless Oracle includes only its narrowest claims in its final set of three asserted claims, it is highly probable that the claims selected will be cancelled or amended during the reexamination process. The claims subject to inter partes reexamination are even less likely to emerge unchanged. The statistics discussed above are available at the U.S. Patent and Trademark Office’s website under Reexamination Information, which is available at http://www.uspto.gov/patents/stats/ Reexamination_Information.jsp.

The Court is in the process of construing five of the many claim terms at issue in this case. The claim construction process relies heavily on the administrative record supporting the claims of the patents-in-suit. Yet, this record has been reopened and is subject to significant further development. Indeed, one week ago, Oracle asked for an extension of time to respond to a first office action in the reexamination of the ‘720 patent. Request for Extension of Time Under 37 C.F.R. § 1.956, In re Inter Parte Reexamination of Nedim Fresko, Control No. 95/001,560 (Apr. 29, 2011) (available at http://portal.uspto.gov/external/ portal/pair). Such an extension requires a showing of good cause, and Oracle argued that it would need time to prepare and submit evidence, possibly including testimonial evidence from the inventor, along with its arguments in support of the patentability of its claims. Id. at 3. This continuing development of the administrative record is highly material to the issues in this case, and will likely alter the bases for the parties’ arguments, including Oracle’s infringement theories in the present case, which would again moot the need for a trial.

Some additional statistics may be helpful to the Court on this point. Currently, the PTO is issuing first rejections on the merits of claims in about three months for inter partes reexaminations and in about six months for ex parte reexaminations. Because these patents are in litigation, Oracle will have limited ability to extend the time to respond to these office actions. As a result, it is highly likely that the administrative record for all of the patents-in-suit will be in flux by this summer, and certainly before trial. In addition, the PTO is currently issuing notices of intent to issue a reexamination certificate in just over 20 months for ex parte reexaminations and about 34 months for inter partes reexaminations. Such a notice is the effective end of substantive prosecution and is the earliest date that the parties can know with some certainty what claim scope, if any, will survive the reexamination proceeding.

As discussed above, cancelled claims cannot be infringed and past damages are eliminated for amended claims. 35 U.S.C. §§ 307(b), 252; Seattle Box Co., Inc. v. Indust. Crating & Packing, Inc., 731 F.2d 818, 830 (Fed. Cir. 1984). Ongoing damages may also be eliminated for products existing prior to the claim amendments under a theory of equitable intervening rights. Seattle Box, 731 F.2d at 830. All but one patent asserted by Oracle have limited lives, expiring within 6-7 years of today for the most part. As a result, the pending reexaminations may have a significant impact on the value of the case to Oracle and may well moot all claims of infringement against the accused instrumentalities, or dramatically impact the chance for settlement.

III. When Will the Ex Parte Reexaminations be Completed

The Court specifically inquired into the duration of the pending ex parte reexaminations. The average pendency of ex parte reexaminations is just over 30 months, which is about 6 months shorter than the average pendency of inter partes reexaminations. (This timeframe reflects additional administrative work after the notice of intent to issue a reexamination certificate discussed above.) Thus, by the time the two inter partes reexaminations complete, all of the ex parte reexaminations should have also completed. The overall pendency time for each ex parte reexamination may be longer if additional reexaminations are filed for those patents, e.g., by other entities.

You see how both sides presented their issues persuasively? Does that give you an idea of how hard it is to be a judge? It does me. Both sides make valid points, and yet he has to structure things so that a jury can understand everything and deal with it all. That's why Google's points about reexamination are so compelling. The judge has stated he wants the case reduced to a more manageable size. Why not let the USPTO prune the case, then? From Google's point of view, it makes perfect sense. But if you are Oracle, delay is the very last thing you want, as it gives Android more time to spread and take over the mobile world. Whether the judge is willing to wait as long as a reexam would require is unknown to me. We'll have to wait and see. But let's face it. You saw how long litigation can drag on in the SCO litigations, and judges there were willing to let the IBM case go first, knowing that it would require at least as long as a patent reexamination.

  


Oracle is not Happy; Asks Judge to Reconsider Order Reducing Claims | 83 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Corrections
Authored by: Cypher3c on Monday, May 09 2011 @ 03:25 PM EDT
Please post corrections here with correction in title, like this:

whta --> what

[ Reply to This | # ]

Newspicks
Authored by: Cypher3c on Monday, May 09 2011 @ 03:27 PM EDT
Please put name of article in title and use clicky linkeys...ahem, clicky links.

[ Reply to This | # ]

Off Topic
Authored by: Cypher3c on Monday, May 09 2011 @ 03:29 PM EDT
On topic posters will be forced to reconstruct SCO's arguments diagrammatically
and formally refute each one.

[ Reply to This | # ]

Comes
Authored by: Cypher3c on Monday, May 09 2011 @ 03:30 PM EDT
Comes goes here. Follow the prescribed format, and post 'em up here.

[ Reply to This | # ]

Delay, business vs law
Authored by: vb on Monday, May 09 2011 @ 04:23 PM EDT
Pj says that delay is the very last thing Oracle wants. What does that have to
do
with the law? Is the Judge obligated to help a business manage the marketplace

by considering lawsuit delays?

In the SCO case, we saw skillful lawsuit delays by SCO. They played the Judges

for the maximum marketplace manipulation. But that was an aberration, wasn't
it?

[ Reply to This | # ]

Dear Google
Authored by: BitOBear on Monday, May 09 2011 @ 04:28 PM EDT
Now is the time, and this may be the judge, for you to launch an assault against
software patents entirely.

A single device becoming all those separate "specific machines", and
Android inherently (along with any discrete operating system) making any device
a-priori a multi-purpose computer (e.g. _not_ a specific machine).

Patent bombardment by individuals not engaged with the target product, and cross
entity patent licences, as inherently indistinguishable from the abuses that
lead to anti-trust laws.

Gross harm to emerging technologies.

All of these are present in one case before one judge.

Yes, it would cost you your software patent portfolio should you succeed. But it
would cost all the other companies theirs as well, and you would never have to
fight this patent battle again.

It would also moot all those "non practicing entities" nipping at your
heels.

Seriously, this is the time, the place, and the product for you to craft an
assault on software patents entirely.

And your lawyers would get to set some mighty precedent.

Consider it, give it some thought, and then dive in and play the long game.

[ Reply to This | # ]

Patents broken.. waiting for IBM
Authored by: YurtGuppy on Monday, May 09 2011 @ 04:37 PM EDT

Reading the bit about how the judge went forward with IBM instead of waiting for
the patent system.

It seems to me that any system in which a reexamination will produce a change
75-80% of the time is an unreliable system and should not be depended on.

(but I could be misreading the implications of those 75-80% figures)

Let us imagine that you drive an old clunker auto that has a bad fuel gauge.
When you tap on the gauge, 75% of the time it moves to a substantially different
reading. Friend, that gauge is broken.




---
Life from inside the bowl.

[ Reply to This | # ]

Google's highly elastic defense strategy
Authored by: jbb on Monday, May 09 2011 @ 05:20 PM EDT
Jacobs said:
The limitations should also be imposed after Google refines its invalidity defenses. Although the order imposes limits on Google’s triable prior art references, it imposes no limits on Google’s other invalidity defenses. This could result in considerable unfairness: Google can maintain a highly elastic defense strategy and present multiple invalidity defenses against Oracle’s excessively narrowed claim set target.
This does not make sense to me. Why would it be unfair for Google to have a highly elastic defense strategy? Why would it be unfair for Google to present multiple invalidity defenses against Oracle's narrowed claims? If the defenses are limited before the claims are then the defense could be totally sandbagged by an unexpected claim.

ISTM this is the same game Oracle has been playing all along where they want Google to limit their defenses before Oracle specifies their claims. ISTM Oracle has been trying to make this extremely unfair from the get-go. I don't really understand why the judge proposed such a drastic reduction to Oracle's claims but I wonder if maybe he was just giving Oracle a taste of their own medicine.

---
[ ] Obey DRM Restrictions
[X] Ignore DRM Restrictions

[ Reply to This | # ]

Reexamination? Judge says, Do It Yourself!
Authored by: cpeterson on Monday, May 09 2011 @ 06:36 PM EDT
I think Oracle will probably not get what they are asking for on this. I think
there's a certain point the judge was trying to make, and Oracle - well, I doubt
they missed it, but they'd rather not acknowledge it.

Judge Alsup has been very openly asking both sides about the reexamination
process, and how it can trim the issues the court needs to address. (Or could,
if reexamination moved fast enough.) The point, however, is that there is not
any deep magic in the process of granting or reexamining a patent. A reasonable
person, or group of people, having familiarity with a particular patent,
legalese, patents in general, and the stack of prior art associated with a
particular patent, should be able to make a pretty shrewd estimate about how
that patent will fare under reexamination.

Oracle has those reasonable people. They work at a place called MoFo. They have
the expertise; and, if they're unsure of the prior art, I don't think Google
would hesitate an instant in providing it.

Mr. Jacobs might say, "Hey, re-exam isn't my job!"

Judge Alsup may counter, "No, Mike, that's *my* line."

[ Reply to This | # ]

ORACLE’S RESPONSE TO NARROWING ISSUES FOR TRIAL - "Slow Down, Judge!"
Authored by: webster on Monday, May 09 2011 @ 07:01 PM EDT

Judge Alsup has been around the block. There is a certain genius to his methods of dealing with slick, smart, a-league corporate litigants with the deepest pockets. These guys can go up to the Supreme Court twice and back. His judicious use of a draconian measure by limiting a response to another draconian measure forces the litigants and Mr. Jacobs to betray the truth: Delay. DM 2.3; 5.1.3 (2011).

  1. "Oracle recommends that the Court decide the number of claims to be tried closer to trial." p. 1. "Delay" that means. That is what "closer to trial" means. In any type of litigation it is better that delay or nothing happen rather than something bad happen. Cutting claims is bad. So to the extent of not cutting claims now, he joins Google in asking for delay, albeit not as much or for the same reasons.
  2. Why do Jacobs and Oracle want the Judge to delay cutting their claims? They present a grab bag of prejudices. There are five to be precise --prejudice to: 1) damages; 2) liability; 3) untried claims; 4) jury trial, and; 5) the Court's and parties' workloads.
  3. Oracle does not argue that damages from 123 claims is greater than three, but that is the message. They have seven patents. A compromise on one million dollars per claim is going to be more with 123 claims than with three with or without substance. "Oracle’s case is not based on multiple patent claims without meaningful differences between them; rather, each patent embodies significant inventive contributions and distinct innovations." p. 2. They write this with a straight face while telling the Judge elsewhere in this document how long it will take to re-examine their patents. These damage claims will have to be re-examined if they are limited, too, they say. So does Google. Delay.
  4. Limiting claims will also limit Oracles chances at establishing liability. They are being denied the shotgun approach. One hundred twenty-three bullets is better than three bullets. Without more claims, "The proposed restrictions would undermine Oracle’s ability to have a [not only] full and[but a] fair trial regarding Google’s extensive infringement of Oracle’s valuable intellectual property rights." p. 3. They mention the presumptive validity of their patents somewhere too. So they warn the Judge not to "wrest these valuable intellectual property rights from Oracle to the benefit of Google, the accused infringer, providing Google with a greater likelihood of prevailing on liability."
  5. Oracle throws some caselaw in to argue the prejudice they suffer from a lack of due process. They accuse the judge of not having gone through this process to winnow their claims to three. [But isn't that what is going on now?] They argue that their patents are not duplicative and glibly discuss some of them as if they understood them. The Judge did get Oracle to finally come up with a number, three claims per patent. p. 4, l. 10. Oracle notes the limits on prior art, but asks for limits on Google's defenses "in toto." p. 4. Be fair to them too. Mete out the limits fairly they say.
  6. Oracle did no specific pounding on their sacro-sanct right to a jury trial in the previous section. It is understood that limiting claims also limits jury considerations. As SCO appeal one illustrates, A judge does not take a jury trial away lightly. The Judge figures that a trial on the best claims should dispose of the matter. The rest can be adjusted in damages, appeals or settlement some day. He wants a manageable and meaningful trial. He knows a jury can't chew on 123 claims, maybe not even 21, but three he and they can manage.
  7. The final prejudice is a threat by Oracle on everyone's workload. They inform the Court that they will have to file Motions for Summary Judgment on every patent [and every claim] since they will not get their day in court before a jury. So they say "Wait, Judge, until Your Honor's decision on the Motions before your strike our claims. You haven't ruled already have you?" These motions will be a trial on paper with experts, depositions, exhibits, prior art... All unlimited! :0 Delay it must be. No gang of law clerks will grok this by November if it is all even ready then, and the new one(s) will need time. "We raise this issue now to prevent surprising the Court regarding the scope of these motions." p. 5. Delay or give Oracle its claims. This is what Oracle means by pressure on summary judgment. Jacobs and the Boies crew are all good scouts working for deep pockets. There is no one hand that can pull the plug.

The final item is the Patent Reexamination Proceedings. This screams out delay and informs the Court that every patent is contested and it will be years before they are all resolved. It makes the current posture of the case a waste of time and effort. Delay. However, some people, judges included, are of the opinion that the best way to expose a bad procedure or rule is to enforce it. PJ notes the RIM litigation when the patents changed after the trial and settlement which the judge chose to ignore. There is no urgency here. Both sides have billions. He ought to stay it like a bankruptcy judge.


~webster~

Tyrants live their delusions. Beware. Deal with the PIPE Fairy and you will sell your soul.



[ Reply to This | # ]

'720 Patent
Authored by: dio gratia on Monday, May 09 2011 @ 07:28 PM EDT

Oracle asked for an extension of time to respond to a first office action in the reexamination of the ‘720 patent. Request for Extension of Time Under 37 C.F.R. § 1.956, In re Inter Parte Reexamination of Nedim Fresko, Control No. 95/001,560 (Apr. 29, 2011)
I went and looked in PAIR for the control number, and after some difficulty gaining access due to system load found that Oracles request for an extension of time was rejected on the 6th of May.

Further the office action triggering the request was the rejection of claims 1-8, 10-17, 19-22, while claims 9 and 18 are not subject to reexamination.

Oracle has two months either from the 18th or the 27th of April to respond (the date of the letter or the date of certification of action, as a non-practitioner it isn't clear to me which).

The claims are those for which Google requested reexamination based on too narrow of references distinguishing claims from prior art which if expanded appears to teach the claims.

Personally as a person having ordinary skill in the art there appears to be little distinction other that copy-on-write in the patent (System and Method for Dynamic Preloading of Classes through Memory Space Cloning of a Master Runtime System Process, U.S. 7,426,720, Sep 16, 2008 (adjusted by 745 days)) from the use of dynamic libraries in common between processes. Google stuck to questions of patentability based on a copy-on-write process cloning mechanism revealed by correct examination of cited prior art and not obviousness, attacking instead usefulness of the combined fork() system call with copy-on-write as lacking innovation.

The Examiner found that it would have been obvious to one of ordinary skill in the art at the time the invention was made to modify Webb's teaching by adding a runtime environment to clone a parent memory space as a child runtime process responsive to a process requested and to execute the child runtime process as taught by Kuck. See Non-Final Rejection (Apr 27,2007) at 5 (attached as Exhibit 4). In response to these objections in conjunction with the Applicant's filing of a Request for Continued Examination, the Applicant added the copy-on-write limitation to all independent claims. (Page 13, In re Reexamination of: Fresko Patent No: 7,426,720, Request for INTER PARTES REEXAMINATION Under 37 C.F.R. § 1.902, Google Inc., March 1, 2011).
It seems that Google is attacking the pivotal means by which the patent was issued. The net result leaving it up to Oracle to prove non-obviousness and perhaps to demonstrate otherwise that their prosecution of the patent wasn't irregular.

I'm not a patent practitioner but overly narrow citations of prior art doesn't strike me as a winning strategy in proving claim validity. There were two patents cited as prior art 6,823,509 (Webb) and 2003/0088604 (Kuck) causing the claims to be narrowed. Also cited by reference Chapter 7 of M.J. Bach's "The Design of The Unix Operating System", which I happen to own a copy of, and which Google points out teaches copy-on-write in Chapter 9 (See 9.2.1, Data Structures for Demand Paging, the '720 patent is claiming something that happens automatically when the Copy On Write bit is set), which wasn't cited. I've owned my copy of Bach's book since 1990 and the '720 patent was filed December 22, 2003.

It appears to a non-practitioner that Oracle might have a hard time persevering.

[ Reply to This | # ]

Oracle is not Happy; LOL
Authored by: SilverWave on Tuesday, May 10 2011 @ 03:01 AM EDT
Well I'm not surprised ;-)

His response will be interesting.



---
RMS: The 4 Freedoms
0 run the program for any purpose
1 study the source code and change it
2 make copies and distribute them
3 publish modified versions

[ Reply to This | # ]

Google vs USPTO
Authored by: Anonymous on Tuesday, May 10 2011 @ 04:04 PM EDT
Perhaps Google will sue the USPTO, and we can finally knock
some sense into the patent system.

This will require a judgement at the supreme court, and
Google is one of few companies with the means to take it that
far.

[ Reply to This | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )