(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2013/0339166A1
`(43) Pub. Date:
`Dec. 19, 2013
`Baer et al.
`
`US 2013 0339166A1
`
`(54)
`
`USER-CONFIGURABLE ACTIVATION OF
`CARD APPLETS
`
`(75)
`
`Inventors: Matthias Baer, Seattle, WA (US);
`Michael Connolly, Seattle, WA (US);
`Alejandro Steckler, Bellevue, WA (US);
`Sogol Malekzadeh, Sammamish, WA
`(US); Tirthankar Sengupta, Redmond,
`WA (US)
`
`(73)
`
`Assignee: MICROSOFT CORPORATION,
`Redmond, WA (US)
`
`(21)
`
`Appl. No.: 13/526,536
`
`(22)
`
`Filed:
`
`Jun. 19, 2012
`
`Publication Classification
`
`(2012.01)
`
`(51) Int. Cl.
`G06Q 30/06
`(52) U.S. Cl.
`USPC ............................................ 705/16; 705/26.1
`ABSTRACT
`(57)
`Card applets associated with an electronic wallet are activated
`and deactivated based on user-defined rules. Based on the
`rules and a device state, a card emulation State and card applet
`states are modified to enable or disable completion of trans
`actions. The transactions are between a computing device and
`a reader Such as a point-of-sale terminal. In some embodi
`ments, a user designates a plurality of the card applets as fast
`cards capable of completing a transaction via near-field com
`munication (NFC) interaction without user input at a time of
`the transaction.
`
`
`
`
`
`
`
`
`
`
`
`
`
`APPLICATION
`SERVICES
`
`SERVICE PROVIDER
`TRUSTED SERVICE
`MANAGER (TSM)
`
`PRIMARY DEVICE
`TSM
`
`1 10
`NFC PLATFORM
`MOBILE NETWORK
`OPERATORPLUG-IN
`
`ELEMENT
`
`
`
`
`
`OVER-THE-AIR (OTA)
`APPLET INSTALLATION
`
`
`
`APPL-1013
`APPLE INC. / Page 1 of 14
`
`

`

`Patent Application Publication
`
`Dec. 19, 2013 Sheet 1 of 6
`
`US 2013/0339166 A1
`
`I 15D/-/
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`APPL-1013
`APPLE INC. / Page 2 of 14
`
`

`

`Patent Application Publication
`
`Dec. 19, 2013 Sheet 2 of 6
`
`US 2013/0339166 A1
`
`102
`
`COMPUTING DEVICE
`
`PROCESSOR
`
`204
`
`MEMORY AREA
`
`APPLICATION(S)
`
`104
`
`ELECTRONICWALLET
`
`CARD
`APPLET#1
`
`CARD
`APPLET#N
`
`CARD
`APPLET
`#1 STATE
`
`CARD
`APPLET
`iN STATE
`
`210
`
`CARD
`EMULATION
`STATE
`
`USER-DEFINED
`RULES
`
`INTERFACE COMPONENT
`
`CONTEXT COMPONENT
`
`DRIVER COMPONENT
`
`TRANSACTION PREPARATION
`COMPONENT
`
`216
`
`218
`
`- 220
`
`222
`
`READER(S)
`(e.g., POINT-OF
`SALE TERMINAL)
`
`
`
`224
`
`AIG, 2
`
`APPL-1013
`APPLE INC. / Page 3 of 14
`
`

`

`Patent Application Publication
`
`Dec. 19, 2013 Sheet 3 of 6
`
`US 2013/0339166 A1
`
`
`
`DETERMINEDEVICE STATE
`
`
`
`2
`
`USER-DEFINEDRULES
`
`ADJUST CARDEMULATION STATE
`BASED ON THE DEVICE STATE
`
`
`
`
`
`USER-DEFINEDRULES
`
`2
`
`ADJUST EACH CARD APPLET STATE BASED
`ON CARDEMULATION STATE AND USER
`DEFINED RULES FOREACH CARD APPLET
`TOENABLE OR DISABLE CARD APPLETS
`
`
`
`
`
`DETECT
`POINT-OF-SALE
`TERMINAL
`
`310
`
`PRESENT ENABLED CARD APPLETS
`TO POINT-OF-SALE TERMINAL
`
`AIG 3
`
`APPL-1013
`APPLE INC. / Page 4 of 14
`
`

`

