Chrimar Systems, Inc. v. Cisco Systems, Inc.

72 F. Supp. 3d 1012, 2014 U.S. Dist. LEXIS 153393, 2014 WL 5477666
CourtDistrict Court, N.D. California
DecidedOctober 29, 2014
DocketNo. C 13-01300 JSW
StatusPublished
Cited by4 cases

This text of 72 F. Supp. 3d 1012 (Chrimar Systems, 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
Chrimar Systems, Inc. v. Cisco Systems, Inc., 72 F. Supp. 3d 1012, 2014 U.S. Dist. LEXIS 153393, 2014 WL 5477666 (N.D. Cal. 2014).

Opinion

ORDER REGARDING MOTION FOR JUDGMENT ON THE PLEADINGS

JEFFREY S. WHITE, UNITED STATES DISTRICT JUDGE

Now before the Court is the motion by Plaintiff ChriMar Systems Inc. d/b/a/ CMS Technologies and ChriMar Holding Company, LLC (collectively, “ChriMar”) for judgment on the pleadings regarding the antitrust counterclaims filed by Defendants Cisco Systems, Inc. and Linksys LLC (together, “Cisco”) and by Defendant Hewlett-Packard Company (“HP”) (collectively, “Defendants”). Having considered the parties’ pleadings and relevant legal authority, the Court hereby grants Chri-Mar’s motion.

BACKGROUND

On October 31, 2011, ChriMar filed this patent infringement action against Defendants, accusing them of infringing United States Patent,No. 7,457,250 (“'250 Patent”). Cisco filed counterclaims on January 6, 2012 and amended its counterclaims on December 26, 2012. HP filed counterclaims on December 26, 2012.

In their counterclaims, Defendants allege that the Institute of Electrical and Electronics Engineers (“IEEE”) is a standard setting organization and that it amended the 802.3 standard with the 802.3af and 802.3 at standards. (Cisco’s First Amended Counterclaims (“FAC”), ¶¶ 19-21; HP’s Counterclaims, ¶¶ 18-20.) The IEEE has a “ ‘patent disclosure policy’ that requires participants in the standards setting process to disclose patents or patent applications they believe to be infringed by the practice of the proposed standard.” (Cisco FAC, ¶ 21; HP Counterclaims, ¶ 21.) The disclosure policy further requires those who disclose intellectual property rights to provide a letter of assurance stating whether they would enforce any of their present or future patents) whose use would be required to implement the proposed IEEE standard or provide a license to applicants without compensation or under reasonable rates, [1016]*1016with reasonable terms and conditions that are demonstrably free of any unfair discrimination (“RAND” terms). (Id.) Defendants allege that ChriMar was required to but failed to disclose to the IEEE its belief that its '250 Patent was essential to the proposed 802.3af and/or the 802.3at amendments to the 802.3 standard and that ChriMar was not willing to license the '250 Patent on RAND terms. (Cisco FAC, ¶ 25; HP Counterclaims, ¶ 24.)

Defendants further allege that “Chri-Mar’s failure to disclose the '250 Patent was done knowingly and with intent to deceive and induce the IEEE and participants in the standards-setting process” for the amendments to the IEEE 802.3af and 802.3at standards. (Cisco FAC, ¶ 31; HP Counterclaims, ¶ 30.) “Due in part to ChriMar’s knowing and intentional deception, the industry adopted the present form of the IEEE 802.3af and IEEE 802.3at amendments to the IEEE 802.3 standard, and is now locked-in to the current implementation ... for Power over Ethernet-enabled products.” (Cisco FAC, ¶ 32; HP Counterclaims, ¶ 31.) According to Defendants, if ChriMar had properly disclosed to the IEEE its belief that the '250 Patent “would be infringed by practicing the 802.3af and 802.3at amendments to the 802.3 standard, and that ChriMar was unwilling to license the patent on RAND terms, the IEEE would have (a) incorporated one or more viable alternative technologies into the IEEE 802.3af and IEEE 802.3at amendments to the IEEE 802.3 standard; (b) required ChriMar to provide a letter of assurance that it would license the '250 Patent on RAND terms; (c) decided to either not adopt any amendment to the IEEE 802.3; and/or (d) adopted an amendment that did not incorporate technology that ChriMar claims is covered by the '250 Patent.” (Cisco FAC, ¶ 36; HP Counterclaims, ¶ 35.)

Defendants allege that ChriMar has taken the position that all Power over Ethernet-enabled products infringe the '250 Patent. To the extent that the '250 Patent is essential to the 802.3af and the 802.3at standards, no viable technology substitutes exist and ChriMar has monopoly power over the Power over Ethernet Technology Market. (Cisco FAC, ¶ 64; HP Counterclaims, ¶ 60.)

Defendants allege that Plaintiffs violated Section 2 of the Sherman Act by abusing monopoly power. HP also brings a claim for attempted monopolization. Defendants both bring claims under California’s Unfair Competition Law, California Business Code § 17200 (“UCL”) based on their monopolization claims.

ANALYSIS

A. Applicable Legal Standards.

A motion for judgment on the pleadings pursuant to Federal Rule of Civil Procedure 12(c) challenges the legal sufficiency of the claims asserted in the complaint. A Rule 12(c) motion is “functionally identical” to a motion to dismiss pursuant to Federal Rule of Civil Procedure 12(b)(6). Ross v. U.S. Bank Nat’l Ass’n, 542 F.Supp.2d 1014, 1023 (N.D.Cal.2008). “For purposes of the motion, the allegations of the non-moving party must be accepted as true ... Judgment on the pleadings is proper when the moving party clearly establishes on the face of the pleadings that no material issue of fact remains to be resolved and that it is entitled to judgment as a matter of law.” Hal Roach Studios, Inc. v. Richard Feiner and Co., Inc., 896 F.2d 1542, 1550 (9th Cir.1990). However, “[t]he court need not ... accept as true allegations that contradict matters properly subject to judicial notice.... ” Sprewell v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir.2001).

[1017]*1017Where a plaintiff alleges fraud, Federal Rule of Civil Procedure 9(b) (“Rule 9(b)”) requires the plaintiff to state with particularity the circumstances constituting fraud, including the “who, what, when, where, and how” of the charged misconduct. See Hess v. Ciba-Geigy Corp. USA 317 F.3d 1097, 1106 (9th Cir.2003); In re GlenFed, Inc. Sec. Litig., 42 F.3d 1541, 1547-49 (9th Cir.1994). However, Rule 9(b) particularity requirements must be read in harmony with Federal Rule of Civil Procedure 8’s requirement of a “short and plain” statement of the claim. Thus, the particularity requirement is satisfied if the complaint “identifies the circumstances constituting fraud so that a defendant can prepare an adequate answer from the allegations.” Moore v. Kayport Package Exp., Inc., 885 F.2d 531, 540 (9th Cir.1989); see also Vess, 317 F.3d at 1106 (“Rule 9(b) demands that, when averments of fraud are made, the circumstances constituting the alleged fraud be specific enough to give defendants notice of the particular misconduct ... so that they can defend against the charge and not just deny that they have done anything wrong.”) (internal quotation marks and citations omitted).

B. ChriMar’s Motion.

1. Defendants’ Monopolization Counterclaims.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
72 F. Supp. 3d 1012, 2014 U.S. Dist. LEXIS 153393, 2014 WL 5477666, Counsel Stack Legal Research, https://law.counselstack.com/opinion/chrimar-systems-inc-v-cisco-systems-inc-cand-2014.