throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`ASSA ABLOY AB, ASSA ABLOY INC., ASSA ABLOY RESIDENTIAL
`GROUP, INC., AUGUST HOME, INC., HID GLOBAL CORPORATION,
`ASSA ABLOY GLOBAL SOLUTIONS, INC.,
`Petitioner,
`
`v.
`
`CPC PATENT TECHNOLOGIES PTY LTD.,
`Patent Owner.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Case IPR2022-01006
`Patent 9,665,705
`
`
`
`
`
`
`
`
`
`
`
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`

`

`B.
`
`C.
`
`D.
`
`
`TABLE OF CONTENTS ........................................................................................... i
`TABLE OF AUTHORITIES ................................................................................... iii
`I.
`INTRODUCTION ........................................................................................... 1
`II.
`FACTUAL AND PROCEDURAL BACKGROUND .................................... 3
`A.
`The Apple Action Was Served More Than 1 Year Before The
`Petition Was Filed ................................................................................. 3
`The ’705 Patent And The Yale/August Products At Issue In The
`Parallel Litigation .................................................................................. 4
`Patent Owner Contacted Petitioner Yale Regarding The ’705
`And The ’208 Patents (But Not The ’039 Patent) ................................. 9
`The Petitioners’ Declaratory Judgment Complaint And IPR
`Petitions Against All Three Of The Patents Asserted In The
`Apple Action .......................................................................................10
`The Petitioners’ Admissions Regarding Apple ...................................11
`E.
`The Apple Developer Program License Agreement ...........................12
`F.
`III. LEGAL STANDARDS .................................................................................14
`A.
`Petitioners Bear The Burden Of Persuasion ........................................14
`B.
`Real Parties-In-Interest And Privity Standards ...................................15
`1.
`Scope Of Real Parties In Interest ..............................................16
`2.
`Scope Of Privity ........................................................................17
`INSTITUTION IS BARRED UNDER SECTION 315(b) BECAUSE
`APPLE IS AN RPI AND PRIVY OF PETITIONERS .................................18
`A. Apple Is An Unnamed RPI To This Proceeding .................................18
`1.
`Apple Has A Preexisting, Established Relationship With
`Petitioners ..................................................................................18
`a.
`Petitioners Admitted To A Preexisting, Established
`Relationship With Apple In The Declaratory
`Judgment Complaint .......................................................18
`The Apple Agreement Also Establishes That
`Apple Is An RPI To This Proceeding .............................22
`
`IV.
`
`TABLE OF CONTENTS
`
`b.
`
`i
`
`

`

`Representations And Warranties Of
`Noninfringement ..................................................24
`Indemnification Clauses .......................................26
`Product Inspection And Insurance Coverage
`Clauses ..................................................................29
`iv. Apple Appointed As Petitioners’ Agent ..............31
`v.
`Summary Of Apple Agreement Significance ......31
`Apple’s Homekit Platform And Related
`Documents Are Further Evidence That Apple Is A
`RPI To This Proceeding .................................................34
`Apple Is A Clear Beneficiary Of The Petition ..........................36
`The Petitioners Filed An IPR Petition Against The ’039
`Patent For Apple’s Benefit ........................................................38
`Apple Is A Privy To This Proceeding .................................................39
`B.
`CONCLUSION ..............................................................................................41
`
`c.
`
`2.
`3.
`
`i.
`
`ii.
`iii.
`
`V.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ii
`
`

`

