- Bj’S Wholesale Club Holdings, Inc. v. Walmart Apollo, LLCAll claims unpatentablePTAB · Apr 10, 2024 · IPR2022-01564 · APJ Patrick R Scanlon · IPR · Final written decision
Claims 1–14 are unpatentable as anticipated by Keith; the Board did not reach the alternative obviousness ground over Hanson and Keith.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“claims of the later-filed application must be supported by the written description in the parent ‘in sufficient detail that one skilled in the art can clearly conclude that the inventor invented the claimed invention as of the filing date sought.’” Anascape, Ltd. v. Nintendo of Am. Inc., 601 F.3d 1333, 1335 (Fed. Cir. 2010) (quoting Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997)). “[T]he hallmark of written description is disclosure,” and the test “is whether the disclosure of the application relied upon reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date” of that application. Ariad Pharms., Inc. v. Eli Lilly and Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc) (citing Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1562–63 (Fed. Cir. 1991)). “[T]he test requires an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Id. But, “[i]t is not sufficient for purposes of the written description requirement of [35 U.S.C.] § 112 that the disclosure, when combined with the knowledge in the art, would lead one to speculate as to modifications that the inventor might have envisioned, but failed to disclose.” Lockwood, 107 F.3d at 1572.” slip op. at 33
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“A claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal Bros. Inc., v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Moreover, “[b]ecause the hallmark of anticipation is prior invention, the prior art reference—in order to anticipate under 35 U.S.C. § 102—must not only disclose all elements of the claim within the four corners of the document, but must also disclose those elements ‘arranged as in the claim.’” Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 (Fed. Cir. 2008). Whether a reference anticipates is assessed from the perspective of an ordinarily skilled artisan. See Dayco Prods., Inc. v. Total Containment, Inc., 329 F.3d 1358, 1368 (Fed. Cir. 2003) (“‘[T]he dispositive question regarding anticipation [i]s whether one skilled in the art would reasonably understand or infer from the [prior art reference’s] teaching’ that every claim element was disclosed in that single reference.”). slip op. at 13
- BurdenFwd all claims unpatentableDecided for petitioner
“preponderance of the evidence that the claims are unpatentable. 35 U.S.C. § 316(e) (2018); 37 C.F.R. § 42.1(d) (2022). “In an IPR, the petitioner has the burden from the onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (2012) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015) (discussing the burden of proof in inter partes review).” slip op. at 12
Patent outcomesUS 10,803,435 unpatentable§ 102 anticipation§ 112 disclosurecites KSR · GrahamPatents in suitUS 10,803,435 - Apple Inc. v. Rfcyber Corp.All claims unpatentablePTAB · Jan 19, 2024 · IPR2022-01256 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–11 are unpatentable as obvious over Buhot, GPC, and Zhu.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“earlier applications, in particular Application No. 11/534,653 (“the ’653 application”), which issued as U.S. Patent No. 8,118,218 B2 (“the ’218 patent”). “‘It is elementary patent law that a patent application is entitled to the benefit of the filing date of an earlier filed application only if the disclosure of the earlier application provides support for the claims of the later application, as required by 35 U.S.C. § 112.’” PowerOasis, Inc. v. T- Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008). The test for determining compliance with the written description requirement under § 112(a) is whether the original disclosure of the earlier-filed application reasonably would have conveyed to one with ordinary skill in the art that the inventor had possession of the claimed subject matter at the time of the earlier-filed application. Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). It is well settled that “[e]ntitlement to a filing date does not extend to subject matter which is not disclosed but would be obvious over what is expressly disclosed.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571−72 (Fed. Cir. 1997). “It is not sufficient for purposes of the written description requirement of § 112 that the disclosure, when combined with the knowledge in the art, would lead one to speculate as to modifications that the inventor might have envisioned, but failed to disclose.” Id. We agree with Petitioner there does not appear to be support for limitation [1(j)] in the ’653 application. We find that the disclosure of the ’653 application—limited to general teachings of a smart card, an operating system, and a smart card manager—is insufficient to show possession of limitation [1(j)]. See Ex. 2001 (’218 patent), 4:47–56. As we explained above, “[e]ntitlement to a filing date does not extend to subject matter which is not disclosed but would be obvious over what is expressly disclosed.” Lockwood, 107 F.3d at 1571−72. The ’653 Application contains no disclosure of replacing applications, even if the disclosure might render such replacing obvious, it is not sufficient to show the possession required to establish entitlement to a priority date. Accordingly, we agree with Petitioner that the challenged claims of the ’724 patent are entitled to a priority date no earlier than March 4, 2012.” slip op. at 7
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Relying on the declaration testimony of Mr. Smith, Petitioner contends that an ordinarily skilled artisan for the ’724 patent “would have had at least a bachelor’s degree in computer engineering, computer science, electrical engineering, or a related field, with at least one year of experience in the field of mobile payment technology. Additional pertinent education might substitute for the requisite experience and vice versa.” Pet. 6–7 (citing Ex. 1007 (Smith Decl.) ¶¶ 34–35). Patent Owner states that “[t]he parties agree on the level of skill in the art.” PO Resp. 11. Accordingly, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’724 patent and the asserted prior art, and we apply it in our obviousness evaluations below. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art, itself, can reflect appropriate level of ordinary skill in art).” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“Petitioner contends that it applies “the plain and ordinary meaning as understood by a [person of ordinary skill in the art] for all terms not expressly construed below,” and indicates that in parallel District Court litigation, the parties agreed to claim construction for the term “emulator device” to mean “hardware device, alone or containing software, that pretends to be another particular device or program that other components expect to interact with.” Pet. 8. Petitioner proposes that the term “application” should be construed to mean “‘software program suitable for being executed on a portable device,’” but that the “distinction between the parties’ respective proposals need not be resolved for this proceeding.” Id. at 8–9. Petitioner finally contends that the phrase “a portion of or in entirety” in each independent claim means “in its entirety or partially,” but not both. Id. at 9. Patent Owner submits that “[t]he parties agree that the Board should construe ‘emulator device’ as ‘hardware device, alone or containing software, that pretends to be another particular device or program that other components expect to interact with.’” PO Resp. 11. Patent Owner “does not believe that any other terms require construction to resolve the issues presented in this proceeding.” Id. We apply the agreed upon constructions above, but otherwise find that no express constructions are necessary for this decision.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“We agree with Petitioner that, even if the applications were stored in “generic memory” as Patent Owner contends, Zhu provides adequate security and would not undermine Petitioner’s motivation to combine. See Intel, 61 F.4th at 1380 (“It’s not necessary to show that a combination is the best option, only that it be a suitable option.”). Indeed, Zhu addresses the problem Patent Owner contends it would cause in the combination.3 As Zhu 3 Patent Owner argues that Petitioner should be precluded from discussing Zhu’s encryption embodiment because it was not raised in the Petition. See Sur-Reply 6–7. We disagree. The claims do not recite anything about how the data should be stored. Thus, it is not surprising that the Petition did not address it. Patent Owner raised the teaching away argument regarding the security of the data. See PO Resp. 12–16. Petitioner relies on the exact same mapping, same motivation, and same arguments why Zhu accounted for certain limitations. See Reply 4–11. Petitioner’s Reply merely explained that Zhu did address the problem Patent Owner contended would “teach away” from the combination. Indeed, Patent Owner was aware of Zhu’s teachings and addressed them in their Patent Owner Response. The Federal recognizes, “[l]oading one of the smart card applications already resident on the smart card to another memory location on the mobile device can provide sufficient memory for the selected smart card application, but can also create a security problem.” Ex. 1006 (Zhu), 3:25–34. To address this problem, Zhu proposes encrypting these applications in generic memory which “reduces the possibility of unauthorized access to the information.” Id. at 3:59–61, 8:30–55, 9:28–33; Ex. 1033 (Smith Supp. Decl.) ¶¶ 5–6. Although acknowledging this disclosure, Patent Owner’s expert, Dr. Weaver, testifies that Zhu’s encryption is inadequate and that encryption would have certain drawbacks. See Ex. 2002 (Weaver Decl.) ¶ 69. We find this testimony, which directly contradicts the teachings of Zhu that encryption is an adequate solution, lacks sufficient support to be entitled to much weight. Dr. Weaver provides no citations to support his contention that a person of ordinary skill at the time of the invention would find encryption so inadequate or problematic as he now contends. Moreover, we find that Dr. Weaver’s testimony on cross examination provides an additional, independent basis to give this testimony little weight. On cross examination, Dr. Weaver contended that there was nothing uniquely inadequate about the particular encryption scheme disclosed in Zhu, but rather that his “opinion was more general, that encryption schemes known in the 2012 time frame were all breakable with computing power and time,” and thus, inadequate Circuit has explained that “the petitioner in an inter partes review proceeding may introduce new evidence after the petition stage if the evidence is a legitimate reply to evidence introduced by the patent owner.” Anacor Pharm., Inc. v. Iancu, 889 F.3d 1372, 1380–81 (Fed. Cir. 2018). That is the case here, so we find that Petitioner’s arguments and evidence regarding Zhu’s encryption are proper. for storing payment applications in a mobile device’s general memory. Ex. 1027 (Weaver Tr.), 26:11–23; see also id. at 23:3–8 (“[D]oes encryption ever provide a sufficiently high security to permit storing payment application on a mobile device’s general memory? A. No”); 24:15–25:23 (testifying all publicly known encryption schemes in 2012 were breakable). However, when confronted with the fact that the ’724 patent discloses storing payment application on general baseband memory using an encryption method that was breakable, id. at 26:24–29:7, Dr. Weaver testified that this encryption method was sufficient to allow storing payment applications in general baseband memory even though it was “not perfectly secure,” id. at 29:8–14. Dr. Weaver provides no explanation or rationale why the encryption method in the ’724 patent, which he admits suffers from the same drawbacks he identified with respect to Zhu, is sufficient, but other encryption methods would not be sufficient. In its Sur-reply, Patent Owner attempts to rehabilitate Dr. Weaver’s testimony with justifications and qualifications not found in his original testimony. Sur-Reply 7–8. Yet, Dr. Weaver’s testimony discussed above was clear and unequivocal. See Ex. 1027 (Weaver Tr.), 24:15–29:14. Patent Owner made no effort to redirect his testimony at his deposition, so it cannot now do so through mere attorney argument. We find the inconsistency between Dr. Weaver’s treatment of Zhu and his treatment of similar disclosure in the ’724 patent exposes the insufficient reasoning supporting his opinions regarding the adequacy of Zhu’s use of encryption in the combination. Accordingly, we give no weight to his testimony that a skilled artisan would not have combined Zhu with a Buhot/GPC system due to security concerns. In contrast, we find the testimony of Mr. Smith regarding the use of encryption and the tradeoffs with the benefits of adopting Zhu’s memory management technique, which he offers in his Supplemental Declaration, to be well-reasoned, consistent with the disclosure of Zhu and the ’724 patent4, and entitled to substantial weight. See Ex. 1033 (Smith Supp. Decl.) ¶¶ 4–15. As Petitioner recognizes, “‘[a] given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.’” Allied Erecting & Dismantling Co. v. Genesis Attachments, LLC, 825 F.3d 1373, 1381 (Fed. Cir. 2016). As Mr. Smith and Dr. Weaver testified, decryption without access to the security keys is an extremely computationally intensive and time-consuming process. Ex. 1033 (Smith Supp. Decl.) ¶¶ 6–8; Ex. 1027 (Weaver Tr.), 23:17–25:2; see also Ex. 10175, 132. Mr. Smith testifies that the benefits of using encryption would be sufficient to resolve the security concerns Patent Owner raises, and that any burden of generating a certificate would be outweighed by the benefits of using encryption and the memory advantages Zhu’s technique would offer. See Ex. 1033 (Smith Supp. Decl.) ¶¶ 4–15. Accordingly, we find that Patent Owner’s security concerns would be” slip op. at 25
Patent outcomesUS 11,018,724 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 11,018,724 - Unified Patents Inc. v. KCG Technologies LLCAll claims unpatentablePTAB · Feb 10, 2021 · IPR2019-01536 · APJ Kalyan K Deshpande · IPR · Final written decision
Claims 1–13 are unpatentable as obvious; the revised motion to amend is denied because proposed substitute claims 14–26 are unpatentable as obvious or indefinite.
RulingsFinal written decision- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied
“We agree with Petitioner. Proposed substitute claim 24 recites “the handheld device” without antecedent basis. This lack of antecedent basis renders proposed substitute claim 24 indefinite, as we noted in our Preliminary Guidance. Pet. Opp. to RMTA 25; Prelim. Guidance 8 (“Proposed substitute claim 24 also recites ‘the handheld device’ and also suffers from the lack of antecedent basis). Despite having the opportunity to correct its error and amend proposed substitute dependent claim 24 when independent claim 14 was amended to remove the recitation of “a handheld device,” Patent Owner did not do so in its Contingent Revised Motion to Amend. RMTA 31. Proposed substitute claim 24 is indefinite because the claim “fails to inform, with reasonable certainty, those skilled in the art about the scope of the invention.” Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898, 901 (2014); see USPTO Memorandum on the Approach to Indefiniteness Under 35 U.S.C. § 112 in AIA Post-Grant Proceedings (Jan. 6, 2021)13; see MPEP 2173.05(e) (9th ed., Rev. 08.2017, June 2020). This is because “the handheld device” is only recited in proposed substitute claim 24, and the proposed substitute claim fails to inform one skilled in the art the scope of invention related to synchronizing “data on the handheld device” “in the virtual smart phone.” Because proposed substitute claims 25 and 26 depend from proposed substitute claim 24, we similarly agree with Petitioner that claims 25 and 26 also are indefinite for lacking an antecedent basis for the term “handheld device.” Pet. Opp. to RMTA 25. Accordingly, we determine Petitioner has demonstrated by a preponderance of the evidence that proposed substitute claims 24–26 are unpatentable under 35 U.S.C. § 112 as indefinite.” slip op. at 40
- Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner
“Whether to treat a preamble term as a claim limitation is determined on the facts of each case in light of the claim as a whole and the invention described in the patent.” Am. Med. Sys., Inc. v. Biolitec, Inc., 618 F.3d 1354, 1358 (Fed. Cir. 2010) (quoting Storage Tech. Corp. v. Cisco Sys., Inc., 329 F.3d 823, 831 (Fed. Cir. 2003) (internal quotation marks omitted). “Absent clear reliance on the preamble in the prosecution history, or in situations where it is necessary to provide antecedent basis for the body of the claim, the preamble generally is not limiting.” Symantec Corp. v. Computer Assoc. Int’l, Inc., 522 F.3d 1279, 1288 (Fed. Cir. 2008) (internal quotation marks omitted). When the limitations in the body of the claim rely upon or derive essential structure from the preamble, then the preamble acts as a necessary component of the claimed invention and is limiting. See Eaton Corp. v. Rockwell Int’l Corp., 323 F.3d 1332, 1339 (Fed. Cir. 2003). A claim preamble also is limiting if the preamble is “necessary to give life, meaning, and vitality” to the claim. Pitney Bowes, Inc., 182 F.3d at 1305. We disagree with Patent Owner. Specifically, we do not agree that limitations in the body of the claims require the preamble to serve as an antecedent basis nor do they derive essential structure from the preamble. Rather, all of the elements recited in the body of claim 1 comprise a “virtual smart phone.” That is, we do not discern, and Patent Owner fails to persuasively point us to, any structure imparted by the preamble’s recitation of a “virtual smart phone.” See Pet. Reply 1–2. We similarly do not agree that the without the term “virtual smart phone” there would be no understanding of the “emulating” or “handheld device” limitations. Rather, the recited “software application executing on the processor” limitation provides the structure and meaning for the “emulating” of the “handheld device” features. Furthermore, we agree with the Petitioner that there is no evidence in the record that the prosecution history requires that the preamble is limiting, and the claims were distinguished during prosecution based on the recitation of a “virtual” smart phone. Id. at 2–3. Accordingly, we do not agree with Patent Owner that the preamble is limiting. slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“on the process to . . . emulate features of a handheld device.” Ex. 1001, 12:58–60 (emphasis added). Patent Owner argues that the term “‘emulate’ has a meaning in the art that is common and understood to mean ‘to imitate.’” PO Resp. 18. Patent Owner provides a dictionary definition to support its contention. Ex. 2004 (defining “emulate” as “to imitate in an effort to equal or surpass”). Patent Owner contends the use of “emulate” in claim 1 comports with its commonly understood meaning as “to imitate,” as does the use of the term “emulate” in the written description. Pet. 18–20 (citing Ex. 1001, 1:66–2:3, 2:6–3:5, 12:54–13:2 (claim 1)). Petitioner argues that the term “emulate” should be given its plain and ordinary meaning and does not contest Patent Owner’s construction of the term “emulate” as “to imitate.” Pet. 6–7; Pet. Reply 7. Petitioner, however, contests Patent Owner’s application of that construction to the asserted prior art. Pet. Reply 4–7 (citing Ex. 1034 ¶¶ 24–26). Petitioner specifically argues that Patent Owner implies that “(1) the imitation must be an exact duplicate in display and manner of input . . . or (2) the imitation relates only to the display and touch screen aspects.” Pet. Reply 4–5. In support of its position that Patent Owner’s interpretation of “to imitate” improperly narrows the meaning of “emulate,” Petitioner contends the written description discloses “less than full replication as emulation” and “controlling the handheld device th[r]ough control of a projected image using a variety of control input mechanisms provides emulation.” Pet. Reply 5–6 (citing Ex. 1001, 2:2–5, 3:57–61, 4:63–66, 6:24–42). Petitioner also notes that the dictionary definition Patent Owner proffered indicates that an exact duplication is not required. Pet. Reply 7 (“The complete definition of emulate [as] ‘to imitate in an effort to equal or surpass.’ Ex. 1004, 3”). We conclude that a preponderance of evidence supports the construction of the term “emulate” to mean “to imitate,” without any further restriction such as exact duplication or only display or touch screen aspects. Accordingly, we construe the term “emulate” as “to imitate.”” slip op. at 9
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner asserts that a person of ordinary skill in the art at or before the priority date of the ’955 patent “would have had a bachelor’s degree in electrical engineering, computer science, computer engineering, physics, or a related subject, and two to three years of work experience in the field of automotive information systems.” Pet. 6 (citing Ex. 1002 ¶¶ 38–39); Ex. 1034 ¶ 14 (Petitioner’s expert reiterating the same level of ordinary skill in the art). Patent Owner does not propose an ordinary level of skill in the art. We agree with and adopt the level of ordinary skill in the art as articulated by Petitioner.” slip op. at 10
Patent outcomesUS 9,671,955 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 9,671,955 - SZ Dji Technology Co., Ltd. / Parrot Inc. v. Drone-Control, LLCAll claims unpatentablePTAB · Jun 11, 2019 · IPR2018-00207 · APJ Frances L Ippolito · IPR · Final written decision
Claims 1–15 are unpatentable: claims 1, 3–6, 8–11, and 13–15 are anticipated by Thornberg ’983; claims 2, 7, and 12 are obvious over Thornberg ’983 and Karem. The motion to amend is denied.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner did not file a Patent Owner Response and has not otherwise disputed Petitioner’s proposed level of skill. See Tr. 77:1–6. We find, based on our review of the complete record, that the evidence of record supports a level of ordinary skill in the art consistent with Petitioner’s definition. Our findings are supported by the level of ordinary skill in the art reflected by the prior art of record and the ’116 patent. See Ex. 1001, 1:36–37 (“This invention relates generally to radio controlled toys such as airplanes and helicopters.”); Ex. 1006, 1:8–10 (“The present invention relates to the control of remotely operated vehicles, and more particularly to a variable reference for the control of a remotely operated vehicle.”), see id. at 3:41–44 (“The system provides for the referencing of vehicle commands based on an operator frame of reference so that control commands provided by the operator remain intuitive and independent of the orientation of the vehicle with respect to the operator.”). Thus, we adopt Petitioner’s proposed level of ordinary skill in the art and apply it to our discussion below.” slip op. at 11
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“Ex. 1006, 5:22–29. We further observe that once the disclosed pitch/roll commands (i.e., command data) are provided to the pitch axis and roll axis transformation functions, the pitch axis transformation 410 and roll axis transformation 412 use transformation equations to determine a transformed pitch stick signal (TPSS) and a transformed roll stick signal (TRSS). See Ex. 1006, 6:17–28. In other words, the flight control computer transforms received command pitch/roll data into TPSS and TRSS commands. In performing this transformation, the pitch axis transformation function 410 and the roll axis transformation function 412 also receive a transformation angle (θ) input. Id. at 5:30–32. Thornberg ’983 teaches that the transformation angle θ is determined based on the true heading of the vehicle as determined by the navigation system 36 and the desired vehicle reference and vehicle reference mode. Id. at 5:31–35. As discussed above, we find that the true heading of the vehicle as determined by navigation system 36 provides motion data generated by a sensor. Thornberg ’983 teaches that the transformations into TPSS and TRSS take into account transformation angle (θ), which Thornberg ’983 teaches is determined based on the true heading (i.e., motion data) of the vehicle and the control data (pitch/roll commands) received from control panel 200 of the remote operator control. See Ex. 1006, 4:29–33, 5:23–25, 5:36–38. Further, in the operator reference mode, the orientation of the operator/remote control upon activation of the operator mode is used as the reference axis (i.e., operator’s coordinate system). Additionally, as noted in the Petition (see Pet. 30–31), Thornberg ’983 teaches a variable operator reference mode in which the operator reference changes based on changes in the orientation of the operator control panel. Ex. 1006, 7:32–35. Based on the disclosure discussed above, we find that the pitch and roll commands received at lines 405, 415 in the operator mode teach command data in “a first coordinate system from a perspective of the remote control device” as recited in claim 1. Moreover, we find that Thornberg ’983 teaches that the received pitch/roll command data is transformed into control data in “a second coordinate system that is from a perspective of the RC aircraft.” Specifically, Thornberg ’983 teaches that the transformation equations 1 and 2 transform the pitch command and roll command based on the difference between the aircraft heading and the reference heading. See Ex. 1066, 7:9–11, 7:19–24. Further, Dr. Hansman testifies that TPSS and TRSS control data control the vehicle in the vehicle’s coordinate system, which is from the perspective of the vehicle. Ex. 1003 ¶ 411. We credit Dr. Hansman’s undisputed testimony in this regard because this testimony is consistent with the disclosure of Thornberg ’983, which teaches, among other things, that “[t]he system provides for the referencing of vehicle commands based on an operator frame of reference so that control commands provided by the operator remain intuitive and independent of the orientation of the vehicle with respect to the operator.” Ex. 1006, 3:41–44.” slip op. at 19
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentableUnpatentable
“[a] POSITA would have been motivated to modify Thornberg’s control panel 200 to “control” the UAV 100 in a hovering state, i.e., by sending appropriate lift command data to the vehicle when the operator releases the input controls as Karem teaches, in order to facilitate aerial tasks that may involve a hovering state, such as airborne surveillance, inspection, maintenance, and repair, that Thornberg teaches were “well known” uses of UAVs. Ex. 1006, 1:15-24; Ex. 1003, ¶443. Pet. 45. We are persuaded that Petitioner’s rationale and evidence demonstrate by a preponderance of the evidence that claims 2, 7, and 12 would have been obvious in view of Thornberg ’983 and Karem. For example, Petitioner’s arguments are supported by the disclosure of Karem, which teaches a remotely-operated vehicle in a hovering state (Ex. 1008, 7:13–23, 32–39, and Thornberg ’983 teaches remotely operated vehicles include helicopters (Ex. 1006, 1:14–17). Further, Petitioner’s arguments are supported by Dr. Hansman’s undisputed testimony that a POSITA would have been motivated to modify Thornberg ’983’s control panel 200 to control UAV 100 in a hovering state, i.e., by sending appropriate lift command data to the vehicle when the operator releases the input controls as Karem teaches, in order to facilitate aerial tasks that may involve a hovering state, such as airborne surveillance, inspection, maintenance, and repair. Ex. 1003 ¶ 443. This testimony is supported by Thornberg ’983’s teaching that (1) airborne surveillance, inspection, maintenance, and repair were well known uses of UAVs; and (2) remote operation of UAVs apply to remotely operated helicopters. See Ex. 1006, 1:15–24.” slip op. at 29
- Expert testimonyPetitioner expert creditedOther
“In the same manner described in the ’116 patent, we find that the orientation of the control panel in Thornberg ’983 indicates the angular displacement (i.e., position data) of the vehicle relative to the operator mode reference axis because the control panel is directed toward the vehicle. Thornberg ’983’s Figure 2 discloses that the control panel is directly facing the remotely operated vehicle, which is nearly identical to placement of the remote control device and RC aircraft in Figure 5 of the ’116 patent. Ex. 1001, 3:67–4:2, Fig. 5; Ex. 1006, Fig. 2.” slip op. at 50
Patent outcomesUS 9,079,116 unpatentable§ 102 anticipation§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 9,079,116 - Nautilus Hyosung Inc. v. Diebold Nixdorf, Inc.All claims unpatentablePTAB · Aug 14, 2017 · CBM2016-00034 · APJ Barbara A Benoit · CBM · Final written decision
Claims 1–24 are unpatentable under § 101; claims 1–3 and 5 are also anticipated by Riach, and specified claims are obvious over combinations of Riach, Graf, Gustin, and Anderson.
RulingsFinal written decision- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“For these reasons, we determine that claim 20—its focus and its” slip op. at 37
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“For the foregoing reasons, we conclude that claim 20 is directed to an” slip op. at 52
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“encompasses Riach’s process that copies a portion (but not all) of the original check image data to produce the required modified check image data. Accordingly, we agree that the portion of Riach on which Petitioner relies discloses step (b) of claim 1 that requires, among other limitations, the modified check image data not include at least some visual feature data included in the check image data. Pet. 30 (relying on Ex. 1008, 5:16–30, Figs. 4, 7).” slip op. at 73
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentable
“several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art.” KSR, 550 U.S. at 418. Rather, “it can be important to identify a reason that would have prompted a person of ordinary skill in the relevant field to combine the elements in the way the claimed new invention does.” Apple, 839 F.3d at 1058 (quoting KSR, 550 U.S. at 418–19); see also KSR, 550 U.S. at 418 (“[T]here must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.”) (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)).” slip op. at 89
Patent outcomesUS 7,314,163 unpatentable§ 101 eligibility§ 102 anticipation§ 103 obviousnesscites Alice · Mayo · Bilski · Enfish · Electric Power · Phillips · GrahamPatents in suitUS 7,314,163 - Captioncall, L.L.C. / Sorenson Communications, Inc. v. Ultratec, Inc.All claims unpatentablePTAB · Sep 7, 2016 · IPR2015-00637 · APJ William V Saindon · IPR · Final written decision
Claims 1–30 are unpatentable as obvious; Patent Owner’s contingent motion to amend is denied for lack of written-description support and indefiniteness.
RulingsFinal written decision- ExcludeMotion to exclude, grantedMotion to exclude, deniedGranted in part
“admitted that the patented features of voice and revoiced text are responsible for ‘giv[ing] the phone back to folks with hearing loss.’” PO Resp. 48 (emphasis added). Thus, Patent Owner is offering the statement for the truth that voice and re-voiced text gives the phone back to folks with hearing loss. Patent Owner’s argument that Mr. Puzey was discussing the existence of features in his company’s product rather than features in Patent Owner’s product does not change that his statement is offered as proof regarding an alleged long-felt need for the features. Accordingly, his testimony is hearsay. slip op. at 15
- Skill levelSkill level petitioner adoptedDecided for petitioner
“art is telecommunication systems. Thus, a [POSA] is a person familiar with at least that technology by way of background and/or experience.” CaptionCall, LLC v. Ultratec, Inc., Case IPR2013-00549, Paper 71, 13 (Final Written Decision) (PTAB 2015); see also CaptionCall, LLC v. Ultratec, Inc., Case IPR2013-00780, Paper 35, 9 (Final Written Decision) (PTAB 2015) (reaffirming our finding in IPR2013- 00549). Patent Owner states that it “does not agree” with that definition of a person of ordinary skill in the art, and that, “without waiving the foregoing objection and reserving all rights,” states that it will “appl[y]” our prior definition of a person of ordinary skill in the art “for purposes of this Response.” PO Resp. 3. By not setting forth arguments advocating a particular definition of the level of ordinary skill in the art, and by applying our prior definition, Patent Owner has waived arguments for any other definition. Accordingly, we adopt Petitioner’s proposed level of ordinary skill in the art, as expressed by its declarant, Mr. Occhiogrosso. Ex. 1009 ¶¶ 26–27. This person typically has “a bachelor’s degree” slip op. at 35
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionDecided for petitioner
“understand a “communication link,” as claimed, to refer to the “communication line” described in the specification. In particular, the link is “intended not only to apply to a traditional land-line . . . but also to all equivalents that offer similar functionality.” Id. at 8:60–63. A link could be “a portion of the bandwidth” of a particular connection, such that a single mode of connection (e.g., IP) could carry out two types of communication (voice and text), with each type corresponding to a different “communication link.” See id. at 8:44–47, 8:63–65. For example, as explained in the ’838 patent, “[e]ach of the telephone lines could be . . . a portion of the bandwidth of an ISDN or DSL service.” Id. at 8:53–65. Accordingly, we adopt Petitioner’s construction of “communication link” as “any communication session, protocol, link, connection, or path distinguishable from [another] communication link[].”” slip op. at 22
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“3. Combination of References As we discussed above, Petitioner’s combination takes the two-line” slip op. at 43
Patent outcomesUS 8,908,838 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSRPatents in suitUS 8,908,838 - Sega Of America, Inc. / Ubisoft, Inc. et al. v. Uniloc USA, Inc. And Uniloc Luxembourg S.A.All claims unpatentablePTAB · Mar 10, 2016 · IPR2014-01453 · APJ Donna M Praiss · IPR · Final written decision
Claims 1–20 are unpatentable: claims 1–11 and 17–20 as anticipated by Schull; claims 10–11 also as obvious over Schull; claims 12–14 as anticipated by Logan or obvious over Haines and Manduley; claims 15–16 as obvious …
RulingsFinal written decision- Skill levelOther
“between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of nonobviousness. Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966). An invention “composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art.” KSR, 550 U.S. at 418. Moreover, a determination of unpatentability on the ground of obviousness must include “articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006). The obviousness analysis “should be made explicit” and it “can be important to identify a reason that would have prompted a person of ordinary skill in the relevant field to combine the elements in the way the claimed new invention does.” KSR, 550 U.S. at 418.” slip op. at 24
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“In addition, we do not find credible Dr. DiEuliis’s testimony that the text in Figure 2B, which states “registration no. generated from user details added to serial no. is encrypted and re-arranged,” describes the addition of two numbers (registration no. and serial no.). There is no previous step in the flowchart depicted in Figure 2B that describes the step of generating the registration number to indicate that the registration number is an input, rather than an output. Ex. 1025, Fig. 2B; see Ex. 1026, Fig. 2. Further, as explained next, the “user details” encompass text, which further explains why the flowchart is not discussing the addition of numbers.” slip op. at 17
- Disclosure Requirements (§112) › Written description (Ariad)Not reached
“Regarding Petitioner’s assertion that certain claim terms lack definiteness or written description support, because those issues are neither appropriate for an inter partes review proceeding nor briefed by the parties, we do not address them in this decision. See 35 U.S.C. § 311(b). For purposes of this decision and for the reasons expressed by the District Court, we adopt and apply the constructions provided in the table above. See Ex. 1008, 53–54, 58–61.” slip op. at 12
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“We are persuaded by Petitioner’s argument that Schull discloses a summation algorithm for generating its Passwordable ID. As explained by Petitioner, Schull’s algorithm combines three ID numbers: Program ID, Feature ID, and Target ID, which Petitioner refers to as X, Y, and Z in its explanation. Pet. 21. The X number has “N” digits, the Y number has “M” digits, and the Z number has “T” digits. Id. The algorithm combines the numbers X, Y, and Z “(e.g., by concatenating them to produce a number” slip op. at 28
Patent outcomesUS 5,490,216 unpatentable§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 5,490,216 - Sega Of America, Inc. / Ubisoft, Inc. et al. v. Uniloc USA, Inc. And Uniloc Luxembourg S.A.All claims unpatentablePTAB · Mar 10, 2016 · IPR2015-01026 · APJ Donna M Praiss · IPR · Final written decision
Claims 1–20 are unpatentable: claims 1–11 and 17–20 over Schull, claims 12–14 over Logan and Haines with Manduley, and claims 15–16 over Logan and Grundy.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“We are not persuaded by Patent Owner’s evidence that the Australian provisional applications conveyed to a person of ordinary skill in the art a summation algorithm or a summer and equivalents thereof. The preponderance of the evidence is that the cited disclosures from the Australian provisional applications are insufficient for this purpose.” slip op. at 15
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“In addition, we do not find credible Dr. DiEuliis’s testimony that the text in Figure 2B, which states “registration no. generated from user details added to serial no. is encrypted and re-arranged,” describes the addition of two numbers (registration no. and serial no.). There is no previous step in the flowchart depicted in Figure 2B that describes the step of generating the registration number to indicate that the registration number is an input, rather than an output. Ex. 1025, Fig. 2B; see Ex. 1026, Fig. 2. Further, as explained next, the “user details” encompass text, which further explains why the flowchart is not discussing the addition of numbers.” slip op. at 17
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“We are persuaded by Petitioner’s argument that Schull discloses a summation algorithm for generating its Passwordable ID. As explained by Petitioner, Schull’s algorithm combines three ID numbers: Program ID, Feature ID, and Target ID, which Petitioner refers to as X, Y, and Z in its explanation. Pet. 21. The X number has “N” digits, the Y number has “M” digits, and the Z number has “T” digits. Id. The algorithm combines the numbers X, Y, and Z “(e.g., by concatenating them to produce a number 3 Patent Owner does not dispute Dr. Madisetti’s observation that Schull contains a typographical error (referring first to P, F, and T-digits and then to N, M, and T-digits) and his determination that N and M are equivalent to P and F. Ex. 1007 ¶ 41. with N+M+T digits)”. Ex. 1002, 7:24–25; Pet. 21; Ex. 1007 ¶ 41. In 1992, concatenating three integers to produce the desired result “boils down to two basic approaches: (1) multiplying the first integer and second integer by a power of ten (dependent on the number of digits of the subsequent numbers) and adding the three integers together, or (2) converting the integers to ‘strings,’ concatenating the strings, and converting the result back to an integer.” Ex. 1007 ¶ 42. Using the former approach to produce a number with the combined number of digits as the numbers being combined, which Petitioner argues is the one disclosed in Schull, Dr. Madisetti describes the mathematical operations that can be performed programmatically. The mathematical operation provided by Dr. Madisetti is X*10(M+T) + Y*10T + Z, which uses multiplication and addition. Id. ¶¶ 44; Pet. 21. According to Dr. Madisetti, this approach is a summation algorithm and is “computationally quicker” for the reason that “it is a matter of performing basic calculations and processing smaller numbers, as opposed to converting, combining and reconverting large strings . . . .” Ex. 1007 ¶ 43.” slip op. at 28
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“supports Petitioner’s assertion that claim 12 would have been obvious over the combination of Haines and Manduley. As an initial matter, we find Haines and Manduley to be analogous art. The PTO and its reviewing courts have developed and applied a two-step “test” to determine whether a prior art reference is “analogous” art and therefore may be used as evidence with respect to a question of obviousness under § 103. See In re Oetiker, 977 F.2d 1443, 1447 (Fed. Cir. 1992); In re Clay, 966 F.2d 656, 659 (Fed. Cir. 1992); In re Wood, 599 F.2d 1032 (CCPA 1979). Step 1 requires an answer to the following question: “Is the reference within the field of the inventor’s endeavor?” If the answer is “yes,” then the reference is “analogous” and therefore may be used as evidence. If the answer is “no,” then Step 2 requires an answer to the following question: “Is the reference reasonably pertinent to the particular problem the inventor was trying to solve?” If the answer is “yes,” then the reference is analogous and therefore may be used as evidence. Haines and Manduley are analogous art because, like the ’216 patent, they relate to systems for remotely permitted use of software on a device. Ex. 1007 ¶ 59. The scope of the ’216 patent is not limited to personal computers, but, rather, any “platform” on which software runs. Ex. 1001, 2:52–55 (“In broad terms, the system according to the invention is designed and adapted to allow digital data or software to run in a use mode on a platform . . . .”), 2:24–30 (“[T]he term ‘platform’ denotes an environment to be associated with a computer device such as a microprocessor or other data processing device which permits execution of the digital data . . . .”). Even if the Haines and Manduley references could be considered in a different field of endeavor than the ’216 patent because their intended use is postage and parcel systems rather than a personal computer, they are analogous art for the additional reason that they relate to the problem of restricting access to software to those who have a right to use it. Ex. 1001, 2:40–44 (“In this specification, ‘use mode’ refers to use of the digital data or software by its execution on a platform so as to fulfill the seller’s/licensor’s obligations in relation to the sale or license of the right to execute the digital data or software in the use mode.”); Ex. 1005, Abstr., 1:41–49 (“only authorized meter reconfigurations can occur”), 11:13–17; Ex. 1006, Abstr, 1:29–32 (“the marketer may wish to charge the customer a separate amount for each software function or each variety of data and the customer may wish to pick and choose among the functions and/or varieties”), 2:31–63.” slip op. at 43
Patent outcomesUS 5,490,216 unpatentable§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 5,490,216 - The United States Postal Service (Usps) / The United States Of America, As Represented By The Postmaster General v. Return Mail, Inc.All claims unpatentablePTAB · Oct 15, 2015 · CBM2014-00116 · APJ Kevin F Turner · CBM · Final written decision
Claims 39–44 are unpatentable under § 101 because they claim the abstract idea of relaying mailing address data without significantly more; anticipation by 1997 ACS was not shown.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for petitioner
“II. ANALYSIS A. Claim Construction We construe all terms, whether or not expressly discussed here, using the broadest reasonable construction in light of the ’548 Patent specification. See 37 C.F.R. § 42.300(b); see also In re Cuozzo Speed Techs., LLC, 93 F.3d 1268, 1278–80 (Fed. Cir. 2015) (“Congress implicitly approved the broadest reasonable interpretation standard in enacting the AIA,” and “the standard was properly adopted by PTO regulation.”). During the pre-trial stage of this proceeding, the parties submitted their constructions for specific claim terms and we adopted constructions consistent with the constructions adopted by the U.S. Court of Federal Claims (Ex. 1011). Dec. 8–10. Return Mail does not dispute the constructions adopted. PO Resp. 16–27. Upon review of the parties’ explanations and supporting evidence before us, we discern no reason to modify our claim constructions set forth in the Decision on Institution with respect to these claim terms. Dec. 8–10. For convenience, our claim constructions are reproduced in the table below:” slip op. at 6
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionIneligibleUnpatentable
“USPS has shown, by a preponderance of the evidence, that claim 39, as a whole, is directed to the processing of returned mail items, involving decoding information, obtaining an updated address, and electronically transmitting that updated address to a transferee. USPS has shown that the steps are directed to the abstract idea of relaying mailing address data, with the inclusion of an electrical transmission step. Regarding whether claim 39 includes limitations that amount to significantly more than the abstract idea of relaying mailing address data, per our claim construction, USPS has shown that the “decoding” step is “deciphering information into useable form,” but that does not necessarily bring it out of the realm of processes performed in the past by human beings. In fact, all of the claimed steps could be performed in the human mind, with the exception of the transmitting step. Additionally, USPS has shown that what the data might be deemed to represent to the human mind — e.g., “information indicating whether the sender wants a corrected address to be provided for the intended recipient” — does not substantially affect the underlying structure or function of the claim or any machine on which it is carried out. Consistent with USPS’s position, the ’548 Patent disclosure does not describe any particular hardware to perform the steps recited in claim 39, but refers merely in broad terms to generic computer hardware and software.” slip op. at 14
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptIneligibleUnpatentable
“significantly more than the abstract idea of relaying mailing address data, per our claim construction, USPS has shown that the “decoding” step is “deciphering information into useable form,” but that does not necessarily bring it out of the realm of processes performed in the past by human beings. In fact, all of the claimed steps could be performed in the human mind, with the exception of the transmitting step. Additionally, USPS has shown that what the data might be deemed to represent to the human mind — e.g., “information indicating whether the sender wants a corrected address to be provided for the intended recipient” — does not substantially affect the underlying structure or function of the claim or any machine on which it is carried out. Consistent with USPS’s position, the ’548 Patent disclosure does not describe any particular hardware to perform the steps recited in claim 39, but refers merely in broad terms to generic computer hardware and software.” slip op. at 14
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“deciding between the proffered constructions of “[d]ecipher information into useable form” and “[c]onvert information into useable form,” the court concluded that “using the terms ‘decipher’ and ‘deciphered’ more closely follow the customary meaning of the terms and reflects the claim language. This is because decoding must operate on encoded data,” which is recognized in the term “decipher” but not in “convert.” Ex. 1011, 22–23. USPS contends that “the carrier converts into intelligible form the participant code and endorsement thereby performing the claimed ‘decoding.’” Pet. 45. However, we find no support within 1997 ACS that the carrier decodes or deciphers the participant code or endorsement because the carrier (a person) is merely reading those indicators. The indicator “ADRESS SERVICE REQUESTED” is merely read and there is no disclosure that the carrier decodes the participant code or the keyline. We disagree with Dr. Lubenow that the plain-English endorsements “meet the plain and ordinary meaning of the term ‘code.’” Ex. 1028 ¶ 18. As such, we are not persuaded that the carrier in 1997 ACS acts to decode encoded data on the returned mail items.” slip op. at 24
Patent outcomesUS 6,826,548 unpatentableClaim construction§ 101 eligibility§ 102 anticipationcites Alice · MayoPatents in suitUS 6,826,548 - PNC Bank, N.A. / U.S. Bank, N. A. et al. v. Secure Axcess, LLCAll claims unpatentablePTAB · Sep 8, 2015 · CBM2015-00009 · APJ Barbara A Benoit · CBM · Final written decision
Claims 1–32 are unpatentable as obvious over the SHTTP document and Arent.
RulingsFinal written decision- BurdenFwd all claims unpatentableUnpatentable
“For the foregoing reasons, we determine that Petitioner has established by a preponderance of the evidence that the subject matter recited in claims 1–32 of the ’191 patent as a whole would have been obvious to one of ordinary skill in the art in view of the teachings of the SHTTP document and Arent. See 35 U.S.C. § 103(a).” slip op. at 71
- ExcludeMotion to exclude, deniedNot reached
“Information Prepared by Paul C. Clark” (Ex. 1018). Petitioner opposes, arguing that Exhibit 1018 is Dr. Clark’s notes used during his deposition. We did not refer to or rely on Exhibit 1018 in this Final Written Decision. As such, we need not reach the merits as to Patent Owner’s Motion to Exclude. Accordingly, Patent Owner’s Motion to Exclude certain evidence (Ex. 1018) is dismissed as moot.” slip op. at 71
- Skill levelSkill level board ownOther
“Petitioner’s expert adopted the level of ordinary skill in the art at the time of the invention used by Patent Owner’s expert. See Ex. 2006 ¶ 8 (testimony by Patent Owner’s declarant identifying the level of ordinary skill); Ex. 1002 ¶ 29 (testimony by Petitioner’s declarant). We do not 31 disagree with the parties. Therefore, one of ordinary skill in the art would have a bachelor’s degree in computer science, computer engineering, or an equivalent field and least two years of work experience in the area of information technology.” slip op. at 31
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“We agree with Petitioner and its declarant that the provisional application does not disclose the claimed authenticity key or preferences file or the claimed use thereof, as recited in each of independent claims 1, 17, 29, 31, and 32. The provisional application describes the invention in a few sentences. The scarcity of detail fails to provide sufficient disclosure of the claimed steps. For example, we see no disclosure of inserting any data in the provisional application, much less inserting something that could be identified as an authenticity key. Although a shared secret is disclosed, the shared secret is not described as being inserted into the web page or any other data. See id. at 5–6 (“The invention proposes to utilize the shared secret data created as part of being” a credit card holder of a particular credit 33 card company.). Moreover, the record evidence indicates that the provisional application does not disclose the recited “authenticity key.” Pet. 20 (citing Ex. 1002 at 18, ¶ 37). Thus, we agree with Petitioner that the provisional application lacks written description support for “authenticity key,” which is recited by all claims in the ’191 patent. Accordingly, we determine Arent is prior art under 102(a) to the ’191 patent and is available for consideration in this covered business method patent review.” slip op. at 33
Patent outcomesUS 7,631,191 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 7,631,191
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.