• Cisco Systems, Inc. / Juniper Networks, Inc. v. Orckit CorporationSome claims unpatentable
  PTAB · Oct 22, 2024 · IPR2024-00034 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 1–13 and 17–20 are unpatentable over the stated obviousness grounds; claims 14–16 are not shown unpatentable because the cited art does not teach logic configured to determine concurrent failure probability.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “We decline to adopt Patent Owner’s implicit construction that would require “selecting an entity pair from” all of the entity pairs of “said plurality of transport entities.” Contrary to Patent Owner’s arguments addressing the claim language, the plain language of claim 1 does not require the selection to be from all of the entity pairs of the plurality of transport entities for which an overall cost has been determined. The plain language of claim 1 also does not preclude the selection to be from a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined. Rather, dependent claim 9, through its dependence on claims 1 and 4, explicitly allows for the selection to be from a subset of the entity pairs of the plurality of transport entities. Patent Owner’s arguments advocate for the importation of limitations from the ’821 Patent Specification into the claim––namely the disclosure that all entity pairs of transport entities examined in step 220 of Figure 2 are input to the entity pair selection step 230. See PO Sur-reply 4. It is well settled that it is improper to read an extraneous limitation into a claim from the specification. See e.g., Commark Comm’s Inc. v. Harris Corp., 156 F.2d 1182, 1186 (Fed. Cir. 1998); E.I. du Pont de Nemours & Co. v. Phillips Petroleum Co., 849 F.2d 1430, 1433 (Fed. Cir. 1988). An extraneous limitation is “a limitation read into a claim from the specification wholly apart from any need to interpret what the patentee meant by particular words or phrases in the claim.” E.I. du Pont de Nemours, 849 F.2d at 1433. Accordingly, we construe “selecting an entity pair from said plurality of transport entities based at least upon said overall cost” according to its plain meaning, the scope of which includes selecting an entity pair from all or a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined.” slip op. at 11

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

    “As demonstrated in the analysis below, we need not construe “working entity” and “protection entity” in order to resolve the controversy before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). Other Claim Terms and Phrases As demonstrated in our analysis below, we need not construe any other claim terms or phrases to resolve the controversy before us. See, e.g., Realtime, 912 F.3d 1368, 1375.” slip op. at 13

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s level of ordinary skill for purposes of this Patent Owner Response.” PO Resp. 25. We adopt Petitioner’s definition of a person of ordinary skill in the art because it is supported by declaration testimony and is consistent with the level of skill reflected by the ’821 Patent Specification and the asserted prior art. slip op. at 14

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

    “Based on the entire record and after having considered Petitioner’s citations to Doshi, Guichard, and Dr. Houh’s testimony (Ex. 1003) as well as Patent Owner’s citations to Doshi, Guichard and Mr. Gomez’s testimony, we are persuaded Petitioner sets forth sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to one of ordinary skill in the art to combine the teachings of Doshi with Guichard’s teachings of reoptimization of a LSP path triggered by an network change. See Pet. 20–22, 40–45; KSR, 550 U.S. at 418. Petitioner asserts that “[t]he results of the combination would have been predictable and there would have been a reasonable expectation of success since Doshi and Guichard both address the same technology.” Pet. 22 (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “a POSITA would have had a reasonable expectation of success in reoptimizing Doshi’s LSP pair selection because Guichard provides significant implementation details, including when to trigger reoptimization evaluations and how to ‘avoid network instabilities.’” Pet. 22–23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1006, 5). Petitioner asserts that a reasonable expectation of success is evidenced by other skilled artisans that reoptimized similar systems. See Pet. 23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1009, 136; Ex. 1010, 1; Ex. 1023, 34; Ex. 1034 ¶¶ 27–33, claim 19; Ex. 1035 ¶ 24). In support, Petitioner contends that “the combination would be within a POSITA’s skillset since Doshi already sets forth the calculation and selection techniques that would be utilized during the reoptimization evaluation.” Id. (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “since Doshi is already ‘monitoring and updating . . . network topology’ . . . event-based reoptimization evaluation per Guichard, would be directly applicable.” Id. (citing Ex. 1003 ¶¶ 63–65; Ex. 1005 ¶¶ 270–281).” slip op. at 38

  Patent outcomesUS 8,830,821 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,830,821
• Cisco Systems, Inc. / Juniper Networks, Inc. v. Orckit CorporationSome claims unpatentable
  PTAB · Oct 22, 2024 · IPR2023-00402 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 1–13 and 17–20 are unpatentable over the Doshi and Guichard grounds; claims 14–16 were not shown unpatentable over Doshi, Guichard, and Xu.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “require “selecting an entity pair from” all of the entity pairs of “said plurality of transport entities.” Contrary to Patent Owner’s arguments addressing the claim language, the plain language of claim 1 does not require the selection to be from all of the entity pairs of the plurality of transport entities for which an overall cost has been determined. The plain language of claim 1 also does not preclude the selection to be from a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined. Rather, dependent claim 9, through its dependence on claims 1 and 4, explicitly allows for the selection to be from a subset of the entity pairs of the plurality of transport entities. Patent Owner’s arguments advocate for the importation of limitations from the ’821 Patent Specification into the claim––namely the disclosure that all entity pairs of transport entities examined in step 220 of Figure 2 are input to the entity pair selection step 230. See PO Sur-reply 4. It is well settled that it is improper to read an extraneous limitation into a claim from the specification. See e.g., Commark Comm’s Inc. v. Harris Corp., 156 F.2d 1182, 1186 (Fed. Cir. 1998); E.I. du Pont de Nemours & Co. v. Phillips Petroleum Co., 849 F.2d 1430, 1433 (Fed. Cir. 1988). An extraneous limitation is “a limitation read into a claim from the specification wholly apart from any need to interpret what the patentee meant by particular words or phrases in the claim.” E.I. du Pont de Nemours, 849 F.2d at 1433. Accordingly, we construe “selecting an entity pair from said plurality of transport entities based at least upon said overall cost” according to its plain meaning, the scope of which includes selecting an entity pair from all or a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined.” slip op. at 11

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

    “As demonstrated in the analysis below, we need not construe “working entity” and “protection entity” in order to resolve the controversy before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). Other Claim Terms and Phrases As demonstrated in our analysis below, we need not construe any other claim terms or phrases to resolve the controversy before us. See, e.g., Realtime, 912 F.3d 1368, 1375.” slip op. at 13

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s level of ordinary skill for purposes of this Patent Owner Response.” PO Resp. 25. We adopt Petitioner’s definition of a person of ordinary skill in the art because it is supported by declaration testimony and is consistent with the level of skill reflected by the ’821 Patent Specification and the asserted prior art. slip op. at 14

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

    “Based on the entire record and after having considered Petitioner’s citations to Doshi, Guichard, and Dr. Houh’s testimony (Ex. 1003) as well as Patent Owner’s citations to Doshi, Guichard and Mr. Gomez’s testimony, we are persuaded Petitioner sets forth sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to one of ordinary skill in the art to combine the teachings of Doshi with Guichard’s teachings of reoptimization of a LSP path triggered by an network change. See Pet. 20–22, 40–45; KSR, 550 U.S. at 418. Petitioner asserts that “[t]he results of the combination would have been predictable and there would have been a reasonable expectation of success since Doshi and Guichard both address the same technology.” Pet. 22 (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “a POSITA would have had a reasonable expectation of success in reoptimizing Doshi’s LSP pair selection because Guichard provides significant implementation details, including when to trigger reoptimization evaluations and how to ‘avoid network instabilities.’” Pet. 22–23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1006, 5). Petitioner asserts that a reasonable expectation of success is evidenced by other skilled artisans that reoptimized similar systems. See Pet. 23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1009, 136; Ex. 1010, 1; Ex. 1023, 34; Ex. 1034 ¶¶ 27–33, claim 19; Ex. 1035 ¶ 24). In support, Petitioner contends that “the combination would be within a POSITA’s skillset since Doshi already sets forth the calculation and selection techniques that would be utilized during the reoptimization evaluation.” Id. (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “since Doshi is already ‘monitoring and updating . . . network topology’ . . . event-based reoptimization evaluation per Guichard, would be directly applicable.” Id. (citing Ex. 1003 ¶¶ 63–65; Ex. 1005 ¶¶ 270–281).” slip op. at 38

  Patent outcomesUS 8,830,821 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,830,821
• Cisco Systems, Inc. v. Orckit CorporationSome claims unpatentable
  PTAB · Oct 8, 2024 · IPR2023-00714 · APJ Brent M Dougal · IPR · Final written decision

  Claims 1–5, 7–16, 18–22, and 24–26 are unpatentable as obvious over Vink and Patrick, with or without AAPA; claims 6, 17, and 23 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art at the time of the invention. Id. at 13, 17. Petitioner asserts that a person of ordinary skill in the art (“POSA” or “POSITA”) would have had a bachelor’s degree in computer science, computer engineering, electrical engineering, or equivalent training, or approximately two years of experience working in the field of information technology and networking . . . . Lack of professional experience can be substituted by additional education, and vice versa. Pet. 12 (citing Ex. 1003 ¶¶ 59–60). “Patent Owner does not dispute Petitioner’s proposed level of ordinary skill.” PO Resp. 19. We are persuaded that Petitioner’s proposal is consistent with the problems and solutions addressed in the ’904 patent and prior art of record. We adopt Petitioner’s definition of the level of skill for the purposes of this Decision.” slip op. at 6

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “Patent Owner argues “that ‘subscriber lines’ should be construed as ‘communication lines to users of subscription-based network services.’” Id. Petitioner does not dispute this construction directly, but rather argues that no construction is necessary. Reply 6. We determine that no terms need to be construed. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 7

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

    “Here however, we have found that it was known to connect LANs to external networks. See Ex. 1014, 6:23–28, Fig. 1; Ex. 1015, 1:6–9; Ex. 1016, 1:22–25; Ex. 1017, 1:7–11. We further agree with Petitioner’s uncontested point that “[t]echniques to further allow the communication system to access external networks by connecting the master to an external network were well-known in the art, as evidenced by Patrick and/or AAPA.” Pet. 24 (citing Ex. 1003 ¶¶ 74–88). The Petition focusses on combining the “communication systems” of Vink, Patrick and/or AAPA, as opposed to relying on a particular type of LAN. Thus, in contrast to Forest Lab’ys, we determine that the general or “generic” benefit of providing “access to a wider array of information,” where it was already known to provide external network access (e.g., the internet) to LANs,5 does provide a motivation to combine Vink and Patrick, with or without AAPA. See Intel Corp. v. Pact XPP Schweiz AG, 61 F.4th 1373, 1380–81 (Fed. Cir. 2023) (“There is a motivation to combine when a known technique ‘has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way.’” (quoting KSR, 550 U.S. at 417)).” slip op. at 20

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner

    “Patent Owner also argues that Vink “teaches against” hierarchical addressing because “doing so would eliminate the purported advantages associated with using a non-hierarchical system.” PO Resp. 36 (citing Ex. 2005 ¶ 69 (Patent Owner’s declarant making the same statement)). Patent Owner does not further discuss the reasoning behind this statement, identify the “purported advantages,” or even identify the relevant disclosure relied on in Vink. We decline to speculate as to Patent Owner’s position in this regard. We further note that “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.” Medichem, S.A. v. Rolabo S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006).” slip op. at 19

  Patent outcomesUS 6,680,904 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,680,904
