throbber

`
`UNI’I‘ED STATES PA’I‘ENT AND TRADEMARK OFFICE
` UNITED STATES DEPARTMENT Ul“ C(IMMI‘LRCE
`linilcd Slulcs Palcnl and Trademark Gmcc
`Addnss. CDMMISSIONER FDR PATENTS
`I‘ll Hm H51]
`-\Ic\.nmln.|. \I'Ilglum .51.“ .l Hill
`www mum [cm-I
`
`APPLICA I'IUN Nil
`FILING [IA l'l';
`['lRS'l' IRAAIUD iNV’l‘IN'l'UR
`AT'l URN]?! DOCKET NU.
`['ONFIRMATIUN NU.
`
`14!?23349
`0631911015
`Xiangmun Kie
`RHD—GSSCI
`534a
`
`Loglantents. LLC
`2170: Stevens. Creek Boulevard. #284
`CUPERTINO. CA 95015
`
`“M ”‘3‘ ”WORDS
`
`AR'I' liNl'i
`PAPER NUMBER
`
`3M?
`
`NUI'U’ICAI‘ION DATE
`DELIVERY MODE
`
`0331510019
`FJJECTRONII '
`
`Please find below andfor attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any. is scl in the attached communication.
`
`Nolicc of lhe Office communication was sent electronically on above-indicated "Nolificalion Date" 10 lhc
`
`following c—mail addressms]:
`
`uspulcnoa (i??- ah Cglnbul .net
`
`PTUl.—lllI.A IRcv. (HIM?!
`
`Google LLC v. RFCyber Corp. / Page 342 of 792
`
`6006-1002
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 342 of 792
`
`

`

`App/Ibaflf-lflitllafed Interment Summary
`
`Applicantts)
`Application No.
`
`14i728,349 Xie et al.
`
`Examiner
`ASH FORD S HAYLES
`
`MA Stains
`No
`
`All participants (applicant, applicants representative. PTO personnel}:
`
`(1} ASHFORD S. HAYLES.
`
`{2] Joe Zheng.
`
`{3} Liangsen Koh.
`
`(4}
`
`.
`
`Date of Interview: '12 February 2019.
`
`Type:
`
`C] Video Conference
`Telephonic
`C] Personal [copy given to: Cl applicant
`
`Ci applicant’s representative]
`
`Exhibit shown or demonstration conducted:
`If Yes. brief description:
`
`3 Yes
`
`No.
`
`
`
`
`
`
`
`2103 DOthers
`[3102
`8112
`IssuesDiscussed [1101
`(For each til the chucked l1rr\{l’\i:l|¥t\'t’. itit’tru: rlcne’rilru itL'Inw I111: issue and dcrtriicd tit‘wt'irrtrrrn tri' lht: iliscuhsnlrri
`
`Claimts} discussed: _1_.
`
`Identification of prior art discussed: fl.
`
`Substance of Interview
`{For each issue dixt‘usser]. provide a rlelatilcd ctr-script ion and indicate it'ugrcemcr'il was reached. Some topics mag.- im'ludc: idcrrlil iculion or t-irLritic-dtiorr ni' ..
`reference or '4 portion thttreol. chum inlemrelution. [imposed amendments. ttrgttrnunl.‘ nt' an} applied r'el'erences L'I‘. ...i
`
`Discussed proposed amendments, recommended that clarification of how the payment gateway server is introduced
`into the payment process or state the novel limitation of writing data to an nfc medium provided by the P08. Additional
`search will be reguired. no agreement has been reached. Formal response to follow.
`
`Applicant recordation instructions: The lorrnal written reply to the last Ottice acllon must include the substance oi the interview. [See MPEF’
`section r13.ddi.lla reply tothe last Otlice action has already been filed. applicant is given a non-extendeole period oltne longer at one month or
`thirty davs from this interview date. or the mailing date ol this interview summary form. whichever is later. to file a statement at the substance of the
`interview
`
`Examiner recordation instructions: Examiners must summarize the substance of any interview of record. A complete and proper recordation ol
`the substance of an interview should include the items listed in MPEF' F1304 tor complete and proper recordation including the identification of the
`general lrrrusl ol each argument orissue discussed. a general indication at any other penrnent matters discussed regarding patentabrlitv and the
`general results or outcome at Ihe interview. to include an rndrcation as to whether or not agreement was reached on the issues raised.
`
`i3 Attachment
`
`r‘ASHFORD S HAYLESI
`
`Primary Examiner. Art Unit 3687
`
`US. Patent and Trademark Office
`
`PTOL-413 tFlev. arr-rector
`
`interview Summary
`
`Paper No. 20190212
`
`
`y er orp.v.ooge age
`
`
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 343 of 792
`
`

`

`Manual ol' Patent Examining Procedure (MPEPL Section ?13.04, Substance of Interview Must be Made of Record
`A complete written statement as to the substance of any iace-to-iace. video conference. or telephone Interview with regard to an application must be made of record In the
`applicallon whether or not an agreemeitl with the exainrner was reached at Ihe interview.
`
`Summary of Record of Interview Requirements
`
`Title 3‘! Code of Federal Regulations (CFR) 1.133 Interviews
`Paragraph (of
`
`In every instance where reconsideration Is requested In view at an interview with an examiner. a complete written statement oi the reasons presented at the Interview as
`warranting favorable action must be filed by the applicant. An intervlew does not remove the necessity for reply to Office action as specified In §§ 1.111. 1.135. [35 L151).
`‘lBEt
`
`3? CFR §12 Busmess to be transacted in writing.
`All busrness with the Patent or Trademark Office should be transacted in writing. The personal allendance of applicants or their attorneys or agents at the Patent and
`Trademark Office is unnecessary. The action of the Patent and Trademark Office will be based explosively on the written record in the Office. No attention will be paid to any
`alleged oral promrse. stipulation. or understanding in relation to which there is disagreement or doubt.
`
`The action at the Patent and Trademark Oltice cannot be based exclusively on the written record in the Ot‘fice it that record is itself
`incomplete through the failure to record the substance of interviews.
`it is the responsibility of the applicant or the attorney or agent to make the substance of an interview of record in the application file. unless
`the examiner indicates he or she will do so. It is the examiners responsibility to see that such a record is made and to correct material inaccuracies
`which bear directly on the question of patsntability.
`
`Examiners must complete an Interview Summary Form for each interview held where a matter of substance has been discussed during the
`interview by checking the appropriate boxes and filling in the blanks. Discussions regarding only procedural matters. directed solely to restriction
`requirements for which interview recordation is otherwise provided for in Section 812.01 of the Manual of Patent Examining Procedure. 0r pointing out
`typographical errors or unreadable script in Office actions or the like. are excluded from the interview recordalion procedures below. Where the
`substance of an interview is completely recorded in an Examiners Amendment. no separate Interview Summary F-tecord is required.
`
`The interview Summary Forrn shall be given an appropriate Paper No. placed in the right hand portion oi the file. and listed on the
`"Contents" section of the life wrapper. in a personal interview. a duplicate of the Form is given to the applicant (or attorney or agent) at the conclusion or
`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 lrom the examiner is not likely before an allowance or if other Circumstances dictate. the
`Form should be mailed promptly alter the interview rather than with the next oliicial communication.
`
`The Form provides for recordalion of the following information:
`- Application Number [Series Code and Serial Numberl
`- Name of applicant
`- Name of examiner
`- Date of interview
`- Type of Interview (telephonic. video—conference, or personal}
`Name of panicipanttsl (applicant. attorney or agent. examiner. other PTO personnel. etc.)
`- An indication whether or not an exhibit was shown or a demonstration conducted
`- Ah Identification oi 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; Agreement as to allowability is tentative and does
`not restrict further action by the examiner to the contrary
`- The signature ol the examiner who conducted the interview (it Form is not an attachment to a signed Office action)
`
`It is desirable that the examiner orally remind the applicant of his or her obligation to record the substance of the interview oi 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 applicant or the examiner to Include. all of the applicable items required below concerning the substance of the
`interview.
`
`A complete and proper recordaiion of the substance of any interview should include at least the following applicable items:
`1} A brief description of the nature of any exhibit shown or any demonstration conducted.-
`2) an identification of the claims discussed.
`3) an identification of the specific prior art discussed.
`at
`an identification of the principal proposed amendments ol a substantive nature discussed. unless these 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 the examiner,
`(The identification oi arguments need not be lengthy or elaborate. A verbatim or highly detailed description of the arguments is not
`required. The identification of the arguments is sufficient if the general nature or thrust of the principal arguments made to the
`examiner can be understood in the context of the application file. Of course. the applicant may desire to emphasize and lofty
`describe those arguments which he or she feels were or might be persuasive to the examiner.)
`6) a general indication of any other pertinent matters discussed. and
`iii
`if appropriate. the general results or outcome of the interview unless already described in the Interview Summary Form completed
`by the examiner.
`Examiners are expected to carelully review the applicants record of the substance of an interview. if the record is not complete and accurate.
`the examiner will give the applicant an extendable one month time period to correct the record
`
`Examiner to Check tor Accuracy
`
`it the claims are allowable for other reasons ol record. the examiner should send a letter setting forth the examiners version oi the statement
`attributed to him or her. it the record is complete and accurate. the examiner should place the indication, Interview Record OK on the paper recording
`the substance of the interview along with the date and the examiners initials.
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 344 of 792
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Applicant(s)z
`Title:
`Serial No.:
`
`Filing Date:
`Confirmation:
`
`Examiner:
`Group Art Unit:
`Docket No.:
`
`Xiangzhen Xie et al
`Trusted Service Management Process
`14(728349
`
`06!02i2015
`5346
`
`HAYLES, ASHFORD 8
`368?
`RFD-08501
`
`
`
`
`
`Interview Agenda
`
`Time: 02:00PM EST (1 1 :00 AM PST}
`
`Date: Tuesday, February 12. 2019
`
`Participants:
`
`Examiner: Ashford
`
`Inventor: Liangseng Kon
`
`Connection.
`
`Representative: Joe Zheng (Reg. No.: 39,450. Cell: 408-891-9381)
`Dialin
`in: 415 36343338 and conference “31987987
`
`Agenda:
`
`1. Joe briefly describes what this invention is about with respect to Claim 1:
`
`2. Joe presents the distinctions between Claim 1 and the three cited references
`Sineai (US. 201310339253) in view of Mullen (U.S. 2012i029472) further in view of
`Shank (US. 201110066550)
`
`3. Examiner presents his view on the distinctions;
`
`4. Examiner suggests possible amendments to overcome the references:
`
`5. Conclusion (Interview Summary)
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 345 of 792
`
`

`

`AMENDMENTS TO THE CLAIMS
`
`Please amend Ctaim 1 as follows:
`
`1.
`
`(Currently amended) A method for mobile payment. the method comprising:
`*Sicaitv
`
`
`“resented
`
`
`causing a mobile device to capture data directly from a medium a h‘
`
`thereto, 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 and transfer the data to the medium;
`
`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 amount in the
`
`electronic invoice;
`
`generating a payment request ggtom aticalty 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 message directly 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.
`
`
`tits shown in Fits.
`"'the mob r-Cievtca 1 ”hita getti "no it 1’) eats $6.1;
`
`medium '* "it’s, where the date is getaseted and irehe: ered on“;
`'
`"=
`“H”- A
`.
`...
`.
`
`t \J
`L"
`‘3 :
`.I
`it“! £21.:
`
`rt.
`
`,t-
`.
` Eh.n:at went“:*3 earth; 1"!" ”aragra pi“.
`
`a Hit?
`
`crates the rait?! ant my’ncct rtate and set“: '
`dete t: the
`HG'that 2309'}!
`
`I-J
`
`
`
`
` y er orp. age
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 346 of 792
`
`

`

`:3. user 51331.3 a°13'1331:..113'1 cede 13111211313111.1310Ltd's the. data from
`
`
`1:13:31 12'13-: 1133:13111311311:213:33. the 13'-
`111.1313213ce1331.11e:3
`1, . A41.
`'... 31331313311311; 133:1:“uteri re".11:ed in S:~.':1c:-1'
`
`".33 1.1.1.313 13.313113;11:31:11.1 131113-11333111:e 31:311'111e'.=3'31.1e
`data directiy from a medium physrcaiiy presented thereto the data including an
`
`.
`
`.
`
`
`3:31'-..-'e..
`
`.
`
`etectronic'in voice and settiement information with a merchant associated with a POS
`
`device, wherein the POS device is used to prepare the etectronic invoice and
`transfer the data to the medium”
`
`
`
`{2-11 Pace Tr" that: 3433113315.": cs1.3.11.3 if‘uitee Etioeait'aiis 113 1:13:13"
`' 11’ 3151161111113 psi-C1131
`
`shown.:11
`13111133110113; term 111 Cit-11111.
`13.11
`151,711. 14.?11’113113313 3331;. 111311;}; 131.11.114.33 111:.
`
`11113111133 device 11331::'13 3113 .131.=3- "ey'nhr‘3‘ redo est based 1311 111:1 1:11:31 31330...11311111:
`121111 scat-113' items ca: 131.1: ated in 1131-3 113311513: :1.--'-1'cw.e {31311112111;: ct:'11.;"the P08 device is
`used to prepare the eiectronic invoice and transfer the data to the medium,
`the
`payment request includes the total amount and the settlement information [from the
`P08131133 modification of .3131 11.1.1111 Matti-”.311 Mani1-2-1: 3131:} the. deiit‘aehcies 111
`‘ai?":v...
`
`
`(3:11age 881133111133 cited 10111111111- oer".131at1'1g 31 pe111131—3111.erg-1.133131 11111333 1111;11.31'1'e
`demee '11 1-151113113-33 to thee-=est1'r31-1:. 11111111313.- nq't-1 the 111o-J'it1 '31-'31'o‘ of 8113:311 at 113
`1.1111113313135113 3113:1111:3131.111313013'13133111'131 '1—31‘1..1e;1n1e.1 :1'1 {13.3331
`
`(Previously amended) The method as recited in claim 1, wherein said causing a
`
`mobile device to capture data directly from a medium inctudes placing the medium
`
`near the mobile device.
`
`(Previously amended) The method as recited in claim 2, wherein the POS device
`
`inciudes a secure element that provides security and authentication to generate the
`
`electronic bill and transfer the data to the medium.
`
`(Previousty amended) The method as recited in claim 1. wherein said displaying the
`
`electronic invoice on a display of the mobile device com prises:
`
`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)
`
`
`
`
` y er orp. age
`
`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 as recited 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 as recited 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 amount from an account owned by the
`
`user and generates an electronic notification for sending to the P08 device.
`
`8.
`
`(PrevthSi'y amended) The method as recited in claim 7, wherein said displaying the
`
`electronic invoice on the display of the mobile device comprises:
`
`allowing the user to modify the total amount in 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 moduie in the mobile device is
`
`configured to generate the payment request including the data pertaining to the
`
`electronic invoice to the payment gateway for processing.
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 348 of 792
`
`

`

`9.
`
`(Previousiy amended) The method as recited in claim 8, wherein data exchange
`
`between the mobile device and the payment gateway is conducted In a secured
`
`channel established therebetween.
`
`10_(Previousiy amended) The method as recited 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
`
`user in the mobile device that then monetary transaction per the payment request
`
`has been successfully completed with the POS device com prising: sending a
`
`notification of successful payment to the merchant of the POS device
`
`12. (Previously amended) A method for mobile payment, the method com prising:
`
`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 response to the captured data, the payment request being sent to a
`
`payment gateway includes a total amount combining an additional amount added
`
`by a user of the mobite device and an amount expressed in the electronic invoice;
`
`and
`
`receiving a message in the POS device directly from the payment gateway that the
`
`electronic invoice has been settled but for the total amount more than the amount
`
`expressed in the electronic invoice, wherein the payment gateway is 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.
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`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 as recited in claim 14. wherein the data includes
`
`security information of the merchant associated with the P08 device. the security
`
`information includes an account and bank information, an identifier of the secure
`
`element in the contactless card or the POS device.
`
`16. (Previously amended) The method as recited 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 as recited in claim 1 2, wherein data exchange
`
`between the mobile device and the payment gateway is conducted in a secured
`
`channel established between the mobiie device and the payment gateway.
`
`18. (Previously amended) A system for mobile payment. the system comprising:
`
`a point of sale (P03) 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
`
`{I
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`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 P08
`
`device.
`
`20. (Previousty 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.
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 351 of 792
`
`

`

`
`
`Electronic Patent Application Fee Transmittal
`
`Application Number:
`
`i4?28349
`
`Filing Date:
`
`02-Jun-2015
`
`Title of Invention:
`
`Method and apparatus for mobile payments
`
`.-.L_
`
`First Named lnventon‘Applicant Name:
`
`Xiangzhen Xie
`
`Filer:
`
`Attorney Docket Number:
`
`Joe Zheng
`
`RFD-085C]
`
`Filed as Small Entity
`
`Filing Fees for Utility under 35 USC 11 Ha}
`
`
`
`
`Quantity
`
`Amount
`
`Sub-Total in
`USDlSl
`
`
`
`
`Description
`
`Basic Filing:
`
`
`
`Miscellaneous-Filing:
`
`Petition:
`
`
`Paten t—Appea ls-a nd-l rite rferenc e:
`
`Post-AIIowance-and-Post-Issuance:
`
`
`Extensionaof-Tirne:
`
`
`
`
`
`
`
`
`
` ooge v. y er orp. age 0
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 352 of 792
`
`

`

`
`
`Sub~Total in
`Description "50(5) Fee Code Quantity Amount
`
`
`
`
`
`
`
`
`
`Extension - 2 months wilh SD paid
`
`2252
`
`1
`
`300
`
`300
`
`Miscellaneous:
`
`Total in USD (5)
`
`300
`
`
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 353 of 792
`
`

`

`Electronic Acknowledgement Receipt
`
`
`
`EFS ID: 3345434
`
`Application Number:
`
`i4?28349
`
`Title of Invention:
`
`Method and apparel us for mobile payments
`
`
`
`
`
`Filer: Joe Zheng
`
`Filer Authorized By:
`
`
`
`Attorney Docket Number: RFID-085C1
`
`Receipt Date:
`
`Filing Date:
`
`i4-FEB-2019
`
`02-JUN-2015
`
`Application Type:
`
`Ulilily under 35 USC 11 Iia
`
`Payment information:
`
`3? CFR 1.19 (Document supply fees]
`
`y er orp.
`
`age
`
`
`
`The Director of the USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:
`3? CFR 1.1?{Parent application and reexamination processing feesi
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 354 of 792
`
`

`

`3? CFR 1.20 {Post Issuance feesl
`
`3? CFR 1.21 (Miscellaneous fees and charges)
`
`File Listing:
`
`Document
`Number
`
`Document Descri “on
`p
`
`File SizelBytesli
`Message Digest
`155335
`
`Multi
`Part inp
`
`
`
`
`
`Amendmenlr’fieq. Reconsideration-After
`Non-Final Reject
`
`ResponseTolstOARCEpdf
`
`-'.n:':.:| r my 17mm gu-
`'._'.n
`
`.iuiifiEDJEF’ - =
`
`Information:
`
`Fee Worksheet [5806}
`
`fee-infopdf
`
`llFIMHIMJljn-J'o.".‘T'>1-F.5.-1\|:|~r-'5D'It-I|
`‘iri l.~|
`
`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, and including 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 components for a filing date [see 37 CFR
`1.53lbl-ld) and MPEP 506}, a Filing Receipt (37 CFR 1.54} will be issued in due course and the date shown on this
`Acknowledgement Receipt will establish the filing date of the application.
`National Stage of an International Application under 35 U.S.C: 371
`If a timely submission to enter the national stage ofan international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCTIDOIEOI903 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 asa Receiving Office
`If a new international application is being filed and the international application includes the necessary components for
`an international filing date (see PCT Article 1 'l and MPEP1810}, a Notification of the lntemational Application Number
`and ofthe International Filing Date (Form PCTIROHOSl will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of
`the application.
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 355 of 792
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`Applicant(s):
`Title:
`Serial No.:
`
`Filing Date:
`Confirmation:
`
`Xiangzhen Xie et al
`Trusted Service Management Process
`14l728,349
`
`06l02l2015
`5346
`
`Examiner:
`Group Art Unit:
`Docket No.:
`
`Ashford Hayles
`368?
`RFD-08501
`
`
`February 13. 2019
`
`Mail Stop: No-Fee Amendment
`Commissioner for Patents
`PO Box 1450
`
`Alexandria, VA 22313-1450
`
`ReSponse to First 0A (RCE)
`
`Dear Sir:
`
`In response to Office Action dated 09l17l2019, the Applicant respectfully
`
`requests the Examiner to enter the following amendments:
`
`AMENDMENTS TO THE CLAIMS are reflected in the listing of claims which
`
`begins on page 2 of this Reaponse.
`
`REMARKSIARGUMENTS begin on page 9 of this Response.
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`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:
`
`1.
`
`(Currently amended) A method for mobile payment, the method comprising:
`
`causing a mobile device to capture data directly from assist ‘ii-
`receives the data directly from a POS device
`
`and aitovrs the rabbits} deviw to capture the data therefrom the data including an
`
`electronic invoice and settlement information with a merchant associated with a-ttg;
` P08 devicemwi'ssseieAllie-445 " "
`we,
`Inch“.
`;-;.._.
`...'_-'.,
`\ .
`L-
`..
`.
`..
`{ii-xt‘i-vxf-wtits:---:-:4:?"'at}.3:13-3:3-{edict-Ref}
`
`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 amount in 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 message directly to the P03 device that a monetary
`
`transaction per the payment request sent from the mobile device has been
`
`successfully completed in the payment getaway with the POS device when an
`
`amount equivalent to the total amount is deducted from an account associated with
`
`the user--; and
`
`I..I
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`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 method as recited in claim 1, wherein said causing a
`
`mobile device to capture data directly from a -'s'-':-"+es::ivzsntad oh sicaii
`
`
`
`,.reset'tted
`
`(Currently amended) The method as recited in claim 2, wherein the P08 device
`
`Mttcxsmwtwprovrdes security and authentication to generate the
`
`electronic bill and transfer the data to the “tag
`
`(Currently amended) The method as recited in claim 1, wherein said displaying the
`
`electronic invoice on a display of the mobile device corn prises:
`
`allowing the user to verify the amount in the electronic invoice and make a change
`
`to the amount when needed; ang
`
`paying the total amount with the chosen paying instrument, wherein the chosen
`
`paying instrument is selected from a group consisting of an electronic waltet
`
`already created in the mobile device‘ a traditional credit or debit card, and an
`
`electronic transfer
`
`.
`
`('Currentiy amended) The method as recited 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 directiy from the t .gagcarrying the electronic invoice and the
`
`settlement information.
`
`.
`
`(Currently amended) The method as recited in claim 5, wherein the data further
`
`includes security information about the merchant associated with the P08 device.
`
`the security information includes an account and bank information of the registered
`
`1)
`
`
`
`
` ooge v. y er orp. age
`
`
`
`
`
`GOOG-1002
`Google LLC v. RFCyber Corp. / Page 358 of 792
`
`

`

`
`merchant, an identifier of sewn
`Q[if-ni'fii't'iiTi-‘éi-ii‘i‘e tag or the
`
`P08 device.
`
`7.
`
`(Previousiy amended) The method as recited 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 amount from an account owned by the
`
`user and generates an electronic notification for sending to the POS device.
`
`8.
`
`(Cun‘entiy amended) The method as recited in claim 7’. wherein said displaying the
`
`electronic invoice on the display of the mobile dewce comprises:
`
`allowing the user to modify the tetai-amount in 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 request including the data pertaining to the
`
`electronic invoice to the payment gateway for processing.
`
`9.
`
`(Previously amended) The method as recited in claim 8, wherein data exchange
`
`between the mobile device and the payment gateway is conducted in a secured
`
`channel established therebetween.
`
`10.

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket