• Apple Inc. v. Fintiv, Inc.No claims unpatentable
  PTAB · May 23, 2024 · IPR2023-00398 · APJ George R Hoskins · IPR · Final written decision

  Claims 1–22 were not shown unpatentable as obvious over Dill, Vadhri, and Akashika because Dill was not shown to disclose the claimed Integration Tier Limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We adopt Petitioner’s undisputed formulation of ordinary skill in the art as set forth above, because we are satisfied this formulation generally comports with the level of skill necessary to understand and implement the teachings of the ’196 patent and the asserted prior art. We do not adopt Patent Owner’s annotation to Petitioner’s formulation as requiring knowledge of “mobile wallets” specifically, because we determine knowledge of “mobile payment systems and techniques” per Petitioner’s formulation is tied sufficiently to the claims of the ’196 patent to reflect the level of ordinary skill in the pertinent art. At the same time, even if we were to include knowledge of “mobile wallets” in our formulation, it would not materially change our Decision as set forth below. That is, we would still determine Petitioner has not shown by a preponderance of the evidence that Dill discloses the Integration Tier Limitation.” slip op. at 10

  • Expert testimonyNot reached

    “We need not resolve the parties’ dispute as to whether Dr. Houh qualifies as an ordinarily skilled artisan. Even assuming that Dr. Houh possesses, at a minimum, ordinary skill in the art—as we have done in this Decision—we determine Petitioner still fails to show that any of the challenged claims are unpatentable.” slip op. at 12

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

    “The Integration Tier Limitation requires no further construction for purposes of this proceeding. See Pet. Reply 7 (“[N]o specific construction is required.”). The claim clearly specifies that the claimed “web services communication mechanisms” must serve as an interface between the integration tier and (1) the claimed mobile wallet application and, separately, (2) “a plurality of different device types over a plurality of different communication channels.” For purposes of this Decision, we assume that this interface may be direct or indirect. See id. at 6 (asserting that “communication channels that interface, even indirectly, with the ‘web services communication mechanisms’ still interface with the ‘web services communication mechanisms’”).” slip op. at 28

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “However, we find that of those four channels (1)–(4), only the first channel (1) is associated with web interface 137 such that it qualifies as a “communication channel,” as required by claim 1. There is no indication in the Dill disclosures cited by Petitioner that any of the other three channels (2)–(4) are associated with web interface 137. For example, Figure 9 of Dill includes a double-headed arrow to illustrate communication between web interface 137 and transfer options module 145, but Figure 9 does not include any arrows to illustrate communication between web interface 137 and any one or more of IVR interface 136, other interfaces 138, agent system 135, or mobile network 115. See Ex. 1005, Fig. 9. In other words, Petitioner fails to show Dill teaches web interface 137 interfaces with any devices over any of channels (2)–(4), as would be required by Petitioner’s mapping. In the Petition, Petitioner never clearly (or persuasively) addresses this requirement of the claim. Petitioner does contend that transfer options module 145 is coupled to various devices via interfaces 136–138 and exchanges transaction information (see Pet. 25–26; see also Pet. Reply 10– 11), but that contention misses the mark. The salient question is whether Dill’s web interface 137 (i.e., the claimed “web services communication mechanisms”) interfaces with the different device types over the channels, not whether transfer options module 145 (i.e., the claimed “integration tier”) does so.” slip op. at 30

  Patent outcomesUS 10,438,196 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,438,196
