throbber
Filed: May 16, 2018
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`ARRIS INTERNATIONAL PLC
`Petitioner
`v.
`CHANBOND, LLC
`Patent Owner
`_____________________
`Case IPR2018-00575
`Patent 8,984,565
`
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`TO PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 8,984,565
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`

`

`TABLE OF CONTENTS
`
`I.
`
`Introduction ...................................................................................................... 1
`
`II.
`
`Overview of U.S. Patent No. 8,984,565 .......................................................... 3
`
`III.
`
`Prior Proceedings ............................................................................................. 7
`
`IV. Argument .......................................................................................................12
`
`A.
`
`B.
`
`The Petition Is Time Barred Under 35 U.S.C. § 315(b) .....................12
`
`The Board Should Deny Institution Under 35 U.S.C. § 314(a) ..........33
`
`V.
`
`Conclusion .....................................................................................................47
`
`
`
`
`
`
`
`
`i
`
`PUBLIC VERSION
`
`

`

`TABLE OF AUTHORITIES
`
`Cases
`Abiomed, Inc. v. Maquet Cardiovascular, LLC,
`Case IPR2017-02150 (PTAB March 12, 2018) .................................................. 43
`
`Page(s)
`
`Alcatel-Lucent USA Inc. v. Oyster Optics, LLC,
`Case IPR2017-02146 (PTAB Feb. 28, 2018) ..................................................... 37
`
`Alere Inc. v. Rembrandt Diagnostics, LP,
`Case IPR2017-01130 (PTAB Sept. 28, 2017) ................................................... 39
`
`Apple Inc. v. Achates Reference Publishing, Inc.,
`Case IPR2013-00080 (PTAB June 2, 2014) ....................................................... 32
`
`ARRIS Group, Inc. v. C-Cation Techs., LLC,
`Case IPR2014-00746 (PTAB Nov. 24, 2014) .............................................. 32, 33
`
`Aruze Gaming Macau, Ltd. v. MGT Gaming, Inc.,
`Case IPR2014-01288 (PTAB Feb. 20, 2015) ..................................................... 16
`
`Bros, Inc. v. W. E. Grace Mfg. Co.,
`261 F.2d 428 (5th Cir. 1958) ........................................................................ 25, 26
`
`Cal. Physicians’ Serv. v. Aoki Diabetes Research Inst.,
`163 Cal. App. 4th 1506 (2008) ........................................................................... 14
`
`In re ChanBond, LLC Patent Litigation,
`No. 1:15-cv-00842-RGA (D. Del. Apr. 24, 2018) ...................................... 11, 45
`
`Cisco Systems, Inc., v. ChanBond LLC,
`Case IPR2016-01890 (PTAB Mar. 29, 2017) .............................................. 34, 41
`
`Cisco Systems, Inc., v. ChanBond LLC,
`Case IPR2016-01891 (PTAB Mar. 29, 2017) .................................................... 34
`
`Cisco Systems, Inc. v. Hewlett Packard Enterprise Co.,
`Case IPR2017-01933 (PTAB Mar. 16, 2018) .................................................... 30
`
`ESET, LLC v. Finjan, Inc.,
`Case IPR2017-01969 (PTAB Feb. 15, 2018) ......................................... 35, 36, 40
`
`
`
`ii
`
`PUBLIC VERSION
`
`

