throbber
From:
`To:
`Cc:
`
`Subject:
`Date:
`
`Daniel Kiang
`Trials
`IPR50095-0045IP1; IPR50095-0045IP3; AppleIPR745-1; AppleIPR745-3; Nicholas Stephens; AppleIPR127-1;
`"AXF-PTAB"; Andrew Patrick; bisenius@fr.com; leung@fr.com; pking@fr.com; IPR50095-0046IP1
`RE: IPR2022-01291, IPR2022-01465, IPR2022-01299 - September 27, 2023 Conference Call
`Wednesday, September 27, 2023 12:39:50 AM
`
`CAUTION: This email has originated from a source outside of USPTO. PLEASE CONSIDER THE SOURCE before
`responding, clicking on links, or opening attachments.
`
`Dear Board,
`
`Pursuant to the Board’s September 5 Order in IPR2022-01291 and IPR2022-01465 and the Board’s
`September 25 email in IPR2022-01299, the parties tentatively propose the following schedule,
`subject to confirmation during the conference call, for the IPRs concerning the ’745 Patent (IPR2022-
`01291, -01465) and the IPR concerning the ’127 Patent (IPR2022-01299):
`
`Anthony Deposition (’127 Patent IPR Only)
`Duckworth Deposition (’745 Patent IPRs Only)
`Patent Owner Sur-Reply (’127 Patent IPR Only)
`Apple’s Response to Expert Testimony (’745
`Patent IPRs Only)
`Motion to Exclude (All IPRs)
`King Deposition (’127 Patent IPR Only)
`Opposition to Motion to Exclude (All IPRs)
`
`Apple’s Observations on Cross-Examination (’127
`Patent IPR Only)
`Reply to Motion to Exclude (All IPRs)
`Parties’ Exchange (Service) of Oral Hearing
`Demonstratives (All IPRs)
`Filing of Oral Hearing Demonstratives (All IPRs)
`Oral Hearing (All IPRs)
`
`Original Due Date
`
`N/A
`N/A
`Oct. 11
`N/A
`
`Oct. 13
`N/A
`Oct. 19 (’127) /Oct.
`20 (’745)
`N/A
`
`Oct. 27
`Oct. 25
`
`N/A
`Nov. 1
`
`Joint Proposed
`New Due Date
`Fri., Oct. 13
`Wed., Oct. 18
`Fri., Oct. 20
`Fri., Oct. 27
`
`Mon., Oct. 30
`Fri., Nov. 3
`Mon., Nov. 6
`
`Fri., Nov. 10
`
`Mon., Nov. 13
`Mon., Nov. 13
`
`Wed., Nov. 15
`Fri., Nov. 17
`
`Additionally, pursuant to the Board’s September 5 Order in IPR2022-01291 and -01465, Patent
`Owner confirms that its sur-replies in IPR2022-01291 and -01465 will conform to the Board’s rules,
`including the default 5,600 word limit for a sur-reply.
`
`Patent Owner has also arranged for a court reporter to attend and transcribe the conference call.
`Petitioner’s counsel has been copied on this email.
`
`Best regards,
`Daniel
`
`Exhibit 3006
`
`

`

