throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`APPLE INC.,
`
`Petitioner
`
`
`
`v.
`
`
`
`BILLJCO LLC,
`
`Patent Owner
`
`
`
`
`
`CASE: IPR2022-00310
`
`U.S. PATENT NO. 9,088,868
`
`PATENT OWNER’S PRELIMINARY RESPONSE
`
`PURSUANT TO 35 U.S.C. § 313 AND 37 C.F.R. § 42.107(a)
`
`
`
`
`
`39838176.5
`
`

`

`
`
`TABLE OF CONTENTS
`
`V. 
`
`Page
`INTRODUCTION ...................................................................................... - 1 - 
`I. 
`ALLEGED GROUNDS OF UNPATENTABILITY ................................. - 3 - 
`II. 
`III.  THE ‘868 PATENT .................................................................................... - 3 - 
`IV.  HABERMAN DOES NOT TEACH OR SUGGEST “THE FIRST
`IDENTIFIER INDICATIVE OF THE MOBILE DATA
`PROCESSING SYSTEM OF THE MOBILE APPLICATION USER
`INTERFACE” ............................................................................................. - 7 - 
`THE COMBINATION OF HABERMAN AND BOGER DOES NOT
`TEACH OR SUGGEST “THE FIRST IDENTIFIER INDICATIVE
`OF THE MOBILE DATA PROCESSING SYSTEM OF THE
`MOBILE APPLICATION USER INTERFACE” ..................................... - 8 - 
`VI.  PETITIONER DOES NOT ADDRESS ALL CLAIM FEATURES IN
`GROUNDS 3 OR 4 .................................................................................... - 9 - 
`VII.  THE BOARD SHOULD EXERCISE DISCRETION TO NOT
`INSTITUTE BASED ON THE FACIAL DEFICIENCIES OF
`GROUNDS 3 & 4 ..................................................................................... - 10 - 
`VIII.  THE PETITION SHOULD BE DENIED UNDER § 314(A) .................. - 11 - 
`A. 
`Fintiv Factor 1–Likelihood of Stay ................................................ - 11 - 
`B. 
`Fintiv Factor 2–Trial Date Versus FWD Due Date ....................... - 12 - 
`C. 
`Fintiv Factor 3–Investment in the Proceeding ............................... - 13 - 
`D. 
`Fintiv Factor 4–Overlap of Issues .................................................. - 14 - 
`E. 
`Fintiv Factor 5–Identity of Parties ................................................. - 15 - 
`D. 
`Fintiv Factor 6–Other Circumstances ............................................ - 15 - 
`IX.  CONCLUSION ......................................................................................... - 17 - 
`
`39838176.5
`
`i
`
`

`

`
`
`
`INTRODUCTION
`Petitioner Apple, Inc. (“Petitioner”) has not met its burden in demonstrating
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`I.
`
`that U.S. Patent No. 9,088,868 (“the ‘868 patent”) is more likely than not invalid,
`
`and, as such, institution should be denied.
`
`Petitioner’s contention that the challenged claims of the ‘868 patent are
`
`invalid as obvious lacks merit. Petitioner relies on one primary prior art reference—
`
`U.S. Patent Application Publication US 2005/0096044 A1 to Haberman (Ex. 1004).
`
`The Petition is facially defective in that it fails to demonstrate “a reasonable
`
`likelihood that the Petitioner would prevail with respect to at least one of the claims
`
`challenged in the petition” under 35 U.S.C. § 314(a).
`
`Petitioner’s obviousness arguments fail because none of the cited references
`
`teach or suggest the recited “the first identifier indicative of the mobile data
`
`processing system of the mobile application user interface”. Petitioner twice
`
`attempts to equate an address with this feature. However, the addresses in Haberman
`
`and Boger that Petitioner attempts to utilize are no more “indicative of” the “system”
`
`at that address in each reference than a given street address is “indicative of” whether
`
`or what structure is located on that piece of land.
`
`Neither the Petition, nor the declaration submitted by Petitioner’s expert,
`
`provide an articulated reasoning with a rational underpinning to support a legal
`
`conclusion of obviousness. KSR Int’l Co. v. Teleflex, Inc., 550 U.S. 398, 418 (2007),
`
`
`
`
`39838176.5
`
`- 1 -
`
`

`

