• Cisco Systems, Inc. v. Portsmouth Network Corp.No claims unpatentable
  PTAB · Mar 31, 2026 · IPR2024-01450 · APJ Peter D Shapiro · IPR · Final written decision

  Claims 1–4, 6–11, and 13–20 were not shown unpatentable because Dziong and Sathyanath do not teach the claimed sharing definition for existing connections with allocated bandwidth.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “First, the claims use present-tense language, “one or more other connections, which have respective bandwidths and which are permitted to share a bandwidth allocation with the new connection.”3 Ex. 1001, claim 1 (emphasis added). The exclusive use of the present tense have indicates “other connections” must have current possession of the bandwidth. For these other connections to share bandwidth with a newly established connection, they must already exist and have bandwidth ready for immediate use, rather than merely holding a dormant “reservation” pending a network failure. See PO Supp. Br. 1. The Federal Circuit addressed a similar situation where the Court found the present-tense limitation “is connected to the computer network” means a device was required to be connected at the” slip op. at 15

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “combination, do not teach or suggest limitations 1.2 and 1.3 requiring: providing a sharing definition specifying one or more other connections, which have respective bandwidths and which are permitted to share a bandwidth allocation with the new connection, such that a total bandwidth allocated jointly to the new connection and to the other connections in any given segment is equal to a maximum of the requested bandwidth and of the bandwidths of the other connections in the given segment Ex. 1001, limitations 1.2, 1.3 (emphasis added); see PO Resp. 17–22; Sur-reply 4–5, 12–14. As discussed above in Section II.C.2, we interpret “other connections” to mean “existing connections in the network that already have bandwidth allocated to them.” Because the information shared in Dziong and Sathyanath, described below, relates to reserved protection paths, rather than existing connections that have bandwidth that can currently transmit network traffic, the references do not teach or suggest the “other connections” part of the sharing definition in limitations 1.2 and 1.3. Dziong describes advertising, across the network, the amount of bandwidth reserved for recovery on each link that would be activated when a protected link fails. See, e.g., Ex. 1005 ¶ 60; Pet. 36. Once activated, network traffic from a “primary path” failure is rerouted to these recovery paths. See Ex. 1005 ¶¶ 7–9, 70, 83. Petitioner points to this advertising of the reserved bandwidth information as teaching the claimed “sharing definition.” Pet. 33–36 (arguing that the “protection paths [in Dziong] have bandwidth reservations” and “share an overall protection bandwidth reservation”); Reply 21–23. However, since the advertised information only contains information about the recovery paths “that would be activated” upon a primary path failure, such paths are not existing connections that already have bandwidth allocated to them, and therefore do not teach the claimed “other connections” that are part of the sharing definition. See, e.g., Ex. 1005 ¶ 60.” slip op. at 43

  Patent outcomesUS 7,596,088 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,596,088
