- Platform Science, Inc. v. Omnitracs, LLCRehearing grantedPTAB · Sep 3, 2021 · IPR2020-01612 · APJ Bart A Gerstenblith · IPR · Rehearing
The Board granted rehearing and instituted IPR on all petition grounds for claims 1–4, 6–9, 11, 12, and 15, finding a reasonable likelihood of prevailing.
RulingsRehearing decision- RehearingRehearing, grantedGranted
“II. STANDARD OF REVIEW A party requesting rehearing bears the burden of showing that the decision should be modified. 37 C.F.R. § 42.71(d). “The request must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, or a reply.” Id. When rehearing a decision on a petition, we review the decision for an abuse of discretion. 37 C.F.R. § 42.71(c).” slip op. at 2
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“preliminary stage, we determine that Petitioner demonstrates a reasonable likelihood of prevailing with respect to claim 1.” slip op. at 44
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“The only dispute pertaining to claim construction at this stage of the proceeding is whether the phrase “a process for creating said response message,” recited in claim 1, is governed by 35 U.S.C. § 112 ¶ 6.6 Petitioner 6 As noted above, Petitioner raises a second claim construction issue in its Rehearing Request. See Req. Reh’g 12–15 (asserting that the claims require only one instance of copying information from a formatted message to a response message based on which formatted message was received). Petitioner did not raise this issue in the Petition, Patent Owner has not had an contends that the phrase should be interpreted as a means-plus-function limitation, whereas Patent Owner contends that it should not. Compare Pet. 2–7 (advocating for a means-plus-function construction), with Prelim. Resp. 9–11 (advocating for an ordinary and customary meaning). At this stage of the proceeding, the dispute between the parties regarding the construction of this claim phrase does not impact our Decision. Accordingly, we need not construe expressly any claim terms for the purpose of this Decision.” slip op. at 17
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“VI. ANALYSIS Legal Standards – Anticipation “[A] claim is anticipated ‘if each and every limitation is found expressly or inherently in a single prior art reference.’” King Pharm., Inc. v. Eon Labs., Inc., 616 F.3d 1267, 1274 (Fed. Cir. 2010) (quoting Celeritas Techs., Ltd. v. Rockwell Int’l Corp., 150 F.3d 1354, 1361 (Fed. Cir. 1998)). Anticipation is a question of fact, In re Gleave, 560 F.3d 1331, 1334–35 (Fed. Cir. 2009), assessed from the perspective of one of ordinary skill in the art, see Dayco Prods., Inc. v. Total Containment, Inc., 329 F.3d 1358, 1368 (Fed. Cir. 2003) (“the dispositive question regarding anticipation [i]s whether one skilled in the art would reasonably understand or infer from the [prior art reference’s] teaching that every claim element was disclosed in that single reference” (alteration in original) (quotation omitted)).” slip op. at 18
Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 6,925,308 - Blue Coat Systems, Inc. v. Finjan, Inc.Rehearing grantedPTAB · Jul 18, 2017 · IPR2016-01444 · APJ Patrick M Boucher · IPR · Rehearing
Granted Blue Coat’s rehearing request and instituted review of claims 1, 4–6, 9, 12–14, 17, 24, 35, and 37; the petition showed a reasonable likelihood of prevailing on the asserted § 103 grounds.
RulingsRehearing decision- RehearingRehearing, grantedGranted
“reexamination proceeding. Of particular relevance, the reexamination concluded with a Reexamination Certificate issued on November 28, 2016, including a claim for the benefit of the November 8, 1996 filing date of U.S. Provisional Appl. No. 60/030,639 (“the ’639 provisional application”). Ex. 3006 at [60]. In denying the Petition, the Prior Decision noted that “Petitioner has taken no steps to explain or respond to the effect of these developments on its argument.” Dec. 7. This remains true. Nevertheless, we agree with Petitioner that our Prior Decision gave insufficient consideration to the Petition’s assertion that “U.S. Patent No. 7,613,926 [(“the ’926 patent”), i.e., an intermediate patent in the priority chain of the ’086 patent] fails to claim priority to the ’639 provisional application and instead the earliest priority document cited in the ’926 patent is [the ’194 patent].” Pet. 5 (citing Ex. 1012, col. 1, ll. 8–32); see Req. Reh’g 4–5, 6 n.4, 7–9. For a claim of a patent to be entitled to the effective filing date of an earlier filed application, each application in the priority chain must refer to the earlier filed application. Encyclopaedia Britannica, Inc. v. Alpine Elecs. of Am., Inc., 609 F.3d 1345, 1350–52 (Fed. Cir. 2010). Accordingly, we grant Petitioner’s Rehearing Request and proceed to the merits of the Petition.” slip op. at 8
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedMixed
“a formally defined safety policy” and allows checking “with certainty, that the proof is valid and hence the foreign code is safe to execute.” Ex. 1004, 107. Thus, Petitioner argues that one of ordinary skill in the art would reasonably understand Necula to teach that its proof-carrying code adds to the foreign code, consistent with the construction of “append” that we apply herein, and Petitioner articulates sufficient reasoning with rational underpinning to apply that teaching to Swimmer’s representation of DSP data. See Pet. 46–49. This is not an instance, for example, in which Petitioner relies on a characterization of the problem provided by the patent to derive its reasoning. Cf., e.g., Mintz v. Dietz & Watson, Inc., 679 F.3d 1372 (Fed. Cir. 2012). Indeed, Patent Owner’s contention that “the storage of the DSP in a database is one of the key features that distinguishes the ‘086 Patent over the prior art” dilutes the strength of its argument. The contrary positions of the parties’ declarants in their testimonial evidence creates a genuine issue of material fact, which we resolve in the light most favorable to Petitioner for purposes of this Decision. 37 C.F.R. § 42.108(c). Accordingly, we conclude that Petitioner has made a sufficient showing also with respect to these elements, and that Petitioner demonstrates a reasonable likelihood of prevailing on its challenge of claims 1 and 9. See infra Section II.E.10 (discussing limits in our weighing of Patent Owner’s Secondary Considerations evidence in this Preliminary Proceeding).” slip op. at 21
- PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner
“be considered under 35 U.S.C. § 312 because Petitioner has failed to name all real parties in interest, as required by the statute.” Prelim. Resp. 9. The parties agree that, on June 12, 2016, Symantec Corporation (“Symantec”) announced that it was acquiring Petitioner. Pet. 13; Prelim. Resp. 9. The Petition discloses that “[t]he transaction is expected to close in the third quarter of 2016,” and that “[a]s of the filing date of this petition the transaction has not been executed.” Pet. 13. The Petition further represents that “Symantec has not controlled or had the ability to control the filing of this petition, whether through funding or strategy.” Id. As noted above, Petitioner expressly identified Symantec as a real party in interest before any decision on institution of an inter partes review was made. Paper 8, 2. Patent Owner contends that “Symantec had control over the filing of the Petition during the period between the announcement of the acquisition and the closing of the acquisition,” which it asserts occurred on August 1, 2016. Prelim. Resp. 9. Patent Owner also contends that it “understands from the underlying litigation that ‘Blue Coat Systems, Inc.’ no longer exists 1 A petition to accept an unintentionally delayed claim of priority for the ’926 patent, claiming the benefit of U.S. Patent Appl. No. 08/790,097 which was filed January 29, 1997, was dismissed by the Office on June 13, 2017. Exs. 1027, 3007. A renewed petition was filed on June 16, 2017. Ex. 3008. At this time, the Office has not ruled on the renewed petition, and that pending petition accordingly does not affect our determination of the challenged claims’ effective filing date for purposes of this Decision. as an entity, or at least goes by ‘Blue Coat Systems LLC’ for at least the last two months.” Id. at 10. We have reviewed the evidence provided by Patent Owner and find it insufficient to support Patent Owner’s allegation that Petitioner has failed to comply with 35 U.S.C. § 312(a) or 37 C.F.R. § 42.8(a)(3). That evidence is, at best, suggestive regarding an issue that is not jurisdictional. Lumentum Holdings, Inc. v. Capella Photonics, Inc., Case IPR2015-00739, slip op. (PTAB Mar. 4, 2016) (Paper 38) (precedential).” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“1. “Downloadable” Every challenged independent claim recites a “Downloadable,” and Petitioner contends that “[t]he broadest reasonable interpretation of the term ‘downloadable’ includes ‘an executable application program, which is downloaded from a source computer and run on a destination computer.’” Pet. 15. Petitioner’s proposed construction parallels a statement made in the Specification of the ’194 patent. Ex. 1012, col. 1, ll. 44–47. Patent Owner “does not dispute” this proposed construction, which we adopt for purposes of this Decision. Prelim. Resp. 5. 2. “database” Challenged independent claim 42 recites “a database of Downloadable security profiles.” Petitioner contends that “[t]he broadest reasonable interpretation of the term ‘database’ includes ‘a collection of interrelated data organized according to a database schema to serve one or more applications.’” Pet. 15. Patent Owner also “does not dispute” this proposed construction, but argues that “the practical import of Petitioner’s proposed construction for the term ‘database,’ is that log files, such as Swimmer’s audit trail, do not fall within the scope of the claims.” Prelim. Resp. 5–6. That is, Patent Owner contends that “logging functionality is distinct from storing in a database, which allows DSP to be efficiently retrieved from the database,” as compared with the “record-keeping” functionality of an “event log.” Id. at 7. Patent Owner’s argument was considered by the panel in IPR2015- 01892, which concluded that, “[t]o the extent that construction would exclude a log file consisting of an ‘unstructured collection of data on a computer,’ . . . [an] unstructured log file would not be a database,” but the construction does not “necessarily exclude[] all log files from being databases.” 1892 Dec. 16 (emphasis in original). We agree with the reasoning expressed in the Final Written Decision of IPR2015-01892. Id. at 12–17. For purposes of this Decision, we adopt Petitioner’s proposed construction.” slip op. at 10
Claim construction§ 102 anticipation§ 103 obviousnesscites PhillipsPatents in suitUS 8,079,086 - Palo Alto Networks, Inc. v. Finjan, Inc.Rehearing grantedPTAB · May 19, 2017 · IPR2016-00151 · APJ Miriam L Quinn · IPR · Rehearing
The Board clarified the construction of “a call to a first function” but left unchanged its determination that claims 1–8, 10, and 11 were not shown unpatentable over Ross.
RulingsRehearing decision- RehearingRehearing, grantedGranted in part
“proceeding. Paper 51 (“Final Dec.”). On April 14, 2017, Palo Alto Networks, Inc. (“Petitioner”) filed a Request for Rehearing. Paper 52 (Req. Reh’g.). Petitioner’s Request urges the Board to review the construction of “a call to a first function” for consistency with the construction given to the same term in our Final Written Decision in IPR2015-01979.2 We agree with Petitioner that the construction of “a call to a first function” must be consistent with our determination in IPR2015-01979. Accordingly, we hereby modify our Final Written Decision in this proceeding to reflect that the construction for the term “a call to a first function” means “a statement or instruction in the content, the execution of which causes the function to provide a service.” That construction remains, however, consistent with our analysis and determinations made in our Final Written Decision, and therefore requires no modification of our conclusions. For example, at page 8 of that Decision we stated that “we determine that the ‘call’ is a statement or instruction in the content, the execution of which causes the function to provide a service.” Final Dec. 8. Accordingly, the last sentence of the first paragraph in page 9 of the Final Written Decision is modified to repeat what we stated earlier in page 8 of the Decision: “we determine that a ‘call to a first function’ means a statement or instruction in the content, the execution of which causes the function to provide a service.”” slip op. at 2
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“Petitioner advocates. The word “call” is recited in claim 1 as a noun, and is the statement or instruction included in the content that causes the first function to provide a service. Final Dec. 7; Ex. 1001, 17:34−36. The word “invoking” appears elsewhere in the claim in connection with the transmission of the call’s input, which occurs “when the first function is invoked.” Ex. 1001, 17:39−40. The claim language is straightforward: the received content includes a call to a first function, and when that same first function is invoked, the function’s input is transmitted to the security computer. In summary, Petitioner’s request urges us to view the claim construction as allowing the call included in the received content to request the services of a function different from the function in the call statement or instruction. To illustrate, if the content states “call function X” but instead, during runtime, function Y is invoked, Petitioner asserts that this scenario would be a “call” to function Y, and therefore meet the claim. As stated above, however, the claim language does not support this reading. The call to the first function must be included in the content, and it is the same first function that is invoked later in the claim. Our claim construction does not change the plain reading of the claim language. Therefore, the execution of the statement or instruction included in the content must cause the function identified in the statement or instruction to provide a service. To illustrate, if the content states “call function X,” during runtime, function X must be invoked. Ross,3 as we discuss in our Final Written Decision, does not do this. See Final Dec. 17−19 (concluding that Ross invokes indirectly the hook function without any need to include a call to that hook function).” slip op. at 4
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableNot shown unpatentable
“construction as allowing the call included in the received content to request the services of a function different from the function in the call statement or instruction. To illustrate, if the content states “call function X” but instead, during runtime, function Y is invoked, Petitioner asserts that this scenario would be a “call” to function Y, and therefore meet the claim. As stated above, however, the claim language does not support this reading. The call to the first function must be included in the content, and it is the same first function that is invoked later in the claim. Our claim construction does not change the plain reading of the claim language. Therefore, the execution of the statement or instruction included in the content must cause the function identified in the statement or instruction to provide a service. To illustrate, if the content states “call function X,” during runtime, function X must be invoked. Ross,3 as we discuss in our Final Written Decision, does not do this. See Final Dec. 17−19 (concluding that Ross invokes indirectly the hook function without any need to include a call to that hook function).” slip op. at 4
Claim construction§ 103 obviousnessPatents in suitUS 8,141,154 - Square, Inc. v. Think Computer CorporationRehearing grantedPTAB · Feb 9, 2016 · CBM2014-00159 · APJ Michael W Kim · CBM · Rehearing
The Board granted Patent Owner’s rehearing request insofar as it addressed the assertions in the decision, but denied it in all other respects; the prior analysis remained unchanged.
RulingsRehearing decision- RehearingRehearing, grantedGranted in part
“A request for rehearing can only point out that which the Board misapprehended or overlooked, and will be reviewed for abuse of discretion. 37 C.F.R. § 42.71(d). Moreover, as the moving party, the burden of persuasion falls on Patent Owner. 37 C.F.R. § 42.20(c). The request must specifically identify all matters the party believes the Board misapprehended or overlooked, and where each matter was previously addressed in a motion, an opposition, or a reply. Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,768 (Aug. 14, 2012).” slip op. at 1
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“are unpersuaded that they would alter our construction. For example, Patent Owner asserts that the claim limitation “any particular transaction” requires that “bidirectional account” be construed as allowing an account to function simultaneously as both a merchant account and a purchaser account under all transactions. We disagree, primarily because we are unclear as to what Patent Owner means by “under all transactions.” The relevant limitation of independent claim 1 reads “wherein the first account and the second account are adapted to selectively function as either a merchant or a purchaser account during any particular transaction.” We find that “[a]ny particular transaction” means any specific transaction, and is not necessarily limited to all transactions going forward, and find further that, logically, an account need only function in “merchant mode” or “purchaser mode” for that particular transaction; otherwise the account would be in the awkward position of performing a transaction with itself. Moreover, we are unclear as to why the same account cannot function as both, depending on the transaction, as an account is merely a repository within which funds are held, and whether the account is in “merchant mode” (i.e., the ability to send funds from the account) or “purchaser mode” (i.e., the ability to send funds to the account) does not alter the fundamental repository nature of the account itself. A similar analysis of the cited portions of the prosecution history and Specification yields similar conclusions. For example, Patent Owner’s discussion of the prosecution history on pages 4 and 5 of the Request for Rehearing do not amount to Patent Owner providing an explicit definition of “selectively function,” “during any particular transition,” or any other claim term as meaning “simultaneously”; nor do Patent Owner’s statements rise to the level of a clear and unmistakable disclaimer with respect to the meaning of the claim terms.” slip op. at 8
- Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached
“2. whether Dalzell fails to meet the claims’ requirements Based on Patent Owner’s proposed claim construction of “bidirectional accounts,” Patent Owner asserts that Dalzell does not disclose “bidirectional accounts.” Req. 7‒10. As we are unpersuaded, however, that the Board misapprehended or overlooked the items identified by Patent Owner in construing “bidirectional accounts,” we are unpersuaded that our analysis of Dalzell and “bidirectional accounts” set forth on pages 28 to 29 of the Final Written Decision should be modified in any way. See Dec. 29 (“[W]e find that a more logical reading of paragraph 59 of Dalzell is that a buyer, from a particular account, can add a seller feature to that particular account, without the need to create a whole new account. Such a finding is supported by extensive analysis and testimony by Dr. Sadeh-Koniecpol, with explicit citations to Dalzell, which we find credible, reasonable, and persuasive. Ex. 1002 ¶¶ 147-164 (citing Ex. 1006 ¶¶ 9, 27, 49, 57, 61, 82, 85, 87, 132, 163, Figs. 1A, 1B).”)” slip op. at 9
Claim construction§ 103 obviousnessPatents in suitUS 8,396,808
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.