throbber

`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`Google LLC,
`Petitioner,
`
`v.
`
`WAG Acquisition, L.L.C.,
`Patent Owner.
`
`
`
`IPR2022-01413
`
`U.S. Patent No. 9,762,636 B2
`
`
`
`
`PETITIONER’S RESPONSE TO PATENT OWNER’S BRIEF
`REGARDING RELEVANCE OF DECISION ON APPEAL IN EX PARTE
`WAG ACQUISITION, APPEAL 2023-003319 (WAG ʼ141 Patent)
`
`
`

`

`
`
`
`
`In its Brief in Support of Relevance of Decision on Appeal in Ex Parte WAG
`
`Acquisition, Appeal 2023-003319 (Paper No. 27 (“Brief”)), Patent Owner WAG
`
`Acquisition, LLC (“PO”) admits that the Decision on Appeal in Appeal 2023-
`
`003319 (Exhibit 2017 (“’319 Reexam Decision”)) is distinguishable because “it
`
`concerned different claim language.” (Brief at 1.) This is not the only reason that
`
`the ’319 Reexam Decision is not relevant or persuasive to the analysis here. As an
`
`initial matter, the ’319 Reexam Decision cannot be used against Google because
`
`Google was not a party to Appeal 2023-003319 and did not have an opportunity to
`
`present evidence or argument in that appeal or the underlying proceedings. Comair
`
`Rotron, Inc. v. Nippon Densan, Corp., 49 F.3d 1535, 1537 (Fed. Cir. 1995) (party
`
`asserting estoppel “must show that in the prior action the party against whom
`
`estoppel is sought had a full and fair opportunity to litigate the issue”).
`
`
`
`Most critically though, the Board’s ’319 Reexam Decision was narrowly
`
`focused on a specific argument that differs from the arguments regarding the Carmel
`
`prior art reference (Exhibit 1003) in this IPR. In particular, there the Board found
`
`that the quality level assessment “diamond boxes” in Figure 6B of Carmel do not
`
`meet the “providing a server programmed to receive requests from the user…”. (See
`
`’319 Reexam Decision at 6, 8-9; Exhibit 1117 at 25-27 (summarizing the panel’s
`
`understanding of the argument at issue).) The Board found that the examiner did not
`
`sufficiently “demonstrate[] that such changes in quality in Figure 6B” (the
`
`
`
`

`

`IPR2022-01413
`U.S. Patent No. 9,762,636 B2
`
`
`“diamond boxes”) “are correlated to symbols J, J+1, J+2, . . . N for bar 56,” as
`
`depicted in Figure 3C of Carmel and as required by claim 1 of the ʼ141 patent. (’319
`
`Reexam Decision at 8-9 (emphasis added).) The paragraph PO cites from the ’319
`
`Reexam Decision is thus in the context of analyzing only specific portions of those
`
`figures from Carmel. (Id. at 9.) The ’319 Reexam Decision does not include any
`
`analysis of any other figures, including Figures 6A and 3A, of Carmel. (See
`
`generally id.)
`
`Here, Google’s Petition (Paper No. 1 (“Petition”)) focuses on different figures
`
`and different aspects of those figures. In particular, Google has presented evidence
`
`explaining why the looping nature of Figure 6A of Carmel discloses claim limitation
`
`1[c] of the ʼ636 patent, reciting “receiving requests at the server system via one or
`
`more data connections over the Internet, for one or more of the media data elements
`
`stored in the data structure[.]” (See, e.g., Petition at 28-29 (“in both options, Carmel
`
`Figure 6A confirms this process is repeated for each slice”), 30-31, 40-43; Reply to
`
`Patent Owner’s Response (Paper No. 13 (“Reply”)) at 10-18.) Google has further
`
`explained how, contrary to PO’s assertions, Carmel discloses a client-controlled
`
`system where “[p]referably, each segment or slice is contained in a separate,
`
`respective file,” such as in Figure 3A, and slices are requested each loop in order to
`
`support requesting separate files on separate links as shown in Figure 6A. (Reply at
`

`
`
`
`-2-
`

`
`

`

`IPR2022-01413
`U.S. Patent No. 9,762,636 B2
`
`
`12-13 (quoting Carmel, 2:22-23); Petition at 12, 19-20.) Nothing in the ’319
`
`Reexam Decision contradicts or even relates to these issues.
`
`Google does not rely on the “diamond boxes” of Figures 6B (see Exhibit 1117
`
`at 25:11-24), nor has Google limited its arguments to Figures 3C and 6B, to disclose
`
`the limitations of the ʼ636 patent in this IPR. Instead, Google has presented different
`
`arguments and different evidence that were not at issue in the ’319 Reexam Decision.
`
`As such, the Board’s reasoning in the ’319 Reexam Decision—reviewing different
`
`figures and disclosures of Carmel against different claim language—is not relevant
`
`to the analysis here.
`
`For at least these reasons, the Board in this IPR should give the ’319 Reexam
`
`Decision little to no weight.
`
`
`
`Dated: December 21, 2023
`
`COOLEY LLP
`ATTN: Patent Group
`1299 Pennsylvania Avenue NW
`Suite 700
`Washington, DC 20004
`Tel: (202) 842-7885
`Fax: (202) 842-7899
`
`
`Respectfully submitted,
`
`
`By:
`/Eamonn Gardner/
`
` Eamonn Gardner
`
` (Reg. No. 63,322)
`
`

`
`-3-
`

`
`
`
`
`
`

`

`
`Pursuant to 37 C.F.R. §§42.6(e)(4)(i) et seq., a complete copy of the attached
`PETITIONER’S RESPONSE TO PATENT OWNER’S BRIEF REGARDING
`RELEVANCE OF DECISION ON APPEAL IN EX PARTE WAG
`ACQUISITION, APPEAL 2023-003319 (WAG ʼ141 Patent) is being served via
`email on the 21st day of December 2023, upon Patent Owner’s appointed attorneys
`of record:
`
`
`CERTIFICATE OF SERVICE
`
`Ronald Abramson
`ron.abramson@listonabramson.com
`M. Michael Lewis
`michael.lewis@listonabramson.com
`Ari J. Jaffess
`ari.jaffess@listonabramson.com
`Gina K. Kim
`gina.kim@listonabramson.com
`LISTON ABRAMSON LLP
`405 Lexington Ave, 46th Floor
`New York, NY 10174
`Telephone: (212) 257-1630
`Facsimile: (914) 462-4175
`
`
`
`
`
`
`
`
`
`Dated: December 21, 2023
`
`COOLEY LLP
`ATTN: Patent Docketing
`1299 Pennsylvania Avenue NW
`Suite 700
`Washington, D.C. 20004
`Tel: (202) 842-7885
`Fax: (202) 842-7899
`
`
`
`
`/Eamonn Gardner/
`Eamonn Gardner
`(Reg. No. 63,322)
`
`
`
`
`
`
`-4-
`
`
`
`

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