• Google Inc. v. Better Food Choices LLCAll claims unpatentable
  PTAB · Aug 18, 2016 · CBM2015-00071 · APJ Minn Chung · CBM · Final written decision

  Claims 1–20 are unpatentable under § 101; claims 1–10 are also indefinite under § 112, ¶ 2 because the specification lacks an algorithm for the claimed correlating function.

  RulingsFinal written decision

  • BurdenOther

    “As an initial matter, Patent Owner asserts that Petitioner has not met its burden of proof because Petitioner relies only on the ’115 patent and its prosecution history to argue unpatentability and does not present any other evidence, such as a witness. PO Resp. 6–7, 13–20. Patent Owner argues that Petitioner has presented no evidence of unpatentability because the ’115 patent and its file history “shows the Patent Owner has a valid, issued patent and nothing more.” Id. at 7. We are not persuaded because, as discussed below, in this case we need to look only to the ’115 patent and its prosecution history to support a finding of unpatentability under §§ 101 and 112. See In re TLI Comm. LLC Patent Litig., 823 F.3d 607, 613–14 (Fed. Cir. 2016) (the patent alone is sufficient to sustain a finding of unpatentability under § 101).” slip op. at 12

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesDecided for petitioner

    “rebuttable presumption that the limitation is written in a means-plus-function format under 35 U.S.C. § 112, ¶ 6. TriMed, Inc. v. Stryker Corp., 514 F.3d 1256, 1259 (Fed. Cir. 2008) (citation omitted). If, in addition to the word “means” and the functional language, the claim recites sufficient structure for performing the described functions in their entirety, the presumption is overcome, and § 112, ¶ 6 does not apply. Id. “Sufficient structure exists when the claim language specifies the exact structure that performs the functions in question without need to resort to other portions of the specification or extrinsic evidence for an adequate understanding of the structure.” Id. at 1259–60.” slip op. at 28

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “with the Supreme Court and Federal Circuit precedents on step one analysis under the Alice framework. In step one of the Alice analysis, to determine whether the challenged claims are directed to an abstract idea, the inquiry is to ask, considered in light of the Specification, whether “their character as a whole” is directed to an abstract idea, not, as Patent Owner contends, identifying the “core invention” of the patent. See Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 1335 (Fed. Cir. 2016) (quoting Internet Patents Corp. v. Active Network, Inc., 790 F.3d 1343, 1346 (Fed. Cir. 2015)). Relying on the distinction made in Alice between, on one hand, computer-functionality improvements and, on the other, uses of existing computers as tools in aid of processes focused on “abstract ideas,” the court in Enfish clarified that a relevant inquiry in step one of the Alice framework is to ask whether the “focus” of the claims is on the specific asserted improvement in computer capabilities or, instead, on a process that qualifies as an “abstract idea” for which computers are invoked merely as a tool. Enfish, 822 F.3d at 1335–36 (citing Alice, 134 S. Ct. at 2358–59). In this inquiry, claims “directed to an improvement in the functioning of a computer” are contrasted with claims “simply adding conventional computer components to well-known business practices” or “generalized steps to be performed on a computer using conventional computer activity.” See TLI, 823 F.3d at 612 (quoting Enfish, 822 F.3d at 1338). The Federal Circuit further clarified recently and described the first-stage inquiry as “looking at the ‘focus’ of the claims, their ‘character as a whole.’” Elec. Power Grp., LLC v. Alstom S.A., No. 2015-” slip op. at 17

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable

    “claims fail to recite any elements that individually or as an ordered combination transform the abstract idea of collecting and correlating information to provide personalized nutritional information of food products to shoppers into a patent-eligible application of that idea. It is well-settled that mere recitation of concrete, tangible components is insufficient to confer patent eligibility to an otherwise abstract idea. TLI, 823 F.3d at 613. Rather, the recited components must involve more than performance of “‘well- understood, routine, conventional activit[ies]’ previously known to the industry.” Alice, 134 S. Ct. at 2359 (quoting Mayo, 132 S. Ct. at 1294).” slip op. at 22

  Patent outcomesUS 5,841,115 unpatentable
  Claim construction§ 101 eligibility§ 112 disclosurecites Alice · Mayo · Bilski · Enfish · Nautilus
  Patents in suitUS 5,841,115
• HP Inc. / SAP America, Inc. v. Big Baboon, Inc.Institution denied
  PTAB · Jun 28, 2016 · CBM2016-00020 · APJ Trenton A Ward · CBM · Institution

  The Board denied institution because Petitioner did not show that claims 15 and 20–34 were more likely than not unpatentable under § 101 or any of the three § 103 grounds.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “For the reasons that follow, Petitioner failed to establish that it is more likely than not that at least one of the challenged claims is unpatentable. Therefore, we deny the Petition.” slip op. at 2

  • BurdenDenied

    “We believe the same is true in this matter. Petitioner fails to identify specific documentary evidence indicating that the claim element “via Web administration, producing a software configuration in which selected ones of the modules are enabled or disabled” would have been obvious to a person of ordinary skill in the art at the time of the ’275 patent. At best, Petitioner provides a string cite to nine different documents, without pointing to any particular page or disclosure in any of those documents, as allegedly illustrating an “industry-wide push to Web-enable,” and provides a string cite to eight different paragraphs of testimony from Dr. Greenspun, as allegedly indicating why a skilled artisan “would have seen a strong need to provide Web-enabled system administration capabilities for the R/3 system described in R/3 Online and R/3 Book.” See Pet. 63–64 (citing Exs. 1017– 1021, 1023, 1026, 1027, 1030; Ex. 1032 ¶¶ 58–60, 85–86, 110–112). Petitioner, however, fails to identify with specificity which documentary evidence indicates that it would have been common knowledge to provide a Web interface for system administration of the system described by R/3 Online and the R/3 Book and, thus, that claim 15 would have been obvious to an ordinarily skilled artisan based on combining this alleged common knowledge with the system described by R/3 Online and R/3 Book. The Board, and Patent Owner, are left to speculate as to which particular evidence Petitioner is relying on. See Pet. 12, 42; 37 C.F.R. §§ 42.304(b)(4)–(5) (a petition must “specify where each element of the claim is found in the prior art” and identify “specific portions of the evidence that support the challenge”), 42.22(a)(2) (a petition must include a “full statement of the reasons for the relief requested, including a detailed explanation of the significance of the evidence”). In view of this deficiency, we determine that Petitioner fails to articulate sufficient reasoning to support its assertion of obviousness. See KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). Accordingly, based on the record before us, we determine that Petitioner fails to demonstrate that it is more likely than not that independent claim 15, and claims 20–34 dependent therefrom, would have been obvious over R/3 Online and R/3 Book.” slip op. at 29

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

    “Petitioner urges the Board to construe two claim phrases. First, Petitioner urges us to construe the claimed “end-to-end, business-to-business, e-commerce business automation software for automation business functions across multiple business domains” to mean “[s]oftware that, using a computer network, at least partially automates business functions relating to two or more businesses and from two or more business domains (such as products, payments, and financial performance).” Pet. 19. Second, Petitioner urges us to construe the claimed “via Web administration, producing a software configuration in which selected ones of the modules are enabled or disabled” to mean “producing a software configuration in which modules can be enabled or disabled by (1) changing the configuration parameters of a web server program or (2) using a Web browser to change configuration parameters of software running on a server.” Pet. 21. Patent Owner does not offer any proposed constructions of claim terms in its Preliminary Response. For the reasons explained below, in this case determining the scope of the terms proffered by Petitioner is not necessary to determine whether Petitioner has met the standard for institution of a covered business method patent review, and we decline to adopt the constructions sought by Petitioner. See, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 not directed to exceptionNot shown unpatentable

    “Claim 15 (the only claim substantively addressed by Petitioner), however, does not recite any “gathering” steps, and Petitioner does not explain sufficiently how the limitations of claim 15 are directed to the concept of “gathering” information. For example, claim 15 merely recites “providing . . . business automation software, “identifying multiple modules of the software,” and producing a “software configuration.” Additionally, claim 15 requires producing a “workscope/workflow structured display of complex database records,” which constitutes “an integrated decision-making environment for a particular business function.” Thus, the method of claim 15 does not expressly require that information be gathered across “multiple business domains.” Rather, claim 15 requires providing “business automation software” to produce a “structured display” of “records” pertaining to a “business transaction,” such that the display constitutes an “integrated decision-making environment for a particular business function.” Thus, even if Petitioner is correct that “gathering information from across a business and using the information to make decisions” by itself is an abstract idea, Petitioner’s analysis does not address sufficiently the specific language of claim 15 and explain why claim 15 is directed to that idea. See Pet. 27. Similarly, dependent claims 20–34 are not directed to “gathering information,” and Petitioner provides no analysis of the language of the dependent claims. In light of the above, we determine that Petitioner has failed to establish the first step of the Mayo framework; i.e., Petitioner fails to identify sufficiently an abstract idea to which claim 15 is directed.8 Petitioner combines its arguments under § 101 against dependent claims 20– 34 with its arguments against claim 15 and fails to provide any additional arguments for these dependent claims. See Pet. 25 (arguing that the “sixteen challenged claims of the ’275 patent are likewise unpatentable under §101”). Therefore, we similarly determine that Petitioner fails to establish the first step of the Mayo framework with respect to dependent claims 20–34. Based on the foregoing, we determine Petitioner has failed to establish, based on the record presented, that claims 15 and 20–34 are more likely than not directed to patent ineligible subject matter under 35 U.S.C. § 101. 8 We need not decide whether claim 15 is directed to a different abstract idea, and only determine that Petitioner has not shown sufficiently that claim 15 is directed to the alleged abstract idea that Petitioner proposes in the Petition.” slip op. at 19

  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo
  Patents in suitUS 6,343,275