`TABLE OF AUTHORITIES
`
`Cases
`Apple Inc., v. Achates Reference Publ, Inc.,
`IPR2013-00080 (PTAB June 2, 2014) ................................................... 32, 33
`Applications in Internet Time, LLC v. RPX Corp.,
`897 F.3d 1336 (Fed. Cir. 2018) ............................................................. passim
`Bungie v. Worlds Inc.,
`IPR2015-01264 (PTAB Jan. 14, 2020) ................................................. passim
`Cisco Sys., Inc. v. Hewlett Packard Enter. Co.,
`IPR2017-01933 (PTAB Mar. 16, 2018) .......................................................16
`CPC Patent Technologies Pty Ltd. v. Apple, Inc.,
`No. 5:22-cv-02553-NC (N.D. Cal., San Jose Division) .................................. 4
`CPC Patent Technologies Pty Ltd. v. Apple, Inc.,
`No. 6:21-cv-00165 (W.D. Tex., Waco Division) ............................................ 1
`Power Integrations, Inc. v. Semiconductor Components Indus., LLC,
`926 F.3d 1306 (Fed. Cir. 2019) ............................................................. 15, 17
`RPX Corp. v. Applications in Internet Time, LLC,
`IPR2015-01750 (PTAB Oct. 2, 2020) ..........................................................39
`Taylor v. Sturgell,
`553 U.S. 880 (2008) ......................................................................... 18, 39, 40
`U.S. v. N.Y., New Haven & Hartford R.R. Co.,
`355 U.S. 253 (1957) ......................................................................................19
`Ventex Co., Ltd., v. Columbia Sportswear North America, Inc.,
`IPR2017-00651 (PTAB Jan. 24, 2019) ................................................. passim
`WesternGeco LLC v. ION Geophysical Corp.,
`889 F.3d 1308 (Fed. Cir. 2018) ....................................................................17
`Wi-Fi One, LLC v. Broadcom Corp.,
`887 F.3d 1329 (Fed. Cir. 2018) ............................................................. 15, 16
`Worlds, Inc. v. Bungie, Inc.,
`903 F.3d 1237 (Fed. Cir. 2018) ............................................................. passim
`Statutes
`35 U.S.C. § 314 ........................................................................................................37
`
`iii
`
`

`

`35 U.S.C. § 315(b) ........................................................................................... passim
`Other Authorities
`BLACK’S LAW DICTIONARY (10th ed. 2014) ..................................................17
`Congressional Record Volume 157, Number 132
`(Thursday, September 8, 2011) ....................................................................39
`Office Patent Trial Guide, 77 Fed. Reg. 48756, 48759 (Aug. 14, 2012) ..............16
`Rules
`37 C.F.R. § 42.51(b)(2) .............................................................................................. 2
`
`
`
`
`
`iv
`
`

`

`I.
`
`INTRODUCTION
`CPC Patent Technologies Pty. Ltd. (“CPC” or “Patent Owner”), respectfully
`
`submits this Preliminary Response to Petition IPR2022-01006 (“Petition”) for inter
`
`partes review U.S. Patent No. 9,665,705 (“the ’705 Patent”) filed by Petitioners
`
`ASSA ABLOY AB, ASSA ABLOY Inc., ASSA ABLOY Residential Group, Inc.
`
`(“Yale”), August Home, Inc. (“August”), HID Global Corporation (“HID”), ASSA
`
`ABLOY Global Solutions, Inc. (“Hospitality”) (collectively “Petitioners”). The
`
`Board should deny the Petition for at least the reason that it is time-barred under 35
`
`U.S.C. 315(b). Specifically, the Petition is time-barred because Apple, Inc.
`
`(“Apple”) is a real party-in-interest (“RPI”) and privy, and Patent Owner served a
`
`complaint on Apple alleging infringement of the ’705 Patent more than 1 year
`
`before this Petition was filed.1 Petitioners bear the burden of proving that Apple is
`
`not an RPI or privy to this proceeding.
`
`
`1 In particular, the complaint in CPC Patent Technologies Pty Ltd. v. Apple, Inc.,
`
`No. 6:21-cv-00165 (W.D. Tex., Waco Division) (“the Apple Action”) was served
`
`on Apple on March 1, 2021. See EX2001, EX2002. The complaint in the Apple
`
`Action asserts infringement of the ’705 Patent as well as CPC’s U.S. Patent Nos.
`
`9,269,208 (“the ’208 Patent”) and 8,620,039 (“the ’039 Patent”), which are also the
`
`subject of IPR petitions filed by Petitioners more than 1 year after service of the
`
`1
`
`

