throbber
Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 1 of 6
`Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 1 of 6
`
`
`
`
`
`EXHIBIT 1
`EXHIBIT 1
`
`

`

`3/20/23, 7:18 PM
`
`Mail - Lewis Hudnell - Outlook
`Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 2 of 6
`Re: VoIP-Pal v. Amazon (WDTX 2020)
`Lewis Hudnell <lewis@hudnelllaw.com>
`Fri 3/10/2023 3:03 PM
`To: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>;Kelley, Christopher L. (PAO)
`<CKelley@perkinscoie.com>;Nick Gikkas <Nick@hudnelllaw.com>;Sean Parmenter
`<sean@parmenterip.com>
`Dan,
`
`Amazon has no legimate basis to object to entry of a schedule. If Amazon will not agree to entry of a
`schedule, then VoIP-Pal intends to move for entry of the version of the schedule that I last sent you.
`Please confirm whether Amazon will maintain its objecon and oppose the moon.
`
`Regarding VoIP-Pal's request that Amazon idenfy documents, VoIP-Pal disagrees that it is trying to flip
`the burden of proof. You asserted that "Amazon’s system does not have any roung message that
`contains such a [me to live] field." If Amazon has documents that it believes supports that statement,
`then it is incumbent upon Amazon to idenfy them. Indeed, such documents would be covered by VoIP-
`Pal's RFPs 10, 11, and 14 and ROG 3.
`
`While VoIP-Pal is willing to accept Amazon's producon in the 2021 case for use in this case, VoIP-Pal will
`agree to do so only under the interim protecve order and not the protecve order in the 2021 case.
`VoIP-Pal intends to seek entry of a new protecve order in this case. Please confirm that VoIP-Pal may
`use these documents under the interim protecve order.
`
`We intend to file the opposed moon for reconsideraon today.
`
`Regards,
`
`Lewis E. Hudnell, III
`Hudnell Law Group PC
`t: 650.564.7720
`f: 347.772.3034
`m: 917.861.3494
`e: lewis@hudnelllaw.com
`www.hudnelllaw.com
`
`This e-mail message is intended for the sole use of the intended recipient(s) and may contain
`informaon that is confidenal, privileged and/or aorneys' work product. Any review or distribuon by
`any other person is prohibited. If you are not an intended recipient, please immediately contact the
`sender and delete all copies.
`
`From: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Sent: Wednesday, March 8, 2023 7:28 PM
`To: Lewis Hudnell <lewis@hudnelllaw.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>; Kelley, Christopher L. (PAO) <CKelley@perkinscoie.com>;
`
`https://outlook.office.com/mail/deeplink?popoutv2=1&version=20230310007.16&view=print
`
`1/5
`
`

`

