throbber
UNITED STATES DISTRICT COURT
`NORTHERN DISTRICT OF OHIO
`EASTERN DIVISION
`
`CASE NO.4:08CV1184
`
`JUDGE CHRISTOPHER A. BOYKO
`
`ORDER
`
`)
`
`))
`
`)
`)
`
`))
`
`)
`
`))
`
`)
`
`RESPONSIVE INNOVATIONS, LLC.,
`ET AL.,
`
`Plaintiff,
`
`vs.
`
`HOLTZBRINCK PUBLISHERS, LLC.,
`ET AL.,
`
`Defendant.
`
`CHRISTOPHER A. BOYKO, J:
`
`This matter comes before the Court following the Order and Opinion on Motions for
`
`Summary Judgment (Doc. No. 129), which withheld ruling on the issues of infringement pending
`
`resolution of further claim construction. Upon consideration of the Briefs, Responses, Exhibits,
`
`and applicable law, the Court finds the following claim construction.
`
`I. BACKGROUND
`
`A. Procedural History
`
`This is a patent infringement case brought by Responsive Innovations, LLC
`
`(“Responsive”) and Turning Technologies, LLC (“Turning”) (collectively, “Plaintiffs”) against
`
`Holtzbrinck Publishers, LLC (“Holtzbrinck”) and MacMillan Publishers, Inc. (“MacMillan”)
`
`(collectively, “Defendants”). Both Plaintiffs and Defendants market and sell radio frequency
`
`based audience response systems that employ handheld-initiated communications. Plaintiffs
`
`brought suit on May 13, 2008, alleging infringement of U.S. Patent No. 7,330,716 (“the ‘716
`
`1
`
`IRONBURG EX2026, Page 1
`
`

`

`Patent”), entitled “Wireless Communication System.” (Doc. No. 1; Doc. No. 23). Plaintiffs
`
`specifically allege that Defendants, through Defendants’ i>Clicker wireless audience response
`
`system, infringe claims 1-5, and 8-9 (“the asserted claims”) of the ‘716 Patent. (Doc. No. 23).
`
`Defendants deny infringement and further deny that the patent is valid. (Doc. No. 15;
`
`Doc. No. 25). Defendants brought declaratory judgment counterclaims of non-infringement and
`
`invalidity under 35 U.S.C. §§ 102, 103, and 112 and counterclaims of unfair competition under
`
`the Lanham Act § 43(a), common law unfair competition, deceptive trade practice under Ohio
`
`Rev. Code § 4165.02, defamation, and tortious interference. (Doc. No. 25). On April 3, 2009,
`
`the Court issued its Markman Order. (Doc. No. 38). On June 29, 2009, Defendants moved to
`
`amend its affirmative defenses and counterclaims to add new allegations of inequitable conduct
`
`and patent misuse. (Doc. No. 39).
`
`On June 24, 2010, Defendants filed a Motion for Summary Judgment on their invalidity
`
`defenses of anticipation, obviousness, and failure to disclose the best mode. (Doc. No. 72).
`
`Plaintiffs filed a Motion for Summary Judgment on: (1) their claim of patent infringement, (2)
`
`Defendants’ invalidity defenses of anticipation, obviousness, written description, enablement,
`
`and best mode, (3) Defendants’ unenforceability defenses of inequitable conduct, and patent
`
`misuse, and (4) Defendants’ counterclaims. (Doc. No. 73 corrected at 76). The Court heard Oral
`
`Argument on the parties’ Motions for Summary Judgment on July 7, 2010. (See Doc. No. 125).
`
`Pursuant to motion by Plaintiffs, the Court withheld ruling until after the United States Supreme
`
`Court addressed the issue of burden of proof in a case pending before it in 2011. The Supreme
`
`Court decision did not fundamentally alter the burden of proof implicated in the Motions of the
`
`parties and the Court issued a ruling granting in part each party’s Motions for Summary
`
`2
`
`IRONBURG EX2026, Page 2
`
`

`