`

`FedEx Corp. v. Intellectual Ventures II LLC,
`Case IPR2017-02028 (PTAB Feb. 21, 2018) .................................................... 43
`
`FutureVision.com, LLC v. Cequel Commc’ns, LLC,
`No. CV 13-855-GMS-MPT, 2016 WL 373790 (D. Del. Feb. 1, 2016) ....... 10, 11
`
`General Electric Co. v. TransData, Inc.,
`Case IPR2014-01380 (PTAB Apr. 15, 2015) ......................................... 29, 30, 31
`
`General Plastic Indus. Co., Ltd. v. Canon Kabushiki Kaisha,
`Case IPR2016-01357 (PTAB Sept. 6, 2017) ...............................................passim
`
`Gonzalez v. Banco Cent. Corp.,
`27 F.3d 751 (1st Cir. 1994) ..................................................................... 16, 17, 25
`
`Halyard Health, Inc. v. Kirn Med. Design, LLC,
`Case IPR2017-01990 (PTAB Mar. 8, 2018) ...................................................... 43
`
`Intel Corp. v. Alacritech, Inc.,
`Case IPR2017-01392 (PTAB Nov. 30, 2017) .................................................... 32
`
`Intel Corp. v. U.S. Int’l Trade Comm’n,
`946 F.2d 821 (Fed. Cir. 1991) ............................................................................ 27
`
`Mitsuba Corp. v. Intellectual Ventures II LLC,
`Case IPR2018-00071 (PTAB Apr. 23, 2018) ..................................................... 37
`
`Montana v. United States,
`440 U.S. 147 (1979) ...................................................................................... 17, 25
`
`NetApp Inc. v. Realtime Data LLC,
`Case IPR2017-01195 (PTAB Oct. 12, 2017) ............................................... 39, 45
`
`NetApp Inc. v. Realtime Data LLC,
`Case IPR2017-01660 (PTAB Jan. 25, 2018) ...................................................... 35
`
`One World Techs., Inc. v. The Chamberlain Group, Inc.,
`Case IPR2017-01546 (PTAB Dec. 13, 2017) ............................................... 34, 43
`
`RPX Corp. v. ChanBond LLC,
`Case IPR2016-00234 (PTAB May 25, 2017) ....................................................... 9
`
`
`
`iii
`
`PUBLIC VERSION
`
`

`

`RPX Corp. v. ChanBond LLC,
`No. 2017-2346 (Fed. Cir. Jan. 17, 2018) .............................................................. 9
`
`RPX Corp. v. Virnetx Inc.,
`Case IPR2014-00171 (PTAB June 5, 2014) ....................................................... 29
`
`Samsung Electronics Co., Ltd. v. Elm 3DS Innovations, LLC,
`Case IPR2017-01305 (PTAB Oct. 17, 2017) ............................................... 35, 40
`
`Sorenson v. Sec’y of Treasury of U.S.,
`475 U.S. 851 (1986) ............................................................................................ 15
`
`Taylor v. Sturgell,
`553 U.S. 880 (2008) .......................................................................... 14, 26, 27, 28
`
`Tidewater Patent Dev. Co. v. Kitchen,
`421 F.2d 680 (4th Cir. 1970) .............................................................................. 26
`
`Ventex Co., Ltd. v. Columbia Sportswear North America, Inc.,
`Case IPR2017-00651 (PTAB July 26, 2017) ..................................................... 32
`
`Vulcan, Inc. v. Fordees Corp.,
`658 F.2d 1106 (6th Cir. 1981) ............................................................................ 27
`
`WesternGeco LLC v. ION Geophysical Corp.,
`No. 2016-2099, 2018 WL 2090314 (Fed. Cir. May 7, 2018) ....................... 14, 26
`
`Wi-Fi One, LLC v. Broadcom Corp.,
`887 F.3d 1329 (Fed. Cir. 2018) .............................................................. 13, 26, 27
`
`Statutes
`
`35 U.S.C. 314(a) ...................................................................................................... 46
`
`35 U.S.C. § 314 .......................................................................................................... 1
`
`35 U.S.C. § 314(a) ............................................................................................passim
`
`35 U.S.C. § 315(b) ............................................................................................passim
`
`35 U.S.C. § 316(a)(11) ............................................................................................. 46
`
`35 U.S.C. § 325(d) ................................................................................................... 40
`
`
`
`iv
`
`PUBLIC VERSION
`
`

`

`Other Authorities
`
`37 C.F.R. § 42.107(a) ................................................................................................. 1
`
`37 C.F.R. § 42.108(a) ............................................................................................... 46
`
`18A Charles Alan Wright, Arthur R. Miller & Edward H. Cooper, Federal Practice
`& Procedure § 4451 (2d ed.) ................................................................... 16, 25, 33
`
`157 Cong. Rec. S5432 (daily ed. Sept. 8, 2011) ...................................................... 15
`
`Trial Practice Guide, 77 Fed. Reg. 48,756, 48,759 (Aug. 14, 2012) ................. 13, 16
`
`
`
`
`
`
`
`v
`
`PUBLIC VERSION
`
`

`

