throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________________
`
`
`
`
`
`iAPARTMENTS, INC.,
`Petitioner
`
`v.
`
`
`EDST LLC,
`Patent Owner
`
`
`
`
`
`
`
`
`
`
`
`Case PGR2022-00059
`Patent 11,189,118
`_________________
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`
`TABLE OF CONTENTS
`
`
`
`INTRODUCTION .............................................................................................. 1 
`I. 
`II.  THE ’118 PATENT ........................................................................................... 3 
`III.  CLAIMS 1-20 HAVE WRITTEN DESCRIPTION (GROUND 1) .................. 6 
`A.  The Office already decided the written description issue raised in the
`Petition, and Petitioner does not justify a do-over ........................................ 6 
`B.  The ’118 Patent’s specification shows “possession” of the limitations
`Petitioner contests ....................................................................................... 12 
`C.  Petitioner’s contrary arguments do not outweigh clear written description
`support ......................................................................................................... 15 
`IV.  THE CAHILL-DEROS GROUND FAILS (GROUND 2) .............................. 21 
`A.  Petitioner makes no real attempt to show that Cahill or Deros discloses a
`“property management platform” ............................................................... 21 
`1.  Petitioner ignores a fundamental aspect of the claimed “property
`management platform”........................................................................... 22 
`2.  Petitioner’s terse analysis is an improper notice pleading ..................... 26 
`B.  Petitioner fails to establish that the Cahill and Deros combination teaches
`“a Long Range (LoRa) wide area network (LoRaWAN) communication
`link” ............................................................................................................. 28 
`1.  Petitioner’s motivation is inadequate and nonsensical .......................... 29 
`2.  Deros does not teach a smart hub with LoRa, as asserted in Petitioner’s
`combination ............................................................................................ 33 
`C.  Petitioner does not fully address the “smart hub” limitations .................... 37 
`V.  THE KRAUS GROUNDS FAIL (GROUNDS 3-5) ........................................ 40 
`A.  Petitioner’s reliance on Deros for the LoraWAN features works no better
`with Kraus than with Cahill (Ground 3) ..................................................... 40 
`1.  Petitioner’s one-paragraph discussion on motivation fails to persuade 41 
`2.  Deros does not teach a smart hub with LoRa, as asserted in Petitioner’s
`combination ............................................................................................ 42 
`B.  Petitioner’s vague and ambiguous mapping to the claimed “property
`management system” makes institution untenable (Grounds 3-5) ............. 43 
`
`i
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`C.  Petitioner does not substantiate its assumption that Kraus’s brief disclosure
`on generating signals satisfies multiple claim limitations (Grounds 3-5) .. 46 
`D.  Petitioner’s Kraus-Ho combination falls short of the claimed LoRaWAN
`features and lacks sufficient motivation (Grounds 4-5).............................. 49 
`1.  Petitioner is wrong: Ho does not “disclose” a LoRaWAN link between
`a smart hub and a property management platform ................................ 49 
`2.  Accounting for Ho’s true disclosure, Petitioner’s Kraus-Ho
`combination diverges from the claimed LoRaWAN first interface ...... 53 
`3.  Petitioner’s generic motivation analysis is divorced from its mapping to
`the Challenged Claims and also ignores the specific details of Kraus
`and Ho .................................................................................................... 55 
`E.  Petitioner makes no effort to show Ho is prior art (Grounds 4-5) .............. 57 
`VI.  CONCLUSION ................................................................................................ 60 
`
`
`
`
`
`ii
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`
`EXHIBITS
`
`US Patent Publication No. 2019/0371096, Fisher
`
`US Patent Publication No. 2016/0241543, Jung, et al.
`
`US Patent Publication No. 2017/0046893, Tseng, et al.
`
`US Patent Application No. 16/162,262
`
`
`
`
`EX2001
`
`EX2002
`
`EX2003
`
`EX2004
`
`
`
`
`
`
`
`
`
`
`
`iii
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`
`I. INTRODUCTION
`Petitioner iApartment’s Petition is riddled with conclusory assertions and
`
`unfinished proofs that make post grant review untenable. Time and time again,
`
`Petitioner declares that the prior art discloses a claim limitation without even
`
`attempting to explain why that is so. This is not how post grant reviews work.
`
`In these proceedings, the petitioner bears the burden of proof from the start to
`
`show at least a reasonable likelihood that it will prevail in establishing
`
`unpatentability. Conclusory assertions are not assumed true, and the Board does not
`
`simply take the petitioner’s word for it. And yet, that is exactly what Petitioner
`
`would have the Board do here—bypass its requirements that the petitioner must
`
`explain how the challenged claim is construed and how the construed claim is
`
`unpatentable. In short, Petitioner has not made the necessary showing.
`
`For example, when analyzing the Challenged Claims1 against the Cahill
`
`reference (EX1005) in Ground 2 and the Kraus reference (EX1006) in Grounds 3-5,
`
`Petitioner makes blanket statements that the references disclose the claimed
`
`“property management platform” without any meaningful explanation or analysis of
`
`what that claim term means and why its meaning embraces what the references
`
`1 Claims 1-20.
`
`
`
`1
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`describe.2 See infra Sections IV.A (Cahill) and V.B (Kraus). As another example,
`
`when addressing the claimed “smart hub,” Petitioner assumes, without actually
`
`proving, that Cahill and Kraus disclose the detailed limitations of “receiv[ing]
`
`control information” and “transmit[ting] a command derived from the control
`
`information.” See infra Sections IV.C (Cahill) and V.C (Kraus). Far from
`
`disclosing these limitations, as is required for Petitioner to make its case, Cahill and
`
`Kraus are silent in this regard.
`
`While illustrative, these examples are not comprehensive of the Petition’s
`
`litany of errors. Elsewhere, the Petition:
`
` Fails to support its proposed combination of Cahill-Deros and Kraus-
`
`Deros, and Kraus-Ho with legally sufficient motivation rationales (see
`
`infra Section IV.B, V.A and V.D);
`
` Makes no effort to establish that Ho’s teachings are actually prior art
`
`(see infra Section V.E).
`
`All of these fundamental flaws in the Petition are beyond repair. The efficient
`
`timeline Congress implemented for post grant review does not permit petitioners to
`
`make wholesale changes to the grounds initially put forward. But impermissible
`
`wholesale changes are exactly what Petitioner would need to even potentially redress
`
`2 All emphasis added.
`
`
`
`2
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`the many problems that plague its Petition. Institution is not warranted, deserved,
`
`or even feasible.
`
`II. THE ’118 PATENT
`Patent Owner EDST, LLC is one in a group of companies that provides
`
`technology solutions purpose-built for multi-family residential properties, such as
`
`apartments, based on the inventions of the ’118 Patent. At the heart of this solution
`
`is a unique smart hub. The smart hub receives control information from a property
`
`management platform through a wide area network (WAN) communication link and
`
`transmits commands to a door lock through a non-WAN communication link. See
`
`EX1001, Figure 1 (annotated below).
`
`
`
`3
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`At the time of the ’118 Patent, conventional keyless entry systems utilized one
`
`of two types of locks: “online door locks” or “offline door locks.” EX1001, 1:43-
`
`44. These “online” door locks could be controlled to lock and unlock both remotely
`
`(e.g., through an internet connection) and locally (e.g., by a device such as a
`
`smartphone or fob). Id., 1:44-48. Conventional “offline” door locks3 were typically
`
`controlled locally by a device placed in proximity to the lock. Id., 1:49-52.
`
`Conventional online and offline door locks both had disadvantages. Online
`
`door locks, for example, required a network communication infrastructure (such as
`
`Wi-Fi, or the like), which increased capital costs, installation costs, and operating
`
`costs. Id. at 1:52-58.
`
`Though less costly than online door locks, conventional offline door locks
`
`“require[d] an individual, such as a property manager or property maintenance
`
`personnel, to connect . . . an external device . . . to the offline door lock and then use
`
`software or another utility provided by the external device to disable access
`
`credentials.” Id., 1:67-2:6. This proved a slow and cumbersome process, as it
`
`required one or more individuals to physically come to the lock’s location to alter
`
`credentials. Id., 1:59-2:20. The need for in-person access, and the concomitant
`
`
`3 The conventional offline door locks referenced are distinct from the “offline door
`
`locks” recited in the Challenged Claims.
`
`4
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`delays, posed an inconvenience to residents and visitors. It also introduced security
`
`risks. For instance, access by certain individuals could not be revoked in a timely
`
`manner in the event such individuals were to become violent or abusive. Id., 1:59-
`
`2:20, 19:22-31.
`
`The ’118 Patent’s inventors set out to solve the various problems with
`
`conventional offline and online entry systems. Their solution—the ’118 Patent’s
`
`unique smart hub, which provides a communication interface between a property
`
`management platform and one or more door locks installed at a multi-family
`
`residential property. Id., 2:34-37. For the first time, with this unique smart hub,
`
`entry systems at multi-family properties could leverage the remote credential
`
`management functionality lacking from conventional offline locks without
`
`incurring the costs and complications associated with conventional online locks.
`
`In other words, the ’118 Patent’s smart hub enables users of the management
`
`platform (such as property managers) to disable, enable, or otherwise change access
`
`credentials for each of the door locks on the system, all without requiring the use of
`
`a costly Wi-Fi communications infrastructure. Id. at 2:34-37, 18:23-24.
`
`Patent Owner EDST, LLC, by and through its wholly owned subsidiary Quext
`
`IoT, LLC, has successfully marketed and sold products featuring smart thermostat
`
`hubs and smart locks that embody the Challenged Claims since 2020. These patent-
`
`5
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`practicing products are installed in or contracted to be installed in 20 different
`
`properties representing nearly 15,600 doors throughout the United States.
`
`
`
`See https://onequext.com/product/iot.
`
`III. CLAIMS 1-20 HAVE WRITTEN DESCRIPTION (GROUND 1)
`Petitioner invites the Board to revisit a written description issue that was
`
`addressed on the record during examination. The Board should decline to do so.
`
`The fact that Petitioner turns a blind eye to express disclosure in the ’118 Patent does
`
`not justify re-litigating what the Office already decided.
`
`A. The Office already decided the written description issue raised in
`the Petition, and Petitioner does not justify a do-over
`The limitations Petitioner objects to represent a core functionality of the ’118
`
`Patent’s system that is disclosed throughout the specification and figures. As
`
`detailed below, an experienced primary examiner fully considered these limitations
`
`and concluded that their written description in the ’118 Patent is sufficient.
`
`6
`
`