• Cisco Systems, Inc. v. Portsmouth Network Corp.No claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00503 · APJ Charles J Boudreau · IPR · Final written decision

  Claims 1–18 were not shown unpatentable because the asserted obviousness combinations did not cure the failure to show the claimed request and routing steps.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art in the field of the ’279 patent in January 2001 “would have had a working knowledge of the network communication technologies that are pertinent to the ’279 patent, including network flow allocation in a ring topology.” Pet. 12. More specifically, Petitioner argues, a person of ordinary skill in the art “would have had a master’s degree in computer science, computer engineering, or an equivalent, and two years of professional experience relating to network communications and resource allocations,” where “[a]dditional work experience can substitute for specific educational background, and vice versa.” Id. (citing Ex. 1003 ¶ 20). Patent Owner represents that it “does not dispute Petitioner’s definition” for the purposes of its Response. PO Resp. 5. We find Petitioner’s proposal is consistent with the evidence of record, including the asserted prior art and the ’279 patent, and, therefore, we likewise adopt Petitioner’s proposed definition of the level of ordinary skill in the art for purposes of this Decision.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached

    “Neither party contends that any formal claim construction is necessary. See Pet. 12 (“Petitioner submits that, for the purposes of this proceeding and the grounds presented herein, no claim term requires express construction.”); PO Resp. 4 (“Here, at this stage in the proceeding, Patent Owner will apply the ordinary and customary meaning to the ’279 Patent’s claim terms.”). Patent Owner notes, however, that Petitioner had asserted specific constructions in the Cisco litigation for the term “predetermined,” as recited in claims 1, 10, 14–16, and 18, and for the term “quantum.” PO Resp. 4. Specifically, according to Patent Owner, Petitioner proposed that “predetermined” be construed as “determined before the data flow request” and that “quantum” be construed as “an amount of a requested resource by which to increase or decrease.” Id. (citing Ex. 2007). Patent Owner contends asserted prior art combinations disclose or render obvious the challenged claims under these constructions. Id. Because our conclusion that Petitioner has not demonstrated that any of the challenged claims are unpatentable does not turn on the construction of either “predetermined” or “quantum,” there is no need for us to construe those terms. See Realtime Data, 912 F.3d at 1375.” slip op. at 12

  • Strike new argumentNew argument disregardedDecided for patent owner

    “We again are not persuaded by Petitioner’s argument. As an initial matter, we find no argument with respect to “best effort data traffic” or dropped packets in the Petition. See Tr. 12:10–21 (conceding that “the phrase ‘best effort’ was not in the Petition” but arguing that it was raised in response to the Patent Owner Response). Moreover, we are unable to identify any argument in the Patent Owner Response to which this line of argument is properly responsive, and Petitioner does not identify any such line of argument. Instead, Petitioner’s argument appears to advance belatedly a new theory. See 37 C.F.R. § 42.23(b); Patent Trial and Appeal Board Consolidated Trial Practice Guide (Nov. 2019), 73–74, available at” slip op. at 43

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedMixed

    “We credit the supporting testimony of Dr. Olivier on the points discussed above, as it is explained sufficiently and consistent with the testimony simply mirrors the Petition and does not explain sufficiently why a person of ordinary skill in the art would have understood Kovvali in the manner Petitioner asserts. See Pet. 35; Reply 17–18; Ex. 1003 ¶ 83.” slip op. at 44

  Patent outcomesUS 7,035,279 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,035,279
• Cisco Systems, Inc. v. Portsmouth Network Corp.Some claims unpatentable
  PTAB · 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 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,917,986
• Microsoft Corporation v. X1 Discovery, Inc.Instituted
  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 · KSR
  Patents in suitUS 9,633,139
• Microsoft Corporation v. X1 Discovery, Inc.Instituted
  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 Phillips
  Patents in suitUS 10,552,490
• Microsoft Corporation v. X1 Discovery, Inc.Instituted
  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 Phillips
  Patents in suitUS 7,370,035
