throbber

`
`
`
`
`Paper No. _____
`Filed: November 27, 2017
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`_____________________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_____________________________
`
`BUNGIE, INC.,
`Petitioner,
`
`v.
`
`ACCELERATION BAY, LLC,
`Patent Owner.
`_____________________________
`
`Case IPR2017-01600
`Patent No. 6,910,069 B1
`_____________________________
`
`
`BUNGIE’S REPLY TO THE PRELIMINARY RESPONSE
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`As authorized by the Board (Paper 9), Bungie replies to Acceleration Bay’s
`
`preliminary response (Paper 6) to address a 2015 district court complaint,
`
`dismissed without prejudice for lack of standing, as to the one year bar of
`
`35 U.S.C. § 315(b), and Acceleration Bay’s reliance on Apple Inc. v. Rensselaer
`
`Polytechnic Institute, No. IPR2014-00319, Paper 12 (PTAB June 12, 2014).
`
`Even assuming privity exists,1 the Apple decision is distinguishable from the
`
`present case. Moreover, Acceleration Bay ignores the more pertinent Hamilton
`
`Beach case that confirms the one year bar of § 315(b) is inapplicable here.
`
`The Board has held that a complaint dismissed without prejudice is
`
`irrelevant to the one year bar of § 315(b). See, e.g., LG Elecs., Inc. v. Rosetta-
`
`Wireless Corp., No. IPR2016-01516, Paper 23 at 8 (PTAB Feb. 3, 2017)
`
`(discussing precedential decisions). Acceleration Bay argues that (1) the Board’s
`
`non-precedential decision in Apple recognized a broad exception whenever a later-
`
`filed complaint corrects a defect of an earlier complaint; and (2) this case fits that
`
`exception because Acceleration Bay filed its new complaint after gaining standing.
`
`
`
`1 The preliminary response incorrectly characterizes Bungie as having taken “an
`
`active role in the litigation.” While Bungie has responded to third-party subpoenas,
`
`Bungie is not a party to the litigation and was never served with the 2015
`
`complaint nor any related complaint.
`
`1
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`It is wrong on both counts. See Hamilton Beach Brands, Inc. v. F’Real Foods,
`
`LLC, No. IPR2016-01105, Paper 10 at 12 (PTAB Nov. 30, 2016) (“The Apple case
`
`is distinguishable because the earlier, first-filed lawsuit against Apple was not
`
`jurisdictionally defective for lack of standing.”); see also id. at 7-12 (full § 315(b)
`
`analysis); LG, IPR2016-01516, Paper 23 at 5-9 (PTAB Feb. 3, 2017) (same result
`
`on dismissal for misjoinder).
`
`To begin, rather than creating a broad new exception, Apple involved the
`
`existing and narrow exception for dismissals that do not actually leave the parties
`
`as if the complaint had never been filed.2 In Apple, a first complaint was filed. Id.
`
`A second complaint was also filed. Id. The parties then agreed to consolidate the
`
`two cases. To do so, they agreed to voluntarily dismiss the first-filed case3 and
`
`“proceed to litigate their claims and defenses in [the later-filed action.]” Id. In such
`
`circumstances, the Board’s “precedential cases are clear that the guiding principle
`
`is whether or not the dismissal in question left the parties as though the action had
`
`never been brought.” LG, IPR2016-01516, Paper 23 at 8 (citations omitted). The
`
`
`
`2 Acceleration Bay’s argument confuses discussion of a statute of limitations case
`
`from the Third Circuit (POPR at 33 (quoting IPR2014-00319, Paper 12 at 5-6))
`
`with the facts actually considered in Apple (IPR2014-00319, Paper 12 at 3).
`
`3 Consolidated cases are typically administratively closed, not dismissed.
`
`
`
`2
`
`
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`Board in Apple applied that guiding principle, concluding the earlier-filed case
`
`“did not cease in the same sense as a complaint dismissed without prejudice and
`
`without consolidation—it was consolidated with another case, and its complaint
`
`cannot be treated as if it never existed.” IPR2014-00319, Paper 12 at 7. The Board
`
`also noted that the earlier-filed case “immediately continued as a consolidated
`
`case, similar, in effect, to an amended case.” Id. Thus, Apple applied the existing
`
`exception for a dismissal that does not leave the parties as if the action had never
`
`been brought.
`
`Even if there were an exception where an “order of dismissal grants leave to
`
`amend within a time certain” (POPR at 33), that is not what happened here.
`
`Acceleration Bay filed the 2015 complaint. EX1045 at 2. The defendants moved to
`
`dismiss for lack of standing. Id. at 1. The court determined that Acceleration Bay
`
`lacked standing and ordered a conditional dismissal: the complaint would be
`
`dismissed unless Acceleration Bay joined Boeing, the patents’ co-owner, as a
`
`necessary party under FRCP 21. Id. at 10. Acceleration Bay did not comply.
`
`Instead, it executed an agreement with Boeing to obtain standing, requested that
`
`the 2015 complaint be dismissed, and refiled the complaint. EX1046. The court
`
`dismissed the 2015 complaint without prejudice. EX1047.
`
`The Board has recognized that amended operative complaints do not leave
`
`the parties as if the earlier complaint were never filed. See LG, IPR2016-01516,
`
`
`
`3
`
`
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`Paper 23 at 7. But here, there was no leave to amend, no time certain within which
`
`to do so, and no amended complaint within any such time certain. Acceleration
`
`Bay cites a venue order from another district court where defendants had filed for
`
`declaratory judgment in anticipation of Acceleration Bay’s re-filed complaints. But
`
`that court’s statement that “the re-filed complaints functionally were equivalent to
`
`amendments of the co-pending 2015 complaints” was made solely “for purposes of
`
`the first-to-file rule” which “is not a rigid or inflexible rule … [and] is to be
`
`applied with a view to the dictates of sound judicial administration.” 2016 WL
`
`4548985 at *3, *5; see also id. at *4 n.3 (“To be clear, the relation back doctrine,
`
`strictly construed, may not technically apply, but the present circumstances warrant
`
`the same result its application would dictate.”). That court’s analysis thus has no
`
`bearing on the instant analysis under § 315(b).4
`
`Moreover, “relation back” for purposes of § 315(b) was never possible
`
`because agreements of the type Acceleration Bay entered into with Boeing cannot
`
`confer standing retroactively. See Alps South, LLC v. Ohio Willow Wood Co., 787
`
`F.3d 1379, 1384-86 (Fed. Cir. 2015) (nunc pro tunc agreement does not cure
`
`standing). The 2015 complaint had to be dismissed, and legally became as if it had
`
`
`
`4 That court also determined the defendants’ “actions smack of gamesmanship.”
`
`2016 WL 4548985 at *6. Bungie was not a party to those actions.
`
`
`
`4
`
`
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`never been filed, because Acceleration Bay did not have standing to bring it. See
`
`id. at 1384-85 (“a party may not vindicate rights in court before the party actually
`
`possesses the rights”). Acceleration Bay is incorrect to argue that the “2015
`
`complaint ‘has not gone away’” in any sense because that argument ignores the
`
`nature of standing. As the Board recognized in Hamilton Beach, in a dismissal for
`
`lack of standing, the earlier action “is not shown to be a mere continuation of the”
`
`later, because there “is a fundamental difference between the allegation of patent
`
`infringement in the [earlier action] and the allegation of patent infringement in the
`
`[later action.]” IPR2016-01105, Paper 10 at 10-11. That is because only the later
`
`“was supported by facts necessary for Article III standing, i.e., title to the [patent at
`
`issue] held by plaintiff.” Id. The Board expressly confirmed that a complaint
`
`without standing “was not a proper federal pleading and did not trigger the one-
`
`year time period under 35 U.S.C. § 315(b).” Id. at 10.
`
`Acceleration Bay’s proposed exception is unsupported and incorrect, and the
`
`2015 complaint that was dismissed without prejudice for Acceleration Bay’s lack
`
`of standing could not trigger the one year bar as a matter of law. Acceleration
`
`Bay’s arguments regarding § 315(b) should be rejected and trial instituted.
`
`
`
`Respectfully submitted,
`
`Date: November 27, 2017
`
`
`
`
`/ Michael T. Rosato /
`Michael T. Rosato, Lead Counsel
`Reg. No. 52,182
`
`
`
`
`
`5
`
`
`
`
`
`
`
`

`

`LIST OF EXHIBITS
`
`Exhibit No.
`
`Description
`
`Case IPR2017-01600
`Patent 6,910,069 B1
`
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`1014
`
`1015
`
`U.S. Patent No. 6,910,069
`
`File History of U.S. Patent No. 6,910,069 - 0001 to 1442
`
`Declaration of Dr. Nicholas Bambos, Ph.D.
`
`Curriculum vitae of Dr. Nicholas Bambos, Ph.D.
`
`Francis, Paul, Yallcast: Extending the Internet Multicast
`Architecture (Sep. 30, 1999) (“Francis”)
`Ciriculum Vitae of Dr. Paul Francis, Ph.D
`
`Sept. 2, 2000, snapshot of www.yallcast.com, from
`web.archive.org, The Wayback Machine, last visited Feb. 9, 2017
`Feb. 17, 2001, snapshot of www.yallcast.com/docs/index.html,
`from web.archive.org, The Wayback Machine, last visited Feb. 9,
`2017
`Post-script encoding for Ex. 1005, Francis
`
`Feb. 17, 2001, snapshot of www.yallcast.com/mail/index.html,
`from web.archive.org, The Wayback Machine, last visited Feb. 9,
`2017
`Jun. 23, 2001, snapshot of groups.yahoo.com/group/yc-
`announce/, from web.archive.org, The Wayback Machine, last
`visited Feb. 9, 2017
`Jun. 23, 2001, snapshot of groups.yahoo.com/group/yc-discuss/,
`from web.archive.org, The Wayback Machine, last visited Feb. 9,
`2017
`Oct. 19, 1999, USENET annoucement, group:umich.engin.cseg.
`“Software Seminar: Dr. Paurl Francis from NTT Software
`Lab…”,
`Nov. 7, 1999, USENET annoucement, group:la.seminars.
`“Seminar – Francis – Nov. 9 10am – Y’allcast architecture”
`Presentation – Yallcast Architecture Overview
`
`
`
`6
`
`
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`Presentation – Overview of Yallcast Dynamic Topology
`Configuration
`Apr. 3, 2002 snaptshot of www.icir.org/yoid/ from
`web.archive.org, the Wayback Marchine, last visited Feb. 9, 2017
`Aug. 31, 2002 snaptshot of www.icir.org/yoid/docs/index.html
`from web.archive.org, the Wayback Marchine, last visited Feb. 9,
`2017
`Francis, Paul, Yoid: Extending the Internet Multicast Architecture
`(April 2, 2000) (“Yoid paper”)
`Declaration of Paul T. Francis
`
`U.S. Patent No. 6,490,247 to Gilbert et al. (“Gilbert”)
`
`U.S. Patent No. 5,170,482 to Shu et al.
`
`Frank et al., Multicast Communication on Network Computers,
`IEEE Software (1985)
`Friesen et al., Resource Management with Virtual Paths in ATM
`Networks, IEEE Network (1996)
`Dalal, Yogen Kantilal, Broadcast Protocols in Packet Switched
`Computer Networks, Ph.D. dissertation, Stanford University
`(1977)
`Chen et al., Addressing, Routing, and Broadcasting in Hexagonal
`Mesh Multiprocessors, IEEE Transactions on Computers (1990)
`Fragopoulou et al., Efficient Algorithms for Global Data
`Communication on the Multidimensional Torus Network, Parallel
`Processing Symposium Proceedings, IEEE (1995)
`Maxemchuk, Nicholas F., Routing in the Manhattan Street
`Network, IEEE Transactions on Communications (1987)
`Chalasani et al., Adaptive Wormhold Routing in Tori with Faults,
`IEEE Proceedings – Computers and Digital Techniques (1995)
`U.S. Patent No. 5,056,085 to Vu
`
`Ballardie et al., Core Based Trees (CBT): An Architecture for
`Scalable Inter-Domain Multicast Routing, ACM SIGCOMM
`Computer Communication Review (1993)
`U.S. Patent No. 5,331,637 to Francis et al.
`
`1016
`
`1017
`
`1018
`
`1019
`
`1020
`
`1021
`
`1022
`
`1023
`
`1024
`
`1025
`
`1026
`
`1027
`
`1028
`
`1029
`
`1030
`
`1031
`
`1032
`
`
`
`7
`
`
`
`