• Apple Inc. v. Fintiv, Inc.No claims unpatentable
  PTAB · May 23, 2024 · IPR2023-00399 · APJ Juliet Mitchell Dirba · IPR · Final written decision

  Claims 1–22 were not shown unpatentable under § 103 over Dill, Vadhri, and Akashika because Dill did not teach or render obvious the hardware SIM card and integration tier limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In the Institution Decision, we determined that a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering, computer science, or equivalent training, and approximately two years of work experience in software development with a basic knowledge of accounting” and “working knowledge of mobile payment systems and techniques,” as Petitioner proposes. Inst. Dec. 9 (quoting Pet. 3–4). We stated that “this definition generally comports with the level of skill necessary to understand and implement the teachings of the ’488 patent and the asserted prior art.” Id. (citing Ex. 1003 ¶ 22; Ex. 2001 ¶ 35).” slip op. at 10

  • Expert testimonyPetitioner expert discountedMixed

    “In addition, Petitioner’s reliance on Dr. Houh’s testimony (see Pet. 23–24) is unavailing. Although Dr. Houh agrees with the arguments in the Petition and includes quotes from the cited portions of Dill and Bykov (see Ex. 1002 ¶¶ 95–97), he provides no additional analysis or explanation beyond what was provided in the Petition. As a result, his testimony suffers the same deficiencies as the Petition. Also, we do not credit his conclusion that Dill includes the requisite disclosure (see id. ¶ 97) because he fails to provide sufficient supporting explanation or evidence (see 37 C.F.R. § 42.65(a)). Finally, we note that Petitioner misrepresents Dr. Shamos’s testimony by stating that Dr. Shamos “agrees that if a mobile device executes a mobile wallet over a cellular network, the mobile device has a SIM card for the mobile wallet.” Pet. Reply 22 (emphasis added) (citing Ex. 1022, 29:4–7, 40:9–10). In the cited testimony, Dr. Shamos agrees that mobile devices have SIM cards, but he does not address where a mobile wallet application would be installed. Ex. 1022, 29:4–7, 40:9–10. Thus, contrary to Petitioner’s argument, we determine that Dr. Shamos’s testimony does not support Petitioner’s position.” slip op. at 27

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

    “for the term “hardware SIM card” because the important points are undisputed. In particular, the parties agree that a “hardware SIM card” is a SIM card implemented in hardware rather than software. See Pet. Reply 9 (citing Ex. 1021 ¶ 36); Tr. 40:25–41:2 (Patent Owner’s counsel explaining that the language in its proposed construction was “to differentiate it from a software SIM card”); see also PO Resp. 16, 19 (asserting that the term refers to a specific type of hardware, namely a “chip” or a “smart card”) (citing Ex. 2003 ¶¶ 32–33). The parties also agree that an ordinarily skilled artisan would have known that a “SIM card” is a component in a mobile device involved in identifying and authenticating a user to a mobile network. See Tr. 30:23–31:3 (Petitioner’s counsel stating “a SIM card, just as known in the art . . . would allow the user to be able to access the mobile network” 10 Each page in Exhibit 2021 includes at least two page numbers. For clarity, we refer to the page number of the exhibit (shown in the bottom right corner), and we have adjusted Patent Owner’s citation accordingly. given “the user’s identification information on it”), 39:24–40:2 (Patent Owner’s counsel stating that “I think everyone is in agreement that the critical aspect of what makes a SIM card a SIM card is that it can authenticate a mobile device to a wireless network”). The evidence supports the parties’ understanding. The word “SIM” is an acronym for “subscriber identity module” (see, e.g., Ex. 1001, 6:58–67; Ex. 2021, 5), and the record shows that a SIM is a specific component in a mobile device that is involved in identifying and authenticating a user to a mobile network (see Ex. 2003 ¶¶ 30–31; see also e.g., Ex. 2021, 7 (stating that a SIM’s “primary function” is “to authenticate the subscriber to the network”); Ex. 2025, 3 (describing the SIM)).11 Consequently, we determine that an ordinarily skilled artisan would have understood a “hardware SIM card” to be a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. We do not need to further construe the term, or determine whether the additional requirements proposed by Patent Owner are appropriate, because Petitioner fails to show that the prior art teaches or suggests the claimed “hardware SIM card,” as explained below. See infra § II.D.2.a (analyzing the parties’ substantive contentions).” slip op. at 13

  • BurdenNot shown unpatentable

    “Petitioner has not shown, by a preponderance of the evidence, that Dill discloses “a mobile wallet application installed on a hardware SIM card,” as required by element 1.3B. See Pet. 23–24. In particular, even assuming that Dill teaches installing a mobile wallet application somewhere on a mobile device (see Pet. 23),14 Dill does not teach installing it on a hardware SIM card,15 as specifically required by the claim. Petitioner relies upon paragraph 106 of Dill (see Pet. 23), but that paragraph does not disclose this claim limitation (see Ex. 1005 ¶ 106). In relevant part, that paragraph of Dill simply states: 14 Patent Owner disagrees with this premise, arguing that Dill does not disclose a mobile device that includes a mobile wallet application. See PO Resp. 52–56. We need not resolve that dispute because, even assuming Petitioner’s premise (as we have done in this Decision), Petitioner still fails to show that the claims are unpatentable. 15 As noted above, a “hardware SIM card” is a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. See supra § II.C.1 (addressing meaning of term). It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software. Ex. 1005 ¶ 106 (emphases added). This teaches storing instructions on “other types of machine-readable mediums,” but it fails to teach storing instructions on a hardware SIM card, much less storing Dill’s mobile wallet application there. In short, Dill is silent with respect to this issue, and silence is not disclosure. Notably, Petitioner does not contend (or show) that a mobile wallet application installed on a mobile device would necessarily be installed on a hardware SIM card. See Pet. 23–24; Ex. 1003 ¶¶ 95–97. Indeed, the record indicates that a mobile wallet application installed on a mobile device could instead be installed on a different component. See, e.g., Ex. 1001, 7:1–3, 9:33–35 (identifying device memory as alternate component); Ex. 2021, 5 (describing SIM as the “smaller of two computer chips inside a GSM mobile handset”); cf. Pet. Reply 9 (distinguishing between hardware SIM cards and software ones). Thus, Petitioner fails to show that this claim limitation is inherent in Dill. See PAR Pharm., Inc. v. TWI Pharms., Inc., 773 F.3d 1186, 1196 (Fed. Cir. 2014) (explaining that inherency requires a showing that “the limitation at issue necessarily must be present”).” slip op. at 22

  Patent outcomesUS 9,208,488 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,208,488