`Judgment. The Court, however, withheld ruling on the issues of infringement and anticipation
`
`by the Nordic and X-10 references pending the resolution of supplemental claim construction.
`
`(Doc. No. 129). Both parties filed supplemental claim construction briefs (Doc. Nos. 135, 141,
`
`142, and 144),1 and this ruling follows.
`
`B. ‘716 Patent
`
`The ‘716 Patent is generally directed to audience response systems, i.e., systems
`
`“employed to retrieve (or receive) responses from a group of individuals at a central location.”
`
`U.S. Patent No. 7,330,716, Col. 1, Lines 18-20. The audience response system of the ‘716
`
`Patent has a plurality of transmitters (handheld devices) and at least one receiver (base unit).
`
`U.S. Patent No. 7,330,716, Col. 1, Lines 11-13. Each handheld device includes a wireless data
`
`transmitter illustrated as a radio frequency (“RF”) transceiver configured to transmit and receive
`
`RF signals. U.S. Patent No. 7,330,716, Col. 4, Lines 4-7.
`
`The ‘716 Patent contains one independent claim (claim 1). Claim 1 is as follows (with
`
`the disputed claim terms underlined):
`
`1. A wireless communication system comprising:
`a plurality of handheld devices, each handheld device including:
`a transmitter,
`an input selection control, and
`a processor configured to receive a user selection from the input selection control; and
`upon receipt of the user selection, communicate instructions to the transmitter to
`transmit an RF signal encoding an address and the user selection according to a
`defined RF profile,
`wherein the defined RF profile comprises a distinct period of no RF transmission, and
`a first period of RF transmission corresponding to transmission of the RF signal, where
`the first period of RF transmission occurs after the distinct period of no RF
`
`1 The Court notes that Defendants exceeded the page limit in their supplemental claim
`construction briefs. While no action is taken at this time, future violations may result in
`sanctions.
`
`3
`
`IRONBURG EX2026, Page 3
`
`

`

`transmission and is responsive to receipt of the user selection from the input
`selection control; and
`a receiver including a transceiver configured for data communication with a processor.
`
`II. LEGAL STANDARDS
`
`A. The Claim Construction Process
`
`Claim construction is a matter of law for the Court to determine. Markman v. Westview
`
`Instruments, 52 F.3d 967, 979 (Fed. Cir. 1995) (en banc), aff’d, 517 U.S. 370 (1996). The
`
`Court’s task in this regard is to “inform the meaning of the claim language.” Phillips v. AWH
`
`Corp., 415 F.3d 1303, 1317 (Fed. Cir. 2005) (en banc). Put another way, the Court’s assignment
`
`is “the contextual interpretation of language.” Smithkline Beecham Corp. v. Apotex Corp., 403
`
`F.3d 1331, 1339 (Fed. Cir. 2005). The three main sources for claim construction are the claims
`
`themselves, the written specification of which the claims are a part, and the prosecution history
`
`or file wrapper representing the back-and-forth discussion between the inventor and the Patent
`
`and Trademark Office (“PTO”). Markman, 52 F.3d at 979-80. These sources are collectively
`
`referred to as the intrinsic record of the patent. Chimie v. PPG Indus. Inc., 402 F.3d 1371, 1377
`
`(Fed.Cir.2005).
`
`The words of a claim “are generally given their ordinary and customary meaning.”
`
`Phillips, 415 F.3d at 1312. The ordinary and customary meaning is to be determined from the
`
`perspective of one of ordinary skill in the art at the time of the invention. Id. at 1313.
`
`“Importantly, 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.” Id.
`
`Accordingly, the court first looks to the claim language, read in view of the specification.
`
`4
`
`IRONBURG EX2026, Page 4
`
`

`

