EAST Search History
`
`
`
`$224 and (electronic or digital) adj
`4{(bill$4 or invoic$4)
`
`\s224 and(e-bill)
`
`
`ii(contactless or NFC or wireless or
`\
`[proximity adj (paymentor transaction)
`
`
`18228 and (electronic or digital) adj
`|(statement)
`
`aaaaene! daneees
`
`
`
`(clcontactless or NFC or wireless 0or
`
` |s230and“(electronic0orrdigital)“adj
`|(bill$4 or invoic$4 or statement)
`
`
`
`
`
`[proximity adj (POS)
`
`
`
`$232 and (electronic or digital) adj
`4(bill$4 or invoic$4 or statement)
`
`
`
`
`
`
`——$233 and (contactless or NFC or
`
`
`uwireless or proximity) adj (payment or
`transaction)
`
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 525 of 792
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 525 of 792
`
`

`

`EAST Search History
`
`
`
`
`ui
` POS) near ((digital or electronic or e)
`jad) (wallet or purse))
`
`
`annnl at
`
`
`(merchant) near ((digital or electronic
`
`‘lor e) adj (wallet or purse))
`
`
`
`naneeeeeeeenenenenceseasennnnnnnsnsessnant
`bensenececeeetesennnnensene
`
`
`i(
`Hor proxmity or chip) near (payment or
`
`|purchase or transaction) and
`[rvoies)
`
`
` i(nfc or emv or smartcard or contactless US-PGPU
`
`uor proxmity or chip) near (payment or
`| USPAT;
`
`|purchase or transaction) same
`HUSOCR;
`
`
`u((electronic or eor digital) adj (bill$4 or}HFPRS:
`jlinvoic$4))
`EPO; JPO
`
`\
`DERWEN
`
`
`veered bieneee
`neebee eeeeeeeeeey
`1 BM_TDB
`
`2003023080").
`
`
`
`20040127256").PN
`
`j
`p
`(
`
`
`((contactless or nfc ar proximity) adj
`(adapter)
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 526 of 792
`
`

`

`EAST Search History
`
`
`
`4("2004/0127256").URPN.
`
`(10/625823).APP.
`
`POS near (purse or wallet)
`
`ey eeeeeeencceeeeee anaes
`
`
`
`
`IPOS same8(contactless 0orTproximity or
`
`|PPID) adj (payment or transaction)
`
`
`
`
`
`
`
`Sisanduoaanovenah
`
`$248 and ((merchant or vendor) adj
`|(purse or wallet))
`
`virtual adj POS
`
`Sene
`
`,1$252 and (contactless or proximity or
`|RFID) adj (paymentor transaction)
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
` 1S248 and ((merchant or vendor) near
`(purse or wallet))
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 527 of 792
`
`

`

`EAST Search History
`
`fs254 7
`[$252 and (emv) adj (paymentor
`||US-PGPUB; [OR
`{2017/09/ 25:
`‘itransaction)
`|USPAT;
`2:37
`yo
`|
`HUSOCR;
`|
`FPRS;
`EPO; JPO
`HDERWEN
`
`
`
`
`contactless or proximity or RFID) adj
`invoic$4 or bill$4) atat —
`
`
`
`
`u(NFC) adj (invoic$4 or bill$4)
`ul
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 528 of 792
`
`

`

