- PTAB · Oct 15, 2020 · IPR2019-00995 · APJ Timothy J Goodson · IPR · Final written decision
The Board granted the non-contingent motion to amend, canceling claims 2, 8, 10, 18, 19, 28–30, 32–34, 37, 38, 40–42, 45, and 47 and substituting claims 48–62, which were not shown obvious.
RulingsFinal written decision- ExcludeMotion to exclude, deniedDenied
“minimal probative value because Patent Owner has not adequately demonstrated a nexus between the asserted objective indicia and the merits of the claimed invention. Mot. to Exclude 3–4; Reply Mot. to Exclude 1–2. This argument attacks the merits of Patent Owner’s substantive arguments on objective indicia and does not establish an evidentiary basis for excluding Mr. Van Vliet’s testimony. We agree with Patent Owner that Mr. Van Vliet’s testimony is relevant to the issue of objective indicia of nonobviousness. See Opp. Mot. to Exclude 1–2. Petitioner also argues that Mr. Van Vliet’s declaration should be excluded because it contains hearsay. Mot. to Exclude 4–6; Reply Mot. to Exclude 2. Petitioner states that it “is not moving to exclude based on the fact that the Declaration itself [is] hearsay, but rather that it contains a multitude of statements therein that are themselves hearsay, made by persons other than Van Vliet . . . .” Mot. to Exclude 5. However, as Patent Owner points out, Petitioner does not identify any specific statements in the declaration that constitute hearsay. Opp. Mot. to Exclude 4. Even after Patent Owner pointed out this lack of specificity, Petitioner’s Reply still does not clarify which specific statements in the declaration are alleged to be hearsay and instead simply repeats the assertion there are “a multitude of statements therein that are themselves hearsay.” Reply Mot. to Exclude 2.” slip op. at 11
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted
“however, we first consider whether Patent Owner’s Revised Motion to Amend meets the statutory and regulatory requirements of 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121. Lectrosonics, Paper 15 at 4. To satisfy those requirements, Patent Owner must demonstrate that: (1) the amendment proposes a reasonable number of substitute claims; (2) the amendment responds to a ground of unpatentability involved in the trial; (3) the amendment does not seek to enlarge the scope of the claims of the patent or introduce new subject matter; and (4) the proposed claims are supported in the original disclosure (and any earlier filed disclosure for which the benefit of filing date is sought). See 35 U.S.C. § 316(d) (2018); 37 C.F.R. § 42.121 (2018).” slip op. at 16
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther
“We determine that the plain language of the claim, which requires that the fuel delivery connections “compris[e]” the fuel level sensor, shows that the fuel level sensor is structurally connected to the fuel level sensor. As Petitioner agrees, this claim language requires that the fuel delivery connection includes the fuel level sensor. Tr. 34:17–20. Both the fuel delivery connections and the fuel level sensor are structures, so for one to include the other, they must be physically connected. Petitioner’s argument give effect to the word “comprising.” Because a fuel delivery connection and a fuel level sensor would be operationally connected in any system that has both items, Petitioner’s interpretation essentially reads out the word “comprising” and treats the claim phrase as if it recited “fuel delivery connections and a fuel level sensor.” Our interpretation that the fuel delivery connections must be physically connected to the fuel level sensor is more faithful to the claim’s recitation that the fuel delivery connections “compris[e]” the fuel level sensor. See Stumbo v. Eastman Outdoors, Inc., 508 F.3d 1358, 1362 (Fed. Cir. 2007) (“A claim construction that gives meaning to all the terms of the claim is preferred over one that does not do so.”) (quoting Merck & Co. v. Teva Pharms. USA, Inc., 395 F.3d 1364, 1372 (Fed. Cir. 2005)).” slip op. at 22
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“a low and high fuel level in the tanks to which the fuel delivery connection is connected.” RMTA A1. Patent Owner proposes that “low” fuel level means “empty or nearly empty” and “high” means “full or nearly full.” Id. at 5 nn.16–17 (citing Ex. 1001, 4:1–4, 6:7–12; Ex. 2002, 10). Petitioner does not contest Patent Owner’s proposed constructions or offer competing constructions for these terms. See generally Opp. RMTA; Tr. 13:17–15:14. Although Patent Owner’s argument in support of these constructions is truncated, we determine that Patent Owner’s proposals are supported by the evidence of record. The ’906 patent describes that operators can be provided with “visual representations or displays showing the fuel level in each of the tanks 12. Any visual representation or display may be used that shows at least a high level condition (tank full) and a low level condition (tank empty or nearly empty) and preferably also shows actual fuel level.” Ex. 1001, 3:66–4:4; see also id. at 6:7–10 (explaining that “[t]he control station 56 may be provided with a full readout or display for each fuel tank 12 being filled that shows the level of fuel in the fuel tank 12 including when the fuel tank 12 is near empty and near full. An alternative is to provide only fuel empty (low sensor dry) or fuel full (high sensor wet) signals.”). These descriptions equate a high fuel level with the tank being full or nearly full and a low fuel level with the tank being empty or nearly empty. Patent” slip op. at 24
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,029,906 - 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 · Nov 26, 2014 · IPR2014-01438 · APJ Robert J Weinschenk · IPR · Order
The Board granted the parties’ joint motion and terminated the proceeding as to all parties before deciding whether to institute review.
RulingsOther- PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted
“Preliminary Response has not been filed, and a decision whether to institute a trial has not been rendered. Patent Owner represents that there is no currently pending district court litigation or ITC proceeding regarding the ’990 patent, and no decision has been made regarding future litigation. Mot. 1–2. Patent Owner also represents that there is no other related proceeding regarding the ’990 patent in the Office. Id. at 2. Based on the facts of this case, we determine it is appropriate to enter judgment terminating this proceeding with respect to all parties. We further find sufficient cause to treat the settlement agreement as business confidential information. Therefore, we grant the joint motion to terminate and the joint request to treat the settlement agreement as business confidential information. III. ORDER In consideration of the foregoing, it is hereby: ORDERED that the joint motion to terminate is granted, and this proceeding is terminated as to all parties; and” slip op. at 2
NonePatents in suitUS 6,844,990 - 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.