`
`
`
`quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006). The Petition only provides
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`“mere conclusory statement[s]” (id.) that the claims are obvious, and lacks cogent
`
`reasoning as to why a person of ordinary skill in the art would modify or combine
`
`the cited references in the specific manner that is recited in each of the challenged
`
`claims.
`
`Petitioner’s expert declaration (Ex. 1002) merely repeats the attorney
`
`arguments in the Petition (often verbatim).
`
`In summary, the IPR Petition fails to show a reasonable likelihood that at least
`
`one of the challenged claims of the ‘868 patent is unpatentable. The Board should
`
`not institute inter partes review of the ‘868 patent and should deny the Petition in its
`
`entirety.
`
`
`
`
`39838176.5
`
`- 2 -
`
`

`

`
`
`
`II. ALLEGED GROUNDS OF UNPATENTABILITY
`Petitioner alleges the following grounds of unpatentability under 35 U.S.C.
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`§ 103 against independent claims 1 and 24 and dependent claims 2, 5, 20, 25, 28,
`
`and 43. Pet. 4. All are deficient in meeting the challenged claims.1
`
` Grounds Reference(s)
`
`Challenged Claims
`
`1. § 103
`
`Haberman
`
`1, 2, 5, 20, 24, 25, 28, and 43
`
`2. § 103
`
`Haberman in view of Boger
`
`1, 2, 5, 20, 24, 25, 28, and 43
`
`3. § 103
`
`Haberman in view of Evans
`
`1, 2, 5, 20, 24, 25, 28, and 43
`
`4. § 103
`
`Haberman in view of Boger and
`
`1, 2, 5, 20, 24, 25, 28, and 43
`
`Evans
`
`III. THE ‘868 PATENT
`The ‘868 Patent enables the configuration and performance of location based
`
`conditions. The claimed methods and systems recite accepting user input, from a
`
`user of a mobile application user interface of a user carried mobile data processing
`
`system, for configuring a user specified location based event configuration to be
`
`monitored and triggered by the mobile data processing system. The mobile data
`
`
`1 Patent Owner appreciates Petitioner’s recognition that the claims “should be
`
`interpreted according to their plain and ordinary meaning.” Pet. 6.
`
`
`
`
`39838176.5
`
`- 3 -
`
`

`

`
`
`
`processing system uses the user specified location based event configuration to
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`perform mobile data processing system operations comprising:
`
` Accessing at least one memory storing a first identifier and a second
`
`identifier and a third identifier:
`o Each identifier is determined by the mobile data processing system for
`
`at least one location based condition monitored by the mobile data
`
`processing system for the mobile data processing system triggering a
`
`location based action.
`o The location based action performed by the mobile data processing
`
`system upon the mobile data processing system determines the at least
`
`one location based condition including whether identifier data
`
`determined by the mobile data processing system for a wireless data
`
`record received for processing by the mobile data processing system
`
`matches the third identifier and at least one of the first identifier and
`
`the second identifier.
`o The wireless data record corresponds to a beaconed broadcast wireless
`
`data transmission that is beaconed outbound from an originating data
`
`processing system to a destination data processing system.
`o The first identifier is indicative of the mobile data processing system
`
`of the mobile application user interface for use by the mobile data
`
`
`
`
`39838176.5
`
`- 4 -
`
`

`

`
`
`
`
`
`
`
`IPR2022-00310
`Patent No. 9,088,868
`
`processing system in comparing the first identifier to the identifier
`
`data determined by the mobile data processing system for the wireless
`
`data record received for processing by the mobile data processing
`
`system.
`o The second identifier is indicative of originating data processing
`
`system identity data of the wireless data record received for
`
`processing for use by the mobile data processing system in comparing
`
`the second identifier to the identifier data determined by the mobile
`
`data processing system for the wireless data record received for
`
`processing by the mobile data processing system.
`o The third identifier is indicative of the originating data processing
`
`system of the wireless data record received for processing. The third
`
`identifier is monitored by the mobile data processing system for use
`
`by the mobile data processing system in comparing the third identifier
`
`to the wireless data record received for processing by the mobile data
`
`processing system.
`
` Receiving for processing the wireless data record corresponding to the
`
`beaconed broadcast wireless data transmission that is beaconed outbound
`
`from the originating data processing system to the destination data
`
`processing system
`
`
`
`
`39838176.5
`
`- 5 -
`
`

`

`
`
`
` Determining the identifier data for the wireless data record received for
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`processing by the mobile data processing system
`
` Comparing the identifier data for the wireless data record received for
`
`processing by the mobile data processing system with the third identifier and
`
`the at least one of the first identifier and the second identifier
`
` Determining the at least one location based condition of the user specified
`
`location based event configuration including whether the identifier data for
`
`the wireless data record received for processing by the mobile data
`
`processing system matches the third identifier and the at least one of the first
`
`identifier and the second identifier
`
` Performing, upon the determining the at least one location based condition,
`
`the location based action in accordance with the determining the at least one
`
`location based condition of the user specified location based event
`
`configuration including whether the identifier data for the wireless data
`
`record received for processing by the mobile data processing system
`
`matches the third identifier and the at least one of the first identifier and the
`
`second identifier.
`
`
`
`
`39838176.5
`
`- 6 -
`
`

`

`
`
`
`
`
`
`IV. HABERMAN DOES NOT TEACH OR SUGGEST “THE FIRST
`IDENTIFIER INDICATIVE OF THE MOBILE DATA PROCESSING
`SYSTEM OF THE MOBILE APPLICATION USER INTERFACE”
`Both of independent claims 1 and 24 recite “the first identifier indicative of
`
`IPR2022-00310
`Patent No. 9,088,868
`
`the mobile data processing system of the mobile application user interface”, which
`
`Petitioner refers to as [1.a.1.e] and [24.c.1.e].
`
`The “Internet address” taught by ¶ [0132] of Haberman is not “indicative of
`
`the mobile data processing system of the mobile application user interface” for at
`
`least two reasons.
`
`First, the “Internet address” of Haberman tells nothing about, i.e., is not
`
`“indicative of”, whether and what system is located at that “Internet address”. The
`
`system located at the “Internet address” could be an HTTP server, an FTP server,
`
`an e-mail server, a refrigerator, or anything else in this Internet of Things world.
`
`Second, Haberman teaches that “additional informational content may be
`
`downloaded from the Internet address”. Thus, the “Internet address” of Haberman
`
`cannot be “indicative of the mobile data processing system of the mobile
`
`application user interface” because the “Internet address” is merely a source for
`
`downloading additional information from a different system than the user’s
`
`mobile device in Haberman. Such an address cannot be known a priori because
`
`the mobile device in Haberman can encounter any number of wireless transmitters
`
`broadcasting any number of Internet addresses. Moreover, if user of the mobile
`
`
`
`
`39838176.5
`
`- 7 -
`
`

