throbber
Trials@uspto.gov
`571-272-7822
`
`
`
`
`Paper 39
`Entered: September 13, 2016
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`KAPSCH TRAFFICCOM IVHS INC., and
`KAPSCH TRAFFICCOM HOLDING CORP.,
`Petitioner,
`
`v.
`
`NEOLOGY, INC.,
`Patent Owner.
`____________
`
`Case IPR2015-00814
`Patent 6,690,264 B2
`
`
`
`Before JUSTIN T. ARBES, GLENN J. PERRY, and
`TREVOR M. JEFFERSON, Administrative Patent Judges.
`
`PERRY, Administrative Patent Judge.
`
`
`
`FINAL WRITTEN DECISION
`35 U.S.C § 318(a) and 37 C.F.R. § 42.73
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`I. INTRODUCTION
`
`This is a Final Written Decision entered in an inter partes review
`
`instituted pursuant to 35 U.S.C. § 314. For reasons discussed below, we
`
`determine that Petitioner has shown by a preponderance of the evidence that
`
`claims 1–24 of U.S. Patent No. 6,690,264 B2 (Ex. 1001, “the ’264 patent”)
`
`are unpatentable.
`
`
`
`A. Procedural History
`
`Kapsch TrafficCom IVHS Inc. and Kapsch TrafficCom Holding Corp.
`
`(collectively, “Petitioner”)1 filed a Petition (Paper 1, “Pet.”) seeking inter
`
`partes review of claims 1–24 of the ’264 patent pursuant to 35 U.S.C.
`
`§§ 311–319. On September 14, 2015, we instituted an inter partes review of
`
`claims 1–24 (Paper 11, “Dec. on Inst.”). Patent Owner Neology, Inc. filed a
`
`Patent Owner Response (Paper 20, “Resp.”), and Petitioner filed a Reply
`
`(Paper 30, “Reply”).2 We heard oral argument on May 10, 2016, and a
`
`transcript of that argument is included in the record (Paper 38, “Tr.”).
`
`We have jurisdiction under 35 U.S.C. § 6. This final written decision
`
`is issued pursuant to 35 U.S.C. § 318(a) and 37 C.F.R. § 42.73.
`
`
`1 The original Petitioners were Kapsch TrafficCom IVHS Inc., Kapsch
`TrafficCom IVHS Holding Corp., Kapsch TrafficCom IVHS Technologies
`Holding Corp., Kapsch TrafficCom U.S. Corp., and Kapsch TrafficCom
`Holding Corp. During trial, Kapsch TrafficCom IVHS Holding Corp.,
`Kapsch TrafficCom IVHS Technologies Holding Corp., and Kapsch
`TrafficCom U.S. Corp. merged with Kapsch TrafficCom Holding Corp.
`See Papers 31, 32.
`
`2 Petitioner filed redacted (Paper 30) and unredacted (Paper 28) versions of
`its Reply and other materials, along with two motions to seal, which were
`conditionally granted. See Papers 26, 31. We do not rely on any sealed
`material in this Decision.
`
`2
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`B. Related Proceedings
`
`According to Petitioner, Patent Owner asserted the ’264 patent in
`
`Neology, Inc. v. Kapsch TrafficCom IVHS Inc., et al., D. Del. Case No. 1:13-
`
`cv-02052-LPS. Further, according to Petitioner, Patent Owner originally
`
`filed this action against Confidex, Inc. on December 19, 2013; and filed an
`
`amended complaint against various Kapsch entities on February 27, 2014,
`
`first serving them with the complaint on February 28, 2014. Pet. 1.
`
`Patent Owner previously asserted the ’264 patent in Neology, Inc. v.
`
`Federal Signal Corp., et al., Case No. 11-CV-00672-LPS-MPT (D. Del.
`
`2011). In that case, all pending claims were dismissed with prejudice on
`
`June 25, 2013. Pet. 1−2.
`
`
`
`C. The ’264 Patent (Ex. 1004)
`
`1. Background of the ’264 Patent
`
`Radio-frequency identification (RFID) technology provides remote
`
`identification of objects by using an RFID tag (“tag”) associated with those
`
`objects. The tag wirelessly responds to an RFID reader’s interrogating
`
`signal, thereby identifying items associated with the tag. Ex. 1001 ¶¶ 23−24.
`
`According to Patent Owner, the ’264 patent describes improvements over a
`
`prior art RFID tag disclosed by Kruest (Ex. 1009), incorporated by reference
`
`into the ’264 patent Specification. Resp. 2−3; see Ex. 1004, 1:13−14.
`
`2. The ’264 Patent Improvement
`
`The ’264 patent criticizes Kruest because in Kruest’s disclosed
`
`system, “while the chip is in the C[LOAK] state, it is impossible for the
`
`reader to communicate with the tag.” Ex. 1004, 1:41−42. Kruest places an
`
`RFID tag in a cloaked state by disconnecting the tag’s antenna from the
`
`3
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`chip’s circuitry in response to a command to initiate cloaking. Resp. 3
`
`(citing Ex. 1004, 1:12−26). The antenna remains disconnected for a
`
`predetermined, finite period of time (a “cloaking period”), controlled by an
`
`RC circuit. Id. During this cloaking period, the tag is unable to
`
`communicate with a reader, and is thus unable to respond to any commands,
`
`until the cloaking period expires. Id. (citing Ex. 1004, 1:20−26). The ’264
`
`patent describes its improvement as providing a receiving connection so that
`
`command signals are continuously receivable notwithstanding cloaking of
`
`the RFID tag. Ex. 1004, 1:59−62.
`
`Figure 1 of the ’264 patent is reproduced below.
`
`
`
`4
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`Figure 1 is a circuit diagram of the illustrated embodiment in which
`the RFID tag remains in a condition in which command signals can
`be received during the cloaking period and in response to which the
`tag may be awakened on command. Ex. 1004, 2:18−22.
`
`Cloaking circuit 10 for an RFID tag allows it to receive command
`
`signals via diode 24 while cloaked, even though the tag is prevented from
`
`responding (typically by backscattering from its antenna) to an interrogating
`
`signal while cloaked.
`
`During normal operation (not cloaked), “cloak” node 12, coupled to
`
`the input of AND gate 16, is high. Whenever “Output” node 14 also goes
`
`high (typically for 1 to 2 μsec), transistor 20, acting as a switch, connects
`
`antenna 42 to ground pad 22 (via input pad 18 and diode 23). When antenna
`
`42 is grounded, its impedance is such that it backscatters an interrogating
`
`signal from the reader, thereby responding to it. With both output node 14
`
`and cloak node 12 high (not cloaked), the output of AND gate 16 is high, the
`
`antenna is grounded, and the RFID tag backscatters an interrogating signal.
`
`Ex. 1004, 3:21−34.
`
`Otherwise (when cloaked), antenna 42 does not backscatter an
`
`interrogating signal and therefore is not “seen” by an interrogator. Id.
`
`Figure 2 of the ’264 patent is reproduced below.
`
`5
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`Figure 2 is a timing diagram explaining operation of the
`circuit shown in Figure 1. Ex. 1004, 2:18−24.
`
`
`
`The envelope of the input signal is shown on line 32, the output (input to
`
`AND gate 16) at node 14 on line 34, and Cloak bar on line 36. During
`
`normal operation 28 (not cloaked), when Output goes high at node 14 as
`
`shown by pulse 38, backscattered pulse 40 will be presented on pad 18, i.e.,
`
`a momentary grounding of antenna 42. However, during cloaked period 30,
`
`Output pulse 38 is cut off from antenna 42. During cloaked operation, cloak
`
`node 12 is low. Therefore, the output of AND gate 16 remains low at all
`
`times, the antenna is not grounded, and no interrogating signal is
`
`backscattered from RFID tag 10. Id. at 3:34−45.
`
`3. Illustrative Claim
`
`Claim 1 of the ’264 patent is exemplary of the claims at issue:
`
`1. An improvement in a cloaked RFID tag having an
`antenna comprising:
`
`a switch;
`
`a logic circuit coupled to said switch to selectively allow
`communication of signals through said antenna during normal
`operation to allow output of a signal from said RFID tag
`
`6
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`through said antenna and to disable the output from said RFID
`tag during a cloaking period; and
`
`a receiving connection to said RFID tag so that command
`signals are continuously receivable notwithstanding cloaking of
`said RFID tag.
`
`D. Pending Grounds of Unpatentability
`
`We instituted trial regarding the patentability of claims 1−24 of the
`
`’264 patent on the following grounds. Dec. on Inst. 20.
`
`Reference(s)
`
`Basis
`
`Claims challenged
`
`Atkins3
`
`35 U.S.C. § 102(b)
`
`1–24
`
`Marsh4
`
`35 U.S.C. § 102(b)
`
`Turner5
`
`35 U.S.C. § 102(b)
`
`1–3, 8, 19–21, and
`24
`
`1–3, 8, 19–21, and
`24
`
`Kruest6 and Turner
`
`35 U.S.C. § 103
`
`1−24
`
`II. DISCUSSION
`
`A. Claim Interpretation
`
`The Board interprets unexpired claims using the “broadest reasonable
`
`construction in light of the specification of the patent in which [they]
`
`
`3 PCT International Application Publication No. WO 98/52142, published
`November 19, 1998 (“Atkins,” Exhibit 1006).
`4 U.S. Patent No. 5,966,083–Marsh et al., issued October 12, 1999 (“Marsh,”
`Exhibit 1007).
`5 European Patent Application Publication No. EP 0 924 635 A2, published
`June 23, 1999 (“Turner,” Exhibit 1008).
`6 U.S. Patent No. 5,963,144–Kruest, issued October 5, 1999 (“Kruest,”
`Exhibit 1009).
`
`7
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`appear[].” 37 C.F.R. § 42.100(b); Cuozzo Speed Techs., LLC v. Lee,
`
`136 S. Ct. 2131, 2144–46 (2016) (upholding the use of the broadest
`
`reasonable interpretation standard as the claim interpretation standard to be
`
`applied in inter partes reviews). Under this standard, we interpret claim
`
`terms using “the broadest reasonable meaning of the words in their ordinary
`
`usage as they would be understood by one of ordinary skill in the art, taking
`
`into account whatever enlightenment by way of definitions or otherwise that
`
`may be afforded by the written description contained in the applicant’s
`
`specification.” In re Morris, 127 F.3d 1048, 1054 (Fed. Cir. 1997).
`
`We presume that claim terms have their ordinary and customary meaning.
`
`See Trivascular, Inc. v. Samuels, 812 F.3d 1056, 1062 (Fed. Cir. 2016)
`
`(“Under a broadest reasonable interpretation, words of the claim must be
`
`given their plain meaning, unless such meaning is inconsistent with the
`
`specification and prosecution history.”); In re Translogic Tech., Inc., 504
`
`F.3d 1249, 1257 (Fed. Cir. 2007) (“The ordinary and customary meaning is
`
`the meaning that the term would have to a person of ordinary skill in the art
`
`in question.” (internal quotation marks omitted)). A patentee, however, may
`
`rebut this presumption by acting as his or her own lexicographer, providing a
`
`definition of the term in the specification with “reasonable clarity,
`
`deliberateness, and precision.” In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir.
`
`1994).
`
`1. Previously Construed Terms
`
`a. “cloak/ed/ing”
`
`In our Decision on Institution, we preliminarily construed
`
`“cloak/ed/ing” as “the RFID tag’s output is disabled for a period of time
`
`during which it cannot respond to commands from a reader even though
`
`8
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`command signals are continuously receivable.” Dec. on Inst. 7−8.
`
`Petitioner agrees with this construction. Tr. 8.
`
`Patent Owner indicates that it “adopts the Board’s construction of this
`
`term.” Resp. 8−9. However, Patent Owner comments on our construction
`
`as follows:
`
`In acknowledging this language from the SUMMARY, the
`PTAB confirmed three things in relation to the claim terms: 1)
`the term “respond” as used in the PTAB’s adopted construction
`of “cloak/ed/ing” means to “backscatter from antenna;” 2) a
`“cloaking period” is a period of time during which a tag does
`not backscatter from its antenna and; 3) a cloaked tag can
`receive a command that “lifts the tag out of its cloaked state.”
`Ex. 2030, ¶ 90. This acknowledgement is important to
`understanding other terms used in the ‘264 patent.
`
`Id. at 9.
`
`We disagree with Patent Owner’s comments. It was not and is not our
`
`intention to construe “respond” to require “backscatter from antenna,”7
`
`although backscatter from antenna is one possible, and often-used, manner
`
`of responding. Nor does our construction require that a command lift the tag
`
`out of its cloaked state, although that is certainly one command that can be
`
`received while the tag is cloaked. Based on Patent Owner’s comments and
`
`the fully developed record, we now clarify our construction of
`
`“cloak/ed/ing.” Id.
`
`Arguments of the parties on both sides demonstrate that construction
`
`of “cloak/ed/ing” was at issue during trial and could be outcome–
`
`determinative as to the asserted grounds. Patent Owner confirmed during
`
`
`7 Our original interpretation of “cloaking period” as “a period of time during
`which a tag does not respond (backscatter from antenna) to an interrogation”
`did require backscatter. As explained below, however, we do not now
`interpret the term in that manner. See infra Section II.A.1.b.
`
`9
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`oral argument that the term “cloaked” was first introduced in the Kruest
`
`reference (incorporated by reference into the challenged patent). Ex. 1004,
`
`1:13−14; Tr. 33. Nothing in the record contradicts this assertion. Kruest
`
`used the term “cloaked” to describe a state in which an RFID tag was
`
`rendered incapable of responding to an interrogator (reader) by
`
`disconnecting its antenna. Ex. 1009, 2:60−3:13, 3:65–4:4, 4:51–63.
`
`We take strong guidance in construing this term from Kruest, which
`
`appears to be the first time the term “cloak” was used in the context of an
`
`RFID tag. We are not persuaded that the term “cloak” itself evolved to
`
`embrace a requirement of being able to receive commands while in a
`
`cloaked state, even though that is the improvement described by the
`
`’264 patent.
`
`There is no description in the ’264 patent Specification that rises to
`
`the level of a definition of the term “cloak/ed/ing.” Patent Owner argues
`
`that we should appreciate that a cloaked tag can receive a command that lifts
`
`the tag out of its cloaked state. Resp. 9.
`
`We appreciate that the ’264 patent describes a circuit arrangement that
`
`permits commands to be received even when backscatter is prohibited by the
`
`tag being cloaked. Commands can be received that lift the tag out of its
`
`cloaked state and allow it to operate in another state, e.g., a normal state in
`
`which it is able to backscatter and thus be interrogated by a reader. Clearly
`
`that is the improvement offered by the ’264 patent. However, these
`
`capabilities are not required by the term “cloak/ed/ing” itself. “Cloaked”
`
`merely describes a condition in which the tag is incapable of responding
`
`(backscattering in an embodiment) to an interrogator signal and therefore is
`
`not “seen” by the interrogator. Other words of the claims describe the
`
`10
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`’264patent improvement.
`
`The SUMMARY portion of the ’264 patent Specification describes
`
`the improvement provided by the ’264 patent as follows:
`
`The invention is defined as an improvement in a cloaked
`RFID tag having an antenna comprising a switch and a logic
`circuit coupled to the switch. The logic circuit or gate
`selectively allows communication of signals through the
`antenna during normal operation to thereby allow output of a
`signal from the RFID tag through the antenna and to disable the
`RFID output during a cloaking period. A receiving connection
`is provided to the RFID tag so that command signals are
`continuously receivable notwithstanding cloaking of the RFID
`tag.
`
`Ex. 1004, 1:53−62. We glean from this description that a cloaking period is
`
`a period of time during which a tag does not respond (e.g., backscatter from
`
`antenna) to an interrogation. We further glean that this invention
`
`distinguishes itself from other tags in that during cloaked operation, signals
`
`can be received even though the tag does not respond to an interrogation by
`
`a reader.
`
`Patent Owner contends that the cloaking concept evolved from what
`
`was understood at the time of Kruest to what was understood at the time of
`
`the challenged patent. Tr. 38. Nevertheless, Patent Owner acknowledges
`
`that there is no clear definition of “cloaked” in the Specification of the
`
`challenged patent. Id. at 37.
`
`Petitioner argues that the term “cloaking” was known in the prior art
`
`before the ’264 patent. Id. at 4. The record evidence suggests that the term
`
`was known at least from Kruest, which was incorporated by reference into
`
`the challenged patent.
`
`In light of the now fully developed record, we construe “cloak/ed/ing”
`
`11
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`as “the RFID tag does not respond to an interrogating signal.” We find that
`
`this is the understanding that one of ordinary skill would have had at the
`
`time of the ’264 patent invention.
`
`b. “cloaking period”
`
`Our preliminary construction of “cloaking period” was “a period of
`
`time during which a tag does not respond (backscatter from antenna) to an
`
`interrogation.” Dec. on Inst. 8.
`
`Patent Owner argues that our preliminary construction is unreasonably
`
`broad in that it does not take into account the fundamental novel aspect of
`
`the ’264 patent. Resp. 9. According to Patent Owner and its declarant, Jack
`
`Goldberg, that fundamental aspect is that the tag is able to be lifted out of its
`
`cloaked state upon receipt of a command from the reader. Id. (citing Ex.
`
`2030 ¶ 94). Patent Owner proposes the following construction: “the
`
`predetermined and finite period of time, which may be shortened by receipt
`
`of a command, during which a tag is cloaked and does not backscatter from
`
`its antenna.” Id. at 9−10 (citing Ex. 2030 ¶ 96).
`
`Patent Owner has identified the improvement provided by the ’264
`
`patent. However, we are not persuaded that the term “cloaking period,” as
`
`used in the claims, is so limited. The term “cloaking period” is not defined
`
`in the ’264 patent Specification and had meaning in the art (see the prior art
`
`patents cited above) before the ’264 patent. The claims say nothing about
`
`shortening the cloaking period by receipt of a particular command. See
`
`Reply 6–7. Certainly a cloaked tag could receive a command to lift it out of
`
`its cloaked state, but we see nothing in the claim language or otherwise that
`
`requires that functionality. Indeed, Patent Owner could have easily added
`
`this feature to the claims. For example, claim 1 could have been drafted to
`
`12
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`require that during a cloaking period, the tag can be lifted out of its cloaked
`
`state upon receipt of a command from the reader. But Patent Owner did not
`
`do so.8
`
`Consistent with our construction of “cloak/ed/ing,” we construe
`
`“cloaking period” as a “period of time during which the tag does not provide
`
`a response to an interrogating signal.”
`
`2. Terms Not Preliminarily Construed in Decision on Institution
`
`a. “cloaked/cloakable RFID tag”
`
`The term “cloaked/cloakable RFID tag” was not preliminarily
`
`construed by the Board in the Decision on Institution. Patent Owner asks
`
`that we construe this term to avoid conflict or confusion with the construed
`
`term “cloak/ed/ing.” Resp. 11.
`
`According to Patent Owner, the term “cloaked/cloakable RFID tag” as
`
`used in the context of the challenged claims should be construed to mean “an
`
`RFID tag whose output is disabled for a period of time during which it
`
`cannot respond to commands from a reader even though command signals
`
`are continuously receivable.” Id.; Ex. 2030 ¶ 97.
`
`Consistent with our construction of “cloak/ed/ing,” we construe
`
`“cloaked/cloakable RFID tag” as “an RFID tag that does not provide a
`
`response to an interrogating signal.” Claim 1, for example, states
`
`specifically that “command signals are continuously receivable
`
`notwithstanding cloaking of said RFID tag.” It would be superfluous to
`
`8 Indeed, claim 1 of U.S. Patent No. 7,064,653 B2 (Ex. 1038), which is a
`continuation of the ’264 patent, recites “disabling an output of an RFID tag
`during a cloaking operation,” “receiving input transmissions regardless of
`the cloaking operation,” and “enabling the output of the RFID tag responsive
`to an input transmission received during the cloaking operation.” See
`Tr. 59:9–18.
`
`13
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`include a similar limitation in the construction of “cloaked RFID tag” in the
`
`preamble of claim 1.
`
`b. “cloaking operation”
`
`We did not preliminarily construe “cloaking operation” in our
`
`Decision on Institution. This term appears in independent claim 19 as well
`
`as dependent claims 20, 23, and 24.
`
`Patent Owner asks that we construe this term “to avoid conflict or
`
`confusion with the construed term “cloak/ed/ing.” Resp. 11. In particular,
`
`Patent Owner asks that we construe this term to mean “cloaking period.” Id.
`
`We agree with Patent Owner that in all instances in the ‘264 patent, this term
`
`is expressed as a period of time. In claim 19, for example, it appears in the
`
`limitation “receiving command signals by said RFID tag through said
`
`antenna during said cloaking operation.” In claim 23, the term appears in
`
`the limitation “by selectively isolating said data signals from said switch
`
`coupled between said antenna and ground during cloaking operation.” In the
`
`written description of the ’264 patent, the phrase “during the cloaking
`
`operation” also appears. Ex. 1004, 2:5–9. In fact, nowhere in the ’264
`
`patent does the term “cloaking operation” appear without being preceded by
`
`“during” or “during the/said.” Accordingly, construing “cloaking operation”
`
`to mean “cloaking period” is supported by the Specification and reflects the
`
`broadest reasonable construction of that term.
`
`c. “switch”
`
`We did not preliminarily construe “switch” in our Decision on
`
`Institution.
`
`Patent Owner proposes that we construe “switch” to be “an electrical
`
`or mechanical device used for opening, closing, or changing a connection of
`
`14
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`an antenna circuit.” Resp. 12 (citing Ex. 2030 ¶¶ 100, 108, 114−15,
`
`99−115). According to Patent Owner, its proposed construction would be
`
`“consistent with the ‘264 Patent being involved with the backscattering of
`
`data from the tag.” Id. At oral argument, Patent Owner stressed that
`
`“switch” should be construed as requiring more than a flip-flop or flag in
`
`memory. Tr. 46.
`
`Petitioner argues that Patent Owner’s proposed construction of
`
`“switch” is too narrow in that it attempts to limit “switch” to item 20 of
`
`Figure 1 of the ’264 patent. Reply 15−17.
`
`We find Patent Owner’s construction to be unreasonably narrow.
`
`The context in which the word “switch” is used conveys the configuration of
`
`the switch and its function. We adopt a more reasonable construction of
`
`“switch” as “an electrical or mechanical device used for opening, closing, or
`
`changing a circuit connection.”
`
`We find no reason to limit the term “switch” itself to an antenna
`
`circuit. For example, claim 22 uses additional words to describe how the
`
`claimed switch functions in circuit. It states “selectively grounding said
`
`antenna through a switch coupled between said antenna and ground during
`
`normal operation.” Claim 1 requires the switch to be coupled to a logic
`
`circuit. It further specifies the function of the switch in that it requires
`
`“selectively allow[ing] communication of signals through [an] antenna”
`
`based on whether or not cloaking is in effect. Claim 9 specifies that the
`
`switch is a “switching transistor.” As another example, claim 4 requires a
`
`specific placement of the switch in circuit between an antenna and ground.
`
`Clearly, the claim drafter had no difficulty describing various circuit
`
`configurations setting forth how a switch is configured in a circuit and how
`
`15
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`it functions in that circuit. It would be unreasonable to include in the
`
`construction of the word “switch” itself any particular circuit configuration
`
`or utilization easily provided by other words of a claim.
`
`d. “disabling communication of data signals . . . during cloaking”
`
`The claim term “disabling communication of data signals . . . during
`
`cloaking” appears in independent method claim 19.
`
`Patent Owner argues that this claim term should be construed to mean
`
`that “data signals which are present during cloaking are not communicated
`
`in that communication of those data signals is disabled.” Resp. 12 (citing
`
`Ex. 2030 ¶¶ 116−17). Thus, according to Patent Owner, an RFID tag that
`
`does not generate data during cloaking could not practice a claimed step of
`
`“disabling communication of data signals . . . during cloaking” because there
`
`would be no data of which to disable the communication. Id. at 12−13.
`
`For clarity, we construe the phrase “disabling communication of data
`
`signals . . . during cloaking” to require that it is not possible to communicate
`
`data signals during cloaked operation. According to our construction, an
`
`RFID tag that does not generate data during cloaking would satisfy the claim
`
`limitation of “disabling communication of data signals . . . during cloaking.”
`
`Patent Owner has provided no persuasive reason to construe this claim term
`
`as requiring that an RFID tag actually generate data that is then blocked
`
`from being communicated. We agree with Petitioner that Patent Owner’s
`
`proposed interpretation adds to the claim an explicit step of generating data
`
`signals that is not present. Reply 12–13.
`
`e. “logic circuit . . . isolates signals from said switch
`during said cloaking operation” and “isolating data
`signals from said switch . . . during cloaking operation”
`
`Patent Owner asks that we construe “logic circuit . . . isolates signals
`
`16
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`from said switch during said cloaking operation” and “isolating data signals
`
`from said switch . . . during cloaking operation.” Resp. 13. The claim term
`
`“logic circuit . . . isolates signals from said switch during said cloaking
`
`operation” appears in claims 6 and 7, which depend on claim 1, and also
`
`appears in claims 15 and 16, which depend on claim 10. The claim term
`
`“isolating said data signals from said switch . . . during cloaking operation”
`
`appears in claim 23, which depends on claim 22 which in turn depends on
`
`independent method claim 19.
`
`According to Patent Owner, these terms should be given their plain
`
`and ordinary meaning. Id. Patent Owner points to The American Heritage
`
`Dictionary of The English Language, Third Edition, 1992, which defines
`
`“isolate” as “to set apart or cut off from others.” Ex. 2030 ¶ 118 (citing Ex.
`
`2045, 956). Patent Owner argues that in the context of the ’264 patent, one
`
`of ordinary skill would have understood that a logic circuit that isolates
`
`signals from a switch sets apart or cuts off the signals from the switch.
`
`Resp. 13 (citing Ex. 2030 ¶ 118). Likewise, a person of ordinary skill would
`
`have understood that “isolating data signals” from a switch means to set
`
`apart or cut off those data signals from the switch. Id. (citing Ex. 2030
`
`¶ 120). According to Patent Owner, one of ordinary skill would have
`
`understood that in order to isolate signals, those signals “must be present.”
`
`Id.
`
`Thus, according to Patent Owner, a tag in which there are no signals
`
`to be isolated present at the logic circuit during cloaking does not meet the
`
`“isolate” limitation in claims 6, 7, 15 or 16; and such a tag also does not
`
`practice the “isolating” step of claim 23. Id.
`
`Petitioner argues that, similar to the “disabling” limitations, Patent
`
`17
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`Owner’s proposed interpretation is illogical because there is no point in
`
`generating data if the tag is not going to communicate it. Reply 19–20.
`
`We regard Patent Owner’s proposed construction as being too narrow.
`
`We construe the claim terms requiring “disabling” or isolating data only to
`
`the extent that we hold these terms do not require that signals actually be
`
`generated in order to be disabled or isolated from being transmitted.
`
`
`
`B. Challenge Based on Atkins (Ex. 1006)
`
`1. Overview of Atkins
`
`Figure 2 of Atkins is reproduced below.
`
`Atkins Figure 2 is a block diagram showing an interrogator and
`three transponders (RFID tags) according to an embodiment.
`
`
`
`Atkins describes a method and an identification system for communicating
`
`between reader (interrogator) 10 and transponders 1, 2, 3. Reader 10 has
`
`transmitter 11 for transmitting a signal. Each transponder 1, 2, 3 includes a
`
`receiver for receiving the reader signal and a transmitter for generating a
`
`transponder signal. When reader 10 recognizes a transponder signal from
`
`18
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`one of the transponders 1, it issues a mute instruction, muting all other active
`
`transponders 2, 3 and passing control to transponder 1, without the need for
`
`a specifically timed acknowledgement to transponder 1. Reader 10 may
`
`issue a single disable/wakeup instruction which disables the controlling
`
`transponder 1, returning control to the reader 10 and reactivating all muted
`
`(but not disabled) transponders 2, 3. Ex. 1006, 1.9 The “mute” instruction is
`
`communicated in the form of a “gap,” the length of which is ascertained by a
`
`gap length detector in the tag. When a tag’s normal (random) wait to
`
`respond period ends, it checks to see if the “mute” flag is still set to prohibit
`
`transmission. Id. at 10.
`
`Figure 4 of Atkins is reproduced below.
`
`
`
`Atkins Figure 4 is a block diagram of a transponder
`
`
`9 Exhibit page numbers reflect the actual page of the exhibit and not the
`printed page number of the document internal to the exhibit.
`
`19
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`according to an embodiment.
`
`Figure 4 is a block and schematic diagram of a tag which may be used
`
`with the reader of Atkins Figure 2. The tag includes a dipole antenna having
`
`poles 60 and 61. Atkins discloses:
`
`A code generator 62, when enabled by a logic circuit 64,
`modulates transistor Q1 with a code, using Manchester coding
`(signal 77). The timing for the code generator is derived from a
`local oscillator 66. Diodes D1 and D2 in combination with a
`capacitor C1 supply the power for [the] tag. The oscillator is
`disconnected from the random wait time generator when either
`FFl or FF2 is in the reset state (signals 70 and 72). FFl is set
`only when the tag is powered up and resets when the tag is
`switched off after being read successfully. FF2 is in the reset
`state when the tag is muted and in the set state on power up and
`when the tag is in its normal operating mode. When the tag
`initially receives the reader signal FFl will be in the set state.
`On power up the logic circuit 64 triggers the random wait timer
`63 to select a random value and begin a countdown.
`
`Id. at 10–11.
`
`2. Petitioner Contentions
`
`Petitioner provides a detailed explanation of how Atkins discloses all
`
`of the limitations of claims 1−24 at pages 10−23 of the Petition. The
`
`Petition makes frequent reference to the declaration testimony of Roger
`
`Stewart (Ex. 1001), which we find generally supports the arguments set forth
`
`in the Petition. Petitioner provides on page 11 of the Petition an annotated
`
`version of Atkins Figure 4, reproduced below, which summarizes
`
`Petitioner’s argued correspondence between Atkins and the main elements
`
`of the challenged claims.
`
`20
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`
`
`
`Petitioner reads the claimed antenna on Atkins antenna elements 60
`
`and 61; the claimed receiving connection on Atkins diode D3; the claimed
`
`switch on Atkins transistor Q1; the claimed input circuit on Atkins bus 68;
`
`the claimed logic circuit on Atkins circuit 67; and the claimed ground on
`
`Atkins ground path (no reference numeral) at center bottom of Figure 11.
`
`Pet. 10−23.
`
`Petitioner argues that RFID tag output is disabled during a cloaking
`
`period by the operation of logic circuit 19 disabling generation of the output
`
`signal. Pet. 12–13; see Tr. 21. Petitioner’s analysis of claims 1–24,
`
`supported by the testimony of Mr. Stewart, is persuasive. See Pet. 10–23;
`
`Ex. 1001 ¶¶ 80–135.
`
`3. Patent Owner Contentions
`
`Patent Owner characterizes Atkins as a “tag-talks-first” system. Resp.
`
`16. An interrogator (reader) “‘broadcasts an interrogation signal’ ‘to a
`
`21
`
`
`
`

`
`IPR2015-00814
`Patent 6,690,264 B2
`
`number of passive transponders’ which derive power from the interrogation
`
`signal ‘to generate a response signal, which is transmitted back to the
`
`interrogator.’” Id. at 18 (citing Ex. 1006 ¶ 2; Ex. 2030 ¶ 128). Each tag,
`
`upon r

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