`Id. at 1315 (stating that the 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”).
`
` However, while the court may look to the written description to define a term already in a claim
`
`limitation, the court may not read a limitation from the written description into a claim. Id. at
`
`1323. In other words, although it is often stated that a patentee may be his own lexicographer, “a
`
`claim must explicitly recite a term in need of definition before a definition may enter the claim
`
`from the written description.” Renishaw PLC v. Marposs Societaper Azioni, 158 F.3d 1243,
`
`1248 (Fed. Cir. 1998).
`
`The prosecution history is also relevant to claim construction as part of the intrinsic
`
`record. Phillips, 415 F.3d at 1317.2 For example, an inventor may disclaim a particular claim
`
`construction during prosecution before the PTO. Hockerson-Halberstadt, Inc. v. Avia Group
`
`Intern., Inc., 222 F.3d 951, 956 (Fed. Cir. 2000). However, prosecution history is often
`
`ambiguous, Inverness Medical Switzerland v. Warner Lambert Co., 309 F.3d 1373, 1382 (Fed.
`
`Cir. 2002), and courts must consider it carefully. Phillips, 415 F.3d at 1317 (“[B]ecause the
`
`prosecution history represents an ongoing negotiation between the Patent and Trademark Office
`
`(‘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 for claim construction purposes.”). While the
`
`prosecution history, including art referenced in the patent, may be used to inform the meaning of
`
`the claims, V-Formation, Inc. v. Benetton Group Spa, 401 F.3d 1307, 1311 (Fed. Cir. 2005),
`
`2 The ‘716 Patent’s prosecution file wrapper (Dkt. 29, Ex. 4, RI000909 to RI001054) was
`admitted into evidence at the Markman hearing. Markman Tr. 29:16-24.
`
`5
`
`IRONBURG EX2026, Page 5
`
`

`

`using a prior art reference to infer what the Examiner or the applicant thought about the meaning
`
`of a term, based on whether a particular claim interpretation would read on the reference, is not
`
`an appropriate use of the prosecution history. At claim construction, the court is “not concerned
`
`with the state or scope of the prior art.” Sky Technologies, LLC v. Ariba, Inc., 491 F.Supp. 2d,
`
`154, 157 (D.Mass. 2007) (citations omitted). The court “is also not concerned with how far the
`
`patent or claims as a whole may extend in terms of breadth of subject matter. A court is
`
`concerned only with the interpretation of a disputed term.” Id.
`
`Other evidence of claim meaning, such as inventor testimony, expert testimony, and lay
`
`or technical dictionary definitions, is referred to as extrinsic evidence. Phillips, 415 F.3d at
`
`1317. However, extrinsic evidence is less important than the intrinsic evidence and cannot
`
`contradict a claim definition from the intrinsic record. Id. at 1318-19; see also C.R. Bard, Inc. v.
`
`U.S. Surgical Corp., 388 F.3d 858, 861 (Fed. Cir. 2004) (explaining “that the intrinsic record is
`
`the primary source for determining claim meaning”). The only extrinsic evidence offered by the
`
`parties in this case is from general purpose and technical dictionaries.
`
`A. Introduction
`
`III. ANALYSIS
`
`The following analysis addresses only the present issues regarding claim construction of
`
`the ‘716 Patent. Although both parties argue the issues surrounding summary judgment, the
`
`Court should withhold judgment until after receiving supplemental briefs based on the following
`
`claim construction. The Court should also note that there is no need for an additional Markman
`
`hearing, as there is already expert testimony regarding the terms and phrases to be construed.
`
`6
`
`IRONBURG EX2026, Page 6
`
`

`

`B. “A plurality of handheld devices”
`
`1. Construction
`
`Plaintiffs’ proposed construction: Two or more devices, like in kind, that are usable or
`
`operable while held in the hand without the need for external support. Doc. No. 141, at 3.
`
`Defendants’ proposed construction: Two or more devices that are usable or operable in
`
`the hand. Doc. No. 135, at 4 and 18.
`
`Court’s construction: Two or more devices that are usable or operable while held in the
`
`hand without the need for external support.
`
`2. Discussion
`
`Regarding the term “plurality,” both parties agree that it means “two or more.” Plaintiffs,
`
`however, further contend that the term should include the limitation “like in kind.” The addition
`
`of such a limitation would be redundant because the term “plurality” is not used in a vacuum.
`
`Although plurality is inherently limited to a certain group, that group is defined by a subsequent
`
`prepositional phrase. For example, “a plurality of bicycles” is limited to the narrow category of
`
`bicycles; on the other hand, “a plurality of vehicles” is limited to the much broader category of
`
`all vehicles, including bicycles. Here, the plurality is of “handheld devices.” Therefore, the
`
`plurality at issue need not to be limited by the additional phrase “like in kind.” Instead, the
`
`meaning of handheld devices as determined below and by its claimed limitations (transmitter,
`
`input selection, processor, etc) properly limits the plurality.
`
`Regarding the term “handheld device,” Defendants seek a broad construction to any
`
`device that is usable or operable while in the hand. In contrast, Plaintiffs seek a narrower
`
`construction to any device usable or operable while held in the hand, without the need for
`
`7
`
`IRONBURG EX2026, Page 7
`
`