`EXHIBIT LIST
`
`Exhibit No.
`
`Description
`
`2001
`
`2002
`
`2003
`
`2004
`
`2005
`
`2006
`
`2007
`
`2008
`
`2009
`
`2010
`
`2011
`
`2012
`
`2013
`
`
`
`Cisco Systems, Inc. Form 10-K (Sept. 7, 2017)
`
`ARRIS International plc Form 10-K (Feb. 29, 2016)
`
`ARRIS International plc Form 10-K (March 1, 2017)
`
`ARRIS International plc Form 10-K (March 1, 2018)
`
`Stipulation and [Proposed] Order to Amend Scheduling Order, In
`re ChanBond, LLC Patent Litigation, No. 1:15-cv-00842-RGA
`(D. Del. Apr. 24, 2018) (so ordered Apr. 24, 2018)
`
`Summons and Proof of Service on Delaware Defendants (Oct. 1,
`2015)
`
`ARRIS Corporate Terms and Conditions of Sale, https://
`www.arris.com/globalassets/resources/company-overview/tc.pdf
`
`
`
`
`
`
`
`vi
`
`
`
`
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Atlantic Broadband Answer to the Complaint (Nov. 23, 2015);
`
`Mediacom Answer to the Complaint (Nov. 23, 2015)
`
`Wave Answer to the Complaint (Nov. 23, 2015)
`
`vii
`
`2014
`
`2015
`
`2016
`
`2017
`
`2018
`
`2019
`
`2020
`
`2021
`
`2022
`
`2023
`
`2024
`
`2025
`
`2026
`
`
`
`PUBLIC VERSION
`
`

`

`2027
`
`2028
`
`2029
`
`2030
`
`2031
`
`2032
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`WOW Answer to the Complaint (Nov. 23, 2015)
`
`ARRIS’s Objections and Responses to ChanBond’s Subpoena for
`Documents (Jan. 16, 2017)
`
`ARRIS Group, Inc.’s Objections and Responses to ChanBond’s
`Subpoena to Testify at a Deposition (Jan. 22, 2018)
`
`Petitioner’s Responses to Patent Owner’s Requests for Additional
`Discovery (Apr. 13, 2018)
`
`ARRIS Press Release, “ARRIS Acquires Motorola Home: Creates
`Premier Video Delivery and Broadband Technology Company”
`(Apr. 17, 2013)
`
`New York Times, “Motorola Completes General Instrument
`Acquisition” (Jan. 6, 2000)
`
`
`
`
`
`
`
`
`
`
`
`
`
`viii
`
`PUBLIC VERSION
`
`

`

`I.
`
`INTRODUCTION
`
`Pursuant to 37 C.F.R. § 42.107(a), Patent Owner, ChanBond, LLC, submits
`
`the following preliminary response to the Petition, setting forth reasons why no
`
`inter partes review should be instituted under 35 U.S.C. § 314.
`
`This proceeding is the latest in a seemingly endless string of challenges to
`
`the validity of this patent family. Not even two months after Patent Owner
`
`initiated infringement litigation in Delaware District Court in 2015, RPX
`
`Corporation (“RPX”) filed a first, and ultimately unsuccessful, inter partes review
`
`petition against one of the asserted patents. This was followed less than a year
`
`later by a second salvo of eight inter partes review petitions filed by Cisco
`
`Systems, Inc. (“Cisco”) against each of the three patents asserted in the Delaware
`
`litigation. The Board, however, denied institution on seven of those eight
`
`petitions. This latest round of five petitions, again challenging all three asserted
`
`patents, was filed by Petitioner ARRIS International plc (“ARRIS”) just before
`
`issuance of a final written decision on the one Cisco petition that was instituted by
`
`the Board.
`
`These are not separate challenges by actors with independent interests.
`
`Cisco and ARRIS are suppliers of telecommunications equipment to the
`
`defendants in the Delaware litigation (“the Delaware Defendants”). Both Cisco
`
`and ARRIS are member companies of RPX. Cisco listed all of the Delaware
`
`
`
`1
`
`PUBLIC VERSION
`
`