`Patent Application Publication
`
`Dec. 19, 2013 Sheet 4 of 6
`
`US 2013/0339166 A1
`
`
`
`SETIS
`
`|-402
`-40
`
`isie: passwo
`Or
`
`
`
`ise the waitet password for potected
`app purchase
`naketoace
`
`charge password
`
`
`
`To make a NFC transaction with your Phone
`hoid it against the eader and wait for a
`contination essage
`
`
`
`only winer - aliei is oper
`
`when phone is siniacket
`
`any time is thor's screer is or
`
`&ws when the phase is powered dow
`
`88 siste 88 y Otis is set
`
`AIG. 4
`
`APPL-1013
`APPLE INC. / Page 5 of 14
`
`

`

`Patent Application Publication
`
`Dec. 19, 2013 Sheet 5 of 6
`
`US 2013/0339166 A1
`
`
`
`
`
`fast (&stis & S8i x 8 (six 8wer w8s &
`$$38 is Yi
`
`d
`
`is a Naza
`
`x 3-i-
`
`S
`
`sefise $xy 888
`Example Company
`is Egis's
`NC 88te
`Example Airline
`By triage
`- 8s 3.
`Example Bank Card
`S3500 awaiiate balance
`issi cai, R388.888 is cass3
`Example Telco
`$8.8 operatof
`Raketace Echases
`(F) fy
`At
`
`--------------------------
`
`S.
`
`sis :
`
`AIG, .5
`
`APPL-1013
`APPLE INC. / Page 6 of 14
`
`

`

`Patent Application Publication
`
`Dec. 19, 2013 Sheet 6 of 6
`
`US 2013/0339166 A1
`
`§ § 3. §§§ §§ §§
`
`
`
`
`
`
`
`
`
`
`
`
`
`§§§§ §§§§
`
`erduoxe
`
`APPL-1013
`APPLE INC. / Page 7 of 14
`
`

`

`US 2013/0339166 A1
`
`Dec. 19, 2013
`
`USER-CONFIGURABLE ACTIVATION OF
`CARD APPLETS
`
`BACKGROUND
`0001 Short-range wireless communication protocols
`enable a computing device to communicate with readers
`proximate to the computing device. For example, radio fre
`quency identification (RFID). BLUETOOTH brand commu
`nications, Wi-Fi, and near-field communication (NFC) tech
`nology enable a user to perform actions with the computing
`device Such as completing a financial transaction, gaining
`access to a building, and gaining entry to a transit System.
`Existing systems have an electronic wallet that stores a plu
`rality of cards. In some of the existing systems, however, the
`user is limited to manually selecting and activating one of the
`cards to complete a transaction. In some of the existing sys
`tems where each of the cards remains activated at all times,
`the reader, rather than the user, chooses among the activated
`cards to complete a transaction.
`
`SUMMARY
`0002 Embodiments of the disclosure selectively activate
`card applets on a computing device for completing point-of
`sale transactions. A device state for a computing device is
`determined. The computing device has an electronic wallet
`having a plurality of card applets stored therein. Each of the
`card applets has a card applet state. A card emulation state is
`adjusted based on the determined device state. A plurality of
`user-defined rules for each of the plurality of card applets is
`accessed. The card applet states are adjusted based on the
`adjusted card emulation state and the accessed plurality of
`user-defined rules to enable or disable point-of-sale transac
`tions via the plurality of card applets.
`0003. This Summary is provided to introduce a selection
`of concepts in a simplified form that are further described
`below in the Detailed Description. This Summary is not
`intended to identify key features or essential features of the
`claimed Subject matter, nor is it intended to be used as an aid
`in determining the scope of the claimed Subject matter.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0004 FIG. 1 is an exemplary block diagram illustrating an
`architecture for installing card applets on a secure element in
`a computing device.
`0005 FIG. 2 is an exemplary block diagram illustrating a
`computing device storing a plurality of card applets.
`0006 FIG.3 is an exemplary flow chart illustrating opera
`tion of the computing device to enable or disable card applets
`based on card applet States and a card emulation state.
`0007 FIG. 4 is an exemplary diagram illustrating a user
`interface element for configuring settings associated with an
`electronic wallet.
`0008 FIG. 5 is an exemplary diagram illustrating a user
`interface element displaying a set of fast cards selected and
`configured by a user.
`0009 FIG. 6A is an exemplary diagram illustrating a user
`interface element for selecting a manually-activated card for
`a transaction.
`0010 FIG. 6B is an exemplary diagram illustrating a user
`interface element for completing a transaction using a
`selected manually-activated card.
`0011 Corresponding reference characters indicate corre
`sponding parts throughout the drawings.
`
`DETAILED DESCRIPTION
`0012 Referring to the figures, embodiments of the disclo
`sure selectively enable or disable card applets 208 based at
`least on user-defined rules 214 that operate, in some embodi
`ments, responsive to user actions. A card emulation state 212
`and card applet states 210 associated with the card applets 208
`are adjusted or modified based on device state and the user
`defined rules 214. In some embodiments, a user 202 chooses
`which card applets 208 in an electronic wallet 207 are to be
`activated manually to complete a transaction (e.g., manually
`activated cards), and which card applets 208 remain active to
`complete a transaction without user 202 input at a time of the
`transaction (e.g., fast cards). For each of the fast cards, the
`user 202 may further configure the availability, conditions, or
`criteria for activating the fast card, as well as enabling card
`emulation. The manually-activated cards may also be referred
`to as “slow cards' or “one-time-use cards. In some embodi
`ments, the manually-activated cards are used to complete
`only one transaction after being activated. To use one of the
`manually-activated cards again, the user 202 re-activates the
`manually-activated card.
`0013 While some embodiments are described herein with
`reference to interactions via near-field communication
`(NFC), aspects of the disclosure are operable with any wire
`less communication protocol including, for example, the
`BLUETOOTH brand wireless communications protocol.
`Further, while some embodiments are described herein with
`reference to interactions between a computing device 102 and
`a point-of-sale terminal, aspects of the disclosure are operable
`with interactions between the computing device 102 and any
`reader 224, or other computing device. Still further, while
`some embodiments are described herein with reference to
`point-of-sale transactions between the computing device 102
`and the reader 224. Such as those relating to the acquisition of
`goods and/or services, aspects of the disclosure are operable
`with any transactions. For example, the transactions may
`include transactions not associated with goods and/or ser
`vices, such as providing user 202 identification, location
`information, contact information, and the like.
`0014 Referring next to FIG. 1, an exemplary block dia
`gram illustrates an architecture for installing card applets 208
`on a secure element 114 in the computing device 102. The
`computing device 102 illustrated in FIG. 1 includes one or
`more applications 104, a wallet core 106 (e.g., logic for
`implementing the electronic wallet 207), an NFC platform
`108 for implementing NFC interactions, and an underlying
`operating system (OS) platform 112. The computing device
`102 also includes the secure element 114, chip, or other
`hardware component on the computing device 102 for Stor
`ing, among other items, one or more card applets 208. The
`secure element 114 is accessible to the OS platform 112 and
`to one or more of the readers 224 that are in proximity of the
`computing device 102. The secure element 114 may be stored
`in various places on the computing device 102. Such as on a
`motherboard or a universal integrated circuit card (UICC)
`(e.g., or other removable storage card). The secure element
`114 cryptographically protects the information stored thereon
`(e.g., the card applets 208).
`0015 The applications 104 on the computing device 102
`communicate with application services 116. Communication
`between the computing device 102 and the application ser
`vices 116 (or other services or devices) may occur via one or
`more networks using any protocol or mechanism over any
`wired or wireless connection. Each of the application services
`
`APPL-1013
`APPLE INC. / Page 8 of 14
`
`

`

`US 2013/0339166 A1
`
`Dec. 19, 2013
`
`116 communicates with a service provider trusted service
`manager (TSM) 118. The service provider TSM 118 commu
`nicates with a primary device TSM120. The primary device
`TSM 120 communicates state and/or status with a mobile
`network operator (MNO) plug-in 110 or other component
`that is associated with the NFC platform 108 on the comput
`ing device 102. The MNO plug-in 110 communicates with the
`secure element 114 to install card applets 208 received from
`the primary device TSM120. For example, the card applets
`208 are installed via over-the-air (OTA) installation.
`0016 Referring next to FIG. 2, an exemplary block dia
`gram illustrates the computing device 102 storing a plurality
`of the card applets 208. In the example of FIG. 2, the com
`puting device 102 represents a system for selectively activat
`ing one or more card applets 208 on the computing device 102
`for completing any quantity of point-of-sale transactions with
`one or more of the readers 224 (e.g., point-of-sale terminals).
`The computing device 102 represents any device executing
`instructions (e.g., as application programs, operating System
`functionality, or both) to implement the operations and func
`tionality associated with the computing device 102. The com
`puting device 102 may include a mobile computing device or
`any other portable device. In some embodiments, the mobile
`computing device includes a mobile telephone, laptop, tablet,
`computing pad, netbook, gaming device, and/or portable
`media player. The computing device 102 may also include
`less portable devices such as desktop personal computers,
`kiosks, and tabletop devices. Additionally, the computing
`device 102 may represent a group of processing units or other
`computing devices.
`0017. In some embodiments, the computing device 102
`has at least one processor 204, at least one memory area 206,
`and at least one user interface (not shown). The processor 204
`includes any quantity of processing units, and is programmed
`to execute computer-executable instructions for implement
`ing aspects of the disclosure. The instructions may be per
`formed by the processor 204 or by multiple processors
`executing within the computing device 102, or performed by
`a processor external to the computing device 102. In some
`embodiments, the processor 204 is programmed to execute
`instructions such as those illustrated in the figures (e.g., FIG.
`3).
`0018. In some embodiments, the processor 204 represents
`an implementation of analog techniques to perform the opera
`tions described herein. For example, the operations may be
`performed by an analog computing device and/or a digital
`computing device.
`0019. The computing device 102 further has one or more
`computer readable media such as the memory area 206. The
`memory area 206 includes any quantity of media associated
`with or accessible by the computing device 102. The memory
`area 206 may be internal to the computing device 102 (as
`shown in FIG. 2), external to the computing device 102 (not
`shown), or both (not shown). In some embodiments, the
`memory area 206 includes read-only memory and/or memory
`wired into an analog computing device.
`0020. The memory area 206 stores, among other data, one
`or more applications 104. The applications 104, when
`executed by the processor 204, operate to perform function
`ality on the computing device 102. Exemplary applications
`104 include mail application programs, web browsers, calen
`dar application programs, address book application pro
`grams, messaging programs, media applications, location
`based services, search programs, and the like. The
`
`applications 104 may communicate with counterpart appli
`cations or services (e.g., application services 116) Such as
`web services accessible via a network. For example, the
`applications 104 may represent downloaded client-side appli
`cations that correspond to server-side services (e.g., applica
`tion services 116) executing in a cloud.
`0021. The memory area 206 further stores the electronic
`wallet 207 having a plurality of card applets 208 stored
`therein, such as card applet #1 through card appletiiN. Each
`of the card applets 208 is associated with an electronic wallet
`item or card. For example, the card applets 208 may corre
`spond to payment applets (e.g., creditor debit), access applets
`(e.g., for gaining access to a building or other area), loyalty
`applets, transit applets, coupon applets, and gift card applets.
`0022. Each of the plurality of card applets 208 has one of
`the card applet states 210 associated therewith, such as card
`applet state #1 through card applet state iiN. In some embodi
`ments, each card applet 208 maintains its corresponding card
`applet state 210. The card applet states 210 may be read into
`the OS via an application programming interface (API) or
`may be published to the OS by the card applets 208. For
`example, another applet in the secure element 114 may cen
`tralize the card applet states 210 and respond to queries via the
`API or publish the card applet states 210. In some embodi
`ments, each card applet State 210 stores data indicating
`whether the corresponding card applet 208 is active or inac
`tive (e.g., available or unavailable to the reader 224, respec
`tively) and installed or uninstalled.
`0023 The memory area 206 also stores the card emulation
`state 212. The card emulation state 212 affects the availability
`of the electronic wallet 207 for completing transactions. For
`example, the card emulation state 212 may enable or disable
`NFC interactions between the computing device 102 and the
`reader 224, thus acting as a global setting that can enable or
`disable point of sale transactions without changing any of the
`card applet states 210.
`(0024. While the electronic wallet 207, card applets 208,
`card applet states 210, and card emulation state 212 are shown
`as being logically stored in memory area 206. Some of this
`data may be physically stored elsewhere on the computing
`device 102 in some embodiments. For example, the secure
`element 114 (e.g., a module that is outside the memory area
`206) may store the card applets 208 while the memory area
`206 stores the card applet states 210 in the electronic wallet
`207. In such embodiments, the electronic wallet 207 may
`store metadata describing the card applets 208, Such as a
`representation of the card applets 208 as well as a link from
`each of the card applet states 210 in the electronic wallet 207
`to the corresponding card applets 208 physically stored in the
`secure element 114.
`0025. Further, in some embodiments, the card emulation
`state 212 may be physically stored in an NFC driver and/or
`hardware outside, or separate from, the memory area 206.
`0026. The user 202 interacts with the computing device
`102, as described below, to define, provide, or make acces
`sible one or more of the rules 214. For example, the user 202
`may draft the rules 214 or may select or choose among pre
`defined, Suggested, or recommended rules. The user-defined
`rules 214 are stored in the memory area 206, and affect the
`availability of the electronic wallet 207 and the card applets
`208 therein. For example, the user-defined rules 214 may
`separate the card applets 208 into categories. Such as fast
`cards and slow cards (e.g., manually-activated cards). Card
`applets 208 designated as fast cards are capable of completing
`
`APPL-1013
`APPLE INC. / Page 9 of 14
`
`

`

`US 2013/0339166 A1
`
`Dec. 19, 2013
`
`transactions without explicit or manual selection, use, autho
`rization, and/or confirmation input by the user 202. In some
`embodiments, card applets 208 designated as fast cards are
`available to the readers 224 without explicit or manual selec
`tion by the user 202, but the readers 224 may still attempt to
`challenge (e.g., authenticate) the user 202 by, for example,
`asking for a personal identification number (PIN). Further,
`fast cards may remain active after completing a transaction, or
`may be deactivated after completing the transaction (e.g.,
`depending on the user-defined rules 214).
`0027. In contrast, card applets 208 designated as manu
`ally-activated cards are capable of completing transactions
`only with explicit or manual selection, use, authorization,
`and/or confirmation input by the user 202.
`0028. The rules 214 may also identify other criteria for
`enabling or disabling the card applets 208. For example, the
`rules 214 may identify a location for the computing device
`102 at which the card applet 208 is enabled. The rules 214
`may also identify a time of day or durations during which the
`card applet 208 is enabled. For example, the user 202 may
`associate a duration with one of the card applets 208 desig
`nated as a fast card Such that the fast card deactivates after
`expiration of the duration.
`0029. The memory area 206 further stores one or more
`computer-executable components. Exemplary components
`include an interface component 216, a context component
`218, a driver component 220, and a transaction preparation
`component 222. Operation of these components, when
`executed, is described below with reference to FIG. 3.
`0030. In some embodiments, the user interface includes a
`display (e.g., a touchscreen display) and/or computer-execut
`able instructions (e.g., a driver) for operating the display. The
`user interface may also include one or more of the following
`to provide data to the user 202 or receive data from the user
`202: Speakers, a Sound card, a camera, a microphone, a vibra
`tion motor, one or more accelerometers, a BLUETOOTH
`brand communication module, global positioning system
`(GPS) hardware, and a photoreceptive light sensor. For
`example, the user 202 may input commands or manipulate
`data by moving the computing device 102 in a particular way.
`0031
`Referring next to FIG. 3, an exemplary flow chart
`illustrates operation of the computing device 102 to enable or
`disable one or more of the card applets 208 based on the card
`applet states 210 and the card emulation state 212. While the
`operations illustrated in FIG. 3 are described as being
`executed by the computing device 102, aspects of the disclo
`Sure are operable with other entities executing one or more of
`the operations. For example, one or more of the operations
`may be executed by a server remote from the computing
`device 102 yet in communication with the computing device
`102.
`0032. At 302, the computing device 102 determines a
`device state. Determining the device state includes, but is not
`limited to, determining a hardware state and/or a software
`state. Determining the hardware state includes determining,
`for example, whether a display of the computing device 102
`is on or off, and whether the computing device 102 is powered
`on or off. Determining the software state includes determin
`ing a current execution context. The execution context, for
`example, describes one or more of the applications 104 cur
`rently being executed by the computing device 102. As
`another example, the execution context also identifies one or
`more of the following: whether the electronic wallet 207 is
`open or closed, whether the electronic wallet 207 is in a
`
`foreground of the user interface in the computing device 102
`or in the background, and whether the computing device 102
`is locked or unlocked. In some embodiments, the electronic
`wallet 207 and/or the card applets 208 may be locked and/or
`unlocked with a PIN or other security measure.
`0033. At 304, the computing device 102 adjusts or modi
`fies the card emulation state 212 based on the determined
`device state. For example, the computing device 102 may
`adjust the card emulation state 212 to be active or inactive. If
`the card emulation state 212 is set to active, then one or more
`of the card applets 208 may be available for transactions,
`depending on the corresponding card applet States 210. If the
`card emulation state 212 is set to inactive, then none of the
`card applets 208 is available for transactions, regardless of the
`corresponding card applet states 210. For example, modify
`ing the card emulation state 212 includes enabling or dis
`abling NFC interaction between the computing device 102
`and the reader 224.
`0034. In some embodiments, the computing device 102
`accesses a plurality of the user-defined rules 214. For each of
`the plurality of card applets 208, the user-defined rules 214
`represent settings or configurations defining the conditions
`under which the card applets 208 are available or unavailable
`for transactions. For example, the user-defined rules 214 may
`designate one or more of the card applets 208 as fast cards, as
`described above, that are capable of completing point-of-sale
`transactions without explicit user 202 input.
`0035. The card emulation state 212 may also be adjusted
`based on the user-defined rules 214. For example, if the user
`defined rules 214 specify that none of the card applets 208
`should be available when the computing device 102 is pow
`ered off, the computing device 102 adjusts the card emulation
`state 212 to “inactive' when the computing device 102 pow
`ers off, thus disabling each of the card applets 208 (e.g.,
`preventing the card applets 208 from completing transactions
`while the computing device 102 is powered off).
`0036. At 306, the computing device 102 adjusts or modi
`fies the card applet states 210 based on the adjusted card
`emulation state 212 and the user-defined rules 214 to enable
`or disable point-of-sale transactions via the plurality of card
`applets 208. For example, one of the card applet states 210
`may be set to inactive or otherwise disabled, thus making the
`corresponding card applet 208 unavailable for transactions.
`In another example, one of the card applet states 210 may be
`set to active or otherwise enabled, thus making the corre
`sponding card applet 208 available for transactions.
`0037. In general, the card emulation state 212 and/or the
`card applet states 210 are used to control the availability of the
`card applets 208. In some embodiments, the card emulation
`state 212 is adjusted to control when card applets 208 desig
`nated as fast cards are available, while the card applet States
`210 are used to designate which of the card applets 208 are
`fast cards. Other embodiments, however, lack the card emu
`lation state 212. In Such embodiments, the card applet states
`210 are used both to control when the card applets 208 are
`available and to designate which of the card applets 208 are
`fast cards.
`0038. In embodiments in which the user-defined rules 214
`identify some card applets 208 as fast cards and other card
`applets 208 as manually-activated cards, the computing
`device 102 may adjust the card applet states 210 to enable the
`fast cards when the electronic wallet 207 is open. Alterna
`tively or in addition, the computing device 102 may adjust the
`card applet states 210 to enable the fast cards when a display
`
`APPL-1013
`APPLE INC. / Page 10 of 14
`
`

`

`US 2013/0339166 A1
`
`Dec. 19, 2013
`
`of the computing device 102 is on. As another example, the
`computing device 102 may adjust the card applet states 210 to
`disable the fast cards when the computing device 102 is
`locked. In still another example, the computing device 102
`may adjust the card applet states 210 to keep the fast cards
`enabled even when the computing device 102 is powered off
`In Such an example, the fast cards obtain power to complete
`transactions via the mechanism involved in the communica
`tion between the secure element 114 and the reader 224. For
`example, during an NFC interaction, power is derived from an
`electromagnetic field provided by the reader 224.
`0039. Adjusting the card applet states 210 produces a set
`of one or more of the card applets 208 that are available for
`transactions. If a point-of-sale terminal or other reader 224 is
`detected at 308, the computing device 102 presents, or other
`wise makes available, the available set of card applets 208
`(e.g., enabled) at 310 for completing the transaction. Selec
`tion of one of the available card applets 208 may occur
`according to any selection process, as known in the art.
`0040. While examples of the user-defined rules 214 have
`been described herein, aspects of the disclosure are operable
`with any rules that affect the availability of the card applets
`208 for completing transactions.
`0041. In some embodiments, the computer-executable
`components illustrated in FIG. 2 execute to perform one or
`more of the operations illustrated in FIG. 3. For example, the
`interface component 216, when executed by at least one pro
`cessor 204 of the computing device 102, causes the processor
`204 to present to the user 202 the electronic wallet 207 in a
`user interface element and to receive, from the user 202 via
`the user interface element, one or more of the user-defined
`rules 214. The user-defined rules 214 correspond to the elec
`tronic wallet 207 and/or the plurality of card applets 208
`displayed in the electronic wallet 207.
`0042. The context component 218, when executed by at
`least one processor 204 of the computing device 102, causes
`the processor 204 to determine a device state for the comput
`ing device 102. The driver component 220, when executed by
`at least one processor 204 of the computing device 102,
`causes the processor 204 to adjust the card emulation state
`212 based on the device state determined by the context
`component 218. The transaction preparation component 222,
`when executed by at least one processor 204 of the computing
`device 102, causes the processor 204 to adjust the card applet
`states 210 based on the card emulation state 212 adjusted by
`the driver component 220 and the one or more user-defined
`rules 214 received by the interface component 216 to enable
`or disable point-of-sale transactions via the plurality of card
`applets 208.
`0043 Referring next to FIG. 4, an exemplary diagram
`illustrates a user interface element 402 for configuring set
`tings associated with the electronic wallet 207. While the user
`interface element 402 illustrated in FIG. 4 shows a set of
`exemplary configurations on a mobile telephone, aspects of
`the disclosure are operable with any quantity or type of set
`tings or configurations on any mobile device. In the example
`of FIG. 4, the user 202 has provided a password for entry to
`make purchases via an online marketplace. The user 202 has
`also enabled NFC transactions.
`0044. The user interface element 402 further illustrates a
`set of configuration options for selection by the user 202. In
`this example, the configuration options relate to enabling the
`user-selected set of fast cards (1) only when the electronic
`wallet 207 is open, (2) when the mobile telephone is
`
`unlocked, (3) anytime the screen or display of the mobile
`telephone is on, or (4) even when the mobile telephone is
`powered down or off If the user 202 selects option (1), the
`mobile telephone turns on card emulation (e.g., adjust the
`card emulation state 212 to allow any card applet 208 with a
`corresponding card applet state 210 of “active' to complete a
`transaction) when the user 202 opens the electronic wallet
`207. The mobile telephone turns off card emulation (e.g.,
`adjusts the card emulation state 212 to disable each of the card
`applets 208, regardless of the corresponding card applet states
`210) as soon as the user 202 closes the electronic wallet 207
`or switches to another user interface element.
`0045. If the user 202 selects option (2), the mobile tele
`phone turns on card emulation when the user 202 unlocks the
`mobile telephone and turns off card emulation when the user
`202 locks the mobile telephone. If the user 202 selects option
`(3), the mobile telephone turns on card emulation when the
`user 202 turns on the display, even if the mobile telephone is
`locked. The mobile telephone turns off card emulation when
`the user 202 turns off the display. If the user 202 selects option
`(4), the mobile telephone keeps card emulation on even when
`the mobile telephone is turned off. In this option, card emu
`lation may remain on even if a battery is removed from the
`mobile telephone (e.g., depending on whetherhardware asso
`ciated with the mobile telephone uses any power from the
`battery).
`0046. In the example of FIG. 4, the user 202 has selected
`option (1), thus enabling the selected set of fast cards only
`when the electronic wallet 207 is open (e.g., the electronic
`wallet 207 is in the foreground of the display of the mobile
`telephone).
`0047. Additional user-defined rules 214 (not shown) may
`indicate whether the mobile telephone prompts for a pass
`word to open the electronic wallet 207 or unlock the mobile
`telephone.
`0048 Referring next to FIG. 5, an exemplary diagram
`illustrates a user interface element 502 displaying a set of fast
`cards selected and configured by the user 202. In some
`embodiments, the user interface element 502 represents the
`electronic wallet 207. In this example, the user 202 has
`selected four card applets to be “fast cards,” or otherwise
`activated the four card applets as described above. The fast
`cards are shown on the left side of the user interface element
`502, while a list of the available cards is shown on the right
`side of the user interface element 502. The available cards
`include both fast cards (e.g., active) and manually-activated
`cards (e.g., inactive). The user 202 may designate one or more
`of the available cards as fast cards by, for example, selecting
`a menu item or dragging the card to the set of fast cards.
`0049 Referring next to FIG. 6A, an exemplary diagram