throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`In Re:
`
`U.S. Patent 8,326,924
`
`Inventor: Harvey Lunenfeld
`
`Filed:
`
`August 1, 2012
`
`Issued:
`
`December 4, 2012
`
`:
`
`:
`
`:
`
`:
`
`
`
`
`
`CBM2014-00001
`
`Title:
`
`
`
`METASEARCH ENGINE FOR ORDERING AT LEAST ONE
`ITEM RETURNED IN SEARCH RESULTS USING AT LEAST
`ONE QUERY ON MULTIPLE UNIQUE HOSTS AND FOR
`DISPLAYING ASSOCIATED ADVERTISING
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`
`84447497.1
`
`
`
`

`
`
`
`I.
`
`II.
`
`TABLE OF CONTENTS
`
`Page
`
`INTRODUCTION ........................................................................................... 1
`
`THE ’924 PATENT IS DIRECTED AT A NOVEL, NON-OBVIOUS
`METHOD OF PERFORMING A METASEARCH ....................................... 2
`
`a.
`
`The Alleged Prior Art Asserted in the Petition. .................................... 7
`
`III. CLAIM CONSTRUCTION .......................................................................... 10
`
`a.
`
`b.
`
`Petitioners’ Proposed Constructions Are Fanciful and Not the
`Broadest Reasonable Interpretation. ................................................... 10
`
`Patent Owner’s Proposed Constructions ............................................. 11
`
`IV. THE ’924 PATENT IS NOT SUBJECT TO COVERED BUSINESS
`METHOD REVIEW ...................................................................................... 24
`
`a.
`
`b.
`
`c.
`
`The America Invents Act Limits CBM Review to a Narrow
`Range of Patents. ................................................................................. 25
`
`The Invention of the ’924 Patent Is Not a Method of “Performing
`Data Processing…of a Financial Product or Service.” ....................... 27
`
`The Invention of the ’924 Patent Is a “Patent[] for Technological
`Invention[].” ........................................................................................ 28
`
`V.
`
`PETITIONERS HAVE FAILED TO MEET THEIR BURDEN
`UNDER 35 U.S.C. § 101 ............................................................................... 28
`
`a.
`
`Analysis Under 35 U.S.C. § 101 Requires Examination of the
`Claims to Identify Meaningful Limitations That Demonstrate a
`Practical Application of an Abstract Idea. .......................................... 29
`
`i.
`
`ii.
`
`Petitioners Ignore the Claim Elements and the Meaningful
`Limitations in the Challenged ’924 Patent Claims. .................. 30
`
`The Advertising Portions of the Challenged Claims are
`Meaningful Limitations. ........................................................... 31
`
`84447497.1
`
`i
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`iii.
`
`The Challenged Claims as a Whole Recite a Specific
`Combination of Components That Interact in a Particular
`Way. .......................................................................................... 32
`
`b.
`
`The Claims of the ’924 Patent Satisfy the “Machine-Or-
`Transformation” Test Because the Data from the Results Is
`Transformed Into a Response. ............................................................. 35
`
`VI. THE LUNENFELD 2000 APPLICATION AND LUNENFELD PCT
`ARE NOT PRIOR ART TO THE ’924 PATENT AND THUS
`CANNOT RENDER THE CHALLENGED CLAIMS OBVIOUS
`UNDER 35 U.S.C. § 103 ............................................................................... 37
`
`a.
`
`b.
`
`c.
`
`d.
`
`There Is No Break in the Priority Chain. ............................................ 38
`
`The Lunenfeld 2000 Application’s Specification Clearly
`Supports All Challenged Claims of the ’924 Patent. .......................... 40
`
`The CIPs Merely Add Further Description and Detail to
`Elements Already Disclosed in the ’073 Patent. ................................. 60
`
`Petitioners Have Failed to Show That Any Challenged Claim of
`the ’924 Patent Is Rendered Obvious Over the Combination of
`Lunenfeld PCT and Lunenfeld 2000 Application in View of
`Mamma.Com ....................................................................................... 63
`
`VII. PETITIONERS HAVE FAILED TO MEET THEIR BURDEN TO
`SHOW OBVIOUSNESS. .............................................................................. 63
`
`a.
`
`b.
`
`c.
`
`Petitioners Provide No Explanation as to Why One of Skill
`Would Combine These References. .................................................... 64
`
`The References Do Not Teach “Metasearching” as Required by
`All of the Challenged Claims. ............................................................. 66
`
`The References Do Not Teach or Disclose “Incorporating the
`Received Search Results Into a Results List and Incorporating
`the Results List Into a Response” Limitation Found in Claims 2
`and 6. ................................................................................................... 68
`
`VIII. CONCLUSION .............................................................................................. 70
`
`
`
`
`
`ii
`
`