• Apple Inc. v. LBT IP I LLCNo claims unpatentable
  PTAB · Dec 15, 2023 · IPR2020-01189 · APJ John A Hudalla · IPR · Remand

  Claims 8, 10, 13, and 15 were not shown unpatentable because Sakamoto discloses only two battery power thresholds, which do not meet the construed multitude limitation.

  RulingsRemand decision

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

    “threshold values” includes GPS signal level thresholds, we start with the words of claim 8. Claim 8 recites a “battery power level monitor” that (1) “measures a power level of the charging unit” and (2) “adjusts a power level applied to location tracking circuitry responsive to one or more signal levels.” Claim 8 further recites that “the power level compris[es] a multitude of threshold values determined by a user or system administrator.” The remainder of claim 8 states the purpose of the “multitude of threshold values,” which is “to intermittently activate or deactivate the location tracking circuitry to conserve power of the charging unit in response to the estimated charge level of the charging unit.” The natural reading of these recitations is that the “power level” associated with the “multitude of threshold values” is the battery power level that is (1) measured by the battery power level monitor and (2) adjusted by the battery power level monitor and applied to location tracking circuitry. We also note that the claim language already incorporates a limitation directed to “signal levels” insofar as the battery power level monitor “adjusts a power level applied to location tracking circuitry responsive to one or more signal levels” (emphasis added). As such, the limitation “one or more signal levels” is recited separately from the limitation “the power level comprising a multitude of threshold values.” Given “[t]he general presumption that different terms have different meanings,” Chicago Bd. Options Exch., Inc. v. Int’l Sec. Exch., LLC, 677 F.3d 1361, 1369 (Fed. Cir. 2012), we ascribe different meanings to the recited “signal levels” and “power level.”” slip op. at 15

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “the battery power thresholds between (1) high and normal sensitivity positioning modes and (2) normal sensitivity positioning mode and turning off power to the GPS receiver) and Sakamoto’s two GPS signal level thresholds (i.e., K1 and K2) for teaching “the power level comprising a multitude of threshold values.” Pet. 50–51; Pet. Reply 16–18. As discussed above, however, “the power level comprising a multitude of threshold values” refers to battery power level thresholds. See supra § II.C.2. We also determine above that signal level threshold values are not within the scope of “the power level comprising a multitude of threshold values.” See id. Accordingly, we are not persuaded that Sakamoto’s GPS signal level thresholds K1 and K2 teach the recited power level threshold values. Although Petitioner is correct that “Sakamoto uses the same modes with both sets of thresholds” and that both sets of thresholds might ultimately relate to conserving battery power (see Pet. Reply 17 (citing Ex. 1003 ¶ 58; Ex. 1004 ¶¶ 27–29)), we are not persuaded that these different types of thresholds are interchangeable within the scope of “the power level comprising a multitude of threshold values.” This is particularly true given that Petitioner already relies on Sakamoto’s GPS signal level thresholds K1 and K2 for teaching another aspect of claim 8, i.e., “responsive to one or more signal levels.” See Pet. 49–50. For these reasons, Petitioner has only established that Sakamoto teaches two battery power level thresholds within the scope of “the power level comprising a multitude of threshold values.” Because two threshold values are not a “multitude” (see supra § II.C.1), we find that Petitioner has not established that Sakamoto teaches “the power level comprising a multitude of threshold values,” as recited in claim 8. Thus, we determine Petitioner has not shown by a preponderance of the evidence that the subject matter of claim 8 would have been obvious over Sakamoto. 3. Claims 10, 13, and 15 Claims 10, 13, and 15 each depend from claim 8. Ex. 1001, 17:4–10, 17:23–25, 17:29–33. Petitioner’s analysis for these claims does not cure the deficiencies discussed above with respect to claim 8. See Pet. 54–55. Thus, we determine Petitioner has not shown by a preponderance of the evidence that the subject matter of claims 10, 13, and 15 would have been obvious over Sakamoto.” slip op. at 31

  • BurdenNot shown unpatentable

    “III. CONCLUSION Petitioner has not shown, by a preponderance of the evidence, that (1) the subject matter of claims 8, 10, 13, and 15 would have been obvious over Sakamoto; (2) the subject matter of claims 8, 10, 13, and 15 would have been obvious over the combination of Sakamoto and AAPA; or (3) the subject matter of claims 8, 10, 13, and 15 would have been obvious over the combination of Sakamoto and Hayasaka.” slip op. at 33

  Patent outcomesUS 8,497,774 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,497,774
