`1J820100138518A1
`
`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2010/0138518 A1
`(43) Pub. Date: Jun. 3, 2010
`
`Aiglstorfer et al.
`
`(54)
`
`METHOD AND SYSTEM FOR
`DOWNLOADING INFORMATION INTO A
`SECURE ELEMENT OF AN ELECTRONIC
`DEVICE
`
`(75)
`
`Inventors:
`
`Rodney Aiglstorfer, Corte Madera,
`CA (US); Benjamin Vigier, San
`Francisco, CA (US)
`
`Correspondence Address:
`MURABITO, HAO & BARNES, LLP
`TWO NORTH MARKET STREET, THIRD
`FLOOR
`SAN JOSE, CA 95113 (US)
`
`(73)
`
`Assignee:
`
`MFOUNDRY, Sausalito, CA (US)
`
`(21)
`
`Appl.No.:
`
`12/621,319
`
`(22)
`
`Filed:
`
`Nov. 18, 2009
`
`Related US. Application Data
`
`(60)
`
`Provisional application No. 61/117,520, filed on Nov.
`24, 2008.
`
`Publication Classification
`
`(51)
`
`Int. C1.
`(2006.01)
`G06F 15/16
`(2006.01)
`G06Q 30/00
`(2006.01)
`G06Q 20/00
`(2006.01)
`G06Q 50/00
`(2006.01)
`G06F 3/048
`(52) us. C1 ............................. 709/219; 705/26; 715/810
`(57)
`ABSTRACT
`
`A method for downloading information from a remote server.
`The method includes receiving, at a portable device, banking
`card information for an account and storing the banking card
`information into a secure memory within the portable device.
`Responsive to the receiving, a first moblet software module
`automatically sends a wireless message to the remote server
`to inform the remote server of the banking card information
`being received at the portable device. The portable device
`may receive a second moblet software module associated
`with the banking card information. The portable device may
`subsequently execute the second moblet software module
`which utilizes the banking card information, wherein the first
`and second moblet software modules comprise device inde-
`pendent commands of a generic syntax and wherein further
`the commands are executed by a device dependent software
`module also resident on the portable device.
`
`DD
`
`
`RESPONSIVE TO A USER REQUEST, THE PORTABLE DEVICE SENDING A MESSAGE
`TO A REMOTE SERVER TO DOWNLOAD A FIRST MODLET SOFTWARE MODULE
`'IIO
`V
`THE PORTABLE DEVICE RECEIVING FROM THE REMOTE SERVER A DEVICE
`DEPENDENT SOFTWARE MODULE
`I12
`r
`
` V
`
`THE PORTABLE DEVICE RECEIVING FROM THE REMOTE SERVER THE FIRST
`MCDLET SOFTWARE MODULE
`
`
`
`I R
`m l T
`m I
` +
`
`Apple Ex. 1004, p. 1
`Apple Ex. 1004, p. 1
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`m V
`
`|_
`
`THE PORTABLE DEVICE EXECUTING THE FIRST MOBLET SOFTWARE MODULE USING—I
`THE DEVICE DEEENDENT SOFTWARE MODULE
`115.
`
`ECEIVING CARD INFORMATION FOR A FIRST ACCOUNT AND STORING THE CARD
`INFORMATION IN A SECURE MEMORY
`
`HE FIRST MOELET SOFTWARE MODULE AUTOMATICALLY SENDING A WIRELESS
`MESSAGE TO THE REMOTE SERVER T0 INFORM THE REMOTE SERVER OF ll‘HE
`CARD INFORMATION DEINC RECEIVED AT THE PORTABLE DEVICE
`mI
`V
`
`THE PORTABLE DEVICE RECEIVING A SECOND MODLET SOFTWARE MODULE —|
`ASSOCIATED WITH THE CARD INFORMATION
`
`THE PORTABLE DEVICE EIIECDTINC THE SECOND MOELET SOFTWARE MODULE
`fl
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 2 0f 10
`
`US 2010/0138518 A1
`
`
`
`
`
`253593.5%..“:33:EEm5flag
`
`EN
`
`
`
`2555Ego“3333EE
`
`KEEESEEaa
`
`
`
`«anL.......................................,L
`
`Esaufisz
`
`gm
`
`sagas;
`
`:«
`
`
` amagma“Ea—Em
`2:32£33:33:283
`
`.ma_LEE—a“ELEV.E25$5
`
`
`
` a.5:$3sz|
`
`
`
`ESEass;LEE
`
`2N
`
`
`
`2.62mEmEWflmEnosEs...
`
`afiéLL...Egg
`
` lLav..Ema:ea;gm._.........
`
`+1“EtaLN“.
`.....Eng23%
`
`Esta
`
`—
`
`NmmDOE
`
`5:252:ES33:3Eum
`
`
`
`EraséaES22%;ESEmmom
`
`Mum
`
`
`
`
`
`95233LEE—um“uqmgcsmméaz
`
`am.
`
`Apple Ex. 1004, p. 3
`Apple Ex. 1004, p. 3
` Apple v. Fintiv
`Apple v. Fintiv
`IPR2020-00019
`IPR2020-00019
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 4 0f 10
`
`US 2010/0138518 A1
`
`
`
`
`
`
`
`
`
`
`
`
`Mlfiflfififlfflfiflfllflfll
`
`
`
`
`
`
`
`
`FIGURE4
`
`Apple Ex. 1004, p. 5
`Apple Ex. 1004, p. 5
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 6 0f 10
`
`US 2010/0138518 A1
`
`FIGURESC
`
`
`
`
`
`
`
`FIGURE5D
`
`Apple Ex. 1004, p. 7
`Apple Ex. 1004, p. 7
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 8 0f 10
`
`US 2010/0138518 A1
`
`
`
`
`
`
`
`
` FIGURE6C
`
`FIGURE6D
`
`Apple Ex. 1004, p. 9
`Apple Ex. 1004, p. 9
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 10 0f 10
`
`US 2010/0138518 A1
`
`I
`RECEIVING CHRD INFORMIITION FOR 11 SECOND IICCOUNT END STORING THE CERD
`
`INI'ORMIITION FOR THE SECOND IICCOUNT IN E SECURE MEMORY
`
`1%
`
`THE FIRST MOBLET SOFTWRRE MODULE EUTOMETICJILLY SENDING II WIRELESS
`
`MESSEGE TO THE REMOTE SERVER TO INFORM THE REMOTE SERVER THRT THE
`
`CERD INEORMIITION FOR THE SECOND IICCOUNT IS BEING RECEIVED RT THE
`PORTHBLE DEVICE
`
`fl
`
`
`m
`
`THE PORTHBLE DEVICE RECEIVING 11 THIRD MOBLET SOFTWRRE MODULE
`
`ESSOCIHTED WITH THE CIIRD INEORMIITION FOR THE SECOND IICCOIINT
`
`m
`
`THE PORTEBLE DEVICE EXECUTING THE THIRD MOBLET SOTTWIIRE MODULE
`
`m
`
`DISPLIIYING GRHPHICEL ICONS 01' THE SECOND IIND THE THIRD MOBLET
`
`SOFTWRRE MODULES ON II DISPLRY
`
`FIGURE TB
`
`Apple Ex. 1004, p. 11
`Apple Ex. 1004, p. 11
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 A1
`
`Jun. 3, 2010
`
`modules. It is appreciated that the second and the third moblct
`software modules may be controlled by operations ofthe first
`moblet software module.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0015] Embodiments of the present invention are illus-
`trated by way ofexample, and not by way of limitation, in the
`figures of the accompanying drawings and in which like ref—
`erence numerals refer to similar elements and in which:
`[0016]
`7IG. 1 shows an exemplary system for downloading
`information to an electronic wallet comprising a removable
`security element in accordance with one embodiment of the
`present invention.
`[0017]
`:IG. 2 shows an exemplary system for downloading
`information to an electronic wallet comprising a non—remov—
`able security element in accordance with one embodiment of
`the present invention.
`[0018]
`7IG. 3 illustrates a general purpose computer sys-
`tem that may serve as a platfonn for embodiments of the
`present invention.
`[0019]
`:IG. 4 shows a MOJAX enabled wallet component
`architecture in accordance with one embodiment of the
`present invention.
`[0020]
`jIGS. 5A-5D show an exemplary embedded card
`personalization in accordance with one embodiment of the
`present invention.
`[0021] 4le. 6A-6D show extemalized card personaliza-
`tion in accordance with one embodiment of the present inv en-
`tion.
`jIGS. 7A and 7B show an exemplary flow diagram
`[0022]
`for down oading information into a secure element in accor-
`dance with one embodiment of the present invention.
`
`
`
`DETAILED DESCRIPTION
`
`[0023] Reference will now be made in detail to embodi-
`ments of the present invention, examples of which are illus-
`trated in the accompanying drawings, While the invention
`will be described in conj unction with these embodiments, it
`will be understood that they are not intended to limit the
`invention to these embodiments. On the contrary, the inven—
`tion is intended to cover alternatives, modifications and
`equivalents, which may be included within the spirit and
`scope of the invention as defined by the appended claims.
`Furthermore,
`in the following detailed description of the
`present invention, ntunerous specific details are set forth in
`order to provide a thorough understanding of the present
`invention. However, it will be evident to one of ordinary skill
`in the art that the present invention may be practiced without
`these specific details. In other instances, well known meth—
`ods, procedures, components, and circuits have not been
`described in detail as not to unnecessarily obscure aspects of
`the invention.
`
`Notation and Nomenclature
`
`Some portions of the detailed descriptions which
`[0024]
`follow are presented in terms of procedures, steps, logic
`blocks, processing, and other symbolic representations of
`operations on data bits that canbe performed on television set
`memory. These descriptions and representations are the
`means used by those skilled in the art to most effectively
`convey the sub stance oftheir work to others skilled in the art.
`A procedure, television set executed step, logic block, pro-
`cess, etc.,
`is here, and generally, conceived to be a self—
`
`consistent sequence of steps or instructions leading to a
`desired result. The steps are those requiring physical manipu-
`lations of physical quantities.
`these quantities
`[0025] Usually,
`though not necessarily,
`take the form of electrical or magnetic signals capable of
`being stored, transferred, combined, compared, and other-
`wise manipulated in a computer system. It has proven conve—
`nient at times, principally for reasons of common usage, to
`refer to these signals as bits, values, elements, symbols, char-
`acters, terms, numbers, or the like.
`[0026]
`It should be borne in mind, however, that all ofthese
`and similar tenns are to be associated with the appropriate
`physical quantities and are merely convenient labels applied
`to these quantities. Unless specifically stated otherwise as
`apparent from the following discussions, it is appreciated that
`throughout the present invention, discussions utilizing tenns
`such as “processing” or “creating” or “transferring” or
`“executing” or “determining” or “instructing” or “issuing” or
`“halting” or “clearing” or “accessing” or “aggregating” or
`“obtaining” or “selecting” or “calculating” or “measuring” or
`“querying” or “receiving” or “sending” or “providing” or
`“storing” or “displaying” or “rendering” or the like, refer to
`the action and processes of a television set, or similar elec—
`tronic computing device, that manipulates and transforms
`data represented as physical (electronic) quantities within the
`television set’s registers and memories into other data simi-
`larly represented as physical quantities within the television
`set memories or registers or other such information storage,
`transmission or display devices.
`
`A Method and System for Downloading Information
`into a Secure Element of an Electronic Device
`
`[0027] Referring now to FIG. 1, an exemplary system 100
`for downloading infonnation to an electronic wallet compris-
`ing a removable security element in accordance with one
`embodiment of the present invention is shown. The system
`100 includes an electronic device 110 which may be any
`portable electronic device, e.g., an electronic wallet, a cellular
`phone, a personal digital assistant (PDA), etc., a trusted ser-
`vice manager (TSM) 120 and a remote server 130.
`[0028] The electronic device 110 may be a portable elec-
`tronic device that can be used to pay for purchases on the go,
`similar to the use of a credit card in a conventional fashion.
`The electronic device 110 utilizes a graphical user interface
`(GUI) to enable a user friendly interaction associated with
`payments and financial information, for instance.
`[0029] The TSM 120 is a trusted entity in charge of sending
`secure infonnation, e.g., financial infonnation, regarding a
`specific user to the electronic device 110. The TSM 120 may
`verify and authenticate the user with regard to a particular
`bank or financial institution. For example, the identity of a
`user with a Bank of America account may be verified and
`authenticated. It is appreciated that although embodiments
`herein are described with respect to banking information and
`bank accounts, the infonnation may be related to any card,
`e.g., a reward card, a movie rental card, a gas card, a coffee
`shop card. a stored value card, a loyalty card, etc. As such, the
`use of banking infonnation is exemplary and not intended to
`limit the scope of the present invention. After verification of
`the user identity and authentication of the user, the TSM 120
`may transmit the banking information regarding the Bank of
`America accotmt (for instance) to the electronic device 110.
`[0030] The remote server 130 may provide various appli-
`cations to the electronic device 110. For example, the remote
`
`Apple Ex. 1004, p. 13
`Apple Ex. 1004, p. 13
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 A1
`
`Jun. 3, 2010
`
`[004]] According to one embodiment of the present inven-
`tion, the first, the second and the third moblet software mod-
`ules include device independent commands of a generic syn-
`tax. In one embodiment, the first, the second and the third
`moblet software modules may be written using MOJAX corn-
`mands. MOJAX is a language that enables manipulation of a
`web browser and flash. It is appreciated that the MOJAX
`commands are executed by the dependent software of the
`electronic device 110. The electronic device 110 dependent
`software resides on the electronic device 110.
`
`the third moblet
`[0042] According to one embodiment,
`software module 112 may be transmitted wirelessly and
`installed on the electronic device 1 10 transparent to the user.
`It is appreciated that updates to the third moblet software
`module 112 may be transmitted and installed automatically.
`However,
`it is appreciated that the third moblet software
`module 112 or any update thereof may be received and
`installed on the electronic device 110 responsive to a user
`request.
`It is appreciated that the transmission and installa-
`[0043]
`tion ofbanking card information is exemplary and should not
`be construed as limiting the scope ofthe present invention. As
`such, any kind of information and moblet software module
`may be transmitted and installed within the MOJAX environ—
`ment. For example, non-associated modules, e.g., coupon
`information, advertising, ete., may be transmitted and
`installed without requiring the ISM 120 to interact with the
`TSA 102 and to store that information within the removable
`security element 104. As such. non-associated modules may
`be directly transmitted by the remote server 130 to the first
`moblet software module 106 that operates within the MOJAX
`environment.
`It
`is appreciated that the transmission and
`installation of non-associated modules may be performed
`automatically by the remote server 130 or it may be respon-
`sive to a user interaction and/or user initiation.
`
`[0044] Referring now to FIG. 2, an exemplary system 200
`for downloading information to an electronic wallet compris-
`ing a non-removable security element in accordance with one
`embodiment of the present invention is shown. The system
`200 includes an electronic device 210, e.g., an electronic
`wallet, a cellular phone, a PDA, etc., a trusted service man-
`ager (TSM) 220 and a remote server 230. It is appreciated that
`the TSM 220 and the remote server 230 operate similar to the
`TSM 120 and the remote server 130 already described above
`with respect to FIG. 1.
`[0045]
`It is appreciated that a first moblet software module
`204 may be installed during manufacturing of the electronic
`device 210. Alternatively, the first moblet software module
`204 may be requested 201 from the remote server 230. The
`request 201 may indicate a device type of the electronic
`device 210. In response to the request 201, the remote server
`230 may transmit 203 the first moblet software module 204 to
`the electronic device 210. Furthermore, responsive to the
`request 201, the remote server 130 may transmit 203 a device
`dependent software, e.g., MOJAX enviromnent. It is appre—
`ciated that in one embodiment the device dependent software
`may be installed during manufacturing of the electronic
`device 110.
`
`[0046] The first moblet software module 204 is installed
`and becomes operable on the electronic device 210. In this
`embodiment, since the electronic device 210 does not have a
`removable security element 104. the TSM 220 communicates
`to a non-removable security element 202 without using the
`TSA 102. Moreover, the TSM 220 communicates with the
`
`
`
`first moblet software module 204 without using the TSA 102.
`It is appreciated that according to one embodiment of the
`present invention, the non-removable security element 202 is
`near field communication (NFC) enabled.
`[0047]
`It is appreciated that the first moblet software mod—
`ule 204 becomes operable on the electronic device 210 when
`it is installed on the electronic device 210. The first moblet
`software module 204 may manage additional moblet soft-
`ware modules. It is appreciated that the first moblet software
`module 204 may operate within the electronic wallet envi-
`romnent. For example, moblet software modules are operable
`in a MOJAX environment operating on a device. According to
`one embodiment, MOJAX is device specific while moblet
`software modules operating within the MOJAX environment
`are device generic. According to one embodiment, the elec-
`ronic wallet envirormient may have a corresponding graphi-
`cal element icon. Upon selection of the electronic wallet
`environment, additional graphical element icons associated
`with moblet software modules may be displayed. The dis—
`olayed moblet software modules may be executed upon selec—
`ion thereof.
`
`[0048] The first banking card information 205 may be corn-
`municated to the non—removable security element 202 from
`he TSM 220 after the identity of the user is verified and
`authenticated. The TSM 220 may also communicate and
`notify 207 the first moblet software module 204 that the first
`aanking card information 205 has been communicated and
`stored in the non-removable security element 202. It is appre-
`ciated that the non-removable security element 202 may
`ransmit an acknowledgement signal to the TSM 220 that the
`first banking card information 205 has been received and
`stored.
`[0049] The first moblet software module 204 may notify
`209 the remote server 230 that the first banking card infor-
`mation 205 has been received and stored in the non—remov—
`able security element 202. In response to the notification 209,
`the remote server 230 may automatically transmit 211a sec-
`ond moblet software module to the first moblet software
`module 204. It is appreciated that the second moblet software
`module may be an application related to the first banking card
`information 205. The first moblet software module 204 may
`receive and install the second moblet software module 206 on
`the electronic device 210. As a result, the first banking card
`information 205 may be used in conjunction with the execu—
`tion of the second moblet software module 206 to enable the
`user to interact with the second moblet software module 206
`and the first banking card information 205 associated there-
`with. It is appreciated that the second moblet software module
`206 may be a GUI type application that when executed
`enables user interaction therein to perform banking applica-
`tions.
`
`[0050] According to one embodiment, the second moblet
`software module 206 may be transmitted wirelessly and
`installed on the electronic device 210 transparent to the user.
`It is appreciated that updates to the second moblet software
`module 206 may be transmitted and installed automatically.
`However, it is appreciated that the second moblet software
`module 206 or any updates thereof may be received and
`installed on the electronic device 210 responsive to a user
`initiated request.
`[0051]
`It is appreciated that additional banking card infor-
`mation and moblet software modules associated therewith
`may be similarly received and installed. For example, a sec-
`ond banking card information 213 may be transmitted from
`
`Apple Ex. 1004, p. 15
`Apple Ex. 1004, p. 15
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 A1
`
`Jun. 3, 2010
`
`dent syntax that is only MOJAX-specific. It is appreciated
`that the component architecture shown in FIG. 4 represents a
`software hierarchy of software components installed on a
`portable computer system as described herein.
`[0061] Wallet moblets 420a-420h are self-contained appli-
`cations and in one embodiment, only one wallet moblet can
`operate in the wallet at any given time. Moblets can pass
`control to other rrroblets within the wallet. Moblets can be
`updated, blocked or removed by the mobile wallet 410. Mob-
`lets may have their own secure cache for data that cannot be
`accessed by any other moblet. Moblets generally cannot be
`modified by other moblets and they can have their own dcdi-
`eated gateways. Moblets pass control between themselves for
`interaction. Moblet 420a may pass control to moblet 42015 by
`passing a registry function thereto. Parameters can be passed
`between the moblets during load. Moblets have no visibility
`into the data of another moblet. After load, moblet 420a will
`no longer be running and moblet 4201) becomes active, in this
`example. Only registered moblets can be launched and if a
`moblet is not present on the device, launching it will first
`trigger a download of the moblet from a remote control.
`[0062] More specifically, the mobile wallet 410 controls the
`GUI environment that allows user selection of the other mob-
`lets 420a-420h so that moblet presentation and user selection
`can be performed in a uniform graphical environment. Also,
`the mobile wallet 410 controls the sequence in which the
`other moblets 4200-420}: are executed. Mobile wallet 410
`also controls the manner and timing in which other moblets
`are downloaded to the portable computer system, as
`described herein. It is appreciated that the component archi-
`tecture may also contain several plug-ins as shown as 440a-
`4409. Plug-ins are APIs that can be used by any moblet and
`not all plug-ins may be available for a device, e.g., NFC.
`Plugirrs are part of a moblet runtime environment (MRE)
`distribution and are not moblets.
`[0063]
`FIGS. 5A-5D show an exemplary embedded card
`personalization in accordance with one embodiment of tie
`present invention. The embedded card personalization com—
`prises a secure element that is embedded within the device.
`The TSA agent and a wallet moblct operate within the MRE.
`The TSA agent performs all the interactions with the secure
`element. For example, referring to FIG. 5B, TSM pushes a
`new card applet into the TSA agent. In one embodiment, the
`nwv card applet may be banking information. As a result, the
`"SA agent communicates and pushes the received informa-
`tion into the secure element. Referring now to FIG. 5C, the
`"SA agent notifies the wallet moblet operating within the
`MOJAX environment that the information from the TSM has
`been received. Referring now to FIG. 5D, the wallet moblet in
`response to the notification from the TSA agent request a card
`moblet from the wallet registry. In response to the request, the
`wallet registry transmits the card moblet to the wallet MRE
`where the card moblet is installed within the MOJAX envi-
`ronment.
`
`
`
`
`
`FIGS. 6A-6D show extemalized card personaliza-
`[0064]
`tion in accordance with one embodiment ofthe present inven—
`tion. Extemalized card personalization may comprise a
`removable secure element. Removable secure elements do
`not require a TSA agent to interact with the secure element.
`The wallet MRE comprises a wallet moblet. Referring now to
`FIG. 6B, the TSM pushes the new card applet into the remov-
`able secure elerrrent. Referring now to FIG. 6C, the TSM
`notifies the wallet moblet operating within the wallet MRE,
`e.g., MOJAX environment,
`that
`the new card applet
`is
`
`installed. Referring now to FIG. 6f), the wallet moblet in
`response to receiving the notification from the TSM may send
`a request for a card moblet to the wallet registry. In response
`to the request, the wallet registry may transmit the card mob-
`let to the wallet MRE where the card moblet is installed.
`[0065] Referring now to FIGS. 7A and 7B, an exemplary
`flow diagram 700 for downloading information into a secure
`element in accordance with one embodiment of the present
`invention is shown. At step 710, responsive to a user request,
`the portable device, e.g., cellular phone, sends a message to a
`remote server to download a first moblet software module. It
`is appreciated that the message sent to the remote server may
`indicate a device type of the potable device.
`[0066] At step 712, the portable device receives a device
`dependent software module. The device dependent software
`module is transmitted by the remote server via a wireless
`network. At step 714, the portable device receives the first
`moblet software module from the remote server via a wireless
`network.
`[0067] At step 716, the portable device executes the first
`moblet software module using the device dependent software
`module. It is appreciated that according to one errrbodiinerrt,
`the device dependent module resides on the portable device.
`The portable device receives card information associated
`with a first account and stores the card information in a secure
`mcmory within the portable device, at step 718.
`[0068] At step 720, the first moblet software module auto-
`matically sends a wireless message, e.g., via a wireless net—
`work, to the remote server to inform the remote server that the
`card information is being received at the portable device. In
`one embodiment, the automatic transmission of the wireless
`message at step 720 is responsive to the receiving of the card
`information at step 718.
`[0069] According to one embodiment, at step 722, the por—
`table device reeeives, e.g., wirelessly via a wireless network,
`a second moblet software module associated with the card
`information. In one embodiment, the second moblet software
`module is received in a marmer that is transparent to the user
`of the portable device. The portable device executes the sec-
`ond moblet software module that utilizes the card inforrna—
`tion, at step 724. It is appreciated that according to one
`embodiment, the first and the second moblct software mod-
`ules comprise device independent commands of a generic
`syntax. According to one embodiment, the first and the sec-
`ond moblet software modules are written using MOJAX corri-
`mands.
`
`[0070] At step 726, the portable device receives card infor-
`mation for a second account and stores the card information
`for the second account into the secure memory within the
`portable device. According to one embodiment, at step 728,
`the first moblet software module automatically sends a wire-
`less mes sage to the remote server to inform the remote server
`that the card information for the second account is being
`received by the portable device. It is appreciated that the
`automatic transmission of the wireless message may be
`responsive to receiving the card information for the second
`account. According to one embodiment, at step 730, the por-
`table device receives a third moblet software module associ-
`ated with the card information for the second account. At step
`732, the portable device executes the third moblet software
`module that utilizes the card information for the second
`account.
`
`It is appreciated that the third moblet software mod-
`[0071]
`ule comprises device independent commands of the generic
`
`Apple Ex. 1004, p. 17
`Apple Ex. 1004, p. 17
` Apple v. Fintiv
`Apple v. Fintiv
`lPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 A1
`
`Jun. 3, 2010
`
`
`
`
`
`
`
`
`
`12. The electronic cevicc as cescri Jed in claim 10, whcrcin
`said removable security elcmcnt is a subscriber identity mod-
`ule (SIM) card.
`13. The electronic cevice as cescri Jed in claim 10, wherein
`said receiving said second moblet software module is per—
`formed transparcntly to a user of said electronic device.
`14. The electronic cevice as cescri Jed in claim 10, wherein
`said receiving said second moblet software module is per—
`formed responsive to a user request operating said electronic
`device.
`15. The electronic cevice as cescri Jed in claim 10, wherein
`said method further comprises:
`automatically receiving an update for said second moblet
`software module.
`16. The electronic cevice as cescri Jed in claim 10, wherein
`said second moblet software modulc is received wirclcssly.
`17. The electronic cevice as Lescri Jed in claim 10, wherein
`said method further comprises:
`executing said second moblet software module that utilizes
`said card information for said first account.
`18. The electronic cevice as cescri Jed in claim 10, wherein
`said method further comprises:
`responsive a user request, said electronic device transmit—
`ting a signal to said remote server to download said first
`moblet software modulc and indicating therein a device
`type of said electronic device;
`said electronic device receiving from said remote server a
`device dependent software module via a wireless net-
`work;
`said electronic device receiving from said remote server
`said first moblet software module via a wireless net-
`work; and
`said electronic device executing said first moblet software
`module using said device dependent software module.
`19. The electronic device as described in claim 10, wherein
`said method further comprises:
`receiving a second card information for a second account;
`storing said second card information for said second
`account into said removable security element;
`responsive to said receiving said second card information,
`said first moblet software module automatically trans-
`mitting a second signal to said remote server to notify
`said remote server that said second card infonnation is
`received; and
`in response to said transmitting said second signal, said
`first moblet software module receiving a third moblet
`software module associated with said second card infor—
`mation for said second account; and
`executing said third moblet software module that utilizes
`said second card information for said second account,
`wherein said third moblet software module comprise
`device independent commands of a generic syntax and
`wherein further said commands are executed by a device
`dependent software module.
`20. The electronic device as described in claim 19, wherein
`said method further comprises:
`displaying graphical icons for said second and said third
`moblet software modules on a display, wherein said
`displaying is operable to allow a user selection thereof,
`and wherein display and selection of said second and
`said third moblet software modules are controlled by
`operations of said first moblet software module.
`
`21 . The clcctronic device as described in claim 10, wherein
`said rcmovable security elcmcnt compri scs a near ficld com-
`munication chip.
`22. An electronic device comprising:
`a processor for processing data;
`a non-removable security element operable to store secu-
`rity data, wherein said non—removable security element
`automatically receives and stores card information for a
`first account from a trustcd scrvicc manager (TSM); and
`a memory component operable to store data, wherein said
`memory component comprises instructions that when
`executed implement a method for downloading infor-
`mation from a remote server, said method compri sing:
`subsequent
`to said non-removable security element
`receiving said card information for said first account,
`a first moblet software module automatically receiv—
`ing a signal from said TSM that said card information
`for said first account is received;
`responsive to said receiving, a first moblet software
`module automatically transmitting a signal to said
`remote server to notify said remote server that said
`card information is transmitted; and
`said first moblet software module receiving a second
`moblet software module associated with said card
`information.
`23. The electronic device as described in claim 22, wherein
`saic first and said second moblet software modules comprise
`device independent commands of a generic syntax. and
`wherein further said device independent commands are
`executed by a device dependent software module resident on
`saic electronic device.
`24. The c cctronic device as dcscribcc in claim 22, wherein
`saic electronic device is a cellular phone,
`25. The e ectronic device as describec in claim 22, wherein
`saic receiving said second moblet software module is per-
`formed transparently to a user of said e ectronic device.
`26. The e ectronic device as describec in claim 22, wherein
`saic receiving said second moblet software module is per-
`formed responsive to a user request operating said electronic
`device.
`27. The e ectronic device as describec in claim 22, wherein
`saic methoc further comprises:
`automatically receiving an update for said second moblet
`software module.
`28. The e ectronic device as describec in claim 22, wherein
`saic second moblet software module is received wirelessly.
`29. The e ectronic device as describec in claim 22, wherein
`saic methoc further comprises:
`executing said second moblet software module that utilizes
`said card information for said first account.
`30. The e ectronic device as describec in claim 22, wherein
`saic methoc further comprises:
`responsive a user request, said electronic device transmit-
`ting a signal to said remote server to download said first
`moblet software module and indicating therein a device
`type of said electronic device;
`said electronic device receiving from said remote se