Hynix Semiconductor Inc. v. Rambus Inc.

441 F. Supp. 2d 1066, 2006 U.S. Dist. LEXIS 75187, 2006 WL 2038357

Opinion

ORDER DENYING IN PART AND GRANTING IN PART RAMBUS’S MOTION FOR SUMMARY JUDGMENT OF BREACH OF CONTRACT AND FRAUD CAUSES OF ACTION AND GRANTING PARTIAL SUMMARY ADJUDICATION OF CERTAIN ISSUES RELATING TO DUTY

WHYTE, District Judge.

Defendant Rambus Inc. (“Rambus”) moves for summary judgment on the breach of contract and fraud claims for relief 1 in the Second Amended Complaint (“SAC”) filed by plaintiffs Hynix Semiconductor Inc., Hynix Semiconductor America Inc., Hynix Semiconductor U.K. Ltd., and Hynix Semiconductor Deutschland GmbH (“Hynix”). 2 Rambus’s motion also seeks summary adjudication of certain issues related to duty. Hynix opposes the motion. The court has reviewed the papers and considered the arguments of counsel.

For the reasons discussed below, the court GRANTS Rambus’s motion for summary judgment on Hynix’s fifth, sixth, seventh and ninth claims for relief and DENIES Rambus’s motion for summary judgment on Hynix’s eighth claim for relief. The court also SUMMARILY ADJUDICATES that: (1) the JEDEC duty to disclose did not extend to the beliefs, hopes, or intentions to file or amend patent applications; (2) the JEDEC duty to disclose did not continue after a member left JEDEC, except for specific disclosures that arose before the member left; and (3) breach of any JEDEC disclosure duty, without more, does not give rise to anti trust liability. The court DENIES SUMMARY ADJUDICATION that (1) any disclosure of patent applications under the JEDEC disclosure policy was voluntary, not mandatory; (2) the JEDEC duty to disclose extends only to patents necessary to practice the contemplated standard, and (3) Rambus’s alleged breach of the JE-DEC disclosure duty did not cause the injuries Hynix has alleged.

I. BACKGROUND

A. Rambus Interface Technology

In 1990 Rambus applied for a patent with the United States Patent and Trademark Office (“PTO”) for a particular type of dynamic random access memory (“DRAM”) device that is known as the Rambus DRAM or RDRAM. Data is transferred between DRAM devices and components such as the central processing unit (or microprocessor) and controller when data is written to or read from the DRAM device. The RDRAM is a DRAM that is designed with modified architecture and circuitry to enable significantly increased memory bandwidth. The RDRAM design includes a narrow, multiplexed bus architecture using a packetized communications protocol. Vega Decl. Supp. Pls.’s Opp. Def.’s Mot. Summ. J. (“Vega Deck”), Ex. 18 at R 111315. Ram-bus refers to this modified architecture as the Rambus Interface Technology. Ram-bus licenses the Rambus Interface Technology to companies that manufacture DRAMs and other integrated circuits for end users, typically in exchange for royalty payments. 3

B. Joint Electron Device Engineering Council

In December 1991 Rambus applied for membership in the Joint Electron Device Engineering Council (“JEDEC”). 4 Vega Deck, Ex. 26. JEDEC is an organization that develops and sets industry standards, including for the design and manufacture of DRAM devices. Members of JEDEC include representatives of technology companies who develop, manufacture or use DRAM devices. JEDEC committee members discuss and consider technology proposed to be standardized and also provide input on the extent of their interest in proposed technology or improvements. The JEDEC committee votes on whether to send a ballot to the JEDEC Council, which determines whether to standardize the technology set forth in the ballot.

JEDEC is part of the Electronic Industries Association (“EIA”). Accordingly, JEDEC’s policies are set forth in EIA guidelines and its own manuals. The EIA Style Manual EP-7-A guards against adopting standards that are covered by patented technology:

[n]o program standardization shall refer to a patented item or process unless all of the technical information covered by the patent is known to the formulating committee or working group, and the committee chairman has received a written expression from the patent holder that one of the following conditions prevail:

(1) a license shall be made available without charge to applicants desiring to utilize the patent for the purpose of implementing the standard, or

(2) a license shall be made available to applicants under reasonable terms and conditions that are demonstrably free of unfair discrimination.

Vega Decl., Ex. E at R 155981. JEDEC’s manual provides that when patented technology is included in a standard, the JE-DEC committee must know the relevant technical information covered by the patent, and the patent holder must have agreed to license the technology on reasonable and non-diseriminatory (“RAND”) terms. Vega Decl., Ex. I at R 173476. Further, the committee chairman should “call attention to the obligation of all participants to inform the meeting of any knowledge they may have of any patents, or pending patents, that might be involved in the work they are undertaking.” Id.

In January 1993 the JEDEC Council added a footnote to its manual that stated the term “patent” as used in its manual includes patent applications. Vega Decl., Ex. I at R173476. The JEDEC committee chairman for the single data rate synchronous DRAM (“SDRAM”) and double data rate synchronous DRAM (“DDR SDRAM”) devices kept a list of patents and patent applications disclosed to JE-DEC as possibly bearing on the standards JEDEC was undertaking. Richard Crisp July 20, 2001 Dep. (“Crisp 7/20/01 Dep.”) at 434:3. 5 If standards to be adopted contained patented technology, the JEDEC committee was responsible for determining that patent holders had agreed to RAND licensing terms if patented technology was to be included in JEDEC standards. Vega Decl., Ex. I at R 173476. As applicable here, JEDEC adopted standards for the SDRAM device and DDR SDRAM device. While it was a JEDEC member, Rambus was a member of the JEDEC committee that discussed proposed standards for the SDRAM and DDR SDRAM devices.

