(12) United States Patent
`US 10,600,046 B2
`(10) Patent No.:
`
`Xie et al.
`(45) Date of Patent:
`Mar. 24, 2020
`
`USOlO600046B2
`
`(58) Field of Classification Search
`CFC ............. UOGQ 20/3278; GOGQ 20/204; GOGQ
`20/3223; G06Q 20/20; G06Q 30/04;
`(Continued)
`References Cited
`
`(56)
`
`U~S~ PATENT DOCUMENTS
`7,962,369 132*
`6/2011 Rosenberg
`
`3,172,135 B1 *
`
`5/2012 Aidasani
`
`G06Q 20/20
`705/261
`............ G06Q 20/4012
`235/379
`
`(Continued)
`
`
`FOREIGN PATENT DOCUMENTS
`l1073542 A *
`3/1999
`
`WO-2012000438 A1 *
`
`1/2012
`
`......... G07F 7/0866
`
`OTHER PUBLICATIONS
`
`JP
`
`WO
`
`MasterCard International Incorporated, Partnering for performance
`7'th —b
`'
`lt'
`.
`.8.*
`“I
`e “mess ”“10“ p
`Primary Examiner 7 Ashford S Hayles
`(74) Attorney, Agent, or Firm 7 Joe Zheng
`
`ABSTRACT
`(57)
`Techniques for mobile devices configured to support settle-
`ment of charges in electronic invoices or bills are described.
`An NFC mobile device is used to read off from a PCS device
`data pertaining to the electronic invoices for payment. The
`ata me u es t e e ectronic 1nv01ce an 0 er in ormation
`d
`'ld hl "' dth'f
`'
`regarding a registered user of the POS device or an owner
`thereof is. After the user verifies the amount being charged
`and authorizes the payment, the NFC mobile device com-
`municates with a payment gateway or network for payment
`that is configured to proceed with the payment in accordance
`with a chosen payment methods.
`20 Claims, 22 Drawing Sheets
`
`(54) METHOD AND APPARATUS FOR MOBILE
`PAYMENTS
`
`(71) Applicant: EJFSyber Corporation, Fremont, CA
`(72)
`Inventors: Xiangzllen Xie, Shenzhen (CN); Liang
`Seng Koh, Fremont, CA (US); IIsin
`Pa“, Fremont: CA (US)
`a
`_
`,
`(73) Ass1gnee: RFCyber Corporation, Frement, LA
`(US)
`_
`_
`_
`_
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 438 days.
`
`_
`_
`( ’5 ) Notice:
`
`(2]) App]. No.: 14/728,349
`
`(22) Filed:
`
`Jun. 2, 2015
`
`(65)
`
`Prior Publication Data
`
`US 2015/0278800 A1
`
`Oct. 1, 2015
`
`Related US. Application Data
`(63) Continuation 0f application N0~ 13/853,937: filed on
`Mar. 29, 2013. HOW Pat. NO- 9,047,601, Wthh 15 a
`(Continued)
`
`-
`
`11 -
`(51)ItCl
`G06Q 20/32
`G06Q 20/10
`
`(2012.01)
`(2012.01)
`(Continued)
`
`(52) U.S. Cl.
`CPC ....... G06Q 20/32 78 (2013.01); G06Q 20/102
`(201301); G06Q 20/20 (201301);
`(Continued)
`
`100
`
`Day'nem Newark
`
`
`Payment Authorization Request
`
`Smart 5161 Payment Gateway 104
` \
`PaymentAulhofizalion
`<
`/‘
`Payment info with 7’
`\‘Resnonse
`etPf‘JJr‘nil: bitl /
`
`
`
`h 00
`105
`”arsenal NFC device
`reader OR NFC mewce with
` \
`
`wilh watlet soflware 110
`SE {such as Mnbxle PCS.)
`
`
`/
`Beetroot: hell
` stgned exectmnic b0 \1
`10$
`1
`arm .
`FC
`1
`devices) win smart
`n: I applet
`
` lied mm a 5
`
`eleccmwe I)
`
`
`
`Smart an gateway verifies m- electmmc 11.11 and m pm; 11 the
`came—r. new: [S ‘99; :hanme n-lled emomt.
`
`
`5mm ‘00;
`away Uses the new;
`anci’d‘ vary/r1!
`mam respo:
`
`134
`
`
`
`3 13:09 :avend war: w gazewavlor amwssme
`
` 1:137}havkm"Umermawt
`
`
`
`
` y er orp. age 0
`
`
`
`J
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 1 of 39
`
`PGR2022-00003
`Apple EX1001 Page 1
`
`

