throbber
Case 3:11-cv-00719-RBD-TEM Document 347-3 Filed 09/16/13 Page 2 of 4 PageID 14169
`
`imj[imj]; rsulpizio[rsulpizio]; saltman[saltman]
`jjacobsUjacobs]
`Don Schrock
`Thur 2/4/1999 7:38:55 PM
`Fwd: QUALCOMM and ParkerVision
`
`To:
`Cc:
`From:
`Sent:
`Subject:
`
`<x-rich>
`
`<excerpt> FYI. this is critical technology that we must land based on
`what we have seen so far. It offers revolutionary rf versus power
`perfomnace based on early teat resuls. don
`
`</excerpt>
`
`<excerpt>r X-Sender: pkantak@monaco.qualcomm.com
`
`Date: Wed, 03 Feb 1999 17:49:53 -0800
`
`To: JPARKER@parkervision.com, DSORRELLS@parkervision.com
`
`From: Prashant Kantak <<pkantak>
`
`Subject: QUALCOMM and ParkerVision
`
`Cc: jjacobs, jlodenius, dschrock, sjha, syounis, sciccarelli, pak
`
`Mime-Version: 1.0
`
`Folks,
`
`Thanks for coming down to visit with us. I believe we had a successful
`day yesterday. I just wanted to reiterate broadly some of the steps we
`agreed to take in order to get the process moving forward rapidly.
`
`<bold>Action Items
`
`</bold>Here are some of the action items we agreed to pursue
`simultaneously:
`
`1) During the next couple of weeks, the QC engineering team will
`conduct preliminary tests on D2D to better understand its technical
`performance using the boards left behind by PV. These tests will give
`us a first pass idea of the strengths and weaknesses of the
`technology. So far, we have all seen many of the strengths of D2D.
`Getting a better understanding of the weaknesses will give QC a sense
`of how and to what extent we can compensate for them in our system
`architecture.
`
`CONFIDENTIAL
`
`QCPV005526982
`
`ParkerVision Ex. 2016
`Intel Corp. v. ParkerVision, Inc.
`IPR2020-01265
`
`

`

`Case 3:11-cv-00719-RBD-TEM Document 347-3 Filed 09/16/13 Page 3 of 4 PageID 14170
`
`2) The extended-NOA effort will move ahead full speed. Sterne,
`Kessler will send us a first draft of the NOA by the end of the week.
`We will do a 3+3 (6 people from QC) format so that we address PV's
`concerns for keeping the group as narrow as possible while, at the same
`time, allowing QC room to do due diligence on PV's technology
`disclosure.
`
`3) We will expand our discussions on the business (market)
`opportunities both in the telecom area (i.e. CDMA, GSM, etc.) and in
`other horizontal markets.
`
`4) The early indications are that PV is envisioning a licensing based
`business model with QC. However, the details will fall into place as
`we get a clearer understanding and agreements on point 3 above and also
`depending on the priorities and timeframes involved in achieving
`different product milestones.
`
`<bold>Goals
`
`</bold>Folks, I am excited about the set of common goals that flowed
`out of our discussions. Both parties are interested in
`
`<paraindent><param>left</param>
`
`Achieving rapid time-to-market and time-to-revenues
`
`Exploring products and applications across a breadth of the market so
`that our combined market and technical expertise will provide a
`sustainable competitive advantage in those markets
`
`Getting to technology disclosure rapidly so that QC can gain a better
`understanding of the technology for near-term use and help in advancing
`the technology longer term.
`
`Getting a level of commitment in terms of devoting resources, reaching
`a formal agreement and achieving the above goals in the shortest
`possible time.
`
`</para indent>
`
`Regards,
`
`Prashant
`
`</excerpt>
`
`Don Schrock
`
`Phone 619-658-5444
`
`Pager 1-800-707-3891
`
`CONFIDENTIAL
`
`QCPV005526983
`
`ParkerVision Ex. 2016
`Intel Corp. v. ParkerVision, Inc.
`IPR2020-01265
`
`

`

`Case 3:11-cv-00719-RBD-TEM Document 347-3 Filed 09/16/13 Page 4 of 4 PageID 14171
`
`Fax
`
`619-658-1587
`
`Email Address dschrock@qualcomm.com
`<Ix-rich>
`
`CONFIDENTIAL
`
`QCPV005526984
`
`ParkerVision Ex. 2016
`Intel Corp. v. ParkerVision, Inc.
`IPR2020-01265
`
`

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