`

`The limitations questioned by Petitioner are:
`
`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`
` “the smart hub [comprising]. . . a second communication interface
`configured to communicatively couple . . . to a user device associated
`with an occupant of the unit via a non-LoRaWAN communication link”
`(Element [1c]); and
` “the smart hub configured to be communicatively coupled to a user
`device associated with an occupant of the unit via the non-LoRaWAN
`communication link” (Elements [11c], [17c]).
`
`Petitioner does not dispute that Examiner Pendleton, an experienced primary
`
`examiner, carefully considered these “user device” limitations and determined that
`
`they have written description support. Verifying written description support under
`
`35 U.S.C. § 112 is a fundamental part of examining an application. Accordingly,
`
`the Office’s examination procedures require examiners to analyze written
`
`description support for the claims and amendments to any application. See MPEP §
`
`2163 (establishing “policies and procedures to be followed by Office personnel in
`
`the evaluation of any patent application for compliance with the written description
`
`requirement 35 U.S.C. § 112”). Thus, Examiner Pendleton was duty bound to
`
`consider written description when examining the Challenged Claims, including the
`
`“user device” limitations. Petitioner gives no explanation for why Examiner
`
`Pendleton failed to do his job.
`
`7
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`In fact, the record shows that Examiner Pendleton did exactly what was
`
`required of him. As Petitioner acknowledges, the “user device” limitations were
`
`added to each independent claim by amendment. See Petition, 29. They were not
`
`overlooked, a fact made clear by the sequence of events.
`
`First, the Applicant submitted the amendment with the “user device”
`
`limitations to Examiner Pendleton as a written proposal in an agenda “for the
`
`Examiner Interview scheduled for Thursday, January 28, 2021.” The amendment
`
`was the “SECOND PROPOSAL” of two alternatives presented for the examiner’s
`
`consideration.
`
`
`
`8
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`EX1004, 117-121, Interview Agenda (“FIRST PROPOSAL” and “SECOND
`
`PROPOSAL”).
`
`Next, the Applicant’s representative, David Lukach, and Examiner Pendleton
`
`“discussed . . . the first and second proposed amendments” during the Interview, and
`
`Examiner Pendleton approved the second proposal with the “user device”
`
`limitations. See EX1004, 115-116, Applicant-Initiated Interview Summary, dated
`
`February 2, 2021. As detailed in the Examiner’s Interview Summary, the purpose
`
`of the “user device” limitations was to clarify that the term “smart hub” was not
`
`intended to read on “the occupant’s user device.” Id.
`
`After the Interview, the Applicant submitted an Office Action Response
`
`proposing an amendment formally introducing the “user device” limitations.
`
`EX1004, 95-106, Office Action Response, dated February 15, 2021 (excerpt below).
`
`As part of the Response, under the heading “Claim Amendments,” the Applicant
`
`affirmatively argued that “[s]upport for the claim amendment may be found in the
`
`Specification.” Id., 98.
`
`
`
`9
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`Despite agreeing that the “user device” limitations clarified the term “smart
`
`hub,” Examiner Pendleton remained critical. Instead of allowing the claims, he
`
`continued to scrutinize them and, as a result, issued another Office Action with new
`
`rejections. EX1004, 62-80, Non-Final Office Action, dated March 18, 2021. The
`
`Office Action acknowledged that the amendment with the “user device” limitations
`
`had been considered and entered but also applied new prior art. Id. Notably absent
`
`from the Office Action, however, are any rejections for lack of written description.
`
`In the same Office Action, Examiner Pendleton also considered and found
`
`written description support for a dependent claim amendment premised on there
`
`being the communicative coupling described in the “user device” limitations. The
`
`dependent claim, claim 7, clarifies that “communicatively coupling the one or more
`
`processors to the user device enables user interaction with the smart hub.” See,
`
`EX1004, 104, Office Action Response, dated February 15, 2021. Had there been no
`
`written description support for the “user device” limitations, there would likewise
`
`had been no support for the amendment to dependent claim 7.
`
`Thus, the prosecution record shows that an experienced primary examiner,
`
`charged with ensuring claim amendments possess written description support,
`
`thoroughly examined the “user device” limitations. To wit, Examiner Pendleton
`
`considered these limitations on multiple separate occasions—before the Interview
`
`in the agenda, during the Interview, and after the Interview, when analyzing the
`
`10
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`amendments and affirmative arguments for support, prior to issuing a subsequent
`
`Office Action. In each instance, he found written description support.
`
`Given that Examiner Pendleton considered and concluded that the “user
`
`device” limitations had written description support, the Board’s precedent under 35
`
`U.S.C. § 325(d) tasks Petitioner with identifying an error in the prosecution record.
`
`See Advanced Bionics LLC v. MED-EL Elektromedizinische Gerate GmbH,
`
`IPR2019-01469, Paper 6 at 8 (PTAB Feb. 13, 2020) (precedential) (Part 2 of the
`
`two-part framework). But Petitioner has not even attempted to explain how
`
`Examiner Pendleton erred. Nor has Petitioner provided any new evidence that might
`
`reveal an error.4 Without such an explanation or evidence, Petitioner’s arguments
`
`are just an invitation to second guess the Office because it disagrees with the
`
`Examiner. See Advanced Bionics at 9 (“If reasonable minds can disagree regarding
`
`the purported treatment of the art or arguments, it cannot be said that the Office erred
`
`in a manner material to patentability.”). Such invitations are routinely denied, and
`
`this one should be, too. See Prism Pharma. Co., Ltd. v. Choongwae Pharma. Corp.,
`
`
`4 Petitioner’s expert parroting back arguments from the Petition is not entitled
`
`weight, and thus, presents no “new evidence.” 37 C.F.R. § 42.65(a) (“Expert
`
`testimony that does not disclose the underlying facts or data on which the opinion is
`
`based is entitled to little or no weight.”).
`
`11
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`IPR2014-00315, Paper 14 (PTAB Jul. 8, 2014) (informative opinion) (petition
`
`denied under § 325(d), refusing to revisit examiner’s determination of written
`
`description in a priority document); Hospira Inc. v. Genentech Inc., IPR2017-00739,
`
`Paper 16 (PTAB July 27, 2017) (denying institution where Petitioner brought no
`
`new evidence to justify reaching a different conclusion from the examiner’s on
`
`written description in a priority document).
`
`B.
`
`The ’118 Patent’s specification shows “possession” of the
`limitations Petitioner contests
`It is unsurprising that Examiner Pendleton repeatedly considered the “user
`
`device” limitations and found them sufficiently supported. These limitations reflect
`
`a core aspect of the ’118 Patent—that the smart thermostat hub bi-directionally
`
`communicates with all manner of smart devices, the claimed “user devices”
`
`included, via the non-LoRaWAN communication link. Consistent with its
`
`significance, this communication functionality is described in the very first
`
`paragraph of the Summary. The Summary explains that the “Smart thermostat hubs
`
`may comprise . . . a second communication interface that facilitates bi-directional
`
`communication between the thermostat smart hub and the smart devices present
`
`within a unit of the multi-family residential property.” EX1001, 2:27-33; see also,
`
`12
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`5:64-6:14, 6:61-7:6.5 The bi-directional communication is discussed throughout the
`
`’118 Patent, including that the second communication interface can be non-
`
`LoRaWAN. Id.
`
`When the ’118 Patent broadly describes that the smart hub’s second
`
`communication interface is configured to communicate with “smart devices,” it is
`
`disclosing an interface configured to communicatively couple with “user devices,”
`
`just as the limitations in the Challenged Claims require. This is so because the ’118
`
`Patent expressly states that “user devices” include devices that are smart, such as a
`
`“smartphone” and a “smart watch.” EX1001, 10:28-33. The Applicant cited this
`
`very passage to Examiner Pendleton as support for the amendment that included the
`
`“user device” limitations. See EX1004, 98, Office Action Response, dated February
`
`15, 2021 (citing Paragraph [0040] of the as-filed specification).
`
`It is telling that Petitioner does not dispute the fact that the ’118 Patent
`
`describes specific examples of “user devices” that are “smart devices.” Nor does
`
`Petitioner dispute that, at the time of the ’118 Patent in 2018, “user devices” like
`
`smart phones were known in the art as “smart devices.” See, e.g., US 2019/0371096
`
`
`5 The ’118 Patent is a continuation of US Application No. 16/162,262, and its
`
`specification and figures are materially identical to those of the ’262 application.
`
`See, EX1001, 1:6-9; see also, EX1004, [0005], [0028] and [0030].
`
`13
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`(EX2001), ¶[0112] (“a smart device, such as a smart phone”) (cited by the
`
`Examiner); US 2016/0241543 (EX2002), Abstract (“a personal smart device used
`
`by an individual such as a smart phone”); and US 2017/0046893 (EX2003), [0040]
`
`(“the operation apparatus 63 can be a smart phone, a smart watch, a smart bracelet,
`
`a tablet computer” and “the operation apparatus 63 (e.g. a smart device)”)
`
`(considered by the Examiner).
`
`Yet another fact left unaddressed by Petitioner is that the ’118 Patent expressly
`
`states that the smart hub and the user devices are configured to use the same
`
`communication protocols. The user devices are configured to communicate via
`
`“Bluetooth, ZigBee,” (EX1001, 10:28-33), and likewise, the smart hub’s second
`
`communication interface is “configured to communicatively couple” via “ZigBee
`
`communication links, a Bluetooth communication links [sic], and the like,” (id.,
`
`6:61-7:6). Thus, the second communication interface of the smart hub is configured
`
`to communicatively couple to the user devices at least via Bluetooth and ZigBee.
`
`These portions of the ’118 Patent (and others) show the “user device”
`
`limitations—a conclusion endorsed by Examiner Pendleton during prosecution.
`
`Petitioner’s ignoring clear disclosure from the ’118 Patent is not a showing that the
`
`Examiner erred. And, Petitioner’s failing to consider anything but verbatim
`
`disclosure of the “user device” limitations also does not satisfy Petitioner’s burden
`
`of proof. “[I]n haec verba support” has never been the standard, Purdue Pharma
`
`14
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`L.P. v. Faulding Inc., 230 F.3d 1320, 1323 (Fed. Cir. 2000), the law on written
`
`description requires only sufficient disclosure to demonstrate “possession,” Ariad
`
`Pharms, Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010).
`
`C.
`
`Petitioner’s contrary arguments do not outweigh clear written
`description support
`Petitioner appears to assume a distinction between the claimed “user devices”
`
`and the “smart devices,” i.e., that the two are mutually exclusive, because of
`
`references in the ’118 Patent to both “user devices 140” and “smart devices 120.”
`
`But, such a mutual exclusivity is not present in the ’118 Patent. The reference to
`
`“user devices 140” says nothing about the types of devices, smart or not. Instead,
`
`“user devices 140” are simply the “resident’s” devices. EX1001, 10:28-33.
`
`Additionally, the “smart devices 120” are just a subset of the smart devices
`
`contemplated in the ’118 Patent. The reference to “smart devices 120” is expressly
`
`identified as one example (“e.g.,”) of the smart devices with which the smart hub
`
`can communicate. The ’118 patent does not exclude communication between the
`
`smart hub and other devices that are also smart—e.g., a resident’s smart phone,
`
`which is also a user device.
`
`15
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`
`
`
`EX1001, 6:61-7:6 (annotated).
`
`Beyond a few instances in its Detailed Description (e.g., EX1001, 4:22, 6:36,
`
`7:2), the ’118 Patent repeatedly uses the term “smart devices” generally, without
`
`referencing the specific “smart devices 120” labeled in Figure 1. The term “smart
`
`devices” appears a total of 41 other times in a manner not limited to the particular
`
`“smart devices 120.” Id., 1:13-19, 2:24-33 and 48-56, 3:22-25 and 42-45, 4:8-12,
`
`6:40-44 and 61-7:6, 7:22-25, 8:24-31 and 53-61, 9:5-11, 13:44-50, 14:25-46, 16:6-
`
`10, 17:55-62, 18:51-62, 19:34-38, 20:4-8 and 48-53, 21:12-21 and 48-66, 21:66-
`
`22:7, 22:10-15, 27:37-45. In other words, the described coupling between the smart
`
`device hub and the “smart devices” is a coupling to any of the smart devices
`
`contemplated in the ’118 Patent, not just “smart devices 120,” as Petitioner
`
`apparently contends.
`
`16
`
`