• Cerebras Systems Inc. v. Rex Computing, IncNo claims unpatentable
  PTAB · Oct 11, 2023 · IPR2022-00741 · APJ Michael T Cygan · IPR · Final written decision

  Claims 1–19 were not shown unpatentable under § 103 because the cited combinations failed to teach required router retention, scratchpad memory, or optimal square-versus-linear tile assignment limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “the time the ’975 patent was filed. Pet. 6. Relying upon the Conte Declaration, Petitioner asserts a person of ordinary skill in the art would have had “a Bachelor of Science degree in electrical engineering, computer engineering, or a related subject matter, plus at least two years of professional experience in the field of microprocessor design or a similar field . . . and more experience would compensate for less formal education, and vice versa.” Id. (citing Ex. 1002 ¶¶ 27–30). Patent Owner applies this 2 Patent Owner does not identify any secondary considerations to be considered. assessment in its Response. Resp. 8. Based on the fully developed record, we accept the assessment offered by Petitioner because it is supported by the Conte Declaration and is consistent with the ’975 patent and the asserted prior art.” slip op. at 8

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

    “[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We determine that no constructions are required for the above-disputed terms. slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed patent owner constructionDecided for patent owner

    “above-described manner to store data. But Dr. Conte’s direct testimony does not address other statements in the ’975 patent specification that describe the scratchpad memory as an alternative to a cache. See Ex. 1001, 8:27–33 (“each of the cores includes a scratchpad memory . . . . As a result, conventional L-level caches may not be used in the architecture 299 because the scratchpad memories . . . provide data storage”); see also id. at 3:21–4:35 (describing drawbacks of prior art architectures that rely on caches), 5:14–20 (stating that each core may include a scratchpad memory instead of a cache). As Dr. Bagherzadeh stated, “Dr. Conte never reconciled [his] opinion with the ’975 Patent’s disclosure, which, as I described, connects the concept of using a scratchpad memory to a cache-less architecture.” Ex. 2001 ¶ 92 (citing Ex. 1001 Fig. 3). Dr. Conte’s deposition testimony did not clarify this issue, stating that the issue of cacheless architecture was “disconnected” from whether a microprocessor has a scratchpad. Ex. 2002, 40:10–15. The ’975 patent specification’s description of a scratchpad memory module as an alternative to cache memory is evidence that an ordinary artisan, upon reading the entirety of the ’975 patent, would not have considered the scope of the claimed scratchpad memory to include a cache memory. Dr. Conte has relied upon the ’975 patent specification for general properties seemingly common to both caches and scratchpad memory, but has not explained why the ’975 patent specification’s statements distinguishing a scratchpad memory from a cache should not limit the scope of the claimed “scratchpad memory.” As a result, Dr. Conte’s testimony does not significantly assist in construing “scratchpad memory” in any manner relevant to the pertinent issue; i.e., whether it may be taught by a prior art cache memory.” slip op. at 30

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “data “occurs in the router’s input buffer” (Pet. Reply 10 (emphasis added)), but Petitioner does not support this assertion with analysis or evidence. To the contrary, Petitioner has clarified that the “input” on which words wait is “the input of the processor,” not the router. Pet. Reply 12. Claim 1 requires that a router must be operable to retain such data (limitation [1g]), and that the processor cores are distinct from the routers (limitation [1a]). Thus, to the extent that MIT2002 teaches data waiting at the input of the processor, Petitioner has not pointed to evidence or reasoning persuasively showing that the claimed router is operable to retain a data packet, even if a buffer at the input of the processor is able to do so. Instead, Petitioner primarily relies on our preliminary determination, and on Patent Owner’s lack of argument to the contrary. Id. at 11–12. Neither of these act to satisfy Petitioner’s burden to show that MIT2002, in combination with the other applied references, teaches a router operable to retain data packets in the event of a traffic condition. Consequently, we are not persuaded that retention of data in the Raw system occurs at the router’s input buffer. For the above described reasons, we determine that Petitioner has not shown by a preponderance of evidence that the combined teachings of the applied references of this ground teach or suggest the “each router is operable to retain a data packet in the event of a traffic condition” limitation of [1g]. Accordingly, Petitioner has not demonstrated by a preponderance of the evidence that the subject matter of claim 1 would have been obvious.” slip op. at 24

  Patent outcomesUS 10,355,975 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,355,975
• Linkedin Corporation v. Ebuddy Technologies B.V.No claims unpatentable
  PTAB · Jun 30, 2023 · IPR2022-00164 · APJ Jason M Repko · IPR · Final written decision

  LinkedIn did not prove claims 1–3 and 6–10 unpatentable on any asserted Eaton- or Kim-based anticipation or obviousness ground.

  RulingsFinal written decision

  • ExcludeOther

    “In its Motion to Exclude, Patent Owner seeks to exclude Petitioner’s Exhibits 1017–1020, 1022–1026, 1030, 1032, 1033, 1034, and 1036. Mot. 1. Even without excluding any of these exhibits, Petitioner has not proven that any challenged claims are unpatentable. Thus, we dismiss Patent Owner’s Substitute Motion to Exclude as moot.” slip op. at 36

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner’s alternative definition that “a PHOSITA[3] would possess equivalent additional formal education such as graduate studies, or work experience to replace formal education” is unclear or, at best, does not meaningfully contribute to the first definition. See id. For example, Petitioner does not explain whether or how additional graduate studies would be both equivalent and additional to the education described in the first definition. See id. Patent Owner does not propose an alternative definition. See generally PO Resp.; Sur-reply. Thus, in this decision, we apply Petitioner’s proposed definition, without the alternative qualifier about “equivalent additional formal education . . . or work experience.” See Pet. 6. We determine that Petitioner’s definition is supported by the testimony of Dean Willis. Ex. 1004 ¶¶ 32–35.” slip op. at 6

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

    “B. Claim Construction We need only construe terms that are in controversy and only to the extent necessary to resolve the dispute. Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). We need not construe any terms to resolve the issues in this case.” slip op. at 6

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “We credit Dr. Rajeev Surati’s testimony6 (Ex. 2020 ¶ 2053) on this issue over Dean Willis’s testimony (Ex. 1004 ¶¶ 211–13) because Dr. Rajeev Surati’s testimony is more consistent with Kim’s disclosure and Dean Willis’s Declaration lacks an adequate explanation. Thus, Petitioner has not shown that Kim discloses the associating step.” slip op. at 16

  Patent outcomesUS 8,230,135 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 8,230,135
