throbber
From:
`Sent:
`To:
`Cc:
`
`Subject:
`
`Follow Up Flag:
`Flag Status:
`
`Dear Board,
`
`Lesovitz, Jeffrey <JLesovitz@bakerlaw.com>
`Wednesday, October 30, 2019 6:16 PM
`Trials
`Goettle, Daniel; Rocci, Steven; Guest-TekIPR; BoxNomadix; 2dgm; Amy.Rodriguez;
`William.Shreve
`IPR2019-01191 -- Request to Submit Petitioner's Reply to Patent Owner Preliminary
`Response
`
`Follow up
`Flagged
`
`Petitioner Guest Tek Interactive Entertainment Ltd. respectfully requests authorization from the Board to
`promptly file a short reply to Patent Owner’s October 11, 2019 preliminary response. Specifically, Guest Tek
`requests authorization to file a reply limited to addressing Patent Owner’s newly raised arguments as to the
`priority date of the challenged claims and Patent Owner’s backup argument under 35 U.S.C. § 314(a), and
`believes that there is good cause for submitting a reply.
`
`First, Guest Tek intends to briefly address Patent Owner’s first argument that the challenged claims are entitled
`to an October 20, 2000 priority date. Guest Tek believes there is good cause for a reply addressing the specific
`applications relied upon by Patent Owner because the 917 patent claims priority to over 14 different patent
`applications, which in turn incorporate numerous other patent applications. In its proposed reply, Guest Tek
`intends to briefly address why: (1) the 060 application/890 provisional’s general disclosure of comparing an
`attribute received from a source device with profiles does not amount to performing that comparison
`specifically based on a source IP address as recited in limitations 1.C and 11.C (see Patent Owner’s prelim.
`resp. § VI.B.4); (2) why the Federal Circuit’s Knowles case is exactly on point as a result of that general, rather
`than specific, disclosure (prelim. resp. at 20); (3) why mere reference in the 890 provisional to “pass-through IP
`addresses,” for example, is far from disclosing the specific requirements of limitations 1.D and 11.D (prelim.
`resp. § VI.B.6); and (4) why block 220 in Figure 2’s reference to determining authorization based on an
`attribute associated with a “source, destination or content” (prelim. resp. § VI.B.6) does not disclose
`authentication based on both a source IP address and destination IP address (let alone the other requirements of
`combined limitations 1.C/11.C and 1.D/11.D).
`
`Second, Guest Tek also intends to briefly address Patent Owner’s backup argument that the Board should deny
`institution under Section 314(a). There is good cause because Guest Tek could not have reasonably predicted
`Patent Owner raising this argument in view of the correct facts regarding the district court case. In its proposed
`reply, Guest Tek intends to explain why: (1) Guest Tek did not delay in filing the IPR petition (prelim. resp. §
`VII.A.1) at least because the proceedings in the district court case were stayed for close to a year, Guest Tek
`diligently prepared its petition, and Guest Tek timely filed the petition after the stay was lifted; (2) the district
`court case is irrelevant to this inter partes review at least because invalidity of the 917 patent is not likely to be
`decided at the district court; even if it were, the district court would not reach a final decision until well after the
`Board’s decision; and the district court is also in the process of possibly rescheduling the trial date, which Guest
`Tek has requested be no earlier than the end of 2020; and (3) certain PTAB decisions that Patent Owner cites
`are inapposite, while other decisions in which the PTAB refused to deny institution under Section 314(a) apply.
`
`1
`
`IPR2019-01191
`Ex. 3001 p. 1 of 2
`
`

`

`In sum, Guest Tek respectfully requests the Board’s authorization to file the foregoing reply. If authorized,
`Guest Tek’s reply will only respond to arguments raised in the Patent Owner preliminary response as outlined
`above, will be promptly filed, and will comply with 37 C.F.R. §§ 42.23 and 42.24(c).
`
`Counsel for Patent Owner has stated that it opposes Petitioner’s request. Counsel for the parties are available
`for a conference call with the Board on Monday, November 4 at 2-5pm EST or the same time on Tuesday,
`November 5.
`
`Sincerely,
`Jeff
`
`Jeffrey W. Lesovitz
`Partner
`
`
`
`Cira Centre
`2929 Arch Street | 12th Floor
`Philadelphia, PA 19104-2891
`T +1.215.564.2406
`
`jlesovitz@bakerlaw.com
`bakerlaw.com
`
`This email is intended only for the use of the party to which it is
`addressed and may contain information that is privileged,
`confidential, or protected by law. If you are not the intended
`recipient you are hereby notified that any dissemination, copying
`or distribution of this email or its contents is strictly prohibited.
`If you have received this message in error, please notify us immediately
`by replying to the message and deleting it from your computer.
`
`Any tax advice in this email is for information purposes only. The content
`of this email is limited to the matters specifically addressed herein
`and may not contain a full description of all relevant facts or a
`complete analysis of all relevant issues or authorities.
`
`Internet communications are not assured to be secure or clear of
`inaccuracies as information could be intercepted, corrupted, lost,
`destroyed, arrive late or incomplete, or contain viruses. Therefore,
`we do not accept responsibility for any errors or omissions that are
`present in this email, or any attachment, that have arisen as a result
`of e-mail transmission.
`
`IPR2019-01191
`Ex. 3001 p. 2 of 2
`
`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