`
`
`Daniel Kiang
`Partner
`Daniel.Kiang@knobbe.com
`949-721-5205 Direct
`Knobbe Martens
`2040 Main St., 14th Fl.
`Irvine, CA 92614
`www.knobbe.com/daniel-kiang
`
`
`From: Trials <Trials@USPTO.GOV>
`Sent: Tuesday, September 26, 2023 5:07 AM
`To: Daniel Kiang <Daniel.Kiang@knobbe.com>; Trials <Trials@USPTO.GOV>
`Cc: IPR50095-0045IP1 <IPR50095-0045IP1@fr.com>; IPR50095-0045IP3 <IPR50095-
`0045IP3@fr.com>; AppleIPR745-1 <AppleIPR745-1@knobbe.com>; AppleIPR745-3 <AppleIPR745-
`3@knobbe.com>; Nicholas Stephens <nstephens@fr.com>; 'AXF-PTAB' <AXF-PTAB@fr.com>;
`Andrew Patrick <patrick@fr.com>; bisenius@fr.com; leung@fr.com; pking@fr.com
`Subject: RE: IPR2022-01291, IPR2022-01465 - September 27, 2023 Conference Call
`
`Counsel,
`
`Yes, the Board intends to discuss those topics during this upcoming conference.
`
`Regards,
`
`Esther Goldschlager
`Supervisory Paralegal Specialist
`Patent Trial & Appeal Board
`U.S. Patent & Trademark Office
`
`From: Daniel Kiang <Daniel.Kiang@knobbe.com>
`Sent: Monday, September 25, 2023 4:49 PM
`To: Trials <Trials@USPTO.GOV>
`Cc: IPR50095-0045IP1 <IPR50095-0045IP1@fr.com>; IPR50095-0045IP3 <IPR50095-
`0045IP3@fr.com>; AppleIPR745-1 <AppleIPR745-1@knobbe.com>; AppleIPR745-3 <AppleIPR745-
`3@knobbe.com>; Nicholas Stephens <nstephens@fr.com>; 'AXF-PTAB' <AXF-PTAB@fr.com>;
`Andrew Patrick <patrick@fr.com>; bisenius@fr.com; leung@fr.com; pking@fr.com
`Subject: RE: IPR2022-01291, IPR2022-01465 - September 27, 2023 Conference Call
`
`CAUTION: This email has originated from a source outside of USPTO. PLEASE CONSIDER THE SOURCE before
`responding, clicking on links, or opening attachments.
`
`Dear Board,
`
`
`

`

`Patent Owner understands that the Board has scheduled a conference call on September 27 at 11
`am ET in IPR2022-01299 to discuss IPR2022-01291, IPR2022-01465, and IPR2022-01299. Patent
`Owner respectfully requests confirmation that the scheduled September 27 call will also address the
`issues outlined in the Board’s September 5 Order in IPR2022-01291 and IPR2022-01465, namely:
`“a potential increase of the Board’s default 5,600 word count limitation for Sur-replies,”
`“dates when the deposition [of Patent Owner’s expert] might take place,”
`“a filing deadline for the Response to Expert Testimony,” and
`“whether oral argument in these two cases might be delayed by a few weeks to
`accommodate the deposition date and the filing deadline.”
`
`
`Petitioner’s counsel has been copied on this email.
`
`Best regards,
`Daniel
`
`Daniel Kiang
`Partner
`Daniel.Kiang@knobbe.com
`949-721-5205 Direct
`Knobbe Martens
`2040 Main St., 14th Fl.
`Irvine, CA 92614
`www.knobbe.com/daniel-kiang
`
`
`
`From: Trials <Trials@USPTO.GOV>
`Sent: Friday, September 22, 2023 6:08 AM
`To: Nicholas Stephens <nstephens@fr.com>; Trials <Trials@USPTO.GOV>; 'AXF-PTAB' <AXF-
`PTAB@fr.com>; Andrew Patrick <patrick@fr.com>; bisenius@fr.com; leung@fr.com; pking@fr.com
`Cc: IPR50095-0045IP1 <IPR50095-0045IP1@fr.com>; IPR50095-0045IP3 <IPR50095-
`0045IP3@fr.com>; AppleIPR745-1 <AppleIPR745-1@knobbe.com>; AppleIPR745-3 <AppleIPR745-
`3@knobbe.com>; 2Bcc <2Bcc@knobbe.com>; 2cmp <2cmp@knobbe.com>; 2Jzk
`<2Jzk@knobbe.com>; 2Jup <2Jup@knobbe.com>; 2Dck <2Dck@knobbe.com>
`Subject: RE: IPR2022-01291 - Petitioner's Unopposed Request to Correct the Petition Under 37 CFR
`§ 42.104(c)
`
`Counsel,
`
`The Board intends to discuss Petitioner’s request (below) during the anticipated conference call later
`this month per the Board’s Order of September 5, 2023.
`
`Regards,
`
`Esther Goldschlager
`Supervisory Paralegal Specialist
`Patent Trial & Appeal Board
`
`

`

