US009047601B2
`
`a2) United States Patent
`US 9,047,601 B2
`(10) Patent No.:
`Xie et al.
`Jun. 2, 2015
`(45) Date of Patent:
`
`(54)
`
`(71)
`
`(72)
`
`METHOD AND APPARATUS FOR SETTLING
`PAYMENTS USING MOBILE DEVICES
`
`Applicant: RFCyber Corporation, Fremont, CA
`(US)
`
`Inventors: Xiangzhen Xie, Shenzhen (CN): Liang
`Seng Koh, Fremont, CA (US); Hsin
`Pan, Fremont, CA (US)
`
`(52) U.S.CL
`CPC veescseee G06Q 20/3227 (2013.01); GO6O 20/352
`(2013.01); G06Q 20/3552 (2013.01); GO6Q
`20/3672 (2013.01); G06Q 20/40 (2013.01);
`G06Q 30/0601 (2013.01); GO6Q 20/3278
`(2013.01); GU6Q 20/102 (2013.01)
`(58) Ficld of Classification Search
`USPC wiicecccceecccssseeseeseserecsesesenessssnerecsensnes 705/21
`See application file for complete search history.
`
`(73)
`
`Assignee: RFCyber Corpration, Frement, CA
`(US)
`
`(56)
`
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`US.C. 154(b) by 0 days.
`
`(21)
`
`Appl. No.: 13/853,937
`
`(22)
`
`(65)
`
`(63)
`
`(60)
`
`(1)
`
`Filed:
`
`Mar. 29, 2013
`
`Prior Publication Data
`
`US 2014/0006194 Al
`
`Jan. 2, 2014
`
`Related U.S. Application Data
`
`Continuation-in-part of application No. 13/350,832,
`filed on Jan. 16, 2012, whichis a continuation-in-part
`of application No. 11/534,653, filed on Sep. 24, 2006,
`now Pat. No. 8,118,218.
`
`Provisional application No. 61/618,802,filed on Apr.
`1, 2012.
`
`Int. Cl.
`G06G 1/12
`G060 30/00
`G06Q 40/00
`G06Q 20/32
`G06Q 20/34
`G06Q 2036
`G06Q 20/40
`G06Q 30/06
`G060 20/10
`
`(2006.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`
`References Cited
`
` U.S. PATENT DOCUMENTS
`
`
`7,962,369 B2*
`6/2011 Rosenberg .....0...000.... 705/26.1
`8,196,131 B1*
`vs 717/168
`6/2012 von Behrenetal.
`
`8,341,083 B1* 12/2012 Jain os 705/41
`
`» 455/411
`8,565,676 B2* 10/2013 Gormlcy ctal.
`......
`sees 705/17
`8,577,731 BI* 11/2013 Copeetal.
`
`.. 713/168
`8,601,266 B2* 12/2013 Aabye eval.
`....
`2/2014 von Behren etal.
`.............. 726/9
`8,646,059 B1*
`
`............ 235/492
`2008/0093467 Al*
`4/2008 Narendra etal.
`
`(Continued)
`
`Primary Examiner — Ashford S Hayles
`(74) Attorney, Agent, or Firm — LogicPatents, LLC; Joe
`Zheng,
`
`ABSTRACT
`(57)
`Techniques for mobile devices configured to support settle-
`ment ofcharges in electronic invoicesor bills are described. A
`mobile device embedded with a secure element generates or
`is loaded with an electronic invoice. When the mobile device
`is brought to a consumer with an NFC mobile device,the data
`includingthe electronic invoice and other information regard-
`ing the mobile device or an ownerthereof is read off wire-
`lessly into the NFC mobile device. After the user verifies the
`amount being charged and authorizes the payment, the NFC
`mobile device communicates with a payment gateway or
`network for payment that is configured to proceed with the
`paymentin accordance with a chosen payment methods.
`
`16 Claims, 22 Drawing Sheets
`
`jooioio
`
`Personnel
`
`Personalization
`New e-purse
`SAM
`306
`Application
`Server 304
`
`
`
`
` Existing
`
`
`
`
`
`
`
`Contactless
`Reader
`310
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 1 of 38
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 1 of 38
`
`

`

`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`
`
`2008/0126260
`2009/0289 106
`2010/0211504
`2010/0213253
`2010/0306076
`2011/0078081
`2011/0087610
`2011/0112968
`2011/0113473
`2011/0117839
`2011/0180610
`2011/0251952
`2012/0072309
`2012/0078792
`2012/01 18952
`2012/0136786
`2012/0166333
`2012/0178433
`2012/0290376
`2012/0304255
`2012/0317628
`2013/0024383
`2013/00544 13
`2013/0060618
`2013/0060699
`
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`Al*
`
`2008 CO ct ale ccccccccscccececereceeee 705/67
`11/2009 Bishop et al.
`..
`235379
`. 705/44
`8/2010 Aabye etal.
`...
`2010 Wollbrandetal.
`235/380
`
`12/2010 Taveau etal. .....
`705/26
`
`3/2011 Pirzadeh etal.
`705/44
`705/318
`4/2011 Batadaetal.
`..
`
`/2011 Floreket al.
`705/50
`
`/2011 Corda etal.
`4. 72613
`. 455/4L1
`5/2011 Rhelimi
`.
`
`
`7/2011 Narendra etal.
`.
`.. 235/492
`
`....
`.. 705/40
`10/2011 Kellyetal.
`705/26.41
`3/2012 Hultberg etal.
`
`705/44
`3/2012 Bacastowotal. .
`
`235/380
`5/2012. Norair .........-
`(2012 Romagnoli etal.
`705/44
`
`2012. von Behrenetal.
`705/41
`7/2012 Narendra etal.
`.
`. 455/420
`
`705/14.23
`11/2012 Dryer etal.
`....
`
`.. 7126/3
`11/2012 Carnes ...
`
`.. 726/5
`12/2012 Yeager....
`
`1/2013. Kannappan.
`....
`w 705/71
`2/2013 Brendell et al. ou... 705/26.41
`3/2013 Bartonet al.
`.....
`705/14.23
`
`3/2013. Romagnoli etal... 705/44
`
`
`
`
`
`
`2013/0097031 Al*
`w FOS/M6
`4/2013 Royyuruetal. .....
`2013/0097080 Al*
`. 705/44
`4/2013 Smetsetal.
`..
`
`2013/0103574 Al*
`. 705/39
`4/2013 Conrad et al.
`2013/0124349 Al*
`. 705/21
`5/2013 Khan etal.
`.
`2013/0132219 A1*
`. 705/21
`5/2013 Liberty ...
`
`2013/0138959 Al*
`713/168
`5/2013 Pelly et al.
`
`2013/0140360 Al*
`6/2013 Graylin ...
`.. 235/380
`
`
`2013/0144731 Al*
`6/2013 Baldwinetal.
`» 705/17
`2013/0151292 Al*
`6/2013 Van Deloo ctal.
`w. 7058/5
`
`2013/0151400 Al *
`6/2013 Makhotin et al.
`.
`. 705/39
`
`2013/0152185 Al*
`ww 7226/9
`6/2013 Singh etal.
`...
`
`
`2013/0160134 Al*
`6/2013 Marcovecchioet al.
`. 726/26
`2013/0171929 AL*
`7/2013 Adamsetal. ........
`455/41.1
`
`
`2013/0173736 AL*
`7/2013 Krzeminskiet al
`709/213
`2013/0198086 Al*
`8/2013 Mardikar .............
`vee 705/71
`
`2013/0200999 Al*
`8/2013 Spodak etal.
`.. 340/5.65
`2013/0203345 Al*
`8/2013 Fisher .....
`455/A1.1
`
`2013/0218766 A
`8/2013 Mueller
`..
`. 705/42
`2013/0221092 A
`8/2013 Kushevskyet al.
`........... 235/379
`
`2013/0226812 A
`vee 705/67
`8/2013 Landrok etal.
`...
`2013/0246258 A
`9/2013 Dessert
`......
`. 705/41
`
`2013/0254102 A
`9/2013 Royyuru....
`. 705/39
`
`2013/0334318 A
`12/2013 Wakerlyetal.
`235/492
`2013/0346305 Al* 12/2013 Mendes.....
`. 705/41
`1/2014 Kuhnetal.
`. 705/41
`2014/0012751 Al*
`
`we 7206/5
`2014/0013406 Al*
`1/2014 Tremlet
`..
`
`
`4/2014 Desaietal. 0.0...
`.. 705/41
`2014/0095382 Al*
`
`US 9,047,601 B2
`
`Page 2
`
`
`
`
`
`* cited by examiner
`
` Google LLC v. RFCyber Corp. / Page 2 of 38
`
`GOOG-1031
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 2 of 38
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet1 of 22
`
`US 9,047,601 B2
`
`100
`
`Payment Network
`
`Payment Authorization Request
`
`Smart Bill Payment Gateway 104
`
`Payment Authorization
`
`
`
`
`Response
`
`Payment info with
`electronic bill
`
`Personal NFC device
`with wallet software
`
`110
`
`196
`POS with contactless
`reader OR NEC device with
`SE (such as Mobile POS)
`
`Signedelectronic bill
`
`Contactless smart
`
`card (or secure
`element in NFC
`devices) with smart
`bill applet
`108
`
`Electronic bill
`
`FIG. 1A
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 3 of 38
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 3 of 38
`
`

`

`US 9,047,601 B2
`
`120
`
`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet2 of 22
`
`Merchant POS prepares an electronic bill and writes to a
`smartbill applet on his contactless smart card or SE on NFC
`device
`
`122
`
`Customer service delivers the contactless smart bill card (or
`SE} to customer
`
`Customer with NFC device installed with a smartbill enabled
`
`wallet application retrieves the electronic bill signed by the
`smartbill applet
`
`126
`
`Electronic bill is displayed on the NFC device screen for
`customerto verify the amount and add a tip if he wishes
`
`128
`
`Customer can choose a payment methodthat he has enrolled
`in his wallet application to initiate the payment
`
`130
`
`complete transaction.
`
`Smart bill enabled application sends the transaction information
`to the backend smartbill gateway for processing
`
`132
`
`Smart bill gateway verifies the electronic bill and rejects if the
`payment amountis less than the billed amount.
`
`134
`
`Smart bill gateway uses the traditional financial payment network
`flow to send payment request and get paymentresponse. It also
`can use new online payment method such as Paypal or Alipay to
`
`136
`
`Once the transaction is approved or denied, the payment
`authorization response will return to the payment gateway tobe|138
`forwarded back to the merchant
`
`
`
`FIG. 1B
`
`Google LLC v. RFCyber Corp. / Page 4 of 38
`
`GOOG-1031
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 4 of 38
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet3 of 22
`
`US 9,047,601 B2
`
`00¢
`
`ddyws
`
`aa~gugjeado
`
`VeSid
`
`juaweBeuey,eaUoFSURUSISIA
`SIBPIAQIgeULONe} SIGOW4/\NS
`
`‘.\fZ0Z\\iSISPLAQId‘/eed
`80z<f\SUOINISU]
`yuslUabHeuel|y-Sid,q
`SISPIADISHOPIAOIdr0¢
`BAGGs.ifOM
`SISPIAQ!i\vand902:\peroueul4}13S}UBWU}J=syaquiosans
`aindassinda¢jsiesr
`
`
`
`
`*adlAlasiadopanAe
`a“/\SCShe
`
`O1Z
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©9—°ifs)®D©oO~ai°Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 5 of 38
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 4 of 22
`
`US 9,047,601 B2
`
`
`
`
`
`
`
`ULMUOITeal|ddeau}josnjeysou}
`
`
`
`|JSULBUDpasndeseUsI|qeIsy
`
`
`
`
`
`asspalejsu!Bulsn4g34}uMC|UMIPUSSPUeOU!BdIASPSAaIION
`
`
`
`
`
`J9AJBSBU)O}UO!}eO!|\ddeau)BulAjUap!
`
`Oc?e
`
`ass
`
`Zpal|elsulvee
`
`
`
`ZUOISIAOIALe}IS
`
`ass|Ie}sul
`
`
`
`JSUUBYOUOIed/UNWLUODBYsi|qeisy
`
`
`
`
`
`(INS_L@''B'9)payeolpapeYIMso~uas
`
`
`
`
`
`uoneoi|ddeau}Jo,eyepaiedaigQtSidJOOLL0}0D
`pouoisiaoudBuraqJanssiauAj]Uap|J9SN94}JepulleJO
`
`
`
`
`
`JoJaplAouduoneolddeau)AONSEUASoUtIEpezijeuosied
`
`
`
`
`
`BOIASPa//GOWPaljijUap!SY}
`
`
`
`JBULEYOPsuNndss2USI|GeISy
`
`SIpaauapBuisn3g8uyuM
`
`S|ASS}
`
`pgyeioosse
`
`
`
`Eddyayy/M
`
`deOld
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©9—°©®D©oO—ai°Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 6 of 38
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 5 of 22
`
`US 9,047,601 B2
`
`
`
`
`
`JepMosgsspuSgsansa}3SsassayISLBIKESIQOY&
`
`
`
`
`
`JeVis
`
`el
`
`
`
` 4(dary
`
`
`
`inalQgsszyeuassag'g
`
`
`
`:BoyMOI?|
`
`
`
`‘doypeayumaryy|
`
`aaa2D°3oO
`
`Oo
`
`LLaSs
`
`i®2>Oo
`
`o3oO3OoO
`©9—°xR®D©oO—ai°Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 7 of 38
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet6 of 22
`
`US 9,047,601 B2
`
`
`
`
`
`
`
`
`
`
`
`
`LOeseisoAangdehysg:
`
` ld
`“HASRIEDUORETYSUTSIogft
`
`
`
`FIEDUORPTEuOMEe@=
`
`
`
`Jduguogeredesgeqegdysyeesopueyouveg's
`
`ienheyuarsaaig's¢
`
`
`
`
`
`
`
`lt
`
`
`
`
`
`yBBSSMaBQO
`
`
`
`
`WSHJ20185JEPINGsgSMES||“GlugNonmredaigned‘doySBAESBLLSHAEGSHQCEY6
`
`
`
`
`
`
`rit:PigeepHUGRETHBUGSiSPS
`;ae
`
`
`
`
`
`4THOSS4epsssgo'g:
`
`déVia
`
`
`
`PoRMUNOTT
`
`
`
`
`
`
`
`SpnysssaansdolBuinssidpaopyar
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©9—°©®D©oO~ai°Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 8 of 38
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 7 of 22
`
`US 9,047,601 B2
`
`déSl
`
`O/Z0}jsenbsauolesedoueSajelyulsdiAepoUL
`Z/2uoneaddeay)BuljqesipAqspsed0id4S
`
`plzjusWwebps|mouyoeUeyOeGSpuss4S
`uoeo||\ddepayjuep!ay}Sx90]Jeu}ASOy
`
`
`
`
`
`
`
`
`
`09d
`
`292
`
`
`
`v9éuoneiado
`
`907]WEIS
`
`
`
`aolAapB0}eGessewusndeBpuss
`
`yonsAja,
`
`Zebessouw2
`
`
`
`BOIABP9U}O1(NGdV)PUBWWOSeBpuss
`
`
`
`pueuoneoddesejnomedeAiuep|
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©9—°o>)®D©oO—ai°Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 9 of 38
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 8 of 22
`
`US 9,047,601 B2
`
`08¢
`
`
`
`
`
`Jo}aempseyBuljsixyjuabyqaJOMIONJUBWAe
`
`
`
`
`
`ueul(uoNeuodsuel|JO$910}¢‘6'9)~6Z
`
`
`
`SdJELULUODpaseg-pueyOdUO062SIBAJOSpue
`
`
`déOld
`
`9098ZPJOMSSEd9Z
`
`dW9}SS390V7JICIN
`
`soyeinw3UIIM45)UO
`
`
`
`yIngja\ddy
`
`
`
`
`
`aiqeyodJO90]O1YpledJO90}014
`
`ad|A8q
`coz
`
`
`
`asind-9
`
`
`
`
`
`jeuonjouny3/6uispledWeUWS
`
`
`
`JUSWUOJIAUZpesojouy
`
`
`
`962JapeeyssayjaequoD
`
`
`
`
`
`BOELO}U]SSEJOeJUOD99z
`
`
`
`BOJSWLUOI-990JEWIWOO-W
`
`Lea>oO--2Da°°°Oo
`
`a2>Oo
`
`o3oO3OoO
`©o—°Oo=ooD©a—ar=°oO
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 10 of 38
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 9 of 22
`
`US 9,047,601 B2
`
`LLE
`
`
`
`JeBeuery|pled
`
`psZoyIny
`
`|SUUOSI8g
`
`Buljsixy
`
`NYS
`
`B0€
`
`UOI]BZI|BUOSI9g
`
`uoneoddy
`
`POSJSAIOS
`
`90€
`
`asind-3MON WVS
`
`VeSls
`
`GLE
`ja\ddy
`
`esund
`
`-3
`
`VLE
`
`Jojejnuy
`
`Ssajoe}UOD
`
`Japeey
`
`Ole
`
`aaa2D°3oO
`
`LLaSOo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3<=®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 11 of 38
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 10 of 22
`
`US 9,047,601 B2
`
`LLE
`
`
`
`Jebeueyypied
`
`GeDs
`
`Joye|nwy
`
`
`
`asund-aVIGIN
`
`jo\ddy
`
`CCE
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3nNx®D©oO~ai3Oo
`
`PUBYIOMION
`
`juowhed
`
`PZESIBAIOS
`
`Buyysixy
`
`Ws
`
`80€
`
`esund-3MON
`
`90€WVS
`
`© o
`
`D
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 12 of 38
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 11 of 22
`
`US 9,047,601 B2
`
`oO
`
`
`
`uolezijeuosiad931e2N1u|
`
`pledau}WOG|6212Jopeay
`
`ogejauueydAunseseBUsi|geysso}UleWOpAyuNoesUoHed!|ddeasp
`
`
`
`8SVSosund-3mauau)usemjeqsuidpuesAdyUO!}eJadoasund-2a}Be18Uay
`
`
`
`
`oD
`gcsejouueYSAyNDasBYsI|ge1sa9Oo}UleWOPAyINoasUOeal|ddeeasy
`
`
`
`
`
`
`SdIANPSy}Ul}9|ddeasund-3uepueWYSLONeWodsue.)BunsixdueUs8M1eq
`
`
`
`
`ad|ASpay]Ulyajddeesund-auepueysasund-9mauueUaaMyeq
`
`
`
`
`
`
`QdIABPBy]U!}@\ddeasind-auepue
`
`
`
`COEq|Ge)ou)puewysBunsixeou}BIAJOJ2;NWdUeJoSAB}PSLUOJSUBI]B]eJBUED
`
`
`
`
`
`JeVA
`
`y9EQ|62)au)pueWsBunsixeueBIASpuomssed4)ayesaUas
`S9IA8P9}Ulya|ddeasund-auepukeWSBunsixeau)Usemjeq
`
`
`
`
`,Pezi|euosied
`
`10aje1SBO]asund-89)19S
`
`
`
`Joye|NWeau}pueVSBunsixeou}Ugamjeq
`
`Lea>oO--2Da°°°Oo
`
`a2>Oo
`
`o3oO3OoO
`©o—°©=ooD©a—ar=°oO
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 13 of 38
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 12 of 22
`
`US 9,047,601 B2
`
`Oo
`oO
`wT
`
`chyJajSued)punyeayeiulpueyunoIVeBulpuodseawooeAja,
`
`
`
`vOvpijenBuiejueJayeJe|pilu&BIAjsenbelesjeNlul
`
`
`
`20r]9]PllBU]CO}BSuUCdSaieSBSOdWwODasind-F
`
`
`9ja|ddeasind-a0]jsenbeeBSpUuasISICIAN
`
`
`
`DSIJOAJ‘yUegBulIOSUOdse01ISENbeL
`
`
`JeBeuewasinday}sse00e0}Nid
`
`
`
`asuodsedl3u)
`
`VrSIA
`
`
`
`
`
`
`
`ylyueg8}WO)ssuodseleBBAIsVEy
`
`éPSIJLSA
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3+=®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 14 of 38
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 13 of 22
`
`US 9,047,601 B2
`
`
`
`
`
`LpoBessewYIOMIOUBUlPeppequisesuOodseOU}PIeMIO-4
`
`
`
`
`
`
`
`
`
`LpQSINd-89y}0}LUSY]PUBSPUBSPUBWLUODNGdYy}OexXepuedjsJ9/pIVy
`
`
`
`
`
`
`
`0zBo|uonoesuedeseyepdnpueJo}ejNwWs9y}oO}
`
`
`
`
`
`SPUeLULUODSpuaspueAlIDIUBYINeNCdYVBu}SAeABsund-F
`
`
`
`
`
`esuodselNdUeS9IE|NWUO]JEU}19|PILUOU]O1JEyOI]BSB]BIBUSy
`
`
`
`
`
`
`
`
`
`
`
`Z2vJOAIOSJUQWAed9U}]0]ISONbDEJYIOMISUBUl
`
`GyDs
`
`
`
`
`
`UONIIJIOA912]JO,pouleiasS|asuOdsadMagyau}4eye
`
`
`
`
`
`}9/plluJo,eBessewsnjelsjnjsseoonse9}BIBUe5
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—°re)=®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 15 of 38
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 14 of 22
`
`US 9,047,601 B2
`
`JyVa
`
`ovrOvrvey
`
`BEV
`
`ICI Joye|nugqesind-9
`
`Bulsueul4YIOMIJONJUsWAeY
`
`
`yuegSJBAJSpue
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—°©=®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 16 of 38
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 15 of 22
`
`US 9,047,601 B2
`
`VS‘Olt
`
`
`
`AsoysodayAsoysodey
`
`90Svos
`
`
`
`0SuojeaiiddyuoneaiddyAsoywsoday
`JOIPIAIyo\ddyCOS
`
`cScScaAuojoauiq
`
`
`
`OLSNVSddSISPIAOLdBIIAIOSJOAIOSAIOISIIG
`
`
`
`
`
`L1GWSuoneaddy
`
`VLGSIBAIBSZLS
`
`oes!salAaq7eiqeHod
`
`OCGSJOMION
`NN8is
`jauueUD
`
`Jeineo|”
`
`suoleolunuiwosy’
`
`peinaas
`
`jUsWUd|4peunoss
`
`
`
`
`
`22yo|ddyuoyeolddygzgJoBbeuewpleddO
`
`
`
` begpuegesed€ZGJ@IPINUONeaddy|¢———_|_zzgjebeueyao19g
`
`
`
`
`
`
`
`Lea>oO--2Da°°°Oo
`
`a2>Oo
`
`o3oO3OoO
`©o—°--ooD©a~ar=°oO
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 17 of 38
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 16 of 22
`
`US 9,047,601 B2
`
`
`ALAAioysodeyAjoysodeyKioysoday
`
`
`
`vsJ@IPINjolddyfiooauiq
`
`90gv0sZO
`
`
`
`9LSNYSdOSIBPIAdBIIABSsaniegAu0je.1q
`
`
`
`
`
`zegJaBeuey\|\vzSoes_ASOEs
`
`EZSJICINLoHeo|ddyZzgJeBeuepyaaiaspaunoag|’
`
`
`
`
`
`61gJeuueYD
`
`
`
`ZLWYSuonealddy
`
`PLGSIBAIAS219
`
`
`
`puegesegSd1Aoq
`
`S|QeHod
`
`lZG
`
`4JOMON~”
`
`
`
`ulewogdI1GNdgegJe;ndw0D
`
`x.
`
`gS‘Sls2
`
`
`
`JUusWa|ypeinoes
`
`vES
`
`
`
`
`
`22Syolddyuojeal|ddy9zgsoBeueyw|PIBDdQje---------JapeoyaSS9)}9e}UOD
`
`
`
`
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—°©2®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 18 of 38
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 17 of 22
`
`US 9,047,601 B2
`
`Oo
`
`LO
`
`USSls
`
`
`
`
`
`oggjSOnbeladiAsas&Pudas
`
`
`
`SUO!}E9!|\dde/SEDIAJOSSPIADId
`
`uondisosgnsuopesegBurysi|
`
`
`
`p9}99/9S||e}SU!puepeojuMOG
`
`
`
`(s}a)dde)suoneaijddessaainsas
`
`BGS
`
`pepesuIIJoye|NWepue
`
`
`
`
`
`
`
`SIVIGIAUoNeol|ddepeojumogq
`
`
`
`sjajddepapeo|uMopdau}8Z!|BUOSIa4
`
`
`
`
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—°o2®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 19 of 38
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 18 of 22
`
`US 9,047,601 B2
`
`oO
`
`c
`
`a|qeuod
`
`0¢9Sao1neq
`
`V9
`‘Old
`
`SUONEOIUNWWOD
`
`JeIn|!9D
`
`OzOMAN
`
`PeiNIESiuoljoesue}7Suu]
`|eeJ
`
`uolaeSUBLLSOd
`
`
`
`EL9ISAIBS
`
`jauueyg——"yoyeq10
`
`
`819uoljesedo
`
`
`
`Te[Po
`
`6E9
`
`uonoesue)I
`
`
`
`aul]|2e1~~]
`
`829WIVSSOd
`
`uasyo1-98
`
`pejqeus
`
`9€9BIIABq
`
`puegaseg
`
`vc9
`
`
`
`JUSW8/ypainoas
`
`629
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3SoN®D©oO—ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 20 of 38
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 19 of 22
`
`US 9,047,601 B2
`
`
`
`uoljsesuel!SOdUlBWOdIIIGNd
`
`painoss
`
`jouueuyD
`
`619
`
`gegJojndwoy
`
`
`
`
`
`€/1.9JOAIBS4JOMIONjusbySOd
`
`9‘Sls
`
`
`
`JUQW2]ypeinoes
`
`6S
`
`puegssegq
`
`veg
`
`a1qe10d
`
`a01A0q
`0€9S)
`
`
`
`€z9Jobeueyw|SOd
`
`8z9NVSSOdm=
`
`1t'ii
`
`1
`
`5S9]]02]U0D
`
`Japeey
`
`L2Geeg
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3<N®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 21 of 38
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 20 of 22
`
`US 9,047,601 B2
`
`oO
`LO
`©
`
`
`
`Jaseyoind2WO]U9yO}-8UBsASLIaY
`
`4UB4O}-9PIA
`
`
`
`dn-do}jenyia10
`
`8&9dn-do}eWoLad
`
`
`
`JE34JBLO
`
`
`
`édn-do}ew}
`
`
`
`uBnousdey)$s
`
`-9ulsouRjeq
`
`2U9}0}
`
`
`
`
`
`USYO]-8WOUJUNOWWepeseyoindyanpsq
`
`99‘Sl
`
`(yo12qUlJOUO}OeSue.Yoed)
`
`
`
`
`
`JOAISSPUBYORO}SUO!OBSUBI]peojd/j
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3nNN®D©oO—ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 22 of 38
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 21 of 22
`
`US 9,047,601 B2
`
`g9Dl
`
`
`
`UOIJOESULL]SY)PSpPsoIesSey
`
`v89
`
`0]BBeSSOWWUIJUODJIGepPSu}PUeMIOS
`
`
`
`
`
`-99U}WO,SSUddSalPSAID9JBU]PUBMUO_-4
`
`
`WYVSSOdO}S3IA3pPpojqeusUsy40}
`
`
`UONBOISAJOLWIWSSOd
`
`
`
`
`souerjegyuBnouFy
`
`USYO}-9Ul
`
`
`
`Z80lAappaiqeus
`
`©
`
`cZ9
`
`
`
`
`
`-90}jSaNbesaseyonNd|eiuluepuss
`
`
`
`
`
`Jaseuoind2JoadlAeppajqeueuayo}
`
`WVSSOdJayeuoNoesueyAeidsiq
`
`
`
`
`eBBulule}uosysenbeyiqepBaAlIeoay
`
`WYVSSOdWOdOVIN
`
`USYO}-901ISENbsuGSPsy]PUSS
`
`
`
`
`
`USYO1-91108pO1SIIASPpajqeue
`
`
`
`
`
`JUSW/}JESPUBUOHBIYVSAUOIOeSUeLJOJSOVIN
`
`
`
`
`
`
`
`
`
`
`
`jeuonippeBulpnjou!eBessewWaU0d1qepsAlesey
`
`
`
`
`
`
`
`689
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—°Ce)N®D©oO~ai3Oo
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 23 of 38
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 2, 2015
`
`Sheet 22 of 22
`
`US 9,047,601 B2
`
`ZSl
`
`ayes)
`
`Ul-499UD
`
`Japeay
`
`vel
`
`
`
`
`
`9Z/JUSWWd|3PoINISS
`
`OJUOPdJO}S}9}91]-9
`
`
`“~oe
`
`SUI|UO
`
`Bunaxoi
`
`
`
`aseyoindjay491}
`
`
`
`AJ@aljappue
`
`
`
`Buiseyoind90JBLULUOD-9
`
`OLZ
`
`uoneaiddypelesind-e
`
`a|qeuod
`
`301Aeq
`
`aaa2D°3oO
`
`LLa>Oo
`
`i®2>Oo
`
`o3oO3OoO
`©o—3xN®D©oO—ai3Oo
`
`
`
`iNO¢LJOPIAOld9949LWO-WU1UONAIGSOY|BOIAJOSayo!):WAISAG 19491},recenenenceneneeAJ@Al}eppue9a!aseyoind
`
`JOYOI1-9'BONOXog|
`
`
`
`
`
`
`
`co
`
`7
`
`portcsssaq2rllifiwaskgwfee'Wqeqnipeso|juswdedws
`
`© ~
`
`~
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 24 of 38
`
`
`
`

`

