`
`Unrrep Srares PATENT AND TRADEMARK OFFICE
`UNITED STATES DEPARTMENT OF COMMERCE
`United Stales Patent and Trademark Office
`Addets: COMMISSIONER FOR PATENTS
`PO Box 1450
`Mesundria, Virzitia 22315-1480
`Wane LILO EW
`
`FIRST SAMED INVENTOR
`
`ATTORNEY DOCKETNO,
`
`CONFIRMATION NO.
`
`14/728.349
`
`FILING BATE
`
`6/02/2015
`
` APPLICATION NO
`
`Xiangzhen Xie
`
`RFID-085C1
`
`5346
`
`LogicPatents, LLC
`21701 Stevens Creek Boulevard, #284
`CUPERTINO, CA 95015
`
`HAYLES, ASHPORES
`
` ART UNIT
`
`PAPER NUMBER
`
`5687
`
`NOTIFICATION DATE
`
`DELIVER ¥ MODE
`
`
`
`02/15/2019
`
`ELECTRONIC
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any, is set in the attached communication.
`
`Notice of the Office communication was sent electronically on above-indicated "Notification Date" to the
`following e-mail address(es):
`
`uspatents @ sheglabal.net
`
`PTOL-WA (Rev, 04/07)
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 342 of 792
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 342 of 792
`
`

`

