Elawyers Elawyers
Washington| Change

Hewlett Packard Company v. ServiceNow, Inc., 14-cv-00570-BLF (HRL). (2016)

Court: District Court, N.D. California Number: infdco20160222755 Visitors: 7
Filed: Feb. 19, 2016
Latest Update: Feb. 19, 2016
Summary: ORDER DENYING MOTION FOR LEAVE TO AMEND INVALIDITY CONTENTIONS Re: Dkt. No. 150 HOWARD R. LLOYD , Magistrate Judge . Hewlett Packard Enterprise Company ("HP") sues ServiceNow, Inc. ("ServiceNow") for patent infringement. ServiceNow argued in a claim-construction brief that certain limitations related to U.S. Patent Numbers 7,925,981 ("'981") and 7,945,860 ("'860") are fatally indefinite "means-plus-functions" limitations under 35 U.S.C. 112—they define functions by reference to certain s
More

ORDER DENYING MOTION FOR LEAVE TO AMEND INVALIDITY CONTENTIONS

Re: Dkt. No. 150

Hewlett Packard Enterprise Company ("HP") sues ServiceNow, Inc. ("ServiceNow") for patent infringement. ServiceNow argued in a claim-construction brief that certain limitations related to U.S. Patent Numbers 7,925,981 ("'981") and 7,945,860 ("'860") are fatally indefinite "means-plus-functions" limitations under 35 U.S.C. § 112—they define functions by reference to certain structures, as permitted by § 112(f), but those referenced structures are not, as required by § 112(b), actually defined anywhere else. HP replied that ServiceNow's invalidity contentions did not include any § 112(f) arguments with respect to those two patents and therefore ServiceNow had failed to timely preserve those arguments in the manner required by Patent Local Rule 3-3. During a technology tutorial, District Judge Beth L. Freeman asked ServiceNow's counsel to comment on HP's procedural argument; counsel promptly conceded that ServiceNow needs to amend its defective invalidity contentions and that ServiceNow should have more promptly moved for leave to do so. Judge Freeman advised counsel to move for leave to amend.

ServiceNow has instead moved the court for a ruling that the invalidity contentions do not need to be amended because those contentions already duly raised § 112(f) arguments against the '981 and '860 patents. Counsel explains she was not prepared to discuss HP's procedural argument during the tech tutorial and that her concessions at the tutorial were, in retrospect, wrong; ServiceNow asks for leave to amend only in the alternative. HP argues in opposition: (1) ServiceNow plainly understands its own invalidity contentions are insufficient, even if ServiceNow has changed its official stance on that issue; (2) ServiceNow's invalidity contentions fail to raise § 112(f) arguments against the '981 and '860 claims in the manner required by Patent Local Rule 3-3; and (3) the court should not grant leave to amend because ServiceNow had no good reason to wait nearly a year to seek leave to cure its defective contentions.

Discussion

This district's Patent Local Rules require parties to promptly disclose their infringement and invalidity contentions and to adhere to those contentions unless good cause arises to justify amendment. See, e.g., Avago Technologies General IP PTE LTD. v. Elan Microelectronics Corp., 04-cv-5385-JW-HRL, 2007 WL 951818 at * 1 (N.D. Cal. March 28, 2007) (collecting cases). This district adopted these rules to prevent vexatious "shifting sands" claim-construction strategies and, accordingly, this court is "conservative" in granting leave to amend infringement or invalidity contentions. Atmel Corp. v. Information Storage Devices, Inc., No. 95-cv-1987-FMS, 1998 WL 775115 at *2 (N.D. Cal. Nov. 5, 1998). When a litigant contends that 35 U.S.C. § 112(f) governs a limitation in a patent claim, Patent Local Rule 3-3(c) requires that the invalidity contentions include "[a] chart" that identifies, for each prior art reference, which structures "perform[] the claimed function[.]" Invalidity contentions must also include "[a]ny grounds of invalidity based on" 35 U.S.C. § 112(b). Pat. L.R. 3-3(d).