`

`Petitioner is also wrong when it says:
`
`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`
`
`
`Petition, 33. In reality, Figure 1 hurts Petitioner’s case. It demonstrates a smart hub
`
`communicating with all manner of smart devices. Specifically, Figure 1 illustrates
`
`communication links 114 between the smart device hub 110 and three categories of
`
`devices: user devices 140, smart devices 120, and third party devices 160. EX1001,
`
`7:3-4, 6:61-7:6.
`
`
`
`Petitioner makes much of the fact that Figure 1 represents the communication links
`
`114 as a single lightning bolt symbol. But the specification plainly describes that
`
`the coupling this lightning bolt symbol represents is a plurality of “non-LoRaWAN
`
`17
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`communication links 114.” EX1001, 7:3-4 and 6:61-7:6. Figure 1 is consistent with
`
`this description, as Petitioner’s annotations highlight below. The lightning bolt
`
`symbol representing communication links 114 is not constrained to any particular
`
`category of device. Indeed, unlike other communication links (lightning bolt and
`
`arrows) in this same figure (e.g., the lightning bolt circled by Petitioner in blue), the
`
`symbol for communication links 114 (circled by Petitioner in red) does not touch
`
`any of the boxes representing the three categories of devices (i.e., user devices 140,
`
`smart devices 120 and third party devices 160).6 This different depiction indicates
`
`a difference in the nature of communication links 114.
`
`Petitioner’s annotations also show that direct communicative coupling
`
`between the smart hub and the smart devices of the user devices is not the only
`
`
`
`
`6 Communication link 112 also does not touch the adjacent smart hub 110, and is
`
`expressly said to represent information relayed from the gateways 136 “to one or
`
`more smart hubs.” EX1001, 6:14-19.
`
`18
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`support for the “user device” limitations. The “user device” limitations find further
`
`written description support in the ’118 Patent’s examples of indirect communicative
`
`coupling between the smart hub and user devices.7 Referencing Petitioner’s
`
`annotations, Figure 1 shows this indirect communicative coupling via the non-
`
`LoRaWAN communication links 114 between the smart hub 110 and smart devices
`
`120 in red and the unlabeled non-LoRaWAN communication link between the user
`
`devices 140 and smart devices 120 in blue.
`
`
`
`
`7 Dependent claim 7, which depends from claim 1, makes clear that indirect
`
`communicatively coupling was contemplated to be within the scope of claim 1 by
`
`expressly claiming an instance where the communicative coupling is direct.
`
`19
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`As an additional example of written description support, Figure 11 of the ’118
`
`Patent explains the indirect communicative coupling underscored by Petitioner’s
`
`annotations to Figure 1. EX1001, 24:5-20; see also id., 11:10-40.
`
`
`
`In Figure 11, the offline lock stores an access log that “comprise[s] access credential
`
`information associated with access credentials presented to the sensor” of the lock.
`
`Id., 24:5-11. The user devices present access credential information to the offline
`
`lock, and the offline lock then communicates an access log based on the access
`
`credentials from the user devices to the smart hub via the non-LoRaWAN
`
`communication link. Id., 24:14-20. Accordingly, the user devices communicate
`
`with, and are thus communicatively coupled to, the smart hub by interfacing with an
`
`intermediary—the offline lock.
`
`20
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`In the end, Petitioner’s strained arguments against written description support
`
`fail. Here, the simplest explanation is the right one. The ’118 Patent’s specification
`
`says that the smart hub is communicatively coupled to smart devices, and user
`
`devices like smartphones and smart watches are specific types of smart devices. No
`
`additional disclosure was required to support the “user device” limitations, which
`
`simply require a communicative coupling between user devices and a smart hub.
`
`The Examiner understood as much during prosecution, and Petitioner’s
`
`unsubstantiated request to revisit the issue should be denied.
`
`IV. THE CAHILL-DEROS GROUND FAILS (GROUND 2)
`Ground 2 is based on Cahill in combination with Deros. Petitioner relies on
`
`Cahill and/or Deros for multiple claim features but has not carried its burden on
`
`those features. Therefore, the Cahill-Deros Ground fails.
`
`A.
`
`Petitioner makes no real attempt to show that Cahill or Deros
`discloses a “property management platform”
`The Cahill-Deros Ground points to Cahill or Deros as disclosing the claimed
`
`“property management platform.” Petitioner’s nearly non-existent analysis fails to
`
`address this claim feature adequately, and amounts to an improper notice pleading.
`
`Petitioner’s failure to show that Cahill or Deros discloses the claimed “property
`
`management platform” is fatal to the Cahill-Deros Ground.
`
`
`
`21
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`Petitioner ignores a fundamental aspect of the claimed
`“property management platform”
`The Board’s rules “place an affirmative burden on petitioners to ‘set forth: . .
`
`1.
`
`. How the challenged claim is to be construed.’” OrthoPediatrics Corp. v. K2M,
`
`Inc., IPR2018-01548, Paper 9, 10 (March 1, 2019) (quoting Medicines Co. v. Mylan,
`
`Inc., 853 F.3d 1296, 1308 (Fed. Cir. 2017); 37 C.F.R. § 42.104(b)(3)). “This burden
`
`continues by requiring petitioners to adequately explain ‘[h]ow the construed claim
`
`is unpatentable.’” Id. (quoting 37 C.F.R. § 42.104(b)(4)) (emphasis in original).
`
`Despite accepting the burden when requesting post grant review, Petitioner does not
`
`attempt to satisfy it. See Intelligent Bio-Systems, Inc. v. Illumina Cambridge, Ltd.,
`
`821 F.3d 1359, 1369 (Fed. Cir. 2016) (“While the Board’s requirements are strict
`
`ones, they are requirements of which petitioners are aware when they seek to
`
`institute an IPR.”). This flaw permeates the Petition, and it is particularly striking
`
`for the “property management platform” features in each of independent claims 1,
`
`11, and 17.
`
`Petitioner asserts that it is applying the plain meaning of the claims, except
`
`where terms are expressly construed. The plain meaning of the claim term “property
`
`management platform” is revealed by its words. Simply put, there must be a
`
`platform that facilitates property management tasks or functions, a fact confirmed
`
`by the ’118 Patent’s specification. E.g., EX1001, 2:40-59, 8:26-31, 8:43-49, 9:5-11,
`
`22
`
`

`

`Case PGR2022-00059
`Attorney Docket No: 54577-0007PS1
`
`9:36-42. Petitioner ignores the ’118 Patent’s consistent and repeated reference to
`
`“property management functionalities” as separate from “security” functionalities
`
`relating to offline door lock

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