throbber

`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`_____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`_____________________
`
`GOPRO, INC.
`Petitioner
`
`v.
`
`CONTOUR IP HOLDING LLC,
`Patent Owner.
`
`_____________________
`
`Case No. IPR2015-01078
`
`United States Patent No. 8,896,694 B2
`_____________________
`
`
`Before JUSTIN T. ARBES, NEIL T. POWELL, and
`KIMBERLY McGRAW, Administrative Patent Judges.
`
`
`PETITIONER’S SUPPLEMENTAL PAPER ON RELEVANCE OF
`DISTRICT COURT CLAIM CONSTRUCTION DECISION
`
`

`

`IPR2015-01078
`
`
`During the February 4, 2019 teleconference with the Board, counsel for
`
`Patent Owner asserted that the district court’s claim construction order is relevant
`
`in this proceeding for a limited purpose. (Ex. 1040, 10:3-20). Patent Owner’s
`
`counsel asserted that GoPro argued to the Board that there is no word “parallel” in
`
`the challenged claims, but the district court construed certain claims to require this
`
`limitation. Id.
`
`
`
`Patent Owner seeks to manufacture inconsistency where there is none.
`
`GoPro has consistently argued that Boland teaches generation of high-resolution
`
`and low-resolution video data from the video image data in parallel. (Paper 1, 35-
`
`36 (explaining that Boland discloses “multiple, parallel video streams”); IPR2015-
`
`01080, Paper 38, 14 (explaining that Boland teaches generating “different
`
`qualities/resolutions from the video image data at the same time in parallel, not in
`
`serial as Patent Owner asserts”)). At oral argument in these proceedings, counsel
`
`for GoPro clarified that the claims do not require parallel processors, nor do the
`
`claims require parallel processing solely or directly from the image sensor as
`
`Patent Owner maintained. (Paper 53, 23:4-24:6, 26:23-27:25, 78:11-80:18).
`
`
`
`The district court’s construction of the “generate” and “generating” terms
`
`that appear in claims 1, 3, and 11 in the ’694 patent (Ex. 2016, 9:15-13:28) in no
`
`way undermines GoPro’s arguments in front of the Board or the disclosure of
`
`Boland. While the district court construed the claims to require generation of two
`
`1
`
`

`

`
`video streams in parallel, consistent with GoPro’s arguments to the Board, no
`
`
`
`IPR2015-01078
`
`requirement for the high resolution and low resolution video streams to be
`
`generated solely or directly from the image sensor using parallel processors was
`
`added. (Id., 9:23-11:21).
`
`Thus, even if the district court’s claim construction applied in this
`
`proceeding, Boland teaches the “generating” element, because it discloses high
`
`resolution and low resolution video data generated in parallel. (Paper 1, 35-36;
`
`IPR2015-01080, Paper 38, 14). Thus, the district court’s claim construction order
`
`is irrelevant to the obviousness issues before the Board on remand, and Patent
`
`Owner’s argument to the contrary should be rejected.
`
`Respectfully submitted,
`
`/s/ Adam R. Brausa
`Adam R. Brausa (Reg. No. 60,287)
`DURIE TANGRI LLP
`217 Leidesdorff Street
`San Francisco, CA 94111
`Tel: 415-376-6420
`Fax: 415-236-6300
`
`
`
`
`Dated: February 22, 2019
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2
`
`

`

`
`
`
`
`IPR2015-01078
`
`CERTIFICATE OF SERVICE
`I hereby certify that on February 22, 2019, a copy of PETITIONER’S
`
`SUPPLEMENTAL PAPER ON RELEVANCE OF DISTRICT COURT
`
`CLAIM CONSTRUCTION DECISION PURSUANT TO 37 C.F.R. §
`
`42.8(a)(3) was served by filing this document through the PTAB’s E2E Filing
`
`System as well as delivering a copy via electronic mail upon the following:
`
`For PATENT OWNER:
`
`Andrew R. Sommer
`John R. Keville
`WINSTON & STRAWN LLP
`asommer@winston.com
`jkeville@winston.com
`
`Nicole M. Jantzi
`Ian B. Brooks
`Paul M. Schoenhard
`McDERMOTT WILL & EMERY LLP
`njantzi@mwe.com
`ibrooks@mwe.com
`pschoenhard@mwe.com
`
`
`Dated: February 22, 2019
`
`
`By:
`
`
`
`
`3
`
`/s/ Adam R. Brausa
`Adam R. Brausa (Reg. No. 60,287)
`DURIE TANGRI LLP
`217 Leidesdorff Street
`San Francisco, CA 94111
`Tel: 415-376-6420
`Fax: 415-236-6300
`
`
`

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