`

`US 10,600,046 B2
`
`Page 2
`
`Related US. Application Data
`
`continuation-in-part of application NO- ”350,832,
`filed on Jan. 16, 2012, now abandoned, which is 21
`continuation-in—part of application No. 11,534,653’
`filed on Sep. 24, 2006, HOW Pat. No. 8,118,218.
`
`(51)
`
`(60) Provisional application No, 61/618,802, filed onApn
`1’ 2012'
`‘
`Int- Cl-
`G06Q 20/34
`G06Q 20/36
`G06Q 20/40
`G06Q 30/06
`GIMQ 20/20
`G06Q 30/04
`(52) U.S. C1.
`CPC ....... G06Q 20/204 (2013.01); G06Q 20/3223
`(2013.01); G06Q 20/3227 (2013.01); G06Q
`20/352 (2013.01) G06Q 20/3552 (2013.01)
`’
`_
`’
`G06Q 20/3672 (2013.01); G06Q 20/40
`(201301); G06Q 30/04 (201301); G06Q
`30/060] (2013.01)
`
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`(2012.01)
`
`(58) Field of Classification Search
`CPC ............... G06Q 20/102; G06Q 20/352; G06Q
`20/3;52. G06Q 20/3672‘ G060 20/40.
`”
`2
`'
`, 2
`'
`’
`UOGQ 30/0601: (JOGQ 208227
`USPC ............................................................ 703/21
`See application file for complete search history.
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`8,196,131 1317
`
`8,270,578 1327
`
`8,341,083 1317
`
`12/2012 Jain
`
`8,577,731 1317
`
`8,646,059 1317
`
`2/2014 von 136hron .........
`
`2004/0127256 A :1:
`
`6/2012 V0n Behren ......... GO6Q 20/367
`705/64
`9/2012 Poniatowski
`.......... G06Q 30/06
`235462.45
`
`..... 11041. 63/083
`705/41
`8,565,676 1327 10/2013 Gormley ......... H04M1/274516
`455/41.l
`
`11/2013 Cope ........... G06Q 20/3224
`705/17
`8,601,266 B27 12/2013 Aabye ................... G06F 21/445
`713/168
`(106Q 20/367
`719/311
`77/2004 Goldthwaite ........ GOGK 7/0004
`455/558
`
`........ .
`. G06Q 50/12
`705/15
`/2007 H0 ......................... G06K 19/07
`235/492
`
`G06Q 20/341
`235/492
`5/2008 Cox ....................... G06Q 20/20
`705/67
`
`. G06Q 20/32
`455/414.1
`/2009 Bishop ................... G06Q 20/02
`705/19
`.......... G06Q 20/0855
`705/67
`11/2009 Bishop ................... G06Q 20/02
`235/379
`2009/0307140 A 7 12/2009 Mardikar ........... G06Q 20/1085
`705/71
`5/2010 Skowronek ............ G06Q 20/40
`705/44
`
`2006/0085266 A 7
`
`2007/0131780 A 7
`
`2008/0093467 A 7
`
`2008/0126260 A 7
`
`2008/0167017 A 7
`
`2009/0164330 A 7
`
`4/2006 Wei
`
`4/2008 Narendra
`
`7/2008 \Ventker
`
`2009/0248579 A 7 10/2009 Karninskl
`
`2009/0289106 A 7
`
`2010/0114773 A 7
`
`
`
`20 0/0211504 A *
`
`8/2010 Aabye
`
`20 0/0213253 A 7
`
`G06Q 20/10
`705/44
`8/2010 Wollbrand ....... G06K19/07769
`235/380
`G06Q 20/10
`20 0/0274677 A * 10/2010 Florek
`7057/16
`20 0/0274726 A 7 10/2010 Florek .................... G06Q 20/20
`705/72
`
`
`
`20 1/0042456 A 7
`
`20 1/0066550 A 7
`
`20 1/0078081 A *
`720 1/0087610 A 7
`
`(wiggle/60:
`20 0/0306076 A 7 12/2010 Taveall
`20 0/0325048 A 7 12/2010 Carlson .................. G06Q 20/20
`705/44
`G06Q 20/20
`235580
`Shank ................ G06Q 20/1085
`705/43
`G06Q 20/32
`Pil'zadeh ..
`705/44
`Batada .................... G06F 21/72
`705,318
`Florek .................... G06Q 20/20
`705/50
`Corda .................... G06Q 20/32
`5/201
`,
`.
`726/3
`.............
`7
`/
`'
`Rhellml
`G06Ix41595€2711?
`5/201
`6/201 Mastrangclo ........ GO6Q 20/352
`235/379
`7/201 Gallagher .......... G06Q 20/0425
`7,
`205/1427
`7/201 Narcndra ........... (1061\19/0701
`235/492
`10/201 Kelly ..................... G06Q 20/14
`705/40
`10/201 Weiss ...................... 60614 21/32
`705/44
`
`2011/0112968 A 7
`
`2011/0113473 A 7
`2
`7
`
`011/0117839 A
`20 1/0155800 A 7
`
`20 1/0173060 A 7
`
`7.0 1/0180610 A *
`20 1/0251952 A 7
`
`20 1/0258120 A *
`
`20 2/0072309 A 7
`20 2/007 792 A 7
`
`20 2/0116963 A ’1
`
`20 2/0118952 A 7
`
`20 2/0136786 A ’1
`
`20 2/0143702 A 7
`
`20 2/0166333 A 7‘
`
`20 2/0178433 A *
`
`20 2/0239566 A *
`
`2/201 Masaryk ..
`
`3/201
`
`3/201
`4/201
`
`5/201
`
`
`
`5/2012 Romagnoli
`
`9/2012 Everett
`
`11/2012 Mullen
`
`11/2012 Cames
`
`1/2013 Kannappan ..
`
`2/2013 Brendell
`
`2/2013 Brendell
`
`2/2013 Brendell
`
`..
`
`
`
`
`
`3/2012 Hultberg ................ G06Q 20/32
`705/26.41
`3/2012 Bacastow .......... G06Q 20/3223
`705/44
`5/2012 Klein ................... GO6Q 20/102
`705/40
`5/2012 Norair .................. 006K 7/0008
`235/380
`............ G06Q 20/10
`705/44
`6/2012 llo ......................... G06Q 20/10
`705/16
`6/2012 von Behren ........... G06Q 20/10
`705/41
`7/2012 Narendra ......... G06K19/06187
`455/420
`.................. G06Q 20/10
`705/41
`G06Q 20/29
`705/26.41
`11/2012 Dryer ................. G06Q 201/3278
`705/1423
`G06Q10/00
`705/39
`11/2012 Lu ........................ GO6Q 20/352
`705/41
`H04L 9/3234
`726/3
`20 2/0317628 A * 12/2012 Yeager ................. GO6Q 20/204
`726/5
`G06Q 20/40
`705/71
`.............. GO6Q 20/325
`235/380
`................ G06Q 20/12
`705/26.41
`G06Q 20/3276
`705/26.41
`3/2013 Barton ............... G06Q 20/3223
`705/1423
`
`20 2/0253974 A * 10/2012 Haikonen
`
`20 2/0290376 A *
`
`20 2/0290472 A *
`
`20 2/0296819 A 7
`
`20 2/0304255 A 7
`
`20 3/0024333 A 7
`
`20 3/0048717 A *
`
`20 3/0054412 A 7
`
`20 3/0054413 A 7
`
`20 3/0060618 A 7
`
`
`
`
` y er orp. age 0
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 2 of 39
`
`PGR2022-00003
`Apple EX1001 Page 2
`
`

`