• Qualcomm Incorporated v. Network System Technologies, LLCAll claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,594,052
• Whatfix Inc. v. Walkme Ltd.No claims unpatentable
  PTAB · Mar 28, 2025 · IPR2024-00065 · APJ Charles J Boudreau · IPR · Final written decision

  Claims 1–20 were not shown unpatentable under the Symons and Williams, Allen, or Krishnan and Radhakrishnan obviousness grounds.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Petitioner proposes that a “person of ordinary skill in the art (‘POSITA’) in the field of the ’317 patent would have [had a] bachelor’s degree in engineering or computer science and two years of experience working on NLP [natural language processing] or automation processes” or “[a]lternatively . . . would have [had] five to six years of experience working on NLP or automation processes.” Pet. 6 (citing Ex. 1003 ¶¶ 43–45). We adopted Petitioner’s proposal for purposes of the Decision on Institution, explaining that it appeared to be consistent with the evidence of record, including the asserted prior art and the ’317 patent. Dec. 12. is inconsistent with the asserted Symons prior art and with factors (4)–(6) set forth in Daiichi Sankyo. PO Resp. 20–21 (citing Ex. 2002 ¶¶ 36–45). According to Patent Owner, the technology of the ’317 patent was “evolving rapidly” and the level of sophistication in the technology was “relatively low” in November 2017. Id. at 21–22 (citing Ex. 1004, 1–2; Ex. 1009, 2; Ex. 2002 ¶ 42; Ex. 2003 (transcript of June 26, 2024, deposition of Dr. Beigi), 141:2–9, 191:18–197:5; Ex. 2007; Ex. 2008). Further, Patent Owner contends, “[a]ctive work[ers] in the field, like Symons,[8] had less experience than [Dr. Beigi] proposed.” Id. at 22 (citing Ex. 2002; Ex. 2003, 112:12–24). Accordingly, Patent Owner argues, “[t]he evidence of record demonstrates a more appropriate level of skill would [be] a worker who had some education, formal or informal, in computer science and 1–2 years’ work experience with chatbots using NLP and/or automation processes.” Id. (emphasis omitted) (citing Ex. 1003 ¶ 44; Ex. 2002 ¶ 44; Pet. 5–6). “Under Patent Owner’s more appropriate analysis,” Patent Owner contends, “Dr. Beigi’s interpretation of what a POSITA would understand are overstated,” as “[h]e expects a POSITA to have ‘more experience’ (like himself) and apply a more ‘technically correct’ (in his view) understanding of the prior art than less skilled authors and artisans would have understood.” Id. (citing Ex. 2003, 141:2–9, 191:18–197:5). Nonetheless, Patent Owner argues, “[s]hould the Board continue to apply Petitioner’s” slip op. at 12

  • 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))). construction” “[f]or purposes of this Petition.” Pet. 6. Patent Owner similarly represents that “[t]he parties agree that the claim terms used in the ’317 Patent claims have their ‘ordinary and custom[ary] meanings of terms’ as would be understood by a POSITA as of November 5, 2017.” PO Resp. 24. After reviewing the parties’ arguments and evidence, we determine that no express claim construction is necessary. See Realtime Data, 912 F.3d at 1375.” slip op. at 15

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “Ex. 1042 ¶¶ 35–37). Further, Petitioner asserts, “the Petition relies on Williams, not Symons, for its teachings of a ‘web-based’ target system.” Id. (citing Pet. 40). Petitioner does not, however, address Patent Owner’s main point, i.e., that the Petition relies on Symons’s illustration of its RPA bot purportedly filling in a text input field in the GUI of the Cronos Email Signature Generator for limitation 1[g] but relies on Symons’s illustration of its RPA bot interacting with a widget in Internet Explorer for limitation 1[h], despite the recitation in limitation 1[h] of “interacting with a widget in the GUI.” See, e.g., PO Resp. 38. Dr. Beigi acknowledges that, “[a]ccording to the ’317 patent, a widget is a GUI element,” and he concludes, with reference to Petitioner’s annotated version of the screenshot from page 13 of Exhibit 1006 reproduced above, that “Symon[s]’s GUI button is a widget in a GUI.” Ex. 1003 ¶ 100 (emphasis added) (citing Ex. 1001, 10:19–21). But neither the Petition, nor the Reply, nor Dr. Beigi’s testimony persuasively explains how a dialog box in Internet Explorer teaches or suggests a widget in the Cronos GUI. The Reply’s contention that “the Petition relies on Williams . . . for its teachings of a ‘web-based’ target system” is unavailing, because the issue is not whether either the Cronos program or Internet Explorer is “web-based”12 but whether Petitioner has identified a teaching or suggestion of an implementation of an automation process that fills in a text input field in a GUI of a web-based target system and interacts with a widget in the same GUI. 12 In this regard, we credit Mr. Zatkovich’s statement that Internet Explorer is local to and resident on the user’s computer. Ex. 2002 ¶¶ 161–162; cf. Ex. 2003, 219:24–220:5 (Dr. Beigi testifying that he is “not sure where this Windows software is running”).” slip op. at 39

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundReasonable expectation not foundNot shown unpatentable

    “Petitioner’s reasoning fails to explain “how the combination of the two references was supposed to work.” See Personal Web Techs., LLC v. Apple, Inc., 848 F.3d 987, 994 (Fed. Cir. 2017). More specifically, Petitioner fails to explain how or why a person of ordinary skill in the art would be motivated to perform Krishnan’s automation process (i.e., fulfilling customer requests) by implementing an “automation process by interacting with a Graphical User Interface (GUI)” and “simulating user input to the GUI,” as purportedly taught by Radhakrishnan. Petitioner’s arguments are focused toward using Radhakrishnan’s RPA bot to perform Krishnan’s customer service requests (i.e., automation process) but fail to explain how Radhakrishnan’s RPA bot’s mirroring of the user’s operations (i.e., the simulation on the displayed user interface) as applied in Krishnan would work or provide sufficient reasoning to do so. See Personal Web, 848 F.3d at 993–994 (“[I]t does not imply a motivation to pick out . . . two references and combine them to arrive at the claimed invention”); In re Kahn, 441 F.3d 977, 986 (Fed. Cir. 2006) (“[M]ere identification in the prior art of each element is insufficient to defeat the patentability of the combined subject matter as a whole”).” slip op. at 60

  Patent outcomesUS 11,558,317 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,558,317
