- Palo Alto Networks, Inc. v. Centripetal Networks, Inc.No claims unpatentablePTAB · Jul 21, 2025 · IPR2021-01150 · APJ Stacey G White · IPR · Remand
On remand, the Board held that Petitioner had not shown claims 1–18 unpatentable under § 103 over Paxton, Sutton, and Ivershen because the combination did not teach or motivate transmission responsive to correlation.
RulingsRemand decision- RemandOther
“the Final Written Decision for “not clearly explaining its holding or rationale regarding motivation to combine and whether the proposed combination teaches the final limitation of claim 1: transmitting an indication of the first host responsive to the correlating.” Palo Alto Networks, 122 F.4th at 1384. In the opinion, the Federal Circuit explained that the Final Written Decision “never made a clear finding on whether a person of ordinary skill in the art would have been motivated to modify Paxton by adding Sutton’s step of transmitting a notification of malicious activity after Paxton’s correlation step,” as proposed by Petitioner. Id. at 1385. The Federal Circuit stated that the Board “failed to explain why a person of ordinary skill in the art would not have been motivated to modify Paxton to provide the recited notification as taught by Sutton in response to the correlation disclosed in Paxton.” Id. The Federal Circuit concluded that “[b]y reading Paxton and Sutton in isolation, the Board erred,” and that we vacate and remand for the Board to clarify and explain its holding on whether a person of ordinary skill in the art would have been motivated to transmit the identity of the first host (e.g., to an administrator) as taught by Sutton, responsive to the correlating disclosed by Paxton to improve network security.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“the alleged invention of the ’903 patent “had a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field, and approximately 2–3 years of experience in the design or development of telecommunication systems, or the equivalent.” Pet. 13 (citing Ex. 1003 ¶¶ 18–20). Petitioner further notes that “[a]dditional graduate education could substitute for professional experience, or significant experience in the field could substitute for formal education.” Id. Patent Owner’s proposed level of ordinary skill is similar, with Patent Owner contending that the ordinary skilled artisan “would be someone with a bachelor’s degree in computer science, electrical engineering, or related field, and either (1) two or more years of industry experience and/or (2) an advanced degree in computer science or related field.” PO Resp. 12–13 (citing Ex. 2019 ¶¶ 27– 31). Similar to Petitioner, Patent Owner also states that a person of ordinary skill in the art “may have additional industry experience in lieu of a formal degree.” Id. at 13.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“After review of the current record, we conclude that no express claim construction is necessary for the purposes of this Decision. See, e.g., Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng'g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”).” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable
“responsive to the correlation, we are not persuaded that one of ordinary skill in the art would have been motivated to combine the teachings of these references in the manner advocated by Petitioner. Petitioner contends that this combination would only involve “[t]he application of known techniques (e.g., Sutton’s implementation of rules and data to define security policies, disallowed websites, etc.) to improve similar devices (e.g., servers, gateways, firewalls, etc. in Sutton’s and Paxton’s systems) to provide predictable results in the same way (e.g., to provide packet-filtering functions preventing communications with potentially malicious hosts).” Id. at 22–23.” slip op. at 25
Patent outcomesUS 10,530,903 not shown unpatentableClaim construction§ 103 obviousnesscites GrahamPatents in suitUS 10,530,903 - Dropbox, Inc. v. Motion Offense, LLCAll claims unpatentablePTAB · Jul 1, 2025 · IPR2024-00287 · APJ Norman H Beamer · IPR · Final written decision
Claims 9–12, 14–16, and 22–24 are unpatentable under § 103 over Riepling and Meisels, or Riepling, Manzano, and Meisels; claim 13 was disclaimed.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner’s proposal is consistent with the level of ordinary skill in the art as reflected by the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); GPAC, 57 F.3d at 1579. We apply Petitioner’s articulation.” slip op. at 20
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“construction of “representation of the at least one file.” Petitioner is correct that a representation of a file is not the file itself, but (in keeping with the ordinary meaning of “representation”) is rather some sign or symbol that stands for the folder. Reply 2. This is confirmed by the explicit example of a representation of a folder in the ʼ906 application, illustrated in the portion of Figure 6B reproduced below (highlighted here for purposes of explanation). This portion of Figure 6B depicts representations of two files: “FamilyHistory.docx” and “XmasLetter-2012.pdf.” The ’906 application specifically states: [A] located data resources dialog UI element 630b . . . includes a presentation space 632b for presenting a user detectable representation of some or all of the data objects identified in the received data object identification response from . . . second node 504. Ex. 2004 ¶ 147 (emphasis added). The entries in the above figure are representations of the files, not the files themselves. The actual files are stored in the file system storage associated with the user’s node, and only retrieved if the user selects the “Access” or “Access All” elements. Id. ¶ 148. Patent Owner misconstrues the claim 22 language, “a first representation of the at least one file, in a location among one or more folders, that is stored at the at least one server” and “a second representation of the at least one file, in a location among one or more folders, that is stored at the first node.” Patent Owner infers from this language that the representation is itself a file that is “in a location among one or more folders” and is stored on a server or at a node. PO Resp. 17. Not so — the representation of a file, such as “FamilyHistory.docx” in the above figure, is not stored at a server or node, but rather is simply displayed on a screen. As the ’906 application states: A representation of a program entity may be stored and/or otherwise maintained in a presentation space. As used in this document, the term “presentation space” refers to a storage region allocated and/or otherwise provided for storing presentation information . . . . A screen of a display, for example, is a presentation space.” slip op. at 22
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“because (i) Riepling and Meisels are from the same field of endeavor, directed to sharing files over a network; (ii) the combination would have yielded expected, predictable results, using known and routine computer programming principles, to modify Riepling’s system to generate an electronic message that includes a link pointing to an uploaded file; (iii) the combination would have been readily implemented given Meisels’ teachings of inserting, in an electronic message, a link to a shared location where a file is uploaded; and (iv) the combination was suggested because Meisels expressly disclosed a benefit of sending an email message with a link, to avoid multiple copies of a file from existing at multiple locations, and sending links to one file to multiple recipients and managing permissions on an individual recipient basis. Pet. 67–70 (citing Ex. 1107, Fig. 1, ¶¶ 2, 4, 19; Ex. 1108, Fig. 4, ¶¶ 1, 3, 41–45, 56; Mowry Decl. ¶¶ 194–198). In addition, for reasons similar to the motivation basis, Petitioner argues that a person of ordinary skill in the art would have had a reasonable expectation of success in making the combination. Id. at 70–71 (citing Mowry Decl. ¶¶ 199–200). Other than its arguments directed to ’520 claim requirement 9[l], discussed below in Section III.D.4.d), Patent Owner does not further address Petitioner’s arguments regarding the combination of Riepling and Meisels. As discussed in that section, we are persuaded by Petitioner’s expert’s testimony that one of ordinary skill would have applied the document link teachings of Meisels to modify Riepling. Accordingly, we determine that Petitioner has proved by a preponderance of the evidence that one of ordinary skill in the art would have been motivated to combine Riepling and Meisels in the manner argued by Petitioner.” slip op. at 32
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“We agree with Petitioner that set content field 325 of Riepling teaches or suggests claim requirement 9[b]. As Petitioner’s expert explains, the fact that field 325 has an appearance identical to that of fields 321–324 in Figure 3, which fields are specifically stated to be “text field[s],” strongly suggests that field 325 is also a text field. Mowry Decl. ¶ 70; see also Reply 10–11. Patent Owner’s suggestion that field 325 could be a dropdown list or other type of field is contradicted by the fact that it does not show the typical dropdown arrow associated with a dropdown box, or other typical non-textbox appearance such as the checkbox appearance of field 320. Moreover, in the example of Figure 3, the “Set Content” entry is “audio,” which is a file description. Reply 10. The fact that “JPEG” is checked in field 320 is not inconsistent with the “audio” entry in field 325, given that, as Riepling explains, “it may be possible for audio files such as MP3 files to contain non-MP3 data, such as JPEG data embedded within the MP3 files.” Id. at 11 (citing Ex. 1107 ¶ 32; Mowry 2nd Decl. ¶ ¶ 101–104). Also, there is no reason why the Figure 5 response that gives the uploader the ability to provide additional description of the file being uploaded is inconsistent with the ability of the requester first describing what type of file is being requested via field 325 in Figure 3. Id. at 11–12. Accordingly, for the reasons discussed above, we are persuaded that the record supports Petitioner’s arguments regarding claim requirement 9[b].” slip op. at 37
Patent outcomesUS 11,611,520 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,611,520 - Dropbox, Inc. v. Motion Offense, LLCAll claims unpatentablePTAB · Jun 30, 2025 · IPR2024-00286 · APJ Norman H Beamer · IPR · Final written decision
Claims 17–21 are unpatentable under § 103 over Houston and Garcia; the Board did not reach the alternative grounds.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We conclude that there is no basis for Patent Owner’s proposed construction of “representation of the at least one folder.” Petitioner is correct that a representation of a folder is not the folder itself, but (in keeping with the ordinary meaning of “representation”) is rather some sign or symbol that stands for the folder. Reply 2. This is confirmed by the explicit example of a representation of a folder in the ’635 application, illustrated in the portion of Figure 6D reproduced below (highlighted here for purposes of explanation). This portion of Figure 6D depicts representations of several folders, including the highlighted “Music” folder. The ’635 application specifically states: A folder content pane UI element 648d in navigation window UI element 646d is presented including representations of one or more data objects[11] at a location, identified in a path UI element 650d. A pointer UI element 652d illustrates a drag and drop operation of a “Music” folder represented in contents pane UI element 648d, dropped on edit window UI element 602d. Ex. 2004 ¶ 123 (emphasis added). The word “Music” in the above figure is a representation of a folder, not the folder itself. The actual folder is an entity in a file system that stores files (in the case of a “Music” folder, presumably MP3 or WAV files, or the like).” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“Patent Owner’s arguments are not pertinent to Petitioner’s proffered combination of Houston with Garcia as applied to the remaining challenged claims 17–21. As discussed further below, Petitioner relies on Garcia as supplementing Houston for details regarding the requirements of generating and sending an email with a link to a folder but without a file attachment, and for synchronizing folders and providing interfaces for display of shared folders. Pet. 26–27, 36–39, 57–60. For the challenged claims, Petitioner does not need to rely on the combination to modify Houston’s system such that, when an icon for a shared folder is created in Houston’s interface at an invited user’s client, the client does not store a file in the shared folder — 14 For this argument and others, Patent Owner cites for additional support portions of U.S. Provisional Patent Application No. 61/233,787. PO Resp. 18, 42, 46; Sur-Reply 9–12. This application is designated in Houston as a related application, and incorporated by reference therein. Ex. 1003, code (60), 1:6–10. We denied as untimely Patent Owner’s request to belatedly add this application to the record. Ex. 3002; Paper 39. Even accepting Patent Owner’s representations of the relied-on disclosures in that application, those disclosures are cumulative to Houston’s criticisms of systems that store documents remotely, and are irrelevant for the same reasons as discussed herein with respect to those Houston disclosures. that aspect of the Houston/Garcia combination is only relevant to claims 1–8, which have been disclaimed. Id. at 40–41; Ex. 2045.15 Thus, Patent Owner’s argument that Houston teaches away from combining with Garcia to delay storing a file when a folder is shared is not applicable to Petitioner’s challenges of claim 17–21, in light of our conclusion set forth above in Section III.C rejecting Patent Owner’s proposed construction of claim 17. The fact that the Houston system ensures the availability of synchronized local copies of files at each user’s local system and criticizes systems that store documents remotely, such as in Garcia, is irrelevant to those claims. On this record, there is nothing about that particular difference in the approaches of Houston and Garcia that would support a finding that one of ordinary skill in the art would have been discouraged from adopting Houston to take advantage of the teachings in Garcia regarding use of email and folder interfaces. In sum, Patent Owner focuses on a specific irrelevant detail of Houston regarding local storage of files, whereas Petitioner relies on other features of the combination of Houston and Garcia. In re Merck & Co., 800 F.2d 1091, 1097 (Fed. Cir. 1986); In re Keller, 642 F.2d 413, 425 (CCPA 1981). “The test for obviousness is not whether the features of a secondary reference may be bodily incorporated into the structure of the primary” slip op. at 41
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“To give substantial weight to objective indicia of nonobviousness such as commercial success, a proponent must establish a nexus between the evidence and the merits of the claimed invention. ClassCo, Inc. v. Apple, Inc., 838 F.3d 1214, 1220 (Fed. Cir. 2016). Nexus is a legally and factually sufficient connection between the objective evidence and the claimed invention, such that the objective evidence should be considered in determining nonobviousness. Demaco Corp. v. F. Von Langsdorff Licensing Ltd., 851 F.2d 1387, 1392 (Fed. Cir. 1988). “[T]here is no nexus unless the evidence presented is ‘reasonably commensurate with the scope of the claims.’” ClassCo, 838 F.3d at 1220 (quoting Rambus Inc. v. Rea, 731 F.3d 1248, 1257 (Fed. Cir. 2013)). A patentee is entitled to a presumption of nexus “when the patentee shows that the asserted objective evidence is tied to a specific product and that product ‘embodies the claimed features, and is coextensive with them.’” Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373 (Fed. Cir. 2019) (quoting Polaris Indus., Inc. v. Arctic Cat, Inc., 882 F.3d 1056, 1072 (Fed. Cir. 2018)). “[T]he patentee retains the burden of proving the degree to which evidence of secondary considerations tied to a product is attributable to a particular claimed invention.” Fox Factory, 944 F.3d at 1378. The Federal Circuit has held that “if the marketed product embodies the claimed features, and is coextensive with them, then a nexus is presumed and the burden shifts to the party asserting obviousness to present evidence to rebut the presumed nexus.” Brown & Williamson Tobacco Corp. v. Philip Morris Inc., 229 F.3d 1120, 1130 (Fed. Cir. 2000). “A finding that a presumption of nexus is inappropriate does not end the inquiry into secondary considerations”; rather, “the patent owner is still afforded an opportunity to prove nexus by showing that the evidence of secondary considerations is the ‘direct result of the unique characteristics of the claimed invention.’” Fox Factory, 994 F.3d at 1373–74 (quoting In re Huang, 100 F.3d 125, 140 (Fed. Cir. 1996)). “Ultimately, the fact finder must weigh the [objective indicia] evidence presented in the context of whether the claimed invention as a whole would have been obvious to a skilled artisan.” See Lectrosonics, Inc. v. Zaxcom, Inc., IPR2018-01129, Paper 33, 33 (PTAB Jan. 24, 2020) (precedential) (citing WBIP, LLC v. Kohler Co., 829 F.3d 1317, 1331–32 (Fed. Cir. 2016)).” slip op. at 23
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“However, as Petitioner argues above, Houston discloses that a client can provide an email to the server to invite others to share a folder, and Houston explains that “attaching files [to emails is] cumbersome for many computer users.” Pet. 25–26 (citing Ex. 1003, Fig. 4, 1:41–42, 3:40–43, 7:50–51). From this, Petitioner argues that it would have been obvious for the email invitation to notify how to access the folder, rather than sending the folder contents itself. Id. Petitioner further argues that the claim 17[d] requirement would have been obvious over the combination of Houston and Garcia given the disclosure in Garcia of sharing a folder by sending an email with a link to the folder, instead of an attachment. Id. at 27, 57 (citing Ex. 1004, Figs. 9, 11–12, 10:32–34, 10:38–40, 11:39–43, cl. 3). We are persuaded that the record supports Petitioner’s arguments regarding this claim requirement. Both Houston alone, and the combination of Houston and Garcia, teach or suggest sending an email with a link to a folder to be shared, rather than the folder contents. Only if the recipient clicks on the link are the contents of the folder shared. Ex. 1004, 11:29–31. The act of clicking on the link in the email after the email is received is the required “initiation of the communication” that must occur separately from the email itself, as required by claim 17[d]: “causing generation of at least one email [that] does not include a file attachment, for permitting avoidance of at least one file from being communicated to and stored at the second node until an initiation of the communication of the at least one file by a user of the second node is detected and the communication commences via at least one server that stores the at least one file” (emphasis added). It does not matter if Houston or Garcia automatically downloads local copies of files when a recipient clicks on the email link, because that is a separate step following the step of claim 17[d].” slip op. at 46
Patent outcomesUS 11,611,520 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,611,520 - PTAB · Jun 26, 2025 · IPR2025-00217 · APJ Jason W Melvin · IPR · Institution
The Board instituted inter partes review of claims 1–5, 10–15, and 20 on all four asserted § 103 grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“An inter partes review may not be instituted unless “the information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). For the reasons set forth below, we institute review.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“II. ANALYSIS A. LEVEL OF ORDINARY SKILL IN THE ART Petitioner asserts that ordinarily skilled artisans “would have a bachelor’s degree in electrical engineering, computer engineering, computer science, or equivalent training, and approximately two years of experience working in the field of wireless communication systems or design of similar communication systems.” Pet. 15. Petitioner’s proposed definition, which Patent Owner does not dispute, appears reasonable and consistent with the asserted prior art and the ’153 patent, and we adopt it here.” slip op. at 5
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“The parties’ dispute on this issue turns on claim construction. Petitioner’s approach requires we read “accumulation” as updating transmission power for each received TPC command. That is consistent with some aspects of the ’153 patent’s description. See Ex. 1001, 9:29–42 (“[S]tep is the magnitude of the amount added to an accumulator upon receipt of each TPC command. . . . [T]he transmit power PTx(k) may be updated each time a new TPC command is received.”). Patent Owner’s approach requires only that TPC commands cumulatively affect transmission power. That also appears consistent with the ’153 patent’s description. See id. at 9:35–36 (“The transmit power PTx(k) may be updated for every frame period.”). Based on those disclosures, it appears that the Specification supports Patent Owner’s broader construction. We need not resolve the “accumulation” claim-construction dispute at this stage, because Petitioner’s Zeira-based ground justifies institution, as discussed below. The parties should address the proper construction for “TPC command accumulation” in the instituted trial.” slip op. at 8
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“We do not agree with Patent Owner that the present record shows Andersson’s and Khan’s approaches couldn’t or wouldn’t be combined in the manner Petitioner asserts. Although shared-channel applications may have motivated Khan’s approach, it seems that scheduling grants applicable to a particular UE could be transmitted to that UE along with Andersson’s TPC commands. Thus, Patent Owner does not undermine Petitioner’s prior-art combination on the present record. The additional record developed through trial may ultimately support Patent Owner on this point, but at present, this argument does not justify denial of institution. Patent Owner additionally takes issue with Petitioner’s asserted benefits such as “allowing for a larger number of active wireless units,” reducing complexity, and reducing latency. Prelim. Resp. 38 (quoting Pet. 26–27). Those disputes raise potential factual issues that are best resolved through trial.” slip op. at 10
Claim construction§ 103 obviousnessPatents in suitUS 10,952,153 - 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 - 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 - Google, LLC. v. Escapex IP LLCInstitutedPTAB · May 28, 2025 · IPR2025-00337 · APJ Stacey G White · IPR · Institution
The Board instituted IPR on claims 1–24 based on five § 103 grounds involving Fuloria and Andler with additional references.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Under 35 U.S.C. § 314(a), an inter partes review may not be instituted unless the information presented in the petition “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” For the reasons stated below, we determine that Petitioner has established a reasonable likelihood that it would prevail with respect to at least one claim. We, therefore, grant Petitioner’s request to institute inter partes review of the challenged claims on the asserted grounds.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“According to Petitioner, a person of ordinary skill in the art would have had “a bachelor’s degree in computer science or a similar field and three years of professional computer programming experience, including experience with networked media and databases, where additional education can substitute for experience or vice versa.” Pet. 20 (citing Ex. 1002 ¶¶ 27– 31). The level of ordinary skill in the art is usually evidenced by the references themselves. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Petitioner’s description of a person of ordinary skill appears commensurate with the subject matter before us, and thus, we apply Petitioner’s definition for purposes of this Decision.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner states that “to the extent that [the term “engagement”] requires construction, it should be construed as ‘an indication that a user should be distinguished with respect to the content over another user.” Pet. 11 (citing Ex. 1001, 5:53–55; Ex. 1002 ¶ 41). Based on the record before us, we see no need for express construction of any term for the purposes of this Decision. Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’”).” slip op. at 9
- BurdenInstituted
“We are persuaded by Petitioner’s arguments and evidence. Fuloria teaches “a mechanism for user to promote social networking objects to other users.” Ex. 1004 ¶ 1. Fuloria displays a news feed containing social media content items. Id. at code (57), ¶¶ 6, 27. Users in Fuloria may like a piece of content or “for a given price” the user may turn their like into a “super-like.” Id. ¶ 37. “The ‘super-liked’ story is priced and directed toward users in a similar manner as a social ad. In particular embodiments, sponsored story system 304 may also add a weight to the story to alter its direction toward users.” Id. ¶ 39. Petitioner argues that “[t]his functionality represents uncapped engagement . . . because Fuloria places no limitation on how many times a user can super-like a piece of content.” Pet. 24–25. Dr. Bederson supports Petitioner by noting that Fuloria does not “place any limitation on how many credits a user can spend to increase the reach of the content.” Ex. 1002 ¶ 76. Further, Dr. Bederson states that “[m]ultiple different users can also promote the same content item. By allowing users to promote or ‘super-like’ content which also increases engagement with that content by other users, Fuloria’s system also facilitat[es] uncapped engagement with that content.” Id. ¶77. We find these arguments to be persuasive. The ’687 patent states that “[s]o long as the user has sufficient resources, the user may promote herself or others with uncapped (i.e., unlimited) engagements, which may facilitate getting noticed by other users, whether with respect to a social media content item.” Ex. 1001, 2:6–10. Similarly, Fuloria allows users to expend their resources and to have the super-like displayed according to the amount paid for the super-like. Ex. 1004 ¶ 57 (“In particular embodiments, the advertisement system adjusts the display of the ‘super-liked’ story based upon social factors as well as the real-world value of the credits paid.”); see also id. ¶ 38 (“[T]he social networking system may deduct the credits based on a cost per impression (CPM), effective cost per impression (eCPM), cost per click (CPC), or cost per action (CPA) pricing model”). Fuloria teaches likes from any number of users which is argued to disclose the multiple users recited in the claim. See Ex. 1002 ¶ 82 (discussing Fuloria’s display of engagement by a user and pointing out that Figure 9A shows 1,884 likes); see also id. ¶ 87 (“Fuloria teaches that ‘super-likes’ are available to users in general (and thus to first, second, third, etc. users).”). As to the number of engagements displayed by the first, second, and” slip op. at 16
Claim constructioncites PhillipsPatents in suitUS 10,474,687 - Google LLC v. Security First Innovations, LLCAll claims unpatentablePTAB · May 16, 2025 · IPR2024-00214 · APJ Stephen E Belisle · IPR · Final written decision
Claims 1–10 are unpatentable as obvious over Foster; the Board did not reach the instituted Orsini anticipation or obviousness grounds.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioner contends that a person of ordinary skill in the art, at the time of the invention of the ’609 patent, “would have had at least a bachelor’s degree in computer science, computer engineering, or a related field, with three years of experience in the area of securing data from unauthorized access or use,” and that “[a] higher level of education may substitute for less experience.” Pet. 5 (citing Ex. 1003 ¶¶ 37–38).” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (citing Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). slip op. at 12
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“Initially, we note that Petitioner’s challenge is based on the parties’ proposed district court constructions for “data set.” See Pet. 65–66. But neither party proposes a construction for “data chunks” in this proceeding. Notably, the 83-column Specification of the ’609 patent itself does not use the term “data chunks.” Even so, the meaning of “data chunks” is readily apparent from the plain language: the data chunks are generated “based on a data set,” and the claim defines the steps that comprise the chunk generation, including the relationship between the chunks and the data set. See Ex. 1001, 83:15–30; In re Hiniker Co., 150 F.3d 1362, 1369 (Fed. Cir. 1998) (In all aspects of claim construction, “the name of the game is the claim.” (quoting Giles Sutherland Rich, Extent of Protection and Interpretation of Claims–American Perspectives, 21 Int’l Rev. Indus. Prop. & Copyright L. 497, 499 (1990))).” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Petitioner argues, and we agree, that “it does not need to show that there was a known problem with the prior art system in order to articulate the required rational underpinning for the proposed [modification].” Unwired Planet, LLC v. Google Inc., 841 F.3d 995, 1002–03 (Fed. Cir. 2016) (cited in Pet. Reply 14–15). Petitioner persuasively explains: [C]ontent-owner storage would not negate benefits of content-service providers (“CSPs”) storing Foster-encrypted content. [The skilled artisan] knew CSPs (e.g., cable-TV companies) often purchased/licensed content from content owners and then securely stored it before delivering to recipients. [Ex. 1099], 84-94. CSPs typically and beneficially encrypted and stored that content for repeated use (e.g., downloads by different customers) – rather than repeatedly encrypting it on-the-fly – and for backup purposes. Petition, 77-78 (citing EX1045, EX1050, EX1059-EX1060; [Ex. 1003], ¶¶206-213); [Ex. 1111], ¶¶102-114 (citing EX1073, [0043] (VOD “pre-encrypt[s]” and “stores the content”); EX1097, 2:31-53 (“real-time encryption [for VOD] poses much greater cost and space issues”); EX1075, 1:51-67; EX1105, [0034]-[0037]; EX1080, 2-7). Pet. Reply 15; see id. at 16–17 (“EX1060, e.g., describes prior-art VOD systems where CSP intermediary ‘servers . . . store all movies.’” (citing Ex. 1060 ¶¶ 7–8 (cited in Pet. 77)) (alteration in original)). As for Patent Owner’s allegation that Petitioner’s proposed modification to Foster would “compromise” Foster’s security, Petitioner argues, and we agree, that, “[b]eyond a conclusory expert declaration, [Patent Owner] offers no evidence that hacking risks or overall storage requirements would increase by storing content at a CSP/intermediary rather than a content owner.” Pet. Reply 17. Petitioner also argues, and we agree, “even if it required ‘increased cost and complexity’ to make CSP storage more secure, that does ‘not show that [the technique] was unknown or could not have practical applications,’ and thus does not support non-obviousness.” Id. at 17–18 (quoting In re Cree, 818 F.3d 694, 700–701 (Fed. Cir. 2016)); id. at 18 (“[I]t is a commonplace fact that design decisions entail making tradeoffs among multiple objectives.” (quoting Corephotonics, Ltd. v. Apple Inc., 2021 WL 4944471, at *6 (Fed. Cir. Oct. 25, 2021)); see Allied Erecting and Dismantling Co. v. Genesis Attachments, LLC, 825 F.3d 1373, 1381 (Fed. Cir. 2016) (“[A] given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine [or to modify].”). Although Patent Owner disputes whether a rational reason exists to modify Foster to arrive at the subject limitation (discussed above), Patent Owner otherwise does not dispute reasonable expectation of success in doing so. See generally PO Resp. 32–56.” slip op. at 25
Patent outcomesUS 11,068,609 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,068,609
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.