The parties' briefs present a threshold question: do ServiceNow's invalidity contentions duly preserve § 112(f) theories? If ServiceNow's contentions comply with Patent Local Rule 3-3's requirements, then ServiceNow has preserved its § 112(f) arguments; otherwise, the court shall determine whether to grant leave to amend the defective invalidity contentions.

The court is not persuaded by HP's argument that ServiceNow's own counsel seems to subjectively understand the inadequacy of her client's invalidity contentions. Certainly counsel's concessions during the tech tutorial give the court good reason to carefully scrutinize ServiceNow's motion, but the court does not view those retracted concessions as dispositive. Rather, the court shall directly compare the requirements in Patent Local Rule 3-3 with the invalidity contentions at issue.

ServiceNow's invalidity contentions, to the extent required by Patent Local Rule 3-3(d), fairly identify § 112(f) arguments as the "grounds" for § 112(b) arguments against the '981 and '860 patents. HP asserts that any such argument must follow a general form: "identify the term that is allegedly governed by § 112[(f)], and explain that there is no structure disclosed for performing the claimed function[.]" Dkt. No. 151 at 11. ServiceNow argues it has complied with HP's proposed reading of Patent Local Rule 3-3(d) by asserting, for certain terms, that "no structure was disclosed." The undersigned agrees that ServiceNow's invalidity contentions fairly assert, with respect to the '981 and '860 patents, that certain claimed functions lack any defined underlying structure. For example, as to claim 1 of the '981 patent, ServiceNow contends certain claim terms "[are] indefinite because [they] improperly claim[] the function of the alleged invention without any structural limitations." Dkt. No. 150 at 3. ServiceNow uses similar language to contend that claim 1 of the '860 patent is invalid for claiming a function that lacks "any structural limitations." Dkt. No. 150 at 4. This language, notwithstanding the lack of explicit statutory citations, fairly contends that certain § 112(f) claims are indefinite under § 112(b) because HP failed to disclose the structures underlying claimed functions.

The court rejects HP's argument that Patent Local Rule 3-3(c) requires invalidity contentions to include an explicit invocation of § 112(f). HP relies upon a decision in which the Southern District of California applied a textually identical local rule to conclude that defendants waive § 112(f) arguments when they fail to "identify . . . terms as means-plus-function elements in their preliminary invalidity contentions[.]" I-Flow Corporation v. Apex Medical Technologies, Inc., 07-cv-1200, 2008 WL 2899822 at *5 (S.D. Cal. July 25, 2008). The undersigned is not persuaded by that decision, which cites to the Southern District's analogous local rule but does not analyze the text of the rule or otherwise support its conclusion on this issue. The undersigned does not read this district's Patent Local Rule 3-3(c) to require the use of any particular citation, phrase, or keyword before a defendant may maintain an argument under § 112(f). HP did not cite, and the undersigned has not found, a case in which this court has read into Patent Local Rule 3-3(c) the formalistic requirement that invalidity contentions must explicitly cite § 112(f) or use any specific phrase like "means-plus-function elements." Rather, subsection (c) requires invalidity contentions to include a chart that provides certain information about "each asserted claim" and then, additionally, "for each limitation that such party contends is governed by 35 U.S.C. § 112([f])," the chart shall also "identify . . . the structure[s] . . . in each item of prior art . . . that perform[] the claimed function[.]" The undersigned reads this language to mean that § 112(f) invalidity contentions must be accompanied by a chart which "identif[ies] . . . the structure[s] . . . in each item of prior art . . . that perform[] the claimed function[s]" at issue in the § 112(f) contentions. The undersigned does not read this language to circumscribe how § 112(f) contentions may be fairly raised in the first place.

The court turns to HP's final argument under Patent Local Rule 3-3: ServiceNow's "prior art charts" failed to identify the structures that, under subsection (c), must be identified as part of any § 112(f) contentions against the '981 and '860 patents. Dkt. No. 151 at 14. ServiceNow, in reply, does not actually contend it complied with the requirements of Patent Local Rule 3-3(c), but instead argues subsection (c) is not "relevant" to the question of whether a "separate indefiniteness challenge[]" has been adequately "identified under" subsection (d). Dkt. No. 152 at 4. ServiceNow misreads how the different subsections of Patent Local Rule 3-3 relate to each other. Each subsection describes "information" that complete invalidity contentions "shall contain[.]" Pat. L.R. 3-3. Subsection (d) requires ServiceNow to disclose the grounds for indefiniteness theories, and ServiceNow did adequately disclose those grounds here—the contentions that certain claims lack "any" of the "structural limitations" required by § 112(f). Dkt. No. 150 at 3-4. But subsection (c) requires that § 112(f) contentions be accompanied by a prior art chart that identifies which structures in the prior art items perform the claimed functions; this co-extensive requirement applies regardless of whether the § 112(f) contentions helped to satisfy subsection (d)'s requirements.

ServiceNow's invalidity contentions do not include a prior-art chart that "identif[ies] . . . the structure[s] . . . in each item of prior art . . . that perform[] the claimed function[s]" at issue in ServiceNow's § 112(f) contentions against the '981 and '860 patents. Dkt. No. 150-2 at 7-8. ServiceNow's defective invalidity contentions therefore failed to preserve § 112(f) arguments against the '981 and '860 patents in the manner required by Patent Local Rule 3-3(c). The court turns to the issue of whether good cause exists to grant leave to amend the defective invalidity contentions.

Patent Local Rule 3-6 permits parties to amend patent contentions only "by order of the Court upon a timely showing of good cause." The good-cause inquiry depends on whether the movant diligently discovered the information that might justify amending the contentions and then promptly moved for leave to amend. E.g., Apple Inc. v. Samsung Elecs. Co., 12-cv-630-LHK-PSG, 2012 WL 5632618 at *2 (N.D. Cal. Nov. 15, 2012). The movant has the burden to show diligence. Id. at *6. A movant may show good cause to amend an unpreserved defense into its contentions by promptly moving for leave to amend on the basis of new case law that "ma[d]e available a defense that was previously unavailable." Horus Vision, LLC v. Applied Ballistics, LLC, No. 13-cv-5460-BLF-HRL, 2014 WL 6895572 at *2 (N.D. Cal. Dec. 5, 2014). This court often rules the movant has not been diligent and good cause has not been shown if the motion relies on information that was discovered several months before the motion was filed. E.g., id. If the movant was not diligent then "there is no need to consider the question of prejudice" and the court may deny the motion for leave to amend without any further analysis, e.g., Apple Inc., supra, but the court may, in its discretion, subsequently consider whether the non-movant would suffer prejudice, Brandywine Commc'ns Techs., LLC v. AT&T Corp., 12-cv-2494-CW, 2014 WL 1569544 at *15 (N.D. Cal. Apr. 18, 2014) (citing Apple Inc., supra).

ServiceNow argues it has been diligent because: (1) intervening case law—Williamson v. Citrix Online, LLC, 792 F.3d 1339 (Fed. Cir. 2015) and Media Rights Techs. v. Capital One Fin. Corp., 800 F.3d 1366 (Fed. Cir. 2015)—gave ServiceNow "further confidence that its claim construction arguments were supportable and correct" and therefore, notwithstanding cases like Horus Vision, intervening cases have provided good cause to amend the § 112(f) contentions; (2) ServiceNow amended its proposed claim constructions a few weeks after the Federal Circuit issued Media Rights; and (3) "uncertainty as a result of motions to stay and settlement negotiations" justified waiting for several months before ServiceNow moved for leave to amend. Dkt. No. 150 at 8-9. HP responds ServiceNow has not been diligent because: (1) Williamson altered the strength of a presumption that applies to § 112(f) defenses and Media Rights applied Williamson to determine whether a district court had properly resolved a § 112(f) defenses, but neither Williamson nor Media Rights provided ServiceNow with a new defense that had not previously been available at the outset of this case; (2) even if Williamson and Media Rights are taken as changes in the law that might justify leave to amend, ServiceNow has provided no colorable explanation for waiting six months after Williamson issued or three months after Media Rights issued to file its motion; and (3) ServiceNow's own motion for a stay and the possibility of settlement did not justify ServiceNow in waiting for several months to file a motion for leave to amend. Dkt. No. 151 at 15-18.