`

`Defendants, as well as ARRIS, as real parties in interest in each of its IPR
`
`petitions. And as Petitioner ARRIS admitted in its filings to the U.S. Securities
`
`and Exchange Commission (“SEC”) and other public documents, it has a duty to
`
`indemnify the Delaware Defendants in case of a loss, and under the same
`
`indemnification agreements it also has a legal right to control the litigation.
`
`Under these facts, the Board should deny institution of trial for two separate
`
`reasons. First, Petitioner is in privity with the Delaware Defendants, who were
`
`served with a complaint for infringement of the challenged patent in 2015.
`
`Therefore, the petition is time-barred under 35 U.S.C. § 315(b). Second, the Board
`
`should exercise its discretion to deny institution under 35 U.S.C. § 314(a) because
`
`“multiple, staggered petition filings, such as those here, are an inefficient use of the
`
`inter partes review process and the Board’s resources.” General Plastic Indus.
`
`Co., Ltd. v. Canon Kabushiki Kaisha, Case IPR2016-01357, slip op. at 21 (PTAB
`
`Sept. 6, 2017) (paper 19) (precedential). Petitioner and its allies should not be
`
`allowed to “strategically stage their prior art and arguments in multiple petitions,
`
`using [the Board’s] decisions as a roadmap, until a ground is found that results in
`
`the grant of review.” Id. at 17.
`
`
`
`2
`
`PUBLIC VERSION
`
`

`

`II. OVERVIEW OF U.S. PATENT NO. 8,984,5651
`
`U.S. Patent No. 8,984,565 (“the ’565 Patent,” Ex. 1001) is “directed … to an
`
`intelligent device system and method for distribution of digital signals onto, and
`
`off of, a wideband signal distribution system.” Ex. 1001, ’565 Patent at 1:25–29.
`
`One of the problems the ’565 Patent inventors intended to solve was the inability
`
`to “download to individual users large quantities of digitized images (video, film,
`
`… etc.), and to … allow those digital images to be displayed with the enhanced
`
`quality such digital images can offer.” Id. at 1:59–63. The transfer of such
`
`information typically “clog[ged] data networks” or “severely degraded” the
`
`network’s performance. Id. at 1:36–37, 1:67–2:1. The inventors recognized that it
`
`was “desirable to transport the digitized data on an analog carrier … in a format
`
`that would allow for greater amounts of data to be carried at one time, such as by
`
`modulated RF.” Id. at 2:13–16. The ’565 invention “offers the advantage that a
`
`high amount of throughput can be achieved in the transmission of digital and/or
`
`analog information on an RF … carrier.” Id. at 6:45–49.
`
`The
`
`inventors recognized
`
`that digital
`
`transmission systems “often
`
`employ[ed] analog waveforms, such as RF carrier waveforms, as a physical-layer
`
`transport mechanism ….” Id. at 5:8–10. Fig. 5 of the ’565 Patent (reproduced
`
`1 Patent Owner provides an identical overview of the ’565 Patent in its preliminary
`
`responses to IPR2018-00574 and IPR2018-00575, filed concurrently.
`
`
`
`3
`
`PUBLIC VERSION
`
`

`

`below with annotations in color) depicts “an intelligent device system for use in
`
`local sending of digital information and receiving of digital … information using
`
`RF modulation[.]” Id. at 4:48–51.
`
`Wideband
`Signal
`Distribution
`System
`
`
`
`The exemplary system of Fig. 5 is capable of both sending RF signals to,
`
`and receiving RF signals from, a wideband signal distribution system via
`
`broadband uniform distribution (BUD) unit 38. Id. at 7:10–11, 10:23–27, 10:52–
`
`60. The transmission and reception paths are annotated in blue and red,
`
`respectively. When sending data to the wideband signal distribution system (blue
`
`path in the annotated Fig. 5), the exemplary system of Fig. 5 receives digital
`
`information from a number of addressable devices 202 and modulates it onto an
`
`RF signal. “The system of FIG. 5 preferably includes a plurality of addressable
`
`devices 202, such as Ethernet or NIC cards, or digital display devices ….” Id. at
`
`
`
`4
`
`PUBLIC VERSION
`
`

`

`10:28–30. “The signals incoming from each of the addressable devices 202 are
`
`combined by a digital combiner 410, and passed through a traffic sensor 412, at
`
`least one modulator 414, and an RF converter section 418.” Id. at 10:42–45. “The
`
`output of the RF converter section 418 is preferably impedance matched to a BUD
`
`[broadband uniform distribution unit] 38, and feeds the signal exiting the RF
`
`converter section 418 to the BUD input port or ports.” Id. at 10:52–54.
`
`The intelligent device system of Fig. 5 is capable of dynamically allocating
`
`multiple, separate RF channels for transmission based on the information
`
`throughput of the digital information. “[T]he signal entering the modulator bank
`
`414 is preferably measured via a traffic sensor 412 to determine if the information
`
`volume is greater than the normal capacity of, for example, a single modulator. If
`
`the volume is greater, the DSP 420 will, in turn, direct the incoming data to as
`
`many modulators as necessary to modulate all data from the combiner 410.” Id. at
`
`9:46–52. “The digital signal processor (DSP) 420 … determines the number of
`
`modulators, or the channel width or widths, needed to modulate the signal
`
`incoming to the traffic sensor 412, as well as the number of RF channels, and
`
`which RF channels, on which the output of the modulator or modulators is
`
`modulated. Note that, for example, where QAM modulation is used, QAM
`
`modulation is generally 40 megabits per second, per 6 MHz RF channel, thus
`
`requiring the use of two 6 MHz RF channels in order to modulate … 80 megabits
`
`
`
`5
`
`PUBLIC VERSION
`
`

`

