`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 1 of 17
`
`EXHIBIT O
`EXHIBIT O
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 2 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 2 of 17
`
`EXHIBIT B
`EXHIBIT B
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 3 of 17
`ee= STATTAA
`
`US008448855B1
`
`US8,448,855 B1
`(10) Patent No.:
`a2) United States Patent
`Kohetal.
`(45) Date of Patent:
`May28, 2013
`
`
`(54) METHOD AND APPARATUS FOR FUNDING
`AN ELECTRONIC PURSE
`
`USPC wee 235/380; 235/379; 705/64; 705/65;
`705/66; 705/67
`
`(75)
`
`Inventors: Liang Seng Koh, Fremont, CA (US):
`putone Cho, xCRCUS)B WS); isin
`an, Fremont,
`San Jose, CA (US)
`
`; Fuliang
`
`Cho,
`
`(73) Assignees: Rich House Global Technology Ltd.,
`Shenzhen (CN); RFCyber Corp.,
`Fremont, CA (US)
`
`(*) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`21)
`
`PP
`Appl. No.: 13/400,038
`
`(22) Filed
`
`iled:
`
`eb.
`
`filed on
`
`Feb. 18. 20102
`,
`Related U.S. Application Data
`(63) Continuation ofapplication No. 11/534,653,
`Sen.
`24. 2006 Ye No.8 Ul 8.218 _—
`ep.
`a"
`2 OW Bab
`INO:
`Osh
`LOsk
`18:
`Int.Cl
`(2012.01)
`G060 000
`(2006.01)
`G060 20/36
`(2006.01)
`G06O 20/38
`,
`(52) US. Cl
`.
`a
`CPC we G06@Q 20/367 (2013.01); GO6Q 20/3672
`(2013.01); G06Q 20/3674 (2013.01); G06Q
`20/38 (2013.01); GO6Q 20/382 (2013.01)
`
`(51)
`
`(58) Field of Classification Search
`USPC vcccccecsessessessessessesseessenesseeees 235/379, 380, 492
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`2002/0145632 Al* 10/2002 Shmuelietal.
`....0.0.... 345/835
`
`7/2003 Sarcanin.........
`. 713/172
`2003/0145205 Al*
`2005/0222961 Al* 10/2005 Staib etal.
`..
`. 705/64
`
`-- 370/389
`2006/0171383 A1*
`8/2006 Davydov....
`* cited by examiner
`
`Primary Examiner — Thien M Le
`P
`Assistant Examiner — Christopher Stanford
`
`(74) Attorney, Agent, or Firm — Joe Zheng
`(57)
`ABSTRACT
`Techniques for funding an electronic purse (e-purse) are dis-
`closed. According to one aspect of the invention, a mecha-
`nism is provided to enable a portable device to conduct trans-
`actions over an open network with a paymentserver without
`compromising security. In one embodiment, a device is
`loaded with an e-purse manager. The e-purse manager is
`configured to managevarious transactions and functions as a
`mechanism to access an e-purse therein. The e-purse is
`funded by interactions among the e-purse manager, a pay-
`mentserver and a financial institution (its server) that main-
`tains an accounttherefor.
`
`17 Claims, 9 Drawing Sheets
`
`
`
`Module
`
`440
`
`Payment network
`and servers
`
`442
`
`Financing
`Bank
`
`444 SAM
`
`Purse
`
`manager
`midlet
`
`438
`
`ene
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 4 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 4 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 1 of 9
`
`US 8,448,855 B1
`
`FIG.1A
`
`100
`
`>_
`
`=>o
`
`© O
`
`104
`
`
`
`E-Pursesecurity
`
`102
`
`
`
`Physicalsecurity
`
`O®”— oo
`
`d)
`
`©C
`
`c© = O
`
`o—
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 5 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 5 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 2 of 9
`
`US 8,448,855 B1
`
`OLL
`
`a|6uls
`
`9|Bulgainoexy
`
`uoHoUNL
`esind-F
`
`0]SPUBLULUOD
`
`uoloun,sesjoe
`
`
`
`OL
`
`s6e}
`
`GbSls
`
`s6e]sso00e
`
`Jedsey
`
`VILL
`
`9}e)
`
`NddvJOsousnbes
`
`peseq
`
`pueq
`
`
`
`esind-9juaws|dul
`
`yJOMOU
`
`0}SPUBLULUOD
`JOWVS
`
`
`
`seyonssuoljesado
`
`aseyoind‘peo|
`
`esind-9
`
`clLL
`
`JOAJOS
`
`
`
`
`
`
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 6 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 6 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 3 of 9
`
`US 8,448,855 B1
`
`00¢
`
`ELSWvSs
`
`ainpoyy
`
`asindW
`
`junoes
`
`
`
`juebeqayIOMOUJUBA
`
`
`
`
`
`breOdUoOleSJOAJOSPUB
`
`
`
`
`
`Jo)saempseyBunsixy
`
`
`
`202peowewsZ"c)||YIMBUOY[18D
`
`ainpow
`
`uoYING19\dde
`
`UUMdd
`
`90zZplomssed
`
`4IN0}ss909e
`
`asund-J
`
`
`
`BdJBWULWWODPEseq-pue|
`
`ul(uolewodsue.)
`
`
`
`JO$9101S‘°B'9)
`
`
`
`Japea!qI4y
`
`
`
`
`JUSWUOIIAUSpesojousQIJSWWO9-F
`
`90JSLULUOD-|/\]
`
`
`
`jeuoyounsajBuis29WBWS
`
`
`
`
`
`jodo10/dpiedjo90]0/d
`
`
`
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 7 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 7 of 17
`
`U.S. Patent
`
`May 28, 2013
`
`Sheet 4 of 9
`
`US 8,448,855 B1
`
`VeOs
`
`VLE
`
`Joyejnue
`
`aINpoy
`
`
`!Jebeuewpied|:
`
`
`ble |[Z1Eyaddy
`
`esund-J
`
`
`
`80€|sodsuew)UONEZI|EUOSJ8d
`
`
`
`
`Lone,uoneaddy
`
`00&
`
`Bunsixy
`
`pezuouiny
`
`JSUUOSISA
`
`-3]MON
`
`asund
`
`VS
`
`a|Npoy|
`
`Jepeoy
`
`dlsu
`
`OLE
`
`
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 8 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 8 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 5 of 9
`
`US 8,448,855 B1
`
`GéSls
`
`peereeeeeeeeeeeeee
`
`Joye;nwe
`
`ble !yolddy!!JoBeuewpied3
`
`esind-J
`
`
`
`
`
`JOIPIN
`
` CCE
`
`OE
`
`
`
`80€)sodsuesy
`
`Bunsixy
`
`9g|NPoW
`
`UoNe}
`
`Vs
`
`-qMON
`
`9sind
`
`9g|NPoW
`
`Vs
`
`pueYJOM}eU
`
`juawAed
`
`SIOAIOS
`
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 9 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 9 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 6 of 9
`
`US 8,448,855 B1
`
`8
`
`09
`
`COE
`
`JEVA
`
`G CN&A
`
`
`
`q|6e1suipuewsBunsixsdu}BIAJOle|NWSUeJOSASYPASWUOISUBJ)B]eIBUS
`
`
`
`SOIAVP3}Ul}a\ddedsund-3uepueWySUOHeLWodsue,)BusixsueUsaMjeq
`
`
`
`YS9sund-9mauau}UgeMjegSuidpueSAByUOI}euedoOSsind-9sleusUusy)
`
`BdIAVP9}UlJa|\ddeasind-duePURVSesund-9MoUUeUsEM\Nq
`
`
`g9¢,PEZI|2UOSIAd,JOa}e}SBO}BSINd-99u]JES
`
`
`
`
`
`
`jauueyoAjuNdeseBUsI|qe}seoO}uleWOpANDESUOHeoI|ddeasq
`
`
`
`
`jauueyoAyNdasBUSI|Ge}]seoO}UIBWOpAjNoSssUOIeol|ddeasp
`
`
`
`SOIASP9u}Ul1e|ddessund-9suepukeWsBulsixeay]Usemieq
`
`
`q|62)au)pueWsBulsixeueBIASplomssed4A)e1eJ9UaD
`
`Jo}Je|NWSdy}pue[IVSBuysixssu}uUsamjeq
`
`
`
`uonezijeuosied9121)/U]
`
`pued9u}Wowq|be}eyopeasy
`
`
`
`SdIANP9}UlJe|ddessund-auepue
`
`€
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 10 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 10 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 7 of 9
`
`US 8,448,855 B1
`
`O0v
`
`
`
`90]9]pluSu]0]Bsuodsayesesodwosdasund-g
`
`
`
`asuodsel3y}
`
`&PSIJOA
`
`
`
`
`
`19|\ddeasund-s0]1sanbsa&SpUadsJ9)/pI|
`
`
`
`
`
`JaBeuewasindau}$$e00e0}Nid
`
`VrSIs
`
`
`
`yueqSu}WO)esuodseBeaAls0ey
`
`
`
`chyJa]SUBI]PUNes12I11UIpue1UNOSDNeBulpuodse.09eBAIS)
`
`
`
`PSIJIIBAI‘yueqgBuluosuodse0}ySsenbe.
`
`
`
`
`
`vorpijeABuejusJayee|piweBIAysOnbae91eI1/U]
`
`
`
`
`
`
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 11 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 11 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 8 of 9
`
`US 8,448,855 B1
`
`GySls
`
`eX
`
`CCV
`
`BSLV
`
`au}PueMUO4
`asind-998U}0}W8U]PUSSPUSPUBLUWODAGdy10e1X9puedisJ9/PI|/\
`
`
`
`asuodsasAGdvVUeS8l1E|NWIO!1eU}19/P!WSU}O}1949!)eSB]eIBUdS
`
`
`
`
`SPUBLUWOOSpUuaspUeAjONUBUINeAGdV8}SAlJaABsund-y
`
`
`
`
`UONPOIJIIBA912]JO}poulejes$1esuodselAdaeu}Jaye
`
`
`oBessewyOMJOUeBUlpappequiaesuOodseJ
`
`
`
`
`
`}9|pilWJo}aBessewsnjejs|nysseoonseajeJAUay)
`
`
`Bo}uonoesuesesayepdnpueJoejnwe9U)0}
`
`
`JOAIOSJUsWAed9}0}ISENbSYIOMISUeCUI
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 12 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 12 of 17
`
`U.S. Patent
`
`May28, 2013
`
`Sheet 9 of 9
`
`US 8,448,855 B1
`
`cvOvrvv
`
`Joyejnue
`
`JySIA }9|P!lu
`
`
`Buloueul4yiomjoujusWAeNVS
`yuegSJIOAJOSpueg|npoy
`
`
`9sind
`
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 13 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 13 of 17
`
`US 8,448,855 B1
`
`1
`METHOD AND APPARATUS FOR FUNDING
`AN ELECTRONIC PURSE
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`10
`
`20
`
`30
`
`40
`
`45
`
`50
`
`55
`
`This application is a continuation of U.S. patent applica-
`tion Ser. No. 11/534,653, filed on Sep. 24, 2006, now U.S. Pat.
`No. 8,118,218.
`
`BACKGROUND
`
`1. Technical Field
`
`The present invention is generally related to commerce
`over networks. Particularly, the present inventionis related to
`electronic purses that can be advantageously used in portable
`devices configured for both electronic commerce (a.k.a.,
`e-commerce) and mobile commerce(a.k.a., m-commerce).
`2. Description of the Related Art
`Single functional cards have been successfully used in
`enclosed environments such as transportation systems. One
`example of such single functional cards is MIFAREthatis the
`most widely installed contactless smart card technology in
`the world. With more than 500 million smart card ICs and 5
`
`million reader components sold, MIFAREhasbeen selected
`as the most successful contactless smart card technology.
`MIFAREis the perfect solution for applications like loyalty
`and vending cards, roadtolling,city cards, access control and
`gaming.
`It is noticed that such enclosed systemsare difficult to be
`expanded into other areas such as e-commerce and m-com-
`merce because stored values and transaction information are
`
`stored in data storage of each tag that is protected by a set of
`keys. The natureofthe tag is that the keys needto be delivered
`to the card for authentication before data can be accessed
`
`during a transaction. This constraint makes systems using
`such technologydifficult to be expanded to an open environ-
`ment such as the Internet for e-commerce and cellular net-
`works for m-commerce as the key delivery over a public
`domain network causes security concerns.
`There is, thus, a need for a mechanism in devices, espe-
`cially portable devices, functioning as an electronic purse
`(e-purse) to be able to conduct transactions over an open
`network with a payment server without compromising secu-
`rity.
`
`SUMMARY
`
`This section is for the purpose of summarizing some
`aspects ofembodimentsofthe present invention and to briefly
`introduce some preferred embodiments. Simplifications or
`omissions in this section as well as thetitle and the abstract of
`this disclosure may be madeto avoid obscuring the purpose of
`the section,thetitle and the abstract. Such simplifications or
`omissions are not intended to limit the scope of the present
`invention.
`
`Broadly speaking, the invention is related to a mechanism
`provided to devices, especially portable devices, functioning
`as an electronic purse (e-purse) to be able to conduct trans-
`actions over an open network with a paymentserver without
`compromising security. According to one aspect of the
`present invention,a device is loaded with an e-purse manager.
`The e-purse manageris configured to manage varioustrans-
`actions and functions as a mechanism to access an emulator
`therein. The transactions may be conducted over a wired
`network or a wireless network.
`
`2
`According to another aspect of the present invention, a
`three-tier security model is proposed, based on which the
`present invention is contemplated to operate. The three-tier
`security model includes a physical security, an e-purse secu-
`rity andacard managersecurity, concentrically encapsulating
`one with another. Security keys (either symmetric or asym-
`metric) are personalized within the three-tier security model
`so as to personalize an e-purse and perform secured transac-
`tion with a paymentserver. In one embodiment, the essential
`data to be personalized into an e-purse include one or more
`operation keys (e.g., a load key and a purchase key), default
`PINs, administration keys (e.g., an unblock PIN key and a
`reload PIN key), and passwords(e.g., from Mifare). During a
`transaction, the security keys are used to establish a secured
`channel between an embeddede-purse and an SAM (Security
`Authentication Module) or backendserver.
`The invention may be implemented in numerous ways,
`including a method, system, and device. In one embodiment,
`the present invention is a method for providing an e-purse, the
`method comprises providing a portable device embedded
`with a smart card module pre-loaded with an emulator, the
`portable device including a memory space loaded with a
`midletthat is configuredto facilitate communication between
`an e-purse applet therein and a paymentserver over a wireless
`network, wherein the portable device further includes a con-
`tactless interfacethat facilitates communication between the
`e-purse applet therein and the paymentserver, and personal-
`izing the e-purse applet by reading off data from the smart
`card to generate one or more operation keys that are subse-
`quently used to establish a secured channel between the
`e-purse and a SAM or a paymentserver.
`According to another embodiment, the present invention is
`a system for providing an e-purse, the system comprises a
`portable device embedded with a smart card module pre-
`loaded with an emulator, the portable device including a
`memory space loaded with a midlet that is configured to
`facilitate wireless communication between an e-purse applet
`therein and a payment server over a wireless network, the
`portable device further including a contactless interface that
`facilitates communication between the e-purse applet therein
`and the paymentserver, the payment server associated with
`an issuer of the e-purse, and a SAM module configured to
`enable the e-purse, wherein the SAM module is behind the
`payment server when the e-purse is caused to communicate
`with the payment server via the midlet over a wireless net-
`work (M-commercein FIG.2) or via the agent on a PC over
`a wired network (E-commercein FIG.2).
`Accordingly one of the objects of the present inventions is
`to provide a mechanism to be embeddedin devices, especially
`portable devices, to function as an electronic purse (e-purse)
`to be able to conduct transactions over an open network with
`a paymentserver without compromising security.
`Other objects, features, and advantages of the present
`invention will become apparent upon examining the follow-
`ing detailed description of an embodimentthereof, taken in
`conjunction with the attached drawings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The invention will be readily understood by the following
`detailed description in conjunction with the accompanying
`drawings, wherein like reference numerals designate like
`structural elements, and in which:
`FIG. 1A showsa three-tier security model based on which
`the present invention is contemplated to operate according to
`one embodimentthereof;
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 14 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 14 of 17
`
`US 8,448,855 B1
`
`3
`FIG. 1B showsa data flow in accordance withthethree-tier
`
`security model amongthree entities;
`FIG. 2 shows an exemplary architecture diagram according
`to one embodimentofthe present invention;
`FIG. 3A a block diagram of related modules interacting
`with each other to achieve whatis referred to herein as e-purse
`personalization by an authorized person as shownin FIG.2;
`FIG. 3B showsa block diagram ofrelated modules inter-
`acting with each other to achieve whatis referred to herein as
`e-purse personalization by a user of the e-purse as shown in
`FIG.2;
`FIG. 3C showsa flowchart or process of personalizing an
`e-purse according to one embodiment of the present inven-
`tion;
`FIG. 4A and FIG.4B show togethera flowchart or process
`of financing an e-purse according to one embodimentof the
`present invention; and
`FIG. 4C shows an exemplary block diagram of related
`blocksinteracting with each otherto achieve the process FIG.
`4A.
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`In the following description, numerousspecific details are
`set forth to provide a thorough understanding of the present
`invention. The present invention may be practiced without
`these specific details. The description and representation
`herein are the means used by those experiencedor skilled in
`the art to effectively convey the substance of their work to
`others skilled in theart. In other instances, well-known meth-
`ods, procedures, components, and circuitry have not been
`described in detail since they are already well understood and
`to avoid unnecessarily obscuring aspects ofthe present inven-
`tion.
`Reference herein to “one embodiment” or “an embodi-
`
`ment” meansthat a particular feature, structure, or character-
`istic described in connection with the embodiment can be
`includedin at least one implementation of the invention. The
`appearances of the phrase “in one embodiment”in various
`places in the specification are not necessarily all referring to
`the same embodiment,norare separate or alternative embodi-
`ments mutually exclusive of other embodiments. Further, the
`order of blocksin process, flowcharts or functional diagrams
`representing one or more embodiments do not inherently
`indicate any particular order nor imply limitations in the
`invention.
`Embodimentsofthe present invention are discussed herein
`with reference to FIGS. 1A-4C. However, those skilled in the
`art will readily appreciate that the detailed description given
`herein with respect to these figures is for explanatory pur-
`poses only as the invention extends beyond these limited
`embodiments.
`
`FIG. 1A showsa three-tier security model 100 based on
`which the present
`invention is contemplated to operate
`according to one embodimentthereof. The three-tier security
`model 100 includes physical security 102, e-purse security
`104 and card managersecurity 106.
`Physical security 102 refers to a security mechanism pro-
`vided by a single functional card to protect data stored on the
`card. The card may be hardware implemented or software
`emulated running on a type of media. Data on a single func-
`tion card is protected by a set of access keys. These keys are
`configured onto the card when the card is issued. To avoid
`obscuring aspects ofthe present invention, the process ofhow
`the keys are configured onto the cards is to be omitted. For
`accessing the data, related keys are delivered to a reader for
`authentication.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`E-purse security 104 defines a set of protocols that enable
`micro paymenttransactions to be carried out in both wired
`and wireless environments. With an electronic purse (a.k.a.,
`e-purse) stored on a smart card, a set of keys (either symmet-
`ric or asymmetric) is personalized into the purse when the
`purse is being issued. During a transaction, the purse uses a
`set of respective keys for encryption and MAC computation
`in order to secure the message channel betweenthe purse and
`the SAM or backendservers. For a single functional card, the
`e-purse security 104 will act as gates to protect actual opera-
`tions performed on a single functional card. During person-
`alization, the single functional card access keys(or its trans-
`formation) are personalized into the purse with the purse
`transaction keys.
`Card ManagerSecurity 106, referring to a general security
`framework of a preload operating system in a smart card,
`provides a platform for PIN managementandsecurity chan-
`nels (security domains) for card personalization. This plat-
`form via a card managercan be usedto personalize a purse in
`one embodiment. One example of the card manager security
`106 is whatis referred to as a Global Platform (GP) that is a
`cross-industry membership organization created to advance
`standards for smart card growth. A GP combinestheinterests
`of smart card issuers, vendors, industry groups, public entities
`and technology companies to define requirements and tech-
`nology standards for multiple application smart cards. In one
`embodiment, a global platform security is used to personalize
`a smart card. As a result, both e-purse keys and card access
`keys are personalized into the target tag.
`FIG. 1B showsa data flow in accordancewiththe three-tier
`
`security model amongthree entities a land-based SAM or a
`network e-purse server 112, e-purse 114 acting as a gate
`keeper, and a single function tag 116. According to one
`embodiment of the present
`invention, communications
`between the land-based SAM or the network e-purse server
`112 and the e-purse 114 are conducted in sequenceof a type
`of commands(e.g., APDU) while communications between
`the e-purse 114 andthe single function tag 116 are conducted
`in sequence of another type of commands, wherein the
`e-purse 114 acts as the gate keeper to ensure only secured and
`authorized data transactions could happen.
`In reference to FIG. 1A,the physical security is realized in
`an emulator. As used herein, an emulator means a hardware
`device or a program that pretends to be another particular
`device or program that other components expect to interact
`with. The e-purse security is realized between one or more
`applets configured to provide e-purse functioning and a pay-
`mentserver. The card managersecurity (e.g., global platform
`security) is realized via a card manager to update security
`keys to establish appropriate channels for
`interactions
`betweenthe server andthe applets, wherein the e-purse applet
`(s) acts as a gatekeeper to regulate or control
`the data
`exchange.
`According to one embodiment, a smart card has a pre-
`loaded smart card operating system that provides security
`framework to control the access to the smart card (e.g., an
`installation of external applications into the smart card). In
`order to managethe life cycle of an external application, a
`card manager module is configured by using the smart card
`security framework. For instance, a Java-based smart card,
`SmartMX,is preloaded with an operating system JCOP 4.1.
`The Global Platform 2.1 installed on the SmartMX performs
`the card managerfunctionality.
`Referring now to FIG. 2, there shows an exemplary archi-
`tecture diagram 200 according to one embodiment of the
`present invention. The diagram 200 includes a cellphone 202
`embedded with a smart card module. An example of such a
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 15 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 15 of 17
`
`US 8,448,855 B1
`
`5
`cell phone is a near field communication (NFC) enabled
`cellphone that includes a Smart MX (SMX) module. The
`SMX is pre-loaded with a Mifare emulator 208 (which is a
`single functional card) for storing values. The cellphone is
`equipped with a RFID interface (e.g., ISO 144443) that
`allows the cellphoneto act as a tag. In addition, the SMX is a
`JavaCard that can run Java applets. According to one embodi-
`ment, an e-purse is built on top of the global platform and
`implementedas an applet in SMX. The e-purse is configured
`to be able to access the Mifare data structures with appropri-
`ate transformed passwords based on the access keys.
`In the cellphone 202, a purse manager midlet 204is pro-
`vided. For M-commerce, the midlet 204 acts as an agent to
`facilitate communications between an e-purse applet 206 and
`one or more payment network and servers 210 to conduct
`transactions therebetween. As used herein, a midletis a soft-
`ware component suitable for being executed on a portable
`device. The purse manager midlet 204 is implemented as a
`“midlet” on a Java cellphone, or an “executable application”
`ona PDA device. One of the functions this software compo-
`nent provides is to connect to a wireless network and com-
`municate with an e-purse applet which can reside on either the
`same device or an external smart card. In addition, it is con-
`figured to provide administrative functions such as changing
`a PIN, viewing a purse balance and a history log. In one
`application in which a cardissuer provides an SA module 212
`that
`is used to enable and authenticate any transactions
`between a card and a correspondingserver(also referred to as
`a paymentserver). As shown in FIG. 2, APDU commandsare
`constructed by the servers 210 having access to an SA module
`212, where the APDU stands for Application Protocol Data
`Unit that is a communication unit between a reader anda card.
`
`The structure of an APDU is defined by the ISO 7816 stan-
`dards. Typically, an APDU command is embeddedin network
`messagesanddelivered to the server 210 or the e-purse applet
`206 for processing.
`For e-commerce, a web agent 214 on a computing device
`(not shown)is responsible for interacting with a RFID reader
`and the network server 210. In operation, the agent 214 sends
`the APDU commandsorreceives responses thereto through
`the RFID reader 216 to/from the e-purse applet 206 residing
`in the cellphone 202. On the other hand, the agent 214 com-
`poses network requests (e.g., an HTTP request) and receives
`responses thereto from the paymentserver 210.
`To personalize the cellphone 202, FIG. 3A shows a block
`diagram 300 ofrelated modules interacting with each other to
`achieve what is referred to herein as e-purse personalization
`by an authorized person as shown in FIG. 2. FIG. 3B shows a
`block diagram 320 of related modules interacting with each
`other to achieve what is referred to herein as e-purse person-
`alization by a user of the e-purse as shownin FIG.2.
`FIG. 3C showsa flowchart or process 350 of personalizing
`an e-purse according to one embodimentofthe present inven-
`tion. FIG. 3C is suggested to be understood in conjunction
`with FIG. 3A and FIG. 3B. The process 350 may be imple-
`mented in software, hardware or a combination of both.
`Asdescribed above, an e-purse is built on top of a global
`platform to provide a security mechanism necessary to per-
`sonalize applets designed therefor. In operation, a security
`domain is used for establishing a secured channel between a
`personalization application and the e-purse. According to one
`embodiment, the essential data to be personalized into the
`purse include one or more operation keys(e.g., a load key and
`a purchase key), default PINs, administration keys (e.g., an
`unblock PIN key and a reload PIN key), and passwords(e.g.,
`from Mifare).
`
`10
`
`15
`
`20
`
`25
`
`30
`
`40
`
`45
`
`55
`
`60
`
`6
`It is assumedthat a user desires to personalize an e-purse
`embeddedin a device (e.g., a cellphone). At 352 of FIG. 3C,
`a personalization process is initiated. Depending on imple-
`mentation, the personalization process may be implemented
`in a module in the device and activated manually or automati-
`cally, or a physical process initiated by an authorized person
`(typically associated with a care issuer). As shown in FIG. 3A,
`an authorized personalinitiates a personalization process 304
`to personalize the e-purse for a user thereof via an existing
`new e-purse SA module 306 and a SA module 308 with the
`RFID reader 310 as the interface. The card manager 311
`performs at least two functions: 1. establishing a security
`channel, via a security domain,to install and personalize an
`external application (e.g., e-purse applet) in the card person-
`alization; and 2. creating security means(e.g., PINs) to pro-
`tect the application during subsequent operations. As a result
`ofthe personalization process 304, the e-purse applet 312 and
`the emulator 314 are personalized.
`Similarly, as shown in FIG. 3B, a user of an e-purse desires
`to initiate a personalization process to personalize the e-purse
`wirelessly (e.g., via the m-commercepath of FIG. 2). Differ-
`ent from FIG. 3A, FIG. 3B allowsthe personalization process
`to be activated manually or automatically. For example, there
`is a mechanism on a cellphonethat, if pressed, activates the
`personalization process. Alternatively, a status of “non-per-
`sonalized” may promptto the userto start the personalization
`process. As described above, a midlet 322 in a device acts as
`an agentto facilitate the communication between a payment
`server 324 and the e-purse 312 as well as the emulator 314,
`wherein the paymentserver 324 has the accessto the existing
`new e-purse SA module 306 and an SA module 308. As a
`result of the personalization process, the e-purse applet 312
`and the emulator 314 are personalized.
`Referring now back to FIG. 3C, after the personalization
`process is started, in view of FIG. 3A, the RFID reader 310 is
`activated to read the tag ID and essential data from a card in
`the device at 354. With an application security domain (e.g.,
`a default security setting by a card issuer), a security channel
`is then established at 356 between a new e-purse SAM (e.g.,
`the SAM 306 of FIG. 3A) and an e-purse applet (e.g., the
`e-purse applet 312 of FIG. 3A)in the device.
`Each application security domain of a global platform
`includes three 3DES keys. For example:
`Keyl:
`404142434445464748494a4b4c4d4e4f
`
`255/1/DES-ECB/
`
`Key2:
`404142434445464748494a4b4c4d4e4f
`
`255/2/DES-ECB/
`
`Key3:
`404142434445464748494a4b4c4d4e4f
`
`255/3/DES-ECB/
`
`security domain is used to generate session keys for a
`secured session between two entities, such as the card man-
`ager applet and a host application, in which case the host
`application maybe either a desktop personalization applica-
`tion or a networked personalization service provided by a
`backendserver.
`A default application domain can beinstalled by a card
`issuer and assignedto various application/service providers.
`The respective application owner can changethe value of the
`key sets before the personalization process (orat the initial of
`the process). Then the application can use the new set to
`create a security channel for performing the personalization
`process.
`With the security channel is established using the applica-
`tion provider’s application security domain, the first set of
`data can be personalizedto the purse applet. The secondset of
`data can also be personalized with the same channel, too.
`However,ifthe data are in separate SAM,then a new security
`
`
`
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 16 of 17
`Case 6:21-cv-00916-ADA Document 134-3 Filed 02/06/23 Page 16 of 17
`
`US 8,448,855 B1
`
`7
`channel with the same keyset (or different key sets) can be
`used to personalize the secondset of data.
`Via the new purse SAM 306, a set ofe-purse operation keys
`and pins are generated for data transactions between the new
`e-purse SAM andthe e-purseapplet to essentially personalize
`the e-purse applet at 358.
`is then established at 360
`A second security channel
`between an existing SAM (e.g., the SAM 308 ofFIG. 3A) and
`the e-purse applet (e.g., the e-purse applet 312 of FIG. 3A) in
`the device. At 362, a set of transformed keys is generated
`using the existing SAM andthe tag ID. The generated keys are
`stored in the emulator for subsequent data access authentica-
`tion. At 358, a set of MF passwords is generated using the
`existing SAM andthe tag ID, then is stored into the e-purse
`applet for future data access authentication. Afterit is done,
`the e-purse including the e-purse applet and the correspond-
`ing emulatoris set to a state of “personalized”.
`FIG. 4A and FIG.4B show togethera flowchart or process
`400 of financing an e-purse according to one embodimentof
`the present invention. The process 400 is conducted via the
`m-commerce path of FIG. 2. To better understandthe process
`400, FIG. 4C shows an exemplary block diagram 450 of
`related blocks interacting with each otherto achieve the pro-
`cess 400. Depending on an actual application of the present
`invention, the process 400 may be implemented in software,
`hardware or a combination ofboth.
`
`A useris assumedto have obtained a portable device(e.g.,
`a cellphone)that is configured to include an e-purse. The user
`desires to fund the e-purse from an account associated with a
`bank. At 402, the user enters a set of personalidentification
`numbers (PIN). Assuming the PIN is valid, a purse manger in
`the device is activated andinitiates a request (also referred to
`an OTAtop off request) at 404. The midlet in the device sends
`a request to the e-purse applet at 406, whichis illustrated in
`FIG. 4C where the e-purse manager midlet 434 communi-
`cates with the e-purse applet 436.
`At 408, the e-purse applet composes a responsein respond-
`ing to the request from the midlet. Upon receiving the
`response, the midlet sendsthe responseto a payment network
`andserverovera wireless network. As shown in FIG.4C, the
`e-purse manager midlet 434 communicates with the e-purse
`applet 436 for a response that is then sent to the payment
`network and server 440. At 410, the process 400 needs to
`verify the validity of the response. If the response can not be
`verified, the process 400 stops. Ifthe response can be verified,
`the process 400 moves to 412 where a corresponding account
`at a bank is verified. If the account does exist, a fund transfer
`requestis initiated. At 414, the bank receives the request and
`responds to the request by returning a response. In general,
`the messages exchanged between the payment network and
`server and the bank are compliant with a network protocol
`(e.g., HTTP for the Internet).
`At 416, the response from the bank is transported to the
`payment network and server. The midlet strips and extracts
`the APDU commands from the response and forwards the
`commandsthe e-purse at 418. The e-purse verifies the com-
`mands at 420 and, provided they are authorized, send the
`commandsto the emulator at 420 and, meanwhile updating a
`transaction log. At 422, a ticket is generated to formulate a
`response (e.g., in APDU format) for payment server. As a
`result, the paymentserver is updated with a successful status
`messagefor the midlet, where the