`

`
`
`
`device in Haberman already knew the Internet address, there would be little utility
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`in the wireless transmitters in Haberman emitting it. Thus, even if the “Internet
`
`address” was indicative of any “mobile data processing system”, which it is not, it
`
`certainly would not be suitable “for use by the mobile data processing system in
`
`comparing the first identifier to the identifier data determined by the mobile data
`
`processing system for the wireless data record received for processing by the
`
`mobile data processing system” as further recited in independent claims 1 and 24.
`
`V. THE COMBINATION OF HABERMAN AND BOGER DOES NOT
`TEACH OR SUGGEST “THE FIRST IDENTIFIER INDICATIVE OF
`THE MOBILE DATA PROCESSING SYSTEM OF THE MOBILE
`APPLICATION USER INTERFACE”
`Recognizing that Haberman’s teaching of “the first identifier indicative of
`
`the mobile data processing system of the mobile application user interface” is
`
`lacking, Petitioner proffers a combination with Boger.
`
`The Petition alleges that the AM_ADDR (active member address) of Boger
`
`teaches this feature. In particular, the Petition relies on Boger’s teaching that,
`
`“[d]uring formation of the piconet the master assigns each slave an AM_ADDR
`
`(active member address), an integer from 1 through 7, which uniquely identifies
`
`the slave within the piconet.” Petition at 35, citing EX1005, [0006]; EX1002,
`
`¶ 116.
`
`
`
`
`39838176.5
`
`- 8 -
`
`

`

`
`
`
`Like Haberman, the AM_ADDR of Boger is not “indicative of the mobile
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`data processing system of the mobile application user interface”. Again, the
`
`AM_ADDR tells nothing about the slave to which the AM_ADDR integer is
`
`assigned.
`
`VI. PETITIONER DOES NOT ADDRESS ALL CLAIM FEATURES IN
`GROUNDS 3 OR 4
`Grounds 3 and 4 of the Petition are based on the premise that if the Patent
`
`Owner were to argue that “wireless data record” should be construed to require: (1)
`
`a date/time stamp field, (2) a location field; and (3) a confidence field, then Evans
`
`discloses the claimed “wireless data record.” Petition at 52-53. Patent Owner does
`
`not contend as such; rather, this was Petitioner’s unsuccessful construction in the
`
`parallel District Court litigation. EX2003 at 3.
`
`Regardless, neither the Petition nor the associated expert declaration address
`
`features [1.a.1.e] and [24.c.1.e] in Ground 3 or 4, even by reference to Grounds 1
`
`or 2. This is not surprising because Evans is silent regarding such an identifier.
`
`Therefore, for the reasons discussed with respect to Grounds 1 and 2, the Petition
`
`should be denied.
`
`
`
`
`39838176.5
`
`- 9 -
`
`

`

`
`
`
`
`
`
`VII. THE BOARD SHOULD EXERCISE DISCRETION TO NOT
`INSTITUTE BASED ON THE FACIAL DEFICIENCIES OF
`GROUNDS 3 & 4
`As discussed herein, Petitioner has not demonstrated a reasonable likelihood
`
`IPR2022-00310
`Patent No. 9,088,868
`
`that at least one of the challenged claims of the ‘868 patent is unpatentable based
`
`on either of Grounds 1 (Haberman) or 2 (Haberman and Boger).
`
`However, even if the Board believed that Petitioner made such a showing
`
`with regard to any Grounds, it should still exercise its discretion to not institute on
`
`all grounds (as required under SAS Institute, Inc. v. Iancu) in view of the resulting
`
`need to conduct a trial in which 50% or 75% of the grounds would be challenges
`
`found to have no reasonable likelihood as outlined below.
`
`If the Board finds a reasonable likelihood for:
`
`
`
`Only Ground 2 Grounds 1 and 2
`
`% of trial based on grounds without
`
`75%
`
`50%
`
`reasonable likelihood
`
`Similarly, a finding by the Board that Haberman does not teach or suggest
`
`features [1.a.1.e] and [24.c.1.e] would result in at least 50% of the grounds lacking
`
`
`
`
`39838176.5
`
`- 10 -
`
`

`

