throbber
Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 1 of 69
`
`
`
`
`PROXENSE, LLC,
`
`Plaintiff,
`
` v.
`
`APPLE, INC.
`
`Defendant.
`
`
`UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`
`
`Civil Action No. 6:24-cv-00143
`
`
`JURY TRIAL REQUESTED
`
`
`
`COMPLAINT FOR PATENT INFRINGEMENT
`
`Plaintiff Proxense, LLC (“Proxense” or “Plaintiff”) hereby sets forth its Complaint for
`
`patent infringement against Defendant Apple, Inc. (“Apple” or “Defendant”), for patent
`
`infringement under 35 U.S.C. § 271 and alleges as follows:
`
`NATURE OF THE CASE
`
`1.
`
`This action is for patent infringement arising under the patent laws of the United
`
`States, 35 U.S.C. §§ 1, et seq. As further stated herein, Proxense alleges that Apple willfully
`
`infringes one or more claims of patents owned by Proxense. Accordingly, Proxense seeks
`
`monetary damages and injunctive relief in this action.
`
`THE PARTIES
`
`2.
`
`Plaintiff Proxense, LLC is a Delaware company with its principal place of business
`
`at 689 NW Stonepine Drive, Bend, Oregon 97703. Defendant Apple, Inc. is a corporation
`
`organized and existing under the laws of California, with one or more regular and established
`
`places of business in this District at least at 12545 Riata Vista Circle, Austin, Texas 78727; 12801
`
`
`
`
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 2 of 69
`
`Delcour Drive, Austin, Texas 78727; 6800 W Parmer Lane, Austin, Texas 78729, and 3121 Palm
`
`Way, Austin, Texas 78758. Apple may be served with process through its registered agent, the CT
`
`Corp System, at 1999 Bryan St., Ste. 900 Dallas, Texas 75201-3136. In November 2019, Apple
`
`stated that it had approximately 7,000 employees in Austin and that it expected to open, in 2022,
`
`a $1 billion, 3 million-square foot campus with capacity for 15,000 employees. See Exhibit 7.
`
`Apple is registered to do business in the State of Texas and has been since at least May 16, 1980.
`
`JURISDICTION AND VENUE
`
`3.
`
`This Court has exclusive subject matter jurisdiction over this case pursuant to 28
`
`U.S.C. §§ 1331, 1332, 1338, and 1367 on the grounds that this action arises under the Patent Laws
`
`of the United States, 35 U.S.C. § 1 et seq., including, without limitation, 35 U.S.C. §§ 271, 281,
`
`284, and 285.
`
`4.
`
`5.
`
`The amount in controversy exceeds $75,000.
`
`This Court has specific personal jurisdiction over Apple because Apple is a
`
`multinational technology company that has a significant presence in the District through the
`
`products and services Apple provides residents of this District. Defendant regularly conducts
`
`business and have committed acts of patent infringement within this Judicial District that give rise
`
`to this action and have established minimum contacts within this forum such that the exercise of
`
`jurisdiction over Apple would not offend traditional notions of fair play and substantial justice.
`
`Apple has committed and continues to commit acts of infringement in this Judicial District, by,
`
`among other things, offering to sell, selling, using, importing, and/or making products and services
`
`that infringe the asserted patents. Apple has further induced acts of patent infringement by others
`
`in this Judicial District and/or has contributed to patent infringement by others in this Judicial
`
`District, the State of Texas, and elsewhere in the United States.
`
`
`
`2
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 3 of 69
`
`6.
`
`Apple operates retail stores located in this Judicial District that offer and sell
`
`products on its behalf in this District, including products accused of infringement herein. For
`
`example, Apple operates the Apple Domain NORTHSIDE store located at 3121 Palm Way,
`
`Austin, Texas 78758 and the Apple Barton Creek store located at 2901 S Capital of Texas Hwy,
`
`Austin, Texas 78746. A screenshot of a search for Waco, Texas in the “Find a Store” section of
`
`Apple’s website, taken on February 10, 2024, reveals a picture of its Apple Domain NORTHSIDE
`
`location:
`
`7.
`
`Apple’s website further indicates that its Apple Domain NORTHSIDE location
`
`offers shopping, order pickup, and support/instruction (through the Genius Bar and scheduled
`
`
`
`workshops).
`
`8.
`
`Apple also partners with third parties in this District acting as Apple Authorized
`
`Retailers that can sell Apple products via their physical store(s). These include retailers Target
`
`
`
`3
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 4 of 69
`
`(e.g., the retail location at 5401 Bosque Blvd., Waco, TX), Walmart (e.g., the retail locations at
`
`4320 Franklin Ave and 600 Hewitt Dr located in Waco, TX), Best Buy (e.g. the retail location at
`
`4627 S Jack Kultgen Expy, Waco, TX), Office Depot (e.g., the retail locations at 5524 Bosque
`
`Blvd and 4627 Jack Kultgen Fwy in Waco, TX), T-Mobile (e.g., the retail locations at 2448 W
`
`Loop 340 Suite 24a and 100 N New Rd Ste 110 in Waco, TX), and Verizon (e.g., the retail
`
`locations at 2812 W Loop 340 Ste H12 and 5301 Bosque Blvd Ste 120 in Waco, TX). On
`
`information and belief, Apple Authorized Resellers are important to Apple's retail strategy and
`
`represent a large portion of sales of Apple products worldwide.
`
`9.
`
`Proxense’s causes of action arise directly from Apple’s business contacts and other
`
`activities in the State of Texas and this District.
`
`10.
`
`Apple has derived substantial revenues from its infringing acts within the State of
`
`Texas and this District.
`
`11.
`
`Venue is proper in this Judicial District pursuant to 28 U.S.C. §§ 1400(b) and
`
`1391(b) and (c) because Defendant is subject to personal jurisdiction in this Judicial District, has
`
`committed acts of patent infringement in this Judicial District, and has a regular and established
`
`place of business in this Judicial District. Defendant, through its own acts, makes, uses, sells,
`
`and/or offers to sell infringing products within this Judicial District, regularly does and solicits
`
`business in this Judicial District, and has the requisite minimum contacts with the Judicial District
`
`such that this venue is a fair and reasonable one.
`
`12.
`
`Apple also maintains a significant physical presence in this Judicial District and
`
`employs many people in this Judicial District. On November 20, 2019, Apple announced that it
`
`was breaking ground on its $1 billion, 3-million-square-foot campus “as part of its broad expansion
`
`in the city.” See Apple Newsroom, Press Release: Apple expands in Austin, Exhibit 7. Apple
`
`
`
`4
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 5 of 69
`
`also described in that 2019 press release that it was “steadily growing in Austin with approximately
`
`7,000 employees in the city.” Id. Not only did Apple build a new campus in Austin, “Apple and
`
`its manufacturing partners invested over $200 million in the Mac Pro facility in Austin, building
`
`out the complex assembly line where the Mac Pro is produced.” Id.
`
`13.
`
`The Mac Pro is an accused product in this case capable of using Apple Pay. Apple’s
`
`press release also revealed a photo of its Mac Pro facility in Austin, which it describes as
`
`employing more than 500 people:
`
`
`
`14.
`
`In 2023, Apple “filed projects totaling $240 million for an expansion of its north
`
`Austin campus…” Exhibit 8 “Capstone Phase Two AC09 and Capstone Phase Two AC07, as the
`
`projects are called, are a four-story and a five-story building, respectively, set for construction at
`
`6900 Parmer Lane. Between the two buildings, Apple is adding 419,441 square-feet of office
`
`space. Construction begins for both buildings on September 30 of [2023] and have an estimated
`
`completion date of March 30, 2025.” Id.
`
`
`
`5
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 6 of 69
`
`15.
`
`The “Careers at Apple” section of Apple’s website highlights Austin as having a
`
`“range of teams and specialties.” Exhibit 9. Among the categories of roles shown are Hardware,
`
`Operations and Supply Chain, Corporate Functions, Support and Service, Software and Services,
`
`and Sales and Business Development. So important to Apple is the Austin campus that Apple
`
`recently threatened that one of its teams, located in California, to relocate to Austin or be
`
`terminated. Exhibit 10.
`
`16.
`
`Among the teams located in Austin is the Apple Pay team. Apple Pay is pervasive
`
`and ubiquitous, included in nearly all of Apple’s offerings, from the Mac Pro to the iPhone to the
`
`recently introduced Vision Pro. Several key members of the Apple Pay team are located in Texas,
`
`including:
`
`- Alexander Antunovic is the Servicing and Readiness Lead for Apple Pay Business
`
`Operations, located in Austin, Texas. Mr. Antunovic describes on his LinkedIn profile that
`
`he has “[o]ver 15 years of contactless EMV payment experience that has involved physical
`
`card issuance, digital (device & e-commerce) tokenization, merchant acceptance,
`
`implementation, remediation, business development, commercialization, product roadmap
`
`enhancement and drafting of business rules.” Mr. Antunovic has worked at Apple on its
`
`Apple Pay team since January 2019. Prior to his role at Apple, Mr. Antunovic worked for
`
`Mastercard in New York. He studied Computer Science at Concordia University. Exhibit
`
`11.
`
`- Alex Coulter is the Global Operations Project Manager for the Apple Pay group, located
`
`in Austin, Texas.
`
`
`
`6
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 7 of 69
`
`- Geoff Johnson is a “proven business leader” working for Apple Pay Business Development
`
`group, located in Austin, Texas. According to his LinkedIn profile, he “helps bring the
`
`future of commerce to life with Apple Pay.” Exhibit 12.
`
`-
`
`Jennifer Cervantes is in Partner Operations for the Apple Pay group, located in Austin,
`
`Texas. She has worked for the Apple Pay group since May 2020. Prior to her role at
`
`Apple, Ms. Cervantes lived in California where she worked at TrustCommerce as a Vice
`
`President of Account Management. Exhibit 13.
`
`17.
`
`Apple has also partnered with third parties, such as Austin Telco Federal Credit
`
`Union, to utilize credit and debit cards issued by those third parties, with Apple Pay as “an easy,
`
`secure, and private way to make purchases.” Exhibit 14. Apple Pay can also be used with
`
`shopping apps such as those for Target.
`
`18.
`
`On information and belief, Apple has committed acts of willful direct and indirect
`
`infringement in the Western District of Texas. For example, Apple sells computers (e.g., Mac
`
`Pros, iMacs), laptops (e.g., MacBooks and MacBook Pros), iPads, iPhones, Apple Watches, and
`
`the new Vision Pro to individuals in this Judicial District, which ship with various versions of
`
`MacOS, iOS, iPadOS, watchOS, and visionOS. Apple also distributes Apple Pay, in this Judicial
`
`District, available across its device offerings.
`
`
`
`PATENTS-IN-SUIT
`
`19.
`
`On March 26, 2016, the United States Patent and Trademark Office duly and
`
`legally issued U.S. Patent No. 9,298,905 (the “905 Patent”) entitled “Biometric Personal Data
`
`Key (PDK) Authentication.” A true and correct copy of the 905 Patent is attached hereto as
`
`Exhibit 1.
`
`
`
`7
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 8 of 69
`
`20.
`
`On January 8, 2013, the United States Patent and Trademark Office duly and
`
`legally issued U.S. Patent No. 8,352,730 (the “730 Patent”) entitled “Biometric Personal Data
`
`Key (PDK) Authentication.” A true and correct copy of the 730 Patent is attached hereto as
`
`Exhibit 2.
`
`21.
`
`On November 11, 2014, the United States Patent and Trademark Office duly and
`
`legally issued U.S. Patent No. 8,886,954 (the “954 Patent”) entitled “Biometric Personal Data Key
`
`(PDK) Authentication.” A true and correct copy of the 954 Patent is attached hereto as Exhibit 3.
`
`22.
`
`On June 30, 2020, the United States Patent and Trademark Office duly and legally
`
`issued U.S. Patent No. 10,698,989 (the “989 Patent”) entitled “Biometric personal data key (PDK)
`
`Authentication.” A true and correct copy of the 989 Patent is attached hereto as Exhibit 4.
`
`23.
`
`On June 2, 2015, the United States Patent and Trademark Office duly and legally
`
`issued U.S. Patent No. 9,049,188 (the “188 Patent”) entitled “Hybrid Device Having a Personal
`
`Digital Key and Receiver-Decoder circuit and Methods of Use.” A true and correct copy of the
`
`188 Patent is attached hereto as Exhibit 5.
`
`24.
`
`On February 4, 2014, the United States Patent and Trademark Office duly and
`
`legally issued U.S. Patent No. 8,646,042 (the “042 Patent”) entitled "Hybrid Device Having a
`
`Personal Digital Key and Receiver-Decoder Circuit and Methods of Use." A true and correct copy
`
`of the 042 Patent is attached hereto as Exhibit 6.
`
`25.
`
`Proxense is the sole and exclusive owner of all right, title, and interest to and in, or
`
`is the exclusive licensee with the right to sue for, the 905, 730, 954, 989, 188, and 042 Patents
`
`(together, the “Patents-in-Suit”), and holds the exclusive right to take all actions necessary to
`
`enforce its rights to the Patents-in-Suit, including the filing of this patent infringement lawsuit.
`
`
`
`8
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 9 of 69
`
`Proxense also has the right to recover all damages for past, present, and future infringement of the
`
`Patents-in-Suit and to seek injunctive relief as appropriate under the law.
`
`26.
`
`The technologies of the Patents-in-Suit were invented by John Giobbi and David
`
`L. Brown. The 730, 954, and 905 Patents generally cover systems and methods for an integrated
`
`device that persistently stores biometric data for a user in a tamper-resistant format. Subsequently,
`
`scan data collected from a user (e.g., a fingerprint) can be compared against the stored biometric
`
`data. Once the user has been biometrically verified by the integrated device, a code can be
`
`wirelessly transmitted for authentication. The 989 Patent generally cover systems and methods of
`
`verifying a user during authentication of an integrated device.
`
`27.
`
`The 188 and 042 Patents generally cover a hybrid device including a personal
`
`digital key (“PDK”) and receiver-decoder circuit (“RDC”), wherein the PDK and RDC are coupled
`
`for communication with each other. The 188 and 042 Patents also includes a number of system
`
`configurations for use of the hybrid device including: use of the hybrid device in a cell phone;
`
`simultaneous use of the PDK and the RDC functionality of hybrid device; and use of multiple links
`
`of hybrid device to generate an enablement signal, use of multiple PDK links to the hybrid device
`
`to generate an enablement signal.
`
`FACTUAL ALLEGATIONS
`
`I.
`
`TECHNOLOGY BACKGROUND
`
`28.
`
`Authentication is the process by which the identity of a user is confirmed on a
`
`device, including computers, tablets, and phones. When a person is authenticated, the goal is to
`
`verify that the credentials presented are authentic. For years, users were authenticated with
`
`usernames and passwords. However, with the amount of sensitive personal and financial
`
`information currently stored on personal devices, and the rise of biometric readers and high-speed
`
`
`
`9
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 10 of 69
`
`networks, there was a need to implement improved authentication architectures. For over a decade,
`
`Apple has integrated biometric reader hardware into its devices, beginning with fingerprint
`
`scanners (i.e., Touch ID) and now spanning to facial (i.e., Face ID) and retina scanners (Optic ID),
`
`the latter being introduced in the 2024-released Vision Pro augmented reality headset.
`
`29.
`
`In 2012, Apple acquired AuthenTec, a company focused on fingerprint-reading and
`
`identification management software, for $356 million. By September 10, 2013, Apple would
`
`integrate fingerprint reader technology in the iPhone 5S. The feature was marketed as “Touch
`
`ID.” With the unveiling of the iPhone 6 and 6 Plus at a keynote event on September 9, 2014,
`
`Touch ID was expanded from being used to unlock the device and authenticating App Store
`
`purchases to also authenticating Apple Pay. The first generation of Touch ID was used in iPhone
`
`and iPad products from 2013-2021, including the iPhone 5S, SE (1st generation), 6, and 6 Plus and
`
`the iPad Pro 12.9 inch (2015) and 9.7 inch (2016), Air 2, Mini 3, Mini 4, and 5th to 9th generations
`
`(2015-2021). The second generation of Touch ID was used in iPhone, iPad, MacBook, iMac, and
`
`the Magic Keyboard from 2015 to products that Apple continues to sell today, including the iPhone
`
`6S, 6S Plus, 7, 7 Plus, 8, 8 Plus, SE (2nd and 3rd generations); iPad (10th generation), iPad Pro (2nd
`
`generation), Air (3rd to 5th generations), Mini (5th and 6th generations), MacBook Pro (from 2018-
`
`2023), MacBook Air
`
`30.
`
`The successor to Touch ID was announced by Apple during the unveiling of the
`
`iPhone X on September 12, 2017. It was marketed as Face ID. Like Touch ID, Face ID allows
`
`biometric authentication for unlocking a device and making payments through Apple Pay. Face
`
`ID has been available on newer iPhone models beginning with the iPhone X and all iPad Pro
`
`models, including 2018 iPad Pros and later.
`
`
`
`10
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 11 of 69
`
`31.
`
`In 2024, Apple introduced Retina ID with the Apple Vision Pro. Apple describes
`
`that: “In the same way that Touch ID revolutionized authentication using a fingerprint and Face
`
`ID revolutionized authentication using facial recognition, Optic ID revolutionizes authentication
`
`using iris recognition.” Exhibit 15 (last visited February 11, 2024). “With a look, Optic ID
`
`securely unlocks your Apple Vision Pro. You can use it to authorize purchases from the App Store
`
`and Book Store, payments using Apple Pay, and more.” Id. “Developers can also allow you to use
`
`Optic ID to sign into their apps.” Id. “Apps that support Touch ID or Face ID automatically support
`
`Optic ID.” Id.
`
`32.
`
`Apple leverages the biometric readers integrated on its devices (and Touch ID /
`
`Face ID / Optic ID) for authenticating financial transactions, through Apple Pay. as well as for
`
`passwordless logins. For example, Apple uses “federated authentication” (also known as
`
`“federated identity”), which relies on an external trusted system to provide the service and function
`
`of authenticating users. See e.g. Exhibit 16. In a federated authentication solution, the system
`
`being accessed must request authentication of the user from the external system that is providing
`
`the user authentication functions and services. The external system providing the authentication
`
`service will then communicate successful authentication back to the system being accessed.
`
`Successful authentication is communicated between the two systems with the issuance security
`
`tokens containing claims about user authentication. Upon successful authentication of a user, the
`
`external system issues a security token which can be exchanged for access to the other system.
`
`One such federated architecture is OpenID Connect, which Apple has adopted.
`
`33. While OpenID and OAuth 2 based identity services limit the use of passwords, they
`
`do not eliminate them. Authentication services geared towards eliminating passwords include
`
`those utilizing the WebAuthn protocol and its derivative, FIDO2, an open authentication standard
`
`
`
`11
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 12 of 69
`
`developed by the FIDO Alliance, of which Apple is a member. Identity services utilizing the
`
`WebAuthn protocol, and the derivative protocol FIDO2, utilize an asymmetric key pair to
`
`authenticate a device. Possession and control of the device verifies the identity of the user. The
`
`device, referred to as an authenticator, generates a private/public key pair and a credential ID
`
`uniquely identifying the key pair. The public key and credential ID are sent to the authentication
`
`service – called in the protocol the “relying party”. The private key is held by the authenticator.
`
`During authentication, the authenticator sends a signature generated with its private key and the
`
`credential ID identifying the private key used to generate the signature. The relying party (i.e.,
`
`authentication service) uses the credential ID to retrieve the matching public key. The signature
`
`is then verified with the public key. Upon successful verification of the signature, the relying party
`
`authentication service issues an authentication response. Apple has also adopted FIDO2. Exhibit
`
`17.
`
`34. WebAuthn and federated protocols can be combined by an identity service
`
`provider. When combined, the system to be accessed by the user requests authentication by a
`
`WebAuthn / FIDO2 server of the identity service provider. The server issues an authentication
`
`request to the user’s authenticator. The authenticator responds by providing a signature and
`
`credential ID to the WebAuthn/FIDO2 server. If the signature is verified, the WebAuthn/FIDO2
`
`server informs the OpenID / OAuth 2 server of successful authentication. The OpenID / OAuth 2
`
`server of the identity service provider then sends a security token to be used to access the system
`
`requesting authentication.
`
`35.
`
`Attempting to eliminate the use of passwords, Apple has developed a universal
`
`platform “passwordless” architecture (e.g. Apple ID and “Sign in with Apple”). See Exhibit 18.
`
`The architecture is universal in that it works across ecosystems, such as iOS (and the related
`
`
`
`12
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 13 of 69
`
`iPadOS, watchOS, and visionOS) and MacOS, as well as on PCs and even Android. It is password-
`
`less in that passwords have been replaced with the use of passkeys. Exhibit 19. At Apple’s
`
`Worldwide Developer Conference in 2022, Apple announced: “In macOS Monterey and iOS 15,
`
`we announced a developer preview of the solution -- passkeys -- and got so much great feedback.
`
`In macOS Ventura and iOS 16, we're excited to make passkeys available to everyone. Now is the
`
`time to adopt them.” Exhibit 20.
`
`36.
`
`Apple’s architecture relies on the issuance of security tokens, adopting standards
`
`OAuth 2.0 and OpenID Connect. The hub of Apple’s universal platform password-less
`
`architecture is Apple ID, which receives authentication requests from external systems,
`
`coordinates the action of trusted devices, and issues security tokens.
`
`37.
`
`Apple encourages its users to register an Apple ID to use various functionalities
`
`across its operating systems, including iOS to MacOS.
`
`38.
`
`Apple leverages its vast userbase for “Sign in with Apple,” which allows users to
`
`utilize their Apple ID to sign into a website. It starts with a button in the app or website labeled
`
`“Sign In with Apple”. Exhibit 21.
`
`
`
`39.
`
`Apple uses OAuth 2.0 and OpenID Connect terminology in its documentation and
`
`API calls. Applications providing “Sign in with Apple” must be registered in the Apple Developer
`
`Portal. Apple uses a public/private key client authentication methodology.
`
`40.
`
`Apple users are typically locked into the Apple ecosystem. For example, Apple
`
`users with iPhones typically buy compatible Apple Watches, which are tightly integrated in the
`
`Apple ecosystem (other devices, like the newer models of Samsung’s Galaxy Watch, do not even
`
`
`
`13
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 14 of 69
`
`work with Apple devices). Apple utilizes “trusted devices” that a user owns to enhance two-factor
`
`authentication. “A trusted device is an iPhone, iPad, iPod touch, Apple Watch, or Mac that you've
`
`already signed in to using two-factor authentication. It's a device that we know is yours and that
`
`can be used to verify your identity by displaying a verification code from Apple when you sign in
`
`on a different device or browser. Exhibit 22. “When you sign in with your Apple ID user name
`
`and password for the first time on a new device or the web, you'll receive a notification on your
`
`trusted devices that someone is trying to sign in with your Apple ID.” Id.
`
`41.
`
`In Apple’s ecosystem, a user’s “Apple ID is the account that you use to access all
`
`Apple services and make all of your devices work together seamlessly.” Exhibit 23. “After you
`
`sign in, you can use the App Store, iCloud, iMessage, Apple Music, Apple TV+, and more.”
`
`42.
`
`Apple uses Apple ID (in conjunction with biometrics sensors available on various
`
`devices) across its devices, including iPhone, iPad, and Apple Vision Pro. Apple instructs its users
`
`to (1) Open the Settings app; (2) Tap Sign in to your [device]; and (3) Choose a way to sign in (see
`
`Exhibit 23):
`
`
`
`14
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 15 of 69
`
`
`
`43.
`
`For the “Use Another Apple Device Option,” Apple instructs that “If you have
`
`another iPad or iPhone that’s signed in with your Apple ID, bring that device nearby and follow
`
`the instructions on both devices to complete sign-in.” Exhibit 23. Further, “[i]f you're already
`
`signed in on the iPhone paired with your Apple Watch, you will automatically be signed in to that
`
`Apple ID on your watch.” Id. Apple ID is also used for Mac computers, Apple TV, and signing
`
`into the web as well as other apps (and other devices), as described above. Id. Apple’s users are
`
`directed to sign in using their Apple ID during the setup process (i.e., after purchase, upon first
`
`turning on) of its devices.
`
`44.
`
`Federated authentication is not the only authentication architecture Apple has
`
`incorporated into its operating systems; Apple Pay, which incorporates EMV’s payment
`
`tokenization architecture utilizes token issued by a third-party and stored on the phone. The tokens
`
`are a surrogate for a credit card, debit card, or other Primary Account Number (PAN), and can be
`
`
`
`15
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 16 of 69
`
`used anywhere the underlying account is accepted as payment. As with OpenID / OAuth 2 tokens,
`
`EMV payment tokens indicate a previous authentication of the user. The tokens differ with respect
`
`to authorization claims. OpenID / OAuth 2 authenticates the user and obtains the user’s consent
`
`before issuing a token. As such, the token represents authentication of the user and what the user
`
`has been authorized. As authorization is obtained before token issuance, a token can never be used
`
`for more than authorization claim it contains. EMV tokens, on the other hand, contain no claims
`
`with respect to authorization. Authorization, rather, is indicated by release of an EMV token from
`
`a device. Unlike OpenID / OAuth 2 tokens, payment tokens are locked in a device and can only
`
`be released following verification of the user by the device. As only the legitimate use can be
`
`verified, release of an EMV token is indicative of user consent. Presentation of an EMV payment
`
`token, accordingly, is indicative of user consent to the accompany charge to their account.
`
`Regardless of the differences in their manner of representing authorization and the timing of
`
`obtaining authorization, both OpenID / OAuth 2 tokens and EMV tokens are indicative of user
`
`authentication and authorization.
`
`45.
`
`To facilitate the use of EMV’s payment tokenization architecture, Apple has
`
`deployed technology to secure payment tokens in connection with its operating systems and Apple
`
`Pay. Using biometric security features integrated into its devices (i.e., the ability to unlock Apple
`
`devices through a fingerprint, facial recognition, or an iris scan), Apple offered biometric
`
`authentication for Apple Pay beginning in 2014. See Exhibit 24.
`
`46.
`
`As the popularity of mobile payment solutions increased, Apple Pay surfaced as a
`
`key player in the market. On information and belief, Apple Pay has over 45 million users in the
`
`United States. On further information and belief, Apple Pay’s convenience and security features,
`
`
`
`16
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 17 of 69
`
`attributable to its use of (biometric) authentication, are the major driving forces of its adoption
`
`among users.
`
`47.
`
`As for Sign in with Apple, Built With indicates that 15,258 sites utilize Apple’s
`
`sign-in solution. This authentication mechanism competes with the likes of “Sign in with Google,”
`
`“Sing in with Facebook,” and Microsoft Authentication.
`
`II.
`
`PROXENSE AND ITS INNOVATIVE TECHNOLOGIES
`
`48.
`
`Proxense was founded in 2001.1 From approximately 2004-2012, Proxense
`
`developed, inter alia, mobile payment technologies and commercial products, employing over
`
`thirty engineers, and investing many millions of dollars in product development and other research
`
`and development efforts. Foundational capabilities of Proxense’s technologies included a secure
`
`element, biometrics captured and stored thereon, retrieval of biometrics and token passing to a
`
`trusted third party, and completion of a mobile payment transaction.
`
`49.
`
`Proxense also developed sophisticated, proprietary, proximity-based detection,
`
`authentication, and automation technology, built on the concept of wirelessly detecting,
`
`authenticating, and communicating with personal digital keys (“PDKs”). Proxense’s technology
`
`enabled PDKs to run for as long as two years on tiny batteries. “ProxPay” technology also included
`
`biometrically-based user and device authentication options, the ability to conduct biometric-
`
`verified transactions without sending or exposing the underlying biometric data or storing it
`
`anywhere except the PDK, and the incorporation of a registration for maintaining or verifying the
`
`PDK. Significant financial and engineering resources were deployed to make this possible. The
`
`
`1 The company was formally incorporated as an LLC in 2001 under the name Margent
`Development LLC; in 2005, the business was renamed to Proxense LLC.
`17
`
`
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 18 of 69
`
`resulting developments became primary differentiators of Proxense’s product line, and significant
`
`elements on which its business was built.
`
`50.
`
`John Giobbi is the founder and CEO of Proxense. He is an experienced product
`
`designer and prolific inventor (a named inventor on approximately 200 patents, including the
`
`asserted patents), with over 35 years of experience as an entrepreneur and product development
`
`executive. For example, Mr. Giobbi was a Senior Vice President at WMS Gaming, and managed
`
`over 200 staff; in his six-year tenure at that company, its market capitalization soared from
`
`approximately $80 million to about $1 billion. Mr. Giobbi was also the founder and President of
`
`Prelude Technology Corp. and InPen.
`
`51.
`
`The innovative, visionary nature of Proxense’s technology was recognized in the
`
`media, beginning in mid-2008, when, The Bulletin featured a story on Proxense’s mobile payment
`
`technology, titled “A pint-sized virtual wallet.” Andrew Moore, The Bulletin (May 7, 2008),
`
`Exhibit 25. The story describes a future that greatly resembles the present-day, including a
`
`“wireless wallet” and “fingerprint” verification, including the use of such technology to pay for
`
`goods using such wireless methods protected by biometric measures like a fingerprint. In 2009,
`
`Trend Hunter ran a similar story titled “Virtual Biometric Wallets,” featuring Proxense and Mr.
`
`Giobbi. Michael Plishka, Trend Hunter (January 4, 2009), See Exhibit 26.
`
`52.
`
`Another 2009 article, ran in DARKReading, a publication in InformationWeek’s
`
`IT Network, also featured the company and Mr. Giobbi in an article titled “Startup May Just
`
`Digitize Your Wallet.” George V. Hulme, DARKReading (February 8, 2009), See Exhibit 27.
`
`The DARKReading article described that Proxense was “in the process of bringing to market a
`
`proximity-based communications device that aims to provide a way to securely share information
`
`and conduct payments.” Proxense’s Personal Digital Keys (PDKs) were described as “carried by
`
`
`
`18
`
`

`

`Case 6:24-cv-00143-ADA Document 1 Filed 03/18/24 Page 19 of 69
`
`users, perhaps even within a cell phone, and can security hold data and manage authentication.”
`
`Mr. Giobbi explained that “the data within the PDK also can be protected by additional layers of
`
`authentication, such as biometric…”
`
`53.
`
`It would be years until products like Google Wallet (2011), Apple Pay (2014)

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