• Whatfix Inc. v. Walkme Ltd.Some claims unpatentable
  PTAB · Mar 18, 2025 · IPR2023-01368 · APJ Kara L Szpondowski · IPR · Final written decision

  Claims 1–8, 12, 13, 16, 19–23, 26, 29, and 31 are unpatentable over Symons and Williams; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Petitioner proposes that a person of ordinary skill in the art (“POSITA”) “would have a bachelor’s degree in engineering or computer science and two years of experience working on NLP [natural language processing] and automation processes. Alternatively, a POSITA would have five to six years of experience working on NLP and automation processes.” Pet. 5–6 (citing Ex. 1003 ¶¶ 50–52). We adopted Petitioner’s proposal for purposes of the Decision on Institution, explaining that it appeared to be consistent with the evidence of record, including the asserted prior art and the ’664 patent. Dec. 12.” slip op. at 14

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Plain and ordinary meaningDecided for petitioner

    “We interpret claims using the same claim construction standard that would be used to construe the claims in a civil action under 35 U.S.C. § 282(b). 37 C.F.R. § 42.100(b). Under that standard, words of a claim are generally given their ordinary and customary meaning as understood by a person of ordinary skill in the art at the time of the invention. Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc). However, “the specification may reveal a special definition given to a claim term by the patentee that differs from the meaning it would otherwise possess, and “[i]n such cases, the inventor’s lexicography governs.” Id. at 1316. A patentee may “choose to be his or her own lexicographer by clearly setting forth an explicit definition for a claim term that could differ in scope from that which would be afforded by its ordinary meaning.” Rexnord Corp. v. Laitram Corp., 274 F.3d 1336, 1342 (Fed. Cir. 2001). We only need to construe the claims to the extent necessary to resolve the parties’ disputes. See Realtime Data, LLC. v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019).” slip op. at 18

  • ExcludeGranted in part

    “Exhibits 2015–2017 are three comments made on the Internet in association with the Symons Article. These comments are also shown in Exhibit 2005. According to our rules, “[s]upplemental evidence is not filed at the time of the objection, but simply served, and is filed only in support of an opposition to a motion to exclude.” CTPG14 79 (citing 37 C.F.R. §§ 42.64(a), 42.64(b)(2)). Because no motion to exclude was filed by Petitioner, we agree with Petitioner that Patent Owner improperly filed Exhibits 2014–2017. However, as described above, the comments in Exhibit 2015–2017 are already part of the record in Exhibit 2005, and Petitioner has not filed a motion to expunge Exhibit 2005. Therefore, we are not aware of any harm to Petitioner by leaving these Exhibits in the record, as the information is 14 PTAB Consolidated Trial Practice Guide, November 2019 (the “CTPG”), available at: https://www.uspto.gov/sites/default/files/documents/tpgnov.pdf. already there. See Tr. 100:8–14. Moreover, retaining these Exhibits in the record will avoid confusion in the record and serve the public interest in a full and complete record. Accordingly, we will expunge only Exhibit 2018, as agreed by the parties, and waive the requirements of 37 C.F.R. § 42.64(b)(2) to the extent necessary to retain entry of Exhibits 2014–2017.” slip op. at 27

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentable

    “We need not determine whether Symons alone teaches this limitation, because we are persuaded that Petitioner has sufficiently shown that the combination of Symons and Williams teaches this limitation. We agree with Petitioner that, by disclosing that “chatbots can engage in natural language dialog with the caller and discern, through a series of interactions, the nature of the call[,] . . .capture information required to further handle the request . . [and] then trigger a robot, passing the required information to the robot to complete the request,” Williams teaches “determining . . . an automation process,” as recited in limitation 1[c]. See Pet. 19 (citing Ex. 1011, 3) (some emphasis omitted); see Ex. 1003 ¶ 95. We disagree with Patent Owner’s arguments that the combination is “ill-defined.” Sur-reply 8–9. Petitioner argues that the combination of Symons and Williams “results in a chatbot-RPA bot system capable of handling a user request for automated email signature generation along with other requests, such as automated generation of an electronic letterhead or an electronic invoice.” Pet. 20 (citing Ex. 1003 ¶ 98). In other words, in addition to the capability of handling the automated email signature generation (as taught in Symons), the combined chatbot-RPA bot system can handle other requests as well (as taught in Williams). Further, we agree with Petitioner that “[t]he ability to handle multiple requests would expand the capabilities and flexibilities of the chatbot-RPA bot” as well as “improv[e] costs, time, and capabilities.” Id. at 19–20 (citing Ex. 1003 ¶¶ 95, 96, 99). Both Symons and Williams support this argument. Ex. 1011, 2 (stating that RPA “support[s] repetitive, labor-intensive and transactional business processes,” that “software robots [are] an attractive way to drive operational cost reduction,” and that “[a]utomation through RPA can offer a return on investment (ROI) often ranging between 30 and 50 percent”); id. at 5 (stating that “[d]eployment of these cognitive tools promises new levels of productivity and innovation–freeing human workers to focus on higher-value activities and bringing industrial-level quality, consistency and auditability to business processes”); Ex. 1004, 2 (stating that “combining [RPA bots and chatbots] to automate processes can tremendously boost productivity in multiple organizations” and that “[RPA bots] reduce[] costs and human efforts”). Patent Owner’s argument that “[n]either Symons nor Williams suggest using a single chatbot-RPA to handle multiple requests at once in the same conversation thread” (PO Resp. 38) is not commensurate with the claim language, which does not require a single automation process (e.g., chatbot-RPA) to handle multiple inputs (e.g., multiple requests in the same conversation thread). See Reply 9–10. Regardless, however, we are not persuaded that Williams does not suggest using a single chatbot-RPA to handle multiple requests, as argued by Patent Owner. Sur-reply 9; see Ex. 1011, 2 (stating, for example, that “[t]he most common processes enabled by RPA today include back-office administrative processes and workflow within IT, finance, procurement, and human resources functions” and that “RPA enlists software robots to perform complex, nested routines that cut across multiple applications and interact with these systems”); id. at 3 (“Through several scripted questions, the virtual agent can surmise that the supplier is asking for status on their payment and, thus, trigger an RPA robot to access the appropriate enterprise resource planning (ERP) backend system, validate the caller’s details, retrieve necessary information, and provide status back in real-time to the supplier.”).” slip op. at 35

  Patent outcomesUS 10,819,664 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,819,664
