- PTAB · Jun 30, 2022 · IPR2021-00361 · APJ Stephen E Belisle · IPR · Final written decision
Claims 1, 2, 5, 7, 14, and 17 are unpatentable as anticipated by Dukach and obvious over Dukach, alone or with Dunsmuir.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“of the invention of the ’613 patent, “would have had a Bachelor’s degree in computer science or a related field, and two years of work experience in operating systems, file systems, networks, and/or client-server applications, though additional education or work experience can make up for more or less formal education.” Pet. 20 (citing Ex. 1002 ¶ 31). Patent Owner does not present an alternative definition of the skilled artisan, and does not dispute Petitioner’s definition thereof. See generally PO Resp.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“skilled artisan to have its “ordinary and customary meaning[],” allegedly “a stream of data bytes that can be read and written (among other common operations).” PO Resp. 3. But as noted by Petitioner (Pet. Reply 3–4), the only intrinsic evidence cited by Patent Owner does not support its proposed construction in the context of the ’613 patent; rather, such evidence favors Petitioner. See PO Resp. 4 (citing Ex. 1001, 2:35–45 (a “‘file is accessed via the file descriptor’”), 2:46–3:7 (“‘the system calls that access files via file descriptors do not distinguish between a file on media and a communication channel’”)); see also PO Resp. 7 (“It is undisputed that file descriptors were conventionally ‘associated with’ files stored on media, communication channels, and even hardware devices.” (emphasis added)). Patent Owner also cites extrinsic evidence, namely, Dunsmuir (Ex. 1007), to support its proposed construction: “Conceptually, a file consists of a stream of data bytes followed by a logical end-of-file. … Because UNIX file I/O is performed through a uniform file interface, a program that can read and write files can read and write anything.” PO Resp. 4 (quoting Ex. 1007, 22). But as noted by Petitioner (Pet. Reply 4–6), Patent Owner does not explain why this “conceptual” meaning set forth in the generic context of programming interfaces in a UNIX operating system would apply in the specific context of the ’613 patent. See Pet. Reply 4 (“[Patent Owner’s] proposed construction is problematic because it is inconsistent with the specification of the ’613 patent.”). Patent Owner also does not explain what “among other common operations” means in the context of its own proposed construction. For the foregoing reasons, and those discussed below, we agree with Petitioner’s proposed construction of “file.” First, the claims of the ’613 patent support Petitioner’s proposed construction. For example, claim 1 recites that a “file” is accessed via a file descriptor. Ex. 1001, 14:55. Claim 5 recites a file descriptor being associated with “a communication channel” and determining with what file type the file descriptor is associated. Ex. 1001, 15:44–57. Together, these limitations show that a “file” is an entity assessed via a file descriptor, and such an entity includes, for example, a communication channel (i.e., per these claims, a communication channel is a type of file associated with a file descriptor). We find nothing in the claims, and Patent Owner does not direct us to anything in the claims, that supports limiting the term “file” only to a “stream of data bytes that can be read and written.”” slip op. at 20
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“in the abstract, discloses the claimed “indicator,” but rather the inclusion (or storage or presence) of that number in a list of monitored file descriptors discloses such a stored “indicator.” See, e.g., Pet. 49 (“[The skilled artisan] would have understood that, before the listen( ) call or the accept( ) call attempts to access a file using a file descriptor, it examines the file descriptor to determine if it is on the list of monitored file descriptors—the ‘indicators’ of a file type associated with the control pipe for services to be performed by the front end server.” (emphasis added)); Pet. 37–38 (“Dukach utilizes the presence or absence of a file descriptor’s number stored in a list of monitored file descriptors to indicate the file type associated with the file descriptor, which is how the ’613 patent describes indicating a file type by the indicator’s presence or absence in an indicator table.”); see also Pet. Reply 13 (“Petitioner contended in the Petition and maintains that it is the presence of a file descriptor’s number on the list of monitored file descriptors, not the file descriptor’s number itself, that teaches the claimed indicator.” (bold omitted)); cf. PO Resp. 9 (“[A]n ‘indicator’ . . . must reflect . . . an indication that such file descriptor is associated with a communication channel.”). Patent Owner also variously argues “Dukach does not disclose or” slip op. at 34
- Expert testimonyPetitioner expert creditedDecided for petitioner
“In our Institution Decision, we credited the foregoing and related testimony of Dr. Greenspun (Ex. 1002 ¶¶ 96–98), and noted that Patent Owner at that stage of the proceeding had not offered any evidence to rebut Dr. Greenspun’s testimony. Dec. 30–31. Despite that, as highlighted by Petitioner, Patent Owner still offers no evidence to rebut Dr. Greenspun’s testimony in this regard. See Pet. Reply 16 (“But in arguing all these [above arguments], [Petitioner] presents no rebuttal evidence—neither a deposition testimony of Dr. Greenspun, nor a rebuttal testimony by its own expert, nor any other evidence.”); see generally PO Resp. Instead, Patent Owner merely declares Dr. Greenspun’s testimony “conclusory” and tainted by “vague leap[s]” (see, e.g., PO Resp. 14), but yet makes such accusations against a technical declarant with nothing but attorney-argument. Regardless, for the same reasons given by Petitioner (see Pet. Reply 16–18), we disagree with Patent Owner and continue to credit Dr. Greenspun’s technical testimony as to the subject limitation. See Pet. Reply 16–18 (Petitioner explaining why “[Patent Owner’s] attorney argument is wrong”.). As noted above, Patent Owner variously argues Dukach does not disclose “storing” of the indicator at issue in this limitation. See generally PO Resp. 7–17. To summarize, we disagree with Patent Owner, and as explained above, are persuaded by Petitioner’s evidence, including the unrebutted testimony of Dr. Greenspun, that Dukach discloses storing information that points to a file type associated with a file descriptor. First, we are persuaded that, in Dukach, the presence or absence of a file descriptor’s number in the list of monitored file descriptors constitutes information that points to a file type associated with the file descriptor. See Pet. 37–40 (citing, inter alia, Ex. 1005, 11:5–40; Ex. 1002 ¶ 96; Ex. 1001, 11:12–42). Second, we also are persuaded that, in Dukach, the list of monitored file descriptors “needs to be maintained in memory such that it can be used by software to check an at-issue file descriptor’s presence or absence in the list,” which constitutes storing the indicator. Pet. Reply 16– 17 (quoting Ex. 1002 ¶ 97); see Pet. 40 (citing Ex. 1002 ¶ 97). Finally, even if Patent Owner were correct that Dukach does not disclose a particular embodiment in the ’613 patent (see, e.g., PO Resp. 15 (discussing an embodiment “only applicable for binary file types”)), the issue before us is not whether Dukach indeed discloses such an embodiment, but rather whether Dukach discloses the invention recited, for example, in claim 1, given the breadth (scope) of the limitations defining that invention.” slip op. at 37
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 6,560,613 - Andersen CorporationOtherPTAB · Mar 20, 2019 · DER2017-00007 · APJ Justin T Arbes · DER · Final written decision
Andersen did not prove derivation of any invention in claims 1–22 because it did not show that Oquendo communicated the claimed stop spaced away from the corners.
RulingsFinal written decision- BurdenDecided for patent owner
“2. Burden of Proof To prevail in an instituted derivation proceeding, the petitioner must demonstrate that “an inventor named in the earlier application derived the claimed invention from an inventor named in the petitioner’s application and, without authorization, the earlier application claiming such invention was filed.” 35 U.S.C. § 135(b). Unlike the statutory provisions governing inter partes review and post-grant review, which specify that a petitioner must prove unpatentability of a claim by a “preponderance of the evidence,” the statutory provision for derivation proceedings does not set forth an evidentiary standard for proving derivation. See 35 U.S.C. §§ 135, 316(e), 326(e). Our rules, however, provide that “[a] derivation proceeding is a trial subject to the procedures set forth in subpart A of this part [i.e., 37 C.F.R. §§ 42.1–42.80],” 37 C.F.R. § 42.400(a), and “[t]he default evidentiary standard [for trial proceedings] is a preponderance of the evidence,” 37 C.F.R. § 42.1(d).5 We apply that standard for purposes of this Decision.” slip op. at 17
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionDecided for petitioner
“construed. Andersen argues in its Petition that the term “stop” in all of the claims should be interpreted to mean “[a] physical abutment that prohibits movement of the adjoining structure beyond a predetermined location.” Pet. 9. In the Decision on Institution, based on the record at the time, we preliminarily agreed with and adopted that interpretation, and concluded that no other terms required interpretation. Dec. on Inst. 17–18.” slip op. at 20
- Expert testimonyPetitioner expert discountedDecided for patent owner
- Adverse judgmentOther
“all of the evidence of alleged communication. Taking into account the parties’ arguments and the full record in this proceeding, we conclude that Andersen has not demonstrated that Mr. Oquendo communicated to a named inventor of the ’953 patent a conception of the complete invention recited in claim 1. Specifically, Andersen has not shown that Mr. Oquendo communicated, as part of his spacer frame design, a stop spaced away from the corners. Mr. Oquendo’s testimony regarding such an alleged communication is not corroborated by evidence in the record for all of the reasons explained above. Andersen has not proven derivation of the invention recited in claim 1 by a preponderance of the evidence. E. Alleged Derivation of the Inventions Recited in Claims 2–22 Andersen asserts that Mr. Oquendo conceived of the subject matter of” slip op. at 64
Claim constructionPatents in suitUS 9,428,953 - 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 · Dec 22, 2016 · DER2016-00022 · APJ Joni Y Chang · DER · Order
The Board denied institution because Shukh had no pending claim substantially the same as the Respondents’ claimed invention or the invention allegedly disclosed to them.
RulingsOther- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“is required to show that the petitioner has at least one claim that is: (1) the same or substantially the same as the respondent’s claimed invention; and (2) the same or substantially the same as the invention disclosed to the respondent. In the instant Petition, Petitioner asserts that claim 19 of Petitioner’s” slip op. at 3
NonePatents in suitUS 9,853,053 - 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 · Oct 28, 2014 · IPR2014-00059 · APJ Joni Y Chang · IPR · Order
The Board granted the parties’ joint motions, terminated the instituted review as to all parties, and entered judgment after settlement before deciding the merits.
RulingsOther- Adverse judgmentAdverse judgmentGranted
“a proceeding will terminate after the filing of a settlement agreement, unless the Board already has decided the merits of the proceedings. Id. In their Joint Motions to Terminate, the parties indicate that they have settled all of their disputes involving the Rackspace inter partes reviews, as well as the related district court proceeding styled PersonalWeb Tech. LLC v. Rackspace US, Inc., No. 6-12-cv-00659 (E.D. Tex.). Mot. 1, 4. The parties also indicate that they concurrently filed their Stipulation of Dismissal, as to only the Rackspace Defendants with prejudice, in that related district court proceeding. Id.; Ex. 2019. More importantly, the parties expressly state that “no other disputes between the parties remain,” and “[t]here is no other litigation or dispute in any court or forum involving [Rackspace and PersonalWeb].” Id. at 4. Upon consideration of the facts before us, we determine that it is appropriate to terminate the Rackspace inter partes reviews as to both parties, and enter judgment.” slip op. at 5
- PTAB / AIA Trials › §315(b) time barDecided for patent owner
“3. However, Google’s Petitions were not filed timely in accordance with 35 U.S.C. § 315(b) (“[a]n inter partes review may not be instituted if the petition requesting the proceeding is filed more than 1 year after the date on which the petitioner . . . is served with a complaint alleging infringement of the patent.”).3 Google could have, but did not, file a petition for inter partes review with the one-year time period. More significantly, Google’s Motions for Joinder were not filed timely in accordance with 37 C.F.R. § 42.122(b) (“[a]ny request for joinder must be filed, as a motion under § 42.22, no later than one month after the institution date of any inter partes review for which joinder is requested.”).4 Google fails to provide sufficient reasons as to why we should exercise our discretion under 37 C.F.R. § 42.5(b) to waive the one-month time limit for filing a Motion for Joinder.5” slip op. at 4
NonePatents in suitUS 6,415,280 - PTAB · Oct 28, 2014 · IPR2014-00066 · APJ Joni Y Chang · IPR · Order
The Board granted the parties’ joint motions, terminated the Rackspace inter partes reviews as to all parties, and granted confidential treatment of the settlement agreement.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“The parties further argue that maintaining the Rackspace inter partes reviews, after the parties have settled their disputes, would be contrary to public policy and would discourage future settlements by removing a significant motivation for settlement. Mot. 5. In view of the circumstances, we agree. Indeed, there are strong public policy reasons to favor settlement between the parties to a proceeding. Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,768 (Aug. 14, 2012). Generally, the Board expects that” slip op. at 4
- PTAB / AIA Trials › §315(b) time barDecided for patent owner
“3. However, Google’s Petitions were not filed timely in accordance with 35 U.S.C. § 315(b) (“[a]n inter partes review may not be instituted if the petition requesting the proceeding is filed more than 1 year after the date on which the petitioner . . . is served with a complaint alleging infringement of the patent.”).3 Google could have, but did not, file a petition for inter partes review with the one-year time period. More significantly, Google’s Motions for Joinder were not filed timely in accordance with 37 C.F.R. § 42.122(b) (“[a]ny request for joinder must be filed, as a motion under § 42.22, no later than one month after the institution date of any inter partes review for which joinder is requested.”).4 Google fails to provide sufficient reasons as to why we should exercise our discretion under 37 C.F.R. § 42.5(b) to waive the one-month time limit for filing a Motion for Joinder.5” slip op. at 4
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingNot reached
“3. However, Google’s Petitions were not filed timely in accordance with 35 U.S.C. § 315(b) (“[a]n inter partes review may not be instituted if the petition requesting the proceeding is filed more than 1 year after the date on which the petitioner . . . is served with a complaint alleging infringement of the patent.”).3 Google could have, but did not, file a petition for inter partes review with the one-year time period. More significantly, Google’s Motions for Joinder were not filed timely in accordance with 37 C.F.R. § 42.122(b) (“[a]ny request for joinder must be filed, as a motion under § 42.22, no later than one month after the institution date of any inter partes review for which joinder is requested.”).4 Google fails to provide sufficient reasons as to why we should exercise our discretion under 37 C.F.R. § 42.5(b) to waive the one-month time limit for filing a Motion for Joinder.5” slip op. at 4
NonePatents in suitUS 6,928,442 - PTAB · Oct 28, 2014 · IPR2014-00062 · APJ Joni Y Chang · IPR · Order
The Board granted the joint motion and terminated IPR2014-00062 as to all parties after settlement, before deciding the merits.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“reviews, after the parties have settled their disputes, would be contrary to public policy and would discourage future settlements by removing a significant motivation for settlement. Mot. 5. In view of the circumstances, we agree. Indeed, there are strong public policy reasons to favor settlement between the parties to a proceeding. Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,768 (Aug. 14, 2012). Generally, the Board expects that” slip op. at 4
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingDenied
“3. However, Google’s Petitions were not filed timely in accordance with 35 U.S.C. § 315(b) (“[a]n inter partes review may not be instituted if the petition requesting the proceeding is filed more than 1 year after the date on which the petitioner . . . is served with a complaint alleging infringement of the patent.”).3 Google could have, but did not, file a petition for inter partes review with the one-year time period. More significantly, Google’s Motions for Joinder were not filed timely in accordance with 37 C.F.R. § 42.122(b) (“[a]ny request for joinder must be filed, as a motion under § 42.22, no later than one month after the institution date of any inter partes review for which joinder is requested.”).4 Google fails to provide sufficient reasons as to why we should exercise our discretion under 37 C.F.R. § 42.5(b) to waive the one-month time limit for filing a Motion for Joinder.5” slip op. at 4
NonePatents in suitUS 7,802,310 - PTAB · Oct 28, 2014 · IPR2014-00058 · APJ Joni Y Chang · IPR · Order
The Board granted the parties’ joint motions, terminated the Rackspace inter partes reviews as to all parties, and granted confidential treatment of the settlement agreement.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“Hosting, Inc. (collectively, “Rackspace”) and Patent Owner PersonalWeb Technologies, LLC and Level 3 Communications (collectively, PersonalWeb) filed a Joint Motion to Terminate in each of the above-identified inter partes reviews (“the Rackspace inter partes reviews”). Paper 34, “Mot.”2 The parties also filed a true copy of their Written Settlement Agreement, made in connection with the termination of the Rackspace inter partes reviews, in accordance with 35 U.S.C. § 317(b) and 37 C.F.R. § 42.74(b). Ex. 1014. Additionally, the parties submitted a Joint Request to have their Written Settlement Agreement treated as confidential business information under 35 U.S.C. § 317(b) and 37 C.F.R. § 42.74(c). Paper 33. For the reasons set forth below, the Joint Motions to Terminate and the Requests to have their Written Settlement Agreement treated as confidential business information are granted.” slip op. at 2
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingDenied
“court proceedings involving PersonalWeb and third parties. Mot. 6–7. However, except for EMC Corporation and VMWare, Inc. (collectively “EMC”) and Apple, Inc. (“Apple”), none of the third parties elected to file a Petition for inter partes review within the one-year statutory period under 35 U.S.C. § 315(b). Id. at 7. We note that the termination of the Rackspace inter partes reviews would not affect the inter partes reviews that involve EMC and Apple. We are cognizant that Google, Inc. and YouTube, LLC (collectively “Google”) filed four Petitions—IPR2014-00977, IPR2014- 00978, IPR2014-00979, and IPR2014-00980—and Motions for Joinder with four of the Rackspace inter partes reviews. See, e.g., IPR2014-00977, Paper 3. However, Google’s Petitions were not filed timely in accordance with 35 U.S.C. § 315(b) (“[a]n inter partes review may not be instituted if the petition requesting the proceeding is filed more than 1 year after the date on which the petitioner . . . is served with a complaint alleging infringement of the patent.”).3 Google could have, but did not, file a petition for inter partes review with the one-year time period. More significantly, Google’s Motions for Joinder were not filed timely in accordance with 37 C.F.R. § 42.122(b) (“[a]ny request for joinder must be filed, as a motion under § 42.22, no later than one month after the institution date of any inter partes review for which joinder is requested.”).4 Google fails to provide sufficient reasons as to why we should exercise our discretion under 37 C.F.R. § 42.5(b) to waive the one-month time limit for filing a Motion for Joinder.5” slip op. at 3
NonePatents in suitUS 8,099,420 - PTAB · Sep 15, 2014 · IPR2014-00470 · APJ Joni Y Chang · IPR · Order
The Board granted the joint motions to terminate the instituted inter partes reviews as to Intel and Zond after settlement; it did not decide patentability.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“Generally, 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). Upon consideration of the facts before us, we determine that it is appropriate to terminate the above-identified proceedings as to both parties, and enter judgment. For the foregoing reasons, it is: ORDERED that the Joint Motions to Terminate the above-identified inter partes reviews are granted; FURTHER ORDERED that the above-identified proceedings are terminated as to all parties—namely, Intel and Zond; and” slip op. at 3
NonePatents in suitUS 7,811,421
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.