`EAST Search History
`
` |((payment or transaction) adj
`Iprocess$4)
`
`see! hee Se
`
`:\333
`i
`
`merchant-to-person)
`
`
`wallet) and NFC ::
`
`
`
`
`
`
`
`i(person-to-merchant) and (contactless ||US-PGPUB; /OR HOFF=2017/09/25!
`Hor proximity or RFID) adj (payment or
`#USPAT;
`|
`121:19
`i
`i
`
`
`transaction)
`USOCR;
`\333
`i
`iFPRS;
`i
`
`
`
`4(person-to-merchant) and (nfc) adj
`(payment or transaction)
`
`
`
`
`u(person-to-merchant) and (nfc)
`
`
`
`SSuEEERRSeheteSEESLEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEAEEEEREEEELEEEEEEES Mennocursssnsspannanan!focounepnennnsenesssssnssndfensssssssnnnnnnennedAasesseesspeenssssesnsnnnant
`
`
`
`
`
`
`
`
`
`(payment or transaction) same (wallet
`jor purse)
`
`
`\333
`i
`
`
`
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 529 of 792
`
`

`

`EAST Search History
`
`([so72“and (electronicoorTrdigitaloorre)adj|lu
`(invoic$4 or bill$4)
`|
`
`1$272 and (wireless or paperless or nfc )
`
`Ir (invoic$4 or bill$4)
`
`‘
`
`|smart or chip or RFID or IC) adj card)
`
`i(contactless or proximity or RFID or
`infec) adj (paymentor transaction) and
`ii(wireless or paperless or nfc ) adj
`'(invoic$4 or bill$4)
`
`i(ccontactless0orTproximityoorrRFIDoor
`info) adj (payment or transaction) near
`urequest
`
`4(person-to-merchant) and ((smart or
`iichip or RFID or IC) adj card)
`
`person-to-person) and ((contactless or |
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 530 of 792
`
`

`

`EAST Search History
`
`
`
`
`s280‘and:‘(transmit$4oorsrsends)“adj
`(payment or transaction) near request
`
`
`
`(person-to-person) same ((contactless
`‘lor smart or chip or RFID or IC) adj
`
`|card)
`|;;uuuu
`
`
`
`soat“and“(electronic near (purse or
`
`jiwallet))
`\;
`
`u i
`
`
`$281 and mobile adj (transaction or
`payment)
`
`
`
`
`
`
`Ihcinnee_ta_annaimarandmahilead
`business-to-consumer and mobile adj
`(transaction or payment)
`
`i
`
`
`
`
`
`
`
`\icard-to-card and (nfc or contactless or 4US-PGPUB; }OR
`i
`i
`RFID or proximity or wireless) adj
`USPAT;
`i
`|(transaction or payment)
`USOCR;
`
`
`
`ycard-to-card and (nfc or contactless or
`|RFID or proximity or wireless) near
`ii(transaction or payment)
`ti
`at
`
`i u
`
`li3i
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 531 of 792
`
`

`

`d
`
`$293 and (mobile adj (payment or
`\itransaction))
`u3utat
`
`t 'i
`
`iuu
`l
`at
`
`#S293 and (nfc adj (paymentor
`utransaction))
`i
`
`client adj side) adj (transaction or
`Hpoayment)
`
`utransaction))
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`$289 and mobile adj (transaction or
`payment)
`ti
`at
`
`u3i
`
`EAST Search History
`
`H(client-side) adj (transaction or
`payment)
`
`uu3i uM
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 532 of 792
`
`

`

`EAST Search History
`
`
`|jtransaction))
`
`basannneed beeen
`annnel neeeee
`
`4358
`(closed-loop adj (payment or
`
`iitransaction))
`
`
`
`
` 49296 and (nfc adj (payment or
`
`
`
`
`
`‘itransaction))
` aaaaa! ances
`
`
`$299 and (nfc adj (payment or
`
`|transaction))
`
`
`S300 and (mobile adj (payment or
`
`aaa! heey at
`
`"20100114773"
`
`(mobile or virtual) adj (wallet or purse)
`near (payment or transaction)
`
` 1535
`
`;
`
`‘
`
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 533 of 792
`
`

`

`EAST Search History
`
`
`
`
`
`418306 and (secure adj element)
`
`
`
`aenenevenentnetienneteetnnnnetnaenl aneneee
`20140187153"
`
`weehis we
`
` (smartcard) and (electronic or digital)
`Hadj (bill or invoice)
`
`
`
`
`anneneseneeeneEEREEEEEEEEEeenbcunetaaneenenes
`
`smartcard) with (electronic or digital)
`dj (bill or invoice)
`
`4a
`
` (electronic or digital) adj (bill or invoice) |
`|adj (paymentor transaction)
`\
`
`
`
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 534 of 792
`
`

`

`EAST Search History
`48315 11267
`‘(electronic or digital or virtual) adj (bill
`|US-PGPUB;|OR
`i
`2017/10/05:
`
`;
`\
`i
`“or invoice) adj (paymentor
`WUSPAT;
`0:40
`;
`|transaction)
`4USOCR;
`\
`|FPRS;
`EPO; JPO
`
`49315 and nfc
`
`
`
`
` (
`
`electronic or virtual or digital) adj (bill
`|
`{jor invoice) adj (transaction or
`
`payment)
`|a
`
`
`
`
`electronic or-virtual 0or digital) adj
` (
`i(check) and (nfc or wireless or
`
`|contactless or proximity) adj
`(transaction or payment)
`
`
`
`
`
`DRasssssescreseee
`
`
`(electronic or virtual or digital) adj
`{i (check) and ((nfc or wireless or
`‘icontactless or proximity) adj
`
`{i(transaction or payment))
`
`Jor proximity) adj (payment or
`transaction)
`
`$322 and POS
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 535 of 792
`
`

`

`EAST Search History
`
`Sate
`"20140143104"
`
`20100274677"
`
`("20090170559") or
`1("20120191612")).PN.
`
`OFF
`
`2017/10/09:
`
`1:48
`
`
`
`4"5748737".pn.
`
`u(electronic or digital or virtual) adj
`(wallet or purse)
`
`16331 and POS
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 536 of 792
`
`

`

`EAST Search History
`
`‘(electronic0orrdigitaloorrvirtual) adi“(bill |HU
`vor invoic$4) adj (payment) and (nfc or
`|
`‘Icontactless or proximity) adj (payment
`‘lor transaction)
`
`Hinvoic$4 or check)
`
`1201 30138517"
`
`(electronic or digital) near (bill$4 or
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 537 of 792
`
`

`

`and need eee
`
` 015/03/26:
`
`
`
`
`
` .
`
`EAST Search History
`
`$160 and (electronic or digital) near
`|ffinvoiceorcheck) |4
`
`A
`
`hanewrenee
`
`
`
`S170 and (electronic or digital) near
`¥(invoice or check)
`\
`3
`i
`3
`;
` $171 and (smart or |G or RFID ar EMV)
`3
`;
`
`
`Hi4 |3 j
`3
`j
`3
`}
`adj card
`
`:
`
`
`
`16:59
`
` :
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 538 of 792
`
`

`

`EAST Search History
`
`$171 and (trusted near service near
`_imanag$5)
`
`(trusted near service near
`
`
`
`
`
`
`12015/03/26
`416:
`;
`
`i
`:
`417:
`2015/03/26!
`417:00
`i
`
`2015/03/26:
`17:00
`;
`
`$177 and (electronic or digital) near
`_|{(invoice or check)
`
`i
`
`\
`\
`
`4/ 6/ 2018 7:46:22 PM
`C:\ Users\ ahayles\ Documents\ EAST\ Workspaces\ 14728349CONTACTLESSpos.wsp
`
`EASTSearchHistory.14728349_AccessibleVersion .htm[4/6/2018 7:46:24 PM]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 539 of 792
`
`

`

`
`
`Provided by the EPO:
` RSs
`
`
`Application US201 213468462
`
`INPADOC family has approximately 3 simple families with 21 family members
`Loaded: 1 simple family with 7 family members
`
`Filter "Hide applicant citations": Off
`Filter "Hide applications without citations": Off
`
`
`
`
`FamSeqNr AppInNrDOCDB=AppinFilingDateAppinSeq Appincc AppinNrEPODOC
`
`CALGZ2R35508
`1
`1CA
`CA2835508
`2012-05-10
`1
`2 EP
`EP2ZE 720783038
`EP12783038
`2012-05-10
`
`
`
`EP12783038
`
`2012-05-10
`
`EP12783038
`
`2012-05-10
`
`EP2o 12072038
`
`EP12783038
`
`2012-05-10
`
`EP20120783038
`EP20120763038
`US201213468462
`
`2012-05-10
`EP12783038
`2012-05-10
`EP12783038
`US201213468462 2012-05-10
`US201213468462 2012-05-10
`* US201213468462 2012-05-10
`US201213468462 2012-05-10
`
`
`
`2458516
`S201 213468518
`
`US201213468462 2012-05-10
`US201213468462 2012-05-10
`2 US201213468462 2012-05-10
`US201213468518 2012-05-10
`US201213468518 2012-05-10
`US201213468518 2012-05-10
`US201213468518 2012-05-10
`US201213468518 2012-05-10
`
`
`
`1
`
`1
`
`1
`
`—_Sos
`—eoasoos
`—-Sseos
`
`1
`
`1
`1
`
`2EP
`
`2 EP
`
`2 EP
`
`2 EP
`2 EP
`3 US
`3 US
`3 US
`3 US
`
`3 US
`3 US
`3 US
`4US
`4 US
`4 US
`4US
`4 US
`
`4 US
`
`4US
`4 US
`4 US
`4US
`4 US
`5 US
`
`5 US
`5 US
`
` LIS2O1 213468625
`
`S20 12 ts4685 18
`
`S20 1213468518
`US2Zo te 134685 18
`USZ01S 13468518
`UBZote 18468518
`USZ01213468518
`US201 213408685
`
`LIS20 1213468625
`
`US201213468518 2012-05-10
`
`US201213468518 2012-05-10
`U$S201213468518 2012-05-10
`US201213468518 2012-05-10
`US201213468518 2012-05-10
`U$S201213468518 2012-05-10
`US201213468625 2012-05-10
`
`US201213468625 2012-05-10
`US201213468625 2012-05-10
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 540 of 792
`
`

`

`
`
`[Se1213468625
`Seo T et s468o25
`
`US201213468625 2012-05-10
`US201213468625 2012-05-10
`
`S20 te 13468625
`
`U$S201213468625 2012-05-10
`
`US201213468625 2012-05-10
`US201213468625 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`U$S201213468571 2012-05-10
`
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`U$201213468571 2012-05-10
`US201213468571 2012-05-10
`US201213468571 2012-05-10
`U$S2012037237
`2012-05-10
`US2012037237
`2012-05-10
`US2012037237
`2012-05-10
`US2012037237
`2012-05-10
`
`8201213488685
`UIS2012 159488625
`LIS2012 13488571
`US2012 13468571
`
`LSe0121g4ggort
`ASZOIAIS468574
`
`US20121346857
`
`orecrrces
`
`US20T 218468571
`US201213468571
`US2012134885771
`US201218458571
`S20 1213458571
`1520 1213468571
`[S20 1213468571
`USeo a 1s4g8a 74
`JOO LETI468574
`ASSOLE 13468574
`USedtei3469574
`US20 1S 13468574
`USZ012 1346857"
`Sco eig46es?
`99
`WO2012US3729
`
`i i5j
`
`Z>f.f
`
`i
`om
`WO20)2Uosf200
`WO2012US9723
`WO2012US3728
`
`WOegteuiss7e37
`WOseQ 1 euS37237
`
`US2012037237
`US2012037237
`
`2012-05-10
`2012-05-10
`
`
`
`
`
`5 US
`
`U5203 218488a6e5
`
`U$S201213468625 2012-05-10
`
`5 US pete134G8ees US201213468625 2012-05-10
`
`
`5 US
`USe01 213468625
`US201213468625 2012-05-10
`5 US
`JED LETI468E25
`US201213468625 2012-05-10
`5 US
`se 1134685 25
`US201213468625 2012-05-10
`5 US
`WS2O TS t3468625
`US201213468625 2012-05-10
`5 US
`Used te t3469625
`US201213468625 2012-05-10
`5 US
`US2012 13468625
`US201213468625 2012-05-10
`5 US
`USzo te 13468625
`U$S201213468625 2012-05-10
`5 US
`US20 1213468625
`US201213468625 2012-05-10
`5 US
`UbZot2 13468625
`US201213468625 2012-05-10
`5 US
`US20t21s46a6e5
`U$S201213468625 2012-05-10
`
`
`
`—_Sos—eSoeeoasasasa
`—eeeeeemememenememesemsmsmemommm
`
`5 US
`5 US
`
`5 US
`
`5 US
`5 US
`6 US
`6 US
`6 US
`6 US
`
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`6 US
`7 US
`7 US
`7 US
`7 US
`
`7 US
`7 US
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 541 of 792
`
`

`

`1
`1
`1
`
`1
`1
`1
`
`7US
`7 US
`7US
`
`7US
`7 US
`7US
`
`Wo2012US3ST237 US2012037237
`Wo2012US37237 US2012037237
`WO201 2US37237 US2012037237
`
`WOeGieussre23? US2012037237
`Wo2gteis37237 US2012037237
`WO2G12is37237 US2012037237
`
`2012-05-10
`2012-05-10
`2012-05-10
`
`2012-05-10
`2012-05-10
`2012-05-10
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 542 of 792
`
`

`

`CitnSeqNr
`
`CitnOrigin
`
`1 Nati
`
`2 Nati
`
`onal Search Report
`
`3 Nati
`
`onal Search Report
`
`4 Nati
`
`onal Search Report
`
`CitnType
`
`PublinNr
`
`PubInDate
`
`PAT
`
`PAT
`
`PAT
`
`PAT
`
`iIS20092226 2009-09-03
`
`WOe006078 2006-07-27
`
`(3920100784 2010-04-01
`
`DE 1 G20080¢ 2010-06-17
`
`3 Nati onal Search Report
`
`PAT
`5 Nati
`onal Search Report
`Ue201106622011-03-17
`
`PAT
`6 Nati
`WO2004012 2004-02-05
`onal Search Report
`PAT
`1 Nati
`US20041272 2004-07-01
`onal Search Report
`PAT
`2 Nati
`US2007 1972 2007-08-23
`onal Search Report
`PAT
`3 Nati
`US204 2037S 2012-02-09
`
`onal Search Report
`PAT
`4 Nati
`
`onal Search Report
`
`PAT
`5 Nati
`onal Search Report
`PAT
`6 Nati
`onal Search Report
`PAT
`7 Nati
`onal Search Report
`52009143t 2009-06-04
`PAT
`1 Nati
`onal Search Report
`
`Usoe13t€ 2012-07-26
`PAT
`2 Nati
`onal Search Report
`Uc00S17022009-07-02
`3 Nati
`PAT
`US5748737 1998-05-05
`onal Search Report
`PAT
`4 Nati
`USL01 02607 2010-10-14
`onal Search Report
`PAT
`5 Nati
`US20711406 2011-06-16
`onal Search Report
`
`iiS2008 1725 2008-07-17
`USeG1ebe23t 2012-01-26
`
`6 Nati
`
`onal Search Report
`
`PAT
`
`US20ino2ec 2010-01-28
`
`PAT
`7 Nati
`onal Search Report
`PAT
`8 Nati
`onal Search Report
`PAT
`9 Nati
`onal Search Report
`2010-12-16
`52010315€
`PAT
`10 Nati
`US20100824 2010-04-01
`onal Search Report
`PAT
`11 Nati
`US2008 1437 2009-06-04
`onal Search Report
`PAT
`1 Nati
`US20072738 2007-11-29
`onal Search Report
`
`USS293548 2013-03-12
`USE3938 11 2002-03-05
`
`2 Nati
`
`onal Search Report
`onal Search Report
`
`PAT
`PAT
`
`US 2G080 7/42 2008-03-27
`US2gusded: 2008-04-24
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 543 of 792
`
`

`

`4 National Search Report
`
`5 National Search Report
`6 National Search Report
`7 National Search Report
`8 National Search Report
`9 National Search Report
`10 National Search Report
`11 National Search Report
`12 National Search Report
`13 National Search Report
`14 National Search Report
`15 National Search Report
`
`16 National Search Report
`17 National Search Report
`
`18 National Search Report
`
`19 National Search Report
`20 National Search Report
`1 National Search Report
`2 National Search Report
`3 National Search Report
`4 National Search Report
`
`
`
`PAT
`
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`
`PAT
`PAT
`
`PAT
`
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`
`US20083004 2008-12-18
`
`LO 20G0 1 80€ 2009-06-25
`UO2G1 07236 2010-05-20
`USeG107 235 2010-05-20
`12520102077 2010-08-19
`L85S380458 2013-03-05
`LE585858508 2013-11-19
`58579293 2013-11-12
`US2006 1997 2006-05-25
`USS9C0344 1999-09-28
`US20052076 2005-09-22
`US20080724 2008-03-27
`
`1257432816 2008-10-07
`US2G08308e 2008-12-18
`
`(520102234 2010-09-02
`
`US201 22 18¢ 2012-08-30
`USS820838 2014-09-02
`US2004 1272 2004-07-01
`US 20092 10S 2009-08-20
`1192009743 7 2009-06-04
`L52010153< 2010-06-17
`
`PAT
`5 National Search Report
`USELO0939712009-12-10
`PAT
`US7S42337 2011-05-17
`6 National Search Report
`PAT
`US20087 91 E 2009-07-30
`7 National Search Report
`PAT
`US204 22540 2012-10-04
`8 National Search Report
`PAT
`US200ee 223 2009-09-03
`9 National Search Report
`PAT
`S201 230s 2010-10-14
`10 National Search Report
`PAT
`US201 12185 2011-09-08
`11 National Search Report
`PAT
`12 National Search Report
`US20091a26 2009-05-21
`PAT
`USSS188S5 2014-12-23
`13 National Search Report
`PAT
`USSS352323 2013-01-08
`14 National Search Report
`PAT
`1859393545 2013-03-12
`15 National Search Report
`PAT
`1$57597250 2009-10-06
`16 National Search Report
`PAT
`1520100824 2010-04-01
`17 National Search Report
`PAT
`USSS65723 2013-10-22
`18 National Search Report
`PAT
`USe8128278 2015-09-08
`19 National Search Report
`PAT
`UES 7278< 2007-12-06
`20 National Search Report
`PAT
`US20082 196 2009-08-20
`1 International Search Report
`PAT
`US2000197 2009-07-30
`2 International Search Report
`PAT
`3 International Search Report
`PAT
`4 International Search Report
`
`MS2070394€ 2010-12-02
`US20409234 2010-01-28
`
`5 International Search Report
`6 International Search Report
`
`PAT
`PAT
`
`1252009 1704 2009-07-02
`LSeG1 01 S37, 2010-06-17
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 544 of 792
`
`

`

`7 Applicant
`8 Applicant
`9 Applicant
`10 Applicant
`11 Applicant
`12 Applicant
`
`PAT
`PAT
`PAT
`PAT
`PAT
`PAT
`
`
`: 2009-09-03
`3 2006-07-27
`4 2010-04-01
`
`
`
`2010-06-17
`
`= 2011-03-17
`2 2004-02-05
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 545 of 792
`
`

`

`Applicant
`
`XPnumber
`
`BROADCOM CORP [US]
`
`VISA USA INC [US], et al
`
`APPLE INC [US]
`
`RACKWITZ KARSTEN [DE]
`
`WAY SYSTEMS INC [US], et al
`GOLDTHWAITE SCOTT, , et al
`
`HAMMAD AYMAN [US]
`HART ANNMARIE D [US]
`
`Deibert Doug, , et al
`EVANS GRAHAM [CA]
`
`SPODAK DOUGLAS [US], et al
`
`DAGGAR, ROBERT N
`Garrett Peter, , et al
`X CARD HOLDINGS LLC [US]
`
`SAMSUNG ELECTRONICS COLTD [KR]
`
`YEN PHILIP W [US], et al
`WEISSMAN STEVEN |
`
`APPLE ING
`
`BROTHER IND LTD [JP]
`
`ZIH CORP
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 546 of 792
`
`

`

`KONINKL PHILIPS ELECTRONICS NV [NL]
`
`DYNAMICS INC [US]
`SAMSUNG ELECTRONICS CO LTD
`
`BOEING CO [US]
`KOREA ELECTRONICS TELECOMM [KR]
`PULESTON DAVID [US], et al
`MUIRHEAD SCOTT A W [CA], et al
`LAMBETH DAVID N [US], et al
`
`NORAND CORP [US]
`RAYTHEON COMPANY
`
`ADVANCED MICROELECTRONIC AND A [IE]
`
`HEWLETT PACKARD DEVELOPMENT CO [US]
`ADVANCED MICROELECTRONIC ANDA[IE]
`
`BUNDESDRUCKEREI GMBH [DE]
`
`TUTTLE JOHN R [US], etal
`COTTER JUDY MARGARET[US], etal
`GOLDTHWAITE SCOTT, , et al
`FIRST DATA CORP [US]
`
`AMERICAN EXPRESS TRAVEL RELATE [US]
`
`DEVICEFIDELITY INC [US]
`GRIFFIN KENT, , et al
`WALKER DAVID RYAN [CA], etal
`BROADCOM CORP [US]
`Garrett Peter, , et al
`SPODAK DOUGLAS, , et al
`MOBILE CANDYDISH INC [US]
`SINGH RAVI
`[CA], et al
`BLAZE MOBILE INC [US], et al
`MULLEN JEFFREY D [US], et al
`DPD PATENT TRUST LTD[IE]
`APPLE INC
`
`COX CHRISTOPHERT [US], et al
`SPODAK DOUGLAS [US], et al
`RANS JEAN-PAUL EDMOND, , et al
`FIRST DATA CORP [US]
`GRIFFIN KENT, , et al
`SHUO JEFFREY,, etal
`FIRST DATA CORP [US]
`
`INTEL CORPORATION
`
`AMERICAN EXPRESS TRAVEL RELATE [US]
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 547 of 792
`
`

`

`BROADCOM CORP [US]
`VISA USA INC [US], et al
`APPLE INC [US]
`RACKWITZ KARSTEN [DE]
`
`WAY SYSTEMS INC [US], et al
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 548 of 792
`
`

`

`NPLbiblio
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 549 of 792
`
`

`

`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 550 of 792
`
`

`

`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 551 of 792
`
`

`

`CitnCategory
`
`XI
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 552 of 792
`
`

`

`xxtt<<a
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 553 of 792
`
`
`

`

`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 554 of 792
`
`

`

`Passage
`
`abstract
`paragraphs [0003] , [0018] - [0020] - [0055] - [0068]
`abstract
`paragraphs [0017] - [0020] - [0025] - [0056]
`abstract
`paragraphs [0178] - [0197]
`abstract
`
`paragraphs [0015] , [0022]
`abstract
`abstract
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 555 of 792
`
`

`

`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 556 of 792
`
`

`

`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 557 of 792
`
`

`

`Claims
`
`1-3,9
`1-9
`10-15
`
`1-15
`
`1-15
`
`1-15
`1-15
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 558 of 792
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Applicant(s):
`Title:
`Serial No.:
`Filing Date:
`Confirmation:
`Examiner:
`Group Art Unit:
`Docket No.:
`
`XiangzhenXie etal
`Trusted Service Management Process
`14/728, 349
`06/02/2015
`5346
`HAYLES, ASHFORD S$
`3687
`RFID-085C1
`
`Mail Stop: No-Fee Amendment
`Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`January 13, 2018
`
`Responseto First OA
`
`Dear Sir:
`
`In responseto Office Action dated 10/13/2017, the Applicant respectfully
`
`requests the Examiner to enter the following amendments before reconsidering the
`
`above-referenced application:
`
`AMENDMENTSTO THE SPECIFICATION begin on page 2 ofthis
`Response.
`
`AMENDMENTSTO THE CLAIMS arereflected in the listing of claims which
`begins on page 3 of this Response.
`
`REMARKS/ARGUMENTSbegin on page 9 of this Response.
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 559 of 792
`
`

`

`AMENDMENTSTO THE SPECIFICATION
`
`1. Please amend Paragraph [0007] as follows:
`
`[0007]
`
`Accordingto 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
`
`paymentinfrastructure (e.g., money transfer or credit card/debit). A payment
`
`response is sent to the merchant once a paymentis delivered to a &s
`
`desicnated account by the merchant.
`
`2. Please amend Paragraph [0009] as follows:
`
`[0009]
`
`Accordingto still another aspect of the present invention, the mobile
`
`device used by the consumeris a near field communication (NFC) device and being
`
`part of a mobile payment ecosystem in which various parties 8ss-work with each
`
`otherin order for the mobile payment ecosystem successful. Via a server(e.g.,
`
`implemented as a manager) configured to provide whatis referred to herein as
`
`Trusted Service Management (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 merchantis referred to as Smart
`
`Bill Payment. The module is configured to facilitate the communication between the
`
`merchant(its device) and the user (his/ner mobile device) and the data exchange
`
`therebetween, where the mobile device being used by the useris installed with a
`
`corresponding application related to Smart Bill Payment.
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 560 of 792
`
`

`

`AMENDMENTSTO THE CLAIMS
`
`Please amend Claims 1, 3-8, 10-12, 14-16, and 18-20 as follows:
`
`1.
`
`(Currently amended) A method for mobile payment, the method comprising:
`
` causing a mobile device to receive cata wirelessly as
`point of sale (POS) device, ihe data inchiding an alectranic invoice and
`
`settiorient information with a merchant associated with thea POS device:
`
`displaying the electronic invoice or a disclayof the mobile device to show an
`
`aount to be paid by & user of ihe mriokuie device, wherein the mobile deviceis
` FAY&
`a
`“as
`
`x-configured to execute an installed
`
`application therein to communicate with the POS device;
`
`receiving ar eniry by the mobile device. the entry incluelina
`
`from the user
`
`an additional arnount
`
`
`
`a total a
`electronic invoice:
`
`te-generatinigs a payment request in responseto the electronic invoice fier the
`
`user has chosen 6 paying instrument, wherein ine payment request includes
`
`the ioial ernourt and the settlement information:
`
`
` Yaasse-for
`displaying the electronic invoice on a-thedisplay s
`
`@ihe_userto verify the payment request alana with the chosen paving
`
`instrument:
`
`
`
`sending the payment request ssfram: the mobile device io a payment
`
`iaiewey, wherein the payment
`
`
`qateway sends @ message to the POS device that
`
`@ monetary transaction oer the payment request has bean successfull
`
`
`
`
`
`leted with the POS device when an amount equivalent to the total amour is
`
`
`
`
`
`deducted from an account associated with the user: and
`
` tTecetving @ confirmation in the mobile device that athe monetary
`
`transaction per the payment request has been successfully completed with the
`
`POS device.
`
`kad
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 561 of 792
`
`

`

`(Original) The method as recited in claim 1, wherein the POS device includes a
`
`contactless card loaded with the electronic invoice, and said causing a mobile
`
`device to receive an electronic invoice from a point of sale (POS) device
`
`comprises reading the contactless card to obtain the electronic invoice by the
`
`mobile device.
`
`(Currently amended) The method as recited in claim 2, wherein the POS device
`
`includes a secure element that provides security and confidentiality required to
`
`support secure data communication between the POS device and jhe mebile
`
`
`(Currently amended) The method as recited in claim 1, wherein said displaying
`the electronic invoice on a display s of the mobile device comprises:
` s-ailowing the user to verify astheamountin the electronic invoice and
`make a changeto the amount when needed;
`
`paying the tote!amount with s-ihechosenpaying instrument, wherein the
`
`chosen payinginstrument is selected from a group consisting of an electronic
`
`wallet already created in the mobile device, a traditional credit or debit card,
`
`and an electronic transfer.
`
`
`mee
`
`Sy
`Boe bh
`SESS
`
`
`
`ss-causing the mobile device to execute an
`
`sin a nearfield
`installed module upon detecting the POS device a
`
`of the mobile device, wherein the installed module exasuted ;
`
`
`
`aio receive the data s
`
`
`
`
`(Currently amended) The method asrecited in claim 5, wherein the data further
`
`includes security information ss
`
`about the merchant associated
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 562 of 792
`
`

`

`with the POS device, the security information includes an account and bank
`
`information of the registered merchanisesr, an identifier of the secure elementin
`
`the contactless card or the POS device.
`
`7.
`
`
`(Currently amended) The method asrecited in claim 6, wherein said asassss:
`
`sencing the payment request framthe mobile device ic a payment gateway
`
`comprises:
`
`transporting the payment request over a secured channel to a-ihepayment
`
`gateway, wherein the payment gateway is configured to perform the
`
`monetary transaction per the payment request by deducting an amount from
`
`an account owned by the user and generates an eieciranis notification iss
`sant for sending tots st-the POS device.
`
`
`
`8.
`
`(Currently amended) The method asrecited in claim 7, wherein said displaying
`
`the electronic invoice on s-the display scsess-of the mobile device comprises:
`
`
`eauengallowing the user to ve asmodiy the total amountin the electronic
`
`
`
`INVOICE As
`st-when needed;
`
`paying the ictalamount with an electronic payment provided by an installed
`
`module in the mobile device, wherein the installed module in the mobile
`
`device is configured to generate 2-ihepayment request including the data
`
`pertaining to the electronic invoice to ethepayment gateway for processing.
`
`9.
`
`(Original The methodasrecited in claim 8, wherein data exchange betweenthe
`
`mobile device and the payment gateway is conducted in a secured channel
`
`established in accordance with the security information in the data pertaining to
`
`the electronic invoice.
`
`10. (Currently amended) The method asrecited in claim 9, wherein the mobile
`
`device includes a secure element Sat-providingss security and confidentiality
`
`required to support secure data communication between the mobile device and
`
`the payment gateway.
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 563 of 792
`
`

`

`11.(Currently amended) The method as recited in claim 9, wherein said notifying the
`
`user in the mobile device that ater monetary transaction per the payment
`
`request has been successfully completed with the POS device comprising:
`
`
`
`sending a notification of successful payment to the merchants ssf
`
`
`
`the POS device.
`
`12. (Currently amended) A method for mobile payment, the method comprising:
`
`generating an electronic invoice in a point of sale (POS) device;
`
`transporting the electronic invoice to a mobile device by causing the mobile
`
`device to read off data pertaining to the electronic invoice from the POS device,
`wherein the data further incluces settlement information with s merchant
`
`
`associsied with the POS device. tne mobile device :s
`
`
`
` SAS seeciic-executes an installed application
`
`
`
`therein to communicate with the POS device to generate a payment requestin
`
`responseto the electronic invoice, ihe sent io a cayment request being
`
`
`
`nevirient galewey includes ¢ tolal arnount combirune ar: additional armaunt
`
`acdced by a user of tha mobile device and an amount expressed in the
`
`
`
`
`
`alectronic invoice: and
`
`
`receiving a message inthe POS device :
`s-from aihepayment gateway
`
`that the electronic invoice has been settled burt for the lotel arniount riore than
`
`
`the amount expressed in ihe electronic inveice, wherein the payment galeway
`
`is configured io send the messaqce directly
`
`
`
`to the POS device when an amount
`
`
`
`
`
`eauivalent ic ihe total amountis deducted fram an account associated with the
`
`
`
`
`
`e user of the mobile devices-.«
`
`
`13. (Original) The method as recited in claim 12, wherein the POS device includes a
`
`contactless card loaded with the electronic invoice, and the mobile device reads
`
`off a contactless card in a near field of the mobile device to obtain the data
`
`pertaining to the electronic invoice from the POS device.
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 564 of 792
`
`

`

`14. (Currently amended) The methodas recited in claim 13, wherein the POS device
`
`
`includes a secure element Ssa*-providingassecurity and confidentiality required
`
`to support secure data communication between the POS device and the mobiis
`
` devices
`
`15. (Currently amended) The methodasrecited in claim 14, wherein the data
`
`includes security information of &
`
`wie merchant associated with
`
`the POS device, the security information includes an account and bank
`
`, an identifier of the secure elementin the information-
`
`contactless card or the POS device.
`
`16. (Currently anended) The method asrecited in claim 15, wherein the message
`sshows how
`reserved in the POS device s
`$:
`
`much has been recerved from the user of the mobile devices
`
`
`
`17. (Original) Tne method as recited in claim 12, wherein data exchange between
`
`the mobile device and the payment gateway is conducted in a secured channel
`
`established in accordance with the security information in the data pertaining to
`
`the electronic invoice.
`
`18. (Currently amended) A system for mobile payment, the system comprising:
`
`a point of sale (POS) device provided to generate an electronic invoice upon
`
`receiving an entry, wherein data inclucing the electronic invoice is seni io 4
`
`mobile device when the POS device is oresented near the mobile device, the
`mobile device is execuling a module contoured to read ihe data and cispiey an
`amount exoressed in the electronic irveoice: and wheren
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 565 of 792
`
`

`

`
`the POS device receives an electronic notification from a payment gateway that
`
`the electronic invoice has been settled for a ictal ariount including an additional
`
`
`
`ammount end the arnount expressed in the electronic invoice, the additional!
`
`
`
`amountisaddedby iheused, after sineuser of the mobile devicesverifies the
`
`electronic invoice displayed on the mobile device and authorizes a payment to
`
`the electronic invoice, the mobile device is configured to genarsie a payment
`
`
`
` requesiva
`
`19. (Currently amended) The system as recited in claim 18, wherein-#
`
`
`deyice includes an account and bank information of the ss
`
`of the POS device
`
`
`20. (Currently amended) The system asrecited in claim 19, wherein the payment
`
`Hleway acts io deduct an amount sauivaeient to the total ariount fram an
`
`account associated with the user of ihe mobile devices and generates the
`
` electroruc notification for the POS devices
`
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 566 of 792
`
`

`

`REMARKS
`
`Claims 1 - 20 were submitted for examination. In the Office Action dated
`
`10/13/2017, Claim(s) 1and12 are rejected under pre-AlA 35 U.S.C. 102(e) as being
`
`anticipated by Mullen et al. (US 2012/029472, hereinafter "Mullen"), Claims 2, 4, 5,
`
`7-9, 11-13, 16-18 are rejected underpre-AlA 35 U.S.C. 103(a) as being
`
`unpatentable over Mullen in view of Dryeret al. (US 2012/0290376, he