PTAB
Advanced fields
31 decisions · 374msnewest first
  • PTAB · Aug 25, 2017 · IPR2016-01634 · APJ Meredith C Petravick · IPR · Adverse judgment

    The Board entered adverse judgment against Patent Owner on claims 1–11 after their cancellation and Patent Owner’s abandonment of the contest.

    RulingsAdverse judgment
    • Adverse judgmentAdverse judgmentGranted

      “Actions construed to be a request for adverse judgment include: . . . [c]ancellation or disclaimer of a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). Ex Parte Reexamination Certificate No. 9,187,921 C1, canceling claims 1–11 of the ’921 patent, issued on July 24, 2017. Ex. 3001; see Paper 14 (memorializing a conference call during which Patent Owner indicated that it was allowing the claims to be canceled in the reexamination intentionally). Claims 1–11 are all of the claims of the ’921 patent and all claims at issue in this inter partes review. Cancellation of claims 1–11 is construed as a request for adverse judgment. Additionally, “[a]ctions construed to be a request for adverse judgment include: . . . [a]bandonment of the contest.” 37 C.F.R. § 42.73(b)(4). Patent Owner did not file a Patent Owner’s Response or a Motion to Amend in this inter partes review by the May 17, 2017 deadline, set in the Scheduling Order (Paper 13), and did not file a paper in response to the Order to Show Cause by the August 22, 2017 deadline. Patent Owner’s lack of response is consistent with abandonment of the contest. Abandonment of the contest is construed as a request for adverse judgement. slip op. at 2

    None
    Patents in suitUS 9,187,921
  • PTAB · Dec 22, 2016 · IPR2016-01450 · APJ Bart A Gerstenblith · IPR · Institution

    The Board denied institution on all challenged claims under § 325(d), citing overlapping prior art and arguments, the pending reexamination appeal, and resource conservation.

    RulingsInstitution decision
    • PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsInstitution denied 325dInstitution denied

      “D. 35 U.S.C. § 325(d) Section 325(d) of Title 35 of the United States Code provides: “In determining whether to institute or order a proceeding under this chapter . . . the Director may take into account whether, and reject the petition or request because, the same or substantially the same prior art or arguments previously were presented to the Office.” In light of § 325(d), we consider whether the reexamination contains the same or substantially the same art or arguments as presented in the Petition.” slip op. at 10

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

      “II. CLAIM CONSTRUCTION Although Petitioner and Patent Owner present proposed constructions for several claim terms, no terms require express construction for purposes of this Decision. Pet. 15–21; Prelim. Resp. 10–23.” slip op. at 7

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

      “On August 29, 2016, Petitioner requested, via electronic mail, to file a motion to correct its identification of the real party in interest in this proceeding. In particular, Petitioner requested the addition of Baker Hughes Incorporated as a real party in interest. Petitioner indicated that Patent Owner would not oppose its request. In a responsive email on September 29, 2016, we authorized Petitioner to file a motion to correct the identified real party in interest. On October 4, 2016, Petitioner filed an Updated Mandatory Notice in which Petitioner stated that it “moves the Board to allow correction of Petitioner’s Real Part in Interest (‘RPI’) disclosure.” Paper 8, 1. Although Petitioner did not file a motion to correct as it had requested, we treat its updated mandatory notice as such and hereby grant Petitioner’s request. Accordingly, Baker Hughes Incorporated is a real party in interest in this proceeding as well.” slip op. at 3

    Claim constructionDiscretionary denial
    Patents in suitUS 6,732,817
  • 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 · Apr 20, 2016 · IPR2015-00035 · APJ Bart A Gerstenblith · IPR · Final written decision

    The Board denied cancellation of claims 1–23 because Petitioner did not show Schuck was entitled to the provisional filing date, so it was not prior art.

    RulingsFinal written decision
    • BurdenDecided for patent owner

      “as those presented in Dynamic Drinkware, with a few exceptions. The main difference is that here, Patent Owner did not have the burden to antedate Schuck because the ’455 patent was filed before the actual filing date of Schuck. The result of that difference is that the burden of production started with Petitioner and remains with Petitioner to establish that Schuck is entitled to claim priority to the ’657 provisional. Dynamic Drinkware is clear in that Petitioner is required to “compare the claims of . . . [Schuck] to the disclosure in the . . . [’657] provisional application.” Dynamic Drinkware, 800 F.3d at 1381. The Federal Circuit explained: “A reference patent is only entitled to claim the benefit of the filing date of its provisional application if the disclosure of the provisional application provides support for the claims in the reference patent in compliance with § 112, ¶ 1.” Id. (citing In re Wertheim, 646 F.2d 527, 537 (CCPA 1981)). Petitioner acknowledges that the ’657 provisional fails to provide support under § 112, first paragraph, for Schuck’s claim 1. Supp. Reply 4. Petitioner’s claim chart, submitted as “Appendix 1” to its Supplemental Reply, indicates that the ’657 provisional refers to a “doublet lens” rather than a “telephoto lens pair.” Id. at App. 1, A-5. And Petitioner does not argue that the “doublet lens” provides support for the recited “telephoto lens pair.” See generally id.” slip op. at 14

    • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted

      “It is only “confidential information” that may be protected from disclosure, 35 U.S.C. § 316(a)(7), and, even then, there is a public interest in “maintaining a complete and understandable file history” of the proceeding. Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,760 (Aug. 14, 2012). The standard for granting a motion to seal is “for good cause.” 37 C.F.R. § 42.54(a). The party moving to seal bears the burden of proof in showing entitlement to the requested relief. 37 C.F.R. § 42.20(c).” slip op. at 19

    • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for patent owner

      “as those presented in Dynamic Drinkware, with a few exceptions. The main difference is that here, Patent Owner did not have the burden to antedate Schuck because the ’455 patent was filed before the actual filing date of Schuck. The result of that difference is that the burden of production started with Petitioner and remains with Petitioner to establish that Schuck is entitled to claim priority to the ’657 provisional. Dynamic Drinkware is clear in that Petitioner is required to “compare the claims of . . . [Schuck] to the disclosure in the . . . [’657] provisional application.” Dynamic Drinkware, 800 F.3d at 1381. The Federal Circuit explained: “A reference patent is only entitled to claim the benefit of the filing date of its provisional application if the disclosure of the provisional application provides support for the claims in the reference patent in compliance with § 112, ¶ 1.” Id. (citing In re Wertheim, 646 F.2d 527, 537 (CCPA 1981)). Petitioner acknowledges that the ’657 provisional fails to provide support under § 112, first paragraph, for Schuck’s claim 1. Supp. Reply 4. Petitioner’s claim chart, submitted as “Appendix 1” to its Supplemental Reply, indicates that the ’657 provisional refers to a “doublet lens” rather than a “telephoto lens pair.” Id. at App. 1, A-5. And Petitioner does not argue that the “doublet lens” provides support for the recited “telephoto lens pair.” See generally id.” slip op. at 14

    • Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference not prior artDecided for patent owner

      “for multiple reasons. First, Petitioner acknowledges that what it refers to as “the Milburn doctrine” was codified in 35 U.S.C. § 102(e), and Petitioner does not show persuasively that we should read Milburn as requiring anything beyond application of that statutory section in light of the facts presented here. Supp. Reply 6. Second, Milburn did not address directly the question of whether an issued patent is entitled to claim priority to a provisional patent application, and, specifically, what must be shown in order to do so. Third, Schuck claims priority to not one, but three provisional applications, which was not the case in Milburn. Fourth, in Giacomini, the Federal Circuit expressly considered Milburn and stated: “An important limitation [on 35 U.S.C. § 119(e)(1)] is that the provisional application must provide written description support for the claimed invention.” Giacomini, 612 F.2d at 1383 (emphasis added). Although the Federal Circuit did not address the application of the argument—that the reference patent’s provisional application fails to provide written description support for the claimed subject matter—in Giacomini, because the appellant had waived it, the Federal Circuit’s decision acknowledges that there was an argument that could have been raised. Id. Finally, Dynamic Drinkware is directly on point and clearly establishes that Petitioner is required to show that the claimed invention of Schuck finds written description support in the ’657 provisional in order to rely on the ’657 provisional’s filing date. Dynamic Drinkware, 800 F.3d at 1381. It is undisputed that Petitioner has not done so. We find that Petitioner has not shown that claim 1 or any other claim of Schuck is supported by the ’657 provisional, and, thus, Petitioner has not shown that Schuck is entitled to claim priority to the ’657 provisional’s filing date. See Apple, Case IPR2015-00969, slip op. at 12–13. The result of our finding is that Schuck does not qualify as prior art, under § 102(e), to the ’455 patent, and, therefore, is not a reference which may be relied upon to establish the unpatentability of claims in an inter partes review. See 35 U.S.C. § 311(b) (“A petitioner in an inter partes review may request to cancel as unpatentable 1 or more claims of a patent only on a ground that could be raised under section 102 or 103 and only on the basis of prior art consisting of patents or printed publications.” (emphasis added)). Accordingly, Petitioner has not demonstrated, by a preponderance of the evidence, that: (1) claims 1–8, 10–14, and 16–22 are unpatentable as anticipated by Schuck and (2) claims 9, 15, and 23 are unpatentable as obvious over Schuck and APA.” slip op. at 16

    Patent outcomesUS 7,857,455 not shown unpatentable
    § 102 anticipation
    Patents in suitUS 7,857,455
  • PTAB · Mar 8, 2016 · IPR2015-00473 · APJ Ken B Barrett · IPR · Adverse judgment

    The Board granted Continental’s request for adverse judgment as patent owner for claims 14, 17, 27, and 31.

    RulingsAdverse judgment
    • Adverse judgmentAdverse judgmentGranted

      “A party may request judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). Pursuant to 37 C.F.R. § 42.73(b)(3), “[c]oncession of unpatentability” may be construed as a request for adverse judgment. We understand Continental to expressly request entry of adverse judgment against itself as the current patent owner. IPR2015-00481, Continental’s Ownership Statement 5. Additionally, we treat Continental’s concession that certain challenged claims are unpatentable (id. at 5; see IPR2015-00481, Paper 4 (Petition) 3–4 (challenging claims 14, 17, 31, and 33 of the ’431 patent)) as a request for adverse judgment at least as to those claims. 37 C.F.R. § 42.73(b)(3). Under these circumstances, entry of judgment adverse to Patent Owner Continental is appropriate.” slip op. at 7

    • PTAB / AIA Trials › Real party in interest / privityDecided for patent owner

      “assignment, and found that neither weighed in favor of Mr. Wingard. Id. at 9–10. The Court ultimately found, “at the time of the [bankruptcy] filing, that the patent was owned by Mr. Wingard personally, and, therefore, became part of the [Bankruptcy] Estate,” and the Court granted the Trustee’s motion to sell the patent. Id. at 10, 11; see also Ex. 1020 (Order granting the motion). The time to appeal the order has expired and no appeal was sought. Ex. 1017, 2 (citing Fed. R. Bankr. P. 8002). In an assignment dated December 17, 2015, the Bankruptcy Trustee assigned to Continental the entire right, title, and interest in the ’431 patent. Ex. 1017. An assignment from the Trustee to Continental Automotive GmbH is recorded in the USPTO at Reel/Frame 037329/0544. Ex. 3001. II. ANALYSIS In light of the Bankruptcy Court’s Order and the authorized sale of the ’431 patent, we recognize Continental as the current owner of the ’431 patent for purposes of this inter partes review proceeding. Continental asserts in the related 481 case: “because Continental is now the patent owner and has represented that the 431 patent claims are invalid, the claims should be found unpatentable either by way of a final determination or in response to a request for adverse judgment.” IPR2015-00481, Continental’s Ownership Statement 5.6 Continental also indicates that the same request” slip op. at 6

    None
    Patents in suitUS 5,530,431
  • PTAB · Mar 8, 2016 · IPR2015-00481 · APJ Ken B Barrett · IPR · Adverse judgment

    The Board granted Continental’s request for adverse judgment on claims 14, 17, 31, and 33 after Continental, as patent owner, conceded those claims were unpatentable.

    RulingsAdverse judgment
    • Adverse judgmentAdverse judgmentGranted

      “A party may request judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). Pursuant to 37 C.F.R. § 42.73(b)(3), “[c]oncession of unpatentability” may be construed as a request for adverse judgment. 5 Continental also asserts that Netlatch should be dismissed as a party and that all papers filed by Netlatch expunged. Continental’s Ownership Statement 5. Continental does not persuade us that those steps are necessary. See 37 C.F.R. § 41.14 (“The record of a proceeding, including documents and things, shall be made available to the public, except as otherwise ordered.”); Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,760 (Aug. 14, 2012) (referring to “the public’s interest in maintaining a complete and understandable file history”). We understand Continental to expressly request entry of adverse judgment against itself as the current patent owner. Continental’s Ownership Statement 5. Additionally, we treat Continental’s concession that the challenged claims are unpatentable (id. at 5; see Pet. 3–4) as a request for adverse judgment. 37 C.F.R. § 42.73(b)(3). Under these circumstances, entry of judgment adverse to Patent Owner Continental is appropriate.” slip op. at 6

    None
    Patents in suitUS 5,530,431
  • 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
  • PTAB · Oct 29, 2015 · IPR2014-00948 · APJ Jon B Tornquist · IPR · Adverse judgment

    The Board granted Patent Owner’s adverse-judgment motion, entered judgment against Patent Owner, and cancelled claims 2, 22, 23, and 25.

    RulingsAdverse judgment
    • Adverse judgmentAdverse judgmentGranted

      “A party may request entry of adverse judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). “Judgment” is defined as “a final written decision by the Board, or a termination of a proceeding.” 37 C.F.R. § 42.2. Although Patent Owner uses the term “termination” in its Motion, it did not submit the Motion under 37 C.F.R. § 42.72 and it did not explain why termination is appropriate in this circumstance. See 37 C.F.R. § 42.72 (noting that the Board may terminate a trial without rendering a final written decision “where appropriate,” such as when the trial is consolidated with another proceeding or pursuant to a settlement under 35 U.S.C. § 317(a)). Under the circumstances presented here, we see no reason not to grant Patent Owner’s Motion. Additionally, for the reasons discussed above, this Decision is a Final Written Decision, not a termination of the proceeding.1” slip op. at 3

    None
    Patents in suitUS 6,370,371
  • PTAB · Oct 29, 2015 · IPR2014-00947 · APJ Jon B Tornquist · IPR · Adverse judgment

    The Board granted Patent Owner’s motion for adverse judgment and cancelled claims 1, 23, 25, 161, 193, and 202.

    RulingsAdverse judgment
    • Adverse judgmentAdverse judgmentGranted

      “A party may request entry of adverse judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). “Judgment” is defined as “a final written decision by the Board, or a termination of a proceeding.” 37 C.F.R. § 42.2. Although Patent Owner uses the term “termination” in its Motion, it did not submit the Motion under 37 C.F.R. § 42.72 and did not explain why termination is appropriate in this circumstance. See 37 C.F.R. § 42.72 (noting that the Board may terminate a trial without rendering a final written decision “where appropriate,” such as when the trial is consolidated with another proceeding or pursuant to a settlement under 35 U.S.C. § 317(a)). Under the circumstances presented here, we see no reason not to grant Patent Owner’s Motion. Additionally, for the reasons discussed above, this Decision is a Final Written Decision, not a termination of the proceeding.1” slip op. at 3

    None
    Patents in suitUS 6,061,551

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.