• Arista Networks, Inc. v. Corrigent CorporationSome claims unpatentable
  PTAB · Jul 3, 2024 · IPR2023-00515 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–10, 12–22, and 24–30 are unpatentable as obvious under § 103; claims 11 and 23 were not shown unpatentable.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “For reasons explained in the Petition and Petitioner’s Reply, we agree with Petitioner that the Baker–Wright–Holender ’699 combination teaches summing the two bandwidths determined in “allocating” steps 12.5 and 12.7 to determine a total allocation for each of the physical links—motivated by the known need to ensure that bandwidths do not exceed the available physical link capacity. We disagree with Patent Owner that Holender ’699’s discussion of summing is merely describing a physical constraint. Holender ’699 teaches normalizing the logical link capacities, which requires summing the logical link capacities. See Ex. 1007, 8:38–51. We credit Dr. Houh’s testimony that this “confirms that [Holender ’699’s] teachings about summing are not simply ‘explaining a physical constraint,’ but actually performed.” Ex. 1036 ¶ 61. Holender ’699 refers to capacities 𝐶𝐶𝑗𝑗 as “logical link capacities for each logical link j over all logical networks. Ex. 1007, 6:52–55. But when mapped to physical links, Holender ’699 denotes capacities 𝐶𝐶𝑘𝑘𝑘𝑘 as “capacities of the logical links [𝑙𝑙] that need capacity on the k:th physical link.” Ex. 1007, 8:38–43. In other words, they are the capacities, or bandwidths, allocated to each physical link 𝑘𝑘 for implementing associated logical link 𝑙𝑙. See also id. at 6:60–67 (describing a matrix designed to indicate “if logical link j needs capacity on the k:th physical link.”).” slip op. at 50

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Relying on Dr. Houh’s testimony, Petitioner argues that a person of ordinary skill in the art “would have had a working knowledge of the networking art that is pertinent to the ’431 patent, including network communications techniques and bandwidth management methodologies,” and “would have had a bachelor’s degree in computer science, computer engineering, electrical engineering, or an equivalent, and two years of professional experience relating to network communications including the use of logical topologies and bandwidth management. Lack of professional experience can be remedied by additional education, and vice versa.” Pet. 3 (citing Ex. 1003 ¶¶ 18–20). Patent Owner adopts Petitioner’s proposed definition of the level of ordinary skill. PO Resp. 3. Because Petitioner’s articulation of that level of skill is uncontested, supported by testimonial evidence, and appears consistent with the types of problems and solutions in the ’431 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:5–6:14.” slip op. at 8

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

    “necessary because the construction does not resolve any contested issues. Pet. Reply 8–10 (citing Ex. 1005 ¶¶ 16, 62; Ex. 1006 ¶¶ 5, 24; Ex. 1003 ¶ 96; Ex. 1036 ¶¶ 49–50). But if a construction is necessary, Petitioner argues that the we should construe in response to as “using,” consistent with how the claimed invention is described in the ’431 patent. Id. at 10–11 (citing Ex. 1001, 2:52–6:10, 8:52–9:2; Ex. 1036 ¶¶ 7–11). Petitioner disagrees that the term means “based on” because limitation 1.3 uses the phrase based on, suggesting that the applicant made a conscious decision to use different language in limitation 1.5. Id. at 11 (citing Ex. 1036 ¶ 11). Patent Owner responds that its two proposed constructions are synonymous, and argues that Petitioner agrees that in response to encompasses “using” or “using information from.” PO Sur-reply 8 (citing Ex. 1001, 2:22–26). Patent Owner contends that its proposed construction resolves a controversy because in Patent Owner’s view, the Baker–Wright combination does not use information from the recited mapping to allocate bandwidth. Id. at 9–12 (citing Ex. 1006 ¶¶ 5, 17, 24; Ex. 2009, 52–56; Ex. 2008 ¶¶ 62–76). Similarly, Patent Owner contends that Holender ’699 does not teach mapping. Id. at 12–13 (citing Ex. 1007, 3:15–17; Ex. 2008 ¶¶ 89–92). We see no significant difference between Petitioner’s proposed construction of in response to as “using” and Patent Owner’s proposed construction as “using information from.” Thus, it does not appear that the construction of in response to is in controversy. Thus, we need not construe the term for this decision. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (alteration in original) (quoting Vivid Techs., Inc. v. Am. Sci & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). To the extent that we need to interpret any other claim language, we address that language below in the context of the prior art.” slip op. at 10

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

    “We find Petitioner’s arguments persuasive that Baker teaches allocating bandwidth as part of its resources and that, in light of Wright and Holender ’699, a person of ordinary skill in the art would have had reason to make this allocation for each of the links in of the physical topology (see Ex. 1006 ¶ 18 (“bandwidth allocation at each link”)) using information from both (1) the bandwidth requirements of Baker’s logical connections and (2) the mapping between Baker’s logical and physical topologies. As Petitioner persuasively argues, we find that Wright’s teaching of further details on ensuring the availability of bandwidth, in a similar context, would have been sufficient motivation for a person of ordinary skill in the art to incorporate Wright’s teachings into Baker’s method. Holender ’669 provides further supporting disclosure. We also determine that whether Wright, itself, teaches a mapping step is not the determining factor because Petitioner relies on Baker, not Wright, for teaching mapping limitation 1.4. Nevertheless, Wright does teach allocating bandwidth using the same information that would be available as a result of Baker’s mapping, including the logical (“restricted”) topology and the physical links associated with that topology. In particular, we agree with Petitioner that a person of ordinary skill in the art would have understood that allocating bandwidth to the physical links (step 510 of Figure 5) requires knowing which physical links correspond to Wright’s restricted topology. See Pet. 33; Pet. Reply 22–23; Ex. 1007 ¶ 17; Ex. 1003 ¶¶ 94–96; Ex. 1036 ¶¶ 49–51. We also disagree with Patent Owner that Petitioner has failed to adequately explain how a person of ordinary skill in the art would have modified Baker’s method to apply Wright’s teachings on bandwidth allocation, such as how Baker’s head node N0 would have been modified. See PO Resp. 31–32. Based on the level of ordinary skill and the level of detail in Baker, Wright, and the ’431 patent, and crediting Dr. Houh’s testimony, we find Petitioner’s argument persuasive that such modification would have been within the capability of someone of ordinary skill in the art. See Pet. 9–12 (citing Ex. 1003 ¶¶ 42–46, 48; Ex. 1021 ¶¶ 100–101). And we agree with Petitioner that modifying Baker with Wright’s teachings would have been “nothing more than the combination of known elements . . . according to known methods . . . to yield predictable results.” Pet. 11–12 (citing Ex. 1003 ¶ 47; Ex. 1021 ¶¶ 102–104).” slip op. at 34

  Patent outcomesUS 7,330,431 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,330,431
