- PTAB · Oct 21, 2025 · IPR2025-00057 · APJ Hung H Bui · IPR · Remand
The Board denied institution on all challenged claims because the conjunctive construction required a hardware action, which the asserted grounds did not show.
RulingsRemand decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)); see also 37 C.F.R. § 42.104(b) (requiring a petition for inter partes review to identify how the challenged claim is to be construed and where each element of the claim is found in the prior art patents or printed publications relied upon). This burden of persuasion never shifts to Patent Owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015) (discussing the burden of proof in inter partes review). A patent claim is unpatentable under 35 U.S.C. § 103(a) when the differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) when in evidence, objective evidence of nonobviousness, i.e., secondary considerations.4 Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966). Additionally, the obviousness inquiry typically requires an analysis of “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue.” KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006) (requiring “articulated reasoning with some rational underpinning to support the legal conclusion of obviousness”)). Petitioner cannot satisfy its burden of proving obviousness by employing “mere conclusory statements,” but “must instead articulate specific reasoning, based on evidence of record, to support the legal conclusion of obviousness.” In re Magnum Oil Tools Int’l, Ltd., 829 F.3d 1364, 1380 (Fed. Cir. 2016).” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“(1) The Claim Language Supports a Conjunctive Construction There is a “heavy presumption” that the terms used in claims “mean what they say and have the ordinary meaning that would be attributed to those words by persons skilled in the relevant art.” SuperGuide, at 875 (citing Tex. Digital Sys., Inc. v. Telegenix, Inc., 308 F.3d 1193, 1202 (Fed.Cir.2002)).” slip op. at 21
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“We agree with Patent Owner. First, the construction of the phrase “at least one of [A] the display, [B] the audio and [C] the hardware (HW) action” is conjunctive in light of the language of the claims and the specification of the ’887 patent. As such, Petitioner has the burden, but fails to show all three (3) components to be reproduced at Yun’s mobile device, including: [A] the display, [B] the audio and [C] the hardware (HW) action by the HW component of the mobile device. Second, as Patent Owner observes, and we agree, “Petitioner ignores the requirement for ‘the hardware (HW) action’ entirely” and does not even mention any “hardware (HW) action.” Prelim. Resp. 14 (Paper 10).” slip op. at 34
- Strike new argumentNew argument disregardedDecided for patent owner
“6 In the Petitioner’s Reply to the Patent Owner’s Preliminary Response, Petitioner presents several arguments to address the Fintiv factors, Apple Inc. v. Fintiv, Inc., IPR2020-00019, Paper 11 (Mar. 20, 2020) (precedential) (“Fintiv”). In support of Factor 6, Petitioner argues for the first time that Overton (not Yun or Lu) is allegedly teaching “the hardware (HW) action” aspect of the claims. Prelim. Reply 5 (citing Ex. 1006, 11:13–24 “force feedback . . . to the input devices 142 [shown in Figure 1]”). However, we decline to consider this belated argument raised for the first time in the context of a Fintiv analysis instead of the Petition.” slip op. at 41
Claim construction§ 103 obviousnessDiscretionary denialcites Phillips · KSR · GrahamPatents in suitUS 8,934,887 - PTAB · Jan 21, 2025 · IPR2023-01458 · APJ Meredith C Petravick · IPR · Remand
On remand, the Board denied institution because the petition failed to show a reasonable likelihood that any challenged claim was unpatentable, including over Hall and Borowski.
RulingsRemand decision- RemandOther
“We entered a first Decision Denying Institution of Inter Partes Review (Paper 8), and Petitioner filed a Request for Director Review (Paper 13). The former Director of the United States Patent and Trademark Office vacated our denial of institution and remanded for further proceedings consistent with the former Director’s decision. Paper 14. After considering the Petition, the Preliminary Response, the Director’s Review Decision, and the post Director’s Review Supplemental Briefing (Papers 16 and 17), and the evidence of record, we determine the information presented fails to show a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of at least one of the challenged claims of the ’236 patent.” slip op. at 2
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“After considering the Petition, the Preliminary Response, the Director’s Review Decision, and the post Director’s Review Supplemental Briefing (Papers 16 and 17), and the evidence of record, we determine the information presented fails to show a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of at least one of the challenged claims of the ’236 patent. Under 35 U.S.C. § 314(a), an inter partes review may not be instituted unless the information presented in the petition “shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” Accordingly, we do not institute an inter partes review of the ’236 patent.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner asserts: “A [person of ordinary skill in the art (‘POSITA’)] as of August 24, 2016 would have had an undergraduate degree in mechanical engineering, electrical engineering, or physics, and two to three years of experience in LiDAR design.” Pet. 9 (citing Ex. 1003 ¶¶ 59–64). Patent Owner does not dispute Petitioner’s definition of a POSITA. Prelim. Resp. 9. For purposes of this Decision, we adopt Petitioner’s assessment of the level of ordinary skill in the art, as it is consistent with the ’236 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“37 C.F.R. § 42.100(b). In applying this standard, we generally give claim terms their ordinary and customary meaning as would be understood by a person of ordinary skill in the art at the time of the invention and in the context of the entire patent disclosure. See id.; Phillips v. AWH Corp., 415 F.3d 1303, 1312–14 (Fed. Cir. 2005) (en banc). We do not need to construe any terms explicitly to reach our decision. See Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))); see also Pet. 10 (“[N]o formal constructions are necessary.”); Prelim. Resp. 10 (“[N]o formal constructions are necessary.”).” slip op. at 11
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,422,236 - 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 · Jan 10, 2018 · IPR2016-01404 · APJ Kamran Jivani · IPR · Final written decision
The Board found claims 1, 2, 13, 14, 33, 34, 39, 46, and 48 not shown unpatentable: Bensimon did not disclose the claimed restricted-access mode, and Takahashi did not cure that deficiency.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioner states––and Patent Owner does not dispute––that “a person having ordinary skill in the art of secure computer data storage devices (i.e. in the art for the ’459 patent) would have had (i) a B.S. degree in electrical engineering, computer engineering, computer science, or equivalent training, and (ii) approximately two years of experience in the design or research of secure computer data storage devices.” Pet. 4 (citing Ex. 1002 ¶ 32). We agree with Petitioner’s statement of the level skill of an ordinary artisan at the time and adopt it as our own. Although Patent Owner does not directly address an ordinary artisan’s level of skill, Petitioner’s description of the level of skill accords with that of Patent Owner’s witness Dr. Goldschlag. Compare id., with Ex. 2004 ¶ 21 (opining that “one of ordinary skill in the art would have had a Bachelor’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent training, as well as two to three years of technical experience in the field of computer security and storage devices.”). We further find the level of ordinary skill in the art is reflected by the prior art of record. See Okajima v. Bourdeau,” slip op. at 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“within an electronic circuit embedded within the storage device.” Ex. 1001, 9:58–59, 10:34–35. Although these claims are not at issue in this case, they evince the patentee’s desire to employ each of the terms “unique” and “specific” where each is intended. It is well established that ordinarily different claim terms are presumed to have different meanings. Applied Med. Res. Corp. v. U.S. Surgical Corp., 448 F.3d 1324, 1333 n.3 (Fed. Cir. 2006) (“[T]he use of two terms in a claim requires that they connote different meanings. . . .”); CAE Screenplates Inc. v. Heinrich Fiedler GmbH, 224 F.3d 1308, 1317 (Fed. Cir. 2000) (“In the absence of evidence to the contrary, we must presume that the use of these different terms in the claims connotes different meanings.”). Further, the Specification describes that, depending on the selected security level, a cryptographic key can be generated using in part “device-specific security information derived from the unique format information of the removable storage device.” Ex. 1001, 3:66–4:1. The Specification thus describes the format information of the removable storage device as “unique” but describes the security information of the device merely as “specific,” not “unique.” Finally, the Specification discloses “for exemplary purposes only” an embodiment wherein “a unique, device-specific security information can be generated from the unique characteristics of the underlying storage medium.” Id. at 7:43–47 (emphasis added). The Specification thus describes device-specific security information as unique in a particular, non-limiting example and explicitly indicates that the device-specific security information derived in that example is “unique.” See id. In light of the foregoing description, we disagree with Patent Owner’s arguments that “specific” in the context of the claim term “device-specific security information” means unique. Construing “specific” to mean “unique” as Patent Owner urges would render meaningless the subsequent use of “unique” in claims 9 and 17, without a clear indication in the Specification of such an intent. See In re Paulsen, 30 F.3d at 1480. Instead, we accord the word “specific” its ordinary and customary meaning and construe “device-specific security information” as meaning “information particular to, but not necessarily unique to, a storage device and used to secure access to the storage device.” Although we construe the disputed term “device-specific security information,” our determination that Petitioner has failed to show by a preponderance of the evidence that any of the Instituted Claims are unpatentable is not dependent upon our construction, as detailed below.” slip op. at 10
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“Petitioner has not identified in Bensimon explicit or inherent disclosure of the claimed restricted-access mode. Claim 1 requires operating in restrictedaccess mode “when the storage device does not have the device-specific security information.” Ex. 1001, 9:24–26. Petitioner identifies Bensimon’s read/write password, either alone or in combination with the password-enabling flag, as meeting the claimed device-specific security information. Reply 13; Pet. 22. Thus, in order to meet the requirements of claim 1, Petitioner is required to show that Bensimon discloses operating in restricted-access mode when the storage device does not have the read/write password, or alternatively does not have the combination of the read/write password and password-enabling flag. See, e.g., In re Bond, 910 F.2d at 832 (Fed. Cir. 1990) (holding that in order to show anticipation, claimed elements must be arranged as required by the claim). Petitioner does not make the required showing. As Petitioner argues: “these claims recite operating in one mode if ‘the device-specific security information’ (i.e., that instance of device-specific security information) is present, and operating in another mode if ‘the device-specific security information’ (i.e., that instance of device-specific security information) is not present.” Reply 16. Petitioner identifies Bensimon’s read/write password, alone or in combination with the password-enabling flag, as the device-specific security information, yet Petitioner does not identify in Bensimon an explicit disclosure that Bensimon’s storage device operates in the claimed restricted-access mode when the read/write password is absent from the device. See id. at 16–22. Rather, Bensimon describes two different possible modes of operation when the read/write password is absent from the storage device, namely either no protection or write protection. Ex. 1004, 5:33–39, 6:3–4, 6:13–29. Contrary to the claim language, operation in Bensimon’s write protection mode depends upon the presence of the write protection password, not upon the absence of the read/write password and password-enabling flag (i.e. the claimed device-specific security information). Ex. 1004, 6:13–23; see also Reply 16 (citing Ex. 1012 ¶ 18) (asserting the claimed restricted-access mode is met “when Bensimon’s storage device 100 only has the write-protection (read-only) password”). This disclosure is insufficient to establish anticipation because claim 1 requires operating in restricted access mode when the storage device does not have the device-specific storage information, which Petitioner asserts is the read/write password and password-enabling flag. “A claim is anticipated only if each and every element as set forth in the claims is found.” Verdegaal Bros., Inc. v. Union Oil. Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). We similarly are not persuaded that Bensimon inherently anticipates claim 1. “Under the principles of inherency, if the prior art necessarily functions in accordance with, or includes, the claimed limitations, it anticipates.” In re Cruciferous Sprout Litig., 301 F.3d 1343, 1349 (Fed. Cir. 2002) (citations and internal quotation marks omitted). Here, the cited disclosure identifies two possible modes of operation when the read/write password and password-enabling flag are absent from Bensimon’s storage device, neither of which necessarily must occur.” slip op. at 16
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableNot shown unpatentable
“E. Obviousness of Claims 2 and 34 based on Bensimon in combination with Takahashi Petitioner asserts dependent claims 2 and 34 would have been obvious in light of Bensimon and Takahashi. Pet. 36–40 (analysis of claim 2) and 42–43 (analysis of claim 34). Petitioner’s analysis of these claims does not repair the deficiencies described above with regard to the claimed restrictedaccess mode. See id.; see also Reply 25. Accordingly, for the reasons discussed above in the context of claim 1 and based on the full trial record, we determine that Petitioner has failed to show by a preponderance of the evidence that claims 2 and 34 would have been obvious in light of Bensimon and Takahashi. See supra Section III.D.2.” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites GrahamPatents in suitUS 6,968,459 - 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 · Feb 4, 2014 · IPR2013-00329 · APJ Justin T Arbes · IPR · Order
The Board granted the parties’ joint motion to terminate the instituted trial based on settlement, without a final written decision.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“JUDGMENT Termination of the Proceeding 37 C.F.R. § 42.73 On January 31, 2014, the parties filed a joint motion (Paper 19) to terminate the instant proceeding on the basis of a settlement reached by the parties. See 35 U.S.C. § 317(a); 37 C.F.R. § 42.72. The parties also filed a copy of their written settlement agreement (Exhibit 2002) and a request” slip op. at 1
NonePatents in suitUS 6,252,964 - PTAB · Feb 4, 2014 · IPR2013-00328 · APJ Justin T Arbes · IPR · Order
The Board granted the parties’ joint motion and terminated the instituted proceeding based on settlement, without a final written decision.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“instituted a trial on November 29, 2013, and Patent Owner has not yet filed its response or any motion to amend claims. The parties further represent that they have agreed to dismissal of the pending district court litigation between the parties involving Patent 6,744,892 B2. See Paper 22 at 2. The parties identify no other related matters. Under the circumstances, the Board determines that it is appropriate to terminate the trial without rendering a final written decision. See 37 C.F.R. § 42.72.” slip op. at 2
NonePatents in suitUS 6,744,892
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.