Source: http://www.google.com/patents/US8073424?dq=6106459
Timestamp: 2014-10-25 10:21:52
Document Index: 603645696

Matched Legal Cases: ['art 4', 'art 4', 'art 1', 'art 1', 'art 2', 'art 3']

Patent US8073424 - System and method of managing contactless payment transactions using a ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA method handling payment transactions in a system using mobile communication devices as stored value devices is disclosed. A transaction operations server receives multiple records of the transaction from the stored value device�one via a communication channel through the telecommunication provider...http://www.google.com/patents/US8073424?utm_source=gb-gplus-sharePatent US8073424 - System and method of managing contactless payment transactions using a mobile communication device as a stored value deviceAdvanced Patent SearchPublication numberUS8073424 B2Publication typeGrantApplication numberUS 11/753,450Publication dateDec 6, 2011Filing dateMay 24, 2007Priority dateJan 5, 2007Also published asUS8014755, US8019320, US8045956, US8275353, US8467767, US20080166995, US20080166996, US20080166997, US20080166998, US20080167988, US20120022957Publication number11753450, 753450, US 8073424 B2, US 8073424B2, US-B2-8073424, US8073424 B2, US8073424B2InventorsAlbert Sun, Pao-Chieh An, Ying-Che Lo, Chee-Horng LeeOriginal AssigneeMacronix International Co., Ltd.Export CitationBiBTeX, EndNote, RefManPatent Citations (54), Non-Patent Citations (9), Referenced by (43), Classifications (39), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetSystem and method of managing contactless payment transactions using a mobile communication device as a stored value deviceUS 8073424 B2Abstract A method handling payment transactions in a system using mobile communication devices as stored value devices is disclosed. A transaction operations server receives multiple records of the transaction from the stored value device�one via a communication channel through the telecommunication provider network, and another via an independent communication channel. The records are reconciled at the transaction server for transaction verification.
1.0�The telecommunication provider network and mobile payment workstation 15 execute a message exchange with the mobile communication device 11 to establish a stored value in the mobile communication device, either by storing a first value, or increasing a stored value. 2.0�In an interchange between the terminal 13 at the merchant's site including a proximity coupling device and the mobile communication device 11, the amount of the stored value is deducted in the mobile communication device and transferred to the transaction terminal in a transaction with a merchant. 3.1�The mobile communication device 11 transmits a transaction record via the telecommunication provider network and mobile payment station 15 using a messaging protocol over the telecom provider network. 3.2�The transaction terminal transmits a transaction record corresponding to the transaction, typically within a batch of transaction records, to the operation server 14. 4.1�The mobile payment station and telecommunication provider network may process the transaction record in a billing system, and bill the customer associated with the mobile communication device 11 for the value established in step 1.0. 4.2�The operation server 14 processes the transaction records passed from the transaction terminal to the operation server in step 3.2. 5.0�The mobile payment workstation transfers the transaction record for the transaction accomplished in step 2.0, typically within a batch of transaction records, to the data server in the operation server and workstation 14. 6.0�The operation server 14 matches the records received in via the telecommunication provider network 16 and mobile payment workstation 15, with the records received from the transaction terminal 13. If the records match, and user authentication and authorization is otherwise properly performed, then the operation server 14 uses the account system to transfer the stored value from the payer's account to the payee's account, settling the transaction. 7.0�The operation server 14 upgrades application programs, maintains current security key exchange for secured data transmissions, credits and debits the stored value at the transaction terminal 13, and downloads promotion data for use by the transaction terminal. FIG. 8 illustrates support by the payment service provider network described herein for an on-line transaction, by which the user accesses an online system using the mobile communication device for obtaining value from a merchant like a service selling tickets to entertainment events. This scenario includes a mobile payment architecture in which the transaction terminal 13 of FIG. 1 is replaced by a �reader-lite� device 90 adapted for use with a personal computer on a desktop for example, including a proximity coupling device for contactless communication with a mobile communication device, and a wired or contactless link to the personal computer or other host processor. The �reader-lite� device 90 in embodiments of the technology also includes a reader for contact based credit or debit cards, such as a magnetic strip reader or the like. The �reader-lite� device 90 can be adapted for personal use by the holder of the mobile communication device, or for multiuser activities. The operation server 14 is adapted for supporting the �reader-lite� device 90 in the same ways as it supports the transaction terminal in the system of FIG. 1. In addition, the operation server 14 is adapted to communicate with a third party, such as a ticket system workstation 91. The ticket system workstation 91 in this example is a merchant for tickets to entertainment events, although it could operate as an interface for merchants for any type of goods or services. A merchant, such as an entertainment venue, places a contactless reader/terminal 92 like a transaction terminal 13 of FIG. 1 at the venue for redeeming the tickets.
1.0�The mobile communication device 11 links with the web site presented on behalf of the payment service provider to act as a portal for merchants such as the ticket system workstation 91. 2.0�The web portal redirects the user's link to the merchant system at the ticket system workstation 91, where the resources available through the ticket system workstation 91 allow the user to purchase a ticket to an entertainment event. 3.0�The ticket system workstation 91 returns stored value data representing the purchased ticket, along with transaction records to the operation server 14. 4.0�The operation server 14 transfers the stored value data representing the ticket via the �reader lite� device 90 to the mobile communication device 11, where it is stored for later use. 5.0�In an interactive exchange with the �reader lite� device 90, the stored value on the mobile communication device 11 is deducted according to the transaction to purchase the ticket. 6.0�The �reader lite� device 90 transfers the transaction record to the operation server 14, where the account system in the operation server transfers stored value from the user's account to the ticket system merchant's account. 7.0�The operation server 14 transfers a record of the transaction, typically within a batch of transaction records, to the terminal 92 at the merchant site. 8.0�The user takes the mobile communication device 11 to the transaction terminal 92 at the merchant site, and validates the ticket in the mobile communication device to gain entry into the event, or otherwise redeems the stored value purchased via the portal operated by the operation server 14. FIG. 9 illustrates support by the payment service provider network described herein for another on-line transaction, by which the user accesses an online system for obtaining value from the web-based, automated teller machine-type online network presented by a bank or other financial institution. In this embodiment, a server which is part of financial transaction network, such as a web based automatic teller machine work station 95 is coupled with the operation server 14. The �reader-lite� device 90 also includes resources for reading a magnetic strip on a financial card 96, such as a credit or debit card issued by a bank. The workstation 95 operates on behalf of the bank that issued the card, or by the bank itself or by an affiliated financial institution.
1.0�The mobile communication device 11 links with the web site presented on behalf of the payment service provider to act as a portal for financial institutions, such as the ATM system workstation 95. 2.0�The operation server web portal redirects the user's link to a web site operated by the workstation 95 on behalf of the financial institution. The payment service provider which operates the operation server 14 maintains an account with the financial institution to support fund transfer between the accounts held by the users and the payment service provider. 3.0�The user inserts the financial card 96 into the �reader-lite� device 90, which performs the necessary authentication processes. 4.0�Via the web site operated by the workstation 95, the user instructs the financial system to transfer funds from the user's account to the payment service provider account managed by the financial institution associated with the workstation 95. 5.0�The Bank returns a message indicating that the transfer has been completed to the operation server, where the account system increases the user's balance of stored value for the payment service provider network. 6.0�The operation server 14 transfers stored value data deducted from the users account via the �reader lite� device 90 to the mobile communication device 11, where it is stored for later use. FIG. 10 illustrates an aspect of the financial transaction architecture described herein by which stored value may be transferred between mobile communication devices. Thus, a first mobile communication device 110 held by the payer and a second mobile communication device 111 held by the payee establish communication, either through proximity coupling or by another communication channel which they may support directly between the devices, or using the telecommunication provider network. A representative control flow for a transaction between the mobile communication devices 110 and 111 is shown in FIG. 10. Each step is described as follows:
1.0�The mobile communication device 110 communicates with the mobile communication device 111, to establish a link for transfers of stored value in the form of an electronic check or a coupon, or a ticket purchased earlier by the payer, to the payee's mobile communication device 111, using resources such as the industry standard SIM Toolkit. 2.1�The balance of the stored value in the payer's mobile communication device 110 is deducted by the amount to be transferred, and a message is composed having the characteristics of a check including a payer's signature and an amount to be transferred, or having the characteristics of an endorsed coupon or ticket including a payer's signature along with the electronic coupon or ticket to be transferred. 2.2�The payer transfers the electronic check or endorsed coupon to the payee's mobile communication device 111. 3.0�The payee's mobile communication device 111 stores the electronic check or endorsed coupon as a blocked balance in the stored value memory on the device 111. The payee cannot redeem the check or coupon at this stage. Rather, the blocked balance must be authenticated in an exchange with the operations server, such as at an exchange as described below with reference to FIG. 11. 4.0�The payee's mobile communication device 111 can execute similar transactions with other mobile communication devices, moving the electronic check or endorsed coupon from device to device along with the necessary signatures or endorsements to allow for future redemption of the check or coupon. FIG. 11 illustrates an extension of the financial transaction architecture of FIG. 10, illustrating the transfer of value among multiple mobile communication devices, and redeeming the transferred value using a payment service provider network in an off-line mode, as described herein. In the architecture of FIG. 11, the first mobile communication device 150 acts as an initial payer. A second mobile communication device 151 is referred to as payee A. Subsequent mobile communication devices are connected in a daisy chain communication sequence to a final mobile communication device 152 referred to as payee Z. Each of the mobile communication devices 150-152 includes on-board resources to act as stored value devices and as transaction terminals using proximity coupling devices or other communication technologies for transferring value from device to device. A �reader-lite� device 153, or other transaction terminal which has a communication link with the operation server 14 is included in the architecture shown in FIG. 11. A representative control flow for transactions moving value from device to device, and settling the transactions, is shown in FIG. 11. Each step is described as follows:
1.0�The payer holding mobile communication device 150 transfers stored value to mobile communication device 151 of payee A using a sequence of events such as that described with respect to FIG. 10. 2.0�Payee A holding mobile communication device 151 transfers the value in a check like form to the next mobile communication device, including the signature from the Payer and an endorsement by Payee A, and so on until the stored value reaches the final mobile communication device 152 held by Payee Z. 3.0�Payee Z using mobile communication device 152 couples with the �reader-lite� device 153 using a contactless link, for example, and presents the stored value with the necessary signatures from the payer and endorsements from all of the payees in the sequence, via the operation server 14 through the links available using the �reader-lite� device 153. 4.0�The operation server 14 managing the accounts moves the stored value from the original payer to each payee in the sequence until the stored value finally is credited to the account of the last payee, payee Z. 5.0�The operation server 14 transfers the stored value, or otherwise releases the blocked value, via the �reader-lite� device 153 to the mobile communication device 152 held by payee Z. A representative procedure for transferring value in a check-like manner can be understood with reference to the sequence of steps illustrated in FIG. 12. According to the procedure shown in FIG. 12, each mobile communication device maintains a data structure including three instruction stacks labeled Load stack 250, Deduct stack 251, and Block stack 252 in this example. The Load stack 250 stores instructions used for loading value or increasing the value stored on the device. The Deduct stack 251 stores instructions used for deducting value stored on the device. The Block stack 252 stores instructions for blocking access to value transferred to the device prior to confirmation of the transfer by the operations server or other authorization service. Of course a variety of other data organizations can be utilized. A representative control flow for transactions moving value from device to device, and settling the transactions, is shown in FIG. 11. Each step is described as follows:
1.1�The payer issuing the check-like the transfer executes a debit instruction in Deduct stack 251 and a corresponding credit instruction in Block stack 252. 1.2�Next, the issuing payer transfers an electronic token to Payee A along with loading a debit instruction in its Block stack 252. In response to the transfer, Payee A loads a corresponding credit instruction in its Block stack 252. 2.1�Payee A transfers an electronic token to Payee B and loads a debit instruction in its Block stack 252. In response to the transfer, Payee B loads a corresponding credit instruction in its Block stack 252. 3.1�Payee B transfers an electronic token to Payee C and loads a debit instruction in its Block stack 252. In response to the transfer, Payee C loads a corresponding credit instruction in its Block stack 252. 4.1�Payee C transfers an electronic token to Payee Z and loads a debit instruction in its Block stack 252. In response to the transfer, Payee Z loads a corresponding credit instruction in its Block stack 252. 4.2�Payee Z communicates with the operation server via a �reader-lite� device 153, or other transaction terminal which has a communication link with the operation server 14, using a web portal or otherwise, and presents the check-like electronic token carrying the signatures of each of the mobile communication devices in the sequence, to be �cashed�. In response to authentication and authorization from the operation server, the mobile communication device held by Payee Z issues a debit instruction in its Block stack 252 and a corresponding credit instruction in its Load stack 250. The accounting programs in the operation server balance the accounts of the issuing payer and the final payee Z, completing the transaction. FIG. 13 illustrates a representative data structure combination maintained on mobile communication devices and secure memory for the purposes of tracking stored value on the device. The data structure for each mobile communication device includes Load stack 250, Deduct stack 251, and Block stack 252 described above with reference to FIG. 12 in which instructions relating to loading value, deducting value and blocking value on the device are maintained. Associated with Load stack 250 is a Load log 255 which maintains a log of executed instructions from Load stack 250 for the purposes of tracking, recordkeeping, fraud detection, and verification of the stored value. Likewise, a Deduct log 256 is maintained in association with Deduct stack 251. The Block stack 252 is associated with a Blocked log 257 and an unBlocked log 258, which respectively maintain records of executed instructions from Block stack 252 which result in blocking value transferred to other parties or otherwise encumber pending action by the operation server or other system.
161�The mobile communication device user A1 requests merchant B2 to add value 300 points. 162�The mobile communication device user A1 pays money to merchant B2. 163�300 points (e-money issued by biz chain B of merchant B2) are added to the mobile device of mobile communication device user A1. 164�The store terminal of merchant B2 sends the transaction record to the payment service provider settlement system. 165�The transaction record is sent from mobile communication device user A1 to telecom operator A, e.g., by short message service 166.1�The transaction record is passed from telecom operator A to the payment service provider settlement system. 166.2�A blacklist of poor credit risks, such as mobile communication device user accounts that are associated or suspected of fraud, is updated from telecom operator A to the payment service provider settlement system. 167�Verification is performed payment service provider settlement system, checking whether the transaction record from the server of telecom operator A matches the transaction record from merchant B2. If yes, the subsequent procedures follow. If no, then the �purse� of stored value in the mobile device is locked, and the mobile communication device user A1 contacted for data correction and unlocking of the mobile device in case fraud was not involved. 168�The payment service provider settlement system generates a record along with a unique serial number for the 300 points. 169�The payment service provider settlement system logs the unique serial number of the 300 points of e-money and proceeds with the bookkeeping and accounting processes, such as those of FIGS. 17-20. In another embodiment, a user can add value to a mobile communication device via a telecom network or wireless LAN connected to the Internet.
171�The payment service provider settlement system debits the account of payment service provider 300 points of e-money, and credits the same value to the account of merchant B2. 172�The payment service provider settlement system purchases the equivalent value of e-money issued by biz chain B from biz chain B. In this example, a ratio of 1:1 is used, as show by the same 300 point value on credit and debit sides. 173�The payment service provider settlement system debits the account of merchant B2 300 points of e-money of biz Chain B, and credits the same value to the account of mobile communication device user A1 FIG. 18 illustrates condensed accounts of credits and debits associated with the money flow of FIG. 17. The account of mobile communication device user A1 181 has only a 300 point credit and has a final credit balance of 300 points. The account of merchant B2 182 has both a 300 point credit and a 300 point debit, and has a final balance of 0 points. The account of the payment service provider 183 has only a 300 point debit and has a final debit balance of 300 points. Although not shown, in one example, ultimately the payment service provider is reimbursed by mobile communication device user A1, such as via the billing system of a telecom service provider or internet service provider.
191�The payment service provider settlement system debits the payment service provider 300 points of e-money, and credits the same value to the purchase account of the payment service provider. 192�The payment service provider settlement system triggers a process to purchase the equivalent value of e-money issued by biz Chain B. In this example, a ratio of 1:1 is used, as shown by the same 300 point figure on credit and debit sides. 193�The payment service provider settlement system debits the purchase account of the payment service provider 300 points of the e-money issued by biz chain B, and credits the same value to merchant B2. 194�The payment service provider settlement system debits merchant B2 300 points of e-money of biz chain B, and credits the same value to mobile communication device user A1. FIG. 20 illustrates condensed accounts of credits and debits associated with the money flow of FIG. 19. The account of mobile communication device user A1 201 has only a 300 point credit and has a final credit balance of 300 points. The account of merchant B2 202 has both a 300 point credit and a 300 point debit, and has a final balance of 0 points. The account of the payment service provider 203 has only a 300 point debit and has a final debit balance of 300 points. The purchase account of payment service provider 204 has both a 300 point credit and a 300 point debit, and has a final balance of 0 points. Although not shown, in one example, ultimately the payment service provider is reimbursed by mobile communication device user A1, such as via the billing system of a telecom service provider or internet service provider.
211�The mobile communicate device user B1 requests telecom operator B to add 500 points of value by SMS. 212�The SMS center of telecom operator B requests authorization to add the 500 points from the authorization center of telecom operator B. 213.1�If the request is determined as valid by the authorization center of telecom operator B, the transaction is passed to the billing system of telecom operator B. 213.2�If the request is determined as valid by the authorization center of telecom operator B, then the SMS Center of telecom operator B replies by SMS to the mobile communicate device user B1 to add 500 points to the mobile device of mobile communicate device user B1. 214.1�The billing system of telecom operator B passes the transaction record to the payment service provider settlement system. 214.2�A blacklist of poor credit risks, such as mobile communication device user accounts that are associated or suspected of fraud, is updated from the billing system of telecom operator B to the payment service provider settlement system. 215�The payment service provider settlement system generates a record along with a unique serial number for the 500 points of e-money issued by the payment service provider. 216�The payment service provider settlement system logs the serial number of the e-money and proceeds with the subsequent bookkeeping and accounting process, so that the payment service provider directly credits 500 points to user B1. FIG. 22 illustrates control flow in a payment service provider network, for a transaction to use a mobile communications device to pay money at a store terminal of a merchant, among mobile communicate device user C1, merchant A1, telecom operator C, and the payment service provider settlement system. The merchant A1 includes a counter and a store terminal. Each step is explained as follows:
221�The mobile communicate device user C1 checks the balance in the e-purse of the mobile device, which turns out to still have 1000 points of stored value. 222�The mobile communicate device user C1 uses the mobile device to pay 200 points for purchases with merchant A1. 223�200 points of e-money issued by the payment service provider is deducted from the e-purse of the mobile device by the store terminal of merchant A1. 224�The store terminal of merchant A1 sends the transaction record to the payment service provider settlement system. 225�The transaction record is sent to the telecom operator C from the mobile communicate device of mobile communicate device user C1 by short message service. 226.1�The billing system of telecom operator C passes the transaction record to the payment service provider settlement system. 226.2�A blacklist of poor credit risks, such as mobile communication device user accounts that are associated or suspected of fraud, is updated from the billing system of telecom operator C to the payment service provider settlement system. 227�If the request is verified by the payment service provider settlement system by matching the transaction record from the server of the telecom operator C with the transaction record from merchant A1. If yes, the subsequent procedures follow. If no, then the �purse� of stored value in the mobile device is locked, and the mobile communication device user C1 contacted for data correction and unlocking of the mobile device in case fraud was not involved. 228�The payment service provider settlement system generates a record along with a unique serial number for the 200 points of e-money. 229�The payment service provider settlement system logs the serial number of the e-money and proceeds with the subsequent bookkeeping and accounting process, such as that shown in FIGS. 23-26. FIG. 23 illustrates a money flow among condensed accounts of credits and debits associated with the transaction of FIG. 22, among the account of mobile communication device user C1 236, the account of merchant A1 237, the account of payment service provider 238, and the purchase account of payment service provider 239. Each step is explained as follows:
231�The payment service provider settlement system debits the account of mobile communication device user C1, assuming C1 has 1000 points of stored value on the mobile communication device, by 200 points issued by the payment service provider, and the account of credits merchant A1 by the same value. 232�The payment service provider settlement system debits the account of merchant A1 by 200 points of the e-money issued by payment service provider, and credits the account of the payment service provider by the same value. 233�The payment service provider settlement system triggers a process to purchase the equivalent value of e-money issued by biz chain A. In this example, a ratio of 1:1 is used, as shown by the same 300 point figure on the credit side of the account of payment service provider 238 and the debit side of the purchase account of payment service provider 239. 234�The payment service provider settlement system debits the 200 points of e-money of Biz Chain A from the purchase account of payment service provider, and credits the account of merchant A1 by the same value. 235�The payment service provider settlement system pays the 200 points of e-money of biz chain A in the account of merchant A1, back to the purchase account of payment service provider, to complete the transaction. FIG. 24 illustrates condensed accounts of credits and debits associated with the money flow of FIG. 23. The account of mobile communication device user C1 241 has a 1000 point credit and a 200 point debit, and has a final credit balance of 800 points. The account of merchant A1 242 has two 200 point credits and two 200 point debits, and has a final balance of 0 points. The account of the payment service provider 243 has both a 200 point credit and a 1000 point debit, and has a final debit balance of 800 points. The purchase account of payment service provider 244 has both a 200 point credit and a 200 point debit, and has a final balance of 0 points. Although not shown, earlier, mobile communication device user C1 had purchased 1000 points of e-money issued by the payment service provider.
2501�The payment service provider settlement system debits the account of mobile communication device user C1, assuming C1 has 1000 points of stored value on the mobile communication device, by 200 points issued by biz chain A, and credits the account of merchant A1 by the same value. 2502�The payment service provider settlement system debits 200 points of the e-money issued by biz chain A from the account of merchant A1, and credits the purchase account of payment service provider. 2503�The payment service provider settlement system triggers a process to purchase the equivalent value of e-money issued by the payment service provider. In this example, a ratio of 1:1 is used, as shown by the same 200 point figure on the credit side of the purchase account of payment service provider 2509 and the debit side of the purchase account of payment service provider 2509. 2504�The payment service provider settlement system pays the 200 points of e-money of the payment service provider back to the account of payment service provider to complete the transaction. FIG. 26 illustrates condensed accounts of credits and debits associated with the money flow of FIG. 25. The account of mobile communication device user C1 261 has a 1000 point credit and a 200 point debit, and has a final credit balance of 800 points. The account of merchant A1 262 has a 200 point credit and a 200 point debit, and has a final balance of 0 points. The account of the payment service provider 263 has both a 200 point credit and a 1000 point debit, and has a final debit balance of 800 points. The purchase account of payment service provider 264 has both a 200 point credit and a 200 point debit, and has a final balance of 0 points. Although not shown, earlier, mobile communication device user C1 had purchased 1000 points of e-money issued by the payment service provider.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4899036May 22, 1989Feb 6, 1990The General Electric Company, P.L.C.Transaction systemUS5521363Feb 16, 1994May 28, 1996Tannenbaum; David H.System and method for tracking memory card transactionsUS5699549Dec 30, 1994Dec 16, 1997Samsung Electronics Co., Ltd.Memory card having a card management information area for improved format capability and recording, reproducing, and erasing methods thereforUS5920847Oct 7, 1996Jul 6, 1999Visa International Service AssociationElectronic bill pay systemUS6378073Dec 22, 1997Apr 23, 2002Motorola, Inc.Single account portable wireless financial messaging unitUS6532518Feb 4, 2002Mar 11, 2003Catuity, Inc.Data carrying device and systems for use therewithUS6577861Dec 14, 1998Jun 10, 2003Fujitsu LimitedElectronic shopping system utilizing a program downloadable wireless telephoneUS6615190Feb 9, 2000Sep 2, 2003Bank One, Delaware, National AssociationSponsor funded stored value cardUS6731199Jul 26, 1999May 4, 2004Rohm Co., Ltd.Non-contact communication systemUS7072864Feb 20, 2003Jul 4, 2006Bank One Deleware, N.A.Customer activated multi-value (CAM) cardUS7127236Dec 18, 2002Oct 24, 2006Vivotech, Inc.Micropayment financial transaction process utilizing wireless network processingUS7231025Dec 19, 2000Jun 12, 2007Enco-Tone Ltd.Acoustic encoding of dynamic identification codesUS7280981 *Aug 27, 2002Oct 9, 2007Visa U.S.A. Inc.Method and system for facilitating payment transactions using access devicesUS20020025796May 8, 2001Feb 28, 2002Taylor William StuartSystem and method conducting cellular POS transactionsUS20020174071Feb 9, 2001Nov 21, 2002Alain BoudouMethod for loading a piece of software in a smart card, in particular appletUS20020194135Jun 15, 2001Dec 19, 2002Stuart TaylorSystem and method for providing e-servicesUS20030055735Apr 23, 2001Mar 20, 2003Cameron Richard N.Method and system for a wireless universal mobile product interfaceUS20030069787 *May 22, 2001Apr 10, 2003Tendon Consulting Group KbComputer system and method for the establishment of a virtual marketplace of promotional valuesUS20030130940Jul 26, 2002Jul 10, 2003First Data CorporationValue transfer systems and methodsUS20030172028Mar 7, 2002Sep 11, 2003International Business Machines CorporationAuthorization of payment for a commercial transaction via a bluetooth enabled deviceUS20030236872May 9, 2003Dec 25, 2003Kestrel Wireless. Inc.Method and system for enabling electronic transactions via a personal deviceUS20040030601Aug 6, 2003Feb 12, 2004Pond Russell L.Electronic payment methods for a mobile deviceUS20040049454Sep 11, 2003Mar 11, 2004Hiroshi KannoElectronic money settlement method using mobile communication terminalUS20040068446Dec 7, 2001Apr 8, 2004Do Thanh VanRoaming for mobile e-commerceUS20040235450 *May 19, 2004Nov 25, 2004Einar RosenbergApparatus and method for increased security of wireless transactionsUS20040243490Sep 3, 2001Dec 2, 2004Juhani MurtoMethod and system for performing a financial transaction in a mobile communications systemUS20050222961Sep 14, 2004Oct 6, 2005Philippe StaibSystem and method of facilitating contactless payment transactions across different payment systems using a common mobile device acting as a stored value deviceUS20060097037Jun 9, 2003May 11, 2006Ken SakamuraElectronic value transfer device equipped with non-contact ic interfaceUS20060165060Jan 21, 2005Jul 27, 2006Robin DuaMethod and apparatus for managing credentials through a wireless networkUS20060253335Jan 22, 2004Nov 9, 2006Gerard KeenaCash based purchasing using mobile communicationUS20060287004 *Jun 17, 2005Dec 21, 2006Fuqua Walter BSIM card cash transactionsUS20090098825 *Mar 7, 2005Apr 16, 2009Heikki HuomoMethod and mobile terminal device including smartcard module and near field communicationsCN1757040ANov 7, 2003Apr 5, 2006比特瓦雷特股份有限公司Portable mobile terminalEP0949593A2Mar 30, 1999Oct 13, 1999Citicorp Development CenterSystem, method and apparatus for value exchange utilizing value-storing apparatusEP1083529A2Aug 30, 2000Mar 14, 2001Nippon Telegraph and Telephone CorporationData storing system, issuing apparatus, data providing apparatus and computer readable medium storing data storing programEP1163633B1Feb 22, 2000Jun 15, 2005Chip Application Technologies LimitedIntegrated point-of-sale and internet multi-application system and method of use thereofEP1221669A1May 30, 2001Jul 10, 2002NTT DoCoMo, Inc.Electronic value systemEP1553510A1Jun 9, 2003Jul 13, 2005Noboru KoshizukaElectronic value transfer device equipped with non-contact ic interfaceGB2130412A Title not availableJP2005020173A Title not availableKR20000034524U Title not availableWO1990003016A1Sep 7, 1989Mar 22, 1990Regie Autonome TransportsContactless infrared payment method using a memory card, particularly for transport means, and payment device using such methodWO1997045814A1May 26, 1997Dec 4, 1997Behruz VazvanReal time system and method for remote purchase payment and remote bill payment transactions and transferring of electronic cash and other required dataWO1999053449A1Apr 6, 1999Oct 21, 1999Moshe AdukSecured data transaction system for smart cardsWO2000079411A2Jun 7, 2000Dec 28, 2000Sun Microsystems IncMethod and apparatus for commercial transactions via the internetWO2001065499A2Mar 1, 2001Sep 7, 2001Cubic CorpSystem and method for electronic distribution of benefitsWO2001093139A1May 30, 2001Dec 6, 2001Ntt Docomo IncElectronic value systemWO2002063528A1Dec 7, 2001Aug 15, 2002Ericsson Telefon Ab L MROAMING FOR MOBILE e-COMMERCEWO2003021544A1Sep 3, 2001Mar 13, 2003Nokia CorpA method and system for performing a financial transaction in a mobile communications systemWO2004066228A1Jan 22, 2004Aug 5, 2004Derek GroganCash based purchasing using mobile communicationWO2004079611A1Nov 7, 2003Sep 16, 2004Bitwallet IncMobile terminalWO2004112329A1Jun 18, 2004Dec 23, 2004Tea Vui HuangMethod and system for data synchronizingWO2005119606A1May 28, 2004Dec 15, 2005IbmSmart card data transaction system and methods for providing storage and transmission securityWO2006085805A1Feb 14, 2005Aug 17, 2006Smarttrust AbMethod for performing an electronic transaction* Cited by examinerNon-Patent CitationsReference1"Digital Cellular Telecommunications System (Phase 2+); Subscriber Identity Modules (SIM); Functional Characteristics (GSM 02.17 version 8.0.0 Release 1999)," ETSI TS 100 922 V8.0.0 (Apr. 2000), www.etsi.org, 2000, 13 pp.23rd Generation Partnership Project; Specification of the SIM Application Toolkit for the Subscriber Identity Module-Mobile Equipment (SIM-ME) Interface (Release 1999), 3GPP TS 11.14 V8.17.0, 2004, 139 pp.3ISO 4443, An Introduction to the Contactless Standard for Smart Cards and Its Relavance to Customers, , created Oct. 2003, 9 pp.4ISO 4443, An Introduction to the Contactless Standard for Smart Cards and Its Relavance to Customers, <http://www.otiglobal.com/objects/ISO%2014443%20WP%204.11.pdf>, created Oct. 2003, 9 pp.5ISO/IEC 7816 Part 4: Interindustry Command for Interchange, http://www.ttfn.net/techno/smartcards/iso7816-4.html, 1995, 106 pp.6ISO/IEC 7816 Part 4: Interindustry Command for Interchange, http://www.ttfn.net/techno/smartcards/iso7816�4.html, 1995, 106 pp.7ISO7816 (Part 1-3) Asynchronous Smartcard Information, http://ttfn.net/techno/smartcards/iso7816123.html, Part 1 2003, Part 2 1999, Part 3 2006, 29 pp.8Short Message Service, http://en.wikipedia.org/wiki/Short-message-service, downloaded Nov. 11, 2006, 16 pp.9Short Message Service, http://en.wikipedia.org/wiki/Short�message�service, downloaded Nov. 11, 2006, 16 pp.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8275353 *Oct 3, 2011Sep 25, 2012Macronix International Co., Ltd.System and method of managing contactless payment transactions using a mobile communication device as a stored value deviceUS8332272 *Dec 27, 2011Dec 11, 2012Blaze Mobile, Inc.Single tap transactions using an NFC enabled mobile deviceUS8352323 *Nov 30, 2007Jan 8, 2013Blaze Mobile, Inc.Conducting an online payment transaction using an NFC enabled mobile communication deviceUS8583494 *Dec 7, 2012Nov 12, 2013Blaze Mobile, Inc.Processing payments at a management server with user selected payment methodUS8589236 *Oct 18, 2010Nov 19, 2013Faber Financial, LlcMobile payment station system and methodUS8589237 *Dec 7, 2012Nov 19, 2013Blaze Mobile, Inc.Online purchase from a mobile device using a default payment methodUS8620754 *Jan 7, 2013Dec 31, 2013Blaze Mobile, Inc.Remote transaction processing using authentication informationUS8630905 *Nov 19, 2012Jan 14, 2014Michelle FisherSingle tap transactions using a secure elementUS8630906 *Nov 19, 2012Jan 14, 2014Michelle FisherSingle tap transactions using a point-of-sale terminalUS8688526 *Dec 7, 2012Apr 1, 2014Michelle FisherFinancial transaction processing with digital artifacts using a mobile communications deviceUS8693995Dec 13, 2007Apr 8, 2014Michelle FisherCustomized mobile applications for special interest groupsUS8694380 *Jan 7, 2013Apr 8, 2014Michelle FisherRemote transaction processing using a default payment method and couponsUS8725575 *Jan 7, 2013May 13, 2014Michelle FisherRemote transaction processing with multiple payment mechanismsUS8725576 *Jan 7, 2013May 13, 2014Michelle FisherRemote transaction processing with multiple payment methods using authenticationUS8725577 *Aug 29, 2013May 13, 2014Michelle FisherPersonalized mobile banking transactionsUS8751313 *Nov 19, 2012Jun 10, 2014Michelle FisherSingle tap transactions using a mobile applicationUS8751314 *Nov 19, 2012Jun 10, 2014Michelle FisherSingle tap transactions using a serverUS8751315 *Dec 5, 2012Jun 10, 2014Michelle FisherUsing a mobile device as a point of sale terminalUS8799085 *Nov 19, 2012Aug 5, 2014Michelle FisherRedeeming coupons using NFCUS8805726 *Dec 10, 2012Aug 12, 2014Michelle FisherOnline shopping using NFC and a mobile deviceUS8818870 *Dec 7, 2012Aug 26, 2014Michelle FisherUsing a secure element coupled to a mobile device as a POS terminal for processing mag stripe transactionsUS20090144161 *Nov 30, 2007Jun 4, 2009Mobile Candy Dish, Inc.Method and system for conducting an online payment transaction using a mobile communication deviceUS20110093351 *Oct 18, 2010Apr 21, 2011Faber Financial, LlcMobile Payment Station System and MethodUS20120022957 *Oct 3, 2011Jan 26, 2012Macronix International Co., Ltd.System and Method of Managing Contactless Payment Transactions Using a Mobile Communication Device as a Stored Value DeviceUS20120150601 *Dec 27, 2011Jun 14, 2012Blaze Mobile, Inc.Single tap transactions using an nfc enabled mobile deviceUS20130073373 *Nov 19, 2012Mar 21, 2013Blaze Mobile, Inc.Single tap transactions using a point-of-sale terminalUS20130080228 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using a user selected cardUS20130080229 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using user selected couponsUS20130080230 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap using both user selected payment method and user selected couponsUS20130080231 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a mobile applicationUS20130080232 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a mobile deviceUS20130080233 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a secure elementUS20130080240 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Single tap transactions using a serverUS20130080241 *Nov 19, 2012Mar 28, 2013Blaze Mobile, Inc.Redeeming coupons using nfcUS20130097032 *Dec 11, 2012Apr 18, 2013Blaze Mobile, Inc.Utilizing shopping lists for nfc transactionsUS20130097036 *Dec 5, 2012Apr 18, 2013Blaze Mobile, Inc.Using a mobile device as a point of sale terminalUS20130097040 *Dec 7, 2012Apr 18, 2013Blaze Mobile, Inc.Online purchase from a mobile device using a default payment methodUS20130097083 *Dec 5, 2012Apr 18, 2013Blaze Mobile, Inc.Using a secure element coupled to a mobile device as a pos terminal for processing nfc transactionsUS20130103512 *Dec 11, 2012Apr 25, 2013Blaze Mobile, Inc.Online shopping using nfc and a secure elementUS20130103517 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Using a secure element coupled to a mobile device as a pos terminal for processing mag stripe transactionsUS20130103588 *Dec 7, 2012Apr 25, 2013Blaze Mobile, Inc.Processing payments at a management server with a user selected payment methodUS20130124351 *Dec 5, 2012May 16, 2013Blaze Mobile, Inc.Using an nfc enabled mobile device as a pos terminalUS20140247822 *May 15, 2014Sep 4, 2014Microsoft CorporationDynamic range wireless communications access point* Cited by examinerClassifications U.S. Classification455/406, 705/44, 705/39, 455/414.1, 455/410, 705/41, 705/26.1, 455/556.1, 705/40International ClassificationH04M11/00Cooperative ClassificationG06Q20/20, G06Q20/3278, G06Q20/102, G06Q20/16, G06Q20/32, H04M15/68, G06Q20/10, G06Q20/382, G06Q20/3229, G06Q20/26, G06Q20/40, G06Q20/085, H04M2215/0196, G06Q30/0601, G06Q20/105European ClassificationG06Q20/16, G06Q20/26, G06Q20/32, H04M15/68, G06Q20/085, G06Q20/3229, G06Q20/382, G06Q20/3278, G06Q20/105, G06Q20/40, G06Q20/102, G06Q20/10, G06Q30/0601, G06Q20/20Legal EventsDateCodeEventDescriptionApr 29, 2008ASAssignmentOwner name: MACRONIX INTERNATIONAL CO., LTD., TAIWANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SUN, ALBERT;AN, PAO-CHIEH;LO, YING-CHE;AND OTHERS;REEL/FRAME:020874/0516;SIGNING DATES FROM 20070514 TO 20070515Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SUN, ALBERT;AN, PAO-CHIEH;LO, YING-CHE;AND OTHERS;SIGNING DATES FROM 20070514 TO 20070515;REEL/FRAME:020874/0516RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google