- Uatp IP LLC v. Slick Slide LLCSome claims unpatentablePTAB · Oct 2, 2026 · PGR2024-00054 · APJ Brian D Range · PGR · Final written decision
Claims 22–26 are unpatentable based on obviousness; claims 1–17, 27, and 28 were not shown unpatentable. Patent Owner’s motion to terminate was denied.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“1. Mesh Layer Petitioner contends “no formal claim construction is necessary in this” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“5. Analysis On this complete record, we determine that Petitioner’s arguments do” slip op. at 31
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“form of nylon and some form of Teflon (and possible combinations thereof) having the specific coefficient of friction range given in limitation [1c] breaks down, because the building blocks of the obviousness argument are not sufficiently identified in Phillips alone, nor in the supporting testimony. Accordingly, we determine that Petitioner’s arguments and evidence fail to show that Phillips renders the challenged claims obvious. 6. Conclusion Based on the foregoing, we determine that Petitioner has not established by a preponderance of the evidence that claims 1–4, 6, and 7 would have been anticipated by or obvious in view of Phillips.” slip op. at 33
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“2. Products and Nexus We first consider the issue of whether certain evidence relied upon by” slip op. at 20
Patent outcomesUS 11,998,854 mixedClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · Graham · NautilusPatents in suitUS 11,998,854 - Weatherford U.S., L.P v. Halliburton Energy Services, Inc.Some claims unpatentablePTAB · Dec 9, 2025 · IPR2024-00990 · APJ Brent M Dougal · IPR · Final written decision
Claims 11–12 and 14–20 are unpatentable; claims 1–10 and 21–23 are not shown unpatentable. Substitute claims 29–37 are unpatentable, and the motion to amend is denied as to them.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“The level of skill is uncontested. Patent Owner adopts the level of skill identified by Petitioner as: [at] the time of the alleged invention in 2018, a POSITA[2] would have had a B.S. degree in mechanical or petroleum engineering or a similar technical discipline, with at least five years of experience in oil or gas well drilling, completion, and/or subsurface production operations or in technical support of such operations including at least some experience in unconsolidated formations utilizing sand control methods and means. Also,” slip op. at 8
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“on embodiments of Yeh with concentric sand screens having nine shunt tubes (six transport tubes and three packing tubes) (Yeh Figures 4A–B) and eccentric sand screens with four shunt tubes (two transport tubes and two packing tubes) (Yeh Figures 8A, 8C). See Pet. 32–37, 39, 41–43. Yet, Petitioner’s reasoning as to why “a higher-pressure shunt tube assembly necessitated greater wall thickness” rests on an unspoken one to one comparison between the shunt tubes of the different systems. See id.; see also Ex. 1003 ¶¶ 291–297 (Petitioner’s declarant comparing possible transport tubes of different pressure regions without considering or addressing any difference in the number of transport tubes). However, the embodiments relied on by Petitioner have different numbers of shunt tubes, and thus the greater wall thickness does not appear to be “necessitated” in the way inferred by Petitioner. Further, Petitioner’s analysis would seem to be most appropriate when comparing two concentric sand screens for different pressure regions, or two eccentric sand screens for different pressure regions. relies on Yeh’s teachings related to a horizontal well bore of 5000 feet for the “concentric screen → crossover tool → eccentric screen” arrangement, as well as, for why the concentric screen needs to be rated for a high pressure. Pet. 32–37, 39, 41–43. Petitioner also refers to these features for why one of skill in the art would combine the teachings of Yeh and Yeh2. Id. at 32. However, on cross-examination, Petitioner’s declarant agreed that it is concentric sand screens having a 6x3 shunt tube design that would provide the noted benefits of being rated for a higher pressure and being more robust (as relied on in the Petition), as compared to eccentric sand screens. Ex. 2013, 42:20–43:8; Sur-reply 4–5. This also exposes another issue with Petitioner’s arguments. Though Petitioner identifies that one of skill in the art would be aware that material choice, wall thickness, and pipe diameter all impact burst pressure of a pipe (Pet. 42 (citing Ex. 1017, 24 (Equation (14))), the Petition essentially ignores the fact that the claims do not require a single pipe in isolation. The claims require two shunt tube assemblies, each surrounding a base pipe within a wellbore. It is uncontested that a wellbore provides a confined space for such a system and thus any change in wall thickness of one pipe can result in a significant impact in the function of the other pipes. We find the testimony of Petitioner’s declarant (see, e.g., Ex. 1003 ¶¶ 290–297) unpersuasive when discussing wall thickness because it focusses on basic considerations of a standalone pipe, without sufficient consideration of the claimed completion assembly with its required pipe and tube structure. PO Resp. 20–26.” slip op. at 17
- Strike new argumentNew argument disregardedDecided for patent owner
“In response to Patent Owner’s argument concerning Yeh’s embodiments relied on in the Petition, Petitioner argues for the first time that Patent Owner’s declarant “conceded, Yeh discloses that both concentric and 47:19–48:21). Petitioner does not provide a citation to Yeh or a citation to where the Petition relies on the same number of shunt tubes between concentric and eccentric screens. The deposition cited by Petitioner discusses Yeh at column 16, lines 26 through 35. However, the Petition does not cite or rely on these teachings of Yeh. Thus, we decline to consider this late argument.4 See 35 U.S.C. § 312(a)(3) (requiring the petition to identify “with particularity . . . the grounds on which the challenge to each claim is based, and the evidence that supports the grounds”); 37 C.F.R. § 42.104(b)(5).” slip op. at 18
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentable
“Thus, we agree with Petitioner that the combination of Yeh and Yeh2 teaches determining the shunt tube system operating pressures associated with the distal end of the production zone, but also more generally, determining the operating pressures along the entire production zone. With this knowledge of the system operating pressures, Petitioner argues that one of skill in the art would have selected eccentric screens for the distal end of the production zone “at any point at which the slurry pressure dropped below the pressure capacity of the eccentric screen shunt tubes.” Pet. 66 (citing Ex. 1005, 30:16–20; Ex. 1003 ¶ 388). In other words, knowing that the pressure decreases as you approach the toe, Yeh’s low-pressure rated eccentric screens could be used from some point prior to and covering the toe. determined pressure.” PO Resp. 37–38. We disagree. As discussed above, the record supports Petitioner’s position that one of skill in the art would have “understood the need to determine the shunt tube system operating pressure throughout the horizontal wellbore.” Ex. 1003 ¶ 383; see also Pet. 64–65. We find convincing Petitioner’s argument that one of skill with this understanding of the system pressures would select a shunt tube system rated to not only address the distal end, but also to address the needs of the adjacent region, so long as the pressure rating supported such a selection. See Pet. 65–67; Ex. 1003 ¶¶ 385–388.” slip op. at 22
Patent outcomesUS 11,333,007 mixedClaim construction§ 101 eligibility§ 103 obviousness§ 112 disclosurecites GrahamPatents in suitUS 11,333,007 - Google LLC v. Sandpiper CDN, LLCInstitutedPTAB · Nov 25, 2025 · IPR2025-00860 · APJ Sheila F Mcshane · IPR · Institution
The Board instituted review of claims 1–20 on all asserted grounds, finding a reasonable likelihood that the Dilley, Pai, and Wang combination renders the claims obvious.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“partes review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a). Under 35 U.S.C. § 314(a), we may not authorize an inter partes review unless the information in the petition and the preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We therefore institute inter partes review as to all of the challenged claims of the ’573 patent and all of the asserted grounds of unpatentability in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“III. ANALYSIS A. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art: would have had at least a bachelor’s degree in computer science, electrical engineering, or a related field, and at least two years of work or research experience in the field of content delivery management or networks. Work experience can substitute for formal education and additional formal education can substitute for work experience. Pet. 12 (citing Ex. 1006 ¶ 70). Patent Owner asserts that “the Board does not need to resolve the appropriate level of skill for a POSA [person of ordinary skill in the art] for purposes of deciding institution because the Petition fails under any articulation of a POSA.” Prelim Resp. 10. For the purposes of this Decision, we adopt the assessment offered by Petitioner as it is consistent with the ’573 patent and the prior art before us. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner asserts that no claim terms need to be expressly construed by the Board and all terms should be given their ordinary meaning. Pet. 12. Patent Owner agrees that the Phillips standard applies. Prelim. Resp. 10. We determine that we need not expressly construe any claim terms at this juncture. 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 9
- Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner
“We consider the disclosures of the Provisional Application, which refer to cases 1 and 2, in which requests are redirected to an origin server for lower popularity content and to a parent server for medium popularity content at steps 522 and 524 as shown in Figure 5, respectively, wherein the edge server receives a redirect from the popularity service without a “followme” flag. See Ex. 1011 ¶¶ 43, 44. The Provisional Application also discloses that, by comparison, if there is a “follow-me” redirect sent to the edge server, it obtains and caches a resource as shown at step 528 for higher popularity content. Id. ¶ 44. On this record, as Patent Owner asserts, these disclosures are consistent with technical reasons provided in the Provisional Application for instructing the edge server not to cache unpopular resources. See Ex. 1011 ¶¶ 68–69. In light of these disclosures, we preliminarily find support for Dr. Shenoy’s testimony that, even with the words “instruction to not cache” are not literally recited in the Provisional Application, caching and not caching are alternative options that indicate the instruction to the edge server that will be implemented for each option. See Ex. 2014 ¶ 56. Further, these disclosures provide support for Dr. Shenoy’s testimony that the disclosures “reasonably convey to those skilled in the art that Patent Owner had possession of the edge server receiving an instruction to not cache the resource (and instead simply forward the redirect).” Id. In re Johnson states that “it is not true that the factual context out of which the question under § 112 arises is immaterial. Quite the contrary. Here, . . . the ‘written description’ in the [] specification supported the claims in the absence of the limitation, and that specification, having described the whole, necessarily described the part remaining.” See Johnson, 558 F.2d at 1019. This is consistent with M.P.E.P. § 2173.05(i) which states, “[i]f alternative elements are positively recited in the specification, they may be explicitly excluded in the claims.” M.P.E.P. § 2173.05(i). Further, “the failure of the specification to specifically mention a limitation that later appears in the claims is not a fatal one when one skilled in the art would recognize upon reading the specification that the new language reflects what the specification shows has been invented.” All Dental Prodx, LLC v. Advantage Dental Prod., Inc., 309 F.3d 774, 779 (Fed. Cir. 2002). Even though we do not discern that the Provisional Application explicitly discloses an “instruction to not cache,” at least on this preliminary record, and for the purposes of this Decision, there is positive recital of instructions to cache in the Provisional Application and Petitioner has provided sufficient supporting evidence that caching and not caching are alternative options. Further, there is sufficient evidence, in the context of the disclosures of written description support in the Provisional Application, providing support for Dr. Shenoy’s testimony that Patent Owner had possession of an edge server receiving an instruction to not cache the resource. Nonetheless, we invite additional briefing on these issues, including issues relating to alternative options of caching and not caching. On this preliminary record, we find that the ’573 patent has a priority date of April 2, 2008, which predates the earliest possible date on which Newton-471 could be effective as prior art, September 30, 2014 (the date on which the earliest application in the priority chain of Newton-471 was filed). Accordingly, we preliminarily find that Newton-471 is not prior art to the challenged claims. Thus, on the present record, Petitioner has not demonstrated a reasonable likelihood that it would prevail in showing that claims 1–20 are anticipated by Newton-471.” slip op. at 13
Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 10,924,573 - Google LLC v. Sandpiper CDN, LLCInstitutedPTAB · Nov 10, 2025 · IPR2025-00806 · APJ Sheila F Mcshane · IPR · Institution
The Board instituted IPR on claims 1–20 and all asserted grounds, finding a reasonable likelihood of success on the § 103 challenges.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“partes review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a). Under 35 U.S.C. § 314(a), we may not authorize an inter partes review unless the information in the petition and the preliminary response “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We therefore institute inter partes review as to all of the challenged claims of the ’517 patent and all of the asserted grounds of unpatentability in the Petition.” slip op. at 2
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“application must comply with the written description requirement of 35 U.S.C. § 112.” Zenon Envtl., Inc. v. U.S. Filter Corp., 506 F.3d 1370, 1378 (Fed. Cir. 2007) (quoting Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571 (Fed. Cir. 1997)); see also In re Hogan, 559 F.2d 595, 609 (CCPA 1977). To comply with the “written description” requirement of 35 U.S.C. § 112, first paragraph, an applicant must “convey with reasonable clarity to those skilled in the art that, as of the filing date sought, he or she was in possession of the invention. The invention is, for purposes of the ‘written description’ inquiry, whatever is now claimed.” Vas-Cath, Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991) (emphasis omitted). The invention claimed does not have to be described in ipsis verbis to satisfy the written description requirement. Union Oil Co. v. Atlantic Richfield Co., 208 F.3d 989, 1000 (Fed. Cir. 2000). The question of written description support should not be confused, however, with the question of what would have been obvious to the artisan. Whether one skilled in the art would find the claimed invention obvious in view of the disclosure is not an issue in the “written description” inquiry. In re Barker, 559 F.2d 588, 593 (CCPA 1977). “A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood, 107 F.3d at 1572.” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundInstituted
“motivated to combine Beaumont and Hasan. Pet. 13–14. Petitioner argues that “Beaumont does not describe a specific interface for manually entering [policy and rules] preferences, Hasan discloses a GUI for exactly this type of policy specification.” Id. at 14 (citing Ex. 1003 ¶ 70). Petitioner asserts that Hasan discloses that its Java-based, “platform independent” GUI takes the form of a “familiar tree structure” and allows administrators to “configure device and service configuration data and policy information.” Id. (citing Ex. 1006, code (57), 7:7–26, 8:19–29, 18:9–20). Petitioner asserts that the combination of Beaumont and Hasan would have been straightforward, and a person of skill “would have been motivated to incorporate Hasan’s GUI so that administrators could conveniently configure preferences for Beaumont’s DNS servers through an intuitive interface.” Id. (citing, inter alia, Ex. 1003 ¶¶ 70–71; Ex. 1007 ¶ 23). Patent Owner does not present any arguments on the rationale to combine. See generally Prelim. Resp. We find that at this juncture Petitioner has presented sufficient rationale to combine Beaumont and Hasan.” slip op. at 16
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Instituted
“We agree with Patent Owner that its understanding of a policy as a rule is consistent with the disclosure in the ’517 patent that “a policy may be created by generating a decision tree representing the ATC rules.” See Ex. 1001, 9:1–3. We do not agree with Patent Owner, however, that Beaumont in combination with Hasan does not disclose the claimed policy features as claimed. As discussed above, Petitioner relies upon Beaumont in combination with Hasan with its teachings on the use of Java-based GUIs in the form of a tree structure that allows administrators to configure device and service configuration data, as well as policy information. See Ex. 1006, code (57), 7:7–26, 8:19–29. For the policy teachings, Petitioner relies upon Beaumont’s “content provider DNS server that directs requests (traffic) according to a preference table (policy).” Pet. 15–16 (citing Fig. 1, ¶¶ 6, 17, 23). Petitioner also asserts that the Beaumont-Hasan GUI would enable an administrator to set policies for a selected content delivery server to allow setting server preferences and rules. Id. at 17–18 (citing, inter alia, Ex. 1007 ¶¶ 76–77). In support, Dr. Lin testifies that: The Beaumont-Hasan GUI would enable an administrator to select a content delivery server (e.g., in Japan) and set policies for that server. Hasan, 8:30–36, 10:25–34, 10:53–67; Beaumont, [0031]. For example, given the description in Hasan, selecting a server would bring up a menu enabling an administrator to assign the preferences shown in Fig. 3 of Beaumont. Hasan, 10:25–34; Beaumont, Figs. 2, 3, [0029]–[0031]. A POSITA would thus have recognized the combined GUI to “support[] the setting of said at least one policy using a decision tree representing rules” because it is presented in a “familiar tree structure” and would allow users to set server preferences and rules. Ex. 1003 ¶ 77 (emphasis added). Beaumont provides support for Dr. Lin’s testimony. Beaumont discloses that “rules such as selecting one [a server] based on user preferences can be used . . . [f]or example, a preference number can be assigned to each content delivery server and a destination domain.” Ex. 1007 ¶ 31. Beaumont further states that “FIG. 3 shows an illustrative example of incorporating preference numbers in a column.” Id. Thus, contrary to Patent Owner’s arguments, Beaumont discloses that rules or policies, represented by the preference number, are represented in the table shown in Figure 3 of Beaumont. Dr. Lin also testifies that in the Beaumont-Hasan combination “the GUI supports the setting of” policy is taught. Ex. 1003 ¶ 77. Hasan provides support that service policies can be modified by the use of a GUI. See Ex. 1006, 8:30–36, 10:25–34, 10:53–67. Accordingly, in the combination of Beaumont and Hasan, wherein the preference database is replaced by the GUI decision tree, Petitioner has provided sufficient evidence at this juncture that the combination of Beaumont and Hasan teaches that the GUI obtains a policy, the preference number, for the direction of network traffic, where the GUI supports the setting of the policy using a decision tree representing rules.” slip op. at 19
Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 8,645,517 - Tesla, Inc. v. Iqar Inc.All claims unpatentablePTAB · Sep 18, 2025 · IPR2024-00630 · APJ Sean P O’Hanlon · IPR · Final written decision
Claims 1–16 are unpatentable as anticipated by Koebler and obvious over Koebler alone and in combination with other references.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“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.” In re Chu, 66 F.3d 292, 297 (Fed. Cir. 1995) (citing 35 U.S.C. § 120). Section 112 requires, inter alia, that the specification contain a written description of the claimed invention. 35 U.S.C. § 112(a). In determining whether the written description requirement is met, we consider “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.” Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). This analysis requires “an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Id. Thus, “the 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.” Id. For example, the analysis must consider “the existing knowledge in the particular field, the extent and content of the prior art, the maturity of the science or technology, [and] the predictability of the aspect at issue.” Id. (alteration in original) (quoting Capon v. Eshhar, 418 F.3d 1349, 1359 (Fed. Cir. 2005)). “While a prior application need not contain precisely the same words as are found in the asserted claims, the prior application must indicate to a person skilled in the art that the inventor was ‘in possession’ of the invention as later claimed.” PowerOasis, Inc. v. T-Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008) (citations omitted); see also Purdue Pharma LP v. Faulding Inc., 230 F.3d 1320, 1323 (Fed. Cir. 2000) (“In order to satisfy the written description requirement, the disclosure as originally filed does not have to provide in haec verba support for the claimed subject matter at issue.”). However, “it is the specification itself that must demonstrate possession. And while the description requirement does not demand any particular form of disclosure . . . , a description that merely renders the invention obvious does not satisfy the requirement.” Ariad, 598 F.3d at 1352 (citations omitted); see also Lockwood v. Am. Airlines, 107 F.3d 1565, 1572 (Fed. Cir. 1997) (“While 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. The question is not whether a claimed invention is an obvious variant of that which is disclosed in the specification. Rather, a prior application itself must describe an invention, and do so 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.”).” slip op. at 7
- Skill levelSkill level board ownDecided for petitioner
“The level of ordinary skill in the art is “a prism or lens” through which we view the prior art and the claimed invention. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). The person of ordinary skill in the art is a hypothetical person presumed to have known the relevant art at the time of the invention. In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995). In determining the level of ordinary skill in the art, we may consider certain factors, including: “(1) the educational level of the inventor; (2) type of problems encountered in the art; (3) prior art solutions to those problems; (4) rapidity with which innovations are made; (5) sophistication of the technology; and (6) educational level of active workers in the field.” Best Med. Int’l, Inc. v. Elekta Inc., 46 F.4th 1346, 1353 (Fed. Cir. 2022) (quoting Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007)). “The patent’s purpose can also be informative.” Id.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner
“Initially, we note that, although Petitioner presents a definition for “traction” in its Reply (see Pet. Reply 10), Dr. Morellas agreed with Patent Owner’s proposed interpretation during his deposition: Q. What would a person having ordinary skill in the art understand the word “traction” to mean? A. It would mean the grip that the -- that the tire has with the road. Q. So when the tire is gripping the road, the vehicle will have traction; correct? A. Correct. Q. But if the wheels are spinning freely and not gripping the road, the vehicle has no traction; correct? A.· Correct. Ex. 2031, 36:8–17. Accordingly, we adopt Patent Owner’s interpretation of “traction” to be a measure “of the friction between the vehicle’s drive wheels and the road surface” such that “a vehicle’s wheels have ‘traction’ when wheel rotation acts to propel the vehicle along the roadway” and “[t]he vehicle’s wheels lose ‘traction’ when they spin freely relative to the road and thus are no longer acting to propel the vehicle along the roadway.” See PO Resp. 27; see also Tr. 18:4–5 (Petitioner’s counsel stating that “the ultimate disposition doesn’t matter which definition [of ‘traction’ the Board] adopt[s]”).” slip op. at 24
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“2. Anticipation “Under 35 U.S.C. § 102 a claim is anticipated ‘if each and every limitation is found either expressly or inherently in a single prior art reference.’” King Pharm., Inc. v. Eon Labs, Inc., 616 F.3d 1267, 1274 (Fed. Cir. 2010) (quoting Celeritas Techs. Ltd. v. Rockwell Int’l Corp., 150 F.3d 1354, 1360 (Fed. Cir. 1998)). “Anticipation requires the presence in a single prior art disclosure of all elements of a claimed invention arranged as in the claim.” Therasense, Inc. v. Becton, Dickinson & Co., 593 F.3d 1325, 1332 (Fed. Cir. 2010) (quoting Connell v. Sears, Roebuck & Co., 722 F.2d 1542, 1548 (Fed. Cir. 1983)). A reference inherently discloses an element of a claim “if that missing characteristic is necessarily present, or inherent, in the single anticipating reference.” Schering Corp. v. Geneva Pharm., 339 F.3d 1373, 1377 (Fed. Cir. 2003) (citing Cont’l Can Co. USA, Inc. v. Monsanto Co., 948 F.2d 1264, 1268 (Fed. Cir. 1991)). “Inherency, however, may not be established by probabilities or possibilities. The mere fact that a certain thing may result from a given set of circumstances is not sufficient.” Therasense, 593 F.3d at 1332 (quoting Cont’l Can, 948 F.2d at 1269).” slip op. at 28
Patent outcomesUS 10,850,616 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 10,850,616 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentablePTAB · Aug 4, 2025 · IPR2024-00509 · APJ Michael J Strauss · IPR · Final written decision
Claims 1–4 and 6–19 are unpatentable as obvious over Throughtek-2012 and the Lorex Video; claims 1–3, 6, 10, 12–14, 17, and 18 are also unpatentable under two other grounds.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Dr. Bims, Petitioner proposes that a person of ordinary skill in the art at the time of the ’842 patent would have been a person having a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies. Pet. 11 (citing Ex. 1001 ¶¶ 15–16). Patent Owner does not provide any proposed qualifications for a person of ordinary skill in the art. In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citation omitted). The level of ordinary skill in the art is also reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt the assessment offered by Petitioner as it is consistent with the ’842 patent and the asserted prior art.” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“Petitioner asserts “no claim elements need a formal construction for purposes of resolving the controversy in this proceeding.” Pet. 11 (citing Ex. 1001 ¶ 55; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011); Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. §42.100). Patent Owner presents no proposed claim constructions. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe 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 8
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner
“In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20
Patent outcomesUS RE47,842 unpatentableClaim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham - Maplebear Inc. D/B/A Instacart v. Consumeron, LLCAll claims unpatentablePTAB · Nov 20, 2024 · IPR2023-00865 · APJ Carl M Defranco · IPR · Final written decision
Claims 1–19 are unpatentable under § 103 over Carr and Lauka, with additional references for the dependent-claim grounds, because the challenged claims lack priority support in the ’848 application.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Instacart submits that a person of ordinary skill in the art (“POSITA”) would have had “a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of electronic commerce” and that “[l]ack of work experience can be remedied by additional education, and vice versa.” Pet. 27 (citing Ex. 1003 ¶¶ 22–25). Consumeron responds that one skilled in the art would have been “someone with a background in electrical engineering, computer science, or the like” and that “industry experience can make up for a lack of technical training, and more education can make up for a lack of industry experience.” PO Resp. 7 (citing Ex. 2016 ¶¶ 19–23). But, as Consumeron’s expert acknowledges, Consumeron’s proposed definition “is not materially different” from Instacart’s. See Ex. 2016 ¶ 22. Accordingly, while we adopt the level of skill in the art as defined by Instacart our findings and analysis would be the same under Consumeron’s proposal.” slip op. at 7
- Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner
“8 Consumeron argues Dr. Houh’s testimony should be given little weight because he “admitted he did not evaluate what the ’848 Application reasonably conveys to a skilled artisan.” Resp. 26 (citing Ex. 2011, 74:8– 76:6, 83:4–84:1, 92:22–95:5). We disagree. Dr. Houh’s testimony indicates that he properly considered what the ’848 application reasonably conveys to a POSITA. See Ex. 1003 ¶¶ 52, 56, 58, 61, 65. The portions of his cross-examination testimony cited by Consumeron do not suggest otherwise. For the reasons explained below, we credit Dr. Houh’s testimony over the competing interpretations offered by Consumeron and Dr. Mitzenmacher. 9 The dissent criticizes the majority’s analysis as “overly narrow” and too focused on the preferred embodiment. See Dissent 7–8. We disagree. Our analysis considers the entirety of the ’848 application, including all of the passages cited by Consumeron and the dissent.” slip op. at 13
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot entitled to earlier dateDecided for petitioner
“But it does not follow that an agent encountering a stock-out would necessarily respond according to the specific steps recited in claims 1 and 14.10 For example, instead of sending information about a replacement product, the agent could travel to another location to look for the same product, or notify the customer that the desired product could not be found and terminate the transaction. Because the ’848 application only contemplates scenarios where a product can be located, it does not describe the agent’s response in the event the identified product cannot be located or is unavailable, much less reasonably convey possession of a method comprising the specific, responsive steps in claims 1 and 14.11” slip op. at 17
- Prior constructionPrior construction adoptedTerm construed petitioner constructionDecided for petitioner
“construed the terms “acquisition request” and “acquiring” in our final written decision in the related 1357 IPR to encompass “not only a request for a delivery agent to shop for and purchase goods, but also a request for the agent to pick up or obtain pre-paid goods.” See 1357 IPR, Paper 35 at 11. It is undisputed that the ’465 patent at issue here and the ’835 patent at issue in the 1357 IPR are related and share essentially identical specifications, figures, and claim terms. See Pet. Reply 16; PO Resp. 38 n.6. Thus, for the same reasons as in our final written decision in the related 1357 IPR, we likewise determine here that Instacart’s construction of “acquisition request” is the correct one. See SightSound Techs., LLC v. Apple Inc., 809 F.3d 1307, 1316 (Fed. Cir. 2015) (“Where multiple patents ‘derive from the same parent application and share many common terms, we must interpret the claims consistently across all asserted patents.’” (quoting NTP, Inc., v. Research in Motion, Ltd., 418 F.3d 1282, 1293 (Fed. Cir. 2005)). Consumeron provides no persuasive justification for us to depart from our prior reasoning in the related 1357 IPR.” slip op. at 23
Patent outcomesUS 11,238,465 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites PhillipsPatents in suitUS 11,238,465 - PTAB · Mar 19, 2024 · PGR2022-00052 · APJ Sheila F Mcshane · PGR · Final written decision
The Board cancelled claims 1–27 and denied substitute claims 28–51 because the original disclosure lacked written-description support for the claimed CSP limitations.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“In our Institution Decision, we adopted Petitioner’s proposed level of ordinary skill in the art, with the exclusion of “at least” because it introduces ambiguity. Inst. Dec. 8. Patent Owner “does not dispute the Board’s findings on the qualifications of a POSA [person of ordinary skill in the art] for purposes of this proceeding.” See RMTA 13. We determine that Petitioner’s definition, with the exclusion of “at least,” is consistent with the prior art of record and the skill reflected in the Specification of the ’034 patent and we use this level of skill here in the evaluation of the Revised Motion to Amend.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner
“Patent Owner argues that “claim construction is not necessary” and that “the meaning of the claims would be easily understood by a POSA.” RMTA 13. In the Petition, Petitioner proposed constructions for the terms “client device” and “first server,” and the original claims were rendered obvious under this construction. Pet. 23–27. Petitioner does not assert that the substitute claims of the Revised Motion to Amend are anticipated or rendered obvious by prior art or are patent ineligible. See generally RMTA Opp. Nor does Petitioner’s patentability challenge of the substitute claims contend that express construction is needed. See generally id. For purposes of this Decision, we determine that express claim construction is unnecessary. We need only construe terms that are necessary to resolve disputes. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017); Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”).” slip op. at 10
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateDenied
“written description requirement. In re Wright, 866 F.2d 422, 425 (Fed. Cir. 1989); All Dental Prodx LLC v. Advantage Dental Prods., 309 F.3d 774, 779 (Fed. Cir. 2002). The issue here, however, is whether the disclosure of the ’034 patent would have reasonably conveyed to a person of ordinary skill that the inventors had possession of the CSP Limitations. Ariad, 598” slip op. at 14
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend granted in partGranted in part
“to cancelling claims 1–27; and deny-in-part the Motion to Amend as to proposed substitute claims 28–51. In summary: Motion to Amend Outcome Claim(s) Original Claims Cancelled by Amendment 1–27 Substitute Claims Proposed in the Amendment 28–51 Substitute Claims: Motion to Amend Granted Substitute Claims: Motion to Amend Denied” slip op. at 20
Claim construction§ 112 disclosurePatents in suitUS 11,272,034 - PTAB · Nov 21, 2023 · IPR2023-00865 · APJ Carl M Defranco · IPR · Institution
The Board instituted IPR of claims 1–19, finding a reasonable likelihood that claims 1 and 14 are obvious over Carr and Lauka.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“III. CONCLUSION For the above reasons, we determine that the information presented in the Petition demonstrates a reasonable likelihood that at least claims 1 and 14 of the ’465 patent are unpatentable as obvious over Carr and Lauka. And because Instacart demonstrates that at least one claim of the ’465 patent meets the threshold for institution, we institute an inter partes review of all claims as challenged in the Petition. See 37 C.F.R. § 42.108(a),(c); SAS, 138 S. Ct. at 1359–60. IV. ORDER Accordingly, it is: ORDERED that, pursuant to 35 U.S.C. § 314(a), an inter partes review of claims 1–19 of the ’465 patent is instituted; and” slip op. at 16
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Consumeron responds that one skilled in the art would have been “someone with a background in electrical engineering, computer science, or the like” and that “industry experience can make up for a lack of technical training, and more education can make up for a lack of industry experience.” Prelim. Resp. 29. Consumeron’s definition appears to overlap significantly with Instacart’s definition. Accordingly, for purposes of institution, we adopt the level of skill in the art as articulated by Instacart.” slip op. at 5
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“product ordered by the customer is available and does not contemplate a scenario where the product is unavailable or otherwise describe the action to be taken if the product is unavailable. See Pet. 17–22. We agree, at least based on the preliminary record. In particular, with reference to Figures 2 and 3, the ’848 parent application describes a method where (1) a customer chooses “a store where a desired product is being sold” (step 105), (2) the customer selects a delivery agent and sends an “acquisition request” to the delivery agent (steps 108, 109, 110), and (3) “the selected delivery agent travels to the store location . . . and finds the desired product to be acquired” (step 113). Ex. 1011 ¶¶ 17, 20, 23 (emphasis added). “The delivery agent then communicates to the customer that the product has been identified, and the customer has the option of inspecting the product in real-time” (step 117). Id. ¶ 23 (emphasis added). “Next, the customer either approves or rejects acquisition of the inspected product” (steps 119, 120, 122). Id. ¶ 24 (emphasis added). That description in the ’848 parent application clearly presumes that the product ordered by the customer has been located and is available for inspection, which is at odds with the additional requirements of claims 1 and 14 of “failing to locate an identified product” and “determining that the identified product is not available.” Ex. 1001, 11:20 (claim 1), 12:30 (claim 14) (emphases added). To the extent Consumeron argues otherwise, we are not persuaded at this preliminary stage. According to Consumeron, the customer’s rejection of the product means that “the agent fails to locate a product that is satisfactory.” See Prelim Resp. 11. But nowhere do we discern that the ’848 parent application hinges the identity and availability of a product on whether it is satisfactory to the customer. That a product might not meet a customer’s satisfaction does not negate the description in the ’848 parent application that the agent locates and identifies the product in the first instance before giving the customer the option to inspect and reject the product. Indeed, because the customer placed the online order with a store advertising the product, the presumption is that the advertised product is available and satisfactory to the customer.8 And, while conceivably the purchase of a product cannot be fulfilled in the event the product is unavailable, it would seem to be improper hindsight to derive written description support by “[w]orking backward from a knowledge of the claims.” Novozymes A/S v. DuPont Nutrition Biosciences APS, 723 F.3d 1336, 1349 (Fed. Cir. 2013). “Entitlement to a filing date does not extend to subject matter which is not disclosed, but would be obvious over what is expressly disclosed. It extends only to that which is disclosed.” Lockwood v. American Airlines, Inc., 107 F.3d 1565, 1571–72 (Fed. Cir. 1997). Thus, based on the preliminary record, the ’848 parent application does not provide sufficient written description for the terms noted above. As such, we find that Instacart demonstrates a reasonable likelihood it will prevail in showing that the asserted references are prior art to the challenged claims.” slip op. at 6
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundInstituted
“and Lauka. See Pet. 30–44, 47–49. We begin with Instacart’s challenge of method claim 1. Instacart provides a detailed mapping of how Carr satisfies all the recited limitations of claim 1, except limitation [1.0.3], for which Instacart points to Lauka. See id. at 35–44. In particular, Instacart cites the following evidence in support of its contentions that Carr and Lauka, when combined, teach or suggest each of the recited limitations of claim 1: Limitation 1.0.1—“A method for remote acquisition and delivery of goods through one or more agents of a service provider” (Pet. 35 (citing Ex. 1005 ¶¶ 36, 39, 43, 45, 92, Figs. 1, 3, 6;; Ex. 1001 ¶¶ 97–100)); Limitation 1.0.2—“each agent having a mobile agent system in communication with at least one remote server,” (Pet. 35–37 (citing Ex. 1005 ¶¶ 2, 6, 40–43, 53, Fig. 1 (annotated); Ex. 1003 ¶¶ 101–104)); Limitation 1.0.3—“with each mobile agent system including: a digital image capture device and a communication device, said method comprising:” (Pet. 37–38 (citing Ex. 1005 ¶¶ 74, 88, 94, 122; Ex. 1006, 3:19–28, 3:49–57, 4:10–21; Ex. 1003 ¶¶ 105– 109)); Limitation 1.1—“receiving, through the at least one remote server, a first acquisition request from a customer for a first set of one or more goods;” (Pet. 38 (citing Ex. 1005 ¶¶ 9, 60, 73, Fig. 1; Ex. 1003 ¶¶ 110–112)); Limitation 1.2—“contacting, through the communications device, the one or more agents;” (Pet. 38 (citing Ex. 1005 ¶¶ 57, 74; Ex. 1003 ¶¶ 113–115)); Limitation 1.3—“upon failing to locate an identified product of the set of one or more goods, electronically transmitting information on a replacement product for the identified product of the set of one or more goods to the customer using the digital image capture device of the agent, including:” (Pet. 38–40 (citing Ex. 1005 ¶¶ 90, 95, 96, 105, 107, ; Ex. 1003 ¶¶ 116– 119)); Limitation 1.4—“obtaining a bar or QR code of the replacement product;” (Pet. 40 (citing Ex. 1005 ¶¶ 95, 107; Ex. 1003 ¶¶ 120– 122)); Limitation 1.5—“determining the information from the bar or QR code, wherein the information includes at least one image of the replacement product; and” (Pet. 40–42 (citing Ex. 1005 ¶¶ 95–96, 116; Ex. 1003 ¶¶ 123–127)); Limitation 1.6—“sending the information for the customer to approve the purchase of the replacement product based on the information determined from the bar or QR code; and” (Pet. 42– 43 (citing Ex. 1005 ¶¶ 51, 96–99, Fig. 12; Ex. 1003 ¶¶ 128– 130)); and Limitation 1.7—“upon receiving approval of the purchase from the customer, acquiring the replacement product, via the agent.” (Pet. 43–44 (citing Ex. 1005 ¶¶ 99, 101; Ex. 1003 ¶¶ 131–132)); Instacart also provides a reason why one skilled in the art would have combined the teachings of Carr and Lauka with a reasonable expectation of success. See Pet. 31–34 (citing Ex. 1003 ¶¶ 86–96); see also id. at 37 (“In view of the teachings of Lauka, a POSITA would have recognized that it was obvious to implement the UPC scanner functionality of Carr’s handheld device using an ‘imaging device’ such as that taught by Lauka, which specifies that the ‘imaging device 206 can comprise a video or still camera’ and ‘can be used to capture images.’ Ex.1006, 3:49-57; Ex.1003, ¶¶105- 107.”).” slip op. at 11
Claim construction§ 103 obviousness§ 112 disclosurePatents in suitUS 11,238,465 - Facebook, Inc. v. Palo Alto Research Center LLCAll claims unpatentablePTAB · Mar 22, 2023 · IPR2021-01461 · APJ Christopher L Ogden · IPR · Final written decision
Claims 1–5, 7–11, 13–17, 19, and 20 are unpatentable under § 103; PARC’s contingent motion to amend is denied because the pending substitute claims lack written-description support and are obvious.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Relying on Mr. Schmandt’s testimony, Facebook argues that a person of ordinary skill in the art “would have possessed at least a bachelor’s degree in electrical engineering or computer science, and two years of work experience in the field of context-based computer systems, such as the collection, processing and use of context data in computer systems capable of adapting their operation based on context.” Pet. 6 (citing Ex. 1002 ¶¶ 15– 18). Facebook also contends that a person might qualify as an ordinarily skilled artisan “with more formal education and less technical experience, or vice versa.” Id. For this proceeding, PARC does not dispute this proposed level of ordinary skill. PO Resp. 16–17. Because Facebook’s uncontroverted articulation of the level of ordinary skill in the art is supported by testimonial evidence and appears consistent with the types of problems and solutions in the ’439 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:4–33 (“Background” section of the ’439 patent, describing the field and related art as relating to the use of using contextual data in computer systems).” slip op. at 10
- Strike new argumentNew argument consideredDecided for petitioner
“construction of the term “facts and assertions” or the identification of facts and assertions within Cheng. See Paper 23, 1–2. Having reviewed the arguments, we do not consider them untimely. As we discuss in more detail below, Facebook relied on the ordinary and customary meaning of the term “facts and assertions” in its Petition, and then when PARC raised an alternative construction of the term in its Response, Facebook responded to those arguments. See infra Sections IV.B.2, IV.C.4(a). Facebook’s Reply only responded to arguments raised in PARC’s Response and was not untimely. See 37 C.F.R. § 42.23(b) (permitting a petitioner to respond to arguments in a patent owner response); Anacor Pharm., Inc. v. Iancu, 889 F.3d 1372, 1380–81 (Fed. Cir. 2018) (“[T]he 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, or if it is used ‘to document the knowledge that skilled artisans would bring to bear in reading the prior art identified as producing obviousness.’” (quoting Genzyme Therapeutic Prod. Ltd. P’ship v. Biomarin Pharm. Inc., 825 F.3d 1360, 1369 (Fed. Cir. 2016))). Moreover, PARC had a meaningful opportunity to address the arguments in its Sur-reply and in oral argument. See PO Sur-reply 7–12; Tr. 22–34. Thus, we do not find Facebook’s contested arguments untimely and we have considered them in our decision.7” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“We agree with Facebook. As we discuss below, Cheng teaches a graph-based model that stores data in memory on a per-user basis. See infra Section IV.C.4(a); Ex. 1003, Fig. 7. Also, as PARC acknowledges, Facebook’s expert Mr. Schmandt stated in deposition that he assumed, for his analysis, that the term “context graph” requires a “graph-based model.” PO Resp. 22 (citing Ex. 2019, 36:16–37:8); see also PO Sur-reply 4. Thus, because Facebook’s analysis of Cheng is consistent with the assumption that “context graph” has the meaning PARC proposes in this proceeding, we do not need to construe the term “context graph” to reach our decision. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe 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 13
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“We agree with the parties that a person of ordinary skill in the art would have understood the term “fact” to include an indication of truth, whereas an assertion need not include such an indication. However, we disagree with PARC that a person of ordinary skill would have considered the term “assertion” to exclude facts. Indeed, in its ordinary and customary meaning, a fact stored in a context graph would be a type of assertion. We appreciate PARC’s argument that when two different terms appear in a claim, they presumably refer to different things. See PO Resp. 27 (citing CAE Screenplates, 224 F.3d at 1317). And we agree that the two terms have different meanings in claim 1 based on the plain meaning of each term. However, the specification refers to “stor[ing] facts and assertions about a user’s behavior and interests,” which simply appears to identify a single category of data for storage, i.e., “facts and assertions,” without specifying a clear difference between “facts” and “assertions.” See Ex. 1001, 3:21–22. In any event, we find no evidence of record suggesting that either (1) the (citing Pet. Reply 8–9). Because Facebook appears to have been relying on what it regarded as the plain meaning of the terms without proposing an explicit construction, we do not interpret Facebook’s argument in the Petition (Pet. 20–21) to imply that there is no distinction between a fact and an assertion, and do not find Mr. Schmandt’s later testimony (see, e.g., Ex. 2019, 41:3–11) inconsistent with arguments made in the Petition. ordinary and customary meaning of the term “assertion” excludes facts, or (2) that the ’439 patent uses these terms in a way that departs from their ordinary and customary meaning. That claim 1 requires the presence of both “facts” and “assertions” does not render the two terms superfluous, as this would exclude prior art in which a context graph includes only assertions but not facts. On the other hand, a disclosure of a collection of facts would meet the term “facts and assertions” because a person of ordinary skill in the art would have regarded any subset of the facts to also be assertions.” slip op. at 15
Patent outcomesUS 9,208,439 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · GrahamPatents in suitUS 9,208,439
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.