throbber
Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 1 of 109
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF PENNSYLVANIA
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IN RE: MAXIM INTEGRATED
`PRODUCTS, INC. MDL NO. 2354
`
`
`
`
`
`
`
`
`
`
`
`
`This Document Relates to: All Actions
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`


`§ Master Docket
`§ Misc. No. 12-244
`§ MDL No. 2354
`§ CONTI, District Judge



`
`
`
`
`
`SPECIAL MASTER’S REPORT AND RECOMMENDATION
`RE: CLAIM CONSTRUCTION
`
`
`
`
`
`This claim construction Report and Recommendation analyzes the disputed claim
`
`terms of United States Patent Nos. 5,805,702 (the “‘702 Patent”), 5,940,510 (the “‘510
`
`Patent”), 5,949,880 (the “‘880 Patent”), 6,105,013 (the “‘013 Patent”), and 6,237,095 (the
`
`“‘095 Patent”).1 Defendants collectively filed consolidated claim construction briefing
`
`(Defendants are referred to as Opposing Parties and referenced herein as “OPs”). A
`
`subset of OPs, Bank of the West, Comerica, Inc. and BMO Harris Bank National
`
`Association, filed a separate claim construction brief as to the term “certificate” (the
`
`subset is referred to as Joining Parties and referenced herein as “JPs”). Some claim
`
`disputes are only relevant to Defendants Starbucks and Groupon (collectively referenced
`
`herein as “S/G”), and the other OPs express no opinion regarding those terms. Citation
`
`herein is made to the briefing in the action numbered 2:12-mc-00244: Maxim’s Opening
`
`Brief (Dkt. 634), OPs’ Responsive Brief (Dkt. 642), Maxim’s Reply Brief (Dkt. 651),
`
`JPs’ Responsive Brief (Dkt. 680), Maxim’s Supplemental Brief as to “certificate” (Dkt.
`
`1 References to column and line numbers of the patents are made as ‘XXX Patent at col:line.
`
`
`
`1
`
`Page 1 of 109
`
`PNC-JP MORGAN EXHIBIT 1010
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 2 of 109
`
`686) and Maxim’s Supplemental Brief as to “packet” (Dkt. 687). A claim construction
`
`Oral Hearing was held on September 12, 2013.2 For the following reasons, the Special
`
`Master recommends the constructions set forth below.
`
`BACKGROUND
`
`
`
`The five patents-in-suit have priority dates in 1995 and 1996. The patents arose
`
`from the development by Dallas Semiconductor (the original assignee subsequently
`
`acquired by Maxim) of a product called the “iButton.” The iButton was a small portable
`
`fob type device. The iButton was a combination of hardware and firmware that allowed
`
`merchants, banks and other service providers to provide in a secure encrypted manner a
`
`mechanism for a user to perform a variety of secure transactions. One application of the
`
`transactions allowed the iButton user to store and transfer data that included “digital
`
`cash” so that goods and services could be purchased through the use of the iButton. The
`
`technologies asserted by Maxim to infringe include smartphones and software “apps.”
`
`
`
`The patents have various relationships. The ‘880 Patent is a divisional of the ‘510
`
`Patent. The ‘702 Patent, ‘013 Patent and ‘095 Patent all date back to a common
`
`provisional application filed September 29, 1995. The regular filing dates for each patent
`
`(either directly or through a parent application) all date to January 31, 1996. The ‘702
`
`Patent, ‘013 Patent and ‘095 Patent share a substantially similar specification. The ‘013
`
`Patent and ‘095 Patent incorporate by reference the ‘510 Patent. The ‘510 Patent and
`
`‘880 Patent incorporate by reference the ‘702 Patent.
`
`LEGAL STANDARDS
`
`Claim construction is a matter of law. Markman v. Westview Instruments, Inc., 52
`
`F.3d 967, 979 (Fed. Cir. 1995). The purpose of claim construction is to resolve the
`
`
`2 References to the Oral Hearing transcript are made as Tr. at xx.
`
`
`
`2
`
`Page 2 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 3 of 109
`
`meanings and technical scope of claim terms. U.S. Surgical Corp. v. Ethicon, Inc., 103
`
`F.3d 1554, 1568 (Fed. Cir. 1997). When the parties dispute the scope of a claim term, “it
`
`is the court’s duty to resolve it.” O2 Micro Int’l Ltd. v. Beyond Innovation Tech. Co., 521
`
`F.3d 1351, 1362 (Fed. Cir. 2008).
`
`“It is a ‘bedrock principle’ of patent law that ‘the claims of a patent define the
`
`invention to which the patentee is entitled the right to exclude.’” Phillips v. AWH Corp.,
`
`415 F.3d 1303, 1312 (Fed. Cir. 2005) (quoting Innova/Pure Water, Inc. v. Safari Water
`
`Filtration Sys., Inc., 381 F.3d 1111, 1115 (Fed. Cir. 2004)). The Court examines a
`
`patent’s intrinsic evidence to define the patented invention’s scope. Id. at 1313-14; Bell
`
`Atl. Network Servs., Inc. v. Covad Commc’ns Group, Inc., 262 F.3d 1258, 1267 (Fed. Cir.
`
`2001). Intrinsic evidence includes the claims, the rest of the specification, and the
`
`prosecution history. Phillips, 415 F.3d at 1312-13; Bell Atl. Network Servs., 262 F.3d at
`
`1267. The Court gives claim terms their ordinary and customary meaning as understood
`
`by one of ordinary skill in the art at the time of the invention. Phillips, 415 F.3d at 1312-
`
`13; Alloc, Inc. v. Int’l Trade Comm’n, 342 F.3d 1361, 1368 (Fed. Cir. 2003).
`
`Claim language guides the Court’s construction of claim terms. Phillips, 415
`
`F.3d at 1314. “[T]he context in which a term is used in the asserted claim can be highly
`
`instructive.” Id. Other claims, asserted and unasserted, can provide additional instruction
`
`because “terms are normally used consistently throughout the patent.” Id. Differences
`
`among claims, such as additional limitations in dependent claims, can provide further
`
`guidance. Id.
`
`“[C]laims ‘must be read in view of the specification, of which they are a part.’”
`
`Id. at 315 (quoting Markman, 52 F.3d at 979). “[T]he specification ‘is always highly
`
`
`
`3
`
`Page 3 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 4 of 109
`
`relevant to the claim construction analysis. Usually, it is dispositive; it is the single best
`
`guide to the meaning of a disputed term.’” Id. (quoting Vitronics Corp. v. Conceptronic,
`
`Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)); Teleflex. Inc. v. Ficosa N. Am. Corp., 299
`
`F.3d 1313, 1325 (Fed. Cir. 2002). In the specification, a patentee may define his own
`
`terms, give a claim term a different meaning that it would otherwise possess, or disclaim
`
`or disavow some claim scope. Phillips, 415 F.3d at 1316. Although the Court generally
`
`presumes terms possess their ordinary meaning, this presumption can be overcome by
`
`statements of clear disclaimer. See SciMed Life Sys., Inc. v. Advanced Cardiovascular
`
`Sys., Inc., 242 F.3d 1337, 1343-44 (Fed. Cir. 2001). This presumption does not arise
`
`when the patentee acts as his own lexicographer. See Irdeto Access, Inc. v. EchoStar
`
`Satellite Corp., 383 F.3d 1295, 1301 (Fed. Cir. 2004). “The person of ordinary skill in
`
`the art is deemed to read the claim term not only in the context of the particular claim in
`
`which the disputed term appears, but in the context of the entire patent, including the
`
`specification.” Phillips, 415 F.3d at 1313. Although the claims themselves may provide
`
`guidance as to the meaning of particular terms, those terms are part of “a fully integrated
`
`written instrument.” Id. at 1315 (quoting Markman, 52 F.3d at 978). Thus, the Phillips
`
`court emphasized the specification as being the primary basis for construing the claims.
`
`Id. at 1314-17.
`
`The specification may also resolve ambiguous claim terms “where the ordinary
`
`and accustomed meaning of the words used in the claims lack sufficient clarity to permit
`
`the scope of the claim to be ascertained from the words alone.” Teleflex, 299 F.3d at
`
`1325. For example, “[a] claim interpretation that excludes a preferred embodiment from
`
`the scope of the claim ‘is rarely, if ever, correct.’” Globetrotter Software, Inc. v. Elam
`
`
`
`4
`
`Page 4 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 5 of 109
`
`Computer Group Inc., 362 F.3d 1367, 1381 (Fed. Cir. 2004) (quoting Vitronics Corp., 90
`
`F.3d at 1583). But, “[a]lthough the specification may aid the court in interpreting the
`
`meaning of disputed language in the claims, particular embodiments and examples
`
`appearing in the specification will not generally be read into the claims.” Constant v.
`
`Advanced Micro-Devices, Inc., 848 F.2d 1560, 1571 (Fed. Cir. 1988); see also Phillips,
`
`415 F.3d at 1323.
`
`The prosecution history is another tool to supply the proper context for claim
`
`construction because a patentee may define a term during prosecution of the patent.
`
`Home Diagnostics Inc. v. LifeScan, Inc., 381 F.3d 1352, 1356 (Fed. Cir. 2004) (“As in
`
`the case of the specification, a patent applicant may define a term in prosecuting a
`
`patent”). The well established doctrine of prosecution disclaimer “preclud[es] patentees
`
`from recapturing through claim interpretation specific meanings disclaimed during
`
`prosecution.” Omega Eng’g Inc. v. Raytek Corp., 334 F.3d 1314, 1323 (Fed. Cir. 2003).
`
`“Indeed, by distinguishing the claimed invention over the prior art, an applicant is
`
`indicating what the claims do not cover.” Spectrum Int’l v. Sterilite Corp., 164 F.3d
`
`1372, 1378-79 (Fed. Cir. 1988) (quotation omitted). “As a basic principle of claim
`
`interpretation, prosecution disclaimer promotes the public notice function of the intrinsic
`
`evidence and protects the public’s reliance on definitive statements made during
`
`prosecution.” Omega Eng’g, Inc., 334 F.3d at 1324. However, the prosecution history
`
`must show that the patentee clearly and unambiguously disclaimed or disavowed the
`
`proposed interpretation during prosecution to obtain claim allowance. Middleton Inc. v.
`
`3M Co., 311 F.3d 1384, 1388 (Fed. Cir. 2002). Statements will constitute disclaimer of
`
`scope only if they are “clear and unmistakable statements of disavowal.” See Cordis
`
`
`
`5
`
`Page 5 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 6 of 109
`
`Corp. v. Medtronic Ave, Inc., 339 F.3d 1352, 1358 (Fed. Cir. 2003). An “ambiguous
`
`disavowal” will not suffice. Schindler Elevator Corp. v. Otis Elevator Co., 593 F.3d
`
`1275, 1285 (Fed. Cir. 2010) (citation omitted). Because the file history “represents an
`
`ongoing negotiation between the PTO and the applicant, rather than the final product of
`
`that negotiation, it often lacks the clarity of the specification and thus is less useful in
`
`claim construction proceedings.” Phillips, 415 F.3d at 1317. Nevertheless, the
`
`prosecution history is intrinsic evidence that is relevant to the determination of how the
`
`inventor understood the invention and whether the inventor limited the invention during
`
`prosecution by narrowing the scope of the claims. Id.
`
`The doctrine of claim differentiation provides that “different words or phrases
`
`used in separate claims are presumed to indicate that the claims have different meaning
`
`and scope.” Seachange Intl. Inc., v. C-COR, Inc., 413 F.3d 1361, 1368 (Fed. Cir. 2005)
`
`(citing Karlin Tech. Inc. v. Surgical Dynamics, Inc., 177 F.3d 968, 971-72 (Fed. Cir.
`
`1999)). However, the doctrine “only creates a presumption that each claim in a patent
`
`has a different scope; it is not a hard and fast rule of construction.” Id. at 1369 (quoting
`
`Kraft Foods, Inc. v. Int’l Trading Co., 203 F.3d 1362, 1368 (Fed. Cir. 2000)). The
`
`“claims cannot enlarge what is patented beyond what the inventor has described as the
`
`invention.” Abbott Labs. v. Sandoz, Inc., 566 F.3d 1282, 1288 (Fed. Cir. 2009) (citations
`
`omitted).
`
`Phillips rejected any claim construction approach that sacrificed the intrinsic
`
`record in favor of extrinsic evidence, such as dictionary definitions or expert testimony.
`
`The en banc court condemned the suggestion made by Texas Digital Systems, Inc. v.
`
`Telegenix, Inc., 308 F.3d 1193 (Fed. Cir. 2002) that a court should discern the ordinary
`
`
`
`6
`
`Page 6 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 7 of 109
`
`meaning of the claim terms (through dictionaries or otherwise) before resorting to the
`
`specification for certain limited purposes. Phillips, 415 F.3d at 1319-24. Still, though
`
`“less significant than the intrinsic record in determining the legally operative meaning of
`
`claim language,” the Court may rely on extrinsic evidence to “shed useful light on the
`
`relevant art.” Phillips, 415 F.3d at 1317 (quotation omitted). Technical dictionaries and
`
`treatises may help the Court understand the underlying technology and the manner in
`
`which one skilled in the art might use claim terms, but such sources may also provide
`
`overly broad definitions or may not be indicative of how terms are used in the patent. Id.
`
`at 1318. Similarly, expert testimony may aid the Court in determining the particular
`
`meaning of a term in the pertinent field, but “conclusory, unsupported assertions by
`
`experts as to the definition of a claim term are not useful.” Id. Generally, extrinsic
`
`evidence is “less reliable than the patent and its prosecution history in determining how to
`
`read claim terms.” Id.
`
`Patent claims must particularly point out and distinctly claim the subject matter
`
`regarded as the invention. 35 U.S.C. § 112, ¶ 2. Whether a claim meets this definiteness
`
`requirement is a matter of law. Young v. Lumenis, Inc., 492 F.3d 1336, 1344 (Fed. Cir.
`
`2007). A party challenging the definiteness of a claim must show it is invalid by clear
`
`and convincing evidence. Id. at 1345.
`
`
`
`“Only claims ‘not amenable to construction’ or ‘insolubly ambiguous’ are
`
`indefinite.” Halliburton Energy Servs., Inc. v. M-I LLC, 514 F.3d 1244, 1250 (Fed. Cir.
`
`2008) (quoting Datamize, LLC v. Plumtree Software, Inc., 417 F.3d 1342, 1347 (Fed. Cir.
`
`2005)). That is, the “standard [for finding indefiniteness] is met where an accused
`
`infringer shows by clear and convincing evidence that a skilled artisan could not discern
`
`
`
`7
`
`Page 7 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 8 of 109
`
`the boundaries of the claim based on the claim language, the specification, and the
`
`prosecution history, as well as her knowledge of the relevant art area.” Halliburton, 514
`
`F.3d at 1249-50. The ultimate issue is whether someone working in the relevant
`
`technical field could understand the bounds of a claim. Haemonetics Corp. v. Baxter
`
`Healthcare Corp., 607 F.3d 776, 783 (Fed. Cir. 2010).
`
`In determining whether that standard is met, i.e., whether the claims at
`issue are sufficiently precise to permit a potential competitor to determine
`whether or not he is infringing, we have not held that a claim is indefinite
`merely because it poses a difficult issue of claim construction. We engage
`in claim construction every day, and cases frequently present close
`questions of claim construction on which expert witnesses, trial courts,
`and even the judges of this court may disagree. Under a broad concept of
`indefiniteness, all but the clearest claim construction issues could be
`regarded as giving rise to invalidating indefiniteness in the claims at issue.
`But we have not adopted that approach to the law of indefiniteness. We
`have not insisted that claims be plain on their face in order to avoid
`condemnation for indefiniteness; rather, what we have asked is that the
`claims be amenable to construction, however difficult that task may be. If
`a claim is insolubly ambiguous, and no narrowing construction can
`properly be adopted, we have held the claim indefinite. If the meaning of
`the claim is discernible, even though the task may be formidable and the
`conclusion may be one over which reasonable persons will disagree, we
`have held the claim sufficiently clear to avoid invalidity on indefiniteness
`grounds. . . . By finding claims indefinite only if reasonable efforts at
`claim construction prove futile, we accord respect to the statutory
`presumption of patent validity . . . and we protect the inventive
`contribution of patentees, even when the drafting of their patents has been
`less than ideal.
`
`Exxon Research & Eng’g Co. v. U.S., 265 F.3d 1371, 1375 (Fed. Cir. 2001) (citations and
`
`internal quotation marks omitted).
`
`
`
`8
`
`
`
`Page 8 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 9 of 109
`
`DISPUTED CLAM TERMS
`
`1(a). “first data” (‘510 Patent claim 1) [No. 12]3
`
`Maxim
`plain meaning; if construction required; “a
`first/second data value”
`
`“first data” and “second data” (‘095 Patent claim 1) [No. 12]
`
`Maxim
`plain meaning; if construction required; “a
`first/second data value”
`
`
`OPs
`“data that includes a value datum”
`
`
`OPs
`“data that is used as money or its equivalent”
`
`The dispute centers upon whether the claims are limited to money based
`
`applications.
`
`Maxim
`
`
`
`Maxim asserts that the terms are used in the ‘095 Patent in the context of “a first
`
`data object” and “a second data object.” Maxim asserts that this references the use in the
`
`specifications of the term “data object” which means a data structure that can be used to
`
`hold a value. Dkt. 634 at 42 (citing ‘095 Patent at 17:5-8, 3:60-64 (“[t]hese objects 42
`
`include both data objects (encryption keys, transaction counts, money amounts, date/time
`
`stamps, etc.”) and…”), 17:45-19:46, 8:9-12 (“locked money object containing a given
`
`cash value”)). Maxim asserts that in context of the claims the objects are a specific value
`
`associated with a secure transaction, such as an amount of money paid or a number of
`
`credits that are being passed, stored or adjusted.
`
`
`
`At the Oral Hearing, Maxim emphasized that the ‘095 Patent was a divisional
`
`application from the ‘702 Patent. Maxim pointed out that that ‘702 Patent was subject to
`
`a restriction between Invention I “drawn to a method for adding a monetary equivalent to
`
`electronic equipment” and Invention II “drawn to a method for receiving and transmitting
`
`
`3 Claim term numbers refer to the numbers in the Joint Disputed Claim Terms Chart. Dkt. 677-1.
`
`
`
`9
`
`Page 9 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 10 of 109
`
`encrypted data.” ‘702 File History JX-2 244MAX001382. 4 Maxim notes that the
`
`applicants subsequently filed the ‘095 divisional patent and explicitly canceled all claims
`
`but the Invention II claims. ‘095 File History JX-10 244MAX000300. Maxim notes
`
`that the ‘095 Patent claim 1 merely recites “encrypted data” in the preamble and “first”
`
`and “second” data object in the claims, in conformance with the Patent Office restriction.
`
`Maxim asserts it is thus improper to limit the ‘095 Patent claims to the monetary
`
`embodiments that the Patent Office stated were different inventions. Maxim also points
`
`to the Abstract and Technical Field of the Invention of the ‘095 Patent as the Abstract
`
`states that the encryption technique can be used “so that money and other valuable data
`
`can be securely passed” and the Technical Field of the Invention states that the module
`
`can “provide at least secure data transfers or to authorize monetary transactions.” ‘095
`
`Patent at Abstract; 1:23-28. Further, Maxim notes that ‘095 Patent dependent claim 7
`
`states that “said first data object includes a base monetary amount and wherein said
`
`second data object includes a transaction monetary amount.” Maxim asserts that claim
`
`differentiation thus supports Maxim’s construction.
`
`
`
`Maxim asserts that “value datum” is not contained in the ‘095 or ‘510 Patent
`
`claims or specifications. Maxim notes that “value datum” is contained in the ‘880 Patent
`
`claim 1. Maxim asserts that OPs inclusion of “value datum” limits the object to units
`
`having value that can be exchanged for goods or services. Maxim asserts that such a
`
`construction excludes the “Software Authorization and Usage Metering” embodiment in
`
`which the data object is not limited to money. Dkt. 634 at 43 (citing ‘095 Patent at
`
`12:45-49).
`
`
`4 The file history citations are made to the Joint Exhibits utilized by the parties and referenced as JX-
`## and filed at Dkt. 634.
`
`
`
`10
`
`Page 10 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 11 of 109
`
`OPs
`
`OPs assert that the summary of invention of the ‘510 Patent limits the “present
`
`invention … for communicating a cash equivalent electronically to and from a portable
`
`module” and that the module can be “filled with electronic money.” ‘510 Patent at 1:59-
`
`67. OPs assert that the only “data” that is stored in the portable module in claim 1 is
`
`“first data,” and thus the first data most have units of value that can be exchanged like
`
`cash equivalents. Dkt. 642 at 11. OPs assert that the specification states that a data
`
`packet stored in the module have “value (monetary value)” (‘510 Patent at 7:21-27) and
`
`the data packet “could be referred to as a first data” (‘510 Patent at 7:36-39, Figure 4
`
`(encrypted data packet with “monetary value” is included in “data-one”)). OPs assert
`
`these passages establish lexicography.
`
`OPs also assert that all embodiments of the ‘510 Patent specification relate to
`
`electronic money or credit. Dkt. 642 at 12 (citing Example A (train fare) ‘510 Patent at
`
`7:14-8:29 and Example B (ATM withdrawal) ‘510 Patent at 8:31-9:16). OPs also assert
`
`that in prosecution the applicants emphasized that issued claim 1 “allows a user to carry
`
`the portable module and install digital money equivalents into the module.” ‘510 File
`
`History, JX-4 244MAX1122-23.
`
`
`
`OPs assert that the ‘095 Patent Technical Field of Invention states “the present
`
`invention relates to…transferring money or its equivalent electronically.” ‘095 Patent
`
`1:24-26. OPs contrast this with the ‘013 Patent Field of Invention which is not limited to
`
`transferring money. OPs assert this intentional differentiation of the two applications
`
`(which date to two different priority documents filed on the same date) indicates a
`
`different scope of the patents. Dkt. 642 at 13, n. 11. OPs assert that the only item
`
`
`
`11
`
`Page 11 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 12 of 109
`
`transferred in ‘095 Patent claim 1 is the “certificate including…a second data object.”
`
`Thus, OPs assert the second data object must be the money equivalent. OPs also assert
`
`that the “first data object” is adjusted according to the second data object, indicating that
`
`the first data object is also a money equivalent. Dkt. 642 at 13.
`
`
`
`OPs assert that the claims require (1) “a first memory for storing a first data
`
`object,” (2) “instructions” to “initiate generation of a certificate” including a “second data
`
`object,” and (3) instructions “to adjust said first data object according to said second data
`
`object.” OPs assert that only the money/value embodiments contain all three items. OPs
`
`correlate the steps as (1) a money register (“first memory”) for storing a money balance
`
`(“a first data object”), (2) generating a “certificate” include a payment or deposit amount
`
`(“the second data object”) and (3) adjusting the money balance in view of the payment or
`
`deposit. Dkt. 642 at 13-14 (providing extensive citations for each step).
`
`
`
`As to the alternative embodiments cited by Maxim, OP asserts those are not
`
`relevant as most of the embodiments do not include the three claimed steps – asserting
`
`that embodiments II.A (secure email – no certificates), II.B (Digital Notary – no data
`
`adjustment), II.J (subscription service – no certificates) and II.K (registry with key
`
`security – no data adjustment) are thus not relevant to the claim at issue. Dkt. 642 at 14-
`
`15, n. 15. As to embodiment II.G (software usage and metering), OPs assert that such an
`
`embodiment relates to units of time which are money equivalents and stored in a “money
`
`object” that is still exchangeable for services. Dkt. 642 at 14-15, n. 14 (citing ‘095 Patent
`
`at 12:45-47).
`
`
`
`12
`
`Page 12 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 13 of 109
`
`Maxim Reply
`
`
`
`Maxim asserts that the ‘095 Patent software usage embodiment is not limited to
`
`money but relates to units of time rather than the actual dollar amount. Maxim also
`
`cites to the Registry With Guaranteed Private Key Security example as stating that it is
`
`not used for money or its equivalent:
`
`The model described here is one in which the authority to perform
`financial transactions derives from the registry maintained by the Service
`Provider. It is therefore essential that this information be accurate and that
`the private key in the module 10 can be secure from all parties. Because
`each module 10 has its own unique RSA key set, there is not provision in
`this model for module 10 to represent money independently of the registry
`maintained by the Service Provider.
`
`‘095 Patent at 16:1-10. Maxim also objects that OPs provide two different constructions
`
`for “first data” in two closely related patents. Maxim cites caselaw indicating that such
`
`different constructions should not be used absent compelling reasons. Dkt. 651 at 16.
`
`Analysis
`
`
`
`With regard to the ‘095 Patent, the claims, the specification and the file history
`
`each support Maxim’s construction. As a starting point, the claims of the ‘095 Patent
`
`merely utilize the terminology “first data object” and “second data object.” It is only in a
`
`dependent claim (claim 7) that the object is explicitly recited as a monetary amount.
`
`Further, passages that OPs assert state “the Invention” is limited to monetary amounts
`
`provide such language in a permissive manner, identifying other data in addition to
`
`money. Thus, as noted above the Abstract states “money and other valuable data” and
`
`the Field of Invention states “provide at least secure data transfers or to authorize
`
`monetary transactions. ‘095 Patent at Abstract; 1:23-28. Further, in the specification
`
`“objects” are used more generally. ‘095 Patent at 3:60-63. In addition, the “Software
`
`
`
`13
`
`Page 13 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 14 of 109
`
`Authorization and Usage Metering” embodiment provides disclosure for objects which
`
`relate to software usage time, not limited to money. ‘095 Patent at 12:45-49. Finally, the
`
`divisional file history of the ‘095 Patent and its parent ‘702 Patent provide clear guidance
`
`that the claims of the ‘095 Patent are not limited to monetary equivalents. ‘702 File
`
`History JX-2 244MAX001382; ‘095 File History JX-10 244MAX000300.
`
`
`
`As to the ‘510 Patent, the claim term at issue arises in the context of “memory for
`
`storing a first data.” As with the ‘095 Patent, such language is more generalized than
`
`asserted by OPs. OPs’ assertion that as a matter of lexicography the patentees have re-
`
`defined “data” is not supported. A statement of lexicography must be clear. Intellicall,
`
`Inc. v. Phonometrics, Inc., 952 F.2d 1384, 1388 (Fed. Cir. 1992). Here OPs cite to a data
`
`packet stored in the module having “value (monetary value)” (‘510 Patent at 7:21-27) and
`
`the data packet “could be referred to as a first data” (‘510 Patent at 7:36-39). The
`
`statement that the data packet “could be” referred to as first data does not rise to the level
`
`of a clear statement of lexicography redefining “data.” OPs also assert that all of the
`
`disclosed embodiments are limited to monetary value and thus “data” must be limited to
`
`monetary value. However, even if only a single embodiment exists the preferred
`
`embodiment is not inherently required to be read into the claims. See Arlington
`
`Industries, Inc. v. Bridgeport Fittings, Inc., 632 F.3d 1246, 1254 (Fed. Cir. 2011) (“Even
`
`where a patent describes only a single embodiment, claims will not be read restrictively
`
`unless the patentee has demonstrated a clear intention to limit the claim scope using
`
`words or expressions of manifest exclusion or restriction.”) (internal citations omitted).
`
`Further, the ‘510 Patent incorporates by reference the ‘702 Patent. The ‘702 Patent
`
`includes a number of embodiments that involve transactions that are not limited to
`
`
`
`14
`
`Page 14 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 15 of 109
`
`monetary exchanges. For example secure email (‘702 Patent at 4:45-6:23), digital notary
`
`service (‘702 Patent at 6:25-7:50), Software Authorization and Usage Metering (‘702
`
`Patent at 12:30-13:5) and the Registry With Guaranteed Private Key Security (‘702
`
`Patent at 14:63-16:19) which discloses at 16:8-17 the concept of providing authority to
`
`perform financial transactions but the module itself does not “represent money
`
`independently of the registry maintained by the service provider.” Thus, even OPs ’
`
`single embodiment argument is contradicted by the specification. Finally OPs provide a
`
`file history argument. As to the File History statement, the Amendment cited as a whole
`
`does not limit the portable module as asserted by OPs. Note the Amendment starts be
`
`stating that the claim “claims a system for communicating data securely.” Then a long
`
`recitation of the claim elements is provided also without any description of money. ‘510
`
`File History JX-4 244MAX001122. Only then does the Amendment state that the system
`
`“allows a user” to use digital money. ‘Id. at 244MAX001122. When distinguishing the
`
`prior art the Amendment focuses on specific claim elements, again with no reference to
`
`money. Id. at 244MAX001123. The Amendment conclusion again focuses on merely
`
`communicating data securely with no money reference: “the present invention is an
`
`improvement over other systems
`
`for communicating data securely.”
`
`Id. at
`
`244MAX001123. When viewed in context of the entire Amendment, the one statement
`
`pulled out by OPs does not appear to be a disclaimer of the broader claim scope of the
`
`terms themselves and the broader statements provided elsewhere in the Amendment.
`
`Rather, the statement merely points to a usage that is allowed by the listed claimed
`
`structure and the Amendment focuses on those claim structures without limiting the claim
`
`to a monetary usage.
`
`
`
`15
`
`Page 15 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 16 of 109
`
`
`
`First data and second data as used in the ‘095 Patent claim 1 and first data as used
`
`in the ‘510 Patent claim 1 are not limited to money, monetary units or their equivalents.
`
`
`
`It is recommended that “first data” and “second data” have their plain
`
`meaning, no construction required.
`
`
`
`1(b). “units of exchange” and “value datum” (‘880 Patent claim 1) [No. 34]
`
`Maxim
`plain meaning; if construction required; “units
`of exchange”: not a limitation; “value datum”:
`“data representing a value for a data object.”
`
`
`OPs
`“units having value that can be exchanged as
`payment for goods and services”
`
`Maxim
`
`Maxim asserts that the plain meaning of “value datum” is value of data and that
`
`this conforms to the claim language which merely describes passing such data between
`
`various modules. Dkt. 634 at 51. Maxim asserts that OPs’ construction renders a
`
`construction that “value datum” must constitute legal tender itself, rather than a simple
`
`variable representing an amount of the same. Maxim asserts that OPs’ construction
`
`conflicts with the specification embodiments and Maxim states that value is “a
`
`representation of some unit of exchange – not a unit of exchange itself.” Dkt. 634 at 51.
`
`Maxim points to ‘880 Patent at 10:23-25: “may be used to represent money or some other
`
`form of credit.”
`
`Maxim also asserts that the ‘880 Patent embodiment describes that when a money
`
`register is loaded, “a register within the secure module may be decremented by the same
`
`amount.” ‘880 Patent at 8:65-9:2. Maxim asserts that the use of “may be” indicates that
`
`the register may be changed by a value that is not the “same amount” and thus indicates
`
`
`
`16
`
`Page 16 of 109
`
`

`

`Case 2:12-mc-00244-JFC Document 691 Filed 10/09/13 Page 17 of 109
`
`that value datum is simply “data representing a value for a data object,” not legal tender.
`
`Dkt. 634 at 52.
`
`
`
`Maxim asserts the same arguments are relevant to “units of exchange” and in
`
`addition the term is not a limitation as it is only found in the preamble and preambles are
`
`assumed not to be

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket