throbber
Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 1 of 12 Page ID #:1280
`
`
`
`
`Aaron S. Jacobs (Cal. Bar No. 214953)
`ajacobs@princelobel.com
`James J. Foster
`jfoster@princelobel.com
`PRINCE LOBEL TYE LLP
`One International Place, Suite 3700
`Boston, MA 02110
`Tel: (617) 456-8000
`
`Matthew D. Vella (Cal. State Bar No. 314548)
`mvella@princelobel.com
`PRINCE LOBEL TYE LLP
`357 S. Coast Highway, Suite 200
`Laguna Beach, CA 92651
`Tel: (949) 232-6375
`
`Attorneys for Plaintiff
`
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`
`
`UNILOC 2017 LLC,
`
`
`
`v.
`
`INFOR, INC.,
`
`Defendant.
`
`UNILOC 2017 LLC,
`
`
`
`v.
`
`UBISOFT, INC.,
`
`
`
`Plaintiff,
`
`Plaintiff,
`
`Defendant.
`
`UNITED STATES DISTRICT COURT
`
`CENTRAL DISTRICT OF CALIFORNIA
`
`SANTA ANA DIVISION
`
`
`Case No. 8:19-cv-01150-DOC-KES
`
`(CONSOLIDATED)
`
`PLAINTIFF’S OPPOSITION TO
`UBISOFT’S MOTION FOR
`JUDGMENT ON THE PLEADINGS
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`3592839.v1
`
`
`
`Case No. 8:19-cv-01150-DOC-KES
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 2 of 12 Page ID #:1281
`
`
`
`1
`
`2
`
`3
`
`Plaintiff, Uniloc 2017 LLC (“Uniloc”), respectfully submits this brief in
`
`Opposition to the Motion for Judgment on the Pleadings, Dkt. No. 67 (“Motion”), of
`
`Defendant Ubisoft, Inc. (“Ubisoft”). For the reasons set forth below, the Motion
`
`4
`
`should be denied.
`
`5
`
`6
`
`7
`
`8
`
`9
`
`Ubisoft’s Motion argues a dismissal of an unrelated action Uniloc had brought
`
`against Akamai Technologies, Inc. (“Akamai”) created claim preclusion that extends
`
`to this action. But Ubisoft was not a party to that action, nor in privity with Akamai.
`
`Further, the action was dismissed on the basis of a defense that was personal to
`
`Akamai, which defense does not apply to Ubisoft. Finally, much of Ubisoft’s
`
`10
`
`infringing activity does not even involve Akamai.
`
`11
`
`12
`
`13
`
`I.
`
`Background
`
`a.
`
`Preclusion in the Federal Courts.
`
`Preclusion law or the law of judgments (sometimes referred to as res judicata
`
`14
`
`or collateral estoppel) is the jurisprudence that determines whether a court should
`
`15
`
`give preclusive effect to an earlier decision made in a different action. The purpose
`
`16
`
`of preclusion law is to avoid the needless relitigation of factual and legal issues that
`
`17
`
`have already been decided, and in some cases even those that were not but could
`
`18
`
`have been decided, in prior adjudications. Preclusion law is generally divided into
`
`19
`
`the broad categories of issue preclusion and claim preclusion.
`
`20
`
`Issue preclusion bars subsequent litigation on an issue of law or fact that was
`
`21
`
`actually litigated. Brain Life, LLC v. Elekta Inc., 746 F.3d 1045, 1054-55 (Fed. Cir.
`
`22
`
`2014). See Restatement (Second) of Judgments §27. If an issue of fact or law is
`
`23
`
`actually litigated and determined by final judgment, and the determination is
`
`24
`
`essential to the judgment, that determination is conclusive in any later action
`
`25
`
`between the parties on the same or a different claim. Brain Life, 746 F.3d at 1055.
`
`26
`
`By contrast, claim preclusion may bar subsequent litigation on issues that
`
`27
`
`were not actually litigated, but only if they would have been part of the same claim
`
`28
`
`that was resolved. The aim of claim preclusion is to avoid multiple suits on identical
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`1
`
`
`
`Case No. 8:19-cv-01150-DOC-KES
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 3 of 12 Page ID #:1282
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`obligations between the same parties. Claim preclusion is invoked upon a
`
`determination that the issues precluded should have been advanced in the earlier suit.
`
`Whether a cause of action is barred by claim preclusion is a question of law.
`
`Generally, the Federal Circuit will apply the law of the regional circuit in which the
`
`trial court resides. Id. at 1052.
`
`The Ninth Circuit has held that claim preclusion applies where the prior suit
`
`(1) involved the same claim or cause of action as the later suit; (2) reached a final
`
`judgment on the merits; and (3) involved identical parties or privies. Mpoyo v. Litton
`
`Electro-Optical Sys., 430 F.3d 985, 987 (9th Cir. 2005). The Federal Circuit will
`
`10
`
`apply its own law as to whether two claims of infringement constitute the same
`
`11
`
`claim or cause of action. Brain Life, 746 F.3d at 1052.
`
`12
`
`Claim preclusion is an affirmative defense. And it is incumbent on the
`
`13
`
`defendant to prove such a defense. Taylor v. Sturgell, 553 U.S. 880, 908 (2008).
`
`14
`
`15
`
`b.
`
`The IBM assignment and the Akamai litigation.
`
`IBM, the original owner of the patents-in-suit in this action, assigned those
`
`16
`
`patents to Uniloc. Gannon Decl., Ex. 1. In the assignment agreement, IBM retained
`
`17
`
`the right to grant a sublicense to “IBM Strategic Partners,” i.e., entities with which it
`
`18
`
`had done a certain volume of business prior to the assignment. Id., § 2.1(f), 5. The
`
`19
`
`assignment also imposed an indemnification obligation on Uniloc if it maintained a
`
`20
`
`claim against any third party “knowing” it was an IBM Strategic Partner. Id., §4.3.
`
`21
`
`IBM provided Uniloc with a written assurance that Akamai did not qualify as
`
`22
`
`an IBM Strategic Partner. See Gannon Decl., Ex. 2. Uniloc then sued Akamai for
`
`23
`
`patent infringement. The assurance from IBM, however, turned out to be wrong.
`
`24
`
`After the suit was filed, Akamai moved to dismiss, providing evidence that it had
`
`25
`
`done sufficient business with IBM to qualify as an IBM Strategic Partner. Dkt. No.
`
`26
`
`67-5, at 2.
`
`27
`
`28
`
`
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`2
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 4 of 12 Page ID #:1283
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`In view of that evidence, and despite the fact that IBM had not issued a license
`
`to Akamai, Uniloc agreed to a dismissal because proceeding with the suit under the
`
`circumstances would be impractical, but argued the dismissal should be without
`
`prejudice. Dkt. No. 67-8; 67-9. The court, however, granted a dismissal with
`
`prejudice, over Uniloc’s objection. Dkt. No. 67-9. (“Akamai Order.”)
`
`c.
`
`Ubisoft’s Motion.
`
`Ubisoft was not a party to, and had no involvement in or relationship to, the
`
`Akamai action. It did not control the Akamai litigation, nor did it have any
`
`indemnification agreement with Akamai.
`
`10
`
`The indemnification issue that arose in the Akamai litigation, described above,
`
`11
`
`does not arise here. Ubisoft is not, and does not claim to be, an IBM Strategic
`
`12
`
`Partner1. Ubisoft does not claim IBM has a right to issue it a sublicense. And it does
`
`13
`
`not claim Uniloc has an obligation to indemnify it. The defense raised by Akamai for
`
`14
`
`its own benefit in the Akamai litigation was personal to Akamai. The defense does
`
`15
`
`not apply to the infringement claims asserted here against Ubisoft.
`
`16
`
`Because the Akamai action was dismissed at the outset based on that defense,
`
`17
`
`no other issues were actually litigated in the action. Ubisoft’s Motion thus does not
`
`18
`
`rely upon issue preclusion.
`
`19
`
`Instead, Ubisoft argues that because the Akamai Order was with prejudice it
`
`20
`
`created claim preclusion requiring the Court to dismiss this action. To support its
`
`21
`
`position, Ubisoft argues its activity accused of infringement in the counterclaims, see
`
`22
`
`Dkt. No. 29, was carried out on an Akamai content delivery network (CDN), and
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`thus Uniloc’s claim against Ubisoft is identical to its claim against Akamai.
`
`
`
`
`1 In fact, the IBM assignment agreement identified Ubisoft as an entity that did not
`“meet the definition of” IBM Strategic Partner. Ex. 1, at 8, 12.
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`3
`
`
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 5 of 12 Page ID #:1284
`
`
`
`II. Argument
`
`a.
`
`The Motion is limited to the use of an Akamai CDN.
`
`Ubisoft’s Motion for judgment on the pleadings argues the dismissal with
`
`prejudice of the action against Akamai, Dkt. No. 67-9, an unrelated entity, created
`
`1
`
`2
`
`3
`
`4
`
`5
`
`claim preclusion here.
`
`6
`
`7
`
`8
`
`9
`
`But Uniloc had not mentioned Akamai in the pleadings in this action, nor had
`
`Ubisoft.2 See Dkt. Nos. 1, 29. Uniloc did mention the Akamai CDN in its
`
`infringement contentions in this action, but only with respect to one of the two
`
`patents-in-suit, the ’293 patent. Those contentions named Akamai not as itself an
`
`10
`
`infringer, but simply as an entity that maintains a CDN on which Ubisoft had
`
`11
`
`conducted some of its infringing activity, as regards the ’293 patent.
`
`12
`
`Akamai’s CDN is not the only CDN that Ubisoft has used or is using to
`
`13
`
`conduct its infringing activity. Ubisoft acquired its own CDN, i3D.net, two years
`
`14
`
`ago, presumably to replace the Akamai CDNs, see Gannon Decl., Ex. 3. And Uniloc
`
`15
`
`believes that even before the acquisition Ubisoft also made extensive use of the
`
`16
`
`CDNs of i3D.net.3
`
`17
`
`Because of this factual problem, this Opposition will treat the Motion as
`
`18
`
`limited to claims of Ubisoft’s infringement by use of an Akamai CDN.
`
`19
`
`20
`
`b.
`
`Claim preclusion does not apply.
`
`Ubisoft cannot argue issue preclusion because the only issue that was actually
`
`21
`
`argued and decided in the Akamai litigation does not arise in this action.
`
`
`2 Although Ubisoft claims to direct its Motion to the pleadings, the pleadings
`themselves nowhere mention Akamai, or any suit against Akamai. As the Motion
`presents matters outside the pleadings, per Rule 12(d) the Court should treat it as one
`for summary judgment under Rule 56.
`
` 3
`
` The above discussion pertains only to the ’293 patent. Ubisoft did not identify any
`documents in this action connecting Ubisoft’s infringement of the ’578 patent to
`Akamai.
`
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`4
`
`
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 6 of 12 Page ID #:1285
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`Instead, Ubisoft argues claim preclusion, which is a doctrine normally
`
`invoked to bar a plaintiff from pursuing in a second action a claim which could have
`
`been, but was not, pursued in a first action against the same party or its privies.
`
`As discussed above, however, Ubisoft was neither a party or a privy to the
`
`Akamai action. In any event, claim preclusion does not apply where, as here, the first
`
`action was decided on a defense that was personal to the defendant in the first action.
`
`On issues of preclusion, the Federal Circuit has repeatedly stated it “would
`
`receive guidance from Restatement (Second) of Judgments (1982).” Young Eng’rs,
`
`Inc. v. United States Int’l Trade Comm’n, 721 F.2d 1305, 1314 (Fed. Cir. 1983); Jet,
`
`10
`
`Inc. v. Sewage Aeration Sys., 223 F.3d 1360, 1362 (Fed. Cir. 2000). This Opposition
`
`11
`
`thus relies on principles from that Restatement.
`
`12
`
`13
`
`c.
`
`Ubisoft was not a privy to the Akamai action.
`
`Uniloc, as the patent owner, sued Akamai and Ubisoft in separate actions.
`
`14
`
`Separate actions against different defendants generally do not result in claim
`
`15
`
`preclusion, even where they could be liable for the same loss. The Restatement
`
`16
`
`(Second) of Judgments § 49 sets forth the applicable rule:
`
`Judgment against One of Several Persons Liable for the Same Loss:
`
`
`A judgment against one person liable for a loss does not terminate a
`
`claim that the injured party may have against another person who
`
`may be liable therefor.
`
`
`
`Comment: a. Rationale. When a person suffers injury as the result
`
`of the concurrent or consecutive acts of two or more persons, he has
`
`a claim against each of them. If he brings an action against one of
`
`them [and] judgment is rendered against him, he is barred from
`
`bringing a subsequent action against the obligor…. But the claim
`
`against others who are liable for the same harm is regarded as
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`5
`
`
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 7 of 12 Page ID #:1286
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`separate. Accordingly, a judgment for … one obligor does not result
`
`in … bar of the claim that the injured party may have against
`
`another obligor.
`
`(Emphasis added).
`
`Claim preclusion operates only against parties to the first suit and others who
`
`bear such a relationship to the suit or to the parties that it is thought proper to
`
`preclude them – generally referred to as privies. The Supreme Court, in Taylor, 553
`
`U.S. at 893-95, after restating the rule against extending claim preclusion to cases
`
`involving nonparties, described the various categories of recognized exceptions,
`
`none of which would seem to apply to Ubisoft’s argument here.
`
`In Taylor, the Court rejected an attempt to make an additional exception for
`
`situations where a party in the first action was argued to have “virtually represented”
`
`the party in the second action because of “an identity of interest and some kind of
`
`relationship” between the party and a nonparty. Id. at 900-01. The Court was
`
`concerned that approach would circumvent procedural protections grounded in due
`
`16
`
`process. Id. at 901.
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`For patent infringement actions, Transclean Corp. v. Jiffy Lube Int’l, Inc., 474
`
`F.3d 1298, 1306 (Fed. Cir. 2007) states the rule:
`
`
`a manufacturer or seller of product who is sued for patent
`
`infringement typically is not in privity with a party, otherwise
`
`unrelated, who does no more than purchase and use the product. In
`
`other words, ordinarily such parties are not so closely related and
`
`their litigation interests are not so nearly identical that a patentee’s
`
`suit against one would bar a second action against the other under
`
`the doctrine of claim preclusion.
`
`Ubisoft claims to be a customer of Akamai, but, as Taylor holds, that two
`
`parties are aligned in interest and have some kind of relationship does not, without
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`6
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 8 of 12 Page ID #:1287
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`more, create privity. A judgment against Akamai, had one been entered, thus would
`
`not have bound Ubisoft, because Ubisoft did not control the Akamai litigation, nor
`
`did it have an indemnification relationship with Akamai.
`
`d.
`
`The Akamai action was decided on a defense personal to the
`
`defendant in that action.
`
`Claim preclusion does not apply where, as here, the first action was decided
`
`on a defense that was personal to the defendant in the first action. The Restatement
`
`(Second) of Judgments §51 sets forth the applicable rule:
`
`Persons Having a Relationship in Which One Is Vicariously Responsible
`
`for the Conduct of the Other
`
`
`If two persons have a relationship such that one of them is
`
`vicariously responsible for the conduct of the other, and an action
`
`is brought by the injured person against one of them, the judgment
`
`in the action has the following preclusive effects against the
`
`injured person in a subsequent action against the other.
`
`
`
`
`
`(1) A judgment against the injured person that bars him
`
`from reasserting his claim against the defendant in the first
`
`action extinguishes any claim he has against the other person
`
`responsible for the conduct unless … (b) the judgment in the
`
`first action was based on a defense that was personal to the
`
`defendant in the first action.
`
`
`
`(Emphasis added). See Gillig v. Nike Inc., 602 F.3d 1354, 1362 (Fed. Cir. 2010)
`
`(claim preclusion does not apply where the only issue determined in the earlier
`
`lawsuit had no bearing on the party in the second lawsuit); Sharp Kabushiki Kaisha
`
`v. Thinksharp, Inc., 448 F.3d 1368, 1372 (Fed. Cir. 2006) (“when a party did not
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`7
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 9 of 12 Page ID #:1288
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`have an opportunity to litigate disputed issues, a decision to permit such litigation is
`
`favored”); Burdette v. Carrier Corp., 158 Cal. App. 4th 1668, 1684, 71 Cal. Rep. 3d
`
`185, 197-98 (Ct. App. 2008) (successful privilege defense in prior defamation action
`
`against employer did not prevent the assertion of a defamation claim against lower
`
`level employees who did not have that defense).
`
`6
`
`
`
`Due process requires such a result. The issue of whether Ubisoft’s use of an
`
`7
`
`8
`
`9
`
`Akamai CDN infringed the claims of either of the patents could not have been
`
`determined in the Akamai litigation for the simple reason that Akamai’s
`
`indemnification defense prevented the court from reaching that issue. Because that
`
`10
`
`defense would not have been available to Ubisoft, the defense would not prevent
`
`11
`
`Uniloc from recovering from Ubisoft. A finding of claim preclusion would thus
`
`12
`
`deprive Uniloc of its day in court.
`
`13
`
`14
`
`
`
`e.
`
`Personal Web is distinguishable
`
`Ubisoft relies heavily on PersonalWeb Technologies LLC, 961 F.3d 1365,
`
`15
`
`1372-74 (Fed. Cir. 2020), where the second action was brought against customers of
`
`16
`
`the defendant (Amazon) in the first action, and the court found claim preclusion. But
`
`17
`
`that case differs from this one in two fundamental ways.
`
`18
`
`
`
`In Personal Web, the plaintiff agreed the customers were in privity with
`
`19
`
`Amazon because Amazon had agreed to indemnify its customers and had assumed
`
`20
`
`the defense of its customers against PersonalWeb. Id. at 1373, 1374. By contrast, as
`
`21
`
`discussed above, Akamai and Ubisoft had no such arrangements, and thus Ubisoft
`
`22
`
`was not in privity with Akamai.
`
`23
`
`
`
`Personal Web can be distinguished on another ground, namely, the dismissal
`
`24
`
`with prejudice had been stipulated to as part of a voluntary dismissal of all of
`
`25
`
`PersonalWeb’s claims in the first action. The Federal Circuit identified that as the
`
`26
`
`reason that preclusion would not be unfair, because where a case is settled plaintiff
`
`27
`
`28
`
`
`
`could have reserved the right to sue Amazon’s customers:
`
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`8
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 10 of 12 Page ID #:1289
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`To the extent that a plaintiff wishes to settle an infringement action
`
`while preserving its rights to sue the same or other parties in the
`
`future, it can do so by framing the dismissal agreement to preserve
`
`any such rights that the defendant is willing to agree to. Settling
`
`parties will remain free to limit the preclusive effect of a dismissal;
`
`they simply have to fashion their agreement in a way that makes
`
`clear any limitations to which they wish to agree as to the
`
`downstream effect of the dismissal.
`
`Id. at 1379.
`
`By contrast, Uniloc did not stipulate to a dismissal with prejudice in Akamai,
`
`but rather vigorously opposed it. Unlike the parties in PersonalWeb, Uniloc was not
`
`free to preserve its rights to sue other parties in the future by limiting the preclusive
`
`effect of a dismissal. As the Federal Circuit has held in another action: “In a
`
`settlement agreement, the parties to an action can determine for themselves what
`
`preclusive effect the settlement of the first action will have has to any potential
`
`subsequent actions between the parties.” Aspex Eyewear, Inc. v. Marchon Eyewear,
`
`Inc., 672 F.3d 1335, 1345 (Fed. Cir. 2012).
`
`For that reason, dismissal here would deprive Uniloc of due process, because
`
`it would deprive Uniloc of its day in court as to whether Ubisoft’s actions infringe.
`
`f.
`
`The Kessler doctrine.
`
`The Motion, at 6-7, briefly mentions the discussion in PersonalWeb of the
`
`doctrine of Kessler v. Eldred, 206 U.S. 285 (1907), as support for extending the
`
`effect of what would otherwise be claim preclusion to the period after the judgment
`
`relied upon. 961 F.3d at 1376-79. Putting aside the issue of temporality, the Motion
`
`does not appear to argue the Kessler doctrine would apply where claim preclusion
`
`26
`
`does not.
`
`27
`
`28
`
`
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`9
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 11 of 12 Page ID #:1290
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`In any event, PersonalWeb found the Kessler doctrine would not bar a second
`
`lawsuit where a license that ended the first lawsuit was no longer in effect, citing
`
`Mentor Graphics Corp v. EVE-USA, Inc., 851 F.3d 1275 (Fed. Cir. 2017). The court
`
`held that because “EVE was a willing licensee, not an adjudicated non-infringer,”
`
`Kessler did not apply. Here, as in Mentor Graphics, the Akamai court did not find
`
`Akamai to be a non-infringer, but dismissed the action on indemnification grounds,
`
`not reaching any infringement-related issues.
`
`III. Conclusion
`
`The Akamai court dismissed that action because of a defense based on a
`
`10
`
`contractual indemnification provision to which Ubisoft is not a third-party beneficiary.
`
`11
`
`Further, Akamai and Ubisoft are not in privity. Claim preclusion thus does not apply
`
`12
`
`and Ubisoft’s Motion should be denied.
`
`
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`10
`
`
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`
`
`
`
`
`
`

`

`Case 8:19-cv-01150-DOC-KES Document 76 Filed 12/07/20 Page 12 of 12 Page ID #:1291
`
`
`
`Dated: December 7, 2020
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`/s/ James J. Foster
`Aaron S. Jacobs (Cal. Bar No. 214953)
`ajacobs@princelobel.com
`James J. Foster
`jfoster@princelobel.com
`PRINCE LOBEL TYE LLP
`One International Place, Suite 3700
`Boston, MA 02110
`Tel: (617) 456-8000
`
`Matthew D. Vella (Cal. State Bar No. 314548)
`mvella@princelobel.com
`PRINCE LOBEL TYE LLP
`357 S. Coast Highway, Suite 200
`Laguna Beach, CA 92651
`Tel: (949) 232-6375
`
`Attorneys for Plaintiff
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`
`
`
`
`
`
`
`
`
`
`
`PLAINTIFF’S OPPOSITION TO UBISOFT, INC.’S MOTION
`FOR JUDGMENT ON THE PLEADINGS
`
`11
`
`
`
`

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