throbber
Paper: _____
`
`Filed: December 3, 2015
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`__________________
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`__________________
`IBG LLC,
`INTERACTIVE BROKERS LLC,
`TRADESTATION GROUP, INC.,
`TRADESTATION SECURITIES, INC.,
`TRADESTATION TECHNOLOGIES, INC.,
`IBFX, INC.
`
`Petitioner
`v.
`
` TRADING TECHNOLOGIES INTERNATIONAL, INC.
`
`Patent Owner
`_________________
`Case CBM2015-00181
`U.S. Patent 7,676,411 B2
`_________________
`
`PATENT OWNER’S REPLY TO
`PETITIONER’S OPPOSITION TO MOTION FOR
` ADDITIONAL DISCOVERY
`
`
`
`
`
`
`
`
`
`
`
`

`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`
`
`
`
`
`
`I.
`
`CONTENTS
`
`PETITIONERS DO NOT DENY COOPERATING WITH CQG
`OR THAT CQG AIDED IN PREPARING THE ’411 PETITION .......... 1
`
`II. TT’S REQUESTS ARE NOT OVERBROAD ............................................ 3
`
`III. PETITIONERS DO NOT DISPUTE THAT THE REMAINING
`GARMIN FACTORS WEIGH IN FAVOR OF DISCOVERY ................. 4
`
`IV. PETITIONERS’ MISAPPREHEND REFLECTIX AND RPX ................. 5
`
`
`
`
`1
`
`

`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`PETITIONERS DO NOT DENY COOPERATING WITH CQG OR
`THAT CQG AIDED IN PREPARING THE ’411 PETITION
`
`I.
`
`Petitioners do not deny cooperation, aid, or labor division with CQG.
`
`Instead, Petitioners claim they “took pains to avoid creating a factual basis for the
`
`suggestion that CQG had any control over the content of the petition, or the
`
`decision to file it.” Paper 19 (“Opp.”) at 8. Using the same counsel and work
`
`product prepared with CQG is not taking “pains” to avoid control by CQG. See
`
`Mot. at 2. Counsel cannot forget what they did for CQG and many exhibits and
`
`sections are used in full from the earlier CBM2015-00179 proceeding jointly
`
`prepared by Petitioners and CQG. E.g., compare Ex. 1008 with CBM2015-00179,
`
`Ex. 1005 (reused new translation); compare Ex. 1032, ¶¶ 56-64, with CBM2015-
`
`00179, Ex. 1019, ¶¶ 58-66 (reused declaration section); compare Pet. § II.B.3 with
`
`CBM2015-00179, Paper 9, § III.C.3 (reused petition argument section).
`
`Rather than taking “pains” to work independently, Petitioners told the
`
`district court they were, in fact, working jointly (when working jointly favored a
`
`stay). Now they deny it and argue that their statements “do not indicate which
`
`defendants were planning to file on which of TT’s patents” (Opp. at 6), and that TT
`
`“failed to appreciate” that parties can file separate petitions (id. at 9). But the
`
`district court briefing contradicts those assertions. The briefing defined
`
`“Defendants” to include both Petitioners and CQG. Ex. 2002 at 2; Ex. 2003 at 2. It
`
`then reported “Defendants’ current efforts challenge the validity of the . . .
`
`
`
`1
`
`

`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`’411 [patent],” among others (Ex. 2003 at 9 (emphasis added)), and that “they
`
`[Defendants] ‘plan to . . . refil[e] challenges to most (if not all) of the patents-in-
`
`suit’” (id. at 8). For those challenges, Petitioners’ stated that CQG “is preparing to
`
`file CBMR petitions on the ’411 [patent].” Id. In context, these statements show
`
`that the CBM petitions, particularly the ’411 petition, were coordinated actions by
`
`the Defendants—not solitary actions. That the Defendants could separately prepare
`
`petitions fails to erase the admissions of joint preparation.
`
`Petitioners also argue that the evidence shows only that CQG prepared “a”
`
`’411 petition, not “the” ’411 petition. See Opp. at 5-10. But Petitioners fail to
`
`explain why Defendants’ promise to file a ’411 petition “in the next several weeks”
`
`(id. at 8) does not implicate “the” ’411 petition—the only ’411 petition filed in that
`
`window. Thus, objective review of the facts warrants additional discovery on
`
`CQG’s involvement in “the” ’411 petition. Moreover, possible differences between
`
`CQG’s “a” petition and “the” petition ultimately filed fail to render Petitioners’
`
`coordination with CQG on the ’411 patent irrelevant. Ex. 2003 at 8-9. That
`
`coordination directly relates to RPI status, even if CQG later relinquished control.
`
`To be clear, TT is not arguing that participation in a litigation joint defense group
`
`creates an RPI. This is not the issue here. The cases Petitioners cite relate to joint
`
`defense groups for district court—not groups coordinating on CBM petitions. Opp.
`
`at 6-7. Coordinated preparation of a petition is exactly the cooperation that
`
`
`
`2
`
`

`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`warrants additional discovery, as shown by RPX and Reflectix. And TT’s request—
`
`limited to communications and agreements between CQG and Petitioners related to
`
`a ’411 post-grant proceeding—seeks only pertinent evidence on that coordination.
`
`This narrower request, despite Petitioners’ assertions (Opp. at 4), remedies
`
`the reasons the Board denied TT’s request in CBM2015-00161, because it is to the
`
`’411 patent and specific types of documents (see Mot. at 11-12 (expressly
`
`addressing that denial)). And the Board already recognized it is not the same
`
`request. Ex. 2001 at 6:19-7:1. Accordingly, Petitioners unsupported
`
`characterization of the requests as being the same without explanation lacks merit.
`
`The pending motion is not on CQG’s RPI status. Instead, the question before
`
`the Board is whether Petitioners (1) admitted coordination with CQG and
`
`(2) statements on CQG’s preparation of a petition for “Defendants” to challenge
`
`the ’411 patent show more than a possibility or mere allegation that evidence on
`
`Petitioners’ coordination with CQG exists. They do. Indeed, Petitioners do not
`
`deny that correspondence between Petitioners and CQG on filing a ’411 petition
`
`exist to certify their statements in Exs. 2002 and 2003 or that they coordinated and
`
`shared labor on filing a ’411 petition. See generally Opp.; see also Mot. at 5-6.
`
`II. TT’S REQUESTS ARE NOT OVERBROAD
`Petitioners argue TT’s request improperly seeks information on
`
`“anticipated” filings against the ’411 patent. Opp. at 10-11. While Petitioners
`
`
`
`3
`
`

