Smart card load and purchase transactions using wireless telecommunications network
Claim Score by NHIP
Abstract
A smart card transaction allows a consumer to load value onto a smart card and to make purchases using a smart card with a mobile telephone handset over the telecommunications network. For loading, the system includes: a mobile telephone handset including a card reader; a gateway computer; a funds issuer computer; and an authentication computer. The mobile telephone handset receives a request from a user to load a value onto the smart card. The handset generates a funds request message which includes the value and sends the funds request message to a funds issuer computer. The funds issuer computer debits an account associated with the user. Next, the handset generates a load request message with a cryptographic signature and sends the load request message to an authentication computer which authenticates the smart card. The handset receives a response message which includes a cryptographic signature and an approval to load. Finally, the handset validates the second cryptographic signature and loads the value onto the smart card. For payment, the system includes a merchant server and a payment server. First, the handset sends an order request message to the merchant server computer, and in return receives a purchase instruction message. The handset processes the purchase instruction message locally, and then sends a draw request message to a payment server computer. The payment server computer sends a debit message which includes a cryptographic signature and an approval to debit the smart card. Finally, the handset validates the cryptographic signature and debits the smart card.

Term
Term ended
Projected expiry passed 31 May 2020, 6.3 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
25 claims: 4 independent, 21 dependent
- 1A method of loading value onto a subscriber identification module (SIM) located within a mobile telephone handset of a user, said method comprising:sending a funds request message from said SIM to a bank system that controls an account of said user, said funds request message including a load value and a funding account identifier that identifies said account of said user;sending a funds response message from said bank system to said SIM indicating an approval to debit said user account by said load value;sending a load request message from said SIM to an issuer system, said load request message including a first cryptographic signature, wherein said first cryptographic signature is generated using a first cryptographic key shared between said SIM and an issuer;validating said first cryptographic signature by said issuer system and authenticating said SIM;sending a load response message from said issuer system to said SIM including a second cryptographic signature, wherein said second cryptographic signature is generated using a second cryptographic key shared between said SIM and said issuer;validating, by said SIM, said second cryptographic signature;and loading said load value into a stored-value application of said SIM.
- 7A method of loading value over a wireless telecommunications network onto a subscriber identification module (SIM) located within a mobile telephone handset, said method comprising:receiving at said SIM within said mobile telephone handset a request from a user to load a load value onto said SIM;generating, by said SIM, a cryptographic signature S 1 using a first cryptographic key shared between said SIM and an issuer;preparing a load data message that includes said load value, a funding account identifier, and said cryptographic signature S 1 ;sending said load data message over said telecommunications network from said SIM of said handset to a gateway server computer;receiving an approval response message from said gateway server computer at said SIM of said handset, said approval response message including a cryptographic signature S 2 and an approval to load said load value, wherein said cryptographic signature S 2 is generated using a second cryptographic key shared between said SIM and said issuer;validating, by said SIM, said cryptographic signature S 2 ;and loading said load value into a stored-value application of said SIM.
- 12A method of purchasing an item from a merchant by a user over a wireless telecommunications network using a mobile telephone handset, said method comprising:formulating a draw request message at a subscriber identification module (SIM) of said handset that includes a purchase amount of said item;sending said draw request message over said telecommunications network from said SIM of said handset to a payment server computer associated with said merchant;generating a first cryptographic signature at said payment server computer using a first cryptographic key shared between said SIM and an issuer;sending a debit message from said payment server computer to said SIM in said handset including said second cryptographic signature and an approval to debit said SIM by said purchase amount;verifying said first cryptographic signature at said SIM using said first shared cryptographic key;debiting a stored-value application of said SIM by said purchase amount;sending a debit result message from said SIM to said payment server computer that includes a second cryptographic signature, said second cryptographic signature being generated using a second cryptographic key shared between said SIM and said issuer, said second cryptographic signature uniquely identifying said SIM and indicating that said stored-value application of said SIM has been debited by said purchase amount;verifying said second cryptographic signature from said SIM using said second shared cryptographic key;and sending a confirmation message from said payment server computer to said merchant indicating that said SIM has been debited by said purchase amount, whereby said merchant releases said item to said user.
- 17Broadest claimClaim Score 41, average(NHIP)A method of purchasing an item from a merchant server computer by a user over a wireless telecommunications network using a mobile telephone handset, said method comprising:formulating a draw request message at said handset that includes a purchase amount of said item;sending said draw request message over said telecommunications network from a subscriber identification module (SIM) of said handset to a payment server computer associated with said merchant server computer;receiving a debit message at said handset from said payment server computer that includes a cryptographic signature S 2 and an approval to debit said SIM by said purchase amount, said cryptographic signature S 2 being generated using a first cryptographic key shared between said SIM and an issuer;verifying said cryptographic signature S 2 at said SIM using said first shared cryptographic key;debiting a stored-value application of said SIM by said purchase amount;sending a debit result message from said SIM to said payment server computer that includes a cryptographic signature S 3 , said cryptographic signature S 3 being generated using a second cryptographic key shared between said SIM and said issuer, said signature S 3 uniquely identifying said SIM and indicating that said stored-value application of said SIM has been debited by said purchase amount;and receiving said item by said user.
Independent claims4
83 paragraphs in 5 sections, as filed
0001This application is a continuation of U.S. patent application Ser. No. 09/587,092 filed May 31, 2000 entitled “Smart Card Transactions Using Wireless Telecommunications Network,” which in turn claims priority of U.S. provisional patent applications No. 60/146,559 filed Jul. 30, 1999 and No. 60/156,765, filed Sep. 29, 1999, all of which are hereby incorporated by reference.
FIELD OF THE INVENTION
0002The present invention relates generally to smart cards. More specifically, the present invention relates to loading value and making purchases using a smart card in conjunction with a mobile telephone.
BACKGROUND OF THE INVENTION
0003Consumers of today have a need to make low-value cash transactions quickly and efficiently. The above-referenced U.S. patent applications describe techniques whereby a consumer may use a smart card to purchase merchandise over the Internet, to load value over the Internet, to perform transactions using a “virtual” smart card, and to perform transactions using a set-top box, respectively. Even with the above techniques, though, there is still a need to use a smart card for low-value cash transactions in other scenarios.
0004In the prior art, consumers have only been able to load value onto a smart card at a fixed device such as an automated teller machine (ATM) or a personal computer connected to the Internet and having a card reader. Consumers these days, however, are extremely mobile (whether in their car or traveling on business) and may desire to load value onto a smart card in many different situations. A consumer may not always have access to an ATM or a personal computer with an Internet connection. For example, a driver pulling up to a parking meter that accepts a smart card for payment may discover that he or she has no value left on the smart card. If there are no ATMs nearby, it will be difficult for this person to load value onto the smart card in order to use the parking meter.
0005<figref idref="DRAWINGS">FIG. 1</figref> illustrates a prior art loading technique <b>10</b>. In this technique a loading device such as an ATM <b>14</b> is used by a consumer to load value onto a smart card <b>18</b>. ATM <b>14</b> is a sophisticated smart card terminal that includes not only a smart card reader, but also a hardware processor and software used to implement the loading of value onto smart card <b>18</b>. As such, ATM <b>14</b> is an integrated unit as it includes both the card reader and the processor. As previously explained, it is not always convenient for a consumer to find an ATM in order to load value onto a smart card.
0006Similarly, consumers may wish to purchase goods and services at other times than when they are sitting in front of their computer at home. For example, a consumer may wish to purchase airtime for a mobile telephone (handset), directions for driving, and other services such as take-out food, theater tickets, traffic reports and stock purchases while they are in transit.
0007<figref idref="DRAWINGS">FIG. 2</figref> illustrates a prior art technique <b>20</b> for making a purchase using a smart card. Using this technique, a consumer uses a purchase terminal <b>22</b> located at a merchant in order to make a purchase using smart card <b>18</b>. Terminal <b>22</b> includes not only a card reader but also a hardware processor and software for decrementing value from card <b>18</b>. As such, terminal <b>22</b> is also an integrated unit in that it includes both the card reader and processor. As previously mentioned, a consumer may wish to make a purchase using a smart card at other times than when the consumer is at a merchant location.
0008As such, there is a need for these consumers to be able to load value and to purchase goods and services when the consumer is mobile.
0009A company named Newcom has implemented a dual subscriber identification module (SIM) for use in a mobile telephone that allows a consumer to swap SIMs. In other words, a consumer may swap a second SIM to provide a new identity for the telephone. This technique, however, is unique to a SIM and is not used for loading value or making a purchase using a smart card. The technique implemented by Newcom only relates to changing the identity of a telephone. As a telephone is essentially a dumb terminal, there are significant challenges to be overcome should a mobile telephone be used in conjunction with smart card transactions.
0010Therefore, a system and technique are desirable that would allow a consumer to perform smart card transactions using a mobile telephone.
SUMMARY OF THE INVENTION
0011To achieve the foregoing, and in accordance with the purpose of the present invention, a system and technique are disclosed that allow a consumer to load value onto a smart card and to make purchases using a smart card with a mobile telephone handset.
0012In a first embodiment, a technique allows the loading of value over a telecommunications network onto a smart card. The mobile telephone handset receives a request from a user to load a value onto the smart card. The handset then generates a funds request message which includes the value and sends the funds request message over the telecommunications network to a funds issuer computer. The funds issuer computer debits an account associated with the user. Next, the handset generates a load request message with a cryptographic signature and sends the load request message over the telecommunications network to an authentication computer which authenticates the smart card. The handset receives a response message which includes a cryptographic signature and an approval to load. Finally, the handset validates the second cryptographic signature and loads the value onto the smart card.
0013In a second embodiment, a technique allows the purchasing of an item over a telecommunications network using a mobile telephone handset. First, the handset sends an order request message to a merchant server computer, and in return receives a purchase instruction message. The handset processes the purchase instruction message locally, and then sends a draw request message over the telecommunications network to a payment server computer. The payment server computer sends a debit message which includes a cryptographic signature and an approval to debit the smart card. Finally, the handset validates the cryptographic signature and debits the smart card, thus the item may be released to a user associated with said smart card.
0014With the explosive growth in mobile telephones over the past several years, a growing number of consumers have access to wireless networks. At the same time, the electronic distribution of goods and services to consumers has also increased. This merchandise includes digitally-delivered goods such as directions, electronic tickets, electronic coupons, games and information, as well as prepaid telephone service. The present invention brings the convenience of electronic cash to consumers and makes it available through their mobile telephones for purchase of such merchandise.
0015The present invention brings smart card transactions to the wireless world. It provides a load and purchase solution for low-value transactions offering consumers a wireless equivalent to cash and coins. Offering loading and purchasing through a mobile telephone provides cardholders the convenience of loading and purchasing without geographic limitation.
0016By integrating defined chip commands with the Short Message Service (SMS) channel, the handset becomes a remote terminal load and purchase device. SMS is a wireless processing protocol capable of sending alphanumeric messages. Chip commands are implemented as special alphanumeric messages in a defined format, containing security data that use SMS as the communications channel. SMS is used as a delivery mechanism that allows users to place data in an “envelope” to be sent and “opened” by a destination. Chip commands are integrated by being placed in the envelope and opened by the recipient.
0017The present invention provides numerous benefits for consumers, banks, merchants and telecommunications service providers.
0018For consumers, the present invention provides a simple, easy-to-use, portable way to pay for goods and services over a wireless network. A smart card can be loaded through a network using the cardholder's handset, putting a wireless ATM in every pocket or purse. The smart card can also be used in both physical and wireless merchant locations to make purchases. Consumer privacy and anonymity is protected throughout the transaction process.
0019For banks, the present invention provides new mobile banking revenue and merchant marketing opportunities. Also, a low-value payment solution is provided without introducing a separate product or brand or requiring a bank to implement significant systems changes.
0020For merchants, the present invention provides a payment solution for low-value transactions, enabling merchants to offer a wider range of digital merchandise. Also, wireless merchants are provided with access to an existing and growing base of cardholders.
0021For operators of a wireless network, the value of the network is increased through new over-the-air revenue and merchant marketing opportunities. Recently, wireless networks have become sensitive to month-end consumer billing “sticker shock.” The present invention offers a pay-as-you-go solution to wireless networks without introducing a separate product or brand. In addition, the present invention integrates into existing wireless networks technologies using the SMS channel.
BRIEF DESCRIPTION OF THE DRAWINGS
0022The invention, together with further advantages thereof, may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:
0023<figref idref="DRAWINGS">FIG. 1</figref> illustrates a prior art smart card loading technique.
0024<figref idref="DRAWINGS">FIG. 2</figref> illustrates a prior art technique for making a purchase using a smart card.
0025<figref idref="DRAWINGS">FIG. 3</figref> illustrates a smart card transaction system according to one embodiment of the invention.
0026<figref idref="DRAWINGS">FIG. 4</figref> illustrates a smart card loading system according to one embodiment of the invention.
0027<figref idref="DRAWINGS">FIGS. 5A and 5B</figref> illustrates a process flow for the loading system of <figref idref="DRAWINGS">FIG. 4</figref>.
0028<figref idref="DRAWINGS">FIG. 6</figref> illustrates a smart card purchasing system according to one embodiment of the invention.
0029<figref idref="DRAWINGS">FIG. 7</figref> illustrates a process flow for the purchasing system of <figref idref="DRAWINGS">FIG. 6</figref>.
0030<figref idref="DRAWINGS">FIGS. 8 and 9</figref> illustrate a computer system suitable for implementing embodiments of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
0031<figref idref="DRAWINGS">FIG. 3</figref> illustrates a smart card transaction system <b>100</b> according to one embodiment of the invention. This high level diagram illustrates that system <b>100</b> includes a mobile telephone <b>102</b> (also referred to as a wireless telephone, cellular telephone or handset), a smart card <b>18</b> able to be inserted into the handset, a telecommunications network <b>104</b> and a server computer <b>106</b> (which may be connected to other computers and/or communications networks). Thus, as opposed to the prior art loading and purchasing techniques shown in <figref idref="DRAWINGS">FIGS. 1 and 2</figref> in which integrated units are used, <figref idref="DRAWINGS">FIG. 3</figref> illustrates a distributed system in which the card reader is present within handset <b>102</b> and processing occurs at a remote location at server <b>106</b> or elsewhere.
0032Handset <b>102</b> is any suitable mobile telephone that incorporates a smart card reader for reading smart card <b>18</b>. Implementation of a card reader inside a handset can be accomplished by those of skill in the art. In a preferred embodiment, system <b>100</b> uses the Europay-Mastercard-Visa (EMV) standard is which case handset <b>102</b> is any handset that can read EMV smart cards and the card reader is an EMV-compliant smart card reader. The EMV standard is a known, published standard for implementing the electromechanical interactions between a smart card and a card reader. Handset <b>102</b> may be preprogrammed with screens of information used to prompt the user or to give information to the user; alternatively, these screens may be downloaded via server <b>106</b>. In a specific embodiment, the Motorola StarTAC D mobile telephone is used to implement the invention, and uses the Motorola StarTAC mobile smart card terminal (MST). Handset <b>102</b> also includes a subscriber identification module (SIM) which are well-known in the art. In a specific embodiment, the SIMphonIC JAVA SIM available from De la Rue is used.
0033Smart card <b>18</b> is typically an ISO 7816 credit card-sized plastic card that includes one or more semiconductor integrated circuits. Also termed “chip cards,” integrated circuit cards, memory cards or processor cards, a smart card can interface with a point-of-sale terminal, an ATM, or with a card reader integrated within a computer, telephone, vending machine, or a variety of other devices. The smart card may be programmed with various types of functionality such as a stored-value application, a credit or debit application, a loyalty application, cardholder information, etc. Although a plastic card is currently the medium of choice for smart cards, it is contemplated that a smart card may also be implemented in a smaller form factor. For example, it may attach to a key chain or be embedded in a subscriber identification module (SIM) or application-specific integrated circuit (ASIC).
0034A smart card may include a microprocessor, random access memory (RAM), read-only memory (ROM), non-volatile memory, an encryption module (or arithmetic unit), and a card reader (or terminal) interface. Other features may be present such as optical storage, flash EEPROM, FRAM, a clock, a random number generator, interrupt control, control logic, a charge pump, power connections, and interface contacts that allow the card to communicate with the outside world. Of course, a smart card may be implemented in many ways, and need not necessarily include a microprocessor or other features.
0035The microprocessor is any suitable central processing unit for executing commands and controlling the device. RAM serves as temporary storage for calculated results and as stack memory. ROM stores the operating system, fixed data, standard routines, look up tables and other permanent information. Non-volatile memory (such as EPROM or EEPROM) serves to store information that must not be lost when the card is disconnected from a power source, and must also be alterable to accommodate data specific to individual cards or changes possible over the card lifetime. This information includes a card identification number, a personal identification number, authorization levels, cash balances, credit limits, and other information that may need to change over time. An encryption module is an optional hardware module used for performing a variety of encryption algorithms. Of course, encryption may also be performed in software. <i>Applied Cryptography</i>, Bruce Schneier, John Wiley & Sons, Inc., 1996 discusses suitable encryption algorithms and is hereby incorporated by reference.
0036The card reader interface includes the software and hardware necessary for communication with the outside world. A wide variety of interfaces are possible. By way of example, the interface may provide a contact interface, a close-coupled interface, a remote-coupled interface, or a variety of other interfaces. With a contact interface, signals from the integrated circuit are routed to a number of metal contacts on the outside of the card which come in physical contact with similar contacts of a card reader device. A smart card may include a traditional magnetic stripe to provide compatibility with traditional card reader devices and applications, and may also provide a copy of the magnetic stripe information within the integrated circuit itself for compatibility.
0037Various mechanical and electrical characteristics of a smart card and aspects of its interaction with a card reader device are described in <i>Smart Card Handbook</i>, W. Rankl and W. Effing, John Wiley & Sons, Ltd., 1997, and are defined by the following specifications, all of which are incorporated herein by reference: <i>Visa Integrated Circuit Card Specification</i>, Visa International Service Association, 1996; <i>EMV Integrated Circuit Card Specification for Payment Systems, EMV Integrated Circuit Card Terminal Specification for Payment Systems, EMV Integrated Circuit Card Application Specification for Payment Systems</i>, Visa International, Mastercard, Europay, 1996; and <i>International Standard; Identification Cards—Integrated Circuit</i>(<i>s</i>) <i>Cards with Contacts, Parts </i>1-6, International Organization for Standardization, 1987-1995.
0038Telecommunications network <b>104</b> is any suitable wireless network implementing a particular protocol for allowing communication with handset <b>102</b>. In general, any wireless application protocol (WAP) may be used. By way of example, the wireless technologies that may be used to implement telecommunications network <b>104</b> are GSM (global system for mobile communications), CDMA (code division multiple access), TDMA (time division multiple access), AMPS (advanced mobile telephone service), and PCS (personal communications service).
0039In the preferred embodiment, the GSM technology is used to implement network <b>104</b> to allow communication with handset <b>102</b>. As is known in the art, GSM technology includes a voice channel and a data channel. The data channel is also termed the Short Message Service (SMS) channel and is used by the present invention to transfer information pertinent to smart card transactions. SMS is a wireless processing protocol capable of sending alphanumeric messages.
0040By integrating defined chip commands with the SMS channel, the handset becomes a remote terminal load and purchase device. Chip commands are implemented as special alphanumeric messages in a defined format, containing security data that use SMS as the communications channel. SMS is used as a delivery mechanism that allows users to place data in an “envelope” to be sent and “opened” by a destination. Chip commands are integrated by being placed in the envelope and opened by the recipient. In other embodiments, the chip commands may be implemented in any suitable fashion, depending upon the protocol used.
0041Server <b>106</b> is a server computer as will be explained in more detail below. Server <b>106</b> includes hardware and software for processing smart card transactions and may be any suitable computer implementing any suitable operating system. Computer <b>106</b> may be stand alone, or may also be connected to other processing computers and financial networks.
Smart Card Loading System
0042<figref idref="DRAWINGS">FIG. 4</figref> illustrates a smart card loading system <b>200</b> according to one embodiment of the invention. System <b>200</b> separates a loading transaction into local cardholder functions (using handset <b>102</b>) and remote bank functions (occurring under the control of processing server <b>106</b>). The local cardholder functions occurring at handset <b>102</b> include the interface to the inserted smart card <b>18</b>, a display for providing the user with information and for accepting commands, the ability to select a load amount, and accept/cancel options. The remote banking functions include validating the transaction, securing funds, authenticating the transaction with the issuer and storing the transaction.
0043Handset <b>102</b> includes an EMV smart card reader, a keypad, a display, a subscriber identification module (SIM) and short message service (SMS) wireless capability. A SIM is a well known multi-application smart card chip located in the handset that identifies the user to the GSM network <b>202</b>, and converts and encrypts voice to data. It also contains both load and purchase software applications to interface between the card/card reader and processing server <b>106</b>. SMS is a data processing channel of the GSM protocol that carries commands, instructions and electronic product delivery.
0044In this embodiment, telecommunications network <b>104</b> is a GSM network <b>202</b> and is used as the communications channel to link the user's handset <b>102</b> with processing server <b>106</b> and the systems located downstream from it.
0045Processing gateway <b>106</b> is a server computer that includes software for conducting load transactions. Gateway <b>106</b> communicates with handset <b>102</b>, funds issuer system <b>204</b> and issuer authentication system <b>206</b>. After the user selects a load transaction, funds issuer system <b>204</b> sends an instruction to processing gateway <b>106</b> that contains necessary funding information. Gateway <b>106</b> acts as a router processing load commands between the smart card and issuer authentication system <b>206</b>, and between authentication system <b>206</b> and funds issuer system <b>204</b>. In one embodiment, communication between server <b>106</b> and systems <b>204</b> and <b>206</b> takes place over any suitable financial network, although communication between the entities may also occur over the Internet or other similar networks.
0046Funds issuer system <b>204</b> offers a bank's remote banking transactions to a user through GSM network <b>202</b>. Issuer system <b>204</b> operates to secure funds from a particular source and can operate to electronically withdraw cash from any suitable consumer account. For example, should the user load value onto smart card <b>18</b> using system <b>200</b>, funds issuer system <b>204</b> may operate to electronically withdraw the same dollar amount from a consumer checking account at the user's bank.
0047Issuer authentication system <b>206</b> allows an issuer to take liability for funds coming from funds issuer system <b>116</b> and any subsequent purchases made with the smart card. Fundamentally, system <b>206</b> is arranged to authenticate smart card <b>18</b> using a secret key and can generate a response that is then verified by card <b>18</b> before value is loaded onto the card.
0048Data communications network <b>208</b> provides secure communications between systems <b>204</b>/<b>206</b> and clearing and administration system <b>210</b>. Data communications network <b>208</b> may be any suitable communications network that allows secure communication between computers. For example, communication via media such as telephone lines, cable, fiber optic, microwave, satellite, etc., may be used. Existing networks using secure links such as ATM networks, the Internet or propriety networks may be used. In one embodiment of the invention, network <b>208</b> is implemented using VisaNet, an existing global clearing and settlement system provided by Visa International Service Association of Foster City, Calif.
0049Clearing and administration system <b>210</b> settles accounts between banks involving a cardholder's use of a smart card. In the case of a cardholder loading value onto a smart card, processing gateway <b>106</b> originates settlements for loading transactions. When a cardholder loads value onto a card, gateway <b>106</b> debits funds issuer system <b>204</b> and credits issuer authentication system <b>206</b>. System <b>206</b> then advises clearing and administration system <b>110</b> through data communications network <b>208</b> for audit and card balance maintenance. System <b>210</b> maintains a value for each card within transaction system <b>100</b> by keeping a database that includes an identifier for each card and the current value of the card. When the card is incremented or decremented in value, the card's value in the database is adjusted accordingly.
0050Once the cardholder uses the value on the card to purchase merchandise from a merchant, the card is decremented and the merchant submits a request to its bank (the acquiring bank) for payment. Clearing and administration system <b>210</b> then transfers a lump sum to the acquiring bank using a suitable settlement service to pay the various merchants having a relationship with the acquirer. Based upon previous collection data, the acquirer then transfers an appropriate amount of money to each merchant reflecting the value of the goods and/or services that that merchant had provided that day to cardholders based upon deductions from their smart cards. Clearing and administration system may be implemented in many ways. Well-known systems that may be used include the clearing and administration system used by Visa International Service Association of Foster City, Calif.
0051<figref idref="DRAWINGS">FIG. 5A</figref> illustrates a process flow <b>300</b> for the loading system of <figref idref="DRAWINGS">FIG. 4</figref>. Flow <b>300</b> describes one embodiment by which card <b>18</b> is loaded with value using GSM network <b>202</b>. In one embodiment, processing gateway <b>106</b> uses a different message format and protocol between the SIM and the authentication and funds issuer systems. For loading, communication between the SIM and processing gateway <b>106</b> may take place using a protocol as defined by Motorola, De la Rue and Logica plc in one particular implementation of specifications published by Visa International. Communication between the gateway and the issuer authentication and funds issuer systems preferably uses the Visa ISO 8583 message format.
0052In step <b>302</b> user turns on handset <b>102</b> which responds by presenting a main menu in step <b>304</b> via the SIM present within the handset. In step <b>306</b> the user requests that a load occur using the handset. In step <b>307</b> the handset prompts the cardholder to insert a smart card and the SIM issues a reset card instruction to the card to open the smart card application. The smart card responds in step <b>308</b> with an ATR (Answer to Reset) response indicating the application is open. In step <b>309</b> the SIM determines the funding account information, the amount of value already present in the stored value application, and the maximum value that may be loaded. This card data is returned to the handset in step <b>310</b>. In step <b>312</b> the user is prompted to enter the amount to be loaded. In step <b>314</b> the user enters an amount to be loaded. In one scenario, if a user desires to load more than the maximum amount or if a load would put the card's value over the maximum amount, the load request may be turned down.
0053The cardholder is next prompted to provide account information. The user's account number (from which the funds will be withdrawn) may be entered by the user at this point (in a home banking funding scenario) or the funding account number may be read off of the smart card. When read off of the smart card, the funding account number is taken from magnetic strip image (MSI) data stored onto the smart card. The user's account number may also be obtained by reading a separate application on the same smart card or by reading an application on a different smart card (as described below). Funding account information may also reside elsewhere as in a separate application in the SIM or on file at the telecommunications network.
0054In step <b>316</b> the user is also prompted to enter a code number (personal identification number) or password which is entered in step <b>318</b>. In step <b>320</b> the smart card issues a request for a random number from processing server <b>106</b>. This random number will be used to form a cryptographic signature within the card that can be used to authenticate the card. The random number is requested from the processing gateway for higher security. In step <b>321</b>, a suitable random number is returned to the SIM in the handset. In step <b>326</b> the SIM sends an Initialize For Load command to the card containing the random number which creates a cryptographic signature S<b>1</b> and returns it to the SIM.
0055Cryptographic signatures are generated during load and purchase operations to authenticate the entities involved or to confirm that operations have occurred. A cryptographic signature termed “S<b>1</b>” is used during a load operation and is typically generated by the smart card. A signature “S<b>2</b>” is used during a load or purchase operation and is generated by the issuer or a payment server. A signature “S<b>3</b>” is generated by the smart card on occurrence of a load or debit and is the final signature that confirms that the card has either loaded value onto, or debited value from, itself.
0056Cryptographic signatures are well-known in the art and may be created in any suitable manner. Preferably, signatures S<b>1</b>, S<b>2</b> and/or S<b>3</b> are created using a cryptographic key shared between the card and the issuer, data unique to the current transaction (including the random number), and data unique to the card. Preferably, the funding account number, card number, PIN or password, and all S1, S2 or S3 signatures are encrypted under 128-bit triple DES between the SIM and the processing gateway, and again with different 128-bit triple DES keys between processing gateway <b>106</b> and the issuer authentication and funds issuer systems.
0057In step <b>330</b> the SIM sends a Load Request (including signature S<b>1</b>) and a Funds Request (including PIN or password), collectively “load data,” to processing gateway <b>106</b>. The Load Request message may include a variety of information and preferably includes the card signature S<b>1</b>, the card number, an expiry date, and a load amount. Other information such as a security algorithm, transaction counter, current card balance, and smart card number are also preferably provided. All of this information is prepackaged into a single Load Request message. The Funds Request message preferably includes the amount of funds to be loaded, the funding account number and the PIN or password.
0058In step <b>332</b> the processing gateway sends the Funds Request to funds issuer system <b>204</b> which determines (using the funding account number and the amount to be withdrawn) whether or not the user's account has enough funds to load the amount desired onto smart card <b>18</b>. Verification of the PIN or password also occurs. If there are enough funds, in step <b>336</b> the funds issuer sends a Funds Response (which includes an approval code) back to processing gateway <b>106</b>. In step <b>334</b> the Load Request is sent from processing gateway <b>106</b> to issuer authentication system <b>206</b>. This Load Request is essentially an authentication request that contains signature S<b>1</b>. Authentication system <b>206</b> accepts the request, validates the card and S1 data, and responds with a Load Response (including an approval) and a cryptographic signature S<b>2</b> used for verification by the smart card in step <b>338</b>.
0059In step <b>340</b>, assuming steps <b>336</b> and <b>338</b> are approvals, the processing gateway receives the Funds Response and Load Response with S<b>2</b> and in turn, sends a single Approval Response with S<b>2</b> to the SIM in the handset. In step <b>342</b> the SIM sends the Approval Response with S<b>2</b> to card <b>18</b>. The smart card then validates signature S<b>2</b> and loads value onto the card corresponding to the requested amount. The card then generates a Load Confirmation message (including a Response Code) and a cryptographic completion signature S<b>3</b>. Signature S<b>3</b> serves as proof for irrepudiation purposes. In step <b>346</b> a shutdown is performed by closing the smart card application.
0060In step <b>348</b> a message is displayed to the user indicating that the load has been approved and the previous value on the card has been incremented to a new value. In step <b>350</b> the SIM sends the Response Code and signature S<b>3</b> to processing gateway <b>106</b> for logging and final validation. In step <b>352</b> the processing gateway issues a Settlement Funds Request to funds issuer <b>204</b> in order to commence debiting the cardholder account and transferring liability from the funds issuer for the authorized debit. In step <b>354</b> the processing gateway also issues a Settlement Load Request including the signature S<b>3</b> to authentication system <b>206</b> in order to commence crediting the issuer authentication system and transferring liability to the issuer authentication system for the authorized credit. In step <b>356</b> the funds issuer system issues a Settlement Funds Response to the <b>352</b> Funds Settlement Request that completes debiting the cardholder account and transferring liability from the funds issuer for the authorized debit. In step <b>358</b> the authentication system issues a Settlement Load Response that completes crediting the issuer authentication system and transferring liability to the issuer authentication system for the authorized credit.
0061Flow <b>300</b> illustrates how cryptographic signatures, S<b>1</b>, S<b>2</b> and S<b>3</b> are used to authenticate a smart card to an issuer authentication system. Other techniques for implementing process flow <b>300</b> may also be used. For a multi-application smart card that includes credit, debit and/or stored-value applications, it may be desirable to more securely authenticate the funds that are available. For example, it may be desirable to authenticate a smart card with funds issuer system <b>204</b>. In this embodiment, an authorization request certificate (ARQC) and an authentication response certificate (ARPC) allow the funds issuer to authenticate the card and vice-versa, with a final resulting transaction certificate (TC) produced by the smart card to serve for irrepudiation purposes. In this scenario, a credit or debit application on a multi-application smart card is being used as the source of funds and makes use of the ARQC, ARPC and TC in a similar manner as is served with the S1, S2 and S3 cryptographic signatures. Preferably, implementation of both the ARQC and ARPC is done with accordance the document Visa Integrated Circuit Card Specification referenced above.
0062In this scenario, the following steps would occur after step <b>318</b> and before step <b>320</b>, preferably. First, the stored-value application on the multi-application smart card is temporarily shut down in order to open up another application on the smart card such as the credit or debit application. The opened application creates a Funds Request including an ARQC cryptographic signature. The ARQC is a cryptogram that uses a key known only to the funds issuer, transaction data including a random number, the card number and the requested debit amount. The Funds Request and the ARQC are sent by the SIM to processing gateway <b>106</b> which passes them on to funds issuer <b>204</b>. Funds issuer <b>204</b> authenticates that the smart card and application are valid, and then formulates an authentication response certificate (ARPC).
0063The ARPC is a cryptogram that uses a key known only to the smart card application. It is created from the ARQC and transaction data including the response code. As part of a Funds Response message, the funds issuer includes the ARPC to the processing gateway <b>106</b> which passes it to the smart card via the SIM. Finally, the smart card validates the ARPC that authenticates that the funds issuer system approved the request message. At this point, the card may continue with the process of loading the dollar amount onto the card. Alternatively, as the approval from funds issuer <b>204</b> is independent of a load, the amount approved may also be applied toward a purchase or other use. Control would now return to step <b>320</b> of <figref idref="DRAWINGS">FIG. 5A</figref> for the stored value load.
Smart Card Purchasing System
0064<figref idref="DRAWINGS">FIG. 6</figref> illustrates a smart card purchasing system <b>400</b>. Purchasing system <b>400</b> separates a purchase transaction into local cardholder and remote merchant functions. Local cardholder functions include a smart card interface, a handset display and accept/cancel options. Remote merchant functions include validation of the transaction, communication with central systems and storing the transactions. GSM network <b>202</b> is a communications channel that links handset <b>102</b>, merchant server <b>410</b> and payment server <b>412</b>, via gateway <b>106</b>.
0065Various of the components of <figref idref="DRAWINGS">FIG. 6</figref> have previously been described in <figref idref="DRAWINGS">FIG. 4</figref>. In addition, merchant server <b>410</b> is any suitable computer that offers the user a product or a service over the GSM network to be displayed on handset <b>102</b>. Payment server <b>412</b> includes a merchant's computer hardware, physical terminal logic, a security card <b>418</b> and a modem. The terminal logic and security card <b>418</b> store transaction information and manage the security of the transaction by validating the integrity of the user's smart card <b>18</b>. Payment server <b>412</b> securely stores the transactions and manages the transmission of the transactions to a concentration point computer <b>420</b>. From the concentration point, the transactions are sent to a central clearing and administration system <b>210</b> for validation, clearing and settlement via data communications network <b>208</b>.
0066Processing gateway <b>106</b> acts as a router for processing purchase commands and instructions between card <b>18</b> and payment server <b>412</b> and between payment server <b>412</b> and merchant server <b>410</b>. Members <b>430</b> are various member banks and other financial institutions that act as acquirer or issuer within system <b>400</b>.
0067<figref idref="DRAWINGS">FIG. 7</figref> illustrates a process flow <b>500</b> for the purchasing system of <figref idref="DRAWINGS">FIG. 6</figref>. This flow describes one embodiment using the GSM network. Through process flow <b>500</b>, a user with a handset may order and pay for products and/or services via handset <b>102</b> using a smart card stored value application.
0068In one embodiment, processing gateway <b>106</b> uses a different message format and protocol between the SIM and the upstream systems. For purchase, communication between the SIM and processing gateway <b>106</b> may take place using a protocol as defined by Motorola, De la Rue and Logica plc in one particular implementation of specifications published by Visa International. Communication between the gateway and the upstream systems preferably is implemented as described in U.S. patent application Ser. Nos. 08/951,614 and 09/070,488 referenced above.
0069In step <b>502</b> a merchant solicits a user to purchase products and/or services by a solicitation message from merchant server <b>410</b> via gateway <b>106</b> and GSM network <b>202</b> to handset <b>102</b>. Alternatively, a user may use the handset and its menu to access merchant server <b>410</b> to view or list products and/or services for purchase. In step <b>504</b> the user uses the displays and keys of the handset to place an order for a product or service. In step <b>506</b> the handset sends the order request to processing gateway <b>106</b>. In step <b>508</b> the gateway sends the request to merchant server <b>410</b> along with a request for specific merchant data. This merchant data includes a merchant identifier and transaction identifier.
0070In step <b>510</b> the merchant transmits a wireless application protocol markup language (WML) page or other formatted message that includes the merchant data to gateway <b>106</b>. In step <b>512</b> the gateway formulates a purchase instruction that includes the item to be purchased, its amount, the merchant identifier and transaction identifier and sends the instruction to the SIM in the handset. In step <b>514</b> the SIM displays a confirmation screen to the user who in step <b>516</b> confirms the item and the amount for purchase. In step <b>518</b> the handset sends this confirmation on to the SIM. The handset then in step <b>520</b> sends an Initialize For Purchase message (that includes a reset command) to card <b>18</b>. In step <b>522</b> the card sends a Response To Initialize for Purchase message (which includes an ATR) back to the SIM.
0071In step <b>524</b> the SIM formulates a Draw Request including the card number, the amount and the merchant data. The Draw Request is then sent on to gateway <b>106</b>. In step <b>526</b> the Draw Request is sent to payment server <b>412</b> along with merchant data. Next in step <b>527</b>, the payment server processes the draw request in conjunction with associated security card <b>418</b> as will be explained in greater detail below.
0072The payment server then receives an OK to Debit command and a security card signature S<b>2</b> from the security card. The security card signature S<b>2</b> is a value that uniquely identifies and validates security card <b>418</b> to prove to card <b>18</b> that the incoming debit command is a valid command from a real security card. This validation ensures that when the smart card is debited the financial totals in the security card are updated. Thus, the user of the smart card is guaranteed that a valid debit of the card has occurred. In a preferred embodiment of the invention, signature S<b>2</b> is an encrypted value ensuring that no other entity can forge an identity of a security card.
0073In step <b>528</b> the payment server sends the OK to Debit command along with the signature S<b>2</b> to gateway <b>106</b>. Gateway <b>106</b>, in turn, sends OK to Debit and S<b>2</b> to card <b>18</b> in step <b>530</b> for the card to debit itself. Upon receiving the OK to Debit command and S<b>2</b>, card <b>18</b> verifies signature S<b>2</b>, debits itself by the purchase amount, and also generates a Debit Result message (presumed to be successful) and a card signature S<b>3</b>. The card signature S<b>3</b> is a unique value identifying a valid smart card. In a preferred embodiment of the invention, this signature is in encrypted form to prevent tampering. If the card does not have enough value to satisfy the purchase amount, then the Debit Result message indicates as such. In step <b>532</b>, card <b>18</b> sends the Debit Result message along with signature S<b>3</b> back to gateway <b>106</b>. At this point, the purchase amount has been deducted from the balance on card <b>18</b>. Next, in step <b>534</b>, the gateway sends Debit Result and S<b>3</b> to payment server <b>412</b>.
0074The payment server then directs this received message to security card <b>418</b>. The security card processes this message and verifies the received card signature S<b>3</b>. As the security card contains the keys and algorithms necessary to compute card signatures, the security card is able to validate that a received card signature is in fact a valid one by comparing this card signature with a generated expected value. A successful comparison indicates that a successful Debit Result message received from the card is in fact a valid success message and that the card has been debited. An error result code or a comparison that is not successful potentially indicates that the card has not been debited by the proper amount. This comparison of card signatures by the security card ensures that a smart card is in fact debited before merchant server <b>410</b> is directed to release the purchased merchandise. Assuming that the transaction is so far valid, the security card sends a Confirmation message back to the payment server which is relayed in step <b>536</b> to the gateway.
0075In step <b>538</b> gateway <b>106</b> passes the Confirmation message on to merchant server <b>410</b>. The merchant server registers this message and checks for success. The merchant server calls a validate routine with the Confirmation message to validate the message. The validate routine takes the transaction identifier along with the encrypted Confirmation message to decrypt the Confirmation message. If the decrypted Confirmation message is acceptable, the merchant server then determines that a successful transaction has occurred. The merchant server then delivers the purchased electronic information to handset <b>102</b>, or mails a product to the user. Alternatively, the merchant server may generate an electronic purchase receipt to deliver to the handset indicating goods and/or services to be rendered.
Computer System Embodiment
0076<figref idref="DRAWINGS">FIGS. 8 and 9</figref> illustrate a computer system <b>900</b> suitable for implementing embodiments of the present invention. <figref idref="DRAWINGS">FIG. 8</figref> shows one possible physical form of the computer system. Of course, the computer system may have many physical forms ranging from an integrated circuit, a printed circuit board and a small handheld device up to a huge super computer. Computer system <b>900</b> includes a monitor <b>902</b>, a display <b>904</b>, a housing <b>906</b>, a disk drive <b>908</b>, a keyboard <b>910</b> and a mouse <b>912</b>. Disk <b>914</b> is a computer-readable medium used to transfer data to and from computer system <b>900</b>.
0077<figref idref="DRAWINGS">FIG. 9</figref> is an example of a block diagram for computer system <b>900</b>. Attached to system bus <b>920</b> are a wide variety of subsystems. Processor(s) <b>922</b> (also referred to as central processing units, or CPUs) are coupled to storage devices including memory <b>924</b>. Memory <b>924</b> includes random access memory (RAM) and read-only memory (ROM). As is well known in the art, ROM acts to transfer data and instructions uni-directionally to the CPU and RAM is used typically to transfer data and instructions in a bi-directional manner. Both of these types of memories may include any suitable of the computer-readable media described below. A fixed disk <b>926</b> is also coupled bi-directionally to CPU <b>922</b>; it provides additional data storage capacity and may also include any of the computer-readable media described below. Fixed disk <b>926</b> may be used to store programs, data and the like and is typically a secondary storage medium (such as a hard disk) that is slower than primary storage. It will be appreciated that the information retained within fixed disk <b>926</b>, may, in appropriate cases, be incorporated in standard fashion as virtual memory in memory <b>924</b>. Removable disk <b>914</b> may take the form of any of the computer-readable media described below.
0078CPU <b>922</b> is also coupled to a variety of input/output devices such as display <b>904</b>, keyboard <b>910</b>, mouse <b>912</b> and speakers <b>930</b>. In general, an input/output device may be any of: video displays, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, biometrics readers, or other computers. CPU <b>922</b> optionally may be coupled to another computer or telecommunications network using network interface <b>940</b>. With such a network interface, it is contemplated that the CPU might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Furthermore, method embodiments of the present invention may execute solely upon CPU <b>922</b> or may execute over a network such as the Internet in conjunction with a remote CPU that shares a portion of the processing.
0079In addition, embodiments of the present invention further relate to computer storage products with a computer-readable medium that have computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and holographic devices; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs) and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher level code that are executed by a computer using an interpreter.
0080Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. Therefore, the described embodiments should be taken as illustrative and not restrictive, and the invention should not be limited to the details given herein but should be defined by the following claims and their full scope of equivalents.
Contents5
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10832246B2 | Cited by | United States of America | Applicant |
| US11062290B2 | Cited by | United States of America | Applicant |
| US2010131413A1 | Cited by | United States of America | Pre-grant |
| US2016080157A1 | Cited by | United States of America | Pre-grant |
| US10395223B2 | Cited by | United States of America | Applicant |
| US10395247B2 | Cited by | United States of America | Applicant |
| US11605077B2 | Cited by | United States of America | Applicant |
| US10970695B2 | Cited by | United States of America | Applicant |
| US10339522B2 | Cited by | United States of America | Applicant |
| US12499427B2 | Cited by | United States of America | Applicant |
| US2015019433A1 | Cited by | United States of America | Search report |
| US9734496B2 | Cited by | United States of America | Applicant |
| US11361290B2 | Cited by | United States of America | Applicant |
| US8054978B2 | Cited by | United States of America | Search report |
| US2010303230A1 | Cited by | United States of America | Pre-grant |
| US2011237224A1 | Cited by | United States of America | Pre-grant |
| US2012130901A1 | Cited by | United States of America | Pre-grant |
| US11144928B2 | Cited by | United States of America | Applicant |
| US10438175B2 | Cited by | United States of America | Applicant |
| US2011238580A1 | Cited by | United States of America | Pre-grant |
| CN108885652A | Cited by | China | Search report |
| US2015019433A1 | Cited by | United States of America | Pre-grant |
| US2012116965A1 | Cited by | United States of America | Pre-grant |
| US9838205B2 | Cited by | United States of America | Search report |
| US11386410B2 | Cited by | United States of America | Applicant |
| US10963856B2 | Cited by | United States of America | Applicant |
| US10762477B2 | Cited by | United States of America | Applicant |
| US8082211B2 | Cited by | United States of America | Applicant |
| US2008222695A1 | Cited by | United States of America | Pre-grant |
| WO2010138358A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US10318936B2 | Cited by | United States of America | Applicant |
| US10970688B2 | Cited by | United States of America | Applicant |
| US8650614B2 | Cited by | United States of America | Applicant |
| US9135424B2 | Cited by | United States of America | Applicant |
| US2007286373A1 | Cited by | United States of America | Pre-grant |
| US2011237223A1 | Cited by | United States of America | Pre-grant |
| US11321682B2 | Cited by | United States of America | Applicant |
| US2010306531A1 | Cited by | United States of America | Pre-grant |
| US10878387B2 | Cited by | United States of America | Applicant |
| US12299658B2 | Cited by | United States of America | Applicant |
| US12135775B2 | Cited by | United States of America | Applicant |
| US2015019433A1 | Cited by | United States of America | Search report |
| US11922387B2 | Cited by | United States of America | Applicant |
| US2010306076A1 | Cited by | United States of America | Pre-grant |
| US11151567B2 | Cited by | United States of America | Applicant |
| US11423134B2 | Cited by | United States of America | Applicant |
| US11373182B2 | Cited by | United States of America | Applicant |
| US2012048372A1 | Cited by | United States of America | Search report |
| US11948148B2 | Cited by | United States of America | Applicant |
| US10318944B2 | Cited by | United States of America | Search report |
| US10878404B2 | Cited by | United States of America | Search report |
| US2009030842A1 | Cited by | United States of America | Pre-grant |
| US11037121B2 | Cited by | United States of America | Applicant |
| US10120993B2 | Cited by | United States of America | Applicant |
| US10078821B2 | Cited by | United States of America | Applicant |
| US11151566B2 | Cited by | United States of America | Applicant |
| US2011237296A1 | Cited by | United States of America | Pre-grant |
| US9467292B2 | Cited by | United States of America | Applicant |
| US8417631B2 | Cited by | United States of America | Applicant |
| US2012108296A1 | Cited by | United States of America | Pre-grant |
| US10839359B2 | Cited by | United States of America | Applicant |
| US11151522B2 | Cited by | United States of America | Applicant |
| US11593800B2 | Cited by | United States of America | Applicant |
| US9112857B2 | Cited by | United States of America | Applicant |
| US11037122B2 | Cited by | United States of America | Applicant |
| US8588415B2 | Cited by | United States of America | Search report |
| US2011238579A1 | Cited by | United States of America | Pre-grant |
| US11715075B2 | Cited by | United States of America | Applicant |
| US2011117966A1 | Cited by | United States of America | Pre-grant |
| US2006089123A1 | Cited by | United States of America | Pre-grant |
| US8078532B2 | Cited by | United States of America | Applicant |
| US2012136797A1 | Cited by | United States of America | Pre-grant |
| US10748127B2 | Cited by | United States of America | Applicant |
| US11157884B2 | Cited by | United States of America | Applicant |
| US2010306819A1 | Cited by | United States of America | Pre-grant |
| US11151523B2 | Cited by | United States of America | Applicant |
| US8805746B2 | Cited by | United States of America | Search report |
| US10846662B2 | Cited by | United States of America | Applicant |
| US10769606B2 | Cited by | United States of America | Applicant |
| US11907918B2 | Cited by | United States of America | Search report |
| US2010306107A1 | Cited by | United States of America | Pre-grant |
| US10956888B2 | Cited by | United States of America | Applicant |
| US9454865B2 | Cited by | United States of America | Search report |
| US9544303B2 | Cited by | United States of America | Applicant |
| US11276093B2 | Cited by | United States of America | Applicant |
| US9516017B2 | Cited by | United States of America | Applicant |
| US2010235282A1 | Cited by | United States of America | Pre-grant |
| US2012166337A1 | Cited by | United States of America | Pre-grant |
| US2012296819A1 | Cited by | United States of America | Search report |
| US9020853B2 | Cited by | United States of America | Applicant |
| US2002112160A2 | Cites | United States of America | Pre-grant |
| US2002175207A1 | Cites | United States of America | Pre-grant |
| US5220501A | Cites | United States of America | Pre-grant |
| US5231569A | Cites | United States of America | Pre-grant |
| US5428684A | Cites | United States of America | Pre-grant |
| US5461217A | Cites | United States of America | Pre-grant |
| US5491693A | Cites | United States of America | Pre-grant |
| US5649118A | Cites | United States of America | Pre-grant |
| US5748737A | Cites | United States of America | Pre-grant |
| US5796832A | Cites | United States of America | Pre-grant |
22 members in 5 offices
Priority claims14
| Document | Office | Kind | Date |
|---|---|---|---|
| 14655999 | United States of America | P | |
| 14655999 | United States of America | P | |
| 15676599 | United States of America | P | |
| 15676599 | United States of America | P | |
| 58709200 | United States of America | A | |
| 58709200 | United States of America | A | |
| 24622808 | United States of America | A | |
| 09587092 | – | – | – |
| 60146559 | – | – | – |
| 60156765 | – | – | – |
| US19990146559P | – | – | – |
| US19990156765P | – | – | – |
| US20000587092 | – | – | – |
| US20080246228 | – | – | – |
Members22
| Document | Office | Kind | |
|---|---|---|---|
| CA2380529A1 | Canada | A1 | |
| WO0109851A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU6370200A | Australia | A | |
| EP1200942A1 | European Patent Office (EPO) | A1 | |
| AU777310B2 | Australia | B2 | |
| US2009030842A1 | United States of America | A1 | |
| US2009030843A1 | United States of America | A1 | |
| US2009030844A1 | United States of America | A1 | |
| US7729986B1 | United States of America | B1 | |
| US2010235282A1 | United States of America | A1 | |
| US8019684B2 | United States of America | B2 | |
| US8078532B2 | United States of America | B2 | |
| US8082211B2 | United States of America | B2 | |
| US2012136795A1 | United States of America | A1 | |
| US8417631B2 | United States of America | B2 | |
| US2013191288A1 | United States of America | A1 | |
| US8805746B2 | United States of America | B2 | |
| US2014310184A1 | United States of America | A1 | |
| US2014379583A1 | United States of America | A1 | |
| US9020853B2 | United States of America | B2 | |
| US9558489B2 | United States of America | B2 | |
| US10339522B2 | United States of America | B2 |
73 transactions on the USPTO file
Allowed after 1 non-final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Terminal Disclaimer FiledDIST | DIST | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
11 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Notice of allowance mailedORIGINAL CODE: MN/=.ZAAB | ZAAB | |
| Notice of allowance and fees dueORIGINAL CODE: NOAZAAA | ZAAA | |
| Notice of allowance mailedORIGINAL CODE: MN/=.ZAAB | ZAAB | |
| Notice of allowance and fees dueORIGINAL CODE: NOAZAAA | ZAAA |
Numbers
- Publication
- 20090030843
- Publication, DOCDB
- 2009030843
- Publication, EPODOC
- US2009030843
- Application
- 12246228
- Application, DOCDB
- 24622808
- Application, EPODOC
- US20080246228
Titles
- English
- SMART CARD LOAD AND PURCHASE TRANSACTIONS USING WIRELESS TELECOMMUNICATIONS NETWORK
Patent term adjustment
- A delay
- +78 daysthe office missed an examination deadline
- Applicant delay
- −91 days
- Net adjustment
- 0 days
Classification
- CPC, 21
- G06Q20/3674
- G06Q20/04
- G06Q20/10
- G06Q20/105
- G06Q20/28
- G06Q20/32
- G06Q20/322
- G06Q20/3255
- G06Q20/341
- G06Q20/353
- G06Q20/363
- G07F7/0866
- G07F7/0886
- G07F7/1008
- G06Q20/349
- G06Q20/3672
- G06Q2220/12
- G06Q20/36
- G06Q20/3229
- G06Q20/3829
- G06Q20/325
- IPC, 9
- H04L9 14
- G06Q20 04
- G06Q20 10
- G06Q20 28
- G06Q20 32
- G06Q20 34
- G06Q20 36
- G07F7 08
- G07F7 10
- USPC, 1
- 705067000