- Clearcorrect Operating, LLC v. Align Technology Inc.No claims unpatentablePTAB · Sep 29, 2026 · IPR2025-00817 · APJ Kevin F Turner · IPR · Final written decision
Claims 1–20 were not shown unpatentable because the cited combinations did not teach or suggest partial insertion of new scan data into an existing 3D model.
RulingsFinal written decision- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“that Boerjes alone teaches or suggests limitation 1(h) by a preponderance of the evidence. Although the Petition is persuasive that Boerjes allows a user to “identify areas that need replacing, such as ‘a margin line’ to be removed, ‘areas of poor margin preparation,’ and ‘holes or areas of incomplete scan[s],’” and that the user can identify regions of a prepared tooth surface requiring additional preparations and “supplemental scanning” (Pet. 32 (citing Ex. 1004 ¶¶ 189, 193, 196)), Boerjes is silent with respect to replacing at least a portion of the removed surface portion of the model using the received second scan data of the patient’s teeth, per claim 1. Boerjes certainly contemplates the re-scanning of the dentition, but does not assert partial insertion of new data into an existing 3D model. We acknowledge that Petitioner has argued (Pet. 43–44) that Boerjes’ Figure 4 and paragraph 144 of Boerjes teach partial replacement, but we are persuaded that those disclosures suggest total replacement and not partial replacement. The reference to “supplemented or replaced with new scan data” (Ex. 1004 ¶ 199) does not necessarily teach or suggest partial scanning, as Petitioner has argued. Additionally, Petitioner has argued (Pet. “combining historical three-dimensional data” (quoting Ex. 1004 ¶¶ 139, 144, 163), would have suggested to ordinarily skilled artisans that “Boerjes would be used to replace at least a portion of the model with the new scan data. Id. at 45 (citing Ex. 1003 ¶ 112). These disclosures are, however, applicable to scans that create complete replacement as well as partial replacement. We remain persuaded that Boerjes does not teach partial scans used to obtain partial replacement. Even under the “comprising” language of claim 1, for example, the complete replacement of a 3D model cannot teach or suggest “replacing at least a portion of the removed surface portion” without repudiating the language of the claim by making a portion be the entire model. Even if, as Petitioner asserts, “removing portions of a virtual model has been a well-known and routine technique in 3D modeling,” and the “process of replacing a user-identified portion would have been well within the skills of a POSITA” (Pet. 35), the disclosure of Boerjes does not teach or suggest such processes. Although Boerjes allows for the possibility that portions of a model can be identified as needing replacement or supplementation, it does not disclose the partial replacement required by the instant, independent claims. Boerjes’s actual disclosure details that supplemental scanning is used to compensate for an inadequate scan, but such supplemental scanning is not disclosed to be used to stitch together before-and-after models that have undergone an intervening physical change.” slip op. at 15
Patent outcomesUS 10,791,936 not shown unpatentable§ 103 obviousnesscites KSRPatents in suitUS 10,791,936 - Netflix, Inc. v. Divx, LLCAll claims unpatentablePTAB · Sep 21, 2026 · IPR2020-00558 · APJ Kevin F Turner · IPR · Remand
Claims 1–24 are unpatentable as obvious over Chen, Lindahl, and Hurst because the combination teaches the claim limitations and has motivation to combine and a reasonable expectation of success.
RulingsRemand decision- RemandOther
“On February 13, 2026, the Federal Circuit issued a decision in the appeal vacating the Second Final Decision as to all challenged claims and remanding for further proceedings. Netflix II, 7. The Federal Circuit reversed the Board’s claim construction, vacated the Board’s decision, and remanded for further proceedings consistent with the claim construction the 6 The First Final Decision also addressed Petitioner’s Motion to Exclude (Paper 42), where we granted-in-part, denied-in-part, and dismissed-in-part that Motion. See 1st Final Dec. 28–37. Our determinations on that Motion were a part of Petitioner’s appeal to the Federal Circuit. See Paper 52. As the Federal Circuit did not address this aspect of the First Final Written Decision, we determine our conclusions with respect to that Motion remain undisturbed. Federal Circuit adopted. Id. The Federal Circuit issued its mandate on March 23, 2026.” slip op. at 4
- Skill levelSkill level petitioner adoptedDecided for petitioner
“person of ordinary skill in the art at the time of the invention (“POSITA”) would have had “a bachelor’s degree in mechanical engineering, electrical engineering, computer science, or a similar field with at least two years of experience in video streaming and media security or . . . a master’s degree in mechanical engineering, electrical engineering, computer science, or a similar field with a specialization in video streaming and media security.” Pet. 14–15 (citing Ex. 1003 ¶¶ 65–67). Patent Owner does not refute Petitioner’s assessment and appears to apply such a level of skill in its arguments against combining Chen, Lindahl, and Hurst to teach or suggest the elements of the challenged claims. See generally PO Resp. As such, we continue to adopt and apply Petitioner’s unopposed position as to the level of ordinary skill in the art for purposes of this decision. See Inst. Dec. 6; 1st Final Dec. 6; 2nd Final Dec. 10.” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“In response, we conclude that the most natural reading of limitation [l] results from examination of the entire limitation: “locating encryption information that identifies encrypted portions of frames of video within the requested portions of the selected stream of protected video.” Ex. 1001, 27:54–57. The “within” most naturally connotes where the encrypted portions of frames of video occur, as opposed to determining where the encryption information may be located. Patent Owner’s interpretation is not wrong, i.e., the limitation could be read as Patent Owner suggests, leading to a narrower construction, but we are not persuaded that the construction of limitation [l] must be so limited, on the basis of the words themselves. We continue to reject Patent Owner’s interpretation that limitation [l] requires locating encryption information within the requested portions of the selected stream of protected video. See Inst. Dec. 27–30; 1st Final Dec. 8. Although it is apparent that encryption information can be found within the requested portions, we are not persuaded that the claim language or ’588 Patent implicitly or explicitly requires such a relationship. Likewise, although embodiments disclosed in the Specification of the ’588 Patent are consistent with Patent Owner’s more restrictive construction, the Specification also is consistent with the more grammatically correct construction as well. Thus, we construe limitation [l] as requiring that the encrypted portions of frames of video be within the requested portions of the selected stream of protected video, but we do not construe limitation [l] as requiring that the encryption information be within the requested portions of the selected stream of protected video.” slip op. at 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“We are persuaded that the Petition demonstrates that one of ordinary skill in the art would have had a motivation to combine Chen, Lindahl, and Hurst, as asserted by Petitioner. As the Federal Circuit found, the Petition pointed to and relied upon the portions in Chen describing pre-Chen art, without scalability or FEC features that were part of what Chen describes as aspects of its own inventive system. Netflix I, slip op. at 9–10 (citing Pet. 17–19, 69–70). We agree with Petitioner that “Chen-924 teaches several embodiments that adaptively stream alternative representations of a video using partially encrypted container files.” Pet. 20 (citing Ex. 1010, 14:41–15:60). We determine that Chen-924 provides support for the rationale provided in the Petition, and that one of ordinary skill in the art would have been motivated to combine Chen and Lindahl in view of the disclosure of Chen-924. As discussed above, the Petition does not rely solely on privacy concerns and improvements to efficiency as its motivation to combine the references. See Pet. 18–19 (specifying piracy concerns, improvements to the efficiency of adaptive streaming, optimization of the balance between bitrate and bandwidth, and improvements to the end-user experience with fast startup and seek). With respect to whether one of ordinary skill in the art would have” slip op. at 30
Patent outcomesUS 10,225,588 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 10,225,588 - Apple Inc. v. Proxense, LLCAll claims unpatentablePTAB · Sep 17, 2026 · IPR2025-00562 · APJ Thu A Dang · IPR · Final written decision
Claims 1–20 are unpatentable as obvious over Giobbi ’157, Giobbi ’139, and Dua; the Board also finds the claims unpatentable under the Broadcom grounds.
RulingsFinal written decision- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner
“IPR2024-00783, Ex. 1001, 22:36–49. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112 ¶ 6. See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112 ¶ 6 is not overcome.” slip op. at 17
- Skill levelOther
“differences between the claimed subject matter 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 non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25
- Expert testimonyPetitioner expert creditedDecided for petitioner
“We find persuasive Dr. Wolfe’s supporting testimony that a POSITA would have understood the terms “PDK” and “RDC” to have “definite structure.” Ex. 1013 ¶¶ 35–56. In particular, we find persuasive Dr. Wolfe’s testimony that the term “PDK,” for example, “encompasses at least ‘a collection of circuit components that includes an antenna, a transceiver, and a controller and memory for storing information particular to a user.’” Id. ¶ 35. Dr. Wolfe’s testimony is consistent with the Specification of the ’188 patent. See Ex. 1001, 5:42–6:7, 3:48–62. In particular, the Specification of the ’188 patent describes a microchip that stores information in memory and responds through an antenna when probed, which is consistent with Dr. Wolfe’s testimony. Id.; Ex. 1001, 1:30–62.” slip op. at 19
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“differences between the claimed subject matter 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 non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25
Patent outcomesUS 9,049,188 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,049,188 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00253 · APJ Scott C Moore · IPR · Final written decision
Claims 1–10 were not shown unpatentable under either § 103 ground because the evidence did not establish a reason to combine the references or a reasonable expectation of success.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent. D.I. 8. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’035 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition. C.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“In our Institution Decision, we construed the claim term “string separator character” to mean “a single-character string separator,” and invited the parties to raise any issues they had with this construction in future briefing. D.I. 10. Patent Owner subsequently indicated that it agreed with this construction. See PO Resp. 8. Petitioner did not raise any objections to this construction (see generally Pet. Reply). Accordingly, and in the absence of any dispute, we construe “string separator character” to mean “a single-character string separator.” Neither Petitioner nor Patent Owner ask us to adopt explicit constructions of any other claim terms. See Pet. 14, PO Resp. 8–9; Pet. Reply 1–23; PO Sur-reply 2–7. We also find that the issues in dispute can be resolved without construing any other claim terms. Accordingly, we do not adopt explicit constructions of any other claim terms. 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)). D.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” See PO Resp. 26–27. Indeed, Petitioner has given little or no explanation of how one of ordinary skill in the art allegedly would have taken the “idea of incremental search” and applied it to Lotus Notes. See, e.g., Ex. 2021, 116:20–117:17 (Petitioner’s declarant, Dr. Terveen, testifying that “Raskin is not explicitly talking about searching across a set of documents, but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin simply does not teach a mode of incremental searching that applies to the query-style, document-finding searching of the type Petitioner cites from Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Mr. Haeberli contrasting the Lotus Notes searches cited by Petitioner with Raskin’s searches). Raskin even states that it is “difficult or impossible to implement incremental searches” using interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Mr. Haeberli’s testimony that this passage of Raskin “directly undermines Dr. Terveen’s suggestion that a POSITA would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 24
Patent outcomesUS 7,370,035 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 7,370,035 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision
Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10
- Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner
“Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27
Patent outcomesUS 10,552,490 not shown unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 10,552,490 - Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision
Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther
“Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. 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 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable
“We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightMotivation not foundNot shown unpatentable
“Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42
Patent outcomesUS 9,633,139 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,633,139 - Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentablePTAB · Jun 11, 2026 · IPR2022-01151 · APJ Kevin F Turner · IPR · Remand
On remand, the Board held claims 1, 24, and 25 unpatentable as obvious over Buruganahalli; the copying evidence did not outweigh the strong obviousness showing.
RulingsRemand decision- RemandOther
“Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4
- Obviousness (§103) › Objective indicia / secondary considerations › CopyingObjective indicia outweighedDecided for petitioner
“given to the Eastern District of Virginia court’s opinion because it was later vacated. The district court considered all of the Read factors (applying Read Corp. v. Portec, Inc., 970 F.2d 816, 826-827 (Fed. Cir. 1992)), of which only the first factor is directed to deliberate copying, although factors 2 and 9 bear indirectly on the issue of copying. The district court determined that “[t]he fact that Cisco released products with Centripetal’s functionality within a year of these meetings goes beyond mere coincidence. Therefore, the fact that Cisco’s system mirrors the functionality of the Centripetal patents is compelling evidence that damages should be enhanced for copying.” Ex. 1027, 157. Without more, it is difficult to evaluate the processes that the district court employed to reach its determination. As the Federal Circuit instructed, we need “not [] go searching throughout the entire litigation record to find the evidence of copying, but [we have] an obligation to consider the specific evidence that was put before” us. Centripetal Networks, 19. We continue to determine that the vacated finding of the district court should be provided little weight, especially in view of the strong case of obviousness discussed above.” slip op. at 40
- Obviousness (§103) › Objective indicia / secondary considerations › Long-felt need / failure of othersObjective indicia outweighedDecided for petitioner
“need and industry recognition for the technology claimed in the ‘856 Patent because it describes the problem of detecting threats in encrypted traffic as ‘unsolvable.’” PO Resp. 68 (citing Ex. 1027, 64). Given that this is a press release by a company announcing that company’s new commercial product, however, we 8 The concurrence reevaluates Patent Owner’s evidence of industry praise and nexus, but we deem such considerations outside the remit of the Federal Circuit’s remand. are reluctant to give the “unsolvable” characterization much weight, as it may amount to puffery. But beyond that, it appears that the problem identified as “unsolvable” in the press release––“detect[ing] known attack signatures even in encrypted traffic”––had, in fact, already been solved in Buruganahalli, using the very same hello message, flow correlation, and man-in-the-middle techniques described in the ‘856 Patent. We thus cannot say that the press release identifies a long-felt need that was actually unsolved. See ZUP, 896 F.3d at 1374 (explaining that “[w]here the differences between the prior art and the claimed invention are . . . minimal . . . it cannot be said that any long-felt need was unsolved”) (quoting Geo. M. Martin Co. v. All. Mach. Sys. Int’l LLC, 618 F.3d 1294, 1304–05 (Fed. Cir. 2010) (first alteration in original)).” slip op. at 35
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“The District Court did not provide an element-by-element analysis of how the claims of the ‘856 Patent cover this description. See Ex. 1027, 41. However, from the description, we understand the Court to have concluded that the system receives rules, identifies a set of packets as part of a flow using the NetFlow logs, “determines” that encrypted packets in the flow match known malicious signatures based on unencrypted data in other packets (e.g., data in the SNI), and then filters the flow based in a URI (e.g., that from the SNI), routing it to the null interface. The Court does not describe how the system “determines” that encrypted packets match known malicious signatures based on information in unencrypted packets, but we assume that is done as in the ‘856 Patent, by correlation, i.e., an encrypted packet is “determined” to match a threat indicator if it is in the same flow as a packet with unencrypted information that matches the threat indicator.10 With that understanding, we conclude that the allegedly infringing system operates, as least at the level described in the court’s decision, in the same way Buruganahalli’s system operates, filtering encrypted packets due to their presence in a flow that includes packets with unencrypted data, such as in a handshaking packet. It follows that Patent Owner is unable to establish a nexus, because “[w]here the offered secondary consideration actually results from something other than what is both claimed and novel in the claim, there is no nexus to the merits of the claimed invention.” Novartis AG v. Torrent Pharms. Ltd., 853 F.3d 1316, 1330 10 See Ex. 1001, 9:3–10 (explaining that, at step 17, rule gate 120 may “determine . . . that the packets comprise data corresponding to the network-threat indicators, for example, by correlating the packets with one or more packets previously determined . . . to comprise data corresponding to the network-threat indicators based on data stored in [the] logs”).” slip op. at 38
Patent outcomesUS 9,917,856 unpatentable§ 103 obviousnessPatents in suitUS 9,917,856 - Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentablePTAB · Jun 11, 2026 · IPR2022-01199 · APJ Kevin F Turner · IPR · Remand
On remand, the Board held claims 1, 24, and 25 unpatentable as obvious over Buruganahalli; the copying evidence did not outweigh the strong obviousness showing.
RulingsRemand decision- RemandOther
“Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4
- Director reviewDirector review, deniedDenied
“not object to a new panel of APJs hearing this case if remanded.” Id. at 20. As such, Patent Owner requested Director Review (Paper 74), asking that the Director “de-institute,” based on an abuse of discretion. The Director (Paper 75) denied the request and directed the Board to assign a new panel on remand (see Papers 76, 77). B.” slip op. at 3
- Skill levelOther
“Level of Ordinary Skill in The Art We adopt the level of ordinary skill in the art adopted in the prior Decision. See Decision 25. F.” slip op. at 13
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“This argument is unpersuasive because Buruganahalli uses rules/policies to filter encrypted packets by correlating them with handshaking packets that have unencrypted data, in the same way that is done in the ‘856 Patent. The only “filtering step” in the patent that “use[s] rules to filter encrypted packets without decryption” (PO Resp. 20) is the hello message approach used, for example, at steps 19 and 23 (see id.), which is clearly disclosed in Buruganahalli.7 As explained above, the ‘856 Patent does not describe applying rules to encrypted packets. Instead, it describes (a) filtering encrypted packets by correlating them with unencrypted data in other packets and (b) by decrypting the packets and applying the rules that are recited in the claims to unencrypted data. As also explained above, the amendment added the rules of step 22, which are applied to decrypted data, to a claim that was drafted to cover filtering of encrypted packets. However, among the criteria used in the filtering performed at step 22 is a “uniform resource identifier (URI),” which, we conclude, covers Buruganahalli’s “domain name.” Thus, despite the error made during prosecution, the claims that issued cover Buruganahalli’s method of determining that a session should be filtered based on a domain name in unencrypted handshake data.” slip op. at 28
Patent outcomesUS 9,917,856 unpatentable§ 103 obviousnessPatents in suitUS 9,917,856 - Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentablePTAB · Jun 11, 2026 · IPR2022-00182 · APJ Kevin F Turner · IPR · Remand
On remand, claims 1, 24, and 25 are unpatentable under § 103 over Buruganahalli; the evidence of copying does not outweigh the strong obviousness showing.
RulingsRemand decision- RemandOther
“Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4
- Obviousness (§103) › Objective indicia / secondary considerations › CopyingObjective indicia outweighedNot shown unpatentable
“given to the Eastern District of Virginia court’s opinion because it was later vacated. The district court considered all of the Read factors (applying Read Corp. v. Portec, Inc., 970 F.2d 816, 826-827 (Fed. Cir. 1992)), of which only the first factor is directed to deliberate copying, although factors 2 and 9 bear indirectly on the issue of copying. The district court determined that “[t]he fact that Cisco released products with Centripetal’s functionality within a year of these meetings goes beyond mere coincidence. Therefore, the fact that Cisco’s system mirrors the functionality of the Centripetal patents is compelling evidence that damages should be enhanced for copying.” Ex. 1027, 157. Without more, it is difficult to evaluate the processes that the district court employed to reach its determination. As the Federal Circuit instructed, we need “not [] go searching throughout the entire litigation record to find the evidence of copying, but [we have] an obligation to consider the specific evidence that was put before” us. Centripetal Networks, 19. We continue to determine that the vacated finding of the district court should be provided little weight, especially in view of the strong case of obviousness discussed above. Examination of Aaron Striegel We also do not find the Aaron Striegel’s testimony to be particularly persuasive. The testimony provides statements such as “I found evidence that it could be plausible,” “[s]o we can see the timeline is very plausible,” and “I found it very plausible that indeed that this technology could have made its way into these respective accused products.” Ex. 1029, 31:12–32:3. This testimony suggests the possibility of copying but does not demonstrate actual evidence of copying. At most, this testimony indicates that further consideration of the underlying evidence is warranted, but does little to support an ultimate finding of copying. Again, even taking this testimony as evidence of copying, it still must stand up against the strong case of obviousness discussed above.” slip op. at 40
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“The District Court did not provide an element-by-element analysis of how the claims of the ‘856 Patent cover this description. See Ex. 1027, 41. However, from the description, we understand the Court to have concluded that the system receives rules, identifies a set of packets as part of a flow using the NetFlow logs, “determines” that encrypted packets in the flow match known malicious signatures based on unencrypted data in other packets (e.g., data in the SNI), and then filters the flow based in a URI (e.g., that from the SNI), routing it to the null interface. The Court does not describe how the system “determines” that encrypted packets match known malicious signatures based on information in unencrypted packets, but we assume that is done as in the ‘856 Patent, by correlation, i.e., an encrypted packet is “determined” to match a threat indicator if it is in the same flow as a packet with unencrypted information that matches the threat indicator.10 With that understanding, we conclude that the allegedly infringing system operates, as least at the level described in the court’s decision, in the same way Buruganahalli’s system operates, filtering encrypted packets due to their presence in a flow that includes packets with unencrypted data, such as in a handshaking packet. It follows that Patent Owner is unable to establish a nexus, because “[w]here the offered secondary consideration actually results from something other than what is both claimed and novel in the claim, there is no nexus to the merits of the claimed invention.” Novartis AG v. Torrent Pharms. Ltd., 853 F.3d 1316, 1330” slip op. at 38
- Obviousness (§103) › Objective indicia / secondary considerations › Long-felt need / failure of othersDecided for petitioner
“need and industry recognition for the technology claimed in the ‘856 Patent because it describes the problem of detecting threats in encrypted traffic as ‘unsolvable.’” PO Resp. 68 (citing Ex. 1027, 64). Given that this is a press release by a company announcing that company’s new commercial product, however, we 8 The concurrence reevaluates Patent Owner’s evidence of industry praise and nexus, but we deem such considerations outside the remit of the Federal Circuit’s remand. are reluctant to give the “unsolvable” characterization much weight, as it may amount to puffery. But beyond that, it appears that the problem identified as “unsolvable” in the press release––“detect[ing] known attack signatures even in encrypted traffic”––had, in fact, already been solved in Buruganahalli, using the very same hello message, flow correlation, and man-in-the-middle techniques described in the ‘856 Patent. We thus cannot say that the press release identifies a long-felt need that was actually unsolved. See ZUP, 896 F.3d at 1374 (explaining that “[w]here the differences between the prior art and the claimed invention are . . . minimal . . . it cannot be said that any long-felt need was unsolved”) (quoting Geo. M. Martin Co. v. All. Mach. Sys. Int’l LLC, 618 F.3d 1294, 1304–05 (Fed. Cir. 2010) (first alteration in original)).” slip op. at 35
Patent outcomesUS 9,917,856 unpatentable§ 103 obviousnessPatents in suitUS 9,917,856 - Apple Inc. v. Smart Mobile Technologies LLCSome claims unpatentablePTAB · Jun 3, 2026 · IPR2022-00981 · APJ Jameson Lee · IPR · Remand
On remand, claims 8–11, 13, 17, and 19 were held unpatentable over Rautiola, Regnier, and Sainton; claim 15 was not shown unpatentable.
RulingsRemand decision- RemandMixed
“8–11, 13, 15, 17, and 19, and remanded “for consideration of the patentability of those claims.” Id. at 14. We understand both the reversal and vacature are with respect to Ground 1 of alleged unpatentability, not Ground 2, because the Federal Circuit’s decision did not discuss anything relating to Ground 2. Paper 43. The parties agreed. Paper 44. In this remand proceeding, neither party requested the filing of additional briefing or evidence. In a telephone conference call, both parties expressed agreement with the Board (1) that “there is no issue regarding collateral estoppel or issue preclusion with respect to dependent claims 8– 11, 13, 15, 17, and 19, and (2) that the remand proceeding would not involve the Board revisiting any matter or issue concerning alleged obviousness of claims 1, 8, 9, 11, 13, 17, and 19 over Ground 2.4 Papers 43, 44. The parties also agreed that the remand proceeding would only involve the Board reviewing the alleged obviousness of dependent claims 8–11, 13, 15, 17, and 19 as obvious over Rautiola, Regnier, and Sainton. Id. We have authority to conduct this inter partes review under 35 U.S.C. § 6. This Final Written Decision on Remand is issued pursuant to 35 U.S.C. § 318(a) and 37 C.F.R. § 42.73. On the record before us, which is the same as the record before us at the time we issued the first final written decision (Paper 34), we determine that Petitioner has proved by a preponderance of the evidence that claims 8– 11, 13, 17, and 19, but not claim 15, of the ’936 patent are unpatentable over Rautiola, Regnier, and Sainton.” slip op. at 3
- Expert testimonyPetitioner expert creditedDecided for patent owner
“5. Petitioner’s Request to Discredit Dr. Cooklev’s Declaration Petitioner makes several arguments discrediting Dr. Cooklev’s declaration (Ex. 2031) and asserts that Dr. Cooklev’s declaration should be accorded little to no weight. Reply 13–14. We have already considered and rejected this request in the Final Written Decision issued on November 7, 2023. Paper 34, 21–23. Our reasoning need not be reiterated here. Petitioner does not persuade us that Dr. Cooklev’s declaration testimony should be accorded little to no weight.” slip op. at 15
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner does not dispute Petition’s definition of level of ordinary skill. See generally PO Resp. Patent Owner’s expert, Dr. Cooklev, accepts Dr. Kotzin’s proposed level of ordinary skill in the art. Ex. 2031 ¶ 24. We adopt Petitioner’s proposal regarding the level of ordinary skill in the art. This level of ordinary skill in the art is supported by the testimony of Dr. Kotzin (Ex. 1003 ¶¶ 20–22) and is consistent with the level reflected in the ’936 patent and the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 9
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“only when it is analogous to the claimed invention.” Airbus S.A.S. v. Firepass Corp., 941 F.3d 1374, 1379 (Fed. Cir. 2019). A prior art reference constitutes analogous art if it is “from the same field of endeavor” or “reasonably pertinent to the particular problem with which the inventor is involved.” In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004). The petitioner bears the burden of establishing that a reference is analogous art. See Sanofi-Aventis Deutschland GmbH v. Mylan Pharms. Inc., 66 F.4th 1373, 1377 (Fed. Cir. 2023).” slip op. at 16
Patent outcomesUS 8,472,936 mixed§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,472,936
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.