`Applicant-Initiated Interview Summary
`
`Applicant(s)
`Application No.
`Xie etal.
`14/728 349
`
`=aaninee
`Ant Unit
`AIA Sinus
`ASHFORD S HAYLES
`3687
`No
`
`All participants (applicant, applicants representative, PTO personnel):
`
`(1) ASHFORD S. HAYLES.
`
`(2) Joe Zheng.
`
`Date of Interview: 12 February 2019.
`
`(3) Liangsen Koh.
`
`(4),
`
`Type:
`
`(J Video Conference
`Telephonic
`C) Personal [copy given to:
`OC applicant
`
`(applicant's representative]
`
`Exhibit shown or demonstration conducted:
`lf Yes, brief description:
`
`(1 Yes
`
`No.
`
`
`
`
`
`Primary Examiner, Art Unit 3687 U.S. Palent and Trademark Office
`
`lCothers
`[112 Oio2 Mio3g
`Issues Discussed O1i01
`(Por each of the checked box(es) above, please desenbe below (he issue and detailed dexeription of (he discussian)
`
`Claim(s) discussed: 1.
`
`Identification of prior art discussed: n/a-
`
`Substanceof Interview
`(Foreach issue discussed, provide a detailed description and indicate if agreement was reached. Some topics mayinclude: identification orclarification of ii
`reference or a portion there claiminterpretation. proposed amendments, arguments of any applied referenwes ote...)
`
`Discussed proposed amendments, recommended thatclarification of how the payment gateway serveris introduced
`into the payment processorstate the novellimitation of wnting data to an nfc medium provided by the POS. Additional
`search will be required, no agreement has been reached. Formal response to follow..
`
`Applicant recordation instructions: The formal written reply to the last Office actlon must include the substanceof the interview. (See MPEP
`section 713,04), Il areply to the last OMice action has already beenfiled, applicant is given a non-extendable period of the longer of one month or
`thirly days from this interview dale, or the mailing dale of this interview summary form, whicheveris later, lo file a statement of the substance of the
`inlerview
`
`Examinerrecordation instructions: Examiners must summarize the substance of any interview of record. A complete and proper recordation of
`ihe substance of an inierview should include the ilems listed in MPEP 713.04 for complete and proper recordation including the identificalion of ihe
`general ihrust of each argument or issue discussed, a general indication of any other pertinent matters discussed regarding patentability and Ihe
`general results or oulcome of the interview, lo include an indication as to whether or not agreement was reached on the issuesraised,
`
`| Attachment
`
`/ASHFORD S HAYLES/
`
`PTOL-413 (Rev. 8/17/2010)
`
`Interview Summary
`
`Paper No. 20190212
`
`
`yber Corp./Page
`V.
`oogle
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 343 of 792
`
`

`

`Manual of Patent Examining Procedure (MPEP), Section 713.04, Substanceof Interview Must be Made of Record
`A complete writlen statement as lo the substance of any face-to-face, video conference, or lelephone interview with regard to an application must be made of record in the
`application whether or nolan agreement with the examiner was reached at the interview.
`
`Summaryof Record of Interview Requirements
`
`Title 37 Code of Federal Regulations (CFR) 1.133 Interviews
`Paragraph (b)
`
`In-every Instance where reconsideration is requested in view of an interview Wilh an examiner, a complete wrilten statement of the reasons presented at the Interview as
`warranting favorable action must be filed by the applicant. An intarviaw does not remove the necessity for reply to Office action as specified in §§ 1.111,.1.135, (95 U.S.C.
`132)
`
`37 GFR §1.2 Business to be transacted in writing.
`All business with {he Patent or Trademark Office should be lransacted in wriling. The personal allendance of applicants of (heir allorneys or agents al ihe Palent and
`Trademark Office is unnecessary. The action of the Patent and Trademark Office will be based exclusively on the wrilten record in the Office. No atlention will be paid to any
`alleged oral promise, stipulation, or understanding in relation to which there is disagreement or doubt,
`
`The aclion of the Patent and Trademark Otlice cannot be based exclusively on the writlen record in the Office it that record is itself
`incomplete through the failure to record the substance ofinterviews.
`\tis the responsibility of the applicant or the attorney or agent to make the substance of an interview of record in the applicationfile, unless
`ihe examiner indicates he or she will do so.II is the examiners responsibility to see that such a record is made and to correct material inaccuracies
`which beardirectly on the question of patentability.
`
`Examiners must complete an Interview Summary Form for each interview held where a matter of subsiance has been discussed during the
`interview by checking the appropriate boxes andfilling in the blanks. Discussions regarding only procedural matters, direcied solely to restriction
`requirements for which interview recordation is otherwise provided for in Section 812.07 of the Manual of Patent Examining Procedure, or pointing out
`typographical errors or unreadable script in Office actions or the like. are excluded from the interview recordation procedures below. Where lhe
`substance of an interview is completely recorded in an Examiners Amendment, no separale Interview Summary Record is required.
`
`The Interview Summary Farm shall be given an appropriate Paper No., placed in the right hand portion of the file. and listed on the
`"Contents" section of the file wrapper, In a personal interview, a duplicate of ihe Form is given to the applicant (or attorney or agent) al the conclusion of
`the interview. In the case of a telephone or video-conference interview, the copy is mailed to the applicants correspondence address either with or prior
`to the next official communication.
`If additional correspondence from the examineris nollikely before an allowanceorif other circumstancesdictate, |he
`Form should be mailed promptly alter the interview rather than with the nextofficial communication,
`
`The Form provides for recordation of the following information:
`- Application Number (Series Code and Serial Number)
`- Name of applicant
`- Name of examiner
`- Date of interview
`- Type of interview (telephonic, video-conference, or personal)
`Name of participant(s) (applicant, atlomey or agent. examiner, olher PTO personnel, etc.)
`- An indication whether or not an exhibit was shown or a demonstration conducted
`- An identification of the specific prior art discussed
`An indication whether an agreement was reached and if so, a description of the general nature of the agreement (may be by
`attachment of a copy of amendments or claims agreed as being allowable). Note: Agreementas to allowability is tentalive and does
`nol resirict further action by ihe examiner to the contrary
`- The signature of \he examiner who conducted the interview (if Form ts not an attachment to a signed Office action)
`
`lis desirable thai {he examinerorally remind the applicant of his or her obligation to record the substance olthe interview of each case. It
`should be noted, however, that the Interview Summary Form will not normally be considered a complete and proper recordation of the interview unless
`it includes, or is supplemented by the applican| or |he examinerto include, all of (he applicable items required below concerning the substance of the
`interview.
`
`A complete and proper recordation of the substance of any interview should include at least the following applicable items:
`1) A brief description of ihe nature of any exhibit shown or any demonsiration conducted.-
`2) an identification of the claims discussed,
`3) an identification of the specific prior art discussed,
`4)
`an identification of the principal proposed amendments of a substantive nalure discussed, unless Ihese are already described on
`the Interview Summary Form completed by the Examiner,
`5) a brief identification of the general thrust of the principal arguments presented to he examiner,
`(The identification of arguments need not be lengthy or elaborale. A verbatim or highly detailed description of the arguments is nol
`required, The identification of the arguments is sufficientif the general nature or thrust of the principal arguments made to the
`examiner can be understood in lhe context of the application file. Of course, the applicant may desire to emphasize and fully
`describe those arguments which he or she feels were or might be persuasive to ihe examiner.)
`6) 4 generalindication of any other periinent matters discussed, and
`7)
`ifappropriate, the general results or outcome of the interview unless already described in the Interview Summary Form completed
`by the examiner.
`Examiners are expected to carefully review the applicanis record of ihe substance of an interview, |! the record is not complete and accurate,
`ihe examinerwill give the applicant an extendable one month time period to correct (he record
`
`Examiner to Check for Accuracy
`
`\{ the claims are allowable for other reasons of record, the examiner should sendaletter setting forth the examiners version of the statement
`attributed to him or her, |fihe record is complele and accurate, ihe examiner should place the indication, Inlerview Record OK on the paper recarding
`ihe substance of the interview along with the date and the examinersinitials.
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 344 of 792
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARKOFFICE
`
`Applicant(s):
`Title:
`Serial No.:
`Filing Date:
`Confirmation:
`Examiner:
`Group Art Unit:
`DocketNo.:
`
`Xiangzhen Xie et al
`Trusted Service Management Process
`14/728, 349
`06/02/2015
`5346
`HAYLES, ASHFORD S
`3687
`RFID-085C1
`
`
`
`
`
`Interview Agenda
`
`Time: 02:00PM EST (17:00 AM PST)
`
`Date: Tuesday, February 12, 2019
`
`Participants:
`
`Examiner: Ashford
`
`Inventor: Liangseng Koh
`
`Connection:
`
`Representative: Joe Zheng (Reg. No.: 39,450, Cell: 408-891-9381)
`Dialing
`in:
`(415)363-6338, and conference ID:987987
`
`Agenda:
`1. Joe briefly describes whatthis invention is about with respect to Claim 1;
`2. Joe presents the distinctions between Claim 1 and the three cited references
`Sincal (U.S. 2013/0339253) in view of Mullen (U.S. 2012/029472) further in view of
`Shank (U.S, 2011/0066550)
`3. Examiner presents his view on the distinctions:
`4. Examiner suggests possible amendments to overcome the references;
`5. Conclusion (Interview Summary)
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 345 of 792
`
`

`

`AMENDMENTSTO THE CLAIMS
`
`Please amend Claim 1 as follows:
`
`1.
`
`(Currently amended) A method for mobile payment, the method comprising:
`
`causing a mobile device to capture data directly from a medium_ph :
`
`inereto, the data including an electronic invoice and settlement information with a
`merchant associated with a POS device, wherein the POS device is used to
`
`prepare the electronic invoice andtransfer the data to the medium;
`displaying the electronic invoice on a display of the mobile device to show an
`amountto be paid by a user of the mobile device, wherein the mobile device is
`configured to execute an installed application therein to capture the data from the
`medium,
`receiving an entry by the mobile device, the entry including an additional amount
`from the User’
`calculating a total amount by adding the additional amount to the amountin the
`electronic invoice.
`generating a payment request automatically in the mobile device in response to the
`electronic invoice after the user has chosen a paying instrument, wherein the
`payment requestincludes the total amount and the settlement information;
`displaying the electronic invoice on the display of the mobile device for the user to
`verify the payment request along with the chosen paying instrument:
`sending the payment request from the mobile device to a payment gateway, wherein
`the payment gateway sends a messagedirectly to the POS device that a monetary
`transaction per the payment request sent from the mobile device has been
`successfully completed in the payment gateway with the POS device when an
`amount equivalent to the total amount is deducted from an account associated with
`the user~ and
`
`recording a confirmation in the mobile device that the monetary transaction per the
`payment request has been successfully completed with respect to the electronic
`invoice,
`
`
`AS showmn In FIC
`ihe mobile device 1103s getiing the data diz
`m1eGIC108 where the daia is Generated and transferred ontothSY]
`
`
`
`
`Simcaiteacheseealy nPfaragraph
`nas the data to ine
`
`
`
`
` yber Corp.
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 346 of 792
`
`

`

`
`S a transaction code and downloads the data from
`
`
`peethetransactoncode. The subtle difference pesveet
`Sincai
`bove and Sincai is the 3°entity (ie. a repository server) requirad in
`the instar application is a ore-io-one scheme without 4
`hile
`
`ccording!iy |Sincai feache
`ay frem ‘causing a mobile device to capture
`eS VY
`
`data directly from a medium physically presented thereto, the data including an
`electronic invoice and settlement information with a merchant associated with a POS
`device, wherein the POS deviceis used to prepare the electronic invoice and
`transfer the data to the medium’
`
`
`On Page 7 the Examimer cites Mullen as Sincal fatis to explicitly state Iwo more
`limations recited in Clair4. AS
`
`shown in Fis. 14, Mullen expheitiy requirestthe
`
`mobile device to generate the payment request based on the total amount of the
`purchased items caiculsted in the mobile device. contradicting “the POS deviceis
`used to prepare the electronic invoice and transfer the data to the medium,... the
`payment request includes the total amount and the settlement information [from the
`Snes Phe modification of Sincai with Mullen could not cure the deficiencies in
`Fal?
`“ittymeee yt
`
`
`On Peoe &, Shark'scled fo show generating a payment request inthe mobile
`deyine in resporise to aeelectronic invoice Again the modification of Sincal ar
`Mullen with aewank could fot cure the deficiencies im Since.
`
`(Previously amended) The method as recited in claim 1, wherein said causing a
`
`mobile device to capture data directly from a medium includes placing the medium
`
`near the mobile device.
`
`(Previously amended) The method asrecited in claim 2, wherein the POS device
`
`includes a secure element that provides security and authentication to generate the
`
`electronic bill and transfer the data to the medium.
`
`(Previously amended) The method as recited in claim 1, wherein said displaying the
`
`electronic invoice on a display of the mobile device comprises:
`
`allowing the user to verify the amount in the electronic invoice and make a change
`
`to the amount when needed:
`
`paying the total amount with the chosen paying instrument, wherein the chosen
`
`paying instrument is selected from a group consisting of an electronic wallet
`
`I
`
`
` yber Corp.
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 347 of 792
`
`

`

`already created in the mobile device, a traditional credit or debit card, and an
`
`electronic transfer.
`
`5.
`
`(Previously amended) The method asrecited in claim 1 further comprising: causing
`
`the mobile device to execute an installed module upon detecting the POS device in
`
`a near field of the mobile device, wherein the installed module is executed to receive
`
`the data from the medium carrying the electronic invoice and the settlement
`
`information.
`
`6.
`
`(Previously amended) The method as recited in claim 5, wherein the data further
`
`includes security information about the merchant associated with the POS device,
`
`the security information includes an account and bank information of the registered
`
`merchant, an identifier of the secure element in the contactless card or the POS
`
`device.
`
`7.
`
`(Previously amended) The method asrecited in claim 6, wherein said sending the
`
`payment request from the mobile device to a payment gateway comprises:
`
`transporting the payment request over a secured channel to the payment gateway,
`
`wherein the payment gateway is configured to perform the monetary transaction
`
`per the payment request by deducting an amountfrom an account ownedby the
`
`user and generates an electronic notification for sending to the POS device.
`
`8.
`
`(Previously amended) The method asrecited in claim 7, wherein said displaying the
`
`electronic invoice on the display of the mobile device comprises:
`
`allowing the user to modify the total amountin the electronic invoice when needed;
`
`paying the total amount with an electronic paymentprovided by an installed
`
`module in the mobile device, wherein the installed module in the mobile device is
`
`configured to generate the payment requestincluding the data pertaining to the
`
`electronic invoice to the payment gateway for processing.
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 348 of 792
`
`

`

`9.
`
`(Previously amended) The methodas recited in claim 8, wherein data exchange
`
`between the mobile device and the payment gateway is conducted in a secured
`
`channel established therebetween.
`
`10. (Previously amended) The method asrecited in claim 9, wherein the mobile device
`
`includes a secure element providing security and confidentiality required to support
`
`secure data communication between the mobile device and the payment gateway.
`
`11.(Previously amended) The method as recited in claim 9, wherein said notifying the
`
`userin the mobile device that then monetary transaction per the payment request
`
`has been successfully completed with the POS device comprising: sending a
`
`notification of successful payment to the merchant of the POS device
`
`12. (Previously amended) A method for mobile payment, the method comprising:
`
`generating an electronic invoice in a point of sale (POS) device;
`
`transporting data to a medium, wherein the data includes the electronic invoice and
`
`settlement information with a merchant associated with the POS device; by
`
`causing the mobile device to capture the data from the medium, wherein the
`
`mobile device executes an installed application therein to generate a payment
`
`request in responseto the captured data, the payment request being sent to a
`
`payment gatewayincludes a total amount combining an additional amount added
`
`by a user of the mobile device and an amount expressed in the electronic invaice;
`
`and
`
`receiving a message in the POS device directly from the payment gatewaythat the
`
`electronic invoice has been settled but for the total amount more than the amount
`
`expressed in the electronic invoice, wherein the payment gatewayis configured to
`
`send the message directly to the POS device when an amount equivalent to the
`
`total amount is deducted from an account associated with the user of the mobile
`
`devices.
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 349 of 792
`
`

`

`13.(Previously amended) The method as recited in claim 12, wherein the medium is
`
`placed near the mobile device to allow the user to use the mobile device to capture
`
`the data,
`
`14. (Previously amended) The method as recited in claim 13, wherein the POS device
`
`includes a secure element providing security and authentication to generate the
`
`electronic invoice.
`
`15.(Previously amended) The method asrecited in claim 14, wherein the data includes
`
`security information of the merchant associated with the POS device, the security
`
`information includes an account and bankinformation, an identifier of the secure
`
`element in the contactless card or the POS device.
`
`16. (Previously amended) The method asrecited in claim 15, wherein the message
`
`received in the POS device shows how much has been received from the user of the
`
`mobile device.
`
`17.(Previously amended) The method asrecited in claim 12, wherein data exchange
`
`between the mobile device and the payment gatewayis conducted in a secured
`
`channel established between the mobile device and the payment gateway.
`
`18.(Previously 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 including the electronic invoice and settlement
`
`information is transferred to a medium, the mobile device is executing a module
`
`configured to capture the data and display an amount expressed in the electronic
`
`invoice; and wherein
`
`the POS device receives an electronic notification directly from a payment gateway
`
`that the electronic invoice has been settled for a total amount including an
`
`additional amount and the amount expressed in the electronic invoice, the
`
`additional amount is added by the used, after the user of the mobile devices
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 350 of 792
`
`

`

`verifies the electronic invoice displayed on the mobile device and authorizes a
`
`payment to the electronic invoice, the mobile device is configured to generate a
`
`payment request to be sent to the payment gateway to proceed with a payment
`
`according to the payment request.
`
`19.(Previously amended) The system as recited in claim 18, wherein the data from the
`
`POS device includes an account and bank information of the merchant of the POS
`
`device.
`
`20. (Previously amended) The system as recited in claim 19, wherein the payment
`
`gateway acts to deduct an amount equivalent to the total amount from an account
`
`associated with the user of the mobile devices and generates the electronic
`
`notification for the POS device,
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 351 of 792
`
`

`

`
`
`Electronic Patent Application Fee Transmittal
`
`Application Number:
`
`Filing Date:
`
`14728349
`
`02-Jun-2015
`
`Title of Invention:
`
`Method and apparatus far mobile payments
`
`
`—ji—
`
`First Named Inventor/Applicant Name:
`
`Xiangzhen Xie
`
`Filer:
`
`Joe Zheng
`
`Attorney Docket Number:
`
`Filed as Small Entity
`
`
`Filing Fees for Utility under 35 USC 111(a)
`
`
`Quantity
`
`Amount
`
`Sub-Total in
`UsDIS)
`
`
` RFID-085C1
`
`
`
`Description
`
`Basic Filing:
`
`Pages:
`
`
`Claims:
`
`Miscellaneous-Filing:
`
`Petition:
`
`
`Patent-Appeals-and-Interference:
`
`Post-Allowance-and-Post-Issuance:
`
`
`Extension-of-Time:
`
`
`
` oogle
`
`
`V. yber Corp./Page 0
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 352 of 792
`
`

`

`
`
`Sub-Total in
`Fee Code Quantity AmountDescription USD(S)
`
`
`
`
`
`
`
`
`
`Extension - 2 months with $0 paid
`
`2252
`
`1
`
`300
`
`300
`
`Miscellaneous:
`
`Total in USD (S$)
`
`300
`
`
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 353 of 792
`
`

`

`Utility under 35 USC 171 (a
`
`Electronic AcknowledgementReceipt
`
`
`
`EFS ID; 35145434
`
`Application Number:
`
`14728349
`
`Title of Invention:
`
`Method and apparatus for mobile payments
`
`
`
`Filer; Joe Zheng
`
`Filer Authorized By:
`
`
`
`Attorney Docket Number: RFID-085C)
`
`Receipt Date:
`
`Filing Date:
`
`14-FEB-2019
`
`02-JUN-2015
`
`Application Type:
`
`Paymentinformation:
`
`37 CFR 1.19 (Document supply fees) yber Corp.
`
`The Director of the USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:
`37 CFR 1.17 (Patent application and reexamination processing fees)
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 354 of 792
`
`

`

`37 CFR 1.20 (Post Issuance fees)
`
`37 CFR 1,21 (Mistellaneous fees and charges)
`
`File Listing:
`
`Pages
`Multi
`File Size(Bytes)/
`becumant Desatedon
`Document
`
`
`
`Number Message Digest|Part/.zip|P (ifappl.)
`155885
`
`Amendment/Req. Reconsideration-After
`Non-Final Reject
`
`ResponseTo1stOARCE,padf MDE DeRUAe 7A NaTGSORTTA|
`ps0
`
`Information:
`
`
`
`
`
`Fee Worksheet (SBO6)
`
`fee-info,pdf
`
`ABODAY 2 S427GORSoestotil4s DAtell
`S6lal
`
`Warnings:
`Information:
`
`Total Files Size (in bytes)
`
`186154
`
`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents,
`characterized by the applicant, andincluding page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`New Applications Under 35 U.S.C. 111
`If a new application is being filed and the application includes the necessary componentsfora filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
`AcknowledgementReceiptwill establish thefiling date of the application.
`National Stage of an International Application under 35 U.S.C. 371
`Ifa timely submission to enter the national stage of an international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCT/DO/EO/903 indicating acceptance of the application as a
`national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
`New International Application Filed with the USPTO as a Receiving Office
`Ifa new international application is being filed and the international application includes the necessary componentsfor
`an international filing date (see PCT Article 11 and MPEP 1810), a Notification of the International Application Number
`and ofthe International Filing Date (Form PCT/RO/105) will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this AcknowledgementReceipt will establish the international filing date of
`the application.
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 355 of 792
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARKOFFICE
`
`Applicant(s):
`Title:
`Serial No.:
`Filing Date:
`Confirmation:
`Examiner:
`Group Art Unit:
`Docket No.:
`
`Xiangzhen Xie et al
`Trusted Service Management Process
`14/728,349
`06/02/2015
`5346
`Ashford Hayles
`3687
`RFID-085C1
`
`
`February 13, 2019
`
`Mail Stop: No-Fee Amendment
`Commissioner for Patents
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`Responseto First OA (RCE)
`
`Dear Sir:
`
`In response to Office Action dated 09/17/2019, the Applicant respectfully
`
`requests the Examinerto enter the following amendments:
`
`AMENDMENTSTO THE CLAIMS are reflectedin thelisting of claims which
`begins on page 2 of this Response.
`
`REMARKS/ARGUMENTSbegin on page9 of this Response.
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 356 of 792
`
`

`

`AMENDMENTS TO THE CLAIMS
`
`Please amend Claims 1-6, 8, 12-15 and 18 as follows:
`
`?.
`
`(Currently amended) A method for mobile payment, the method ees
`eea mobile device to Papers data orenty. from assis
`
`and allows the mobile deviceto canlure the data therefrom, the data including an
`POS device—-VBssais sae inaniesTha.daia toting. ore
`
`electronic invoice and settlement information with a merchant associated with 2-the
`
`displaying the electronic invoice on a display of the mobile device to show an
`
`amount to be paid by a user of the mobile device, wherein the mobile device is
`
`configured to execute an installed application therein to capture the data from the
`
`medium;
`
`receiving an entry by the mobile device, the entry including an additional amount
`
`from the user:
`
`calculating a total amount by adding the additional amount to the amountin the
`
`electronic invoice;
`
`generating a payment request in the mobile device in response to the electronic
`
`invoice after the user has chosen a paying instrument, wherein the payment
`
`request includes the total amount and the settlement information;
`
`displaying the electronic invoice on the display of the mobile device for the user to
`
`verify the payment request along with the chosen paying instrument;
`
`sending the payment request from the mobile device to a payment gateway, wherein
`
`the payment gateway sends a messagedirectly to the POS device that a monetary
`
`transaction per the payment request sent from the mobile device has been
`
`successfully completed in the payment gateway with the POS device when an
`
`amount equivalent to the total amount is deducted from an account associated with
`
`the user-; and
`
`
` yber Corp.
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 357 of 792
`
`

`

`recording a confirmation in the mobile device that the monetary transaction per the
`
`payment request has been successfully completed with respect to the electronic
`
`invoice.
`
`(Currently amended) The methodasrecited in claim 1, wherein said causing a
`
`mobile device to capture data directly from a #edkes-tag physically
`
`presented
`
`
`
`
`(Currently amended) The method asrecited in claim 2, wherein the POS device
`
`MAGGSSSSSIGHea-provides security and authentication to generate the
`
`electronic bill and transfer the data to the mecsustiag,
`
`(Currently amended) The method asrecited in claim 1, wherein said displaying the
`
`electronic invoice on a display of the mobile device comprises:
`
`allowing the userto verify the amountin the electronic invoice and make a change
`
`to the amount when needed; and
`
`paying the total amount with the chosen paying instrument, wherein the chosen
`
`paying instrument 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
`
`(Currently amended) The method asrecited in claim 1 further comprising: causing
`
`the mobile device to execute an installed module upon detecting the POS device in
`
`a near field of the mobile device, wherein the installed module is executed to receive
`
`the data directly from the messasstagcarrying the electronic invoice and the
`
`settlement information.
`
`(Currently amended) The method asrecited in claim 5, wherein the data further
`
`includes security information about the merchant associated with the POS device,
`
`the security information includes an account and bank information of the registered
`
`_
`
`.
`
`.
`
`.
`
`-
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 358 of 792
`
`

`

`
`ee-oarc-the tag or the
`merchant, an identifier of t:o.securs-clementthe.oaits
`
`POS device.
`
`7.
`
`(Previously amended) The methodasrecited in claim 6, wherein said sending the
`
`payment requestfrom the mobile device to a payment gateway comprises:
`
`transporting the payment request over a secured channel to the payment 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 electronic notification for sending to the POS device.
`
`8.
`
`(Currently amended) The method asrecited in claim 7, wherein said displaying the
`
`electronic invoice on the display of the mobile device comprises:
`
`allowing the user to modify the teta:-amountin the electronic invoice when needed;
`
`paying the total amount 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 the payment requestincluding the data pertaining to the
`
`electronic invoice ta the payment gateway for processing.
`
`9.
`
`(Previously amended) The method asrecited in claim 8, wherein data exchange
`
`between the mobile device and the payment gateway is conducted in a secured
`
`channel established therebetween,
`
`10. (Previously amended) The method asrecited in claim 9, wherein the mobile device
`
`includes a secure element providing security and confidentiality required to support
`
`secure data communication between the mobile device and the payment gateway.
`
`11.(Previously amended) The method as recited in claim 9, wherein said notifying the
`
`userin the mobile device that then monetary transaction per the payment request
`
`has been successfully completed with the POS device comprising: sending a
`
`notification of successful payment to the merchant of the POS device.
`
`
` oogle
`V. yber Corp./Page
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 359 of 792
`
`

`

`12. (Currently amended) A method for mobile payment, the method comprising
`
`
`
`generating a set of data in 2 point of sale (POS) device,
`
`
`
`the data including an
`
`
`
`electronic invoice arid séttiement information with a merchant associaied with the
`
`
`
`
`S-DSRSWSLS
`
`UEOS IAG
`
`ROGERSBy
`
`or