- Charter Communications, Inc. / Altice USA, Inc. v. Touchstream Technologies, Inc.Some claims unpatentablePTAB · Jun 12, 2025 · IPR2024-01231 · APJ Georgianna W Braden · IPR · Final written decision
Claims 22–26 are unpatentable under §103; claims 1–21 were not shown unpatentable because the cited combinations do not teach or justify the claimed server-side command conversion.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner contends that a person of ordinary skill in the art of the ’251 patent would have had: (1) the equivalent of a four-year, B.S. degree from an accredited institution in computer science, computer engineering or an equivalent field; (2) approximately two years of professional experience with Internet-based video delivery systems; and (3) working proficiency with network architecture, including Internet-hosted server-client systems, and with computer programming. PO Resp. 21 (citing Ex. 2025 ¶¶ 24–25). Patent Owner’s declarant, Dr. Wicker, testifies that the parties’ definitions are only “slightly different,” and that if Dr. Wicker were to adopt Petitioner’s definition, that would not change any of his opinions. Ex. 2025 ¶ 24. Because the parties’ definitions of a person of ordinary skill in the art only “slightly differ,” we accept the assessment offered by Petitioner, which appears consistent with the ’251 patent and the asserted prior art. Regardless of which definition is applied, our analysis and decision would not change.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction Both parties propose construing the claim term “media player” because it was construed in a related inter partes review proceeding as well as in a district court case. Pet. 19; PO Resp. 21. According to Patent Owner, construing “media player” to mean “software for playing media” would be consistent with the construction applied in both related proceedings. PO Resp. 21. Petitioner agrees, noting that the term “media player” “‘refers to software and not to a hardware device.’” Pet. 19 (citing Ex. 1164, 13). player” used by both parties, and we need not engage in any further claim construction because there are no claim construction disputes that bear on the issues before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D. Alleged Obviousness of Claims 1–26 in View of Danciu and Mahajan or” slip op. at 11
- Expert testimonyPetitioner expert discountedPatent owner expert creditedMixed
“Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position. To the contrary, we find Dr. Wicker’s testimony to be credible because it is supported by the disclosures in both Mahajan and Danciu. Specifically, we agree with Dr. Wicker, who testified that Mahajan does not describe an abstraction layer as ever being on “a server in the network.” See Ex.1197, 18:21–24. We also find Dr. Wicker’s testimony credible when he explained that even if Mahajan’s abstraction layer were implemented on a server in a network as posited by Petitioner, it still would not result in the claim mapping proposed by Petitioner. See Ex. 2025 ¶ 45 (Dr. Wicker: “[T]he two abstraction modules work together to create a ‘collaboration media abstraction layer 130.’”) (citing Ex. 1114 ¶ 22; Ex. 2027, 39:6–40:12, 44:10–19 (Mr. Lett reading from and agreeing with paragraph 45 of Dr. Wicker’s Declaration)).” slip op. at 25
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentableNot shown unpatentable
“Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position.” slip op. at 25
Patent outcomesUS 8,356,251 mixedClaim construction§ 103 obviousnesscites KSRPatents in suitUS 8,356,251 - Charter Communications, Inc. / Altice USA, Inc. v. Touchstream Technologies, Inc.Some claims unpatentablePTAB · Jun 12, 2025 · IPR2024-01262 · APJ Georgianna W Braden · IPR · Final written decision
Claims 22–26 are unpatentable as obvious; claims 1–21 were not shown unpatentable because the asserted combinations did not teach or justify the claimed server-side command conversion.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner contends that a person of ordinary skill in the art of the ’251 patent would have had: (1) the equivalent of a four-year, B.S. degree from an accredited institution in computer science, computer engineering or an equivalent field; (2) approximately two years of professional experience with Internet-based video delivery systems; and (3) working proficiency with network architecture, including Internet-hosted server-client systems, and with computer programming. PO Resp. 21 (citing Ex. 2025 ¶¶ 24–25). Patent Owner’s declarant, Dr. Wicker, testifies that the parties’ definitions are only “slightly different,” and that if Dr. Wicker were to adopt Petitioner’s definition, that would not change any of his opinions. Ex. 2025 ¶ 24. Because the parties’ definitions of a person of ordinary skill in the art only “slightly differ,” we accept the assessment offered by Petitioner, which appears consistent with the ’251 patent and the asserted prior art. Regardless of which definition is applied, our analysis and decision would not change.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction Both parties propose construing the claim term “media player” because it was construed in a related inter partes review proceeding as well as in a district court case. Pet. 19; PO Resp. 21. According to Patent Owner, construing “media player” to mean “software for playing media” would be consistent with the construction applied in both related proceedings. PO Resp. 21. Petitioner agrees, noting that the term “media player” “‘refers to software and not to a hardware device.’” Pet. 19 (citing Ex. 1164, 13). player” used by both parties, and we need not engage in any further claim construction because there are no claim construction disputes that bear on the issues before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D. Alleged Obviousness of Claims 1–26 in View of Danciu and Mahajan or” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“attempts to extrapolate Mahajan’s specific teachings and specific architecture into a general principle such that specific commands are converted to universal commands and then universal commands are converted to specific commands regardless of the location of the process within a distributed system. See Tr. 14:5–11. Rather, we agree with Patent Owner that Petitioner’s extrapolation arguments are unsupported by Mahajan. We understand Petitioner argues that Mahajan’s “distributed computing environments” would have rendered it obvious to alter the location where command conversions occur. Pet. 41; Reply 10–11, 14. Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain” slip op. at 24
- Expert testimonyPetitioner expert discountedPatent owner expert creditedOther
“Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position. To the contrary, we find Dr. Wicker’s testimony to be credible because it is supported by the disclosures in both Mahajan and Danciu. Specifically, we agree with Dr. Wicker, who testified that Mahajan does not describe an abstraction layer as ever being on “a server in the network.” See Ex.1197, 18:21–24. We also find Dr. Wicker’s testimony credible when he explained that even if Mahajan’s abstraction layer were implemented on a server in a network as posited by Petitioner, it still would not result in the claim mapping proposed by Petitioner. See Ex. 2025 ¶ 45 (Dr. Wicker: “[T]he two abstraction modules work together to create a ‘collaboration media abstraction layer 130.’”) (citing Ex. 1114 ¶ 22; Ex. 2027, 39:6–40:12, 44:10–19 (Mr. Lett reading from and agreeing with paragraph 45 of Dr. Wicker’s Declaration)).” slip op. at 25
Patent outcomesUS 8,356,251 mixedClaim construction§ 103 obviousnesscites KSRPatents in suitUS 8,356,251 - Charter Communications, Inc. / Altice USA, Inc. v. Touchstream Technologies, Inc.Some claims unpatentablePTAB · Jun 12, 2025 · IPR2024-00322 · APJ Georgianna W Braden · IPR · Final written decision
Claims 22–26 are unpatentable under § 103; claims 1–21 were not shown unpatentable because the cited combinations do not teach or justify the claimed server-side command conversion.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner contends that a person of ordinary skill in the art of the ’251 patent would have had: (1) the equivalent of a four-year, B.S. degree from an accredited institution in computer science, computer engineering or an equivalent field; (2) approximately two years of professional experience with Internet-based video delivery systems; and (3) working proficiency with network architecture, including Internet-hosted server-client systems, and with computer programming. PO Resp. 21 (citing Ex. 2025 ¶¶ 24–25). Patent Owner’s declarant, Dr. Wicker, testifies that the parties’ definitions are only “slightly different,” and that if Dr. Wicker were to adopt Petitioner’s definition, that would not change any of his opinions. Ex. 2025 ¶ 24. Because the parties’ definitions of a person of ordinary skill in the art only “slightly differ,” we accept the assessment offered by Petitioner, which appears consistent with the ’251 patent and the asserted prior art. Regardless of which definition is applied, our analysis and decision would not change.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Construction Both parties propose construing the claim term “media player” because it was construed in a related inter partes review proceeding as well as in a district court case. Pet. 19; PO Resp. 21. According to Patent Owner, construing “media player” to mean “software for playing media” would be consistent with the construction applied in both related proceedings. PO Resp. 21. Petitioner agrees, noting that the term “media player” “‘refers to software and not to a hardware device.’” Pet. 19 (citing Ex. 1164, 13). player” used by both parties, and we need not engage in any further claim construction because there are no claim construction disputes that bear on the issues before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). D. Alleged Obviousness of Claims 1–26 in View of Danciu and Mahajan or” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundMotivation foundMixed
“Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position.” slip op. at 25
- Expert testimonyPetitioner expert discountedPatent owner expert creditedMixed
“Mr. Lett testifies that Mahajan “allows for its server media abstraction module to be located in a processing device that may not typically be labeled a ‘server,’ such as remote control 14 of Danciu.” Ex. 1198 ¶ 9 (citing Ex. 1102 ¶ 162; Ex. 1114 ¶ 17). Yet, both Petitioner and Mr. Lett fail to explain how or why a person of ordinary skill in the art would take the distributed nature allowed by Mahajan and completely flip its teachings to put a client or remote device process on a server device. Mr. Lett further fails to explain how or why one would want to move Mahajan’s abstraction layer in the first place. Although Mahajan teaches that its system can operate in a distributed environment, based on the explicit disclosure of Mahajan and its examples, we do not understand “distributed” to mean that (i) the server processes can occur on client devices and (ii) that client processes can occur on server devices. See Ex. 1114 ¶¶ 51, 58, 60, 61, 76, 77. Rather, we understand “distributed computing environments” to encompass “an environment where tasks are performed by remote processing devices that are linked through a communications network” because that is what is taught in Mahajan. Id. ¶ 58. Our understanding is supported by the testimony of Mr. Lett. See Ex. 1198 ¶ 8 (reciting the explicit disclosure in Mahajan). It is clear, based on the plain reading of Mahajan, that the distributed environment indicates that server 202 and client 204 could be located in different locations, but would be linked through a communications network where user-command 230 flows from client 204 to server 202. See Ex. 1114 ¶ 35, Fig. 2. At no point does Mahajan teach or even suggest that user-commands 230 would flow from server 202 to client 204 as proposed by Petitioner. Additionally, we find insufficient reason in the record to explain Petitioner’s argument appears to be based completely on hindsight bias created in view of the challenged claims. Therefore, we find little credibility in Mr. Lett’s testimony regarding the change or in Petitioner’s position. To the contrary, we find Dr. Wicker’s testimony to be credible because it is supported by the disclosures in both Mahajan and Danciu. Specifically, we agree with Dr. Wicker, who testified that Mahajan does not describe an abstraction layer as ever being on “a server in the network.” See Ex.1197, 18:21–24. We also find Dr. Wicker’s testimony credible when he explained that even if Mahajan’s abstraction layer were implemented on a server in a network as posited by Petitioner, it still would not result in the claim mapping proposed by Petitioner. See Ex. 2025 ¶ 45 (Dr. Wicker: “[T]he two abstraction modules work together to create a ‘collaboration media abstraction layer 130.’”) (citing Ex. 1114 ¶ 22; Ex. 2027, 39:6–40:12, 44:10–19 (Mr. Lett reading from and agreeing with paragraph 45 of Dr. Wicker’s Declaration)).” slip op. at 25
Patent outcomesUS 8,356,251 mixedClaim construction§ 103 obviousnesscites KSRPatents in suitUS 8,356,251 - Innolux Corporation v. Phenix Longhorn LLCInstitution deniedPTAB · Jun 9, 2025 · IPR2025-00044 · APJ Michael J Strauss · IPR · Institution
The Board denied institution because the Petition violated Rule 42.104(b)(3) and did not show a reasonable likelihood that claims 1–3, 5, and 6 were unpatentable as obvious.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“Accordingly, Petitioner has not identified corresponding structure for performing the recited functions of “optimizing . . . gamma reference voltage levels using means for executing a predetermined algorithm according to a predetermined criteria and data sensed by . . . at least one sensor, wherein said means for executing said predetermined algorithm is separate from [a] display to achieve [a] desired gamma curve” as required under 37 C.F.R. § 42.104(b)(3). Because Petitioner has not provided constructions, either rebutting the presumption that “means for executing” is a means-plus-function term, or identifying corresponding structure if it is a means-plus-function term, Petitioner has violated Rule 104(b)(3).” slip op. at 20
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner argues that a person of ordinary skill in the art (POSA) “would have had at least a bachelor of science degree in physics, electrical engineering, or the equivalent thereof and three (3) years of experience in circuit design or display technologies.” Pet. 12 (citing Ex. 1003 ¶ 24). According to Petitioner “[s]uch a POSA would have had knowledge of integrated circuits, gamma correction, and storage of gamma correction voltage values within memory, and would have understood how to search available literature for relevant publications.” Id. (citing Ex. 1003 ¶ 24). Patent Owner applies Petitioner’s definition for the purposes of the Preliminary Response. Prelim. Resp. 2. For purposes of this Decision, and based on the current record, we adopt Petitioner’s assessment of the level of skill for one of ordinary skill in the art. Pet. 12. This assessment is consistent with the ’788 Patent and the asserted prior art, and we apply it in our analysis below.” slip op. at 8
- BurdenDecided for patent owner
“Accordingly, Petitioner has not identified corresponding structure for performing the recited functions of “optimizing . . . gamma reference voltage levels using means for executing a predetermined algorithm according to a predetermined criteria and data sensed by . . . at least one sensor, wherein said means for executing said predetermined algorithm is separate from [a] display to achieve [a] desired gamma curve” as required under 37 C.F.R. § 42.104(b)(3). Because Petitioner has not provided constructions, either rebutting the presumption that “means for executing” is a means-plus-function term, or identifying corresponding structure if it is a means-plus-function term, Petitioner has violated Rule 104(b)(3).” slip op. at 20
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesDecided for patent owner
“and 5 recites “means for executing.” Ex. 1001, 7:36–40, 8:35–37. The use of the term “means” creates a rebuttable presumption that 35 U.S.C. § 112 ¶ 6 applies. See Williamson, 792 F.3d at 1348. Consistent with Patent Owner’s arguments (Prelim. Resp. 36–39), the Petition does not address the presumption and, more specifically, the Petition does not provide any argument or evidence as to why the presumption is rebutted. Furthermore, even if we were to consider Petitioner’s newly presented argument that “[t]he plain and ordinary meaning of ‘means for executing a predetermined algorithm . . . ’ connotes a general-purpose processor, which is understood as structure sufficient to perform the function” (Pet. Reply 5), such argument is not persuasive as it is not supported by evidence earlier presented in the Petition or otherwise. Furthermore, even if the plain and ordinary meaning of means for executing a predetermined algorithm were a general-purpose processor, for a computer implemented means-plus-function term the corresponding structure must be the specific algorithm implemented by the processor as argued by Petitioner. Pet. Reply 6.” slip op. at 16
Claim construction§ 103 obviousnessDiscretionary denialcites Phillips · GrahamPatents in suitUS 7,557,788 - Oracle Corporation v. Joseph L. De BellisAll claims unpatentablePTAB · Jun 4, 2025 · IPR2024-00221 · APJ Jon M Jurgovan · IPR · Final written decision
The Board held claims 1–7, 15–23, and 25–30 unpatentable as obvious over the five asserted combinations; Zellweger was prior art under § 102(e).
RulingsFinal written decision- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportReference is prior artPriority date, deniedDecided for petitioner
“We agree with Petitioner’s assertions that Patent Owner has not shown conception of the noted claim language prior to Zellweger’s filing date. For example, claim 1’s limitation 1A requires “determining a database schema.” We find no mention of this in Patent Owner’s conception evidence.” slip op. at 20
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“Patent Owner does not identify any evidence in the ’720 patent, its file history, or elsewhere, to support its restrictive construction of the claim language, nor do we find any lexicographical definition or disavowal of claim scope to support it. Luminara Worldwide, LLC v. Liown Elecs. Co., 814 F.3d 1343, 1353 (Fed. Cir. 2016) (“Absent lexicography or disavowal, we do not depart from the plain meaning of the claims”). Hence, the ordinary and customary meaning of “providing a list of database fields” in limitation 1B is not limited to the time a search query was 3 A patent related to the ’720 patent, US Patent No. 9,507,835 B2, filed December 17, 2015, uses the term “search-on-the-fly” in its claims. In contrast, the ’720 patent’s claims are directed toward the truncation feature described in the patent. This suggests that Patent Owner chose not to limit the ’720 patent’s claims to the context of “search-on-the-fly” notwithstanding the ’720 patent’s title. Ex. 1001, code (54). submitted.” slip op. at 11
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner contends as follows: A person of ordinary skill in the art at the time of the alleged invention (“POSITA”) would have had at least a bachelor’s degree in computer science, electrical engineering, or a related subject, and at least two years of experience working with databases, computer networks, and related web technologies. A more advanced degree can substitute for less work experience and vice versa. Pet. 17 (citing Ex. 1003 ¶¶ 57–61). Patent Owner does not dispute Petitioner’s proposed level of skill in the art, which is consistent with the problems, solutions, technology, and educational level set forth in the ’720 patent and the prior art references asserted by Petitioner. See generally PO Resp.; Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (the applied prior art may reflect an appropriate level of skill). Accordingly, we apply Petitioner’s proposed level in this Decision.” slip op. at 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Specifically, Petitioner contends that Cochran seeks to provide an efficient and user-friendly method to search computer databases, and recognizes that pick lists for searches may be voluminous and exceed the capacity of a pick box to display them simultaneously such that Cochran would benefit from improved navigation methods. Pet. 55–56 (citing Ex. 1005, 4:4–19, 10:58–65; Ex. 1003 ¶¶ 482–485). Petitioner asserts that Zellweger sought to remedy the same problem of navigating long pick box lists, and argues that a POSITA would have looked to Zellweger’s Alphabet or Content Lists to replace Cochran’s scroll bars. Id. at 56–57 (citing Ex. 1003 ¶ 485). Petitioner contends that the combination is “nothing more than using one known method (Zellweger) to improve another known method (Cochran) according to the express teachings of Zellweger to yield predictable results.” Id. at 57. Petitioner contends that Cochran and Zellweger are analogous because they are directed to the same field of accessing information in databases through graphical interfaces that make information more accessible, and are both implemented as computer software. Id. (citing Ex. 1005, code (57), 1:14–20, 4:2–57; Ex. 1007, code (57), 1:35–40, 2:30–43; Ex. 1003 ¶¶ 480–481). Petitioner alleges that a POSITA would have had a high expectation of success because, among other reasons, altering Cochran to truncate entries using Zellweger’s Alphabet and Content List menus would require nothing more than routine programming. Id. at 57–58.” slip op. at 26
Patent outcomesUS 6,760,720 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,760,720 - Charter Communications, Inc. / Plume Design, Inc. v. Adaptive Spectrum And Signal Alignment, Inc.Institution deniedPTAB · May 22, 2025 · IPR2025-00088 · APJ Kevin C Trock · IPR · Institution
The Board denied institution of IPR on all challenged claims under § 314(a), finding the Fintiv factors favored discretionary denial.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Institution denied fintivInstitution denied
“7. Conclusion on Discretionary Review When considering the Fintiv factors, we take “a holistic view of whether efficiency and integrity of the system are best served by denying or instituting review.” Fintiv, Paper 11 at 6. Based on our review, we find that the factors weigh in favor of exercising discretion to deny institution of the Petition. The factors weighing in favor of exercising discretionary denial include the scheduling of the parallel proceeding’s trial date many months prior to the Board’s projected statutory deadline for a final written decision, the substantial investment by the parties and the District Court in the ASSIA Litigation, the recommended denial of the motion to transfer by the District Court, and the issues on the merits raised by the Patent Owner in its Preliminary Response and our preliminary consideration. In our view, these factors outweigh the other Fintiv factors, including the lack of a stay, Petitioner’s offer to limit overlap between the two proceedings via stipulation, and the presence of Plume Design as a Petitioner in this proceeding. We, therefore, are persuaded that the interests of the efficiency under 35 U.S.C. § 314(a) to deny institution of the Petition.” slip op. at 16
Discretionary denialPatents in suitUS 11,050,654 - Innolux Corporation v. Phenix Longhorn LLCInstitution deniedPTAB · May 15, 2025 · IPR2025-00043 · APJ Kevin F Turner · IPR · Institution
The Board denied institution of IPR challenging claims 1–5 and 8–14, exercising § 314(a) discretion under Fintiv based on the Texas litigation.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Institution denied fintivInstitution denied
“We agree with Patent Owner that its asserted trial date of February 17, 2026, would likely occur approximately 4 months before the latest date on which a final decision can be issued in this proceeding (June 12, 2026), and that is the metric we should use to determine the proximity of trial date to the projected statutory deadline. Accordingly, the facts underlying this factor weigh in favor of denial.” slip op. at 9
Discretionary denialPatents in suitUS 7,233,305 - PTAB · May 7, 2025 · IPR2021-00906 · APJ Jameson Lee · IPR · Remand
On remand, the Board denied the motion to amend with proposed substitute claims 69, 70, 77, and 78 because the ’872 application did not provide written-description support.
RulingsRemand decision- RemandOther
“for the Federal Circuit. Papers 75–78. On February 3, 2025, the Federal Circuit issued a decision in which it stated: “We vacate and remand the Board’s decision with regard to claims 69 and 77, and their dependent claims, but otherwise affirm.” Paper 80.3 The formal mandate from the Federal Circuit was issued on March 12, 2025. Paper 79.” slip op. at 3
- 112 supportMotion to amend, deniedDenied
“Per the Federal Circuit’s instruction, the “first message” must come before the “another message” and “message preceding the another message.” However, the “first message” identified by Patent Owner, i.e., the RRC Connection Setup message, occurs after what Patent Owner identifies as the “another message,” i.e., the RRC Connection Request message. That mismatching sequence is evident from Figure 15 reproduced above.” slip op. at 8
NonePatents in suitUS 7,580,388 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. v. Fendgo, LLCAll claims unpatentablePTAB · May 5, 2025 · IPR2024-00113 · APJ Jon M Jurgovan · IPR · Final written decision
Claims 9–15 are unpatentable as obvious: claims 9, 11 over Zellner and Kim; claim 15 over Walker; and claims 9–14 over Martin and Kim, with claim 14 also over Martin, Kim, and Dixit.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner does not address, let alone dispute, Petitioner’s proposed level of skill in the art, which is consistent the problems, solutions, technology, and educational level set forth in the ’404 patent and the prior art references asserted by Petitioner. See generally PO Resp.; Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (the applied prior art may reflect an appropriate level of skill). Accordingly, we apply Petitioner’s proposed level in this Decision.” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“Reviewing the written description, we find no lexicographical definition or disavowal related to “owner identification information” in the ’404 patent. Instead, we find the term mentioned in relation to embodiments and examples. See, e.g., Ex. 1001, code (57), 4:17–25. Claim 8 of the ’404 patent recites that “owner identification information includes a name and a description of the owner of the mobile device” but, as Petitioner notes, the doctrine of claim differentiation suggests the term as used in claim 1 should be construed more broadly. Paper 28, 2; Littelfuse, Inc. v. Mersen USA EP Corp., 29 F.4th 1376, 1380 (Fed. Cir. 2022) (citing Ortho-McNeil Pharm. v. Mylan Lab'ys, Inc., 520 F.3d 1358, 1362 (Fed. Cir. 2008) (“[T]his court strives to reach a claim construction that does not render claim language in dependent claims meaningless.”)). Patent Owner is correct that “owner identification information” in claim 1 of the ’404 patent must be construed to encompass the name and description of the mobile device’s owner, as recited in claim 8. Paper 29, 2. However, we decline to restrict the term to exclude other indicia that may identify the device owner because that is not warranted by the written description, claims, and file history of the ’404 patent. Consequently, we construe “owner identification information” to mean “information that identifies the owner of the mobile device” under its ordinary and customary meaning as set forth in the ’404 patent and its file history. As recited in claim 8 of the ’404 patent, the term includes, but is not limited to, the name and description of the mobile device owner.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“have been aware of the need to implement techniques to reduce risk of false activation of panic button devices, and Zellner expressly recognizes this problem. Pet. 43–44 (citing Ex. 1008, 13:40–42; Ex. 1002 ¶¶ 242, 244). Petitioner asserts that Kim’s technique of requiring the user to press its device’s emergency key button a plurality of times was a known way to reduce false activations. Id. at 44 (citing Ex. 1002 ¶ 245). Petitioner posits that a POSITA would have considered the combination of Zellner and Kim to amount to the use of a known technique to improve a similar device in the same way, as well as the application of a known technique to a known device ready for improvement to yield predictable results. Id. at 44–45 (citing Ex. 1002 ¶¶ 246–247). These are recognized rationales supporting a motivation to combine. KSR, 550 U.S. at 417. We agree with Petitioner that a POSITA would have been motivated to modify Zellner’s device to require multiple button presses as taught by Kim in order to reduce false activations. Petitioner further contends that a POSITA would have had a reasonable expectation of success in modifying Zellner’s panic button to require three presses for activation, and that examples of prior art showed how this could be done. Pet. 45 (citing Ex. 1002 ¶¶ 248–251). Since Kim expressly discloses implementation of this feature, we agree with Petitioner that a POSITA would have expected success in combining Zellner and Kim. Ex. 1008, 13:40–42.” slip op. at 37
Patent outcomesUS 11,265,404 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,265,404 - Charter Communications, Inc. / Plume Design, Inc. v. Adaptive Spectrum And Signal Alignment, Inc.Institution deniedPTAB · May 5, 2025 · IPR2025-00087 · APJ Kevin C Trock · IPR · Institution
The Board denied institution of IPR challenging claims 1–20, exercising § 314(a) discretion based on the Fintiv factors.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Institution denied fintivDenied
“Accordingly, based on the current record, we disagree with Petitioner that Factor 2 is neutral. Instead, we agree with Patent Owner that Factor 2 favors discretionary denial.” slip op. at 11
Discretionary denialPatents in suitUS 11,477,108
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.