• Cellco Partnership D/B/A Verizon Wireless / T-Mobile USA, Inc. et al. v. Aspen Networks, Inc.Institution denied
  PTAB · Mar 17, 2025 · IPR2025-00008 · APJ Donald E Daybell · IPR · Institution

  The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–28 were unpatentable over Tagg or Kottilingal and Politis.

  RulingsInstitution decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner

    “There is, however, a consistent thread that flows through the relevant disclosures of the specification; namely, that the “state involving the SIP sequence” is maintained throughout a dialog. Ex. 1001, 5:1–38 (step 210); see also id. (step 160). Using the method of Figure 4, including steps 160 and 210 and maintaining the SIP signaling state, is how the ’554 Patent discloses that calls are not broken or dropped. See, e.g., id. at 7:10–25. Maintaining the “state” of the SIP signaling sequence includes (but is not limited to) the teachings that a “SIP signaling sequence number” is maintained, as well as the details of how that number is maintained, as set forth in the specification. We find that the state of the SIP signaling sequence as that term is used in the specification refers to the rules (or paradigm) used to identify a collection of SIP signals as a “SIP signaling sequence,” and in particular the rules used to identify the next SIP packet received as belonging to a sequence of packets previously received. One key to the disclosed invention discussed in the specification is the concept that the invention prevents a call 3:45–4:9. The specification contends that the invention accomplishes this goal by configuring the packets involved in a VoIP call such that the receiving device (e.g., a SIP server) is able to recognize those packets as belonging to the same call, even though the packets are received over different paths. Id. at 7:35–50; 7:60–8:3. The particular way that the receiving devices are able to recognize that the packets are part of the same call is, per the claims, because the SIP signaling sequence is maintained after a network switch. Id. at 8:27–29. Thus, where a sequence of SIP signals uses numbers such as cseq values, there is a rule for identifying what the next signal in the sequence is. Ex. 1001, 5:1–38. A receiving device that knows the rule can identify an incoming packet as the next packet in the same signaling sequence as previously received packets, by applying the rule. Id. at 7:35–50. The specification provides one example rule, that the next SIP signal bears a monotonically-increasing cseq number. Id. at 5:1–38. But there could be other such rules as well. For example, the value could be monotonically decreased, or the value could be determined using some other formula.8 The claims also do not require that the sequence of SIP signals use “numbers” as sequence identifiers.9 Other labeling paradigms could be possible as well, 8 Patent Owner’s litigation claim construction improperly imports implementation details from the preferred embodiment, such as “cseq numbers” and the limitations that these numbers “monotonically increase” for new transmissions, or be “preserved” for re-transmissions. While such embodiments would be one way of maintaining a SIP signaling sequence, the specification does not clearly limit the invention to only these embodiments. 9 Petitioner’s litigation claim construction improperly imports the limitation from the preferred embodiment that the SIP signaling sequence must be” slip op. at 14

  • Skill levelSkill level board ownDecided for patent owner

    “as of the time of the invention of the ’554 Patent “would have been familiar with designing rules for implementing policies for service plans for use of an access network and provisioning those rules to network elements for policy enforcement” and would have gained this knowledge through a mixture of training and work experience, such as by having a Bachelor’s degree in electrical engineering or computer science and two years of experience; or by obtaining a Master’s degree in electrical engineering or computer science, but having only one year of experience; or by having no formal education but experience in network service plan provisioning systems of at least four years. Pet. 10. 4 The Leahy-Smith America Invents Act (“AIA”), Pub. L. No. 112–29, 125 Stat. 284, 287–88 (2011), amended 35 U.S.C. § 103. Because the ’554 Patent was filed before the effective date of the relevant amendment, the pre- AIA version of §103 applies. that a POSITA must specifically have “been familiar with designing rules for implementing policies for service plans for use of an access network and provisioning those rules to network elements for policy enforcement.” Prelim. Resp. 17–18. At this juncture, we adopt the agreed-upon portion of Petitioner’s definition, without the specific requirement relating to designing rules. This definition appears to be consistent with what is reflected by the content of the applied prior art references. Cf. Okajima v. Bourdeau, 261 F.3d 1350, 1354–55 (Fed. Cir. 2001) (recognizing that the applied prior art may reflect an appropriate level of skill). Our analysis would be the same under either definition.” slip op. at 8

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “determine whether to institute review. Upon consideration of the arguments and evidence before us, we conclude that Petitioner has not shown a reasonable likelihood of success in establishing that any claim of the ’554 Patent is unpatentable, and thus we decline to institute review. The Petition is denied, and inter partes review is not instituted.” slip op. at 2

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “We disagree with Petitioner’s view of Tagg. At best, the cited portions of Tagg disclose that SIP is used by endpoint 1512 to communicate with SIP server 1500, and by the SIP server to communicate with SIP proxy 1504. Figure 15 discloses that SIP is used for both of the paths from endpoint 1520 to SIP server 1500, via the WWAN or the WLAN. Figure 15 further discloses that SIP is used for the path from SIP server 1500 to SIP proxy 1504. But Figure 15 and the accompanying text are silent about any “sequences” of SIP signals at all, much less whether any such “sequences” are maintained, as required by the language of limitation 1.6. Ex. 1005 ¶¶ 324–346, Fig. 15. Instead, Tagg’s specification simply discloses that SIP is used to perform call management functions. Id. ¶¶ 245–247. Tagg’s cases 1 and 6, relied on by Petitioner, teach that Tagg’s server can ensure that the end user appears to the rest of the world (i.e. the devices upstream of the SIP server) as if no network change is being made. Ex. 1005 ¶ 320. Tagg further teaches that either “make before break” or “make and break” schemes may be used. Id. But these cases do not explain how any SIP signaling sequences are used, much less how or even that any SIP signaling sequence is maintained when a network switches. At most, Tagg teaches that each path will have an IP (Internet Protocol) address, which may be the same or different for each path. Id. ¶ 288. But IP addresses are part of the IP disclosing or suggesting that IP addressing schemes are maintained or otherwise accounted for in a network switch, that would not be sufficient to disclose or suggest that SIP signal sequences are maintained. Furthermore, under our construction of limitation 1.6, it must be shown that the same rules or paradigm used to identify that an incoming SIP packet is the next SIP packet in a sequence, regardless of whether that packet is transmitted on the first network path or the one of a plurality of alternative network paths. The Petition is silent on this point. The closest Petitioner comes is the assertion that Figure 15 depicts preservation of “the same SIP signaling sequence,” with the Petitioner’s explanation being that Tagg allows simultaneous connections across a WWAN and a WLAN, and that “POSITAs would have understood that Tagg’s SIP protocol uniformity in directionality teaches that a ‘SIP signaling sequence . . . is maintained.’” Pet. 39–40.” slip op. at 22

  Claim construction§ 103 obviousnessDiscretionary denialcites Phillips · KSR · Graham
  Patents in suitUS 8,009,554

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.