- Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentablePTAB · Oct 13, 2026 · IPR2025-00710 · APJ Scott A Daniels · IPR · Final written decision
Claims 1–7, 9, 13, and 16–20 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 8 was not shown unpatentable under either ground.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’294 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner indicates that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction. Thus, no express construction is required.” Pet. 13 (citing Ex. 1003 ¶ 86). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 17
- Expert testimonyPetitioner expert discountedDecided for patent owner
“and reliance on Figure 19 do not in any way explain how updating game costs by meter 502 with a new Cost_Table is relevant to a credit multiplier or even a multiplier being varied over time. Ex. 1003 ¶ 155. Considering this evidence, we determine that Petitioner and Mr. Crevelt’s reliance mainly on snippets from Schneier’s “Updating Cost Information protocol” embodiment does not sufficiently explain why or how a person of ordinary skill in the art would have understood updating game cost to encompass varying a multiplier of credits over time. We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004:158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to persuasive evidence in Schneier as to how or why a person of ordinary skill in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 8.” slip op. at 20
Patent outcomesUS 10,825,294 mixedClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,825,294 - Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentablePTAB · Oct 13, 2026 · IPR2025-00709 · APJ Scott A Daniels · IPR · Final written decision
Claims 1, 2, 4, 6, 8, 10, 14–18, 21–23, 25, 27, and 29 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 9 was not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner states it “does not dispute Petitioners’ proposed level of skill, and under any level of skill a POSITA would not understand the asserted Grounds to raise any unpatentability issue.” PO Resp. 4. Patent Owner states further that “this [Patent Owner Response] and supporting declarations apply Petitioner’s proposed level of skill.” Id. On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’635 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 7
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner indicated in the Petition that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction.[] Thus, no express construction is required.” Pet. 12–13 (citing Ex. 1003 ¶ 85). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8
- Expert testimonyPetitioner expert discountedDecided for patent owner
“We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004, 158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. Id. at 161:2–6. These explanations are unpersuasive because the testimony relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 9.” slip op. at 21
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“Discount Credit Pricing Structure The $0.20 discount described by Schneier for purchasing 20 credits, rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not address the idea of a time component, i.e., “over time,” as required by claim 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 18
Patent outcomesUS 10,650,635 mixedClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,650,635 - PTAB · Oct 6, 2026 · IPR2025-00530 · APJ Scott C Moore · IPR · Final written decision
Original claims 1–9 were canceled; the non-contingent motion to add substitute claims 10–18 was denied for lack of written-description support, and claim 18 was also indefinite.
RulingsFinal written decision- 112 supportMotion to amend, deniedDenied
“that either the ’303 application or the ’838 provisional contain adequate written description support for the disputed feature of limitation [10.d]. Though the disclosures cited by Patent Owner indicate that a secondary identifier can be used to aid in verification of a UAV, these disclosures also make clear that both first and second identifiers are transmitted by and received from the UAV. See, e.g., Ex. 2002, 4:15–17, 30:24–31:6; Ex. 2003 ¶¶ 14, 66. Patent Owner’s reliance on disclosure characterized as transmitting an identifier from a remote computing system “through the UAV” (Reply 2) is not persuasive. The cited disclosures from the ’303 application and ’838 provisional generally disclose that the identifiers transmitted by a UAV can be “generated remotely,” such as by a “remote computing system.” Ex. 2002, 14:23–15:2; Ex. 2003 ¶ 45. But Patent Owner has not identified disclosure indicating that a remote computing system may transmit an identifier to the identification receiver. In the ’303 application and ’838 provisional, only the UAV (which is part of the discrimination system, and thus not “remote”) actually transmits identifiers to the identification receiver. Patent Owner is correct in its assertion that an “aerial system identifier can be generated on-board the aerial system” or “generated remotely . . . at a remote computing system.” Mot. 7 (citing Ex. 2002, 14:23–15:2; Ex. 2003 ¶ 45). But even if a UAV’s identifier was at some time in the past generated by a remote computing system, the subsequent transmission of that identifier from the UAV to the identification receiver would not satisfy the plain language of limitation [10.d]. The claim language “receive … a second identifier from a computing system that is remote to the discrimination system” requires the receipt of a transmission of the second identifier from a remote computing system. This claim language limits the source of the received transmission (i.e., where the particular transmission is “receive[d] … from”). Thus, the relevant issue is from where was the recited second identifier received. The relevant is not where the second identifier was originally generated.” slip op. at 12
- Disclosure Requirements (§112) › Definiteness (Nautilus)DefiniteIndefiniteMixed
“We determine that the disputed language in limitation [10.d] is not indefinite. There is no recitation in proposed substitute claim 10 that the second identifier is transmitted solely from the identifier transmission system. Thus, the alleged irreconcilable contradiction cited by Petitioner is not recited in the claims. Petitioner’s position appears to rest on the fact that the ’303 application and ’838 provisional do not disclose receiving the second identifier from a remote computing system. See Sur-reply 6 (“To manufacture written description support, [Patent Owner] argues the claim encompasses identifiers routed ‘through the UAV.’”). Though we agree that limitation [10.d] lacks adequate written description support, this defect does not render the claim indefinite because the scope of limitation [10.d] is otherwise reasonably certain based on its plain language. See supra § III.C.4.” slip op. at 18
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference not prior artPriority date, deniedDecided for patent owner
“In contrast, the ’393 provisional never discloses that the described drone defense system may use the identity of a detected drone to develop a particular countermeasure. The disclosed RTSS certainly uses identity information to determine whether a drone is a threat. And if a threat is identified, the RTSS immediately starts “a series of processes … to determine what rule of engagement will be applied on the intruding drone.” Ex. 1006 ¶ 10. The ’393 provisional discloses that the system may select a particular countermeasure based on (i) the particular zone within a protected area within which a drone is located, (ii) “the behavior of the hostile drone,” or (iii) “other instructions.” Id. ¶¶ 9, 10. But the ’393 provisional never discloses that these “other instructions” may include the identity of the drone. The system disclosed in the ’393 provisional uses the identity of a drone to determine whether to activate the countermeasure system. See id. ¶¶ 16–18. But there is no disclosure in the ’393 provisional that the countermeasure system, once activated, uses the identity of the drone to develop the particular countermeasure to be employed. See generally Ex. 1006. Thus, though the Whitmarsh reference itself contains ample written description support for limitation [19e], the earlier-filed ’393 provisional does not. On this record, and having reviewed the ’393 provisional in its entirety, we determine that the ’393 provisional does not “reasonably convey[] to those skilled in the art that the inventor had possession of” the subject matter of limitation [19e] of Whitmarsh’s claim 19 “as of the filing date” of the ’393 provisional. See Ariad, 598 F.3d at 1351.” slip op. at 27
§ 102 anticipation§ 112 disclosurecites NautilusPatents in suitUS 10,249,199 - 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 - Shenzhen Tuozhu Technology Co., Ltd. v. Stratasys, Inc.No claims unpatentablePTAB · Jun 9, 2026 · IPR2025-00321 · APJ Christopher M Kaiser · IPR · Final written decision
The Board held claims 1, 2, 5–7, 9, 16, and 17 not unpatentable because the asserted combinations did not establish the required purge-tower teachings or prior-art status.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends that one of ordinary skill in the art “would have had (1) at least a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a related field, and (2) at least two years of research or industry experience in 3D printing or materials used for 3D printing.” Pet. 5 (citing Ex. 1003 ¶¶ 14–16). Petitioner also argues that “[a]dditional experience could substitute for a formal degree or formal training (and vice versa).” Id. Patent Owner proposes a slightly different level of skill, arguing that a person of ordinary skill in the art “would have had a bachelor’s degree in Mechanical Engineering, Computer Engineering, Chemical Engineering, Materials Science, or a comparable field and at least two years of experience related to 3D printing, with additional experience potentially being a substitute for a formal degree or training (and vice versa).” Prelim. Resp. 24. Neither party explains why the outcome of this case would be affected by the adoption of any of the proffered definitions of a person of ordinary skill in the art. We adopt Petitioner’s assessment of the level of ordinary skill in the art, as it appears consistent with the ’324 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“According to the ’713 patent, “[p]urge tower 24 itself may be . . . recycled or otherwise discarded as desired.” Ex. 1001, 8:27–28. This description provides some support for Patent Owner’s view, because a purge tower too intimately integrated with the part would be difficult or impossible to recycle or discard. This is further supported by the ’713 patent’s statement that “purge tower 24 may be printed at any suitable location on build substrate 44 (i.e., at any location in the x-y build plane not occupied by 3D part 20 or support structure 22).” Id. at 8:30–34. It also is supported by Dr. Hickner’s testimony that the ’713 patent “clearly shows . . . the 24 purge tower separated from the part” and that “the purge tower is a separate physical object.” Ex. 2016, 28:8–10, 64:1–9. On the other hand, there is evidence supporting Petitioner’s view that, as long as the purge tower is generally separate from the part and the support structure, it may still make contact with those portions of the print. As noted above, “purge tower 24 may be printed at any suitable location on build substrate 44 (i.e., at any location in the x-y build plane not occupied by 3D part 20 or support structure 22).” Ex. 1001, 8:30–34. This language does not exclude locations adjacent to or in contact with the part or the support structure. Thus, determine that a “purge tower,” as that term is used in the context of the ’713 patent, may not be an integrated portion of a printed part or support structure but need not be free of all contact with the printed part or support structure.” slip op. at 9
- BurdenNot shown unpatentable
“There is evidence of record to support both Petitioner’s view and Patent Owner’s view. On the record developed at trial, however, we cannot say that the preponderance of the evidence favors Petitioner, who bears the burden of proof. See 35 U.S.C. § 316(e). Accordingly, Petitioner has not shown by a preponderance of the evidence that KISSlicer teaches printing a layer of a purge tower each time the printer switches one extruder to the operating mode. Because proving the obviousness of claims 1 and 16 requires such a showing, Petitioner has not shown by a preponderance of the evidence that claims 1 and 16 would have been obvious over the combination of Priedeman and KISSlicer. 5. Analysis of Remaining Claims Claims 2, 6, 7, 9, and 17 all depend, directly or indirectly, from claim 1 or claim 16. Accordingly, they all include the limitations of either claim 1 or claim 16. Because, as discussed above, Petitioner has not shown that the combination of Priedeman and KISSlicer teaches or suggests all the limitations of claims 1 and 16, Petitioner also has not proven by a preponderance of the evidence that claims 2, 6, 7, 9, and 17 would have been obvious over that combination of references.” slip op. at 21
- Obviousness (§103) › Analogous artAnalogous artOther
“On the record developed at trial, we agree with Petitioner. According to several industry forum posts, people interested in three-dimensional printing located the website where KISSlicer was posted between February 2012 and April 2012. Ex. 1028, 1 (post discussing and directing others to KISSlicer on April 11, 2012); Ex. 1031, 1 (two posts discussing KISSlicer on March 16, 2012, and March 21, 2012); Ex. 1032, 1 (two posts discussing KISSlicer on February 11, 2012, and February 14, 2012). Thus, not only was it possible for people of ordinary skill in the art to locate KISSlicer; people of ordinary skill in the art actually did locate it. Accordingly, Petitioner has shown by a preponderance of the evidence that KISSlicer was publicly accessible.” slip op. at 19
Patent outcomesUS 9,421,713 not shown unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,421,713 - Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2022-00572 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under §103 because the prior-art combinations teach the limitations at issue under the Federal Circuit’s construction of “style.”
RulingsRemand decision- RemandDecided for petitioner
“We agree with Petitioner. Lemay Web discloses that the style settings of width, height, pause, and repeat for the pocket watch images can be changed by changing the values for width, height, pause, and repeat in the HTML file. Ex. 1004, 89–90. This results in changing the size, duration, and frequency of the display of the multiple pocket watch image objects without changing the image files or the Java applet. Id. That is, the 12 image objects of Lemay Web can be uniformly formatted by applying and altering the style settings of the HTML file, which is stored separately from the image objects and the Java applet. Id. at 88– 89. In our Final Written Decision, we wrote that “Lemay Web discloses that the image files that are displayed as the animation object are separate from the HTML.” Ex. 1004, 88–89.” Dec. 22. The Federal Circuit wrote that “how the Board evaluated what constitutes separateness in the prior art software is less than clear.” Opinion, 13 n.7. To be clear, the animation of Lemay Web comprises 12 different pocket watch image objects. Ex. 1004, 89. The HTML file that contains the style settings for the 12 different pocket watch image objects is stored separately from the 12 different pocket watch image objects. Id. at 88–91. The style of the 12 different pocket watch image objects can be altered by changing the values of the style settings in the separate HTML file, thus allowing the style to be uniformly applied to each of the associated 12 pocket watch image objects when the pocket watch image objects are created on the web page. Id.; see Ex. 1030 ¶¶ 28–29; Dec. 21–22. In conclusion for issue (B), we find that Lemay Web teaches applying the style located in the separate HTML file to the pocket watch image objects when creating the pocket watch image objects on the web page. Therefore, Lemay Web’s style is “defined separately from any single object” as claimed. Because Lemay Web’s style can be applied to one object and more than one object and Lemay Web’s style is defined separately from any single object, we find that the prior art combination teaches limitations 1(c) and 1(g) under the proper construction of “style.”” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached
“As directed by the Federal Circuit, we determine whether the prior art combination teaches limitations 1(c) and 1(g) under the proper construction of “style,” but otherwise do not revisit our analysis of claim 1. Remand Opinion 7, 13–14. The Federal Circuit construed “style” to mean “a collection of one or more settings that is defined separately from any single object but can be associated with one or more objects,” with the understanding that “associated with one or more” means capable of being associated with both one object and more than one object. Id. at 14.” slip op. at 4
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner
“Because the Specification discloses that data defines an object, we construe the plain meaning of the claimed “object,” read in light of the Specification of the ’168 patent, as encompassing data that defines the object. See Phillips v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 2005) (The “specification . . . is the single best guide to the meaning of a disputed term.”); Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1583 (Fed. Cir. 1996); (Excluding an embodiment in the specification from “the scope of the patent claim . . . is rarely, if ever, correct.”). Further, because the Specification discloses that data defines image objects, and that objects include images, we construe the plain meaning of the claimed “image object,” read in light of the Specification, as encompassing data that defines an image, such as one of the 12 different pocket watch images of Lemay Web.” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for petitioner
“What you see in the bottom right is an excerpt from the Lemay Web book . . . [y]ou can still use the Java applet just by putting this applet code into your HTML file. So this shows the animator class is going to be run within height or how big a window within the browser should be allocated in this applet. You can . . . tell the animator class how long to pause in between each image. So that’s a style that’s being applied to all of the multiple images that make up this animation. Ex. 2029, 746:23–747:7. Patent Owner then asked GoDaddy’s expert “for each unique animation you want to create with this animator class that’s shown here, you’re going to have to have a unique set of HTML code with the settings along with any of the images you’ll want to associate with the animator class, right?” Ex. 2030, 793:7–11. GoDaddy’s expert testified, with reference to Exhibit 2027, 80, that “Yeah. I’m not a hundred percent sure I understand your question, but yes, if you had six animations on a page, for example, you’d have six blocks of markup that looked like the markup at the bottom right of that slide, starting with applet.” Id. at 793:12–16. In addressing Patent Owner’s question about “each unique animation,” GoDaddy’s expert provided a hypothetical example of a web page having six animations, and explained that the six animations have six blocks of markup. Ex. 2030, 793:13–16. We find that this testimony means that if a web page has six unique animations, then for each unique animation, a corresponding HTML file contains the style settings for the image objects of that animation, such that the “six animations on a page . . . have six blocks of markup.” Id. We find that the subsequent testimony of GoDaddy’s expert cited by Patent Owner is consistent with the expert’s initial testimony that Lemay Web’s style is “applied to all of the multiple images that make up this animation.” Ex. 2029, 747:5–7. We also find that the subsequent testimony is consistent with and supported by the disclosure of Lemay Web, which teaches that an animation has a set of image files and is added to a Web page using the Animator applet. Ex. 1004, 88 (“[Y]ou’ll learn just enough about Java applets to set up animation on your Web page. . . . To create animation using Java and the Animator applet, you’ll need . . . [a] set of image files . . . that make up your animation.”); see id. at 88–91. That is, Lemay Web, consistent with the testimony of GoDaddy’s expert, discloses that the style settings for the animation of the pocket watch in the HTML file are uniformly applied to the 12 pocket watch image objects. Id. at 88–91.” slip op. at 17
Patent outcomesUS 7,594,168 unpatentableClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 7,594,168 - Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2022-00597 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under §103 over both listed prior art combinations; Lemay Web teaches the claimed style under the Federal Circuit’s construction.
RulingsRemand decision- RemandOther
“As directed by the Federal Circuit, we determine whether the prior art combination teaches limitations 1(c) and 1(g) under the proper construction of “style,” but otherwise do not revisit our analysis of claim 1. Remand Opinion 7, 13–14. The Federal Circuit construed “style” to mean “a collection of one or more settings that is defined separately from any single object but can be associated with one or more objects,” with the understanding that “associated with one or more” means capable of being associated with both one object and more than one object. Id. at 14.” slip op. at 4
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“We agree with Petitioner. As discussed above, the plain meaning of an “image object” read in light of the Specification encompasses data that defines an image, such as each of the 12 different pocket watch images of Lemay Web. Ex. 1004, 89–90. Therefore, the HTML file of Lemay Web, which specifies attributes including width, height, pause value, and repeat value of the pocket watch image objects, is “capable of being applied to more than one” image object, such as each of the 12 different pocket watch image objects described by Lemay Web. Id.” slip op. at 11
- Strike new argumentNew argument consideredDecided for petitioner
“We agree with Petitioner. The Board and Petitioner understood the meaning of “or” in the phrase “one or more objects” in Patent Owner’s proposed construction of style as meaning that “a style . . . can be associated with just one object.” Dec. 22; see Reply 4–5. The Federal Circuit “ultimately conclude[d] that Express Mobile’s proposed construction, with ‘or’ properly interpreted,” means “that the claimed ‘style’ must be capable of being applied to both one and more than one ‘object,’” and “remand[ed] for further proceedings in view of the correct claim construction.” Remand Opinion 13. In doing so, the Federal Circuit stated that “[i]t may be that under the correct claim construction, the Board finds that Lemay Web teaches the claimed ‘style’; however, that is still an open fact question for the Board to decide in the first instance.” Id. at n.6. Given that the Federal Circuit has ordered the Board to determine whether the prior art teaches the claimed “style” under the proper construction, we find that Petitioner’s arguments on this issue are timely.” slip op. at 6
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“Contrary to Patent Owner’s contention, the Specification discloses, “Data that defines text button, image, paragraph, or other parent objects . . . can be stored in two-dimensional arrays (by web page and by object number).” Ex. 1001, 22:11–13 (emphasis added). The Specification further discloses that “objects . . . include colors, fonts, images, audio clips, video clips, text areas, URLs and thread objects.” Id. at 2:16–17 (emphasis added); see id. at 8:40. We highlight that the Specification’s use of “object” is consistent with a definition of “object” in the computing art at the time of the invention, which is “(2) A passive entity that contains or receives data; for example, bytes, blocks, clocks fields, files . . . .” George McDaniel, IBM Dictionary of Computing, McGraw-Hill, Inc. 1994, p. 471 (Ex. 3001). Because the Specification discloses that data defines an object, we construe the plain meaning of the claimed “object,” read in light of the Specification of the ’168 patent, as encompassing data that defines the object. See Phillips v. AWH Corp., 415 F.3d 1303, 1315 (Fed. Cir. 2005) (The “specification . . . is the single best guide to the meaning of a disputed term.”); Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1583 (Fed. Cir. 1996); (Excluding an embodiment in the specification from “the scope of the patent claim . . . is rarely, if ever, correct.”). Further, because the Specification discloses that data defines image objects, and that objects include images, we construe the plain meaning of the claimed “image object,” read in light of the Specification, as encompassing data that defines an image, such as one of the 12 different pocket watch images of Lemay Web.” slip op. at 8
Patent outcomesUS 7,594,168 unpatentableClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 7,594,168 - Cambridge Industries USA, Inc. v. Applied Optoelectronics, Inc.Rehearing deniedPTAB · Dec 19, 2025 · IPR2025-00434 · APJ Mitchell G Weatherly · IPR · Rehearing
The Board denied Petitioner’s rehearing request, leaving institution denied because Shen and Soldano did not establish a reasonable likelihood of anticipating claims 1–7.
RulingsRehearing decision- RehearingRehearing, deniedDenied
“When rehearing a decision on petition, the Board will review the decision for an abuse of discretion. See 37 C.F.R. § 42.71(c). An abuse of discretion may be determined if a decision is based on an erroneous interpretation of law, if a factual finding is not supported by substantial evidence, or if the decision represents an unreasonable judgment in weighing relevant factors. See Arnold P’ship v. Dudas, 362 F.3d 1338, 1340 (Fed. Cir. 2004). The party challenging the decision has the burden of showing the decision should be modified, and the request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed” in its papers. 37 C.F.R. § 42.71(d).” slip op. at 2
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“II. ANALYSIS In our Decision, we concluded that Petitioner had failed to carry its burden of demonstrating a reasonable likelihood of prevailing that either Shen or Soldano anticipated claims 1–7. Dec. 18, 26. Petitioner argues that we should institute review for three reasons. First, Petitioner argues that we abused our discretion by (a) “refusing” to interpret the scope of the claimed” slip op. at 2
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Owner’s interpretation of “carrier” as meaning “one or more components for supporting ROSA components such as an AWG.” Dec. 9 (quoting Pet. 11). For our analysis of Petitioner’s challenges, we referred to this interpretation of “carrier” as Petitioner’s second alternative construction. Id. We also noted that Petitioner appeared to dispute Patent Owner’s interpretation when it argued that “carrier” should mean “a ceramic or silicon substrate.” Id. (quoting Pet. 10). We referred to this interpretation of “carrier” as the first alternative construction. Id. Rather than resolve this apparent dispute about the meaning of “carrier,” we found that both of Petitioner’s anticipation challenges failed under both interpretations of “carrier.” Id. at 10–26. Because we found that Petitioner had failed to carry its burden regardless of which interpretation of “carrier” applied, we found it unnecessary to resolve the dispute over that interpretation. Id. at 9–10. For the reasons expressed in Parts II.B–C below, we maintain our conclusion that Petitioner has failed to demonstrate a reasonable likelihood of proving that either Shen or Soldano anticipates any claim under either interpretation of “carrier.” Accordingly, Petitioner fails to demonstrate an abuse of discretion in our alleged “refusal” to interpret “carrier.”” slip op. at 3
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“Reh’g Req. 14. We cannot weigh Petitioner’s arguments based on its assertions about “caselaw” because Petitioner cited no cases to support its arguments. See id. Nevertheless, we infer that Petitioner intends its statements of “caselaw” to refer to the requirements to make out a case for anticipation. If so, Petitioner demonstrably miscasts what appear to be the legal principles for proving anticipation. As stated in our Decision: “A claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal Bros., Inc. v. Union Oil Co. of California, 814 F.2d 628, 631 (Fed. Cir. 1987).” Dec. 7. Making a showing that a prior art reference anticipates a patent claim thus necessarily requires proof that a single reference “expressly or inherently” describes every element of that claim and with all elements being arranged in the reference as they are in the” slip op. at 7
Claim construction§ 102 anticipationPatents in suitUS 10,379,301 - PTAB · Nov 20, 2025 · IPR2025-00951 · APJ Eric C Jeschke · IPR · Institution
The Board instituted IPR on claims 1–19 and all asserted grounds, finding a reasonable likelihood that claim 1 would have been obvious over DuroMax and De Vries.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a) (2024) (“The Board institutes the trial on behalf of the Director.”). Inter partes review may not be instituted “unless . . . the information presented in the petition . . . 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.” 35 U.S.C. § 314. Upon consideration of the evidence and arguments in the record, for the reasons below, we determine that the information presented shows a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. We thus institute inter partes review on all challenged claims on all asserted grounds. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 362–63, 369–70 (2018); 37 C.F.R. § 42.108(a) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“For purposes of this Decision, we adopt the definition of the level of ordinary skill in the art proposed by Petitioner. As to the inclusion of physics in Petitioner’s definition, Patent Owner acknowledges that an undergraduate mechanical engineering degree holder would have the requisite knowledge here but does not adequately explain why an undergraduate physics degree holder would not. In addition, Patent Owner requires “a four-year degree in mechanical engineering or a closely related field,” but fails to identify what fields are “closely related.” See Prelim. Resp. 10 (emphasis added). Based on the Winkel Declaration, we are persuaded at this stage that a hypothetical undergraduate physics degree holder would have had adequate knowledge for one of ordinary skill in the art of the invention here. See Winkel Decl. ¶ 106. As to the requisite years of experience proposed in the definitions— three for Petitioner versus “at least one” for Patent Owner—we note that Patent Owner’s definition is broader than, but includes, Petitioner’s definition. Moreover, for both the inclusion of physics and the years of experience issues, Patent Owner acknowledges that the arguments in the Preliminary Response “are not impacted based on which definition is applied.” Prelim. Resp. 10. Further, Patent Owner does not argue at this stage that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would have understood either the challenged patent or the prior art.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“At this stage of the proceeding and on the current record, we need not and do not explicitly construe the phrase “selector switch.” 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)). Although we do not expressly adopt Petitioner’s proposed construction at this stage of the proceeding, we note that it at least generally aligns with the tentative claim construction issued by the United States District Court in the California Litigation: “Mechanical device whose positioning precludes simultaneous access to two fuels.” Ex. 300310 at 2; see also 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action, or a proceeding before the International Trade Commission, that is timely made of record in the inter partes review proceeding will be considered.”); Memorandum from Acting Director Coke Morgan Stewart to Members of the Patent Trial and Appeal Board (Sept. 15, 2025), available at https://www.uspto.gov/sites/default/files/documents/ Memo_re_prior_findings_of_fact_and_conclusions_of_law_9_16_25.pdf (“Prior Determinations Memo”) (discussing PTAB consideration of prior findings of fact and conclusions of law). We also note that Patent Owner” slip op. at 14
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“Like the Federal Circuit in In re Ellis, although the patent classification of the reference is “some evidence of ‘non-analogy, . . . we consider the similarities and differences in structure and function of the inventions . . . to carry far greater weight.” In re Ellis, 476 F.2d at 1372 (affirming the Board and rejecting the applicant’s nonanalogous art argument). Here, the challenged patent discusses in the Background of the Invention the need for a way to “prevent both valves from being ‘on’ at the” slip op. at 21
Claim construction§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 10,598,101 - PTAB · Nov 13, 2025 · IPR2025-00805 · APJ Eric C Jeschke · IPR · Institution
The Board instituted IPR on claims 1–24 and all asserted grounds, finding a reasonable likelihood that Petitioner would prevail on at least one challenged claim.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 314; 37 C.F.R. § 42.4(a) (2024) (“The Board institutes the trial on behalf of the Director.”). Inter partes review may not be instituted “unless . . . the information presented in the petition . . . 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.” 35 U.S.C. § 314. Upon consideration of the evidence and arguments in the record, for the reasons below, we determine that the information presented shows a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. We thus institute inter partes review on all challenged claims on all asserted grounds. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 362–63, 369–70 (2018); 37 C.F.R. § 42.108(a) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2
- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsNot reached
“C. Patent Owner’s Arguments Under 35 U.S.C. § 325(d) In the Preliminary Response, Patent Owner contends that Petitioner’s unpatentability arguments presented in this proceeding were previously considered by the USPTO. See Prelim. Resp. 31–33. In her decision referring this matter to the Board, then-Acting Director Stewart rejected that argument. See Paper 20 at 2–3 (discussing why “Petitioner provides persuasive reasoning, supported by evidence, that discretionary denial under 35 U.S.C. § 325(d) is not appropriate”); see also Prelim. Resp. 31–33 (referring to and citing Patent Owner’s Discretionary Denial Brief (Paper 8)). We need not and do not address this issue further.” slip op. at 15
- Skill levelSkill level petitioner adoptedDecided for petitioner
“For purposes of this Decision, we adopt the definition of the level of ordinary skill in the art proposed by Petitioner. As to the inclusion of physics in Petitioner’s definition, Dr. Singhose (a professor of mechanical engineering) testifies as to why undergraduate mechanical engineering degree holders would have the requisite knowledge here, but does not testify that undergraduate physics degree holders would not. See Singhose Decl. ¶¶ 2, 27, 28. In addition, Patent Owner and Dr. Singhose require “a four-year degree in mechanical engineering or a closely related field,” but fail to identify what fields are “closely related.” See Prelim. Resp. 11; Singhose Decl. ¶ 27. Based on the Morse Declaration, we are persuaded at this stage that a hypothetical undergraduate physics degree holder would have adequate knowledge for one of ordinary skill in the art of the invention here. See Morse Decl. ¶ 31. As to the requisite years of experience proposed in the definitions— three for Petitioner versus “at least one” for Patent Owner—we note that Patent Owner’s definition is broader than, but includes, Petitioner’s definition. Moreover, for both the inclusion of physics and the years of experience issues, Patent Owner acknowledges that the arguments in the Preliminary Response “are not impacted based on which definition is applied.” Prelim. Resp. 12 (citing Singhose Decl. ¶¶ 30–34). Further, Patent Owner does not argue at this stage that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would understand either the challenged patent or the prior art.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“B. Claim Construction In inter partes reviews, the Board interprets claim language using the same claim construction standard that would be used in a civil action under 35 U.S.C. § 282(b), as described in Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc). See 37 C.F.R. § 42.100(b). Under that standard, we generally give claim terms their ordinary and customary meaning, as would be understood by a person of ordinary skill in the art at the time of the invention, in light of the language of the claims, the specification, and the prosecution history. See Phillips, 415 F.3d at 1313–14. Although extrinsic evidence, when available, may also be useful when construing claim terms under this standard, extrinsic evidence should be considered in the context of the intrinsic evidence. See id. at 1317–19. Petitioner does not propose express constructions for any claim terms. Pet. 12. Patent Owner also does not propose any express constructions. See Prelim. Resp. 12. On the current record, we need not construe explicitly any 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)). As discussed below, however, the parties dispute the meaning of “gaseous fuel.” We address this issue below in the analysis of the challenge to claims 1–3, 5–9, and 18 based on Nakafushi and Olmr.” slip op. at 12
Claim construction§ 102 anticipation§ 103 obviousnessDiscretionary denialcites PhillipsPatents in suitUS 10,393,034
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.