• Dental Recycling North America, Inc. v. Solmetex, LLCInstitution denied
  PTAB · Mar 19, 2024 · PGR2023-00055 · APJ Michael A Valek · PGR · Institution

  The Board denied institution because Petitioner did not show it was more likely than not that any challenged claim was unpatentable under the asserted grounds.

  RulingsInstitution decision

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

    “Institution of post-grant review is authorized only when “the information presented in the petition . . . demonstrate[s] that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324; 37 C.F.R. § 42.4. Upon considering the present record, we determine that Petitioner has not satisfied its burden to show that it is more likely than not that any of the challenged claims are unpatentable.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Relying on the testimony of its declarant, Petitioner contends a person of ordinary skill (“POSA”) “would have been an individual with at least a bachelor’s degree in mechanical engineering, or at least 3 years of experience designing or manufacturing vacuums, filters, medical devices, or the related components.” Pet. 22 (citing Ex. 1003 ¶¶ 94–95). Patent Owner does not respond to Petitioner’s contention in its Preliminary Response, but asks its declarant to apply Petitioner’s proposed level of skill in the art in his analysis. See Ex. 2001 ¶ 86. Because Petitioner’s proposed level of ordinary skill in the art appears to be consistent with the cited prior art and is undisputed on this record, we adopt it for purposes of this decision. C. Claim Construction” slip op. at 11

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

    “Petitioner contends that “[a]ll terms of the ’175 patent should be given their plain and ordinary meaning as understood by a POSA,” but does not propose any express claim construction for consideration. See Pet. 22–23. Petitioner further asserts that the preambles of the independent claims are limiting. Id. at 23–25. Patent Owner argues “that claim construction is not necessary at this time,” but urges that “in the event the Board determines that claim construction is necessary, Petitioner’s proposal to construe the preambles of the independent claims as limiting should be rejected.” Prelim. Resp. 65. We need not determine whether the preambles of the independent claims are limiting to reach the outcome in this decision. Accordingly, no express claim construction is necessary here. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”). D. Grounds 1–4 and Petitioner’s Related Priority Challenge” slip op. at 11

  • Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateNot shown unpatentable

    “Based on the record before us, Patent Owner has the better position. It is well settled that the original drawings may themselves be sufficient to provide description for later-filed claims. Vas-Cath, 935 F.2d at 1565 (holding that “drawings alone may provide a ‘written description’ of an invention as required by § 112”). That is the case here with respect to the original figures submitted with the Great-Grandparent application. We agree with Patent Owner and Dr. Garris that original Figures 4A–B and 5B show a flange or “radially protruding structure” configured as in the challenged claims. Ex. 2001 ¶¶ 106–113. Moreover, the original description in the Great-Grandparent application describes “removable retaining pins 13” that “ensure the recycling container,” i.e., container 12 in Figures 4A–B, “does not detach from the air-water separation tank 5 when there is no vacuum in the system.” Ex. 1002, 213 (¶ 92). Based on this description and the depiction of retaining pin 13 in the original Figure 2, a POSA would have understood that the pins engage with the radially protruding structure to hold the container in place as recited in the challenged claims. Ex. 2001 ¶ 114. Petitioner’s argument that the original figures do not depict the radially protruding structure and retaining pins working together to hold the container in place is unpersuasive. Patent Owner has sufficiently demonstrated that a POSA would have understood how the structures in original Figures 2 and 4A interact based on a side-by-side comparison of the same. See Pet. 38–43; Ex. 2001 ¶ 114. Indeed, the applicants made a similar comparison during prosecution, which proved persuasive to the Examiner. Ex. 1002, 87, 98. The Petition provides no reason to doubt that a POSA would understand the original figures and description just as Patent Owner contends. Moreover, contrary to Petitioner’s arguments, the fact that the specification and drawings were amended does not mean that Patent Owner had to add new matter to overcome the Examiner’s rejections. See Pet. 16– 17. In this case, the amendments to the specification during prosecution of the ’175 patent made the operation of the retaining pin and radially protruding structure, as shown by the original figures, even clearer. But that does not mean that the original description was inadequate.” slip op. at 18

  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosure
  Patents in suitUS 11,660,175
