`571-272-7822
`
`Paper 40
`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-00818
`Patent 8,237,568 B2
`____________
`
`
`
`Before JUSTIN T. ARBES, GLENN J. PERRY, and
`TREVOR M. JEFFERSON, Administrative Patent Judges.
`
`ARBES, Administrative Patent Judge.
`
`
`
`FINAL WRITTEN DECISION
`35 U.S.C. § 318(a) and 37 C.F.R. § 42.73
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`I. BACKGROUND
`
`Petitioners 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–11 of U.S. Patent No. 8,237,568 B2
`
`(Ex. 1004, “the ’568 patent”) pursuant to 35 U.S.C. §§ 311–319. On
`
`September 14, 2015, we instituted an inter partes review of claims 1–3 and
`
`6–8 on one ground of unpatentability (Paper 11, “Dec. on Inst.”). Patent
`
`Owner Neology, Inc. filed a Patent Owner Response (Paper 21,
`
`“PO Resp.”), and Petitioner filed a Reply (Paper 31, “Reply”).2 A combined
`
`oral hearing with Case IPR2015-008193 was held on May 10, 2016, and a
`
`transcript of the hearing is included in the record (Paper 39, “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. For the
`
`reasons that follow, we determine that Petitioner has shown by a
`
`preponderance of the evidence that claims 1–3 and 6–8 are unpatentable.
`
`
`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 1, 32, 33.
`
`2 Petitioner filed redacted (Paper 31) and unredacted (Paper 29) versions of
`its Reply and other materials, along with two motions to seal, which were
`conditionally granted. See Papers 27, 32. We do not rely on any sealed
`material in this Decision.
`
`3 U.S. Patent No. 8,587,436 B2, which was challenged in Case
`IPR2015-00815, and U.S. Patent No. 8,325,044 B2 (“the ’044 patent”),
`which is being challenged in Case IPR2015-00819, are continuations of
`the ’568 patent.
`
`
`
`
`2
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`A. The ’568 Patent
`
`The ’568 patent describes a system for “verifying and tracking
`
`identification information” using “a radio frequency (RF) identification
`
`device, an identification mechanism (e.g., a card, sticker), and an RF
`
`reader/writer.” Ex. 1004, col. 1, ll. 27–40. The system facilitates electronic
`
`identification by reading data stored on the RF device (without having to
`
`contact the device) and verifying the data against known identification
`
`information. Id. at col. 2, ll. 25–53. The system also provides security by
`
`checking and validating security keys stored on the RF device before reading
`
`the data. Id. The ’568 patent explains that the system can be used in a
`
`number of different applications, such as for “vehicle identification,”
`
`“border crossing solutions,” or “toll booths.” Id. at col. 10, ll. 11–53, Fig. 4.
`
`Figure 2 of the ’568 patent is reproduced below.
`
`
`
`
`3
`
`
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`As shown in Figure 2, dual frequency RF device 110 comprises modulator
`
`215 that receives baseband signals from an antenna, security management
`
`unit 255, cryptographic block 210, and electrically erasable programmable
`
`read-only memory (EEPROM) memory 205 that stores data. Id. at col. 2,
`
`ll. 26–53, col. 20, ll. 32–41. RF device 110 receives security keys from an
`
`RF reader, and security management unit 255 “checks and validates” the
`
`keys to “grant or deny access to the memory chip.” Id. at col. 2, ll. 47–51.
`
`
`
`B. Illustrative Claim
`
`Claim 1 of the ’568 patent recites:
`
`1. A system of verifying registration information of a
`vehicle, the system including:
`
`a database configured to store vehicle identification
`information;
`
`a radio frequency device, the radio frequency device
`including a radio frequency antenna and a chip, the chip
`comprising:
`
`a memory, the memory configured to store a security key
`and vehicle identification information, and
`
`a processor coupled with the memory the processor
`configured to provide access to the memory based on a security
`key, the processor further configured to:
`
`receive a signal via the radio frequency antenna,
`the signal comprising a request to access the memory and
`a security key,
`
`compare the security key included in the received
`message with the security key stored in the memory,
`
`provide the vehicle information in response to the
`access request when the security keys match; and
`
`a reader coupled with the database, the reader configured
`
`to:
`
`
`
`
`4
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`generate the access request, insert the security key
`into the generated request, and transmit the access
`request to the radio frequency device,
`
`receive the vehicle information from the radio
`frequency device,
`
`cause the vehicle information to be compared to
`the vehicle information stored in the database, and
`
`verify the information related to the vehicle based
`on the comparison.
`
`
`
`C. Prior Art
`
`The pending ground of unpatentability in the instant inter partes
`
`review is based on the following prior art:
`
`U.S. Patent No. 5,627,544,
`(Ex. 1009, “Snodgrass”); and
`
`issued May 6, 1997
`
`U.S. Patent No. 5,819,234, issued Oct. 6, 1998 (Ex. 1008,
`“Slavin”).
`
`
`
`D. Pending Ground of Unpatentability
`
`The instant inter partes review involves the following ground of
`
`unpatentability:
`
`References
`
`Basis
`
`Claims
`
`Slavin and Snodgrass
`
`35 U.S.C. § 103(a) 1–3 and 6–8
`
`
`
`5
`
`
`
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`II. ANALYSIS
`
`A. Claim Interpretation
`
`The Board interprets claims using the “broadest reasonable
`
`construction in light of the specification of the patent in which [they]
`
`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).
`
`
`
`
`
`
`6
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`1. Previously Interpreted Terms
`
`In the Decision on Institution, we interpreted “security key” in claim 1
`
`of the ’568 patent to mean a key that is checked and validated to grant or
`
`deny access to a memory, and encouraged the parties to address the term
`
`further during trial if necessary. Dec. on Inst. 5–8. We also interpreted
`
`“second signal” in claims 2 and 6 as referring to the “signal” of claim 1. Id.
`
`at 8–9. The parties do not dispute these interpretations in their Patent Owner
`
`Response and Reply. See PO Resp. 12; Reply 7–8. We do not perceive any
`
`reason or evidence that compels any deviation from these interpretations.
`
`Accordingly, we adopt our previous analysis of “security key” and “second
`
`signal” for purposes of this Decision.
`
`
`
`2. “Provide Access to the Memory Based on a Security Key”
`
`In its Response, Patent Owner argues that the phrase “provide access
`
`to the memory based on a security key” in claim 1 should be interpreted to
`
`mean “provide the capability to read or write protected information based on
`
`a key that is checked and validated to grant or deny access to the memory.”4
`
`PO Resp. 14–15. According to Patent Owner, the phrase means that
`
`the decision to grant or deny access to the chip’s memory is
`made by the processor only after the processor has actually
`received the security key. A [person of ordinary skill in the art]
`would understand that the security key is similar to a key that
`
`
`4 With respect to the individual words of the phrase, Patent Owner argues
`that “provide access” has the same meaning as “grant access” and means
`“provide the capability to read or write information,” and “memory” means
`an “area for storing computer instructions and data for either short-term or
`long-term purposes,” where “data” is “any information, represented in
`binary, that a computer receives, processes, or outputs.” PO Resp. 13–14.
`We address the individual words in our discussion of the full phrase herein.
`
`
`
`
`7
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`unlocks a door. Without the key the door is closed; and in the
`context of the ’568 Patent, without the security key, there is no
`access to any of the information in the memory which is
`protected by the security key. Thus, [a radio-frequency
`identification (RFID)] system in which a reader has the
`capability to read or write protected information to the chip’s
`memory prior to the chip’s processor having received, checked
`and validated the security key, would not meet the limitations
`of claim 1 of the ’568 Patent.
`
`Id. at 14. Petitioner disagrees with various aspects of Patent Owner’s
`
`proposed interpretation, and argues that the phrase instead means that
`
`“access to memory depends, in part, on the security key.” Reply 7–15,
`
`18–20 (emphasis omitted).
`
`Based on our review of the full record and the parties’ arguments, we
`
`are persuaded that Patent Owner’s proposed interpretation is too narrow, and
`
`incorrectly limits the claim in five respects. First, according to Patent
`
`Owner, access to the memory includes the ability to read from or write to the
`
`memory. PO Resp. 13–15. Claim 1, however, only recites information
`
`being provided from the memory to the reader, not the reader writing
`
`information to the memory. Thus, we do not include in our interpretation
`
`the concept of writing information to the memory.
`
`Second, Patent Owner appears to contend that access to the memory
`
`must be based only on checking and validating the security key (i.e., the
`
`system cannot check any other information). See id. at 14, 38–39 (arguing
`
`that Snodgrass does not teach the “provide access” limitation because there
`
`are “several other parameters in addition to the arbitration number that must
`
`be checked”). We agree with Petitioner that the claim language is not
`
`limited in that respect. See Reply 18–20. Claim 1 specifies that the
`
`processor is configured to compare the received security key to the one
`
`
`
`
`8
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`stored in memory and provide the vehicle identification information from
`
`memory if there is a match. Thus, access to the vehicle identification
`
`information in memory is contingent on, or “based on,” the security keys
`
`matching. The claim does not include any language precluding other
`
`security checks from being performed as well. Based on Patent Owner’s
`
`locked door analogy quoted above, the parties discussed at the hearing that a
`
`door may have both a key lock and a deadbolt lock, but access to the house
`
`is still “based on” the physical key matching the pins in the key lock. See
`
`PO Resp. 14; Tr. 9:8–18, 45:12–46:13. We agree that the “based on”
`
`language in claim 1 should be read the same way.
`
`Third, Patent Owner appears to argue that claim 1 requires all data
`
`stored in memory to be “protected” by the security key (i.e., nothing in
`
`memory may be accessible without checking and validating the security
`
`key). See PO Resp. 14, 26–35 (arguing that “the tag’s decision to grant or
`
`deny access to the tag’s memory is made only after the processor has
`
`actually received the security key,” and Snodgrass does not teach the
`
`“provide access” limitation because the REVISION data field “is accessible
`
`to the reader without the reader providing an arbitration number” (emphasis
`
`omitted)). Interpreting claim 1 in the manner Patent Owner suggests would
`
`be inconsistent with the language of the claims. Claim 1 recites that the
`
`“memory [is] configured to store a security key and vehicle identification
`
`information.” Thus, because the security key is in memory itself, it must be
`
`accessed first so that it can be checked and validated to grant or deny access
`
`to the memory. See Tr. 13:21–14:4, 19:3–9. In addition, dependent claim 4
`
`recites granting access to the memory based on a received “second security
`
`key,” and sending “further memory contents.” See Reply 15; Tr. 13:21–
`
`
`
`
`9
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`14:4. Access to the portion of memory storing the “further memory
`
`contents” is granted based on the “second security key,” not based on the
`
`“security key” of claim 1. Thus, the claims contemplate that there are
`
`certain portions of memory (i.e., at least the portion storing the vehicle
`
`identification information) for which access is granted based on the security
`
`key, and certain portions of memory that may be accessed without checking
`
`and validating the security key (e.g., the portion storing the security key
`
`itself). Patent Owner agreed with this principle at the hearing. Tr. 52:9–20.
`
`Patent Owner’s declarant, Jack Goldberg, agreed as well. Ex. 1049, 56:12–
`
`57:22 (agreeing that “there may be some information [in memory] that’s
`
`protected by a security key and some information that’s not,” such as the
`
`security key itself). Accordingly, in the context of claim 1, providing access
`
`to the “memory” means providing the capability to read certain data stored
`
`in the memory.
`
`Fourth, Patent Owner contends that the “primary purpose” of the
`
`’568 patent (which allegedly distinguishes the claims from prior art
`
`references like Snodgrass) is to “provide security to the contents of a tag’s
`
`memory.” PO Resp. 7–8. Regardless of how the “primary purpose” of
`
`claim 1 is characterized, its scope is defined by the language of the claim.
`
`Claim 1 does not recite any encryption, and the “security” provided by virtue
`
`of the “security key” is based on what is recited expressly in the claim—
`
`determining whether the received security key matches the security key
`
`stored in memory and providing protected information only when there is a
`
`match. See Dec. on Inst. 7–8. This reading is supported by Patent Owner’s
`
`statements in a previous district court case involving related patents:
`
`
`
`
`10
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`THE COURT: What you are saying is that the communication
`isn’t encrypted, but isn’t the information in the reader and the
`tag encrypted?
`
`[PATENT OWNER’S COUNSEL]: I don’t believe so.
`
`THE COURT: Okay. So anybody who could figure out what’s
`going on between the reader and the tag could do this?
`
`[PATENT OWNER’S COUNSEL]: Yes.
`
`THE COURT: So how is it a security key?
`
`[PATENT OWNER’S COUNSEL]: Well, it’s making sure that
`– that’s right. So it’s a low level of security potentially, if that’s
`the point. But it is making sure that I am talking to a reader
`that got my random number before I send it back. . . .
`
`Ex. 1031, 108:3–16 (emphasis added);5 see Reply 10. We do not read any
`
`additional “security” requirements into the claim.
`
`Fifth, Patent Owner contends that “[t]he claim language of the
`
`’568 Patent . . . clearly shows that singulation is not part of the inventions.”
`
`PO Resp. 8–11. Singulation is “a method utilized in an RFID system that
`
`allows an RFID reader to identify a specific tag within a group of tags in its
`
`RF field” and avoid collisions when multiple tags are “sending and receiving
`
`signals in the same shared frequency band . . . at the same time.” Id. at 8
`
`(citing Ex. 2032 ¶ 24); see also Ex. 1016 ¶ 45 (“The process of identifying a
`
`single tag is called ‘singulation.’”). Patent Owner argues that the
`
`embodiments described in the Specification of the ’568 patent involve a
`
`single tag within the field of a reader, and claim 1 “includes one and only
`
`one radio frequency device (tag).” PO Resp. 9–11. Thus, the claimed
`
`system “assumes” that “singulation has already occurred prior to any
`
`
`5 When citing Exhibits 1031 and 2022, we refer to the page numbers of the
`original transcript, rather than the page numbers in the lower-right corner
`added by the parties.
`
`
`
`
`11
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`exchange of protected information and prior to the transmission of any
`
`security key.” Id. (emphasis omitted). According to Patent Owner, prior art
`
`like Snodgrass, which is directed to “singulation” rather than “security,”
`
`does not disclose “provid[ing] access to the memory based on a security
`
`key,” as recited in claim 1. Id. at 11.
`
`We do not read into claim 1 any limitation with respect to singulation.
`
`Neither the claim nor the Specification mention the concept. Again, claim 1
`
`recites a particular set of components that are configured to do certain
`
`things; if those components are present in the prior art, the prior art may
`
`render the claim obvious, regardless of the ultimate purpose behind why the
`
`components are so configured (e.g., for singulation or any other function).6
`
`We also disagree with Patent Owner that claim 1 is limited to “one and only
`
`one” radio frequency device. See id. at 10. Because claim 1 uses the
`
`open-ended term “including,” the fact that it recites a single “radio
`
`frequency device” does not preclude the system from having additional
`
`RF devices. See Amgen Inc. v. Hoechst Marion Roussel, Inc., 314 F.3d
`
`1313, 1344–45 (Fed. Cir. 2003) (“comprising” and “including” mean that
`
`“the named elements are essential, but other elements may be added and still
`
`form a construct within the scope of the claim” (citation and internal
`
`quotation marks omitted)). Likewise, exemplary embodiments are described
`
`in the Specification with respect to one RF device communicating with one
`
`RF reader, but Patent Owner does not point to any language indicating that
`
`the invention is limited to communication with a single RF device. See, e.g.,
`
`
`6 The testimony of Petitioner’s declarant, Roger Stewart, is consistent with
`this reading, as he testified that although the ’568 patent “wasn’t an
`anticollision patent, . . . the claims are broad enough to cover anticollision
`situations.” Ex. 2022, 204:19–205:8.
`
`
`
`
`12
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`Ex. 1004, col. 2, ll. 19–53 (“This embodiment comprises an RF device 110
`
`. . . and an RF reader/writer 125.”), col. 10, ll. 15–24. Thus, we do not
`
`interpret claim 1 to exclude any use of the recited components for
`
`singulation, or any requirement that singulation already have occurred; the
`
`claim means just what it says.
`
`Accordingly, applying the broadest reasonable interpretation of the
`
`claims in light of the Specification, we interpret “provide access to the
`
`memory based on a security key” to mean provide the capability to read
`
`certain data stored in the memory (i.e., at least the vehicle identification
`
`information) based on checking and validating the security key.
`
`
`
`B. Analysis
`
`Petitioner argues that claims 1–3 and 6–8 are unpatentable over Slavin
`
`and Snodgrass under 35 U.S.C. § 103(a), relying on the supporting
`
`testimony of Mr. Stewart. Pet. 42–57, 59 (citing Ex. 1001). We have
`
`reviewed the Petition, Patent Owner Response, and Reply, as well as the
`
`evidence discussed in each of those papers, and are persuaded, by a
`
`preponderance of the evidence, that claims 1–3 and 6–8 are unpatentable
`
`over Slavin and Snodgrass.
`
`
`
`1. Slavin
`
`Slavin describes an “electronic toll collection system” where a toll
`
`collection plaza receives information from RF transponders in vehicles
`
`passing through the plaza. Ex. 1008, col. 1, ll. 4–8, col. 5, ll. 40–49.
`
`
`
`
`13
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`Figure 1 of Slavin is reproduced below.
`
`
`
`Figure 1 depicts an automatic toll collection plaza with Roadside Collection
`
`Stations (RCS’s) 24, 26, and 28 that communicate wirelessly with RF
`
`transponders 30 in vehicles 16, 18, and 20. Id. at col. 5, ll. 40–49. The
`
`RCS’s interrogate the transponders, and “each of the transponders 30
`
`broadcasts a unique tag number associated therewith which is received and
`
`correlated by the RCS’s with a toll account number of the vehicle.” Id. at
`
`col. 1, ll. 33–40, col. 5, ll. 49–52. Toll plaza computer 32 uses the tag
`
`number to identify the transponder and corresponding account, causes the
`
`toll amount to be deducted from the account, and alerts the driver
`
`accordingly (e.g., by flashing green light 34). Id. at col. 1, ll. 33–40, col. 9,
`
`ll. 49–63.
`
`
`
`2. Snodgrass
`
`Snodgrass describes a messaging protocol for establishing RF
`
`communication between an interrogator and a particular responder from
`
`
`
`
`14
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`among a group of responders, such as in a baggage handling system in an
`
`airport terminal. Ex. 1009, col. 1, ll. 29–35. Figure 1 of Snodgrass is
`
`reproduced below.
`
`
`
`Figure 1 depicts commander station 10, which communicates wirelessly
`
`with a group of responder stations, including responder station 40. Id. at
`
`col. 5, ll. 41–53. Responder station 40 includes register array 66, memory
`
`64, flag register 84 (storing addressed-bit 86 and locked-bit 88), and random
`
`number generator 90. Id. at col. 6, ll. 57–61, col. 7, ll. 40–47. “Memory 64
`
`is used to store values for responder station identification and data related to
`
`the communication system application,” such as, in the case of a baggage
`
`handling system, “data describing [the] destination for the item to which the
`
`tag is attached.” Id. at col. 7, ll. 12–19. Register array 66 stores additional
`
`data, such as a random number (designated as the ARBITRATION
`
`NUMBER) generated by random number generator 90. Id. at col. 7,
`
`ll. 21–30, 50–55. Addressed-bit 86 is set to “indicate whether responder
`
`
`
`
`15
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`station 40 has been addressed in a received command message,” and
`
`locked-bit 88 is set to “indicate whether responder station 40 should ignore
`
`messages from a commander station because responder station 40 has
`
`already announced its identification to a commander station.” Id. at col. 7,
`
`ll. 40–47.
`
`Snodgrass discloses a communication system protocol comprising
`
`various actions taken by the commander station, shown in Figure 10, and
`
`actions taken by the responder station, shown in Figure 11 reproduced
`
`below.
`
`
`
`Figure 11 is a state diagram of the protocol followed by the responder
`
`station. Id. at col. 5, ll. 26–27, col. 12, ll. 30–38.
`
`The protocol begins by the commander station first broadcasting an
`
`“identify, clear, and generate” (IDCG) command to a group of responder
`
`stations. Id. at col. 13, ll. 40–45. The IDCG command causes each
`
`responder station to “generate a random number and retain it as its
`
`ARBITRATION NUMBER, and broadcast a response.” Id. at col. 13,
`
`
`
`
`16
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`ll. 45–48, col. 15, ll. 47–52, Fig. 11 (state 318). The IDR response from
`
`each responder station includes, inter alia, REVISION, LOCAL ID, and
`
`ARBITRATION NUMBER data fields. Id. at col. 12, ll. 5–21, col. 15,
`
`ll. 47–52, Figs. 8, 9 (format 192). REVISION is “a one-byte value set by a
`
`communication system developer at the time of manufacture or
`
`commissioning of a responder station,” and “represents the responder station
`
`configuration and connotes its capability.” Id. at col. 12, ll. 17–21. LOCAL
`
`ID is a “unique identification number assigned” to the commander station.
`
`Id. at col. 11, ll. 11–14.
`
`The commander station waits to receive responses and then
`
`determines whether a collision between multiple responses occurred. Id. at
`
`col. 13, ll. 51–57. If only one response was received, the commander station
`
`“determines and validates the responding responder station’s
`
`ARBITRATION NUMBER.” Id. at col. 14, ll. 7–13. The commander
`
`station then selects a command to communicate with the particular
`
`responder station, such as a read (RD) command, and broadcasts it to the
`
`responder stations. Id. at col. 14, 13–23. The RD command includes, inter
`
`alia, the ARBITRATION NUMBER identifying the responder station as the
`
`one that “should act on [the] command and should reply,” and causes the
`
`responder station to set its locked-bit 88. Id. at col. 11, ll. 18–22, col. 14,
`
`ll. 13–23, Figs. 5, 6 (format 144).
`
`In response to receiving the RD command, the responder station
`
`determines whether it has been addressed by determining whether the
`
`ARBITRATION NUMBER stored in its register array is “bit-wise identical
`
`to [the] ARBITRATION NUMBER as received in the command.” Id. at
`
`col. 15, ll. 26–32, Fig. 11 (address check state 312). If so, the responder
`
`
`
`
`17
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`station responds with a message that includes, inter alia, its stored
`
`ARBITRATION NUMBER, TAG, and DATA. Id. at col. 12, ll. 5–29,
`
`Figs. 8, 9 (response format 194). TAG is a long value identifying the
`
`responder station “throughout the life of the communication system
`
`application,” whereas the ARBITRATION NUMBER is a short value
`
`identifying the responder station only for the period of time when it is in
`
`communication with a particular commander station. Id. at col. 11,
`
`ll. 22–33. DATA includes data stored in various memory devices in the
`
`responder station, and may include “some or all of the contents of any or all
`
`devices including memory 64, register array 66, flag register 84, or random
`
`number generator 90.” Id. at col. 7, ll. 13–20, col. 12, ll. 26–29. Once the
`
`commander station receives a proper response to the RD command, “two
`
`party uninterrupted communication between commander station 10 and one
`
`responder station 60 has been established.” Id. at col. 14, ll. 23–30.
`
`
`
`3. Level of Ordinary Skill in the Art
`
`Section 103(a) forbids issuance of a patent when “the
`differences between the subject matter sought to be patented
`and the prior art are such that the subject matter as a whole
`would have been obvious at the time the invention was made to
`a person having ordinary skill in the art to which said subject
`matter pertains.”
`
`KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007) (quoting 35 U.S.C.
`
`§ 103(a)). Petitioner’s declarant, Mr. Stewart, testifies that he believes a
`
`person of ordinary skill in the art would have had “a graduate degree in
`
`engineering or physics” and “at least 2–4 years of relevant experience in
`
`designing and developing RFID tags and readers, including understanding
`
`RFID systems and communication protocols.” Ex. 1001 ¶ 63. Patent Owner
`
`
`
`
`18
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`argues that a person of ordinary skill in the art would have had “a university
`
`degree in electrical engineering or a related field and at least two years of
`
`industrial or academic experience in radio frequency data communication
`
`and/or RFID systems.” PO Resp. 15–16. According to Patent Owner, a
`
`person of ordinary skill in the art would have had “experience in RFID
`
`communication systems and protocols,” but need not have “actually
`
`developed or designed components” for such systems. Id. Petitioner
`
`disagrees, arguing that design and development experience is necessary.
`
`Reply 2–4.
`
`Based on our review of the ’568 patent, the types of problems and
`
`solutions described in the ’568 patent and cited prior art, and the testimony
`
`of the parties’ declarants, we conclude that a person of ordinary skill in the
`
`art would have had a degree in electrical engineering or a similar field and at
`
`least two years of industrial or academic experience with radio frequency
`
`data communication and/or RFID systems, including an understanding of
`
`RFID systems and communication protocols. We do not include a
`
`requirement of actually designing and developing RFID tags and readers.
`
`The challenged claims are directed mainly to what signals are exchanged,
`
`and under what circumstances, between a “radio frequency device” and
`
`“reader,” not the mechanics of how the communications work. The
`
`Specification of the ’568 patent also describes the physical construction of
`
`such devices at a fairly high level of granularity, as does the cited prior art.
`
`See, e.g., Ex. 1004, col. 2, ll. 18–59; Ex. 1008, col. 1, l. 4–col. 2, l. 48;
`
`Ex. 1009, col. 5, l. 41–col. 10, l. 37. We are satisfied that an individual
`
`having general experience with radio frequency data communication and/or
`
`RFID systems, as well as an understanding of RFID systems and
`
`
`
`
`19
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`communication protocols, would have been able to understand the
`
`’568 patent and similar art, without having actually designed and developed
`
`RFID tags and readers.
`
`Applying the level of ordinary skill in the art set forth above for
`
`purposes of this Decision, we conclude that both of the parties’ declarants,
`
`Mr. Stewart and Mr. Goldberg, are qualified to offer expert testimony in this
`
`proceeding, and we do not give Mr. Goldberg’s testimony less weight
`
`merely based on his qualifications, as Petitioner advocates. See Ex. 1001
`
`¶¶ 8–16; Ex. 1002 (describing the qualifications of Mr. Stewart, who has
`
`bachelor’s and master’s degrees in electrical engineering and experience
`
`with RF technology); Ex. 2032 ¶¶ 3–16, pp. 92–106 (describing the
`
`qualifications of Mr. Goldberg, who has bachelor’s and master’s degrees in
`
`electrical engineering and experience with RF technology); Reply 5–7.
`
`
`
`4. Claim 1
`
`a. Slavin and Snodgrass Teach Every Limitation of Claim 1
`
`Petitioner has presented evidence showing that Slavin and Snodgrass
`
`teach every limitation of claim 1. Pet. 42–52. Specifically, Petitioner argues
`
`that Snodgrass teaches a “radio frequency device” (i.e., responder station)
`
`with a “memory” and “processor” that receives a signal (i.e., RD command)
`
`comprising a “security key” (i.e., arbitration number), compares the received
`
`arbitration number with the one stored in memory, and provides
`
`identification information (i.e., TAG or DATA) when the arbitration
`
`numbers match. Id. at 45–52.
`
`
`
`
`20
`
`
`
`
`
`IPR2015-00818
`Patent 8,237,568 B2
`
`
`To demonstrate how it maps the signals of Snodgrass to the signals of
`
`claim 1, Petitioner provides a chart on page 44 of its Petition, the relevant
`
`portion of which is reproduced below.
`
`
`
`Petitioner’s chart illustrates the various signals between the commander
`
`station and responder station in Snodgrass. Id. at 44. Petitioner relies on
`
`Slavin as teaching other limitations of claim 1, such as a “database
`
`configured to store vehicle identification information” and the transmission
`
`of “vehicle identification information” (i.e., the unique tag number
`
`identifying the vehicle) from a transponder to a reader. Id. at 45–46, 48–49.
`
`According to Petitioner, a person of ordinary skill in the art would have had
`
`reason to combine Slavin’s teaching of a transponder bein