`

`As discussed below, at the time this Petition was filed Apple possessed a
`
`pre-existing substantive legal relationship with Petitioners concerning at least the
`
`Yale and August technology at issue. Indeed, Petitioners admit that Apple is their
`
`“business partner” with respect to the relevant products. Further, it is clear that
`
`Apple would receive more than a merely generalized benefit from institution of the
`
`Petition. To the contrary, Apple would be a direct and specific beneficiary of a
`
`potential finding of unpatentability of patent claims for which Patent Owner has
`
`accused Apple of infringing in the Apple Action.
`
`While Patent Owner respectfully submits that the evidence presented below
`
`is more than sufficient to establish that this Petition is time-barred under § 315(b),
`
`Patent Owner is in the process of seeking additional discovery on the RPI and
`
`privity issues under 37 C.F.R. § 42.51(b)(2). To that end, on August 17, 2022,
`
`Patent Owner (through counsel), contacted Petitioners’ counsel to initiate a meet-
`
`and-confer regarding additional discovery. See EX2010 at 4. Petitioners’ counsel
`
`responded and indicated that Apple and the Petitioners are parties to the Apple
`
`Developer Program License Agreement (“Apple Agreement” or “Agreement”) (id.
`
`
`Apple Action (namely IPR2022-01045; IPR2022-01089; IPR2022-01093;
`
`IPR2022-01094). CPC maintains that those petitions are time-barred under 35
`
`U.S.C. 315(b) as well and will make timely filings in those matters to that effect.
`
`2
`
`

`

`at 2), which is submitted with this Preliminary Response as EX2009 and is
`
`discussed in detail below. After reviewing the Apple Agreement, Patent Owner
`
`sent Petitioners a set of narrowly tailored proposed discovery requests. Id. at 1. In
`
`the event the parties are unable to agree on the scope of additional discovery,
`
`Patent Owner will promptly seek leave from the Board to file a motion for
`
`additional discovery.
`
`For at least the reasons discussed below, this Petition is barred by 35 U.S.C.
`
`§ 315(b). In view of that, Patent Owner will not address in this Preliminary
`
`Response the invalidity grounds advanced by Petitioners, other than to state that
`
`the invalidity grounds are deficient, as Patent Owner will demonstrate as needed if
`
`institution is granted.
`
`II.
`
`FACTUAL AND PROCEDURAL BACKGROUND
`A. The Apple Action Was Served More Than 1 Year Before The
`Petition Was Filed
`On February 23, 2021, Patent Owner filed a complaint against Apple in the
`
`Western District of Texas for infringement of three patents, the ’705 Patent (the
`
`subject of this Petition), the ’208 Patent, and the ’039 Patent. EX2003. The
`
`complaint in the Apple Action was served on March 1, 2021. EX2004. The Apple
`
`Action was subsequently transferred to the Northern District of California and is
`
`now pending as CPC Patent Technologies Pty Ltd. v. Apple, Inc., No. 5:22-cv-
`
`3
`
`

`

`02553-NC (N.D. Cal., San Jose Division). The Apple Action is identified as a
`
`related matter in the Petition’s mandatory notices. Petition at 4.
`
`B.
`
`The ’705 Patent And The Yale/August Products At Issue In The
`Parallel Litigation
`The ’705 Patent describes a secure access system that includes at least a
`
`transmitter subsystem and a controlled item such as a physical locking mechanism
`
`on a door. EX1001, Abstract. The transmitter subsystem includes a sensor to
`
`receive a biometric signal such as a fingerprint of facial data, and can match the
`
`biometric signal against a database of stored biometric signatures in order to output
`
`an accessibility attribute. The transmitter subsystem also includes the ability to
`
`enroll biometric data in the database. Some embodiments of the ’705 Patent further
`
`include a receiver subsystem that receives information corresponding to the
`
`accessibility attribute and provides access to the controlled item. Id. at Abstract,
`
`5:54–6:20, 6:67–7:3, 7:15-26, 8:24-38, FIG. 2.
`
`4
`
`

`

`
`Yale markets a line of smart lock products called Yale Assure Locks. These
`
`
`
`door locks can connect to a user’s existing deadbolt, replacing the other door
`
`hardware to allow key-free entry with a keypad. EX2011. Yale Assure Locks are
`
`also sold with a module that allows users to control, monitor, and share access
`
`from anywhere through the Yale Access mobile app installed on the user’s mobile
`
`device, specifically including an Apple iPhone. EX2012. The Yale Access mobile
`
`app further allows users to restrict access to users that have been authenticated on
`
`their mobile device, including through the use of biometric authentication.
`
`EX2013.
`
`5
`
`

`

`August also markets a line of smart locks, the most current version of which
`
`is called the August Wi-Fi Smart Lock. Like the Yale product, the August line of
`
`smart locks connect to a user’s existing deadbolt, replacing some of the user’s
`
`other door hardware. EX2014. August Wi-Fi Smart Locks provide the user with
`
`the ability to control, monitor, and share access from anywhere through the August
`
`mobile app installed on the user’s mobile device, again including an Apple iPhone.
`
`Id. The August mobile app further allows users to restrict access to users that have
`
`been authenticated on their mobile device, including through the use of biometric
`
`authentication. EX2015.
`
`
`
`
`
`6
`
`

`

`1.
`
`Yale Assure Locks:
`
`Yale’s August 25, 2020, announcement is submitted as EX2013.
`
`
`
`
`7
`
`

`

`2.
`
`August Smart Locks:
`
`
`
`August’s August 25, 2020, announcement is submitted as EX2015.
`
`In its August 25, 2020, announcement, August described the biometric
`
`feature as using “your phone’s built-in authentication tools to prompt fingerprint or
`
`facial recognition before you can unlock or lock your home,” which “further
`
`ensures that your smart lock is only operated by the right people at the time you
`
`intend for it.” Id.
`
`Each of the Yale and August products at issue, specifically the App for each,
`
`is offered on the Apple App Store. See EX2024-EX2025.
`
`8
`
`

`

`C.
`
`Patent Owner Contacted Petitioner Yale Regarding The ’705 And
`The ’208 Patents (But Not The ’039 Patent)
`On or about October 18, 2021, Patent Owner sent a letter to Yale asserting
`
`infringement of the ’705 and ’208 Patents by Yale’s “Smart Locks” products.
`
`EX2005.2 More particularly, the letter included claim charts identifying certain
`
`“Accused Instrumentalities” that include the Yale Assure Lock SL with the Yale
`
`Access software solution as well as “Biometric Verification for August and Yale
`
`Locks.” See e.g., id. at 6-7. In this letter, Patent Owner invited Yale to engage in
`
`licensing discussions. After receiving no response, Patent Owner sent a follow-up
`
`letter on November 4, 2021. EX2006. (The October 18, 2021 letter and the
`
`November 4, 2021 letter are hereinafter referred to collectively as “the Yale
`
`Letters”).
`
`Neither of the Yale Letters made any mention of the ’039 Patent. EX2005-
`
`EX2006. Neither of the Yale Letters made any mention of any of the other
`
`Petitioners, including HID and Hospitality, or any of their products. Id. Patent
`
`Owner never raised or otherwise mentioned the ’039 Patent to Yale or any of the
`
`Petitioners at any time. See EX2008.
`
`
`2 The October 18, 2020 date on the face of the letter is a typographical error. The
`
`parties agree the letter was sent on or about October 18, 2021. See, e.g., EX2007 at
`
`¶ 53.
`
`9
`
`

`

`D. The Petitioners’ Declaratory Judgment Complaint And IPR
`Petitions Against All Three Of The Patents Asserted In The Apple
`Action
`The Petitioners never responded to the Yale Letters. Instead, on May 23,
`
`2022, Petitioners filed a complaint for declaratory judgment of non-infringement of
`
`the ’705, ’208, and ’039 Patents (“the Declaratory Judgment Complaint”).
`
`EX2007.3 The Petitioners did not file the Declaratory Judgment Complaint only as
`
`to Yale and August, however, or only as to the products and patents raised in the
`
`Yale Letters. Instead, the Petitioners also filed the Declaratory Judgment
`
`Complaint as to HID and Hospitality, whom Patent Owner had never contacted
`
`regarding the patents or technology at issue. See EX2005-EX2006, EX2008.
`
`Notably, the Declaratory Judgment Complaint raises the ’039 Patent primarily in
`
`the context of HID and Hospitality’s products and services, and not in connection
`
`with Yale or August. See EX2007 at ¶¶ 100-106. Thus, the Petitioners included
`
`HID and Hospitality as plaintiffs to the Declaratory Judgment Complaint for the
`
`purpose of alleging an apprehension of suit with respect to the ’039 Patent, which
`
`
`3 There is complete overlap among the named Petitioners and the named plaintiffs
`
`in the Declaratory Judgment Complaint (referred to collectively in the Declaratory
`
`Judgment Complaint as “the ASSA ABLOY Entities”). See EX2007 at ¶ 1.
`
`10
`
`

`

`Patent Owner previously asserted against Apple in the Apple Action but never
`
`raised with respect to any of the Petitioners.
`
`After filing the Declaratory Judgment Complaint, Petitioners filed IPR
`
`petitions against all three patents asserted in the Apple Action, as follows:
`
`IPR2022-01006 (’705 Patent); IPR2022-01045 & IPR2022-01089 (’208 Patent);
`
`IPR2022-01093 & IPR2022-01094 (’039 Patent).
`
`The Petitioners’ Admissions Regarding Apple
`E.
`In the Declaratory Judgment Complaint, Petitioners admit that Apple is their
`
`“business partner” with respect to the products at issue. EX2007 at ¶ 30. In an
`
`effort to support their basis for declaratory judgment jurisdiction – i.e., the
`
`existence of a justiciable case or controversy even where Patent Owner never
`
`contacted some of the Petitioners nor ever raised the ’039 Patent at all – Petitioners
`
`Complaint also pleads that Patent Owner’s “litigation campaign that includes
`
`Apple … is likely to expand to include the ASSA ABLOY Entities.” Id. Petitioners
`
`further asserted that “it is highly likely that Charter Pacific4 will sue the Assa
`
`Abloy Entities on the same patents that have been asserted against Apple.” Id. In
`
`
`4 Charter Pacific Corporation Ltd. is Patent Owner CPC’s parent company and is a
`
`named co-defendant in the Declaratory Judgment Complaint, wherein they are
`
`collectively referred to as “Charter Pacific.” See EX2005 at ¶ 1.
`
`11
`
`

`

`addition, Petitioners asserted that “Charter Pacific has a history of alleging
`
`infringement of all three Patents-in-Suit, including against Apple, the ASSA
`
`ABLOY Entities’ business partner.” Id. at ¶¶ 43-44.5 Petitioners also pled that
`
`Patent Owner’s potential infringement allegations against Apple in Germany added
`
`to Petitioners’ purported apprehension of suit. Id. at ¶ 46.
`
`The Declaratory Judgment Complaint includes further assertions regarding
`
`Petitioners’ relationship with Apple and Apple’s connections to the Petitioners’
`
`products at issue. For example, under a heading related to August and Yale’s
`
`alleged reasonable apprehension of suit, the Declaratory Judgment Complaint
`
`references Patent Owner’s “broad interpretation of the claims in the allegations
`
`brought against Apple” and, further, that “the Apple Touch ID and Face ID
`
`features were a prominent focus of the claim charts presented to Yale.” Id. at ¶¶
`
`62-63. The Petitioners further note that “[t]he download page for Yale Access app
`
`identifies August as the developer in the Apple App Store.” Id. at ¶ 65.
`
`The Apple Developer Program License Agreement
`F.
`Consistent with having pled that Apple is their “business partner,” the
`
`Petitioners have also acknowledged that they and Apple are parties to the Apple
`
`Agreement. EX2010 at 2. According to its terms, generally the Apple Agreement
`
`
`5 Unless otherwise indicated, all emphasis is added.
`
`12
`
`

`

`grants a limited license to use the Apple Software and Services for the purpose of
`
`developing and testing Applications (i.e., “Apps”) to be used in conjunction with
`
`Apple devices (e.g., iPhone, iPad, etc.) on the terms and conditions set forth in the
`
`Agreement. EX2009 at 1. The Agreement states that “[t]hese terms and conditions
`
`constitute a legal agreement between you and Apple.” Id.
`
`As discussed in detail below, the Apple Agreement includes several patent-
`
`related obligations and multiple conditions indicating the existence of a structured
`
`and established business relationship between Apple and the Petitioners that
`
`demonstrate that Apple is a real party in interest. Such provisions include, for
`
`example:
`
`• warranties of non-infringement of any third-party patents (EX2009 at 13-14,
`
`16, 77);
`
`• indemnification and defense arrangements in the event of a patent
`
`infringement suit (id. at 10);
`
`• the obligation to get Apple’s approval to settle patent infringement suits that
`
`may affect Apple (id.);
`
`• Apple’s right to inspect the physical samples or components of Petitioners’
`
`products (id. at 36);
`
`• The Petitioners’ obligation to carry certain levels of insurance for certain
`
`types of products as Apple requests (id.);
`
`13
`
`

`

`• The Petitioners’ obligation to name Apple as an additional insured (id.);
`
`• Appointment of Apple as Petitioners’ agent with respect to the distribution
`
`of Petitioners’ software on the Apple App Store (id. at 79-80).
`
`As will be explained in detail below, the facts concerning Apple’s relationship
`
`to Petitioners clearly establish that Apple is a real party in interest and/or privy for
`
`purposes of the present IPR.
`
`III. LEGAL STANDARDS
`35 U.S.C. § 315(b) provides, in pertinent part, that “[a]n inter partes review
`
`may not be instituted if the petition requesting the proceeding is filed more than 1
`
`year after the date on which the petitioner, real party in interest, or privy of the
`
`petitioner is served with a complaint alleging infringement of the patent.” See also
`
`Worlds, Inc. v. Bungie, Inc., 903 F.3d 1237, 1240 (Fed. Cir. 2018) (“Correctly
`
`identifying all real parties in interest with respect to each IPR petition is important,
`
`as the determination may impact whether a petition may be instituted.” Id. citing
`
`35 U.S.C. § 315(b) (concerning a patent owner’s civil action against a real-party-
`
`in-interest)).
`
`Petitioners Bear The Burden Of Persuasion
`A.
`Once Patent Owner introduces some evidence indicating an RPI relationship
`
`between Apple and one or more of the Petitioners, then Petitioners “bear[] the
`
`ultimate burden of persuasion to show that its petitions are not time-barred under §
`
`14
`
`

`

`315(b) based on a complaint served on an alleged real party in interest more than a
`
`year earlier.” Worlds Inc., 903 F.3d at 1242. This same burden applies to proofs on
`
`privity. See Ventex Co., Ltd., v. Columbia Sportswear North America, Inc.,
`
`IPR2017-00651, Paper 148 at 4 (PTAB Jan. 24, 2019) (“Ventex”).
`
`B. Real Parties-In-Interest And Privity Standards
`The law regarding real parties-in-interest and privity has changed
`
`significantly in recent years, beginning with the Federal Circuit’s 2018 decision
`
`in Applications in Internet Time, LLC v. RPX Corp., 897 F.3d 1336, 1351 (Fed.
`
`Cir. 2018) (“AIT”). In AIT, the Federal Circuit found that the Board erred by
`
`taking an “unduly narrow view” of the meaning of real party-in-interest and by
`
`failing to consider the entirety of the record. Id. at 1345. As the court explained,
`
`the inquiry into whether a party is a RPI or privy “demands a flexible approach
`
`that takes into account both equitable and practical considerations, with an eye
`
`toward determining whether the non-party is a clear beneficiary that has a
`
`preexisting, established relationship with the petitioner.” AIT, 897 F.3d at 1351.
`
`“The statutory terms ‘real party in interest’ and ‘privy’ are not defined in Title 35.
`
`However, they are well-established common law terms.” Power Integrations, Inc.
`
`v. Semiconductor Components Indus., LLC, 926 F.3d 1306, 1315 (Fed. Cir. 2019)
`
`(citing Wi-Fi One, LLC v. Broadcom Corp., 887 F.3d 1329, 1335 (Fed. Cir.
`
`2018). Moreover:
`
`15
`
`

`

`[The] Practice Guide explains that “real party in interest,” as used in
`the AIA trial context, differs from the traditional understanding of the
`term: [T]he spirit of that formulation as to [inter partes review] . . .
`proceedings means that, at a general level, the “real party-in-interest”
`is the party that desires review of the patent.
`Cisco Sys., Inc. v. Hewlett Packard Enter. Co., IPR2017-01933, Paper 9 at 12
`
`(PTAB Mar. 16, 2018) (“Cisco”) (quoting Office Patent Trial Guide, 77 Fed.
`
`Reg. 48756, 48759 (Aug. 14, 2012) (“Guide”)).
`
`Scope Of Real Parties In Interest
`1.
`“Congress intended for [the term “real party-in-interest”] to have an
`
`expansive formulation.” AIT, 897 F.3d at 1350. “[T]he focus of the real-party-in-
`
`interest inquiry is on the patentability of the claims challenged in the IPR
`
`petition, bearing in mind who will benefit from having those claims canceled or
`
`invalidated.” AIT, 897 F.3d at 1348. Also relevant is “whether some party other
`
`than the petitioner is the ‘party or parties at whose behest the petition has been
`
`filed.’” Wi-Fi One, 887 F.3d at 1336 (quoting Guide at 48759).
`
`The Trial Practice Guide indicates that “a non-party may be a real party-in-
`
`interest even in the absence of control or an opportunity to control.” Cisco at 13
`
`(citing Guide at 48760). Analysis of who benefits from an IPR petition is a
`
`central focus of the RPI analysis. See Ventex at 7-8 (finding a real party-in-
`
`interest relationship where the parties had “mutual interest in the continuing
`
`commercial and financial success of each other” and where the “clear
`16
`
`

`

`beneficiary” of the IPRs was a party who was otherwise “barred under § 315(b)
`
`from seeking [relief] for itself”).
`
`Scope Of Privity
`2.
`“‘[T]he legislative history [of the Leahy-Smith America Invents Act
`
`(‘AIA’)] . . . lends support to the conclusion that privity in § 315(b) should be
`
`given its common law meaning.’” Power Integrations, 926 F.3d at 1315 (quoting
`
`WesternGeco LLC v. ION Geophysical Corp., 889 F.3d 1308, 1318 (Fed. Cir.
`
`2018)). “Privity is a well-recognized common law concept that is primarily based
`
`on the legal relationship between two parties. The general definition of privity is
`
`‘[t]he connection or relationship between two parties, each having a legally
`
`recognized interest in the same subject matter (such as transaction, proceeding, or
`
`piece of property).’” AIT, 897 F.3d at 1359 (quoting Privity, BLACK’S LAW
`
`DICTIONARY (10th ed. 2014)).
`
`The Supreme Court has provided a non-exhaustive list for examining
`whether the legal relationship between two parties establishes that one
`is the privy of the other. The list consists of six categories that create
`independent exceptions to the common law rule that normally forbids
`non-party preclusion in litigation: (1) an agreement between the
`parties to be bound; (2) pre-existing substantive legal relationships
`between the parties; (3) adequate representation by the named party;
`(4) the non-party’s control of the prior litigation; (5) where the non-
`party acts as a proxy for the named party to relitigate the same issues;
`
`17
`
`

`

`and (6) where special statutory schemes foreclose successive litigation
`by the non-party (e.g., bankruptcy and probate).
`AIT, 897 F.3d at 1360 (citing Taylor v. Sturgell, 553 U.S. 880, 894-95 (2008)).
`
`Importantly, in the precedential Ventex decision, the Board held that
`
`“[a]nalysis under any one of the factors can support a finding of privity.” Ventex
`
`at 12 (citing AIT, 897 F.3d at 1360).
`
`IV.
`
`INSTITUTION IS BARRED UNDER SECTION 315(b) BECAUSE
`APPLE IS AN RPI AND PRIVY OF PETITIONERS
`As set forth in detail below, pursuant to the precedents of the Federal Circuit
`
`and the Board, Apple is an RPI and privy to this proceeding, which is therefore
`
`time-barred.
`
`A. Apple Is An Unnamed RPI To This Proceeding
`Apple Has A Preexisting, Established Relationship With
`1.
`Petitioners
`Petitioners Admitted To A Preexisting, Established
`a.
`Relationship With Apple In The Declaratory
`Judgment Complaint
`There can be no dispute that Apple has a preexisting, established
`
`relationship with the Petitioners. Petitioners admitted in the Declaratory
`
`Judgment Complaint that Apple is their “business partner” with respect to the
`
`technology at issue. EX2007 at ¶¶ 30, 43. Further, as discussed below, Plaintiffs
`
`affirmatively relied on its relationship with Apple and the Apple related features
`
`used in connection with at least the accused Yale and August products as grounds
`
`18
`
`

`

`for asserting that they had a reasonable apprehension that the ’705 Patent would be
`
`asserted against them. These admissions are, by themselves, sufficient to satisfy
`
`the low threshold of putting the RPI issue “into dispute.” See Worlds, 903 F.3d at
`
`1243.
`
`As the Federal Circuit explained, a petitioner’s statement that it is the sole
`
`RPI is not entitled to any legal presumption of truth. Id. Instead, the Petitioners
`
`must show that they “complied with the statutory requirement to identify all the
`
`real parties in interest.” Id. at 1242. Although the Federal Circuit has stated that it
`
`is “practical” for a petitioner’s initial identification to be “accepted unless and
`
`until disputed by a patent owner,” it is nonetheless improper to treat this
`
`pragmatic approach as a presumption, or to shift the burden to the Patent Owner.
`
`Id. at 1243.
`
`It is important that the evidentiary burden remains at all times with the
`
`petitioner. As the court recognized, “an IPR petitioner will usually be in a better
`
`position, at least relative to the patent owner, to access evidence relevant to the
`
`real-party-in-interest inquiry.” Id. at 1242-43; see also U.S. v. N.Y., New Haven &
`
`Hartford R.R. Co., 355 U.S. 253, 256 n.5 (1957) (“The ordinary rule, based on
`
`considerations of fairness, does not place the burden upon a litigant of
`
`establishing facts peculiarly within the knowledge of his adversary.”).
`
`19
`
`

`

`It is true that a patent owner must do more than make a mere assertion,
`
`devoid of any evidentiary support, to bring the real party in interest issue into
`
`debate. Worlds, at 1244. But the quantum of evidence needed to properly raise
`
`the issue is low. As Worlds explained, to “sufficiently raise the issue,” the Patent
`
`Owner need only “produce some evidence that tends to show that a particular
`
`third party should be named a real party in interest.” Id. at 1244 (emphasis in
`
`original). It is then for the Petitioner to meet its burden of persuasion to prove its
`
`RPI statement with admissible evidence. Id. at 1241-44.
`
`Here, in addition to Petitioners’ admission that they and Apple are business
`
`partners with respect to the technology at issue, Petitioners also asserted that
`
`Patent Owner’s “litigation campaign that includes Apple … is likely to expand to
`
`include the ASSA ABLOY Entities.” EX2007 at ¶ 30. Petitioners further asserted
`
`that “it is highly likely that Charter Pacific will sue the Assa Abloy Entities on the
`
`same patents that have been asserted against Apple.” Id. In addition, Petitioners
`
`asserted that “Charter Pacific has a history of alleging infringement of all three
`
`Patents-in-Suit, including against Apple, the ASSA ABLOY Entities’ business
`
`partner.” Id. at ¶¶ 43-44. Petitioners also asserted that Patent Owner’s potential
`
`infringement allegations against Apple in Germany added to Petitioners’ purported
`
`apprehension of suit. Id. at ¶ 46.
`
`20
`
`

`

`The Petitioners further relied on the close relationship between the Yale and
`
`August products and the Apple technology at issue in the Apple Action. For
`
`example, under a heading related to August and Yale’s reasonable apprehension of
`
`suit, the Petitioners referenced Patent Owner’s “broad interpretation of the claims
`
`in the allegations brought against Apple” and, further, that the Apple Touch ID and
`
`Face ID features were a prominent focus of the claim charts presented to Yale.” Id.
`
`at ¶¶ 62-63. The Petitioners further noted that “[t]he download page for Yale
`
`Access app identifies “August as the developer in the Apple App Store.” Id. at ¶
`
`65.
`
`In sum, therefore, Petitioners pled and relied upon their close relationship
`
`with Apple concerning the patents and technology in question so as to support their
`
`allegations of reasonable apprehension of suit to justify purported declaratory
`
`judgment jurisdiction. This reliance by Petitioners on their relationship wi

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