• Apple Inc. v. Ald Social LLCInstituted
  PTAB · Mar 18, 2024 · IPR2023-01399 · APJ Phillip A Bennett · IPR · Institution

  The Board instituted IPR of claims 1–16 on all asserted grounds, finding a reasonable likelihood that Wolfe renders claim 1 obvious under § 103.

  RulingsInstitution decision

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

    “review is under 35 U.S.C. § 314. See also 37 C.F.R. § 42.4(a) (2020). To institute an inter partes review, the information presented in the Petition must show “a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a).” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “factors, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citation omitted). The prior art of record also reflects the level of ordinary skill in the art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). The asserted prior art, like the challenged patent, presents high-level schematics and functional descriptions of various system components used in monitoring events and crowd behavior using location-based services. These system components largely include servers, websites, and mobile telephones utilizing wireless technologies, such as Wi-Fi, cellular, and global positioning system (GPS) to communicate and generate location data regarding mobile devices, as well as the use of databases to store historical information related to location-based services. The prior art and the patent provide description of monitoring crowd behavior by tracking the location of groups of mobile devices. Neither the challenged patent nor the asserted” slip op. at 7

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

    “we agree with Petitioner that “[t]he specification does not provide any explicit definition.” Pet. 14. The written description, however, indicates “[a] viral event is defined as occurring when one or more predefined parameter thresholds have been surpassed, as determined in the exemplary embodiment in the Network Monitor 302.” Ex. 1001, 4:45–48. As Petitioner notes, the written description also provides examples of predefined parameter thresholds used by Network Monitor 302 “to determine if the monitored network indicates that a viral event may be occurring or impending.” Ex. 1001, 5:14–16; Pet. 14 (citing Ex. 1001, 5:16–20). Examples of predefined parameter thresholds include an excessive number of wireless devices in an area, excessive use of wireless devices in an area, two highly dense clusters of wireless devices converging at a significant rate of speed, and the difference in the number of wireless devices in an area exceeds a threshold over consecutive time periods. Ex. 1001, 5:15–20, 5:31–35, 5:41–42 (“to assess the number . . . of wireless devices”), 5:55–57; see Pet. 15 (citing Ex. 1001, 5:31–36, 5:51–57). As such, the written description describes parameter thresholds related to number, use, and movement of wireless devices being used to determine whether a viral event may be occurring.” slip op. at 10

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableInstituted

    “institution. On this preliminary record, Petitioner has sufficiently shown that responsive to the network monitor observing a significant aggregation of devices in a particular area, application 322 functions as a crowd risk determinant because the application 322 assesses the needs arising from the aggregation of devices in that area. Ex. 1004, ¶¶ 46. Additionally, although the example provided in Wolfe relates to determining the number of pizza slices needed based on how many devices are in particular location, on this preliminary record, we agree with Petitioner that a person of ordinary skill in the art would have found it obvious to implement a similar risk analysis to determine that police patrols would be needed in a particular area, as taught by Wolfe, based on the determination of crowd’s location, activity, and movement. Id. at 14.” slip op. at 25

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,402,158
• Apple Inc. v. Ald Social, LLCInstituted
  PTAB · Mar 18, 2024 · IPR2023-01398 · APJ Barbara A Benoit · IPR · Institution

  The Board instituted inter partes review of claims 1–14 on all asserted grounds, finding a reasonable likelihood that claim 1 would have been obvious over Wolfe and Pfeffer.

  RulingsInstitution decision

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

    “II. ANALYSIS A. Legal Standards Petitioner bears the burden to demonstrate unpatentability. Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015). At this preliminary stage, we determine whether the information in the Petition shows a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. See 35 U.S.C. § 314(a).” slip op. at 7

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Relying on declaration testimony from Dr. Guy (Ex. 1003), Petitioner asserts that a person of ordinary skill in the art “would have been someone knowledgeable and familiar with the field of crowd analysis and location-based computing” and would have had “at least a bachelor’s degree in computer science/computer engineering, or equivalent training, and approximately two years of experience working in the field of crowd analysis and location-based computing.” Pet. 12 (citing Ex. 1003 ¶¶ 19–21). Petitioner further notes that “[l]ack of work experience can be remedied by additional education, and vice versa.” Id. For purposes of this Institution Decision, we adopt the assessment offered by Petitioner as it is consistent with the challenged patent and the asserted prior art. See In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “agree with Petitioner that “[t]he specification does not provide any explicit definition” for “indication of a viral event.” Pet. 13. The written description, however, indicates “[a] viral event is defined as occurring when one or more predefined parameter thresholds have been surpassed, as determined in the exemplary embodiment in the Network Monitor 302.” Ex. 1001, 4:40–43. As Petitioner notes, the written description also provides examples of predefined parameter thresholds used by Network Monitor 302 “to determine if the monitored network indicates that a viral event may be occurring or impending.” Ex. 1001, 5:9–12; Pet. 13–14 (citing Ex. 1001, 5:9–15). Examples of predefined parameter thresholds include an excessive number of wireless devices in an area, excessive use of wireless devices in an area, two highly dense clusters of wireless devices converging at a significant rate of speed, and the difference in the number of wireless devices in an area exceeds a threshold over consecutive time periods. Ex. 1001, 5:12–14, 5:27–31, 5:35 (“to assess the number . . . of wireless devices”), 5:48–51; see Pet. 14 (citing Ex. 1001, 5:26–31, 5:45–51). As such, the written description describes parameter thresholds related to number, use, and movement of wireless devices being used to determine whether a viral event may be occurring.” slip op. at 10

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

    “4. The Combination of Wolfe and Pfeffer To demonstrate obviousness, Petitioner must provide “some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” KSR, 550 U.S. at 418. More specifically, to prevail, Petitioner must demonstrate by a preponderance of evidence that “a skilled artisan would have had reason to combine the teaching of the prior art references to achieve the claimed invention, and that the skilled artisan would have had a reasonable expectation of success from doing so.” PAR Pharm., Inc. v. TWI Pharm., Inc., 773 F.3d 1186, 1193 (Fed. Cir. 2014). Regarding the required articulate reasoning, Petitioner contends that “[a]lthough Wolfe teaches providing relevant crowd information to police, Wolfe does not provide the details for how to alert and notify the police.” Pet. 24 (citing Ex. 1004 ¶ 14). “Pfeffer, however, fills in Wolfe’s details by specifically teaching techniques for receiving information about crowds, evaluating the information, and alerting first responders when needed,” according to Petitioner. Pet. 24 (citing Ex. 1005, Abstract, ¶¶ 6, 40–41). Petitioner also contends that the combination would provide additional benefits to Wolfe’s system from Pfeffer’s additional features, such as providing “continuous updates to the incident scenario model saved for future use, recommendations for the most effective methods to respond to the incident based on past responses and current trends, and determining if an incident should be elevated based on the number of people involved in the incident.” Pet. 26 (citing Ex. 1003 ¶ 77; Ex. 1005 ¶¶ 28, 77, 85). Regarding the required expectation of success, Petitioner contends that “[a] POSITA would have found the combination of Wolfe and Pfeffer predictable” because they are similar in that “both systems analyze crowd information to identify safety risks.” Pet. 25 (citing Ex. 1003 ¶ 75; Ex. 1004, Abstract, ¶¶ 11, 14; Ex. 1005 ¶ 28). Petitioner further asserts that “[a] POSITA would have had a reasonable expectation of success when combining Wolfe and Pfeffer because [they] are implemented in the same manner,” with both being implemented on servers and with Pfeffer indicating that its techniques could be “any combination of software and/or hardware that is configured to perform one or more tasks.” Pet. 25–26 (citing Ex. 1003 ¶ 78; Ex. 1004 ¶ 70, 74; Ex. 1005 ¶¶ 37, 32). Petitioner also contends “the combination would use known techniques (Pfeffer’s implementation details of an incident response method) to improve a similar system (Wolfe’s crowd detection and incident response system) in the same way (providing crowd details and incident information to first responders so that they may better respond to comprised crowd safety).” Pet. 26–27 (citing Ex. 1003 ¶¶ 77–79). Petitioner’s showing (Pet. 23–27) of articulated reasoning to support” slip op. at 23

  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 9,198,054
