Straight Path IP Group, Inc. v. Cisco Systems, Inc.

CourtDistrict Court, N.D. California
DecidedMay 19, 2020
Docket3:16-cv-03463
StatusUnknown

This text of Straight Path IP Group, Inc. v. Cisco Systems, Inc. (Straight Path IP Group, Inc. v. Cisco Systems, Inc.) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Straight Path IP Group, Inc. v. Cisco Systems, Inc., (N.D. Cal. 2020).

Opinion

1 2 3 4 5 6 UNITED STATES DISTRICT COURT 7 NORTHERN DISTRICT OF CALIFORNIA 8

10 STRAIGHT PATH IP GROUP, INC., No. C 16-03463 WHA 11 Plaintiff, No. C 16-03582 WHA 12 v.

13 CISCO SYSTEMS, INC.,

14 Defendant. ORDER ADOPTING SPECIAL MASTER’S REPORT AND

15 R AE TC TOO RM NM EE YN ’SD FA ET EIO S N FOR STRAIGHT PATH IP GROUP, INC., 16 Plaintiff, 17 v. 18 APPLE INC., 19 Defendant. 20 21 INTRODUCTION 22 This post-merits patent suit has devolved into a protracted fee dispute — “one of the least 23 socially productive types of litigation imaginable,” as Justice William Brennan put it. Hensley 24 v. Eckerhart, 461 U.S. 424, 442 (1983) (dissenting). Prior orders found patent owner’s 25 exceptional infringement theory entitled defendants to fees and appointed a special master who 26 reviewed billing records, heard arguments, and now recommends an award. This order 27 ADOPTS that reasoned recommendation and finally puts this suit to bed. 1 STATEMENT 2 A prior order details the facts of this suit. Straight Path IP Group, Inc. v. Cisco Systems, 3 411 F. Supp. 3d 1026 (N.D. Cal. 2019). Among others, patent owner asserted four patents 4 against Apple and Cisco, United States Patent Nos. 6,009,469 (“the ’469 patent”), 6,108,704 5 (“the ’704 patent”), 6,131,121 (“the ’121 patent”), and 6,701,365 (“the ’365 patent”). The 6 patents described point-to-point Internet communication, including: “(1) a first computer 7 program to query a connection server to determine if a second computer program is currently 8 connected to the network, and (2) if the second computer program is connected, to obtain its 9 existing network address so that the desired point-to-point communication can be established at 10 the time it is sought.” Id. at 1028. 11 Patent owner initially sued in 2014, but voluntarily dismissed when third parties 12 challenged the patents in inter partes review at the United States Patent Office. The review 13 focused on the construction of the “is currently connected” aspect of the patents, embodied in 14 the claims as the term “is connected.” Using the broadest reasonable interpretation of the term, 15 the Patent Trial and Appeal Board (PTAB) invalidated all relevant claims as anticipated or 16 obvious. But the Federal Circuit reversed, agreeing the PTAB had too broadly construed “is 17 connected” and adopting patent owner’s narrow interpretation. Id. at 1028–30 (citing Straight 18 Path IP Grp., Inc. v. Sipnet EU S.R.O., 806 F.3d 1356, 1363 (Fed. Cir. 2015)). 19 On remand in May 2016, the PTAB upheld the claims’ validity, employing patent 20 owner’s construction of “is connected.” In June 2017, the Federal Circuit affirmed, again 21 agreeing with patent owner’s narrow construction. Id. at 1030; Samsung Elecs. Co. v. Straight 22 Path IP Grp., Inc., 696 F. App’x 1008 (Fed. Cir. 2017). 23 But back in June 2016, armed with the PTAB’s favorable finding, patent owner resumed 24 its assertion against Apple and Cisco, filing these suits. In October 2017, both defendants 25 moved for summary judgment, and a November 2017 order found patent owner’s narrow 26 construction of “is connected” before the Federal Circuit precluded its broad infringement 27 theory here. It bears restating. After maintaining the claims’ validity by arguing twice to the 1 sued Apple and Cisco on a contrary broad interpretation. Indeed, during the prosecution of 2 this suit on the broad interpretation, patent owner advanced its narrow interpretation to the 3 Federal Circuit for the second time. So, the November 2017 order also directed patent owner 4 to show cause why it should not be liable for attorney’s fees under 35 U.S.C. § 285. 411 F. 5 Supp. 3d at 1030. 6 Following patent owner’s unsuccessful appeal, Apple and Cisco moved for fees. A 7 November 2019 order reaffirmed the exceptionality of patent owner’s prosecution of this case 8 under § 285. But finding defendants’ fee requests too high and likely including activity not 9 sufficiently related to patent owner’s exceptional prosecution of the “is connected” claims, the 10 order directed the parties to submit their billing requests to a special master on December 5. 11 The order cautioned defendants to “take care to submit only for time and expenses that truly 12 deserve compensation and at billing rates that truly deserve to be compensated,” stating that 13 the Court might treble the deductions for requests the special master found unreasonable. Id. at 14 1035. 15 A companion order directed Apple and Cisco to:

