- Samsung Electronics Co. Ltd. v. Ward Participations B.V.All claims unpatentablePTAB · Apr 21, 2023 · PGR2022-00007 · APJ Thu A Dang · PGR · Final written decision
Claims 1–19 are unpatentable: they lack written-description support, and the asserted combinations of Ellison and Muir, with Al-Salqan or Searle for dependent claims, render them obvious.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable
“specific, and must be determined on a case-by-case basis. Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). The test for sufficiency of support is whether the disclosure of the application relied upon “reasonably conveys to the artisan that the inventor had possession at that time of the later claimed subject matter.” Vas–Cath Inc. v. Mahurkar, 935 F.2d 1555, 1563 (Fed. Cir. 1991). “One shows that one is ‘in possession’ of the invention by describing the invention, with all its claimed limitations,” wherein, “[w]hile the meaning of terms, phrases, or diagrams in a disclosure is to be explained or interpreted from the vantage point of one skilled in the art, all the limitations must appear in the specification.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997). That is, “it is the specification itself that must demonstrate possession” and “a description that merely renders the invention obvious does not satisfy the [written description] requirement.” Ariad Pharm., 598 F.3d at 1351 (“[T]he level of detail required to satisfy the written description requirement varies depending on the nature and scope of the claims and on the complexity and predictability of the relevant technology.”).” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionDecided for petitioner
“Only those terms in controversy need to be construed, and only to the extent necessary to resolve the controversy. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms that . . . are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 22
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“vi. Proposed Combination of Ellison and Muir Petitioner contends that Ellison discloses “an isolated execution architecture that improves security in a computer system or platform by implementing several levels of hierarchy and normal and isolation execution modes for the operating system and processor.” Pet. 46–47 (citing Ex. 1006, 1:12–15, 2:40–61, Fig. 1). Although Petitioner acknowledges that Ellison “does not reveal details of [] a system or transaction between multiple parties,” Petitioner relies on Muir for such teaching. Id. at 47. According to Petitioner, a POSITA looking to implement Ellison’s isolated execution architecture in a computer with multiple devices “would have looked to Muir’s teachings to implement a secure electronic transaction between two parties,” because “both Ellison and Muir are related to providing improved security for transactions involving keys using cryptographic techniques.” Id. at 48 (citing Ex. 1006, 1:38–51; Ex. 1008, 7, 8, 11; Ex. 1003 ¶ 66). We agree with Petitioner’s motivation to combine the teachings of Ellison and Muir, as supported by Dr. Black’s testimony (Pet. 46–51 (citing Ex. 1003 ¶¶ 64–71), and find unavailing Patent Owner’s contention that “a POSITA would not have looked to Muir to cure the deficiencies of Ellison.” PO Resp. 39. Although Patent Owner contends that “Petitioner fails to show with particularity the why and how required for its obviousness combinations” (PO Resp. 68), we agree with Petitioner’s contention that, in the combination of Ellison and Muir, “each device involved in a transaction would have been connected through a computer network such as Mui’s included Ellison’s isolated execution architecture and one or more parts of Muir’s system.” Pet. 48. We credit the testimony of Dr. Black as sufficient support for Petitioner’s contention, when he explains, “a POSITA would have viewed extension of Ellison’s system to include the multi-party transactions described by Muir to have been a natural and obvious extension,” wherein a “a POSITA would have been motivated to enable such multi-party transaction [] in Ellison’s system to increase the functionality and usefulness of Ellison’s system.” See Ex. 1003 ¶ 69. Thus, we find unavailing Patent Owner’s contention that Petitioner “has not established its prima facie case.” PO Resp. 68.” slip op. at 44
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“We find unavailing Patent Owner’s contention which is directed to Ellison alone, and not to the combination of Ellison and Muir proposed by Petitioner. See PO Resp. 47. We agree with Petitioner’s contention that Ellison’s private key 204 “can be used ‘to encrypt a digest of a message producing a signature” (see Ex. 1006, 60–65 (“In the digital signature generation process, the protected private key 204 is used as an encryption key to encrypt a digest of a message producing a signature”)), wherein “Muir clearly discloses using a digital signature for transactions between two parties.” Pet. Reply 25 (citing Ex. 1006, 8:59–65; Ex. 1008, 2, 3, 6, 9, 10, 12, 18; Ex. 1032 ¶ 29). Thus, contrary to Patent Owner’s contention, we agree with Petitioner’s position regarding the combination of Ellison and Muir for teaching that “private key 204” is “for the protection of digital transactions involving two parties.” PO Resp. 47. Based on the complete record presented, we determine Petitioner has demonstrated sufficiently that a POSITA would have been motivated to combine Ellison and Muir, wherein the combination of Ellison and Muir teaches “providing a private key in a memory of said electronic device,” the device,” the private key being “inaccessible to a user of said electronic device,” and “encrypted when the private key is stored in said memory,” as recited in claim 1.” slip op. at 36
Patent outcomesUS 10,992,480 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 10,992,480 - PTAB · Apr 26, 2022 · PGR2022-00007 · APJ Thu A Dang · PGR · Institution
The Board instituted PGR on claims 1–19 based on likely lack of written description and obviousness over Ellison and Muir, with Al-Salqan or Searle added for certain claims.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Section 324(a) of Title 35 of the United States Code provides that a post-grant review may not be instituted “unless . . . the information presented in the petition . . . , if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” Upon consideration of the evidence and arguments in the Petition (including its supporting testimonial evidence) as well as the evidence and arguments in the Preliminary Response, for the reasons below, we determine that the information in the Petition satisfies the threshold provided in 35 U.S.C. § 324(a) and we institute this proceeding.” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther
“not present in the written description whose benefit is sought it must be shown that a person of ordinary skill would have understood, at the time the patent application was filed, that the description requires that limitation.” Hyatt v. Boone, 146 F.3d 1348, 1353 (Fed. Cir. 1998) (emphasis added). In other words, where the written description fails to disclose an element explicitly, “the applicant must show that any absent text is necessarily comprehended in the description provided and would have been so understood at the time the patent application was filed.” Id. at 1354–55 (emphases added). At this stage of the proceeding, we do not find persuasive Patent Owner’s contention that a person of ordinary skill in the art would have recognized that authentication software has a “private key” that forms an “integral part of the authentication software component and/or is embedded therein” (Prelim. Resp. 13 (quoting Ex. 1001, 5:39–40)), in view of the cited section in the Detailed Description describing the authentication software as comprising the unique serial number, the unique software ID and/or a private encryption key, but only the unique serial number or the unique software ID is embedded therein. See Ex. 1001, 5:39–49. That is, we are unpersuaded at this stage of the proceeding that the person of ordinary skill in the art will directly and unambiguously deduce from the ’773 application as filed that the “private encryption key” is embedded in the authentication software, as Patent Owner contends. Prelim. Resp. 13. Instead, we find persuasive Petitioner’s contention that the ’480 patent (i.e., the ’773 application) merely teaches storing the digital signing algorithm in a secure part of the BIOS 44 but is silent as to storage of the private key. Pet. 18 (citing Ex. 1001, 9:27–34, 13:31–44; Ex. 1003). As Petitioner contends, the” slip op. at 20
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“The Specification of the ’480 patent discloses secure area 62 only accessible to BIOS 44, comprising applications and storage locations not reported to operating system 48 (Ex. 1001, 8:62–9:1), wherein, as shown in Figure 3, secure area 62 comprises secure storage location 60, recovery application 56, and authentication software 54. Id. at 9:7–11. That is, the Specification shows “secure memory inaccessible to said operating system” as a location that holds software not accessible to operating system 48. Id. Nothing in the Specification, or the general knowledge in the art, limits “secure memory inaccessible to said operating system” to Ellison’s “isolated storage area 70,” or precludes Ellison’s “secure platform 200,” as Patent Owner proposes. Prelim. Resp. 35–36. In fact, nothing in the Specification or the general knowledge in the art limits the “storage” to any amount of time in the secure memory. We are unpersuaded by Patent Owner’s apparent position that software that is loaded into a secure location of execution is not software that is “stored” in a “secure memory” location. Prelim. Resp. 35–36. In view of the Specification and the general knowledge in the art, we determine that the term “stored in said secure memory inaccessible to said operating system” encompasses being held in any secure location that is determination here is preliminary, and the parties are invited to address this claim construction issue at trial, if so desired.” slip op. at 25
- Obviousness (§103) › Motivation to combine / reasonable expectation of successInstituted
“ii. “providing a private key in a memory of said electronic device, said memory being a secure part of a Basic In Out System or any other secure location in said electronic device, which private key is inaccessible to a user of said electronic device, wherein the private key is encrypted when the private key is stored in said memory” (claim 1) Petitioner contends that Ellison’s “isolated execution regions ‘is accessible only to elements of the operating system and processor operating in isolated execution mode,’” and that “isolated mode applets 461 to 46K and their data are tamper-resistant and monitor-resistant from all software attacks from other applets and OS 12.” Pet. 56 (citing Ex. 1006, 4:1–22). According to Petitioner, “[a] user is not an element of the operating system and processor operating in isolated execution mode, and therefore 6 The issue of whether the preamble is limiting need not be resolved at this stage of the proceeding because, regardless of whether the preamble is limiting, Petitioner shows sufficiently for purposes of institution, and Patent Owner does not dispute, that the combination of Ellison and Muir teaches a method for performing an electronic transaction between first and second transaction parties, as recited in the preamble. See Realtime Data, 912 F.3d at 1375 (noting that we need only construe “only those terms that . . . are in controversy”). Ex. 1003 ¶ 92). Petitioner then contends that Ellison discloses “a secure platform 200 that ‘includes the OS nub 16, the processor nub 18, a key generator 240, . . . , all operating within the isolated execution environment.’” Pet. 58 (citing Ex. 1006, 8:25–32; Ex. 1003 ¶ 95). Petitioner also contends that “the private key 204 can be stored in the cryptographic key storage 155 and in a multiple key storage of the non-volatile flash memory 160,” and “only the OS nub 16 can retrieve the private key.” Id. at 59–60. According to Petitioner, because “the OS nub 16 is within the secure platform and isolated environment,” it would have been obvious to a person of ordinary skill in the art (POSITA) that “the cryptographic key storage 155 and the non-volatile flash memory 160 are secure storage locations so that the private key 204 can be accessed securely by OS nub 16.” Id. (citing Ex. 1003 ¶ 96). Thus, Petitioner contends that “Ellison explicitly teaches that the OS nub 16 and private key 204 shown in platform 200 all operate within the isolated execution environment,” which “would indicate to a POSITA that private key 204 is stored in a secure memory and is inaccessible to a user of said electronic device.” Id. Nevertheless, Petitioner contends that Muir “explicitly teaches a private key 167 stored in a restricted memory space 170 which is inaccessible to the operating system.” Id. at 60 (citing Ex. 1008, 7–9, 3). Petitioner then contends that Ellison’s OS nub 16 “retrieves the encrypted private key 204 and decrypts it for use in the isolated environment.” Pet. 61 (citing Ex. 1006, 8:33–65, 11:1–12:26). Thus, Petitioner contends that “Ellison and Muir render obvious the private key 204 being encrypted when stored in a secure memory (e.g.,” slip op. at 32
Claim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 10,992,480
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.