`

`Case IPR2017-01600
`Patent 6,910,069 B1
`Garcia-Luna-Aceves et al., A Multicast Routing Protocol for Ad-
`Hoc Networks, INFOCOM'99, Eighteenth Annual Joint
`Conference of the IEEE Computer and Communications
`Societies, IEEE (1999)
`Deering, Request for Comments: 1112, IETF (1989)
`
`Fenner, Request for Comments: 2236, IETF (1997)
`
`Estrin et al., Request for Comments: 2362, IETF (1998)
`
`Liu et al., A Scalable Multicast Routing, MILCOM 97
`Proceedings, IEEE (1997)
`U.S. Patent No. 6,603,742 to Steele et al. (“Steele”)
`
`Chawathe et al., RMX Reliable Multicast for Heterogeneous
`Networks, INFOCOM 2000, Nineteenth Annual Joint Conference
`of the IEEE Computer and Communications Societies, IEEE
`(2000) (“Chawathe”)
`Chu et al., A Case for End System Multicast, ACM SIGMETRICS
`Performance Evaluation Review (2000)
`http://gaia.cs.umass.edu/sigmetrics2000/cfp.htm (retrieved
`February 9, 2017).
`http://nms.lcs.mit.edu/projects/ron/refs/ (retrieved June 5, 2017).
`
`Aug. 18, 2000, snapshot of nms.lcs.mit.edu/projects/ron/, from
`web.archive.org, The Wayback Machine, last visited June 15,
`2017
`http://nms.lcs.mit.edu// (retrieved June 5, 2017).
`
`Memorandum regarding Standing in Acceleration Bay LLC v.
`Activision Blizzard, Inc., Civil Action No. 15-228, D.I. 148, June
`3, 2016
`Letter to the Honorable Richard G. Andrews from Philip A.
`Rovner, Esq. in Acceleration Bay LLC v. Activision Blizzard,
`Inc., Civil Action No. 15-228, D.I. 155, June 24, 2016
`Order regarding Standing in Acceleration Bay LLC v. Activision
`Blizzard, Inc., Civil Action No. 15-228, D.I. 153, June 20, 2016
`
`
`8
`
`
`
`1033
`
`1034
`
`1035
`
`1036
`
`1037
`
`1038
`
`1039
`
`1040
`
`1041
`
`1042
`
`1043
`
`1044
`
`1045
`
`1046
`
`1047
`
`
`
`
`
`

`

`CERTIFICATE OF SERVICE
`
`Case IPR2017-01600
`Patent 6,910,069 B1
`
`I certify that the foregoing Bungie’s Reply to the Preliminary Response and
`
`Exhibits 1045 through 1047 were served on this 27th day of November, 2017 on
`
`the Patent Owner at the electronic service addresses of the Patent Owner as
`
`follows:
`
`James Hannah
`Jeffrey H. Price
`KRAMER LEVIN NAFTALIS & FRANKEL LLP
`Email: jhannah@kramerlevin.com
`Email: jprice@kramerlevin.com
`Email: svdocketing@kramerlevin.com
`
`
`
`
`Date: November 27, 2017
`
`
`
`
`
`Respectfully submitted,
`
`
`/ Michael T. Rosato /
`Michael T. Rosato, Lead Counsel
`Reg. No. 52,182
`
`
`
`
`
`9
`
`
`
`
`
`

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