`per second coming from the digital combiner …. The RF channel frequency is
`
`selected from at least two available frequency channels.” Id. at 9:65–10:10. “[A]n
`
`RF system channel detector [239] is preferably in communication with the DSP
`
`420 in order to update the DSP 420 as to the RF channels in use and available.” Id.
`
`at 10:49–51.
`
`When receiving data from the wideband signal distribution system (red path
`
`in the annotated Fig. 5), the exemplary system of Fig. 5 recombines the
`
`information carried by the separate RF channels into a digital stream for reception
`
`by the addressable devices. “The signal entering the intelligent device is
`
`preferably split by at least one RF splitter 214, and is then differentiated according
`
`to the information frequency on the incoming carrier.” Id. at 8:46–49. “The IP
`
`portion of the modulated RF signal fed through a second bandpass filter 218 …
`
`and the IP portion is then demodulated by at least one demodulator 220. The
`
`demodulator 220 strips the RF carrier signal from the digital baseband signal ….
`
`Following demodulation, the digital signals may be combined by a digital
`
`combiner 212, such as a multiplexer, in order to effectuate a parallel to serial
`
`conversion. The output of the digital combiner 212 is a high speed serial digital
`
`output, on the order of, for example, up to, or in excess of, several Gbit/sec. The
`
`output of the digital combiner 212 is then preferably routed to a splitter, which
`
`
`
`6
`
`PUBLIC VERSION
`
`

`

`splitter feeds an outgoing signal to the input pin pairs … of at least one addressable
`
`device 202.” Id. at 11:15–29.
`
`III. PRIOR PROCEEDINGS2
`
`This is the third wave of challenges against the patents in this family. Over
`
`the last two and a half years, three petitioners, and numerous other real parties in
`
`interest and privies, have filed 14 separate petitions for inter partes review of the
`
`same three related patents. Of the nine petitions filed by RPX and Cisco, eight
`
`were unsuccessful. As discussed in Sections IV.A and IV.B below, the Board
`
`should deny institution on this latest salvo of five petitions because they are
`
`inextricably linked to those prior proceedings.
`
`On September 21, 2015, Patent Owner filed patent infringement actions in
`
`the U.S. District Court
`
`for
`
`the District of Delaware against several
`
`telecommunications companies (“the Delaware Defendants”).3 In its complaints,
`
`
`2 Patent Owner provides a substantially identical summary of prior proceedings in
`
`its preliminary
`
`responses
`
`to
`
`IPR2018-00574 and
`
`IPR2018-00575,
`
`filed
`
`concurrently.
`
`3 The Delaware Defendants are Atlantic Broadband Group, LLC (“Atlantic
`
`Broadband”) (No. 1:15-cv-00842); Bright House Networks, LLC (“Bright House”)
`
`(No. 1:15-cv-00843); Cable One Inc. (“Cable One”) (No. 1:15-cv-00844);
`
`
`
`7
`
`PUBLIC VERSION
`
`

