as) United States
`a2) Patent Application Publication co) Pub. No.: US 2010/0190437 Al
`
` Buhot (43) Pub. Date: Jul. 29, 2010
`
`
`US 20100190437A1
`
`(54) WIRELESS COMMUNICATION DEVICE FOR
`PROVIDING AT LEAST ONE NEAR FIELD
`COMMUNICATION SERVICE
`
`(75)
`
`Inventor:
`
`Thomas Buhot, Toulouse (FR)
`
`(73
`
`(21
`
`(22
`
`(30
`
`(51
`
`Correspondence Address:
`MOTOROLAINC
`600 NORTH US HIGHWAY45, W4 - 39Q
`LIBERTYVILLE,IL 60048-5343 (US)
`
`Assignee:
`
`MOTOROLA,INC., Schaumburg,
`IL (US)
`
`Appl. No.:
`
`12/646,251
`
`Filed:
`
`Dec. 23, 2009
`
`Foreign Application Priority Data
`
`an. 26, 2009
`
`(EP) ooeee LEP09290052
`
`Publication Classification
`
`Int. Cl.
`HO4B 5/00
`
`(2006.01)
`
`
`
`(52) U.S. CI. sseccssssssssssssssssssssssssssenssssssvesenssneee 455/411
`(57)
`ABSTRACT
`A wireless communication device (102) is arranged to pro-
`videat least one Near Ficld Communication service to a user.
`The wireless communication device (102) comprises a Near
`Field Communication unit (218) for storing a plurality of
`application elements (302-312) for use in providing a plural-
`ity of Near Field Communication services, and a plurality of
`Near Field Communication managing elements (318-328).
`Each of the plurality ofNear Field Communication managing
`elements (318-328) is associated with at least one ofthe
`plurality ofapplication elements (302-312) stored in the Near
`Field Communication unit (218) for managingtheat least one
`associated application elementof the plurality of application
`elements. A user interface element (224) interfaces with at
`east some of the Near l'ield Communication managing ele-
`ments (318-328) and provides informationto a user relating
`o the Near Ficld Communication services provided by the
`plurality of application elements (302-312) associated with
`he at least some ofthe Near Field Communication managing
`elements. In operation, the user interface element (224) in
`response to user selection of a Near Field Communication
`service based on the user provided information is further
`arrangedto activate the Near Field Communication managing
`elementofthe selected Near Field Communication service to
`manage theat least one associated application clement.
`
`Ne
`
`114
`
`108
`
`110
`
`102
`
`100
`
`Apple Ex. 1005, p. 1
`Apple Ex. 1005,p. 1
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 1 of 9
`
`US 2010/0190437 Al
`
`Ne
`
`114
`
`108
`
`110
`
`102
`
`106
`
`100
`
`FIG. 1
`
`Apple Ex. 1005, p. 2
`Apple Ex. 1005, p. 2
` Apple v. Fintiv
`Apple v. Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 2 of 9
`
`US 2010/0190437 Al
`
`FIG.2
`
`Apple Ex. 1005, p. 3
`Apple Ex. 1005, p. 3
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 3 of 9
`
`US 2010/0190437 Al
`
`
`
`
`
`vg
`
` reeeee———_————EOEEEOE—_OEEE_OEEE—_EOEEEE—_OE——EE—EOEEEEEEEO—EEEEEEOEEEOEOEOO|
` ||||||968ZAvd«4228!||I
`
`:||oveLogs||||I
`IIIWEi|
`Zre+86
`
`Apple Ex. 1005, p. 4
`Apple Ex. 1005,p. 4
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 4 of 9
`
`US 2010/0190437 Al
`
`a6
`
`500
`33f
`
`
`
`NFC MANAGING
`REGISTRATION
`ELEMENT
`ELEMENT
`
`
`
` GET INSTANCE
`| REGISTRATIONINSTANCE oe
`
`
`
`504
`
`
`
`ADD MANAGING ELEMENT
`
`508
`
`REGISTER A NEW NFC
`MANAGING ELEMENT
`
`FIG. 5
`
`Apple Ex. 1005, p. 5
`Apple Ex. 1005, p. 5
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 5 of 9
`
`US 2010/0190437 Al
`
`€@INSW3714ONISVNVIN
`
`
`VLNAWSTSONISVNVN
`~|AdAL139_|\999|ISevo_||SauvoLSI||adAL_||AdALLID[-—
`
`
`
`Q3YSLS193dLWHLSLNAWF13
`ONISVNVAOANSHLLSI
`
`
`
`r09
`
`LNSWSTS
`
` V9Dla
`
`JANNOILVYLSIOSy
`JANNOILVYLSIOSY
`NOILVY.LSIO4Y
`
`JOVAYSLNIY3aSN
`
`
`
`OANISAYV9
`
`AHLLAS
` ANISNA
`
`YdSNSHLLOdTAS
`
`
`
`LNAW313SOVAYALNI
`
`009
`
`Apple Ex. 1005, p. 6
`Apple Ex. 1005,p. 6
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`
`
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 6 of 9
`
`US 2010/0190437 Al
`
`
`
`GYV9139aSWVNGuo>JWYNGYVOLAD '
`
`
`
`O19
`
`LSIGuv9SHLaNd
`
`809
`
`@9DI
`[OOGav_|_——roamaa}——»_—ro|NOOIGVO.NOOI
`
`
`ISIGYVv9AHLALVddN
`OANISGYVOSHLHLIM
`
`
`OANISCUVO
`OANISAYV9
`
`|0|AHLAVIdSIO
`
`
`
`“19
`
`
`
`Apple Ex. 1005, p. 7
`Apple Ex. 1005,p. 7
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`
`
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 7 of 9
`
`US 2010/0190437 Al
`
`
`
`
`VINSW314SAOVAYSLNIYSNVINAWS13
`
`
`
`
`SS300UdONVCYVOLOATASNOLLOVSNVULONISSADONd
`
`
`
`NOILVAYOSNIGYVOAHL139
`
`dHL139
`
`
`
`OANISQYVO
`
`
`
`OANISGUVO
`
`yeas|
`
`YASNSHLLOATSS
`
`
`
`LNAWITSJOVAYSLNI
`
`NOLLVAXYOANIGYV9AV1dSId
`
`ANIDNA ONISVNVINDANINSW3714SNISYNVWO4NNOLLVYLSIOSYJOVAYSLNIYASN
`
`
`
`
`
`
`
`Lavis404dYvo¥1035738
`
`Apple Ex. 1005, p. 8
`Apple Ex. 1005, p. 8
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 8 of 9
`
`US 2010/0190437 Al
`
`
`
`dNLAsNOLLOVSNVYL
`
`(NOLLVZITVLLINI
`
`NOILOVSNVYL
`
`
`
`YSNAHLONILIANISDVSSAW
`
`INOWNIFTIGOWSIHSAVMOL
`
`WNIWYSLFHLJO
`
`NOILOVSNVUL
`
`JOGNA
`
`
`
`JHLONINYOANIADVSSAWN
`
`AHL40ONSAHL4043SN
`
`NOLLOVSNVYL
`
`GZDIA
`
`
`JUYMLIOSCNYSYVMCYVH)[—-O1Z
`LYVLSM0|ry|ClL
`
`Gd
`
`Bld
`
`|0|
`
`024
`
`Apple Ex. 1005, p. 9
`Apple Ex. 1005, p. 9
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`
`
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 9 of 9
`
`US 2010/0190437 Al
`
`PROVIDING TO A USER INFORMATION
`RELATING TO AVAILABLE NFC SERVICES
`
`SELECTING BY A USER A NFC SERVICE
`BASED ON PROVIDED INFORMATION
`
`MANAGE THE APPLICATION ELEMENT
`
`ACTIVATING THE NFC MANAGING ELEMENT
`OF THE SELECTED NFC SERVICE TO
`
`FIG. &
`
`Apple Ex. 1005, p. 10
`Apple Ex. 1005, p. 10
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0190437 Al
`
`Jul. 29, 2010
`
`WIRELESS COMMUNICATION DEVICE FOR
`PROVIDING AT LEAST ONE NEAR FIELD
`COMMUNICATION SERVICE
`
`FIELD OF THE DISCLOSURE ies
`
`
`
`[0001] This disclosurerelates to a wireless communication
`device for providing at least one Near Field Communication
`service to a user and a method of providing a Near Field
`Communication service by a wireless communication device.
`
`BACKGROUND OF THE DISCLOSURE
`
`[0002] Near Ficld Communication (NFC)is a short-range
`wireless communication technology which enables the
`exchange of data between devices allowing users of NI'C
`enabled devices to use NFC services such as performing
`contactless transactions, accessing digital content and con-
`necting devices with a single touch.
`[0003] NFC is based on contactless and Radio Frequency
`Identification (RFID) solutions, whichtypically consist of a
`tag or device storing a small amountofdata and a reader. The
`reader, whenactivated, emits a short-range radio signal that
`when brought next to the tag, powers up a microchip on the
`tag, and allows for reading a small amount of data that is
`stored on the tag. However, NFC is different from other
`contactless or RFID technologies in thatit has a very short
`operating distance and also allows two devices to intercon-
`nect. The effective distance of an NFC solution depends on
`the tag design and the reader, but is typically only a few
`centimetres. The underlying layers of NFC technology are
`
`based on ISO/IEC 14443, ECMA 340,ECMA 352, ETSI 102
`613, and NFC forum standards.
`[0004]
`Investigations are being performedinto the use of
`NFC in mobile phones. The current main use cases for NFC
`in a mobile phoneinclude:
`[0005] Card emulation—the NI'C enabled device can
`behavelike an existing contactless NFC card;
`[0006]
`Reader mode: the NFC enabled device can read a
`passive NFCtag, for examplefor interactive advertising;
`[0007]
`Peer-to-Peer (P2P) mode: two NFCenabled devices
`can communicate together and exchanging informatione.g.
`to set up a Bluetooth connection.
`[0008] Examples ofthe different types ofNFC servicesthat
`maybe available to an user of a mobile phone having NFC
`capability include:
`[0009] Ticketing services such as mobile ticketing in public
`transport which is an extension ofthe existing contactless
`infrastructure, and electronic Uickeling such as for airline
`tickets, concert/eventtickets;
`[0010]
`Payment services where for example the mobile
`phoneacts as a debit/credit payment card or possibly elec-
`tronic money;
`[0011] Advertising services where for example the mobile
`phoneis used to read NFC tags on advertising boards in order
`to access information easily whilst on the move;
`[0012] Exchanging small amounts of data quickly such as
`electronic business cards, calendar synchronisation,
`[0013]
`Bluetooth or Wi-Fi pairing where for example the
`process ofactivating Bluetooth or Wi-Fi between two devices
`can be achieved by a simple “touch” of the devices and
`thereafter communication takes place over a Bluetooth or
`Wi-Fi communication link;
`[0014] Loyalty services, for example,
`acts as a loyalty card; and
`
`
`
`
`
`the mobile phone
`
`Identity services, for example, the mobile phone
`[0015]
`acts as an identity card or key.
`[0016] A mobilephonethat supports NFC,and for example
`the card emulation mode, contains a secure element for stor-
`ing different NFC application elements for use in providing
`the NFC services. The secure clement may be a dedicated
`module or chipset that is part of the mobile phone or may be
`aremovable component, such as the UMTSIntegrated Circuit
`Card (UICC) also knownas the SIM card or USIM card or a
`removable memory card.
`[0017] When for example the mobile phoneis in the card
`emulation modeandactslike a contactless card, a contactless
`reader can select the contactless NFC application elements
`stored in the secure element of the mobile phone and
`exchange Application Protocol Data Unit (APDU) com-
`mands with the NFC application elements so as to proceed
`with contactless transactions (as defined by the 15S014443-4
`standard). This may involve retricving cardholder banking
`information fromthe selected NFC application element(s).
`[0018] Asdiscussed above,different types ofNFC services
`maybe available andthus, different types ofNFC application
`elements associated with the different types ofNFC services,
`such as payment, transport, ticketing, or loyalty NFC ele-
`ments, may be stored in the secure element. There can also be
`different NFC application elements of the same type at the
`same time stored in the secure element. For example, there
`may be several payment type contactless NFC application
`elements stored in the secure element, such as PayPass™
`NFC application element from MasterCard®, Visa Smart
`Debit Credit™ (VSDC) NFC application clement from
`
`Visa® or ExpressPay™ NFC application element from
`American Express®. Current payment application elements,
`such as the examples given above from Mastercard®, Visa®
`and American express®, are typically stand alone applica-
`tions which usually run in their own secure environment
`(whichis generally a global platform or JavaCard based) and
`are protected bya firewall of the runtime environmentin the
`secure clement (as defined, for example, by the JavaCard
`runtime environment or the global platform specification).
`This is because these payment application elements typically
`correspondto the reference contactless application elements
`developed and already deployed for contactless smartcards,
`whereonlyonesingle contactless application element runs on
`acontactless smartcard andthus,they have not been designed
`to coexist or interface with other application elements.
`[0019] Having a plurality of stand alone NFC application
`elements, particularly when there are several NFC applica-
`tion elements of the sametype, for use in a mobile phone can
`raise a numberofissues due to the fact that each NFC appli-
`cation element operates in isolation of the other elements.
`Such issues include, for example, difficulties for a user to
`manage such stand alone NFC application elements. For
`example, with stand alone application elements, whena user
`wishes to change dynamically the available NFC services
`which will involve changing the NFC application elements
`stored in the secure element, the user has to view and select
`each NFC application element separately. These issues are
`likely to increase as the numberof available NFC services
`increase, and the number ofapplication element providers
`increase,
`
`In order to take account of specific issues that arise
`[0020]
`whenproviding NFC services ina mobile phone, an approach
`would be to modify the reference contactless application
`elements for NFC applicationsto allow, for example, interop-
`
`Apple Ex. 1005, p. 11
`Apple Ex. 1005, p. 11
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0190437 Al
`
`Jul. 29, 2010
`
`disclosure will now be described, by way of cxample only,
`erability or interfacing with other clements or OTAprovision-
`withreference to the accompanying drawings in which:
`ing. However, this would require for the application clement
`[0024] TIG.1 isa block schematic diagram of a communi-
`providers to modify their reference application elements to
`cation system arrangement in accordance with an embodi-
`support these services on NFC devices which will involve
`ment ofthe disclosure;
`extra cost, new code baseline, new deployment and newcer-
`[0025]
`FIG.2 is a block schematic diagramof a wireless
`tification processes.
`communication device in accordance with an embodiment of
`[0021]
`Some mobile phones include NFC managing appli-
`the disclosure;
`cations which may run on an application processor ofthe
`[0026]
`FIG. 3 is a schematic representation of example
`mobile device and whichactivate NFC application elements
`NFCapplication elements held in the NFC unit of FIG. 2 and
`and handle the NFC services, for example, for mobile pay-
`exampleuserinterface elements of T1G.2 in accordance with
`ment, ticketing, transport, access etc. These NFC managing
`an embodimentofthe disclosure;
`applications canbe native applications or Java applications.
`[0027]
`FIG. 4 is a block schematic diagram of an example
`Tach NIC managing application may manageseveral appli-
`UICC card implementation of the NFC unit of the wireless
`cation elements from the same application provider at the
`communication device of FIG.2;
`same time. For example, a payment NFC managing applica-
`
`[0028] FIG.5isa simplified schematic diagram represent-
`tion may support several payment card application elements
`ing an example flowofinteractions betweenthe userinterface
`and a ticketing NFC managing application may support dif-
`element and a NFC managing element whenregistering the
`ferent ticketing card application elements. These NFC man-
`NFC managing element in accordance with an embodiment
`aging applications enable a userto select a card (i.e. a card
`ofthe disclosure;
`application element) amonga list associated with the NFC
`[0029]
`FIG.6 is a simplified schematic diagram represent-
`application to pay, get on the bus, access a building, etc. A
`ing an exampleflowofinteractions betweenthe userinterface
`NFC managing application can handle card applicationele-
`element and two NFC managing elements when gathering
`ments of different types such as payment, ticketing or trans-
`NFCservice information in accordance with an embodiment
`port card applications from the sameapplication provider.
`of the disclosure;
`[0022] As the number of NEC services and the numberof
`[0030] TIG. 7 is a simplified schematic diagram represent-
`application providers increases, in order to support several
`ing an example flowofinteractions between the userinterface
`NFC managing applications from different application pro-
`element and a NFC managing element during user selection
`viders at the same time, many NFC managing applications,
`of a NFC service in accordance with an embodimentof the
`such as payment,ticketing, or access, are installed and may be
`disclosure; and
`running simultancously on the NFC mobile phonc. Since
`[0031]
`FIG. 8 is a flow diagramof a methodfor providing a
`there is currently no interoperability between these different
`NFC service by a wireless communication device in accor-
`NFC managingapplications andthe different application pro-
`dance with an embodimentofthe disclosure.
`viders, information cannot be shared even between two NFC
`managing applications supporting the same use case (such as
`payment, ticketing, transport, etc). For example, if a user
`installs two different payment NFC managing applications
`provided by two different banks (A & B) on an NFC mobile
`phone, the NFC managing application of the bank B cannot
`address cards from the bank A and vice versa. This means that
`from a user’s point of view there may be several NFC man-
`aging applications from different application providers to
`access the same sel of! NFC services which makes accessing
`the NFC services more complicated and less user friendly.
`For example, it may not bepossible for the userto list, access,
`and manageall the card application elements on the user’s
`NFC mobile phone at once. Furthermore, since a card. appli-
`cation element can only be managed by the associated NFC
`managing application, in orderto use a given card application
`element for payment, transport, access, etc., the user has to
`remember with which NFC managing application the card
`application elementis associated. In addition, the application
`elementlist information presented to the user on the mobile
`phone’s user interface to select a card application element
`from the different NI'C managing applications is not stan-
`dardized and will differ from one NFC managing application
`to another depending onthe application provider’s specifica-
`tion.
`
`
`
`DETAILED DESCRIPTION OF TIE DRAWINGS
`
`In the following description, examples of embodi-
`[0032]
`ments of the disclosure will be described with respect to a
`mobile device operating within one or more wireless commu-
`nication networks, such as a 2nd generation cellular commu-
`nication system known as the Global System for Mobile
`communication (GSM) with General Packet Radio System
`(GPRS)capability, a 3rd generation cellular communication
`system such as an Universal Mobile Telecommunication sys-
`tem (UMTS), or Long Term Evolution (LTE) communication
`system. It will however be appreciated the present disclosure
`can be usedin other types ofwireless communication devices
`and networks, such as a subscriber unit, wireless user equip-
`ment, a portable telephone, a wireless video or multimedia
`device, a communication terminal, a personaldigital assistant
`(PDA), a laptop computer, or any electronic device having
`wireless capability, such as a digital camera which can trans-
`fer pictures wirclessly. The term wireless communication
`device for providing at least one NFC serviceis thus intended
`to cover all electronic devices which have wireless capability
`to provide NFC services to a user.
`[0033] Referring firstly to FIG. 1, a communication system
`arrangement 100 comprises a mobile device 102 having NFC
`capability (that is, having wireless capability to provide NFC
`services to a user) and being capable of operating with a
`communication system 104 such as a GSM communication
`system. In the following, the communication system will be
`described as a GSM communication system but it will be
`appreciated that the disclosure may apply to any communi-
`cation system andit is not intended to limit the disclosure to
`
`Apple Ex. 1005, p. 12
`Apple Ex. 1005, p. 12
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0023] A wireless communication device for providing at
`least one Near Field Communication service to a user and a
`method of providing a Near Field Communication service by
`a wireless communication device, in accordance with the
`
`

`

