throbber
Case 1:16-cv-00453-WCB Document 852 Filed 05/02/24 Page 1 of 4 PageID #: 56706
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF DELAWARE
`
`
`
`
`
`
`
`C.A. No. 16-453-WCB
`
`
`
`)))))))))
`
`
`
`Plaintiffs,
`
`
`
`v.
`
`ACCELERATION BAY LLC,
`
`
`
`
`
`ACTIVISION BLIZZARD INC.,
`
`
`
`
`
`Defendants.
`
`
`
`
`
`ACCELERATION BAY LLC’S LETTER BRIEF REGARDING
`THE CONSTRUCTION OF “M-REGULAR” IN CLAIM 1 OF THE ’147 PATENT
`
`
`POTTER ANDERSON & CORROON LLP
`Philip A. Rovner (#3215)
`Hercules Plaza
`P.O. Box 951
`Wilmington, DE 19899
`(302) 984-6000
`provner@potteranderson.com
`
`Attorneys for Acceleration Bay LLC
`
`
`
`OF COUNSEL:
`
`Paul J. Andre
`Lisa Kobialka
`James R. Hannah
`Christina Finn
`Aakash Jariwala
`Melissa Brenner
`KRAMER LEVIN NAFTALIS
` & FRANKEL LLP
`333 Twin Dolphin Dr., Suite 700
`Redwood Shores, CA 94065
`(650) 752-1700
`
`Aaron M. Frankel
`Cristina Martinez
`Marcus Colucci
`KRAMER LEVIN NAFTALIS
` & FRANKEL LLP
`1177 Avenue of the Americas
`New York, NY 10036
` (212) 715-9100
`
`Dated: May 2, 2024
`
`
`
`
`
`
`
`

`

`Case 1:16-cv-00453-WCB Document 852 Filed 05/02/24 Page 2 of 4 PageID #: 56707
`
`The Court should reject Activision’s eleventh-hour request to import into “m-regular” a
`
`requirement that the network be incomplete. The Court already construed “m-regular” without
`
`requiring that it be incomplete. D.I. 275 at 14-15. Activision did not previously request a
`
`construction that “m-regular” must be incomplete and, therefore, waived the argument.1
`
`Claim 1 of the ’147 Patent requires a broadcast channel that forms an “m-regular graph,”
`
`but does not require that the graph is incomplete:
`
`A method of disconnecting a first computer from a second computer, the first
`computer and the second computer being connected to a broadcast channel, said
`broadcast channel forming an m-regular graph where m is at least 3, the method
`comprising:
`
`In contrast, Claim 1 of the ’344 Patent includes a clause specifically requiring a network
`
`that is both “m-regular” and “non-complete”:
`
`further wherein the network is m-regular, where m is the exact number of neighbor
`participants of each participant and further wherein the number of participants is
`at least two greater than m thus resulting in a non-complete graph.
`
`The inventors’ use of both “m-regular” and “non-complete” confirms their awareness of
`
`that the two concepts are distinct. Their decision not to include an “incomplete graph” limitation
`
`in the claims of the ’147 Patent should be credited. Comark Commc’ns, Inc. v. Harris Corp.,
`
`156 F.3d 1182, 1186-87 (Fed. Cir. 1998) (noting the starting point of claim construction is the
`
`“asserted claim itself” and there is a presumed “‘difference in meaning and scope when different
`
`words or phrases are used in separate claims.’”) (citation omitted). Moreover, the use of the
`
`“further wherein” language in Claim 1 of the ’344 Patent confirms that m-regular and non-
`
`complete have distinct meanings to a person of ordinary skill in the art. Otherwise there would
`
`
`1 Activision contends that O2 Micro Int’l Ltd. v. Monolithic Power Sys., Inc., requires that the
`Court address this issue. 467 F.3d 1355 (Fed. Cir. 2006). O2 Micro does not apply because the
`m-regular claim term was already construed as part of the Court’s extensive claim construction
`process. There is no new development that requires reconsideration of the prior construction.
`
`
`
`
`
`