`

`external support. Without an express definition of “handheld device” in the ‘716 Specification,
`
`the Court must first look to the intrinsic evidence and ordinary meaning of the term.
`
`Defendants argue that neither the intrinsic evidence, nor the extrinsic evidence, support
`
`Plaintiffs’ addition of the “without the need for external support” limitation. The ‘716
`
`Specification only discusses general sizes of the device (‘716 Specification, col. 3, ll. 8-21), and
`
`although it teaches that the device “may be larger or smaller,” it is clear that the intent of the
`
`drafter was to disclose a device that could fit within a person’s hand. The weight and other
`
`external needs of the device, however, are never discussed; therefore, it is difficult to determine
`
`from the intrinsic evidence alone whether external support would be necessary for one holding
`
`the handheld device. Defendants’ broad interpretation, however, is inconsistent with the
`
`ordinary meaning and use of “handheld.” Handheld devices are those that can be used when
`
`held only in the hand; in other words, usable or operable without the need for external support.
`
`To suggest otherwise, as Defendants do, indicates a desktop or similar device, not a handheld
`
`device.
`
`Defendants also quote their expert from the Markman hearing, Mr. McIntyre; however,
`
`this extrinsic evidence fails to shed anymore sufficient light on the issue. Rather than answering
`
`in the affirmative to support Defendants’ proposed construction, Mr. McIntyre merely restated
`
`facts and possibilities. When asked whether a keyboard held in the hand is a handheld device,
`
`Mr. McIntyre stated only “[w]ell, you just held it in your hand.” (Ma Dec., Exh. 8) (McIntyre
`
`Dep., at 84:13-20). Later, when asked whether a laptop computer is a handheld device because it
`
`is held in your hand, Mr. McIntyre again failed to answer affirmatively, stating only it could be a
`
`handheld device. (Ma Dec., Exh. 8) (McIntyre Dep., at 86:17-25) (emphasis added). These
`
`8
`
`IRONBURG EX2026, Page 8
`
`

`

`statements suggest that there is more to the interpretation of a handheld device than simply the
`
`capability to hold it in a hand.
`
`In light of the above, the Court construes “a plurality of handheld devices” to mean “two
`
`or more devices that are usable or operable while held in the hand without the need for external
`
`support.”
`
`C. “Address” as used in the limitation “an RF signal encoding an address and the user
`
`selection”
`
`1. Construction
`
`Plaintiffs’ proposed construction: Address of the handheld device. Doc. No. 141, at 11.
`
`Defendants’ proposed construction: One or more network accessible addresses, device
`
`identifiers, electronic identification numbers (such as EINs), IP addresses, url and ftp locations,
`
`e-mail addresses, names, a distribution list including one or more addresses, network drive
`
`locations, account numbers or other types of addresses that can identify a desired destination or
`
`device. Doc. No. 135, at 28.
`
`Court’s construction: An identifier of a desired destination or device, where the address is
`
`one or more network accessible addresses, device identifiers, electronic identification numbers
`
`(such as EINs), IP addresses, URL and FTP locations, e-mail addresses, names, a distribution list
`
`including one or more addresses, network drive locations, or account numbers.
`
`2. Discussion
`
`Defendants argue that because the term “address” is explicitly defined in the
`
`specification, Plaintiffs must be held to this definition. As explained by the Federal Circuit, “the
`
`specification is the single best guide to the meaning of a disputed term, and . . . the specification
`
`9
`
`IRONBURG EX2026, Page 9
`
`

