MasterObjects, Inc. v. Google, Inc.

Filing 157

ORDER by Judge Hamilton denying 140 Motion for Partial Summary Judgment; denying 149 Administrative Motion to File Under Seal (pjhlc2, COURT STAFF) (Filed on 6/11/2013)

1
2
3

UNITED STATES DISTRICT COURT

4

NORTHERN DISTRICT OF CALIFORNIA

5
6
7

MASTEROBJECTS, INC.,
Plaintiff,

8

GOOGLE, INC.,

11
For the Northern District of California

v.

10

United States District Court

9

No. C 11-1054 PJH
ORDER DENYING MOTION FOR
PARTIAL SUMMARY JUDGMENT

Defendant.
_______________________________/

12
13

Plaintiff’s motion for partial summary judgment came on for hearing before this court

14

on June 5, 2013. Plaintiff MasterObjects, Inc. (“plaintiff” or “MasterObjects”) appeared

15

through its counsel, Darrell Atkinson. Defendant Google Inc. (“defendant” or “Google”)

16

appeared through its counsel, Joseph Lee. Having read the papers filed in conjunction with

17

the motion and carefully considered the arguments and the relevant legal authority, and

18

good cause appearing, the court hereby DENIES plaintiff’s motion as follows.

19

MasterObjects seeks an order that Google is judicially estopped from making certain

20

invalidity arguments regarding one prior art reference - namely, U.S. Patent No. 6,704,727

21

(referred to as “Kravets”). Specifically, MasterObjects argues that Google is precluded

22

from arguing that Kravets (1) anticipates retrieving search results for predicted queries, and

23

(2) anticipates a server-side cache containing prior queries and results thereto.

24

MasterObjects points to Google’s statements during prosecution of its own patents (which

25

are not at issue in this action), and argues that Google should be precluded from taking

26

inconsistent positions in this case.

27
28

MasterObjects is correct about the general principle that Google should not be
permitted to make statements in this case that are inconsistent with its statements to the

1

U.S. Patent and Trademark Office (“PTO”). As MasterObjects notes, judicial estoppel is an

2

equitable doctrine that precludes a party from gaining an advantage by asserting one

3

position, and then later taking to their benefit a clearly inconsistent position. See Rissetto

4

v. Plumbers & Steamfitters Local 343, 94 F.3d 597, 600-601 (9th Cir.1996). Judicial

5

estoppel applies if the prior proceeding was “quasi-judicial” in nature. Id. at 604. Even

6

though plaintiff has not cited authority applying judicial estoppel based on statements made

7

to the PTO, it has cited authority showing that courts (including the Ninth Circuit) have

8

characterized PTO proceedings as “quasi-judicial.” See, e.g., Chamberlain v. Isen, 779

9

F.2d 522, 524 (9th Cir. 1985) (“PTO employees perform a ‘quasi-judicial’ function in

11
For the Northern District of California

United States District Court

10

examining patent applications.”).
As an initial matter, MasterObjects has not yet identified any statements by Google

12

in this case that are “clearly inconsistent” with its statements to the PTO. Instead,

13

MasterObjects’ motion is based on speculation about positions that Google may potentially

14

take later in the case. While Google has served invalidity contentions identifying Kravets

15

as an invalidating prior art reference, it has not made any statements regarding Kravets in

16

front of this court. And to the extent that MasterObjects seeks a prophylactic order against

17

future possible inconsistent statements by Google, the court finds that plaintiff has not met

18

its burden of showing that there is “no genuine issue as to any material fact” as to the

19

estoppel effect of Google’s previous statements to the PTO. Fed. R. Civ. P. 56(a).

20

First, MasterObjects argues that Google should be estopped from arguing that

21

Kravets anticipates “retrieving search results for predicted queries.” In support of its

22

argument, MasterObjects cites to a statement by Google, made during the prosecution of

23

its own patents, that Kravets (in view of another prior art reference, referred to as

24

“Monteverde”) “does not include obtaining search results for predicted query completions.”

25

Dkt. 141, Ex. B at 15. The key dispute here centers around what Google meant by “search

26

results” in that statement, and whether it conflicts with Google’s position in this case. In

27

this case, Google’s position is that the term “search results,” as used in the MasterObjects

28

patents, refers only to the predicted search queries. That is, if a user were to type in the
2

1

letters “M-A-D” as part of a search query, the computer would retrieve a set of predicted full

2

search queries, such as “Mad Men” or “Madison Square Garden.” However, before the

3

PTO, Google used the term “search results” to refer to something different. Google

4

explained to the PTO that Kravets did disclose the prediction of full search queries based

5

on partial search queries, but did not disclose the retrieval of actual web content responsive

6

to those predicted search queries. Thus, in arguing to the PTO that Kravets did not

7

disclose “retrieving search results,” Google was defining “search results” as the actual web