`

`ChanBond alleged infringement of three related patents, namely, U.S. Patent Nos.
`
`7,941,822 (“the ’822 Patent”), 8,341,679 (“the ’679 Patent”), and 8,984,565 (“the
`
`’565 Patent”), by the Delaware Defendants’ cable systems and services. The ’565
`
`Patent is at issue in this proceeding.
`
`On November 20, 2015, about two months after ChanBond filed its
`
`infringement complaints, RPX, a so-called “patent risk management” company,4
`
`filed the first petition for inter partes review of the ’822 Patent. RPX Corp. v.
`
`ChanBond LLC, Case IPR2016-00234 (“the RPX IPR”). RPX purported to be
`
`Cablevision Systems Corporation and CSC Holdings, LLC (“Cablevision”) (No.
`
`1:15-cv-00845); Cequel Communications, LLC and Cequel Communications
`
`Holdings I, LLC d/b/a Suddenlink Communications (“Cequel/Suddenlink”) (No.
`
`1:15-cv-00846); Charter Communications, Inc. (“Charter”) (No. 1:15-cv-00847);
`
`Comcast Corporation and Comcast Cable Communications, LLC (“Comcast”)
`
`(No. 1:15-cv-00848); Cox Communications, Inc. (“Cox”) (No. 1:15-cv-00849);
`
`Mediacom Communications Corporation (“Mediacom”) (No. 1:15-cv-00850);
`
`RCN Telecom Services, LLC (“RCN”) (No. 1:15-cv-00851); Time Warner Cable,
`
`Inc. and Time Warner Cable Enterprises LLC (“TWC”) (No. 1:15-cv-00852);
`
`WaveDivision Holdings, LLC (“Wave”) (No. 1:15-cv-00853); and WideOpen
`
`West Finance, LLC (“WOW”) (No. 1:15-cv-00854).
`
`4 See http://ir.rpxcorp.com/investor-relations.
`
`
`
`8
`
`PUBLIC VERSION
`
`

`

`acting independently of the Delaware Defendants as it only listed itself as real
`
`party in interest, and stated: “RPX has complete, unilateral control of all aspects of
`
`this proceeding and is also solely responsible for all costs and expenses associated
`
`with this proceeding.” Petition at 2, RPX Corp. v. ChanBond LLC, Case IPR2016-
`
`00234 (Nov. 20, 2015). After oral hearing, the Board issued a final written
`
`decision in Patent Owner’s favor, determining that RPX had not shown by a
`
`preponderance of the evidence that any of the claims at issue were unpatentable.
`
`RPX Corp. v. ChanBond LLC, Case IPR2016-00234, slip op. at 2 (PTAB May 25,
`
`2017) (paper 28). RPX attempted to appeal the Board’s decision, but the U.S.
`
`Court of Appeals for the Federal Circuit dismissed the appeal for lack of standing.
`
`RPX Corp. v. ChanBond LLC, No. 2017-2346 (Fed. Cir. Jan. 17, 2018).
`
`Between September 6 and September 28, 2016, while the RPX IPR was
`
`pending, Cisco filed eight more petitions for inter partes review of the ’822, ’679
`
`and ’565 Patents. Cisco Systems, Inc., v. ChanBond LLC, Cases IPR2016-01744
`
`and IPR2016-01746 (filed Sept. 6, 2016), IPR2016-01889, IPR2016-01890 and
`
`IPR2016-01891 (filed Sept. 26, 2016), IPR2016-01898, IPR2016-01899 and
`
`IPR2016-01900 (filed Sept. 28, 2016) (collectively, “the Cisco IPRs”). Cisco is a
`
`maker of telecommunications equipment, including cable modem termination
`
`systems (CMTSs) used by telecommunications companies such as the Delaware
`
`Defendants. Ex. 2001, Cisco Form 10-K at 6 (Sept. 7, 2017). Unlike RPX, Cisco
`
`
`
`9
`
`PUBLIC VERSION
`
`

`

`listed all of the Delaware Defendants as real parties in interest in each of its IPR
`
`petitions. See, e.g., Petition at 2, Cisco Systems, Inc., v. ChanBond LLC, Case
`
`IPR2016-01744 (Sept. 6, 2016). In addition, Cisco, “out of an abundance of
`
`caution based on certain decisions from the PTAB describing the test for real
`
`parties-in-interest,” identified ARRIS Group, Inc., the predecessor-in-interest to
`
`the Petitioner in this proceeding,5 as a real party in interest in each of its IPR
`
`petitions. Id.
`
`Cisco’s challenge was marginally more successful than RPX’s, because the
`
`Board denied institution on seven out of eight petitions filed by Cisco. Having
`
`instituted trial on the sole surviving petition, the Board issued a final written
`
`decision determining that certain claims of the ’822 Patent were unpatentable.
`
`Cisco Systems, Inc., v. ChanBond LLC, Case IPR2016-01744 (PTAB Feb. 23,
`
`2018) (paper 28). That decision is currently on appeal to the U.S. Court of
`
`Appeals for the Federal Circuit. ChanBond, LLC v. Cisco Systems, Inc., No. 18-
`
`1886 (filed Apr. 25, 2018).
`
`This third wave of challenges involves five inter partes review petitions, this
`
`time filed by Petitioner ARRIS and, once again, targeting the ’822, ’679 and ’565
`
`Patents. ARRIS International plc v. ChanBond, LLC, Cases IPR2018-00570,
`
`IPR2018-00572, IPR2018-00573, IPR2018-00574, and IPR2018-00575. ARRIS
`
`5 See Ex. 2002, ARRIS Form 10-K at 2 (Feb. 29, 2016).
`
`
`
`10
`
`PUBLIC VERSION
`
`