• Linkedin Corporation v. Ebuddy Technologies B.V.No claims unpatentable
  PTAB · Jun 30, 2023 · IPR2022-00165 · APJ Jameson Lee · IPR · Final written decision

  Claims 1–3 and 6–10 were not shown unpatentable because Eaton and Kim each failed to disclose the claimed array and alternative-title limitations, and the obviousness grounds did not cure those deficiencies.

  RulingsFinal written decision

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

    “alternative” or “alternative title.” Neither party contends that “alternative” or “alternative title” is a term of art with an art recognized meaning. In plain English, “alternative” as an adjective designates something that is another option, another choice. Dictionary.com (accessed June 23, 2022), https://www.dictionary.com/browse/alternative (Ex. 3002) (“affording a choice of two or more things, propositions, or courses of action,” “(of two things, propositions, or courses) mutually exclusive so that if one is chosen the other must be rejected: The alternative possibilities are neutrality and war.”). The specification of the ’179 patent also consistently uses the word “alternative” to mean something in lieu of or in place of another choice. For instance, the ’179 patent describes: Advantageously, data associated with the event can also (or in the alternative) be provided to the title provisioning engine 616. Ex. 1001, 8:15–17 (distinguishing “also” from “alternative”). A given event may cause the title provisioning engine 616 to rewrite the entire title array 618 with title strings associated with the most recent events. Alternatively, a given event may cause the title provisioning engine 616 to append title strings to the end of the title array 618. Id. at 8:24–28 (using “alternative” in mutually exclusive context). slip op. at 12

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

    “During oral hearing, counsel for Petitioner clarified that the index to an array may start from “0” rather than “1” and that the index also need not be a number. Tr. 18:13–19:19. With that clarification, counsel for Patent Owner indicated that there no longer is any dispute with regard to the meaning of “array.” Tr. 61:14–25. Accordingly, we have no need to construe the term “array.” 4. “event” The term “event” is recited in independent claim 1. The specification” slip op. at 14

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

    “reproduced above, are “event messages / strings 300 (shaded in green).” Pet. 30 (citing Ex. 1006 ¶ 31). But the cited evidence does not support that assertion. Paragraph 31 of Eaton describes the referenced column simply as “associated event 300.” Ex. 1006 ¶ 31. Further, even if the column stores associated event messages, Petitioner cites nothing to show that the associated messages in server memory column 300 are the event presence notification messages discussed above in the context of limitation 1[ii]. Alternatively, Petitioner relies on Eaton’s Figure 6 embodiment. Pet. 31. Petitioner asserts (id.) that in the Figure 6 embodiment server memory 160 stores an array of event notifications, referencing an annotated version of Eaton’s Figure 6, reproduced below: Figure 6 is a block diagram of an alternate embodiment of a server memory for use within a server of the instant message communication system, and Petitioner has shaded the EVENT AN–NN column green and the words “SERVER MEMORY” red. Ex. 1006 ¶ 19. Petitioner asserts that both the TOPIC N column 540 and the EVENT AN-NN column 670 as the stored event notifications. Pet. 31 (citing Ex. 1006 ¶¶ 56–58). But the assertion is not supported by the cited evidence. Paragraphs 56–58 of Eaton do not indicate that either topic entries 540 or event entries 670 are the event presence notification messages discussed above in the context of limitation 1[ii]. In its Reply, Petitioner asserts that event presence notification message EPNM “is associated with the character strings labelled Topics [1]- [N], and using ‘Topic N’ as the example, it is tied to ‘Event[s] AN-NN’ (representing the ‘events’ from the plurality of events 180 discussed in Claim 1[i]).” Reply 22. Even assuming that there is an association, Petitioner still has not shown that EPNM is any of Topics [1]-[N] in Figure 6. Similarly, Petitioner has not shown that EPNM is any of Event [1]-[N] in Figure 2.” slip op. at 26

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “’179 Patent as provided above in Ground 1. To the extent that there are arguably any meaningful differences between those claims and Eaton’s disclosures, those differences would have been trivial and obvious modifications to make for a PHOSITA.” Pet. 49. This conclusory assertion of obviousness does not specifically identify any difference between the claimed invention and Eaton, and does not provide any reasoning or rational underpinning to support the assertion. Conclusory assertions of obviousness are insufficient to satisfy Petitioner’s burden of proof. In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016). Petitioner asserts that to the extent that Eaton discloses various, “distinct” embodiments, it would have been obvious to one with ordinary skill in the art to combine Eaton’s teachings into a single system. Pet. 49. Petitioner also asserts that one with ordinary skill in the art “would understand that Eaton discloses possible configurations and/or operations of the same system, and to the extent that it is argued or found otherwise, the functions would have been entirely obvious to combine for [one of ordinary skill in the art] given Eaton’s express disclosures.” Id. It is uncertain what distinct embodiments are referred to by Petitioner. However, even assuming that the disclosures of Eaton’s embodiments, already discussed by Petitioner, are properly combinable, there still remains the deficiencies, discussed above in the alleged anticipation of claim 1 by Eaton, relating to the step of storing the event notification in an array, the step of providing the event notification from the array to a process executed by a processor, and the step of providing an alternative title from the array to the process. Accord Inst. Dec. 57.” slip op. at 33

  Patent outcomesUS 8,402,179 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 8,402,179