• Life Technologies Corporation v. Unisone Strategic IP, Inc.All claims unpatentable
  PTAB · Jun 28, 2016 · CBM2015-00037 · APJ Jacqueline Wright Bonilla · CBM · Final written decision

  Claims 52, 62, 67, 70–76, 81, 83–85, and 96 are unpatentable under § 101 because they claim the abstract idea of inventory management using generic computer components.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “degrees in inventory management or similar fields such as supply chain control or logistics” per se, and has “not studied, for a profession, the history of inventory management.” Id. at 34–35 (citing Ex. 2005, 16:14–21, 41:22– 42:3). According to Patent Owner, “Dr. Siegel admits he has no expertise in information management history and only attempted to educate himself in order to prepare his declaration.” Id. at 35. It is clear from Dr. Siegel’s testimony, however, that he has extensive experience in “the use of information technology with business strategy and operations,” has handled professionally “issues related to the integration of information” using computer and software systems, and holds advanced degrees in engineering and computer science. Ex. 1006 ¶¶ 3–11. We are satisfied that Dr. Siegel possesses sufficient qualifications to testify on matters that are relevant to our analysis here, including matters that do not concern the alleged “ancient” history of inventory management. PO Resp. 35. For example, Dr. Siegel testifies that relevant aspects of automated inventory management and VMI were well known before the priority date of the ’538 patent. Ex. 1006 ¶¶ 25–28 (citing Ex. 1018); Ex. 1027 ¶¶ 5–22 (citing Exs. 1020-1022, 1024, 1025). Dr. Siegel also testifies that the ’538 patent specification describes hardware and software that “require only generic computer implementation—not specialized hardware or software.” Ex. 1006 ¶¶ 43–54, 78–79, 89. In addition, Dr. Siegel discusses general concepts of inventory management using a computer and whether certain limitations of the challenged claims can be performed mentally, using pen and paper, or manually, without use of a computer. Id. at ¶¶ 40, 58–66, 80, 90.” slip op. at 23

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “Both Petitioner and Patent Owner present constructions for several claim terms. Pet. 19–24; PO Resp. 12–23. For example, Patent Owner asserts that Petitioner misconstrues the term “customer” by defining it as “a buyer (person or organization) that uses the claimed inventory management.” PO Resp. 15; Pet. 19–20. Consistent with the specification of the ’538 patent, we adopt Patent Owner’s construction of “customer” as referring to a “buyer of products via the present invention” (Ex. 1001, 5:52– 56), i.e., a buyer of products using the inventory management system recited in the respective claims.” slip op. at 7

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

    “Patent Owner also presents constructions in relation to other claim terms such as “inventory restocking parameters provided by said customer,” “tracks” or “tracking,” “access” to information according to “assigned permissions or roles,” and “detecting.” PO Resp. 18–23. For many of the reasons stated in Petitioner’s reply to those constructions, we decline Patent Owner’s invitation to import inappropriately “computerized” aspects into those general terms, notwithstanding the fact that the challenged claims elsewhere recite computer components, such as a “computer,” “databases,” and “software.” Reply 23–25; see also Ex. 1001, 3:3–10 (stating that Customer Inventory System 130 allows manual inventory tracking). For purposes of this Decision otherwise, however, we need not expressly construe claim terms further. Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (only claim terms in controversy need to be construed, and only to the extent necessary to resolve the controversy).” slip op. at 8

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “Based on the complete record before us, we determine that claim 67 is directed to the abstract idea of managing inventory in view of information. We are persuaded that managing inventory in view of collected and analyzed customer inventory, cost information, restocking information provided by a customer, as recited in claim 67, describes the basic concept of inventory management, i.e., a “fundamental economic practice.” Alice, 134 S. Ct. at 2356. The method of claim 67 is sufficiently similar in this regard to the method of hedging against financial risk at issue in Bilski, 130 S.Ct. 3218 (2010), and the idea of intermediated settlement at issue in Alice, 134 S. Ct. at 2356–57 (discussing Bilski). See also Accenture Global Servs., GmbH v. Guidewire Software, Inc., 728 F.3d 1336, 1344 (Fed. Cir. 2013) (holding the abstract idea at the heart of a system claim to be “generating tasks [based on] rules . . . to be completed upon the occurrence of an event” (citation omitted)).” slip op. at 22

  Patent outcomesUS 6,996,538 unpatentable
  Claim construction§ 101 eligibilitycites Alice · Mayo · Bilski
  Patents in suitUS 6,996,538
