MICHAEL H. SCHNEIDER, UNITED STATES DISTRICT JUDGE.
The above entitled and numbered civil action was referred to United States Magistrate Judge K. Nicole Mitchell pursuant to 28 U.S.C. § 636. The Report and Recommendation of the Magistrate Judge ("R & R"), which recommends adoption of the Court's claim construction and denial of Defendants' Motions for Summary Judgment for Invalidity, has been presented for consideration (6:13cv447, Doc. No. 229; 6:13cv448, Doc. No. 270). Defendants filed objections (6:13cv447, Doc. No. 251; 6:13cv448, Doc. Nos. 303, 304) to the R & R.
Defendants' objections assert that the R & R violated the "Federal Circuit's clear directions" by not applying 35 U.S.C. § 112, ¶ 6 to apparatus claims reciting the word "processor." 6:13cv448, Doc. No. 304 at 2 (citing Aristocrat Techs. Austl. PTY Ltd. v. Int'l Game Tech., 521 F.3d 1328 (Fed.Cir.2008) (holding that under § 112, ¶ 6, a "control means" claim limitation was indefinite because the patent did not disclose an algorithm); Noah Sys. Inc. v. Intuit Inc., 675 F.3d 1302 (Fed.Cir.2012) (holding that under § 112, ¶ 6, an "access means" claim limitation was indefinite because the patent disclosed an algorithm that failed to enable one skilled in the art)); see also 6:13cv447 Doc. No. 251 at 5. Additionally, Defendants point out that the R & R did not address the Personal Audio case from this District that construed limitations reciting a "processor" as means plus function claims subject to § 112, ¶ 6. 6:13cv448, Doc. No. 304 at 2; 6:13cv447, Doc. No. 251 at 5; Personal Audio, LLC v. Apple, Inc., No. 9:09-cv-111, 2011 WL 11757163 (E.D.Tex. Jan. 30, 2011). The Court addresses Federal Circuit guidance on this issue and the Personal Audio case below.
Section 112, ¶ 6(now § 112(f)) allows a patentee to claim a "means or step for" a function without reciting structure to support that function, but the "claim shall be construed to cover the corresponding structure ... described in the specification and equivalents thereof." Accordingly, "[m]eans-plus-function claiming applies only to purely functional limitations that do not provide the structure that performs the recited function." Phillips v. AWH Corp., 415 F.3d 1303, 1311 (Fed.Cir. 2005). Thus, the court must first determine whether the limitation invokes § 112, ¶ 6. Rodime PLC v. Seagate Tech., Inc., 174 F.3d 1294, 1302 (Fed.Cir.1999). A limitation that actually uses the word "means" raises a rebuttable presumption that § 112, ¶ 6 applies. Lighting World, Inc. v. Birchwood Lighting, Inc., 382 F.3d 1354, 1358 (Fed.Cir.2004). By contrast, when a claim limitation lacks the term "means," it creates a rebuttable presumption that § 112, ¶ 6 does not apply. Id. "The use of the term `means' is `central to the analysis,' because the term `means,' particularly as used in the phrase `means for,' is `part of the classic template for functional claim elements,' and has come to be closely associated with means-plus-function claiming." Id. (internal citations omitted).
The presumption that § 112, ¶ 6 does not apply can be "overcome if the claim fails to recite sufficiently definite structure, or else recites function without sufficient structure for performing that
In computer implemented inventions, one of ordinary skill in the art can understand "structure" through an outline of an algorithm, a flowchart, or set of instructions or rules, rather than traditional physical structure. Id. (citing Typhoon Touch Techs., Inc. v. Dell, Inc., 659 F.3d 1376, 1385 (Fed.Cir.2011) ("[T]he patent need only disclose sufficient structure for a person of skill in the field to provide an operative software program for the specified function.")). Section 112, ¶ 6 will not apply to terms "used in common parlance of by persons of ordinary skill in the pertinent art to designate structure." Lighting World, 382 F.3d at 1359. Additionally, the Federal Circuit has held that terms such as "detector" and "circuit" are structural terms while generic terms such as "means," "element," and "device" are non-structural. Apple, 757 F.3d at 1299 (citing Personalized Media Commc'ns, LLC v. Int'l Trade Comm'n, 161 F.3d 696, 705 (Fed.Cir.1998); Apex Inc. v. Raritan Computer, Inc., 325 F.3d 1364, 1373 (Fed.Cir. 2003)). Even if a term covers a broad class of structures and identifies structures by their function, it is sufficient to avoid means-plus-function treatment. Lighting World, 382 F.3d at 1360. What is important is whether the term is understood to describe structure and is not simply a substitute for "means for." Id.
As a preliminary matter, in two cases cited by Defendants as providing clear directions to the Court, Aristocrat and Noah, the asserted claims included the term "means." There were no disputes that means-plus-function claim construction applied. Thus, neither case analyzed the presumption against the applicability of § 112, ¶ 6 where a claim does not recite "means."
In Aristocrat, the court determined that the specification's disclosure for "control means" of a standard microprocessor with appropriate programming did not sufficiently define the scope of the means-plus-function claim. 521 F.3d at 1331, 1338. Noting its clear applicability because the claim explicitly recited "means," the court applied § 112, ¶ 6, which requires the scope of the claim limitation to be defined by the structure disclosed in the specification plus any equivalents thereof. Id. at 1331. The court noted that "[i]n cases in which the inventor has invoked means-plus-function claiming, this court has consistently required that the structure disclosed in the specification be more than simply a general purpose computer or microprocessor." Id. at 1333. Additionally, the court stated that allowing the "patentee to claim a means for performing a particular function and then to disclose only a general purpose computer as the structure designed to perform that function amounts to pure functional claiming."
Defendants' argument essentially applies Aristocrat in reverse. Defendants argue that because "processor" does not adequately define the scope of a means-plus-function limitation, it also cannot describe sufficient structure to avoid means-plus-function treatment when recited in the claim itself. 6:13cv448, Doc. No. 304 at 2; see also Doc. No. 177-1 ¶¶ 38-45 (asserting "the identified claims fail[] to disclose sufficient structure" because "the identified claims do not disclose the specialized algorithms that would be required to enable a general purpose processor to perform any of the claimed high-level functions."). However, in light of the Federal Circuit's guidance in Apple, Defendants' reasoning fails; Aristocrat does not apply here, where the claim is not drafted in means-plus-function format. See 757 F.3d at 1298; see also Wi-Lan USA, Inc. v. Alcatel-Lucent USA, Inc., No. 12-23568-CIV, 2013 WL 4811233, at *40 (S.D.Fla. Sept. 9, 2013). The standard used to prove sufficient structure to avoid means-function-treatment is not identical to the standard for identifying corresponding structure to a means-plus-function claim. See 757 F.3d at 1298; see also Wi-Lan, 2013 WL 4811233, at *40-41. Similarly, Noah does not apply here because it also analyzes the adequacy the specification's disclosure for defining claim scope where a patentee has explicitly invoked means-plus-function claiming. 675 F.3d at 1314-18. It does not address the standard for overcoming the presumption against means-plus-function treatment. Id.
Defendants' expert report also fails to address the legal requirements for overcoming the presumption against means-plus-function treatment when the claims themselves do not recite the term "means." In fact, Defendants' expert begins with the presumption that the disputed claims contain "`means-plus-function' terms governed by 35 U.S.C. § 112, ¶ 6." Doc. No. 177-1 ¶ 38. Further, the report states that a processor "available for purchase during the relevant [] time period is designed to interpret and execute instructions that are provided to it as compiled machine code." Id. at ¶ 40. According to Defendants' expert, even a "general purpose processor" without specific instructions can perform "maintenance functions (like stopping, self-testing, or restarting.)"
Federal Circuit precedent requires only that the claim recite some structure. Lighting World, 382 F.3d at 1359-60. Although "processor" may not define a specific structure, it describes a class of structures. See Apple, 757 F.3d at 1300 (citing Personalized Media, 161 F.3d at 705 (finding that "detector" did not evoke particular structure but conveyed to one knowledgeable in the art the variety of structures known as "detectors"); Flo Healthcare Solutions, LLC v. Kappos, 697 F.3d 1367, 1374-75 (Fed.Cir.2012) (finding that "height adjustment mechanism" designates "a class of structures that are generally understood to persons of skill in the art")). Like "circuit" in Linear, "processor" is a structure-connoting term. See 379 F.3d at 1320. It is not a generic nonstructural term such as "means," "element," and "device" that typically do not connote sufficient structure. Apple, 757 F.3d at 1299-1300. As Defendants' expert noted, a processor can be purchased, can perform certain functions even without specific instructions, and has a design for interpreting and executing instructions. Thus, the term "processor," even on its own, recites at least some structure.
Moreover, the Court must not analyze the term "processor" on its own; limitations should be examined as a whole. See Wi-Lan, 2013 WL 4811233, at *42 (citing Apex, 325 F.3d at 1372). When a
In Personal Audio, another court in this District found that the strong presumption against means-plus-function treatment flowing from the absence of "means" had been rebutted. Personal Audio, 2011 WL 11757163, at *21-22. As in this case, the claim limitations recited a "processor." Id. However, the reasoning in Personal Audio relied heavily on Aristocrat. Id. Since Personal Audio, the Federal Circuit clarified that "where the claim is not drafted in means-plus-function format, the reasoning in the Aristocrat line of cases does not automatically apply, and an algorithm is not necessarily required." Apple, 757 F.3d at 1298. The Aristocrat reasoning applies where a patentee has expressly invoked means-plus-function claiming to determine whether the patentee has disclosed sufficient structure to define the scope of such a claim. Accordingly, the analysis of recited structure in Personal Audio differs from the Federal Circuit's guidance in Apple.
Moreover, Personal Audio differs further from this case. In Personal Audio, both asserted patents shared a common specification and nearly identical claims were at issue. 2011 WL 11757163, at *1-2, *21-22. The second-issued patent was a divisional of the first-issued patent. Id. at *1. The court noted that "[t]he claim terms at issue in the [second-issued] patent are nearly identical to the means-plus-function terms found in the [first-issued] patent, except that `means for' and `means responsive' have been replaced with "processor for" and "said processor responds." Id. at *21. Accordingly, there was support for finding that the "processer" terms did not describe structure and were simply a substitute for "means for," which overcame the presumption. See Lighting World, 382 F.3d at 1360. In this case, "processor" has not simply replaced "means" in otherwise identical claim language between asserted patents. Therefore, Personal Audio is even less persuasive in this situation.
The R & R's reasoning on the "processor" terms follows Federal Circuit precedent on the strong presumption against applying § 112 ¶ 6 where claims do not recite "means." Defendants cite case law instead addressing the adequacy the specification's disclosure for defining claim scope where a patentee has explicitly invoked means-plus-function claiming. Even though Personal Audio is from this District, it does not control here for the reasons above.
Having also made a de novo review of the other objections filed by Defendants, the Court finds that the findings, conclusions, and recommendation of the Magistrate Judge are correct and Defendants' objections are without merit. Therefore, the Court hereby
K. NICOLE MITCHELL, UNITED STATES MAGISTRATE JUDGE.
This Memorandum Opinion construes the disputed claim terms in United States Patent Numbers: (1) 7,334,720; (2) 7,942,317; (3) 8,033,458; (4) 8,061,598; (5) 8,118,221; and (6) 8,336,772. Also before the Court are Defendants Apple, Inc., Robot Entertainment, Inc., KingIsle Entertainment, Inc., Samsung Electronics Co., Ltd., Samsung Electronics America, Inc., Samsung Telecommunications America, LLC, HTC Corporation, HTC America, Inc., Exedea, Inc. and Game Circus LLC's (collectively "Defendants") Motions for Summary Judgment of Indefiniteness (6:13-cv-447 Doc. No. 161 & 6:13-cv-448 Doc. No. 177) ("Motions for Summary Judgment"). On July 17, 2014, the parties presented arguments on the disputed claim terms and the Motions for Summary Judgment at the Markman hearing. For the reasons discussed below, the Court resolves the claim term disputes as stated below and recommends that Defendants' Motions for Summary Judgment of Indefiniteness be
On May 29, 2013, Plaintiffs Smartflash LLC and Smartflash Technologies Limited (collectively "Smartflash") filed two separate actions, one against Defendants Apple, Inc., Robot Entertainment, Inc., KingIsle Entertainment, Inc., and Game Circus LLC (6:13-cv-447), and one against Defendants Samsung Electronics Co., Ltd., Samsung Electronics America, Inc., Samsung Telecommunications America, LLC, HTC Corporation, HTC America, Inc., Exedea, Inc. and Game Circus LLC (6:13-cv-448). Smartflash alleges Defendants infringe the following patents: U.S. Patent No. 7,334,720; U.S. Patent No. 7,942,317; U.S. Patent No. 8,033,458; U.S. Patent No. 8,061,598; U.S. Patent No. 8,118,221; and U.S. Patent No. 8,336,772. All patents are titled "Data Storage and Access Systems." The patents-in-suit all stem from a common specification and share a common written description and figures. In the interest of simplicity,
"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-1314; 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, 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. (quoting Markman v. Westview Instruments, Inc., 52 F.3d 967, 979 (Fed.Cir.1995)). "[T]he specification `is always highly 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 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, Inc., 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. Elan 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
Although, "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.
The patent in suit may contain means-plus-function limitations that require construction. Where a claim limitation is expressed in means-plus-function language and does not recite definite structure in support of its function, the limitation is subject to 35 U.S.C. § 112 ¶ 6. Braun Med., Inc. v. Abbott Labs., 124 F.3d 1419, 1424 (Fed.Cir.1997). In relevant part, § 112 mandates that "such a claim limitation be construed to cover the corresponding structure ... described in the specification and equivalents thereof." Id. (citing 35 U.S.C. § 112 ¶ 6.). Accordingly, when faced with means-plus-function limitations, courts "must turn to the written description of the patent to find the structure that corresponds to the means recited in the [limitations]." Id.
Construing a means-plus-function limitation involves two inquiries. The first step requires "a determination of the function of the means-plus-function limitation." Medtronic, Inc. v. Advanced Cardiovascular Sys., Inc., 248 F.3d 1303, 1311 (Fed. Cir.2001). Once a court has determined the limitation's function, "the next step is to determine the corresponding structure disclosed in the specification and equivalents thereof." Medtronic, 248 F.3d at 1311. A structure is corresponding "only if the specification or prosecution history clearly links or associates that structure to the function recited in the claim." Id. Moreover, the focus of the corresponding structure inquiry is not merely whether a
"Summary judgment is appropriate in a patent case, as in other cases, when there is no genuine issue as to any material fact and the moving party is entitled to judgment as a matter of law." Nike, Inc. v. Wolverine World Wide, Inc., 43 F.3d 644, 646 (Fed.Cir.1994); FED. R. Cw. P. 56(c). The moving party bears the initial burden of "informing the district court of the basis for its motion" and identifying the matter that "it believes demonstrate[s] the absence of a genuine issue of material fact." Celotex Corp. v. Catrett, 477 U.S. 317, 323, 106 S.Ct. 2548, 91 L.Ed.2d 265 (1986). If the moving party meets this burden, the nonmoving party must then set forth "specific facts showing that there is a genuine issue for trial." FED. R. Civ. P. 56(c), see also T.W. Elec. Serv., Inc. v. Pacific Elec. Contractors Ass'n, 809 F.2d 626, 630 (9th Cir.1987).
A party seeking to invalidate a patent must overcome a presumption that the patent is valid. See 35 U.S.C. § 282; Microsoft Carp. v. i4i Ltd. P'ship, ___ U.S. ___, 131 S.Ct. 2238, 2243, 180 L.Ed.2d 131 (2011); United States Gypsum Co. v. National Gypsum Co., 74 F.3d 1209, 1212 (Fed.Cir.1996). This presumption places the burden on the challenging party to prove the patent's invalidity by clear and convincing evidence. Microsoft, 131 S.Ct. at 2243; United States Gypsum Co., 74 F.3d at 1212. Close questions of indefiniteness "are properly resolved in favor of the patentee." Datamize, LLC v. Plumtree Software, Inc., 417 F.3d 1342, 1348 (Fed.Cir.2005); Exxon Research & Eng'g Co. v. United States, 265 F.3d 1371, 1380 (Fed.Cir.2001).
Claims must particularly point out and distinctly claim the invention. "The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention." 35 U.S.C. § 112 ¶ 2. The primary purpose of the requirement of definiteness is to provide notice to those skilled in the art of what will constitute infringement. See United Carbon Co. v. Binney Co., 317 U.S. 228, 236, 63 S.Ct. 165, 87 L.Ed. 232 (1942). The definiteness standard is one of reasonableness under the circumstances, requiring that, in light of the teachings of the prior art and the invention at issue, the claims apprise those skilled in the art of the scope of the invention with a reasonable degree of precision and particularity. See Shatterproof Glass Corp. v. Libbey-Owens Ford Co., 758 F.2d 613, 624 (Fed.Cir.1985). To rule "on a claim of patent indefiniteness, a court must determine whether one skilled in the art would understand what is claimed when the claim is read in light of the specification." Bancorp. Servs., L.L.C. v. Hartford Life Ins. Co., 359 F.3d 1367, 1372 (Fed.Cir.2004). "A determination of indefiniteness is a legal conclusion that is drawn from the court's performance of its duty as the construer of patent claims, [and] therefore, like claim construction, is a question of law." Atmel Corp. v. Info. Storage Devices, Inc., 198 F.3d 1374, 1378 (Fed.Cir. 1999).
The parties have agreed to the construction of one term. Doc. No. 180 at 6.
Claim Terms Agreed Claim Construction Supplementary data Advertising data customer reward Management data, and or hot links to web sites
In view of the parties' agreements on the proper construction of this term, the Court
Smartflash's Proposed Construction Defendants' Proposed Construction "Data that can be used to make payment for "data, distinct from access control data and content" user identity data, representing either actual payment made or record of payment made for requested content data"
The parties dispute two key issues: (1) whether "payment data" makes payments or represents payments; and (2) whether "payment data" is distinct from other forms of data.
Smartflash proposes that "payment data" is merely any data that can be used to pay for content. Smartflash argues that the patents-in-suit make it clear that the purpose of "payment data" is to make payments, not to represent a payment that has been made. Opening Brief at 5. Smartflash relies on Figure 12c, which diagrams a process beginning with "payment data for making a payment." Id. at 5 (citing '720 21:15-21:16). Smartflash argues that Defendants' construction is inappropriate because it would make certain claims nonsensical. Id. For example, Claim 30 of the '772 patent requires a device to transmit payment data for an item in response to a user selection for the item. '772 at 31:19-26. According to Smartflash, Defendants' construction would mean this claim requires a user to pay for an item before even selecting it. Opening Brief at 5. Smartflash also contends that "access control data" or "user identity data" may act as payment data if either is used to pay for content. Id. at 6.
Defendants contend that "payment data" can only be one of two things: (1) data representing an actual payment; or (2) data recording such payment. Apple Resp. at 2-3. In support, Defendants point to specification language stating, "payment data received may either be data relating to an actual payment made to the data supplier or it may be a record of a payment made ...." Id. at 2 (citing '720 Patent at 6:58-63). Defendants argue that their proposal is not nonsensical because it is not limited to prior payments. Id. at 3. According to Defendants, their construction only requires that "payment data" reflect actual payment, whether past or present. Id. Thus the claim language would not be nonsensical because payment would only be made after a user selects the content. Id. Additionally Defendants argue that "[t]he specification consistently describes `payment data' as being distinct from access control data and user identity data." Samsung Resp. at 3-4.(citing '720 Patent at 4:31-33 & 17:62-18:5). According to Defendants, "access control data" and "user identity data" are independent of "payment data" and thus, may be used to access payment data, which is the only type of data the patents ever describe as being "used to pay for content." Samsung Resp. at 4-5 (citing '720 Patent at 5:30-33 & 14:57-61).
The specification discloses using payment data to "make a payment" through
Defendants' proposal also seeks to import a negative limitation into the construction of "payment data" that would exclude "user identity data" and "access control data." As Defendants note, the Summary of the Invention discusses "payment data" and "identification data" in relation to one another. '720 Patent at 4:31-33 ("The payment data will normally be linked to a card or card holder identification data for payment by the card holder."). Statements that describe the invention as a whole, rather than preferred embodiments, are more likely to support a limiting definition of a claim term. C.R. Bard, Inc. v. U.S. Surgical Corp., 388 F.3d 858, 864 (Fed.Cir.2004). This type of statement is more likely to be found in certain sections of the specification, such as the Summary of the Invention. Id.
Turning to the claims of the patent, Claim 30 of the '772 patent is representative and states:
'772 Patent at 30:65-31:7 & 31:22-29 (emphasis added). Claim 30 does not refer to user identification data, nor does it preclude "payment data" from being user identification data.
In support of their argument, Defendants cite to Claim 12 of the '598 Patent, which does recite both "payment data" and "identification data":
The recitation of both "payment data" and "identification data" in the same claim suggests that these terms do refer to different, distinct data. See Becton, Dickinson & Co. v. Tyco Healthcare Group, LP, 616 F.3d 1249, 1254 (Fed.Cir.2010) ("Where a claim lists elements separately, the clear implication of the claim language is that those elements are distinct components of the patented invention.") (citations and internal quotation marks omitted). However, Claim 12 of the '598 Patent also suggests that identification data itself may be used for payment. This reading is consistent with the claims from which Claim 12 depends, such as Claim 8. Claim 8 recites:
'598 Patent at 26:29-33.
Given this claim language, Defendants' proposed negative limitation is not warranted. Similarly, Defendants' proposal that "payment data" can only represent "actual payment made or record of payment made" is too narrow. The specification and cited claim language uses payment data broadly to refer to whatever data is being used "for making a payment." '720 Patent at 21:15; '598 Patent at Cl. 8. Accordingly,
Smartflash's Proposed Construction Defendants' Proposed Construction
No construction necessary "system to validate payment data and authorize
payment"
alternatively:
"system that returns payment validation data in
response to valid payment data"
The parties agree that the "payment validation system" is a system that validates payment data. The parties dispute whether "payment validation system" should have the additional limitation that it authorizes payment.
Smartflash argues that the claim language is clear and that no construction is necessary. Opening Brief at 7. Smartflash contends that Defendants' proposal would exclude certain embodiments. Id. at 7-8. According to Smartflash, Defendants' construction relies on certain embodiments in the specification where a user device transfers payment data to a data supplier that relies on a third party payment authority to process and authorize the payment. Id. at 8 (citing '720 Patent at 11:66-12:4). Smartflash argues that other portions of the specification directly contradict this construction because "payment validation system" is also used to refer to a system that validates payment data without performing the additional functions of a banking process system. Id. (citing '720 Patent at 13:53-13:62).
Defendants contend that the specification teaches that the "payment validation data" both validates and authorizes payment. Apple Resp. at 5 (citing '720 Patent at 8:21-23). Defendants argue that this is the only portion of the specification that describes the role of the "payment validation system." Id. According to Defendants, their construction only requires that the payment validation system be capable of validating payment data and authorizing payment in response to receipt of payment data, thus infringement is not tied to a particular use as Smartflash contends. Id. at 6-7 (citing Nazomi Commc'ns, Inc. v. Nokia Corp., 739 F.3d 1339, 1344 (Fed.Cir. 2014)). Defendants argue that this is consistent with the inventors' stated goal of reducing data piracy by "binding the data access and payment together." Samsung Resp. at 5 (citing '720 Patent at 1:66-2:3).
The Summary of the Invention states:
'720 Patent at 1:62-2:3, 8:21-25 & 8:64-9:2 (emphasis added).
Smartflash is correct that "[t]he fact that a patent asserts that an invention achieves several objectives does not require that each of the claims be construed as limited to structures that are capable of achieving all of the objectives." See Liebel-Flarsheint Co. v. Medrad, Inc., 358 F.3d 898, 908 (Fed.Cir.2004). Indeed, the specification also discloses e-payment systems where payment authentication is performed at a later stage. See '720 Patent at 23:22-33 ("[p]ayment may be made directly to the system owner, and either concurrently with the content access and download process, or at some later stage ....") (emphasis added). In such a system, the content supplier could "validate" the payment by allowing a purchase on credit, with actual payment to occur at a later time. Thus, the specification is not as clear as Defendants have argued. Indeed the specification disclosure of "validating the data and authorizing the payment" suggests that "authorizing" is distinct from "validating." See '720 Patent at 8:21-25.
However, Smartflash's proposed construction is not complete. The payment validation system is not limited to returning data in response to only valid payment data. The system must return whatever data results from an attempt to validate payment data. See '772 Patent at Claim 30 ("code to receive payment validation data defining if said payment validation system has validated payment for said selected at least one content data item"). The purpose of a validation system would be moot if it only worked when valid payment data was sent. Accordingly,
Smartflash's Proposed Construction Defendants' Proposed Construction
No construction necessary "data received from payment validation system
representing that payment was authorized for
Alternatively: requested content data"
"data indicating that payment data is valid"
The dispute for this term is similar to the previous dispute for "payment validation system." Smartflash argues that "payment validation data" is data returned from a payment validation system indicating that payment data is valid. Opening Brief at 11. Smartflash contends that "payment validation data" is not required
Defendants' construction requires that the "payment validation data" represent that payment data was both validated and authorized. Defendants rely on the same arguments discussed previously for "payment validation system." See Apple Resp. at 5-7; Samsung Resp. at 5-8. Thus, if the "payment validation system" must authorize the payment data, then the "payment validation data" must represent that authorization.
As previously discussed, the parties' constructions for this term are too narrow. See '772 Patent Claim 30 ("code to receive payment validation data defining if said payment validation system has validated payment for said selected at least one content data item."). Thus, "payment validation data" is merely data received from a payment validation system and relates to whether a payment has been validated. Such a construction would add little clarity to the plain language of the term. Accordingly,
Smartflash's Proposed Construction Defendants' Proposed Construction
No construction necessary Each of (1) "content data memory," "data
memory," "memory ... for storing data," and
These terms do not require "physically "memory configured to store ... content" is
separate" memories physically separate from each of (2)
"parameter memory" and "use rule memory"
These terms all deal with types of memory for storing content. Smartflash contends that these "memory" terms do not need to be construed because the plain and ordinary meaning is sufficient. Opening Brief at 12. According to Smartflash, "the mere fact that some claims use two different phrases to identify required memory does not imply that those claims require `physically' separate memories" because a single component may satisfy multiple elements of a claim. Id. at 13 (citing Cannon Rubber Ltd. v. First Years, Inc., 163 Fed. Appx. 870, 877 (Fed.Cir.2005) & Intellectual Property Development, Inc. v. UA-Columbia Cablevision, 336 F.3d 1308, 1320 n.9 (Fed.Cir.2003)). Smartflash argues that many of the asserted claims recite memory used to store different things, but that none of the claims require the memories be "physically separate." Id. at 12-13. Smartflash contends that Defendants' argument is flawed because the claims in the '772 Patent require "non-volatile memory configured to store multimedia content," but do not require any "parameter memory" or "use rule memory." Id. at 13. Thus, according to Smartflash, Defendants' construction would require that "parameter memory" and "use rule memory" be physically separate from the claimed memory, even though "parameter memory" and "use rule memory" are not actually required by the claims. Id.
Defendants respond that the use of the conjunction "and" in a claim indicates that an inventor intended to claim distinct, separate components. Apple Resp. at 16 (citing TIP Sys., LLC v. Phillips & Brooks/Gladwin, Inc., 529 F.3d 1364, 1375-76 (Fed.Cir.2008) & Gaus v. Conair Corp., 363 F.3d 1284, 1288 (Fed.Cir.2004)).
Distinctly recited limitations are usually interpreted as distinct structures. See Becton, 616 F.3d at 1254 ("Where a claim lists elements separately, the clear implication of the claim language is that those elements are distinct components of the patented invention.") (citations and internal quotation marks omitted). The specification discloses distinct memory structures. See '720 Patent at 17:40-42, 18:8-10, & 18:18-20. Likewise, Figure 9 in the specification illustrates the "content data memory 214" and "non-volatile data memory 218" separately.
Defendants rely on the prosecution history to argue that these distinct memories must also be "physically separate." The patentee's statements regarding the Hiroya prior art reference are as follows:
Doc. No. 160, Ex. G, 2/6/2007 Amendment at 2 & 9-10 (emphasis and formatting modified). Defendants interpret these statements as applicant arguing that content data being stored in a separate chip is what distinguishes it from the prior art.
Reading the statements in their entirety, the applicant was not arguing that the content data must be physically separate from other data. Instead, the applicant relied on evaluating "separate use data" according to use rules. The applicant contrasted the invention with the electronic ticket information of Hiroya, which was validated by an electronic signature, not use rules. The applicants' remarks do not rise to the level of "definitive statements" or a "clear and unmistakable" disclaimer that warrants importing Defendants' limitation. See Omega Eng'g, Inc. v. Raytek Corp., 334 F.3d 1314, 1324 (Fed.Cir.2003) ("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.") (emphasis added); see also SanDisk Corp. v. Memorex Prods., Inc., 415 F.3d 1278, 1286-87 (Fed.Cir.2005) ("There is no `clear and unmistakable' disclaimer if a prosecution argument is subject to more than one reasonable interpretation, one of which is consistent with a proffered meaning of the disputed term.") (citations and internal quotation marks omitted).
Additionally, Defendants rely on corporate documents created by Smartflash's predecessor that refer to a "Smartflash card" with a "second flash memory chip which can store downloaded music." Apple Resp. at 13 (quoting Ex, K at
Smartflash's Proposed Apple's Proposed Construction Sainsong's Proposed
Construction Construction
No construction necessary "Removable smart card or "A removable smart card
integrated circuit (IC) card, or integrated circuit (IC)
Alternatively: distinct from data access card, distinct from a data
"Medium capable of storing terminal, data access device, and access device, a handheld
information" handheld multimedia terminal, multimedia terminal and
having two or more separate a data access terminal,
nonvolatile memories, for storing incorporating a processor
both payment data and content and two or more separate
data" nonvolatile memories for
storing both payment data
and content data"
The dispute over "data carrier" is whether the data carrier can be a general data storage medium, as Smartflash proposes, or whether it must be a smart card or integrated circuit card.
Smartflash believes no construction is necessary for "data carrier." Smartflash argues that Defendants' proposals improperly import new limitations into the claims. Opening Brief at 17 (citing Phillips, 415 F.3d at 1324-27, 1329-30). According to Smartflash, some, but not all, embodiments of a data carrier are removable smart cards or IC cards. Id. at 18. In support, Smartflash cites to portions of the specification it contends disclose data carriers integrated with other apparatuses. Id. (citing '720 Patent at 16:6-10). Additionally, Smartflash argues that the "data carrier" does not require separate non-volatile memories for the same reasons as the previous "memory" terms. Opening Brief at 20. Finally, Smartflash contends that the construction should not define what must be stored on all data carriers because each claim specifies what must be on the carrier. Id. at 21.
Defendants respond that the patents' descriptions and embodiments uniformly describe the "data carrier" as a removable smart card or IC card. Apple Resp. at 7. Defendants also note that Smartflash has proposed that another disputed term — "the card" — be construed to mean "the data carrier." Id. at 8. In support of their proposal to require separate memories, Defendants argue that "applicants expressly disclaimed a data carrier with only
The first issue is whether to require a "removable smart card." The Summary of the Invention states:
'720 Patent at 6:17-31 (emphasis added); see id. at 4:62-64 ("use rules may be linked to payments made from the card ....") (emphasis added). Defendants are correct that consistent usage of a claim term in a particular manner could warrant a narrower construction than would otherwise be appropriate based on the claim language. AstraZeneca LP v. Apotex, Inc., 633 F.3d 1042, 1052 (Fed.Cir.2010) ("[W]hen a patentee uses a claim term throughout the entire patent specification, in a manner consistent with only a single meaning, he has defined that term by implication.").
The specification does disclose a "portable data carrier (30)" that is illustrated as a card in Figure 2 and states that it is "based on a standard smart card...." '720 Patent at 11:36-40. The same paragraph refers to the "card (30)" using the same numeral (30) that the specification used to refer to the data supplier. Id. at 11:40. Thus, "data carrier" and "card" are used interchangeably to some degree. However, the specification refers to "a data carrier or smart Flash card." See '720 Patent at 18:55-58 ("FIGS. 11a and 11b show a flow diagram of a process for registering a data carrier or smart Flash card with a data supplier or system owner operating a data supply system as illustrated in FIG. 6.") (emphasis added). The usage of "or" could either imply that "data carrier" and "smart Flash card" are synonyms, or that a "data carrier" can be something broader than a smart card.
Additionally, the specification also shows that "data carrier" need not be removable. '720 Patent at 16:1-10 ("In most embodiments of the terminal the SFC interface allows the smart Flash card data carrier to be inserted into and removed from the terminal, but in some embodiments the data carrier may be integral with the terminal.") (emphasis added); see id. at 4:42-43 ("the data carrier may also be integrated into other apparatus, such as a mobile communications device.") (emphasis added). An integrated data carrier would be contrary to the idea of a removable card.
Considering the specification in its entirety, Defendants' proposed construction would improperly limit "data carrier" to a preferred embodiment. See Constant v. Advanced Micro-Devices, Inc., 848 F.2d 1560, 1571 (Fed.Cir.1998) ("Although 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."). None of the extrinsic evidence offered by Defendants warrants limiting the generic term "data carrier" to the specific physical structure of a removable card.
Although Smartflash contends that no construction is necessary, "data carrier" will be construed so as to clarify that the "carrier" portion of the term does not refer to a signal carrier wave, such as for wireless communications. Accordingly,
Smartflash's Proposed Apple's Proposed Construction Samsung's Proposed
Construction Construction
No construction necessary "Removable smart card or "A removable smart card
integrated circuit (IC) card that or integrated circuit (IC)
Alternatively: interfaces with a variety of card, distinct from a data
"Portable medium capable of devices, distinct from data access access device, a handheld
storing information" terminal, data access device, and multimedia terminal and a
handheld multimedia terminal, data access terminal,
having two or more separate incorporating a processor
nonvolatile memories, for storing and two or more separate
both payment data and content nonvolatile memories for
data" storing both payment data
and content data that
interfaces with a variety
of devices"
The dispute over this term is similar to the dispute over the "data carrier" term. The key difference is the dispute over the term portable. Smartflash contends that the word "portable" is commonly understood and thus does not need to be construed. Opening Brief at 22.
The Apple Defendants respond that the specification equates portability with the ability to interface with a variety of devices." Apple Resp. at 14-15 (citing '720 Patent at 6:26-31). The Samsung Defendants contend that "data carrier" and "portable data carrier" are used synonymously throughout the patents. Samsung Resp. at 20 (citing '720 Patent at 8:10-15, 9:61-63, 10:66, 11:36, 16:4, & 16:7-8). Alternatively, the Samsung Defendants agree with the Apple Defendants that the only difference between a "data carrier" and a "portable data carrier" is that a "data carrier" is a removable card that interfaces with a single or dedicated device, whereas a "portable data carrier" can interface with a variety of devices. Samsung Resp. at 21.
The Summary of the Invention refers to portability as allowing the data carrier to "access content or, in the example, play music without the need to be linked to a communications system or to be on-line to the internet." '720 Patent at 5:12-15. Additionally, it states that the "`memory stick' format may be used .... [to] provide[] a small and convenient portable format [that] facilitates removable interfacing with a variety of devices." Id. at 6:17-31 (emphasis added). These disclosures don't warrant giving "portable" a special meaning beyond its ordinary meaning of being readily moveable. See Constant, 848 F.2d
Smartflash's Proposed Construction Defendants' Proposed Construction
No construction necessary "Rule/data, associated with a separately stored
content data item, indicating permissible use of
Alternatively: the content data item"
"Regulation (or rule) related to the use of
content"
Smartflash's Proposed Construction Defendants' Proposed Construction
No construction necessary Rule, associated with a separately stored
content data item, specifying under what
Alternatively: conditions a user is allowed access to the
Regulation (or rule) related to access to content content data item
Smartflash contends that there is no basis in the patents or prosecution history for the proposition that "use rules" or "access rules" must be "physically separate" from content. Opening Brief at 24. Smartflash argues that there was no clear disavowal in the in the prosecution history, and that any disavowal would not apply to different claim terms appearing in later continuation applications. Id. at 25. Smartflash contends that Defendants' proposed "indicating permissible use ..." and "specifying under what conditions ..." limitations are taken directly from certain claims and placed into the claim term definitions. Id. at 26. According to Smartflash, this would force language into other claims where it would not make sense. Id.
For "access rule(s)," Defendants respond that the applicant argued that access rules and content data were written in physically separate memories in order to overcome Hiroya. Apple Resp. at 21. Defendants contend that their construction "aligns with the teachings of the patent to explain that these `access rules' are used to control access to specific content data items...." Id. (citing '720 Patent at 7:31-33 & 23:59-24:8.).
Defendants argue that their proposed construction for the "use rule(s)" terms, use both the specification' disclosures and the applicant's statements to the PTO to assist the jury's understanding of the terms. Apple Resp. at 21. According to Defendants, the applicant "specifically disclaimed being able to read `use status data' and `use rules' from anything but a memory that is physically separate from the content memory." Id. at 22.
For the reasons previously discussed for the "memory" terms, Defendants' proposal of requiring "separately stored content" is rejected.
Once the separately stored issue is resolved, Smartflash's alternative proposals for these terms are very similar to Defendants' proposals. Both constructions are supported by the specification, which states that "[t]he carrier may ... store content use rules pertaining to allowed use
This intrinsic evidence shows that the disputed terms are being used in accordance with their plain and ordinary meaning. Further construing the terms would only lead to confusion instead of clarification. Accordingly,
Smartflash's Proposed Construction Defendants' Proposed Construction
No construction necessary "data, associated with a separately stored
content data item, indicating past use of the
Alternatively: content data item"
"indication of use status"
Smartflash argues that "use status data" need not be stored separately from content for the same reasons it set forth in the "use rules" terms above. Opening Brief at 27. Smartflash also contends that Defendants' construction is incorrect because it would limit asserted claims to only covering use rules that rely on tracking the past use of a content data item. Id.
Defendants respond that the patent makes it clear that "use status data" indicates "past use of stored data." Apple Resp. at 23 (citing '720 Patent at 9:35-38). Defendants cite to an embodiment of Claim 1 where a user's past use of a content item is compared with a specific use rule. Id. (citing '720 Patent Claim 1(c)).
For the same reasons discussed in the "memory" terms, Defendants' proposed requirement of "separately stored content" is rejected.
As to the issue of whether "use status data" should be limited to "indicating past use," the Summary of the Invention states:
'720 Patent at 9:35-38 (emphasis added). The specification also refers to "use status data" being updated after content has been accessed. Id. at 25:51-56 ("Once play is complete the process moves to step S85 where updated content use data is written to the smart Flash card.... This record can then be used in steps S81 and S83 to determine, on a subsequent occasion, whether further use of the content data item is permitted.") (emphasis added). However, Smartflash cites to portions of the specification it contends refer to use status data in situations other than past use. For example, the specification states that:
Id. at 4:59-5:3 (emphasis added); id. at 3:17-18 ("access to part of the data set might thereafter be controlled by payments made by a user at a later stage"). The specification also provides for rules that "could provide access for, say, one month from the download date" or "unlimited plans but only on specified players, for example set top boxes owned by a particular cable TV network ...." Id. at 23:59-24:2 (emphasis added). Defendants contend that these disclosures refer to "content use rules" and "content access rules" rather than "use status data." However, these rules must be applied to something in order to be operative. The claims show that the rules are applied to use status data. For example, Claim 1 of the '720 Patent recites: "reading the use status data and use rules from the parameter memory that pertain to use of the at least one requested content item; / evaluating the use status data using the use rules to determine whether access to the at least one requested content item stored in the content memory is permitted." Given this context, and the disclosures cited by Smartflash, "use status data" is not limited to only past use. Defendants' proposed construction would improperly limit the disputed term to particular embodiments. Accordingly,
Smartflash's Proposed Construction Defendants' Proposed Construction No construction necessary indefinite Alternatively: "code to evaluate use status data and use rules to determine whether access is permitted to second selected one or more items of retrieved multimedia content items"
Smartflash contends that the antecedent basis for this term is "code to evaluate said use data and use rules to determine whether access is permitted to said second selected one or more items of retrieved multimedia content." Opening Brief at 29-30. Smartflash also submits an expert declaration in support of this position. Id., Ex. 1, 6/13/2014 Declaration of Mark T. Jones.
Defendants respond that Claim 1 also contains this phrase, and that the only reasonable interpretation is "code to control access," and thus, the lack of any such antecedent support for this phrase in claim 25 renders the claim indefinite. Apple Resp. at 25; Samsung Resp. at 34. Defendants also cite to Claim 6 of the '772 Patent which uses both the phrase "said code to control access" and "code to evaluate," but not referring to each other. Apple Resp. at 26. According to Defendants, this negates Smartflash's argument that they should be interpreted as referring to the same code in Claim 25. Id. Defendants also offer their own expert opinion stating that one of ordinary skill in the art would not understand "code to evaluate" to be the antecedent basis for "said code to control access." Id. (citing Doc. No. 163-1, 6/27/2014 Cromarty Decl. at ¶ 57). Defendants contend that "code to control access" is the code that allows access, whereas "code to evaluate use status data and use rules to determine whether access is
"The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention." 35 U.S.C. § 112 ¶ 2. If a claim does not satisfy this requirement, it is indefinite, and thus invalid. "A determination of indefiniteness is a legal conclusion that is drawn from the court's performance of its duty as the construer of patent claims" and "therefore, like claim construction, is a question of law." Atmel Corp. v. Info. Storage Devices, Inc., 198 F.3d 1374, 1378 (Fed.Cir.1999) (citation and internal quotation marks omitted).
The Supreme Court of the United States has recently interpreted 35 U.S.C. § 112 ¶ 2 "to require that a patent's claims, viewed in light of the specification and prosecution history, inform those skilled in the art about the scope of the invention with reasonable certainty." Nautilus, Inc. v. Biosig Instruments, Inc., ___ U.S. ___, 134 S.Ct. 2120, 2129, 189 L.Ed.2d 37 (2014). However, antecedent basis may be implicit rather than explicit. Energizer Holdings Inc. v. Int'l Trade Comm'n, 435 F.3d 1366, 1371 (Fed.Cir.2006) (holding that "an anode gel comprised of zinc as the active anode component" provided implicit antecedent basis for "said zinc anode"); see also Manual for Patent Examining Procedure § 2173.05(3) (8th ed., rev.9, Mar. 2014) (noting that "the failure to provide explicit antecedent basis for terms does not always render a claim indefinite").
Looking at Claim 25 in its entirety, the implicit antecedent basis for "said code to control access" is the "code to evaluate said use status data and use rules to determine whether access is permitted to said second selected one or more items of retrieved multimedia content." See Energizer, 435 F.3d at 1371. The implicit antecedent basis language states that the purpose of the "evaluation" is "to determine whether access is permitted to said second selected one or more items of retrieved multimedia content." '772 Patent Claim 25. The disputed term refers to "code to control access permitting access to said second selected one or more items of retrieved multimedia content." Id. Reading the plain language of the claim, a person of ordinary skill would understand with reasonable certainty that the second statement is referencing the first. Thus, Defendants' indefiniteness argument is rejected and
Smartflash's Proposed Apple's Proposed Construction Samsung's Proposed
Construction Construction
"the data carrier" "the data carrier" indefinite
Smartflash argues the "the card" in Claim 13 of the '317 Patent "is an obvious clerical drafting mistake that should read `the data carrier.'" Opening Brief at 31.
The Apple Defendants agree that "the card" should be construed as "the data carrier," but contend that it was not a clerical error on the part of the drafter. Apple Resp. at 25. According to the Apple Defendants, "[t]he fact that `the card' was substituted for `the data carrier' in the claim suggests not that the draftsman made a mistake, but that a data carrier is, in fact, a smart card." Id.
The Samsung Defendants argue that the more plausible explanation is that the phrase "the card" should have been "a card." Samsung Resp. at 35. According
A court may correct an error in a patent claim "only if (1) the correction is not subject to reasonable debate based on consideration of the claim language and the specification and (2) the prosecution history does not suggest a different interpretation of the claims." See Novo Indus., L.P. v. Micro Molds Corp., 350 F.3d 1348, 1354 (Fed.Cir.2003). Judicial correction of a claim is retroactive. Advanced Medical Optics, Inc. v. Alcon Inc., 361 F.Supp.2d 370, 384 (D.Del.2005).
Because the purported error is more than a misspelling or a missing letter, Smartflash's request to modify the plain language is inappropriate. See LG Elecs., Inc. v. Quanta Computer Inc., 566 F.Supp.2d 910, 913 (W.D.Wis.2008) (noting the "nearly impossible standard for judicial correction of a patent" and citing Novo, which the court noted "refus[ed] to correct `a' to `and' because other possibilities for correction existed"). This decision is consistent with the principle that "[c]ourts do not rewrite claims; instead, we give effect to the terms chosen by the patentee." K-2 Corp. v. Salomon S.A., 191 F.3d 1356, 1364 (Fed.Cir.1999); see Chef Am., Inc. v. Lamb-Weston, Inc., 358 F.3d 1371, 1374 (Fed.Cir.2004) (noting that "courts may not redraft claims, whether to make them operable or to sustain their validity"). Unlike the "said code to control access ..." term addressed above, the antecedent basis for "the card" is not reasonably certain. Nautilus, 134 S.Ct. at 2129. The Samsung Defendants' theory is a reasonable interpretation. Indeed, it would be consistent with the patent to have a dependent claim that further narrowed the "data carrier" to an embodiment where it was "a card." Since the Court cannot know what correction is appropriate, Claim 13 must be found
As a threshold matter, the parties dispute whether the remaining terms for construction are means-plus-function terms under 35 U.S.C. § 112 ¶ 6. Defendants contend that twelve of the terms are means-plus-function terms that require construction to determine the proper structure. Defendants argue that the rest of the terms are means-plus-function terms that lack sufficient structure.
Title 35 U.S.C. § 112, ¶ 6 provides: "An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof." Further, "[t]he scope of a claim under [35 U.S.C.] section 112, paragraph 6 ... must be limited to structures clearly linked or associated with the claimed function in the specification or prosecution history and equivalents of those structures." Med. Instrumentation & Diagnostics Corp. v. Elekta AB, 344 F.3d 1205, 1219
When a claim term does not use "means," there is a "rebuttable presumption that [35 U.S.C.] § 112 ¶ 6 does not apply." Lighting World, Inc. v. Birchwood Lighting, Inc., 382 F.3d 1354, 1358 (Fed.Cir.2004). This presumption can be overcome if it is demonstrated that the claim term fails to recite sufficiently definite structure or else recites function without reciting sufficient structure for performing that function. Id. at 1359-60. The presumption flowing from the absence of the term "means" is a strong one that is not readily overcome. Id.
Here, the claims at issue do not use the term "means." To overcome the presumption, Defendants argue that the claims recite only the word "processor," without any other structure. Samsung MSJ at 3. According to Defendants, the recitation of a "processor" and "code", without any specialized structure for performing the claimed functions, is insufficient. Id. at 5.
Some courts have found that reciting a "computer" can warrant means-plus-function treatment:
Soque Holdings Bermuda Ltd. v. Keyscan, Inc., No. 09-2651, 2010 WL 2292316, at *12 (N.D.Cal. June 7, 2010) (Patel, J.) (citations omitted). However, the present case is more analogous to Linear Technology Corp. v. Impala Linear Corp., in which the Court of Appeals for the Federal Circuit found that "when the structure-connoting term `circuit' is coupled with a description of the circuit's operation, sufficient structural meaning generally will be conveyed to persons of ordinary skill in the art, and § 112 ¶ 6 presumptively will not apply." 379 F.3d 1311, 1320 (Fed.Cir. 2004). Here, in each of the disputed terms in Appendix C, "code" and "processor" are coupled with a description of the code's or processor's operation.
Courts in this district have reached the same conclusion under similar circumstances. See, e.g., Eolas Techs., Inc. v. Adobe Sys., Inc., 810 F.Supp.2d 795, 810 (E.D.Tex.2011) (Davis, J.) (finding sufficient the patentee's argument that "virtually every element asserted by Defendants includes a phrase containing either the words `computer readable program code for ...' or `software comprising computer executable instructions [to] ...' followed by a description of the code's (or software's) operation"), aff'd sub nom. Eolas Techs. Inc. v. Amazon.com, Inc., 521 Fed. Appx. 928 (Fed.Cir.2013), opinion withdrawn in part on reconsideration as to another term, 6:09-cv-446, 2011 WL 11070303 (E.D.Tex. Sept. 23, 2011); Aloft Media, LLC v. Adobe Sys. Inc., 570 F.Supp.2d 887, 898 (E.D.Tex.2008) (Love, J.) ("[W]hen the structure-connoting term `computer code' is coupled with a description of the computer code's operation, as provided by the `wherein' clauses, sufficient structural meaning is conveyed to persons of ordinary skill in the art.") (footnote omitted), adopted, No. 6:07-CV-355, 2008 WL 5784443 (E.D.Tex. Sept. 24, 2008) (Davis, J.); Versata Software, Inc. v. Sun Microsystems, Inc., No. 2:06-cv-358, 2008 WL 3914098, at *14 (E.D.Tex. Aug. 19, 2008) (Ward, J.) (holding that the presumption
Additionally, several Federal Circuit opinions support this conclusion. Apple Inc. v. Motorola, Inc., 757 F.3d 1286, 1298 (Fed.Cir.2014) ("[W]here a claim is not drafted in means-plus-function format, the reasoning in the Aristocrat line of cases does not automatically apply, and an algorithm is therefore not necessarily required."); Flo Healthcare Solutions, LLC v. Kappos, 697 F.3d 1367, 1374 (Fed.Cir. 2012) ("When the claim drafter has not signaled his intent to invoke § 112, ¶ 6 by using the term `means,' we are unwilling to apply that provision without a showing that the limitation essentially is devoid of anything that can be construed as structure."); Greenberg v. Ethicon Endo-Surgery, Inc., 91 F.3d 1580, 1583 (Fed.Cir. 1996) (finding that "detent mechanism" was not a means-plus-function term because it denotes a type of device with a generally understood meaning in the mechanical arts).
Finally, other district courts have reached similar conclusions. See, e.g., Affymetrix, Inc. v. Hyseq, Inc., 132 F.Supp.2d 1212, 1232 (N.D.Cal.2001) (Fogel, J.) (finding that "`computer code' is not a generic term, but rather recites structure that is understood by those of skill in the art to be a type of device for accomplishing the stated functions"); Trading Techs. Int'l, Inc. v. eSpeed, Inc., No. 04 C 5312, 2006 WL 3147697, at *11-13 (N.D.Ill. Oct. 31, 2006) (similar as to "program code" terms); Wi-LAN USA, Inc. v. Alcatel-Lucent USA, Inc., No. 12-23568, 2013 WL 4811233, at *41-42 (S.D.Fla. Sept. 9, 2013) (similar as to "processor" terms).
Defendants have failed to overcome the presumption that the disputed terms, which do not use the word "means," are not means-plus-function terms governed by 35 U.S.C. § 112, ¶ 6. Thus, these disputed terms need not be construed. See Doc. No. 174 at 1-2 (Smartflash submits that "neither side has alleged that the terms at issue require construction if the Court finds that § 112 ¶ 6 is inapplicable.").
Similar to the previous terms, Defendants argue that several terms are means-plus-function terms and are indefinite because they lack adequate corresponding structure. For the same reasons discussed above, Defendants have failed to show that these terms lack structure so as to overcome the presumption against being treated as means-plus-function terms. Accordingly, it is recommended that Defendants' Motions for Summary Judgment of Indefiniteness be
The Court hereby
Within fourteen days after receipt of the Magistrate Judge's report, any party may serve and file written objections to the findings and recommendations of the Magistrate Judge.
A party's failure to file written objections to the findings, conclusions, and recommendations contained in this Report within fourteen days after service shall bar that party from de novo review by the District Judge of those findings, conclusions, and recommendations and, except upon grounds of plain error, from attacking
Non-Means-Plus-Function Terms Court's Construction Payment data "data that can be used to make payment for content" Payment validation system "system that returns payment validation data based on an attempt to validate payment data" Payment validation data Plain meaning Data carrier "medium capable of storing information" Portable data carrier Plain meaning Content data memory / data memory / Plain meaning memory ... for storing data / memory configured to store ... content / parameter memory / use rule memory Use rules(s) / use rule(s) data / data use rule Plain meaning data Access rule(s) Plain meaning Use status data Plain meaning Said code to control access to said second Not indefinite. No further construction selected one or more items of retrieved necessary multimedia content The card Invalid as indefinite
Alleged Means-Plus-Function Terms for Court's Construction Construction Code responsive to the payment validation data Not subject to 35 U.S.C. § 112 ¶ 6. No further to retrieve data from the data supplier and to construction required. write the retrieved data into the data carrier Code responsive to the payment validation data Not subject to 35 U.S.C. § 112 ¶ 6. No further to retrieve said selected at least one content construction required. data item from a data supplier and to write said retrieved at least one content data item into said data carrier Code responsive to said payment validation Not subject to 35 U.S.C. § 112 ¶ 6. No further data to retrieve said selected at least one item construction required. of multimedia content via said wireless interface from a data supplier and to write said retrieved at least one item of multimedia content into said non-volatile memory Code responsive to the payment validation data Not subject to 35 U.S.C. § 112 ¶ 6. No further to receive at least one access rule from the data construction required. supplier and to write the at least one access rule into the data carrier, the at least one access rule specifying at least one condition for accessing the retrieved data written into the
data carrier, the at least one condition being dependent upon the amount of payment associated with the payment data forwarded to the payment validation system Code responsive to the request and to the Not subject to 35 U.S.C. § 112 ¶ 6. No further received payment data, to read data for the construction required. requested data item from a content provider Code, responsive to the request and to the Not subject to 35 U.S.C. § 112 ¶ 6. No further received payment data to output the item data construction required. to the requester over the communication interface Code to output payment data for a data item for Not subject to 35 U.S.C. § 112 ¶ 6. No further making payments for the item when the item is construction required. supplied to a said requester Code to write updated use status data to the Not subject to 35 U.S.C. § 112 ¶ 6. No further carrier after user access to the stored data construction required. Code to write partial use status data to the data Not subject to 35 U.S.C. § 112 ¶ 6. No further carrier when only part of a stored data item has construction required. been accessed Code to present said second selected one or Not subject to 35 U.S.C. § 112 ¶ 6. No further more items of retrieved multimedia content to construction required. a user via said display if access is permitted "electronic payment system for confirming an Not subject to 35 U.S.C. § 112 ¶ 6. No further
electronic payment ... wherein the electronic construction required. payment system makes payments according to data in the payment distribution store associated with the forwarded data on confirmation of the payment and/or provision of the forwarded data to the card" Electronic payment system for confirming an Not subject to 35 U.S.C. § 112 ¶ 6. No further electronic payment construction required.
Alleged Means-Plus-Function Terms Court's Construction Lacking Adequate Structure A processor ... for implementing ... code, the Not subject to 35 U.S.C. § 112 ¶ 6. No further code comprising construction required. Processor for controlling access to data Not subject to 35 U.S.C. § 112 ¶ 6. No further construction required. Processor control code comprises Not subject to 35 U.S.C. § 112 ¶ 6. No further construction required. Code responsive to said user selection of said Not subject to 35 U.S.C. § 112 ¶ 6. No further at least one selected item of multimedia construction required. content to transmit payment data relating to payment for said at least one selected item of multimedia content via said wireless interface for validation by a payment validation system
Code responsive to said user selection of said Not subject to 35 U.S.C. § 112 ¶ 6. No further selected content data item to transmit payment construction required. data relating to payment for said selected content item for validation by a payment validation system Code to control access to said selected content Not subject to 35 U.S.C. § 112 ¶ 6. No further data item responsive to the payment validation construction required. data Code to control access to said at least one Not subject to 35 U.S.C. § 112 ¶ 6. No further selected item of multimedia content on said construction required. terminal responsive to said payment validation data Code to retrieve supplementary data in Not subject to 35 U.S.C. § 112 ¶ 6. No further response to said characterizing data construction required. Code to output the supplementary data Not subject to 35 U.S.C. § 112 ¶ 6. No further construction required. Code to evaluate said use status data and use Not subject to 35 U.S.C. § 112 ¶ 6. No further rules to determine whether access is permitted construction required. to said second selected one or more items of retrieved multimedia content Code to evaluate said use status data and use Not subject to 35 U.S.C. § 112 ¶ 6. No further rules to determine whether access is permitted construction required. to said second selected one or more retrieved
content data items Code to evaluate the use status data using the Not subject to 35 U.S.C. § 112 ¶ 6. No further use rules data to determine whether access is construction required. permitted to the stored data Code to access the stored data when access is Not subject to 35 U.S.C. § 112 ¶ 6. No further permitted construction required. Code to provide access to the at least one Not subject to 35 U.S.C. § 112 ¶ 6. No further content data item in accordance with the at construction required. least one use rule Processor for controlling access to data Not subject to 35 U.S.C. § 112 ¶ 6. No further construction required. Content synthesis code to generate Not subject to 35 U.S.C. § 112 ¶ 6. No further substantially complete item data from partial construction required. item data provided from two or more sources