`US 2010/0190437 Al
`
`Jul. 29, 2010
`
`Go
`
`a GSM communication system. As is well known, the GSM
`communication system 104 provides a plurality of coverage
`areasor cells (not shown)served bybasestations (not shown)
`with which the mobile device 102 can operate or communi-
`cate via radio communication links (suchaslink 108 shownin
`FIG. 1). Device 106 also has NFC capability and may be
`another mobile device capable of operating with the GSM
`communication system 104 or with another wireless commu-
`nication system (not shown) or maybe a fixed device such as
`a NFCtag or may bea reader device suchas a contactless card
`reader (fixed or mobile). When the mobile device 102 and
`device 106 are close enough, for example within a couple of
`centimetres, a NFC communication link 110 can be estab-
`lished and data can be exchanged between the devices 102,
`106.
`In an example, the device 106 may be a contactless
`[0034]
`card reader which may be connected to a backend system(not
`shown) and the mobile device 102 can support a card emula-
`tion mode. A NFC communication link 110 is established
`between the mobile device 102 and the card reader device 106
`to exchange data so that the mobile device 102 may enter a
`card emulation modein whichit acts as a contactless card and
`contactless transactions may then be performed.
`[0035]
`In another example, the mobile device 102 and the
`device 106 may be devices having Bluctooth communication
`capability. A NFC communication link 110 is established
`between the mobile device 102 and the device 106 to
`exchange data so as to enable a Bluetooth communication
`link to be established between the devices for subsequent
`communications.
`[0036] The mobile device 102 mayactas a reader/writer or
`a tag.
`[0037] FIG.2 is a block diagram ofa wireless communica-
`tion device, such as the mobile device 102 shownin FIG.1, in
`accordance with an embodimentofthe disclosure. As will be
`apparent to a skilled person, FIG. 2 shows only the main
`functional components of an exemplary mobile device 102
`that are necessary for an understanding of the invention.
`[0038] The mobile device 102 comprises a processing unit
`200 for carrying out operational processing, for the mobile
`device 102. The mobile device 102 also has a RI’ communi-
`cation section 202 for providing wireless communicationvia
`a radio communication link 108 with the GSM communica-
`tion system 104 and a NFC communication section 204 for
`providing NFC services via a NFC communicationlink 110.
`The mobile device may, for example, establish a NFC com-
`munication link with a reader having NFC capability via the
`NIC communication section 204 when the mobile device 102
`is within a couple of centimetres ofthe reader. ‘The RF com-
`munication section 202 typically includes, for example, an
`anlenna 206,
`transmit and receive paths 208 including a
`modulation/demodulation section (not shown), and a coding/
`decoding section (not shown), as will be knownto a skilled
`person and thus will not be described further herein. The NFC
`communication section 204 typically includes, for example, a
`NFC antenna 210 and a modulation/demodulation section
`212, as will be knownto a skilled person and thus will not be
`described further herein. The communication sections 202,
`204 are coupled to the processing unit 200.
`[0039] The mobile device 102 also has a Man Machine
`Interface MMI 214, including elements such as a key pad,
`microphone, speaker, display screen, for providing an inter-
`face between the mobile device 102 and a user of the device.
`The MMI 214is also coupled to the processing unit 200.
`
`
`
`[0040] The processing unit 200 maybe a single processor
`or may comprise two or more processors carrying out the
`processing required for the operation of the mobile device
`102. The numberofprocessors and the allocation of process-
`ing, functions to the processing unit is a matter of design
`choice for a skilled person. The mobile device 102 also has a
`program memory 216 in which is stored programscontaining
`processorinstructions for operation ofthe mobile device 102.
`The programs may contain a numberof different program
`elements or sub-routines containing processor instructions
`or a variety of different tasks, for example, for: communi-
`cating with the user via the MMI 214; and processing signal-
`ing, messages (e.g. paging signals) received from the com-
`munication system 104.
`[0041]
`‘lhe mobile device 102 further comprises a NFC unit
`218 which can act as a secure elementto store at least one
`NFCapplication element for use in providing at least one
`NFCservice. The NFC unit 218 may store only one NFC
`application elementbut typically, the NFC unit 218 will store
`a plurality of NFC application elements associated with a
`plurality of NI'C services, with someofthe services being of
`he same type. For example, the NFC unit 218 may store
`several contactless payment application elements fromdif-
`erent service providers such as MasterCard®, Visa®, and
`
`American Express®. The NFC unit 218 is coupled to the
`processing unit 200 and may comprise a removable module or
`a module incorporated into the mobile device 102. The NFC
`unit 218 may also be coupled to the NFC communication
`section 204. Whether the module is removable or incorpo-
`rated into the mobile device 102, the module may be a dedi-
`cated module whosesole function is for providing, NFC ser-
`vices or may be a module that has other functions additional
`to providing NFCservices.
`[0042] Whenthe NFC unit 218 includes a removable mod-
`ule (represented bythe dotted box 220 in FIG.2), an interface
`222 is coupled to the processing unit 200 for interfacing
`between the removable module 220 and the processing unit
`200. The removable module 220 maybe a SubscriberIdentity
`Module (SIM) card or a Universal Integrated Circuit Card
`(UICC) which, in addition to storing network specific infor-
`mationused to authenticate and identify the subscriber on the
`GSM communication system 104 (and/or other systems) to
`control access, also stores the NFC application elements. In
`his case, the interface 222 is a SIMor UICCinterface. The
`UICC card is the nameofthe standardised platform that can
`run several telecom applications such as the USIM applica-
`ion for a 3G network, or the SIM application for a 2G net-
`work, or others. he UICC card was introduced with the
`release 99 of the 3GPP standards, and replaces the SIMplat-
`orm (that has GSM capabilities only). The term UICC card
`will be used for the rest of the document to designate the
`ntegrated Circuit Card (ICC) used in a mobile phonefor the
`support of the telecom applications such as USIM,SIM,and
`SIM.
`
`
`
`[0043] Communication between the NFC unit 218 and the
`processing unit 200 may occur via a direct connection
`througha serial link, such as an ISO link between the UICC
`interface 222 and the processing unit 200, or via the NFC
`modulator/demodulator 212 that acts as a proxy.
`[0044] When NIC unit 218 is a dedicated module that is
`incorporated into the mobile device 102, the module may be
`soldered on the main Printed Circuit Board (PCB) ofthe
`mobile device 102 or may be a removable module such as a
`memory card and will act as a dedicated secure memory
`
`Apple Ex. 1005, p. 13
`Apple Ex. 1005, p. 13
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0190437 Al
`
`Jul. 29, 2010
`
`coupled to the processing unit 200, for example via a ISO link
`or any other suitable connection (such as USB, fC). The
`dedicated module may comprise, for example, an Integrated
`Circuit (IC) whichis substantially the same as the IC used for
`contactless smartcard devices.
`
`
`
`[0045] The NIC unit 218 mayalternatively be a element in
`the mobile device 102 which emulates a UICC card or a
`memory card. For example, the NFC unit 218 may be an NFC
`unit element (not shown) which is part of the program
`memory 216.
`[0046]
`FIG. 4 showsa simplified schematic diagramofan
`example of a UICC implementation of a NFC unit 218 in
`accordance with an embodimentofthe disclosure. The UICC
`NFC unit 218 comprises the UICCinterface 222 for coupling
`to the processing unit 200, the UICC card 220 when coupled
`to the mobile device 102 and aninterface 404 for coupling to
`the NFC modulator/demodulator or modem 212. In an
`example, interface 404 is a Host Controller Interface (HCI)
`
`interface which controls the communication ofdata accord-
`
`
`
`ing to a protocol standardised by ETSI (ETSI 102 622). The
`UICC card 220 typically comprises a processor 400 and
`memory 402. In the example shown in FIG.2, the program
`memory 216 stores specific program elementsfor controlling
`the operation of the mobile device 102 by means of the
`processing unit 200 which include a user interface element
`224, and a plurality of NFC managing elements (represented
`
`as group by 226 in FIG. 2). Each of the plurality of NFC
`managing elements is associated with at least one of the
`plurality of application elements stored in the NFC unit 218
`for managingthe at least one associated application clement
`of the plurality of application elements. The user interface
`element 224 is for interfacing withat least some of the NFC
`managing elements, and for providing information to a user
`relating to the NFC services provided by the plurality of
`application elements associated with theat least some of the
`NFC managing elements. In operation, the user interface
`element 224 in response to user selection of a NFC service
`based on the user provided information is further arranged to
`activate the NI'C managing element of the selected NI'C
`service to manage the at least one associated application
`
`element. Each ofthe plurality of NFC managing elementsis
`arranged to manage the al least one associated application
`element so as to controlthe at least one associated application
`element to provide a NFC service or to update a NFC service.
`A NEFCservice maybe updated by adding a newapplication
`element to the NFC unit 218, by updating one or more param-
`eters ofthe at least one associated application element and by
`removing the at least one associated application element
`stored in the NFC unit 218.
`[0047]
`It will be appreciated that in addition to the user
`interface element 224, each of the NFC managing elements
`mayhave ils own dedicated user interface which is indepen-
`dent from the user interface element 224 and dedicated user
`interfaces of other NFC managing elements. The dedicated
`user interface of a NFC managing element maybe a regular
`application that is currently deployed on NFC devices and
`which provide logic to manage the NFC application elements
`in the NFC unit 218 as well as a user interface to trigger
`contactless transactions for the NFC application elements
`they manage.
`[0048] Referring now to FIG. 3 whichillustrates schemati-
`cally and in more detail the arrangement of the NFC applica-
`tion elements held in the NFC unit 218 and the elements 224,
`and 226 in accordance with an exampleofthe disclosure.
`
`
`
`[0049] Block 300 represents the secure operating environ-
`ment of the NF'Cunit 218 and block 301 represents the oper-
`aling environment of the main processor 200 and program
`memory 216. Block 300 showsaplurality ofNFC application
`elements 302-312, and an operating system 314 of the NFC
`unit 218. In a UICC implementation, the NFC application
`elements 302-312 are stored in the memory 402 (shown in
`FIG. 4) and called by the processor 400. The operating system
`314 maybestored in the memory 402 or memory that is part
`ofthe processor 400 or a separate memory. The dotted boxes
`around the NFC application elements 302-312 represent that
`the NFC application elements 302-312 are stand alone appli-
`cations operating in isolation from other application ele-
`ments. For instance, the operating system 314 may be based
`on the JavaCard specifications and may also implement the
`global platform standards that both define the process of
`isolation of the applications. It will however be appreciated
`that someorall ofthe NFC application elementsstored in the
`NFC unit 218 maybe designed to have someinteroperability.
`Forillustration purposes, the NFC application element 302 is
`associated with a first payment service (e.g. PayPass™ from
`MasterCard®), the NFC application clement 304 is associ-
`ated with a first transport service (e.g. train ticket), the NFC
`application element 306 is associated with a second payment
`service (e.g. VSDC™from Visa®), the NFC application ele-
`ment 308 is associated with a first loyalty card (e.g. card to
`collect points fora particular book shop), the NFC application
`element 310 is associated witha secondloyaltycard (e.g. card
`to collect points for a particularairline), and the NFC appli-
`cation element 312 is associated with a second transport
`service (e.g. airline ticket). It is noted that an NFC service
`may have more than one NFC application clement associated
`with it. For example, the NFC paymentservice from Master-
`card® comprises two application elements: one is a Proxim-
`ity Payment System Environment (PPSE)and the second one
`is the PayPass™application. The PPSE application is used to
`retrieve the reference of the PayPass™applicationsif several
`have beeninstalled.
`
`In order to manage the NFC ap