`2013/0060699 A ""
`
`2013/ 097031 A *
`2013/0097080 A '1‘
`
`2013/
`
`03574 A *
`
`2013/0 24349 A ’1‘
`
`2013/0 38517 A ’1‘
`
`32219 A *
`
`38518 A *
`
`40360 A *
`
`2013/0 38959 A ""
`
`2013/
`
`2013/
`
`2013/
`
`2013/
`
`2013/0 44731 A ""
`
`51292 A *
`
`2013/0 51400 A *
`
`52185 A *
`2013/
`2013/0 60134 A ”‘
`
`
`
`
`
`US 10,600,046 B2
`
`Page 3
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`20 3/0171929 A *
`20 3/0173736 A *
`
`7/2013 Adams
`7/2013 Krzeminski
`
`3/2013 Romagnoli
`
`............ G06Q 20/10
`705/44
`4/2013 Royyuru ................ GUéQ 20/20
`705/16
`/2013 Smets ....................... G06T 1/20
`705/44
`/2013 Conrad .................. GUéQ 20/36
`705/39
`5/2013 Khan ..................... G06Q 20/36
`705/21
`5/2013 Liberty 1111111111111111 GO6Q 20/202
`705/21
`5/2013 Khan ..................... G06Q 30/00
`705/l6
`5/2013 White rrrrrrrrrrrrrrrrrr GO6Q 20/204
`705/16
`5/2013 Pelly ....................... H04L 9/083
`713/168
`6/2013 Graylin ............... G06Q 20/322
`235/380
`/2013 Baldwin ................ G06Q 20/20
`705/17
`6/2013 Van Deloo ............. G06Q 10/02
`705/5
`
`H04W 12/08
`705/39
`6/2013 Singh .................... G06F 21/35
`726/9
`6/2013 Marcovecchio
`G06Q 20/3563
`726/26
`
`6/2013 Makhotin
`
`H04W4/80
`455/411
`.......... H04W 12/10
`709/213
`G06Q 20/1085
`705/71
`8/2013 Spodak .................... GOSB 1/01
`340/565
`8/2013 Fisher
`H04B 11/00
`455/41.1
`................. G06Q 20/32
`705/42
`G06Q 20/3672
`235/379
`8/2013 Landrok ................ G06Q 20/32
`705/67
`G06Q 20/40
`705/41
`9/2013 Royyuru .............. GO6Q 20/382
`705/39
`20 3/0334318 A * 12/2013 Wakerly ............. G06Q 20/3576
`235/492
`rrrrrrrrrrrrrrrr G06Q 20/3227
`705/71
`20 3/0346305 A * 12/2013 Mendes ............... GO6Q 20/351
`705/41
`1/2014 Kuhn ..................... G06Q 20/36
`705/41
`G06F21/32
`726/5
`................... GO6Q 20/322
`705/41
`
`
`
`20 3/0198086 A *
`
`20 3/0200999 A *
`20 3/0203345 A *
`
`20 3/0218766 A *
`
`20 3/0221092 A *
`
`20 3/0226812 A *
`
`20 3/0246258 A *
`
`20 3/0254102 A *
`
`20 3/0339253 A *
`
`20 4/0012751 A *
`
`20 4/0013406 A *
`
`20 4/0095332 A *
`
`
`
`8/2013 Mardikar
`
`8/2013 Mueller
`
`8/2013 Kushevsky ..
`
`9/2013 Dessert
`
`12/2013 Sincai
`
`1/2014 Tremlet
`
`4/2014 Dcsai
`
`
`
`* ci ed by examiner
`
`
`
`
` y er orp. age 0
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 3 of 39
`
`PGR2022-00003
`Apple EX1001 Page 3
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 1 of 22
`
`US 10,600,046 B2
`
`100
`
`Payment Network
`
`
`
`
`Payment Authorization Request
`
`Smart Biii Payment Gateway 104
`
`
`
`Payment Authorization
`Response
`
`
`Payment info with
`eiectronic biii
`
`
`
`
`POS with contactiess
`106
`
`Persona! NFC device
`
`reader OR NFC device with
`
`with waiiet software
`
`
`SE (such as Mobile POS)
`110
`
`
`Contactiess smart
`
`Signed eiectronic biii
`card (or secure
`element in NFC
`
`
`
`Eiectronic b.”
`
`
`
`
`devices) with smart
`biii appiet
`108
`
`
`
`
`
`FIG. 1A
`
`
`
`
`
`
`
`
` ooge V. y er orp. age 0
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 4 of 39
`
`PGR2022-00003
`Apple EX1001 Page 4
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 2 of 22
`
`US 10,600,046 B2
`
` 120
`
`Merchant POS prepares an electronic bill and writes to a
`smart bill 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 smart bill enabled
`
`
`
`wallet application retrieves the electronic bill signed by the
`smart bill applet
`
`
`Electronic bill is displayed on the NFC device screen for
`customer to verify the amount and add a tip if he wishes
`
`124
`
`126
`
`128
`
`
`
`
`
`
` Smart bill enabled application sends the transaction information
`
`to the backend smart bill gateway for processing
`
`
`
` 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.
`
`
`Customer can choose a payment method that he has enrolled
`in his wallet application to initiate the payment
`
`130
`
`132
`
`Smart bill gateway verifies the electronic bill and rejects if the
`
`payment amount is less than the billed amount.
`
`134
`
`136
`
`
`
`forwarded back to the merchant
`
`Once the transaction is approved or denied, the payment
`authorization response will return to the payment gateway to be
`
`138
`
`FIG. 1 B
`
`
`
`
` y er orp. age 0
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 5 of 39
`
`PGR2022-00003
`Apple EX1001 Page 5
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 3 0f 22
`
`US 10,600,046 B2
`
`
`
`Sakai£302
`
`
`
`
`.mom.mmuamxmm
`.Wm.NwN
`
`momfiwn§8wm...,..,,..mmsmmfimcw
`
`
`
`fiwvmgfi......,
`
`
`
`Emfiwma33%,“
`
`
`
`......................m5§ma0
`
`
`
`finuwmw»mum,,.
`
`£5”:memammfiwmmEmmwfimamm
`
`
`
`
`oomwmmawmm
`
`
`
`
`
`
`
`
`
`
`andfig,,hamzvEwwgmoum,
`
`Ewfiwmwmmfificmxfimfi
`fimmmgimemwwm
`
`Now
`
`<NGE
`
`
`Emfiwmwcmé.N.and
`
`magmohamagmafiwmfiwbwm
`
`$3erw.m
`
`Qwfiwmfim3m
`
`0E
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 6 of 39
`
`PGR2022-00003
`Apple EX1001 Page 6
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 4 0f 22
`
`US 10,600,046 B2
`
`0mm
`
`““8mewa
`
`
`
`$03303tflm
`
`ovmoz
`
`wa:EwE
`
`
`
`6:550cosmomcsEEoom533mm
`
`CNN
`
`
`
`
`
`
`
`
`
`
`
`
`NmN
`
`30:05:65@2me
`
`wNN
`
`$339:9552
`
`
`
`Em:m5EDEEEEm:.OE$00:B00
`
` NVN@NN
`
`HB5935commozaamm5>262
`
`£5,50:8:an05”6mBEmm5
`
`cosmozagm9:2.2SanSwamia0mmUmmmumcm@594mm9.:£_>>
`8:2:vam5
`
`wmccmgo350mmm5533
`550wm59commonaam9:335ng:53>:ccomncmSE83%993mm
`
`22w“.m:3:Eamm832anm£5,
`099%th95:mmm55:3
`finance
`
`850%m:wzafiwm @250£59:
`
`mm:mw9::
`
`obmwzmcomWLw.
`
`mm0mmt
`
`$305EBEBOmmw
`
`MN.QE
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 7 of 39
`
`PGR2022-00003
`Apple EX1001 Page 7
`
`