• Care N’ Care Insurance Company, Inc. / Trizetto Corporation v. Integrated Claims Systems, LLCAll claims unpatentable
  PTAB · Jun 21, 2016 · CBM2015-00064 · APJ Timothy J Goodson · CBM · Final written decision

  Claims 81 and 83–88 are unpatentable under § 101 because they are directed to an abstract idea without an inventive concept.

  RulingsFinal written decision

  • BurdenFwd all claims unpatentableUnpatentable

    “Considering the full record before us, we agree with, and adopt as our own, Petitioners’ explanation of why the challenged claims fail to recite any elements that individually or as an ordered combination transform the abstract idea of receiving information, storing it, and determining which of its parts to enter into a display into a patent-eligible application of that idea. Pet. 34–43. Stated simply, the challenged claims require no more than generic computer components performing generic computer functions and conventional activities. See Alice, 134 S. Ct. at 2359 (noting, in carrying out the second step, that the “the relevant question is whether the claims here do more than simply instruct the practitioner to implement the abstract idea . . . on a generic computer”); TLI, 2016 WL 2865693 at *6 (“These steps fall squarely within our precedent finding generic computer components insufficient to add an inventive concept to an otherwise abstract idea.”). For example, claim 81 recites receiving data in fields, storing data in memory, determining which data to enter for display using a generic “logic process,” and displaying data. “[A]ll of these computer functions are ‘wellunderstood, routine, conventional activit[ies]’ previously known to the industry.” Alice, 134 S. Ct. at 2359 (quoting Mayo, 132 S. Ct. at 1294). The parallels that Petitioner draws between the claims challenged here and those addressed in Content Extraction are compelling. See Pet. 35–36. Patent Owner’s reliance on the use of fields in the challenged claims to satisfy the second step of the Mayo/Alice analysis and to distinguish Content Extraction is unpersuasive in view of Petitioners’ argument and evidence that computer software fields are a generic, well-known concept in data processing, and that using fields to transfer information from a field in one form to a correlated field in another form was routine and conventional. Reply 12; Ex. 1001 ¶¶ 36–37.” slip op. at 24

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

    “We agree with Petitioners. We see no reason why the resolution of the issues before us requires an express construction of this term. Even if we were to construe “field” as a “computer software field,” it would not impact our analysis of claims 81 and 83‒88 under 35 U.S.C. § 101. Accordingly, we do not provide an express construction of “field.” See Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”).” slip op. at 14

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “We agree with Petitioners that the challenged claims are directed to a process of receiving information, storing it, and determining which of its parts to enter into a display. Pet. 29. Claims directed to such a process are analogous to the data processing claims that the Federal Circuit held were directed to an abstract idea in Content Extraction and Cyberfone. In particular, as Petitioners argue, the step in claim 81 “of determining which parts of the information to enter into a graphical display is analogous to the step in [Content Extraction] of ‘recognizing certain data within the collected data set.’” Pet. 33. Further, the steps in claim 81 of receiving information and storing it are similar to the steps in Content Extraction of collecting data and storing the recognized data in a memory. Id. With respect to Cyberfone, we agree with Petitioners that the challenged claims can be “described as directed to methods of ‘obtaining data . . . separating it into component parts, and sending those parts to different destinations’ that the Federal Circuit in Cyberfone held embodied an abstract idea.” Id. at 34 (quoting Cyberfone, 558 F. App’x at 990). We have considered Patent Owner’s arguments that the challenged claims are not directed to an abstract idea, but those arguments are not persuasive for the reasons that follow.” slip op. at 17

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable

    “Considering the full record before us, we agree with, and adopt as our own, Petitioners’ explanation of why the challenged claims fail to recite any elements that individually or as an ordered combination transform the abstract idea of receiving information, storing it, and determining which of its parts to enter into a display into a patent-eligible application of that idea. Pet. 34–43. Stated simply, the challenged claims require no more than generic computer components performing generic computer functions and conventional activities. See Alice, 134 S. Ct. at 2359 (noting, in carrying out the second step, that the “the relevant question is whether the claims here do more than simply instruct the practitioner to implement the abstract idea . . . on a generic computer”); TLI, 2016 WL 2865693 at *6 (“These steps fall squarely within our precedent finding generic computer components insufficient to add an inventive concept to an otherwise abstract idea.”). For example, claim 81 recites receiving data in fields, storing data in memory, determining which data to enter for display using a generic “logic process,” and displaying data. “[A]ll of these computer functions are ‘wellunderstood, routine, conventional activit[ies]’ previously known to the industry.” Alice, 134 S. Ct. at 2359 (quoting Mayo, 132 S. Ct. at 1294). The parallels that Petitioner draws between the claims challenged here and those addressed in Content Extraction are compelling. See Pet. 35–36. Patent Owner’s reliance on the use of fields in the challenged claims to satisfy the second step of the Mayo/Alice analysis and to distinguish Content Extraction is unpersuasive in view of Petitioners’ argument and evidence that computer software fields are a generic, well-known concept in data processing, and that using fields to transfer information from a field in one form to a correlated field in another form was routine and conventional. Reply 12; Ex. 1001 ¶¶ 36–37. We also agree with Petitioners that the challenged claims fail the machine-or-transformation test because the claims “are not tied to any particular novel machine or apparatus, only a general purpose computer,” and “adding a computer to otherwise conventional steps does not make an invention patent-eligible.” Ultramercial, 772 F.3d at 716–17. We discern nothing in the challenged claims requiring a novel machine or apparatus. Indeed, as noted above, Patent Owner concedes that “the hardware components recited by the Challenged Claims were known at the time the application leading to the ’609 Patent was filed.” Prelim. Resp. 19; PO Resp. 20. Turning to the transformation prong of the test, “[a]ny transformation from the use of computers or the transfer of content between computers is merely what computers do and does not change the analysis.” Ultramercial, 772 F.3d at 717. Moreover, as the Federal Circuit explained in CyberSource, the “mere collection and organization of data regarding credit card numbers and Internet addresses is insufficient to meet the transformation prong of the test.” 654 F.3d at 1370. Here, claim 81 recites receiving an electronic communication that includes digital data in fields, some of which include insurance transaction data and at least one of which includes attachment data, storing the electronic communication, and processing the electronic communication by determining which of the received data to display and displaying the selected data and the attachment on a GUI. Ex. 1003, 50:20–43. We agree with Petitioners that the claimed method merely collects and organizes data, which is insufficient to meet the transformation prong of the machine-or-transformation test. Dependent claims 83–88 also do not recite more than the mere collection and organization of data.” slip op. at 24

  Patent outcomesUS 8,676,609 unpatentable
  Claim construction§ 101 eligibilitycites Mayo
  Patents in suitUS 8,676,609
• Samsung Electronics America, Inc. / Samsung Electronics Co., Ltd. et al. v. Smartflash LLCRehearing denied
  PTAB · Jun 10, 2016 · CBM2014-00194 · APJ Jennifer S Bisk · CBM · Rehearing

  The Board denied Patent Owner’s rehearing request, leaving intact its determination that claim 32 is unpatentable under § 101.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “showing unpatentability by a preponderance of the evidence. 35 U.S.C. § 326(e). The standard of review for rehearing requests is set forth in 37 C.F.R. § 42.71(d), which states: The burden of showing a decision should be modified lies with the party challenging the decision. The request must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, or a reply.” slip op. at 3

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Not reached

    “Patent Owner’s arguments are either new or were addressed in our Final Decision. For example, Patent Owner’s argument that the challenged claims are not directed to an abstract idea (Req. Reh’g 10–12) is new, and therefore, improper in a request for rehearing, because Patent Owner did not argue the first step of the analysis articulated in Mayo and Alice in its Patent Owner Response (see PO Resp. passim (arguing only the second step of the Mayo and Alice test)). To the extent portions of the Request are supported by Patent Owner’s argument in the general citations to the record, we considered those arguments in our Final Decision, as even Patent Owner acknowledges. See, e.g., Req. Reh’g 7 (citing Final Dec. 15) (“The Board rejected Patent Owner’s reliance on DDR Holdings (at 15), holding that Claim 7 was not ‘rooted in computer technology in order to overcome a problem specifically arising in the realm of computer networks.’”). For example, Patent Owner’s arguments about inventive concept (Req. Reh’g 5– 7, 12–15) were addressed at pages 10–13 and 18–20 of our Final Decision, Patent Owner’s arguments about preemption (Req. Reh’g. 6–7) were addressed at pages 20–22 of our Final Decision, and Patent Owner’s arguments about DDR Holdings (Req. Reh’g. 7–10) were addressed at pages 14–18 of our Final Decision. Mere disagreement with our Final Decision also is not a proper basis for rehearing.” slip op. at 5

  § 101 eligibilitycites Alice
  Patents in suitUS 8,118,221
