- Shopify, Inc. / Priceline.Com LLC et al. v. DDR Holdings, LLCRehearing grantedPTAB · Oct 26, 2020 · IPR2018-01012 · APJ Patrick M Boucher · IPR · Rehearing
Granted Petitioner’s rehearing request and held claims 1–3, 5, 7–8, 11–13, 15, 17, and 18 unpatentable, including claims 4, 5, 12, and 13 over the Digital River Publications.
RulingsRehearing decision- RehearingRehearing, grantedGranted
“Petitioner’s argument on rehearing is persuasive, particularly under the broadest-reasonable-interpretation standard of claim construction applied in this proceeding. See Dec. 12–13 (Final Written Decision noting that, for an inter partes review proceeding based on a petition filed prior to November 13, 2018, “the Board interprets claims of an unexpired patent using the broadest reasonable construction in light of the specification of the patent in which they appear”). Petitioner clarifies that the Petition identifies Exhibit 1009’s buy page as corresponding to the “composite web page contain[ing] one or more selectable URLs” recited in the claim and identifies the “view cart,” “modify cart,” and “check out” pages linked to the “buy” page as corresponding to the recited “hierarchical set of additional pages.”” slip op. at 5
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“we find provide sufficient support for this position. Specifically, the Petition cites to paragraph 105 of Dr. Shamos’s Declaration, and both the Petition and that Declaration cite multiple times to page 1 of Exhibit 1009. See Pet. 23; Ex. 1002 ¶ 105. In describing the correspondence to the “hierarchical set of additional pages,” Dr. Shamos testifies that “[t]he buy pages also provide a link (i.e., selectable URL) to a shopping cart, which, as described by the 21 Software Drive website, allows a user to add products to a shopping cart, view a shopping cart, modify a shopping cart, and check out.” Ex. 1002 ¶ 105 (citing Ex. 1009, 1). We credit this testimony, which is unrebutted on the record before us. Indeed, Dr. Shamos’s testimony that a skilled artisan would have understood Exhibit 1009’s sequence of URLs as satisfying the claimed “hierarchical set of additional webpages” is consistent with the manner in which the ’228 patent itself describes its shopping cart functionality—namely, as nothing more than the ability to “ADD TO CART,” “VIEW SHOPPING CART,” “UPDATE QUANTITIES,” and “CHECK OUT.” Ex. 1001, Fig. 22. Petitioner thus demonstrates that the buy page shown in Exhibit 1009, i.e., the recited “composite web page,” contains one or more selectable URLs connecting the “view cart,” “modify cart,” and “check out” pages to the buy page, i.e., the recited “hierarchical set of additional web pages,” as required by the claim. Because each of those pages “pertain[s] to a subset of the product offerings in the electronic catalog,” such as those selected for purchase, Petitioner demonstrates, by a preponderance of the evidence, that each limitation of the second “wherein” clause of claim 4 is met by the Digital River Publications.” slip op. at 6
- Expert testimonyPetitioner expert creditedDecided for petitioner
“we find provide sufficient support for this position. Specifically, the Petition cites to paragraph 105 of Dr. Shamos’s Declaration, and both the Petition and that Declaration cite multiple times to page 1 of Exhibit 1009. See Pet. 23; Ex. 1002 ¶ 105. In describing the correspondence to the “hierarchical set of additional pages,” Dr. Shamos testifies that “[t]he buy pages also provide a link (i.e., selectable URL) to a shopping cart, which, as described by the 21 Software Drive website, allows a user to add products to a shopping cart, view a shopping cart, modify a shopping cart, and check out.” Ex. 1002 ¶ 105 (citing Ex. 1009, 1). We credit this testimony, which is unrebutted on the record before us. Indeed, Dr. Shamos’s testimony that a skilled artisan would have understood Exhibit 1009’s sequence of URLs as satisfying the claimed “hierarchical set of additional webpages” is consistent with the manner in which the ’228 patent itself describes its shopping cart functionality—namely, as nothing more than the ability to “ADD TO CART,” “VIEW SHOPPING CART,” “UPDATE QUANTITIES,” and “CHECK OUT.” Ex. 1001, Fig. 22.” slip op. at 6
§ 103 obviousnessPatents in suitUS 9,043,228 - Shopify, Inc. / Priceline.Com LLC et al. v. DDR Holdings, LLCRehearing grantedPTAB · Oct 26, 2020 · IPR2018-01011 · APJ Patrick M Boucher · IPR · Rehearing
Petitioner’s rehearing request was granted; claims 1–3, 5, 7, 8, 11–13, 15, 17, and 18 were held unpatentable over the listed grounds.
RulingsRehearing decision- RehearingRehearing, grantedGranted
“II. LEGAL STANDARD A request for rehearing “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.” 37 C.F.R. § 42.71(d). The burden of showing a decision should be modified on a request for rehearing lies with the party challenging the decision. Id.” slip op. at 2
- Expert testimonyPetitioner expert creditedOther
“we find provide sufficient support for this position. Specifically, the Petition cites to paragraph 107 of Dr. Shamos’s Declaration, and both the Petition and that Declaration cite multiple times to page 1 of Exhibit 1009. See Pet. 25; Ex. 1002 ¶ 107. In describing the correspondence to the “hierarchical set of additional pages,” Dr. Shamos testifies that “[t]he buy pages also provide a link (i.e., selectable URL) to a shopping cart, which, as described by the 21 Software Drive website, allows a user to add products to a shopping cart, view a shopping cart, modify a shopping cart, and check out.” Ex. 1002 ¶ 107 (citing Ex. 1009, 1). We credit this testimony, which is unrebutted on the record before us. Indeed, Dr. Shamos’s testimony that a skilled artisan would have understood Exhibit 1009’s sequence of URLs as satisfying the claimed “hierarchical set of additional webpages” is consistent with the manner in which the ’876 patent itself describes its shopping cart functionality—namely, as nothing more than the ability to “ADD TO CART,” “VIEW SHOPPING CART,” “UPDATE QUANTITIES,” and “CHECK OUT.” Ex. 1001, Fig. 22.” slip op. at 6
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“Petitioner’s argument on rehearing is persuasive, particularly under the broadest-reasonable-interpretation standard of claim construction applied in this proceeding. See Dec. 12–13 (Final Written Decision noting that, for an inter partes review proceeding based on a petition filed prior to November 13, 2018, “the Board interprets claims of an unexpired patent using the broadest reasonable construction in light of the specification of the patent in which they appear”). Petitioner clarifies that the Petition identifies Exhibit 1009’s buy page as corresponding to the “composite web page contain[ing] one or more selectable URLs” recited in the claim and identifies” slip op. at 5
§ 103 obviousnessPatents in suitUS 9,639,876 - 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
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.