16 [P]rovide the special master a detailed declaration, organized by discrete projects, breaking down all attorney and paralegal time 17 sought to be recovered. For each project, there must be a detailed description of the work, giving the date, hours expended, attorney 18 name, and task for each work entry, in chronological order. A “project” means a deposition, a motion, a witness interview, and so 19 forth. It does not mean generalized statements like “trial preparation” or “attended trial.” It includes discrete items like 20 “prepare supplemental trial brief on issue X.” 21 It then directed that “[a]ll entries for a given project must be presented chronologically one 22 after the other, i.e., uninterrupted by other projects, so that the timeline for each project can be 23 readily grasped.” It also requested justification of each timekeeper’s billing rate, a summary 24 chart of that timekeeper’s activities, and proof of billing judgment. Last, the order directed the 25 special master to “identify each item requested that bears little or no relation to the conduct 26 found exceptional herein. For example, all work on [U.S. Patent No. 7,149,208 (“the ’208 27 patent”)] had no connection to the about-face representations at summary judgment made by 1 On December 16, the special master held an initial hearing with the parties. After 2 briefing, he held a hearing on threshold legal issues on February 5 and issued a preliminary 3 report on February 10. Following February 27 and March 3 hearings, the special master 4 recommended an award of $2,334,054 to Apple and $1,920,146 to Cisco (Report & 5 Recommendation of special master (“Rpt.”), Dkt. No. 232). Apple would receive nearly all it 6 asked for, with minor deductions taken for certain ambiguous or duplicative time entries. 7 But Cisco would receive only half because its billing records never conformed to the 8 Court’s direction. The special master explained that Cisco did not pay counsel by the hour, 9 rather it paid a flat-monthly fee. The special master found Cisco’s original billing submission 10 deficient and asked Cisco to resubmit. Cisco did so, but the special master found the records 11 remained deficient for an ordinary lodestar review. To be sure, the special master found this 12 alternative billing method compensable under § 285, but the records did not paint a clear 13 picture of counsel’s billable activities or clearly delineate between this case and other, non- 14 compensable work for Cisco. Thus, the special master concluded a 50% reduction would 15 ensure patent owner did not overpay, yet still compensate Cisco for fees actually paid. Finally, 16 the special master declined to treble the deduction, finding Cisco’s noncompliance a product of 17 the alternate billing arrangement and not of bad faith. 18 Patent owner objects that the special master’s awards of fees are too high. Apple and 19 Cisco urge this Court to adopt the special master’s recommendation. This order follows patent 20 owner’s objections, defendants’ responses, and a hearing conducted telephonically due to the 21 COVID-19 pandemic. 22 ANALYSIS 23 1. SCOPE OF REVIEW.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Hensley v. Eckerhart
461 U.S. 424 (Supreme Court, 1983)
City of Burlington v. Dague
505 U.S. 557 (Supreme Court, 1992)
Microsoft Corp. v. i4i Ltd. Partnership
131 S. Ct. 2238 (Supreme Court, 2011)
Straight Path Ip Group, Inc. v. Sipnet Eu S.R.O.
806 F.3d 1356 (Federal Circuit, 2015)
Samsung Electronics Co., Ltd. v. Straight Path Ip Group, Inc.
696 F. App'x 1008 (Federal Circuit, 2017)
Perdue v. Kenny A. ex rel. Winn
176 L. Ed. 2d 494 (Supreme Court, 2010)
Mathis v. Spears
857 F.2d 749 (Federal Circuit, 1988)

Cite This Page — Counsel Stack

Bluebook (online)
Straight Path IP Group, Inc. v. Cisco Systems, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/straight-path-ip-group-inc-v-cisco-systems-inc-cand-2020.