`

`filed its five petitions on February 2, 2018, just three weeks prior to issuance of the
`
`final written decision in the Cisco IPRs. Like Cisco, ARRIS is a maker of
`
`telecommunications equipment used by the Delaware Defendants. As ARRIS
`
`stated in its filings to the SEC, if ChanBond prevails in the district court litigation
`
`“ARRIS may be required to indemnify the [Delaware Defendants] and/or pay
`
`damages for utilizing certain technology.” Ex. 2002, ARRIS Form 10-K at 31
`
`(Feb. 29, 2016).
`
`As a result of these endless, staggered challenges by the Delaware
`
`Defendants, their suppliers Cisco and ARRIS, and alleged third party RPX,6 there
`
`has not been a single day since November 2015 when Patent Owner has not had to
`
`litigate at least one, if not multiple PTAB proceedings in parallel with the
`
`infringement litigation against the Delaware Defendants. Fact discovery in the
`
`Delaware litigation will close on June 1, 2018, and the case is expected to go to
`
`trial by early 2019. Ex. 2005, Stipulation and [Proposed] Order to Amend
`
`Scheduling Order, In re ChanBond, LLC Patent Litigation, No. 1:15-cv-00842-
`
`RGA (D. Del. Apr. 24, 2018) (so ordered Apr. 24, 2018).
`
`
`6 It is public knowledge that both Petitioner ARRIS and prior Petitioner Cisco are
`
`member companies of RPX. See FutureVision.com, LLC v. Cequel Commc’ns,
`
`LLC, No. CV 13-855-GMS-MPT, 2016 WL 373790, at *2 (D. Del. Feb. 1, 2016).
`
`
`
`11
`
`PUBLIC VERSION
`
`

`

`IV. ARGUMENT7
`
`As explained below, the Board may not institute an inter partes review
`
`because Petitioner is time barred under 35 U.S.C. § 315(b). In the alternative, the
`
`Board should exercise its discretion to deny institution under 35 U.S.C. § 314(a).
`
`A. The Petition Is Time Barred Under 35 U.S.C. § 315(b)
`
`Under 35 U.S.C. § 315(b), “[a]n inter partes review may not be instituted if
`
`the petition requesting the proceeding is filed more than 1 year after the date on
`
`which the petitioner, real party in interest, or privy of the petitioner is served with a
`
`complaint alleging infringement of the patent.” Patent Owner served the Delaware
`
`Defendants with a complaint alleging infringement of the ’565 Patent on
`
`October 1, 2015, more than one year before the present petition was filed. See Ex.
`
`2006, Summons and Proof of Service on Delaware Defendants (Oct. 1, 2015).
`
`Because, as explained below, Petitioner was in privity with the Defendants in the
`
`Delaware litigation, the petition is time barred under § 315(b).
`
`1. Involvement in a Prior Litigation Creates Privity with the Defendants
`
`The Section 315(b) one-year time bar is triggered by service of a complaint
`
`on any “privy” of Petitioner. “The use of the familiar common law terms ‘privy’
`
`
`7 Patent Owner provides substantially identical arguments in its preliminary
`
`responses to IPR2018-00574 and IPR2018-00575, filed concurrently.
`
`
`
`12
`
`PUBLIC VERSION
`
`

