PTAB
Advanced fields
9 decisions · 413msnewest first
  • PTAB · Sep 7, 2021 · PGR2021-00060 · APJ Ryan H Flax · PGR · Institution

    The Board denied institution because the petition did not show claims 1–7 likely unpatentable, and a possible § 112(a) issue for claims 8–9 did not justify instituting on all claims and grounds.

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

      “not demonstrated with particularity that it is more likely than not that most claims challenged in the petition are unpatentable under the asserted grounds. Although there is a reasonable argument that claims 8 and 9 may be unpatentable under 35 U.S.C. § 112(a), as discussed above, this analysis is applicable to only these two dependent claims under a single ground for unpatentability, leaving Petitioner’s other ten grounds insufficient regarding independent claim 1 and dependent claims 2–7. As discussed above, instituting trial under these circumstances would not be an efficient use of the Board’s or the parties’ time and resources. See Chevron, IPR2018- 00923, Paper 9, 10–11; Deeper, UAB v. Vexilar, Inc., IPR2018-01310, Paper 7, 41–43 (PTAB Jan. 24, 2019) (informative). Our decision at this stage derives from our review of the record presented. In accordance with the Court’s decision in SAS (138 S. Ct. at 1359– 60) and Office guidance, we deny institution of a post-grant review of the challenged claims of the ’631 patent on any grounds alleged by Petitioner. This decision does not reflect a final determination on the patentability of any claim.” slip op. at 66

    • Other 314aInstitution denied discretionary otherInstitution denied

      “Even when a petitioner satisfies the minimum statutory institution standard (e.g., demonstrating a reasonable likelihood of prevailing with respect to one or more claims in an inter partes review or that it is more likely than not that at least one claim is unpatentable in a post-grant review), institution of review remains discretionary. SAS Inst. v. Iancu, 138 S. Ct. 1348, 1356 (2018); Harmonic, Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1367 (Fed. Cir. 2016) (“First of all, the PTO is permitted, but never compelled, to institute an IPR proceeding.”). Under such circumstances, the Board takes into account other considerations, including efficiency and fundamental fairness for all parties. See Adaptics Limited v. Perfect Co., IPR2018-01596, Paper 20 at 17 (PTAB Mar. 6, 2019) (informative); Chevron Oronite Co. LLC v. Infineum USA L.P., IPR2018-00923, Paper 9 (PTAB Nov. 7, 2018) (informative); see also Consolidated Trial Practice Guide, 84 FR 64280, 53– 63 (2019) (addressing various considerations at institution phase, including efficiency and fundamental fairness for all parties).1 We conclude that Petitioner has not demonstrated in the petition that it is more likely than not that challenged claims 1–7 are unpatentable under any asserted grounds for unpatentability. Although it is a closer question as to whether Petitioner has demonstrated it is more likely than not that dependent claims 8 and 9 are unpatentable based on a single asserted unpatentability ground under § 112, we determine based on the record here that instituting a trial with respect to all challenged claims under all eleven asserted grounds for unpatentability is not an efficient use of the Board’s or the parties’ time and resources. Therefore, we do not institute post-grant review pursuant to 35 U.S.C. § 324. See SAS, 138 S. Ct. at 1359–60 (requiring institution on all claims, if any); see also Consolidated Trial Practice Guide, 55 (providing guidance in view of SAS).” slip op. at 2

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

      “to read the concept of “flush with” into the claims. We agree with Petitioner’s position that such an interpretation is not supported by the ’631 patent’s written description, which illustrates and describes two embodiments, each having a turbine engine and reduction gearbox configured to be flush with one another, but refers to only the configuration of Embodiment 1 as being “directly connected” and refers to the configuration of Embodiment 2 as being merely “connected.” See Ex. 1001, 5:27–28, 5:62–6:2, Figs. 2, 3; see also Ex. 2001 ¶ 63 (Patent Owner’s expert witness confirming there is a difference between merely “connected” and “directly connected”). Thus, the intrinsic record supports a conclusion that the concept of “directly connected” is not related to whether one component is “flush with” another component. This disclosure of the ’631 patent also illuminates the meaning of “directly connected.” As shown in Embodiment 2, something may be connected with another thing even if there are intervening components, e.g., a transmission shaft or coupling; however, as shown in Embodiment 1, the ’631 patent uses the term “directly connected” only where no such intervening components are disclosed. Ex. 1001, 5:15– 6:19, Figs. 2, 3. Besides the guidance provided with respect to the embodiments discussed above, the ’631 patent does not otherwise expressly define the term “directly connected.” See generally Ex. 1001. Thus, we consider what the ordinarily skilled artisan would consider to be its ordinary and customary meaning. In this respect, Patent Owner also uses the word “uninterrupted” to describe “directly connected.” See Prelim. Resp. 6; see also Ex. 2001 ¶¶ 61–71. We conclude based on this record that the concept of “uninterrupted” is more apt than the concept of “flush with,” and find it to be a better description for the ordinary and customary meaning of “directly connected.” For example, the ’631 patent describes, in Embodiment 1, “the turbine engine 19 is connected to the plunger pump 18.” Ex. 1001, 5:26–27 (emphasis added). However, it is without question that Embodiment 1 positions a reduction gearbox between the turbine engine and plunger pump; thus, the engine and pump may be connected, but they are not directly connected. See, e.g., Fig. 2. On the other hand, regarding this same Embodiment 1, the ’631 patent describes that “the turbine engine 19 is directly connected to an input end of the reduction gearbox 24,” and there are no components illustrated or described as being between the turbine engine and reduction gearbox. Id. at 5:28–30 (emphasis added), Fig. 3. The connection between the turbine engine and reduction gearbox shown in Embodiment 1 is more aptly described as being uninterrupted. Thus, this illuminates the meaning of “directly connected.” In view of the above, we ascribe to the term “directly connected” its ordinary and customary meaning as it would have been understood by a person of ordinary skill in the art, and we find that ordinary and customary meaning to require that the turbine engine and reduction gearbox are connected with nothing intervening there-between so that their connection is uninterrupted.” slip op. at 29

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

      “Petitioner’s evidence shows that the Apollo 1 apparatus has two gearboxes and a clutch between its turbine engine and plunger pump, thus the Apollo 1 does not meet the claim limitation “the plunger pump is a plunger pump integrated with a reduction gearbox, the turbine engine is directly connected to an input end of the reduction gearbox integrated on the plunger pump.” Ex. 1001, 6:51–54. Petitioner’s Exhibit 1017 is explained by Mr. Zhang11 as having these two gearboxes and clutch, where at least one of the gearboxes and the clutch forecloses the system from having a single reduction gearbox that is both integrated on a pump and directly connected to a turbine engine. Ex. 2010 ¶¶ 8–12. Petitioner presents no evidence contradicting Mr. Zhang’s understanding of the Apollo 1 configuration and, notably never attempted to explain exactly what is shown in the above-reproduced photograph from its own Exhibit 1017, even when given the opportunity to address Mr. Zhang’s testimony in its Reply. See generally Reply.” slip op. at 50

    Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosureDiscretionary denialcites Phillips · KSR · Graham · Nautilus
    Patents in suitUS 10,865,631
  • PTAB · Aug 12, 2021 · PGR2021-00026 · APJ Jamie T Wisz · PGR · Rehearing

    The Board denied rehearing, leaving institution denied for claims 1–20 because Petitioner did not show error in the priority-support finding or improper burden shifting.

    RulingsRehearing decision
    • RehearingRehearing, deniedDenied

      “II. ANALYSIS Pursuant to 37 C.F.R. § 42.71(d): A party dissatisfied with a decision may file a single request for rehearing without prior authorization from the Board. 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. When reconsidering a decision on institution, we review the decision for an abuse of discretion. 37 C.F.R. § 42.71(c). An abuse of discretion exists where a “decision [i]s based on an erroneous conclusion of law or clearly erroneous factual findings, or . . . a clear error of judgment.” PPG Indus. Inc. v. Celanese Polymer Specialties Co., 840 F.2d 1565, 1567 (Fed. Cir. 1988). A rehearing request is not an opportunity for the requesting party to reargue its case or merely to express disagreement with the underlying decision. Nor is it an opportunity for the moving party to present new arguments that were not in its original submissions.” slip op. at 2

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

      “The ’611 provisional application discloses a first side (8) and a second side (9) of the beveled platform (5)/distal member wherein the first lateral blade (10) and the second lateral blade (11) are “along the sides of said beveled platform.” Ex. 1007, 38. As shown in the annotated figures below, the ’611 provisional application depicts right and left edges, which are the lines/borders between the sides (8, 9) and top of the distal member, wherein these edges extend towards the rearward end from the tip (6). Decision 39–40 (citing Prelim. Resp. 21, 45–46 (citing Ex. 1007, Figs. 1, 3)). Annotated Figures 1 and 3 include added lines and labels indicating the edges of the distal member. Petitioner’s argument appears to hinge on the contention that the beveled nature of the platform prevents it from being an edge. See Req. Reh’g 4, 6. However, Petitioner provides no persuasive arguments or evidence for this contention. We understand that Petitioner disagrees with the Board’s assessment, but simple disagreement is not effective to demonstrate an abuse of discretion.” slip op. at 5

    • Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateDecided for patent owner

      “The ’611 provisional application discloses a first side (8) and a second side (9) of the beveled platform (5)/distal member wherein the first lateral blade (10) and the second lateral blade (11) are “along the sides of said beveled platform.” Ex. 1007, 38. As shown in the annotated figures below, the ’611 provisional application depicts right and left edges, which are the lines/borders between the sides (8, 9) and top of the distal member, wherein these edges extend towards the rearward end from the tip (6). Decision 39–40 (citing Prelim. Resp. 21, 45–46 (citing Ex. 1007, Figs. 1, 3)). Annotated Figures 1 and 3 include added lines and labels indicating the edges of the distal member.” slip op. at 5

    • BurdenDecided for patent owner

      “We are not persuaded by Petitioner’s arguments. Contrary to Petitioner’s assertions, Patent Owner’s arguments regarding the claim terms raised by Petitioner were not limited to only showing support in the ’391 patent. In fact, Patent Owner’s Preliminary Response discusses in detail where these claim terms are supported in the ’611 provisional application. See Prelim. Resp. 12–24, 39–41, 43–59. We also disagree with Petitioner’s contention that Patent Owner only provided “conclusory remarks” that the challenged claims were supported by priority applications other than the ’611 provisional. Req. Reh’g 11. For example, the Preliminary Response discusses how the challenged claim terms are supported by U.S. Patent No. 15/207,329 (“the ’329 application”). See Prelim. Resp. 24–27, 61, 63–64. Further, as noted in our Decision, Patent Owner also submitted a claim chart providing exemplary excerpts from the ’611 provisional, the ’329 application, and the ’391 patent to establish support for all elements of several exemplary challenged claims. See Decision 26 n.4 (citing Prelim. Resp., Appx. A). Petitioner has not demonstrated that we improperly shifted the burden to Petitioner. Instead, we concluded that the record before us supported Patent Owner’s contention that the non-disclaimed ’391 patent claims should receive priority to the ’611 provisional application. Decision 42.” slip op. at 8

    § 112 disclosure
    Patents in suitUS 10,786,391
  • PTAB · Jun 11, 2019 · IPR2018-00207 · APJ Frances L Ippolito · IPR · Final written decision

    Claims 1–15 are unpatentable: claims 1, 3–6, 8–11, and 13–15 are anticipated by Thornberg ’983; claims 2, 7, and 12 are obvious over Thornberg ’983 and Karem. The motion to amend is denied.

    RulingsFinal written decision
    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “Patent Owner did not file a Patent Owner Response and has not otherwise disputed Petitioner’s proposed level of skill. See Tr. 77:1–6. We find, based on our review of the complete record, that the evidence of record supports a level of ordinary skill in the art consistent with Petitioner’s definition. Our findings are supported by the level of ordinary skill in the art reflected by the prior art of record and the ’116 patent. See Ex. 1001, 1:36–37 (“This invention relates generally to radio controlled toys such as airplanes and helicopters.”); Ex. 1006, 1:8–10 (“The present invention relates to the control of remotely operated vehicles, and more particularly to a variable reference for the control of a remotely operated vehicle.”), see id. at 3:41–44 (“The system provides for the referencing of vehicle commands based on an operator frame of reference so that control commands provided by the operator remain intuitive and independent of the orientation of the vehicle with respect to the operator.”). Thus, we adopt Petitioner’s proposed level of ordinary skill in the art and apply it to our discussion below.” slip op. at 11

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “Ex. 1006, 5:22–29. We further observe that once the disclosed pitch/roll commands (i.e., command data) are provided to the pitch axis and roll axis transformation functions, the pitch axis transformation 410 and roll axis transformation 412 use transformation equations to determine a transformed pitch stick signal (TPSS) and a transformed roll stick signal (TRSS). See Ex. 1006, 6:17–28. In other words, the flight control computer transforms received command pitch/roll data into TPSS and TRSS commands. In performing this transformation, the pitch axis transformation function 410 and the roll axis transformation function 412 also receive a transformation angle (θ) input. Id. at 5:30–32. Thornberg ’983 teaches that the transformation angle θ is determined based on the true heading of the vehicle as determined by the navigation system 36 and the desired vehicle reference and vehicle reference mode. Id. at 5:31–35. As discussed above, we find that the true heading of the vehicle as determined by navigation system 36 provides motion data generated by a sensor. Thornberg ’983 teaches that the transformations into TPSS and TRSS take into account transformation angle (θ), which Thornberg ’983 teaches is determined based on the true heading (i.e., motion data) of the vehicle and the control data (pitch/roll commands) received from control panel 200 of the remote operator control. See Ex. 1006, 4:29–33, 5:23–25, 5:36–38. Further, in the operator reference mode, the orientation of the operator/remote control upon activation of the operator mode is used as the reference axis (i.e., operator’s coordinate system). Additionally, as noted in the Petition (see Pet. 30–31), Thornberg ’983 teaches a variable operator reference mode in which the operator reference changes based on changes in the orientation of the operator control panel. Ex. 1006, 7:32–35. Based on the disclosure discussed above, we find that the pitch and roll commands received at lines 405, 415 in the operator mode teach command data in “a first coordinate system from a perspective of the remote control device” as recited in claim 1. Moreover, we find that Thornberg ’983 teaches that the received pitch/roll command data is transformed into control data in “a second coordinate system that is from a perspective of the RC aircraft.” Specifically, Thornberg ’983 teaches that the transformation equations 1 and 2 transform the pitch command and roll command based on the difference between the aircraft heading and the reference heading. See Ex. 1066, 7:9–11, 7:19–24. Further, Dr. Hansman testifies that TPSS and TRSS control data control the vehicle in the vehicle’s coordinate system, which is from the perspective of the vehicle. Ex. 1003 ¶ 411. We credit Dr. Hansman’s undisputed testimony in this regard because this testimony is consistent with the disclosure of Thornberg ’983, which teaches, among other things, that “[t]he system provides for the referencing of vehicle commands based on an operator frame of reference so that control commands provided by the operator remain intuitive and independent of the orientation of the vehicle with respect to the operator.” Ex. 1006, 3:41–44.” slip op. at 19

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentableUnpatentable

      “[a] POSITA would have been motivated to modify Thornberg’s control panel 200 to “control” the UAV 100 in a hovering state, i.e., by sending appropriate lift command data to the vehicle when the operator releases the input controls as Karem teaches, in order to facilitate aerial tasks that may involve a hovering state, such as airborne surveillance, inspection, maintenance, and repair, that Thornberg teaches were “well known” uses of UAVs. Ex. 1006, 1:15-24; Ex. 1003, ¶443. Pet. 45. We are persuaded that Petitioner’s rationale and evidence demonstrate by a preponderance of the evidence that claims 2, 7, and 12 would have been obvious in view of Thornberg ’983 and Karem. For example, Petitioner’s arguments are supported by the disclosure of Karem, which teaches a remotely-operated vehicle in a hovering state (Ex. 1008, 7:13–23, 32–39, and Thornberg ’983 teaches remotely operated vehicles include helicopters (Ex. 1006, 1:14–17). Further, Petitioner’s arguments are supported by Dr. Hansman’s undisputed testimony that a POSITA would have been motivated to modify Thornberg ’983’s control panel 200 to control UAV 100 in a hovering state, i.e., by sending appropriate lift command data to the vehicle when the operator releases the input controls as Karem teaches, in order to facilitate aerial tasks that may involve a hovering state, such as airborne surveillance, inspection, maintenance, and repair. Ex. 1003 ¶ 443. This testimony is supported by Thornberg ’983’s teaching that (1) airborne surveillance, inspection, maintenance, and repair were well known uses of UAVs; and (2) remote operation of UAVs apply to remotely operated helicopters. See Ex. 1006, 1:15–24.” slip op. at 29

    • Expert testimonyPetitioner expert creditedOther

      “In the same manner described in the ’116 patent, we find that the orientation of the control panel in Thornberg ’983 indicates the angular displacement (i.e., position data) of the vehicle relative to the operator mode reference axis because the control panel is directed toward the vehicle. Thornberg ’983’s Figure 2 discloses that the control panel is directly facing the remotely operated vehicle, which is nearly identical to placement of the remote control device and RC aircraft in Figure 5 of the ’116 patent. Ex. 1001, 3:67–4:2, Fig. 5; Ex. 1006, Fig. 2.” slip op. at 50

    Patent outcomesUS 9,079,116 unpatentable
    § 102 anticipation§ 103 obviousness§ 112 disclosurecites KSR · Graham
    Patents in suitUS 9,079,116
  • PTAB · Dec 30, 2016 · PGR2015-00018 · APJ Richard E Rice · PGR · Final written decision

    Claims 1–6, 8, and 10–14 are unpatentable as indefinite under § 112(b); the Board did not reach the § 103(a) grounds.

    RulingsFinal written decision
    • Skill levelSkill level patent owner adoptedDecided for patent owner

      “II. ANALYSIS A. Level of Skill in the Art Petitioner contends that a person of ordinary skill in the art (“POSA”) “would have been a person having a general knowledge about and experience with expandable containers, including without limitation balloons, and at least an associate’s degree in science or engineering.” Pet. 15–16 (citing Ex. 1015 ¶¶ 10–13; Ex. 1016 ¶¶ 10–13). Patent Owner responds that “the Board should limit Petitioner’s overly broad definition of a POSA from having an associate’s degree in any science or engineering to having an associate’s degree in mechanical engineering.” See, e.g., PO Resp. 12. According to Patent Owner, “Petitioner’s proposed definition should be limited because the inclusion of persons with an associate’s degree in any science or engineering fails to take into account the scope of the relevant art, which indisputably utilizes mechanical engineering principles.” Id. Upon consideration of the parties’ contentions, we determine that a POSA would have been a person having a general knowledge about and experience with expandable containers, including without limitation balloons, and at least an associate’s degree in mechanical engineering, or the equivalent.” slip op. at 7

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther

      “1. “elastic fastener” In our Institution Decision, we preliminarily determined that the broadest reasonable interpretation consistent with the Specification of the claim term “elastic fastener” is an elastic element for attaching things together. Inst. Dec. 7–8. As neither party proposes any change to our interpretation, and our review of the evidence does not indicate that any change is necessary, we maintain that interpretation.” slip op. at 8

    • Disclosure Requirements (§112) › Definiteness (Nautilus)IndefiniteUnpatentable

      “We determine that the test for indefiniteness that is applied in patent examination and reexamination matters, approved in Packard, should be applied in this post-grant review AIA proceeding, rather than the Nautilus requirement. The different approaches to indefiniteness before the PTO and the courts stem from the distinct roles that the PTO and the courts play in the patent system.12 In AIA proceedings, as in patent examination and reexamination matters, applying the broadest reasonable interpretation standard, coupled with an opportunity to amend the claims, is an approach that is fair to the patent holder and protects the public. See Cuozzo, 136 S. Ct. at 2145–46; Packard, 751 F.3d at 1312–14. This approach serves to ensure precision in patent claims, thereby helping the public to understand the limits of the claims and keeping the rights afforded by patents within their legitimate scope. See Cuozzo, 136 S. Ct. at 2144–45; Packard, 751 F.3d at 1313. Accordingly, among the reasons supporting application of the Packard-approved indefiniteness test in this AIA proceeding are those recognized by the Supreme Court in Cuozzo as supporting use of the broadest reasonable interpretation standard in inter partes review AIA proceedings. See Cuozzo, 136 S. Ct. at 2143–2146. Of these, the most important is the opportunity to amend the claims to correct any ambiguity. See id. at 2145 (“The patent holder may, at least once in the process, make a motion to do just what he would do in the examination process, namely, necessary) that a person of ordinary skill in the art would not consider the claim language unclear.” 12 See Packard, 751 F.3d at 1325 (Plager, J., concurring) (stating that “unlike courts which have a full prosecution record to consider, the prosecution record before the USPTO is in development and not fixed during examination”). amend or narrow the claim.”) (citation omitted); 35 U.S.C. § 326(d); 37 C.F.R. § 42.221. An applicant’s ability to clarify claim language through amendment was a significant reason why the Federal Circuit in Packard approved of the indefiniteness test recited in the MPEP (i.e., a “claim is indefinite when it contains words or phrases whose meaning is unclear”). Packard, 751 F.3d at 1313–14.” slip op. at 18

    • ExcludeMotion to exclude, deniedDenied

      “III. MOTIONS TO EXCUDE In its Motion to Exclude (Paper 57), Patent Owner seeks to exclude Petitioner’s Exhibits 1031 and 1032. Paper 57, 1–3. We deny Patent Owner’s motion, as moot, because we did not consider the referenced exhibits in reaching our decision in this case. In its Motion to Exclude (Paper 59), Petitioner seeks to exclude Patent Owner’s Exhibits 2016–2018, 2020 (¶ 84), 2024, 2025 (¶ 39), 2026 (¶ 39), 2027–2070, 2073, 2074, 2078, and 2085. Paper 59, 1–8. We deny Petitioner’s motion, as moot, because we did not consider the referenced exhibits and paragraphs in reaching our decision in this case.” slip op. at 34

    Patent outcomesUS 9,051,066 unpatentable
    Claim construction§ 103 obviousness§ 112 disclosurecites Nautilus
    Patents in suitUS 9,051,066
  • PTAB · Jul 28, 2016 · CBM2015-00063 · APJ Hyun J Jung · CBM · Final written decision

    Claims 1, 6, 8, 9, 12, 13, 15, 20, 21, 24, and 25 are unpatentable under § 101; claims 1, 6, 9, 15, and 20 are anticipated by Lech; and claims 6, 8, 12, 13, …

    RulingsFinal written decision
    • BurdenDecided for petitioner

      “Decision is issued pursuant to 35 U.S.C. § 328(a) and 37 C.F.R. § 42.73. For the reasons that follow, we determine that Petitioners have shown by a preponderance of the evidence that claims 1, 6, 8, 9, 12, 13, 15, 20, 21, 24, and 25 are unpatentable.” slip op. at 2

    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

      “Patent Owner proposes construing “field” as “computer software field.” Prelim. Resp. 24–33. We see no reason to interpret “fields” as “computer software fields.” We agree with Petitioners that Patent Owner’s proposed construction is circular insofar as the construction includes the entire term being construed. See Pet. Reply 6. Further, as discussed below, even if “fields” were interpreted as “computer software fields,” the complete record persuades us that Petitioners have shown unpatentability of the challenged claims by a preponderance of the evidence. Petitioners propose that the broadest reasonable interpretation of “digital attachment” recited by claim 9 is “information that can be digitized.” Pet. 5 (citing Ex. 1001 ¶¶ 32, 33, 36; Ex. 1003, 11:18–19, 20– 35). For the purposes of this Decision, we need not construe this or any other term expressly. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (holding that only those terms that are in controversy need to be construed, and only to the extent necessary to resolve the controversy).” slip op. at 8

    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPrior construction adoptedDecided for patent owner

      “In the Decision on Institution, we interpreted “unitary data stream” as “transmitted set of information.” Dec. on Inst. 12. Patent Owner states that it “agrees that such definition is the broadest reasonable construction.” PO Resp. 24; see also Pet. Reply 4 (stating “Patent Owner does not dispute that the correct construction of ‘unitary data stream’ for this proceeding is ‘transmitted set of information.’”). Based on our review of the complete record, we do not perceive any reason or evidence that now compels any deviation from this interpretation.” slip op. at 7

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

      “device operatively coupled to a computer network receiving and transferring or transmitting contents of fields of a unitary data stream. Based on the full record before us, we determine that the subject matter of the challenged claims, when considered as a whole, is directed to the abstract idea of transmitting or copying information from a source to a destination. In particular, the complete record persuades us that the idea of transmitting or copying information from a source to a destination represents a disembodied, well-known concept, i.e., a basic building block of human ingenuity and that does not rise beyond the level of an abstract idea. See Content Extraction, 776 F.3d at 1347 (“Applying Mayo/Alice step one, we agree with the district court that the claims of the asserted patent are drawn to the abstract idea of 1) collecting data, 2) recognizing certain data within the collected data set and 3) storing that recognized data in a memory. The concept of data collection, recognition, and storage is undisputedly well-known. Indeed, humans have always performed these functions.”); see also Alice, 134 S. Ct. at 2354 (“[I]n applying the § 101 exception, we must distinguish between patents that claim the ‘“buildin[g] block[s]”’ of human ingenuity and those that integrate the building blocks into something more”) (quoting Mayo, 132 S. Ct. at 1303). We also agree with Petitioners that the” slip op. at 28

    Patent outcomesUS 7,178,020 unpatentable
    Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnesscites Alice · Bilski
    Patents in suitUS 7,178,020
  • PTAB · Jul 28, 2016 · CBM2015-00062 · APJ Hyun J Jung · CBM · Final written decision

    Claims 27, 30, 36, 42–45, and 49–52 are unpatentable under § 101; claims 27, 42–45, and 49–52 under § 102; and claims 30, 36, and 42 under § 103.

    RulingsFinal written decision
    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionNo construction neededDecided for petitioner

      “In the Decision on Institution, we interpreted “unitary data stream” as “transmitted set of information.” Dec. on Inst. 12. Patent Owner states that it “agree[s] that such definition is the broadest reasonable construction.” PO Resp. 24; see also Pet. Reply 5 (stating “Patent Owner does not dispute that the correct construction of ‘unitary data stream’ for this proceeding is ‘transmitted set of information’”). Based on our review of the complete record, we do not perceive any reason or evidence that now compels any deviation from this interpretation. Patent Owner further proposes interpreting “fields” as “computer software fields.” PO Resp. 24–33. Petitioners dispute the proposed interpretation of “fields.” Reply 4–7. We see no reason to interpret “fields” as “computer software fields.” We agree with Petitioners that Patent Owner’s proposed construction is circular insofar as the construction includes the entire term being construed. See Pet. Reply 5. Further, as discussed below, even if “fields” were interpreted as “computer software fields,” the complete record persuades us that Petitioners have shown unpatentability of the challenged claims by a preponderance of the evidence. Petitioners also propose interpreting “identities” recited by claims 42– 45 and 50–52 as “labels” (Pet. 4), and Patent Owner states that it “does not dispute that such definition is the broadest reasonable construction” (PO Resp. 24). For the purposes of this Decision, we need not expressly construe this or other claim terms further. 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.’”). III.” slip op. at 8

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

      “simply ask whether the claims involve a patent-ineligible concept” and that “some improvements in computer-related technology when appropriately claimed are undoubtedly not abstract, such as a chip architecture, an LED display, and the like.” Enfish, 882 F.3d at 1335. Therefore, the Federal Circuit “f[ou]nd it relevant to ask whether the claims are directed to an improvement to computer functionality versus being directed to an abstract idea” and that the “first step in the Alice inquiry . . . asks 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.” Id. at 1335–1336. Here, claim 27 recites “a digital device,” “first and second networked components,” and a method that includes receiving and parsing a data stream with N fields and routing portions of the N fields to networked components. Claim 42 recites a “server” that receives a file with identifiable fields and copies a subset of the fields to correlated fields of a second file. Claim 50 does not expressly require any computers and recites a method that includes receiving a file with identifiable fields and copying a subset of the fields to correlated fields of a second file. The claims do not recite an improvement in computer-related technology, “such as a chip architecture, an LED display, and the like.” See Enfish, 882 F.3d at 1335. Patent Owner’s asserted improvement is “an improvement to data processing performed by a mainframe computer system or similar systems, allowing processing text data with associated digital attachments” (PO Resp. 48), but the focus of the challenged claims is not on “processing text data with associated digital attachments.” The claims instead require receiving data with fields and routing or copying a portion or subset of the fields. The asserted improvement is not an improvement in “computer functionality” or capabilities, but instead, as Patent Owner concedes, “an improvement to data processing performed by a mainframe computer system or similar system.” See PO Resp. 48. As discussed further below, the challenged claims invoke computers merely as a tool. See Enfish, 822 F.3d at 1338 (stating “patent-ineligible claims at issue in other cases . . . recited generalized steps to be performed on a computer using conventional computer activity”); see also Bascom Global Internet Servs., Inc. v. AT&T Mobility LLC, No. 2015-1763, 2016 WL 3514158, at *5 (Fed. Cir. June 27, 2016) (stating that the “Enfish claims, understood in light of their specific limitations, were unambiguously directed to an improvement in computer capabilities”).” slip op. at 30

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

      “Based on our factual findings from the specification of the ’020 patent described above and the full record before us, we determine that the recited “digital device operatively coupled to first and second networked components” can be at least one of a personal computer, legacy computer, network server, or buffer computer. The complete record does not persuade us that the “digital device operatively coupled to first and second networked components” requires more than generic computer components. See Alice, 134 S. Ct. at 2357–58 (explaining computer implementation not enough when “the process could be ‘carried out in existing computers long in use’” or when “the computer implementation was purely conventional”). Considering the full record before us, for the reasons explained above, we determine that claim 27 recites well-known, routine, conventional activities previously known to the industry and generic computer components. Alice, 134 S. Ct. at 2359 (“Taking the claim elements separately, the function performed by the computer at each step of the process is ‘[p]urely conventional.’”). When considered as an ordered combination, we determine that claim 27 adds nothing that is not already present when its elements are considered individually. See Alice, 134 S. Ct. at 2359 (“Considered ‘as an ordered combination,’ the computer components of petitioner’s method ‘ad[d] nothing . . . that is not already present when the steps are considered separately.”); OIP Techs., Inc. v. Amazon.com, Inc., 788 F.3d 1359, 1363 (Fed. Cir. 2014) (“[R]elying on a computer to perform routine tasks more quickly or more accurately is insufficient to render a claim patent eligible.”); Bancorp, 687 F.3d at 1278 (explaining that a computer “employed only for its most basic function ... does not impose meaningful limits on the scope of those claims”); cf. DDR Holdings, 773 F.3d at 1258–59 (finding a computerimplemented method patent eligible where the claims recite a specific manipulation of a general-purpose computer such that the claims do not rely on a “computer network operating in its normal, expected manner”). Claim 27 “merely recite[s] the abstract idea . . . with the requirement . . . to perform it on a set of generic computer components”; does not “recite a specific, discrete implementation of the abstract idea”; and cannot “be read to ‘improve[] an existing technological process.’” See Bascom, 2016 WL 3514158, at *7. As discussed above, claim 27 recites well-known, routine, conventional activities that are arranged conventionally and generically. See id. at *6 (stating that “an inventive concept can be found in the non-conventional and non-generic arrangement of known, conventional pieces”).” slip op. at 40

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “receiving a unitary data stream including N fields of data,” Petitioners cite column 5, line 59 to column 6, line 16 and Figure 2 of Lech, not just column 6, lines 11–16. Pet. 59–60. In the cited portion, we find that Lech discloses that “scanner 210 stores all of the information extracted off of hard copy document 100 in the scanner memory 220” and that the “extracted information is stored in two forms . . . as image information [and] textual information recognized on the hard copy document 100 by, for example, employing standard character recognition software.” Ex. 1009, 5:66–6:7. We find that the portion of Lech cited by Petitioners supports their contention that the “exemplary hard copy document 100 of Fig. 2 is preferably scanned in and fields of information on it are recognized using standard optical character recognition software.” Pet. 59–60 (citing Ex. 1001 ¶ 64; Ex. 1009, 5:66–6:8). We also agree with Petitioners that the stored information is sent to computer 230. The portion of Lech cited by Petitioners discusses first and second operational modes and explicitly states that, in the second mode of operation, the information is displayed on computer 230. Ex. 1009, 6:13–16. The first and second operational modes appear to differ by how much of the document is scanned, not where the scanned information is sent. See id. at 6:63–67 (describing that “[t]hese second modes of operation are efficient for small businesses . . . since the user does not necessarily have to store all of the information that appears on the hard copy document”). Moreover, we find that Lech expressly discloses that the “information from scanner memory 220 or main memory 250 is transmitted to computer 230.” Ex. 1009, 5:1–2. Petitioners provide an asserted understanding of Lech by one of ordinary skill in the art in an “Overview of Lech,” and Petitioners cite this same portion of Lech to assert that the “document image, the extracted textual information, or both are then sent to a computer.” Pet. 56–57 (citing Ex. 1001 ¶ 52). We, thus, find that Lech discloses that the output from the scanner is sent to the computer 230 and that the output includes information in fields, as shown in Figure 2 of Lech, and therefore, discloses “receiving a unitary data stream including N fields of data,” as required by claim 27. slip op. at 55

    Patent outcomesUS 7,178,020 unpatentable
    Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnesscites Alice · Bilski
    Patents in suitUS 7,178,020
  • 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
  • PTAB · Mar 30, 2016 · CBM2014-00187 · APJ Hyun J Jung · CBM · Final written decision

    Claims 27, 30, 36, 42, 43, 45, and 50–52 are unpatentable under § 101; claim 27 is also anticipated by Toy under § 102. The motion to amend is granted.

    RulingsFinal written decision
    • BurdenFwd all claims unpatentableUnpatentable

      “Supreme Court clarified the process for analyzing claims to determine whether claims are directed to patent-ineligible subject matter. In Alice, the Supreme Court applied the framework set forth previously in Mayo Collaborative Services v. Prometheus Laboratories, Inc., 132 S. Ct. 1289 (2012), “for distinguishing patents that claim laws of nature, natural phenomena, and abstract ideas from those that claim patent-eligible applications of these concepts.” Alice, 134 S. Ct. at 2355. The first step in the analysis is to “determine whether the claims at issue are directed to one of those patent-ineligible concepts.” Id. If they are directed to a patent-ineligible concept, the second step in the analysis is to consider the elements of the claims “individually and ‘as an ordered combination”’ to determine whether there are additional elements that “‘transform the nature of the claim’ into a patent-eligible application.” Id. (quoting Mayo, 132 S. Ct. at 1297, 1298). In other words, the second step is to “search for an ‘inventive concept’––i.e., an element or combination of elements that is ‘sufficient to ensure that the patent in practice amounts to significantly more than a patent upon the [ineligible concept] itself.’” Id. (alteration in original) (quoting Mayo, 132 S. Ct. at 1294). Further, the “prohibition against patenting abstract ideas ‘cannot be circumvented by attempting to limit the use of the formula to a particular technological environment’ or adding ‘insignificant post solution activity.”’ Bilski v. Kappos, 561 U.S. 593, 610– 11 (2010) (quoting Diamond v. Diehr, 450 U.S.175, 191–92 (1981)).” slip op. at 22

    • Prior constructionPrior construction adoptedDecided for petitioner

      “Board will interpret claims according to their broadest reasonable construction in light of the specification of the patent in which they appear. See 37 C.F.R. § 42.300(b). In our Decision to Institute, we construed “unitary data stream” to mean a “transmitted set of information.” Dec. on Inst. 13. The parties do not present arguments for another interpretation (see Reply 6), and based on the complete record, we do not perceive any reason or evidence that now compels any deviation from this interpretation.” slip op. at 20

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

      “We agree with Petitioner that Patent Owner’s proposed construction reads a particular embodiment in the Abstract into claim 27, which only requires “a unitary data stream including N fields of data.” See Superguide Corp. v. DirecTV Enter., Inc., 358 F.3d 870, 875 (Fed. Cir. 2004) (“Though understanding the claim language may be aided by the explanations contained in the written description, it is important not to import into a claim limitations that are not a part of the claim. For example, a particular embodiment appearing in the written description may not be read into a claim when the claim language is broader than the embodiment.”). “Parsing” does not seem to appear in the specification of the ’020 patent. We thus decline to accept Patent Owner’s proposed construction and give “parsing the unitary data stream” its ordinary and customary meaning.” slip op. at 21

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

      “Patent Owner also proposes that the broadest reasonable interpretation of “field” in view of the specification is a “computer software field” with citations to the specification. PO Resp. 15–24 (citing Ex. 1001, 8:32–37, 9:59–10:12, 10:19–35, 11:53–63, 13:40–14:20, 14:29–38, 15:26–47, 16:26– 32, 17:3–11, 18:5–18, 18:50–19:3, 19:61–20:6, 24:19–31, 24:38–43). Petitioner argues that the plain meaning should be applied. Reply 8. We do not see that the dispute impacts the analysis set forth in the Decision, so we need not decide between the two competing proposals. 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 21

    Patent outcomesUS 7,178,020 unpatentable
    Claim construction§ 101 eligibility§ 102 anticipationcites Alice · Mayo · Bilski
    Patents in suitUS 7,178,020
  • PTAB · Mar 30, 2016 · CBM2014-00186 · APJ Hyun J Jung · CBM · Final written decision

    Claims 1, 6, 10-17, and 28-31 are unpatentable under § 101 because they claim an abstract idea without an inventive concept.

    RulingsFinal written decision
    • BurdenDecided for petitioner

      “We have jurisdiction under 35 U.S.C. § 6(c). This Final Written Decision is issued pursuant to 35 U.S.C. § 328(a) and 37 C.F.R. § 42.73. For the reasons that follow, we determine that Petitioner has shown by a preponderance of the evidence that claims 1, 6, 10–17, and 28–31 of the ’768 patent are unpatentable. We also grant the motion to amend and deny the motion to dismiss.” slip op. at 2

    • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted

      “MOTION TO AMEND In its Motion to Amend, Patent Owner moves to amend the ’768 patent by canceling claims 11 and 30. Paper 15, 1; see 35 U.S.C. § 316(d); 37 C.F.R. § 42.121(a)(3) (“A motion to amend may cancel a challenged claim or propose a reasonable number of substitute claims.”). The Motion to Amend does not indicate that Patent Owner’s request to cancel claims 11 and 30 is contingent on the claims being determined to be unpatentable. We, therefore, grant the request.” slip op. at 42

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

      “construction in light of the specification of the patent in which they appear. See 37 C.F.R. § 42.300(b). In our Institution Decision, we did not need to construe any term expressly. Patent Owner proposes that the broadest reasonable interpretation of “field” in view of the specification is a “computer software field” with citations to the specification and claim 1. PO Resp. 14–15 (citing Ex. 1001, 10:6–10, 12:66–13:38, 15:57–64, 17:62–66, 28:5–21). Petitioner argues that the plain meaning should be applied. Reply 6 (citing Ex. 1007, 8). We do not see that the dispute impacts the analysis set forth in the Decision, so we need not decide between the two competing proposals. 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 21

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

      “Claim 1 requires accepting data, generating a first subset of that data, generating a second subset of that data, and transmitting the first and second subsets of data. Ex. 1001, 45:27–46. We determine that the subject matter of the challenged claims, when considered as a whole, is directed to an abstract idea, namely, examining information to extract relevant portions of that information. In particular, the complete record persuades us that the idea of examining information and extracting relevant portions of that information represents a disembodied, well-known concept, a basic building block of human ingenuity and rises to the level of an abstract idea. See Content Extraction and Transmission LLC v. Wells Fargo Bank, N.A., 776 F.3d 1343, 1347 (Fed. Cir. 2014) (“Applying Mayo/Alice step one, we agree with the district court that the claims of the asserted patents are drawn to the abstract idea of 1) collecting data, 2) recognizing certain data within the collected data set, and 3) storing that recognized data in a memory. The concept of data collection, recognition, and storage is undisputedly well-known. Indeed, humans have always performed these functions.”); see also Alice, 134 S. Ct. at 2354 (“in applying the § 101 exception, we must distinguish between patents that claim the ‘“building[g] block[s]”’ of human ingenuity and those that integrate the building blocks into something more”) (quoting Mayo, 132 S. Ct. at 1303).” slip op. at 24

    Patent outcomesUS 7,346,768 unpatentable
    Claim construction§ 101 eligibilitycites Alice · Mayo · Bilski
    Patents in suitUS 7,346,768

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.