`US 9,047,601 B2
`
`1
`METHOD AND APPARATUS FOR SETTLING
`PAYMENTSUSING MOBILE DEVICES
`
`BACKGROUND OF THE INVENTION
`
`
`
`2
`Accordingto still another aspect of the presentinvention, a
`consumer uses his/her mobile device, per the data received
`therein, to settle the payment process with a payment net-
`work, where the payment network may be an existing pay-
`mentinfrastructure (e.g., money transfer or credit card/debit).
`A paymentresponseis sent to the merchant once a paymentis
`delivered to a designed account by the merchant.
`According to still another aspect of the present invention,
`the mobile device being used by the consumeris itself an
`electronic purse. Thus the consumeroperates his/her mobile
`device to settle the charge once the electronic invoice is
`received and displayed thereon.
`Accordingto still another aspect of the present invention,
`the mobile device used by the consumeris a near field com-
`munication (NFC) device and being part ofa mobile payment
`ecosystem in which various parties are work with each other
`in order for the mobile payment ecosystem successful. Via a
`server (e.g., implemented as a manager) configured to pro-
`vide whatis referred to herein as Trusted Service Manage-
`ment (TSM), the secure element in the mobile device can be
`remotely personalized and various applications or modules
`can be downloaded, updated, managedor replaced after they
`are respectively provisioned via the Trusted Service Manager
`(.e., the TSMserver). One of the modules being installed in
`the POS machine or an NFC device used bythe merchantis
`referred to as Smart Bill Payment. The module is configured
`to facilitate the communication between the merchant (its
`device) and the user (his/her mobile device) and the data
`exchange therebetween, where the mobile device being used
`by the user is installed with a corresponding application
`related to Smart Bill Payment.
`One important features, advantages and benefits in the
`present invention is to facilitate the settlement of charges
`using an NFC mobile device to read off data pertaining to an
`electronic invoice. The present invention may be imple-
`This section is for the purpose of summarizing some
`mented as a single device, a server, a system or a part of
`aspects ofthe present invention andto briefly introduce some
`system.It is believed that various implementations may lead
`preferred embodiments. Simplifications or omissions may be
`to results thal may not be achieved conventionally.
`made to avoid obscuring the purpose of the section. Such
`According to one embodiment, the present inventionis a
`simplifications or omissions are nol intended to limit the
`method for settling a payment, the method comprises: pro-
`scope ofthe present invention.
`viding a software module to be executed in a first mobile
`‘The present invention is related to techniques for mobile
`device embedded with a secure element, wherein the secure
`devices configured to support settlement of charges in elec-
`element has been personalized and the software module is
`tronic invoicesor bills. According to one aspect ofthe present
`invention, a mobile device embedded with a secure element
`provisioned with the personalized secure element, the first
`mobile device is configured to include data pertaining to an
`generates or is loaded with an electronic invoice. When the
`electronic invoice; receiving a payment request from a second
`mobile device is brought to a consumer with an NFC mobile
`mobile device after a user ofthe second mobile device autho-
`device, the data including the electronic invoice and other
`rizes the paymentto the electronic invoice transported wire-
`information regarding the mobile device or an owner thereof
`lessly from thefirst mobile device, wherein the second mobile
`is read off wirelessly into the NFC mobile device. After the
`deviceis a near-field communication device andis configured
`user verifies the amount being charged and authorizes the
`to execule an application thal communicates with the sofi-
`payment, the NFC mobile device communicates with a pay-
`ware module in the first mobile device to read the data off
`ment gateway or network for payment that is configured to
`fromthe first mobile device; verifying the payment request;
`proceed with the payment in accordance with a chosen pay-
`ment methods.
`and sending a paymentresponseto a user ofthe first mobile
`device after the payment request is processed. In the embodi-
`According to another aspec
`of the present invention, the 55
`ment, the second mobile device includesa display screen and
`mobile device is a contactless card or part of a point of sale
`is caused to displaythe electronic invoice whenthedata is in
`(POS) machine used to generate the clectronic invoice. One
`the second mobile device.
`embodimentof the present invention provides unanticipated
`According to another embodiment, the present inventionis
`benefits and advantages in an application in which a payment
`) a gatewayprovided for settling a payment, the gateway may
`process would otherwise haveto be involved in more than one
`contacts between a merchant and the consumer. One of such
`includeaserver or a collection of servers. The gateway com-
`applications is a payment process in a restaurant, where a
`prises a portal providing a software module to be downloaded
`and executedin a first mobile device embedded with a secure
`consumeris givena checkfirst for verification and a chance to
`add a gratitude before a final charge is determined and paid.
`element, wherein the secure element has been personalized
`Using the NFC mobile device, the consumer canfinish the
`and the software module is provisioned with the personalized
`payment using a chosen payment methodatthe pointof sale
`secure element,
`the first mobile device is configured to
`without further contacting the merchant.
`include data pertaining to an electronic invoice. The gateway
`
`2
`
`mB wu
`
`n> D
`2
`
`1. Field of the Invention
`The present invention is generally related to the area of
`electronic commerce. Particularly, the present invention is
`related to a mobile device configured to settle payments using
`a mobile device reading electronic bills or invoices off from
`another mobile device in a near field communicationrange.
`2. The Background of Related Art
`For many credit or debit card transactions, the payment
`processis started by a customerasking fora bill when check-
`ing out a purchase. A cashier or service memberbringsa bill
`to the customer for verification. The customer then hands out
`a credit/debit card to the service staff member. The service
`memberbrings the card to a Point of Sales (POS) counter to
`iniliale a transaction payment. The service member then
`brings back a receipt to the customerfor signature to autho-
`rize the transaction.It is a lengthyprocess that typically takes
`acouple ofminutes or much longer whenthe service member
`has to take care ofmultiple paymenttransactionsat a time. In
`addition, in the case for the debit card transactions, the pro-
`cess maybe even more troublesome whena PIN is needed to :
`authorize the transaction at the POS.
`There is a need to simplify the payment process. With the
`advancement in mobile devices, it is anticipated that many
`consumers will carry one with them. Thusthere is an oppor-
`tunity of using a mobile device to quicklysettle the payment
`ata pointof sale (POS).
`
`
`SUMMARYOF THE INVENTION
`
`
`35
`
`40
`
`45
`
`50
`
`
`
`Google LLC v. RFCyber Corp. / Page 25 of 38
`
`GOOG-1031
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 25 of 38
`
`

`

`US 9,047,601 B2
`
`3
`further comprises a server that includes: a processor and a
`store, coupled to the processor, for code to be executed in the
`processor to cause the server to performoperationsof:
`recciving a payment request from a second mobile device
`after a user of the second mobile device authorizes the
`
`paymentto the electronic invoice transported wirelessly
`fromthe first mobile device, wherein the second mobile
`device is a near-field communication device and is con-
`figured to execute an application that communicates
`with the software module in the first mobile device to
`read the data off from the first mobile device;
`verifying the payment request; and
`sending a payment response to a user of the first mobile
`device after the payment request is processed.
`Other objects, features, and advantages of the present
`invention will become apparent upon examining the follow-
`ing detailed description of an embodiment thereof, taken in
`conjunction with the allached drawings.
`
`
`
`BRILT DESCRIPTION OF THE DRAWINGS
`
`Td
`
`
`4
`FIG. 5A is a diagram showinga first exemplary architec-
`ture of a portable device for enabling e-commerce and
`m-commercefunctionalities over a cellular communications
`network (i.e., 3G, LTE or GPRS network), according an
`embodimentof the present invention;
`FIG. 5B is a diagram showing a second exemplary archi-
`tecture of a portable device for enabling e-commerce and
`m-commerce functionalities over a wired and/or wireless
`data network(e.g., Internet), according another embodiment
`of the present invention;
`FIG. 5C is a flowchart illustrating an exemplary process of
`enabling the portable device of FIG. 5A for services/applica-
`tions provided by one or more service providers in accor-
`dance with one embodimentofthe present invention;
`FIG. 6A is a diagram showing an exemplaryarchitecture,
`in which a portable device is enabled as a mobile POS con-
`ducting e-commerce and m-commerce, according to one
`embodimentofthe present invention;
`FIG. 6B is a diagram showing an exemplaryarchitecture,
`in whicha portable device is enabled as a mobile POS con-
`ducting a transaction upload operation over a network,
`according to an embodimentof the present invention;
`FIG. 6C is a flowchart illustrating an exemplary process of
`conducting m-commerce using the portable device enabled as
`a mobile POS with an e-token enabled device as a single
`functional card in accordance with one embodiment of the
`present invention;
`FIG.6D is a flowchart illustrating an exemplary process of
`conducting m-commerce using the portable device enabled as
`a mobile POS against a an e-token enabled device as a multi-
`functional card; and
`FIG.7 is a diagramdepicting an exemplary configuration
`in whicha portable device used for an e-ticking application.
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`ie)D
`
`36
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`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 shows a system configuration according to one
`embodiment ofthe present invention, where the payment
`network represents a collection of services or networks pro-
`vided to settle payments via a financialinstitution;
`‘IG. 1B showsa flowchart orprocess ofsettling a payment
`according to one embodiment, where the process may be
`implemented in software or a combination of software and
`hardware;
`FIG. 2A shows a mobile payment ecosystem in which
`related parties are shown in order for the mobile payment
`In the following description, numerousspecific details are
`ecosystem successful;
`Td
`set forth to provide a thorough understanding of the present
`G. 2B showsa flowchart orprocess of provisioning one
`invention. The present invention may be practiced without
`or more applications according to one embodiment;
`Td
`these specific details. The description and representation
`G. 2C showsa data flow illustrating various interactions
`herein are the means used by those experienced or skilled in
`among different parties when an application is being provi-
`sioned in one embodiment;
`the art to effectively convey the substance of their work to
`others skilled in the art. In other instances, well-known meth-
`[IG. 2D showsa data flow among different entities when
`ods, procedures, components, and circuitry have not been
`preparing the application data in provisioning anapplication;
`described in detail since theyare already well understood and
`FIG. 2E shows a flowchart or process for locking or dis-
`co
`to avoid unnecessarily obscuring aspects ofthe present inven-
`abling an installed application;
`Td
`tion.
`G. 2F shows an exemplary architecture diagram of a
`Reference herein to “one embodiment” or “an embodi-
`portable device enabled as an e-purse conducting e-com-
`ment” meansthat a particular feature, structure, or character-
`merce and m-commerce, according to one embodimentofthe
`istic described in connection with the embodiment can be
`present invention;
`
`G. 3A isablock diagram of related modules interacting includedin at least one implementation of the invention. The
`with each otherto achieve whatis referred to herein as e-purse
`appearances ofthe phrase “in one embodiment”or “in the
`personalization by an authorized personnel (a.k.a., personal-
`embodiment” in various places in the specification are not
`izing a mobile device or a secure element therein while pro-
`necessarily all referring to the same embodiment, nor are
`visioning an application);
`separate or alternative embodiments mutually exclusive of
`FIG. 3B showsa block diagram of related modules inter-
`other embodiments. Further, the order of blocks in process,
`acting with cach other to achieve whatis referred to herein as
`flowcharts or functional diagrams representing one or more
`c-purse personalization by a user of the e-purse;
`embodiments do not inherently indicate any particular order
`FIG. 3C showsa flowchart or process of personalizing an
`nor imply limitations in the invention. As usedin this speci-
`e-purse according to one embodimentof the present inven-
`fication and the appended claims, the singular forms “a,”
`tion:
`“an,” and “the” include plural referents unless the context
`FIG. 4A and FIG.4B show together a flowchart or process
`clearly dictates otherwise. It should also be noted that the
`of financing, funding, load or top-up an e-purse according, to
`term “or” is generally employed inits sense including “and/
`one embodimentofthe present invention;
`or” unless the context clearlydictates otherwise.
`FIG. 4C shows an exemplary block diagram ofrelated
`Embodiments ofthe present inventionare discussed herein
`with reference to FIGS. 1A-7. However, those skilled in the
`blocks interacting with each other to achieve the process FIG.
`4A and T'IG. 4B;
`art will readily appreciate that the detailed description given
`
`Google LLC v. RFCyber Corp. / Page 26 of 38
`
`GOOG-1031
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 26 of 38
`
`

`

`US 9,047,601 B2