`Mail - Lewis Hudnell - Outlook
`3/20/23, 7:18 PM
`Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 3 of 6
`Nick Gikkas <Nick@hudnelllaw.com>; Sean Parmenter <sean@parmenterip.com>
`Subject: RE: VoIP-Pal v. Amazon (WDTX 2020)

`Lewis,
`
`Amazon maintains that no schedule should be entered if VoIP-Pal cannot idenfy a basis for asserng that the
`“roung message” limitaon, as construed by the Court, is met by the accused system. If VoIP-Pal cannot idenfy
`such a basis but intends to seek reconsideraon of the Court’s claim construcon order, then the pares should
`address the case schedule aer the resoluon of that moon for reconsideraon. Amazon will oppose any such
`moon for reconsideraon.
`
`In regard to your request that Amazon idenfy proof of noninfringement, you are trying to flip the burden of
`proof and are asking Amazon to prove a negave. This is made all the more difficult given VoIP-Pal’s vague and
`deficient infringement contenons regarding what communicaons VoIP-Pal contends constutes the alleged
`“roung message.” VoIP-Pal bears the burden to maintain a basis for its infringement allegaons throughout the
`life of this case.
`
`VoIP-Pal is well-aware that Amazon does not charge for Alexa calling. Given that, VoIP-Pal also knows that
`Amazon does not generate any “message” that contains a “me-to-live field,” which, as I menoned previously,
`the ‘606 patent says “holds a value represenng the number of seconds the call is permied to be acve, based
`on subscriber available minutes and other billing parameters.” (‘606 patent at 21:55-60.)
`
`For purposes of discovery in this acon, Amazon designates that the documents Amazon produced in the 2021
`case are also produced in this case. Should VoIP-Pal believe it needs to confirm Amazon’s posion regarding the
`“roung message” limitaon, it is welcome to refer to such producon to do so.
`
`Regards,
`Dan
`
`
`From: Lewis Hudnell <lewis@hudnelllaw.com>
`Sent: Thursday, March 2, 2023 9:24 AM
`To: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>; Kelley, Christopher L. (PAO) <CKelley@perkinscoie.com>;
`Nick Gikkas <Nick@hudnelllaw.com>; Sean Parmenter <sean@parmenterip.com>
`Subject: Re: VoIP-Pal v. Amazon (WDTX 2020)
`
`Dan,
`
` I
`
` accepted your changes and made a couple of changes to allow more me to finish expert discovery.
`Please let me know if these changes are agreeable.
`
`Regarding the roung message issue, VoIP-Pal intends to move for reconsideraon of the Court's claim
`construcon order, specifically to request that the me to live field be dropped from the construcon. I
`assume that Amazon opposes the moon but please let me know if you would like to meet and confer
`on the issue.
`
`In the meanme, please provide the Bates numbers of whatever documents Amazon has produced in
`this case that support your statement that "Amazon’s system does not have any roung message that
`contains such a [me to live] field."
`
`Many thanks.
`
`https://outlook.office.com/mail/deeplink?popoutv2=1&version=20230310007.16&view=print
`
`2/5
`
`

`

`Mail - Lewis Hudnell - Outlook
`Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 4 of 6
`
`3/20/23, 7:18 PM
`
`Lewis E. Hudnell, III
`Hudnell Law Group PC
`t: 650.564.7720
`f: 347.772.3034
`m: 917.861.3494
`e: lewis@hudnelllaw.com
`www.hudnelllaw.com
`
`This e-mail message is intended for the sole use of the intended recipient(s) and may contain
`informaon that is confidenal, privileged and/or aorneys' work product. Any review or distribuon by
`any other person is prohibited. If you are not an intended recipient, please immediately contact the
`sender and delete all copies.
`
`
`From: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Sent: Monday, February 27, 2023 10:36 AM
`To: Lewis Hudnell <lewis@hudnelllaw.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>; Kelley, Christopher L. (PAO) <CKelley@perkinscoie.com>;
`Nick Gikkas <Nick@hudnelllaw.com>; Sean Parmenter <sean@parmenterip.com>
`Subject: RE: VoIP-Pal v. Amazon (WDTX 2020)
`
`Lewis,
`
`Thank you for the dra schedule. We have proposed edits in the aached. The change of dates in October is to
`accommodate a pre-scheduled trip I have planned to be out of the country. We also moved some later dates in
`the schedule to preclude filings being due immediately aer the winter holidays. We also propose that Amazon
`will respond to the outstanding discovery requests within two weeks aer the Court enters the schedule.
`
`But before Amazon will agree to this schedule, we want to know what basis, if any, VoIP-Pal has for connuing
`with this case. The Court construed “roung message” to require a “me to live field.” The ‘606 patent explicitly
`states that the “me to live” field “holds a value represenng the number of seconds the call is permied to be
`acve, based on subscriber available minutes and other billing parameters.” (‘606 patent at 21:55-60.) Amazon’s
`system does not have any roung message that contains such a field.
`
` I
`
` understand that VoIP-Pal disagrees with that claim construcon. If so, the appropriate steps would be to
`spulate to a final judgment of noninfringement and then appeal the construcon of “roung message.” It is not
`appropriate for VoIP-Pal to connue this ligaon and cause Amazon to incur addional, unnecessary expense if
`VoIP-Pal has no basis for contending that the “roung message” limitaon is met.
`
`So please let us know VoIP-Pal’s basis for contending that the limitaon is met in the accused system, or please
`agree to spulate to a final judgment of noninfringement and then raise VoIP-Pal’s issue on appeal.
`
`Regards,
`Dan
`
`
`From: Lewis Hudnell <lewis@hudnelllaw.com>
`Sent: Monday, February 27, 2023 7:04 AM
`To: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>; Kelley, Christopher L. (PAO) <CKelley@perkinscoie.com>;
`Valenne, James (PAO) <JValenne@perkinscoie.com>; Nick Gikkas <Nick@hudnelllaw.com>; Sean Parmenter
`
`https://outlook.office.com/mail/deeplink?popoutv2=1&version=20230310007.16&view=print
`
`3/5
`
`

`