• Amazon.Com, Inc. / Blizzard Entertainment, Inc. v. Ac Technologies S.A.No claims unpatentable
  PTAB · Mar 6, 2017 · IPR2015-01801 · APJ Peter P Chen · IPR · Final written decision

  Claims 30, 31, 33, and 40–46 were not shown unpatentable because Rabinovich required prior client access before replication, and Carter did not cure that limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedPetitioner expert creditedDecided for petitioner

    “C. Level of Ordinary Skill in the Art Petitioner’s declarant, Dr. Ratner, testifies that a person of ordinary skill in the art at the time of the alleged invention “would have had an undergraduate degree in Computer Science or a related field, such as Electrical Engineering, and two to three years of experience working in the field, or an equivalent level of experience.” Ex. 1005 ¶ 17; Pet. 14. Patent Owner does not challenge this definition or present its own. Accordingly, we credit the testimony of Dr. Ratner regarding the level of ordinary skill in the art, and find that a person of ordinary skill in the art would have had an undergraduate degree in Computer Science or a related field, such as Electrical Engineering, and two to three years of experience working in the field, or an equivalent level of experience. This level of ordinary skill is reflected not only by the information presented by the parties, but also by the prior art of record. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art itself can reflect the appropriate level of ordinary skill in the art).” slip op. at 9

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “We agree with and adopt Petitioner’s reasoning and determine Rabinovich to be a printed publication. We credit the unrebutted testimony of Dr. Rabinovich regarding the consistency of his professional practice in 1998 for republication of his AT&T technical memoranda on a webpage that he managed on AT&T’s publicly accessible website. Furthermore, we find the December 1998 IEEE article corroborates the public availability of Rabinovich on that website, and would have been a roadmap, for one of ordinary skill in the art of data management and optimized access to data, to be guided to Rabinovich. See Reply 21–22. As Petitioner points out, Patent Owner’s own declarant states that Rabinovich and the December 1988 IEEE article “are ‘similar[]’ in that they both address ‘problems in network connectivity caused by multiple clients accessing servers.’ (Ex. 2006 at 12).” Id. at 20. Additionally, the passage in the December 1998 IEEE article that cites to Rabinovich refers to an algorithm in Rabinovich for optimizing access to data in order to increase performance. Id. at 21. Accordingly, we find that footnote 16 of the IEEE article, which contains the URL to Rabinovich, would have guided one of ordinary skill directly to Rabinovich. We are, therefore, persuaded, that Rabinovich is a printed publication under 35 U.S.C. § 102.” slip op. at 12

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

    “whether to replicate data object xs. Rabinovich defines cnt(s,xs) as the “total access count for xs,” which is equal to cnt(xs). Ex. 1006, 11. According to Dr. Ratner, “[t]he metric cnt(s,xs) measures the total number of times in that window that replica xs has been served to a client computer.” Ex. 1005 ¶ 253. As Patent Owner points out, Rabinovich teaches replicating/migrating object xs only if the ratio of cnt(s,xs) over aff(xs) is greater than m, and the ratio can be greater than m only if cnt(s,xs) is greater than zero. PO Resp. 19; Ex. 1006, 12, Fig. 4. In view of this, we agree with Patent Owner that if cnt(s,xs) has a value of zero, meaning that object x has not been served to any client computer, then the ratio of cnt(s,xs) to aff(xs) will be zero, i.e., less than m, and Rabinovich will not carry out its replication or migration step. This means that Rabinovich will not replicate or migrate object xs until xs has been accessed by a client computer at least once, such that the access count for xs is greater than zero. In this regard, we agree with Patent Owner that object xs is not “sen[t], from the at least one data storage device to the another data storage device . . . independent of an access of the at least one client computer” because Rabinovich teaches explicitly that object xs is not sent unless there has been at least one access from the client computer.” slip op. at 18

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “30, for use with a computer game (claim 45) and with an interactive computer game accessed by at least two users (claim 46). Ex. 1001, 30:47– 54. In connection with its obviousness contentions, Petitioner makes no separate arguments why Rabinovich teaches or suggests shifting redundantly stored data based upon data transmission parameters between the servers independent of an access of the client. Pet. 45–47; Reply 17–18. Because claims 45 and 46 depend from claim 30, we find that Petitioner has failed to demonstrate by a preponderance of the evidence that Rabinovich teaches or suggests the limitations in these two dependent claims for the same reasons discussed above with respect to claim 30.” slip op. at 21

  Patent outcomesUS RE40,521 not shown unpatentable
  § 102 anticipation§ 103 obviousnesscites KSR · Graham