The court agrees with HP that ServiceNow has not been diligent. Where a party seeks leave to amend a "defense" into the case that was not duly preserved in the party's initial contentions, ordinarily the party "must" justify the amendment by showing that intervening case law provided the "previously . . . unavailable" defense. Horus Vision, supra. Williamson elaborated on how courts should resolve a presumption that applies to § 112(f) arguments, 792 F.3d at 1349, and Media Rights relied upon Williamson to review a judgment granted on the pleadings, 800 F.3d at 1372-73, but neither case provided a new defense that had previously been unavailable to ServiceNow. Rather, ServiceNow's § 112(f) arguments were available at the outset of this case and ServiceNow's invalidity contentions failed to preserve those arguments against the '981 and '860 patents in the manner required by Patent Local Rule 3-3(c). The court considers it particularly clear that Media Rights, which merely applied Williamson, did not change the law in any way that might justify a motion for leave to amend. See id.

Even if the court accepts for the sake of argument that Williamson changed the law enough to justify a prompt motion for leave to amend, ServiceNow has still failed to provide a satisfactory explanation for why it waited six months to file its motion—the Federal Circuit issued Williamson on June 16 and ServiceNow moved for leave to amend on December 18. The court rejects the argument that pending settlement talks and a pending motion for a stay justified a six-month delay in filing ServiceNow's motion. The looming possibility that the case might ultimately settle does not excuse a party's failure to comply with an imminent procedural requirement. The court also agrees with HP's response: ServiceNow fails to explain why, if ServiceNow was simply waiting for these issues to be resolved, ServiceNow waited to move for leave to amend until more than two months after Judge Freeman ruled on the motion for a stay and one month after settlement negotiations concluded. Dkt. No. 151 at 18; see also Dkt. No. 132.

Moreover, the undersigned believes the proper question in this case is whether ServiceNow diligently discovered that it had filed defective invalidity contentions in January of 2015 and promptly filed a motion for leave to cure the defect. Horus Vision, supra, strongly suggests that a party simply cannot show diligence under these circumstances—the § 112(f) arguments were available to ServiceNow when it filed its initial invalidity contentions and ServiceNow's failure to initially preserve those arguments reflects a lack of due diligence. Even setting aside Horus Vision, ServiceNow did not realize its contentions might be defective until nearly one year later, and even then the realization was not due to ServiceNow's own diligence. Rather, HP discovered and raised the issue of defective invalidity contentions when HP's counsel were surprised to see § 112(f) claim-construction arguments ServiceNow had not properly preserved. ServiceNow has therefore failed to carry its burden to show diligence. The information before the court tends to show, instead, that for one year ServiceNow was not diligent in discovering and seeking leave to amend the defects in its invalidity contentions.

In light of both ServiceNow's substantial lack of diligence and this district's firm policy against permitting parties to "shift[]" the "sands" opponents stand upon in the midst of an ongoing claim-construction battle, the court finds a lack of good cause and denies ServiceNow's motion for leave to amend the invalidity contentions. The court declines to consider prejudice. Brandywine, supra.

Conclusion

ServiceNow's invalidity contentions failed to preserve § 112(f) arguments against HP's claims under the '981 and '860 patents because the contentions did not include a chart that identifies which structures in the prior-art references perform the claimed functions. For one year ServiceNow showed a lack of diligence in discovering and seeking leave to cure the defects in the § 112(f) contentions. ServiceNow has failed to show intervening case law, or a pending motion for a stay, or pending settlement talks could justify ServiceNow's lack of diligence. Even if the court assumes that ServiceNow's justifications could show good cause under the right circumstances, ServiceNow nevertheless failed to diligently and promptly move for leave to amend after the intervening cases issued, after the court resolved the pending motion, or after the settlement talks concluded. The motion for leave to amend is therefore denied for lack of diligence.

IT IS SO ORDERED.

Source:  Leagle

Can't find what you're looking for?

Post a free question on our public forum.
Ask a Question
Search for lawyers by practice areas.
Find a Lawyer