USOO9047601B2
`
`(12) United States Patent
`US 9,047,601 B2
`(10) Patent N0.:
`Xie et a].
`
`(45) Date of Patent: Jun. 2, 2015
`
`(54)
`
`(71)
`
`(72)
`
`METHOD AND APPARATUS FOR SETTLING
`PAYMENTS USING MOBILE DEVICES
`
`Applicant: RFCyber Corporation, Fremont, CA
`(US)
`
`Inventors: Xiangzlien Xie, Shenzhen (CN); Liang
`Seng Koh, Fremont, CA (US); Hsin
`Pan, Fremont, CA (US)
`
`(52) U.S. Cl.
`CPC .......... G069 20/322 7 (2013.01 ); G069 20/352
`(2013.01); G069 20/3552 (2013.01); G069
`208672 (201301); G069 20/40 (2013.01);
`G069 30/0601 (2013.01); G069 20/32 78
`(2013.01), G069 20/102 (2013.01)
`(58) Field of Classification Search
`USPC ............................................................ 705/21
`See application file for complete search history.
`
`(73)
`
`Assignee: RFCyber Corpration, Frement, CA
`(US)
`
`(5 6)
`
`(*)
`
`Notice:
`
`Subject to any disclaimer, the term of this
`patcnt is cxtcndcd or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21)
`
`Appl. N0.: 13/853,937
`
`(22)
`
`(65)
`
`(63)
`
`(60)
`
`(51)
`
`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, which is a continuation-in-part
`ofapplication 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
`G06Q 30/00
`G06Q 40/00
`006g 20/32
`Gfl6Q 20/34
`G06Q 20/36
`G06Q 20/40
`G06Q 30/06
`G06Q 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 ............. 705/26 1
`8,196,131 B1 'V"
`6/2012 von Behren et a1.
`717/168
`
`8.341.083 Bl ‘ 12/2012 Jain ......................... 705/41
`
`.. 455/411
`8,565,676 B2 * 10/2013 Gormlcy ct 31.
`.... 705/17
`8,577,731 B1 * 11/2013 Cope et a1. ....
`8,601,266 B2 * 12/2013 Aabye el 31.
`713/168
`
`2/2014 von Behren et a1.
`....... 726/9
`8,646,059 B1 “
`
`............. 235/492
`2008/0093467 A1 *
`4/2008 Narendra et a1.
`
`(Continucd)
`
`Primary Examiner 7 Ashford S Haylcs
`(74) Allomefy, Agent, or Firm 7 LogicPatents, LLC; Joe
`Zheng
`
`ABSTRACT
`(57)
`Techniques for mobile devices configured to support settle—
`mcnt ofchargcs in clcctronic invoiccs orbills arc dcscribcd. 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
`including the electronic invoice and other information regard-
`ing the mobile device or an owner thereof is read off wire-
`lessly into the NFC mobile device. After the user verifies the
`amount being charged and authorizes the payment, the NFC
`mobilc dcvicc communicatcs With a paymcnt gatcway or
`nctwork for paymcnt that is configurcd to procccd With thc
`payment in accordance with a chosen payment methods.
`
`16 Claims, 22 Drawing Sheets
`
`01)C)O
`
`Personnel
`
`
`Ex1sting
`New e-purse
`Personalization
`SAM
`306
`SAM
`
`
`Application
`
`
`303
`Sewer 304
`
`
`
`
`Conlactlass
`Reader
`31 0
`
`Google LLC v. RFCyber Corp. / Page 1 of 38
`
`GOOG-1031
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 1 of 38
`
`PGR2022-00003
`Apple EX1031 Page 1
`
`

`

`US 9,047,601 B2
`Page 2
`
`2 13/0097031 A *
`705/16
`4/20 3 Royyuru et al,
`2013/0097080 A 5
`. 705/44
`4/20 3 Smets et a1.
`..
`2013/0103574 A 8-
`. 705/39
`4/20 3 Conrad et a1.
`
`2013/0124349 A 5
`. 705/21
`5/20 3 Khan etal/ 4
`
`2 [3/0132219 A *
`1 705/21
`5/20 3 Liberty
`20130133959 A ’f
`713/168
`5/20 3 Pelly Fta1~
`
`201340140360 A “
`-. 235/380
`6/20 3 Graylu}
`
`10130144731 A 3
`6/20 3 Baldwm eta~
`~ 705/17
`
`2 130151292 A *
`“111130100 ctal~
`6/20 3
`705/5
`
`
`3 13/013140“ A ’f
`6/20 3 Makhotln et81~ ~
`~ 705”?
`20130132185 A “
`6/20 3 Slngh et a1.
`726/9
`
`
`2013/0160134 A ‘
`6/20 3 Marcovecchloe a.
`. 726/26
`2013/0171929 A *
`........
`7/20 3 Adams et al.
`455/4l.l
`
`2 [3/0173736 A *
`7/20 3 Krzeminskiet al
`709/213
`
`
`2013/0198086 A ’<
`8/20 3 Mardlkar .............
`705/71
`20139200999 A
`8/20 3 Spodak etal~
`~- 340/565
`30130203345 A '
`8/20 3 Fisher
`455/41-1
`3 13/0218766 A
`3/20 3 Mueller
`~
`1 705/43
`
`20130221092 A
`8/20 3 KusheVsky 6t 31/
`~ 235/379
`
`20130226812 A
`8/10 3 Landrok eta-L
`705/67
`10130246258 A
`9/20 3 Dessefi
`~~~~~~
`~ 705/41
`2 130254102 A
`9/20 3 Roywru
`~ 705/39
`
`2013/0334318 A
`12/20 3 Wakerlyetal.
`235/492
`2 13/0346305 A * 12/20 3 Mendes .....
`. 705/41
`
`1/20 4 Kuhn et a1.
`. 705/41
`2014/0012751 A 5
`
`..
`2014/0013406 A 5
`1/20 4 Tremlet
`726/5
`
`4/20 4 Desai et 31.
`705/41
`2014/0095382 A 5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(56)
`
`References Cited
`US. pATpNT DOCUMENTS
`
`/2008 COX ctal. ..........
`2008/0126260 A1*
`
`
`11 235/379
`2009/ 1289106 A1* 11/2009 Bishop et a1 11
`
`2010/0211504 A1*
`8/2010 Aahye e1a1.
`705/44
`/2010 Wollbrand et al.
`235/380
`2010/0213253 A1 ’1
`
`.....
`2010/0306076 A1* 12/2010 Taveau et a1.
`705/26
`
`
`3/2011 Pir7adeh et a1
`2()ll/)()78081 Al*
`705/44
`705/318
`..
`2011/0087610 A1*
`4/2011 Batada etal.
`2011/0112968 A1*
`/2011 Florek etal.
`705/50
`
`.. 726/3
`2011/0113473 A1*
`//2011 Cordaet 31.
`5/2011 Rhelimi ....455/411
`2011/ 117839 A1*
`
`
`
`7/2011 Nal‘endl‘ae a.
`.
`.. 235/492
`2011/ 180610 A1*
`
`2011/0251952 A1* 10/2011 Kelly el al.
`705/40
`3/2012 Hultberg et a1.
`705/26441
`2012/0072309 Al*
`
`3/2012 Bacastow ct a1.
`.
`2012/0078792 A1*
`705/44
`5/2012 Norair 111111111111
`235/380
`2012/)118952 Al*
`
`/2012 Romagnoli el a1.
`2012/0136786 A1*
`705/44
`/2012 von Behren et al.
`2012/0166333 A1 ’1
`705/41
`
`.. 455/420
`.
`2012/0178433 A1*
`7/2012 Narendm et a1.
`
`705/1423
`2012/ 1290376 A1* 11/2012 Dryereral.
`.. 726/3
`2012/0304255 A1* 11/2012 Cm‘nes
`
`
`.. 726/5
`2012/0317628 A1* 12/2012 Yeager
`
`2013/0024383 Al*
`1/2013 Kannappan
`705/71
`2/2013 Brendell et a1.
`........... 705/26/41
`2013/ 054413 A1*
`2013/ 060618 A1*
`3/2013 Banon et a1,
`705/1423
`.....
`
`............ 705/44
`2013/0060699 A1 *
`3/2013 Romagnoli el al.
`
`
`
`* cited by examiner
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 2 of 38
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 2 of 38
`
`PGR2022-00003
`Apple EX1031 Page 2
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 1 0f 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
`
`106
`POS with contactless
`reader OR NFC device with
`
`SE (such as Mobile POS)
`
`Contactless smart
`Electronic bill
`
`Signed electronic bill
`card (or secure
`element in NFC
`
`
`
`devices) with smart
`bill applet
`108
`
`FIG. 1A
`
`
`
`Google LLC v. RFCyber Corp. / Page 3 of 38
`
`GOOG-1031
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 3 of 38
`
`PGR2022-00003
`Apple EX1031 Page 3
`
`

`

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

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 3 0f 22
`
`US 9,047,601 B2
`
`com
`
`3%:on
`
`58:5$5922,,
`
`
`
`...x\\..m...»r,"5/rN—\N
`
`Enumw$3.8mEmma
`
`
`
`
`8N...,,.,waging.
`mm52M,
`
`gnawa8m,0,$655au0m.mEmEmmmmhmatomnnm
`
`
`
`
`
`
`
`
`
`.0,,,‘..,,,ml_2.m._wwn_0,
`
`
`
`
`
`
`
`EmEmmm£502/,5
`
`<N.OE
`
`
`
`amfi,,,,,6szEfimnmoow
`
`mom/_
`
`
`Emfimmmcmé/.,EEmaEwE
`Emvfiflm../Nmhwzfiwm
`
`EwEmmwsz.mRan.a
`EgEoimhmngflm3N
`magmaM.4x.Mx
`.$36$30mi
`
`SN
`
`3mGooG
`83fo5e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 5 of 38
`
`PGR2022-00003
`Apple EX1031 Page 5
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 4 0f 22
`
`US 9,047,601 B2
`
`
`
`”65935cozmeaam9:>502mm:mm05t085E590.
`
`
`
`
`
`oww=99:Eccmcoco=moEsEE8m5593
`
`
`
`Eccmco850%m£m__nfimm_
`
`
`
`omw8:92:0:6:mm05£5,._53>:23960E_83%o>mEmm
`
`.623m59cozmgaam0595:82
`
`
`
`A_>_w._.m5.3.65386285m5:;
`
`
`co=mo=QQm9:.6»,San989im:.9“.Bo:900
`09563059:83329:3:595m:9:EusEeLo
`
`wa
`
`avg—NEE
`
`ONN
`
`vwm
`
`
`
`wco_w_>oatfiw
`
`
`
`
`
`
`5E5cosmeaam9:Po36%9:
`
`83%250E85:529:
`
`
`
`Eccmco850%mcmfifimw
`
`om_82509%:mm9:5E
`
`«a?9:E$66882wav
`
`MN.GE
`
`3mGooG
`83fO6e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 6 of 38
`
`PGR2022-00003
`Apple EX1031 Page 6
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 5 0f 22
`
`US 9,047,601 B2
`
`omN
`
`UN.GE
`
`
`
`
`
`.wmfivfiummuwizw
`
`
`
`nmfiwwm,wrw
`
`mhwwwfiwmmafiaE
`$leMuwfimfimm5CEW
`
`vmfifigflfikm
`
`
` 83,4
`
`
`
`
`
`3mGooG
`83fo7e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 7 of 38
`
`PGR2022-00003
`Apple EX1031 Page 7
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 6 0f 22
`
`US 9,047,601 B2
`
`
`
`4f
`,1
`
`
`
`
`QN.OE
`
`
`
`
`.rmfigmiwmw#me.Di4
`
`[|I.l
`
`
`4””.meShun.:Owumwzmchumgvmh
`
`
`TUmmMummynomwmmzvucuflwu:A|:
`if;,.._
`
`_
`
` mymtwmmfimmmNmcomwmcnmyafimfldflfl_..L. _5r.Gauflfivmmuwhmd
`
`
`
`
`
`
`
`
`
`.EEMcummnfiflwhaflwh2mm“.
`
`
`
`J-VMMEMUmwfimrmU»Ma-Mm.,mP
` wawmmcomwwfihud_
`
`
`{.
`
`
`
`
`,fiZmJ.ymflbmgnvumfiuwrmhmvcuwwank.“UREGEND.9315.959“.MB,“w.
`
`
`
`
`
`
`
`
`
`02.3.0uflamnaéWW
`
`
`
`MmmDmuwmwmEEO?
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`I.awn—W.COM“MMMHWEOMMIL:C)
`
`5‘3
`
`
`
`Junfomawn?mhuwmm
`
`
`
`mzufimwuuflwmrxjwwwfinbzdwinn“
`
`
`
`
`
`
`
`
`
`m1.”~4N..mu.flou..m.W
`
`
`
`hma.oonu
`
`3mGooG
`83fo8e9aPlnroCre.Dv.CF.RmCILIL
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 8 of 38
`
`PGR2022-00003
`Apple EX1031 Page 8
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 7 0f 22
`
`US 9,047,601 B2
`
`MN.OI
`
`com
`
`Now
`
`EN22658
`
`x03:me
`
`
`
`83%mB@939::35mvcow
`
`cosm>Em>
`
`$339:w
`
`0R9.50:59cozfioqocw85:583%9:.
`NRSuwozaqmo5mEBmmE>92888amm
`ENEmEmmvmtsoEomcmxomnmacawmm
`
`cozmgaam8:5:meme.$09HEmw9:
`
`
`
`
`
`
`ucmco:mo__qqmESoqum35:02
`
`
`
`83%059Sam/iucmEEoow23
`
`3mGooG
`83fO9e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 9 of 38
`
`PGR2022-00003
`Apple EX1031 Page 9
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 8 0f 22
`
`US 9,047,601 B2
`
`
`
`
`
`Lomahogmrmdvvmm
`
`
`
`ooEEEoo8236chOn_co0mmEmEowvcm
`
`
`
`
`
`
`Lou,EmEEmImEExmEom<20>>.63waE9961
`
`owN
`
`
`
`
`
`
`EoEcoL_>cm_886cm.
`
`cmEEcumtoumcmfi
`
`mom$98KwmmzomEoo
`
`
`
`
`
`moLwEEooéooBEEooé
`
`
`
`
`
`momtBEwmwzomEoowwm
`
`"N.OE
`
`Nam\00300
`
`..OESEm—53>l0:0memCmS—
`25m.63%8.3-0
`
`
`
`“:2O”—wwmoo<“0—02)—
`
`859$
`
`
`
`
`
`
`
`Enmton—_OoOH_O._n_EGO_OQO#O._n_
`
`
`
`Ecozocsuo_mc_wUmo:me
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`3mGooG
`83fOo1egaPla.
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 10 of 38
`
`PGR2022-00003
`Apple EX1031 Page 10
`
`

`

`US. Patent
`
`HJ
`
`5
`
`099
`
`2Bm
`
`mwow52mm
`
`2,2%co_ao__&<8m2%
`
`
`
`
`n.mc:m_xm_5023298961@923262
`
`6Im<mwt
`
`SIIIIIIIIIIIIIIIIIIIIIIIIIIIJUu_"3%mSHEEN_
`
`0_u9muwu:muh"LommcmE
`Ewo"
`2"Em65%"58$.mm3.590"£96380
`
`mSm
`
`3mGooG
`83fo11e9aPla.roCrebV.CFRv.CLLb9ooG
`
`oom
`
`U0Nt0£3<
`
`_mcc0m._on_
`
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 11 of 38
`
`PGR2022-00003
`Apple EX1031 Page 11
`
`

`

`US. Patent
`
`m
`
`409,S
`
`2B
`
`m.mMmGE
`
`n.Ucm#6362m“5.26;
`
`2,vmm29me
`
`U...........................Jm3mm.9325m2mu2__mmmmmmam_55:2mumsu:mu"memcmE
`Emo"uuu
`
`SEE
`
`2%
`
`mom
`
`
`
`8.590262
`
`mom_>_<w
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`3mGooG
`83fO21egaPla.
`
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 12 of 38
`
`PGR2022-00003
`Apple EX1031 Page 12
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 11 0f 22
`
`US 9,047,601 B2
`
`
`
`Um..GE
`
`hboszcomLmQ
`
`Em0.m9m5cam_>_<wmczexmcmw_>mEQSmwmaH__>_BSmcmo
`83mmQ:E66%mquécm95_>_<wmcsflxm0559,38
`
`
`
`
`
`u69.9%m93:569:“mm
`
`02m.
`
`camEccmgo3:8mem53989EmEov3:88ceswozqammm:
`
`
`wmm_>_<m@92326:9:$0258$5EB928:930859099960
`
`
`wmm655%350mmm525.3%9EmEou3:30mecorneaamom:
`
`
`
`93::
`83%9:c_63%859mcm0cm_>_<mcormtoamcmb9525cm5958
`
`
`
`83%9:E66%@225cmcam_>_<mmmSa-w26:cm5938
`
`8355883
`
`Emo9:E0:0.mgmtocmmm
`
`
`
`
`
`Nmmn:930Evcm_>_<w9.52me05m_>883:5cmB938::chth993mm
`
`
`
`85:809:vcm_>_<m9:2505coma/En
`
`83%9:c_66%8590cm98
`
`
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`3mGooG
`83fO31egaPla.
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 13 of 38
`
`PGR2022-00003
`Apple EX1031 Page 13
`
`

`

`US. Patent
`
`22,
`
`1mh
`
`22
`
`U
`
`M0,
`
`2B
`
`1Im,3»GE
`
`Mw;xcmg05E0:3:0qumwagom
`
`
`
`Mm.8%?
`2mmcoawm:05
`mm53%33$950:59mmvcmm65:2
`Swow66E9:93:88;mmmmoquommSQm
`
`m.5939:3:59:38$92EJvowU__m>meEwEta66::mm_>“$3chaSEE.
`
`N38%?t.xcmg9:8:onm950:58
`
`
`
`
`Lflmcm:UcEmEma;ccmEsooommcficoqmotoombcm>
`
`O‘
`
`1'
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`3mGooG
`83fO41egaPla.
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 14 of 38
`
`PGR2022-00003
`Apple EX1031 Page 14
`
`

`

`US. Patent
`
`HJ
`
`m2
`
`S
`
`3
`
`U
`
`4
`
`2
`
`
`
`ccm863259:9HmccmEEoombcwmucmbaccmfismDom/«9:moat?35am.
`omm9Cenommcm:a$88:
`
`
`
`
`
`n.m;$59GGE.989:9.3EmmccmEEooDan?“0968Ucm9556:2
`
`
`
`
`
`m;093me£036:ac_838:58:8me052950“.
`
`
`
`
`
`
`
`Dan?cmwofisELQ“m5“BEE059.Eva:mwEEocmoHmmv$38E95805B50:59€036:mc_m0.060qu
`
`
`
`
`
`M,mvwt
`
`1P0l6,my7I.0:
`
`Bmm.
`
`SV.
`
`
`5.588%m99950mMG
`3n_n_<9:Stam.n59EL8$8on25me82.8%?05L88599m_omcoamm:
`
`
`
`v.Cu.
`
`b
`
`mn4.mm=1.
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 15 of 38
`
`PGR2022-00003
`Apple EX1031 Page 15
`
`

`

`US. Patent
`
`Jun.2,2015
`
`Sheet140f22
`
`US 9,047,601 B2
`
`UV.OE
`
`wmw
`
`“03:2 BESEm.Q
`
`
`9635;{9,302EoE>wn_
`xcmmwLmEowUcm
`
`
`83-o
`
`vaovvvww
`
`
`
`.ma.ooG
`
`I.
`
`3mGooG
`83fo61e9aPI.RroCre.Dv.CF.RmCI.
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 16 of 38
`
`PGR2022-00003
`Apple EX1031 Page 16
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 15 of 22
`
`US 9,047,601 B2
`
`«6GE
`
`
`
`EmEoE850mm
`
`am8888$229:55252.|mmmwommcmg835m
`
`
`
`
`NmmEQQ<co:_mo__qq<mwmEmmcmEEmun5
`
`
`
`
`
`
`
`
`3968?.5968mm
`
`8m3m
`
`
`
`NE_>_<wco:mo__aq<
`
`
`
`EmeoaomNEoB_>_<m10$2.38.“.833m53%@9095
`
`0%m0250\“wage;__
`
`55:8
`
`omm€03sz
`
`mcozmoEsEEoox
`
`/wE
`Eccmco
`
`bosomw
`
`onco_umo__aq<cosmo=qa<3968mm---$595
`“06:2“0594mom
`
`
`
`
`
`
`
`
`
`
`
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`3mGooG
`83fO71egaPla.
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 17 of 38
`
`PGR2022-00003
`Apple EX1031 Page 17
`
`

`

`US. Patent
`
`2
`
`
`
`
`
`J,EmEmaowNBm8m25no2025a83me52$€685
`
`
`
`HxmCm3.5;56252
`
`{oéwzx
`
`EwEo‘QEEwmm55350
`
`
`|@950quEotwoamm3968mm
`
`vm56:26325985
`
`wowwowmom
`
`
`
`
`
`
`
`
`oo_>mn_%@5981an\2mmm65:2co=8__&<mmm3595.283.5%858mmM/\mmm53%:Mvmm0mm\83.6wmbcmnmmmm
`_mmozoficoouNb22m6&chw.
`Rm3603co_Eo__o_q<mmm53:5228noA:IIIIIIIII583.mL------.\----
`
`
`
`1Iw,mmatm,MEOEQE
`UOLDOGwAw0’r9mSwmm5525wUFvmmR.
`BWW.
`
`18330cl4Omm
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 18 of 38
`
`PGR2022-00003
`Apple EX1031 Page 18
`
`

`

`US. Patent
`
`HJ
`
`5m
`
`71ae
`
`4099w
`
`2B
`
`m.mUmGE
`
`
`
`
`
`$90.25:8:qu325500
`
`
`H,53:0me:0Emma95m:
`
`
`n.wcozmgaqfiwwgiwwwU_>9n_
`
`
`
`«m355qumcozmozqqfimogiwm
`
`
`
`c9098:99:vcmvmoEBoD
`
`
`
`
`
`2wmm880:tBESEQucmm9.9ancoumoE30cwe.mN__mcow$n_
`
`
`
`
`
`
`
`mmm60:52835mmucom
`
`0 L
`
`0
`
`
`
`
`
`
`.lOC.lebV.CFRv.CLLbg0OG
`
`3mGooG
`83fO91egaPla.
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 19 of 38
`
`PGR2022-00003
`Apple EX1031 Page 19
`
`

`

`US. Patent
`
`m
`
`f
`
`n.omm{050.2mwcozmoEsEEoo
`
`2,.wE:69
`
`5:88Lomcozommcmb
`s08K._
`
`MANN/Mam“.:0szon
`
`MfieHucmnmwmm
`
`5260_..
`
`r
`
`8:888...moi
`
`mrmLOEGW
`
`2maBGw1P0I/6,n7<0O~H~m88:8mM,
`8395m9c963mSm.Ummo_F
`9::EB/"Cmgm:wEm930mbmg2%won.#mcwm.nm.
`conommcmb_DV“.
`
`wn4.m.G0
`
`
`
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 20 of 38
`
`PGR2022-00003
`Apple EX1031 Page 20
`
`

`

`2Bm
`
`6Iammat
`
`US. Patent
`
`m2,
`
`h
`
`09,SU
`
`MEmm8mm555mm{9562Eom<
`mOn_
`
`
`
`0................................................./w«mmmwhommcmm0mvcmfimwmmN_>_n_Lovmom
`
`s08K._
`8300n5oEmtom._
`
`mmmzoficoo
`
`
`
`EoEom.850me
`
`mmm
`
`
`
`wmo_>_<mwOn_4/
`
`/
`
`
`
`
`
`cozomwcmt.wOn_EmEooo__p:n_
`
`8508
`
`mE65.20
`
`mmo@5950
`
`
`
`
`3mGooG
`83fo12e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 21 of 38
`
`PGR2022-00003
`Apple EX1031 Page 21
`
`

`

`US. Patent
`
`n.
`
`22,
`
`22f00
`
`99S
`
`2B1069
`
`7Im00GE
`
`
`
`UEBBELocozommcmh:83
`
`
`
`
`
`53mmUcmxomnEwcozommcgumoa:
`
`
`
`
`
`c963E0:EsoEm83:836:83
`
`
`
`5$39_w3.__>Lomm89‘39.m€8th
`
`m3:399::wcoxoy%0mm:5.-w:_8:38%_to£96599:m
`
`.oo-wmR0cv_u.u:>
`
`
`
`58:83mE0:c303cm@533.
`
`0L
`
`O0
`
`
`
`
`
`
`
`
`3mGooG
`83fo22e9aPla.roCrebV.CFRv.CLLb9ooG
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 22 of 38
`
`PGR2022-00003
`Apple EX1031 Page 22
`
`

`

`US. Patent
`
`Jun. 2, 2015
`
`Sheet 21 0f 22
`
`US 9,047,601 B2
`
`Q0.GE
`
`wwo
`
`
`
`germoctm>5+_>_<wmOn_9£639:EEcooEmu9:Emzcou
`
`
`
`_>_<mmOn_LEEcozommcmb>w_am_n_
`
`cozomwcm:9:8982mm:
`
`
`
`
`
`
`
`
`
`8528cmsofi
`
`5onc_
`
`
`
`mmosmfi8395
`
`
`
`-o9H.832mmmcoSQREEcmccmm
`
`
`
`$9383P683%umfimco:39
`
`Nwm
`
`
`
`
`
`no05EOt.wwcoamg“5200905902:0“—
`
`
`
`
`
`_>_<wmo.“—OH®o_>®_oDEQmaCOxOy
`
`
`
`
`_2<mmo;E2».
`
`
`
`0<_>_mm:_:_mEoo59‘.me:23m9603.
`
`
`
`:96:9#8352:chon“ccmw
`
`596$Emu983%uwfimcm
`
`Nww
`
`
`
`
`
`EmEmEomucmcosmoccgcozowmcg.6»,mo<_>_
`
`
`
`
`
`
`
`
`
`EcoEbum96202mummmoEE.__E8Emuw>_moom
`
`
`
`
`
`3mGooG
`83fO32e9aPla.rOCrebV.CFRv.CLLb9OOG
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 23 of 38
`
`PGR2022-00003
`Apple EX1031 Page 23
`
`

`

`US. Patent
`
`|
`
`o\c
`
`.\
`
`_|IIIIIIIIIIIIIIIJ.\.uEmx.
`
`EEm>w"KmEm“58285mEgg2%
`
`mEmEEooé2,"Cezmzommm"ogzomExozéJm8E0xommm_IIIIIIIIIIIIIIII_J..
`
`s6%:/u................"bm>__ouucm
`5uoE"ommcoSQHoxo:m_E226TI........ONN525$
`
`
`oEmEEoQoUcma$283“96:m96283
`
`
`
`.mf9:cM.._O>Lm>=mu
`co_umo__qa<vmnmquom.n9:96:
`@250m0K-ofiwton.L
`
`2maBGm1I0/6,NQ\H§m.7O4cM,vmwa$93K.w.mc.2850omwEmEQm
`8503m.0:0EOmooToR98H_o:v:)8“v.
`
`
`
`18mm4OG4
`
`
`
`
`
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 24 of 38
`
`PGR2022-00003
`Apple EX1031 Page 24
`
`

`

`US 9,047,601 B2
`
`1
`METHOD AND APPARATL S FOR SETTLING
`PAYMENTS USING MOBILE DEVICES
`
`BACKGROUND OF THE INVENTION
`
`
`
`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 communication range,
`2. The Background of Related Art
`For many credit or debit card transactions, the payment
`process is started by a customer asking for a bill when check—
`ing out a purchase. A cashier or service member brings a bill
`to the customer for verification. The customer then hands out
`a credit/debit card to the service staff member. The service
`member brings the card to a Point of Sales (POS) counter to
`initiate a transaction payment. The service member then
`brings back a receipt to the customer for signature to autho-
`rize the transaction. It is a lengthy process that typically takes
`a couple ofminutes or much longer when the service member
`has to take care ofmultiple payment transactions at a time. In
`addition, in the ca se for the debit card transactions. the pro-
`cess may be even more troublesome when a 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. Thus there is an oppor—
`tunity of using a mobile device to quickly settle the payment
`at a point of sale (POS).
`
`
`SUMMARY OF TH e lNV *NTlON
`
`
`10
`
`15
`
`30
`
`This section is for the purpose of summarizing some
`aspects ofthe present invention and to briefly introduce some
`preferred embodiments. Simplifications or omissions may be
`made to avoid obscuring the purpose of the section. Such
`simplifications or omissions are not intended to limit the
`scope of the present invention.
`The present invention is related to techniques for mobile
`devices configured to support settlement of charges in elec-
`tronic invoices or bills. According to one aspect ofthe present
`invention, 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 including the electronic invoice and other
`information regarding the mobile device or an owner thereof
`is read off wirelessly into the \IFC mobile device. After the
`user verifies the amount being charged and authorizes the
`payment, the NFC mobile device communicates with a pay-
`ment gateway or network for 3ayment that is configured to
`proceed with the payment in accordance with a chosen pay-
`ment methods,
`According to another aspec of the present invention, the
`mobile device is a contactless card or part ofa point of sale
`(POS) machine used to generate the electronic invoice. One
`embodiment of the present invention provides unanticipated
`benefits and advantages in an a splication in which a payment
`process would otherwise have to be involved in more than one
`contacts between a merchant and the consumer. One of such
`applications is a payment process in a restaurant, where a
`consumer is given a check first or verification and a chance to
`add a gratitude before a final charge is determined and paid.
`Using the NFC mobile device, the consumer can finish the
`payment using a cho sen payment method at the point of sale
`without further contacting the merchant.
`
`
`
`35
`
`4O
`
`45
`
`5O
`
`55
`
`60
`
`65
`
`2
`According to still another aspect of the present invention, 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-
`ment infrastructure (e.g., money transfer or credit card/debit).
`A payment response is sent to the merchant once a payment is
`delivered to a designed account by the merchant.
`According to still another aspect of the present invention,
`the mobile device being used by the consumer is itself an
`electronic purse. Thus the consumer operates his/her mobile
`device to settle the charge once the electronic invoice is
`received and displayed thereon.
`According to still another aspect of the present invention,
`the mobile device used by the consumer is 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 what is 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, managed or replaced after they
`are respectively provisioned via the Trusted Service Manager
`(i.e., the TSM server). One of the modules being installed in
`the POS machine or an NFC device used by the merchant is
`referred to as Smart Bill Payment. The module is configured
`to facilitate the communication between the merchant (its
`device) and the user (hi 5/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—
`mented as a single device, a server, a system or a part of
`system. It is believed that various implementations may lead
`to results that may not be achieved conventionally.
`According to one embodiment, the present invention is a
`method for settling a payment, the method comprises: pro-
`viding a software module to be executed in a first mobile
`device embedded with a secure element, wherein the secure
`element has been personalized and the software module is
`provisioned with the personalized secure element, the first
`mobile device is configured to include data pertaining to an
`electronic invoice; receiving a payment request from a second
`mobile device after a user ofthe second mobile device autho—
`rizes the payment to the electronic invoice transported wire—
`les sly from the first mobile device, wherein the second mobile
`device is a near-field communication device and is configured
`to execute an application that communicates with the soft-
`ware 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. In the embodi-
`ment, the second mobile device includes a display screen and
`is caused to display the electronic invoice when the data is in
`the second mobile device.
`According to another embodiment, the present invention is
`a gateway provided for settling a payment, the gateway may
`include a server or a collection of servers. The gateway com-
`prises a portal providing a software module to be downloaded
`and executed in a first mobile device embedded with a secure
`element, wherein the secure element has been personalized
`and the software module is provisioned with the personalized
`secure element,
`the first mobile device is configured to
`include data pertaining to an electronic invoice. The gateway
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 25 of 38
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 25 of 38
`
`PGR2022-00003
`Apple EX1031 Page 25
`
`

`

`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 perform operations of:
`receiving a payment request from a second mobile device
`after a user of the second mobile device authori7es the
`
`payment to the electronic invoice transported Wireles sly
`from the 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
`conj metion with the attached drawings.
`
`BRIEF DESCRIPTION OF TI I: E DRAWINGS
`
`10
`
`15
`
`Tie 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:
`3 G. 1A shows a system configuration according to one
`embodiment of the present invention, where the payment
`network represents a collection of services or networks pro-
`vic ed to settle payments via a financial institution;
`3 G. 1B shows a flowchart or process of settling a payment
`according to one embodiment where the process may be
`im olementcdin software or a combination of software and
`hardware;
`3 G. 2A shows a mobile payment ecosystem in which
`related parties are shown in order for the mobile payment
`ecosystem successful;
`ii
`G. 2B shows a flowchart or process of provisioning one
`or more applications according to one embodiment;
`3 G. 2C shows a data flow illustrating various interactions
`among different parties when an application is being provi-
`sioned1n one embodiment,
`3 G 2D shows a data flow among different entities when
`preparing the application data1n provisioning an application;
`3.G 2E shows a flowchart or process for locking or dis-
`abling an installed application,
`G. 2F shows an exemplary architecture diagram of a
`portable device enabled as an e—purse conducting e—com—
`merce and m-commerce, according to one embodiment ofthe
`present invention;
`3 G. 3A is a block diagram of related modules interacting
`with each other to achieve what is referred to herein as e-purse
`personalization by an authorized personnel (a.k.a., personal-
`izing a mobile device or a secure element therein while pro-
`visioning an application);
`FIG. 3B shows a block diagram of related modules inter-
`acting With each other to achieve what is referred to herein as
`c-purse personalization by a user of the e-pursc;
`FIG. 3C shows a flowchart or process of personalizing an
`e—purse according to one embodiment of the present inven—
`tion;
`FIG. 4A and FIG. 4B show together a flowchart or process
`of financing, funding, load or top-up an e-purse according to
`one embodiment of the present invention;
`FIG. 4C shows an exemplary block diagram of related
`blocks interacting with each other to achieve the process FIG .
`4A and FIG, 4B;
`
`4
`FIG. 5A is a diagram showing a first exemplary architec—
`ture of a portable device for enabling e—commerce and
`m—commerce functionalities over a cellular communications
`network (i.e., 3G, LTE or GPRS network), according an
`embodiment of the present invention;
`FIG. 5B is a diagram showing a second exemplary archi-
`tecture of a portable device for enabling e-commerce and
`m-conunerce 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 embodiment of the present invention;
`FIG. 6A is a diagram showing an exemplary architecture,
`in which a portable device is enabled as a mobile POS con—
`ducting e—commerce and m—commerce, according to one
`embodiment of the present invention;
`FIG. 6B is a diagram showing an exemplary architecture,
`in which a portable device is enabled as a mobile POS corr-
`ducting a transaction upload operation over a network,
`according to an embodiment of the present invention;
`FIG. 6C is a flowchart illustrating an exemplary process of
`conducting m-commerce u sing the portable device enabled a s
`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 inulti—
`functional card; and
`FIG. 7 is a diagram depicting an exemplary configuration
`in which a portable device used for an e-ticking application.
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`In the following description, numerous specific 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 experienced or skilled in
`the art to effectively convey the substance of their work to
`others skilled in the art. 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" means that a particular feature, structure, or character-
`istic described in connection with the embodiment can be
`included in at least one implementation of the invention. The
`appearances of the phrase “in one embodiment” or “in the
`embodimen ” in various places in the specification are not
`necessarily all referring to the same embodiment, nor are
`separate or alternative embodiments mutually exclusive of
`other embodiments. Further, the order of blocks in process,
`floweharts or functional diagrams representing one or more
`embodiments do not inherently indicate any particular order
`nor imply limitations in the invention. As used in this speci—
`fication and the appended claims, the singular forms “a,”
`“an,” and “the” include plural referents unless the context
`clearly dictates otherwise. It should also be noted that the
`term “or” is generally employed in its sense including “and/
`or” unless the context clearly dictates otherwise.
`Embodiments ofthe present invention are discussed herein
`with reference to FIGS. 1A-7. However, those skilled in the
`art will readily appreciate that the detailed description given
`
`I
`
`
`30
`
`35
`
`4O
`
`45
`
`50
`
`55
`
`60
`
`65
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 26 of 38
`
`GOOG-1031
`Google LLC v. RFCyber Corp. / Page 26 of 38
`
`PGR2022-00003
`Apple EX1031 Page 26
`
`

`

`US 9,047,601 B2
`
`5
`herein with respect to these figures is for explanatory pur—
`poses only as the invention extends beyond these limited
`embodiments.
`Near Field Communication (NFC) presents significant
`business opportunities when used in mobile devices for appli-
`cations such as payment, transport ticketing, loyalty, physical
`access