throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`APPLE INC., HTC CORPORATION, HTC AMERICA, INC., SAMSUNG
`ELECTRONICS CO. LTD, SAMSUNG ELECTRONICS AMERICA, INC., AND
`AMAZON.COM, INC.,
`Petitioners,
`
`v.
`
`MEMORY INTEGRITY, LLC,
`Patent Owner.
`____________
`
`Case IPR2015-00163
`Patent 7,296,121
`____________
`
`
`
`
`
`PETITIONER’S REQUEST FOR REHEARING
`PURSUANT TO 37 C.F.R. § 42.71
`
`
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`I.
`
`Introduction
`Apple Inc., HTC Corporation, HTC America, Inc., Samsung Electronics Co.
`
`Ltd, Samsung Electronics America, Inc., and Amazon.com, Inc. (“Petitioners”)
`
`hereby respectfully request rehearing of the May 8, 2015 Decision (“Decision”),
`
`granting-in-part and denying-in-part institution of trial. In particular, Petitioners
`
`request rehearing of the Board’s decision not to institute review with regard to
`
`claim 12. In rendering its Decision, the Board misapprehended the Petition’s
`
`application of Koster to the language of claim 12.
`
`First, the Board misapprehended the Petitions’ argument with respect to
`
`claim 12, which focused solely on the exemplary single response memory
`
`transaction disclosed in FIG. 9 of Koster, where a requesting microprocessor 182
`
`received one and only one response from the other microprocessors and, therefore,
`
`in this example, necessarily completed its memory transaction after receiving one
`
`and only one response. See Petition, pp. 34-37. While this example alone satisfies
`
`claim 12, as described in the Petition, the Board focused on the fact that Koster’s
`
`system additionally supports memory transactions that may involve multiple
`
`responses, where the “requesting processor 182 could potentially receive one, two,
`
`or three responses with copies of the requested data” (emphasis added). See
`
`Decision, p. 23. The ability of Koster’s system to support memory transactions
`
`that involve multiple responses does not undermine its disclosure of a processor
`
`
`
`1
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`programmed to function as described in its Fig. 9, which clearly supports memory
`
`transactions that involve a single response and, as noted in the Petition, such single
`
`response transactions alone satisfy the features of claim 12.
`
`Second, when explaining its denial of the Petition’s proposed ground for
`
`unpatentability of claim 12 based on Koster, the Board criticized the Petition for
`
`failing to demonstrate how Koster disclosed a node programmed to perform a
`
`“memory transaction ... before all the responses are in.” See Decision, p. 23
`
`(“Petitioner does not point us to any disclosure in Koster that the memory
`
`transaction occurs before all the responses are in. See Pet. 23–37. Thus, we are not
`
`persuaded that Petitioner nodes is programmed to complete a memory transaction
`
`after receiving a first number of responses to a first probe” “and the first number is
`
`one,” as required by claim 12.”). It is evident from this portion of the Decision that
`
`the Board has misapprehended the plain meaning attributed by the Petition to claim
`
`12, as the Decision introduces the allegedly unmet non-limitations (“before all the
`
`responses are in”) into claim 12. Specifically, contrary to the Petition, the
`
`Decision reads claim 12 as if that claim requires a node programmed to trigger
`
`transactions “before all the responses are in.” In fact, claim 11 merely requires a
`
`node programmed to trigger transactions “after receiving a first number of
`
`responses,” and claim 12 merely requires the first number to be “one.” Neither the
`
`Patent Owner Preliminary Response nor the Petition misapprehends the plain
`
`
`
`2
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`meaning of claim 12 by introducing this new limitation. Rather, in applying
`
`Koster to claim 12, the Petition explains that claim 12 is given its plain meaning
`
`and that FIG. 9 of Koster meets claim 12 by disclosing a microprocessor (182) that
`
`is programmed to complete a memory transaction after receiving just “one”
`
`response to a first probe. See Petition, pp. 4-5 and 36. While the Decision
`
`embraces this description of Koster, it nevertheless refused to apply Koster to
`
`claim 12 based on Koster’s alleged failure to meet the “before all the responses are
`
`in” feature that was inappropriately introduced by the Decision into claim 12.
`
`Accordingly, misapprehension and oversight led the Board to deny
`
`institution of the proposed ground for unpatentability of claim 12 based on Koster.
`
`II. Applicable Rules
`37 C.F.R. § 42.71 (d) states:
`
`(d) Rehearing. A party dissatisfied with a decision may file a request
`for rehearing, without prior authorization from the Board. The burden
`of showing a decision should be modified lies with the party
`challenging the decision. 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. A request for rehearing does not toll
`times for taking action. Any request must be filed:
`(1) Within 14 days of the entry of a non-final decision or a decision
`to institute a trial as to at least one ground of unpatentability asserted
`in the petition; or
`
`
`
`3
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`
`(2) Within 30 days of the entry of a final decision or a decision not to
`institute a trial.
`
`In accordance with 37 C.F.R. § 42.71 (d)(1), this request is being filed
`
`within 14 days of the entry of a decision to institute a trial as to at least one ground
`
`of unpatentability asserted in the petition.
`
`III. Requested Relief
`Petitioners respectfully request reconsideration of the Board’s decision not
`
`to institute a review of claim 12 of U.S. Patent No. 7,296,121 as being anticipated
`
`by Koster. Petitioners submit that Koster anticipates claim 12 and respectfully
`
`request that the Board institute review of claim 12 as part of IPR2015-00163.
`
`IV. Claim
`Claim 12 is reproduced below—along with the language of claim 11 from
`
`which it depends—with the significant language highlighted:
`
`
`
`11. The computer system of claim 1 wherein each of the processing
`nodes is programmed to complete a memory transaction after
`receiving a first number of responses to a first probe, the first number
`being fewer than the number of processing nodes.
`
`
`
`12. The computer system of claim 11 wherein the probe filtering unit
`has temporary storage associated therewith for holding read response
`data from one of the cache memories, and the first number is one.
`
`
`
`4
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`(emphasis added).
`
`
`V. Argument
`Referencing the example depicted in Koster’s Fig. 9, the Petition addresses
`
`each feature of claim 12. For instance, the Petition states: “in the example of FIG.
`
`9, a requesting microprocessor 182 necessarily completes its memory transaction
`
`based on a single response from a microprocessor 188 that is determined to be
`
`storing a copy of requested data” (emphasis added). See Petition, p. 36. In
`
`referencing the example shown in FIG. 9 of Koster, the Petition asserts that Koster
`
`discloses a requesting microprocessor 182 receiving one and only one response
`
`from a plurality of microprocessors 184, 186 and 188 in response to a probe
`
`request. That is, in the example shown in FIG. 9, the requesting microprocessor
`
`182 receives a single response from microprocessor 188, with no responses being
`
`received from microprocessors 184 and 186. Thus, in this disclosed example,
`
`which was cited in the Petition, the requesting microprocessor 182 is indeed
`
`programmed to complete its memory transaction after receiving one (and only one)
`
`response. This is evident from the fact that the Koster processor performs the
`
`memory transaction in response to the one and only response, when no other
`
`responses are received. After all, in the absence of such programming, the Koster
`
`processor would not have similarly responded. As such, as noted in the Petition,
`
`this disclosure alone is sufficient to satisfy claim 12.
`5
`
`
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`
`While the Petition clearly relies on Koster’s Fig. 9 disclosure,
`
`misapprehension of this argument (and the corresponding portion of Koster) led to
`
`denied institution of the Koster ground against claim 12. In greater detail, while
`
`the Petition’s argument focused solely on the exemplary single response memory
`
`transaction shown in FIG. 9, the Board instead focused on the fact that Koster’s
`
`system supports memory transactions that may involve multiple responses, where
`
`the “requesting processor 182 could potentially receive one, two, or three
`
`responses with copies of the requested data” (emphasis added). See Decision, p.
`
`23. But the ability of Koster’s system to support memory transactions that involve
`
`multiple responses is not relevant to the language of claim 12, as Koster’s system
`
`clearly supports memory transactions that involve a single response, and such
`
`single response transactions alone satisfy the features of claim 12. After all, as
`
`indicated above, through its Fig. 9 example, Koster discloses a processor that
`
`reacts to a single probe response by performing a memory transaction. This
`
`processor configuration is sufficient to meet claim 12, and it is not undone by how
`
`that processor reacts when facing scenarios that involve multiple probe responses.
`
`Importantly, given the Petition’s focus on single response memory
`
`transactions as satisfying claim 12, the Decision’s assertion that the Petition makes
`
`no attempt to “point us to any disclosure in Koster that the memory transaction
`
`occurs before all responses are in” (emphasis added) is neither surprising nor is it a
`
`
`
`6
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`deficiency of the Petition. See Decision, p. 23. Rather, through reference to the
`
`example of FIG. 9 of Koster, the Petition points out Koster’s disclosure of a node
`
`that completes a memory transaction after receiving just one response to a probe,
`
`thus satisfying claim 12. Inasmuch as the Fig. 9 node (i.e., microprocessor 182)
`
`completes its memory transaction after receiving only one response, the Petition
`
`adds that said node is “necessarily programmed” to do the same. See Petition, p.
`
`36.
`
`The Decision reveals a further but distinct misapprehension of the Petition’s
`
`application of Koster when criticizing the Petition for its failure to demonstrate that
`
`Koster’s microprocessors are programmed to complete memory transactions
`
`“before all the responses are in.” See Decision, p. 23. Specifically, this criticism is
`
`the result of a misapprehension of the Petition’s application of Koster to the
`
`language of claim 12. Turning first to the Petition’s application of Koster, no
`
`attempt is made to address whether Koster completes memory transactions “before
`
`all responses are in,” nor is this a deficiency of the Petition. Rather, through
`
`reference to Fig. 9 of Koster, the Petition points out Koster’s disclosure of a node
`
`that completes a memory transaction after receiving just one response to a probe,
`
`thus satisfying claim 12. Inasmuch as the Fig. 9 node (i.e., microprocessor 182)
`
`completes its memory transaction after receiving only one response, the Petition
`
`
`
`7
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`adds that said node is “necessarily programmed” to do the same. See Petition, p.
`
`36.
`
`The Petition does not address whether Koster’s nodes are programmed to
`
`complete memory transactions “before all responses are in,” because the Petition
`
`rightly recognized no such limitation in claim 12 when viewed through the prism
`
`of the broadest reasonable interpretation standard. Rather, as implicit from its
`
`application of Koster's Fig. 9 implementation to claim 12, the Petition treated that
`
`claim consistent with its plain language1 - as merely requiring nodes programmed
`
`to complete a memory transaction after receiving one response to a first probe.
`
`Inasmuch as claim 11 recites “after receiving a first number of responses” and
`
`claim 12 merely indicates that the first number is “one,” there exists no basis for
`
`the Decision’s introduction of “before all responses are in,” nor its denial of Koster
`
`for allegedly failing to meet this non-limitation. Rather, the Board’s interpretation
`
`of claim 12 as requiring “before all responses” reveals its misapprehension, since
`
`this interpretation introduces a boundary that is left unspecified by the plain claim
`
`language of claims 11/12.
`
`
`1 Section III(C), entitled “Claim Construction under 37 C.F.R. §§ 42.104(b)(3),”
`
`submits that “all remaining claims [not specifically construed in the Petition] be
`
`given their plain meaning.” Petition, pp. 4-5.
`
`
`
`8
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`
`In attempting to justify its denial of the Koster ground against claim 12, the
`
`Decision addresses a partial quote from the Petition, as follows: “We are, therefore,
`
`not persuaded that Petitioner has shown that Koster’s requesting microprocessor is
`
`‘necessarily programmed to complete [its memory] transaction after receiving one
`
`response to the broadcast request for data.’” Decision, p. 23. This point of
`
`apparent contention is moot, however, as it is the product of misapprehension
`
`regarding the Petition’s argument as applied to the plain meaning of the claim 12
`
`language of concern. Specifically, in the Petition, the “necessarily programmed”
`
`language was offered to describe the actions of microprocessor 182 of Koster in
`
`the context of the Fig. 9 exemplary flow, as that particular microprocessor is
`
`indeed disclosed as being programmed (i.e., it is necessarily programmed) to
`
`complete the particular memory transaction shown in Fig. 9, albeit after receiving
`
`one and only one response to the broadcast request for data from the other
`
`microprocessors 184, 186 and 188 (, i.e., a single response from microprocessor
`
`188 and no responses from microprocessors 184 and 186). Rather, the Petition
`
`offers that Koster discloses a processing node programmed to complete a memory
`
`transaction after receiving one response to a first probe, consistent with the plain
`
`meaning of claim 12.
`
`Finally, the Decision offers that “Petitioner does not point us to any
`
`disclosure in Koster that the memory transaction occurs before all the responses
`
`
`
`9
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`are in.” Decision, p. 23. As indicated above, this position assumes that the claim
`
`requires the node to be programmed to complete its memory transaction before all
`
`the responses are in, which reflects a misapprehension of the plain meaning
`
`addressed in the Petition. Claim 12 instead simply requires that each of the
`
`processing nodes is programmed to complete a memory transaction after receiving
`
`one response to a first probe. Where a first probe elicits a response from a single
`
`microprocessor, as in Fig. 9, the microprocessors described by Koster are
`
`programmed to complete the corresponding memory transaction after receiving the
`
`single response, perfectly consistent with the plain language of the claim. See
`
`Petition, p. 36; see also Decision, p. 23 (acknowledging that in the exemplary flow
`
`illustrated in Fig. 9, Koster completes a memory transaction after receiving one
`
`response). Whether or how Koster programs its microprocessors to handle
`
`memory transactions when more than one microprocessor responds to a probe
`
`therefore does not undo what Koster sets forth with respect to Fig. 9. Nor does
`
`disclosure of additional detail regarding the handling of two or more responses
`
`change the fact that the limitations of claim 12 are fully met by the Fig. 9
`
`disclosure of Koster, as applied in the Petition against the plain meaning of claim
`
`12, whose only temporal requirement is for transactions to be performed after
`
`receipt of the first probe.
`
`
`
`10
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`
`Accordingly, the Decision misapprehended the Petition’s application of
`
`Koster to the language of claim 12. Because, for the reasons noted above, the
`
`Petition adequately demonstrates how Koster explicitly discloses that “each of the
`
`processing nodes is programmed to complete a memory transaction after receiving
`
`a first number of responses to a first probe” “and the first number is one,” as
`
`required by claim 12, Petitioner respectfully requests the Board reconsider its
`
`Decision and institute the Petition’s proposed ground for unpatentability of claim
`
`12 based on Koster in the pending inter partes review.
`
`VI. Conclusion
`For the foregoing reasons, Petitioners respectfully request rehearing of claim
`
`12 of the ’121 Patent and respectfully request that inter partes review be instituted
`
`Respectfully submitted,
`
`
`/ Roberto J. Devoto /
`
`Roberto Devoto, Reg. No. 55,108
`W. Karl Renner, Reg. No. 41,265
`Attorneys for Petitioner
`
`
`
`on Ground 1 for that claim.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` .
`
`
`
`
`
`Dated: 5-22-15
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`11
`
`

`
`IPR2015-00163
`Patent 7,296,121
`
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 CFR §§ 42.6(e), the undersigned certifies that on May 22,
`
`2015, a complete and entire copy of this Petitioner’s Request for Hearing was
`
`provided via email, to the Patent Owner by serving the correspondence address of
`
`record as follows:
`
`Jonathan D. Baker
`Farney Daniels PC
`411 Borel Avenue, Suite 350
`San Mateo, CA 94402
`
`Bryan Atkinson
`Farney Daniels PC
`800 S. Austin, Suite 200
`Georgetown, TX 78626
`
`Email: jbaker@farneydaniels.com
`Email: batkinson@farneydaniels.com
`Email: fdlitsupport@farneydaniels.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/Edward G. Faeth/
`
`Edward G. Faeth
`Fish & Richardson P.C.
`3200 RBC Plaza
`60 South Sixth Street
`Minneapolis, MN 55402
`(202) 626-6420

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket