- PTAB · May 7, 2025 · IPR2021-00906 · APJ Jameson Lee · IPR · Remand
On remand, the Board denied the motion to amend with proposed substitute claims 69, 70, 77, and 78 because the ’872 application did not provide written-description support.
RulingsRemand decision- RemandOther
“for the Federal Circuit. Papers 75–78. On February 3, 2025, the Federal Circuit issued a decision in which it stated: “We vacate and remand the Board’s decision with regard to claims 69 and 77, and their dependent claims, but otherwise affirm.” Paper 80.3 The formal mandate from the Federal Circuit was issued on March 12, 2025. Paper 79.” slip op. at 3
- 112 supportMotion to amend, deniedDenied
“Per the Federal Circuit’s instruction, the “first message” must come before the “another message” and “message preceding the another message.” However, the “first message” identified by Patent Owner, i.e., the RRC Connection Setup message, occurs after what Patent Owner identifies as the “another message,” i.e., the RRC Connection Request message. That mismatching sequence is evident from Figure 15 reproduced above.” slip op. at 8
NonePatents in suitUS 7,580,388 - PTAB · Jul 28, 2023 · IPR2022-00483 · APJ Jon M Jurgovan · IPR · Final written decision
The Board cancelled original claims 1–18 and 20–22, but denied substitute claims 23–43 for lack of written-description support.
RulingsFinal written decision- 112 supportMotion to amend, deniedDenied
“37 C.F.R. §§ 42.121(b)(1) and (2). The patent owner bears the burden to show, by a preponderance of the evidence, that a motion to amend complies with these requirements. 37 C.F.R. § 42.121(d)(1). “[T]he motion [to amend] must set forth written description support for each proposed substitute claim as a whole, and not just the features added by the amendment.” Lectrosonics, Inc. v. Zaxcom, Inc., IPR2018-01129, Paper 15, 8 (PTAB Feb. 25, 2019) (precedential). B. Lack of Written Description Support” slip op. at 9
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateNot shown unpatentable
“the ’556 application does not provide written description support for the proposed substitute claims. For limitations 23e, 30e, and 37e of respective independent proposed claims 23, 30, and 37, Patent Owner points to paragraphs 11, 37, 60, 78, 83–85, 90, 109–113, 119–130, 150, and Figure 11 of the ’556 application as providing written description support. MTA 6–7, 10, 14–15; Reply 2–3. Reviewing these paragraphs, however, we find no description of the subject matter recited in limitation 23e, which recites “responsive to determining that the [first] variation of the soft information change how the hard information is displayed at the client device, determine a second variation of the soft information.” Nor do we find in those passages written description of the subject matter recited in the similar language of limitations 30e and 37e. Specifically, paragraphs 11 and 37 of the ’556 application address prediction of the response message expected from the client device (similar to limitations 23h–23j, 30h–30j, and 37h–37j, which were added in the MTA to the original claims of the ’759 patent). Paragraphs 60, 78, 83, and 84 describe specific ways to vary soft messaging to establish secondary communications between a server and a client device to detect the presence of a malicious application. Paragraph 85 describes a priori recording of soft information variations to create large sets of composite (hard and soft) messages to be transmitted together. Paragraph 85 also states that, alternatively, the hard and soft messages may be transmitted separately. Paragraph 90 mentions use of “spaghetti” code and soft formatting to make it difficult for malicious applications to alter, replace, or counterfeit in real time. Paragraphs 109 to 113 mention various ways to vary soft information and soft messaging, such as varying or selecting different characters sets, font type, color, or weight, and point sizes from session to session, and predicting the response from the client device to compare with the actual response. Paragraphs 119 to 125 and Figure 11 address soft messaging using un-rendered page elements, and paragraphs 126 to 130 describe soft messaging using graphical elements. Paragraph 150 discusses identifying compatible soft information and selecting a variation of soft information to prevent malicious applications from reverse engineering the soft messaging used to validate communications. None of these disclosures describe the “trial and error” or “testing” approach of limitations 23e, 30e, and 37e in which, responsive to determining that a first variation of the soft information changes how the hard information is displayed at the client device, the security processor creates a second variation of soft information (which is included in the message to the client device if it does not vary how the hard information is displayed—see limitations 23f–23g, 30f–30g, and 37f–37g) to prevent a malicious application from interacting with the hard information. Accordingly, Patent Owner fails to meet its burden to show that limitations 23e, 30e, and 37e of independent proposed substitute claims 23, 30, and 37, as presented in the Motion to Amend, have written description support in the ’556 application, as required under 37 C.F.R. § 42.121(b)(2).” slip op. at 11
§ 112 disclosurePatents in suitUS 10,230,759 - PTAB · Mar 30, 2023 · DER2017-00031 · APJ Jameson Lee · DER · Final written decision
Petitioner failed to prove that any of Respondent’s claims 24–36 was derived from Petitioner’s inventor because Respondent proved earlier conception of the disclosed subject matter.
RulingsFinal written decision- BurdenNot shown unpatentable
“Conclusion As explained above, Petitioner’s proven time of conception and communication of the subject matter of “the invention disclosed to the respondent” is “February 14, 2014 4:04:17 PM EST.” Respondent’s proven time of conception of the subject matter of “the invention disclosed to the respondent” is “Feb 14, 2014 12:55 pm.” If Respondent’s time is Eastern Standard Time, then Respondent’s conception precedes Petitioner’s conception and communication by 3 hours and 9 minutes. If Respondent’s time is Pacific Standard Time, it precedes Petitioner’s conception and communication by 9 minutes. Accordingly, Petitioner has not shown that Bradley Burnam conceived of “the invention disclosed to the respondent” prior to Marc Selner’s conception of that same subject matter, and Petitioner has not shown that Bradley Burnam communicated “the invention disclosed to the respondent” to Marc Selner prior to Marc Selner’s conception of the same subject matter. As a result, Petitioner has not proven, by a preponderance of the evidence, that any one of claims 24–36 of Respondent’s Application 15/549,111 is derived from Bradley Burnam. J.” slip op. at 51
- ExcludeNot reached
“We need not decide Respondent’s Motion to Exclude because, even considering all of the evidence Respondent seeks to exclude, Petitioner still does not prevail. Further, Respondent’s reasons for excluding Exhibit 1107 do not address admissibility, but rather implicate the proper weight to give to Marc Selner’s cross-examination testimony. See, e.g, Corning Inc. v. DSM IP Assets B.V., IPR2013-00053, Paper 66 at 19 (PTAB May 1, 2014) (Final Written Decision) (“[T]he Board, sitting as a non-jury tribunal . . . is well-positioned to determine and assign appropriate weight to the evidence presented.”). Accordingly, Respondent’s Motion to Exclude is dismissed as moot.” slip op. at 52
- Expert testimonyOther
“testimony. There also is no indication that Brad Meeuwsen possessed or considered all of the evidence that is now before us, in particular Exhibits 2067, 2067A, and 2041. Further, inventorship is a legal question. Univ. of Colorado Found. Inc. v. American Cyanamid Co., 342 F.3d 1298, 1304 (Fed. Cir. 2003). Although Brad Meeuwsen as a fact witness may testify to what he heard or received from Bradley Burnam or Marc Selner, and such testimony would be probative, any testimony from Brad Meeuwsen with regard to the ultimate conclusion of inventorship carries no weight.” slip op. at 44
None - PTAB · Jan 8, 2018 · IPR2017-01692 · APJ Jameson Lee · IPR · Order
The Board granted the parties’ joint motion to terminate the proceedings before institution and granted both requests to keep the settlement agreements confidential.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“Under the circumstances, we grant the parties’ Motion to Terminate, Motion to File the Settlement Agreement as Confidential, and Motion to File the Final Settlement Agreement as Confidential in each proceeding. These proceedings are in their early stages: a decision on institution has not issued,” slip op. at 2
NonePatents in suitUS 6,138,147 - PTAB · Mar 4, 2016 · IPR2014-01368 · 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 disclose the required current connection status.
RulingsFinal written decision- 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 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.” 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. 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
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“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
- BurdenFwd mixedUnpatentable
“8. Conclusion We have reviewed the Petition and supporting evidence and find that Petitioner has shown by a preponderance of the evidence that claims 1, 2, and 5 of the ʼ469 patent are obvious over Microsoft Manual and NetBIOS, and claim 10 is unpatentable because it depends from a cancelled claim. Accordingly, we determine that Petitioner has demonstrated by a preponderance of the evidence that claims 1, 2, 5, and 10 of the ʼ469 patent are unpatentable.” slip op. at 29
Claim construction§ 103 obviousnesscites PhillipsPatents in suitUS 6,131,121 - PTAB · Sep 17, 2015 · IPR2015-00531 · APJ Patrick M Boucher · IPR · Order
The Board terminated the proceedings as to MediaTek Inc. and MediaTek USA, Inc., vacated the scheduling orders, and continued the proceedings as to Bandspeed, Inc.
RulingsOther- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingNot reached
“IPR2015-01581, and IPR2015-01582 (“the related proceedings”). In each of the related proceedings, a petition was filed by Qualcomm Incorporated on July 12, 2015, with a motion to join a respective one of these proceedings. Papers 1, 2 in each of the related proceedings. We note that the joinder motions in the related proceedings were filed before the instant motions to terminate were filed in these proceedings. Patent Owner opposes the joinder motions in the related proceedings. Paper 8 in each of the related proceedings. If the joinder motions are not granted, the related proceedings are barred under 35 U.S.C. § 315(b). See 35 U.S.C. § 315(c). Patent Owner has not yet filed a preliminary response in any of the related proceedings, the deadline for which is October 28, 2015, nor sought to expedite the related proceedings by filing a waiver under 37 C.F.R. § 42.107(b). It is thus 2 Citations are to IPR2015-00314. premature to decide the joinder motions in the related proceedings. See 35 U.S.C. § 315(c). Nevertheless, we discern no compelling interest to be served by delaying termination of these proceedings with respect to MediaTek Inc. and MediaTek USA, Inc., both of which have settled with Patent Owner. See 35 U.S.C. § 317 (“An inter partes review instituted under this chapter shall be terminated with respect to any petitioner upon the joint request of the petitioner and the patent owner unless the Office has decided the merits of the proceeding before the request for termination is filed” (emphasis added)). These proceedings are at an early stage, and no motions are pending in any of these proceedings. Under these circumstances, we determine that it is appropriate to terminate these proceedings with respect to MediaTek Inc. and MediaTek USA, Inc. We exercise the discretion afforded under 35 U.S.C. § 317(a) to decline, at this time, to terminate these proceedings with respect to Patent Owner. Because no petitioner remains in these proceedings, we vacate the Scheduling Order in each proceeding (Paper 13 in IPR2015-00314, IPR2015-00316, and IPR2015-00531; and Paper 15 in IPR2015-00315). If necessary, we will revisit scheduling for these proceedings after decisions on the joinder motions are made in the related proceedings. If appropriate, we will also revisit the Motions to Terminate as to Patent Owner after ruling on the motions for joinder in the related proceedings.” slip op. at 2
- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted in part
“The Joint Motions to Seal are granted to the extent that they request that the agreement be treated as business confidential information and be kept separate from the patent files under 37 C.F.R. § 42.74(c) but otherwise denied. The requests should not have been filed as “Motions to Seal,” which has other meaning, under 37 C.F.R. § 42.14, with respect to the underlying document in the context of the proceeding, e.g., expungement or made public under certain circumstances.” slip op. at 3
NonePatents in suitUS 8,542,643 - PTAB · Mar 6, 2015 · IPR2014-00439 · APJ Matthew R Clements · IPR · Order
The Board granted the parties’ revised joint motion and terminated the proceeding as to both parties without a final written decision.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“and that, even if the parties agree to settle any issue in a proceeding, the Board may independently determine any question of patentability. 37 C.F.R § 42.74(a). Generally, however, the Board expects that a proceeding will terminate after the filing of a settlement agreement. See, e.g., Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,768 (Aug. 14, 2012). We have not yet decided the merits of this proceeding. For example, the oral argument has not been held. The Board is persuaded that, under these circumstances, it is appropriate to terminate this proceeding as to both Petitioner and Patent Owner without rendering a final written decision. 37 C.F.R. § 42.72. ORDER Accordingly, it is: ORDERED that the revised joint motion to terminate this proceeding is GRANTED and this proceeding is hereby terminated as to both Petitioner and Patent Owner; and” slip op. at 3
NonePatents in suitUS 7,365,871 - PTAB · Nov 19, 2014 · IPR2014-00308 · APJ Kristina M Kalan · IPR · Order
The Board granted the parties’ joint motion and terminated the proceeding after settlement, before a final decision on the merits.
RulingsOther- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Petitioner filed a Petition on December 27, 2013, and Patent Owner filed a Preliminary Response to the petition on April 14, 2014. The Board instituted inter partes review on July 10, 2014. Patent Owner filed a Patent Owner Response on September 10, 2014, but Petitioner has not yet filed a Reply. This proceeding has not resulted in a final decision on the merits.” slip op. at 3
- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“Based on the facts of the case, it is appropriate to terminate the proceeding as to both Petitioner and Patent Owner. Therefore, the joint motion to terminate and the joint motion to file the release agreement as business confidential information are granted. Accordingly, it is ORDERED that the joint motion to file the release agreement as business confidential information, to be kept separate from the patent file, is granted; FURTHER ORDERED that the joint motion to terminate the proceeding is granted; FURTHER ORDERED that the proceeding is terminated.” slip op. at 3
NonePatents in suitUS 5,825,891 - PTAB · Nov 19, 2014 · IPR2014-00300 · APJ Michael W Kim · IPR · Order
The Board granted the parties’ joint motions and terminated the proceeding after settlement, before a final decision on the merits.
RulingsOther- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedOther
“Petitioner filed a Petition on December 26, 2013, and Patent Owner filed a Preliminary Response to the petition on April 14, 2014. The Board instituted inter partes review on July 9, 2014. Patent Owner filed a Patent Owner Response on September 10, 2014, but Petitioner has not yet filed a Reply. This proceeding has not resulted in a final decision on the merits.” slip op. at 3
NonePatents in suitUS 7,254,621 - PTAB · Nov 19, 2014 · IPR2014-00299 · APJ Michael W Kim · IPR · Order
The Board granted the parties’ joint motions and terminated the instituted IPR after settlement, before deciding the merits.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“Under 35 U.S.C. § 317(a), “[a]n inter partes review instituted under this chapter shall be terminated with respect to any petitioner upon the joint request of the petitioner and the patent owner, unless the Office has decided the merits of the proceeding before the request for termination is filed.” The requirement for terminating review with respect to Petitioner is met. Under 35 U.S.C. § 317(a), “[i]f no petitioner remains in the inter partes review, the Office may terminate the review or proceed to a final written decision under section 318(a).” SAP America is the sole petitioner in this review. The Board has discretion to terminate this review with respect to Clouding IP as Patent Owner.” slip op. at 2
NonePatents in suitUS 6,925,481
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.