`

`U.S. Patent
`
`teehS
`
`US 10,600,046 132
`
`0mm
`
`
`
`vywwmnowmmwhhmfiw.
`
`
`
`.mmflVmoflagflfi.w
`
`g
`
`
`
`
`
`
`
`0m2m0u2m$3$00.60Mm........................
`“M4m
`.mmm“ru
`ewrw0..x3.30.0@362W
`
`
`
`EfiwrflkmwwwflzmEvawwm
`
`
`
`.fn0HM............................
`2a_~,2hmmzmmwmuuzmQmmmwmmgu0wawmwmzfl
`5“Jr
`
`.Hv
`
`UNGE
`
`
`
`1-...............................\
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 8 of 39
`
`PGR2022-00003
`Apple EX1001 Page 8
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 6 0f 22
`
`US 10,600,046 B2
`
`
`
`
`
`
`
`
`
`
`
`
`mmw
`
`
`
`
`
`
`u%«.~mi2hwfivmé
`
`.058m.5«$th%
`
`
`
`$anm.~0mmmmm§uw»wm.m
`
`QNGE
`
`
`
`
`
`
`
`
`
`mmsmmmflwqumdawn»wfifimmm“wwfluxwuw.
`
`53..
`£34“
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 9 of 39
`
`PGR2022-00003
`Apple EX1001 Page 9
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 7 0f 22
`
`US 10,600,046 B2
`
`
`
`omm
`
`
`
`
`Now
`
`EN203330
`
`
`
`x004tSw
`
`wow
`
`cosmPEw>
`
`ommmwmmEm
`
`
`
`83%m8mmmmmmEswagmccwm
`
`
`
`96commozaqm552thm33:02
`
`
`
`@0320m58Son};ucwEEoom3:3
`
`
`
`cum2$03.09confioaocm$me583%9F
`
`
`
`commoiam8%:029:£8.55mm9:
`
`
`
`mum5:8:anm5953%Emummooamm
`
`
`
`
`
`ENEmEmmUmEocxomcmxomnwucmmmm
`
`MN
`
`0E
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 10 of 39
`
`PGR2022-00003
`Apple EX1001 Page 10
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 8 0f 22
`
`US 10,600,046 B2
`
`owN
`
`E46
`
`Nam
`
`$.30
`
`:50me
`
`
`
`9:95:003039.0ch
`
`cmEEomgmtoamcmfi
`
`Lo$555.3
`
`
`
`28mfiBEmImcnflxm
`
`:5?82,
`
`£0352
`
`
`
`:WNonco
`
`omm
`
`Emimmvcm
`
` EmEcEScm88.05.
`
`wagon.
`
`8300
`NwmK.
`
`
`5:265”.995
`
`89:25mwmzomEoomwwm
`
`BESEm
`
`mom
`
`.ooeoiEmu
`
`38E5
`
`“5090.5
`
`mwm99$me
`
`“:29wmooo<
`
`sum63%
`
`53>a0:0
`
`@330
`
`vwm
`
`memcmE
`
`$5an
`
`65:2
`
`mam58mmmmmzuflcoo
`
`wogwEEOOuw
`
`
`
`GOLGEEDDIE
`
`MN.
`0E
`
`
`
`EmEbmm
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 11 of 39
`
`PGR2022-00003
`Apple EX1001 Page 11
`
`