• Netflix, Inc. v. Avago Technologies International Sales Pte. LimitedSome claims unpatentable
  PTAB · May 16, 2022 · IPR2021-00057 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 1–7, 10–20, and 23–27 are unpatentable as obvious over Lai and Knauerhase; claims 9 and 22 were not shown unpatentable because the combination did not teach the claimed primary and secondary server selection.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “C. Level of Ordinary Skill in the Art Petitioner asserts that a person of ordinary skill in the art (POSITA) of the ’976 patent would have been a person with a bachelor’s degree in computer engineering, electrical engineering, computer science, or a similar field with at least two years of experience in web services or a person with a master’s degree in computer engineering, electrical engineering, computer science, or a similar field with a specialization in web services. . . . A person with less education but more relevant practical experience may also meet this standard. Pet. 21 (citing Ex. 1003 ¶¶ 51–52). Petitioner further contends that, in the 2003 timeframe, a person of ordinary skill in the art would have known and had the skills necessary to: (1) design systems and author software for the discovery and invocation of web services, including using Extensible Markup Language (XML), Web Services Description Language (WSDL) and Simple Object Access Protocol (SOAP); (2) implement web service registries, such as UDDI or equivalent Internet-based registries; (3) implement load balancing for web services, including employing various scheduling algorithms; and (4) implement failovers for servers. See id. at 21–22 (citing Ex. 1003 ¶ 53; Ex. 1004 ¶¶ 54, 42–43, 213–215, 449, 601–606, 659; Ex. 1005 code (57), ¶¶ 5, 23–25, 29; Ex. 1006 ¶¶ 5–7; Ex. 1007 ¶¶ 4–8, 12–14; Ex. 1009, 1:59–2:4; Ex. 1010, 4:47–5:9). Patent Owner does not dispute Petitioner’s assertions addressing the skill level of a person of ordinary skill in the art. See generally PO Resp. We adopt Petitioner’s definition of a person of ordinary skill in the art because it appears to be consistent with the level of skill reflected by the ’976 Patent Specification and the asserted prior art.” slip op. at 10

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “We decline Patent Owner’s urging to give little weight to Dr. Cromarty’s testimony and, in particular, his testimony that the ’976 Patent prosecution history made clear that the selection of the server by the registry is necessary for the selection to be independent (see Ex. 1003 ¶ 96). We do not agree that the reliability of Dr. Cromarty’s testimony is wholly contaminated based on Patent Owner’s criticism of the extent of Dr. Cromarty’s review of Pruitt and alleged inaccurate paraphrasing in paragraph 38 of statements made in the Appeal Brief. Contrary to Patent Owner’s argument, Dr. Cromarty’s testimony in paragraph 96 is supported by citations to the prosecution history. See Ex. 1003 ¶ 96 (citing Ex. 1002, 342–343, 425). Consistent with Dr. Cromarty’s testimony, the prosecution history cited by Dr. Cromarty reveals the following: (1) “Appellants note that the cited portions of Pruitt do not appear to disclose that UDDI registry 410 selects a service location among one or more capable service locations;” (2) “Appellants note that [the] Examiner cites column 8, lines 33-35 of Pruitt (disclosing that ‘client 225 may determine which service location to use . . .’) and column 10, lines 62-65 of Pruitt (disclosing that ‘the client may select a service location . . .’ as allegedly disclosing ‘selecting a server among one or more servers capable of running the web service;’” (3) the Board found that “Pruitt discloses that ‘[a]fter receiving a list of service locations, client 225 may determine which service location to use [to] access the service at the service location;’” (4) the Board found that “Pruitt discloses that the client running the requesting application selects the server from among the one or more servers capable of running the selected web service;” and (5) the Board found “the selection of the server in Pruitt is not ‘independent of input from a requesting application subsequent to selection of the web service.’” Ex. 1002, 342–343, 425. Notably, Patent Owner does not dispute the accuracy of Dr. Cromarty’s testimony that the prosecution history makes clear that selection of the server by the registry is necessary for the selection to be independent (Ex. 1003 ¶ 96). See PO Resp. 20–26, 34–36.” slip op. at 37

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

    “Petitioner proposes claim constructions for “real address” and “distributed scheduling algorithm.” See Pet. 22–26. Patent Owner does not agree with Petitioner’s proposed claim constructions, but instead asserts these terms should be construed in accordance with their plain and ordinary meanings. See PO Resp. 12–13 (citing Ex. 2002 ¶ 45). As demonstrated in the analysis below, we need not construe explicitly these claim terms or any other claim terms or phrases. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017).” slip op. at 9

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner

    “We do not agree with Patent Owner’s arguments. As pointed out by Petitioner, the Petition provides reasons to combine the teachings of Lai and Knauerhase based on the prior art. See Pet. Reply 25 (citing Pet. 32–33; Ex. 1012, Abstract, 12–13; Ex. 1013, Abstract, 585–587; Ex. 1015, 565). We also agree with Petitioner that, contrary to Patent Owner’s arguments, the ’976 Patent does not mention any advantages or benefits of connecting a client with a server without client input, and the words “independent of input” do not appear in the ’976 Patent. After having analyzed the entirety of the record and assigning appropriate weight to the cited supporting evidence, we determine that Petitioner has set forth sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to a person of ordinary skill in the art to modify the teachings of Lai to include Knauerhase’s teachings of an improved UDDI registry that identifies or selects the best service provider in order to improve web services architecture for web services discovery and invocation with improved reliability and availability. See Pet. 30–36; KSR 550 U.S. 418.” slip op. at 45

  Patent outcomesUS 8,548,976 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,548,976
• Intel Corporation v. VLSI Technology LLCSome claims unpatentable
  PTAB · Feb 6, 2020 · IPR2018-01144 · APJ Bart A Gerstenblith · IPR · Final written decision

  Claims 2, 7, and 8 are unpatentable as obvious over Bednar and Gunther; claim 3 was not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “to the level of ordinary skill in the art was incorrect. Accordingly, because our preliminary finding is consistent with the level of ordinary skill in the art reflected by the prior art of record, we maintain and reaffirm that one of ordinary skill in the art at the time of the invention would have had “at least (1) an undergraduate degree in electrical engineering (or an equivalent subject), together with three years of post-graduate experience designing power management circuits; or (2) a master’s degree in electrical engineering (or equivalent subject) together with two years of post-graduate experience designing power management circuits.” Inst. Dec. 8; see Pet. 29 (citing Ex. 1102 ¶¶ 26–27).” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed board ownDecided for patent owner

    “construction is erroneous. Accordingly, because the ’922 patent defines “power island,” we maintain and reaffirm that “power island” means a “group of components with similar power requirements.”” slip op. at 12

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

    “not to expressly construe “conversion controller” was erroneous or that an express construction is required to resolve any dispute between the parties. Accordingly, we maintain and reaffirm that because the construction of “conversion controller” does not resolve a controversy in the matter before us, we decline to construe it expressly.” slip op. at 13

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “construction of “memory device,” specifically whether it encompasses a latch. Neither party argues that “memory device” is expressly defined in the ’922 patent. Accordingly, the plain and ordinary meaning of the term controls. And, the standard under which we construe the term is the broadest reasonable construction in light of the specification.” slip op. at 86

  Patent outcomesUS 8,004,922 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,004,922
• Department Of Justice v. Discovery Patents, LLCSome claims unpatentable
  PTAB · Nov 9, 2017 · IPR2016-01041 · APJ Matthew R Clements · IPR · Final written decision

  Claims 11, 12, 14, 16–18, and 20–31 are unpatentable over Monroe ’183; claims 15 and 19 were not shown unpatentable over Monroe ’183.

  RulingsFinal written decision

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

    “A petition for inter partes review may be considered only if, inter alia, “the petition identifies all real parties in interest.” 35 U.S.C. § 312(a)(2). The Office Patent Trial Practice Guide provides guidance regarding factors to consider in determining whether a party is a real party in interest. 77 Fed. Reg. 48,756, 48,759–60 (Aug. 14, 2012). Considerations may include whether a non-party “funds and directs and controls” an IPR petition or proceeding. Id. at 48,760. Additional relevant factors include: the non-party’s relationship with the petitioner; the non-party’s relationship to the petition itself, including the nature and/or degree of involvement in the filing; and the nature of the entity filing the petition. Id. Whether a party who is not a named participant in a given proceeding is a real party in interest to that proceeding “is a highly fact-dependent question.” Id. at 48,759. There is no “bright line test.” Id. Courts invoke the term real party in interest to describe relationships and considerations sufficient to justify applying conventional principles of estoppel and preclusion. Id. A non-party’s participation with a petitioner may be overt or covert, and the evidence may be direct or circumstantial, but the evidence as a whole must show that the non-party possessed effective control over the petitioner relating to the inter partes review. Zoll Lifecor Corp. v. Philips Elecs. N. Am. Corp., Case IPR2013-00609, slip op. at 10 (PTAB Mar. 20, 2014) (Paper 15). We have considered Patent Owner’s and Petitioner’s arguments and evidence, and we determine that Petitioner was not required to identify the Third Parties as real parties in interest because there is insufficient evidence that any of these companies exercised, or could exercise, control over Petitioner with respect to this proceeding. Patent Owner’s arguments regarding the motion practice before the Court of Federal Claims and notification of that action to the Third Parties does not reflect otherwise. Although we acknowledge that the existence of the above-identified indemnification clauses supports Patent Owner’s argument, we are unaware of any inter partes review decision in which a real party in interest finding was based solely on evidence of an indemnification clause, and we decline to do so here.” slip op. at 7

  • PTAB / AIA Trials › Constitutional / APA (Arthrex, Oil States, due process)Decided for petitioner

    “We decline to consider Patent Owner’s constitutional challenge as, generally, “administrative agencies do not have jurisdiction to decide the constitutionality of congressional enactments.” See Riggin v. Office of Senate Fair Employment Practices, 61 F.3d 1563, 1569 (Fed. Cir. 1995); see also Harjo v. Pro-Football, Inc., 50 USPQ2d 1705, 1710 (TTAB 1999) (“[T]he Board has no authority . . . to declare provisions of the Trademark Act unconstitutional.”); Amanda Blackhorse v. Pro-Football, Inc., 111 USPQ2d 1080 (TTAB 2014), rev’d on other grounds, 284 F. Supp. 2d 96 (D.D.C. 2003); but see Am. Express Co. v. Lunenfeld, Case CBM2014- 00050, slip op. at 9–10 (PTAB May 22, 2015) (Paper 51) (“for the reasons articulated in Patlex [Corp. v. Mossinghoff, 758 F.2d 594 (Fed. Cir. 1985)], we conclude that covered business method patent reviews, like reexamination proceedings, comply with the Seventh Amendment”).” slip op. at 8

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

    “We agree with Petitioner. The ’980 patent states that “the term ‘secured location’ may refer to residences, commercial properties, public venues, such as hospitals and sports arenas, government facilities, military installations and any other location, outside or inside, which is protected by a security alarm system.” Ex. 1003, 3:20–24. This definition is non-limiting and does not exclude a changeable area or region. Based on the record developed during this proceeding, we maintain that the broadest reasonable construction in light of the ’980 patent of “secured location” is “any location, outside or inside, which is protected by a security alarm system.”” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner

    “We agree with Petitioner. Although the Specification of the ’980 patent gives examples of “response agency,” e.g., Ex. 1003, 1:41–43 (“an emergency response agency (e.g., the police department, the fire department or an emergency medical team)”), Patent Owner does not identify, and we do not find, a definition in the specification limiting “response agency” to 911, police, or fire departments. Patent Owner also does not identify, and we do not find, anything in the entire disclosure of the ’980 patent requiring a “response agency” to be distinct from the “surveillance system infrastructure.” Accordingly, we decline to limit “response agency” to 911, police, or fire departments, or construe it to be distinct from surveillance system infrastructure.” slip op. at 11

  Patent outcomesUS 7,323,980 mixed
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 7,323,980
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01400 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable under §103; the other challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “Patent Owner’s argument is not persuasive. We agree with Petitioner that 35 U.S.C. § 315(b) applies only to civil actions for patent infringement, and not to an administrative proceeding, including an ITC investigation. See Amkor, Paper 98, slip op. at 6–18; Brinkman Corp. v. A&J Mfg., LLC, Case IPR2015-00056, slip op. at 7–8 (PTAB Mar. 23, 2015) (Paper 10). Although Amkor and Brinkman Corp. are not precedential, we find them instructive and directly on point. In Amkor, the Board determined that “had Congress intended for arbitration, ITC, or other non-judicial proceedings to trigger the time bar of section 315(b), it would have used more encompassing language than ‘Patent Owner’s Action’ and ‘served with a complaint,’ which are harmonious with a civil action.” Amkor, Paper 98, slip op. at 11 (determining that the time bar is limited to being triggered by the service of a complaint in a civil action). A similar decision by the Board in Brinkman Corp. reaches the same result and specifically is directed toward an ITC investigation. Accordingly, we are not persuaded by Patent Owner that Petitioner is barred under 35 U.S.C. § 315(b).” slip op. at 18

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

    “Petitioner further contends that WINS discloses that NetBIOS is incorporated into the WINS system and expressly discloses that WINS should be combined with NetBIOS. Id. at 37–38 (citing 198 Ex. 1002 ¶ 81; Ex. 1003, 65). Accordingly, Petitioner concludes that one of ordinary skill in the art would have known about and been motivated to combine the references. Id. Petitioner further contends that a person with ordinary skill in the art would have been motivated similarly to combine WINS and NetBIOS with Pinard because Pinard discloses a telephony application with a graphical user interface that allows a user to establish and manage telephone calls. Id. at 38–39. Petitioner specifically argues that Pinard references Windows 3.1 and WINS references Windows 3.11 and Windows NT, and, therefore, a person with ordinary skill in the art would have known how to adapt the graphical user interfaces in Pinard to the system in WINS. Id. We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by WINS, and Pinard’s program is compatible with a Windows operating system, and, therefore, a person with ordinary skill in the art would have readily combined the disclosures of WINS, NetBIOS, and Pinard.” slip op. at 30

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1004, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to WINS, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.”” slip op. at 23

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

    “In Straight Path, the Federal Circuit held that the claim language “is connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query 11 Petitioner argues that the relevant specifications do not include an embodiment that “guarantee[s]” that an entry in its database is online, and, therefore, Patent Owner’s argument does not distinguish the ’704, ’469, and ’121 patents over the prior art. Addʼl Br. 6‒7. However, such an argument goes towards whether there is written description and enablement support for the claims. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time that the query is transmitted to the server.” Id. at 1363. Petitioner and Patent Owner argue that the limitations “on-line status” and “is accessible” have the same meaning as “is connected to the computer network.” See 209 Pet. 35–36; 209 PO Resp. 36‒48; 198 Pet. 35–36; 198 PO Resp. 35‒46; 196 Pet. 29; 196 PO Resp. 38‒51. Similar to “is connected to a computer network,” the “on-line status” and “is accessible” of the second process are recited in the present tense, and therefore must be claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter partes review.” Straight Path, 806 F.3d at 1363. We similarly do not determine whether this claim limitation is supported by the specifications of the ʼ704, ʼ469, and ʼ121 patents. determined at the time of the querying whether the second process “is accessible” or selecting of the process having an “on-line status.” Therefore, we construe “on-line status” and “is accessible” as having the same meaning as “is connected to the computer network.”” slip op. at 12

  Patent outcomesUS 6,009,469 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,009,469
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01397 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable as obvious; all other challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “2. Section 315(b) Under 35 U.S.C. § 315(b), “[a]n inter partes review may not be instituted if the petition requesting the proceedings is filed more than 1 year after the date on which the petitioner, real party in interest, or privy of the petitioner is served with a complaint alleging infringement of the patent.”” slip op. at 17

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “In Straight Path, the Federal Circuit held that the claim language “is connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query 11 Petitioner argues that the relevant specifications do not include an embodiment that “guarantee[s]” that an entry in its database is online, and, therefore, Patent Owner’s argument does not distinguish the ’704, ’469, and ’121 patents over the prior art. Addʼl Br. 6‒7. However, such an argument goes towards whether there is written description and enablement support for the claims. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time that the query is transmitted to the server.” Id. at 1363. Petitioner and Patent Owner argue that the limitations “on-line status” and “is accessible” have the same meaning as “is connected to the computer network.” See 209 Pet. 35–36; 209 PO Resp. 36‒48; 198 Pet. 35–36; 198 PO Resp. 35‒46; 196 Pet. 29; 196 PO Resp. 38‒51. Similar to “is connected to a computer network,” the “on-line status” and “is accessible” of the second process are recited in the present tense, and therefore must be claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter partes review.” Straight Path, 806 F.3d at 1363. We similarly do not determine whether this claim limitation is supported by the specifications of the ʼ704, ʼ469, and ʼ121 patents. determined at the time of the querying whether the second process “is accessible” or selecting of the process having an “on-line status.” Therefore, we construe “on-line status” and “is accessible” as having the same meaning as “is connected to the computer network.”” slip op. at 12

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1004, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to WINS, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.” Given that the combination of WINS and NetBIOS fails to teach or suggest the claims as construed, we need not reach the remaining arguments presented by Petitioner and Patent Owner.” slip op. at 23

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

    “unpatentable under 35 U.S.C. § 103(a) as obvious over WINS, NetBIOS, and Pinard, and claim 5 of the ’469 patent is unpatentable under 35 U.S.C. § 103(a) as obvious over WINS, NetBIOS, and Palmer. 198 Pet. 37–47, 54‒ 55, 58‒59. For claims 1, 2, and 5, Petitioner provides citations for where each claim limitation is disclosed by WINS and NetBIOS. Id. Petitioner also articulates reasoning with rational underpinnings why a person of ordinary skill in the art at the time of the invention would have combined the teachings of WINS and NetBIOS. Id. See KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007) (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We determine the record supports Petitioner’s contentions and adopt Petitioner’s contentions discussed below as our own. Furthermore, we have reviewed the Petition and supporting evidence and determine that Petitioner has shown by a preponderance of the evidence that claims 1, 2, and 5 of the ’469 patent would have been obvious over WINS and NetBIOS. See id.” slip op. at 25

  Patent outcomesUS 6,131,121 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,131,121

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.