`3/20/23, 7:18 PM
`Mail - Lewis Hudnell - Outlook
`Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 5 of 6
`<sean@parmenterip.com>
`Subject: Re: VoIP-Pal v. Amazon (WDTX 2020)
`
`Dan,
`
` I
`
` don't believe that we received a response on the schedule. Please advise. Many thanks.
`
`
`Lewis E. Hudnell, III
`Hudnell Law Group PC
`t: 650.564.7720
`f: 347.772.3034
`m: 917.861.3494
`e: lewis@hudnelllaw.com
`www.hudnelllaw.com
`
`This e-mail message is intended for the sole use of the intended recipient(s) and may contain
`informaon that is confidenal, privileged and/or aorneys' work product. Any review or distribuon by
`any other person is prohibited. If you are not an intended recipient, please immediately contact the
`sender and delete all copies.
`
`From: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Sent: Friday, February 17, 2023 4:51 PM
`To: Lewis Hudnell <lewis@hudnelllaw.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>; Kelley, Christopher L. (PAO) <CKelley@perkinscoie.com>;
`Valenne, James (PAO) <JValenne@perkinscoie.com>; Nick Gikkas <Nick@hudnelllaw.com>; Sean Parmenter
`<sean@parmenterip.com>
`Subject: RE: VoIP-Pal v. Amazon (WDTX 2020)
`
`Lewis,
`
` am coordinang with my client and will get you a response next week.
`
`
`Dan
`
`From: Lewis Hudnell <lewis@hudnelllaw.com>
`Sent: Wednesday, February 15, 2023 8:30 PM
`To: Shvodian, Daniel T. (PAO) <DShvodian@perkinscoie.com>
`Cc: Tyler, M. Craig (AUS) <CTyler@perkinscoie.com>; Kelley, Christopher L. (PAO) <CKelley@perkinscoie.com>;
`Valenne, James (PAO) <JValenne@perkinscoie.com>; Nick Gikkas <Nick@hudnelllaw.com>; Sean Parmenter
`<sean@parmenterip.com>
`Subject: VoIP-Pal v. Amazon (WDTX 2020)
`
`Dan,
`
`Please see the aached proposed amended scheduling order for the 2020 case. It tracks the Court's
`default me periods based on today's Markman hearing except that I added a week to avoid the
`holidays. Please let me know if the dates are agreeable to Amazon and please also let me know
`Amazon's proposed date for responding to the pending discovery. Many thanks.
`
`
` I
`
`https://outlook.office.com/mail/deeplink?popoutv2=1&version=20230310007.16&view=print
`
`4/5
`
`

`

`3/20/23, 7:18 PM
`
`Mail - Lewis Hudnell - Outlook
`Case 6:20-cv-00272-ADA Document 90-2 Filed 03/20/23 Page 6 of 6
`
`This e-mail message is intended for the sole use of the intended
`recipient(s) and may contain informaon that is confidenal,
`privileged and/or aorneys' work product. Any review or distribuon by
`any other person is prohibited. If you are not an intended recipient,
`please immediately contact the sender and delete all copies.
`
`
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply
`email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.
`
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply
`email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.
`
`NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply
`email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you.
`
`https://outlook.office.com/mail/deeplink?popoutv2=1&version=20230310007.16&view=print
`
`5/5
`
`

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