• T-Mobile USA v. Dali Wireless, Inc.All claims unpatentable
  PTAB · Mar 5, 2024 · IPR2023-00830 · APJ Sharon Fenick · IPR · Final written decision

  Claims 1–19 are unpatentable: claims 1–5, 8–11, 13–16, 18, and 19 are anticipated by Wu; claims 6, 7, 12, and 17 are obvious over Wu and Sabat-552.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “an educational background in electrical engineering and experience in the design of wireless communication systems,” and “[m]ore particularly, a POSA would be a person with a bachelor’s degree in electrical engineering (or a similar technical degree or equivalent work experience) and at least 3 years of experience working with wireless communication systems.” PO Resp. 13. We found in the Decision on Institution that Patent Owner’s definition was generally consistent with Petitioner’s definition, with the exception of requiring 3 years or more (as opposed to 2 to 3 years) of work experience in wireless communication systems and, for the purpose of institution, we adopted Petitioner’s provided definition for the level of skill of a person of ordinary skill in the art as reasonable and consistent with the prior art. Dec. on Inst. 20–21. The record does not contain further argument or evidence regarding the level of skill of one of ordinary skill in the art, and we again adopt Petitioner’s definition, which does not encompass an open-ended (“at least 3 years”) amount of experience and which is supported by the testimony of Dr. open-ended terminology from Patent Owner’s definition and adopt that definition.” slip op. at 15

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

    “b) Our Conclusion We conclude that the proper construction of “digital representation of a . . . set of radio resources” encompasses user payload data packaged in or combined with RF carrier channels. We further conclude that “digital representation of a . . . set of radio resources” is not limited to and does not necessarily include configuration information that is required to or used to reconfigure remote radio units.” slip op. at 18

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

    “packetize” or “packetizing” as recited in claims 2, 9, and 14. PO Resp. 19– 20; Pet. Reply 5–6. Patent Owner argues that we should construe “packetize” to mean “create data packets that include destination information.” PO Resp. 19–20. Patent Owner argues that this is consistent with how the Board previously interpreted this claim term in the 00571 IPR. PO Resp. 19 (citing Ex. 1017). We do not need to construe “packetizing” because collateral estoppel prevents Patent Owner from arguing that Wu does not disclose “packetizing” as explained below. We also do not need to construe any other terms to resolve the disputes before us. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms ... that are in controversy, and only 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 22

  • PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner

    “When deciding whether issue preclusion applies, we consider whether: (1) a prior action presents an identical issue; (2) the prior action actually litigated and adjudged that issue; (3) the judgment in that prior action necessarily required determination of the identical issue; and (4) the prior action featured full representation of the estopped party. VirnetX Inc. v Apple, Inc., 909 F.3d 1375, 1377 (Fed. Cir. 2018) (citing Stephen Slesinger, Inc. v. Disney Enterprises, Inc., 702 F.3d 640, 644 (Fed. Cir. 2012)). To the extent Petitioner asks us to consider the 01473 IPR institution decision for issue preclusion, we do not. In that decision the Board reached a finding based on the institution standard (showing of a “reasonable likelihood that the petitioner will prevail,” 35 U.S.C. § 314(a)) rather than proof by a preponderance of the evidence, which is before us now (35 U.S.C. § 316(e)). Ex. 1016. Thus, issues before us here were not presented and adjudged in that institution decision. Regarding the 01473 IPR adverse judgment decision, that decision did not require determination of any issues before us, as that decision was based on Patent Owner canceling the challenged claims rather than any determination regarding unpatentability that had been shown by a preponderance of the evidence. Ex. 1014. 2. Collateral Estoppel With Respect to the 00571 IPR We find and determine that the final written decision in the 00571 IPR, and the Federal Circuit’s CommScope decision affirming that decision, satisfies the conditions for applying collateral estoppel because the 00571 discloses materially the same claim limitations7 challenged here, and Patent Owner had full representation throughout the proceedings. Setting aside the factors of issue preclusion for a moment, our reviewing court’s affirmance of our final written decision in CommScope is persuasive authority that supports our prior construction of “packetizing” and Petitioner’s showing that Wu teaches the disputed packetizing limitations under that construction. In addition, issue preclusion prevents Patent Owner from re-litigating the issue of whether Wu teaches materially the same disputed limitation. See Pet. Reply 24; Ex. 1017, 31–34 (final written decision determining obviousness of claims 9, 10, 14, and 16 of the ’473 patent over Wu and Sabat-426); Ex. 1072, 5 (summarizing the final written decision regarding the packetizing limitations), 10–16 (finding no error in the determinations regarding the packetizing limitations).” slip op. at 12

  Patent outcomesUS 10,334,499 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,334,499