`U.S. Patent & Trademark Office
`
`From: Nicholas Stephens <nstephens@fr.com>
`Sent: Thursday, September 21, 2023 1:37 PM
`To: Trials <Trials@USPTO.GOV>
`Cc: IPR50095-0045IP1 <IPR50095-0045IP1@fr.com>; IPR50095-0045IP3 <IPR50095-
`0045IP3@fr.com>; AppleIPR745-1 <AppleIPR745-1@knobbe.com>; AppleIPR745-3 <AppleIPR745-
`3@knobbe.com>
`Subject: IPR2022-01291 - Petitioner's Unopposed Request to Correct the Petition Under 37 CFR §
`42.104(c)
`
`CAUTION: This email has originated from a source outside of USPTO. PLEASE CONSIDER THE SOURCE before
`responding, clicking on links, or opening attachments.
`
`
`
`Your Honors,
`
`During the parties’ recent meet and confer in relation to Patent Owner’s requested authorizations
`for a motion to strike and to submit additional evidence with its Sur-Reply, Patent Owner contended
`that Section I.D of Petitioner’s Reply “requests a substantive change to the petition to correct
`typographical errors,” and argued that “such a request can only be made via motion under §
`42.104(c).”
`
`While the Reply cited cases that Petitioner believes demonstrates authority for the Board to correct
`a typographical error even in the absence of a motion under § 42.104(c), out of an abundance of
`caution, Petitioner respectfully requests authorization under § 42.104(c) to correct the Petition’s
`typographical error as identified in Section I.D of the Reply. Specifically, in addressing limitations
`[20.0]-[20.8] in Ground 1B, the Petition at page 27 includes a mistaken cross-citation to limitations
`from independent claim 15 (i.e., [15.0]-[15.8]) rather than independent claim 1 (i.e., [1.0]-[1.7]).
`Petitioner proposes to correct the Petition by replacing the citation to “[15.0] - [15.8]” with “Ground
`1A, [1.0] - [1.7]” on page 27, consistent with the parallel limitations recited in claims 1 and 20.
`Petitioner proposes no other corrections to the body of the Petition. Clean and redlined versions of
`the proposed corrected Petition are attached for reference.
`
`Petitioner submits that good cause exists for the correction given that the parties have consistently
`addressed corresponding limitations from claims 1 and 20 together in the POR and Reply.
`Petitioner’s intent to cross-cite limitations [1.0]-[1.7] rather than [15.0]-[15.8] is also evident from
`the Petition’s proper cross-citation to claim 1 in addressing claim 20 in Ground 2B (pages 41-42) and
`Petitioner’s proper cross-citation to claim 1 in addressing claim 20 in both grounds of the Petition in
`IPR2022-01465. The Board has also confirmed that § 42.104(c) permits corrections to petitions
`based on motions filed after institution. See, e.g., Group III Int’l, Inc. v. Targus Int’l LLC, IPR2021-
`00371, Paper 88 at pp. 9-13 (PTAB July 6, 2022).
`
`The parties have conferred and Patent Owner indicates that it does not oppose Petitioner’s request.
`
`

`

`
`Should the Board desire a conference call, the parties will provide their availability. The parties are
`also amenable to discussing this request at the conference call that we anticipate scheduling later
`this month pursuant to the Board’s Order of September 5, 2023 (Paper 43).
`
`Best Regards,
`Nick Stephens
`
`Counsel for Petitioner Apple Inc.
`
`Nick Stephens :: Principal :: Fish & Richardson P.C.
`612 766 2018 direct :: nstephens@fr.com :: fr.com
`
`************************************************************************************
`****************************************
`This email message is for the sole use of the intended recipient(s) and may contain
`confidential and privileged information. Any unauthorized use or disclosure is
`prohibited. If you are not the intended recipient, please contact the sender by
`reply email and destroy all copies of the original message.
`************************************************************************************
`****************************************
`
`
`NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and
`privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not
`the intended recipient, please contact the sender by reply email and destroy all copies of the original
`message.
`
`NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and
`privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not
`the intended recipient, please contact the sender by reply email and destroy all copies of the original
`message.
`
`

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