`
`385
`
`18Al
`
`US 201001
`
`as) United States
`a2) Patent Application Publication co) Pub. No.: US 2010/0138518 Al
`(43) Pub. Date: Jun. 3, 2010
`
`Aiglstorferet al.
`
`(54)
`
`METHOD AND SYSTEM FOR
`DOWNLOADING INFORMATION INTO A
`SECURE ELEMENT OF AN ELECTRONIC
`DEVICE
`
`(75)
`
`Inventors:
`
`RodneyAiglstorfer, 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 U.S. Application Data
`
`(60)
`
`Provisional application No. 61/117,520, filed on Nov.
`24, 2008.
`
`Publication Classification
`
`(51)
`
`Int. Ch
`(2006.01)
`GO6F 15/16
`(2006.01)
`G06Q 30/00
`(2006.01)
`G060 20/00
`(2006.01)
`G060 50/00
`(2006.01)
`GO6F 3/048
`(52) WSe Ve ceccccscsssseseseseseeeseee 709/219: 705/26; 715/810
`(57)
`ABSTRACT
`
`A method for downloading information from a remote server.
`The method includesreceiving, 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
`whichutilizes the banking card information, whereinthe first
`and second moblet software modules comprise device inde-
`pendent commandsof a generic syntax and wherein further
`the commands are executed by a device dependent software
`module also resident on the portable device.
`
`00
`
`Apple Ex. 1004, p. 1
`Apple Ex. 1004,p. 1
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`Ba
`
` ¥
`
`
`RESPONSIVE TO & USER REQUEST, THE PORTABLE DEVICE SENDING A MESSAGE
`TO 4 REMOTE SERVER TO DOWNLOAD A FIRST MOBLET SOFTWARE MODULE
`vali}
` y
`THE PORTABLE DEVICE RECEIVING FROM THE REMOVE SERVER A DEVICE
`DEPENDENT SOFTWARE MODULE
`
`U2 i
`
`¥
`THE PORTABLE DEVICE RECEIVING FROW THE REMOTE SERVER THE FIRST
`MOBLET SOFTWARE MODULE
`a4
`
`THE PORTABLE DEVICE EXECUTING THE FIRST MOBLET SOFTWARE MODULE USING|
`THE DEVICE DEPENDENT SOFTWARE MODULE
`OB
`LL
`
`RECEIVING CARD INFORMATION FOR A FIRST ACCOUNT AND STORING THE CARD
`INFORMATION IN A SECURE MEMORY
`113
`t
`THE FIRST MOBLET SOFTWARE NODULE AUTOMATICALLY SENDING A WIRELESS
`MESSAGE TO THE REMOTE SERVER TO INFORM THE REMOTE SERVER OF THE
`CARD INFORMATION BEING RECEIVED AT THE PORTABLE DEVICE
`120T
`¥
`THE PORTABLE DEVICE RECEIVING 2 SECOND MOBLET SOFTWARE MODULE |
`ASSOCIATED WITH THE CARD INFORMATION
`12
`
`
` THE PORTABLE DEVICE EXECUTING THE SECOND MOBLET SOFTWARE MODULE
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 2 of 10
`
`US 2010/0138518 Al
`
`SOIAMISCHLSIDfeetiew”TUWAMLIOS©TT|Se(COMCNL,WE)
`"09pONOMne|SpeeNOS
`
`Otay‘_ITQOH(0938)
`
`
`
`
`
`ifWM
`
`
`ee1
`
`(HSI)4a9¥NEWpe
`
`HONPUOFUpAeIHunyUeSly¥
`
`
`
`
`INAWETIALIMNOISTIAVAOWTE-NON
`
`082
`
`
`
`aytponyseasJOHPAUL
`
`HOHRITCH
`
`G02
`
`UoneayLONWe
`
`
`WIAUISLOWY
`
`
`
`A[NpOY]aTEMIOSya[qORYpuosas
`
`
`
`
`|_|FINCOWTHRMLIOSLITGOWLSHTZ
`
`ple
`
`i
`
`
`
`
`
`IRPOTaTeMIgOSjaTqOWIAL&Loyysonbay
`
`10g
`
`
`
`
`
`MPOY]aTEMIOyalqoyyysAy
`
`e02boneeeeceoyyreeoneeesneoneresneennanyfr.-een
`
`XK
`
`
`
`INTWNOWLANTXYLOH
`
`¢AYNDIA
`
`ge
`
`
`
`
`
`
`
`UOHEUMOFUpreaHuryweqpuovasyG02
`
`a2
`
`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 of 10
`
`US 2010/0138518 Al
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`FIGURE4
`
`Apple Ex. 1004, p. 5
`Apple Ex. 1004, p. 5
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 6 of 10
`
`US 2010/0138518 Al
`
`FIGURE5D
`
`FIGURE5C
`
`
`
`
`
`
`
`Apple Ex. 1004, p. 7
`Apple Ex. 1004, p. 7
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 8 of 10
`
`US 2010/0138518 Al
`
`
`
`
`
`
`
`
` FIGURE6C
`
`
`
`Apple Ex. 1004, p. 9
`Apple Ex. 1004, p. 9
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`Patent Application Publication
`
`Jun. 3, 2010 Sheet 10 of 10
`
`US 2010/0138518 Al
`
`
`
`RECEIVING CARD INFORMATION FOR A SECOND ACCOUNT AND STORING THE CARD
`INFORMATION FOR THE SECOND ACCOUNT IN A SECURE MEMORY
`T26
`
`THE FIRST MOBLET SOFTWARE MODULE AUTOMATICALLY SENDING A WIRELESS
`MESSAGE TO THE REMOTE SERVER TO INFORM THE REMOTE SERVER THAT THE
`CARD INFORMATION FOR THE SECOND ACCOUNT IS BEING RECEIVED AT THE
`PORTABLE DEVICE
`128
`
`THE PORTABLE DEVICE RECEIVING A THIRD MOBLET SOFTWARE MODULE
`ASSOCIATED WITH THE CARD INFORMATION FOR THE SECOND ACCOUNT
`130
`
`
`134
`
`THE PORTABLE DEVICE EXECUTING THE THIRD MOBLET SOFTWARE MODULE
`182
`
`DISPLAYING GRAPHICAL ICONS OF THE SECOND AND THE THIRD MOBLET
`SOFTWARE MODULES ON A DISPLAY
`
`FIGURE 7B
`
`Apple Ex. 1004, p. 11
`Apple Ex. 1004, p. 11
` Apple v. Fintiv
`Apple v. Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 Al
`
`Jun. 3, 2010
`
`modules. Itis appreciated that the second andthethird moblet
`software modules may be controlled byoperationsofthe first
`moblet software module.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`
`
`[0015] Embodiments of the present invention are illus-
`trated by way ofexample, and not by wayoflimitation, in the
`figures of the accompanying drawings and in which like ref-
`erence numerals refer to similar elements and in which:
`[0016]
`TIG.1 shows an exemplary system for downloading
`information to an electronic wallet comprising a removable
`security element in accordance with one embodiment ofthe
`presentinvention.
`[0017]
`FIG.2 shows an exemplary systemfor downloading
`information to an electronic wallet comprising a non-remov-
`able security clement in accordance with one embodiment of
`the present invention.
`[0018]
`TIG.3 illustrates a general purpose computer sys-
`tem that may serve as a platform for embodiments ofthe
`present invention.
`[0019]
`FIG. 4 shows a MOJAX enabled wallet component
`architecture in accordance with one embodiment of the
`present invention.
`[0020]
`FIGS. 5A-5D show an exemplary embedded. card
`personalization in accordance with one embodimentof the
`present invention.
`[0021]
`FIGS. 6A-6D show externalized card personaliza-
`tion in accordance with one embodimentof the present inven-
`tion.
`FIGS. 7A and 7B show an exemplaryflow diagram
`[0022]
`for downloading information into a secure clement in accor-
`dance with one embodiment ofthe present invention.
`
`DETAILED DESCRIPTION
`
`[0023] Reference will now be made in detail to embodi-
`ments of the present invention, examples of whichare illus-
`trated in the accompanying drawings. While the invention
`will be described in conjunction 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.
`Turthermore,
`in the following detailed description of the
`present invention, numerous 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 maybe practiced without
`these specific details. In other instances, well known meth-
`ods, procedures, components, and circuits have not been
`described in detail as not ta unnecessarily obscure aspects of
`the invention.
`
`Notation and Nomenclature
`
`Someportions 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 can be performed ontelevision set
`memory. These descriptions and representations are the
`means used by those skilled in the art to most effectively
`conveythe substance oftheir work to others skilled intheart.
`A procedure,lelevision sel 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. Thestepsare those requiring physical manipu-
`lations of physical quantities.
`these quantities
`[0025] Usually,
`though not necessarily,
`take the formofelectrical 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 commonusage, to
`refer to these signalsas bits, values, elements, symbols, char-
`acters, terms, numbers, or the like.
`[0026]
`It should be bornein mind, however,that all ofthese
`and similar terms are to be associated with the appropriate
`physical quantities and are merely convenient labels applied
`lo these quantities. Unless specifically stated otherwise as
`apparent fromthe following discussions,it is appreciated that
`throughoutthe present invention, discussions utilizing terms
`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 ofa 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 Methodand System for Downloading Information
`into a Secure Element of an Electronic Device
`
`[0027] Referring nowto FIG. 1, an exemplary system 100
`for downloading informationto an electronic wallet compris-
`ing, a removable security element in accordance with one
`embodimentof 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, acellular
`phone, a personal digital assistant (PDA), ctc., a trusted ser-
`vice manager (TSM) 120 and a remote server 130.
`[0028] The electronic device 110 maybe a portable elec-
`tronic device that can be used to pay for purchases onthe 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] TheTSM 120isa trusted entity in charge of sending
`secure information, e.g., financial information, 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 maybe verified and
`authenticated. Tt is appreciated that although embodiments
`herein are described with respect to banking information and
`bank accounts, the information maybe 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 loyaltycard, etc. As such,the
`use of banking information is exemplaryand not intended to
`limit the scope ofthe present invention. After verification of
`the useridentity and authentication ofthe user, the TSM 120
`maytransmit the banking information regarding the Bank of
`America account (for instance) to the electronic device 110.
`[0030] The remote server 130 mayprovide 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
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 Al
`
`Jun. 3, 2010
`
`[0041] According to one embodimentofthe present inven-
`tion, the first, the second andthe third moblet software mod-
`ules include device independent commandsof a generic syn-
`tax. In one embodiment, the first, the second and the third
`moblet software modules may be written using MOJAX com-
`mands, MOJAX is a language that enables manipulation ofa
`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 onthe electronic device 110 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 construedas limiting the scope ofthe present invention. As
`such, any kind of information and moblet software module
`maybe transmitted and installed within the MOJAX environ-
`ment. For example, non-associated modules, c.g., coupon
`information, advertising, ctc., may be transmitted and
`installed without requiring the TSM 120to interact with the
`TSA 102 andto 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/oruser initiation.
`
`[0044] Referring now to FIG. 2, an exemplary system 200
`for downloading information to an electronic wallet compris-
`ing anon-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]
`Itis appreciated that a first moblet software module
`204 maybe installed during manufacturing ofthe 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 maytransmit 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 environment.It is appre-
`ciated that in one embodiment the device dependent software
`maybe 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.
`Tt is appreciated that according to one embodiment of the
`present invention, the non-removable security element 202is
`near field communication (NFC) enabled.
`[0047]
`It is appreciated thatthefirst moblet software mod-
`ule 204 becomesoperable 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-
`ronment. For example, moblet software modules are operable
`ina MOJAX environmentoperating ona 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 environment mayhave 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-
`played moblet software modules maybe executed uponselec-
`ion thereof.
`
`Thefirst banking card information 205 may be com-
`[0048]
`municated to the non-removable security element 202 from
`he TSM220 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
`banking 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
`ransmil an acknowledgementsignal to the TSM 220that the
`first banking card information 205 has been received and
`stored.
`‘Lhe first moblet software module 204 maynotify
`[0049]
`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 responseto the notification 209,
`the remote server 230 may automatically transmit 211¢ sec-
`ond moblet software module to the first moblet software
`module 204. It is appreciated that the second moblet software
`module maybe an applicationrelated to the first banking card
`information 205. Thefirst 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 maybe used in conjunction with the execu-
`tion of the second moblet software module 206 to enable the
`userto 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 maybe 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
`initialed request.
`[0051]
`Itis appreciated that additional banking card infor-
`mation and moblet software modules associated therewith
`maybe 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
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 Al
`
`Jun. 3, 2010
`
`dent syntax that is only MOJAX-specific. It is appreciated
`that the componentarchitecture 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 moblets 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 dedi-
`cated gateways. Moblets pass control between themselves for
`interaction. Moblet 420a maypass control to moblet 4206 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 4205 becomesactive,in this
`example. Only registered moblets can be launched andif 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
`GUIenvironmentthat allowsuser selection of the other mob-
`lets 420a-420/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 420a-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 componentarchi-
`tecture mayalso contain several plug-ins as shown as 440a-
`440e. 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.
`Plugins 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 embodimentof the
`present invention. The embedded card personalization com-
`prises a secure element that is embedded within the device.
`The TSA agent and a wallet moblet operate within the MRF.
`The TSA agent performs all the interactions with the secure
`element. For example, referring to FIG. 5B, TSMpushes a
`new card applet into the TSA agent. In one embodiment,the
`new card applet may be banking information.Asa result, the
`TSA agent communicates and pushes the received informa-
`tion into the secure element. Referring now to FIG. 5C, the
`TSA agent notifies the wallet moblet operating within the
`MOJAX environmentthat the information from the TSM has
`been received. Referring now ta FIG. 5D,the wallet moblet in
`responseto the notification from the TSA agent request a card
`moblet from the wallet registry. ln responseto the request, the
`wallet registry transmits the card moblet to the wallel MRE
`where the card mobletis installed within the MOJAX envi-
`ronment.
`
`
`
`
`
`FIGS. 6A-6D show externalized card personaliza-
`[0064]
`tion in accordance with one embodimentofthe present inven-
`tion. Externalized 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 nowto
`FIG. 6B, the TSM pushesthe new card applet into the remov-
`able secure element. Referring, now to FIG. 6C, the TSM
`nolifies the wallet moblet operating within the wallet MRE,
`e.g., MOJAX environment,
`that
`the new card applet
`is
`
`installed. Referring now to FIG. 6D, the wallet moblet in
`response to receiving the notification from the TSM may send
`a request for a card mobletto the wallet registry. In response
`to the request, the wallet registry may transmit the card mob-
`let to the wallet MRE where the card mobletis installed.
`[0065] Referring now to FIGS. 7A and 7B, an exemplary
`flow diagram 700 for downloading informationinto 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 downloada 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 sofiware module from the remote servervia a wireless
`network.
`[0067] At step 716, the portable device executes thefirst
`moblet software module using the device dependent software
`module, It is appreciated that according to one embodiment,
`the device dependent moduleresides on the portable device.
`The portable device receives card information associated
`witha first account andstoresthe card informationin a secure
`memory within the portable device, at step 718.
`[0068] Al step 720, the first moblet software module auto-
`matically sends a wireless message, e.g., via a wireless net-
`work, to the remoteserver to inform the remote serverthat the
`card information is being reccived at the portable device. In
`one embodiment, the automatic transmission of the wireless
`messageat step 720 is responsive to the receiving of the card
`informationat step 718.
`[0069] According to one embodiment, at step 722, the por-
`table device receives, e.g., wirelessly via a wireless network,
`a second moblet software module associated with the card
`information. In one embodiment, the second moblet software
`moduleis received in a mannerthatis transparent to the user
`of the portable device. The portable device executes the sec-
`ond moblet software module that utilizes the card informa-
`tion, at step 724. It is appreciated that according to one
`embodiment, the first and the second moblet 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 com-
`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 message to the remote server to inform the remote server
`that the card information for the second account is being
`received by the portable device. Tt 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.Atstep
`732, the portable device executes the third moblet software
`module that utilizes the card information for the second
`account.
`
`tis appreciated that the third moblet sofiware mod-
`[0071]
`ule comprises device independent commandsofthe generic
`
`Apple Ex. 1004, p. 17
`Apple Ex. 1004, p. 17
` Apple v. Fintiv
`Apple v.Fintiv
`IPR2020-00019
`IPR2020-00019
`
`