• Informatica Corporation v. Protegrity CorporationAll claims unpatentable
  PTAB · May 31, 2016 · CBM2015-00021 · APJ Kevin F Turner · CBM · Final written decision

  Claims 1–8 and 18–53 are unpatentable under § 101; claims 1, 2, 8, 19–26, 29, 31–35, 37–44, and 47–53 are also unpatentable under § 103.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “claim, and “it is the single best guide to the meaning of a disputed term.” Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996). The written description of the ’201 Patent provides specific definitions of many terms (Ex. 1001, 2:64–3:43) but does not contain a definition of “database.” The claimed database for storing a plurality of data element values corresponds to the O-DB database disclosed in the ’201 Patent. The O-DB database is part of a larger “database management system” that includes multiple databases. Id. at 5:49–6:12, Fig. 3. Similar to the other databases, the O-DB database is described as containing data and, in particular, data to be protected. Id. at 5:53–58. Contrary to Patent Owner’s argument (Resp. 20), the ’201 Patent does not describe the O-DB database, or any other database, as performing any other data processing or managing functions. In particular, the ’201 Patent does not describe that the O-DB database produces the compelling calling to the data protection catalogue. See Ex. 1001, 10:44–58 (“is first collected by the system”); see id. at Abstract, 2:54– 61, 3:51–65, 4:16–22, 7:57–61 (describing a compelling calling to a data protection catalogue, but failing to describe the compelling calling being produced by the O-DB database).” slip op. at 9

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningOther

    “Claims 1 and 8 do not recite unencrypted data element values, and only recites “encrypted data element values.” Those claims do not specify that the “given data element value” should be encrypted or unencrypted. We are not persuaded by Patent Owner’s declarants (Ex. 2063 ¶ 33; Ex. 2064 ¶ 48) as their testimonies are conclusory and are unsupported by the Specification or claims of the ’201 Patent. Although the “given data element value” could be the unencrypted data element value, it need not be in the context of claim 1.” slip op. at 15

  • ExcludeMotion to exclude, deniedDenied

    “As the Board has noted in numerous cases, “the Board, sitting as a non-jury tribunal with administrative expertise, is well-positioned to determine and assign appropriate weight to the evidence presented in this trial, without resorting to formal exclusion that might later be held reversible error.” See, e.g., Liberty Mutual Insurance Co. v. Progressive Casualty Insurance Co., CBM2012-00002, Paper 66 at 70 (PTAB Jan. 23, 2014); Gnosis S.P.A., et al. v. S. Alabama Medical Science Foundation, IPR2013- 00118, Paper 64 at 43 (PTAB June 20, 2014); S.E.C. v. Guenthner, 395 F. Supp. 2d 835, 842 n.3 (D. Neb. 2005); Opp. to Mot. Exclude 4. We, thus, are not persuaded by Petitioner to exclude Exhibits 2064, 2089, and 2093 and Petitioner’s Motion to Exclude is denied. Additionally, we are also not persuaded that Dr. Direen is unqualified to testify as an expert. As Petitioner points out, Dr. Direen has knowledge, skill, experience, and training beyond degrees and is the holder of several patents. Opp. to Mot. Exclude 3–8; See Ex. 1002 ¶¶ 1–7 (discussing additional credentials and qualifications). Given this, we are persuaded that Dr. Direen is qualified to testify as an expert as to what a person of ordinary skill in the art would know or understand during the relevant time frame.” slip op. at 52

  • Strike new argumentNew argument disregardedGranted

    “The scheduling order states “[a] motion for observation on cross- examination provides the parties with a mechanism to draw the Board’s attention to relevant cross-examination testimony of a reply witness because no further substantive paper is permitted after the reply” and refers to the Office Patent Trial Practice Guide. Paper 15, 4–5. The Trial Practice Guide states: In the event that cross-examination occurs after a party has filed its last substantive paper on an issue, such cross-examination may result in testimony that should be called to the Board’s attention, but the party does not believe a motion to exclude the testimony is warranted. The Board may authorize the filing of observations to identify such testimony and responses to observations, as defined below. 77 Fed. Reg. at 48,767–68 (emphasis added).” slip op. at 53

  Patent outcomesUS 6,321,201 unpatentable
  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Bilski · Graham
  Patents in suitUS 6,321,201
