XpertUniverse, Inc. v. Cisco Systems, Inc., No. 3:2017cv03848 - Document 169 (N.D. Cal. 2019)
Court Description: ORDER DENYING CISCO'S MOTION TO STRIKE APPENDICES F1, F2, G1, AND G2 TO XPERTUNIVERSE'S INFRINGEMENT CONTENTIONS re 140 Notice (Other) filed by Cisco Systems, Inc.. Signed by Judge Richard Seeborg on 7/29/2019. (tlS, COURT STAFF) (Filed on 7/29/2019)
Download PDF
<![CDATA[
XpertUniverse, Inc. v. Cisco Systems, Inc. Doc. 169 1 2 3 4 5 6 7 UNITED STATES DISTRICT COURT 8 NORTHERN DISTRICT OF CALIFORNIA 9 10 XPERTUNIVERSE, INC., Case No. 17-cv-03848-RS Plaintiff, 11 United States District Court Northern District of California v. 12 13 CISCO SYSTEMS, INC., Defendant. ORDER DENYING CISCO’S MOTION TO STRIKE APPENDICES F1, F2, G1, AND G2 TO XPERTUNIVERSE’S INFRINGEMENT CONTENTIONS 14 15 16 I. INTRODUCTION In July 2017, Plaintiff XpertUniverse, Inc. (“XU”) filed the present action in federal court 17 accusing Defendant Cisco Systems, Inc. (“Cisco”) of infringing U.S. Patent No. 7,499,903 (“the 18 ’903 patent”). The action was stayed from July 13, 2018 until May 30, 2019. Cisco now renews its 19 motion to strike Appendices F1, F2, G1, and G2 to XU’s infringement contentions, which was 20 fully briefed prior to the stay. A hearing was held on July 18, 2019 and the motion was taken 21 under submission. For the reasons set forth below, the motion to strike is denied. 22 II. BACKGROUND 23 A. Prior Infringement Action Between XU and Cisco 24 The present action is not the first time XU and Cisco have squared off over alleged 25 infringement of the ’903 patent. In March 2009, XU filed a complaint against Cisco in the District 26 of Delaware. XU’s infringement contentions in that case (the “Delaware Case”) accused the Cisco 27 Unified Expert Advisor (“Expert Advisor”) product and the Remote Expert product, among 28 others. Evidence in that case showed Expert Advisor was, at the time, an optional feature or add- Dockets.Justia.com 1 on for the Cisco Unified Contact Center (“UCC”).1 Publicly available documentation confirms 2 that Expert Advisor was a feature of UCCE versions 7.2, 7.5, and 8.0. At the close of discovery in the Delaware Case, Cisco moved for summary judgment of no United States District Court Northern District of California 3 4 indirect infringement of the ’903 patent by either the Expert Advisor or Remote Expert products. 5 To establish indirect infringement, XU had to show Cisco’s customers directly infringed the patent 6 and that Cisco induced this infringement. The court noted that “XU seems to concede that the 7 products have optional functionalities, and that if the end user does not use those features, there is 8 no direct infringement” by those users. XpertUniverse, Inc. v. Cisco Sys., Inc., No. 09-157-RGA, 9 2013 WL 865974, at *2 (D. Del. Mar. 7, 2013). The court concluded there was insufficient 10 evidence that Cisco’s customers had used the infringing features of Expert Advisor and Remote 11 Expert, rejecting the testimony of XU’s expert in the process. Accordingly, the court granted 12 partial summary judgment in Cisco’s favor with respect to indirect infringement. XpertUniverse, 13 Inc. v. Cisco Sys., Inc., No. 09-157-RGA, 2013 WL 867640, at *8, 11 (D. Del. Mar. 8, 2013). 14 Despite this setback, XU proceeded to trial on its direct infringement claims. The jury 15 found, inter alia, that the Expert Advisor and Remote Expert products infringed claim 12 of the 16 ’903 patent. The court upheld this verdict, but refused to grant an injunction because Cisco had 17 stopped including the infringing features in these products. Ultimately, the court entered a 18 judgment of direct infringement of the ’903 patent with respect to the Expert Advisor and Remote 19 Expert products. The judgment also addressed U.S. Patent No. 7,366,709, which is not at issue 20 here. Finally, the District of Delaware entered judgement for Cisco on all other claims, including 21 the indirect infringement claims which were the subject of the summary judgment order. Cisco 22 filed a Notice of Appeal, but subsequently withdrew that appeal. 23 B. Procedural Background in this Case 24 On July 6, 2017, XU initiated the present action, once again alleging infringement of the 25 26 27 There are multiple versions of the UCC products, including Cisco’s Unified Contact Center Enterprise (“UCCE”) and Cisco’s Unified Contact Center Express (“UCCX”). 1 28 CASE NO. 2 17-cv-03848-RS 1 ’903 patent. The Complaint accuses recent versions of Remote Expert, as well as other products 2 that “incorporate Cisco’s Remote Expert products or similar technology (including, but not limited 3 to, Cisco’s Unified Communications and Unified Contact Center product suites).” Compl. ¶ 77. 4 The Complaint describes how version 11 of Remote Expert meets each of the elements of claim 12 5 of the ’903 patent, but does not specify how any other product satisfies the limitations of any of 6 the claims in this patent. On August 30, 2017, Cisco moved to dismiss, inter alia, XU’s claims with respect all 7 8 9 10 United States District Court Northern District of California 11 products other than Remote Expert. Cisco argued XU’s allegations were too vague to put Cisco on notice of the accused products, noting that the Complaint failed to explain how exactly these other products infringed the ’903 patent. XU responded that it had plausibly alleged infringement as to products that incorporate “the Remote Expert [s]olution and [r]elated [t]echnology.” Opp. Mot. to Transfer, Stay, Dismiss, or Strike at 19. XU contended that a plaintiff is “not required to 12 mechanically map every asserted claim element onto every accused product or technology”; rather 13 14 it is sufficient to indicate that the “general class of other application” is similar to the named product. Id. at 20 (quoting Novitaz, Inc. v. inMarket Media, LLC, No. 16-cv-06795-EJD, 2017 WL 15 2311407, at *4 (N.D. Cal. May 26, 2017)). In XU’s view, it met this standard by laying out the 16 “alleging infringement of Claim 12 by Remote Expert.” Id. On October 11, 2017, Cisco’s request 17 to dismiss all products other than Remote Expert was denied.2 The order stated in pertinent part: 18 In the context-specific task of reviewing a complaint for plausibility, a formal charting of patent claim elements against each accused product is not always necessary. Although XpertUniverse does challenge a broad range of products, it limits the scope to products that incorporate Remote Expert, a product for which it has mapped the claim elements of the ’903 patent. XpertUniverse has met its burden of alleging infringement with respect to the products listed in its complaint. 19 20 21 22 23 Order on Mot. to Transfer, Stay, Dismiss, or Strike 10. (quotation omitted). 24 In November 2017, XU served infringement contentions accusing Remote Expert versions 25 26 27 Cisco’s motion to dismiss was granted with respect to XU’s willful infringement claims. XU subsequently filed a First Amended Complaint, setting forth additional allegations concerning Cisco’s willful infringement of the ’903 Patent, which Cisco answered. 2 28 CASE NO. 3 17-cv-03848-RS 1 1.9 through 11, as well as UCCE and UCCX versions 10 and 11, of infringing claim 12 of the 2 ’903 patent. These contentions allege UCCE and UCCX independently infringe the ’903 patent. In 3 other words, XU accuses these products based on features other than the Remote Expert software. 4 These infringement contentions include 13 appendices, labeled Appx A-1 through G-2, which map 5 how each version of the accused products infringes claim 12. United States District Court Northern District of California 6 In February 2018, Cisco filed a motion for judgment on the pleadings and XU filed a 7 motion for partial summary judgment to preclude Cisco from challenging the validity of claim 12 8 of the ’903 patent. The motion for judgment on the pleadings was denied, however XU’s motion 9 for partial summary judgment was granted. Then, in July, the action was stayed pending the 10 United States Patent and Trademark Office’s reexamination of the ’903 patent. On May 30, 2019, 11 the stay was lifted. Shortly thereafter, Cisco renewed the present motion to strike, which had been 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 denied without prejudice in light of the stay. III. LEGAL STANDARD Rule 12(f) permits a court to strike “any redundant, immaterial, impertinent, or scandalous matter” from a pleading. Motions to strike are also used to bar a party from asserting infringement where either claim preclusion or issue preclusion applies. See Finjan, Inc. v. Blue Coat Sys. LLC, 230 F. Supp. 3d 1097, 1102-04 (N.D. Cal. 2017). The purpose of a motion to strike is “to avoid the expenditure of time and money that must arise from litigating spurious issues by dispensing with those issues prior to trial.” Whittlestone, Inc. v. Handi-Craft Co., 618 F.3d 970, 973 (9th Cir. 2010) (quotation omitted). Motions to strike are generally disfavored “because of the limited importance of pleadings in federal practice and because they are often used solely to delay proceedings.” Capella Photonics, Inc. v. Cisco Sys., Inc., 77 F.Supp.3d 850, 858 (N.D. Cal. 2014) (quotation omitted). Furthermore, “any doubt concerning the import of the allegations to be stricken weighs in favor of denying the motion to strike.” Park v. Welch Foods, Inc., No. 12-cv06449, 2014 WL 1231035, at *1-2 (N.D. Cal. Mar. 20, 2014). IV. DISCUSSION Cisco advances three arguments in support of its motion to strike Appendices F1, F2, G1, 28 CASE NO. 4 17-cv-03848-RS United States District Court Northern District of California 1 and G2 to XU’s infringement contentions. First, Cisco contends XU should be judicially estopped 2 from arguing the UCC products independently infringe the ’903 patent because this position is 3 inconsistent with the position XU took in its opposition to the motion to dismiss. Second, Cisco 4 argues issue preclusion bars XU from litigating whether the UCC products infringe the ’903 patent 5 because the court in the Delaware Case already determined through its summary judgment order 6 that they do not. Third, the Kessler doctrine purportedly bars XU from alleging the UCC products 7 infringe the patent based on that same summary judgment order. 8 A. Judicial Estoppel 9 Judicial estoppel is an equitable doctrine that “prevents a litigant from ‘perverting’ the 10 judicial process by, after urging and prevailing on a particular position in one litigation, urging a 11 contrary position in a subsequent proceeding—or at a later phase of the same proceeding—against 12 one who relied on the earlier position.” SanDisk Corp. v. Memorex Products, Inc., 415 F.3d 1278, 13 1290 (Fed. Cir. 2005). Courts typically consider three factors when deciding whether to apply 14 judicial estoppel, specifically whether: (1) the later position is clearly inconsistent with the earlier 15 position; (2) the party succeeded in persuading a court to accept the earlier position; and (3) the 16 party seeking to assert the inconsistent position would derive an unfair advantage if not estopped. 17 See Zedner v. United States, 547 U.S. 489, 504 (2006); see also United States v. Liquidators of 18 European Fed. Credit Bank, 630 F.3d 1139, 1148-49 (9th Cir. 2011). Courts also consider 19 whether the party who is asserting inconsistent positions did so intentionally. Samson v. NAMA 20 Holdings, LLC, 637 F.3d 915, 935 (9th Cir. 2011). 21 Cisco’s argument in favor of judicial estoppel is unpersuasive. XU’s assertion that the 22 UCC products independently infringe the ’903 patent is not “clearly inconsistent” with the 23 position it took in opposition to Cisco’s motion to dismiss. Indeed, XU argued in opposition to the 24 motion to dismiss that it had plausibly alleged infringement of products that incorporate “the 25 Remote Expert [s]olution and [r]elated [t]echnology.” Opp. Mot. to Transfer, Stay, Dismiss, or 26 Strike at 19. XU went on to argue that, at the pleading stage, a plaintiff can identify a general class 27 of unnamed applications as long as the products in the class are similar to a product named in the 28 CASE NO. 5 17-cv-03848-RS United States District Court Northern District of California 1 complaint. XU believed it had satisfied this standard by “alleging infringement of Claim 12 by 2 Remote Expert and other named products incorporating Remote Expert.” Id. 20. At no point did 3 XU state that it intended to limit the accused products to those that incorporated Remote Expert. 4 Furthermore, XU specifically named the UCC product suit in the Complaint, therefore Cisco was 5 on notice that these specific products were at issue. In sum, XU’s current position that the UCC 6 products infringe the ’903 patent regardless of whether they incorporate Remote Expert is not 7 “manifestly inconsistent” with its prior position. Wyler Summit Partnership v. Turner 8 Broadcasting Sys., Inc., 235 F.3d 1184, 1190 (9th Cir. 2000). Accordingly, the doctrine of judicial 9 doctrine does not apply. 10 B. Issue Preclusion 11 The doctrine of issue preclusion bars successive litigation “of an issue of fact or law 12 actually litigated and resolved in a valid court determination essential to the prior judgment.” 13 Garity v. APWU Nat'l Labor Org., 828 F.3d 848, 858 n.9 (9th Cir. 2016) (quotation omitted); see 14 also In re Reynoso, 477 F.3d 1117, 1122 (9th Cir. 2007). In the Ninth Circuit, a party seeking to 15 establish issue preclusion must show that (1) the issue decided in the prior proceeding is 16 “identical” to the one sought to be relitigated; (2) the prior proceeding resulted in a final judgment 17 on the merits; and (3) the party against whom issue preclusion is asserted was a party to—or in 18 privity with a party to—the first proceeding. Roche Palo Alto LLC v. Apotex, Inc., 526 F. Supp. 2d 19 985, 994 (N.D. Cal. 2007) (citing Reyn’s Pasta Bella, LLC v. Visa USA, Inc., 442 F.3d 741, 746 20 (9th Cir. 2006)). 21 The primary dispute regarding issue preclusion relates to whether the first requirement is 22 satisfied. In analyzing this element, courts must first consider whether the issue in question was 23 “actually litigated” and decided. Reyn’s Pasta Bella, 442 F.3d at 746 & n.6. Issue preclusion 24 generally does not attach to an issue that was uncontested in the prior litigation unless it is clear 25 the parties intended the issue be foreclosed in subsequent litigation. See United States v. Real 26 Prop. Located at 22 Santa Barbara Drive, 264 F.3d 860, 873 (9th Cir. 2001) (quotation omitted) 27 (“A stipulation may meet the fully litigated requirement where it is clear that the parties intended 28 CASE NO. 6 17-cv-03848-RS United States District Court Northern District of California 1 the stipulation of settlement and judgment entered thereon to adjudicate once and for all the issues 2 raised in that action.”); see also United States v. Young, 804 F.2d 116, 118 (8th Cir. 1986). Courts 3 also consider whether the relevant features of the accused product are the same as those of the 4 product at issue in the earlier case. See, e.g., EON Corp IP Holdings LLC v. Apple Inc., No. 14- 5 CV-05511-WHO, 2015 WL 4914984, at *6 (N.D. Cal. Aug. 17, 2015); see also Phil-Insul Corp. 6 v. Airlite Plastics Co., 854 F.3d 1344, 1353 (Fed. Cir. 2017) (explaining that the accused products 7 must be “essentially the same” for issue preclusion to apply). 8 According to Cisco, the question whether the UCC products infringe claim 12 of the ’903 9 patent was “necessarily decided” in the summary judgment order issued in the Delaware Case. In 10 that order, the District of Delaware noted that “XU seems to concede that the products have 11 optional functionalities, and that if the end user does not use those features, there is no direct 12 infringement” by those users. XpertUniverse, 2013 WL 865974, at *2. Cisco construes this to 13 mean that the UCC products, without the optional Expert Advisor and Remote Expert features 14 discussed in that order, do not infringe the ’903 patent. When read in context, however, it becomes 15 clear the “products” referred to in that order are Expert Advisor and Remote Expert, not the UCC 16 products. In other words, the court was explaining that use of Expert Advisor and Remote Expert 17 does not result in infringement of the ’903 patent unless certain optional features of those products 18 were activated. The summary judgment order does not make any explicit findings regarding the 19 UCC products. Indeed, the order makes no mention of these products. This is unsurprising given 20 that the UCC products were not named in either the operative complaint or in XU’s infringement 21 contentions in that case. Cisco argues that, even though the UCC products were not named in XU’s pleading or 22 23 infringement contentions, or in the court’s summary judgment order, they were still “at issue” in 24 that case. First, XU’s expert stated that Expert Advisor was “part of . . . UCCE.” Ginnings Decl., 25 Ex. 15 at 1061:24-1062:1.3 Furthermore, XU characterizes Expert Advisor as “part of a larger 26 27 3 The relevant Ginnings Declaration can be found at Docket 114. 28 CASE NO. 7 17-cv-03848-RS 1 product suite” of products which includes the UCC products. Opp. Mot. Strike 22-23. Finally, 2 Cisco notes that, in the Delaware Case, XU moved to compel sales data regarding UCC products 3 that contained Expert Advisor software. Therefore, Cisco argues, the UCC products “were at 4 issue” in that case and were “an integral part of the functionality XU accused of infringement.” 5 Mot. Strike 12. United States District Court Northern District of California 6 This argument is unpersuasive. Although it is undisputed that Expert Advisor was included 7 in some UCC products at the time of the Delaware Case, there is no indication that either the 8 parties or the court intended to adjudicate whether the UCC products independently infringed the 9 ’903 patent. In other words, the UCC products were at issue only to the extent they incorporated 10 the challenged Expert Advisor technology. The question whether the UCC products independently 11 infringe the ’903 patent was not “actually litigated” or “necessarily decided” in the Delaware 12 Case, therefore issue preclusion does not apply. 13 C. Kessler Doctrine 14 The Kessler Doctrine is a doctrine that “fills the gap between [the claim and issue] 15 preclusion doctrines [], allowing an adjudged non-infringer to avoid repeated harassment for 16 continuing its business as usual post-final judgment in a patent action where circumstances justify 17 that result.” Brain Life, LLC v. Elekta Inc., 746 F.3d 1045, 1056 (Fed. Cir. 2014). When a 18 defendant succeeds in establishing non-infringement, “the specific accused device(s) acquires the 19 status of a non[-]infringing device vis-à-vis the asserted patent claims.” Brain Life, 746 F.3d at 20 1057 (quotation omitted). Similarly, new products that are “essentially the same” as the product in 21 the prior suit acquires the status of a non-infringing device. Id. 22 As explained in the issue preclusion section, Part IV.B, supra, the UCC products were 23 neither named in the operative complaint nor in XU’s infringement contentions. Rather, the sole 24 relevance of these products was that they were capable of incorporating the challenged Expert 25 Advisor software—which was the focus of that litigation. Furthermore, the summary judgment 26 order in that case made no reference to the UCC products; rather it held that XU’s indirect 27 infringement claims regarding Expert Advisor (and other products not at issue in this action) failed 28 CASE NO. 8 17-cv-03848-RS United States District Court Northern District of California 1 as a matter of law because XU could not show Cisco customers actually used the infringing 2 features of those products. This holding did not address whether the UCC products independently 3 infringe the ’903 patent. Given these facts, the issuance of a final judgment in Cisco’s favor with 4 respect to XU’s indirect infringement claims did not confer non-infringing status on the UCC 5 products. Accordingly, the Kessler Doctrine does not apply. 6 D. Motion to Seal 7 On June 14, 2018, Cisco requested leave to file Exhibit 25 to the Declaration of C. Austin 8 Ginnings in support of Cisco’s Motion to Strike Appendices F1, F2, G1, and G2 under seal. 9 Although Cisco does not contend this exhibit includes any confidential or proprietary information, 10 XU had previously designated this exhibit as “HIGHLY CONFIDENTIAL – ATTORNEYS’ 11 EYES ONLY” pursuant to the terms of the Protective Order entered in this case. XU did not, 12 however, file the requisite declaration to support this motion under Civil Local Rule 79-5(e). The 13 motion to seal Exhibit 25 to the Ginnings declaration is therefore denied. V. CONCLUSION 14 15 For the reasons set forth above, the motion to strike is denied. 16 17 18 IT IS SO ORDERED. 19 20 21 22 Dated: July 29, 2019 ______________________________________ RICHARD SEEBORG United States District Judge 23 24 25 26 27 28 CASE NO. 9 17-cv-03848-RS
]]>
Some case metadata and case summaries were written with the help of AI, which can produce inaccuracies. You
should read the full case before relying on it for legal research purposes.
This site is protected by reCAPTCHA and the Google
Privacy Policy and
Terms of Service apply.