`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`contend CQG’s efforts were unrelated to this proceeding, the sharing of its work
`
`with Petitioners and other coordination (e.g., agreements on who would file when)
`
`with respect to the ’411 patent is highly relevant to CQG’s RPI status. And
`
`communications on “anticipated” proceedings appropriately encompass
`
`communications before the filing of this proceeding. Moreover, TT specifically
`
`limited its request to communications and agreements between CQG and the
`
`Petitioners to eliminate any concern that the request would include any truly
`
`independent work by CQG. If the Board thinks the request needs further narrowing
`
`but discovery is warranted, the Board can instruct the parties to meet and confer on
`
`scope or explicitly carve privileged work product out of any ordered discovery.
`
`III. PETITIONERS DO NOT DISPUTE THAT THE REMAINING
`GARMIN FACTORS WEIGH IN FAVOR OF DISCOVERY
`Petitioners do not challenge the Board’s previous findings that the third and
`
`fourth Garmin factors weigh in favor of granting additional discovery. See
`
`generally Opp.; see also Tradestation v. Trading Techs., CBM2015-00161, Paper
`
`20, at 9-10 (PTAB 2015). Regarding factor two, except for a cursory statement,
`
`Petitioners did not explain why TT’s request seeks litigation positions. Opp. at 4.
`
`TT narrowly tailored its request to “communications (including emails) and
`
`agreements [between Petitioners and CQG] . . . related to the filing, preparation, or
`
`funding” of post-grant petitions against the ’411 patent to avoided seeking
`
`privileged material or positions prepared for the litigation. Mot. at 1.
`
`
`
`4
`
`

`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`IV. PETITIONERS’ MISAPPREHEND REFLECTIX AND RPX
`Petitioners read RPX and Reflectix too narrowly. See Opp. at 11-13. TT’s
`
`Motion relies on joint statements by Petitioners and CQG that CQG was preparing
`
`a petition on the ’411 patent for “Defendants” as part of a coordinated strategy.
`
`RPX provided discovery when one party prepared a petition for others, as occurred
`
`here. RPX, IPR2014-00171, Paper 57 (PTAB 2014). RPX did not, as Petitioners
`
`suggest, add a requirement of metadata and statements about funding to warrant
`
`discovery. Opp. at 11-12. “Defendants” promised to file a petition prepared by
`
`CQG on the ’411 patent “in the next several weeks” (Ex. 2003 at 8, 9), and only
`
`one petition was filed against the ’411 patent in that window. Petitioners cannot
`
`avoid discovery because the form of its admission differs from the form in RPX.
`
`Reflectix recognizes that relinquishing control does not absolve a party who
`
`drafted a petition in a coordinated effort, such as CQG, from RPI status. Reflectix,
`
`IPR2015-00039, Paper 18, at 10-11 (PTAB 2015). Reflectix found an unnamed
`
`party to be an RPI when that party acknowledged preparing the petition, similar to
`
`the facts here, where Petitioners admitted CQG was preparing the petition for
`
`“Defendants.” Accordingly, Reflectix also supports granting additional discovery.
`
`Dated: December 3, 2015
`
`Respectfully submitted,
`
`By: /Kevin D. Rodkey
` Kevin D. Rodkey, Reg. No. 65,506
`
`
`
`
`
`5
`
`

`
`CERTIFICATE OF SERVICE
`
`Case CBM2015-00181
`U.S. Patent 7,676,411
`
`The undersigned hereby certifies that a copy of the foregoing Patent
`
`Owner’s Reply to Petitioner’s Opposition to Motion for Additional Discovery
`
`was served on December 3, 2015, via email directed to counsel of record for the
`
`Petitioners at the following:
`
`
`Robert E. Sokohl
`rsokohl-PTAB@skgf.com
`
`Lori Gordon
`lgordon-ptab@skgf.com
`
`Richard M. Bemben
`rbemben-PTAB@skgf.com
`
`PTAB@skgf.com
`
`
`
`/Lisa C. Hines/
`Lisa C. Hines
`Litigation Clerk
`
`Finnegan, Henderson, Farabow, Garrett &
`Dunner, LLP
`
`
`
`6
`
`Dated: December 3, 2015

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