`

`U.S. Patent
`
`m
`
`09
`
`US 10,600,046 132
`
`%
`
`mom
`
`83852
`
`6:28th
`
`
`
`
`
`“Mamczflxmcoszzmcoflwn.359$262
`
`Sm.GE
`
`
`
`a:m%EmmcmE350
`
`0...........................
`
`
`
`2,vomEzmwu2%83.0233mom2%
`
`2EnmmmnwwmzomEoo
`
`orm
`
`552cm
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 12 of 39
`
`PGR2022-00003
`Apple EX1001 Page 12
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 10 0f 22
`
`US 10,600,046 B2
`
`omm
`
`mcfixm
`
`§<w
`
`SEEEM
`
`llllllllllllllllllllllllllll
`
`Sm
`
`
`
`kmmmcmEEmo
`
`mom
`
`9:»{0362
`
`vmm302$
`
`Eszmm
`
`momE<m
`
`“05.2
`
`NNm
`
`MmGE
`
`
`
`3.25262
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 13 of 39
`
`PGR2022-00003
`Apple EX1001 Page 13
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 11 of 22
`
`US 10,600,046 B2
`
`0mm
`
`omm
`
`
`
`NmmcOEmwzmcomEQEmEE
`
`EmomgE80,9mm“mto20¢
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`"accuseatmommm55.38EEmEonbraommcozmoiqmmmm
`
`
`
`
`
`
`
`mmm
`
`com
`
`
`
`83%m5563%35mecmcam§<mmmSa-w26:cm:8303
`
`
`
`
`§<m@923Ema9:5363EBvcm£3confimaomeaé993mm4,
`
`83%9:cm5.an3.25cmvcm
`
`
`
`
`
`
`
`5:58@503mswfifimmowEmEov350mmgermofiqmaw:
`
`
`
`
`
`mom30.mm“mayvcm_2<wmcmflxmm5mw>565:5:mBm>mx85.03%:$9300a83%05E#2anmezaé
`
`
`cmucmE<mcomumtoawcmbmcmflxmcm$053
`
`553:5mg95E<mmczmwxm9.:$938
`
` a
`
`
`
`
`
`vowQ.mm“$595E<wmczflxw:mm;€525me“E996ch
`
`
`
`0m..GE
`
`momumszcoflma:u6BaummBmwSaxmm5Em2
`
`02m
`
`3539:E63%323$cmncmE<wmesmmxm9:cmoznmn
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 14 of 39
`
`PGR2022-00003
`Apple EX1001 Page 14
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 12 0f 22
`
`US 10,600,046 B2
`
`3».OE
`
`cow
`
`kmdFW
`
`v9“
`
`Em>mccmycw5%“06::m«S“3:59mBEE.
`
`5mmcmEmmigm£wmmoom22E
`
`Nov
`
` é
`
`wow63%359$95269mmucwm65:2
`
`
`
`wow“0:26.059$539wmmmanoo859m
`
`
`
`o3
`
`3:0mem£
`
`w8:29
`
`mg
`
`nmcco>t3chmarowcoamm2$0309
`
`
`
`53%.:useawas:ocmEsooommsocoammtoomRig
`
`
`
`ivxcmn9:So:mwcoamm:mmimomm
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 15 of 39
`
`PGR2022-00003
`Apple EX1001 Page 15
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 13 0f 22
`
`US 10,600,046 B2
`
`m;
`
`omv
`
`
`
`
`
`m3mammmmEx559.mEcmuumsEm088699:Emzcom
`
`
`
`
`
` »mmSa-mm5.3E9:ncmmUcmmvcmEEooDon?Embxmcam2.66.22
`
`
`
`
`
`
`
`
`casemmcm:m.388:UcmEREEm9:9mbcmEEoomccmmUcmEozcmfizmDan?9:mmccg$59M
`
`
`mo.
`
`
`
`
`
`BenzcmmEmEEkEEr:EEE0526x0:m$6550€953we.2$262 vmw66F:50Fmmmmme2:me.Ewmooosmm0:20ch»mmv53mmx525:mE38%?
`
`
`
`
`
`
`
`
`
`
`
`NV.OE
`
`
`
` szacommomcmfiBE.8SEEM:m_09.88»Dan?9:5am.
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 16 of 39
`
`PGR2022-00003
`Apple EX1001 Page 16
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 14 0f 22
`
`US 10,600,046 B2
`
`mg
`
`03V
`
`win
`
`
`
`
`
`UV.
`OE
`
`msocmci
`
`xcmm
`
`
`
`{9,3meEmE>ma
`
`965%cam
`
`wmv
`
`LofiSEm
`
`8:30
`
`65:).
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 17 of 39
`
`PGR2022-00003
`Apple EX1001 Page 17
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 15 0f 22
`
`US 10,600,046 B2
`
`
`
`3268mm3868mm
`
`momgm
`
`gm2<mn5
`
`tm2<m52023.?
`
`
`
`920305moEow
`
`3mEwimm
`
`N552mm32095
`
`6.260
`
`\
`
`own{93va
`
`mco_umoE:EEoox
`
`/Em
`6::ch
`
`nmSomw
`
`Eat
`
`vmmUcmnmwmm
`
`
`
`EoEmE850mm
`
`mNm
`
`mfimtom
`
`0%.\moSmQ
`
`
`
`$32928:3324,113....mmmgommcg833m
`
`
`
`
`
`RmESE83.02305
`
`
`
`mmmEmmcmE.950am
`
`
`
`3260qu
`
`mom
`
`
`“06:263%%commgaad.gracing
`39095
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 18 of 39
`
`PGR2022-00003
`Apple EX1001 Page 18
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 16 0f 22
`
`US 10,600,046 B2
`
`
`
`
`
`
`I@2583;bofiammbofiogmm
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` OVm“29—2“9054‘5069:0—
`
`
`
`‘
`
`5m32%cofigaq<
`
`gmE<mQO
`
`
`
`9w§>oi02me
`
`3m99.0w
`
`55%39085
`
`NE
`
`
`
`vcmnmwmm83mm
`
`mfimtomEm\
`
`{oz/EZX
`
`EmEo‘QuznsmwmmEEanU
`
`25vommom
`
`wmmomm\;/025mm
`
`\Nmmhmmmcms.
`
`mmm65:256233mmm5%sz835m858m
`
`.........................l.|.l.l.|.l.l.l.|.l.|.l.l.l.l2l.l.l.l.l.l.|.l.l.|.|.l.|.|arm*mccmr—O\x‘
`
`
`
`
`
`
`
`
`A5----.\.-:mmmzoficoo
`
`
`
`RmEma/x:ozmuzagqwmm53:322805AI111111111qummm
`
`
`
`
`
`mm6E
`
`
`
`EmEmE850mm
`
`«mm
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 19 of 39
`
`PGR2022-00003
`Apple EX1001 Page 19
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 17 0f 22
`
`US 10,600,046 B2
`
`83.3mncwm
`
`
`
`
`
`
`
`
`Nmm“mwadmh
`
`
`
`
`
`«mm2232083:0Emma95m:
`
`
`
`mcgmoiafimmgzmwm9>oi
`
`
`
`
`
`omm3209mm=EmEUcmumoEBoD
`
`
`
`Emaamv20382335228
`
`
`
`
`
`wmm
`
`cmcmm:t553:5was
`
`
`
`
`
`com£292cosmozqam325500
`
`Um
`
`0E
`
`
`
`
`
`
`
`$295cmcmoEBonor:mwzmcomgmm
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 20 of 39
`
`PGR2022-00003
`Apple EX1001 Page 20
`
`

`

`U.S. Patent
`
`ee
`
`nf
`
`US 10,600,046 132
`
`000EmHncmnowmm
`
`
`
`<0.OE@0833
`
`mmo
`
`cozommcg_mEzE9I/l"
`
`cmxofim
`
`Umfimcm
`
`mmmmmmsummg2%won.EEmaLm
`
`
`
`r.owm{03wamwcozmoEsEEoO
` :0szonm.2520:28LomCezommcmbM,.952mm:mwmwwma
`
`
`
`m08\...........................................................
`
`
`65:8
`
`0OC
`
`O
`
`cofimmcmfiwOQ
`
`mE.52%
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 21 of 39
`
`PGR2022-00003
`Apple EX1001 Page 21
`
`

`

`U.S. Patent
`
`0m2
`
`US 10,600,046 132
`
`2///2X/f1rg00,«mm
`Loumoma.,e«3:05:00mone\.
`128.83mg5905.2won.
`
`
`
`
`
`ovm
`
`0930mm
`
`mEEccmco
`
`Emm<mOQMcozomwcmfimOn.EmEoO0:35U
`uanmmoum552mm£03me
`
`\
`
`mmmEEgEoO
`
`
`
`
`
`
`
`@250mmfimtoa..
`
`Mm.GE
`
`
`
`EmEmm850%
`
`mmm
`
`mg52mmg4/
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 22 of 39
`
`PGR2022-00003
`Apple EX1001 Page 22
`
`

`

`U.S. Patent
`
`m,
`
`S
`
`f
`
`US 10,600,046 132
`
`r.0cMDzm239$26>
`
`
`
`0339EELSLomwmmundo“m55thmm»
`
`m.“dado“0E:oc0:39
`
`
`
`tm95:0-mEmocflmnm.cmsocm.89:m
`
`n0:mg
`
`mg
`
`0mm
`
`|
`
`
`
`mmomemzohsamEotcmxowécmw>mem
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`08$onEo:EzoEmvmmmcea63va
`
`Nam
`
`
`
`
`
`530m5:963Smcozommcm:nmofi:
`
`
`
`383E5cowommcm:sommv
`
`Um.OE020
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 23 of 39
`
`PGR2022-00003
`Apple EX1001 Page 23
`
`

`

`U.S. Patent
`
`Mar. 24, 2020
`
`Sheet 21 0f 22
`
`US 10,600,046 B2
`
`wwo
`
`QmGE
`
`
`
`
`
`sz:mxovm2$9.09Emum5vcmm
`
`:mxofmEon9.83%Umfimcm
`
`
`
`
`
`
`
`65:639.6203@9308EECOO5%968m
`
`
`
`EmEmEmwUcmSamoan?:Onommcm:5»,832
`
`
`
`owe
`
`Nmo
`
` >maw5»c9385.?Lou,33wwOa9mmmwmmE55805%05Emacom
`
`
`
`§<wwOm.mamcomommcmh
`
`comommcmb9:8.9509mm:
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`-o9“$330.8283EEEcmccmm
`
`
`
`53:83m.we83%cmfimcm:0on
`
`mum
`
`:mxBéE8:98cmzocm
`
`
`
`wmom>mvUmfimco
`
`vnm
`
`
`
`
`
`-mm5Eatmwcoamm:828Em5“Ema/Eu
`
`
`
`33mmOn.8.838859$:38
`
`
`
`
`
`
`
`_>_<wWOm60¢032mmEEmEooEgan::anm.memomm
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 24 of 39
`
`PGR2022-00003
`Apple EX1001 Page 24
`
`

`

`U.S. Patent
`
`US 10,600,046 B2
`
`
`
`4,":ofiiwmmm”moEmm5x030JmoEOxomXM_llllllllllllllll~\2Ma\..
`
`.\
`
`U\
`
`.IIIIIIIIIIIIIIIII..\.ninWx.mE995“KmE.m580285m5532<w
`
`o:
`
`mEmEEooévcm0wM@35236x0:mE9w>wr‘........CNN$6305
`
`2cesmozgofwan@230mEmtoan9:25M9:25
`8x0:m96283bw>=mvcamammmcoSQ
`
`
`meEEooéSExes/n......wt:......“Em>=mn
`
`
`
`k.OE
`
`9mm
`
`5285
`
`Ecmwm
`
`EM
`
`
`
`ownEmEmE850%
`
`9:08.9mmeozé
`jOE
`
`8300
`
`
`
`
`
`
`
`
`
`
`
`
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 25 of 39
`
`PGR2022-00003
`Apple EX1001 Page 25
`
`

`

`US 10,600,046 BZ
`
`1
`METHOD AND APPARATUS FOR MOBILE
`PAYME‘ITS
`
`
`
`
`
`CROSS-R A F A RENC 4 TO R AI ATED
`
`
`APPLICATIONS
`
`This application is a continuation of US. patent applica—
`tion Ser. No. 13/853,937 filed on Mar. 29, 2013, now US.
`Pat. No. 9,047,601 issued on Jun. 2, 2015.
`
`
`
`BACKGROUND OF 1H4 INV4NTION
`
`1. Field of the Invention
`
`
`
`The present invention is genera ly related to the area 0
`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 o m
`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
`checking 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 member. The
`service member brings the card 0 a Point of Sales (POS)
`counter to initiate a transaction payment. The service mem-
`ber then brings back a receipt to he customer for signature
`to authorize the transaction. It
`is a lengthy process that
`typically takes a couple of minutes or much longer when the
`service member has to take care of multiple payment trans—
`actions at a time. In addition, in he case for the debit card
`transactions, the process may be even more troublesome
`when a PIN is needed to authorize the transaction at the
`POS.
`There is a need to simplify the oayment process. With the
`advancement in mobile devices, it is anticipated that many
`constuners will carry one with them. Thus there is an
`opportunity of using a mobile device to quickly settle the
`payment at a point of sale (POS .
`
`
`
`SUMMARY OF THE INVENTION
`
`10
`
`15
`
`,
`
`30
`
`35
`
`4o
`
`45
`
`This section is for the purpose of summarizing some
`aspects of the 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 of the
`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 c ata including the electronic invoice
`
`and other information regarding the mobile device or an
`
`owner thereof is read 0 “ wirelessly into the NFC mobile
`device. After the user verifies the amount being charged and
`authorizes the payment, the NFC mobile device communi-
`cates with a payment ga eway or network for payment that
`is configured to proceed with the payment in accordance
`with a chosen payment method.
`
`6O
`
`65
`
`
`
`2
`According to another aspect of the present invention, the
`mobile device is a contactless card or part of a point of sale
`(POS) machine used to generate the electronic invoice. One
`embodiment of the present invention provides tmanticipated
`benefits and advantages in an application in which a pay-
`ment 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 restau-
`rant, where a consumer is given a check first for 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 chosen payment
`method at the point of sale without further contacting the
`merchant.
`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
`network, where the payment network may be an existing
`payment infrastructure (e.g., money transfer or credit card/
`debit). A payment response is sent to the merchant once a
`payment is delivered to a designated account by the mer-
`chant.
`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
`communication (NFC) device and being part of a mobile
`payment ecosystem in which various parties work with each
`other in order for the mobile payment ecosystem successful.
`Via a server (e.g., implemented as a manager) configured to
`provide what is referred to herein as Trusted Service Man-
`agement (TSM), the secure element in the mobile device can
`be remotely personalized and various applications or mod-
`ulcs 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 (his/her mobile device)
`and the data exchange therebetween, Where the mobile
`device being used by the user is installed with a correspond-
`ing 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 N FC 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 personali7ed 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 of the second mobile
`device authorizes the payment
`to the electronic invoice
`transported wirclcssly from the first mobile device, wherein
`the second mobile device is a near—field communication
`device and is configured to execute an application that
`conmlunicates with the software module in the first mobile
`
`
`
`
` y er orp. age
`
`GOOG-1001
`Google LLC v. RFCyber Corp. / Page 26 of 39
`
`PGR2022-00003
`Apple EX1001 Page 26
`
`

`

`US 10,600,046 BZ
`
`3
`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 embodiment, the sec-
`ond 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 ofservers. The gateway
`comprises 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 includc data pcrtaining to an clcctronic
`invoice. The gateway 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 authorizes the
`payment to the electronic invoice transported wire-
`lessly from the first mobile device, wherein the second
`mobilc dcvicc is a ncar-ficld communication dcvicc and ,
`is configured to execute an application that communi—
`cates with the software module in the first mobile
`device to read the data ofl‘ 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 dctailcd dcscription of an cmbodimcnt thcrcof, taken in
`conjunction wit1 the attached drawings.
`
`10
`
`15
`
`30
`
`35
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`
`
`
`
`T16 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:
`T 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
`providcd to settle paymcnts via a financial institution;
`T G. 1B shows a flowchart or process of settling a
`payment according to one embodiment. where the process
`may be implemented in software or a combination of
`software and hardware;
`T G. 2A shows a mobile payment ecosystem in which
`related parties are shown in order for the mobile payment
`ecosystem successful;
`T G. 213 shows a flowchart or process of provisioning one
`or
`morc applications according to onc cmbodimcnt;
`T G. 2C shows a data flow illustrating various interactions
`among different parties when an application is being provi-
`sioned in one embodiment;
`T G. 2D shows a data flow among different entities when
`preparing the application data in provisioning an applica—
`tion;
`T G. 2E shows a flowchart or process for locking or
`disa aling an installed application;
`T G. 2F shows an cxcmplary architccturc diagram of a
`portable device enabled as an e—purse conducting e—com—
`merce and m-commerce, according to one embodiment of
`the present invention;
`
`
`
`4o
`
`45
`
`6O
`
`65
`
`4
`FIG. 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 pers01mel (a.k.a.,
`personalizing a mobile device or a secure element therein
`while provisioning an application);
`FIG. 3B shows a block diagram of related modules
`interacting with each other to achieve what is referred to
`herein as e—purse personalization by a user of the e—purse;
`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 intcracting with cach othcr to achicvc the proc