`
`
`
`a reasonable likelihood because the Petition cannot (and did not event attempt) to
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`show a teaching or suggestion of this feature in Evans.
`
`VIII. THE PETITION SHOULD BE DENIED UNDER § 314(A)
`Patent Owner contends that, in view of the pending litigation in the Western
`
`District of Texas (“WDTX”) -- BillJCo v. Apple Inc., Case No. 6:21-cv-00528-ADA
`
`(“Litigation”), the Fintiv factors enumerated below weigh in favor of discretionary
`
`denial. Apple Inc. v. Fintiv, IPR2020-00019, Paper 11, 5-6 (PTAB Mar. 20, 2020)
`
`(precedential).
`
`Preliminarily, Petitioner stated that it was challenging venue in the Litigation
`
`and had moved to transfer the Litigation to the Northern District of California. Pet.
`
`at 62. Petitioner’s motion to transfer, however, was denied on February 17, 2022
`
`(corrected March 1, 2022). EX2001 (Public Version).
`
`A. Fintiv Factor 1–Likelihood of Stay
`Petitioner advised that it will move to stay the Litigation if the IPR is
`
`instituted. Pet. at 64. Petitioner contended that institution of an IPR would provide
`
`an opportunity to simplify the Litigation, which would increase the likelihood that a
`
`stay would be granted. Id. Petitioner also contended that a finding of invalidity in
`
`the IPR would “relieve the Western District of Texas of the need to continue with
`
`the companion litigation for the ‘868 patent.” Id. Neither contention is correct.
`
`
`
`
`39838176.5
`
`- 11 -
`
`

`

`
`
`
`First, unless all claims asserted in the Litigation are found invalid in the IPR,
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`the district court will not be relieved of the need to continue with the Litigation.
`
`Second, a stay is not likely to be granted on a contested motion in the WDTX. As
`
`the “LegalMetric District Report Texas Western District Court in Patent Cases,
`
`January, 2017–September, 2021” (EX2002) reveals, stays pending an IPR were
`
`granted in the WDTX only 36.4% of the time during the five-year reporting period.
`
`Id., p.3. The percentage is even lower for the judge assigned to the Litigation, Judge
`
`Albright. His stay grant rate is only 28.6%. Id., pp. 70-71. It is more than 70% likely
`
`that a stay will not be granted if an IPR is instituted.
`
`Fintiv Factor 1 weighs strongly in favor of discretionary denial.
`
`B. Fintiv Factor 2–Trial Date Versus FWD Due Date
`Trial is scheduled for February 13, 2023, “or as soon as practicable.” EX1007.
`
`Petitioner emphasizes the phrase in quotes to support its contention that the trial date
`
`is not reliable. Pet. at 63. To further support its contention, Petitioner discusses the
`
`reliability of trial dates in general rather than addressing the facts specific to the
`
`Litigation.
`
`The facts specific to the Litigation suggest that this trial date is extremely
`
`reliable. A review of the Agreed Scheduling Order confirms that the court and parties
`
`have kept to the scheduling order fairly closely. EX1007. Indeed, although the
`
`Markman hearing was held on February 22, 2022 instead of February 10, 2022 (this
`
`
`
`
`39838176.5
`
`- 12 -
`
`

`

`
`
`
`was done at the request of Petitioner to accommodate its counsel’s schedule), the
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`Claim Construction Order was issued March 23, 2022 (EX2003). Judge Albright’s
`
`average time to a claim construction decision is 12.1 months from the date of filing
`
`of a case, which is May 25, 2021 for the Litigation. EX2002; EX2004. Judge
`
`Albright, thus, is about three months ahead of schedule with his claim construction
`
`decision.
`
`Fintiv Factor 2 weighs strongly in favor of discretionary denial.
`
`C. Fintiv Factor 3–Investment in the Proceeding
`Petitioner was served in the Litigation on May 28, 2021. EX2005. Petitioner
`
`filed its Petition on December 22, 2021, almost seven months thereafter. Petitioner
`
`stated that “almost no other court would be as far along in its trial calendar” within
`
`six months. Pet. at 65. Petitioner’s statement is an express acknowledgement both
`
`of the alacrity of proceedings in the WDTX and of the investment by the court and
`
`parties in the Litigation.
`
`Indeed, the parties have already disclosed extrinsic evidence and identified
`
`expert witnesses for claim construction and indefiniteness (November 16, 2021);
`
`served initial disclosures (February 15, 2022); submitted claim construction briefs
`
`(completed January 27, 2022); and begun fact discovery (opened February 15,
`
`2022). EX1007. As noted above, a Claim Construction Order was already issued.
`
`EX2003. And, two claim terms of the ‘868 patent were construed. EX2003. It is
`
`
`
`
`39838176.5
`
`- 13 -
`
`