`

`US 2010/0138518 Al
`
`Jun. 3, 2010
`
`
`
`
`
`
`
`
`
`12. The electronic device as described in claim 10, whercin
`21. The electronic device as described in claim 10, wherein
`said removable security clement comprisesa near ficld com-
`said removable security clementis a subscriberidentity mod-
`munication chip.
`ule (SIM)card.
`13. The electronic device as described in claim 10, wherein
`22. Anelectronic device comprising:
`a processor for processing, data;
`said receiving said second moblet software module is per-
`a non-removable security element operable to store secu-
`formedtransparently to a user ofsaid electronic device.
`rity data, wherein said non-removable security element
`14. The electronic device as described in claim 10, wherein
`automatically receives and stores card information for a
`said receiving said second moblet software module is per-
`first accountfromatrusted service manager (TSM); and
`formed responsiveto a user request operating said electronic
`device.
`a memory component operable to store data, wherein said
`memory component comprises instructions that when
`15. The electronic device as described in claim 10, wherein
`executed implement a method for downloading infor-
`said method further comprises:
`mation from a remote server, said method comprising:
`automatically receiving an update for said second moblet
`software module.
`subsequent
`to said non-removable security element
`receiving said card informationforsaidfirst account,
`16. The electronic device as described in claim 10, wherein
`a first moblet software module automaticallyreceiv-
`said second moblct software module is received wirelessly.
`ing a signal from said. TSM that said card information
`17. The electronic device as described in claim 10, wherein
`for said first accountis received;
`said method further comprises:
`responsive to said receiving, a first moblet software
`executing said second moblet software module that utilizes
`module automatically transmitting, a signal to said
`said card information for saidfirst account.
`remote server to notify said remote server that said
`18. The electronic device as described in claim 10, wherein
`card information is transmitted; and
`said method further comprises:
`said first moblet software module receiving a second
`moblet software module associated with said card
`responsive a user request, said electronic device transmit-
`information.
`ting a signal to said remote server to downloadsaid first
`23. The electronic device as described in claim 22, wherein
`moblet software module and indicating therein a device
`type of said electronic device;
`said first and said second moblet software modules comprise
`device independent commands of a generic syntax, and
`said electronic device receiving from said remote server a
`wherein further said device independent commands are
`device dependent software module via a wireless net-
`work;
`executed by a device dependent software module resident on
`said electronic device.
`said electronic device receiving from said remote server
`said first moblet software module via a wireless net-
`24. The electronic device as described in claim 22, wherein
`said electronic device is a cellular phone.
`work; and
`25. The electronic device as described in claim 22, wherein
`said electronic device executing said first moblet software
`said receiving said second moblet software module is per-
`module using said device dependent software module.
`formedtransparentlyto a user of said electronic device.
`19. The electronic device as described in claim 10, wherein
`26. The electronic device as described in claim 22, wherein
`said method further comprises:
`said receiving said second moblet software module is per-
`receiving a second card information for a second account;
`formed responsive to a user request operating said electronic
`device.
`storing said second card information for said second
`accountinlo said removable securily element;
`27. The electronic device as described in claim 22, wherein
`responsive to said receiving said second card information,
`said method further comprises:
`said first moblet software module automatically trans-
`automatically receiving an update for said second moblet
`software module.
`milling a second signal to said remote server to notify
`said remote server that said second card information is
`28. The electronic device as described in claim 22, wherein
`received; and
`said second moblet software moduleis received wirelessly.
`in response to said transmilling said second signal, said
`29. The electronic device as described in claim 22, wherein
`first moblet software module receiving a third moblet
`said method further comprises:
`software module associated with said second cardinfor-
`executing said second moblet software modulethat utilizes
`said card informationfor said first account.
`mation for said second account; and
`executing said third moblet software module that utilizes
`30. The electronic device as described in claim 22, wherein
`said second card information for said second account,
`said method further comprises:
`wherein said third moblet software module comprise
`responsive a user request, said electronic device transmit-
`device independent commandsof a generic syntax and
`ting a signal to said remote server to downloadsaidfirst
`whereinfurther said commandsare executed by a device
`moblet software module and indicating therein a device
`dependent software module.
`type of said electronic device:
`20. The electronic device as described in claim 19, wherein
`said electronic device receiving fromsaid remote server a
`said method further comprises:
`device dependent software module via a wireless net-
`work;
`displaying graphical icons for said. second and. said. third
`moblet software modules on a display, wherein said
`said clectronic device recciving from said remote server
`said. first moblet software module via a wireless net-
`displaying is operable to allow a user selection thereof,
`work; and
`and wherein display and selection of said second and
`said third moblet sofiware modules are controlled by
`said electronic device executing said first moblet softwar