`

`Case 1:16-cv-00453-WCB Document 852 Filed 05/02/24 Page 3 of 4 PageID #: 56708
`
`be no need to include the modifier in Claim 1 of the ’344 Patent that the m-regular network must
`
`also be non-complete. Indeed, Activision’s technical expert, Dr. Wicker, confirmed that an “m-
`
`regular” network can be either “complete” or “incomplete,” confirming that an m-regular
`
`network should not be limited to only incomplete networks. 5/1/24 Draft Trial Tr. at 224:2-3 (“I
`
`showed you an m-regular graph that was also incomplete.”), 213:1-2 (“So not only is this m-
`
`regular, or, in this case, 4-regular, it's also complete.”) (emphasis added).
`
`Activision’s proposed construction also should be rejected because it would render as
`
`mere surplusage the “further wherein …. Thus resulting in a non-complete graph” clause in
`
`Claim 1 of the ’344 Patent. “[I]nterpretations that render some portion of the claim language
`
`superfluous are disfavored.” Power Mosfet Techs., L.L.C. v. Siemens AG, 378 F.3d 1396, 1410
`
`(Fed. Cir. 2004). Instead, terms should be “construe[d] . . . with an eye toward giving effect to
`
`all of their terms” lest it “undermine[]” the essential notice function of patent claims.
`
`Haemonetics Corp. v. Baxter Healthcare Corp., 607 F.3d 776, 781 (Fed. Cir. 2010).
`
`There is no basis to import into Claim 1 of the ’147 Patent a requirement that the graph
`
`be incomplete. Indeed, the words “incomplete” or “non-complete” do not appear anywhere in
`
`the specification of the ’147 Patent. It would be improper to import limitations from another
`
`patent, such as the ‘344 Patent, into the ’147 Patent. Aventis Pharms. Inc. v. Amino Chems. Ltd.,
`
`715 F.3d 1363, 1373 (Fed. Cir. 2013) (Courts should “look to the words of the claims themselves
`
`. . . to define the scope of the patented invention.”). The ’344 and ’147 Patents are not related
`
`and have different specifications.
`
`Finally, the file history further confirms that “m-regular” should not be construed to be
`
`incomplete. During the prosecution of the ’147 Patent, the “m-regular” limitation was originally
`
`set forth in a dependent claim. Ex. 1 (12/11/03 Amendment) at 11. In order to overcome a prior
`
`2
`
`

`

`Case 1:16-cv-00453-WCB Document 852 Filed 05/02/24 Page 4 of 4 PageID #: 56709
`
`art rejection, the inventors reformed that dependent claim into an independent claim including
`
`the “m-regular” limitation. Id. at 4-6, 11. Their accompanying argument to overcome the
`
`rejection was limited to the claimed network being m-regular, and made no reference to the
`
`network being incomplete. Id. at 8-13.2
`
`Activision suggests that the Court’s prior rulings in the Take-Two summary judgment
`
`order found Claim 1 of the ’147 Patent to require an incomplete network. Neither party
`
`presented that issue to the Court in connection with the summary judgment briefing because
`
`most of the asserted claims at issue in that case expressly recited networks that were both m-
`
`regular and incomplete. Thus, the Court’s passing reference in the background section of the
`
`summary judgment order to the claims being directed to networks that are m-regular and
`
`incomplete was not a claim construction decision. See Acceleration Bay LLC v. Take-Two et al,
`
`1:16-cv-00455-RGA, D.I. 492 at 2 (D. Del. Mar. 23, 2020).
`
`Accordingly, the Court’s prior construction for “m-regular” should not be changed to
`
`include an “incomplete” network requirement.
`
`Respectfully submitted,
`
`/s/ Philip A. Rovner
`
`
`
`
`
`Philip A. Rovner (#3215)
`
`
`cc: All counsel of Record (Via ECF Filing, Electronic Mail)
`
`
`
`2 IPR 2016-00747 does not support importing into Claim 1 of the ’147 Patent a limitation that the
`network be incomplete. Activision appears to be relying on some general characterizations of
`the art that were not used in Acceleration Bay’s response to any of the specific grounds at issue
`(which was based on m-regularity) and were not argued as claim construction. The PTAB’s
`decision not to institute on Claim 1 did not depend on or even refer to the asserted references
`failing to disclose an incomplete network. Ex. 2 at 15-16. Thus, there was no “clear and
`unmistakable disclaimer” to support a disavowal of claim scope and there is no claim
`construction from the PTAB for the Court to consider adopting. Cont’l Circuits LLC v. Intel
`Corp., 915 F.3d 788, 796-97 (Fed. Cir. 2019).
`
`3
`
`

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