`

`
`
`
`not likely that an institution decision will issue before the end of July 2022, which
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`means an FWD will not issue before July 2023. The parties’ and the court’s
`
`investment will most likely be substantial before an FWD issues.
`
`Fintiv Factor 3 weighs strongly in favor of discretionary denial.
`
`D. Fintiv Factor 4–Overlap of Issues
`Petitioner stipulated that it would not assert invalidity of the challenged claims
`
`in the Litigation using grounds asserted in the Petition. Pet. 67-68. The Petitioner’s
`
`stipulation is quite limited in scope. The Board views stipulations like Petitioner’s
`
`as only mitigating concerns of duplicate efforts and of potentially conflicting
`
`decisions “to some degree.” See Apple Inc. v. Seven Networks, LLC, IPR2020-
`
`00180, Paper 12, at 15 (PTAB Aug. 14, 2020). Such a stipulation, then, may slightly
`
`favor institution.
`
`Under the present facts, however, discretionary denial should be favored
`
`instead. Petitioner asserted only four bases for challenging validity in its Petition,
`
`and
`
`relied upon only
`
`three
`
`references; Haberman, Haberman+Boger,
`
`Haberman+Evans, and Haberman+Boger+Evans. Pet. 4. In the Litigation, Petitioner
`
`cited eight references, and enumerated eight single reference, and numerous two-,
`
`three-, four-, and five-reference combinations, for a total of 244 bases for
`
`challenging validity, including the two of the four bases relied upon in the Petition.
`
`Defendant Apple Inc.’s Preliminary Invalidity Contentions, EX2006, pp 40-54. If
`
`
`
`
`39838176.5
`
`- 14 -
`
`

`

`
`
`
`both actions proceed simultaneously, not only is efficiency decreased, but also the
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`possibility of conflicting decisions is increased, assuming that all bases of invalidity
`
`asserted by Petitioner in the litigation are of equal merit. It is possible that the claims
`
`challenged in the Petition could be determined to be valid over the art relied upon in
`
`the Petition, but invalid over art relied upon in the Litigation.
`
`Fintiv Factor 4 weighs in favor of discretionary denial.
`
`E. Fintiv Factor 5–Identity of Parties
`The Litigation involves the same parties. Petitioner argued that this factor is,
`
`at worst, neutral. Pet. at 68. In Apple v. Seven Networks, however, the Board found
`
`that, when the parties are the same, Fintiv factor 5 weighed slightly in favor of the
`
`Patent Owner. Apple v. Seven Networks, at 16.
`
`Fintiv Factor 5 weighs in favor of discretionary denial.
`
`D. Fintiv Factor 6–Other Circumstances
`Unlike the situation in Apple v. Seven Networks, the number of prior art
`
`challenges has not been limited in the Litigation. Indeed, more art and bases for
`
`challenging the claims of the ‘868 Patent were raised in the Litigation. Also unlike
`
`the situation in Apple v. Seven Networks, then, an IPR will not provide the parties
`
`with an in-depth analysis of the ‘868 Patent, nor a full record that will enhance the
`
`integrity of the patent system.
`
`
`
`
`39838176.5
`
`- 15 -
`
`

`

`
`
`
`Petitioner made a weak showing on the merits. Patent Owner has pointed out
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`weaknesses in the Petition, on three separate bases, regarding each of the challenged
`
`independent claims. Therefore, the merits, taken as a whole, do not favor Petitioner
`
`and instead also weigh in favor of discretionary denial.
`
`Fintiv factor 6 weighs in favor of discretionary denial.
`
`
`
`
`39838176.5
`
`- 16 -
`
`