• Informatica Corporation v. Protegrity CorporationAll claims unpatentable
  PTAB · May 9, 2016 · CBM2015-00010 · APJ Meredith C Petravick · CBM · Final written decision

  Claims 33–60 are unpatentable under § 101; the motion to amend is denied as to substitute claims 61–68 and granted as to cancellation of claims 1–32.

  RulingsFinal written decision

  • Adverse judgmentAdverse judgmentGranted

    “B. Patent Owner’s Request to Cancel Claims 1–32 In the Patent Owner’s Response and the Motion to Amend, Patent Owner requests cancellation of claims 1–32 of the ’281 patent. PO Resp. 2– 3; Mot. Amend 1. Patent Owner’s request to cancel these claims is not contingent on the claims being determined to be unpatentable or on the entry of the proposed substitute claims. Patent Owner’s request to cancel claims 1–32 is granted and we need not address these claims further. Paper 23. Patent Owner, subsequently, filed the Motion to Amend as Exhibit 2098. See Paper 43.” slip op. at 3

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “Vehicular Techs. Corp. v. Titan Wheel Int'l, 141 F.3d 1084, 1088 (Fed. Cir. 1998) (citing Bell Commc’ns Research, Inc. v. Vitalink Commc’ns Corp., 55 F.3d 615, 619–20 (Fed. Cir. 1995)). Independent claim 33 recites “[a] computer-implemented data processing method” that includes, among other steps, a step of “maintaining a database comprising a plurality of data portions.” Ex. 1001, 13:38–41. Similarly, independent claim 47 recites “[a] computer system” that includes, among other elements, “a database storing a plurality of data portions.” Id. at 14:47–48. As can be seen from the above, claims 33 and 47 recite that the database comprises or stores data portions. Neither of claims 33 and 47, nor any claims dependent, therefrom, recite that the database performs any other function, such as producing a compelling calling to the data protection catalogue to retrieve the data processing rules. See id. at 13:38–16:29. Indeed, unlike the parent ’201 patent, none of the claims of the ’281 patent recite a compelling calling at all. See id.; Ex. 1004, Ex Parte Reexamination Certificate 1:24–51 (amended claim 8). Notably, independent claim 8 of the parent ’201 patent recite an apparatus having a database that stores data to be protected. Ex. 1004, Ex Parte Reexamination Certificate 1:24–51 (amended claim 8). Claim 8 of the parent ’201 patent was amended during reexamination to recite that the apparatus, not the database, controls the user’s processing of the data according to the data processing rules, and the apparatus, not the database, also produces the compelling calling to the data element protection catalogue. Id. at Ex Parte Reexamination Certificate 1:41–51. The words of the claims of the ’281 patent, thus, are consistent with Petitioner’s proposed construction as the broadest reasonable construction.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

    “v. Other Proposed Constructions Petitioner also proposed a construction of “encryption/encrypted” and “separate data protection table.” Pet. 15–18. Patent Owner also proposed a construction of “data element type.” PO Resp. 27–28. For the purposes of our review of the claims of the ’281 patent, however, no explicit construction of any other claim term is needed.” slip op. at 18

  • BurdenInstitution denied meritsDecided for petitioner

    “A party may not petition for post-grant review if it has filed a civil action challenging the validity of a claim of the patent before the petition is filed. 35 U.S.C. § 325(a)(1); 37 C.F.R. § 42.201(a). In SecureBuy, LLC, the Board determined the 35 U.S.C. § 325(a)(1) applied to covered business method review proceedings, but made no determination as to whether or not a dismissal without prejudice triggered the statutory bar. See SecureBuy, LLC, CBM2014-00035 (PTAB April 25, 2014) (Paper 12). Here, Petitioner’s filing of a civil action before filing the Petition did not trigger the statutory bar because the civil action was dismissed without prejudice. See id. Dismissal without prejudice does not trigger the statutory bar. See Decision 9 (citing Cyanotech Corp. v. Bd. of Trustees of the Univ. of Ill., IPR2013-00401, slip op. at 11–12 (PTAB Dec. 19, 2013) (Paper 17) (“Excluding an action that de jure never existed from the scope of § 315(a)(1) is consistent with both relevant case law and 7 On May 4, 2015, Petitioner, via email, informed the Board of a clerical typographical error on page 11 of the Petition. The sentence starting with “[i]n the prior cases, petitioner was sued . . .” should be read as “[i]n the prior cases, petitioner was not sued . . . .” legislative history.”); Callidus Software, Inc. v. Versata Software, Inc., CBM2013-00052, slip op. at 5–7 (PTAB Mar. 4, 2014) (Paper 21). “The dismissal of an action without prejudice leaves the parties as though the action had never been brought.” Ariosa Diagnostics v. Isis Innovation Ltd., IPR2012-00022, slip op. at 16–18 (PTAB Sept. 2, 2014)(Paper 166) (citing Graves v. Principi, 294 F.3d 1350, 1356 (Fed. Cir. 2002)).” slip op. at 19

  Patent outcomesUS 8,402,281 unpatentable
  Claim construction§ 101 eligibilitycites Alice · Mayo
  Patents in suitUS 8,402,281
• Epicor Software Corporation v. Protegrity CorporationSome claims unpatentable
  PTAB · Apr 20, 2016 · CBM2015-00002 · APJ Kevin F Turner · CBM · Final written decision

  Claims 1, 5, 19, and 20 are unpatentable under § 101; claims 27–31 were not shown unpatentable under that ground.

  RulingsFinal written decision

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionDecided for petitioner

    “e. Broadest Reasonable Construction of “Database” We determine that the broadest reasonable construction, in light of the specification of the ’201 Patent, and the proffered evidence, of “database” is “an organized collection of structured data.” As discussed above, this construction is consistent with the words of the claims, the disclosure of the ’201 Patent, the testimony of Mr. Schneier and Dr. Shamos and the position taken by Patent Owner in the related district court proceeding. We are not persuaded by Patent Owner’s arguments, Patent Owner’s declarants’ testimony, database manual, or technical encyclopedia that this construction is unreasonably broad.” slip op. at 13

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for patent owner

    “Mr. Mattsson’s and Dr. Direen’s testimony is unpersuasive because it is inconsistent with the ’201 Patent. As discussed above, the ’201 Patent describes the O-DB as one database in a larger database management system. Ex. 1001, 5:49–6:12. The ’201 Patent describes the O-DB database as containing data and describes the modules of the larger database management system as performing data processing. Id. at 5:53–58, 6:13–45. The ’201 Patent does not describe the O-DB database as producing the compelling calling. See Ex. 1001, 10:44–58 (“is first collected by the system”); see id. at Abstract, 2:54–61, 3:51–65, 4:16–22, 7:57–61 (disclosing a compelling calling to a data protection catalogue, but failing to describe the compelling calling being produced by the O-DB database). The assertion that the compelling calling is produced by the O-DB database is only found in Patent Owner’s arguments, Mr. Mattsson’s testimony, and Dr. Direen’s testimony, and not the ’201 Patent. See, e.g., Ex. 2045 ¶¶ 12– 16, 22, 29; Ex. 2046 ¶ 57. Extraneous features should not be read into the claim. Renishaw PLC v. Marposs Societa’ per Azioni, 158 F.3d 1243, 1249 (Fed. Cir. 1998); E.I. du Pont de Nemours & Co. v. Phillips Petroleum Co., 849 F.2d 1430, 1433 (Fed. Cir. 1988). In that regard, “extrinsic evidence may be used only to assist in the proper understanding of the disputed limitation; it may not be used to vary, contradict, expand, or limit the claim language from how it is defined, even by implication, in the specification or file history.” Bell Atl. Network Servs. v. Covad Commc'ns Grp., 262 F.3d 1258, 1269 (Fed. Cir. 2001); see Vitronics, 90 F.3d at 1584 (“expert testimony, which was inconsistent with the specification and file history, should have been accorded no weight”). Further, we give little weight to Mr. Mattsson’s testimony because Mr. Mattsson is not a disinterested witness. Mr. Mattsson is Patent Owner’s Chief Technology Officer (Ex. 2045 ¶ 1) and has an interest in the outcome of this proceeding.” slip op. at 11

  • ExcludeMotion to exclude, deniedDenied

    “We are not persuaded by Patent Owner’s argument that Mr. Schneier’s declaration should be excluded under FRE Rule 702 or 403. Patent Owner’s arguments attack the sufficiency and credibility of Mr. Schneier’s testimony. As the Board has noted in numerous cases, “the Board, sitting as a non-jury tribunal with administrative expertise, is well-positioned to determine and assign appropriate weight to the evidence presented in this trial, without resorting to formal exclusion that might later be held reversible error.” See, e.g., Liberty Mutual Insurance Co. v. Progressive Casualty Insurance Co., CBM2012-00002, Paper 66 at 70 (PTAB Jan. 23, 2014); Gnosis S.P.A., et al. v. S. Alabama Medical Science Foundation, IPR2013-00118, Paper 64 at 43 (PTAB June 20, 2014); S.E.C. v. Guenthner, 395 F. Supp. 2d 835, 842 n.3 (D. Neb. 2005); Opp. to Mot. Exclude 4. We, thus, are not persuaded by Patent Owner to exclude Exhibit 1002 and Patent Owner’s Motion to Exclude is denied.” slip op. at 35

  • Strike new argumentNew argument disregardedGranted

    “The scheduling order authorizes the filing of such a motion for observations regarding cross-examination of a reply witness by Due Date 4. Mr. Schneier cross-examination testimony was given on June 12, 2015, prior to Patent Owner filing its Patent Owner’s Response, on June 24, 2105. The cross-examination did not occur after Patent Owner filed its last substantive paper. Patent Owner’s Motion for Observation, thus, is improper. The Scheduling Order did not authorize Patent Owner to file a Motion for Observation of cross-examination that occurred prior to Patent Owner filing its last substantive paper on an issue, the Patent Owner’s Response and Patent Owner did not seek other authorization for such. The improper observations are akin to an unauthorized sur-reply to argument made in Petitioner’s Reply. We, thus, expunge Patent Owner’s unauthorized observations from the record. See 37 C.F.R. § 42.7(a). Additionally, we expunge Petitioner’s Opposition to that Observation (Paper 40) as being unnecessary.” slip op. at 37

  Patent outcomesUS 6,321,201 mixed
  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo · Bilski
  Patents in suitUS 6,321,201
• Epicor Software Corporation v. Protegrity CorporationRehearing denied
  PTAB · Apr 19, 2016 · CBM2015-00002 · APJ Kevin F Turner · CBM · Rehearing

  The Board denied both rehearing requests, leaving the institution of § 101 review of claims 1, 5, 8, 19, 20, and 27–31 and denial of prior art grounds unchanged.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “D. Conclusion We are not persuaded of an abuse of discretion either by Patent Owner or Petitioner. III. ORDER In consideration of the foregoing, it is hereby: ORDERED that each Request for Rehearing is denied.” slip op. at 18

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “The Board instituted covered business method patent review of the ’201 Patent based upon the following ground, combined from both proceedings: Ground Prior Art Challenged Claims § 101 n/a 1, 5, 8, 19, 20, and 27–31 Papers 17 and 13 (’02 Decision and ’30 Decision, respectively). The Board did not institute covered business method patent review upon any prior art grounds. See ’02 Decision 6 and ’30 Decision 4–5 (listing grounds proffered by Petitioner).” slip op. at 2

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionDecided for petitioner

    “Response, Patent Owner argues that the claims are directed toward protection of data in a database on a more granular level, namely at the data element level. Prelim. Resp. 27 (“the ’201 Patent is not directed to some abstract idea, but rather a specific improvement in computing technologies to protect data in a database at the date element level”). However, the abstract idea we identified is that of “determining whether access to a given data element value in a database should be granted based on whether one or more rules are satisfied.” ’02 Decision 20. See also Pet. 20. As such, the abstract idea goes directly to the concept of protecting data at the data element level.” slip op. at 13

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “Although Atalla discloses authorization to a file based on information about the file, Ex. 1007, 3:27–58, Petitioner has not shown that the information about the file is individual data element types. Overall, Atalla addresses accessing files, in part, based on whether the files were previously accessed, but a file in not the same as an individual data element value. The section of Atalla cited in Petitioner’s Rehearing Request discloses the need for a correct key code, but that key code is for the entire file and not specific to the data element type. Pet. Req. 6 (citing Ex. 1007, 3:27–58). Although “information about the file” could include information about individual data element types, Petitioner has not demonstrated any such teaching or suggestion in Atalla. As stated in the ’02 Decision, Atalla “does not describe that access authorization file 15 comprises ‘a data element protection catalogue (DPC), which contains each individual data element type (DT) and one or more protection attributes stating processing rules for data element values’ as requires by claim 1.” ’02 Decision 28. Thus, we are not persuaded by Petitioner that we abused our discretion in denying institution of covered business method patent review of claims 1, 5, 19, 20, and 27–31 over the anticipation ground of Atalla provided in the Petition.” slip op. at 16

  § 101 eligibility§ 102 anticipation§ 103 obviousness
  Patents in suitUS 6,321,201
• Epicor Software Corporation v. Protegrity CorporationSome claims unpatentable
  PTAB · Apr 18, 2016 · CBM2015-00006 · APJ Meredith C Petravick · CBM · Final written decision

  Claims 33–38, 41, 43–52, 55, and 57–60 are unpatentable under § 101; claims 39, 40, 42, 53, 54, and 56 were not shown unpatentable. Substitute claims 61–68 were denied.

  RulingsFinal written decision

  • Adverse judgmentAdverse judgmentGranted

    “B. Patent Owner’s Request to Cancel Claims 1–32 In the Patent Owner’s Response and the Motion to Amend, Patent Owner requests cancellation of claims 1–32 of the ’281 patent. PO Resp. 2– 3; Mot. Amend 1. Patent Owner’s request to cancel these claims is not contingent on the claims being determined to be unpatentable or on the entry of the proposed substitute claims. Patent Owner’s request to cancel claims 1–32 is granted and we need not address these claims further.” slip op. at 3

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “1998) (citing Bell Commc’ns Research, Inc. v. Vitalink Commc’ns Corp., 55 F.3d 615, 619–20 (Fed. Cir. 1995)). Independent claim 33 recites “[a] computer-implemented data processing method” that includes, among other steps, a step of “maintaining a database comprising a plurality of data portions.” Ex. 1001, 13:38–41. Similarly, independent claim 47 recites “[a] computer system” that includes, among other elements, “a database storing a plurality of data portions.” Id. at 14:47–48. As can be seen from the above, claims 33 and 47 recite that the database comprises or stores data portions. Neither of claims 33 and 47, nor any claims dependent therefrom, recites that the database performs any other function, such as producing a compelling calling to the data protection catalogue to retrieve the data processing rules. See id. at 13:38–16:29. Indeed, unlike the parent ’201 patent, none of the claims of the ’281 patent recite a compelling calling at all. See id.; Ex. 1004, Ex Parte Reexamination Certificate 1:24–51 (amended claim 8). Notably, independent claim 8 of the parent ’201 patent recite an apparatus having a database that stores data to be protected. Ex. 1004, Ex Parte Reexamination Certificate 1:24–51 (amended claim 8). Claim 8 of the parent ’201 patent was amended during reexamination to recite that the apparatus, not the database, controls the user’s processing of the data according to the data processing rules, and the apparatus, not the database, also produces the compelling calling to the data element protection catalogue. Id. at Ex Parte Reexamination Certificate 1:41–51. The words of the claims of the ’281 patent, thus, are consistent with Petitioner’s proposed construction as the broadest reasonable construction.” slip op. at 10

  • BurdenDecided for petitioner

    “We are persuaded by Petitioner that a preponderance of the evidence shows that at least claim 33 encompasses activities that are financial in nature, incidental to a financial activity, or complementary to a financial activity.” slip op. at 21

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionDecided for petitioner

    “Independent claim 33 recites a data processing method that grants access to a requested data portion if the rules associated with a data category that is associated with the requested data portion is satisfied. Ex. 1001, 13:38–54. Claim 33 requires a database that comprises the data portions and requires a separate data protection table comprising data processing rules that must be satisfied before the data portion can be accessed. Id. The data processing rules are associated with the data category. Id. Independent claim 47 recites a corresponding computer system. Id. at 14:47–63. Independent claims 33 and 47, thus, recite a method or system that grants access to a requested data portion if the rules associated with a data category that is associated with the requested data portion are satisfied. Ex. 1001, 13:38–54. Given the above, we are persuaded by Petitioner that the claims are directed to the abstract idea of determining whether access to data should be granted based on whether one or more rules are satisfied. We are not persuaded by Patent Owner that the claims are not directed to an abstract idea, because Patent Owner’s argument is based upon elements not required by the claims. See PO Resp. 29–38. Given our construction of “data portion” and “database” in section II (A) above, the claims do not require protection on the data element level based on rules stored in a separate database, where the first database calls out to the second database. Patent Owner’s argument is not commensurate with the scope of the claims.” slip op. at 30

  Patent outcomesUS 8,402,281 mixed
  Claim construction§ 101 eligibilitycites Alice · Mayo
  Patents in suitUS 8,402,281

Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.