Patent Grant
10063714
This invention relates to stored-value card accounts. More particularly, the invention relates to adding stored value to a stored-value account as a result of a point-of-sale transaction. The stored value account may be managed by a third party. As described in the related applications, the data of the stored-value cards is related to services and/or products paid or prepaid by the owner or end user of the card. Each of the stored-value cards may be associated with a PIN.
Conventional stored value accounts are reloaded in a two-step process. First, the customer purchases a stored value card associated with a specific value, such as $20. Second, the customer accesses a central processor, e.g., by calling an 800 number on the back of the card, and requests to add the card's value to the customer's account. During the call, the customer typically provides card account information as well as information sufficient to identify the customer's account. For a mobile telephone service account, such identifying information may include the identify of the telecommunications service provider (such as AT&T) as well as the customer's mobile phone number.
This two-step process is time-consuming for the customer. In particular, contacting a central processor such as an IVR and navigating through all the prompts to provide all the necessary information can be especially time-consuming and/or difficult, especially for customers who do not speak the languages of the IVR system. For pay-as-you-go accounts, the burdensome IVR system may be navigated anew each time the customer adds value to the account. It is desirable to provide an improved system and method for iteratively adding value to a stored-value account.
A method of adding a value to a customer account is provided. A request to add a value to a customer account of a customer is received from a point of sale terminal. The request may comprise value identification data associated with the value and account identification data associated with the customer account. The customer account identification data may be entered at the point of sale. The request may be associated with a purchase of the value. The value may be caused to be added to the customer account. During subsequent value purchase transactions, additional value may be added to the account.
[Insert other independent claims in summary form here.]
The present invention can be more fully understood by reading the following detailed description together with the accompanying drawings, in which like reference indicators are used to designate like elements, and in which:
Before any embodiment of the invention is explained in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangements of components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced or being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting.
Many wireless telephone users and other recipients of goods and/or services utilize prepaid account arrangements that require payment before services will be provided. (It should be understood that prepaid wireless telephone service providers are used herein for exemplary purposes only. The invention relates to any customer account, such as an account provided by a provider of one or more goods or services (such as telecommunications service). Examples of prepaid services that may be accommodated by accounts include long distance telephone communication, wireless communication, paging and internet-enabled communication services, etc. For instance, prepaid telecommunications customers may pay as they go with the telecommunications carrier deducting payment for the services directly from the customer's account.
The invention, through a combination of technologies, provides a customer-friendly process that allows the customer to add value, i.e., money or usage credits, to an existing customer account from a point-of-sale (POS) device. The customer may purchase value at a merchant POS terminal or other terminal (such as an ATM). For instance, as in prior art methods, the customer may purchase a stored value card or a PIN associated with value, such as a $20 phone card. Alternatively, a customer may simply request to have a particular value added to a specific account. (It should be noted that the account may belong to the customer or another entity.) In either case, value purchase data and/or customer account identification data (such as phone number corresponding to a telecommunications account) may be provided, e.g., by entering it at the point of sale (e.g., a POS terminal). The value purchase data and customer account identification data may be passed from the POS terminal to a central processor. The central processor may identify the value and/or the customer account based on the received value purchase data and the customer account identification data. For instance, the central processor may identify the value based on a database that links the value identification data (e.g., a value identifier or card number) to a specific value. The central processor may then cause the identified value to be added to (or “inserted” into) the identified account. For instance, the central processor may send an automated and/or electronic request (e.g., via an API) to an account provider system to add the value to the identified customer account.
An advantage of this approach is that value may be added to a customer account via a single POS transaction. This saves time and hassle compared to prior systems, which typically required a POS transaction that activates the value followed by a subsequent phone call and IVR navigation to cause the account provider system to have the activated value added to a specific customer account.
In one aspect of the invention, a central system manages the process that allows the customer to add service value to the customer's account. The central system may maintain a set of identifiers, or Personal Identification Numbers (“PINs”), with each identifier having an associated service value, which preferably represents a monetary figure (i.e., number of dollars, $10, $25 or $50, for example), or some unit of service usage (i.e., minutes). Indicia associated with the identifiers are distributed to merchants for further distribution to customers. In one example, the indicia may be distributed on magnetic stripe cards having predetermined values, such as $10, $25 and $50 cards. It should be appreciated that each indicia, or article bearing indicia, is associated with only one identifier maintained at the central system. Thus, each card distributed is linked to only one identifier maintained at the central system.
Once the customer selects the indicia, or an article bearing the indicia, the customer provides payment for the service value associated with the identifier represented by the indicia. For example, the customer pays $25 for a $25 card associated with an identifier associated with a $25 service value (e.g., the identifier may be printed on the card, e.g., beneath a scratch-off adhesive to obscure it from view). The merchant sends a communication to the central system confirming the transaction with the customer so that the identifier at the central system can be activated. Customer account identification information may also be passed to the central system so that the central system may identify the target account to which the value will be added. For instance, the customer may enter the phone number corresponding to a telecommunications service account at a POS device, and the POS device may transmit this information to the central system.
When the identifier and customer account information are identified, the central system may communicate with the customer's account provider system to add the service value to the customer's account. The act of causing the value to be added to the customer's account is sometimes referred to herein as “value insertion” because value is being inserted into the customer's account. In some cases, the account provider system may be separate from the central system. In other cases, the central system may comprise a provider system that provides the customer account. In these cases, value may be inserted into the customer account without communicating with an external account provider.
Following the value insertion, the customer's updated account information may be obtained and provided to the customer. For instance, the value insertion process may occur within a very short timeframe (e.g., 0.1 to 10 seconds), and a confirmation that the value was added to the customer account may be passed back to the merchant (e.g., at the merchant POS terminal). Confirmation may be output to the customer, e.g., by printing a receipt or displaying a confirmation at the POS terminal.
As seen from some of the above examples, the central system may act as an intermediary between the customers, merchants and account providers. The central system may maintain arrangements with several carriers to allow for value insertion, and becomes a broker of prepaid communication services. The customer is benefited by having access to a resource that can be obtained at several points of sale and allows an easy method to replenish service value for a number of participating carriers. The carriers benefit by having a product in the marketplace whereby customers can more easily replenish customer account balances. Lastly, the merchants benefit from increased sales because they are selling a product that is in demand because it is a single product that allows customers have value added directly into their account from a POS device instead of a subsequent phone call with time-consuming and confusing IVR navigation.
In at least one implementation of the invention, the central system may manage at least one relational database of information while also allowing access by the various users of the central system (i.e., customers, merchants, and administrators), to the various features and interfaces of the invention. A relational database system may also allow information contained in different tables to be accessed and shared, while also providing the additional advantage that changes to data contained in one table of a relational database affects the same data in any other table sharing the same data. A table is a collection of several data records with similar data information fields. Data records represent a collection of data that is organized into fields. These fields may also be formatted to receive data of varying types. Accordingly, the central system, or a user of the system, can process, query or report data contained in the various data tables and records for use in accomplishing the features of the invention. In one aspect of the invention, the various databases could include the set of identifiers and Mobile Identification Numbers (“MINs”), for example.
Method for Supplying Communication Service Value
In accordance with one embodiment of the invention, an illustrative flowchart showing a method for supplying communication service is shown in
The process begins in step S1, and passes to step S20, which includes establishing a set of identifiers having associated service values. As described above, each identifier forms a part of a data record, or identifier record, that allows the central system to identify the specific associated service value that will later be sold to a customer. One example of an identifier is a Personal Identification Number (“PIN”). The PIN comprises one field of the identifier record, while another field in the same identifier record contains the associated service value. Illustratively, record X may have identifier ABC and an associated service value of $25. The service value is preferably a monetary figure (i.e., an amount in dollars, $10, $25 or $50, for example), but may also represent some unit of service usage, if supported by the carrier systems (i.e., minutes).
The set of identifiers forms the identifier database. Each identifier record may also contain fields for Status Indicator (i.e., whether the identifier is Active or Inactive), Serial Number, Visa Account Network Number (VAN), or a Merchant Code identifying the merchant through which the indicia will be distributed.
Following the establishment of the set of identifiers, in step S40, the process includes distributing indicia of the identifiers to merchants for distribution to customers. As described above, the indicia provides information related to the identifier for several reasons. First, the indicia allows the merchant to communicate to the central system the identifier that must be activated following distribution. Similarly, the information conveyed by the indicia later allows the customer to communicate to the central system the identifier and the service value purchased when the indicia was obtained from the merchant. It should be appreciated that the indicia may also encompass any article bearing such information. In other aspects, the indicia may provide instructions to the customer for communicating with the central system.
The indicia may comprise an article, such as magnetic stripe card, smart card, bar coded card, or any combination thereof. Either the magnetic stripe, chip or bar code would contain information that represents the card's identifier. Therefore, when completing the sale of the card to the customer, the merchant could swipe the card through a network terminal, or alternatively, scan the bar code on the card. The merchant's system would then locate the identifier and notify the central system of the sale of the article bearing the associated identifier.
To allow the customer to utilize the card upon purchase, the card also displays the identifier so that the customer can communicate the identifier to the central system. In addition, the card should display the service value associated with the identifier represented on the card to facilitate the customer's purchase of the correct card. Lastly, the card should contain instructions for communicating with the central system, i.e., a general toll-free number.
The indicia may also be provided to the customer through the delivery of a receipt or other notice. In such an embodiment, the customer would commence a purchase transaction at the point of sale, either through the merchant or a system device, such as a verifone terminal. The customer would request a certain prepaid service value, and upon payment, the central system would deliver the identifier to the point of sale for distribution to the customer.
Then, in step S60, the process includes activating an identifier upon distribution of indicia to a customer. As described above, the identifiers may be activated following communication from the merchants of the indicia distribution to the customers. This measure assists in avoiding the theft of the indicia prior to payment. The activation may include changing a status indicator associated with the specific identifier record from Inactive to Active. The communication between the merchant and central system preferably comprises a “host-to-host or Visanet connection”, but may include any network communication wherein the central system receives input from the merchant system confirming the transaction. Accordingly, the features of the present invention may use or be combined with any of the features described in U.S. application Ser. No. 09/641,363, filed Aug. 18, 2000, which is incorporated herein by reference in its entirety.
In step S80, a request from the customer for adding the service value associated with the identifier to a customer account may be received, e.g., by the central system. The request may occur during a transaction involving the distribution of the indicia to the customer. For instance, this may occur when a POS terminal transmits value data and/or customer identification data (such as a telephone number associated with a customer telecommunications service account) to the central system.
In some embodiments, communication with the central system may be achieved via any suitable communication interface, Ethernet connection, modem, telephone, digital or analog connections with the system using wireless communication devices (i.e., mobile phones, PDAs, or other handheld wireless communication devices), point of sale device or transceiver device (i.e., a verifone terminal, for example), token ring, Internet or Intranet or other computer connection, or any other suitable connection that allows the customer to receive input from and send output to the central system through the network connection.
As shown in
In step S106, the system may determine whether the input identifier correlates with an identifier from the set of identifiers maintained by the central system. The central system may compare the received value identifier (e.g., as received from a POS device and/or as provided by the customer (or other entity)) with those kept in the identifier database. If a record containing the PIN is found on the database, the process passes to step S108. If the identifier is found in the database, the system determines whether the identifier is active in step S108. The status of the identifier can be determined by relating a Status Indicator associated with the pertinent identifier record. Thus, when the central system finds the identifier record, it can determine whether a value in the Status Indicator field represents Active or Inactive status. If the identifier is found in the database and is active, the system determines whether the identifier has already been redeemed in step S110. This feature allows the central system to inform the customer that the identifier has already been redeemed. In some circumstances, the customer's communication session with the central system may be ended prematurely, before confirmation of the value insertion procedure. When this occurs, the customer may not be aware that the value insertion function was completed in the prior call. Thus, if the customer had previously called within a certain period (i.e., the last 24 hours), the central system can inform the customer that the value insertion was successful. If the identifier has not been redeemed, the process passes to step S116.
If the identifier cannot be found in the database in step S106, or the identifier is found in the database but is determined to be inactive in step S108, or the identifier is found in the database and is active, but is determined to have already been redeemed in step S110, the process passes to step S112. The system determines whether there has been a previous identifier check in step S112, and if so the process passes to step S114, where the customer is transferred to customer service. A previous identifier check would have occurred if the customer had previously supplied identifier input and the input failed any of the determinations in steps S106, S108 or S110. If there had not been a previous identifier check, the process returns to step S102, where the systems requests that the customer re-enter the identifier input.
For those identifiers found in the system that are active and have not been redeemed, in step S116 the system determines the associated service value for the identifier. The process then passes to step S119, wherein it returns to step S120.
As shown in
Thus, in some embodiments, the system may determine whether the customer MIN (or other account identifier) was captured and/or identified. For instance, it may be identified when customer identification information is passed to the central system in step S121. In some embodiments, wherein the customer contacts the system from a mobile phone (that has an account for which value is to be added), the account corresponding to the targeted account may be identified. For example, the customer's MIN can be captured utilizing Automatic Number Identification (“ANI”), or similar caller ID function. Through ANI, the central system acquires the customer's MIN from the ISDN transmission. Alternatively, the customer may supply his MIN upon request. This would allow the customer to confirm which MIN account the prepaid service value should be credited. In some embodiments, the account identification information may be identified without identifying the actual corresponding account.
It should be understood that a “MIN” is used for exemplary purposes only, and any other account identifier is contemplated herein, such as an account number, phone number, ESN, SMS address, home or work address, name, or other information from which an account may be identified (by using the account identification information alone or in combination with other information). For instance, the central system may identify a specific account from only a last name and a mailing address. In this example, the last name and mailing address may serve the purpose of “account identification information”.
If the customer's MIN has not already been captured, the process may pass to step S127. If the MIN has been captured, the process may pass to step S122, wherein the system may determine whether the customer's MIN can be found in the MIN database. The MIN database may comprise a compilation of existing MINs that includes each MIN, as well as an associated carrier. The MIN database may be stored locally in the central system, or maintained externally in a publicly accessible database, such as Telcordia®. This database may also include one created pursuant to the Wireless Local Number Portability Act. If the MIN is not found in the MIN database, the process passes to step S123. In situations when the MIN is not found in the MIN database, the customer may have contacted the central system using a non-wireless phone or other non-telephone connection, the system prompts the customer to enter the MIN that the customer wishes to add the service value. If the MIN is found in the MIN database, the process passes to step S125.
In step S123, the system determines whether the system has previously requested the customer's MIN from the customer. If so, the process passes to step S124, wherein the customer is transferred to customer service personnel. If the customer's MIN has not been previously requested, the process passes to step S127.
In step S125, the system determines whether the customer input his MIN. If so, the process passes to step S129. If not the customer did not input his MIN, the process passes to step S126, wherein the system determines whether the customer MIN has been confirmed. The confirmation includes input from the customer that the MIN identified is the correct account to add the service value. If the MIN is confirmed, the process passes to step S129.
Alternatively, if the customer MIN is not confirmed, the process passes to step S127, wherein the system requests that the customer provide input representing the customer's MIN for which the service value addition is requested. Then, in step S128, the system accepts the customer's MIN input before returning to step S121.
In step S129, the system determines the account provider (such as the carrier that provides a telecommunications account to the customer). The carrier can be determined by locating the MIN identified in the MIN database and relating the associated carrier. (It should be appreciated that while a “carrier” that provides telecommunications service accounts is being used as an example, any account provider is contemplated herein, such as toll service account providers, emergency road service account providers, Internet service account providers, stored value card account providers, and any other account provider.)
Once the carrier is determined, in step S130, the system may determine whether the customer ought to supply a carrier region code based on the customer's carrier. If not, the process may skip to step S138. If the carrier region code is required, the system may request the customer's carrier region code in step S132. The carrier region code may be required for carriers that have regional centers that maintain data on the local mobile phone customers. The carrier region code may be represented by the customer's zip code.
In step S133, the system may accept the customer's carrier region code, and the process may pass to the step S134. The system may determine whether the carrier region code is valid in step S134. The code may be presumed valid if it can be related to a region code maintained in a carrier specific region code database. If the code is simply the customer's zip code, the system can determine the appropriate carrier region by referring to the carrier database. If the code is not valid, the process returns to step S132, wherein the system requests reentry of the region code. If the code is valid, the process passes to step S135, wherein the system sets an association between the customer's MIN and the carrier region code, to avoid later requests of the code upon subsequent interactions. The process then passes to step S138, wherein it returns to step S139.
After receiving the customer's request, in step S140, the process may include adding the associated service value to the customer account.
However, if in step S146, the system determines that the add value request was not approved, the process passes to step S147, wherein the system obtains the reasons from the carrier system that the value insertion was not approved. The process then passes to step S152, wherein the system ends the communication session with the carrier system. The process then passes to step S159, wherein it returns to step S160.
For those carriers that do not support direct value insertion, in step S142, the system provides the customer with an alternate carrier identifier. This carrier identifier operates similarly to the identifier used with the central system, however, the carrier identifier must be redeemed through communication with the carrier system. These carrier identifiers may be maintained in a separate carrier identifier database. Accordingly, in step S143, the system transfers the customer to an IVR system managed by the carrier system to complete the value redemption.
Returning to
It should be appreciated that the methods described herein may be adapted such that each indicia of an identifier distributed may not have a predetermined associated service value. In this respect, the indicia would include the identifier, however, the customer would be allowed to select a service value to purchase for the card. Therefore, upon distribution of the card, the customer would select a service value, such as $25, for insertion into the record at the central system. The communication from the merchant would notify the central system of the amount purchased, which would then be inserted into the associated service value field for the record.
An Illustrative Communication Service Value System
As described above,
The central system 10 may comprise a processor portion 12 for processing input from and generating output to the various customer, merchant and carrier systems in communication with the central system 10, a memory portion 14, the processor portion 12 retrieving data from and storing data for use by the central system 10 in the memory portion 14, and a user interface portion 16 accepting input from and transmitting output to the various customer, merchant and carrier systems in communication with the central system 10. Each of processor portion 12, memory portion 14 and user interface portion 16 are connected to and in communication with each other through a data bus 11.
The processor portion 12 monitors and controls the various operations of the central system 10. Initially, the processor portion 12 processes the information provided by the merchant system 40 when confirming the indicia distribution and the customer system 20 when accessing, or making requests of, the central system 10.
The memory portion 14 serves as a memory store for a wide variety of data used by the processor portion 12, as well as the other components of the central system 10. For example, in one embodiment, the memory portion 14 contains the various databases of identifiers and associated service values, MINs, carriers, and other information needed by the central system. It should be appreciated that the various memory components contained in the memory portion 14 may take on a variety of architectures as is necessary or desired by the particular operating circumstances. Further, the various memory components of the memory portion 14 may exchange data or utilize other memory component data utilizing known techniques such as relational database techniques.
The user interface portion 16 provides the interface through which the user can provide input to and receive output from the central system 10. The user interface portion 16 generally provides interaction capabilities for communicating with the customer, merchant and carrier systems. The user interface portion 16 is controlled by the processor portion 12, or components thereof, to interface with a customer or other operating system, including inputting and outputting data or information relating to the central system 10. The user interface portion 16 also provides the interface between the system administrator, the central system 10, and other remote systems. A system administrator mainly utilizes the user interface portion 16 to manage the storage of data and information in the memory portion 14, as well as provide updates to the central system 10 applications and functions.
In operation, a customer utilizing a suitable customer system 20 accesses the central system 10 through customer network 19. The customer system 20 may be any suitable processing machine, such as a mobile phone, as well as a computer accessing the Internet, personal digital assistants (PDAs) or other wireless communication device, networked to customer network 19. The merchant system 40 may be any suitable processing machine, including a transceiver device (i.e., a verifone terminal, for example) capable of receiving input from the central system, printing indicia or other information, performing smart card or magnetic stripe card reader or bar code scanner functions, and sending output to the central system 10. Accordingly, in one embodiment of the invention, to activate an identifier upon payment, the card is swiped through an appropriate card interface on the merchant transceiver, which initiates a network connection to the central system 10, wherein the central system 10 activates the identifier in the appropriate database.
The user interface portion 16 also transmits data to the customer system 20 to present a user interface on the customer system 20 for accepting input and allowing the customer to submit output to the central system 10. Although these user interfaces have been described with respect to a some interfaces, alternate user interfaces may be presented on an Internet web page whereby customers access the page and provide the necessary redemption information on an appropriate form.
Although several customer systems and vendor systems are shown in
The user interface portion 16 accepts the customer request for value insertion from the customer system 20, including the identifier input and customer account input. The processor portion 12 verifies the identifier input with the identifier database maintained in the memory portion 14, and then verifies the customer account input with the MIN database, either maintained locally in the memory portion 14 or externally in a publicly available database of MINs. The user interface portion 16 then communicates with a carrier system 60 to complete the value insertion process before providing the customer with a customer account summary.
It should also be appreciated that the invention may include a device for distributing communication service value. Such a device may include a distribution terminal (i.e., a verifone terminal-like device or a vending machine-like apparatus) that allows a customer to select a prepaid service value for purchase, and make payment for the service value. The terminal would include a product selection portion for presenting the various service value denominations available (i.e., any user interface for accepting the customer's selection, for example), a payment portion for receiving payment from the customer (i.e., through cash, or magnetic stripe card or smart card readers, for example), a communication portion for notifying the central system of the sale of the indicia and the need to activate the associated identifier (i.e., a modem, for example), and a delivery portion for providing the customer with the indicia of the identifier (i.e., a mechanical card delivery system or printer means to provide a printout of the indicia, for example).
As described above,
As noted above, the processing machine executes the instructions that are stored in the memory or memories to process data. This processing of data may be in response to commands by a user or users of the processing machine, in response to previous processing, in response to a request by another processing machine and/or any other input, for example.
As noted above, the processing machine used to implement the invention may be a general purpose computer. However, the processing machine described above may also utilize any of a wide variety of other technologies including a special purpose computer, a computer system including a microcomputer, mini-computer or mainframe for example, a programmed microprocessor, a micro-controller, a peripheral integrated circuit element, a CSIC (Customer Specific Integrated Circuit) or ASIC (Application Specific Integrated Circuit) or other integrated circuit, a logic circuit, a digital signal processor, a programmable logic device such as a FPGA, PLD, PLA or PAL, or any other device or arrangement of devices that is capable of implementing the steps of the process of the invention.
It is appreciated that in order to practice the method of the invention as described above, it is not necessary that the processors and/or the memories of the processing machine be physically located in the same geographical place. That is, each of the processors and the memories used in the invention may be located in geographically distinct locations and connected so as to communicate in any suitable manner. Additionally, it is appreciated that each of the processor and/or the memory may be composed of different physical pieces of equipment. Accordingly, it is not necessary that the processor be one single piece of equipment in one location and that the memory be another single piece of equipment in another location. That is, it is contemplated that the processor may be two pieces of equipment in two different physical locations. The two distinct pieces of equipment may be connected in any suitable manner. Additionally, the memory may include two or more portions of memory in two or more physical locations.
To explain further, processing as described above is performed by various components and various memories. However, it is appreciated that the processing performed by two distinct components as described above may, in accordance with a further embodiment of the invention, be performed by a single component. Further, the processing performed by one distinct component as described above may be performed by two distinct components. In a similar manner, the memory storage performed by two distinct memory portions as described above may, in accordance with a further embodiment of the invention, be performed by a single memory portion. Further, the memory storage performed by one distinct memory portion as described above may be performed by two memory portions.
Further, various technologies may be used to provide communication between the various processors and/or memories, as well as to allow the processors and/or the memories of the invention to communicate with any other entity; i.e., so as to obtain further instructions or to access and use remote memory stores, for example. Such technologies used to provide such communication might include a network, a dedicated circuit, IP based connection, the Internet, Intranet, Extranet, LAN, WAN, VPN, an Ethernet, or any client server system that provides communication, for example. Such communications technologies may use any suitable protocol such as TCP/IP, UDP, OSI, SNA, X.25, ISO 85/83, XML or SOAP, for example.
As described above, a set of instructions is used in the processing of the invention. The set of instructions may be in the form of a program or software. The software may be in the form of system software or application software, for example. The software might also be in the form of a collection of separate programs, a program module within a larger program, or a portion of a program module, for example The software used might also include modular programming in the form of object oriented programming. The software tells the processing machine what to do with the data being processed.
Further, it is appreciated that the instructions or set of instructions used in the implementation and operation of the invention may be in a suitable form such that the processing machine may read the instructions. For example, the instructions that form a program may be in the form of a suitable programming language, which is converted to machine language or object code to allow the processor or processors to read the instructions. That is, written lines of programming code or source code, in a particular programming language, are converted to machine language using a compiler, assembler or interpreter. The machine language is binary coded machine instructions that are specific to a particular type of processing machine, i.e., to a particular type of computer, for example. The computer understands the machine language.
Any suitable programming language may be used in accordance with the various embodiments of the invention. Illustratively, the programming language used may include assembly language, Ada, APL, Basic, C, C++, COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX, Visual Basic, and/or JavaScript, for example. Further, it is not necessary that a single type of instructions or single programming language be utilized in conjunction with the operation of the system and method of the invention. Rather, any number of different programming languages may be utilized as is necessary or desirable.
Also, the instructions and/or data used in the practice of the invention may utilize any compression or encryption technique or algorithm, as may be desired. An encryption module might be used to encrypt data. Further, files or other data may be decrypted using a suitable decryption module, for example.
As described above, the invention may illustratively be embodied in the form of a processing machine, including a computer or computer system, for example, that includes at least one memory. It is to be appreciated that the set of instructions, i.e., the software for example, that enables the computer operating system to perform the operations described above may be contained on any of a wide variety of media or medium, as desired. Further, the data that is processed by the set of instructions might also be contained on any of a wide variety of media or medium. That is, the particular medium, i.e., the memory in the processing machine, utilized to hold the set of instructions and/or the data used in the invention may take on any of a variety of physical forms or transmissions, for example. Illustratively, the medium may be in the form of paper, paper transparencies, a compact disk, a DVD, an integrated circuit, a hard disk, a floppy disk, an optical disk, a magnetic tape, a RAM, a ROM, a PROM, a EPROM, a wire, a cable, a fiber, communications channel, a satellite transmissions or other remote transmission, as well as any other medium or source of data that may be read by the processors of the invention.
Further, the memory or memories used in the processing machine that implements the invention may be in any of a wide variety of forms to allow the memory to hold instructions, data, or other information, as is desired. Thus, the memory might be in the form of a database to hold data. The database might use any desired arrangement of files such as a flat file arrangement or a relational database arrangement, for example.
In the system and method of the invention, a variety of “user interfaces” may be utilized to allow a user to interface with the processing machine or machines that are used to implement the invention. As used herein, a user interface includes any hardware, software, or combination of hardware and software used by the processing machine that allows a user to interact with the processing machine. A user interface may comprise a series of Interactive Voice Responses, or take the form of a dialogue screen, for example. A user interface may be in the form of a web page or other interactive application presented on a customer system by the customer's browser. The web page or application could include fields for accepting data and transmitting data to the advertising marketing system for storage. A user interface may also include any of a mouse, touch screen, keyboard, keypad, card slot, voice reader, voice recognizer, dialogue screen, menu box, list, checkbox, toggle switch, a pushbutton or any other device that allows a user to receive information regarding the operation of the processing machine as it processes a set of instructions and/or provide the processing machine with information. Accordingly, the user interface is any device that provides communication between a user and a processing machine. The information provided by the user to the processing machine through the user interface may be in the form of a command, a selection of data, or some other input, for example.
As discussed above, a user interface is utilized by the processing machine that performs a set of instructions such that the processing machine processes data for a user. The user interface is typically used by the processing machine for interacting with a user either to convey information or receive information from the user. However, it should be appreciated that in accordance with some embodiments of the system and method of the invention, it is not necessary that a human user actually interact with a user interface used by the processing machine of the invention. Rather, it is contemplated that the user interface of the invention might interact, i.e., convey and receive information, with another processing machine, rather than a human user. Accordingly, the other processing machine might be characterized as a user. Further, it is contemplated that a user interface utilized in the system and method of the invention may interact partially with another processing machine or processing machines, while also interacting partially with a human user.
Thus, as shown in
In step 1001, the customer selects a card. The customer may select the card from among a plurality of different cards. The cards may be associated with different values and different providers. The cards are associated with one or more prepaid services, such as wireless telecommunications service. For instance, the customer may select a card enabling $40 of wireless telephone service with a particular provider.
In a preferred embodiment, the card has an associated PIN, serial number (in the form of a barcode or a magnetically stored number), and a card number.
The PIN or other numbers may be hidden on the card so that they are not visible until after purchase. For instance, the PIN may have material covering and hiding it, wherein the material may be scratched off with a coin after purchase. Alternately, an opaque adhesive tape may be used to temporarily prevent viewing the PIN until after purchase. These and other methods for securing valuable card information are well-known in the art.
The PIN may be a unique identifier, such as a randomly generated number that is unique to the specific card. The associated barcode number may also be printed on the card so that it can be scanned (or swiped) at a merchant terminal at the point of sale. The use of barcodes and magnetic stripes are well-known in the art. The card number may be another number associated with the card for other purposes. For instance, it may be a provider routing number. It may also be a number printed on the card in accordance with governmental guidelines or other norms.
The card information, such as the PIN number, associated barcode and/or magnetically stored serial number, value, and card number may be stored in a database at the central processor. These numbers may be associated together in a single entry for a single stored-value card. By associating them together in a single entry, the central processor may later determine the other associated numbers after receiving a single number, such as the PIN.
These numbers and other indicia may be printed on the card. For instance, the name of the service provider and the value of the card may be printed on the card. The card may also show activation information instructing the customer how to activate the card. Redemption information may comprise a 1-800 number (or other 8xxx number or other phone number), an IVR input code or series of inputs, a website, and/or other information or instructions for accessing a central system and/or redeeming the card or otherwise modifying a customer account. The redemption instruction information may be printed on the card, or it may be printed on a receipt and provided to the customer upon purchase of the card.
Different instructions may be associated with different cards. For instance, cards associated with one service provider may have different instructions, such as a different 1-800 number, than a card associated with a different service provider. Different 1-800 numbers, websites, or inputs enable the central processor to distinguish the identity of the provider or other feature of the card based on the method used to access the central system.
In step 1002, the customer purchases the card. The merchant (or customer) scans the card's barcode, swipes the card's magnetic strip, and/or otherwise inputs card information at a terminal, such as a merchant terminal. If the card is not pre-associated with a specific value, the customer may specify a particular value which may then be input at the terminal. This defined value would then become the card's associated value, unless and until the associated value were later changed by the customer, merchant, central processor, or provider.
The merchant terminal transmits this card information to the central processor. The merchant terminal may include other information in the transmission, such as merchant or terminal identification information, other indicia information on the card, or customer information such as name and account number. This transmission may be either a request to activate the card or a request to preauthorize the card (which may then follow with a related authorization request). A preauthorization request may merely query the central processor whether the card is a valid card that is ready to be activated.
In step 1003, the central processor receives information from the merchant terminal. This information may comprise card information and customer account information, such as a customer phone number. For instance, a terminal may read card information from the card and send the card information to a central processor. Customer account information may also be input at the terminal. For instance, the phone number may be entered into a POS terminal, and the phone number may be passed to a central processor (e.g., in the same or separate communication as passing the card information to the same central processor).
This information may comprise any information input at the terminal as well as any additional information passed from the terminal. In a preferred embodiment, the received information comprises the card's barcode or magnetic strip information. The central processor accesses the database entry corresponding to the card. It may check the status of the card. For instance, it may check whether the card is a valid card that is ready to be activated. It may also verify whether the card has been lost or stolen, or whether there is a database entry corresponding to the card information. It may also check whether the card is associated with the merchant or requesting terminal; for instance, it may check received terminal information against terminal information stored in the card's entry in the database. In a preferred embodiment, the central processor verifies that the terminal is an authorized terminal, such as a trusted source, for making stored-value card requests (or that the communication network used to make the request is a trusted communication network). For instance, if the merchant transmits a merchant identifier along with the card information, the central processor may verify that the merchant identifier is associated with the card information in the database. At this point, the central processor may send a pre-authorization back to the merchant terminal.
At this point, the central processor may preauthorize the card if the transmission from the merchant terminal was a preauthorization request. For instance, the central processor may preauthorize a card that is valid and ready to be issued. It may also make an amendment to the entry to indicate that the card has been preauthorized by a particular terminal. The preauthorization may be passed from the central processor to the merchant terminal. At this point, the card has not been purchased.
The merchant terminal may then receive the preauthorization and allow the customer to proceed with the purchase. For instance, the merchant terminal may collect funds from the customer, e.g., in a credit card or cash transaction. Before, during, or after this time (such as when the customer's funds have cleared or after), the merchant terminal may then send an authorization/activation request to the central processor. The central processor may receive the authorization request, which may include card information and merchant or terminal information (as described herein), and process the information.
The central processor may then amend the stored-value card entry corresponding to the received card information. The central processor may then activate and/or register the card. For example, the central processor may amend the entry to show that the card has been registered and/or activated. By activating and/or registering the card, the central processor acknowledges that the card has been properly purchased at a merchant terminal. When the customer later attempts to redeem the card and/or add value to a customer account (or otherwise amend a customer account), the central processor may deny the request if the card has not been validly issued or activated. This prevents theft of the cards, because a stolen card cannot be activated. The central processor may send a transaction confirmation to the merchant terminal, which may pass a confirmation to the customer. In some cases, the authorization will occur long after the preauthorization (such as after a check clears), so a confirmation will not be passed to the customer.
If a PIN is not pre-printed on the card, the central processor may also transmit a PIN to the merchant terminal upon activation of the card. The merchant terminal may then distribute the PIN to the customer, such as on a printed receipt. The central processor would then associate the PIN with the card, for example by storing the PIN in the card entry (or vice versa).
A preauthorization step is advantageous for theft and loss prevention. Without a preauthorization step, it was possible to redeem a card before paying for it. For instance, the card could be redeemed during the delay between when the card is processed (e.g., scanned and activated) and when the card is paid for (either by the merchant or by the customer). The delay may comprise the time it takes for a credit card or check to be processed, or it may comprise the time at the checkout counter between when the card is scanned and the time the customer is actually charged. However, only an activated/authorized card can be redeemed, not a preauthorized card. By doing a preauthorization at the time of scanning (or otherwise inputting card information at the merchant terminal), users cannot exploit this delay for illicit purposes. Then, when the card is activated, the funds may already be transferred, so the customer may not redeem value that has not been properly purchased.
It should be appreciated that steps 1002 and 1003 may involve back-and-forth communication between the merchant terminal and the central processor, including preauthorization and authorization/activation requests and responses.
In step 1004, the customer accesses the central processor system. For instance, the customer may access the central processor to request to redeem the associated value. The central processor may comprise an IVR phone system or a central website associated with the central processor. The central processor system may also comprise any other means for communication between a customer and a central system known in the art. For purposes of the description herein, the central IVR and central website may be considered part of the general central processor system, along with the central processor database.
In optional step 1005, the central system prompts the customer for information. The prompt may be a prompt at a POS terminal. The prompt may also be at a customer's mobile phone (e.g., wherein the mobile phone has a mobile phone number already provided by the customer and/or on record with the central system). In some embodiments, the prompt may comprise instructions on a website, such as an input field on a website. The prompt may comprise any query by the central processor requesting information from the customer, such as a request to verify account identification information. The prompt may ask for any information associated with the card (e.g., a purchased card having associated value), the service, or the customer, such as the PIN, associated value, and customer name, phone number or account number. For instance, the customer may be prompted for the identity of the provider. This and other information may also be automatically determined as described herein.
In step 1006, the information is provided to the central system, such as by passing information from the merchant (e.g., the merchant terminal) to the central system (e.g., in response to the prompts). In a preferred embodiment, the customer may enter the card's PIN number and/or the customer's account number or phone number at a POS device, and this information may be passed from the POS device to the central processor.
In step 1007, the central processor may identify the service provider associated with the customer account and the customer account number. The central processor may also identify other information such as the serial number, other card indicia, value, customer name, address, social security number, or other customer or account information. This information may be identified based on customer input.
Some of the information may be automatically determined by the central system. This information therefore does not require prompts or customer input. For wireless telecommunication service, the account number may be the customer's mobile phone number or mobile identification number (MIN). Identification information such as a MIN may be ascertained by automatic number identification (ANI). For instance, if the customer calls an 800 number from the customer's wireless telephone, the central system may identify the account associated with the wireless telephone number. For telephone long distance service, the central system may similarly identify an account associated with the telephone number. (It should be noted that ANI may be used to identify a merchant and/or merchant terminal if the merchant terminal sends information to the central system via phone. For instance, a database linked to the central processor may store a table or other database that associates different merchant phone numbers (or terminal phone numbers) with specific merchants. In this way, a merchant may be identified.
The identity of the provider may also be determined automatically. For instance, as described above, the provider may be identified by the manner in which the customer accesses the central system. For instance, a particular 1-800 number (or similar number) may be associated with a particular provider. Thus, when the central system receives a call from a customer at that number, it may automatically determine that a customer's account must be associated with the particular provider.
The information received and identified by the central processor may be stored in a database, such as in the database entry for the associated card, where the different items of information are associated together. One piece of identifying information associated with the card may enable the central processor to identify other associated card or account information stored in the database entry.
It should be understood that steps 1005-1007 may involve back-and-forth communication between the customer and central system, and they may therefore overlap and occur over the same time period.
In step 1008, the central processor inserts value information into the provider's system. If the customer's account can be modified directly by the central system, then the central system amends the customer's account and adds the value. For instance, the central processor may be the provider or an affiliate of the provider and accordingly have managerial control over the accounts. In this case, it may add value to the accounts directly.
It may also store amended account information, account history information, and other account information according to well-known methods in the art.
If the customer's account cannot be modified directly by the central system, then the central processor may “insert value” by passing value insertion information to the provider's system to enable the provider's system to process the customer's request to add value. In a preferred embodiment, this information comprises the customer account and the associated value. For example, the information may instruct the provider to add a certain amount (the associated value) to a specific account (the customer's account).
In order to pass the information to the provider, the central processor may access a database of the provider, wherein the provider database stores stored-value account information for user accounts associated with the provider, such as wireless service accounts. The central processor may also access the provider's website or other computer interface.
In one embodiment, the central processor uses an internet protocol and/or file transfer protocol to transfer stored-value card and/or PIN data of the user. For instance, the central processor may send an xml request to the provider's computer platform. Alternately, the request may be via email, ftp, or other means. The request may conform to the provider's application programming interface (API) or other formatting requirements. The request may comprise accessing a provider's IVR system or website and/or inputting information at prompts from the provider system. The processor may make any appropriate inputs to add value to a customer's stored-value account. The central processor may pass PIN and/or other account-related information to the provider (and/or its database), such as a PIN, user name, address, account number, wireless telephone number, password, or other information. For instance, the central processor may instruct the provider to add a certain amount to a user's stored-value account. This may occur during the same time frame as the original value insertion request from a POS terminal.
In step 1009, the provider adds the associated value to the customer account. This step is not necessary if value has already been added to the customer account in step 1008, such as if the central system manages the customer's account directly.
The third-party provider may first receive information from the central processor passed in step 1008. To add value, the provider may amend its customer account records (such as those stored in a database) to reflect the passed information, such as an increased value in a customer account. The provider may also send a transaction confirmation to the central processor via similar communication means, such as via xml. The confirmation may confirm that the PIN-related transaction was (or was not) completed successfully.
After value is added to (or inserted into) the account, the processor and/or provider may provide a transaction confirmation to the customer. The confirmation may comprise a positive or negative response, a new account balance, or other account- or card-related information. A negative response may result when the carrier doesn't recognize the account, the customer's account has been deactivated, the account has been suspended, or when other negative or questionable circumstances are present.
In step 1010, the customer uses the same stored-value card in a subsequent transaction. For instance, the card may be scanned or swiped at a second merchant terminal, and it may proceed in a manner similar to step 1002. I.e., the merchant may input card information and transmit information to the central processor. This terminal may or may not be the same as the first terminal, and it may be located at a different merchant's store.
Alternately, the central processor may receive card information over the internet, email, phone, POS terminal, or other communication means. For instance, a customer may log onto a website associated with the central processor and input card information, such as the card number or PIN. The customer may use any means for communicating with central processor, including a phone, PDA, computer, or other means.
In one embodiment, a different associated value may be specified for each subsequent transaction. For instance, a customer may enter the value at an input field on a website, or the merchant may input the new value into the merchant terminal before or after inputting the card information.
In another embodiment, a different provider may also be specified (e.g., by the customer) for each transaction.
In step 1011, the central processor receives card information. Based on this information, the central processor may automatically “recharge” the card by causing the associated value into the customer's account.
This may occur in a manner similar to step 1003. The information may be received pursuant to a second request to activate the card or to otherwise process card information. The second request may be from a second merchant terminal, which may be associated with a different merchant. The second request may also be from the same merchant terminal. The request may also be from a any source that may communicate with the central processor, such as a computer, PDA, telephone or other device.
The central processor may then determine whether an account number and provider have been previously identified for the card associated with the received card information. For instance, the processor may access the card's record in the database and determine whether the entry includes an identified provider and account number. Because this account has already registered/activated above, and because the account and card information have already been stored, the central processor recognizes that this is an active card. For instance, the central processor may receive the barcode serial number or other identifier from the merchant terminal, and it may access the appropriate database entry and determine that the account is activated.
Here, the account is already associated with a provider and account number (and value, in a preferred embodiment) because the central processor has already identified and stored such information during a prior transaction. There is no need for the extra step of 1006, wherein the customer accesses the central system directly to make a redemption request. Thus, the central processor automatically inserts the value into the customer's account, as described above for step 1008.
In some embodiments, value identification information and account identification information may be passed to the central processor during the recharge request. The value insertion process may then continue as described elsewhere herein.
Step 1011 describes the process when a previously-processed card is used for a subsequent transaction. If a card has never been used for a transaction (and consequently the provider and account number have never been identified), the process would begin from step 1001. It should be noted that each time card information is transmitted from a merchant terminal (or other source) to the central processor, the processor may check to determine whether the card is already associated with an account number and provider. If it has been, the processor may automatically complete the transaction, such as by passing a request to add value to the provider or otherwise adding or inserting value into the customer's account.
In step 1012, the central processor optionally sends a confirmation to the merchant terminal, and the merchant terminal provides the confirmation to the customer.
Additional activation requests may be made for the card. For instance, after purchasing a card from a merchant terminal and activating the card, the customer may recharge the value of the card any number of times at any number of merchant terminals, including the same merchant terminal(s). The customer may also recharge the card via the internet or telephone. The customer may also specify various parameters during recharge, such as a new associated value, new provider, and new PIN (or other identifier).
It should be appreciated that the central processor may be a computer system of a provider, or it may be a separate system. For instance, the central processor may itself be a wireless carrier's computer system, wherein the carrier provides and redeems wireless PINs for customers. Alternately, it may be a system that is not directly affiliated with any wireless carrier, in which case it may merely serve as a centralized system.
The central processor may offer special deals and promotions to customers based on this information. For instance, the central processor may make offers or give awards or advantages to customers based on the number (or value, or total value) of cards or PINs they purchase and/or process.
It should be understood that a service provider may be any provider of any product and/or service. It should also be understood that the service may be any product or service.
It will be understood that the specific embodiments of the invention shown and described herein is exemplary only. Numerous variations, changes, substitutions and equivalents will now occur to those skilled in the art without departing from the spirit and scope of the present invention. Accordingly, it is intended that all subject matter described herein and shown in the accompanying drawings be regarded as illustrative only and not in a limiting sense and that the scope of the invention be solely determined by the appended claims.
This application is a continuation of U.S. application Ser. No. 12/607,141, filed on Oct. 28, 2009, which is a continuation of U.S. Continuation-in-Part patent application Ser. No. 11/290,606, filed on Dec. 1, 2005 (now U.S. Pat. No. 7,630,926) which is a continuation-in-part of U.S. application Ser. No. 10/739,301, filed Dec. 19, 2003, which claims priority to U.S. Provisional Application No. 60/519,630 filed on Nov. 14, 2003, U.S. Provisional Application No. 60/519,629 filed on Nov. 14, 2003, and U.S. application Ser. No. 10/253,243 filed Sep. 24, 2002, which claims priority to U.S. Provisional Application No. 60/324,333 filed Sep. 24, 2001 and U.S. Provisional Application No. 60/396,404 filed Jul. 15, 2002. This application also claims priority to U.S. application Ser. No. 10/712,182 filed Nov. 13, 2003, U.S. application Ser. No. 10/655,828 filed Sep. 5, 2003, and U.S. patent application Ser. No. 10/698,084 filed Nov. 3, 2003. This application also claims priority to U.S. application Ser. No. 10/411,971, filed Apr. 11, 2003, which claims priority to U.S. application Ser. No. 09/641,363 filed Aug. 18, 2000, now issued U.S. Pat. No. 6,575,361, which claims priority to U.S. Provisional Application No. 60/149,740 filed Aug. 19, 1999. This application also claims priority to U.S. application Ser. No. 10/732,641 filed Dec. 10, 2003. This application is related to International Application No. PCT/US02/30281 filed Sep. 24, 2002. All of the aforementioned applications are incorporated herein by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4068213 | Nakamura | Jan 1978 | A |
| 4482802 | Aizawa et al. | Nov 1984 | A |
| 4734858 | Schlafly | Mar 1988 | A |
| 4747049 | Richardson et al. | May 1988 | A |
| 4750119 | Cohen | Jun 1988 | A |
| 4755940 | Brachtl et al. | Jul 1988 | A |
| 4767917 | Ushikubo | Aug 1988 | A |
| 4795892 | Gilmore | Jan 1989 | A |
| 4877947 | Mori | Oct 1989 | A |
| 4900904 | Wright | Feb 1990 | A |
| 4908521 | Boggan et al. | Mar 1990 | A |
| 4943707 | Boggan | Jul 1990 | A |
| 4984155 | Geier | Jan 1991 | A |
| 5117355 | Mccarthy | May 1992 | A |
| 5128520 | Rando | Jun 1992 | A |
| 5202826 | Mccarthy | Apr 1993 | A |
| 5231569 | Myatt | Jul 1993 | A |
| 5255182 | Adams | Oct 1993 | A |
| 5256863 | Ferguson | Oct 1993 | A |
| 5309506 | Alexander | May 1994 | A |
| 5311424 | Mukherjee | May 1994 | A |
| 5350906 | Brody et al. | Sep 1994 | A |
| 5375240 | Grundy | Dec 1994 | A |
| 5383113 | Kight | Jan 1995 | A |
| 5384449 | Peirce | Jan 1995 | A |
| 5416306 | Imahata | May 1995 | A |
| 5465288 | Falvery | Nov 1995 | A |
| 5477038 | Levine et al. | Dec 1995 | A |
| 5500513 | Langhans et al. | Mar 1996 | A |
| 5502765 | Ishiguro | Mar 1996 | A |
| 5511114 | Stimson | Apr 1996 | A |
| 5524073 | Stambler | Jun 1996 | A |
| 5577109 | Stimson | Nov 1996 | A |
| 5578808 | Taylor | Nov 1996 | A |
| 5619559 | Kennedy | Apr 1997 | A |
| 5621201 | Langhans | Apr 1997 | A |
| 5621787 | McKoy | Apr 1997 | A |
| 5644721 | Chung et al. | Jul 1997 | A |
| 5657389 | Houvener | Aug 1997 | A |
| 5671279 | Elgamal | Sep 1997 | A |
| 5679938 | Templeton et al. | Oct 1997 | A |
| 5679940 | Templeton et al. | Oct 1997 | A |
| 5696909 | Wallner | Dec 1997 | A |
| 5705798 | Tarbox | Jan 1998 | A |
| 5712989 | Johnson | Jan 1998 | A |
| 5721768 | Stimson | Feb 1998 | A |
| 5721832 | Westrope | Feb 1998 | A |
| 5732136 | Murphree | Mar 1998 | A |
| 5754655 | Hughes et al. | May 1998 | A |
| 5760381 | Stich et al. | Jun 1998 | A |
| 5765143 | Sheldon | Jun 1998 | A |
| 5777305 | Smith et al. | Jul 1998 | A |
| 5799285 | Klingman | Aug 1998 | A |
| 5804803 | Cragun | Sep 1998 | A |
| 5806045 | Biorge et al. | Sep 1998 | A |
| 5828740 | Khuc | Oct 1998 | A |
| 5844972 | Jagapish | Dec 1998 | A |
| 5870724 | Lawlor | Feb 1999 | A |
| 5887253 | O'Neil | Mar 1999 | A |
| 5889863 | Weber | Mar 1999 | A |
| 5903633 | Lorsch | May 1999 | A |
| 5903830 | Joao | May 1999 | A |
| 5903874 | Leonard et al. | May 1999 | A |
| 5907142 | Kelsey | May 1999 | A |
| 5909492 | Payne et al. | Jun 1999 | A |
| 5918909 | Fiala | Jul 1999 | A |
| 5930363 | Stanford | Jul 1999 | A |
| 5943424 | Berger | Aug 1999 | A |
| 5945653 | Walker | Aug 1999 | A |
| 5949335 | Maynard | Sep 1999 | A |
| 5956636 | Lipsit | Sep 1999 | A |
| 5956695 | Carrithers et al. | Sep 1999 | A |
| 5956700 | Landry | Sep 1999 | A |
| 5974311 | Lipsit | Oct 1999 | A |
| 5987132 | Rowney | Nov 1999 | A |
| 5991748 | Taskett | Nov 1999 | A |
| 5991750 | Watson | Nov 1999 | A |
| 5999624 | Hopkins | Dec 1999 | A |
| 6000608 | Dorf | Dec 1999 | A |
| 6012049 | Kawan | Jan 2000 | A |
| 6018570 | Matison | Jan 2000 | A |
| 6032135 | Molano | Feb 2000 | A |
| 6032859 | Muehlberger | Mar 2000 | A |
| 6058300 | Hanson | May 2000 | A |
| 6073842 | Yoshinaga | Jun 2000 | A |
| 6088682 | Burke | Jul 2000 | A |
| 6092053 | Boesch et al. | Jul 2000 | A |
| 6094643 | Anderson | Jul 2000 | A |
| 6098053 | Slater | Aug 2000 | A |
| 6105008 | Davis et al. | Aug 2000 | A |
| 6119105 | Williams | Sep 2000 | A |
| 6119106 | Mersky | Sep 2000 | A |
| 6119946 | Teicher | Sep 2000 | A |
| 6124799 | Parker | Sep 2000 | A |
| 6125356 | Brockman et al. | Sep 2000 | A |
| 6129276 | Jelen et al. | Oct 2000 | A |
| 6134533 | Shell | Oct 2000 | A |
| 6138106 | Walker | Oct 2000 | A |
| 6167387 | Lee-Wai-Yin | Dec 2000 | A |
| 6169975 | White | Jan 2001 | B1 |
| 6169976 | Colosso | Jan 2001 | B1 |
| 6173272 | Thomas | Jan 2001 | B1 |
| 6185545 | Resnick | Feb 2001 | B1 |
| 6188752 | Lesley | Feb 2001 | B1 |
| 6189787 | Dorf | Feb 2001 | B1 |
| 6190256 | Walker | Feb 2001 | B1 |
| 6202933 | Poore | Mar 2001 | B1 |
| 6208851 | Hanson | Mar 2001 | B1 |
| RE37122 | Levine | Apr 2001 | E |
| 6226364 | O'Neil | May 2001 | B1 |
| 6226624 | Watson | May 2001 | B1 |
| 6237023 | Yoshimoto | May 2001 | B1 |
| 6240397 | Sachs | May 2001 | B1 |
| 6253027 | Weber | Jun 2001 | B1 |
| 6256690 | Carper | Jul 2001 | B1 |
| 6270012 | Dawson | Aug 2001 | B1 |
| 6282566 | Lee, Jr. | Aug 2001 | B1 |
| 6285749 | Manto | Sep 2001 | B1 |
| 6289010 | Volt | Sep 2001 | B1 |
| 6295522 | Boesch | Sep 2001 | B1 |
| 6298336 | Davis | Oct 2001 | B1 |
| 6302326 | Symonds | Oct 2001 | B1 |
| 6304915 | Nguyen | Oct 2001 | B1 |
| 6308887 | Korman et al. | Oct 2001 | B1 |
| 6311165 | Coutts et al. | Oct 2001 | B1 |
| 6311170 | Embrey | Oct 2001 | B1 |
| 6314171 | Dowens | Nov 2001 | B1 |
| 6315195 | Ramchandran | Nov 2001 | B1 |
| 6315206 | Hansen | Nov 2001 | B1 |
| 6324525 | Kramer | Nov 2001 | B1 |
| 6328341 | Klure | Dec 2001 | B2 |
| 6330544 | Walker | Dec 2001 | B1 |
| 6332135 | Conklin | Dec 2001 | B1 |
| 6333976 | Lesley | Dec 2001 | B2 |
| 6375073 | Aebi | Apr 2002 | B1 |
| 6381315 | Nhaissi | Apr 2002 | B1 |
| 6397196 | Kravetz | May 2002 | B1 |
| 6422462 | Cohen | Jul 2002 | B1 |
| 6424706 | Katz et al. | Jul 2002 | B1 |
| 6434238 | Chaum | Aug 2002 | B1 |
| 6434379 | Despres | Aug 2002 | B1 |
| 6442532 | Kawan | Aug 2002 | B1 |
| 6445780 | Rosset | Sep 2002 | B1 |
| 6467684 | Fite et al. | Oct 2002 | B2 |
| 6473500 | Risafi et al. | Oct 2002 | B1 |
| 6473739 | Showghi et al. | Oct 2002 | B1 |
| 6478401 | King | Nov 2002 | B1 |
| 6490445 | Holmes | Dec 2002 | B1 |
| 6494367 | Zacharias | Dec 2002 | B1 |
| 6502745 | Stimson | Jan 2003 | B1 |
| 6507644 | Henderson | Jan 2003 | B1 |
| 6529593 | Nelson | Mar 2003 | B2 |
| 6542933 | Durst | Apr 2003 | B1 |
| 6549770 | Marran | Apr 2003 | B1 |
| 6575361 | Graves | Jun 2003 | B1 |
| 6581827 | Welton | Jun 2003 | B2 |
| 6588658 | Blank | Jul 2003 | B1 |
| 6591098 | Sheih | Jul 2003 | B1 |
| 6592035 | Mandile | Jul 2003 | B2 |
| 6594640 | Postrel | Jul 2003 | B1 |
| 6612487 | Tidball | Sep 2003 | B2 |
| 6615189 | Phillips et al. | Sep 2003 | B1 |
| 6615190 | Slater | Sep 2003 | B1 |
| 6625438 | Hanson | Sep 2003 | B2 |
| 6636489 | Fingerhut | Oct 2003 | B1 |
| 6636833 | Flitcroft | Oct 2003 | B1 |
| 6643504 | Phillips | Nov 2003 | B1 |
| 6648222 | McDonald | Nov 2003 | B2 |
| 6651885 | Arias | Nov 2003 | B1 |
| 6659259 | Knox et al. | Dec 2003 | B2 |
| 6736314 | Cooper et al. | May 2004 | B2 |
| 6745022 | Knox | Jun 2004 | B2 |
| 6785537 | Hicks | Aug 2004 | B2 |
| 6805289 | Noreiga | Oct 2004 | B2 |
| 6820802 | Biggar | Nov 2004 | B2 |
| 6827260 | Stoutenberg | Dec 2004 | B2 |
| 6829596 | Frazee | Dec 2004 | B1 |
| 6836962 | Khandros et al. | Jan 2005 | B2 |
| 6882984 | Boyle | Apr 2005 | B1 |
| 6918537 | Graves | Jul 2005 | B2 |
| 6934529 | Bagoren | Aug 2005 | B2 |
| 6961412 | Ruckart | Nov 2005 | B2 |
| 7024174 | Nagy | Apr 2006 | B2 |
| 7028891 | O'Neal | Apr 2006 | B2 |
| 7063251 | Namekawa | Jun 2006 | B2 |
| 7069248 | Huber | Jun 2006 | B2 |
| 7072864 | Brake | Jul 2006 | B2 |
| 7083084 | Graves | Aug 2006 | B2 |
| 7086584 | Stoutenburg | Aug 2006 | B2 |
| 7093761 | Smith | Aug 2006 | B2 |
| 7096003 | Joao | Aug 2006 | B2 |
| 7103347 | Chow | Sep 2006 | B2 |
| 7131582 | Welton | Nov 2006 | B2 |
| 7168615 | Smith | Jan 2007 | B2 |
| 7194438 | Sovio et al. | Mar 2007 | B2 |
| 7209890 | Peon | Apr 2007 | B1 |
| 7222090 | Oddo | May 2007 | B2 |
| 7243839 | Beck | Jul 2007 | B2 |
| 7249054 | Keil | Jul 2007 | B2 |
| 7260381 | Lipsit | Aug 2007 | B2 |
| 7269256 | Rosen | Sep 2007 | B2 |
| 7272385 | Mirouze | Sep 2007 | B2 |
| 7292998 | Graves | Nov 2007 | B2 |
| 7328190 | Smith | Feb 2008 | B2 |
| 7333955 | Graves et al. | Feb 2008 | B2 |
| 7343406 | Buonanno | Mar 2008 | B1 |
| 7363265 | Horgan | Apr 2008 | B2 |
| 7370012 | Karns et al. | May 2008 | B2 |
| 7376431 | Niedermeyer | May 2008 | B2 |
| 7398248 | Phillips et al. | Jul 2008 | B2 |
| 7434729 | Cracchiolo | Oct 2008 | B2 |
| 7437328 | Graves et al. | Oct 2008 | B2 |
| 7483862 | Robinson | Jan 2009 | B1 |
| 7536349 | Mik et al. | May 2009 | B1 |
| 7566000 | Agostino et al. | Jul 2009 | B2 |
| 7650308 | Nguyen et al. | Jan 2010 | B2 |
| 7673327 | Polis et al. | Mar 2010 | B1 |
| 7735724 | Fujita | Jun 2010 | B2 |
| 7866548 | Reed et al. | Jan 2011 | B2 |
| 7904333 | Perkowski | Mar 2011 | B1 |
| 7941373 | Chang et al. | May 2011 | B1 |
| 7958049 | Jamison et al. | Jun 2011 | B2 |
| 7959076 | Hopkins | Jun 2011 | B1 |
| 8046268 | Hunt | Oct 2011 | B2 |
| 8060413 | Castell et al. | Nov 2011 | B2 |
| 8152060 | Wolfe et al. | Apr 2012 | B2 |
| 8152061 | Wolfe et al. | Apr 2012 | B2 |
| 8195568 | Singhal | Jun 2012 | B2 |
| 8245910 | Sullivan et al. | Aug 2012 | B2 |
| 8332277 | Mccaffery et al. | Dec 2012 | B2 |
| 8332323 | Stals et al. | Dec 2012 | B2 |
| 8355982 | Hazel | Jan 2013 | B2 |
| 8371502 | Galit et al. | Feb 2013 | B1 |
| 8631999 | Wolfe et al. | Jan 2014 | B2 |
| 8662387 | Geller | Mar 2014 | B1 |
| 20010000808 | Lesley | May 2001 | A1 |
| 20010001321 | Resnick | May 2001 | A1 |
| 20010001856 | Gould | May 2001 | A1 |
| 20010023415 | Keil | Sep 2001 | A1 |
| 20010032878 | Tsiounis | Oct 2001 | A1 |
| 20010034707 | Sakaguchi | Oct 2001 | A1 |
| 20010034720 | Armes | Oct 2001 | A1 |
| 20010042784 | Fite | Nov 2001 | A1 |
| 20010044293 | Morgan | Nov 2001 | A1 |
| 20020002503 | Matsuoka | Jan 2002 | A1 |
| 20020022966 | Hogan | Feb 2002 | A1 |
| 20020025797 | Joao | Feb 2002 | A1 |
| 20020077076 | Suryanarayana | Jun 2002 | A1 |
| 20020004889 | Fiala | Jul 2002 | A1 |
| 20020088851 | Hodes | Jul 2002 | A1 |
| 20020088855 | Hodes | Jul 2002 | A1 |
| 20020091573 | Hodes | Jul 2002 | A1 |
| 20020095420 | Hovsepian | Jul 2002 | A1 |
| 20020101966 | Nelson | Aug 2002 | A1 |
| 20020115424 | Bagoren | Aug 2002 | A1 |
| 20020119767 | Fieldhouse | Aug 2002 | A1 |
| 20020133457 | Gerlach | Sep 2002 | A1 |
| 20020138450 | Kremer | Sep 2002 | A1 |
| 20020161631 | Banerjee et al. | Oct 2002 | A1 |
| 20020190123 | Anvekar | Dec 2002 | A1 |
| 20020198737 | Valtanen | Dec 2002 | A1 |
| 20030001005 | Risafi | Jan 2003 | A1 |
| 20030014360 | Arditti | Jan 2003 | A1 |
| 20030028481 | Flitcroft | Feb 2003 | A1 |
| 20030033246 | Slater | Feb 2003 | A1 |
| 20030038175 | Welton | Feb 2003 | A1 |
| 20030046249 | Wu | Mar 2003 | A1 |
| 20030055782 | Slater | Mar 2003 | A1 |
| 20030061157 | Hirka | Mar 2003 | A1 |
| 20030061162 | Matthews | Mar 2003 | A1 |
| 20030070080 | Rosen | Apr 2003 | A1 |
| 20030078835 | Plutchinske | Apr 2003 | A1 |
| 20030092435 | Boivin | May 2003 | A1 |
| 20030105672 | Epstein | Jun 2003 | A1 |
| 20030126079 | Roberson | Jul 2003 | A1 |
| 20030135462 | Brake | Jul 2003 | A1 |
| 20030144909 | Flaherty | Jul 2003 | A1 |
| 20030144935 | Sobek | Jul 2003 | A1 |
| 20030167207 | Berardi et al. | Sep 2003 | A1 |
| 20030172031 | Graves | Sep 2003 | A1 |
| 20030187781 | Goodman | Oct 2003 | A1 |
| 20030194988 | Knox | Oct 2003 | A1 |
| 20030200179 | Kwan | Oct 2003 | A1 |
| 20030204457 | Arias | Oct 2003 | A1 |
| 20030212796 | Willard | Nov 2003 | A1 |
| 20030218062 | Noreiga | Nov 2003 | A1 |
| 20030236704 | Antonucci | Dec 2003 | A1 |
| 20040007618 | Oram | Jan 2004 | A1 |
| 20040009760 | Layburn | Jan 2004 | A1 |
| 20040046035 | Davila et al. | Mar 2004 | A1 |
| 20040049427 | Tami | Mar 2004 | A1 |
| 20040054587 | Dev | Mar 2004 | A1 |
| 20040064412 | Phillips | Apr 2004 | A1 |
| 20040078332 | Ferguson et al. | Apr 2004 | A1 |
| 20040114766 | Hileman | Jun 2004 | A1 |
| 20040118914 | Smith | Jun 2004 | A1 |
| 20040128395 | Miyazaki | Jul 2004 | A1 |
| 20040129777 | Smith | Jul 2004 | A1 |
| 20040133511 | Smith | Jul 2004 | A1 |
| 20040153402 | Smith | Aug 2004 | A1 |
| 20040164145 | Licciardello et al. | Aug 2004 | A1 |
| 20040167821 | Baumgartner | Aug 2004 | A1 |
| 20040181453 | Ray | Sep 2004 | A1 |
| 20040205023 | Hafer | Oct 2004 | A1 |
| 20040210449 | Breck | Oct 2004 | A1 |
| 20040210519 | Oppenlander | Oct 2004 | A1 |
| 20040215573 | Teutenberg | Oct 2004 | A1 |
| 20040218741 | Welton | Nov 2004 | A1 |
| 20040224660 | Anderson | Nov 2004 | A1 |
| 20040225605 | Rowe | Nov 2004 | A1 |
| 20040230536 | Fung | Nov 2004 | A1 |
| 20040232225 | Bishop | Nov 2004 | A1 |
| 20040260647 | Blinn et al. | Dec 2004 | A1 |
| 20040267663 | Karns | Dec 2004 | A1 |
| 20050001027 | Bahar | Jan 2005 | A1 |
| 20050027624 | Cai | Feb 2005 | A1 |
| 20050027655 | Sharma | Feb 2005 | A1 |
| 20050033645 | Duphily | Feb 2005 | A1 |
| 20050051619 | Graves | Mar 2005 | A1 |
| 20050060248 | O'Neal | Mar 2005 | A1 |
| 20050061872 | Paschini | Mar 2005 | A1 |
| 20050079863 | Macaluso | Apr 2005 | A1 |
| 20050086171 | Abe | Apr 2005 | A1 |
| 20050107068 | Smith | May 2005 | A1 |
| 20050108096 | Burger | May 2005 | A1 |
| 20050108121 | Gravett et al. | May 2005 | A1 |
| 20050127169 | Foss | Jun 2005 | A1 |
| 20050131815 | Fung | Jun 2005 | A1 |
| 20050143051 | Park | Jun 2005 | A1 |
| 20050149387 | O'Shea | Jul 2005 | A1 |
| 20050177517 | Leung | Aug 2005 | A1 |
| 20050182678 | Walker | Aug 2005 | A1 |
| 20050182720 | Willard | Aug 2005 | A1 |
| 20050202850 | Kuty | Sep 2005 | A1 |
| 20050203835 | Nhaissi et al. | Sep 2005 | A1 |
| 20050228717 | Gusler | Oct 2005 | A1 |
| 20050228720 | Pavlic | Oct 2005 | A1 |
| 20050234820 | Mackouse | Oct 2005 | A1 |
| 20050240472 | Postrel | Oct 2005 | A1 |
| 20050259589 | Rozmovits et al. | Nov 2005 | A1 |
| 20050261968 | Randall et al. | Nov 2005 | A1 |
| 20050263587 | Martinez | Dec 2005 | A1 |
| 20050278216 | Graves | Dec 2005 | A1 |
| 20060019634 | Hawkes | Jan 2006 | A1 |
| 20060023856 | Welton | Feb 2006 | A1 |
| 20060026073 | Kenny | Feb 2006 | A1 |
| 20060030306 | Kuhn | Feb 2006 | A1 |
| 20060035632 | Sorvari | Feb 2006 | A1 |
| 20060058011 | Vanska | Mar 2006 | A1 |
| 20060069642 | Doran et al. | Mar 2006 | A1 |
| 20060085335 | Crawford | Apr 2006 | A1 |
| 20060100927 | Zormati | May 2006 | A1 |
| 20060113376 | Reed | Jun 2006 | A1 |
| 20060161490 | Chakiris | Jul 2006 | A1 |
| 20060163343 | Changryeol | Jul 2006 | A1 |
| 20060163347 | Foss | Jul 2006 | A1 |
| 20060213985 | Walker | Sep 2006 | A1 |
| 20060217996 | Graves | Sep 2006 | A1 |
| 20060235754 | Walker et al. | Oct 2006 | A1 |
| 20060249570 | Seifert | Nov 2006 | A1 |
| 20060255125 | Jennings | Nov 2006 | A1 |
| 20060289621 | Foss | Dec 2006 | A1 |
| 20070021969 | Homeier-Beals | Jan 2007 | A1 |
| 20070057045 | Beck | Mar 2007 | A1 |
| 20070063024 | Guillot | Mar 2007 | A1 |
| 20070108269 | Benco | May 2007 | A1 |
| 20070114274 | Gibbs | May 2007 | A1 |
| 20070118478 | Graves | May 2007 | A1 |
| 20070119920 | Hogg | May 2007 | A1 |
| 20070174166 | Jones | Jul 2007 | A1 |
| 20070185820 | Talker | Aug 2007 | A1 |
| 20070187490 | Feldman | Aug 2007 | A1 |
| 20070214080 | Babi et al. | Sep 2007 | A1 |
| 20070257767 | Beeson | Nov 2007 | A1 |
| 20070284434 | Fletcher | Dec 2007 | A1 |
| 20080010215 | Rackley, III | Jan 2008 | A1 |
| 20080041938 | Wise | Feb 2008 | A1 |
| 20080070690 | Van Luchene | Mar 2008 | A1 |
| 20080109356 | Sutton | May 2008 | A1 |
| 20080148408 | Kao et al. | Jun 2008 | A1 |
| 20080162341 | Zimmer et al. | Jul 2008 | A1 |
| 20080255942 | Craft | Oct 2008 | A1 |
| 20090006116 | Baker | Jan 2009 | A1 |
| 20090112709 | Barhydt et al. | Apr 2009 | A1 |
| 20090132415 | Davis et al. | May 2009 | A1 |
| 20090157554 | Hobson et al. | Jun 2009 | A1 |
| 20090173782 | Muscato | Jul 2009 | A1 |
| 20090173784 | Yang | Jul 2009 | A1 |
| 20090240516 | Palestrant | Sep 2009 | A1 |
| 20090254432 | Mccaffery et al. | Oct 2009 | A1 |
| 20090281941 | Worth | Nov 2009 | A1 |
| 20090298427 | Wilkinson et al. | Dec 2009 | A1 |
| 20100005025 | Kumar et al. | Jan 2010 | A1 |
| 20100008535 | Abulafia | Jan 2010 | A1 |
| 20100042471 | Chang | Feb 2010 | A1 |
| 20100057554 | Lanford | Mar 2010 | A1 |
| 20100057580 | Raghunathan | Mar 2010 | A1 |
| 20100097180 | Cardullo | Apr 2010 | A1 |
| 20100312636 | Coulter et al. | Dec 2010 | A1 |
| 20110071913 | Chakiris et al. | Mar 2011 | A1 |
| 20110082772 | Hirson | Apr 2011 | A1 |
| 20110087592 | Van Der et al. | Apr 2011 | A1 |
| 20110091092 | Nepomniachtchi | Apr 2011 | A1 |
| 20110166992 | Dessert et al. | Jul 2011 | A1 |
| 20110173083 | Reed et al. | Jul 2011 | A1 |
| 20110270693 | Paschini | Nov 2011 | A1 |
| 20110295749 | Scalisi | Dec 2011 | A1 |
| 20120099780 | Smith | Apr 2012 | A1 |
| 20120234911 | Yankovich | Sep 2012 | A1 |
| 20120284185 | Mettler | Nov 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1361775 | Nov 2003 | EP |
| 1534043 | May 2005 | EP |
| 1705610 | Sep 2006 | EP |
| 2006309729 | Nov 2006 | JP |
| WO 01-02233 | Mar 2001 | WO |
| WO 2005098770 | Nov 2005 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20110071913 A1 | Mar 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60519630 | Nov 2003 | US | |
| 60519629 | Nov 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12607141 | Oct 2009 | US |
| Child | 12955543 | US | |
| Parent | 11290606 | Dec 2005 | US |
| Child | 12607141 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10739301 | Dec 2003 | US |
| Child | 11290606 | US |
