PTAB
Advanced fields
7 decisions · 471msnewest first
  • PTAB · Jun 17, 2021 · IPR2020-00300 · APJ Amber L Hagy · IPR · Final written decision

    Claims 1 and 21–26 were held unpatentable as obvious over Huber, Everett, and Lexer; claims 2, 27, 40, and 42 were not shown unpatentable. Substitute claims 44 and 45 were entered.

    RulingsFinal written decision
    • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed

      “(7) Claim 1 Conclusion After having analyzed the entirety of the trial record and assigning” slip op. at 31

    • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted

      “For the above reasons, Petitioner has not met its burden to” slip op. at 72

    Patent outcomesUS 8,690,330 mixed
    § 103 obviousnesscites Phillips · KSR · Graham · Nautilus
    Patents in suitUS 8,690,330
  • PTAB · Jan 11, 2021 · IPR2019-01234 · APJ Sheila F Mcshane · IPR · Final written decision

    Claims 2–5, 15–17, 23–26, 29, and 30 are unpatentable over the stated obviousness grounds; claims 8, 9, 19, 20, 27, and 28 were not shown unpatentable.

    RulingsFinal written decision
    • Skill levelSkill level petitioner adoptedDecided for petitioner

      “In the Decision on Institution, we adopted Petitioner’s proposed skill level, that is, that one of ordinary skill in the art would have a Bachelor’s degree or equivalent in electrical engineering, computer engineering, or similar field, and at least two years of experience in a relevant field such as telecommunications or multimedia communications. Inst. Dec. 20. We also agreed with Petitioner that one of ordinary skill would have some familiarity with the design and implementation of VoIP and multimedia networks. Id. We did not agree, however, that the level of qualifications included monitoring and maintaining VoIP and multimedia networks, as Petitioner asserted, and therefore declined to adopt those requirements. Id. ordinary skill in the art adopted in the Decision on Institution to include “familiarity with the design and implementation of VoIP and multimedia networks,” but further described this requirement to include other requirements: an understanding of the techniques employed by network firewalls and the issues they present with respect to establishing and conducting multimedia communication sessions; an understanding of the performance demands placed on the network by multimedia communications, and the constraints that such demands place on processing and security measures that could be adopted; and a recognition of the distinctions between prior art firewall traversal solutions and the inventions of the ’978 Patent. PO Resp. 21–22. Patent Owner refers to GPAC, which identifies the factor of the “type of problems encountered in the art” as a consideration in determining the level of ordinary skill in the art. Id. at 22 (citing In re GPAC, 57 F.3d 1573, 1579 (Fed. Cir. 1995)). We have reviewed the relevant technology and claims of the ’978 patent, as well as the technology of the asserted prior art, and we adopt the same qualifications as those adopted in the Decision on Institution because they are commensurate with the relevant technology. These qualifications are similar to presented by Petitioner, with the” slip op. at 8

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

      “Petitioner relies on the ordinary and customary meaning of the claim terms as understood by one of ordinary skill in the art. Pet. 20. Patent Owner indicates that its arguments are also based upon the ordinary and customary meaning of the terms as they would be understood by one of ordinary skill in the art. PO Resp. 22. We determine that it is not necessary to provide an express interpretation of any of the terms of the claims. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017); Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”).” slip op. at 11

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed

      “As discussed above, we agree with Petitioner that Kirchhoff discloses the use of SSL, a protocol that uses data encryption (Ex. 1005, 8:47–49). We also agree with Petitioner that Krtolica discloses the use of HTTP protocols on port 80 (Ex. 1004, 6:23–24), and does so with a goal of maintaining high network security (id. at 1:7–10, 2:33–36). As Kirchhoff discloses, and Dr. Lavian’s testimony supports, one of ordinary skill in the art would have been aware that port 443, rather than port 80, would be used for secure web connections using SSL, which includes the use of encryption, and this would have resulted in enhanced network security. See Ex. 1005, 3:38–41; Ex. 1002 ¶¶ 52, 69, 108. As Dr. Lavian testifies, SSL/TLS was the most widely deployed security protocol in the world and the well-known use of SSL in HTTPS protocol enables secure web-based e-commerce. Ex. 1002 ¶¶ 69, 108; Ex. 1035 ¶ 8; Ex. 1006, 5. And, Krtolica has a stated goal to maintain network security. Ex. 1004, 1:7–10, 2:33–37. We find this evidence provides a sufficient rational underpinning in support of obviousness for combining the teachings of Krtolica and Kirchhoff. See KSR, 550 U.S. at 418. Owner’s arguments that use of encryption in SSL was optional and adding encryption would allegedly undermine network security. Nor do we find persuasive the argument that the Petitioner’s motivation to combine based on efficiency is insufficient, because Petitioner relies on another rationale for the combination of Krtolica and Kirchhoff, that is, enhanced network security, also discussed above. We additionally do not find persuasive Patent Owner’s arguments that combining Krtolica and Kirchhoff would render the system of Krtolica unsatisfactory for its intended purpose because, as Petitioner argues, this assertion is contradicted by the state of the art at the time. See Pet. Reply 9. As discussed above, Dr. Lavian explains that there were known systems having firewalls with SSL traversal at the time of the invention. Ex. 1002 ¶¶ 53, 59–65; Ex. 1035 ¶ 20; Ex. 1014. Moreover, the ’978 patent uses encryption with firewalls using a single-port protocol, and Patent Owner does not direct us to any disclosure in that patent that indicates that the use of encryption with a single-port protocol was inventive in that the system, or that encryption had to be done in a special manner. See Pet. Reply 3 (citing Ex. 1001, Fig. 3 (at 311, 341), Fig. 5 (503, 508)); see also Ex. 1001, 6:4–8. In a similar vein, Patent Owner argues that due to incompatibilities the combination of SSL with Krtolica would be unsuccessful, and we address this issue below.” slip op. at 30

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

      “Where the prior art contains “apparently conflicting” teachings (i.e., where some references teach the combination and others teach away from it) each reference must be considered “for its power to suggest solutions to an artisan of ordinary skill . . . consider[ing] the degree to which one reference might accurately discredit another.” In re Young, 927 F.2d 588, 591 (Fed. Cir. 1991). In Hosner, AES encryption appears to have one of the higher processing speeds of the algorithms tested. See Ex. 1006, 23. Further, the ’978 patent itself supports the acceptable performance of AES encryption in single-port protocol, stating that “[a]ny method or algorithm of encryption may be used” with its invention “including, but not limited to 128-bit find Patent Owner’s argument on the use of AES to be persuasive. We have reviewed Petitioner’s explanations and supporting evidence as to how the combination of Kirchhoff and Krtolica teach the limitations of claims 4, 16, and 24, and we agree with and adopt Petitioner’s analysis. Pet. 75–76, 81.” slip op. at 65

    Patent outcomesUS 7,710,978 mixed
    Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 7,710,978
  • PTAB · May 23, 2019 · IPR2018-00180 · APJ Kamran Jivani · IPR · Final written decision

    Claims 4–7, 9–16, and 18 are unpatentable over Hwang or Hwang and Balakrishnan; claim 17 was not shown unpatentable over Hwang.

    RulingsFinal written decision
    • Skill levelSkill level patent owner adoptedDecided for patent owner

      “Although the parties formulate slightly differently their respective assessments of the skill level, neither party disputes directly the other’s assessment nor makes any arguments related to the assessments. See generally Pet.; PO Resp. The ’221 patent states its disclosure “relates, in general, to integrated circuits and, more particularly, to power converter integrated circuits.” Ex. 1001, 1:9–11. In view of the foregoing, we adopt Patent Owner’s formulation of the level of ordinary skill in the art. Further, this level of ordinary skill is reflected by the prior art of record. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art itself can reflect the appropriate level of ordinary skill in the art).” slip op. at 8

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

      “construction must begin with the words of the claims themselves.”); In re NTP, Inc., 654 F.3d 1279, 1288 (Fed. Cir. 2011) (citing Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005) (en banc)) (“As with any claim construction analysis, we begin with the claim language.”). None of the challenged claims (nor even unchallenged claim 8) recites the claimed disabling or terminating occurs in response to the detect signal independent of other circuit conditions or in response only to the detect signal. See Ex. 1001, 12:5–14:36. For instance, independent claim 4 merely recites, “wherein the control circuit disables the switched drive control signal in response to the detect signal.” Id. at 12:49–51. Independent claim 7 similarly recites, “wherein the gating circuit disables the drive control signal in response to the detect signal.” Id. at 13:11–13. Independent claim 9 discloses only, “a first comparator . . . having an output for disabling the pulse generator.” Id. at 13:27–30. Finally, independent claim 15 requires, “comparing the error signal to a reference signal . . . to terminate the step of generating in response to the error signal.” Id. at 14:21–23. Therefore, the plain language of the challenged claims does not, standing alone, support adoption of Patent Owner’s proposed construction.” slip op. at 13

    • Expert testimonyPetitioner expert creditedDecided for petitioner

      “testimony from their respective declarants on whether one of ordinary skill in the art would understand “in response to” as requiring “independent of other circuit conditions.” Compare Reply 2–3 (citing Ex. 1016 ¶¶ 18–21, 26–30; Ex. 2003, 43:16–45:1) with PO Resp. 14–15, 17 (citing Ex. 2001 ¶¶ 42, 44–45.) and Sur-Reply 11–12 (citing Ex. 2001 ¶ 45). Patent Owner further directs our attention to a single sentence of deposition testimony in which Petitioner’s declarant Dr. Szepesi appears to agree with Patent Owner’s construction by stating, in the context of claim 9, that “the output signal of this first comparator disables the output pulses driving the gate of that independent of anything else.” PO Resp. 8 (citing Ex. 2003, 44:16– 45:1). Petitioner rebuts Patent Owner’s arguments by identifying additional deposition testimony and statements made in a second declaration offered by Dr. Szepesi opposing Patent Owner’s construction. Reply 2–3 (citing Ex. 1016 ¶¶ 18–21, 26–30; Ex. 2003, 43:16–45:1). For instance, immediately before the statement Patent Owner cites, Dr. Szepesi testified: Q: “So is it your opinion that an output for disabling the pulse generator must disable the pulse generator regardless of the other conditions in the circuit?” . . . A: “I don't understand your question. I said disabling the pulse generator means that the output of the pulse generator which is providing the pulses to the gate of the main switch, those pulses are disabled. That’s what it means in my opinion in this context.” Ex. 2003, 43:24–44:9. And, in his supplemental declaration, Dr. Szepesi states: As a first matter, I opined during my deposition that “an output disabling a pulse generator” means that “the output signal of this first comparator disables the output pulses driving the gate of that independent of anything else.” But, at the time of my deposition I had not done a focused claim construction analysis of the limitation “a first comparator […] having an output for disabling the pulse generator.” This is because I hadn’t anticipated there being a dispute relevant to the validity analysis in view of what I understood as the plain meaning of the language. Despite the quote that Patent Owner relied upon, I believe now that a POSITA would not understand the claim language to require the first comparator to disable the output pulses independent of anything else. This belief is consistent with my responses to the first two of three successive questions in which I was asked about “disabling the pulse generator.” It is my opinion that the operation of the disclosed embodiment requires the presence of other conditions precedent before the first comparator can disable the drive pulses and this requirement is not excluded by the claim language. Ex. 1016 ¶ 18 (emphasis added). Our reviewing court has made clear that extrinsic evidence “is generally of less significance than the intrinsic record” in matters of claim construction. Wi-LAN, Inc. v. Apple Inc., 811 F.3d 455, 462 (Fed. Cir. 2016) (citation omitted). Here, beyond competing declarant testimony, neither party has entered into the record extrinsic evidence, such as dictionary definitions or contemporaneous usage in the art, addressing the scope of “in response to.” Having considered the testimony upon which Patent Owner relies and weighing it against the claim language itself, the Specification’s disclosures set forth above, and the contrary testimony of Petitioner’s declarant, we find on balance that it does not warrant departing from the plain and ordinary meaning of “in response to” as Patent Owner urges. See In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994) (holding that an inventor may define specific terms used to describe invention, but must do so “with reasonable clarity, deliberateness, and precision”) (quoting Intellicall, Inc. v. Phonometrics, Inc., 952 F.2d 1384, 1387-88 (Fed. Cir. 1992)).” slip op. at 17

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “Claim 4 further recites, “a control circuit having an input coupled for receiving the detect signal, wherein the control circuit disables the switched drive control signal in response to the detect signal.” Patent Owner’s sole contention with respect to claim 4 is that “[t]he alleged detect signal in Hwang does not satisfy this limitation” because “unlike the ’221 patent, the alleged ‘control circuit’ does not disable the switched drive control signal ‘in response to the detect signal’ independent of other circuit conditions.” PO Resp. 15–16. As discussed above, we decline to import into claim 4 a requirement that the claimed disabling must occur independent of other circuit conditions. See supra Section III.C.1. Because Patent Owner’s argument relies on a claim construction that we rejected above, we are not persuaded that Hwang fails to meet the limitations of claim 4. Rather, having reviewed the evidence cited by Petitioner, we agree with Petitioner that Hwang discloses the limitations of independent claim 4, arranged as recited in the claim. Petitioner’s analysis, as supported by the Szepesi Declaration, further demonstrates where Petitioner contends each element of dependent claims 5 and 6 is disclosed in Hwang. Pet. 21–24. Patent Owner does not dispute Petitioner’s analysis beyond the argument raised with respect to claim 4. See PO Resp. 17. Having reviewed the evidence cited by Petitioner, we agree with Petitioner that Hwang discloses the limitations of dependent claims 5 and 6, arranged as recited in these claims, and we adopt that analysis as our own. Accordingly, for the foregoing reasons, we find Petitioner has shown by a preponderance of the evidence that Hwang anticipates claims 4–6.” slip op. at 25

    Patent outcomesUS 6,597,221 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 6,597,221
  • Qualcomm Inc. v. Bandspeed, Inc.Some claims unpatentable
    PTAB · Sep 7, 2016 · IPR2015-01580 · APJ Patrick M Boucher · IPR · Final written decision

    Claims 5, 6, 8, 17, 18, and 20 are unpatentable; claims 7 and 19 were not shown unpatentable because Cuffaro does not disclose a specified number of votes and the obviousness testimony was insufficient.

    RulingsFinal written decision
    • PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted

      “After institution, Qualcomm Inc. filed substantially the same petition in IPR2015-01580 (IPR2015-01580, Paper 1), together with a Motion for Joinder of IPR2015-01580 with the instant proceeding (IPR2015-01580, Paper 2). On September 17, 2015, we granted a motion to terminate this proceeding with respect to MediaTek Inc. and MediaTek USA, Inc., but not as to Patent Owner, leaving only Patent Owner as a party to the proceeding. Paper 22. On November 16, 2015, we granted Qualcomm Inc.’s Motion for Joinder, joining Qualcomm Inc. to the instant proceeding. Paper 23. Qualcomm Inc. (“Petitioner”) is now the sole petitioner.” slip op. at 2

    • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesTerm construed petitioner constructionDecided for petitioner

      “phrase “means for . . . .” Petitioner construes these terms in accordance with 35 U.S.C. § 112 ¶ 6, identifying an algorithm described in the specification corresponding to each “means” limitation. Pet. 7–9 (citing Ex. 1001, col. 8, l. 8–38, col. 8, ll. 49–col. 9, l. 16, col. 19, l. 25–col. 20, l. 67). Petitioner identifies a general purpose computer, processor 704 in Figure 7, as structure for “executing the instructions associated with the corresponding function” recited in each “means limitation,” except for the “means fro [sic] the first participant to communicate . . .” recited in claims 5 and 20. Pet. 7–9 (citing Ex. 1001, Fig. 7, col. 25, ll. 13–18). For the “means fro [sic] the first participant to communicate” limitation, Petitioner identifies transceiver 216, shown in Figure 2, reproduced supra. Pet. 9 (citing Ex. 1001, Fig. 2, col. 9, ll. 54–59). Patent Owner does not contest these identifications. We agree with Petitioner’s identifications and adopt them as our constructions of the means-plus-function limitations. Specifically, as to those means-plus-function limitations that correspond to processor 704 in Figure 7, Petitioner identifies in its claim chart the algorithm described in the specification for performing each function of these means. Pet. 8–9; See also Function Media, L.L.C. v. Google, Inc., 708 F.3d 1310, 1318 (Fed. Cir. 2013) (“When dealing with a ‘special purpose computer-implemented means-plus-function limitation,’ [the Federal Circuit] require[s] the specification to disclose the algorithm for performing the function.”); Blackboard, Inc. v. Desire2Learn, Inc., 574 F.3d 1371, 1384 (Fed. Cir. 2009) (“[W]hen a computer is referenced as support for a function in a means-plus-function claim, there must be some explanation of how the computer performs the claimed function.”).” slip op. at 8

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

      “We are not persuaded by this reasoning. As Petitioner observes, the embodiments of the ’624 patent identified by Patent Owner are characterized as “examples,” and a person of ordinary skill “would understand that the example scenarios of the specification are not necessarily limiting on the claims.” Reply 3 (citing Ding Supp. Decl. ¶ 6). In addition, Petitioner notes that claim language in related patents owned by Patent Owner explicitly refers to participants, evidencing Patent Owner’s understanding “how to expressly create participant-specific voting requirements in claims.” Id. at 3. At the oral hearing, Patent Owner suggested that explicit reference to participants in such other claim language “was because it wanted to clarify that each participant got a single vote,” and explained its position that, in the claims at issue in this proceeding, “participant is implicit in the claim language as it is.” Tr. 78:16–25. But the claims are directed to a “communications apparatus,” and recite “votes” in the context of what the “particular communications channel” “receives.” Nothing within the structure of the claims requires resolving the origin of such votes. Furthermore, Patent Owner’s proposed construction is inconsistent with the construction it agreed to before the district court in the Qualcomm Litigation. In that litigation, the parties agreed that the term “vote” should be construed as “a binary expression (to use or not to use),” a construction that makes no reference to the origin of the “vote” as from a participant or otherwise. Ex. 1014, 6. We see no compelling reason to excuse the inconsistency by adopting a narrower construction when the Board applies a claim-construction standard (broadest reasonable interpretation) that could only result in the same or a broader construction. See Amazon.com, Inc. v. Barnesandnoble.com, Inc., 239 F.3d 1343, 1351 (Fed. Cir. 2001) (“A patent may not, like a ‘nose of wax,’ be twisted one way to avoid anticipation and another to find infringement.” (quoting Sterner Lighting, Inc. v. Allied Elec. Supply, Inc., 431 F.2d 539, 544 (5th Cir. 1970))). Accordingly, we construe “votes to use a particular communications channel” as “expressions of preference for using the particular communications channel.”” slip op. at 10

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “Patent Owner responds that “the Gerten device is not capable of and expressly teaches away from performing this functionality.” PO Resp. 15 (citing Melendez Decl. ¶ 33). Patent Owner contends that “Gerten’s disclosure is directed toward eliminating channels for use in an entire piconet as opposed to eliminating channels for use by certain participants within a piconet.” Id. at 16 (emphasis added). Patent Owner argues that Gerten does not disclose a selection kernel capable of maintaining synchronization between a master and more than one slave in a piconet, with the master and one slave using a default set of channels while the same master and a different slave use a different set of channels. Id. We are not persuaded that the absence of a specific teaching of such a selection kernel supports the conclusion that one of skill in the art would understand Gerten to function in the manner Patent Owner suggests. In this instance, Petitioner refers to two embodiments of Gerten “in which a first participant communicates with a second participant via a normal sequence and with another participant via an adaptive hopping sequence.” Reply 5. First, Figure 3 of Gerten is reproduced below. Figure 3 illustrates “methodology for determining and communicating channels to be avoided to a remote device.” Ex. 1003, col. 2, ll. 4–6. As illustrated in the drawing, a master unit performs a discovery process (block 110) upon connecting with a new slave unit. Ding Decl. ¶¶ 60, 64. If the slave unit is capable of using interference avoidance, the master unit begins the process of determining a modified set of channels for use (block 120). Id. ¶ 45. If a second slave unable to use interference avoidance enters the piconet, standard frequency hopping is used. Supp. Ding Decl. ¶ 9. Under Patent Owner’s characterization of Gerten, entry of the second slave into the network would require the first slave necessarily to revert back to the default hopping sequence. Id. ¶ 10. But this would undermine the stated benefits of Gerten, which explicitly discloses: The above process can be applied to a Bluetooth example and includes identification of a Bluetooth device’s ability to support interference avoidance, the measurements of signal strength on all channels and identification of which channel should not be used without violating the FCC rules, a method of modifying the Bluetooth hop sequence so that it will avoid channels containing strong or fixed interferers while still supporting standard Bluetooth hopping with other non-enabled members of the piconet and a method of relating necessary interference avoidance information to the remote Bluetooth devices. Ex. 1003, col. 4, l. 66–col. 5, l. 9 (emphasis added).” slip op. at 17

    Patent outcomesUS 7,477,624 mixed
    Claim construction§ 102 anticipation§ 103 obviousness
    Patents in suitUS 7,477,624
  • PTAB · Mar 4, 2016 · IPR2015-01011 · APJ Kalyan K Deshpande · IPR · Final written decision

    Claims 1, 2, 5, and 10 of the ’469 patent are unpatentable; the remaining challenged claims were not shown unpatentable because the cited art did not establish current network connection status.

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

      “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 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 the query is transmitted to the server.” Id. at 1363. 11 Petitioner argues that the relevant specifications do not include an embodiment that “‘guarantees’ or ‘ensures’ the availability of the second process at any given point in time” and the file histories of the challenged patents “expressly reject[] the notion that the claims contain any guarantee of perfect accuracy.” Addʼl Br. 6. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter parties review.” Straight Path, 806 F.3d at 1363. We similarly do not offer any determination as to whether this claim construction is supported by the specifications of the ʼ704 patent, ʼ469 patent, and the ʼ121 patent. 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 66 Pet. 24–30; 66 PO Resp. 32‒35; 67 Pet. 25–31; 67 PO Resp. 30‒34; 68 Pet. 24–29; 68 PO Resp. 36‒42. 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 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 11

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

      “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 19

    • PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted

      “and AVAYA, Inc. (“AVAYA”) filed three Petitions and Motions to Join the IPR2014-01366, IPR2014-01367, and IPR2014-01368 proceedings. IPR2015-01011, Papers 2, 4; IPR2015-01007, Papers 3, 4; IPR2015-01006, Papers 2, 4. We granted these motions and joined Samsung, Cisco, and AVAYA (collectively, “Petitioner”) to these inter partes reviews. 66 Paper 26; 67 Paper 23; 68 Paper 25.” slip op. at 3

    Patent outcomesUS 6,108,704 mixed
    Claim construction§ 103 obviousnesscites Phillips
    Patents in suitUS 6,108,704
  • PTAB · Mar 4, 2016 · IPR2015-01007 · APJ Kalyan K Deshpande · IPR · Final written decision

    Claims 1, 2, 5, and 10 of the ’469 patent were held unpatentable; the remaining challenged claims were not shown unpatentable because the cited art did not establish current network connection status.

    RulingsFinal written decision
    • BurdenFwd mixedMixed

      “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 19

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

      “In Ancora Techs., the Federal Circuit explained that “[t]he ordinary meaning of the word ‘program’ in the computer context encompasses both operating systems and the applications that run on them (as well as other types of computer programs)” and “‘to a computer programmer’ a program is merely a ‘set of instructions’ for a computer.” Ancora Techs., Inc. v. Apple, Inc., 744 F.3d 732, 734 (Fed. Cir. 2014). Applying this guidance to the case before us, we agree with Petitioner and construe the term “process” to mean “a running instance of a computer program or application,” where a “computer program” is a set of instructions for a computer that encompasses both operating systems and the applications that run on them. We further note that the ʼ704, ʼ469, and ʼ121 patent specifications interchange the terms “process” and “processing unit.” For example, the specifications explain that a first “processing unit” is “established in the database [] as an active on-line party.” Ex. 1001, 5:29–34. The claims recite the term “process.” Accordingly, our construction is also consistent with the specifications, such that a “process” includes a “processing unit” that is running a program (operating system) or application.” slip op. at 14

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

      “Petitioner contends that “WINS is an implementation of NetBIOS” and, therefore, Petitioner contends that “one having skill in the art would have known about and been motivated to combine Microsoft Manual with NetBIOS.” Id. at 34 (citing 67 Ex. 1004 ¶¶ 88–89). We are persuaded by Petitioner that the combination is reasonable because Microsoft Manual demonstrates that Microsoft TCP/IP has combined the elements of NetBIOS and Microsoft Manual in the same manner in which Petitioner proposes to combine NetBIOS and Microsoft Manual. See 67 Ex. 1012, 3, 11. Microsoft Manual discloses that Microsoft TCP/IP for Windows NT provides support for application interfaces, including NetBIOS for establishing logical names and sessions on the network. Id. at 11. Microsoft Manual describes that “[w]hen WINS servers are in place on the network, NetBIOS over TCP/IP resolves names on a client computer by communication with the WINS server.” 67 Pet. 34 (quoting 67 Ex. 1012, 62). We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by Microsoft Manual, and a person with ordinary skill in the art would have readily combined the disclosures of Microsoft Manual and Microsoft Manual.” slip op. at 25

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

      “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual 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. 1014, 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 Microsoft Manual, 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 Microsoft Manual 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 19

    Patent outcomesUS 6,009,469 mixed
    Claim construction§ 103 obviousnesscites Phillips
    Patents in suitUS 6,009,469
  • Microsoft Corporation v. Enfish, LLCSome claims unpatentable
    PTAB · Mar 2, 2015 · IPR2013-00560 · APJ Barbara A Parvis · IPR · Final written decision

    Claims 47–48 are unpatentable as anticipated by Visual Basic, and claims 49–50 as obvious over Visual Basic and Jensen; claims 51–53 were not shown unpatentable, and claims 17–23 were terminated.

    RulingsFinal written decision
    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownNo construction neededDecided for patent owner

      “Enfish contends that our construction for “object identification number” is incomplete. PO Resp. 15. We evaluate Enfish’s contention below. Enfish also provides a proposed construction for “anchor,” recited in claims 21 and 51. PO Resp. 22. Because we determine that Microsoft has not met its burden with respect to these claims for other reasons, no construction of this term for the purposes of this Decision is necessary. We discern no reason, based on the complete record now before us, to change our constructions in the Decision to Institute of “logical table,” “object identification number,” and “attribute set.”” slip op. at 8

    • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

      “evidence, and the detailed claim analysis, which reads persuasively all elements of claim 47 onto the disclosure of Visual Basic. Pet. 33–46 (citing Ex. 1104, LR 162, 185, 280, 425, 484, 532, 558, PF 1, 3, 18, 37–39, 40, 47, 76, 80, PG 453, 471, 481, 482 ; Ex. 1119 ¶¶ 67–98). For example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses configuring memory according to a logical table, as recited in claim 47. In the cited portions above, Visual Basic discloses storing data in a computer formatted as a table object, which is “a logical representation of a physical table.” Ex. 1104, LR 558. The table object comprises “records (rows) and fields (columns).” Id.” slip op. at 16

    • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed

      “2007 ¶ 231. In contrast to Dr. Jagadish’s statement, however, Jensen teaches an object-oriented application for managing information retrieved from a structured database, such as a relational database. Ex. 1106, Abstract. Enfish further contends that Microsoft does not explain why one of ordinary skill in the art would have been motivated to apply the pointers of Jensen to the indexing structure in Visual Basic. PO Resp. 35. We, however, are persuaded that Microsoft has shown a sufficiently articulated reason with rational underpinning to support obviousness (Pet. 48–49 (citing Ex. 1119 ¶¶ 387–404)). Microsoft, for example, states “[i]t was well known in the art at the time that indexes such as the index disclosed in [Visual Basic], maintain object identification numbers of the cell for locating data.” Pet. 49 (emphasis added). Microsoft continues, “Jensen discloses containing the address in a pointer, e.g., a physical memory address (i.e., OIDs).” Id. (citing Ex. 1106, 7:29–35). Dr. Hosking testifies “[i]t was well known in the art at the time that Index Objects locate data by maintaining object identification numbers in the internal pointers as disclosed in Jensen.” Ex. 1119 ¶ 403 (emphasis added). Dr. Hosking further testifies “[a] person of ordinary skill in the art would be motivated to combine Jensen’s teaching of maintaining the OIDs in a pointer with [Visual Basic’s] disclosure of identifying the logical columns / rows with the OIDs.” Ex. 1119 ¶ 404. The predictable use of familiar prior art elements according to their established functions renders the recited invention obvious. See KSR Int’l Co. v. Teleflex, Inc., 550 U.S. 398, 417 (2007).” slip op. at 19

    • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

      “invention, the totality of the evidence submitted, including objective evidence of nonobviousness, may lead to a conclusion that the claimed invention would not have been obvious to one with ordinary skill in the art. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). However, to accord substantial weight to objective evidence requires the finding of a nexus between the evidence and the merits of the claimed invention. In re GPAC Inc., 57 F.3d 1573, 1580 (Fed. Cir. 1995); see also In re Huang, 100 F.3d 135, 140 (Fed. Cir. 1996) (“success is relevant in the obviousness context only if there is proof that the sales were a direct result of the unique characteristics of the claimed invention.”). Enfish contends that the claimed invention received industry accolades, including praise from Microsoft, satisfied a long-felt need, resulted in success where others had failed, as well as commercial success. PO Resp. 42–47. Enfish points to features of claim 17, which Enfish contends are the features of the claimed invention that resulted in the objective indicia of success to which Enfish refers. Id. at 43–44. Claim 17 of the ’775 patent, however, is challenged on the basis that it is anticipated by Visual Basic. Secondary considerations do not weigh into determinations regarding anticipation. Cohesive Techs., Inc. v. Waters Corp., 543 F.3d 1351, 1364 (Fed. Cir. 2008). Because we conclude that Microsoft has not shown that claims 51–53 of the ’775 patent are unpatentable for other reasons, the only claims that we need to evaluate are dependent claims 49 and 50 of the ’775 patent. Microsoft asserts that claims 49 and 50 are obvious over the combination of Visual Basic with a reference that teaches referencing objects through two-way pointers. Pet. 49 (citing Ex. 1106, 7:29–35). Enfish has not shown a nexus between any of the accolades or successes it says occurred and the use of two-way pointers.” slip op. at 24

    Patent outcomesUS 6,163,775 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites KSR
    Patents in suitUS 6,163,775

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.