throbber
Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 1 of 20 PageID #: 5928
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`UNILOC 2017 LLC,
`
`
`Plaintiff,
`
`
`v.
`
`GOOGLE LLC,
`
`
`
`Defendant.
`
`
`
`Civil Action No. 2:18-cv-00553-JRG
`
`
`PATENT CASE
`
`JURY TRIAL DEMANDED
`
`
`OPENING CLAIM CONSTRUCTION BRIEF OF UNILOC 2017
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`James L. Etheridge
`Ryan S. Loveless
`Etheridge Law Group, PLLC
`2600 E. Southlake Blvd., Suite 120 / 324
`Southlake, TX 76092
`Tel.: (817) 470-7249
`Fax: (817) 887-5950
`
`
`Counsel for Plaintiff Uniloc 2017 LLC
`
`Page 1 of 20
`
`GOOGLE EXHIBIT 1004
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 2 of 20 PageID #: 5929
`
`TABLE OF CONTENTS
`
`I. BACKGROUND ......................................................................................................................... 1
`
`II. LEGAL PRINCIPLES ............................................................................................................... 1
`
`A.
`
`B.
`
`Claim Construction ................................................................................................. 1
`
`Departing from the Ordinary Meaning of a Claim Term ........................................ 4
`
`III. NO AGREED TERMS ............................................................................................................ 5
`
`IV. THE DISPUTED PATENT TERMS ....................................................................................... 5
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`9.
`
`“keyfact” (all claims) ........................................................................................ 6
`
`“keyword” (claim 6) ......................................................................................... 7
`
`“extracting keywords without part-of-speech ambiguity” (claim 6) ................ 8
`
`“keyfact extracting step for analyzing a document collection and a user
`query, and extracting keywords without part-of-speech ambiguity from
`said document collection and said user query, and respectively extracting
`keyfacts of said document collection and said user query from said
`keywords” (claim 6) .......................................................................................... 9
`
`“keyfact indexing step for calculating the frequency of said keyfacts of
`said document collection and generating a keyfact list of said document
`collection for a keyfact index structure” (claim 6) ......................................... 10
`
`“keyfact retrieving step for receiving said keyfact of said user query and
`said keyfacts of said document collection” (claim 6) ..................................... 11
`
`“keyfact retrieving step for . . . defining a keyfact retrieval model in
`consideration of weigh factors according to a keyfact pattern” (claim 6) ...... 11
`
`“keyfact retrieving step for . . . generating a retrieval result” (claim 6) ......... 11
`
`Order of steps of claim 6 of the ’908 patent (claim 6) .................................... 13
`
`10.
`
`Order of steps of claim 11 of the ’908 patent (claim 11) ................................ 13
`
`
`
`
`
`i
`
`Page 2 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 3 of 20 PageID #: 5930
`
`TABLE OF AUTHORITIES
`
`Cases
`
`3M Innovative Props. Co. v. Tredegar Corp.,
`725 F.3d 1315 (Fed. Cir. 2013) ........................................................................................ 4
`
`Alloc, Inc. v. Int’l Trade Comm’n,
`342 F.3d 1361 (Fed. Cir. 2003) .......................................................................................... 1
`
`Apple Inc. v. Motorola, Inc.,
`757 F.3d 1286 (Fed. Cir. 2014) .......................................................................................... 2
`
`Athletic Alternatives, Inc. v. Prince Mfg.,
`73 F.3d 1573 (Fed. Cir. 1996) .......................................................................................... 3
`
`Avid Tech., Inc. v. Harmonic, Inc.,
`812 F.3d 1040 (Fed. Cir. 2016) .......................................................................................... 4
`
`Azure Networks, LLC v. CSR PLC,
`771 F.3d 1336 (Fed. Cir. 2014) .......................................................................................... 1
`
`Bell Atl. Network Servs., Inc. v. Covad Commc’ns Group, Inc.,
`262 F.3d 1258 (Fed. Cir. 2001) .......................................................................................... 1
`
`C.R. Bard, Inc. v. U.S. Surgical Corp.,
`388 F.3d 858 (Fed. Cir. 2004) ....................................................................................... 1, 3
`
`Centricut, LLC v. Esab Grp., Inc.,
`390 F.3d 1361 (Fed. Cir. 2004)........................................................................................... 6
`
`Comark Commc’ns, Inc. v. Harris Corp.,
`156 F.3d 1182 (Fed. Cir. 1998) .......................................................................................... 2
`
`Constant v. Advanced Micro-Devices, Inc.,
`848 F.2d 1560 (Fed. Cir. 1988) ........................................................................................ 2
`
`Continental Paper Bag Co. v. Eastern Paper Bag,
`210 U.S. 405 (1908) ............................................................................................................ 2
`
`Cordis Corp. v. Boston Sci. Corp.,
`561 F.3d 1319 (Fed. Cir. 2009) .......................................................................................... 4
`
`Elcommerce.com, Inc. v. SAP AG,
`564 Fed. Appx 599 (Fed. Cir. Jun. 6, 2014) ....................................................................... 6
`
`Elcommerce.com, Inc. v. SAP AG,
`745 F.3d 490 (Fed. Cir. 2014)............................................................................................. 6
`
`GE Lighting Solutions, LLC v. AgiLight, Inc.,
`750 F.3d 1304 (Fed. Cir. 2014) .......................................................................................... 4
`
`ii
`
`Page 3 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 4 of 20 PageID #: 5931
`
`Golden Bridge Tech., Inc. v. Apple Inc.,
`758 F.3d 1362 (Fed. Cir. 2014) .......................................................................................... 4
`
`In re Hiniker Co.,
`150 F.3d 1362 (Fed. Cir. 1998).......................................................................................... 2
`
`Innova/Pure Water Inc. v. Safari Water Filtration Sys., Inc.,
`381 F.3d 1111 (Fed. Cir. 2004) .......................................................................................... 1
`
`Interactive Gift Express, Inc. v. Compuserve Inc.,
`256 F.3d 1323 (Fed. Cir. 2001)......................................................................................... 13
`
`Liebel-Flarsheim Co. v. Medrad, Inc.,
`358 F.3d 898 (Fed. Cir. 2004)............................................................................................. 2
`
`Markman v. Westview Instruments, Inc.,
`52 F.3d 967 (Fed. Cir. 1995) (en banc) .............................................................................. 2
`
`Mobile Telecommunications Techs., LLC v. Sprint Nextel Corp.,
`2014 WL 10726788 (E.D. Tex. May 2, 2014) .................................................................... 6
`
`Nautilus, Inc. v. Biosig Instruments, Inc.,
`572 U.S. 898 (2014) ............................................................................................................ 6
`
`On Demand Mach. Corp. v. Ingram Indus., Inc.,
`442 F.3d 1331 (Fed. Cir. 2006) ......................................................................................... 5
`
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005) (en banc) ................................................................. 1, 2, 3
`
`Renishaw PLC v. Marposs Societa’ per Azioni,
`158 F.3d 1243 (Fed. Cir. 1998) ....................................................................................... 2, 4
`
`Schumer v. Lab. Computer Sys., Inc.,
`308 F.3d 1304 (Fed. Cir. 2002)........................................................................................... 7
`
`Seal-Flex, Inc. v. Athletic Track and Court Const.,
`172 F.3d 836 (Fed. Cir. 1999)................................................................................. 9, 10, 12
`
`Sonix Tech. Co. v. Publ’ns Int’l, Ltd.,
`844 F.3d 1370 (Fed. Cir. 2017)........................................................................................... 7
`
`Teleflex, Inc. v. Ficosa N. Am. Corp.,
`299 F.3d 1313 (Fed. Cir. 2002) ........................................................................................ 2
`
`Teva Pharm. USA, Inc. v. Sandoz, Inc.,
`135 S. Ct. 831 (2015) .......................................................................................................... 3
`
`Thorner v. Sony Computer Entm’t Am. LLC,
`669 F.3d 1362 (Fed. Cir. 2012) ......................................................................................... 4
`
`Trs. of Columbia Univ. v. Symantec Corp.,
`
`iii
`
`Page 4 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 5 of 20 PageID #: 5932
`
`811 F.3d 1359 (Fed. Cir. 2016) .......................................................................................... 5
`
`Vitronics Corp. v. Conceptronic, Inc.,
`90 F.3d 1576 (Fed. Cir. 1996) ............................................................................................ 2
`
`Statutes
`
`35 U.S.C. § 112 ...................................................................................................................... passim
`
`35 U.S.C. § 112(f) ......................................................................................................... 9, 10, 11, 12
`
`
`
`
`
`
`
`iv
`
`Page 5 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 6 of 20 PageID #: 5933
`
`I. BACKGROUND
`
`U.S. Patent No. 6,366,908 (“the ’908 patent”) describes keyfact-based search techniques.
`
`Words in a document of a document collection (or words in a search query) can be analyzed to
`
`extract keywords. ’908 patent, 5:19-6:4, Fig. 3, Abstract. Keyfacts can then be extracted from
`
`the keywords. ’908 patent, 6:5-55, Fig. 3, Abstract. Indexing of the document collection can
`
`result in a list of keyfacts for a document and statistics regarding those keyfacts. ’908 patent,
`
`4:66-5:6, Fig. 4, Abstract. Queries can be parsed for keyfacts and information can be retrieved
`
`from the document collection based on keyfacts. ’908 patent, 7:36-8:24, Fig. 5, Abstract.
`
`A.
`
`Claim Construction
`
`II. LEGAL PRINCIPLES
`
`“It is a ‘bedrock principle’ of patent law that ‘the claims of a patent define the invention
`
`to which the patentee is entitled the right to exclude.’” Phillips v. AWH Corp., 415 F.3d 1303,
`
`1312 (Fed. Cir. 2005) (en banc) (quoting Innova/Pure Water Inc. v. Safari Water Filtration Sys.,
`
`Inc., 381 F.3d 1111, 1115 (Fed. Cir. 2004)). To determine the meaning of the claims, courts start
`
`by considering the intrinsic evidence. Id. at 1313; C.R. Bard, Inc. v. U.S. Surgical Corp., 388
`
`F.3d 858, 861 (Fed. Cir. 2004); Bell Atl. Network Servs., Inc. v. Covad Commc’ns Group, Inc.,
`
`262 F.3d 1258, 1267 (Fed. Cir. 2001). The intrinsic evidence includes the claims themselves, the
`
`specification, and the prosecution history. Phillips, 415 F.3d at 1314; C.R. Bard, Inc., 388 F.3d at
`
`861. The general rule—subject to certain specific exceptions discussed infra—is that each claim
`
`term is construed according to its ordinary and accustomed meaning as understood by one of
`
`ordinary skill in the art at the time of the invention in the context of the patent. Phillips, 415 F.3d
`
`at 1312–13; Alloc, Inc. v. Int’l Trade Comm’n, 342 F.3d 1361, 1368 (Fed. Cir. 2003); Azure
`
`Networks, LLC v. CSR PLC, 771 F.3d 1336, 1347 (Fed. Cir. 2014) (“There is a heavy presumption
`
`that claim terms carry their accustomed meaning in the relevant community at the relevant time.”)
`
`(vacated on other grounds).
`
`1
`
`Page 6 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 7 of 20 PageID #: 5934
`
`“The claim construction inquiry . . . begins and ends in all cases with the actual words of
`
`the claim.” Renishaw PLC v. Marposs Societa’ per Azioni, 158 F.3d 1243, 1248 (Fed. Cir. 1998).
`
`“[I]n all aspects of claim construction, ‘the name of the game is the claim.’” Apple Inc. v. Motorola,
`
`Inc., 757 F.3d 1286, 1298 (Fed. Cir. 2014) (quoting In re Hiniker Co., 150 F.3d 1362, 1369 (Fed.
`
`Cir. 1998)). First, a term’s context in the asserted claim can be instructive. Phillips, 415 F.3d at
`
`1314. Other asserted or unasserted claims can also aid in determining the claim’s meaning,
`
`because claim terms are typically used consistently throughout the patent. Id. Differences among
`
`the claim terms can also assist in understanding a term’s meaning. Id. For example, when a
`
`dependent claim adds a limitation to an independent claim, it is presumed that the independent
`
`claim does not include the limitation. Id. at 1314–15.
`
`“[C]laims ‘must be read in view of the specification, of which they are a part.’” Id. (quoting
`
`Markman v. Westview Instruments, Inc., 52 F.3d 967, 979 (Fed. Cir. 1995) (en banc)). “[T]he
`
`specification ‘is always highly relevant to the claim construction analysis. Usually, it is dispositive;
`
`it is the single best guide to the meaning of a disputed term.’” Id. (quoting Vitronics Corp. v.
`
`Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)); Teleflex, Inc. v. Ficosa N. Am. Corp., 299
`
`F.3d 1313, 1325 (Fed. Cir. 2002). But, “‘[a]lthough the specification may aid the court in
`
`interpreting the meaning of disputed claim language, particular embodiments and examples
`
`appearing in the specification will not generally be read into the claims.’” Comark Commc’ns, Inc.
`
`v. Harris Corp., 156 F.3d 1182, 1187 (Fed. Cir. 1998) (quoting Constant v. Advanced Micro-
`
`Devices, Inc., 848 F.2d 1560, 1571 (Fed. Cir. 1988)); see also Phillips, 415 F.3d at 1323. “[I]t
`
`is improper to read limitations from a preferred embodiment described in the specification—even if
`
`it is the only embodiment—into the claims absent a clear indication in the intrinsic record that the
`
`patentee intended the claims to be so limited.” Liebel-Flarsheim Co. v. Medrad, Inc., 358 F.3d 898,
`
`913 (Fed. Cir. 2004). Care must be taken to avoid limiting the claims to the embodiments described
`
`in the specification as it is the claims, not the specific that defines the scope of the patent right.
`
`Continental Paper Bag Co. v. Eastern Paper Bag, 210 U.S. 405, 419 (1908); see also Comark
`
`Communications, Inc. v. Harris Corp., 156 F.3d 1182 (Fed. Cir. 1998).
`
`2
`
`Page 7 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 8 of 20 PageID #: 5935
`
`The prosecution history is another tool to supply the proper context for claim construction
`
`because, like the specification, the prosecution history provides evidence of how the U.S. Patent
`
`and Trademark Office (“PTO”) and the inventor understood the patent. Phillips, 415 F.3d at 1317.
`
`However, “because the prosecution history represents an ongoing negotiation between the PTO
`
`and the applicant, rather than the final product of that negotiation, it often lacks the clarity of the
`
`specification and thus is less useful for claim construction purposes.” Id. at 1318; see also
`
`Athletic Alternatives, Inc. v. Prince Mfg., 73 F.3d 1573, 1580 (Fed. Cir. 1996) (ambiguous
`
`prosecution history may be “unhelpful as an interpretive resource”).
`
`Although extrinsic evidence can also be useful, it is “‘less significant than the intrinsic
`
`record in determining the legally operative meaning of claim language.’” Phillips, 415 F.3d at
`
`1317 (quoting C.R. Bard, Inc., 388 F.3d at 862). Technical dictionaries and treatises may help a
`
`court understand the underlying technology and the manner in which one skilled in the art might
`
`use claim terms, but technical dictionaries and treatises may provide definitions that are too
`
`broad or may not be indicative of how the term is used in the patent. Id. at 1318. Generally,
`
`extrinsic evidence is “less reliable than the patent and its prosecution history in determining how
`
`to read claim terms.” Id. The Supreme Court has explained the role of extrinsic evidence in claim
`
`construction:
`
`In some cases, however, the district court will need to look beyond the
`patent’s intrinsic evidence and to consult extrinsic evidence in order
`to understand, for example, the background science or the meaning of
`a term in the relevant art during the relevant time period. See, e.g.,
`Seymour v. Osborne, 11 Wall. 516, 546 (1871) (a patent may be “so
`interspersed with technical terms and terms of art that the testimony
`of scientific witnesses is indispensable to a correct understanding of
`its meaning”). In cases where those subsidiary facts are in dispute,
`courts will need to make subsidiary factual findings about that
`extrinsic evidence. These are the “evidentiary underpinnings” of claim
`construction that we discussed in Markman, and this subsidiary
`factfinding must be reviewed for clear error on appeal.
`
`Teva Pharm. USA, Inc. v. Sandoz, Inc., 135 S. Ct. 831, 41 (2015).
`
`3
`
`Page 8 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 9 of 20 PageID #: 5936
`
`B.
`
`Departing from the Ordinary Meaning of a Claim Term
`
`There are “only two exceptions to [the] general rule” that claim terms are construed
`
`according to their plain and ordinary meaning: “1) when a patentee sets out a definition and acts
`
`as his own lexicographer, or 2) when the patentee disavows the full scope of the claim term
`
`either in the specification or during prosecution.” Golden Bridge Tech., Inc. v. Apple Inc., 758
`
`F.3d 1362, 1365 (Fed. Cir. 2014) (quoting Thorner v. Sony Computer Entm’t Am. LLC, 669 F.3d
`
`1362, 1365 (Fed. Cir. 2012)); see also GE Lighting Solutions, LLC v. AgiLight, Inc., 750 F.3d
`
`1304, 1309 (Fed. Cir. 2014) (“[T]he specification and prosecution history only compel departure
`
`from the plain meaning in two instances: lexicography and disavowal.”). The standards for finding
`
`lexicography or disavowal are “exacting.” GE Lighting Solutions, 750 F.3d at 1309.
`
`To act as his own lexicographer, the patentee must “clearly set forth a definition of the
`
`disputed claim term,” and “clearly express an intent to define the term.” Id. (quoting Thorner,
`
`669 F.3d at 1365); see also Renishaw, 158 F.3d at 1249. The patentee’s lexicography must
`
`appear “with reasonable clarity, deliberateness, and precision.” Renishaw, 158 F.3d at 1249. To
`
`disavow or disclaim the full scope of a claim term, the patentee’s statements in the specification
`
`or prosecution history must amount to a “clear and unmistakable” surrender. Cordis Corp. v.
`
`Boston Sci. Corp., 561 F.3d 1319, 1329 (Fed. Cir. 2009); see also Thorner, 669 F.3d at 1366
`
`(“The patentee may demonstrate intent to deviate from the ordinary and accustomed meaning of
`
`a claim term by including in the specification expressions of manifest exclusion or restriction,
`
`representing a clear disavowal of claim scope.”) “Where an applicant’s statements are amenable
`
`to multiple reasonable interpretations, they cannot be deemed clear and unmistakable.” 3M
`
`Innovative Props. Co. v. Tredegar Corp., 725 F.3d 1315, 1326 (Fed. Cir. 2013); see also Avid
`
`Tech., Inc. v. Harmonic, Inc., 812 F.3d 1040, 1045 (Fed. Cir. 2016) (“When the prosecution history
`
`is used solely to support a conclusion of patentee disclaimer, the standard for justifying the
`
`conclusion is a high one.”).
`
`Although a statement of lexicography or disavowal must be exacting and clear, it need
`
`not be “explicit.” See Trs. of Columbia Univ. v. Symantec Corp., 811 F.3d 1359, 1364 (Fed. Cir.
`
`4
`
`Page 9 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 10 of 20 PageID #: 5937
`
`2016) (“a patent applicant need not expressly state ‘my invention does not include X’ to indicate
`
`his exclusion of X from the scope of his patent”). Lexicography or disavowal can be implied
`
`where, e.g., the patentee makes clear statements characterizing the scope and purpose of the
`
`invention. See On Demand Mach. Corp. v. Ingram Indus., Inc., 442 F.3d 1331, 1340 (Fed. Cir.
`
`2006) (“[W]hen the scope of the invention is clearly stated in the specification, and is described
`
`as the advantage and distinction of the invention, it is not necessary to disavow explicitly a
`
`different scope.”). Nonetheless, the plain meaning governs “[a]bsent implied or explicit
`
`lexicography or disavowal.” Trs. of Columbia Univ., 811 F.3d at 1364 n.2.
`
`III. NO AGREED TERMS
`
`Uniloc and Google have not agreed to constructions of any terms of the ’908 patent.
`
`IV. THE DISPUTED PATENT TERMS
`
`It is plaintiff’s contentions that the Markman claim construction process was created to
`
`resolve latent ambiguities in a claim, and to determine when principles of equity should foreclose a
`
`patentee from asserting a scope surrendered in the patent or the prosecution history. Claim
`
`construction was never intended to provide a mechanism by which an accused infringer can redefine
`
`the scope of the patent to create a basis to assert non-infringement. It is plaintiff’s view that re-
`
`definition of a claim term should be undertaken sparingly as even a good interpretation of an
`
`existing claim term can change the scope of the claim allowed by the Patent Office.
`
`Here, the parties dispute the meaning of 8 claim terms in the ’908 patent and dispute the
`
`order of steps in claims 6 and 11. As a general matter, Google’s proposed constructions
`
`improperly seek to incorporate limitations discussed in certain exemplary embodiments of the
`
`’908 patent’s specification. Google either does that directly, by seeking to graft elements from
`
`the specification into its constructions, or indirectly by seeking to interpret method claims as
`
`“step-plus-function” elements.
`
`
`
`5
`
`Page 10 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 11 of 20 PageID #: 5938
`
`IV. CONSTRUCTION OF DISPUTED TERMS
`
`1.
`
`“keyfact” (all claims)
`
`Uniloc’s Proposed Construction
`“fact contained in sentences”; not indefinite
`
`Defendant’s Proposed Construction
`Indefinite under 35 U.S.C. § 112(2)
`
`The ’908 patent describes a “keyfact-based” index and retrieval method. The ’908 patent
`
`explains what a keyfact is (e.g., 1:15-16), how it can be represented (e.g., 1:16-17), how a keyfact
`
`can be extracted (e.g., 5:15-18), how it can be used to retrieve documents (e.g., 5:7-14), and how
`
`it can be used to create an index (e.g., 6:58-64). See also ’908 patent, 1: 51-2:2, 2:10-3:36, 3:49-
`
`67, 4:22-5:19, 5 29-57, 6:5-7:45, 8:25-42. In fact, the ’908 patent plainly states: “A keyfact means
`
`an important fact contained in sentences which constitute a document,” ’908 patent, 1:15-16,
`
`which hews closely to Uniloc’s proposed construction.
`
`Google has effectively waived its alternate theory of indefiniteness by failing to preserve
`
`the right to rely on expert testimony in its Patent Rule 4-2 and 4-3 disclosures. The Supreme Court
`
`reiterated in Nautilus that “[d]efiniteness is measured from the viewpoint of a person skilled in
`
`[the] art at the time the patent was filed.” Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898,
`
`908 (2014). Here, Google has waived any reliance on any expert declaration or testimony to
`
`establish how the challenged claim terms would be understood by a person of ordinary skill in the
`
`art. Because attorney argument is not evidence, Google will not be able to meet its burden to prove
`
`indefiniteness by clear and convincing evidence. See Mobile Telecommunications Techs., LLC v.
`
`Sprint Nextel Corp., No. 2:12-CV-832-JRG-RSP, 2014 WL 10726788, at *29 (E.D. Tex. May 2,
`
`2014) (“Defendants have failed to present any evidence of the understanding of a person of
`
`ordinary skill in the art, such as through an expert declaration or expert testimony. Defendants
`
`have therefore failed to meet their burden of proving indefiniteness by clear and convincing
`
`evidence.”) (citing Elcommerce.com, Inc. v. SAP AG, 745 F.3d 490, 505-06 (Fed. Cir. 2014),
`
`vacated on other grounds (settlement), 564 Fed. Appx 599, 600 (Fed. Cir. Jun. 6, 2014)); see also
`
`Centricut, LLC v. Esab Grp., Inc., 390 F.3d 1361, 1370 (Fed. Cir. 2004) (noting that “‘typically’
`
`expert testimony will be necessary in cases involving complex technology.”) (quoting Schumer v.
`
`6
`
`Page 11 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 12 of 20 PageID #: 5939
`
`Lab. Computer Sys., Inc., 308 F.3d 1304, 1315 (Fed. Cir. 2002)); see also Sonix Tech. Co. v.
`
`Publ’ns Int’l, Ltd., 844 F.3d 1370, 1377 (Fed. Cir. 2017) (“Indefiniteness must be proven by clear
`
`and convincing evidence.”). Google thus cannot show that the claims do not “inform those skilled
`
`in the art about the scope of the invention with reasonable certainty” without evidence of how a
`
`person of ordinary skill in the art would understand the term.
`
`2.
`
`“keyword” (claim 6)
`
`Uniloc’s Proposed Construction
`Plain and ordinary meaning
`
`
`Defendant’s Proposed Construction
`“a noun expressed within a query used to retrieve
`documents”
`
`“Keyword” has a plain and ordinary meaning to a person of ordinary skill in the art.
`
`Consistent with Google’s extrinsic dictionaries provided with its Rule 4-2 statement, “keyword”
`
`has an understood meaning as a reference word. See, e.g., Ex. 2, The Computer Desktop
`
`Encyclopedia, (c. 1996) (defining “key word” as a “word used in a text search” or a “word in a
`
`text document that is used in an index to best describe the contents of the document.”). The term
`
`to be construed is “keyword,” not “keynoun,” and Google’s attempt to limit keywords of the ’908
`
`patent to nouns is unsupported by the plain language of the term.
`
`The ’908 patent’s specification also provides keywords other than nouns. It describes that
`
`a “sentence in the document is divided into words and morphological analysis is performed with
`
`dictionaries.” ’908 patent, 5:21-22. The dictionaries “include a noun dictionary, a verb dictionary,
`
`an adjective dictionary, an adverb dictionary, a preposition dictionary, a conjunction dictionary,
`
`and a stop-word lexicon.” ’908, 5:24-28. In fact, in the next disputed term, Google’s proposed
`
`construction requires “extracting keywords tagged with a single part-of-speech,” suggesting that
`
`different keywords can be different parts-of-speech, i.e. nouns and verbs, e.g. Moreover, the ’908
`
`patent criticizes keyword-based methods system using only nouns as keywords. ’908 patent, 1:19-
`
`26 (“the meaning of the document is not precisely represented and the representativeness of
`
`document expression is low because the document is represented by keywords, which are nouns”).
`
`7
`
`Page 12 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 13 of 20 PageID #: 5940
`
`Thus, there is no basis to limit a keyword in the context of the ’908 patent’s improvement to a
`
`“noun.”
`
`Google is also wrong to limit a keyword to a “query.” The ’908 patent analyzes words
`
`found in documents in a document collection (e.g., 5:15-18) as well as queries (e.g., 8:26-29).
`
`Claim 6, in fact, recites “extracting keywords … from said document collection and said user
`
`query.” (emphasis added). Accordingly, Google’s attempt to define a “keyword” as only applying
`
`to nouns “expressed within a query” should also fail.
`
`3.
`
`“extracting keywords without part-of-speech ambiguity” (claim 6)
`
`Uniloc’s Proposed Construction
`Plain and ordinary meaning
`
`
`Defendant’s Proposed Construction
`“Extracting keywords tagged with a single part-
`of-speech”
`
`Claim 6 of the ’908 patent requires “extracting keywords without part-of-speech
`
`ambiguity.” As discussed in the ’908 patent regarding a document in a document collection:
`
` A
`
` document is supplied at stage 31 and morphological analysis is
`performed at stage 32. A sentence in the document is divided into
`words and the morphological analysis is performed with dictionaries
`36 at stage 32. The morphological variation is considered in order
`to recover prototypes. The dictionaries 36 include a noun dictionary,
`a verb dictionary, an adjective dictionary, an adverb dictionary, a
`preposition dictionary, a conjunction dictionary, and a stop-word
`lexicon. In some cases, a part-of-speech of a word is determined by
`rules without dictionaries.
`
`’908 patent, 5:19-28. Thus, the “morphological analysis” described in the preferred embodiment
`
`analyzes the words of the document (or query) to resolve ambiguities in their part of speech. This
`
`can be done using a “part of speech tag in dictionaries” (5:29-30) or “a part-of-speech of a word
`
`is determined by rules without dictionaries” (5:27-28). Accordingly, the ’908 patent broadly
`
`teaches, in a manner consistent with the understanding of person of ordinary skill in the art, that
`
`the extraction of keywords resolves ambiguities in their part of speech. Nothing more is required
`
`by claim 6.
`
`Google’s proposed construction is unsupported and inconsistent with the ’908 patent. The
`
`words in a document found in a document collection or found in a query does not have tags, so
`
`8
`
`Page 13 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 14 of 20 PageID #: 5941
`
`requiring a document collection or query to have “keywords tagged with a single part-of-speech,”
`
`as suggested by Google finds no support in the ’908 patent. Further, while the specification does
`
`use tagging, there is no basis for requiring claim 6 to use tagging as part of the claimed
`
`“extracting.”
`
`4.
`
`“keyfact extracting step for analyzing a document collection and a user query,
`and extracting keywords without part-of-speech ambiguity from said
`document collection and said user query, and respectively extracting keyfacts
`of said document collection and said user query from said keywords” (claim 6)
`
`Uniloc’s Proposed Construction
`Not governed by 35 U.S.C. § 112(f); Plain
`and ordinary meaning
`
`Defendant’s Proposed Construction
`This limitation is subject to 35 U.S.C. § 112, ¶6.
`
`Function: analyzing a document collection and a
`user query, and extracting keywords without part-
`of-speech ambiguity from said document
`collection and said user query, and respectively
`extracting keyfacts of said document collection
`and said user query from said keywords
`
`Act: Acts specified at 5:20 to 6:55.
`
`Google errs by asking that the claimed “keyfact extracting step” be construed under 35
`
`U.S.C. § 112(f). While the claim element does use the phrase “step for,” the element then recites
`
`acts that perform keyfact extraction. “In general terms, the ‘underlying function’ of a method
`
`claim element corresponds to what that element ultimately accomplishes in relationship to what
`
`the other elements of the claim and the claim as a whole accomplish. ‘Acts,’ on the other hand,
`
`correspond to how the function is accomplished.” See Seal-Flex, Inc. v. Athletic Track and Court
`
`Const., 172 F.3d 836, 849-51 (Fed. Cir. 1999) (J. Rader, concurring). Where the claim element
`
`recites acts, 35 U.S.C. § 112(f) should not be applied.
`
`In the keyfact extracting step, the “what” aspect of the element is “analyzing a document
`
`collection and a user query,” and the element then recites the acts to perform such an analysis,
`
`including the acts of “extracting keywords…” and “extracting keyfacts…from said keywords.”
`
`Confirming that these elements are “acts,” Google’s passage of patent text describing “acts” (’908
`
`patent, 5:20-6:55) includes the act of extracting. For example, the specification describes at 6:8-
`
`9
`
`Page 14 of 20
`
`

`

`Case 2:18-cv-00553-JRG Document 128 Filed 01/09/20 Page 15 of 20 PageID #: 5942
`
`12: “the stage of keyfact pattern extraction 34 … extracts meaningful keyfact patterns necessary
`
`for keyfact generation.” Thus, as the element recites acts, 35 U.S.C. § 112(f) should not apply.
`
` Moreover, Google’s construction is fundamentally flawed as it merely recites the claim
`
`element verbatim and, thus, fails to identify any claimed “function.” Google also cites no specific
`
`act as corresponding to the “function,” and, instead, would require a jury to parse more than full
`
`column of patent text to identify “acts” contained therein, many of which do not perform the
`
`actions related to the language of the keyfact extraction step.
`
`5.
`
`“keyfact indexing step for calculating the frequency of said keyfacts of said
`document collection and gener

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket