(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2012/0123937 A1
`Spodak
`(43) Pub. Date:
`May 17, 2012
`
`US 2012O123937A1
`
`(54) PORTABLE E-WALLET AND UNIVERSAL
`CARD
`
`(76) Inventor:
`
`Douglas Spodak, Bala Cynwyd, PA
`(US)
`
`(21) Appl. No.:
`
`13/359,352
`
`(22) Filed:
`
`Jan. 26, 2012
`
`Related U.S. Application Data
`(63) Continuation-in-part of application No. 13/310,491,
`filed on Dec. 2, 2011, which is a continuation-in-part
`of application No. 12/715,977, filed on Mar. 2, 2010.
`
`Publication Classification
`
`(51) Int. Cl.
`(2012.01)
`G06O 40/00
`(52) U.S. Cl. .......................................................... 705/41
`(57)
`ABSTRACT
`Universal cards are used in place of all the other traditional
`cards which a person may want to carry. The universal card
`can include a short range communications transceiver to com
`municate with a mobile device. The mobile device can
`include a user interface and an e-wallet application so that the
`user can interface with the e-wallet application for program
`ming the universal card via the short range communication
`link. Once programmed, the universal card emulates a func
`tion of a traditional card.
`
`:38:
`8:38 83&: s
`
`38
`8xxx88or
`
`33:
`
`
`
`: ;
`{y::3:::::: 8:::::::::::::::8
`
`3xx888
`
`s
`
`388x38; 3:38:
`
`.xy.
`
`APPL-1008
`APPLE INC. / Page 1 of 36
`
`

`

`Patent Application Publication
`
`May 17, 2012 Sheet 1 of 19
`
`US 2012/O123937 A1
`
`
`
`
`
`
`
`APPL-1008
`APPLE INC. / Page 2 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 2 of 19
`
`US 2012/O123937 A1
`
`
`
`APPL-1008
`APPLE INC. / Page 3 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 3 of 19
`
`US 2012/O123937 A1
`
`
`
`
`
`38:
`
`
`
`
`
`------------------------------------
`
`
`
`
`
`&:38 3:::::::
`8-x8: 833i:8:38
`
`FIGURE 3
`
`APPL-1008
`APPLE INC. / Page 4 of 36
`
`

`

`Patent Application Publication
`
`May 17, 2012 Sheet 4 of 19
`
`US 2012/O123937 A1
`
`
`
`*****
`
`***********
`
`
`
`× ×××××
`
`APPL-1008
`APPLE INC. / Page 5 of 36
`
`

`

`Patent Application Publication
`
`May 17, 2012 Sheet 5 of 19
`
`US 2012/O123937 A1
`
`3..* *
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`? ? ?.
`
`
`******* 33,843
`?ž?
`
`ssisssssssssssssss.
`
`&sssssssssssssss
`
`8
`
`APPL-1008
`APPLE INC. / Page 6 of 36
`
`

`

`Patent Application Publication
`
`May 17, 2012 Sheet 6 of 19
`
`US 2012/O123937 A1
`
`8:888
`
`s
`
`i88 :::::::: 88:
`3:388::::::::::
`
`8.
`
`: 8
`
`---------------------------
`
`8 :x:8:8;
`:::::::::::::::::.
`38:38.388. 8:
`
`:X:::::::::
`
`vs.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`.
`
`
`
`
`
`to to
`
`::::::::: $88:8
`8:8
`
`8:8 ---
`-iroad data-ser
`s'-x & ".
`-
`.
`-
`x: 8
`^: 808 - *:
`
`-:
`
`8.
`
`D
`
`
`
`&
`
`w s
`
`
`
`
`
`a
`
`a.
`
`- 83--.
`-xxxicit- 8
`- .38838:8: *
`-- seriec
`
`s
`
`'s
`
`loto
`
`FIGURE 6
`
`APPL-1008
`APPLE INC. / Page 7 of 36
`
`

`

`Patent Application Publication
`
`May 17, 2012 Sheet 7 of 19
`
`US 2012/O123937 A1
`
`
`
`
`
`::::::::: *{
`8::ixxixx:
`
`8xx xxgir: 38:
`3:88:8:
`
`8. ^vertex *
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`:::::::::::8:k
`:::::::::::::::::::::
`{{Ki: 88xxx xx 8.
`
`
`
`
`
`8.
`
`-
`w
`*...*
`
`-
`
`assassssssssssssssssssssssss
`
`s
`
`FIGURE 7
`
`APPL-1008
`APPLE INC. / Page 8 of 36
`
`

`

`Patent Application Publication May 17,2012 Sheet 8 of 19
`
`US 2012/0123937 Al
`
`B02 Gard oot
`
`OM
`Brand Area
`
`oo,
`
`800 Front of
`Linkversal Card o-—~,
`
`:
`‘
`
`BO5 ae
`
`804 Biometric
`spounly reader
`
`1
`
`B19 Front of
`Universal Gard --~
`
`\
`%
`
`Brand Ares EM chip
`
`Hie Card wu.
`
`__.
`B43
`Gisolay|
`
`osspencer
`B14 Biometric,
`security reader
`
`2
`
`
`APPL-1008
`APPLEINC./ Page 9 of 36
`
`APPL-1008
`APPLE INC. / Page 9 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 9 of 19
`
`US 2012/O123937 A1
`
`:::
`::
`*x
`Brard Area
`
`-
`
`8:: *::::::::
`iriversai Oar: *x
`^
`t
`
`8: .
`8:
`xix: is 8:88
`
`8x Bier8tric
`8x:ity exer
`
`Y
`
`FIGURE 8C
`
`:3:
`8:88: 888
`
`riversai Carci -
`
`832 card --
`
`xix: is 8:88
`
`SS:
`
`
`
`83- sometric
`xx:ity Exx
`
`FIGURE 8D
`
`APPL-1008
`APPLE INC. / Page 10 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 10 of 19
`
`US 2012/O123937 A1
`
`... xxx xf
`
`
`
`APPL-1008
`APPLE INC. / Page 11 of 36
`
`

`

`Patent Application Publication May 17,2012 Sheet 11 of 19
`
`US 2012/0123937 Al
`
`Snund Area HEB
`
`enwBOG
`iinversal infegrahad
`Choult Cart
`
`-
`¥
`
`avs
` EMV Chip 111 —~J
`
`we
`Gant Holders Neme
`
`a#
`
`~ JOHN DOE
`
`‘
`Brant of Gard
`
`G18. Display
`
`FIGURE 10A
`
`ff
`
`one +t Uo
`Universal integrated
`Choa Card
`
`
`
`ie
`Sionsture Aras
`
`von AGG
`Backof Cars
`
`
`
`
`
`on OES
`Beoret Ares
`
`FIGURE 108
`
`APPL-1008
`APPLEINC./ Page 12 of 36
`
`APPL-1008
`APPLE INC. / Page 12 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 12 of 19
`
`US 2012/O123937 A1
`
`
`
`; ; ; ; -
`{:x: 8::::::: 888
`
`121 -
`:::::::: -
`
`*:::: *
`&:::::::::::: 888
`
`
`
`«; 38
`*::::::::::::::
`
`:
`
`is 2 Estay
`
`FIGURE ffA
`
`-X ::x:
`/
`38x88: 83:
`
`*M ::::::
`88: 8: 8:
`
`• 323
`:::::::::8:8
`
`&:38& :8:
`
`FIG URE f fB
`
`APPL-1008
`APPLE INC. / Page 13 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 13 of 19
`
`US 2012/O123937 A1
`
`y
`8:38883 : 338 X.
`
`-- 3:8:
`::::::::::::::::::
`
`888 (8: 3:3-
`
`
`
`%
`
`~ 2:3
`*::::::::::::::::
`
`: : t : -
`88: 8::8's Kare
`
`FIG URE f 2A
`
`'' 383 .
`
`
`
`
`
`
`
`-- 3:33
`
`« $233
`
`88: 888
`
`&x:3888:8:
`
`FIGURE 12B
`
`APPL-1008
`APPLE INC. / Page 14 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 14 of 19
`
`US 2012/O123937 A1
`
`
`
`*:::::::::::::::::
`
`^ 333
`88:::::::::::::
`
`cardiese's Name
`
`FIGURE 13
`
`&: :::::
`
`
`
`.
`v.
`V.
`~ 8x:
`*::::::::::::::
`
`- JOHN DoE
`
`{88: 8:88 888
`
`FGURE 1.
`
`APPL-1008
`APPLE INC. / Page 15 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 15 of 19
`
`US 2012/O123937 A1
`
`8.8 x.
`8:38: 8: 888:
`
`
`
`ox. 888
`it:8;&i{38
`
`*
`
`
`
`
`
`aaraaaaaaaaa
`: 888
`83: 388xx:
`
`FIGURE fa
`
`APPL-1008
`APPLE INC. / Page 16 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 16 of 19
`
`US 2012/O123937 A1
`
`88:
`38:33::::::::::
`388 storage :-
`
`ra1a.
`
`Sws-------war
`
`*Y
`
`
`
`
`
`s
`Srrrrrrrrrrrrrrrrrrrrrrrr,
`
`M: 3883
`*:::::::::::::::::::
`
`
`
`s
`88:
`88: 8388:8
`
`s: -
`&:::::: 888:
`
`FIGURE 15B
`
`APPL-1008
`APPLE INC. / Page 17 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 17 of 19
`
`US 2012/O123937 A1
`
`traditional card Data
`
`xxxiii: xxix:
`
`w x:
`88: 8 ::::::8:
`
`
`
`
`
`
`
`FIGURE 15C
`
`APPL-1008
`APPLE INC. / Page 18 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 18 of 19
`
`US 2012/O123937 A1
`
`88:
`88:
`
`^
`^
`
`
`
`
`
`883:
`8:3x3:
`
`cripting
`:::::::::
`
`
`
`
`
`88:
`$33888 {:
`
`- 888 8:8::::::::::::::::
`? 3888: 8:888
`
`8:3
`{{x8:g 38x8
`
`FIGURE 16
`
`APPL-1008
`APPLE INC. / Page 19 of 36
`
`

`

`Patent Application Publication May 17, 2012 Sheet 19 of 19
`
`US 2012/O123937 A1
`
`requester sends request
`for card data to be sent to
`
`:::
`
`:
`
`:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Card distributor receives
`be est for a stata:
`
`3.
`Card tistributor certifies
`recipient computing
`ckwice
`
`artistrixx xxixe:
`{x : xxx xx xxix.
`
`recipient computing
`device receiwes articiata
`are stores card data in a
`8x8 tick:
`
`APPL-1008
`APPLE INC. / Page 20 of 36
`
`

`

`US 2012/O123937 A1
`
`May 17, 2012
`
`PORTABLE E-WALLET AND UNIVERSAL
`CARD
`
`CROSS REFERENCE TO RELATED
`APPLICATION
`0001. This application is a continuation-in-part of U.S.
`patent application Ser. No. 13/310,491 filed Dec. 2, 2011 and
`a continuation-in-part of U.S. patent application Ser. No.
`12/715,977 filed Mar. 2, 2010. The contents of which are
`herein incorporated by reference in their entirety.
`
`TECHNICAL FIELD
`0002 The presently disclosed subject matters relates to
`universal cards, mobile applications, and mobile devices Such
`as mobile phones, Personal Digital Assistants (PDAs), iPods,
`tablet computers, laptop computers, and similar mobile
`devices. More particularly, the subject matter relates to a
`universal card which can be used at any type of terminal
`equipped with a magnetic stripe reader or a short range wire
`less communication capability.
`
`BACKGROUND
`0003) People carry many types of cards with them every
`day. The cards include credit cards, debit cards, drivers
`licenses, transportation passes, building access cards, and
`many other types of cards. These cards are typically carried in
`a wallet or purse. A person may need to use any number of
`cards during the course of a day. Since people do not know
`which of the cards will be needed on any given day, most
`people carry all the cards that they may need with them every
`day. With the proliferation of card-capable terminals, people
`can end up carrying an inordinate amount of cards with them
`every day.
`0004. Many people also carry mobile devices with them,
`Such as cellphones, PDAs, tablet computers, laptop comput
`ers, and many other types of mobile devices. Mobile devices
`increasingly have short range communication capabilities,
`such as near field communication (NFC) capabilities or Blue
`tooth capabilities.
`0005. A person that carries a wallet or purse also has to
`secure the contents of the wallet or purse at all times to protect
`against theft and fraud. If a card is lost or stolen, it can be used
`in unauthorized ways, leading to identification theft, fraud, or
`financial loss. In addition, as many transactions are increas
`ingly performed without the need for physically possessing
`the card (e.g., online purchases), the mere exposure of the
`information found on a card to an unauthorized person is a
`risk to the card holder.
`0006. There is a need to reduce the number of cards carried
`by a person, and an opportunity to address that need using the
`short range communication capabilities of a mobile device
`which that person carries. In addition, there is a need to secure
`cards and card information so that cards and card information
`is not exposed to unauthorized people.
`
`SUMMARY
`0007 To reduce the number of cards carried by a person, a
`universal card and short range communication enabled
`mobile device can be used in place of all the other cards which
`the person may want to carry. The universal card can include
`a short range communications transceiver to communicate
`with a mobile device. The mobile device can include a user
`interface and an e-wallet application so that the user can
`
`interface with the e-wallet application for programming the
`universal card via the short range communication link. Once
`programmed, the universal card emulates a function of a
`traditional card. Such as emulating the magnetic stripe of the
`traditional card, the NFC communication of the traditional
`card, the radio transmission of the traditional card, or any
`other function.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0008. The foregoing Summary, as well as the following
`Detailed Description, is better understood when read in con
`junction with the appended drawings. In order to illustrate the
`present disclosure, various aspects of the disclosure are
`shown. However, the disclosure is not limited to the specific
`aspects shown. The following figures are included:
`0009 FIG. 1 depicts an exemplary system including a
`mobile device and a universal card.
`0010 FIG. 2 depicts a traditional card with a static mag
`netic stripe.
`0011 FIG.3 depicts a flowchart process for programming
`a universal card.
`0012 FIG. 4 depicts interactions between a mobile device
`and a universal card, and between a universal card and three
`different types of terminals.
`0013 FIG. 5 depicts an exemplary system including a
`personal computer, a mobile device, and a universal card.
`0014 FIG. 6 depicts a flowchart process for managing
`universal card data using a mobile device.
`(0015 FIG. 7 depicts a flowchart process for managing
`universal card data using a personal computer.
`(0016 FIGS. 8A, 8B, 8C, and 8D depict possible designs
`for the front of a universal card.
`0017 FIG. 9 depicts a possible design for the back of a
`universal card.
`(0018 FIGS. 10A and 10B depict an embodiment of a
`universal card with an integrated circuit.
`(0019 FIGS. 11A and 11B depict an embodiment of a
`universal card with a secure element.
`(0020 FIGS. 12A and 12B depict an embodiment of a
`universal card with an integrated circuit and a secure element.
`0021
`FIG. 13 depicts an embodiment of a universal card
`with a power indicator.
`0022 FIG. 14 depicts an embodiment of a universal card
`with an activation Switch.
`(0023 FIGS. 15A and 15B depict ways to add traditional
`card data to a secure element of a universal card.
`0024 FIG. 15C depicts a way to add traditional card data
`to a secure element of a mobile device.
`0025 FIG. 16 depicts an exemplary electronic card data
`delivery system.
`0026 FIG. 17 depicts an exemplary method of providing
`card data to a universal card.
`
`DETAILED DESCRIPTION OF ILLUSTRATIVE
`EMBODIMENTS
`0027. Referring to FIG. 1, an exemplary system is
`depicted with a mobile device 100 and a universal card 110.
`The mobile device 100 can be any number of devices, includ
`ing a cell phone, a PDA, an iPod, a tablet computer, an
`NFC-specialized device, or any other type of mobile device.
`An NFC-specialized device is a device that provides for the
`user to be able to communicate with NFC terminals, such as
`making a contactless payment, and would also provide a user
`
`APPL-1008
`APPLE INC. / Page 21 of 36
`
`

`

`US 2012/O123937 A1
`
`May 17, 2012
`
`with a user interface for interacting with an NFC-enabled
`universal card. The mobile device 100 may include any num
`ber of components, such as a processor 101, memory 102, a
`power source 103, a user interface 104, and a short range
`transceiver 106. Memory 102 can be any type of computer
`storage media in the form of volatile and/or nonvolatile
`memory such as read only memory (ROM) and random
`access memory (RAM). Processor 101 can operate on data
`and/or software applications available in the memory 102.
`The user interface 104 can include any components for user
`input, such as a keyboard, amouse, a trackball, a touch screen
`display, or any similar component. The user interface 104 can
`also include security features on the mobile device. Such as a
`PIN/password login, a fingerprint Scanner, other biometric
`readers, or similar security features.
`0028. The mobile device 100 also includes an e-wallet
`application 105 which is executable by the processor 101. The
`e-wallet application 105 can be pre-installed on the mobile
`device 100 by the manufacturer of the mobile device 100. The
`e-wallet application 105 can also be installed by the user
`either by downloading it directly to the mobile device 100, by
`downloading the e-wallet application 105 over-the-air via a
`wireless data connection, or by inserting a memory card
`containing the e-wallet application 105.
`0029. The e-wallet application 105 allows the user to input
`information about traditional cards for storage in the memory
`102. Information about traditional cards can include an
`account name, an account number, an expiration date, a card
`verification value2 (CVV2), the image of the traditional card,
`the information which would be stored on the magnetic stripe
`of the traditional card, and any other information necessary to
`emulate the card. The information about traditional cards can
`also be stored in a remote location, such as a trusted service
`manager (not shown), which stores the information and pro
`vides the information to the mobile device 100 on demand via
`wireless data communication. In this case, the e-wallet appli
`cation 105 would interface with the remote location to request
`and receive the information.
`0030 The e-wallet application 105 can also be used to
`program the universal card 110 by allowing the user to select
`a traditional card for the universal card to emulate. The uni
`versal card 110 can be configured to emulate any number of
`traditional cards, including credit cards, debit cards, drivers
`licenses, transportation passes, building access cards, and any
`other types of cards. Once the user selects a card for emula
`tion, the e-wallet application 105 causes the mobile device to
`communicate with the universal card and to transmit the
`information necessary for the universal card to emulate the
`selected traditional card.
`0031. In another universal card embodiment, the informa
`tion about the traditional card could be stored in the memory
`115 of the universal card 110. In this embodiment, if the
`universal card 110 has a user interface with sufficient capa
`bilities, the user may be able to program the card by using the
`user interface on the universal card 110.
`0032. The short range transceiver 106 can be configured to
`communicate via any type of short range communication
`link, such as an NFC communication link or a Bluetooth
`communication link. The mobile device 100 may be manu
`factured with the short range transceiver 106. However, not
`all mobile devices are initially manufactured with short range
`transceivers. The short range transceiver 106 may be located
`on a memory card compatible with a memory slot of the
`mobile device 100. In this situation, the memory card with the
`
`short range transceiver 106 is inserted into the memory slot
`(not shown) of the mobile device 100 such that the mobile
`device can transmit and receive information using a short
`range communication link corresponding to the short range
`transceiver 106.
`0033. Another issue with the short range transceiver 106
`may arise if the short range transceiver 106 of the mobile
`device and the short range transceiver 116 of the universal
`card 110 are not configured for the same type of short range
`communication. For example, mobile device 100 may have a
`Bluetooth transceiver, and the universal card 110 may have an
`NFC transceiver. In Such a situation, the short range trans
`ceiver 106 would be a two-type transceiver, capable of com
`municating via both types of short range communication. In
`the example above, the short range transceiver 106 would be
`capable of receiving information via the Bluetooth link from
`the mobile device 100, and also capable of sending that infor
`mation via the NFC link to the universal card 110. The short
`range transceiver 106 would also be capable of communicat
`ing in the opposite direction, receiving information via the
`NFC link from the universal card 110 and sending that infor
`mation via the Bluetooth link to the mobile device 100. One
`example of a two-type transceiver is a MyMax sticker pro
`duced and sold by TwinLinx of France. The MyMax sticker
`can be attached to the housing of a Bluetooth-enabled device,
`can communicate with the device via a Bluetooth connection,
`and can communicate via an NFC connection with an NFC
`enable device.
`0034. Also depicted in FIG. 1 is a universal card 110. The
`universal card 110 may include components such as a display
`112, a power source 113, a processor 114, and memory 115.
`Each of those components are similar in function to the cor
`responding components of the mobile device 100, except that
`the component of the universal card 110 may be physically
`configured differently so as to fit in the shape of the universal
`card 110. For example, the display 112 of the universal card
`110 may be integrated into universal card 110 via hot lami
`nation processes and standard inlay constructs so that the
`universal card 110 will be the approximate shape and size of
`a traditional credit card and generally compliant with ISO
`7810 standards.
`0035. The universal card 110 may also include a dynamic
`magnetic stripe 111 which can be configured to emulate the
`magnetic stripe of any traditional card. The standard mag
`netic stripe format is defined by ISO/IEC 7810:2003, and its
`extensions, including ISO/IEC 7811-1:2002 through ISO/
`IEC 7811-9:2008, and ISO/IEC 7813:2006, each of which are
`hereby incorporated by reference. Traditional magnetic
`stripes include a series of tiny bar magnets which can be
`magnetized in either a north- or south-pole direction. When
`the polarity of the bars aligns in the same direction, the card is
`blank. To write data to the card, the polarity of a bar is
`reversed so that the north pole is facing the north pole of the
`adjacent bar (N-N) or the south pole is facing the south pole
`(S-S). This causes a change in the magnetic field that can be
`detected by a card reader. The two possible flux reversals,
`N-N or S-S, can represent two different information states,
`which corresponds nicely to the binary system (ones and
`Zeros) used by computers.
`0036 Magnetic stripes have three standard track layouts:
`Track 1, Track 2, and Track 3. Referring to FIG. 2, depicted is
`a traditional card 201 with a static magnetic stripe 202. The
`static magnetic stripe includes each of Tracks 1, 2, and 3.
`shown as 203, 204, and 205, respectively. Each of the track
`
`APPL-1008
`APPLE INC. / Page 22 of 36
`
`

`

`US 2012/O123937 A1
`
`May 17, 2012
`
`layouts are 0.110 inches high. Track 1 has 210 bits per inch
`(bpi) with room for 79 characters of 7 bits each (6 data bits,
`plus 1 parity bit). Track 2 has 75 bpi with room for 40 char
`acters of 5 bits each (4 data bits, plus 1 parity bit). Track 3 has
`210 bpi with room for 107 numeric digits. Tracks 1 and 2 have
`a standard for the data content contained in each track. Those
`standards are shown in Tables 1 and 2 below. In contrast,
`Track 3 does not have a standard for the data content in the
`track, and can be used for proprietary data formats.
`
`TABLE 1.
`
`Standard Track 1 Data Content in Magnetic Stripe of Financial Cards
`
`Data Field
`
`Content of Data Field
`
`Start sentinel
`Format code
`
`byte (the % character)
`byte alpha ('A' is reserved for proprietary
`use of the card issuer: “B is a standard for
`financial institutions: “C-Mare reserved for
`use by ANSI; and “N'-“Z” are available for use
`by individual card issuers)
`Op to 19 characters
`Primary Account
`number
`byte (the character)
`eparator
`3 bytes (optional)
`Country code
`Variable number of bytes
`Surname
`byte (the character)
`Surname separator
`First name or initial Variable number of bytes
`Space
`byte (used only when more data follows the
`first name or initial)
`Variable number of bytes
`
`Middle name
`or initial
`Period
`
`Title
`Separator
`Expiration date
`or separator
`Discretionary data
`
`End sentinel
`Longitudinal
`redundancy check
`
`byte (the . character; used only
`when followed by a title)
`Variable number of bytes (optional)
`byte (the - character)
`4 bytes (YYMM format), or a 1-byte separator if
`non-expiring card
`Variable number of bytes (optional; can be used by
`he card issuer)
`byte (the 2 character)
`byte
`
`TABLE 2
`
`Standard Track 2 Data Content in Magnetic Stripe of Financial Cards
`
`Data Field
`
`Content of Data Field
`
`Start sentinel
`Primary account
`number
`Separator
`Country code
`Expiration date or
`separator
`Discretionary data
`
`End sentinel
`Longitudinal
`redundancy check
`
`1 byte (the ; character)
`Up to 19 bytes
`
`1 byte (the = character)
`3 bytes (optional)
`4 bytes (YYMM format), or a 1-byte separator if
`non-expiring card
`Variable number of bytes (optional; can be used by
`the card issuer)
`1 byte (the 2 character)
`1 byte
`
`0037 Traditional financial cards from the banking indus
`try, Such as credit cards and debit cards, typically use both
`Tracks 1 and 2, with Track 2 using format code 'A' or “B”.
`Some traditional credit and debit cards do not have Track 3
`physically present on the cards as its data is not necessary for
`the cards use. Eliminating Track 3 can reduce the physical
`size of the magnetic stripe. Traditional financial cards usually
`include all of the data listed in Tables 1 and 2.
`
`0038 Traditional gift cards typically use Track 2 with
`format code “B”. Those cards usually have a unique account
`number, but usually do not contain the name of the user in the
`track. Some traditional gift cards can include the amount
`available at the time of the original purchase in the magnetic
`track, and Some will store the current balance on the card so
`that the card can be used at any terminal. However, most
`traditional gift cards do not have any value data stored on the
`card; the card merely stores the unique account number, and
`each terminal at the store is connected to a database, where the
`value of the card is associated with the unique account num
`ber
`0039 Traditional loyalty cards typically use Track 2 with
`format code “B”. Like traditional gift cards, traditional loy
`alty cards typically include only a unique account number
`without storing any data about the user or any monetary value
`associated with the card. Most terminals which accept loyalty
`cards are connected to a central database which associates
`data about the user with the unique account number. Some
`traditional loyalty cards also include a barcode printed on the
`face of the card so that the card can be read by a barcode
`scanner. The barcode is representative of the unique account
`number of the user, and typically has no other data encoded in
`the barcode itself.
`0040. Many driver's licenses issued in the United States
`have a magnetic stripe on them. Driver's licenses typically
`include Tracks 1, 2, and 3. The data content of Tracks 1 and 2
`are shown in Table 3. The data content of Track 3 is not
`entirely standardized, but Track 3 typically includes at least
`Some of the following data categories: template number,
`security number, postal code, class, restrictions, endorse
`ments, sex, height, weight, hair color, eye color, ID number,
`error correction, and security field.
`
`TABLE 3
`
`Standard Track 1 and Track 2 Data Content of US Driver's Licenses
`
`Content of Data Fiel
`
`Track 1 Data Fields
`
`Start sentinel
`State or province
`City
`Field separator
`
`Last name
`Field separator
`First name
`Field separator
`First name
`Field separator
`Home address
`Field separator
`Discretionary data
`Start sentinel
`Track 2 Data Fields
`
`1 character (usually the 96 character)
`2 characters
`Up to 13 characters (variable length)
`1 character (usually the - character), unless the
`City field is maxed out
`Variable length
`1 character (usually the Scharacter)
`Variable length
`1 character (usually the Scharacter)
`Variable length
`1 character (usually the character)
`Variable length (usually house number and street)
`1 character (usually the - character)
`Variable length
`1 character (usually the character)
`
`SO issuer ID number 6 character
`License ID number
`8 character
`Field separator
`1 character (usually the = character)
`Expiration date
`4 characters (usually YYMM format)
`Birth date
`8 characters (usually YYYY|MM|DD format)
`License ID number
`Variable length
`OWeOW
`
`0041 Traditional access cards are used to provide access
`to the card holder to a building or other secure area. Tradi
`tional access cards typically use either a magnetic stripe or a
`
`APPL-1008
`APPLE INC. / Page 23 of 36
`
`

`

`US 2012/O123937 A1
`
`May 17, 2012
`
`radio transmitter to convey information to a terminal. When
`using a magnetic stripe, the data encoded on the magnetic
`stripe typically includes the user's name, an ID number asso
`ciated with the user, and an access level relating to where and
`when the user is allowed access. When using a radio trans
`mitter, the access card typically only includes an ID number
`associated with the user, and the access terminal is connected
`to a database which contains information about the user and
`the access level based on the ID number. Radio transmitters in
`access cards can either be “active' radio transmitters (pow
`ered by a power source on the card), or “passive' radio trans
`mitters (powered by the radio receiver in the terminal when
`the card is brought into close proximity with the terminal).
`0042. Referring back to FIG.1, universal card 110 can also
`include a radio communications apparatus 117 to emulate an
`access card which uses a radio communications apparatus.
`Radio communications apparatus 117 can either be a passive
`radio transmitter, or an active radio transmitter powered by
`power source 113. The ID number transmitted by the radio
`communications apparatus 117 can be programmed so that
`the universal card can programmed to emulate different tra
`ditional access cards. When programming the universal card
`110 to emulate an access card, it may be desirable to verify the
`identity of the user prior to programming the universal card
`110. Examples of user verification are discussed below.
`0043. Other types of traditional cards exist and can be
`emulated by universal card 110. Examples of dynamic mag
`netic stripes are shown in US Patent Application Publication
`2005/0194452, applied for by Nordentoft et al, and 2007/
`0189581, applied for by Nordentoft et al. In these examples,
`individually inducible transducer coils are positioned within
`a universal card and are configurable to emulate the static
`magnets in a traditional magnetic stripe. The dynamic mag
`netic stripe 111 of the universal card can be configured to
`emulate any traditional static magnetic stripe, including any
`data or data format used by a static magnetic stripe. Thus,
`even if a data content format is not discussed here, dynamic
`magnetic stripe 111 would be capable of emulating the data
`content format not discussed here.
`0044) Universal card 110 may include a biometric security
`device 118. Such as a fingerprint reader, a microphone for
`voice identification, or other device for input during biomet
`ric identification. The use of such biometric identification for
`security is discussed below.
`0045 Referring now to FIG. 3, depicted is a flowchart
`process for programming a universal card. To initiate power
`on the universal card (UC) the user may be required to take an
`action that may include pushing a button on card to turn it
`“on”, is tapped 301, or any other similar technique. The
`universal card's power is verified 302. If the power is not on,
`the user will repeat the action to initiate power 301 on the
`universal card again. If the power is on, the universal card and
`the mobile device are paired 303, establishing the short range
`communication link 120 (as shown in FIG. 1). The pairing is
`verified 304, with the pairing 303 attempted again if the
`pairing is not successful. Once paired, an e-wallet application
`on the mobile device is automatically launched 305. If the
`e-wallet application is not automatically launched 306, it can
`be manually launched 307 on the mobile device.
`0046 Before allowing access to view, change or modify
`the financial data associated with the e-wallet program 105 on
`the mobile device 100 or on the universal card 110, the user
`must first be authenticated 308. Authentication can take a
`number of forms. One form of authentication can be verifi
`
`cation of something that the user has in their possession. In
`this context, one security feature could be that the mobile
`device 100 can only be paired with one universal card 110.
`and the universal card 110 will only pair to one mobile device
`100. For example, if a user's mobile device 100 is lost or
`stolen, the universal card 110 will not pair with any other
`mobile device. Thus, any personal card information stored on
`the universal card 110 will not be accessible by another
`mobile device.
`0047 Another form of user authentication can be verifi
`cation of something that the user knows. This can be a per
`sonal identification number (PIN), a unique identification of
`the user (such as a Social security number), a fact about the
`user (Such as the maiden name of the user's mother), a pass
`word, or anything else that the user can input. Yet another
`form of user authentication is something about the user. This
`can include a fingerprint, a Voice identification, or other veri
`fiable biometric.
`0048 While each of these forms of authentication can
`alone authenticate the user, it may be desirable to require at
`least two forms of authentication to ensure increased security.
`For example, the mobile device 100 and the universal card
`110 may authenticate each other as being paired; however,
`this fact alone does not ensure that the person operating the
`devices is the authentic user. In this case, it may be advanta
`geous to require the user to enter a password to Verify that the
`user is authentic. In some instances, the issuer of the card may
`impose additional requirement depending on the circum
`stances that the card is being used. For example, if the card is
`being used to make a payment over a certain value, if the card
`is being used in a foreign country, or if the card issuer has
`reason to Suspect that the use of the card is unauthorized, the
`issuer may require another level of authentication. In this