`
`
`
`TABLE OF AUTHORITIES
`
`Page
`
`Cases
`Apple, Inc. v. Sightsound Technologies, LLC,
`CBM2013-00019, Paper 17 (Oct. 8, 2013) ............................................. 26, 33, 34
`Bilski v. Kappos,
`130 S.Ct. 3218 (2010) ............................................................................. 29, 30, 35
`CLS Banking Int’l v. Alice Corp.,
`717 F.3d 1269 (Fed. Cir. 2013) ..................................................................... 29, 30
`Corley v. U.S.,
`556 U.S. 303 (2009) ............................................................................................. 26
`Diamond v. Chakrabarty,
`447 U.S. 303 (1980) ............................................................................................. 26
`Diamond v. Diehr,
`450 U.S. 175 (1981) ...................................................................................... 26, 30
`Griffin v. Oceanic Contractors, Inc.,
`458 U.S. 564 (1982) ............................................................................................. 25
`In re Am. Acad. of Sci. Tech. Ctr.,
`367 F.3d 1359 (Fed. Cir. 2004) ............................................................................ 10
`KSR Intern. Co. v. Teleflex Inc.,
`127 S.Ct. 1727 (2007) .......................................................................................... 70
`Locite Corp. v. Ultraseal Ltd.,
`781 F.2d 861 (Fed. Cir. 1985) .............................................................................. 66
`Mayo Collaborative Services v. Prometheus Labs., Inc.,
`132 S. Ct. 1289 (2012) .................................................................................. 29, 30
`Phillips v. AWH,
`415 F.3d 1303 (Fed. Cir. 2005) ............................................................................ 10
`PowerOasis, Inc. v. T-Mobile USA, Inc.,
`522 F.3d 1299 (Fed. Cir. 2008) ............................................................................ 60
`Research Corp. Tech., Inc. v. Microsoft Corp.,
`627 F.3d 859 (Fed. Cir. 2010) ....................................................................... 36, 37
`SiRF Tech., Inc. v. Int'l Trade Comm'n,
`601 F.3d 1319 (Fed. Cir. 2010) ............................................................................ 36
`
`84447497.1
`
`iii
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`Ultramercial, LLC, et al v. Hulu, Inc., et al,
`657 F.3d 1323 (Fed. Cir. 2011) ............................................................... 30, 33, 34
`Statutes
`35 U.S.C. § 101 ............................................................... 1, 28, 29, 33, 34, 35, 36, 37
`35 U.S.C. § 102 ........................................................................................................ 63
`35 U.S.C. § 103 ................................................................................................... 1, 37
`Other Authorities
`77 Fed. Reg. 48680 .................................................................................................. 10
`77 Fed. Reg. 48699-700 ........................................................................................... 10
`AIA § 18 ...................................................................................................... 24, 25, 28
`Rules
`37 C.F.R. § 42.300(b) .............................................................................................. 11
`37 C.F.R. § 42.304(a) ............................................................................................... 26
`37 C.F.R. § 42.64(b)(1)……………………………………………………………9
`
`
`
`
`
`iv
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`
`EXHIBITS
`
`
`2001
`2002
`
`U.S. Patent No. 6,789,073
`Excerpt from the prosecution of the Lunenfeld 2000 Application
`that resulted in U.S. Patent No. 6,789,073
`
`
`
`v
`
`

`
`
`
`I.
`
`INTRODUCTION
`
`Patent Owner requests that the Patent Trial and Appeal Board (the “Board”)
`
`deny Petitioners’ petition for covered business method (“CBM”) review of claims
`
`2, 6, and 8 of U.S. Patent No. 8,326,924 (the “’924 Patent”) under § 18 of the
`
`America Invents Act, Pub. L. No. 112-29, 125 Stat. 284 (2011) (“AIA”).1
`
`Petitioners have failed to show that the ’924 Patent is even subject to post-
`
`grant review under CBM. The invention of the ’924 Patent is not a financial
`
`product or service but is instead directed to a machine that implements a
`
`technological solution. See Part IV, infra. The claimed invention of the ’924 Patent
`
`is well outside the narrow subset of patents that Congress expressly allowed for
`
`CBM review.
`
`The Petition offers little substantive arguments to support the challenges
`
`raised. Recognizing various critical shortcomings in their position, Petitioners
`
`spend most of their 80 pages making incredible assertions about various
`
`descriptions of different aspects of inventions disclosed in the ’924 Patent, mostly
`
`taken out of context. These absurd assertions are readily dismissed as they provide
`
`1 Petitioners have agreed to limit the challenged claims in the Petition to only
`
`claims 2, 6, and 8. See Joint Motion to Narrow Petitioners’ Request for Post-Grant
`
`Review of U.S. Patent No. 8,326,924, CBM2014-0001, Paper 24, dated Dec. 27,
`
`2013.
`
`
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`no support for the grounds raised by Petitioners. When the facts actually relevant
`
`to the three grounds raised by Petitioners are critically analyzed, it becomes
`
`apparent that there is no support for the three grounds raised in the Petition.
`
`Petitioners have failed to meet their burden to show that any challenged
`
`claim of the ’924 Patent is more likely than not unpatentable under 35 U.S.C.
`
`§ 101. See Part V, infra. Petitioners have failed to show that the challenged claims
`
`of the ’924 Patent lack meaningful limitations that ensure the claims cover more
`
`than an abstract idea. Rather, Petitioners focus on various descriptions in the
`
`specification and ignore meaningful limitations in the ’924 Patent. Consideration
`
`of the claimed invention as a whole and the meaningful limitations in the claims
`
`shows that the claimed invention is directed at patent-eligible subject matter.
`
`Petitioners also have failed to meet their burden to show that any challenged
`
`claim of the ’924 Patent is more likely than not obvious under 35 U.S.C. § 103. See
`
`Parts VI & VII, infra. Petitioners do not even raise an argument that any alleged art
`
`anticipates the ’924 Patent. The first combination includes the Lunenfeld 2000
`
`Application, which resulted in the parent patent to the ’924 Patent, in combination
`
`with screen shots of a web site, Mamma.com—cobbled together from the Internet
`
`Archive’s “WayBack Machine.” This incredible assertion rests on the unfounded
`
`ground that the ’924 Patent is not entitled to claim priority back to the parent
`
`application. The simple facts demonstrate that chain of priority was never broken
`
`
`
`1
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`and the claims of the ’924 Patent are more than sufficiently supported by the
`
`specification in the parent application. Thus, this combination cannot render the
`
`challenged claims invalid.
`
`Petitioners’ second attempted combination relies on Mamma.com WayBack
`
`Machine screenshots grouped with a physics article search engine referred to as
`
`Knowledge Broker. With no substantive support for why one of skill would
`
`combine these references or how the combination allegedly teaches each element
`
`of the challenged claims, the Petition fails to show that it is more likely than not
`
`that the claims are obvious in view of this combination. In particular, the Petition
`
`brushes over several critical elements that are not disclosed in the references. This
`
`failure dooms the Petition. Thus, the Petition must be denied.
`
`II. THE ’924 PATENT IS DIRECTED AT A NOVEL, NON-OBVIOUS
`METHOD OF PERFORMING A METASEARCH
`
`On December 4, 2012, the United States Patent and Trademark Office issued
`
`United States Patent No. 8,326,924, entitled “Metasearch Engine for Ordering At
`
`Least One Item Returned in Search Results Using At Least One Query on Multiple
`
`Unique Hosts and For Displaying Associated Advertising.” Ex. 1001. The ’924
`
`Patent hails from a patent portfolio developed by the sole inventor, Harvey
`
`Lunenfeld, over more than a 10 year period. The ’924 Patent—including other
`
`patents in the portfolio—claims priority to the parent United States Patent
`
`
`
`2
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`Application No. 09/510,749 (the “’749 parent application”)2, which was filed with
`
`the United States Patent and Trademark Office on February 22, 2000 and issued as
`
`United States Patent No. 6,789,073 (the “’073 patent”). Ex. 2001. As noted in the
`
`’924 Patent, clients, servers, and client-server systems were known, but at the time
`
`of the invention, there was a need for client-server multitasking that allowed for
`
`information or service retrieval substantially simultaneously and on-the-fly. See,
`
`e.g., Ex. 1001, 2:7-14.
`
`To address this problem, Mr. Lunenfeld invented a client-server multitasking
`
`process capable of making multiple simultaneous searches, associating queries
`
`with the appropriate sources, incorporating associated advertisements, and capable
`
`of placing orders for items that were searched. The inventor initially described the
`
`claimed technology in terms of “client-server multitasking” in the ’749 parent
`
`application. In subsequent filings, the Examiner recommended that the technology
`
`be described in terms of “metasearching,” and Patent Owner adopted this
`
`recommendation.
`
`Patent Owner did not claim that “client-server multitasking” or
`
`“metasearching” was novel at the time of the invention. Rather, using ’924 Patent
`
`claim 2 as an example, the claimed invention is directed to a process for
`
`metasearching on the Internet, including a metasearch engine that receives an
`
`
`2 Petitioners refer to the ’749 parent application as the Lunenfeld 2000 Application.
`
`
`
`3
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`HTTP request to send at least one query to a plurality of unique hosts wherein the
`
`HTTP request from the client device is associated with at least one travel related
`
`item that may be ordered from a plurality of travel related items that may be
`
`ordered, including limitations such as associating targeted advertisements,
`
`receiving another HTTP request to place an order, and processing orders for travel
`
`related items:
`
`2. A process for metasearching on the Internet, wherein the steps of the
`
`process are performed by a metasearch engine executing on a hardware
`
`device, the process comprising the steps of:
`
`(a) receiving a Hypertext Transfer Protocol request from a client device for
`
`the metasearch engine to send at least one search query to a plurality of
`
`unique hosts that provide access to information to be searched, wherein
`
`the Hypertext Transfer Protocol request from the client device is
`
`associated with at least one travel related item that may be ordered from a
`
`plurality of travel related items that may be ordered;
`
`(b) sending the at least one search query to the plurality of unique hosts in
`
`response to the Hypertext Transfer Protocol request received from the
`
`client device;
`
`(c) receiving search results from the plurality of unique hosts in response to
`
`the at least one search query sent to the plurality of unique hosts;
`
`
`
`4
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`(d) incorporating the received search results into a results list and
`
`incorporating the results list into a response;
`
`(e) causing at least one advertisement associated with the at least one item
`
`that may be ordered to be displayed in the response;
`
`(f) communicating the response from the metasearch engine to the client
`
`device;
`
`(g) receiving another Hypertext Transfer Protocol request from the client
`
`device for placing an order for the at least one item;
`
`(h) processing the order.
`
`The specification provides extensive description and numerous illustrations
`
`of the claimed metasearching technology, including the complex process of
`
`sending at least one search query to a plurality of hosts, receiving search results
`
`from multiple sources, and incorporating results into a response. Figure 63, below,
`
`is an example of the illustrations and disclosures included in the ’924 Patent.
`
`
`
`5
`
`
`
`
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`
`
`
`Ex. 1001, Fig. 63.
`
`The ’924 Patent claims a specific machine, comprising a metasearch engine,
`
`that requires a computer and is programmed to have a specific function, structure,
`
`and operation. The invention of the ’924 Patent cannot function or operate without
`
`the metasearch engine programmed to perform as claimed in the ’924 Patent.
`
`In addition to the art submitted with the ’749 parent application and its
`
`progeny, the ’924 Patent was allowed over at least 114 pieces of art referenced on
`
`
`
`6
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`the face of the ’924 Patent. Notably, these references include work done by Dr.
`
`Etzioni, one of the experts who filed a declaration in support of the Petition.
`
`The Alleged Prior Art Asserted in the Petition.
`
`a.
`Petitioners are in the travel industry and arguably have the best access to
`
`prior art. But they have not presented the Board with any art that they allege
`
`anticipates. In litigation, Petitioners have produced over 40,000 pages of alleged
`
`prior art. In that context, they allege anticipation by at least two specific references
`
`they identified as “single-search services.” Petitioners did not present these
`
`references to the Board. From the perspective of Metasearch Systems, Petitioners
`
`are using CBM review to make their 101 and priority challenges, and are saving
`
`what they consider to be their best prior art for district court litigation. For the
`
`Board’s review, Petitioners only offer two non-anticipatory and disparate
`
`“references” that fail to disclose material elements of the challenged claims.
`
`The first reference cobbles together various webpage printouts from the
`
`“WayBack Machine” of a website called Mamma.com. Ex. 1005.3 The webpage
`
`3 Petitioners have not even attempted to meet their burden of proof to show that the
`
`various “WayBack Machine” screenshots are properly authenticated and can even
`
`be considered under the Federal Rules of Evidence. Petitioners merely attach a
`
`declaration from a paralegal that the paralegal navigated to a website and
`
`downloaded various screenshots and source pages, purportedly showing pages that
`
`
`
`7
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`printouts provide a general and superficial description of what the Mamma.com
`
`web site attempted to do. This promotional material simply describes Mamma.com
`
`as a search engine that “will query the top search engines on the web and create a
`
`virtual database.” Ex. 1005 at 3. And Ex. 1018 (apparently nothing more than the
`
`HTML code of the screen shots provided in Ex. 1005) provides no relevant
`
`information or support for Petitioners’ attempted combination. Mamma.com
`
`appears to be just a generic metasearch engine, like others in the art considered by
`
`the Examiner during examination of the ’924 Patent.
`
`The second set of references relate to Xerox’s Knowledge Broker system.
`
`Exs. 1006 and 1007. This system is described as performing “document retrieval
`
`from a number of Web servers, including the global network of physics
`
`preprints….” Ex. 1007 at 1. These references do not contain any disclosure about
`
`conducting searches for anything other than physics articles. Moreover, there is no
`
`
`existed over thirteen years ago. The declaration provides no discussion or support
`
`as to the accuracy, reliability, or usefulness of the dates or contents of these third-
`
`party screenshots. Patent Owner objects to Petitioners’ attempt to use these
`
`screenshots and understands that the appropriate time for serving formal objections
`
`as to Petitioners’ failure regarding proper authentication is within 10 business days
`
`of the institution of trial under 37 C.F.R. § 42.64(b)(1).
`
`
`
`
`
`8
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`disclosure of associating an advertisement with the searches that one could conduct
`
`on the system. The search engine described in these references was designed for a
`
`very unique setting for a single purpose: the delivery of physics articles. These
`
`references do not provide sufficient disclosure to support the obviousness
`
`combination attempted by Petitioners.
`
`Other generic metasearch services that Petitioners discuss—but do not assert
`
`in alleged prior art combinations—were already considered during prosecution of
`
`the ’749 parent application. For example, references considered during prosecution
`
`of the ’749 parent application included discussion of various existing “multi-
`
`service search” agents and engines that were known at the time of the invention,
`
`including “MetaCrawler,” one of the examples discussed by Petitioners as an
`
`“early metasearch Web site.” Ex. 2001 (Dreilinger, D., Description and Evaluation
`
`of a Meta-Search Agent, M.S. Thesis, Summer 1996, pp. 1-57; Selberg, E., Multi-
`
`Service Search and Comparison Using the MetaCrawler, Proceedings of the Fourth
`
`World Wide Web Conference, pp. 1-18, Oct. 9, 1995.) Petitioners cite nothing
`
`substantively new. In addition, myriad references already considered during
`
`prosecution and others cited on the face of the ’924 Patent are similar to the
`
`“metasearch” web sites discussed in the Petition. E.g., Petition, pg. 3-11.
`
`
`
`9
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`III. CLAIM CONSTRUCTION
`a.
`Petitioners’ Proposed Constructions Are Fanciful and Not the
`Broadest Reasonable Interpretation.
`
`Although claims are to be given their “broadest reasonable construction in
`
`light of the specification of the patent,” Petitioners have failed to offer claim
`
`constructions that are the broadest reasonable interpretations of the claims. 37
`
`C.F.R 42.300(b). Rather, Petitioners seek to add elements in the proposed
`
`constructions that are absurd and contrary to accepted claim construction
`
`principles. Such proposals are unreasonable and incorrect.
`
`Petitioners also fail to offer a definition of what the make-up is of one of
`
`skill in the art, a critical component for performing claim construction. In re Am.
`
`Acad. of Sci. Tech. Ctr., 367 F.3d 1359, 1364 (Fed. Cir. 2004); Phillips v. AWH,
`
`415 F.3d 1303, 1313 (Fed. Cir. 2005); Inter Partes, Post Grant, and Covered
`
`Business Method Review Final Rules, 77 Fed. Reg. 48680, 48699-700 (Aug. 14,
`
`2012). Indeed, Petitioners assert that all other claim elements for which they did
`
`not provide a proposed construction should be construed as “understood by one of
`
`ordinary skill in the art.” Petition, pg. 36. This invitation defies logic as Petitioners
`
`have not identified or described what one of ordinary skill in the art would be for
`
`the ’924 Patent.
`
`Petitioners also seek to improperly add elements that are unnecessary and
`
`would not be included by one of ordinary skill in the art. Many of the proposed
`
`
`
`10
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`constructions include self-serving limitations meant to overcome the shortcomings
`
`in Petitioners’ arguments. Thus, Petitioners’ proposed constructions are not in
`
`compliance with the broadest reasonable interpretation.
`
`Another substantial problem with Petitioners’ proposed constructions is that
`
`Petitioners offer no expert testimony to support their constructions. This is not
`
`surprising given the fact that Petitioners failed to define who is one of ordinary
`
`skill in the art. Curiously, Petitioners submitted two expert declarations, and yet
`
`failed to have either expert offer opinions regarding claim construction.
`
`For these reasons and those articulated below, Petitioners’ proposed
`
`constructions should be rejected. Patent Owner’s proposed constructions are
`
`consistent with the plain language of the challenged claims, the specification, and
`
`how one of skill in the art would understand these terms.
`
`Patent Owner’s Proposed Constructions
`
`b.
`While not necessarily needing to construe the claims to deny the Petition
`
`because of the deficiencies described in detail below, Patent Owner offers
`
`proposed constructions for the terms offered by Petitioners under the broadest
`
`reasonable interpretation.4
`
`4 District courts employ different standards of proof and analyses to claim
`
`construction that are not applied by the USPTO during covered business method
`
`review. The claim constructions provided by Petitioners herein are solely for the
`
`
`
`11
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`Patent Owner provides that one of ordinary skill in the art would be a person
`
`with a bachelor’s degree in computer science, engineering, or a related discipline,
`
`and five years of industry experience.
`
`1. metasearching: sending at least one search query to one or more
`
`information sources substantially simultaneously.
`
`The preamble to each of the challenged claims recites a “process for
`
`metasearching on the Internet, wherein the steps of the process are performed by a
`
`metasearch engine executing on a hardware device . . . .” Ex. 1001, 145:33-36;
`
`147:15-18; 148:5-8. Although Petitioners appear to agree that the preamble is
`
`limiting, Petitioners’ claim construction for this limitation is improper and
`
`inconsistent with the specification and the prosecution history, which requires that
`
`“metasearching” be performed “substantially simultaneously.”
`
`Petitioners agree that the meaning of “metasearching” (or client-server
`
`multitasking as it was initially described) is defined by the inventor in the ’924
`
`Patent:
`
`The patent likewise equates its “metasearch” system/ process with its
`
`“client-server multitasking” system/process. (Id., 111:64- 112:6).
`
`Therefore, the scores of declarations of capabilities of the “invention”
`
`purpose of this CBM. Patent Owner reserves the right to offer different
`
`constructions of the claims in a different forum.
`
`
`
`12
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`or of the “client-server multitasking” process or system, define the
`
`meaning of “metasearch” in this patent.
`
`Petition, pg. 30. Patent Owner agrees that the patent describes various capabilities
`
`of the novel and unique “process for metasearching on the Internet” claimed in the
`
`’924 Patent—which is distinct from the generic “metasearching” which Petitioners
`
`allege was well-known prior to the invention. Patent Owner’s proposed
`
`construction is consistent with the plain claim language and the specification,
`
`while Petitioners’ construction ignores both.
`
`For example, Petitioners ignore the express language of the specification that
`
`client-server multitasking or “metasearching” as described in the ’924 Patent,
`
`allows for “information and/or service retrieval from the same and/or different
`
`ones of servers substantially simultaneously and on-the-fly, using the same
`
`and/or different ones of queries, and sorting, grouping, and/or organizing responses
`
`therefrom substantially on-the-fly.” Ex. 1001, 2:14-19; 3:1-6; 5:10-25; 6:56-64;
`
`102:14-23; 103:1-6; 112:30-34; 115:27-34 (emphasis added).
`
`Rather than sending one query at a time, the claimed method requires that
`
`the “at least one search query” be sent to “a plurality of unique hosts” substantially
`
`simultaneously in time. Id. Petitioners provide no support for ignoring this
`
`limitation in the claimed process of “metasearching,” nor do they explain how this
`
`
`
`13
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`comports with their proposed construction for “metasearch engine”—which
`
`includes entities capable of “simultaneous searches.” Petition, pg. 30.
`
`Petitioners’ proposed construction also ignores the prosecution history of the
`
`’749 parent application, referred to as the Lunenfeld 2000 Application, to which
`
`the ’924 Patent claims priority. The prosecution history shows that Patent Owner
`
`distinguished the claimed invention from the prior art because the references do
`
`not “split a search query and server address pairs into m request groups; open
`
`connection to the specified servers substantially simultaneously and direct queries
`
`comprising different query values to different server addresses….” Ex. 2002,
`
`Preliminary Amendment, August 25, 2003 at pg. 29 (emphasis added). These
`
`statements about the inventions in the Lunenfeld 2000 Application are relevant and
`
`controlling as to the scope of the claimed inventions in the ’924 Patent. Here,
`
`Patent Owner has limited the scope of “metasearching” to require that search
`
`queries are sent “substantially simultaneously.”
`
`Petitioners’ proposed construction is also improper to the extent it seeks to
`
`limit “metasearching” to “unstructured keyword query(ies).” Petition, pg. 29.
`
`Again, Petitioner’s claim construction is inconsistent with the plain claim language
`
`and the specification. First, the plain language of the challenged claims makes
`
`clear that the “at least one search query” is not limited to be either structured or
`
`unstructured. In addition, the ’924 Patent discloses that users may provide user
`
`
`
`14
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`input UIn through the client device as “user input values into fields or alternate
`
`request links of the service and/or information entry request form IEn (38).”
`
`Ex. 1001, 73:17-21. Patent Owner did not limit the structure of the query to be
`
`either structured or unstructured. Petitioners’ own expert, Dr. Etzioni, noted that
`
`search engines in the art could conduct searches based on structured and
`
`unstructured queries. Ex. 1008, at ¶¶ 10-21. It would be improper to limit
`
`“metasearching” to only “unstructured keyword query(ies)” as one of skill in the
`
`art would understand this term to include both types of queries, just as described in
`
`the specification of the ’924 Patent.
`
`2. metasearch engine: software executing on a hardware device that
`
`performs metasearching.
`
`Petitioners’ construction is inconsistent with the plain language of the
`
`challenged claims and the specification. Petitioners’ unwieldy, six-line
`
`construction pushes the boundaries of credulity and is an improper attempt to
`
`import numerous examples from the specification as additional elements to this
`
`claim term.
`
`First, Petitioners’ construction is incorrect to the extent it allows searches of
`
`a “substantially infinite variety of hosts.” One of ordinary skill in the art would
`
`have understood there to be a practical upper boundary of the number of search
`
`queries consistent with the technological capabilities at the time of the invention.
`
`
`
`15
`
`

`
`Patent No. 8,326,924
`CBM2014-00001
`The ’924 Patent is directed toward metasearching “at least one search query.” The
`
`’924 Patent discloses a “substantially infinite” number of potential queries
`
`(qun1…qunm) in connection with the claimed metasearching. Ex. 1001, 20:57-67;
`
`Figs. 2, 3. One of ordinary skill in the art would have known that the “substantially
`
`infinite” potential queries were not “infinite” as Petitioners suggest. Rather, one of
`
`ordinary skill in the art would know that there are in reality a finite number of
`
`potential queries that can be searched. Petitioners’ attempt to cherry pick the word
`
`“infinite” o

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