- 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 - Activision Blizzard, Inc. v. Milestone Entertainment, LLCAll claims unpatentablePTAB · Oct 8, 2026 · IPR2025-00711 · APJ Linda E Horner · IPR · Final written decision
Claims 1, 2, 4–7, 9, 11–13, 15, 19, 23, 24, and 29 are unpatentable as obvious over Kelly, Kelly and Paulsen, or Walker and Schneier.
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“B. Level of Ordinary Skill in the Art There is no evidentiary dispute about the level of ordinary skill in the art.7 Based on the testimony of Mr. Crevelt, we determine that a person of ordinary skill in the art would have had at least a bachelor’s degree in computer science or computer engineering, with at least three years of experience in game development. Pet. 12 (citing Ex. 1003 ¶¶ 100–103). Additional experience could substitute for less education, and additional education could likewise substitute for less experience. Id. We determine that the level of ordinary skill in the art adopted above is consistent with the level of technical understanding and competence reflected in the ’164 patent Specification and the asserted prior art references, based on our review of the record.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner argues that it is not necessary for the Board to provide an express construction for any claim term because the Petition “establishes the prior art meets each claim limitation under any reasonable construction.” Pet. 13. Patent Owner similarly submits that “[t]he Board need not construe any terms at this stage, because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” Resp. 8–9. Patent Owner notes, however that “it has relied on the plain meaning of ‘frequency of play’ in Claim 7.” Id. at 9. We agree that no explicit claim construction is necessary for this decision because, even were we to adopt Patent Owner’s proffered plain meaning of “frequency of play,” Petitioner has demonstrated that the prior art renders obvious this claim limitation. To the extent the parties’ arguments raise any implicit issues of claim construction, we address those issues within the context in which they are raised in our analysis below.” slip op. at 11
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“Patent Owner does not contest Petitioner’s showing that Kelly renders obvious the subject matter of claims 1, 2, 4–6, 11–13, 15, 19, 23, 24, and 29. Resp., passim; Tr. 50:4–13.8 We have reviewed Petitioner’s arguments and 8 Patent Owner argued in its Preliminary Response that Kelly does not disclose limitations [1.c.iii] and [1.c.v]. Prelim. Resp. 10–12. In our Institution Decision, we did not find these contentions persuasive based on the initial record. Dec. 20–24. Patent Owner has not presented these or any other arguments contesting Ground 1 as to claim 1 in its Response. Resp., the evidence and, based on that analysis, we find that Petitioner has shown by a preponderance of evidence that Kelly renders obvious the subject matter recited in these claims.” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentable
“and Paulsen render obvious claims 2 and 4. Pet. 36–40. Petitioner submits that to the extent Kelly’s player account is not player’s club information or information on non-cash amounts, a person having ordinary skill in the art would have been motivated to implement these features based on the teachings of Paulsen. Id. Specifically, Petitioner asserts that Paulsen teaches player tracking cards and player tracking programs including player tracking points. Id. at 38–40 (citing Ex. 1007 ¶¶ 8, 9, 49). Petitioner argues that a person having ordinary skill in the art would have been led to add these features to Kelly’s system to provide a more detailed view of tracking play, which would allow for rewarding patronage and engagement. Id. at 36–37, 39–40 (citing Ex. 1003 ¶ 264; Ex. 1007 ¶ 10). Paulsen discloses a “gaming machine bonusing method utilizing a player tracking card.” Ex. 1007, code (54). Paulsen discloses that player tracking programs and player tracking cards were used in the art to provide rewards, or “comps,” to players based on the player’s level of patronage (e.g., to the player’s playing frequency and/or total amount of game plays at a given casino). Id. ¶ 8. These rewards were intended to maintain a player’s interest in additional game play during a visit and provide loyalty incentives to players. Id. at ¶ 9.” slip op. at 29
Patent outcomesUS 11,335,164 unpatentableClaim construction§ 103 obviousnessPatents in suitUS 11,335,164 - Microsoft Corporation v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00254 · APJ Lisa A Murray · IPR · Final written decision
Claims 1–20 were not shown unpatentable under either §103 ground because Petitioner failed to establish motivation to combine and a reasonable expectation of success.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Mr. Haeberli’s formulation, finding it to be consistent with the evidence then of record, including the asserted prior art and the ’490 patent. Dec. 9. Following a review of the full record, we agree with Mr. Haeberli’s statement that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Mr. Haeberli’s for the purposes of this proceeding. We continue to view Mr. Haeberli’s proposed definition as consistent with the ’490 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“In our Decision on Institution, the only term that we found it necessary to construe was the term “string separator character” in claim 1. We preliminarily construed this term to mean “a single-character string separator.” Dec. 11, 30–31. We invited the parties to address the appropriateness of this construction over the course of the trial. Id. at 11, 31. In its briefing, Patent Owner agrees with the Board’s preliminary construction, arguing that it is “consistent with the intrinsic evidence.” PO Resp. 8 (citing Ex. 1001, claims 8 and 20). Patent Owner further argues that a person of ordinary skill would have understood a multi-character Boolean operator such as “AND” to be “a search syntax instruction rather than a string separator.” Id. at 9 (citing Ex. 1059, 162; Ex. 2001 ¶ 112). Petitioner’s Reply Brief does not address the issue of claim construction. See generally Reply Br.; see also Pet. 11 (“Unless otherwise noted, Petitioner applies the plain and ordinary meaning of all claim terms below.”). Following our review of the full record, we determine that it is not necessary to construe this or any other claim term for the purposes of this Decision.2 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (Only terms that are in controversy need to be construed, and then only to the extent necessary to resolve the controversy.). In our analysis below, we interpret the language of the claims according to its plain and ordinary meaning.” slip op. at 10
- Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner
“Having reviewed the evidence of record, we find Mr. Haeberli’s testimony to be more persuasive and better supported by the evidence. According to Dr. Terveen, “[r]obust programming languages such as C and C++, together with well-developed operating system and UI frameworks, . . . allowed an ordinary programmer to build a UI that supported incremental searching, as evidenced by the numerous prior art systems that implemented such functionality, including Entourage, Eudora, Emacs, Canon Cat, SwyftWare, and others. Ex. 1100 ¶ 43 (citing Ex. 1004, 8–9, 161; Ex. 1021, 125, 127, 129; Ex. 1039, 102–103; Ex. 1043, 385–389). The relevant question, though, is not whether it would have been possible to build a user interface that supported incremental search, but whether it would have been “simple and straightforward” to execute an incremental search of multiple partial search strings on large, indexed multi-file databases such as those described in the Lotus Notes references, as Dr. Terveen alleges. None of the prior art discussed in the “State of the Art” section of Dr. Terveen’s initial declaration, taken individually or together, discloses incrementally searching a plurality of files using two partial search strings. See Ex. 1003 ¶¶ 32–33, 37, 40; Ex. 2001 ¶ 100. Thus, creating a user interface might be “simple,” but the evidence suggests that the back-end execution of an incremental search is not. See, e.g., Ex. 1021, 126 (Raskin, concluding that “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches”).” slip op. at 23
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“different approach from that taken in Lotus Notes. The difference between Raskin’s sequential scanning method and the index-based system described in Wilcox is that sequential scanning by definition can only scan one document at a time as each document is loaded into a “buffer.” See, e.g., Ex. 2020 ¶ 35. Lotus Notes, however, only needs to load the index into memory for a user to be able to locate the single index entry identifying all instances of an indexed term across all indexed files. In fact, Raskin acknowledges that indexing may be necessary to maintain an acceptable response time. Ex. 1021, 132 n.10; see also id. at 129 (indexing speeds search times). Mr. Haeberli’s third and final reason for concluding that one of ordinary skill would not have been motivated to combine Raskin’s incremental search with Lotus Notes is that at the time using incremental searches would have presented “extreme technical difficulties.” Ex. 2001 ¶ 101. Here again we find Mr. Haeberli’s explanation more persuasive than Dr. Terveen’s opinion that combining the teachings from Raskin with Lotus Notes’ teachings “would have required only simple and straightforward software modifications.” Ex. 1003 ¶ 80. According to Mr. Haeberli, “there are serious technical challenges with implementing the complex search strategies of the challenged claims in the systems on which Dr. Terveen relies.” Id. ¶ 96. As Patent Owner argues: searching across a set of files to find specific files requires the system to identify which files are in the set, access those files (which are often not loaded in active memory), search their contents, determine which files contain matches to search criteria, and then present results to the user; all tasks that do not exist in the same way (or at all) for a search confined to text in a single open file already loaded into memory. Sur-Reply 9; see Ex. 2020 ¶¶ 15, 35–36. There would have been other challenges as well. For example, “[t]he type of sequential scanning typically employed to search a single open document is very time and resource intensive if employed to search a large set of documents.” Ex. 2020 ¶ 15. Also, “[i]mplementing incremental search in the Lotus Notes indexed system would necessarily require a larger index, which would slow down, rather than increase the search speed.” PO Resp. 23; see Ex. 2020 ¶ 33. Finally, Raskin itself concludes that “even if incremental searching is advantageous, ‘almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.’” Ex. 2001 ¶ 96 (emphasis added by Mr. Haeberli) (quoting Ex. 1021, 126). In short, Mr. Haeberli presents three significant reasons why there would have been no motivation or expectation of success in combining the teachings of Wilcox with those of Raskin. Dr. Terveen’s opinion to the contrary, on the other hand, is not supported by evidence. Dr. Terveen testifies that “[a] POSITA would have been motivated to perform Lotus Notes’ multi-string search incrementally for the reasons stated by Raskin: speed, effectiveness, and ease of use.” Ex. 1003 ¶ 78 (citing Ex. 1021 ¶¶ 125–127). The evidence, however, not only fails to support Dr. Terveen’s testimony, but also demonstrates that one attempting to make the proposed combination would not have reasonably expected the proposed combination to result in greater speed or effectiveness.” slip op. at 27
Patent outcomesUS 10,552,490 not shown unpatentableClaim construction§ 103 obviousnesscites KSRPatents in suitUS 10,552,490 - Microsoft Corp. v. X1 Discovery, Inc.No claims unpatentablePTAB · Jun 18, 2026 · IPR2025-00255 · APJ William V Saindon · IPR · Final written decision
Claims 1–27 were not shown unpatentable under either §103 ground because Petitioner did not establish a persuasive reason to combine the cited teachings with adequate factual support.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner does not comment on Petitioner’s formulation of the level of ordinary skill, or offer its own formulation in its Response. Patent Owner’s declarant, however, states: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that [Petitioner] has provided its own definition . . . . 31. I believe [Petitioner’s] definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. In our Decision on Institution, we adopted Patent Owner’s formulation, finding it to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent. Dec. on Inst. 8. Following a review of the full record, we agree that Petitioner’s definition of one of ordinary skill in the art is “not meaningfully different” from Patent Owner’s for the purposes of this proceeding. We continue to view Patent Owner’s proposed definition as consistent with the ’139 patent and the asserted prior art, and we apply it in our analysis below. However, our analysis of the issues below would have been the same had we instead adopted Petitioner’s proposed definition.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed patent owner constructionOther
“Petitioner does not assert any explicit claim constructions. Pet. 12. In our Decision on Institution, the Board construed “string separator character” as “a single-character string separator.” Dec. on Inst. 10, 28–29. Patent Owner explicitly agreed with this construction in its Response (Resp. 8–9), and Petitioner offered no further comment in its Reply. Although no claim construction issue is squarely before us now, we maintain our prior construction of “string separator character,” and do not construe any further limitations. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable
“We agree with Patent Owner that a problem with Petitioner’s combination is that it proposes to take the idea of incremental searching from Raskin and divorce it from Raskin’s teaching of incremental searching. See PO Resp. 20 (arguing, “a [person of ordinary skill in the art] must consider all the teachings of a reference, and not pick out general ‘concepts’ disclosed in the art without considering the context in which they are used”); see also id. at 17–28 (setting out the whole argument); Ex. 2020 ¶¶ 39–62 (Patent Owner’s declarant explaining why Petitioner’s approach is “technically problematic”). Raskin’s incremental search is tied to finding and moving to character strings within a document. Ex. 1021, 125. For example, if a user were to type a string that was found in the text, “the instance [of that string] is selected and the cursor placed immediately after the end of the selection.” Id. The cursor can move about the text as characters of the search string are added or deleted. Id. at 125–126. Thus, Raskin discloses in-text search, even when searching across documents. Id. at 132 (“After the local document has been completely searched the search then proceeds through the following documents until the end of the folder is reached, when the search continues from the beginning of the first document in the folder until the current, already searched document is reached. After cycling through the folder, the next larger domain is treated similarly, and so forth.”). Raskin even distinguishes its text-finding search from Lotus Notes’ document-finding search, stating that “[i]t is usually easy to tell in what domain you are searching, because you see the results in context; what you see is not just a list of file names, as with many present search systems.” Id. (emphasis added); see also PO Sur-reply 16 (citing the same page and arguing that “Raskin recommends doing the opposite of what is claimed”). This context gives credence to Patent Owner’s argument that “the search functionalities disclosed in the Lotus Notes References and Raskin are materially different in such a way as to render combining them anything but simple and straightforward.” PO Resp. 26–27. Indeed, Petitioner has given little-to-no explanation of how one takes the “idea of incremental search” and applies it to Lotus Notes. Ex. 2021, 116:20–117:17 (Petitioner’s declarant testifying that “Raskin is not explicitly talking about searching across a set of documents [at once], but the teaching that I relied on in general from Raskin is the idea of incremental searching,” and “I did not have to talk about implementation level details or incorporating a particular implementation. That wasn’t necessary for my opinion.”). Raskin does not teach a mode of incremental searching that applies to the query-style, document-finding searching in Lotus Notes. See generally Ex. 1021; see also Ex. 2020 ¶¶ 34–35 (Patent Owner’s declarant contrasting Lotus Notes and Raskin). Raskin even states that it is “difficult or impossible to implement incremental searches” using standard interface-building tools. Ex. 1021, 126; Ex. 2020 ¶ 60 (Patent Owner’s declarant stating that this passage “directly undermines [Petitioner’s declarant’s] suggestion that a [person of ordinary skill in the art] would have been motivated to implement Raskin’s incremental search approach in the Lotus Notes system”).” slip op. at 34
- Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightMotivation not foundNot shown unpatentable
“Entourage and what True is doing and how it is doing it, Petitioner asserts that it would have been obvious to use True’s two search strings “to provide more targeted searching, as was common sense and well known in the art.” Pet. 60 (citing Pet. 8–9; Ex. 1057, 27); see also id. at 56, 66 (similar). But we are not persuaded by a preponderance of the evidence that True provides more targeted searching or better search results when finding documents. True itself appears silent on the issue. Petitioner cites Exhibit 1057, but all that stands for is the general premise that doing a Boolean AND search in a Web search engine reduces the number of search results. Ex. 1057, 27. Petitioner does not allege that True uses a Boolean AND search of the kind discussed in Exhibit 1057. Thus, the statement in Exhibit 1057 regarding reducing the number of search results is tied to a manner of performing Boolean searches, something Petitioner does not use to modify Entourage. In other words, Exhibit 1057 is of little relevance to the Entourage-True combination, and does not serve as a factual underpinning in support of Petitioner’s reasoning. Petitioner also cites to several other references that discuss Boolean-style searches, but these generic background disclosures do not explain why a person of ordinary skill in the art would have considered it obvious to use one or more features of the probabilistic-based interest level search from True in a document-finding application like Entourage. See Pet. 8–9 (string citing over a dozen references with no pinpoint citations). Accordingly, there appears to be little reason, absent hindsight, to incorporate some aspect of a text-as-proxy-for-sounds system like True into Entourage’s filter or Find feature to provide more targeted searching. Accord Ex. 2020 ¶ 120 (“Patent Owner’s declarant stating that “a [person of ordinary skill in the art] working on the problem of searching large document collections would not look to [True,] a system designed for navigating imprecise transcriptions of single audio files, as the technical approaches and constraints are entirely different”). Patent Owner argues, and we agree, that another problem with Petitioner’s combination is that True does not appear to actually provide more targeted or better searching. PO Resp. 59–60 (“True’s search capabilities are inherently imprecise”) (citing Ex. 1009, 1:18–27; Ex. 2001 ¶ 137); see also Ex. 1009, 4:31–37 (explaining that True uses a speech recognition system that calculates confidence levels based on a “% likelihood that [a word] corresponds to the portion of the digitized audio [at a given time]”); Ex. 2020 ¶ 114 (Patent Owner’s declarant stating that “the purpose of True is not to definitively locate where a search string actually appears”). Petitioner does not explain what about True would make some aspect of Entourage’s filter or Find features more targeted. Even if it was known to use Boolean AND searches, for example, Petitioner is not citing True to modify Entourage to have a Boolean search. True uses an “interest level” search instead, which is more inclusive than a Boolean AND search (it adds together hits for “queen” OR “mother,” and may return hits containing neither). Ex. 1009, 5:29–50, Fig. 2 (showing results list 22 having several results which do not indicate any of the searched-for words); see Ex. 2020 ¶ 116 (Patent Owner’s declarant analyzing True’s interest level search would also include “text [that] does not show the query word”). Petitioner does not appear to be proposing to incorporate an interest level search or a Boolean-style search into the filter or Find features, and we are not persuaded that True in fact provides more targeted searching. Even if the quality of the transcripts in True happened to be perfect (see Pet. Reply 10, arguing that “True describes searching a text file that has 100% accuracy”), the fact remains that True attempts to find text in particular time windows using an interest level search based on the probability that a word or words were spoken in a given time window, which is completely different from what Entourage is doing with its search (see Ex. 2020 ¶¶ 114–116, 121). In its Reply, Petitioner states that True teaches “an incremental search for multiple search strings entered in a search field.” Pet. Reply. 10. This is a broad generalization of what True does, made with the benefit of hindsight, but as we have just explained, True’s interest level search is different from the kinds of searches done in Entourage or even the Boolean-style web searches performed in the background references. See, e.g., Ex. 1057, 27. This means it is not a matter of taking one known teaching and simply applying it to another system. True is doing something different, and it’s not clear how True’s search would actually provide “precise, targeted search results” (Pet. Reply 3) given that True appears to suggest a less-targeted search than claimed (see, e.g., Ex. 1001, 29:62–63, claiming “identifying one or more documents included in both the first one or more documents and the second one or more documents”). See also Ex. 2001 ¶¶ 135 (Patent Owner’s declarant stating that “Entourage and True are directed to completely different purposes”), 136–138 (further analysis); Ex. 2020 ¶ 114 (stating that “the purpose of True is not to definitively locate where a search string actually appears”), ¶ 116 (stating that True returns text that does not even have the search word). True does not teach, suggest, or support Petitioner’s general premise that there is a benefit for an incremental search for multiple search strings entered in a search field or that such searches would provide precise, targeted search results. The problem with Petitioner’s analysis becomes more apparent when the Petition turns to the “string separator character” of claim 1. Notably, it is the claimed string separator character that converts a field with a single search string into a field with two search strings. See, e.g., Ex. 1098, 37:12– 41–4 (deposition of Patent Owner’s declarant) (discussing that a string separator character is what instructs the computer to break up one string of characters into separate strings of characters). Thus, one cannot discuss the string separator character apart from the limitations requiring first and second search strings in a single search field. Nevertheless, Petitioner treats the “string separator character” in isolation. See Pet. 61–62. Petitioner’s reason for modifying one or both of Entourage’s filter and/or Find feature(s) to have a string separator character is because “it was common to [use string separator characters].” Id. at 61. However, even if something was known, it does not mean it is obvious to incorporate it into one or both of these features in Entourage. KSR, 550 U.S. at 418 (“a patent composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art”). Adding a string separator character to divide a single string into two separately searched strings changes how the software would function. See Ex. 1098, 39:22–40:8 (Patent Owner’s declarant testifying that software has to look for a string separator character in order to know multiple search strings were entered in the field). The space character in “Orson Welles,” used in the Advanced Find example in Barber, for example, is not a string separator character because one looking to exclude hits with “Orson Welles” is searching for the string “Orson Welles”—the space is another character in the name string whose inclusion serves a specific semantic purpose (delineating between a first and last name). See Ex. 2001 ¶ 151 (“there is no evidence that when a user types ‘Orson Welles’ into this Find command text box that a search is performed on ‘Orson’ and ‘Welles’ separately as opposed to searching on the full text string ‘Orson Welles.’”); Ex. 1006, 387 (discussing how exclude the specific person “Orson Welles” from the search, not to find someone having the first name “Orson” or the last name “Welles”); see also Ex. 1003 ¶ 144 (Petitioner’s declarant implicitly acknowledging that the space in “Orson Welles” is not a string separator character). Thus, the space character in “Orson Welles” does not signal to the computer to break the string up into two parts at the space and perform” slip op. at 42
Patent outcomesUS 9,633,139 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 9,633,139 - 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 - Adobe Inc. v. Jonathan E. JaffeNo claims unpatentablePTAB · Mar 4, 2026 · IPR2024-01352 · APJ Bach V Hoang · IPR · Final written decision
Claims 1–6 were not shown unpatentable under any asserted §103 ground because the references did not teach monitoring the physical coupling between the sensor and memory.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“The Institution Decision adopted and applied Petitioner’s proposed level of ordinary skill because Petitioner’s “definition generally comports with the level of skill necessary to understand and implement the teachings” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction needed
“The parties present various claim construction arguments, disputing the meaning of three limitations recited in claim 1: “a sensor, which is tightly coupled to said memory”; “monitoring the integrity of the tight coupling between said memory and said sensor”; and “based on.” See Pet. 9–14; PO Resp. 5–12; Pet. Reply 4–9; PO Sur-reply 4–11. For purposes of this Decision, we do not need to discuss the construction of “based on.” 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 explained below, this Decision turns on whether Glass or Rieger discloses limitation [1c] reciting “monitoring the integrity of the tight coupling between said memory and said sensor.” Ex. 1001, 20:65–66; see infra §§ II.C.2, II.E.1, II.F. That limitation recites an element which overlaps with the earlier-recited limitation “a sensor, which is tightly coupled to said memory.” To reach our decision, we need only provide a limited discussion of two of the parties’ claim construction arguments. Our analysis follows.” slip op. at 13
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“said integrity is compromised, then also providing an indication of said compromised integrity.” Ex. 1001, 20:65–21:2. Although Petitioner points out that the limitation does not expressly recite “‘specifically’ monitoring the tight coupling” (Pet. Reply 8), the structure of the clause suggests that the tight coupling is specifically monitored. At a high level, the limitation is straightforward in its recitation that the integrity being monitored is “of the tight coupling” (Ex. 1001, 20:65–66 (emphasis added)), plainly suggesting that the tight coupling is specifically monitored. More granularly, breaking the relevant clause down to its grammatical parts, the clause recites a gerund (“monitoring”) acting on a direct object (“the integrity”) which is modified by a prepositional phrase (“of the tight coupling”). Notably, the object of the preposition (“of”) is “the tight coupling.” Altogether, this reads that the integrity being monitored is specifically of the tight coupling. Also, the claim recites that “if said integrity is compromised, then also providing an indication of said compromised integrity.” Therefore, from the claim language we know that the “integrity” of the tight coupling is something that may be “compromised,” which is consistent with Patent Owner’s proposed construction of determining whether the physical coupling has been “accessed or disturbed.” Petitioner’s interpretation effectively inserts additional language into the limitation such that the limitation includes monitoring the integrity of a device containing or surrounding the tight coupling, such as a camera (or camera housing), e.g., “monitoring the integrity of a camera that includes the tight coupling.” But, because the plain reading and the structure of the limitation reads that it is specifically the tight coupling’s integrity—not another physical structure, like a camera—which is being monitored, a monitored is not consistent with the language of the claim. See PO Resp. 9 (arguing that “Petitioner’s construction is improper because the claim language explicitly requires monitoring the physical coupling between the memory and the sensor as opposed to some third structure” (emphasis omitted)).” slip op. at 17
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“package 50 does not specifically monitor the integrity of the coupling between Glass’s sensor and the memory and, instead, argues that Glass detects tampering of all “the components and interconnections contained in that packaging,” e.g., control logic 44, cropper 46, compressor 47, MUX 45, code generator 48, and the various interconnections between those components. See Pet. Reply 16; Ex. 1005, 5:13–41. As explained above, we construe “monitoring the integrity of the tight coupling between said memory and said sensor” to mean determining whether the physical 7 Petitioner does not assert that a person of ordinary skill in the art would have been motivated to modify Glass’s device in any way; Petitioner solely argues that Glass teaches limitation [1c], based on Petitioner’s proposed claim construction. See Pet. 30–32 (“Glass discloses this limitation.”); Pet. Reply 16–17 (“Glass and Rieger disclose the ‘monitoring’ step.”). disturbed, which specifically requires monitoring the physical coupling between the sensor and the memory. See supra § II.C.2. As we agree with Patent Owner that this limitation requires monitoring the physical coupling between the sensor and the memory, monitoring Glass’s tamper resistant package 50 does not teach or disclose “monitoring the integrity of the tight coupling between said memory and said sensor.” Accordingly, we determine that Petitioner fails to show that Glass teaches or suggests [1c] monitoring the integrity of the tight coupling between said memory and said sensor when said at least one internal and unique parameter is generated, and, if said integrity is compromised, then also providing an indication of said compromised integrity, as required by claim 1. Consequently, we determine that Petitioner has not shown, by a preponderance of the evidence, that the subject matter of claim 1 would have been obvious over Glass.8” slip op. at 30
Patent outcomesUS 6,757,828 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 6,757,828 - Facebook, Inc. / SAP America, Inc. et al. v. Express Mobile, Inc.All claims unpatentablePTAB · Jan 16, 2026 · IPR2022-00518 · APJ Jeffrey S Smith · IPR · Remand
Claims 1–4 and 6 are unpatentable under §103 because the prior-art combinations teach limitations 1(c) and 1(g) under the proper construction of “style.”
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
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided 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
- 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
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-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
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.