- Blackberry Corp. v. Facebook, Inc.Rehearing deniedPTAB · Apr 17, 2020 · IPR2019-01593 · APJ Miriam L Quinn · IPR · Rehearing
The Board denied rehearing and left in place its discretionary denial of the petition, finding no misapprehension or oversight in its assessment of the claim 23 challenges.
RulingsRehearing decision- RehearingRehearing, deniedDenied
“According to 37 C.F.R. § 42.71(d), “[t]he burden of showing a decision should be modified lies with the party challenging the decision,” and the “request must specifically identify all matters the party believes the Board misapprehended or overlooked.” The burden here, therefore, lies with Petitioner to show we misapprehended or overlooked the matters it requests” slip op. at 2
- Other 314aInstitution denied discretionary otherDenied
“Partes Review. Paper 7 (“Dec.”). We exercised our discretion under 35 U.S.C. § 314(a) and denied the Petition based on our determination that Petitioner has only demonstrated a reasonable likelihood of prevailing as to three claim challenges (out of 17).1 Dec. 39−40. Petitioner filed a Request for Rehearing challenging several aspects of our Decision. Paper 8 (Req. Reh’g). In particular, Petitioner challenges our determination of the scope of “Global Positioning System data” (hereinafter “GPS Data”) a term recited in independent claim 23. Req. Reh’g 3−6. Petitioner further challenges our determination concerning the term “range of acceptable values,” recited in claim 23. Id. at 10−12. Thus, Petitioner argues, based on the correct interpretation of “GPS data” and “range of acceptable values,” we should have instituted trial because it demonstrated a reasonable likelihood of prevailing as to four or five out of eight challenged claims.2 Req. Reh’g 13.” slip op. at 2
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“types of information that are GPS data, such as idle time. The portions of the Specification that Petitioner now cites, however, do not show that the GPS data is not, at a minimum, location information. As we stated in our Decision, other types of data may be transmitted from the remote unit to the central location, but the GPS data does refer to location information. Dec. 9. Moreover, Petitioner points out that the Specification discusses vehicle speed, idle time, movement, and actual windshield time as examples of calculated values, arguably from GPS location and time information. Req. Reh’g 3. But the Specification actually refers to these values to determine exceptions to be logged and noted (Ex. 1001, 4:41−49, 4:65−67, 6:1−3), which proves only that the system may use non-GPS data, in combination with GPS data, to determine exceptions. We acknowledge that claim 23’s recitation of GPS data could seem, at first blush, to potentially encompass every comparison that the Specification explains. Claim 23, however, must be interpreted in a manner that accounts for the recited two-part structure. In the first part, the claim recites a first comparison that involves the GPS data; and in the second part, the claim recites the second comparison that does not mention GPS data. Our analysis of the term GPS data in our Decision did not assume that the two comparisons involved the same data, e.g., GPS data. This is where Petitioner disagrees with our assessment, because it urges us to construe GPS data as including values and information recited in the second comparison, i.e., the idle time or recited “stationary time.” Petitioner’s position cannot be correct because the claim does not require that the “stationary time” also be GPS data. Further, the comparison that claim 23 recites with respect to GPS data does not mention exceptions at all, so it does not follow that all the Specification’s descriptions of exceptions encompass GPS data. The second comparison recited in claim 23 (comparing the stationary time to a predetermined stationary time), in contrast, is expressly performed for the purpose of noting an exception. Claim 23 (“if the length of time that the remote unit remains in a stationary position is greater than the predetermined stationary time, the system notes an exception.”). Thus, Petitioner, even in arguing for the first time its claim construction position, has not shown that derived data must also be GPS data according to the plain reading of the claim language. Consequently, having reviewed Petitioner’s arguments, we are not persuaded that GPS data means data that is derived from and representative of GPS coordinates and time stamps, as argued for the first time in the Request for Rehearing.3” slip op. at 4
- BurdenDecided for patent owner
“construction issue. Patent Owner explicitly addressed the construction of the term, a fact we acknowledged in our Decision. Dec. 8 (citing Prelim. Resp. 29−30). Petitioner did not address the scope of the term explicitly or implicitly. And it was not apparent from any of the now-cited portions of the Petition that Petitioner contended a scope of the term to include data that is derived from and representative of GPS coordinates and time stamps. Petitioner’s argument attempts to characterize its omission of a contention regarding claim construction as an oversight on our part. The argument is not persuasive as it is Petitioner’s burden to show in the Petition its contentions regarding how the challenged claim is to be construed and how, so construed, the claim is rendered obvious by the asserted references. See 37 C.F.R. § 42.104(b)(3)−(4). Therefore, we could not have either overlooked Petitioner’s position on claim construction, since none was provided, or misapprehended a position of claim scope not made explicit.” slip op. at 3
Claim constructionDiscretionary denialPatents in suitUS 6,356,841 - Juniper Networks, Inc. v. Finjan, Inc.Rehearing deniedPTAB · Jul 16, 2019 · IPR2019-00060 · APJ Miriam L Quinn · IPR · Rehearing
The Board granted rehearing only to address the overlooked construction dispute, but again denied institution because Jensen did not teach “mobile protection code.”
RulingsRehearing decision- RehearingRehearing, deniedDenied
“(“Dec. on Inst.”). The panel concluded that Petitioner had not shown a reasonable likelihood of prevailing in the asserted obviousness grounds because, for a particular ground, Petitioner failed to demonstrate sufficiently that Jensen1 teaches “mobile protection code.” Dec. on Inst. 11−12.2 Petitioner has filed a Request for Rehearing. Paper 8 (“Req. Reh’g”). Petitioner argues that the scope for the claim term “mobile protection code” was in dispute, and that we “failed to resolve the key claim construction dispute between the parties.” Id. at 1. According to Petitioner, rehearing is warranted to resolve the claim construction dispute and “fix the plain error in the Institution Decision.” Id. We are persuaded that in failing to address Petitioner’s construction, we overlooked the matter raised in Petitioner’s Request for Rehearing. Nevertheless, for the reasons discussed infra, after giving due consideration to Petitioner’s argument, we are persuaded that our decision to deny institution was correct, and therefore we deny the request insofar as it calls upon us to institute trial.” slip op. at 2
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“(“Dec. on Inst.”). The panel concluded that Petitioner had not shown a reasonable likelihood of prevailing in the asserted obviousness grounds because, for a particular ground, Petitioner failed to demonstrate sufficiently that Jensen1 teaches “mobile protection code.” Dec. on Inst. 11−12.2 Petitioner has filed a Request for Rehearing. Paper 8 (“Req. Reh’g”). Petitioner argues that the scope for the claim term “mobile protection code” was in dispute, and that we “failed to resolve the key claim construction dispute between the parties.” Id. at 1. According to Petitioner, rehearing is warranted to resolve the claim construction dispute and “fix the plain error in the Institution Decision.” Id. We are persuaded that in failing to address Petitioner’s construction, we overlooked the matter raised in Petitioner’s Request for Rehearing. Nevertheless, for the reasons discussed infra, after giving due consideration to Petitioner’s argument, we are persuaded that our decision to deny institution was correct, and therefore we deny the request insofar as it calls upon us to institute trial.” slip op. at 2
- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsInstitution denied 325dInstitution denied
“1 Protection Wrappers: A Simple and Portable Sandbox for Untrusted Applications, Proceedings on the 8th ACM SIGOPS European Workshop on Support for Composing Distributed Applications, filed in the record as Exhibit 1006. 2 We also exercised our discretion under 35 U.S.C. §§ 314(a) and 325(d) and denied institution. Petitioner does not challenge the exercise of discretion in this request for rehearing.” slip op. at 2
- Other 314aInstitution denied discretionary otherInstitution denied
“1 Protection Wrappers: A Simple and Portable Sandbox for Untrusted Applications, Proceedings on the 8th ACM SIGOPS European Workshop on Support for Composing Distributed Applications, filed in the record as Exhibit 1006. 2 We also exercised our discretion under 35 U.S.C. §§ 314(a) and 325(d) and denied institution. Petitioner does not challenge the exercise of discretion in this request for rehearing.” slip op. at 2
Claim constructionDiscretionary denialPatents in suitUS 7,647,633
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.