throbber
Alicea, Franchesca
`
`From:
`Sent:
`To:
`Cc:
`Subject:
`
`Good afternoon,
`
`Trials
`Thursday, May 14, 2020 2:53 PM
`Venkat Konda; Trials
`Modi, Naveen; FlexLogix Konda PGR; Anderson, Paul M.
`RE: PGR2019-00037 & 42: Request for more pages - Revised Motion to Amend by
`Tomorrow May 15, 2020
`
`1. The page limits for Patent Owner’s Revised Motion to Amend and for Petitioner’s opposition are increased to 30 pages.
`
`2. Patent Owner’s proposed format for identifying support for claim limitations in the priority documents is acceptable.
`
`Regards,
`
`Andrew Kellogg,
`Supervisory Paralegal
`Patent Trial and Appeal Board
`USPTO
`andrew.kellogg@uspto.gov
`(571)272-7822
`
`From: Venkat Konda <venkat@kondatech.com>  
`Sent: Thursday, May 14, 2020 4:08 AM 
`To: Trials <Trials@USPTO.GOV>; Kellogg, Andrew <Andrew.Kellogg@USPTO.GOV> 
`Cc: Modi, Naveen <naveenmodi@paulhastings.com>; FlexLogix Konda PGR <PH‐FlexLogix‐Konda‐
`PGR@paulhastings.com>; Anderson, Paul M. <paulanderson@paulhastings.com>; Venkat Konda 
`<venkat@kondatech.com> 
`Subject: PGR2019‐00037 & 42: Request for more pages ‐ Revised Motion to Amend by Tomorrow May 15, 2020 
`
`To,
`Patent Trial and Appeal Board,
`United States Patent and Trademark Office.
`
`Dear Mr. Kellogg,
`
`Tomorrow May 15, 2020 is the due date, as I, Patent Owner, am intending to submit Patent Owner's Revised
`Motion to Amend.
`I am cc'ing the Petitioner as well. (Since the following two questions are procedural or prior discussed matter, I
`did not contact the Petitioner and cc'ing them in this email).
`I have two procedural questions:
`
`1. For the PO's Motion to Amend submitted on December 11, 2019, Board approved, "In both PGR2019-
`00037 and PGR2019-00042, the page limits for Patent Owner’s motion to amend and for Petitioner’s
`opposition to Patent Owner’s motion to amend are increased to 30 pages". Is this valid for Revised
`Motion to Amend as well? If not, I would like to request page limit extension to 30 pages for both the
`proceedings just like for Motion to Amend on December 11, 2019.
`2. Also I have a question, regarding the format of Revised Motion to Amend:
`
`1
`
`Ex. 3002
`PGR2019-00037
`
`

`

`1. To explain my question, I am using the attached Motion to Amend submitted on December 11,
`2019 as a sample.
`2. First I ADDED line numbers to each page of the Substitute claims in the Appendix I Page # 1 -
`Page # 24 (Please refer to Appendix I # 1 - Page #24 of the attached sample document)
`3. Next, In the table, within the 30 pages allowed, the original table (please refer to Pages 8-9 in the
`Motion pages of the attached sample document) needs to be modified with corresponding
`columns for each of the priority application. So this will add 3 more columns to the table. To
`accommodate 3 more columns I have removed the "Amended Claim language" in the first
`column of that table titled "Reference to the pages/lines to Claim Language in Appendix I" and
`replaced with page/line numbers (for example: Page 2:21 - Page 3:3 in the first row and first
`column of the attached sample document in Page 9). PLEASE LET ME KNOW if this is the
`correct way of submitting Revised Motion to Amend.
`
`Your guidance is critical for me as a Pro se Patent Owner. Please advise.
`
`Respectfully,
`
`Venkat Konda
`Patent owner for PGR2019-000437 & 42
`Email: venkat@kondatech.com
`Phone # 408-472-3273
`
`
`--
`
`NOTICE: This e-mail and any attached documents are CONFIDENTIAL and intended solely for the use of the individual or entity to whom they are
`addressed, and may be a communication privileged by law. If you have received this email in error, please notify the sender immediately and delete
`all copies from your system. Any review, use, retention, dissemination, distribution, printing or copying of this e-mail is strictly prohibited. Thank
`You.
`
`2
`
`

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