US 20100190437A1
`
`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2010/0190437 A1
`
` Buhot (43,) Pub. Date: Jul. 29, 2010
`
`
`(54) WIRELESS COMMUNICATION DEVICE FOR
`
`(52) US. C1. ....................................................... 455/41.1
`
`PROVIDING AT LEAST ONE NEAR FIELD
`CONIMUNICATION SERVICE
`
`(75)
`
`Inventor:
`
`Thomas Buhot, Toulouse (FR)
`
`Correspondence Address:
`MOTOROLA INC
`600 NORTH US HIGHWAY 45, W4 - 39Q
`LIBERTYVILLE, IL 60048-5343 (US)
`
`(73
`
`Assignee:
`
`MOTOROLA, INC.. Schaumburg,
`IL (US)
`
`(21
`
`(22
`
`(30,
`
`(51‘
`
`
`
`ABSTRACT
`(57)
`A Wireless communication device (102) is arranged to pro-
`vide at least one Near Field Communication service to a user.
`The Wireless communication device (102) comprises a Near
`:ield 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
`\Iear Field Communication managing elements (318-328).
`Each of the plurality ofNear Field Communication managing
`elements (318-328) is associated With at least one of the
`alurality of application elements (3 02 -3 12) stored in the Near
`:ield Communication unit (218) for managing the at least one
`associated application element of the plurality of application
`elements. A user interface element (224) interfaces with at
`east some of the Near Field Communication managing ele-
`ments (318-328) and provides information to a user relating
`o the Near Field Communication services provided by the
`filurality 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
`arranged to activate the Near Field Communication managing
`element of the selected Near Field Communication service to
`manage the at least one associated application element.
`
`E
`
`M
`
`App]. No.:
`
`12/646,251
`
`Filed:
`
`Dec. 23., 2009
`
`Foreign Application Priority Data
`
`an. 26, 2009
`
`(EP) ................................ EP09290052
`
`Publication Classification
`
`Int. Cl.
`H04B 5/00
`
`(2006.01)
`
`108
`
`110
`
`102
`
`100
`
`Apple Ex. 1005, p. 1
`Apple Ex. 1005, p. 1
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 1 0f 9
`
`US 2010/0190437 A1
`
`E
`
`M
`
`108
`
`110
`
`102
`
`106
`
`100
`
`FIG. 1
`
`Apple Ex. 1005, p. 2
`Apple Ex. 1005, p. 2
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

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

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 3 0f9
`
`US 2010/0190437 A1
`
`
`
`
`
`
`
`
`
`Sm.
`
`omm
`
`mmm
`
`vmm
`
`mmm
`
`mwm
`
`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 0f 9
`
`US 2010/0190437 A1
`
`218
`
`500
`331
`
`
`NFC MANAGING
`REGISTRATION
`
`ELEMENT
`ELEMENT
`
`
`
`
`
`GETINSTANCE
`
`
`
`
`
`504
`
`508
`
`. REGISTRATIONINSTANCE a
`
`ADD MANAGING ELEMENT
`
`
`
`
`REGISTER A NEW NFC
`MANAGING ELEMENT
`
`FIG. 5
`
`Apple Ex. 1005, p. 5
`Apple Ex. 1005, p. 5
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`9
`
`wm0m
`
`1A
`
`v665%
`
`MbUNK
`b.UNK
`
`
`
`
`
`on_zzO_._.<m_._.w_0m_m_on_zzo_._.<m_._.w_om_m_zo_._.<~_._.m_0m_m_mo<n_m_m_._.z_mum:
`
`
`
`
`
`
`
`
`
`
`
`m._.Zm__2m_._m_Oz_o<z<_>_<._.2m__>_m_._m_oz_0<z<_2._.2m__>_m_._m_mz_wzmmum:
`
`
`
`
`
`
`
`mmatmoX8m5:E5m8mg5:mgm,fitmex
`
`m.BEEBM2Efizmzflmhoz_w<z<_>_82ME5:
`
`VS
`
`
`
`
`
`
`
`
`
`7Imv6GEN
`
`Apple Ex. 1005, p. 6
`Apple Ex. 1005, p. 6
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`
`
`Ou_z_mom<o0%MEmo
`
`
`
`Emsmdmofimflz
`
`Em:ME55%
`
`
`
`

`

`Patent Application Publication
`
`Jul. 29, 2010 Sheet 6 0f9
`
`US 2010/0190437 A1
`
`28_920I?glags“.
`Ill'i
`
`28_ES
`
`m_
`
`m__>_<z920
`
`IIII
`
`202om<o._.m_®
`$22920._.m_w
`
`Em
`
`
`
`
`
`On_z_mom/3m=._._.1.23
`
`
`
`._.w_._920m__._._.m.._.<n_n_:
`
`Sm
`
`
`
`On_z_may—<0
`
`m3.UNR on_z_
`
`mom<o
`
`m__._._.><._n_w_n_
`
`
`
`
`
`
`
`
`
`._.m_._om<om__._._.35m
`
`mom
`
`
`
`
`
`(a
`
`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 0f 9
`
`US 2010/0190437 A1
`
`
`
`oz_0<z<_>_on_z
`
`<._.2m__>_m_._m_
`
`
`
`wwmoOmEmz<Dm<o._.om_._m_m
`
`><._n_m_n_ on_z_waxed
`
`
`
`1mm:<._.2m__>_m_._m_oz_o<z<_>_on_z
`mo<u_m_m_._.z_
`zO_._.<s_m_On_z_920m._.:.._.m_o
`
`
`zo_._.<w_._.m_om_mmo<n_~_m_._.z_mum:
`
`._.2m__>_m_._m_m_z_02m_
`ES:
`
`zo_._.o<wz<m_._.Gz_mmm_oomn_
`
`Hm/fimmou—om<o<._.om_._m_w
`
`zO_._.<_>_m_On_z_om<o
`
`._.2m__>_m_._m_mo<n_~_m_._.z_
`
`
`mum:m__._._.._.om_._m_m
`
`m__._.rEm
`
`on—z_mom/a
`
`Apple Ex. 1005, p. 8
`Apple Ex. 1005, p. 8
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`8
`
`SU
`
`mm.
`
`MW.
`
`4ImEEm
`
`Azo_._.<N_._<_._._z_
`
`
`
`n5._.m_mzO_._.o<wz<m._.
`
`mm<>>._.n_owoz<mm<>>om<Ivck
`
`
`zo_._.o<wz<m._.”m=._._.“—0GEm__._._.“5Mum:
`
`
`0m=._._.wz__>_mon_z_mw<mmm=2
`
`4.,Enmzo_._.o<wz<m_._.
`
`S“—002mmgH,emu
`
`
`m__._._.wz_._._>z_mw<wwm=2m_><>>O._.J1mm:2._<z__2w_m_._.m__._._.“5fl._.ZOm_u_z_m_I__mO_>_m_I
`
`
`
`
`zO_._.o<mz<m._.
`
`Em
`
`._.m_<._.mgaNR
`
`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 0f 9
`
`US 2010/0190437 A1
`
`800
`
`PROVIDING TO A USER INFORMATION
`RELATING TO AVAILABLE NFC SERVICES
`
`MANAGE THE APPLICATION ELEMENT
`
`SELECTING BY A USER A NFC SERVICE
`BASED ON PROVIDED INFORMATION
`
`ACTIVATING THE NFC MANAGING ELEMENT
`OF THE SELECTED NFC SERVICE TO
`
`FIG. 8
`
`Apple Ex. 1005, p. 10
`Apple Ex. 1005, p. 10
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0190437 A1
`
`Jul. 29, 2010
`
`\VIREIESS COlVIMUNICATION DEVICE FOR
`PROVIDING AT LEAST ONE NEAR FIEID
`COMDIUNICATION SERVICE
`
`FIELD OF THE DISCLOSUR: LU
`
`[0001] This disclosure relates to a wireless communication
`device for providing at least one Near Field Communication
`service to a user and a met iod of providing a Near Field
`Communication serviceby a wireless communication device.
`
`
`
`BACKGROUND OF THE DISCLOSURE
`
`Identity services, for example, the mobile phone
`[0015]
`acts as an identity card or key.
`[001 6] A mobile phone that 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 element may be a dedicated
`module or chipset that is part of the mobile phone or may be
`a removable component, such as the UMTS Integrated Circuit
`Card (UICC) also known as the SIM card or USIM card or a
`removable memory card.
`[0017] When for example the mobile phone is in the card
`emulation mode and acts like 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 ISOl4443—4
`standard). This may involve retrieving cardholder banking
`information from the selected NFC application element(s).
`[0018] As discussed above. different types ofNFC services
`may be available and thus, 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 PayPassTM
`NFC application element from MasterCard®, Visa Smart
`Debit CreditT“ (VSDC) NFC application element from
`
`Visa® or ExpressPayTM NFC application element from
`American Expres s®. 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
`(which is generally a global platform or JavaCard based) and
`are protected by a firewall of the runtime environment in the
`secure element (as defined, for example, by the JavaCard
`runtime environment or the global platform specification).
`This is because these payment application elements typically
`correspond to the reference contactless application elements
`developed and already deployed for contactless smartcards,
`where only one single contactless application element runs on
`a contactless smartcard and thus, 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 same type, for use in a mobile phone can
`raise a number ofissues 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, when a 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 number of available NFC services
`increase; and the number of application element providers
`increase.
`
`In order to take account of specific issues that arise
`[0020]
`when providing NFC services in a mobile phone. an approach
`would be to modify the reference contactless application
`elements for NFC applications to allow, for example, interop—
`
`Apple Ex. 1005, p. 11
`Apple Ex. 1005, p. 11
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`[0002] Near Field Communication (NFC) is a short-range
`wireless communication technology which enables the
`exchange of data between devices allowing users of NFC
`enabled devices to use NFC services such as perfonning
`contactless transactions, accessing digital content and con-
`necting devices with a single touch.
`[0003] NFC is based on contactless and Radio Frequency
`Identification @FID) solutions, which typically consist of a
`tag or device storing a small amount of data and a reader. The
`reader, when activated, 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 that it 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 performed into the Lise of
`NFC in mobile phones. The current main use cases for NFC
`in a mobile phone include:
`[0005] Card emulationithe NFC enabled device can
`behave like an existing contactless NFC card;
`[0006]
`leader mode: the NFC enabled device can read a
`passive NFC tag, for example for interactive advertising;
`[0007]
`‘eer-to-Peer (P2P) mode: two NFC enabled devices
`can communicate together and exchanging infonnation eg.
`to set up a Bluetooth connection.
`[0008] Examples ofthe different types ofNFC services that
`may be 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 of the existing contactless
`infrastructure, and electronic ticketing such as for airline
`tickets. concert/event tickets;
`[0010]
`Payment services where for example the mobile
`phone acts as a debit/credit payment card or possibly elec-
`tronic money;
`[0011] Advertising services where for example the mobile
`phone is 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 conmlunication link;
`[0014] Loyalty services, for example,
`acts as a loyalty card; and
`
`
`
`
`
`the mobile phone
`
`

`

`US 2010/0190437 A1
`
`Jul. 29, 2010
`
`erability or interfacing with other elements orOTA provision-
`ing. However, this would require for the application clement
`providers to modify their reference application elements to
`support these services on NFC devices which will involve
`extra cost, new code baseline, new deployment and new cer-
`tification processes.
`[0021]
`Some mobile phones include NFC managing appli-
`cations which may run on an application processor of the
`mobile device and which activate NFC application elements
`and handle the NFC services, for example, for mobile pay—
`ment, ticketing, transport, access etc. These NFC managing
`applications can be native applications or Java applications.
`Each NFC managing application may manage several appli-
`cation elements from the same application provider at the
`same time. For example. a payment NFC managing applica-
`tion may support several payment card application elements
`and a ticketing NFC managing application may support dif—
`ferent ticketing card application elements. These NFC man—
`aging applications enable a user to select a card (i.e. a card
`application element) among a list associated with the NFC
`application to pay, get on the bus, access a building, etc. A
`NFC managing application can handle card application ele-
`ments of different types such as payment, ticketing or trans-
`port card applications from the same application provider.
`[0022] As the number of NFC services and the number of
`application providers increases, in order to support several
`NFC managing applications from different application pro-
`viders at the same time, many NFC managing applications,
`such as payment, ticketing, or access, are installed and may be
`running simultaneously on the NFC mobile phone. Since
`there is currently no interoperability between these different
`NFC managing applications and the different application pro-
`viders, information calmot 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 bankA and vice versa, This means that
`from a user’s point of view there may be several NFC inan-
`aging applications from different application providers to
`access the same set ofNFC services which makes accessing
`the NFC services more complicated and less user friendly.
`For example, it may not be possible for the user to list, access,
`and manage all 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 order to use a given card application
`element for payment, transport, access, etc., the user has to
`remember with which NFC managing application the card
`application element is associated. In addition, the application
`element list information presented to the user on the mobile
`phone’s user interface to select a card application element
`from the different NFC managing applications is not stan-
`dardized and will differ from one NFC managing application
`to another depending on the application provider’s specifica-
`tion.
`
`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
`
`disclosure will now be described, by way of example only,
`with reference to the accompanying drawings in which:
`[0024]
`FIG. 1 is a block schematic diagram of a communi-
`cation system arrangement in accordance with an embodi-
`ment of the disclosure;
`[0025]
`FIG. 2 is a block schematic diagram of a wireless
`communication device in accordance with an embodiment of
`the disclosure;
`[0026]
`FIG. 3 is a schematic representation of example
`NFC application elements held in the NFC unit of FIG. 2 and
`example user interface elements of FIG. 2 in accordance with
`an embodiment of the disclosure;
`[0027]
`FIG. 4 is a block schematic diagram of an example
`UICC card implementation of the NFC unit of the wireless
`communication device of FIG. 2;
`[0028]
`FIG. 5 is a simplified schematic diagram represent—
`ing an example flow ofinteractions between the user interface
`element and a NFC managing element when registering the
`NFC managing element in accordance with an embodiment
`of the disclosure;
`[0029]
`FIG. 6 is a simplified schematic diagram represent-
`ing an example flow ofinteractions between the user interface
`element and two NFC managing elements when gathering
`NFC service information in accordance with an embodiment
`of the disclosure;
`[0030]
`FIG. 7 is a simplified schematic diagram represent-
`ing an example flow ofinteractions between the user interface
`element and a NFC managing element during user selection
`of a NFC service in accordance with an embodiment of the
`disclosure; and
`[0031]
`FIG. 8 is a flow diagram of a method for providing a
`NFC service by a Wireless communication device in accor-
`dance with an embodiment of the disclosure.
`
`
`
`DETAILED DESCRIPTION OF TI IE 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 OJMTS), or Long Term Evolution (LTE) communication
`system. It will however be appreciated the present disclosure
`can be used in 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 personal digital assistant
`(PDA), a laptop computer, or any electronic device having
`wireless capability, such as a digital camera which can trans—
`fer pictures wirelcssly. The term wireless communication
`device for providing at least one NFC service is 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 1 00 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 and it is not intended to limit the disclosure to
`
`Apple Ex. 1005, p. 12
`Apple Ex. 1005, p. 12
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0190437 A1
`
`Jul. 29, 2010
`
`DJ
`
`a GSM communication system. As is well known, the GSM
`communication system 104 provides a plurality of coverage
`areas or cells (not shown) served by base stations (not shown)
`with which the mobile device 102 can operate or communi-
`cate via radio communication links (such as link 1 08 shown in
`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 NFC tag or may be a reader device such as 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 1 06
`to exchange data so that the mobile device 102 may enter a
`card emulation mode in which it 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 Bluetooth 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 may act as a reader/writer or
`a tag.
`FIG. 2 is a block diagram of a wireless communica—
`[0037]
`tion device, such as the mobile device 102 shown in FIG. 1, in
`accordance with an embodiment ofthe disclosure, As will be
`apparent to a skilled person, FIG. 2 shows only the main
`ftmctional 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 RF communi-
`cation section 202 for providing wireless communication via
`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 communication link 110.
`The mobile device may, for example, establish a NFC com—
`munication link with a reader having NFC capability via the
`NFC communication section 204 when the mobile device 1 02
`is within a couple of centimetres of the reader. The RF com-
`munication section 202 typically includes, for example. an
`antenna 206,
`transmit and receive paths 208 including a
`modulation/demodulation section (not shown), and a coding/
`decoding section (not shown), as will be known to 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 known to 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 MM] 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 214 is 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
`arocessing required for the operation of the mobile device
`102. The number ofprocessors 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
`orogram memory 216 in which is stored programs containing
`orocessor instructions for operation ofthe mobile device 102.
`The programs may contain a number of 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 coni-
`munication system 104.
`[0041] The mobile device 102 further comprises a NFC unit
`218 which can act as a secure element to store at least one
`\IFC application element for use in providing at least one
`\IFC service. The NFC unit 218 may store only one NFC
`application element but typically, the NFC unit 218 will store
`a plurality of NFC application elements associated with a
`alurality of NFC services, with some ofthe services being of
`he same type. For example, the NFC unit 218 may store
`several contactless payment application elements from dif-
`erent service providers such as MasterCard®. Visa®, and
`
`American Express® The NFC unit 218 is coupled to the
`orocessing unit 200 andmay 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 Whose sole function is for providing NFC ser-
`vices or may be a module that has other functions additional
`to providing NFC services.
`[0042] When the NFC unit 218 includes a removable mod-
`ule (represented by the 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 Subscriber Identity
`Module (SIM) card or a Universal Integrated Circuit Card
`(UICC) which, in addition to storing network specific infor-
`mation used 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 SIM or UICC interface. The
`JICC card is the name of the standardised platform that can
`run several telecom applications such as the USIM applica-
`ion for a 3G network, or the SIM application for a 20 net-
`work, or others. The UICC card was introduced with the
`release 99 of the 3GPP standards, and replaces the SIM plat-
`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 phone for the
`support of the telecom applications such as USIM, SIM, and
`SIM.
`
`
`
`[0043] Communication between the NFC unit 218 and the
`wrocessing unit 200 may occur via a direct connection
`hrough a serial link, such as an ISO link between the UICC
`interface 222 and the processing tuiit 200, or via the NFC
`modulator/demodulator 212 that acts as a proxy.
`[0044] When NFC 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) of the
`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
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0190437 A1
`
`Jul. 29, 2010
`
`coupled to the processing unit 200, for example Via a ISO link
`or any other suitable connection (such as USB, I2C). The
`dedicated module may comprise, for example, an Integrated
`Circuit (ICC) which is substantially the same as the IC used for
`contactless smartcard devices.
`
`[0045] The NFC unit 218 may alternatively 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 shows a simplified schematic diagram of an
`example of a UICC implementation of a NFC unit 218 in
`accordance with an embodiment of the disclosure. The UICC
`NFC unit 218 comprises the UICC interface 222 for coupling
`to the processing unit 200, the UICC card 220 when coupled
`to the mobile device 102 and an interface 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 of data accord-
`
`
`
`ing to a protocol standardised by 4 ISI (4 ISI 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 elements for controlling
`the operation of the mobile device 102 by means of he
`processing unit 200 which include a user interface element
`224, and a plurality of N FC managing elements (represen ed
`
`as group by 226 in FIG. 2). Each of the plurality of NjC
`managing elements is associated with at least one of he
`plurality of application elements stored in the NFC unit 218
`for managing the at least one associated application element
`of the plurality of application elements. The user interface
`elemen 224 is for interfacing with at least some of the N :C
`managing elements, and for providing information to a user
`relating to the NFC services provided by the plurality of
`applica ion elements associated with the at least some of he
`NFC managing elements. In operation, the user interface
`elemen 224 in response to user selection of a NFC service
`based on the user provided information is further arrangec to
`activate the NFC managing element of the selected NIC
`service to manage the at least one associated application
`
`elemen . Each of the plurality of NFC managing elements is
`arranged to manage the at least one associated application
`elemen so as to control the at least one associated application
`elemen to provide a NFC service or to update a NFC service.
`A NFC service may be updated by adding a new application
`elemen 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
`may have its 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 may be 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 which illustrates 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 example of the disclosure.
`
`
`
`
`
`[0049] Block 300 represents the secure operating environ-
`ment of the NFC unit 218 and block 301 represents the oper-
`ating environment of the main processor 200 and program
`memory 216. Block 300 shows aplurality 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 may be stored in the memory 402 or memory that is part
`ofthe processor 400 or a separate memory. The dotted boxes
`arotmd 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 .IavaCard 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 some or all ofthe NFC application elements stored in the
`NFC unit 2l8 may be designed to have some interoperability.
`For illustration purposes, the NFC application element 302 is
`associated with a first payment service (e.g. PayPassTM from
`MasterCard®), the NFC application element 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. VSDCTM from Visa®), the NFC application ele-
`ment 308 is associated with a first loyalty card (e.g. card to
`collect points for a particular book shop), the NFC application
`element 3 1 0 is associated with a second loyalty card (e.g. card
`to collect points for a particular airline), 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