• T-Mobile USA v. Dali Wireless, Inc.All claims unpatentable
  PTAB · Mar 5, 2024 · IPR2022-01293 · APJ Sharon Fenick · IPR · Final written decision

  Claims 1–19 are unpatentable: claims 1–5, 8–11, 13–16, 18, and 19 as anticipated by and obvious over Wu; claims 6, 7, 12, and 17 as obvious over Wu and Sabat-552.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner

    “whether: (1) a prior action presents an identical issue; (2) the prior action actually litigated and adjudged that issue; (3) the judgment in that prior action necessarily required determination of the identical issue; and (4) the prior action featured full representation of the estopped party. VirnetX Inc. v Apple, Inc., 909 F.3d 1375, 1377 (Fed. Cir. 2018) (citing Stephen Slesinger, Inc. v. Disney Enterprises, Inc., 702 F.3d 640, 644 (Fed. Cir. 2012)).” slip op. at 12

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “would have a bachelor’s degree in electrical engineering (or equivalent field) with 2–3 years of work experience in wireless communications.” Pet. 21 (citing Ex. 1003 ¶¶ 20–22). Patent Owner argues that one of ordinary skill in the art “would have an educational background in electrical engineering and experience in the design of wireless communication systems,” and “[m]ore particularly, a POSA would be a person with a bachelor’s degree in electrical engineering (or a similar technical degree or equivalent work experience) and at least 3 years of experience working with wireless communication systems.” PO Resp. 13. We found in the Decision on Institution that Patent Owner’s definition was generally consistent with Petitioner’s definition, with the exception of requiring 3 years or more (as opposed to 2 to 3 years) of work experience in wireless communication systems and, for the purpose of institution, we adopted Petitioner’s provided definition for the level of skill of a person of ordinary skill in the art as reasonable and consistent with the prior art. Dec. on Inst. 20–21. The record does not contain further argument or evidence regarding the level of skill of one of ordinary skill in the art, and we again adopt Petitioner’s definition, which does not encompass an open-ended (“at least 3 years”) amount of experience and which is supported by the testimony of Dr.” slip op. at 15

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

    “a . . . set of radio resources” encompasses user payload data packaged in or combined with RF carrier channels. We further conclude that “digital representation of a . . . set of radio resources” is not limited to and does not necessarily include configuration information that is required to or used to reconfigure remote radio units.” slip op. at 18

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

    “We do not need to construe “packetizing” because collateral estoppel prevents Patent Owner from arguing that Wu does not disclose “packetizing” as explained below. We also do not need to construe any other terms to resolve the disputes before us. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms ... that are in controversy, and only 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 22

  Patent outcomesUS 10,334,499 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,334,499
• AT&T Corp. / AT&T Communications LLC et al. v. Dali Wireless, Inc.All claims unpatentable
  PTAB · Mar 5, 2024 · IPR2023-00818 · APJ Sharon Fenick · IPR · Final written decision

  Claims 1–19 are unpatentable as obvious over Wu alone or Wu with Sabat-552.

  RulingsFinal written decision

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

    “institution of inter partes review of claims 1–19 (“the challenged claims”) of U.S. Patent No. 10,334,499 B2 (Ex. 1001, “the ’499 patent”). Dali Wireless Inc. (“Patent Owner”) filed a Preliminary Response (Paper 7, “Prelim. Resp.”). Ericsson filed a Preliminary Reply (Paper 9). We determined that the information presented in the Petition established that there was a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims, and therefore we instituted this proceeding on March 9, 2023, as to all challenged claims and all grounds of unpatentability. Paper 11 (“Dec. on Inst.”). We granted a request in IPR2023-00831 by AT&T Corp., AT&T Communications LLC, AT&T Services, Inc., AT&T Mobility LLC, and AT&T Mobility II LLC to be joined as a Petitioner in this proceeding. Paper 19. After a joint request of Patent Owner and Ericsson, we terminated the proceeding as to Ericsson, leaving AT&T Corp., AT&T Communications LLC, AT&T Services, Inc., AT&T Mobility LLC, and AT&T Mobility II LLC (“Petitioner”) as the lead (and sole) petitioner in this proceeding. Papers 16, 17, 20.” slip op. at 2

  • PTAB / AIA Trials › §315(e) estoppelEstoppel does not applyDecided for petitioner

    “When deciding whether issue preclusion applies, we consider whether: (1) a prior action presents an identical issue; (2) the prior action actually litigated and adjudged that issue; (3) the judgment in that prior action necessarily required determination of the identical issue; and (4) the Apple, Inc., 909 F.3d 1375, 1377 (Fed. Cir. 2018) (citing Stephen Slesinger, Inc. v. Disney Enterprises, Inc., 702 F.3d 640, 644 (Fed. Cir. 2012)). To the extent Petitioner asks us to consider the 01473 IPR institution decision for issue preclusion, we do not. In that decision the Board reached a finding based on the institution standard (showing of a “reasonable likelihood that the petitioner will prevail,” 35 U.S.C. § 314(a)) rather than proof by a preponderance of the evidence, which is before us now (35 U.S.C. § 316(e)). Ex. 1004. Thus issues before us here were not presented and adjudged in that institution decision. Regarding the 01473 IPR adverse judgment decision, that decision did not require determination of any issues before us, as that decision was based on Patent Owner canceling the challenged claims rather than any determination regarding unpatentability that had been shown by a preponderance of the evidence. Ex. 1005.” slip op. at 10

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The record does not contain further argument or evidence regarding the level of skill of one of ordinary skill in the art, and we again adopt Petitioner’s definition, which does not encompass an open-ended (“at least 3 years”) amount of experience and which is supported by the testimony of Dr. Houh. We would reach the same conclusions if we were to remove the open-ended terminology from Patent Owner’s definition and adopt that definition.” slip op. at 14

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

    “a . . . set of radio resources” is not limited to and does not necessarily include configuration information that is required to or used to reconfigure remote radio units. As Petitioner argues, there does not appear to be any indication in the specification and other intrinsic evidence that “digital representation” should be given more than its ordinary meaning, or that an underlying construction of “radio resources” would not be applied to this claim term, which explicitly includes “radio resources.” Pet. Reply 9–10 (citing Ex. 1001, representation” in the specification of the ’499 patent). Our construction is further supported by the language of the claims, which requires that each “set of radio resources” is “for transmission at an antenna of the first remote unit.” Ex. 1001, 14:17–19, 14:22–24, 15:3–5, 15:8–10, 16:6–8, 16:11–13. With respect to the “digital representation” of “set[s] of radio resources,” the specification of the ’499 patent describes that in the downlink (base station to DRU antenna) path for data, RF signals received at the DAU from base station(s), are down-converted, digitized, and further processed resulting in “independently serialized, parallel data streams” that are delivered to DRUs. Ex. 1001, 4:63–5:12. Petitioner contends that this description of delivery of a digitized version of an RF signal to DRUs describes the sending/transmission of a digital representation of the radio. Pet. 9–10. While Patent Owner appears to argue that a “digital representation” of a radio resource would be only an “identifier” of, e.g., an RF carrier (PO Resp. 18), this does not appear to be supported by the specification or the cited testimony of Dr. Chrissan. We do not see a reason to relate “digital representation of . . . a set of radio resources” in the claims to the description in the ’499 patent specification of the remote configuration of DRU parameter settings via the DAU, including detecting or determining radio resources assigned to a DRU and configuring the DRU, turning on and off individual carriers transmitted and received by a DRU. PO Resp. 16–18 (citing Ex. 1001, 4:50–62, 6:31–44, 7:44–50, 12:15–39, 12:58–13:2). No cited portion of the specification describes these signals sent from a DAU to control a DRU as digital representations of a set of radio resources. While Patent Owner cites, in support, Dr. Chrissan’s declaration, Dr. Chrissan does” slip op. at 16

  Patent outcomesUS 10,334,499 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,334,499
• AT&T Corp. / AT&T Communications LLC et al. v. Dali Wireless, Inc.All claims unpatentable
  PTAB · Mar 5, 2024 · IPR2022-01419 · APJ Sharon Fenick · IPR · Final written decision

  Claims 1–19 are unpatentable as obvious over Wu alone or Wu with Sabat-552.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(e) estoppelEstoppel does not applyDecided for petitioner

    “When deciding whether issue preclusion applies, we consider whether: (1) a prior action presents an identical issue; (2) the prior action actually litigated and adjudged that issue; (3) the judgment in that prior action necessarily required determination of the identical issue; and (4) the Apple, Inc., 909 F.3d 1375, 1377 (Fed. Cir. 2018) (citing Stephen Slesinger, Inc. v. Disney Enterprises, Inc., 702 F.3d 640, 644 (Fed. Cir. 2012)).” slip op. at 10

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We found in the Decision on Institution that Patent Owner’s definition was generally consistent with Petitioner’s definition, with the exception of requiring 3 years or more (as opposed to 2 to 3 years) of work experience in wireless communication systems and, for the purpose of institution, we adopted Petitioner’s provided definition for the level of skill of a person of ordinary skill in the art as reasonable and consistent with the prior art. Dec. on Inst. 8–9. The record does not contain further argument or evidence regarding the level of skill of one of ordinary skill in the art, and we again adopt Petitioner’s definition, which does not encompass an open-ended (“at least 3 years”) amount of experience and which is supported by the testimony of Dr. Houh. We would reach the same conclusions if we were to remove the open-ended terminology from Patent Owner’s definition and adopt that definition.” slip op. at 14

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

    “b) Our Conclusion We conclude that the proper construction of “digital representation of a . . . set of radio resources” is not limited to and does not necessarily include configuration information that is required to or used to reconfigure remote radio units.” slip op. at 16

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

    “We do not need to construe “packetizing” because collateral estoppel prevents Patent Owner from arguing that Wu does not disclose “packetizing” as explained below. We also do not need to construe any other terms to resolve the disputes before us. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms ... that are in controversy, and only 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 19

  Patent outcomesUS 10,334,499 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,334,499
• Maplebear Inc. D/B/A Instacart v. Consumeron, LLCAll claims unpatentable
  PTAB · Feb 29, 2024 · IPR2022-01357 · APJ Carl M Defranco · IPR · Final written decision

  Claims 1, 2, 4, 6, 9, 10, 14–17, 21, 22, and 24–26 are unpatentable as obvious over the asserted combinations of Park, Kim, Hileman, Pugliese, and Mault.

  RulingsFinal written decision

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

    “does not equate an “acquisition request” exclusively with a shopping or purchase request. See Ex. 3006, 10–11. Rather, the specification repeatedly uses the phrase “purchase or otherwise acquire” to indicate that a delivery agent may acquire goods by means other than purchasing or shopping. See, e.g., Ex. 1001, 5:25–27 (“[T]he user specifies the exact location from which the selected delivery agent is to purchase or otherwise acquire the product, such as a retail store location.”); id. at 7:56–58 (“If the product is approved at 120, the delivery agent will purchase or otherwise acquire the product on behalf of the customer at 121.”); id. at 2:24–28 (“[T]he user provides the service provider with information regarding the type of product desired and the shopping or acquisition location from which the user desires to purchase or otherwise obtain the product.”) (emphases added). Consumeron’s argument that the specification “uses the word ‘or’ to refer to things that are synonymous to each other” is not persuasive. See PO Resp. 10; see also PO Sur-Reply 3–4 (essentially same). As noted above, the specification uses the phrase “purchase or otherwise acquire.” Ex. 1001, 5:25–27, 7:56–58 (emphasis added); see also id at 2:24–28 (similar). By including the adverb “otherwise,” the specification makes clear that purchase and acquire are not used synonymously, but rather that acquiring is broader and encompasses other ways of obtaining a product. See Ex. 1039, 1 (“otherwise” means “in a different way or manner”). Indeed, the specification unequivocally describes instances where the delivery agent acquires a product without purchasing or shopping for it. For instance, the specification explains that the customer may “pre-purchase[]” goods such that the customer requests simply that the delivery agent “pick-up” of the goods: [T]he customer has the option of paying the retailer or seller directly, in which case the customer will only be billed for the pick-up and delivery services provided. . . . If pre-purchased by the customer, the delivery agent obtains a receipt showing proof of pre-payment by the customer. Id. at 8:15–23 (emphases added). Even more explicitly, the specification states that, “although discussed in the context of a customer who wishes to purchase a product, it should be understood that system 10 may be utilized to schedule both pick-ups and delivery of any type of goods, including free goods. Id. at 10:40–44 (emphasis added). Those disclosures collectively indicate that a delivery agent can fulfill an acquisition request without necessarily shopping for or purchasing goods. Consumeron attempts to distinguish those descriptions, urging that they refer to an “alternative” embodiment that “does not expand the meaning of the term ‘acquisition request’ beyond its ordinary meaning.” PO Sur- Reply 4. But that argument is premised on an incorrect assumption that the ordinary meaning is limited to purchasing or shopping. Here, nothing in the intrinsic record suggests that the term “acquisition request” excludes the specification’s embodiments where “pre-purchased” or “free” goods are only in need of “pick-up.” To the contrary, as noted above, the specification repeatedly states the delivery agent may “otherwise acquire” goods without purchasing them, thereby, indicating that the agent can fulfill an acquisition request without necessarily shopping for the goods on the customer’s behalf. See Ex. 1001, 5:25–27, 7:56–58.” slip op. at 8

  • Prior constructionPrior construction adoptedDecided for petitioner

    “We previously construed the term “acquisition request” in the related 865 IPR to encompass “not only a request for an agent to shop for and purchase goods for delivery to a customer, but also to encompass a request for a delivery agent to simply pick up and deliver goods that have been prepurchased by the customer.” See Ex. 3006, 9–11 (granting institution in conjunction with construing “acquisition request”). As noted above in Section I.A (“Related Matters”), the 865 IPR centers on the ’465 patent, whose lineage derives from the same application—the ’867 application—as the ’835 patent challenged here. Compare Ex. 1001, 1:7–15 (referencing Appl. No. 12/711,867), with Ex. 3005, code (63) (also referencing Appl. No. 12/711,867). Indeed, the ’835 and ’465 patents share essentially identical specifications and figures. Thus, based on the final record before us (as discussed below) and consistent with our prior construction in the related 865 IPR, we likewise determine here that Instacart’s construction of “acquisition request” is the more reasonable one. See SightSound Techs., LLC v. Apple Inc., 809 F.3d 1307, 1316 (Fed. Cir. 2015) (“Where multiple patents ‘derive from the same parent application and share many common terms, we must interpret the claims consistently across all asserted patents.’” (quoting NTP, Inc., v. Research in Motion, Ltd., 418 F.3d 1282, 1293 (Fed. Cir. 2005)). More specifically, as we explained in the 865 IPR, the specification does not equate an “acquisition request” exclusively with a shopping or purchase request. See Ex. 3006, 10–11. Rather, the specification repeatedly uses the phrase “purchase or otherwise acquire” to indicate that a delivery agent may acquire goods by means other than purchasing or shopping. See, e.g., Ex. 1001, 5:25–27 (“[T]he user specifies the exact location from which the selected delivery agent is to purchase or otherwise acquire the product, such as a retail store location.”); id. at 7:56–58 (“If the product is approved at 120, the delivery agent will purchase or otherwise acquire the product on behalf of the customer at 121.”); id. at 2:24–28 (“[T]he user provides the service provider with information regarding the type of product desired and the shopping or acquisition location from which the user desires to purchase or otherwise obtain the product.”) (emphases added).” slip op. at 7

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

    “Although the district court considered “intentional delay” in the course of construing the term “real time,” the district court does not appear to have accepted Consumeron’s narrower construction in that regard. More accurately, the district court stated it “sees no reason that a ‘real-time’ transmission of data could not both involve no inherent delay and permit a system that requires multiple ‘clicks’ to operate.” Ex. 1035, 24 (emphasis added). In addition, the district court quoted from a technical dictionary, which provided: The basic definition of real-time data is that it is data that is not kept or stored, but is passed along to the end user as quickly as it is gathered. It is important to note that real-time data does not mean that the data gets to the user instantly. There may be any number of bottlenecks related to the data collection infrastructure, the bandwidth between various parties, or even just the slowness of the end user’s computer. Real-time data does not promise data within a certain number of microseconds. It just means that the data is not designed to be kept back from its eventual use as it is collected. Id. at 25 (citing “Technopedia”). In other words, the district court contemplated that real-time data includes data that is transmitted as it is gathered despite some inherent delay in transmitting and accessing the data, such as bottlenecks in the infrastructure, slowness of the user’s computer, or “multiple clicks” by the user. With that in mind, we reject Consumeron’s attempt to alter our construction of “real-time” to exclude so-called “intentional delay.” Thus, consistent with the district court and our institution decision, we maintain that “real-time” transmission means “data that is passed along as it is gathered.”” slip op. at 12

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Instacart submits that one skilled in the art would have had “a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of electronic commerce” and that “[l]ack of work experience can be remedied by additional education, and vice versa. Pet. 14 (citing Ex. 1003 ¶ 24). Consumeron responds that one skilled in the art would have been “someone with a background in electrical engineering, computer science, or the like,” but that “industry experience can make up for a lack of technical training, and more education can make up for a lack of industry experience.” PO Resp. 9 (citing Ex. 2016 ¶¶ 17–20). 1 WO 01/11523 A1, published Feb. 15, 2001 (Ex. 1005) (“Park”). 2 Certified translation of KR2003-0085802, published Nov. 7, 2003 (Ex. 1006); corrected certified translation of Figure 2 (Ex. 1038); and original Korean language version (Ex. 1007) (collectively, “Kim”). 3 US 2003/0040944 A1, published Feb. 27, 2003 (Ex. 1009) (“Hileman”). 4 US 2002/0072974 A1, published June 13, 2002 (Ex. 1010) (“Pugliese”). 5 US 2002/0027164 A1, published Mar. 7, 2002 (Ex. 1016) (“Mault”). We discern no material difference between the levels of skill in the art espoused by the parties. Nor does Consumeron’s expert. See Ex. 2016 ¶ 20 (“Petitioner’s definition of a POSITA is not materially different from my definition.”). Accordingly, we adopt the level of skill in the art as defined by Instacart.” slip op. at 6

  Patent outcomesUS 10,628,835 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 10,628,835
• Maplebear Inc. D/B/A Instacart v. Consumeron, LLCAll claims unpatentable
  PTAB · Feb 29, 2024 · IPR2022-01356 · APJ Carl M Defranco · IPR · Final written decision

  Claims 1, 4, 5, 8, 9, and 13–17 are unpatentable as obvious under § 103(a) over the grounds based on Park and Kim, with Hileman or Pugliese for specified dependent claims.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We discern no material difference between the levels of skill in the art espoused by the parties. Nor does Consumeron’s expert. See Ex. 2016 ¶ 20 (“Petitioner’s definition of a POSITA is not materially different from my definition.”). Accordingly, we adopt the level of skill in the art as defined by Instacart.” slip op. at 7

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

    “More specifically, as we explained in the 865 IPR, the specification does not equate an “acquisition request” exclusively with a shopping or purchase request. See Ex. 3006, 10–11. Rather, the specification repeatedly uses the phrase “purchase or otherwise acquire” to indicate that a delivery agent may acquire goods by means other than purchasing or shopping. See, e.g., Ex. 1001, 4:58–60 (“[T]he user specifies the exact location from which the selected delivery agent is to purchase or otherwise acquire the product, such as a retail store location.”); id. at 7:7–9 (“If the product is approved at 120, the delivery agent will purchase or otherwise acquire the product on behalf of the customer at 121.”); id. at 2:9–12 (“[T]he user provides the service provider with information regarding the type of product desired and the shopping or acquisition location from which the user desires to purchase or otherwise obtain the product.”) (emphases added).” slip op. at 8

  • Prior constructionPrior construction adoptedDecided for petitioner

    “course of construing “real time,” the district court does not appear to have accepted Consumeron’s narrower construction in that regard. More accurately, the district court stated it “sees no reason that a ‘real-time’ transmission of data could not both involve no inherent delay and permit a system that requires multiple ‘clicks’ to operate.” Ex. 1035, 24 (emphasis added). In addition, the district court quoted from a technical dictionary, which provided: The basic definition of real-time data is that it is data that is not kept or stored, but is passed along to the end user as quickly as it is gathered. It is important to note that real-time data does not mean that the data gets to the user instantly. There may be any number of bottlenecks related to the data collection infrastructure, the bandwidth between various parties, or even just the slowness of the end user’s computer. Real-time data does not promise data within a certain number of microseconds. It just means that the data is not designed to be kept back from its eventual use as it is collected. Id. at 25 (citing “Technopedia”). In other words, the district court contemplated that real-time data includes data that is transmitted as it is gathered despite some inherent delay in transmitting and accessing the data, such as bottlenecks in the infrastructure, slowness of the user’s computer, or “multiple clicks” by the user. With that in mind, we reject Consumeron’s attempt to alter our construction of “real-time” to exclude so-called “intentional delay.” Thus, consistent with the district court and our institution decision, we maintain that “real-time” transmission means “data that is passed along as it is gathered.” 3. “mobile delivery agent system” In our institution decision, we adopted a construction of “mobile delivery agent system” consistent with the way the term was construed in the Delaware action, namely, “a mobile system that includes at least a device to capture video or still images and a device set up to communicate with a remote server.” See Inst. Dec. 4–5 (citing Ex. 1034, 1; Ex. 1035, 13–17). Neither party disputes that construction. See PO Resp. 12 (adopting our construction); Pet. Reply 1–7 (disputing only the meaning of other claim terms). Thus, we maintain our construction as stated above.” slip op. at 12

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

    “Again, we disagree with Consumeron. As Instacart points out, Park’s system and method is not limited to one-hour delivery. See Pet. Reply 19. To the contrary, Park teaches that items can be “delivered within the hour or within a customer specified delivery window” exceeding an hour. Ex. 1005, Abstract (emphasis added), 20:9–12 (describing “processing orders for deferred delivery (i.e. those not required to be delivered in the next hour)” (emphasis added)); see also Ex. 1044 ¶ 29. Moreover, while Park places some emphasis on delivery time, it also explains that its goal is to promote customer satisfaction. See Ex. 1005, 30:16–18 (increasing “dispatch efficiency and customer satisfaction”), 34:5–7 (resequencing delivery “to ensure 100% customer satisfaction”). In that regard, the reason that Instacart articulates for combining Park and Kim dovetails with Park’s objective of improving customer satisfaction by ensuring the product to be delivered is acceptable to the customer. See Ex. 1044 ¶ 65 (“[A] POSITA would have understood that a customer ordering goods would care little if an unacceptable product was delivered quickly.”).” slip op. at 28

  Patent outcomesUS 8,244,594 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 8,244,594
• Maplebear Inc. D/B/A Instacart v. Consumeron, LLCAll claims unpatentable
  PTAB · Feb 29, 2024 · IPR2022-01358 · APJ Michael A Valek · IPR · Final written decision

  Claims 1–5, 8, 9, 12, 14, 18, 19, and 21–28 are unpatentable as obvious over the four asserted combinations of Park and Kim, with Hileman, Mault, or Pugliese where specified.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner offers a similar description, asserting that a POSITA “is someone with a background in electrical engineering, computer science or the like” and that either experience or training can make up for a lack of the other. Resp. 9–10 (citing Ex. 2016 ¶¶ 17–20). We adopt Petitioner’s definition of the level of ordinary skill in the art. This definition is supported by the record (Ex. 1003 ¶ 24) and consistent with the disclosure in the ’067 patent and the references cited in the Petition. Patent Owner’s definition is “not materially different” from Petitioner’s definition. See Ex. 2016 ¶ 20 (Patent Owner’s declarant acknowledging such). Thus, our analysis and findings would be the same under either sides’ proposal.” slip op. at 8

  • Prior constructionPrior construction adoptedDecided for petitioner

    “In the institution decision, we agreed with and applied the same MDAS construction adopted by the district court in the Delaware litigation. Dec. 12–14. That is, a “mobile delivery agent system” is “a mobile system that includes at least a device to capture video or still images and a device set up to communicate with a remote server.” Ex. 1034, 1. To the extent there was any substantive disagreement with this preliminary construction, we invited the parties to present their alternative positions at trial. See Dec. 14. Neither party has done so. See Resp. 13 (applying same MDAS construction); Reply 1–5 (addressing other claim construction issues, but not raising any issue with the MDAS construction). Accordingly, we apply the same construction of “mobile delivery agent system” here. ii. “real-time” The term “real-time” is not recited in the independent claims, but does appear in some of the challenged dependent claims. See Ex. 1001, 10:8– 14:16 (claims 14 and 18). In the institution decision, we agreed with and applied the same construction adopted by the district court in the Delaware litigation. Dec. 14–15. That is, that “real-time” has its ordinary meaning, which is “data that is passed along as it is gathered.” Ex. 1034, 2. Neither party has proposed an alternative construction. See Resp. 13 (applying same “real-time” construction); Pet. 14 (asserting that “the terms of the Challenged Claims should be given their ordinary and customary meaning”). Accordingly, we apply the same construction of “real-time” here.” slip op. at 8

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

    “We agree with Petitioner. Contrary to Patent Owner’s assertions, the Specification does not exclusively equate an “acquisition request” with a shopping or purchase request. See Resp. 10–12. Rather, the Specification repeatedly uses the phrasing “purchase or otherwise acquire” to indicate that a delivery agent may acquire goods by means other than purchasing or shopping. See, e.g., Ex. 1001, 5:4–6 (“[T]he user specifies the exact location from which the selected delivery agent is to purchase or otherwise acquire the product, such as a retail store location.”); id. at 7:24–26 (“If the product is approved at 120, the delivery agent will purchase or otherwise acquire the product on behalf of the customer at 121 and deliver the product.”); id. at 2:15–18 (“[T]he user provides the service provider with information regarding the type of product desired and the shopping or acquisition location from which the user desires to purchase or otherwise obtain the product.”). Patent Owner’s argument that the Specification uses the “word ‘or’ to refer to things that are synonymous to each other” is not persuasive. See Resp. 10; Sur-reply 4 (citing Epic Games, Inc. v. Ingeniosh, LLC, IPR2022- 00202, Paper 29, 18–19 (PTAB May 19, 2023)). As noted above, the Specification uses the phrasing “purchase or otherwise acquire.” Ex. 1001, 5:4–6, 7:24–26 (emphasis added); see also id. at 2:15–18 (similar). By including the adverb “otherwise,” the Specification makes clear that purchase and acquire are not used synonymously, but rather that acquiring is broader and encompasses other ways of obtaining a product. See Ex. 1039, 1 (“otherwise” means “in a different way or manner”).” slip op. at 10

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

    “Petitioner has also articulated a sufficient rationale for combining these elements of Park and Kim. See Pet. 20–23 (citing exhibits). Kim identifies a problem with purchasing a product from a website, i.e., that the product delivered to the customer may not match the images or videos of that product on the website. Ex. 1006, 2. Kim teaches this problem can be overcome by having the delivery service provider operate a MDAS to transmit an image of the actual product in real time to the customer so that after receiving the image the customer can send instructions back to the delivery service provider confirming that is the product they delivered. Id. We credit Dr. Houh’s testimony that, based on these teachings, a POSITA would have been motivated to incorporate those same steps into Park’s system and methodology to “enhance the reliability of the delivery,” “increase customer satisfaction,” and “save[] resources” by preventing the delivery of goods that, upon viewing, the customer might reject. Ex. 1003 ¶¶ 51–56. Moreover, a POSITA would have had a reasonable expectation of success in combining these teachings because Park’s system was already configured to send live video and images to the customer’s computer. Ex. 1003 ¶ 57. Indeed, while Park primarily discusses transmission of video and images of the delivery process to the customer, it expressly teaches that its objective is to “allow customers to interactively view, in real-time, the progress of his order, from reception to compilation to delivery though the route taken by the delivery agent.” Ex. 1005, 4:26–32 (emphasis added). Incorporating Kim’s teachings regarding elements 1.5–1.7 would further this objective, allowing the customer to interactively view images of the actual products compiled for delivery and send instructions back to the delivery agent regarding those products prior to delivery. See Ex. 1003 ¶ 57 (explaining that the combination allows Park’s system to perform the same intended functionality “in a more reliable way”). Accordingly, Petitioner has shown that it would have been obvious to” slip op. at 24

  Patent outcomesUS 10,115,067 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,115,067

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.