throbber
Trials@uspto.gov
`571-272-7822
`
`Paper 26
`Entered: July 23, 2015
`
`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.,
`Petitioner,
`
`v.
`
`MEMORY INTEGRITY, LLC,
`Patent Owner.
`
`Cases IPR2015-00159 and IPR2015-00163
`Patent 7,296,121 B21
`
`Before JENNIFER S. BISK, NEIL T. POWELL, and
`KERRY BEGLEY, Administrative Patent Judges.
`
`POWELL, Administrative Patent Judge.
`
`ORDER
`
`Conduct of the Proceeding
`
`37 C.F.R. § 42.5
`
`1 This Decision addresses issues pertaining to each of these cases. The
`parties are not authorized to use this style heading for any subsequent
`papers.
`
`

`
`IPR2015-00159 and IPR2015-00163
`Patent 7,296,121 B2
`
`
`
`A conference call in the above proceedings was held on July 21, 2015,
`
`between counsel for Patent Owner, counsel for Petitioner in these cases,
`
`counsel for Petitioner in IPR2015-00158,2 and Judges Bisk, Powell, and
`
`Begley. Patent Owner initiated the conference call to confer with us
`
`regarding filing a motion to amend in these cases and in IPR2015-00158.
`
`DISCUSSION
`
`In the call, we explained that a motion to amend under 37 C.F.R.
`
`§ 42.121 may cancel claims and/or propose substitute claims. As we further
`
`explained, a motion to amend may propose only a reasonable number of
`
`substitute claims, and there is a rebuttable presumption that only one
`
`proposed substitute claim will generally be needed to replace each
`
`challenged claim. 37 C.F.R. § 42.121(a)(3). We also noted that our rules
`
`were amended on May 19, 2015 to change the page limits for certain papers
`
`associated with a motion to amend. See Amendments to the Rules of
`
`Practice for Trials Before the Patent Trial and Appeal Board, 80 Fed. Reg.
`
`28,561, 28,565 (May 19, 2015).
`
`Additionally, we noted that further guidance regarding the mechanics
`
`and substance of motions to amend appears in Idle Free Systems, Inc. v.
`
`Bergstrom, Inc., IPR2012-00027 (PTAB June 11, 2013) (Paper 26), as
`
`well as MasterImage 3D, Inc. v. RealD Inc., IPR2015-00040 (PTAB
`
`July 15, 2015) (Paper 42). The latter paper clarifies certain guidance
`
`provided in the former.
`
`Patent Owner inquired whether it should 1) prepare substantively
`
`identical motions for these cases and IPR2015-00158, or 2) prepare
`
`
`2 In IPR2015-00158, a different set of petitioners challenge the patent that is
`at issue in these cases.
`
`2
`
`

`
`IPR2015-00159 and IPR2015-00163
`Patent 7,296,121 B2
`
`
`substantively unique motions for each of the cases. We advised that Patent
`
`Owner should do the latter, taking care that any amendments in proposed
`
`substitute claims in one case do not conflict with amendments in proposed
`
`substitute claims in other cases.
`
`Petitioner inquired about provisions for potentially changing due dates
`
`related to responding to any motions to amend that Patent Owner may file.
`
`We reminded the parties that they are authorized to stipulate changes to due
`
`dates 1 through 5 in our scheduling order. IPR2015-00158, Paper 8, 1;
`
`IPR2015-00159, Paper 13, 1; IPR2015-00163, Paper 19, 1. We encouraged
`
`the parties to cooperate to resolve any issues that may arise regarding due
`
`dates. Additionally, we noted that if the parties should have a due date issue
`
`they cannot resolve after collaborating, they may contact us to address the
`
`issue.
`
`
`
`In consideration of the foregoing, it is:
`
`ORDER
`
`ORDERED that Patent Owner has satisfied the requirement of
`
`conferring with us prior to filing a Motion to Amend under 37 C.F.R.
`
`§ 42.121(a).
`
`
`
`
`
`3
`
`

`
`IPR2015-00159 and IPR2015-00163
`Patent 7,296,121 B2
`
`
`PETITIONER:
`
`Lewis Popovski
`lpopovski@kenyon.com
`
`Michael Sander
`msander@kenyon.com
`
`Zaed Billah
`zbillah@kenyon.com
`
`
`
`PATENT OWNER:
`
`Jomathan Baker
`jbaker@farneydaniels.com
`
`Bryan Atkinson
`memoryintegrityIPR@farneydaniels.com
`
`4

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