`

`acts as a dictionary when it expressly defines terms used in the claims or when it defines terms
`
`by implication.” Phillips, 415 F.3d at 1321. This is precisely the case with the ‘716 Patent,
`
`which expressly defines the term “address” in the specification:
`
`“Address”, as used herein, includes but is not limited to one or more network
`accessible addresses, device identifiers, electronic identification numbers (such as
`EINs), IP addresses, url and ftp locations, e-mail addresses, names, a distribution list
`including one or more addresses, network drive locations, account numbers or other
`types of addresses that can identify a desired destination or device.
`
`‘716 Specification, col. 2, ll. 14-20. As such, the term “address” as used in the limitation of
`
`Claim 1, “an RF signal encoding an address and the user selection,” should follow the above
`
`definition.
`
`Plaintiffs attempt to limit the term “address” to only that of the handheld device by
`
`showing that “address” is only used in the specification when discussing the address of a
`
`handheld device. First, Plaintiffs rely on the Abstract, which provides, in pertinent part, “[i]n
`
`one embodiment, each transmitter has an address.” ‘716 Abstract. However, this statement only
`
`represents a single embodiment, not the invention as a whole or Claim 1. Moreover, even if each
`
`transmitter has an address, there is no indication that each receiver does not also have an address,
`
`as is possible in accordance with the specification’s definition. Defendants next rely on Figure
`
`3, along with three other embodiments of ‘716, which illustrate a handheld device 305
`
`containing an address 335, ultimately connected to an RF transceiver 315. These embodiments,
`
`however, present the same issues as the Abstract. Additionally, it is not clear whether address
`
`335 is even the address of the handheld device, as it is only referred to as a “stored address.”
`
`‘716 Specification, col. 4, line 42.
`
`Plaintiffs next attack Defendants’ reference to an embodiment teaching that “the receiver
`
`10
`
`IRONBURG EX2026, Page 10
`
`

`

`may have an ID” and the “processing logic may be configured to only accept signals that contain
`
`the receiver ID.” ‘716 Specification, col. 77, ll. 23-25. Plaintiffs contend that the term “ID” is
`
`used, rather than “address,” indicating that “ID” is used with respect to receivers” and “address”
`
`is used with respect to handheld devices. Again, referring to the ‘716 definition, the terms “ID”
`
`and “identifiers” are used as express examples of an “address.” Plaintiffs’ argument is therefore
`
`illogical unless the Court expressly ignores the definition of an address set forth by Plaintiffs,
`
`which it cannot do.
`
`Therefore, the Court construes the term “address” as used in the limitation of Claim 1,
`
`“an RF signal encoding an address and the user selection,” to mean “an identifier of a desired
`
`destination or device, where the address is one or more network accessible addresses, device
`
`identifiers, electronic identification numbers (such as EINs), IP addresses, URL and FTP
`
`locations, e-mail addresses, names, a distribution list including one or more addresses, network
`
`drive locations, or account numbers” as is consistent with the ‘716 Specification.
`
`IV. CONCLUSION
`
`For the foregoing reasons, the Court construes the term “a plurality of handheld devices”
`
`to mean “two or more devices that are usable or operable while held in the hand without the need
`
`for external support”; and the term “address” as used in the limitation “an RF signal encoding an
`
`address and the user selection” to mean “an identifier of a desired destination or device, where
`
`the address is one or more network accessible addresses, device identifiers, electronic
`
`identification numbers (such as EINs), IP addresses, URL and FTP locations, e-mail addresses,
`
`names, a distribution list including one or more addresses, network drive locations, or account
`
`numbers.”
`
`11
`
`IRONBURG EX2026, Page 11
`
`

`

`IT IS SO ORDERED.
`
`Dated: April 9, 2013
`
`s/ Christopher A. Boyko
`CHRISTOPHER A. BOYKO
`United States District Judge
`
`12
`
`IRONBURG EX2026, Page 12
`
`

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