• Corelogic, Inc. v. Boundary Solutions, Inc.No claims unpatentable
  PTAB · May 19, 2016 · IPR2015-00219 · APJ Lynne E Pettigrew · IPR · Final written decision

  Claims 12–15 and 17–21 were not shown unpatentable because Oosterom did not disclose searching the database using a jurisdictional identifier.

  RulingsFinal written decision

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “In the Institution Decision, we construed “jurisdictional identifier” to mean “a number or other name, code, or description that identifies a jurisdiction.” Dec. 6. We based our construction on the only appearance of “jurisdictional identifier” in the written description of the ’352 patent, which states: FIG. 3 illustrates a USA County Boundary Map (USACM). This is a public domain boundary file of each and every of the 3140 counties within the United States. Each of these polygons is geocoded with its county name and FIPS number, a numerical jurisdictional identifier, as illustrated in the figure. Ex. 1001, 8:48–53 (emphasis added).3 BSI does not challenge our construction of “jurisdictional identifier” in its Patent Owner Response, see PO Resp. 6, nor does CoreLogic challenge the construction in its Reply, see Reply 10. For this Final Written Decision, after considering the complete record, we maintain our construction of “jurisdictional identifier” as “a number or other name, code, or description that identifies a jurisdiction.”” slip op. at 5

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

    “Having reviewed the arguments and evidence, we are not persuaded CoreLogic has demonstrated that Oosterom discloses searching the parcel map database “using a jurisdictional identifier” as recited in claim 12. Among the attributes in Oosterom’s parcel and boundary tables identified by CoreLogic in its analysis, only the municipality codes (i.e., “municip” in the parcel table and “L_municip” and “R_municip” in the boundary table) qualify as “jurisdictional identifiers.” See Ex. 1010, 513–14 (Tables 1, 2). The “object_id” of an object, e.g., a parcel or a boundary, is a nationwide unique identifier, but there is no indication in Oosterom that the object_id of a parcel or boundary identifies a jurisdiction. See id. at 512; see also id. at 513–14 (showing object_id attribute in parcel and boundary tables). As for the “ogroup” attribute in the parcel and boundary tables, Oosterom states only that it “indicates to which group the record belongs.” Id. at 519. Nothing in Oosterom describes the ogroup as identifying a jurisdiction. Although the municipality code attributes in the parcel and boundary tables identify jurisdiction, CoreLogic does not cite any portion of Oosterom that illustrates the use of municipality codes in searching the database for selected parcels as required by claim 12. See Pet. 45. Dr. Goodchild opines that the “municipality code . . . would allow us to search [the] parcel table by that jurisdiction and to identify all the parcels in that jurisdiction.” Ex. 2010, 19:22–24. He further testifies that in his analysis, he “was concerned with the specific kind of query identified in the claim, which is much narrower than Oosterom’s discussion [and] much more specific than the broad range of queries discussed by Oosterom.” Id. at 21:14–25. Ultimately, he states that the “question [he] analyzed is whether [Oosterom’s] database is capable of supporting the type of query identified in the claim.” Id. at 22:14–16 (emphasis added). Dr. Goodchild’s testimony that municipality codes could be used in searching Oosterom’s database, however, is insufficient to establish for anticipation purposes that Oosterom discloses the step of searching a multi-jurisdictional digital parcel map database for a selected parcel boundary polygon “using a jurisdictional identifier.”” slip op. at 10

  • ExcludeOther

    “C. CoreLogic’s Motion to Exclude Evidence CoreLogic moves to exclude the redirect testimony of BSI’s expert, Mr. William Huxhold, on the ground that it was provided in response to leading questions. Mot. Excl. 1 (citing Ex. 1034, 150:6–153:8). The redirect testimony relates to a portion of Mr. Huxhold’s cross-examination testimony. Id. at 1–2 (citing Ex. 1034, 72:5–22). Because we do not rely on Mr. Huxhold’s testimony, CoreLogic’s motion is dismissed as moot.” slip op. at 12

  Patent outcomesUS 8,065,352 not shown unpatentable
  Claim construction§ 102 anticipation
  Patents in suitUS 8,065,352