`

`and ‘real party in interest’ indicate that Congress intended to adopt common law
`
`principles to govern the scope of the section 315(b) one-year bar.” Wi-Fi One,
`
`LLC v. Broadcom Corp., 887 F.3d 1329, 1335 (Fed. Cir. 2018). While a
`
`determination of privity is a fact-dependent question, the applicable authorities
`
`provide a few reliable guidelines, starting with the Office Trial Practice Guide and
`
`authorities cited therein.
`
`First, the Section 315(b) time bar may be triggered by Petitioner’s
`
`involvement with the Delaware litigation, even if Petitioner was not a named
`
`defendant. “Privity is essentially a shorthand statement that collateral estoppel is
`
`to be applied in a given case …. The concept refers to a relationship between the
`
`party to be estopped and the unsuccessful party in the prior litigation which is
`
`sufficiently close so as to justify application of the doctrine of collateral estoppel.”
`
`Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,759 (Aug. 14, 2012)
`
`(quoting 154 Cong. Rec. S9987 (daily ed. Sept. 27, 2008) (statement of Sen. Kyl)).
`
`“[T]he privity inquiry … naturally focuses on the relationship between the named
`
`IPR petitioner and the party in the prior lawsuit. For example, it is important to
`
`determine whether the petitioner and the prior litigant’s relationship—as it relates
`
`to the lawsuit—is sufficiently close that it can be fairly said that the petitioner had
`
`a full and fair opportunity to litigate the validity of the patent in that lawsuit.”
`
`
`
`13
`
`PUBLIC VERSION
`
`

`

`WesternGeco LLC v. ION Geophysical Corp., No. 2016-2099, 2018 WL 2090314,
`
`at *6 (Fed. Cir. May 7, 2018).
`
`Second, Petitioner’s relationship with the Delaware Defendants supports a
`
`finding of privity. Taylor v. Sturgell, 553 U.S. 880 (2008) provides a non-
`
`exhaustive list of six categories of qualifying relationships. For example, “a
`
`nonparty is bound by a judgment if she assumed control over the litigation in
`
`which that judgment was rendered. Because such a person has had the opportunity
`
`to present proofs and argument, he has already had his day in court even though he
`
`was not a formal party to the litigation.” Taylor, 553 U.S. at 895 (internal citations
`
`and quotation marks omitted). However, “[w]hile control over the prior action is
`
`commonly present in applications of collateral estoppel, it is not essential:
`
`preclusion can apply even in the absence of such control. … The question is
`
`whether, under the circumstances as a whole, the party to be estopped should
`
`reasonably have expected to be bound by the prior adjudication.” Cal. Physicians’
`
`Serv. v. Aoki Diabetes Research Inst., 163 Cal. App. 4th 1506, 1523–24 (2008).
`
`Thus, “nonparty preclusion may be justified based on a variety of pre-existing
`
`substantive legal relationships between the person to be bound and a party to the
`
`judgment”; also, “a nonparty may be bound by a judgment because she was
`
`adequately represented by someone with the same interests who was a party to the
`
`suit.” Taylor, 553 U.S. at 894 (internal citations and quotation marks omitted).
`
`
`
`14
`
`PUBLIC VERSION
`
`

`

`Moreover, the legislative history of the America Invents Act supports a
`
`construction of “privy” as “a party that has a direct relationship to the petitioner
`
`with respect to the allegedly infringing product or service,” including for example
`
`“customers of the petitioner [that] had been sued for infringement.” 157 Cong.
`
`Rec. S5432 (daily ed. Sept. 8, 2011) (statement of Sen. Schumer).8
`
`Third, to the extent control over the prior litigation is a relevant factor in a
`
`determination of privity, complete control is not a requirement. “Preclusion is fair
`
`so long as the relationship between the nonparty and a party was such that the
`
`nonparty had the same practical opportunity to control the course of the
`
`proceedings that would be available to a party. … The appropriate measure of
`
`control does not require that the named party or parties totally abandon control to
`
`the nonparty. Instead, it should be enough that the nonparty has the actual measure
`
`of control or opportunity to control that might reasonably be expected between two
`
`formal coparties. Such relationships between a party and a nonparty are most often
`
`found when … an indemnitor participates in defending an action brought against
`
`8 While Sen. Schumer’s statement was in the context of Covered Business Method
`
`review proceedings, it is a rule of statutory construction that “identical words used
`
`in different parts of the same act are intended to have the same meaning.”
`
`Sorenson v. Sec’y of Treasury of U.S., 475 U.S. 851, 860 (1986) (quoting
`
`Helvering v. Stockholms Enskilda Bank, 293 U.S. 84, 87 (1934)).
`
`
`
`15
`
`PUBLIC VERSION
`
`

`

`its indemnitee ….” 18A Charles Alan Wright, Arthur R. Miller & Edward H.
`
`Cooper, Federal Practice & Procedure § 4451 (2d ed.) (“Wright & Miller”).
`
`Fourth, it is not necessary that P

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