Leon Stambler v. Rsa Security, Inc.

123 F. App'x 982
CourtCourt of Appeals for the Federal Circuit
DecidedFebruary 11, 2005
Docket2004-1129
StatusUnpublished
Cited by1 cases

This text of 123 F. App'x 982 (Leon Stambler v. Rsa Security, Inc.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Leon Stambler v. Rsa Security, Inc., 123 F. App'x 982 (Fed. Cir. 2005).

Opinion

ARCHER, Senior Circuit Judge.

Leon Stambler (“Stambler”) appeals the judgment of the United States District Court for the District of Delaware denying his motion for judgment as a matter of law (“JMOL”) or, in the alternative, for a new trial. Contrary to Stambler’s argument, RSA Security, Inc. and VeriSign, Inc. (“RSA”) did not argue to the jury a construction of claim 34 of U.S. Patent No. 5,793,302 (“the ’302 patent”) counter to that set forth by the district court. As discussed below, we conclude 1) substantial evidence supports the jury’s noninfringement verdict; 2) Stambler did not show that defense counsel improperly influenced the jury; and 3) the district court did not abuse its discretion in bifurcating the issues of validity and infringement. Accordingly, we affirm, the judgment of the district court. Stambler v. RSA Security, No. 01-0065-SLR, 2003 WL 22749855 (D.Del.2003).

Background

Stambler sued RSA for, inter alia, infringement of the ’302 patent based on its use of Secure Sockets Layer version 3.0 (“SSL 3.0”). The patented methods enable parties to a transaction to assure the identity of an absent party and the accuracy of information involved in the transaction, thus providing for secure transactions and preventing fraud. Id. at 2. SSL 3.0 is widely considered to be the standard method for conducting secured communications via the Internet. Id. at 5. The SSL 3.0 protocol addresses two security issues pertaining to Internet communications. *984 Id. The protocol insures that parties communicating over the Internet are certain of each other’s identity and that communications between the parties cannot be intercepted and deciphered by an unauthorized party. Id.

Claim 34 of the ’302 patent is at issue here. Claim 34 is dependent upon claim 33, which states the following:

A method for authenticating a first party by using information stored in a credential, the credential being previously issued to the first party by a second party, wherein information previously stored in the credential comprises at least a non-secret variable authentication number (VAN) and other non-secret credential information, the method comprising:
previously generating a first error detection code (EDC1) by using at least a portion of the other non-secret credential information;
previously coding the first error detection code (EDC1) with first information associated with the second party to derive a variable authentication number (VAN);
previously storing the VAN and the other non-secret credential information in the credential;
retrieving the VAN and the other non-secret credential information stored in the credential;
deriving a second error detection code (EDC2) by using at least a portion of the retrieved other non-secret credential information;
retrieving second information associated with the second party previously stored in a storage means associated with at least one of the parties; uncoding the VAN using the second information associated with the second party to derive a third error detection code (EDC3);
and authenticating the first party and at least a portion of the non-secret information stored in the credential if the second error detection code (EDC2) corresponds to the third error detection code (EDC3).

’302 patent, col. 30 11. 35-65. Claim 34 states that it is a “method of claim 33 wherein the first information associated with the second party comprises a public key, and the second information associated with the second party comprises a non-secret key.” Id. at col. 30, line 66 — col. 31, line 2.

Following a verdict of non-infringement, Stambler filed a renewed motion for JMOL and, in the alternative, for a new trial. The district court denied the motions, and Stambler now appeals. We have jurisdiction pursuant to 38 U.S.C. § 1295(a)(1).

Discussion

Stambler argues that the district court erred in denying his renewed motion for judgment as a matter of law because the district court permitted defendants to add limitations to the claim language. Stambler further asserts he should be accorded a new trial because defense counsel improperly influenced the jury and because bifurcation of the infringement and validity issues resulted in a fundamentally unfair trial in violation of his rights under the Seventh Amendment.

The denial of JMOL is reviewed without deference and reversed only if substantial evidence does not support a jury’s factual findings or if the law cannot support the legal conclusions underpinning the jury’s factual findings. Moba, B.V. v. Diamond Automation, Inc., 325 F.3d 1306, 1312 (Fed.Cir.2003). The denial of a motion for a new trial is reviewed under the abuse of discretion standard. Motorola, Inc. v. Interdigital Tech. Corp., 121 F.3d 1461, 1468 *985 (Fed.Cir.1997), as is the propriety of the district court’s order bifurcating infringement and validity, Barr Labs., Inc. v. Abbott Labs., Inc., 978 F.2d 98, 105 (3d Cir. 1992).

Stambler argues that the district court erred in denying his renewed motion for judgment as a matter of law because, according to Stambler, it upheld the jury’s verdict of non-infringement based on a finding that it was “reasonable” for the jury to adopt additional claim limitations.

Experts from both sides offered testimony as to the three disputed limitations, “credential,” “storage means associated with one of the parties,” and “authenticating the first party.” RSA’s expert did not change the district court’s claim construction as to any of these elements by adding further claim limitations. To the contrary, RSA’s expert simply took the district court’s claim construction and provided detailed testimony as to why the accused device did not meet the claim limitations.

For example, the district court construed “credential” to mean “a document or information obtained from a trusted source that is transferred or presented to establish the identity of a party.” RSA’s expert explained that SSL 3.0 does not possess a “credential” as construed by the district court because in SSL 3.0 when the credential is presented it does not verify a user’s identity. This argument neither narrows nor is inconsistent with the district court’s claim construction. Rather, it is a reasonable interpretation of the court’s claim construction given that “establish” means “1. to bring into being on firm or permanent basis; found; ... 3. to cause to be accepted or recognized. 4. to show to be valid or true.” Random House Col. Dictionary 452 (revised ed.1980).

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
123 F. App'x 982, Counsel Stack Legal Research, https://law.counselstack.com/opinion/leon-stambler-v-rsa-security-inc-cafc-2005.