• Smart Modular Technologies Inc. v. Netlist, Inc.No claims unpatentable
  PTAB · Mar 9, 2016 · IPR2014-01372 · APJ Linda M Gaudette · IPR · Final written decision

  The Board held claims 1–4, 14–20, 27, and 29 not unpatentable because Averbuj did not disclose a control module configured to generate the claimed address signals.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Based on a comparison of Dr. Bagherzadeh’s and Dr. Sechen’s declarations (Exs. 1009, 2019), we find Dr. Bagherzadeh has a broader range of educational and work experience, and, therefore, accord greater weight to his opinion as to the level of ordinary skill in the art. Dr. Bagherzadeh’s opinion is consistent with our finding as to the level of ordinary skill in the art in our Final Written Decision in IPR-970. We, therefore, adopt our finding in IPR-970 as to the level of ordinary skill in the art: [A] person of ordinary skill in the art at the time of the ’434 patent would have a Bachelor’s degree in electrical engineering, computer engineering, or in a related field and at least one year of work experience relating to memory systems, and would be familiar with the design of memory devices, memory modules, and BIST. IPR-970 FWD, 10–11 (noting that our finding was “based on our review of the ’434 patent and the types of problems and solutions described in the ’434 patent and cited prior art”).” slip op. at 10

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “We are not persuaded by Dr. Bagherzadeh’s testimony because it is devoid of specific facts and analysis as to what led him to conclude that a person of ordinary skill in the art would interpret the claim term “generate” in the manner Petitioner proposes. See id. Dr. Bagherzadeh does not explain how the IEEE definition supports an interpretation of generate as “cause or initiate transmission,” terms that do not appear in the IEEE definition. See id. Nor does Dr. Bagherzadeh identify other extrinsic evidence which he believes to be consistent with an interpretation of “generate” as meaning “cause or initiate transmission.” See id. Likewise, Dr. Bagherzadeh has not explained why he believes the ’434 patent “describe[s] generating as initiating or transmitting” (Ex. 1009 ¶ 28), as these terms do not appear in the cited portions of the ’434 patent. See Ex. 1008, 6:3–5, 10:67–11:2, 6:14–17. Accordingly, Dr. Bagherzadeh’s testimony does not persuade us to accept Petitioner’s interpretation of “generate” as meaning “cause.”” slip op. at 15

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

    “supports a finding that a customary meaning of “generate” to one of ordinary skill in the art is “cause.”1 We, therefore, determine the broadest reasonable 1 Petitioner relies on Webster’s II, for a definition of “cause.” See Reply 4, 6–8 (citing Ex. 1032, 3). Having determined the broadest reasonable interpretation of “generate” does not encompass “cause,” we do not find this evidence relevant to our claim construction analysis. construction of “generate” is “produce” for the reasons stated above and in our Final Written Decision in IPR-970. We adopt and incorporate by reference our analysis and construction of the term “generate” in our Final Written Decision in IPR-970 (IPR-970 FWD, 24–33).” slip op. at 16

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

    “Moreover, the evidence in this proceeding fails to support a finding that Averbuj’s BIST controller 4 is configured to generate address signals for testing the memory devices in the manner claimed. In Averbuj, the algorithms (i.e., CMD_DATA containing OP CODE such as SET ADDRESS (see Ex. 1011, 4:4–12, 5:19–21, Table 1)) communicated to sequencers 8 are either received by user interface 22 via external input (id. at 5:41–43) or generated by another component (i.e., a component that is not part of BIST controller 4 circuitry) and stored in algorithm memory 20 (see Ex. 2012, 30:23–24, 41:1–4, 54:21–22, 55:6–25, 55:20–56:9 (wherein Dr. Bagherzadeh testifies that OP CODE residing in the algorithm memory of BIST controller 4 are generated by hand or by a tool, e.g., a compiler, and that “99 percent of the designs or chips do not have a compiler on-board”)). Multiplexer 24 selects one of the algorithms (i.e., CMD_DATA) and BIST controller 4 provides to sequencers 8 the same CMD_DATA (e.g., address signals) without transformation or modification. See Ex. 1011, 4:4–12, 5:16–21; Ex. 2012, 54:8–13 (“Averbuj Figure 2, without consideration of any other disclosure in Averbuj, illustrates that a multiplexer selects an input from the algorithm memory and the output [] reflect[s] what’s in the input, based on the selection.”). Based on our interpretation of the terms “configured to” and “generate,” as discussed above, the claim recitation “a control module configured to generate address . . . signals for testing the memory devices” (claims 1, 20, and 29) does not read on Averbuj’s BIST controller 4, because the SET ADDRESS signal output by BIST controller 4 is produced by a component external to BIST controller 4, and merely selected by multiplexer 24 and provided to sequencers 8 without transformation or modification by BIST controller 4. In sum, after considering the parties’ arguments and evidence, we determine Petitioner has not shown, by a preponderance of the evidence, that Averbuj discloses “a control module configured to generate address . . . signals for testing the memory devices” as recited in independent claims 1, 20, and 29. Petitioner does not correct this deficiency in its challenges as to dependent claims 2–4, 14–19, and 27. See Pet. 32–39; 35 U.S.C. § 112, ¶ 4 (“A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.”). Because Petitioner has not identified in Averbuj a teaching of each and every limitation recited in claims 1–4, 14–20, 27, and 29, Petitioner has not met its burden to show these claims are unpatentable under 35 U.S.C. § 102(b) as anticipated by Averbuj.” slip op. at 30

  Patent outcomesUS 8,001,434 not shown unpatentable
  Claim construction§ 102 anticipation
  Patents in suitUS 8,001,434

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.