`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`AIRE TECHNOLOGY LTD.,
`
`Plaintiff,
`
`Case No. ______________
`
`v.
`
`JURY TRIAL DEMANDED
`
`SAMSUNG ELECTRONICS CO., LTD. and
`SAMSUNG ELECTRONICS AMERICA, INC.,
`
`Defendants.
`
`COMPLAINT FOR PATENT INFRINGEMENT
`AGAINST SAMSUNG ELECTRONICS CO., LTD AND
`SAMSUNG ELECTRONICS AMERICA, INC.
`
`This is an action for patent infringement arising under the Patent Laws of the United States
`
`of America, 35 U.S.C. § 1 et seq., in which Plaintiff Aire Technology Limited (“Plaintiff” or
`
`“Aire”) makes the following allegations against Defendants Samsung Electronics Co., Ltd. and
`
`Samsung Electronics America, Inc. (collectively, “Defendants” or “Samsung”):
`
`INTRODUCTION
`
`1.
`
`This complaint arises from Samsung’s unlawful infringement of the following
`
`United States patents owned by Plaintiff, which relate to improvements in Near Field
`
`Communication (NFC) and secure digital payment solutions: United States Patent Nos. 8,581,706
`
`(“the ’706 Patent”), 8,816,827 (“the ’827 Patent”), 8,205,249 (“the ’249 Patent”), and 8,174,360
`
`(“the ’360 Patent”) (collectively, the “Asserted Patents”).
`
`PARTIES
`
`2.
`
`Plaintiff Aire Technology Limited is a limited liability company organized and
`
`existing under the law of Ireland, with its principal place of business at The Hyde Building, Suite
`
`6:21-cv-00955
`
`Ex.1015
` Page 1 of 45
`
`GARMIN /
`
`
`
`23, The Park, Carrickmines, Dublin 18, Ireland. Aire is the sole owner by assignment of all rights,
`
`title, and interest in the Asserted Patents, including the right to recover damages for past, present,
`
`and future infringement.
`
`3.
`
`On information and belief, Defendant Samsung Electronics Co., Ltd. is a
`
`corporation organized under the laws of South Korea, with its principal place of business at 129
`
`Samsung-ro, Maetan-dong, Yeongtong-gu, Suwon-si, Gyeonggi-do, 443-742, South Korea.
`
`4.
`
`On information and belief, Defendant Samsung Electronics America, Inc., a wholly
`
`owned subsidiary of Samsung Electronics Co., Ltd., is a corporation organized under the laws of
`
`the State of New York, with its principal place of business at 85 Challenger Rd., Ridgefield Park,
`
`New Jersey 07660.
`
`JURISDICTION AND VENUE
`
`5.
`
`This action arises under the patent laws of the United States, Title 35 of the United
`
`States Code. This Court has original subject matter jurisdiction pursuant to 28 U.S.C. §§ 1331 and
`
`1338(a).
`
`6.
`
`This Court has personal jurisdiction over Samsung in this action because Samsung
`
`has committed acts within this District giving rise to this action and has established minimum
`
`contacts with this forum such that the exercise of jurisdiction over Samsung would not offend
`
`traditional notions of fair play and substantial justice. Samsung, directly and through subsidiaries
`
`or intermediaries, has committed and continues to commit acts of infringement in this District by,
`
`among other things, importing, offering to sell, and selling products that infringe the Asserted
`
`Patents.
`
`7.
`
`Venue is proper in this District under 28 U.S.C. §§ 1391 and 1400(b). Defendant
`
`Samsung Electronics America, Inc. is registered to do business in Texas. Additionally, upon
`
`
`
`2
`
`Ex.1015
` Page 2 of 45
`
`GARMIN /
`
`
`
`information and belief, Defendants have transacted business in this District and have committed
`
`acts of direct and indirect infringement in this District by, among other things, making, using,
`
`offering to sell, selling, and importing products that infringe the Asserted Patents. Defendants
`
`have regular and established places of businesses in this District, including at 12100 Samsung
`
`Boulevard, Austin, Texas 78754; 7300 Ranch Road 2222, Austin, Texas 78730; and 1700 Scenic
`
`Loop, Round Rock, Texas 78681. See Exhibits 1-3. Additionally, venue is proper as to a foreign
`
`defendant in any district. 28 U.S.C. § 1391(c)(3); In re HTC Corp., 889 F.3d 1349 (Fed. Cir.
`
`2018). Defendant Samsung Electronics Co., Ltd. is a foreign corporation organized under the laws
`
`of Korea, with a principal place of business in Korea.
`
`THE ASSERTED PATENTS
`
`8.
`
`On November 12, 2013, the United States Patent and Trademark Office issued U.S.
`
`Patent No. 8,581,706 (“the ’706 Patent”), entitled “Data storage medium and method for
`
`contactless communication between the data storage medium and a reader,” after full and fair
`
`examination. Plaintiff is the assignee of all rights, title, and interest in and to the ’706 Patent and
`
`possesses all rights of recovery under the ’706 Patent, including the right to recover damages for
`
`past, present, and future infringement. The ’706 Patent is valid and enforceable. A true and correct
`
`copy of the ’706 Patent is attached hereto as Exhibit 4.
`
`9.
`
`On August 26, 2014, the United States Patent and Trademark Office issued U.S.
`
`Patent No. 8,816,827 (“the ’827 Patent”), entitled “Data storage medium and method for
`
`contactless communication between the data storage medium and a reader,” after full and fair
`
`examination. Plaintiff is the assignee of all rights, title, and interest in and to the ’827 Patent and
`
`possesses all rights of recovery under the ’827 Patent, including the right to recover damages for
`
`
`
`3
`
`Ex.1015
` Page 3 of 45
`
`GARMIN /
`
`
`
`past, present, and future infringement. The ’827 Patent is valid and enforceable. A true and correct
`
`copy of the ’827 Patent is attached hereto as Exhibit 5.
`
`10.
`
`On June 19, 2012, the United States Patent and Trademark Office issued U.S. Patent
`
`No. 8,205,249 (“the ’249 Patent”), entitled “Method for carrying out a secure electronic transaction
`
`using a portable data support,” after full and fair examination. Plaintiff is the assignee of all rights,
`
`title, and interest in and to the ’249 Patent and possesses all rights of recovery under the ’249
`
`Patent, including the right to recover damages for past, present, and future infringement. The ’249
`
`Patent is valid and enforceable. A true and correct copy of the ’249 Patent is attached hereto as
`
`Exhibit 6.
`
`11.
`
`On May 8, 2012, the United States Patent and Trademark Office issued U.S. Patent
`
`No. 8,174,360 (“the ’360 Patent”), entitled “Communication apparatus for setting up a data
`
`connection between intelligent devices,” after full and fair examination. Plaintiff is the assignee
`
`of all rights, title, and interest in and to the ’360 Patent and possesses all rights of recovery under
`
`the ’360 Patent, including the right to recover damages for past, present, and future infringement.
`
`The ’360 Patent is valid and enforceable. A true and correct copy of the ’360 Patent is attached
`
`hereto as Exhibit 7.
`
`SAMSUNG’S INFRINGEMENT
`
`12.
`
`The allegations provided below are exemplary and without prejudice to Plaintiff’s
`
`infringement contentions provided pursuant to the Court’s scheduling order and local rules.
`
`Plaintiff’s claim construction contentions regarding the meaning and scope of the claim terms will
`
`be provided under the Court’s scheduling order and local rules. As detailed below, each element
`
`of at least one claim of each of the Asserted Patents is literally present in the accused products. To
`
`the extent that any element is not literally present, each such element is present under the doctrine
`
`
`
`4
`
`Ex.1015
` Page 4 of 45
`
`GARMIN /
`
`
`
`of equivalents. Plaintiff’s analysis below should not be taken as an admission that the preamble is
`
`limiting. While publicly available information is cited below, Plaintiff may rely on other forms of
`
`evidence to prove infringement, including evidence that is solely in the possession of Samsung
`
`and/or third parties.
`
`13.
`
`The accused products include at least the following products, as well as products
`
`with reasonably similar functionality and all Edge, Plus (+), Active, and SIM varieties of these
`
`products. Identification of the accused products will be provided in Plaintiff’s infringement
`
`contentions pursuant to the Court’s scheduling order and local rules. Samsung imports, uses,
`
`makes, offers for sale, and sells in the United States the following products that support NFC
`
`and/or mobile payment applications, such as Samsung Pay and Google Pay, that infringe at least
`
`one claim of the Asserted Patents: Galaxy S6, S6 Edge, S6 Edge +, S6 Active, S7, S7 Edge, S7
`
`Active, S8, S8+, S9, S9+, S10, S10+, S10e, S10 5G, S20, S20 +, S20 Ultra, S21, S21+, S21 Ultra,
`
`Note 5, Note 7, Note FE, Note 8, Note 9, Note 10, Note 10+, Note 10 5G, Note 20, Note 20 Ultra,
`
`A50, A51, A51 5G, A71 5G, A52 5G, A42 5G, A32 5G, Fold, Fold 2 5G, Fold 3 5G, Flip, Flip
`
`5G, Flip 3 5G, Watch, Watch 3, Watch 4, Watch Active, Watch Active2, Gear Sport, Gear S2
`
`Classic, Gear S2 Sport, Gear S3 Classic, and Gear S3 Frontier (the “Accused Products”). See
`
`https://www.samsung.com/us/support/owners/app/samsung-pay.
`
`COUNT I
`
`INFRINGEMENT OF U.S. PATENT NO. 8,581,706
`
`14.
`
`Plaintiff realleges and incorporates by reference the foregoing paragraphs as if fully
`
`set forth herein.
`
`15.
`
`Samsung has been and is now directly infringing the ’706 Patent, literally and/or
`
`under the doctrine of equivalents, in violation of 35 U.S.C. § 271(a), including by making, using,
`
`
`
`5
`
`Ex.1015
` Page 5 of 45
`
`GARMIN /
`
`
`
`selling, and/or offering for sale in the United States or importing into the United States infringing
`
`products, including at least the Accused Products identified above. The Accused Products satisfy
`
`all of the claim limitations of one or more claims of the ’706 Patent, including but not limited to
`
`claim 11.
`
`16.
`
`Claim 11 of the ’706 Patent recites a “contactlessly communicating portable data
`
`carrier.” To the extent the preamble is limiting, the Accused Products each include a portable data
`
`carrier that is capable of contactless communication through the use of Near Field Communication
`
`(NFC) technology. For example, Samsung advertises that the Accused Products support NFC:
`
`Network &
`
`Connectivity
`
`Galaxy 521 5G and 521. 5G
`
`Galaxy S21 Ultra 5G
`
`5G
`
`5G
`
`56 Non-Standalone (NSA), Standalone (SA),Sub6 / mmWave
`
`56 Non-Standalone (NSA), Standalone ISA), Sub6 / mmWave
`
`LTE
`
`LTE
`
`Enhanced 4x4 MIMO, Up to 7CA, LTE Cat.20
`
`Enhanced awl MIMO, Up to 7CA, LTE Cat.20
`
`Up to 2.0Gbps Download/ Up to 200Mbps Upload
`
`Up to 2.0Gbps Download/ Up to 200Mbps Upload
`
`Wi-Fi
`
`WI-Fl
`
`Wi-Fl 80211 a/b/g/n/aciax 2.4G45GHz,HE80,M1M0,1024-PAM
`
`Wi-F180211 a/b/g/n/ac/ax 2AG.SGHz+66Hz,HE160, MIM0,1024-QAM
`
`Up to 1.2Gbps Download/ Up to 1.2Gbps Upload
`
`Up to 2.4Gbps Download / Up to 2.4Gbps Upload
`
`Bluetooth
`
`Bluetooth
`
`Bluetooth® v5.0, USE, type-C, NEC,
`
`Location (GPS, Galileo, Glonass, BeiDou)
`
`Bluetooth®v 5.2, USB type-C, NEC,
`
`Location (GPS, Galileo, Glonass, BeiDoul
`
`Samsung Pay E li
`
`Credit & debit cards: supports MST and/or NFC
`
`Membership cards
`
`Gift cards
`
`Transit cards
`
`
`
`
`
`See https://www.samsung.com/global/galaxy/galaxy-s21-ultra-5g/specs/.
`
`17.
`
`Claim 11 of the ’706 Patent recites that the portable data carrier comprises “at least
`
`two applications stored thereon.” The Accused Products are configured to store at least two
`
`
`
`6
`
`Ex.1015
` Page 6 of 45
`
`GARMIN /
`
`
`
`applications. For example, the Accused Products are configured to store at least two applications
`
`that utilize NFC:
`
`Service selection
`
`When the user taps a device to an NFC reader, the Android system needs to know which HCE service the NFC reader
`wants to communicate with. The ISO/IEC 7816-4 specification defines a way to select applications, centered around an
`Application ID (AID). An AID consists of up to 16 bytes. If you are emulating cards for an existing NFC reader
`infrastructure, the AIDs that those readers look for are typically well-known and publicly registered (for example, the AIDS
`of payment networks such as Visa and MasterCard).
`
`If you want to deploy new reader infrastructure for your own application, you must register your own AIDs. The
`registration procedure for AIDs is defined in the ISO/IEC 7816-5 specification. We recommend registering an AID as per
`7816-5 if you are deploying a HCE application for Android, because it avoids collisions with other applications.
`
`AID conflict resolution
`
`Multiple HostApduService components may be installed on a single device, and the same AID can be registered by
`more than one service. Android resolves AID conflicts differently depending on which category an AID belongs to. Each
`category may have a different conflict resolution policy.
`
`For some categories, such as payment, the user might be able to select a default service in the Android settings UI. For
`other categories, the policy might be to always ask the user which service to invoke in case of conflict. For information
`about how to query the conflict resolution policy for a certain category, see getSelectionmodeForCategory( ) .
`
`
`
`
`
`See https://developer.android.com/guide/topics/connectivity/nfc/hce.
`
`18.
`
`Claim 11 of the ’706 Patent recites that the portable data carrier comprises “a
`
`communication device configured to control communication between a reading device and the at
`
`least two applications.” The Accused Products contain a communication device configured to
`
`control communication between a reading device and at least two applications. For example, the
`
`Accused Products utilize an NFC antenna, NFC chip, and related hardware and software to control
`
`communication with a reading device and at least two applications, as shown in the exemplary
`
`Samsung S21:
`
`
`
`7
`
`Ex.1015
` Page 7 of 45
`
`GARMIN /
`
`
`
`en IIN
`
`P
`
`
`
`
`
`NFC
`
`01 301010
`
`o°
`
`2BP
`
`-
`
`IIII
`
`111
`
`WPM
`
`illa cry
`
`12.
`
`NI
`
`It
`
`1•11•1•1•9
`
`
`
`8
`
`Ex.1015
` Page 8 of 45
`
`GARMIN /
`
`
`
`:
`
`!It
`
`I
`
`1 f
`
`NFC Chip
`
`! ". 11
`
`f:
`
`I _
`
`.1 :111 .t•i
`mme• ee
`
`;
`
`-• •
`
`*
`
`:
`
`1:
`
`'•••
`:.•
`
`ay
`
`▪ win
`
`•
`
`II
`
`•:I I.
`•
`
`rn
`
`!".
`
`IA al
`
`••••••
`
`..—.
`
`Elr
`
`•
`
`re I
`
`
`
`
`
`9
`
`Ex.1015
` Page 9 of 45
`
`GARMIN /
`
`
`
`
`
`SNICOU
`
`I SParr
`
`EmbecUed NEC controller
`01100 NFCI
`
`Embecklal SecureElement 01,1100_SEI
`
`- khan Masa
`
`1
`
`NK
`Type A/B/
`
`i—UART /12C-1.
`
` SPA—
`
`I
`
`S
`
`Virtual ISO
`
`0 781
`
`sUCC- =thwart Dornaln
`
`ISO.
`
`IMP
`
`AR,
`
`As
`
`Fig. 1.2: SN100x Product Configurations
`See https://www.commoncriteriaportal.org/files/epfiles/SecurityTarget-
`
`Lite_SN100T_v1.1_20190418.pdf; see also https://www.emvco.com/wp-
`
`content/uploads/approved_products/uploaded/loa/MTA_LOA_SAEL_02859_24Nov20_SHORT
`
`.pdf.
`
`
`
`
`
`10
`
`Ex.1015
` Page 10 of 45
`
`GARMIN /
`
`
`
`•
`
`Android device
`
`(SoC)
`
`L Host CPU
`1
`[INFC
`
`Controller
`
`Secure Element
`
`°
`
`SELECT AID "x"
`
`owi eu
`mmiti
`solommillob
`
`SELECT AID
`
`NFC Reads
`
`
`
`See https://developer.android.com/guide/topics/connectivity/nfc/hce.
`
`19.
`
`Claim 11 of the ’706 Patent recites “wherein the communication device is set up to
`
`generate communication-readiness signals to the reading device which in each case indicate to the
`
`reading device a communication readiness for one of the applications and comprise an
`
`identification number assigned to the corresponding communication-readiness application.” The
`
`Accused Products contain a communication device that is set up to generate communication-
`
`readiness signals to the reading device which in each case indicate to the reading device a
`
`communication readiness for one of the applications and comprise an identification number
`
`assigned to the corresponding communication-readiness application. For example, the
`
`communication device generates communication-readiness signals to an NFC reader which
`
`comprise of an Application ID (AID) that corresponds to an application:
`
`
`
`11
`
`Ex.1015
` Page 11 of 45
`
`GARMIN /
`
`
`
`Service selection
`
`When the user taps a device to an NFC reader, the Android system needs to know which HCE service the NFC reader
`wants to communicate with. The ISO/IEC 7816-4 specification defines a way to select applications, centered around an
`Application ID (AID). An AID consists of up to 16 bytes. If you are emulating cards for an existing NFC reader
`infrastructure, the AIDs that those readers look for are typically well-known and publicly registered (for example, the AIDs
`of payment networks such as Visa and MasterCard).
`
`If you want to deploy new reader infrastructure for your own application, you must register your own AIDs. The
`registration procedure for AIDs is defined in the ISO/IEC 7816-5 specification. We recommend registering an AID as per
`7816-5 if you are deploying a HCE application for Android, because it avoids collisions with other applications.
`
`AID conflict resolution
`
`Multiple HostApduService components may be installed on a single device, and the same AID can be registered by
`more than one service. Android resolves AID conflicts differently depending on which category an AID belongs to. Each
`category may have a different conflict resolution policy.
`
`For some categories, such as payment, the user might be able to select a default service in the Android settings UI. For
`other categories, the policy might be to always ask the user which service to invoke in case of conflict. For information
`about how to query the conflict resolution policy for a certain category, see getSelectionModeForCategory() .
`
`The following is an example of the corresponding apduservice. xml file registering two AIDs:
`
`<offhost-apdu-service xmlns:android="http://schemas.android.com/apk/res/android"
`android:description="@string/servicedesc"›
`<aid-group android:description="@string/subscription" android:category="other"›
`<aid-filter android:name="F0010203040506"/>
`<aid-filter android:name="F0394148148100"/>
`</aid-group>
`</offhost-apdu-service>
`
`*
`
`
`
`
`
`
`
`See https://developer.android.com/guide/topics/connectivity/nfc/hce.
`
`20.
`
`Claim 11 of the ’706 Patent recites “wherein the communication device is set up to
`
`store information in a nonvolatile memory of the data carrier about which of the at least two
`
`applications last communicated with a reading device.” Each of the Accused Products contains a
`
`communication device that is set up to store information in a nonvolatile memory of the data carrier
`
`about which of the at least two applications last communicated with a reading device. For example,
`
`the Accused Products provide information about the last application that communicated with a
`
`reading device:
`
`
`
`12
`
`Ex.1015
` Page 12 of 45
`
`GARMIN /
`
`
`
`Basic Functions
`View Recent Transactions
`
`CARD DR TAILS
`
`CHASE 0
`
`--rwr
`VISA
`
`Chem Debit Cord
`pro writer
`D*61 card number T
`
`Tionsealore
`
`The fol.,
`
`ttansactorts herr
`
`SAMSUNG PAY- GIFT CARD
`
`VIC
`
`(rote)
`Pity with lots or fingerptirt
`
`ID note: Transactions made with Samsung Pay are available to view for one month
`from the time of purchase. A push notification with transaction details will be sent to
`your phone after each purchase.
`
`
`
`See https://publish.samsungsimulator.com/simulator/d9740827-40a4-4580-bf1e-
`
`3373b789f187/#!topic/basic_functions/view_recent_transactions.
`
`21.
`
`Samsung also knowingly and intentionally induces infringement of one or more
`
`claims of the ’706 Patent in violation of 35 U.S.C. § 271(b). As of at least the filing and service
`
`of this complaint, Samsung has knowledge of the ’706 Patent and the infringing nature of the
`
`Accused Products. Despite this knowledge of the ’706 Patent, Samsung continues to actively
`
`encourage and instruct its customers and end users (for example, through user manuals and online
`
`instruction materials on its website, and other online publications cited above) to use the Accused
`
`Products in ways that directly infringe the ’706 Patent, for example by utilizing the NFC
`
`functionality on the Accused Products and/or mobile payment applications, such as Samsung Pay
`
`or Google Pay, in an infringing manner. Samsung does so knowing and intending (or with willful
`
`
`
`13
`
`Ex.1015
` Page 13 of 45
`
`GARMIN /
`
`
`
`blindness to the fact) that its customers and end users will commit these infringing acts. Samsung
`
`also continues to make, use, offer for sale, sell, and/or import the Accused Products, despite its
`
`knowledge of the ’706 Patent, thereby specifically intending for and inducing its customers to
`
`infringe the ’706 Patent through the customers’ normal and customary use of the Accused
`
`Products.
`
`22.
`
`Samsung has also infringed, and continues to infringe, one or more claims of
`
`the ’706 Patent by selling, offering for sale, or importing into the United States, the Accused
`
`Products, knowing that the Accused Products constitute a material part of the inventions claimed
`
`in the ’706 Patent, are especially made or adapted to infringe the ’706 Patent, and are not staple
`
`articles or commodities of commerce suitable for non-infringing use. Samsung has been, and
`
`currently is, contributorily infringing the ’706 Patent in violation of 35 U.S.C. §§ 271(c) and (f).
`
`23.
`
`By making, using, offering for sale, selling and/or importing into the United States
`
`the Accused Products, Samsung has injured Plaintiff and is liable for infringement of the ’706
`
`Patent pursuant to 35 U.S.C. § 271.
`
`24.
`
`As a result of Samsung’s infringement of the ’706 Patent, Plaintiff is entitled to
`
`monetary damages (past, present, and future) in an amount adequate to compensate for Samsung’s
`
`infringement, but in no event less than a reasonable royalty for the use made of the invention by
`
`Samsung, together with interest and costs as fixed by the Court.
`
`COUNT II
`
`INFRINGEMENT OF U.S. PATENT NO. 8,816,827
`
`25.
`
`Plaintiff realleges and incorporates by reference the foregoing paragraphs as if fully
`
`set forth herein.
`
`
`
`14
`
`Ex.1015
` Page 14 of 45
`
`GARMIN /
`
`
`
`26.
`
`Samsung has been and is now directly infringing the ’827 Patent, literally and/or
`
`under the doctrine of equivalents, in violation of 35 U.S.C. § 271(a), including by making, using,
`
`selling, and/or offering for sale in the United States or importing into the United States infringing
`
`products, including at least the Accused Products identified above. The Accused Products satisfy
`
`all of the claim limitations of one or more claims of the ’827 Patent, including but not limited to
`
`claim 22.
`
`27.
`
`Claim 22 of the ’827 Patent recites a “contactlessly communicating portable data
`
`carrier.” To the extent the preamble is limiting, the Accused Products include portable data carriers
`
`that are capable of contactless communication through the use of Near Field Communication
`
`(NFC) technology. For example, Samsung advertises that the Accused Products support NFC:
`
`Network &
`
`Connectivity
`
`Galaxy 521 53 and 521. 5G
`
`Galaxy S21 Ultra 5G
`
`5G
`
`5G
`
`5G Non-Standalone (NSA), Standalone (SA), Sub6 / mmWave
`
`5G Non-Standalone (NSA), Standalone ISA), Sub6 / mmWave
`
`LTE
`
`LTE
`
`Enhanced 4x4 MIMO, Up to KA, LIE Cat.20
`
`Enhanced 4x4 MIMO, Up to 7CA, LIE Cat.20
`
`Up to 2.0Gbps Download/ Up to 200Mbps Upload
`
`Up to 2.0Gbps Download/ Up to 200Mbps Upload
`
`Wi—Fi
`
`Wi-Fl 80211 a/b/g/n/aciax 2.4.G.SGHz,HE80, MIM0,1024-QAM
`
`Wi-Fi 80211 a/b/g/n/ac/ax2AG+SGHz+6GHz,HE160, MIM0,11)24-CAM
`
`Up to 1.2Gbps Download / Up to 1.2Gbps Upload
`
`Up to 2.4Gbps Download/ Up to 2.4Gbps Upload
`
`Bluetooth
`
`Bluetooth
`
`Bluetooth® v5.0, USBtype-C, NEC
`Location (GPS, Galileo, Glonass, BeiDou)
`
`Bluetooth0 v 5.2, USB type-C, NEC,
`
`Location (GPS, Galileo, Glonass, BeiDoul
`
`Samsung Pay E:
`
`Credit & debit cards: supports MST and/or NFC
`
`Membership cards
`
`Gift cards
`Transit cards
`
`See https://www.samsung.com/global/galaxy/galaxy-s21-ultra-5g/specs/.
`
`
`
`15
`
`
`
`
`
`Ex.1015
` Page 15 of 45
`
`GARMIN /
`
`
`
`28.
`
`Claim 22 of the ’827 Patent recites that the portable data carrier comprises “at least
`
`a first and second application stored thereon.” The Accused Products are configured to store at
`
`least two applications. For example, the Accused Products are configured to store at least two
`
`applications that utilize NFC:
`
`Service selection
`
`When the user taps a device to an NFC reader, the Android system needs to know which HCE service the NFC reader
`wants to communicate with. The ISO/IEC 7816-4 specification defines a way to select applications, centered around an
`Application ID (AID). An AID consists of up to 16 bytes. If you are emulating cards for an existing NFC reader
`infrastructure, the AIDs that those readers look for are typically well-known and publicly registered (for example, the AIDs
`of payment networks such as Visa and MasterCard).
`
`If you want to deploy new reader infrastructure for your own application, you must register your own AIDs. The
`registration procedure for AIDs is defined in the ISO/IEC 7816-5 specification. We recommend registering an AID as per
`7816-5 if you are deploying a HCE application for Android, because it avoids collisions with other applications.
`
`AID conflict resolution
`
`Multiple HostApduService components may be installed on a single device, and the same AID can be registered by
`more than one service. Android resolves AID conflicts differently depending on which category an AID belongs to. Each
`category may have a different conflict resolution policy.
`
`For some categories, such as payment, the user might be able to select a default service in the Android settings UI. For
`other categories, the policy might be to always ask the user which service to invoke in case of conflict. For information
`about how to query the conflict resolution policy for a certain category, see getSelectionModeForCategory( ) .
`
`
`
`
`
`See https://developer.android.com/guide/topics/connectivity/nfc/hce.
`
`29.
`
`Claim 22 of the ’827 Patent recites “a communication device for controlling
`
`communication between a reading device and the at least first and second applications.” The
`
`Accused Products contain a communication device configured to control communication between
`
`a reading device and the at least first and second applications. For example, the Accused Products
`
`utilize an NFC antenna, NFC chip, and related hardware and software to control communication
`
`with a reading device and at least a first and second application, as shown in the exemplary
`
`Samsung S21:
`
`
`
`16
`
`Ex.1015
` Page 16 of 45
`
`GARMIN /
`
`
`
`en IIN
`
`P
`
`
`
`
`
`NFC
`
`01 301010
`
`o°
`
`2BP
`
`-
`
`IIII
`
`111
`
`WPM
`
`illa cry
`
`12.
`
`NI
`
`It
`
`1•11•1•1•9
`
`
`
`17
`
`Ex.1015
` Page 17 of 45
`
`GARMIN /
`
`
`
`:
`
`!It
`
`I
`
`1 f
`
`NFC Chip
`
`! ". 11
`
`f:
`
`I _
`
`.1 :111 .t•i
`mme• ee
`
`;
`
`-• •
`
`*
`
`:
`
`1:
`
`'•••
`:.•
`
`ay
`
`▪ win
`
`•
`
`II
`
`•:I I.
`•
`
`rn
`
`!".
`
`IA al
`
`••••••
`
`..—.
`
`Elr
`
`•
`
`re I
`
`
`
`
`
`18
`
`Ex.1015
` Page 18 of 45
`
`GARMIN /
`
`
`
`
`
`SNICOU
`
`I SParr
`
`EmbecUed NEC controller
`01100 NFCI
`
`Embecklal SecureElement 01,1100_SEI
`
`- khan Masa
`
`1
`
`NK
`Type A/B/
`
`i—UART /12C-1.
`
` SPA—
`
`I
`
`S
`
`Virtual ISO
`
`0 781
`
`sUCC- =thwart Dornaln
`
`ISO.
`
`IMP
`
`AR,
`
`As
`
`Fig. 1.2: SN100x Product Configurations
`See https://www.commoncriteriaportal.org/files/epfiles/SecurityTarget-
`
`Lite_SN100T_v1.1_20190418.pdf; see also https://www.emvco.com/wp-
`
`content/uploads/approved_products/uploaded/loa/MTA_LOA_SAEL_02859_24Nov20_SHORT
`
`.pdf.
`
`
`
`
`
`
`
`19
`
`Ex.1015
` Page 19 of 45
`
`GARMIN /
`
`
`
`Android device
`
`r Host CPU
`
`(SoC)
`
`:
`
`NFC Controller
`
`4*--111.
`
`Secure Element
`
`SELECT AID "x"
`
`b
`a olliimi
`400111•11111.6
`
`SELECT AID "y"
`
`NFC Reader
`
`
`
`See https://developer.android.com/guide/topics/connectivity/nfc/hce.
`
`30.
`
`Claim 22 recites “wherein the communication device is configured to generate a
`
`first communication-readiness signal to the reading device which indicates to the reading device a
`
`communication readiness for the first application and a second communication-readiness signal to
`
`the reading device which indicates the reading device a communication readiness for the second
`
`application and comprise an identification number assigned to the corresponding communication-
`
`readiness application.” The Accused Products contain a communication device that is configured
`
`to generate a first communication-readiness signal to the reading device which indicates to the
`
`reading device a communication readiness for the first application and a second communication-
`
`readiness signal to the reading device which indicates the reading device a communication
`
`readiness for the second application and comprise an identification number assigned to the
`
`corresponding communication-readiness application. For example, the communication device
`
`generates communication-readiness signals to an NFC reader which comprise of an Application
`
`ID (AID) that corresponds to an application:
`
`
`
`20
`
`Ex.1015
` Page 20 of 45
`
`GARMIN /
`
`
`
`Service selection
`
`When the user taps a device to an NFC reader, the Android system needs to know which HCE service the NFC reader
`wants to communicate with. The ISO/IEC 7816-4 specification defines a way to select applications, centered around an
`Application ID (AID). An AID consists of up to 16 bytes. If you are emulating cards for an existing NFC reader
`infrastructure, the AIDs that those readers look for are typically well-known and publicly registered (for example, the AIDs
`of payment networks such as Visa and MasterCard).
`
`If you want to deploy new reader infrastructure for your own application, you must register your own AIDs. The
`registration procedure for AIDs is defined in the ISO/IEC 7816-5 specification. We recommend registering an AID as per
`7816-5 if you are deploying a HCE application for Android, because it avoids collisions with other applications.
`
`AID conflict resolution
`
`Multiple HostApduService components may be installed on a single device, and the same AID can be registered by
`more than one service. Android resolves AID conflicts differently depending on which category an AID belongs to. Each
`category may have a different conflict resolution policy.
`
`For some categories, such as payment, the user might be able to select a default service in the Android settings UI. For
`other categories, the policy might be to always ask the user which service to invoke in case of conflict. For information
`about how to query the conflict resolution policy for a certain category, see getSelectionModeForCategory() .
`
`The following is an example of the corresponding apduservice. xml file registering two AIDs:
`
`<offhost-apdu-service xmlns:android="http://schemas.android.com/apk/res/android"
`android:description="@string/servicedesc"›
`<aid-group android:description="@string/subscription" android:category="other"›
`<aid-filter android:name="F0010203040506"/>
`<aid-filter android:name="F0394148148100"/>
`</aid-group>
`</offhost-apdu-service>
`
`*
`
`
`
`
`
`
`
`Android device
`
`Host CPU
`(SoC)
`
`A
`
`V
`
`NFC Controller
`
`Stleur EjAle
`
`SELECT AID "x"
`
`
`
`4111.illiowirob i SELECT AID "y' .1b
`
`
`
`
`
`21
`
`
`
`Ex.1015
` Page 21 of 45
`
`GARMIN /
`
`
`
`See https://developer.android.com/guide/topics/connectivity/nfc/hce.
`
`31.
`
`Claim 22 of the ’827 Patent recites “wherein the first communication-readiness
`
`signal is generated for a first group of applications comprising a first plurality of applications
`
`including the first application, and the first identification number is assigned to every application
`
`in the first group, and the second communication-readiness signal is generated for a second group
`
`of applications comprising a second plurality of applications including the second application, and
`
`the second identification number is assigned to every application in the second group, the first
`
`communication-readiness signal indicating to the reading device the communication readiness of
`
`every application of the first group, and the second communication-readiness signal indicating to
`
`the reading device the communication readiness of every application of the second group.” The
`
`Accused Products generate the first communication-readiness signal for a first group of
`
`applications comprising a first plurality of applications including the first application, and the first
`
`identification number is assigned to every application in the first group, and the second
`
`communication-readiness signal is generated for a second group of applications comprising a
`
`second plurality of applications including the second application, and the second identification
`
`number is assigned to every application in the second group, the first communication-readiness
`
`signal indicating to the reading device the communication readiness of every application of the
`
`first group, and the second communication-readiness signal indicating to the reading device the
`
`communication readiness of every application of the second group. For exam