`

`
`
`
`IX. CONCLUSION
`For the above reasons, the Petition is deficient and institution of the IPR
`
`IPR2022-00310
`Patent No. 9,088,868
`
`
`
`
`should be denied.
`
`Dated April 11, 2022
`
`Mailing address for all correspondence:
`Saul Ewing Arnstein & Lehr LLP
`Centre Square West
`1500 Market Street, 38th Floor
`Philadelphia, PA 19102-2186
`
`
`/s/ Brian R. Michalek
`
`Brian R. Michalek (Reg. No. 65,816)
`Saul Ewing Arnstein & Lehr LLP
`161 North Clark Street, Suite 4200
`Chicago, IL 60601
`Tel: (312) 876-7836
`brian.michalek@saul.com
`
`Joseph M. Kuo (Reg. No. 38,943)
`Saul Ewing Arnstein & Lehr LLP
`161 North Clark Street, Suite 4200
`Chicago, IL 60601
`Tel: (312) 876-7151
`joseph.kuo@saul.com
`
`Brian R. Landry (Reg. No. 62,074)
`Saul Ewing Arnstein & Lehr LLP
`131 Dartmouth Street, Suite 501
`Boston, MA 02116
`Tel: (617) 912-0969
`Brian.Landry@saul.com
`
`Counsel for Patent Owner, BillJCo,
`LLC
`
`
`
`
`39838176.5
`
`- 17 -
`
`

`

`
`
`
`
`
`
`
`Exhibit List
`
`IPR2022-00310
`Patent No. 9,088,868
`
`Exhibit Document
`2001
`Amended Memorandum and Opinion & Order Denying Defendant
`Apple Inc.’s Motion to Transfer Venue [Public Version]
`LegalMetrics District Report for Texas Western District Court from
`January 2017 to September 2021
`Claim Construction Order
`Complaint
`Summons Returned by Apple
`Apple, Inc.’s Preliminary Invalidity Contentions
`
`
`
`
`2002
`
`2003
`2004
`2005
`2006
`
`
`
`
`39838176.5
`
`- 18 -
`
`

`

`
`
`
`
`
`
`
`IPR2022-00310
`Patent No. 9,088,868
`
`Certification of Word Count Under 37 C.F.R. § 42.6(e)(4)
`
`The undersigned hereby certifies that the foregoing complies with the type-
`
`volume limitation in 37 C.F.R. § 42.24(b)(1). According to the word-processing
`
`system’s word count, the document contains 3,208 words, excluding the parts of
`
`the brief exempted by 37 C.F.R § 42.24(b).
`
`Date: April 11, 2022
`
`
`
`
`
`
`
`
`/Brian R. Landry/
`Reg. No. 62,074
`
`
`
`
`
`
`
`
`39838176.5
`
`- 19 -
`
`

`

`
`
`
`
`
`
`
`IPR2022-00310
`Patent No. 9,088,868
`
`Certification of Service Under 37 C.F.R. § 42.6(e)(4)
`
`The undersigned hereby certifies that the foregoing was served in its entirety
`
`by filing through the Patent Trial and Appeal Board End to End (PTAB E2E), as
`
`well as providing a courtesy copy via e-mail to the following attorneys of record
`
`for Petitioner listed below:
`
`Larissa S. Bifano
`
`Jonathan Hicks
`
`Joseph Wolfe
`
`
`
`larissa.bifano@dlapiper.com
`
`jonathan.hicks@dlapiper.com
`
`joseph.wolfe@us.dlapiper.com
`
`Date: April 11, 2022
`
`
`
`
`
`
`
`
`/Brian R. Landry/
`Reg. No. 62,074
`
`
`
`
`39838176.5
`
`- 20 -
`
`

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