- Cisco Systems, Inc. v. Portsmouth Network Corp.Some claims unpatentablePTAB · Aug 4, 2025 · IPR2024-00505 · APJ Justin T Arbes · IPR · Final written decision
Claims 1, 2, 4–7, 9, 10, 13, 14, 16–19, 21, and 22 are unpatentable as obvious over Gai under theory 1B; claims 11, 12, 23, and 24 were not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“patent, we look to “1) the types of problems encountered in the art; 2) the prior art solutions to those problems; 3) the rapidity with which innovations are made; 4) the sophistication of the technology; and 5) the educational level of active workers in the field.” Ruiz v. A.B. Chance Co., 234 F.3d 654, 666–67 (Fed. Cir. 2000). “Not all such factors may be present in every case, and one or more of them may predominate.” Id. at 667.” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningOther
“The most common type of MAC bridge is a switch, which has multiple ports connecting it to LANs, other switches, host computing systems, or other network elements. Switches can be roughly classified as access switches or core switches. An access switch has ports that connect to LANs and/or to other network endpoints, such as user computer systems. Core switches interconnect the access switches into a Wide Area Network (WAN), by direct connection between the core switch and access switches and/or by connection to other core switches. Core switches that are directly connected to access switches are referred to herein as edge switches. Ex. 1001, col. 1, ll. 27–38. Both parties refer to this disclosure when arguing whether particular switches in the asserted prior art (Gai) qualify as an “access switch” or “edge switch.” See Pet. 5, 22, 27–28 (“edge switches are ‘[c]ore switches that are directly connected to access switches’”), 71; PO Resp. 31–32 (“The ’986 patent discloses that ‘[a]n access switch has ports that connect to LANs and/or to other network endpoints.’ . . . The ’986 patent also discloses that edge switches are ‘[c]ore switches that are directly connected to access switches.’”); Reply 20, 22. Dr. Houh and Dr. Olivier do so as well. See Ex. 1003 ¶¶ 39, 66–67, 82–83, 166, 171, 193; Ex. 2001 ¶ 80. Based on the full trial record, we agree and conclude that the descriptions of “access switch” and “edge switch” in the ’986 patent reflect what was understood to be the plain and ordinary meanings of these terms at the time of the invention. Accordingly, we interpret “access switch” to mean a switch with ports that connect to LANs and/or to other network endpoints, such as user computer systems, and interpret “edge switch” to mean a core switch that is directly connected to an access switch.” slip op. at 12
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“and conclude that Petitioner has not shown sufficiently that a person of ordinary skill in the art would have been motivated to designate switch 117 as the root switch when implementing the network reconfiguration method of Gai. The only mention of an access switch connected to port 7 of switch 114 is at column 13, lines 59–63 of Gai. While that sentence establishes that such an access switch may exist in the network, it does not state or imply that it would be the root switch. Instead, when discussing the operation of the Figure 1 network, Gai only identifies switches 120 and 121 as the root switch. See Ex. 1005, col. 10, ll. 37–41, col. 11, ll. 60–64, col. 14, ll. 16–20, col. 15, ll. 27–29, 38–51, col. 16, ll. 42–45. To be sure, Gai does disclose that “execution of the spanning tree algorithm causes the switches to elect a single switch, among all the switches within each network, to be the ‘root’ switch,” where “[e]ach switch has a unique numerical identifier (switch ID) and the root is the switch having the lowest switch ID numeric value,” such that an access switch can be the root switch if it has the lowest switch ID. See Ex. 1005, col. 2, ll. 42–47, col. 10, ll. 29–36. As Patent Owner and Dr. Olivier explain in detail, though, Gai expressly cautions against doing so. Gai discloses that [d]epending on the configuration of a given network, the location of the root can significantly affect the distance that messages must travel. For example, many networks include a plurality of switches designated as access switches that provide connectivity to LANs, end stations, etc., and a plurality of backbone switches that, in turn, interconnect the various access switches. If the root is located at an access switch and the principal server utilized by the end stations (i.e., clients) is coupled to a backbone switch, the average distance between end stations and the primary server may be quite high, resulting in inefficient network operation. In addition, the backbone switches may become partitioned as ports between them are blocked. Id. at col. 3, ll. 17–29; see also id. at col. 10, ll. 26–29 (the “location of the root may affect the average distance (i.e., the average number of hops) a message travels and/or cause undesirable partitioning of backbone switches”). Thus, the location of the root is not an unimportant consideration—it affects the distance messages must travel and can cause backbone switches to be partitioned. See id. Gai, therefore, discloses that “[t]o reduce the average distance and avoid partitioning of the backbone switches, it is desirable to locate the root at a backbone switch.”10 Id. at col. 3, ll. 29–31 (emphasis added). Switch 117 in Petitioner’s modified Figure 1 is an access switch, not a backbone switch. See id. at col. 6, ll. 10–12 (“Access switches are preferably coupled to entities (e.g., LANs, end stations, etc.) whereas backbone switches provide the interconnections between access switches.”).” slip op. at 44
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed
“We agree with Petitioner. For purposes of claim 1, which does not recite “downstream” communication of dummy traffic (unlike claims 11, 12, 23, and 24), the only modification to Figure 1 is the addition of switch 117 and server 112e—otherwise, in Petitioner’s analysis, Gai’s method operates exactly as described when a failure occurs at root port 3 of switch 114. See Pet. 69–73, 81–85; Tr. 47:20–48:2. That modification is expressly supported by Gai, which discloses the following: Rapid reconfiguration entity 234 similarly generates one or more separate multicast messages 400 for each remaining entity directly coupled to access switch 114 (i.e., entities or end stations on LANs 102–104). In each message 400, entity 234 loads SA field 414 with the address of the corresponding entity. Each of these messages are similarly forwarded by access switch 114 through the new forwarding port (i.e., port number four). In addition, entity 234 generates and transmits one or more multicast messages 400 for entities reachable through switch 114 on ports other than its root port. For example, if port number seven at switch 114 were coupled to another access switch, entity 234 would transmit multicast messages 400 carrying the source address of entities directly coupled to this additional access switch as well. Thus, at least one multicast message 400 is generated and transmitted for each entity directly coupled to or downstream of access switch 114 (relative to the root). As set forth above, upon receipt of these multicast messages 400, the other devices within network 100 update their corresponding filtering databases with the new destination ports, as necessary. Ex. 1005, col. 13, l. 50–col. 14, l. 3 (emphasis added). Gai thus expressly contemplates the addition of “another access switch” coupled to port 7 of switch 114. Switch 117 in the modified Figure 1 is such a switch. See PO Resp. 30 (Patent Owner arguing that “a [person of ordinary skill in the art] would understand that switch 117 is an access switch”); Ex. 1018, 84:14–85:9 (Dr. Olivier agreeing that switch 117 is an “access switch”). And because an “access switch” has “ports that connect to LANs and/or to other network endpoints, such as user computer systems,” and the above disclosure mentions “entities directly coupled to th[e] additional access switch,” switch 117 would be directly connected to a device like server 112e as well. See Ex. 1001, col. 1, ll. 31–33; Ex. 1005, col. 13, ll. 59–63; supra Section II.B. We credit Dr. Houh’s testimony that Gai in its written description expressly discloses the particular “variation of the topology” of Figure 1 that Petitioner asserts. See Ex. 1003 ¶ 165. Third, Patent Owner argues that Petitioner has not established that a person of ordinary skill in the art “would have had a reasonable expectation of success in modifying Gai to meet the claims.” PO Resp. 14–16 (citing Ex. 2001 ¶¶ 47–49). Patent Owner’s arguments are primarily directed to Petitioner’s asserted modification for its “1A” theory. See id. To the extent Patent Owner’s arguments apply to claim 1 and “1B,” we disagree, as Gai expressly describes the asserted modification to Figure 1 (i.e., adding an access switch connected to port 7 of switch 114). Thus, we are persuaded that a person of ordinary skill in the art would have had a reasonable expectation of success in achieving the method of claim 1 based on Gai’s full disclosure.” slip op. at 33
Patent outcomesUS 6,917,986 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,917,986 - PTAB · Jul 22, 2025 · IPR2025-00255 · APJ Charles J Boudreau · IPR · Institution
The Board instituted IPR on claims 1–27 and all petition grounds, finding a reasonable likelihood that claims 1, 23, and 27 are obvious over Wilcox, Londergan, Raskin, and Wu.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“c) Summary For the reasons discussed above, Petitioner has made sufficient showings at this stage of the proceeding that the Wilcox-Londergan-Raskin- Wu combination teaches or suggests every limitation in claims 1, 23, and 27 of the ’139 patent, that one of ordinary skill in the art would have had reason to combine those teachings and suggestions to arrive at the inventions recited in claims 1, 23, and 27, and that one of ordinary skill in the art would have had a reasonable expectation of success. Accordingly, Petitioner has demonstrated a reasonable likelihood of prevailing on its challenges to claims 1, 23, and 27 based on the combination of Wilcox, Londergan, Raskin, and Wu. Accordingly, institution of an inter partes review is appropriate under 35 U.S.C. § 314(a).” slip op. at 33
- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner does not comment on Petitioner’s formulation or offer any competing formulation in its Preliminary Response. See generally Prelim. Resp. Mr. Haeberli, however, testifies as follows in his Declaration: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Dr. Terveen has provided its own definition . . . . 31. I believe Dr. Terveen’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. We find Mr. Haeberli’s formulation to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent, and, accordingly, we adopt and apply that definition for purposes of this Decision. B.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther
“missing in the prior art. Prelim. Resp. 29–34. Limitations [1.4], [23.5], and [27.4] each recite: “wherein the first and second partial search strings are separated by a string separator character in the first search field.” Ex. 1001, 29:47–49, 31:33–35, 32:29–31. Petitioner asserts that both of the Lotus Notes references teach receiving a first search string and a second search string in a single search field, separated by “a string separator character (e.g., a Boolean AND operator and/or a comma).” Pet. 25–26 (footnote omitted). We are not fully persuaded by Petitioner’s argument. In particular, the evidence does not support Petitioner’s argument that a Boolean operator such as “AND” is a string separator character. Patent Owner has pointed to intrinsic and extrinsic evidence demonstrating that a string separator character consists of just one character.17 Consequently, based on the 17 As Patent Owner argues, the intrinsic evidence does not support this interpretation of the claim language. Prelim. Resp. 31–32. “First, the ’139 patent distinguishes between string separator characters (such as space, comma, etc.) and ‘modifiers’ (such as AND, OR, NOT, etc.).” Id. at 31; compare Ex. 1001, 30:19–22 (claim 6, “string separator character”), with id. at 31:22–26 (claim 22, Boolean “modifiers”). Moreover, Patent Owner persuasively argues that “a POSITA would not understand Boolean operators such as ‘AND’ to function as string separator characters” and “would have known that the operator AND is a search syntax instruction rather than a string separator.” Prelim. Resp. 31 (citing Ex. 1059, 162; Ex. 2001 ¶ 110). Even Petitioner acknowledges in a footnote that it may not be appropriate to include the Boolean AND operator in the definition of “string separator character.” Petitioner argues:” slip op. at 28
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundInstituted
“one of ordinary skill in the art would have considered “reverting some of the changes that had been made to Lotus Notes R5’s ‘Search Builder’ to make it more similar to Lotus Notes earlier 3.0’s ‘Query Builder.’” Prelim. Resp. 16. The issue, however, is not whether “over the years Lotus Notes moved away from a unified search field[,]” as Patent Owner suggests. Id. at 14. The issue is what “inferences and creative steps” a person of ordinary skill in the art would have employed, based on Wilcox and Londergan, when designing a new method and system for search indexing. KSR, 550 U.S. at 418. Petitioner’s argument is that one of ordinary skill in the art would have been motivated to consider Wilcox and Londergan together in order to “obtain a more complete and comprehensive understanding of the Lotus Notes system,” which in turn would have inspired certain inferences and creative steps that would have resulted in the portions of the claimed invention allegedly disclosed in Wilcox and/or Londergan. Pet. 22. We do not agree with Patent Owner that this argument can only be the result of improper hindsight bias. See Prelim. Resp. 16–17. At this stage of the proceedings and based on the current record, we determine that Petitioner has sufficiently shown that a POSITA would have been motivated to combine Wilcox and Londergan.” slip op. at 20
Claim construction§ 103 obviousnesscites Phillips · KSRPatents in suitUS 9,633,139 - PTAB · Jul 22, 2025 · IPR2025-00254 · APJ Lisa A Murray · IPR · Institution
The Board instituted IPR on claims 1–20 and all asserted grounds, finding a reasonable likelihood that claims 1–20 are unpatentable under § 103(a).
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We may institute an inter partes review when “the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2018). If we institute an inter partes review, the trial must encompass all claims and grounds identified in the Petition. 37 C.F.R. § 42.108(a) (2025) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”). For the reasons set forth below, we conclude that there is a reasonable likelihood that Petitioner will prevail in establishing the unpatentability of all challenged claims. We, therefore, institute an inter partes review of claims 1–20 on the grounds asserted in the Petition. B.” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner does not comment on Petitioner’s formulation or offer any competing formulation in its Preliminary Response. See generally Prelim. Resp. Mr. Haeberli, however, testifies as follows in his Declaration: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. We find Mr. Haeberli’s formulation to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’490 patent, and, accordingly, we adopt and apply that definition for purposes of this Decision. B.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“art. Prelim. Resp. 30–34. Limitation [1.10] reads, “wherein the first and second partial search strings are separated by a string separator character in the first search field.” Ex. 1001, 30:8–10. Petitioner asserts that both of the Lotus Notes references teach receiving a first search string and a second search string in a single search field, separated by “a string separator character (e.g., a comma and/or a Boolean AND operator).” Pet. 23–24 (footnote omitted). We are not fully persuaded by Petitioner’s argument. In particular, the evidence does not support Petitioner’s argument that a Boolean operator such as “AND” is a string separator character. Patent Owner has pointed to intrinsic and extrinsic evidence demonstrating that a string separator character consists of just one character.16 Consequently, based on the current record, for the purposes of this Decision we preliminarily construe the term “string separator character” to mean “a single-character string separator.” The parties are invited to address the appropriateness of this construction in future briefing. If Boolean modifiers are excluded from the definition of a “string separator character,” then the Londergan Search Bar and Search Builder features, which accept only Boolean operators, do not teach or suggest 16 As Patent Owner argues, the intrinsic evidence does not support this interpretation of the claim language. Prelim. Resp. 31–32. “First, the ’490 patent distinguishes between string separator characters (such as space, comma, etc.) and ‘modifiers’ (such as AND, OR, NOT, etc.).” Id. at 32; compare Ex. 1001, 31:14–17 (claim 12, “string separator character”), with id. at 32:19–23 (claim 20, Boolean “modifiers”). Moreover, Patent Owner persuasively argues that “a POSITA would not understand Boolean operators such as ‘AND’ to function as string separator characters” and “would have known that the operator AND is a search syntax instruction rather than a string separator.” Prelim. Resp. 32 (citing Ex. 1059, 162; Ex. 2001 ¶ 110). Even Petitioner acknowledges in a footnote that it may not be appropriate to include the Boolean AND operator in the definition of “string separator character.” Petitioner argues: To the extent Patent Owner argues the Boolean AND operator is not a string separator character (which Petitioner does not acquiesce is appropriate), it would have been obvious to a POSITA when implementing Raskin’s teachings to perform the search incrementally to use a single-character string separator character, such as a plus sign, as was known in the art (e.g., EX1057, 60, 109, 129, 151), or a comma, as described by the Lotus Notes references (EX1059, 159-165), at least because a POSITA knew that a goal of the incremental search is to minimize the number of characters the user has to enter before obtaining the desired search results. Pet. 24 n.7. limitation [1.10].17 See Ex. 1061, 140–42. The Wilcox Search Bar similarly is limited to strings separated by a Boolean operator. See Ex. 1059, 160–62. The Wilcox Query Builder, however, does teach multiple search strings separated by a string separator character, specifically a comma. Id. at 163 (“If you want to search for documents that contain all of several words, type them in this box, separated by commas.”). Thus, while we do not accept all of Petitioner’s reasoning, there is evidence to support Petitioner’s overall argument that the proposed combination discloses multiple search strings separated by a string separator character, as we have preliminarily construed the term.” slip op. at 28
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“extreme technical difficulties with even using incremental searches.” Prelim. Resp. 21, 25 (citing Ex. 1021, 126). Patent Owner argues that “[a] POSITA is not motivated to undertake a modification of the prior art with something that the art teaches would be difficult or impossible to do.” Id. at 21 (citing Natera, Inc. v. NeoGenomics Labs., Inc., 106 F.4th 1369, 1377–78 (Fed. Cir. 2024)). We do not interpret Raskin in this manner. Patent Owner points to a passage in Raskin stating, “almost all interface-building tools make it easy to implement delimited searches and difficult or impossible to implement incremental searches.” Ex. 1021, 126. There is a difference, however, between “difficult to implement” and “difficult to use.” For the end-user, Raskin concludes that “[f]rom the point of view of interface engineering, the advantages of incremental searching are so numerous and the advantages of delimited searches so few that I can see almost no occasions when a delimited search would be preferred.” Id. at 126 & n.7 (“A search is either incremental or excremental.”). It is reasonable to conclude that one of ordinary skill would have been motivated to choose a search method that offered numerous advantages to end-users. Finally, Patent Owner argues that “Raskin’s entire philosophy to user interfaces was incompatible with Lotus Notes.” Prelim. Resp. 22–25. According to Patent Owner, “Lotus Notes is all about centralized collaboration around documents, files, and file structures[,]” while Raskin “goes in a completely different direction, espousing the elimination of filenames and ‘hierarchical file structures’ including directories and folders.” Id. at 23 (citing Ex. 1021, 119). Patent Owner claims that modifying the Lotus Notes references with Raskin would “effectively render[] Lotus Notes’ functionality of hierarchical viewing of and responding to documents unusable.” Id. Petitioner, however, does not propose to incorporate Raskin’s views on hierarchical file structures into the combination of Wilcox and Londergan. It is not necessary for the entirety of Raskin’s teachings to be physically compatible with the Lotus Notes systems described in Wilcox and Londergan. Orthopedic Equip., 702 F.2d at 1013 (“Claims may be obvious in view of a combination of references, even if the features of one reference cannot be substituted physically into the structure of the other reference.”); In re Sneed, 710 F.2d at 1550. Raskin is cited for one purpose: its teachings regarding incremental search. On the current record, we find Petitioner has demonstrated that one of ordinary skill would have been motivated to modify the combination of Lotus Notes references according to those teachings in Raskin. slip op. at 23
Claim construction§ 103 obviousnesscites PhillipsPatents in suitUS 10,552,490 - PTAB · Jul 22, 2025 · IPR2025-00253 · APJ Scott C Moore · IPR · Institution
The Board instituted IPR on claims 1–10 and all petitioned grounds, finding a reasonable likelihood that claims 1 and 10 are obvious over Wilcox, Londergan, Raskin, and Wu.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We may institute an inter partes review when “the information presented in the petition . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2018). If we institute an inter partes review, the trial must encompass all claims and grounds identified in the Petition. 37 C.F.R. § 42.108(a) (2025) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2
- Skill levelSkill level patent owner adoptedDecided for patent owner
“Patent Owner does not comment on Petitioner’s formulation or offer any competing formulation in its Preliminary Response. See generally Prelim. Resp. Mr. Haeberli, however, testifies as follows in his Declaration: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Petitioner has provided its own definition . . . . 31. I believe Petitioner’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. We find Mr. Haeberli’s formulation to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’035 patent, and, accordingly, we adopt and apply that definition for purposes of this Decision. B.” slip op. at 8
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“in the prior art. Prelim. Resp. 30–34. Limitations [1.4] and [10.4] both recite: “wherein the first and second strings are separated by a string separator character in the first search field.” Ex. 1001, 29:44–46, 30:41–43. Petitioner asserts that both of the Lotus Notes references teach receiving a first search string and a second search string in a single search field, separated by “a string separator character (e.g., a comma and/or a Boolean AND operator).” Pet. 26–27 (footnote omitted). We are not fully persuaded by Petitioner’s argument. In particular, the evidence does not support Petitioner’s argument that a Boolean operator such as “AND” is a string separator character. Patent Owner has pointed to intrinsic and extrinsic evidence demonstrating that a string separator character consists of just one character.17 Consequently, based on the current record, for the purposes of 17 As Patent Owner argues, the intrinsic evidence does not support this interpretation of the claim language. Prelim. Resp. 31–32. “First, the ’035 patent distinguishes between string separator characters (such as space, comma, etc.) and ‘modifiers’ (such as AND, OR, NOT, etc.).” Id. at 31 (citing Ex. 1001, 8:45–59, 22:34–46). Moreover, Patent Owner persuasively argues that “a POSITA would not have understood Boolean operators like AND to be a string separator as used in the claims” and “would have known that the operator AND is a search syntax instruction rather than a string separator.” Prelim. Resp. 31 (citing Ex. 1059, 162; Ex. 2001 ¶ 109). Even Petitioner acknowledges in a footnote that it may not be appropriate to include the Boolean AND operator in the definition of “string separator character.” Petitioner argues: To the extent Patent Owner argues the Boolean AND operator is not a string separator character (which Petitioner does not acquiesce is appropriate), it would have been obvious to a POSITA when implementing Raskin’s teachings to perform the this Decision we preliminarily construe the term “string separator character” to mean “a single-character string separator.” The parties are invited to address the appropriateness of this construction in future briefing.” slip op. at 28
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“based on the fact that all three references “generally relate to searching.” See Prelim. Resp. 20. The fact that Raskin does not explicitly discuss searching across multiple files does not mean that there would be no motivation to combine Raskin with the Lotus Notes references. Although a conclusion of obviousness must be supported by findings and analysis establishing a reason to combine or modify the known elements in the manner proposed, the analysis “need not seek out precise teachings directed to the specific subject matter of the challenged claim, [but] can take account of the inferences and creative steps that a person of ordinary skill in the art would employ.” KSR, 550 U.S. at 418. We conclude on the current record that Petitioner’s rationale for combining Raskin with the Lotus Notes references is not over-broad.” slip op. at 22
Claim construction§ 103 obviousnesscites PhillipsPatents in suitUS 7,370,035 - 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 - Qualcomm Incorporated v. Network System Technologies, LLCAll claims unpatentablePTAB · Jun 13, 2025 · IPR2024-00343 · APJ Charles J Boudreau · IPR · Final written decision
Claims 1–7 are unpatentable as obvious over Rădulescu2004 and OCP; the Board did not reach the Weber-based grounds.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“include (1) the educational level of the inventor; (2) the type of problems encountered in the art; (3) prior-art solutions to those problems; (4) the rapidity with which innovations are made; (5) the sophistication of the technology; and (6) the educational level of workers active in the field. Envtl. Designs, Ltd. v. Union Oil Co., 713 F.2d 693, 696–97 (Fed. Cir. 1983). Not all factors may exist in every case, and one or more of these or other factors may predominate in a particular case. Id. These factors are not exhaustive, but merely a guide to determining the level of ordinary skill in the art. Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). Moreover, the prior art itself may reflect an appropriate skill level. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 13
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesDecided for petitioner
“35 U.S.C. § 112 ¶ 6 (2006). “[T]he use of the word ‘means’ in a claim element creates a rebuttable presumption that § 112, para. 6 applies.” Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1348 (Fed. Cir. 2015) (en banc in relevant part); Personalized Media Commc’ns, LLC v. Int’l Trade Comm’n, 161 F.3d 696, 703–04 (Fed. Cir. 1998). “[This] presumption may be rebutted if the properly construed claim limitation itself recites sufficiently definite structure to perform the claimed function.” Kemco Sales, Inc. v. Control Papers Co., 208 F.3d 1352, 1361 (Fed. Cir. 2000).” slip op. at 16
- Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Term construed patent owner constructionDecided for patent owner
“Ex. 1001, 4:46–50. This passage indicates that the interconnect can be a network on a chip and the network on a chip can include wires and buses. That does not necessarily mean that the interconnect can be just wires or buses; rather, it discloses that the interconnect can include wires and buses. In context, the disclosure regarding wires and buses does not support construing the corresponding structure broadly enough to encompass just wires and buses. The networks that constitute the corresponding structure, however, could include networks with wires and buses. Therefore, we agree with Patent Owner that the corresponding structure for the interconnect means should not include a mere bus, switch, and point-to-point wire and instead find that the corresponding structure under 35 U.S.C. § 112 ¶ 6 is a network, which the ’052 patent describes as a multi-hop interconnection between modules separated by one or more network nodes. See Ex. 1001, 2:33–37. Because this structure corresponds to the construction of “interconnect means” proposed by Patent Owner and adopted by the district courts in the TI and Qualcomm litigations (see supra Section III.C.3.b), and we do not rely in our analysis below on a recourse to “equivalents thereto” as permitted by § 112 ¶ 6, we note that our ultimate conclusions on the unpatentability of the challenged claims would be the same if § 112 ¶ 6 did not apply. iii. Conclusion For the reasons stated above, we construe “interconnect means” to cover the structure described in the Specification corresponding to the specified functions of “coupling said plurality of processing modules (M, S)” in the context of claim 6 and “coupling said plurality of processing modules (M, S)” and “enabling a connection-based communication having a set of connection properties” in the context of claims 1 and 7—i.e., a “multi-hop interconnection between modules separated by one or more network nodes”—and equivalents thereof.” slip op. at 28
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“standard as would be used by a district court to construe a claim in a civil action involving the validity or infringement of a patent. 37 C.F.R. § 42.100(b). Under that standard, claim terms are given their ordinary and customary meaning, as would have been understood by a person of ordinary skill in the art at the time of the invention, in light of the language of the claims, the specification, and the prosecution history of record. Id.; Phillips v. AWH Corp., 415 F.3d 1303, 1312–19 (Fed. Cir. 2005) (en banc); Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365–66 (Fed. Cir. 2012). “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) (quoting Vivid Techs., Inc. v. Am. Sci. Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 15
Patent outcomesUS 7,594,052 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,594,052 - 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 - Google LLC v. Security First Innovations, LLCAll claims unpatentablePTAB · May 16, 2025 · IPR2024-00215 · APJ Jason M Repko · IPR · Final written decision
Claims 1–10 are unpatentable as obvious over Foster and Hayhurst; the Board did not reach the anticipation and obviousness grounds based on Orsini.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“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.” Pet. 6 (citing Ex. 1003 ¶¶ 37–38). Petitioner also asserts that a “higher level of education may substitute for less experience.” Id. 2 Available at https://www.uspto.gov/TrialPracticeGuideConsolidated. Patent Owner submitted the Declaration of Dr. Rubin in support of its Response, and in that Declaration, Dr. Rubin accepted Petitioner’s definition. Ex. 2033 ¶¶ 20–21. For the reasons given, we apply the same level of ordinary skill in the art that we did in the Institution Decision. Inst. Dec. 4.” slip op. at 6
- Expert testimonyPetitioner expert creditedPatent owner expert discountedMixed
“See Section II.C.3.a.ii supra. Although Dr. Rubin calls Hayhurst’s security benefits “ancillary” (Ex. 2033 ¶¶ 108–109, quoted in PO Resp. 40), this does not align with Hayhurst (see Ex. 1007 ¶¶ 2, 7, 8, 21). For example, Hayhurst describes the security measures in the Technical Field section (id. ¶ 2) and the Summary of the Invention section (id. ¶¶ 7, 8). Hayhurst also discusses piracy deterrence in both the Summary of the Invention section (id. ¶ 8) and the invention’s detailed description (id. ¶ 21). Because Dr. Rubin does not give sufficient weight to Hayhurst’s discussion of piracy deterrence and security, we do not credit Dr. Rubin’s testimony on this issue. See Ex. 2033 ¶¶ 108–109. Thus, we agree with Petitioner that Hayhurst is reasonably pertinent to the network-security problem that the inventors were trying to solve. See Reply 5–6.” slip op. at 15
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction needed
“Neither party explicitly proposed constructions during trial, and we do not see the need for construing any terms in this Decision.” slip op. at 8
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“3. Claim 1 a. Analogous Art “To be considered within the prior art for purposes of the obviousness analysis, a reference must be analogous.” Circuit Check Inc. v. QXQ Inc., 795 F.3d 1331, 1335 (Fed. Cir. 2015) (citing Wang Lab. v. Toshiba Corp., 993 F.2d 858, 864 (Fed. Cir. 1993)). “Two separate tests define the scope of analogous prior art: (1) whether the art is from the same field of endeavor, regardless of the problem addressed and, (2) if the reference is not within the pertinent to the particular problem with which the inventor is involved.” Sanofi-Aventis Deutschland Gmbh v. Mylan Pharms. Inc., 66 F.4th 1373, 1377 (Fed. Cir. 2023) (quoting In re Bigio, 381 F.3d 1320, 1325 (Fed. Cir. 2004) (citations omitted)).” slip op. at 9
Patent outcomesUS 10,452,854 unpatentableClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 10,452,854
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.