C. Rambus’s Relationship with JE-DEC

As a JEDEC member, Rambus regularly attended committee meetings, including where JEDEC’s policies regarding standardizing patented technology were discussed. Crisp 7/20/01 Dep. at 434:3-9. At the September 1993 meeting, the members discussed JEDEC’s reaction to Texas Instrument’s failure to disclose a patent for quad CAS devices that read on a standard adopted by JEDEC. Vega Decl., Ex. 38. It appears JEDEC decided to remove the patented devices from its standard. Id. In that September 1993 JEDEC meeting, Rambus disclosed its U.S. Patent 5,243,703 (“the '703 Patent”) which Hynix alleges only tangentially related to the SDRAM standards being developed at the time. Richard Crisp Apr. 23, 2001 Dep. (“Crisp 4/23/01 Dep.”) at 177:25-183:19. Rambus’s disclosure did not include any of its pending or planned patent applications or amendments that would cover SDRAM features. 6 The parties do not appear to dispute that during Rambus’s membership with JEDEC and after its membership ended, Rambus had pending and planned patent applications that would cover SDRAM and DDR SDRAM technology as standardized by JEDEC. However, Hy-nix contends Rambus made changes to its patent applications specifically to claim technology in, or proposed to be added to, the JEDEC SDRAM standards. Crisp 7/20/01 Dep. at 483:15M94:17; 626:3-627:18; Vega Decl., Ex. 37. JEDEC adopted standards for the SDRAM device around mid-1993 while Rambus was still a member. Vega Decl., Ex. 32.

In October 1995 JEDEC proposed the use of a delayed locked loop (“DLL”) or phased locked loop (“PLL”) on the chip itself and the use of both edges of the clock as standard SDRAM features. 7 Vega Deck, Ex. M. At this time Rambus did not make any disclosures to JEDEC with respect to its patent applications for, or plans to obtain coverage of, SDRAM that utilized DLL, PLL or both edges of the clock. Vega Deck, Ex. M. It is undisputed that Rambus was not a party to any RAND licensing agreement with JEDEC with respect to either SDRAM or DDR SDRAM.

In June 1996 Rambus formally withdrew as a member of JEDEC. 8 Vega Deck, Ex. 26 at cx0602-08. Some time after Ram-bus’s withdrawal, JEDEC adopted standards for the DDR SDRAM device. The standards adopted for the DDR SDRAM device included the DLL or PLL feature as well as the use of both edges of the clock.

Around late 1999 or early 2000 Rambus began notifying manufacturers of DRAM devices using the JEDEC SDRAM and DDR SDRAM standards and end users of such DRAM devices that the manufacture, sale, offer for sale, and use of the DRAM devices infringed Rambus patents.

D. Rambus’s Relationship with Hy-nix

Hynix manufactures memory devices, including JEDEC-compliant DRAMs such as the SDRAM and the DDR SDRAM. Though unclear, it appears Hynix was also a member or participant in the same JE-DEC committee as Rambus while Rambus was a member. Beginning in mid-1994, Rambus and Hynix were actively discussing a license by Hynix of Rambus Interface Technology. Vega Deck, Ex. 22. On August 31, 1994 Richard Crisp (“Crisp”), a Rambus employee and Rambus’s representative at JEDEC at that time, and Bob Proebsting (“Proebsting”) of Hynix met to discuss a potential license agreement. Id. At this meeting, Proebsting informed Crisp of Hynix’s intent to manufacture the SDRAM device with a PLL feature. Id. Proebsting told Crisp of Hynix’s belief that the production of RDRAMs would involve paying royalties to Rambus while the production of SDRAMs would not involve a royalty payment to Rambus. Id. Tt does not appear Crisp made any response to these statements by Proebsting. Id. When Proebsting asked Crisp whether Rambus had a patent on such a device, Crisp stated that he could not comment. Id. '

In April 1995 Rambus and Hynix continued discussions about a potential license agreement. Hynix indicated an interest in producing a SyncLink DRAM device (“SLDRAM”). 9 In response, Rambus noted that the SLDRAM worked in a similar manner to the RDRAM. Crisp wrote to Hynix: “since Rambus has filed and had issued a number of very fundamental patents, it seems unlikely a device such as [SLDRAM] could avoid infringing one or more Rambus patents.” Vega Decl., Ex. L at HR 905_176335. In the course of these contract discussions Rambus never mentioned that the SDRAM might infringe Rambus’s intellectual property, including issued or pending patents.

In May 1995 JEDEC members, discussed the SLDRAM technology and several JEDEC members inquired of Crisp whether such technology infringed Rambus’s intellectual property rights. Vega Decl., Ex. 42 at R 69583. In August 1995 Rambus made disclosures to an IEEE SyncLink committee that it believed the SLDRAM was bound to infringe Rambus’s intellectual property in the long run. Vega Decl., Ex. 45 at R 168893.

In December 1995 Rambus and Hynix entered into a technology license agreement (“License Agreement”). Under the License Agreement, Rambus granted Hy-nix a “worldwide, nonexclusive, nontransferable license, under the Rambus Intellectual Property Rights, to design, make, have made ... use, import, offer to Sell, and Sell Rambus ICs, Rambus Modules, Rambus Boards, and Rambus Systems” in exchange for royalties. Vega Deck, Ex. 49 at HR905-000007. The License Agreement defines the following terms applicable to the license grant:

“Rambus ICs” means Rambus Memories, Other DRAMs and, only to the extent the option therefor is exercised by [Hynix] ... Rambus Processors, Rambus Peripherals, and/or Rambus ASICs.

* * *

“Rambus Memory” means each dynamic random access memory (“DRAM”) integrated circuit with a principal function of memory storage which (i) incorporates all or part of the Rambus Interface

Technology, (ii) is defined and designed by [Hynix] [or by Rambus for [Hynix]], (iii) is Compatible with the Rambus Interface Specification.

* *

“Other DRAM” means each DRAM which incorporates part of the Rambus Interface Technology but is not Compatible with the Rambus Interface Specification.

* * *

“Rambus Interface Technology” means the following items which are owned by Rambus ... (a) the bus interface technology described in Exhibit A hereto; and (b) all information, inventions, technology, technical documentation, designs (including circuit designs), materials, know-how which describe use of such bus interface technology and which Rambus provides [Hynix] during the course of implementing this Agreement.

“Rambus Interface Specification” means, any time, the then most current version of the interface specification for the Rambus Interface Technology, as such interface specification is finalized and released by Rambus.

Vega Deck, Ex. 49 at HR905_000002-04. The License Agreement specifies separate royalty rates for the Rambus Memories and the “Other DRAMs.” Id. at HR905-000012. The parties dispute the extent of the scope of the License Agreement. 10

II. ANALYSIS

A. Legal Standard

Summary judgment is granted if there is no genuine issue as to any material fact. Fed.R.CivP. 56(c); Celotex Corp. v. Ca trett, 477 U.S. 317, 322, 106 S.Ct. 2548, 91 L.Ed.2d 265 (1986). In a motion for summary judgment, the court draws all reasonable inferences that may be taken from the underlying facts in the light most favorable to the nonmovant. Matsushita Elec. Indus. Co., Ltd. v. Zenith Radio Corp., 475 U.S. 574, 587, 106 S.Ct. 1348, 89 L.Ed.2d 538 (1986). In Nissan Fire & Marine Ins. Co., Ltd. v. Fritz Companies, Inc., the Ninth Circuit elaborated:

In order to carry its burden of production, the moving party must either produce evidence negating an essential element of the nonmoving party’s claim or defense or show that the nonmoving party does not have enough evidence of an essential element to carry its ultimate burden of persuasion at trial. In order to carry its ultimate burden of persuasion on the motion, the moving party must persuade the court that there is no genuine issue of material fact.

If a moving party fails to carry its initial burden of production, the nonmoving party has no obligation to produce anything, even if the nonmoving party would have the ultimate burden of persuasion at trial. In such a case, the nonmoving party may defeat the motion for summary judgment without producing anything. If, however, a moving party carries its burden of production, the nonmoving party must produce evidence to support its claim or defense. If the nonmoving party fails to produce enough evidence to create a genuine issue of material fact, the moving party wins the motion for summary judgment.

210 F.3d 1099, 1102-03 (9th Cir.2000) (citations omitted).

B. Breach of Contract Claims

Hynix’s Fifth Claim for Relief alleges that:

[a]s a result of its membership in JE-DEC, Rambus agreed, both explicitly and implicitly, that it would abide by the rules governing JEDEC members. The body of JEDEC rules governing members constitutes a written contract between all JEDEC members individually. These rules, among other things require JEDEC members, including Rambus, to disclose to other JEDEC members, including Hynix, any patents or patent applications that may bear upon standards being considered by JEDEC committees.

SAC ¶ 127.

Hynix’s sixth claim for relief is. entitled “Breach of Contract by Third Party Beneficiary” and contends that Hynix was a third party beneficiary of Rambus’s alleged contract with JEDEC and other JE-DEC members. The fifth and sixth claims essentially make the same contention, specifically that “if Rambus is allowed to assert its patents in breach of its agreement with Hynix and other JEDEC members and is successful, Hynix will be damaged in' the amount sought by Rambus as license fees.... ” SAC at ¶ 36.

Rambus contends that its membership in JEDEC does not give rise to any contractual claim or duty.

In order for a contact to be formed, the contract terms must be clear enough that the parties can understand what each is required to do. See Cal. Jury Instructions Civil (“CACI”) No. 302; Rest.2d Contracts § 33(1). The question of whether a contract is sufficiently definite is a question of law for the court. Ladas v. Cal. State Automobile Assn., 19 Cal.App.4th 761, 770 n. 2, 23 Cal.Rptr.2d 810 (1993) (An amorphous promise cannot rise to the level of a contractual duty.).

In Rambus Inc. v. Infineon Technologies A.G., 318 F.3d 1081 (Fed.Cir.2003), the Federal Circuit reviewed the language of the same EIA/JEDEC policies at issue in the present suit. The 'Federal Circuit found that:

[t]he language of these policy statements actually does not impose any direct duty on members, no language — in the membership application or manual excerpts — expressly require members to disclose information, and no indication that members ever legally agreed to disclose information.

Id. at 1098. The court further commented on the policy language in connection with whether it raised a disclosure duty that could serve as a basis for a fraud verdict if there were a failure to disclose:

In this case there is a staggering lack of defining details in the EIA/JEDEC patent policy. When direct competitors participate in an open standards committee, their work necessitates a written patent policy with clear guidance on the committee’s intellectual property position. A policy that does not define clearly what, when, how, and to whom the members must disclose does not provide a firm basis for the disclosure duty necessary for a fraud verdict.

Id. at 1102. The alleged agreement between JEDEC and Rambus or JEDEC members and Rambus was not definite enough to make clear to Rambus what disclosures it was required to make, if any.

Another essential element of any contract is the consent of the parties, or mutual assent. Cal. Civ.Code § 1550; Donovan v. RRL Corp., 26 Cal.4th 261, 270, 109 Cal.Rptr.2d 807, 27 P.3d 702 (2001). “A contract must be so interpreted as to give effect to the mutual intention of the parties as it existed at the time of contracting, so far as the same is ascertainable and lawful.” Cal. Civ.Code § 1636. Here, “the staggering lack of details” in the EIA/JEDEC patent disclosure policies precludes a finding of any -mutual assent when Rambus became a member of JEDEC.

Rambus’s membership in JEDEC did not, as a matter of law, create a contract between JEDEC and Rambus or JEDEC members and Rambus.

Hynix’s seventh claim for relief is described as “Breach of Contract— Promissory Estoppel.” Hynix claims that “[a]s a result of its membership in JE-DEC, Rambus agreed, both explicitly and implicitly that it would abide by the rules governing JEDEC members____[includ-ing] to disclose to other JEDEC members any patents or patent applications that may bear upon standards being considered by JEDEC committees.” SAC at ¶ 138. “The elements of a promissory estoppel claim are (1) a promise clear and unambiguous in its terms; (2) reliance by the party to whom the promise is made; (3) the reliance must be both reasonable and foreseeable; and (4) the party asserting the estoppel must be injured by his reliance.” U.S. Ecology, Inc. v. State, 129 Cal. App.4th 887, 901, 28 Cal.Rptr.3d 894 (2005) (internal quotations omitted). The essential difference between a promissory estop-pel claim and one for breach of contract is that, in promissory estoppel, equitable principles are substituted for consideration. Id. at 901-02, 28 Cal.Rptr.3d 894. In the instant case, since there was no clear and unambiguous promise by Ram-bus that it would abide by the JEDEC rules, Hynix does not have a viable promissory estoppel claim based upon Rambus’s membership in JEDEC.

C. Fraud

Hynix asserts “Actual Fraud” by Rambus in its eighth claim for relief. Under California law, the elements of fraud are: (1) representation, (2) - falsity, (3) knowledge of falsity, (4) intent to deceive, and (5) reliance and resulting damage. Vega v. Jones, Day, Reavis & Pogue, 121 Cal.App.4th 282, 291, 17 Cal.Rptr.3d 26 (2004) (citing 5 Within Cal. Procedure, Pleading § 668, p. 123 (4th ed.1997)). Fraudulent deceit occurs where one “willfully deceives another with intent to induce him to alter his position to his injury or risk” and therefore “is liable for any damage which he thereby suffers.” Cal. Crv. Code § 1709. A deceit, within the meaning of Cal. Civ.Code § 1709 is, in relevant part, (1) the suggestion, as a fact, of that which is not true, by one who does not believe it to be true and (2) the suppression of a fact, by one who is bound to disclose it, or who gives information of other facts which are likely to mislead for want of communication of that fact. Cad. Civ.Code § 1710.

The fraud or deceit alleged by Hynix is predicated on more than just Ram-bus’s membership in JEDEC. Hynix claims that Rambus had a duty to disclose its patent applications and intentions related to obtaining coverage of SDRAM and DDR SDRAM based upon a number of factors. Specifically, Hynix asserts:

that Rambus had a duty to disclose based on (a) the JEDEC patent policy, (b) the “partner” relationship between Rambus and Hynix, (c) Crisp’s repeated admissions at the time and during litigation that Rambus had an “obligation” to disclose and should disclose its position the SDRAM and DDR SDRAM infringed, and (d) Rambus’s repeated misleading “half-truths” which required full disclosure to avoid deceiving Hynix (e.g. Rambus told JEDEC and Hynix independently that SyncLink infringed Ram-bus patent rights while saying nothing about SDRAM or DDR SDRAM even though Rambus also believed that those products infringed, Rambus’s failure to seek royalties under the “Other DRAM” provision of Hynix’s license for SDRAM and DDR SDRAM even though it was Rambus’s secret claim that those products used Rambus Technology, and Rambus’s disclosure of the '703 patent while failing to disclose the intellectual property that it believed SDRAM and DDR SDRAM would actually infringe, etc.).

Hynix Opp. Def.’s Mot. Summ. J at 18-19.

There are four circumstances in which nondisclosure or concealment may constitute actionable fraud: (1) when the defendant is in a fiduciary relationship with the plaintiff; (2) when the defendant had exclusive knowledge of material facts not known to the plaintiff; (3) when the defendant actively conceals a material fact from the plaintiff; and (4) when the defendant makes partial representations but also suppresses some material fact.

LiMandri v. Judkins, 52 Cal.App.4th 326, 337, 60 Cal.Rptr.2d 539 (1997) (internal citations omitted). Exception (1) is not applicable because Rambus was not in a fiduciary relationship with Hynix. See infra. However, factual questions are raised with respect to the other three circumstances.

In addition to looking at the policy language in Infineon, the Federal Circuit looked at the conduct and beliefs of JE-DEC members and observed:

[nevertheless, because JEDEC members treat the language of [the EIA policy] as imposing a disclosure duty, this court likewise treats this language as imposing a disclosure duty. Infineon provides no evidence that the policy required (or that JEDEC members understood the policy to require) disclosure of patents and applications not necessary to practice the standard. On this record, a reasonable jury could find only that the duty to disclose a patent or application arises when a license under its claims reasonably might be required to practice the standard.

Infineon, 318 F.3d at 1098. The court then reviewed the jury’s findings regarding the extent of this duty, and at what stage of the JEDEC process the duty arose and concluded: 11

Id. at 1100.

The JEDEC policy itself does not state when a committee member’s duty arises. Id. at 1100-02. The Federal Circuit found that the Infineon record “at most indicates that the disclosure duty arises when proposals are aimed at a particular standard” and that the Infineon record “does not show that JEDEC applied the disclosure duty to a member’s plans or intentions.” Id. at 1103. Turning to the issue of breach, the Federal Circuit then found that Infineon did not establish, by the clear and convincing standard applicable under Virginia law, that the claims of the four patents at issue in that case read on the SDRAM standard. 12 Id. In addition, because formal proposals related to the DDR SDRAM standards did not occur until after Rambus withdrew as a member, Rambus owed no disclosure duty for claims alleged to read on the DDR SDRAM standards. Id. at 1105.

Based upon Infineon and the record in this case, Hynix may be able to prove facts showing at least a duty to disclose pending amendments that would directly read on the proposed SDRAM standard.

A duty to disclose also may arise out of the license negotiations between Rambus and Hynix. Starting in mid-1994, Rambus and Hynix were in preliminary discussions to enter into a technology license agreement. Vega Decl., Ex. 22. The record indicates Hynix’s representative, Proebst-ing, made affirmative statements to Ram-bus’s JEDEC representative, Crisp, of Hy-nix’s beliefs that its manufacture of SDRAMs, including possibly with a PLL, would not require it to pay royalties to Rambus. Id. Proebsting and Crisp also discussed whether SLDRAM might give rise to royalty payments to Rambus. While Crisp and Rambus responded to Hynix that it is likely that the SLDRAM device would infringe Rambus’s patents, they remained silent as to SDRAM and DDR SDRAM. Vega Decl., Ex. L at HR_905-176335, Ex. 45 at R 16889. Notably, Rambus does not dispute that it was at least aware Hynix manufactured or intended to manufacture SDRAM and SLDRAM including features that might infringe Rambus patents.

The court thus cannot conclude that Rambus did not have a duty to disclose its patents or patent applications based upon Rambus’s business and licensing relationship with Hynix.

Even where no duty to disclose would otherwise exist, “where one does speak he must speak the whole truth to the end that he does not conceal any facts which materially qualify those stated. One who is asked for or volunteers information must be truthful, and the telling of a half-truth calculated to deceive is fraud.” 13 Vega, 121 Cal.App.4th at 295, 17 Cal.Rptr.3d 26 (citation omitted). “Active concealment or suppression of facts by a non- fiduciary is the equivalent of a false representation, i.e., actual fraud.” Id.

In Vega, the plaintiff alleged that defendant included in its disclosure schedules the pertinent terms of a pending $10 million private stock transaction, but omitted disclosure of the transaction’s “toxic stock” provisions. There was no dispute that the defendant knew of the toxic stock provisions. Thus, the plaintiff alleged that defendant “deliberately or with a reckless disregard of the truth concealed the toxic stock provisions.” Id. at 292, 17 Cal.Rptr.3d 26. The Vega court held that the plaintiffs allegations stated an “active concealment or suppression of facts.” Id. The Vega court distinguished that “the question in a nondisclosure case is whether the defendant knows of material facts, and also knows that those facts are neither known nor readily accessible to the plaintiff.” Id.

Here, Hynix points to discussions between Hynix’s representative, Proebsting, and Rambus’s representative, Crisp, regarding Hynixs intended manufacture of a SDRAM device with a PLL and/or a SLDRAM device and Hynix’s beliefs that such devices would not result in a royalty to Rambus as compared to the RDRAM. Vega Deck, Ex. 22. The discussions between Hynix and Rambus were not idle exchanges, but were held in anticipation of entering into a license agreement for Hy-nix’s manufacture of DRAMs. Id. Against this backdrop of interchanges, Rambus nevertheless chose to disclose to Hynix only that the SLDRAM potentially infringed its patents. Vega Deck, Ex. L at HR905_176335. In December 1995 Hynix and Rambus entered into the License Agreement which covered the Rambus Interface Technology and “Other DRAM” technology. Vega Deck, Ex. 49. It is undisputed that Rambus did not claim that Hynix might owe royalties for use of the SDRAM or DDR SDRAM standards from the December 1995 effective date of the License Agreement until its June 2000 notice of infringement to Hynix. 14

The court finds that Hynix has demonstrated that a genuine issue of material fact exists as to its allegations of actual fraud in its eighth claim for relief.

In its ninth claim, Hynix asserts constructive fraud on the basis that “Ram-bus, as a member of JEDEC, owed a fiduciary duty under JEDEC’s patent policy, to disclose to JEDEC and other JE-DEC members including Hynix, patents and pending patent applications that might be involved in the work that JEDEC was undertaking with respect to the standardization of SDR SDRAM and DDR SDRAM technology.” SAC ¶ 154. A claim of constructive fraud requires that the parties “stand in a fiduciary relationship.” Estate of Gump, 1 Cal.App.4th 582, 601, 2 Cal.Rptr.2d 269 (1991). Hynix alleges that it stood in a fiduciary capacity with Rambus as a co-member of JEDEC. However, as stated by the Federal Circuit in Infineon:

Rambus and Infineon are competitors. There is no basis for finding that Ram-bus and Infineon shares a fiduciary relationship solely by virtue of their JEDEC membership. Indeed, the implications of holding that mere membership forms a fiduciary duty among all JEDEC members could be substantial and raise serious antitrust concerns.

Infineon, 318 F.3d at 1096 n. 7. This court agrees. The parties do not dispute that JEDEC is a standard setting body whose goal is to set open standards and avoid standardizing technologies subject to patents. To find that the members in a standard setting organization owed a fiduciary duty to each other would be inconsistent with the purpose of such an organization.

Hynix also points to its License Agreement with Rambus as giving rise to a fiduciary relationship with Rambus. Relationships between buyers and sellers of goods and services are generally incompatible with fiduciary obligations. See Comm. on Children’s Television, Inc. v. Gen’l Foods Corp., 35 Cal.3d 197, 221-22, 197 Cal.Rptr. 783, 673 P.2d 660 (1983). As Rambus points out, the License Agreement contains a clause that explicitly provides that no partnership or joint venture relationship is created by the License Agreement. Def.’s Reply Pls.’s Opp. Defs Mot. Summ. J. at 10. The License Agreement cannot be reasonably construed to be other than a commercial contract.

Even viewing the record in the light most favorable to Hynix, there is no genuine issue of material fact that Rambus and Hynix stood in a fiduciary relationship based on either JEDEC membership or the License Agreement. Because a fiduciary relationship is an essential element of a constructive fraud claim, the court grants Rambus’s motion for summary judgment on Hynix’s ninth claim for relief on the basis of constructive fraud.

D. Causation

Rambus asserts Hynix has failed to establish any genuine issue of material fact that Rambus’s alleged failure to disclose caused Hynix’s alleged damages. Rambus argues that if it had been required to disclose its patents or patent applications, it would have issued a RAND letter to JEDEC. Def.’s Mot. Summ. J. at 20-21. Therefore, the JEDEC standards would still incorporate technology covered under Rambus patents and Hynix would still owe royalties to Rambus because it manufactures SDRAM and DDR SDRAM devices following JEDEC standards. Id.

Rambus’s argument fails to address Hy-nix’s contentions that Rambus’s conduct at JEDEC indicated Rambus did not want to issue a RAND letter for the SDRAM and DDR SDRAM standards. Hynix points to Rambus’s June 1996 letter withdrawing from JEDEC, Rambus’s failure to inform anyone that the SDRAM and DDR SDRAM standards might infringe its patents or pending patents, and the possibility that JEDEC would exclude from its standards patented technology if a RAND letter were not obtained. 15 Vega Decl., Exs. 32, 38, 55. In the June 1996 letter, Ram-bus stated:

Recently at JEDEC meetings the subject of Rambus patents has been raised. Rambus plans to continue to license its proprietary technology on terms that are consistent with the business plan of Rambus, and those terms may not be consistent with the terms set by standard bodies, including JEDEC.

Vega Decl., Ex. 55.

Viewing the record in the light most favorable to the nonmoving party, there is a genuine issue of material fact as to whether Rambus would have agreed to a RAND letter if it had disclosed that the JEDEC SDRAM standards infringed its patents or any patent for which application had been made or planned. In addition, there is a genuine issue of material fact as to whether JEDEC would have adopted standards that infringed Rambus’s patents whether or not Rambus refused to issue a RAND letter acceptable to JEDEC.

E. Rambus’s Motion for Summary Adjudication of Certain Issues

1.Disclosure of Patent Applications

Rambus seeks summary adjudication that any disclosure of patent applications was voluntary, not mandatory. In determining the existence of a JEDEC duty, the court considered the JEDEC members’ treatment of the JEDEC patent disclosure policy. In addition to showing that members believed the policy imposed a duty to disclose patents, the record also shows facts that suggest that members believed patent applications should be disclosed. See, e.g., Vega Deck, Ex. I at R 173476; Hynix Opp. Def.’s Mot. Summ. J. at 6 (noting that JEDEC’s JEP21-I required the committee chair to “call attention to the obligation of all participants to inform the meeting of any knowledge they may have of any patents, or pending patents, that might be involved in the work they are undertaking”).

2.Beliefs, Hopes or Intentions to File or Amend Patent Applications

Rambus next seeks summary adjudication that if there was a disclosure duty, it did not extend to beliefs, hopes or intentions to file or amend patent applications. Hynix provides no evidence that any disclosure duty extends to beliefs, hopes or intentions to file or amend patent applications or that any disclosure duty should continue after a member left JE-DEC. In Infineon, 318 F.3d at 1102, the Federal Circuit held that JEDEC’s policy did not extend to the beliefs, hopes or intentions to file or amend patent applications. The court concludes that the JE-DEC disclosure duty did not extend to Rambus’s beliefs, hopes or intentions to file or amend its patent applications and that Rambus’s JEDEC duty to disclose ended after it formally withdrew from JE-DEC. However, the court notes that this conclusion extends only to Rambus’s duty pursuant to the JEDEC policy.

3.Disclosure Duty after a Member Leaves JEDEC

Rambus moves for summary adjudication that if there was a disclosure duty, it did not continue after a member left JEDEC. Hynix does not provide any evidence that any. disclosure duty would continue after a member leaves JEDEC, except as to disclosure duties that had arisen before the member left. The court grants as unopposed Rambus’s motion for summary adjudication that the JEDEC duty to disclose ends once a member formally withdraws from JE-DEC.

4.Disclosure Only of Patents Necessary to Practice the Contemplated Standard

Rambus also seeks summary adjudication that if there was a disclosure duty, it applied only to patents necessary to practice the contemplated standard. In Infineon, the Federal Circuit addressed a similar issue. There, the court observed that the record indicated that disclosure only related to issued or pending claims necessary to practice the standard. Infineon, 318 F.3d at 1100. Thus, the court concluded:

Rambus’s duty to disclose extended only to claims in patents and applications that reasonably might be necessary to practice the standard. In other words, the duty encompassed any patent or application with claims that a competitor or other JEDEC member reasonably would construe to cover the standardized technology.

id. 16 The court explained “to hold otherwise would contradict the record evidence and render the JEDEC disclosure duty unbounded.” Id. at 1101.

Here, Hynix contends that the JEDEC disclosure policy includes patents that might be necessary to practice a standard. Hynix points to JEDEC’s JEP21-I which required the committee chair to “call attention to the obligation of all participants to inform the meeting of any knowledge they may have of any patents, or pending patents, that might be involved in the work they are undertaking.” Hynix Opp. Def.’s Mot. Summ. J. at 6. Hynix notes that when Texas Instruments argued to JEDEC that the patent disclosure policy only required disclosure of essential patents, JEDEC responded that “the committee was concerned with any patent that might be necessary to practice a standard.” Vega Deck, Ex. 39 at R 69526. These statements do not make clear what additional disclosures are required in addition to those that are reasonably necessary to practice the standard.

Rambus’s argument that the disclosure policy should be limited is well taken. However, as discussed above, the disclosure duty arising from the practice of JE-DEC members is defined by the members’ conduct and treatment of the stated policy. Therefore, there is a genuine issue of material fact with respect to whether the disclosure is limited to patents and applications reasonably necessary to practice the standard or extends to patents and patent applications that might be necessary to practice the standard.

5. Antitrust Liability

Rambus also seeks summary adjudication that as a threshold issue of antitrust law, the JEDEC disclosure duty Hynix has alleged was too vague for any breach to give rise to antitrust liability. Rambus notes that the activities of standard setting organizations can sometimes tread a fine line between the policies of the United States patent laws and antitrust laws. Therefore, Rambus argues that the rights and duties of participants in standard setting organizations must be clearly defined with respect to their intellectual property rights.

In opposition, Hynix argues that Ram-bus’s conduct associated with its breach of the JEDEC disclosure requirement is part of a course of conduct to unlawfully secure a monopoly of the DRAM interface technology market. Hynix points to alleged predatory and anticompetitive conduct by Rambus. Specifically, Hynix asserts Ram-bus attended JEDEC meetings so that it could secretly amend it patent applications to claim SDRAM and DDR SDRAM technology being standardized by JEDEC. Vega Deck, Exs. 30, 31, 33-35. Hynix asserts that the evidence shows that Ram-bus chose not to disclose these amendments because it did not “yet” want the industry to know that its patents or patent applications covered JEDEC standards. See, e.g., Exs. 24, 32.

The court agrees that industry wide standards set by organizations such as JEDEC can serve to foster competition, but at the same time also pose a risk of anticompetitive conduct. See Allied Tube & Conduit Corp. v. Indian Head, Inc., 486 U.S. 492, 500-01, 108 S.Ct. 1931, 100 L.Ed.2d 497 (1988). In addition, the patent laws secure upon patentees lawful monopolies to encourage innovation. Intergraph Corp. v. Intel Corp., 195 F.3d 1346, 1362 (Fed.Cir.1999). “It is well-settled that the secrecy of pending and abandoned United States patent applications should be preserved whenever possible.” Cordis Corp. v. SciMed Life Sys., Inc., 982 F.Supp. 1358, 1360 (D.Minn.1997). On the other hand, it is apparent that abuse of the standards setting process could lead to serious anticompetitive and antitrust concerns. See, e.g., Infineon, 318 F.3d at 1096 (noting that interpreting JEDEC membership as creating a fiduciary duty among members would raise serious antitrust concerns).

In light of the patent law policies implicated, breach of the JEDEC disclosure policies, without more, cannot give rise to antitrust liability. To do so, particularly in light of the vagueness of the JEDEC disclosure policy at issue, would directly conflict with the protection afforded patentees and patent applicants to encourage innovation. The court finds that breach of JE-DEC’s disclosure policy, by itself, is not sufficient to constitute antitrust liability. The court notes, however, that Hynix is not barred from asserting that Rambus’s overall course of conduct, which may include the circumstances and intent behind its decision to not disclose its patents and patent applications, violated antitrust laws.

6. Causation of Alleged Injuries

Finally, Rambus seeks summary adjudication that its alleged breach of the JE-DEC disclosure duty did not cause the injuries Hynix has alleged. For the same reason that the court denied Rambus’s motion for summary judgment that Ram-bus’s breach of its JEDEC disclosure duty did not cause Hynix’s alleged damages, the court also denies summary adjudication of this issue.

III. ORDER

For the foregoing reasons, the court GRANTS defendant’s motion for summary judgment on plaintiffs’ fifth, sixth, seventh, and ninth claims for relief and DENIES defendant’s motion for summary judgment on plaintiffs’ eighth claim for relief.

The court also SUMMARILY ADJUDICATES that: (1) the JEDEC duty to disclose did not extend to the beliefs, hopes, or intentions to file or amend patent applications; (2) the JEDEC duty to disclose did not continue after a member left JE-DEC, except for specific disclosures that arose before the member left; and (3) breach of any JEDEC disclosure duty, without more, does not give rise to antitrust liability. The court DENIES SUMMARY ADJUDICATION that (1) any disclosure of patent applications under the JEDEC disclosure policy was voluntary, not mandatory; (2) the JEDEC duty to disclose extends only to patents necessary to practice the contemplated standard, and (3) Rambus’s alleged breach of the JE-DEC disclosure duty did not cause the injuries Hynix has alleged.

1 . Hynix's fifth, sixth and seventh claims for relief allege breach of contract, breach of contract by third party beneficiary, and breach of contract by promissory estoppel, respectively, and Hynix’s eighth and ninth claims for relief allege actual fraud and constructive fraud, respectively.

2 . Hynix was formerly known as Hyundai Electronics Industries, Ltd. References to Hy-nix in this order refers also to Hyundai Electronics Industries, Ltd.

3 . Rambus began licensing the RDRAM technology even before the patents for the RDRAM were issued. Vega Deck, Ex. 19 at R 46400-04, R46422; Ex. 20 at R 169939; Ex. 21; Ex. 22 at R 2970373; Ex. 23.

4 . JEDEC is now known as the JEDEC Solid State Technology Association.

6 . The parties do not dispute that JEDEC had not yet started discussions or development of any standards for the DDR SDRAM technology at this September 1993 meeting.

7 ."Clock” refers to the periodic electronic signals used to coordinate the actions of circuits. "Use of both edges of the clock” refers to a design whereby data is transferred on both the rise (high state) and fall (low state) of the clock to achieve greater bandwidth. DLL and PLL refer to a circuit design feature that synchronizes the clock signals of the various circuits, allowing increased performance speeds. These features were later made part of the DDR standard.

8 . Rambus may have withdrawn from JEDEC earlier in 1996, but its formal letter of withdrawal was dated June 1996.

9 . In particular, the SyncLink device was designed with a "narrow multiplexed bus interface with a'packetized communications protocol.” Rambus refers to this type of DRAM device as the RamLink.

10 . Hynix asserts, and Rambus does not appear to dispute, that the "Other DRAM” provision was intended to cover the SLDRAM and also applies to SDRAM. Hynix's Opp. Def.’s Mot. Summ. J. at 14.

11 . Virginia law was applicable in the Infineon case. Under Virginia law, whether there is a duty is a question of fact.

12 . The Rambus patents at issue in the Infi-neon suit were U.S. Patent Nos. 5,954,804; 5,953,263; 6,034,918; and 6,032,214.

13 . This is distinguished from allegations of negligent misrepresentation which require an affirmative assertion. See Wilson v. Century 21 Great Western Realty, 15 Cal.App.4th 298, 306, 18 Cal.Rptr.2d 779 (1993). Hynix's SAC does not assert a claim of negligent misrepresentation.

14 . It is immaterial whether the alleged infringed patents were issued, pending or planned. The crux of the issue is whether Rambus knowingly omitted facts material to Hynix when it chose to disclose that SLDRAM devices likely infringed Rambus patent in the course of preliminary contract negotiations related to the alternative DRAM technologies. Notably, Hynix had indicated a clear preference to know whether it had to pay royalties to Rambus. See, e.g., Vega Deck, Ex. 22. Rambus has not otherwise explained why it needed to disclose the potential infringement of SLDRAM but not SDRAM (and later DDR SDRAM), including after it had entered in the License Agreement with Hynix.

15 . Notably, this would be consistent with JE-DEC’s overall policy to avoid standardizing technology subject to patents and to promulgate open standards.

16 . The court also held that Rambus's disclosure of the '703 patent satisfied any duty to disclose technologies described but not claimed in its patents or applications. Infi-neon, 318 F.3d at 1100.