8

content (as opposed to the predicted queries). Google thus argues that any perceived

9

inconsistency is explained by the different possible meanings of “search results.” In other
words, if “search results” refers only to the predicted search queries, then Kravets does

11
For the Northern District of California

United States District Court

10

disclose “retrieving search results.” If “search results” refers to the actual web content

12

responsive to those queries, then Kravets does not disclose “retrieving search results.”

13

The court agrees that the term “search results” could have a different meaning in

14

this case, in the context of the patents-in-suit, than it had during prosecution of Google’s

15

patents. The court further notes that the term “search results” was not submitted for

16

construction in this case. For these reasons, the court finds that MasterObjects cannot

17

establish that there is “no genuine issue of material fact” as to the estoppel effect of

18

Google’s statements regarding Kravets’ disclosure of “retrieving search results for predicted

19

queries.”

20

Second, MasterObjects argues that Google should be estopped from arguing that

21

Kravets anticipates “a server-side cache containing prior queries and results thereto.”

22

MasterObjects’ brief is not clear in identifying the specific Google statements that support

23

this estoppel argument, but it appears that MasterObjects’ argument is based on Google’s

24

statements that “Kravets in view of Monteverde does not expressly disclose wherein

25

responding to receiving the portion of the search query further comprise[s] caching the

26

search results” and that “the existence of a cache at the server in Kravets does not teach

27

using a cache for predicted search results.” Dkt. 141, Ex. B at 12, 13. Here, again, there is

28

some confusion regarding the use of the term “search results.” During prosecution of its
3

1

patents, Google pointed out the different types of “search results” that could be stored in a

2

cache:

3
4
5
6
7
8
9

Id. at 12 (emphasis in original).
Google later explained that the “limited discussion of caching data in Kravets does

11
For the Northern District of California

United States District Court

10

Applicants disagree that caching of search results as claimed here was
‘commonly used’ at the time of Kravets and Monteverde. In this regard,
applicants note a key difference between caching of data that has already
been retrieved and used versus retrieving into cache memory for potential
future use (prefetching). For example, if one user issues a query for ‘Michael
Jackson,’ the query server retrieves the search results for that search query
and caches the search results so that the search results will be available
more quickly for the next user who searches for ‘Michael Jackson.’ While this
form of caching may be fairly common, caching of prefetched search results
for possible future queries appears to have been unknown prior to the present
application.

not constitute teaching of the general concept of prefetching search results for predicted

12

queries.” Id. at 13. Based on these statements, it appears that Google was willing to

13

concede that Kravets made some disclosure of a server-side cache. However, Google

14

drew a distinction between a server-side cache that stored search results (i.e., web

15

content) for search queries that the user had already run, versus a server-side cache that

16

stored search results for search queries that the user may run in the future. Google argued

17

that, even if Kravets disclosed the former, it did not disclose the latter. MasterObjects’

18

requested order, which refers only to “a server-side cache containing prior queries and

19

results thereto,” would erase the distinction between these two types of server-side

20

caches. As before, it is not clear that the term “search results” is used the same way in this

21

case than it was in Google’s PTO proceedings. Before the PTO, Google used the term

22

“search results” to refer only to the “prefetched” web content, responsive to search queries

23

that had not yet been run by the user. In this case, Google argues that “the data to be

24

cached in the patents-in-suit are ‘query strings previously communicated from the clients,

25

or content results previously returned from the server.’” Dkt. 150 at 8 (emphasis in

26

original). Because of these different uses of the term “search results,” MasterObjects

27

cannot establish that there is “no genuine issue of material fact” as to the estoppel effect of

28

Google’s statements regarding Kravets’ disclosure of “a server-side cache containing prior
4

1
2

queries and results thereto.”
Thus, while MasterObjects has identified past statements by Google that could be

3

relevant to the present case, the court finds that MasterObjects’ motion is premature as

4

brought. In prosecuting its own patents, Google took the position that Kravets did not

5

disclose the retrieval, or the server-side caching, of web content responsive to predicted

6

search queries. So far, Google has not taken an inconsistent position in this case, nor has

7

MasterObjects shown that Google’s previous statements are directly applicable to this

8

case. MasterObjects’ motion for partial summary judgment is DENIED.

9

Google has also filed a motion to seal exhibit 11 of its supporting declaration. As the
court stated at the hearing, Google did not narrowly tailor its sealing request to cover only

11
For the Northern District of California

United States District Court

10

sealable material, and the motion to seal is thus DENIED. Moreover, as the exhibit was not

12

relied on by the court in ruling on this motion, a properly redacted version need not be filed.

13
14
IT IS SO ORDERED.
15
Dated: June 11, 2013
16

______________________________
PHYLLIS J. HAMILTON
United States District Judge

17
18
19
20
21
22
23
24
25
26
27
28
5