Patent Grant
9672516
At least some embodiments presented in the disclosure relate to a computing system having a plurality of computers connected via one or more networks in general and, more particularly but not limited to, protocols for communication among a plurality of computers for authorization of resource transfer.
The Internet provides a communication channel for flexible communication connections among various computing devices connected to it. For example, web browsers running in computing devices may access web servers via standardized communication protocols, such as Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), etc.
For security reasons, reliability reasons, and/or other reasons, certain computers are interconnected via propriety networks and/or dedicated network connections. For example, certain computers configured with high security considerations may be connected via dedicated network connections. For example, financial transaction card originated messages transmitted in accordance with ISO 8583 are generally propagated in secure networks.
Combining existing propriety networks and/or dedicated network connections with open connections offered by the Internet may offer advantages in some instances.
The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
In one embodiment, a communication protocol is provided in a computing system having multiple computers connected via multiple networks to facilitate the authorization of the transfer of resources among accounts.
In
In
In
In a communication interaction between a mobile device (107) and a reader (109), the reader (109) obtains the source identifier (125) from the mobile device (107) and generates an authorization request for the transfer of resources from the source account (121) identified by the source identifier (125) obtained from the mobile device (107) to a destination account (113) identified by the reader (109) having the reader ID (111) and connected to the destination account controller (115) of the respective destination account (113) that is associated with the same reader ID (111).
In
In
In
In
In
Thus, the centralized router (101) routes an authorization request, originated by a reader (109) interacting with a mobile device (107) having the source identifier (125), from a destination account controller (115) connected to the reader (109) to the source account controller (117) identified by the source identifier (125), receives the authorization response from the source account controller (117) and routes the authorization response back to the respective destination account controller (115), which provides the authorization response to the respective reader (109). In one embodiment, the communication messages between the centralized router (101) and the source account controllers (117) or the destination account controllers (115) are in accordance with a publish standard to support interoperability, such as ISO 8583.
In one embodiment, each of the reader (109) is a separate computer disposed at a different location. A mobile device (107) is configured with a source identifier (125) to be read by the reader (109), e.g., via scanning using laser, reading a magnetic data strip mounted on a plastic card, reading via near field communications. In some instances, the source identifier (125) may be read by a person and entered manually in the reader (109) via a keypad.
In
In
In
In
In
In one embodiment, the linked account controller (119) is connected to the portal (103) via Internet (or a dedicated secure connection). Alternatively or in combination, the linked account controller (119) may be connected to the centralized router (101) in a way similar to the connection between a source account controller (117) and the centralized router (101). In some instances, the linked account controller (119) is one of the source account controller (117) and controls a set of source accounts (121).
At least some embodiments presented in the disclosure provide communication protocols for the multiple computers, connected via the various network connections illustrated in
In
Based on the data linking the source identifier (125) and the linked identifier (127), the portal (103) translates the first authorization request (201) to a second authorization request (202) that identifies the linked identifier (127) and routes the second authorization request (202) to the linked account controller (119) that controls the linked account (123) identified by the linked identifier (127).
Based on a predetermined set of rules, the linked account controller (119) provides an authorization response (203) that identifies the available resource (205) in the linked account (123). In one embodiment, the authorization response (203) authorizes the transfer of the available resource (205) from the linked account (123) to the destination account (113) associated with the reader (109) having the reader ID (111) and connected to the destination account controller (115).
In
Based on the identification of the available resource (205) identified in the authorization response (203) from the linked account controller (119), the reader (109) determines a requested resource (207) and generates a third authorization request (211) transmitted to the destination account controller (115). The third authorization request (211) identifies the requested resource (207) and the source identifier (125) received from the mobile device (107). In one embodiment, the third authorization request (211) is generated by the reader (109) without reading the mobile device (107) again.
The destination account controller (115) routes the authorization request (211), via the centralized router (101), to the source account controller (117), for an authorization response (213) made by the source account controller (117) controlling the source account (121) identified by the source identifier (125).
The centralized router (101) routes the authorization request (211) received from the source account controller (117) back to the reader (109) via the destination account controller (115).
Thus, with a single communication interaction between the reader (109) and the mobile device (107) to initiate a transfer using the source identifier (125), the communication protocol allows the authorization of the transfer of resources from both the linked account (123) and the source account (121).
In some embodiments, the reader (109) may present the available resource (205) and receive a user input to accept or reject the transfer of the available resource (205) from the linked account (123) as part of the transfer of resources from the source account (121) identified by the source identifier (125). The requested resources (207) is then computed based on the user input in connection with the available resource (205) identified by the linked account controller (119).
In
Based on the data linking the source identifier (125) and the linked identifier (127), the portal (103) translates the first authorization request (201) to a second authorization request (202) that identifies the linked identifier (127) and routes the second authorization request (202) to the linked account controller (119) that controls the linked account (123) identified by the linked identifier (127).
Based on a predetermined set of rules, the linked account controller (119) provides an authorization response (203) that identifies the available resource (205) in the linked account (123). The authorization response (203) authorizes the transfer of the available resource (205) from the linked account (123) to the destination account (113) associated with the reader (109) having the reader ID (111) and connected to the destination account controller (115).
In
For example, based on an identifier of the reader (109) provided in the first authorization request (201), such as the reader ID (111), the portal (103) and/or the centralized router (101) determines the identity of the destination account controller (115) to which the reader (109) is connected. Thus, the portal (103) provides the authorization response (203) received from the linked account controller (119) to the centralized router (101), which then provides the authorization response (203) to the destination account controller (115) that is in control of the destination account (113) associated with the reader (109). Based on the reader ID (111) (e.g., initially provided in the first authorization request (201)), the destination account controller (115) routes the authorization response (203) back to the reader (109), which is in general as illustrated in
Based on the identification of the available resource (205) identified in the authorization response (203) from the linked account controller (119), the reader (109) determines a requested resource (207) and generates a third authorization request (211) transmitted to the destination account controller (115). The third authorization request (211) identifies the requested resource (207) and the source identifier (125) received from the mobile device (107). In one embodiment, the third authorization request (211) is generated by the reader (109) without reading the mobile device (107) again.
The destination account controller (115) routes the authorization request (211), via the centralized router (101), to the source account controller (117), for an authorization response (213) made by the source account controller (117) controlling the source account (121) identified by the source identifier (125).
The centralized router (101) routes the authorization request (211) received from the source account controller (117) back to the reader (109) via the destination account controller (115).
Since the destination account controller (115) is in the path of both the authorization responses (203) and (213) for the authorizations of the transfers from the linked accounts (123) and the source account (121), the destination account controller (115) is in a better and informed position to request actual transfer of resources from the linked accounts (123) and the source account (121) to the destination account (113).
In
In
Based on a predetermined set of rules, the linked account controller (119) provides an authorization response (203) that identifies the available resource (205) in the linked account (123). The authorization response (203) authorizes the transfer of the available resource (205) from the linked account (123) to the destination account (113) associated with the reader (109) having the reader ID (111) and connected to the destination account controller (115).
In
Based on the identification of the available resource (205) in the authorization response (203) from the linked account controller (119), the reader (109) determines a requested resource (207) and generates a third authorization request (211) transmitted to the destination account controller (115). The third authorization request (211) identifies the requested resource (207) and the source identifier (125) received from the mobile device (107). The third authorization request (211) is generated by the reader (109) in response to the authorization response (203) without reading the mobile device (107) again.
The destination account controller (115) routes the authorization request (211), via the centralized router (101), to the source account controller (117), for an authorization response (213) made by the source account controller (117) controlling the source account (121) identified by the source identifier (125).
The centralized router (101) routes the authorization request (211) received from the source account controller (117) back to the reader (109) via the destination account controller (115).
In
In
Based on a predetermined set of rules, the linked account controller (119) provides an authorization response (203) that identifies the available resource (205) in the linked account (123). The authorization response (203) authorizes the transfer of the available resource (205) from the linked account (123) to the destination account (113) associated with the reader (109) having the reader ID (111) and connected to the destination account controller (115).
In
Based on the identification of the available resource (205) in the authorization response (203) from the linked account controller (119), the reader (109) determines a requested resource (207) and generates a third authorization request (211) transmitted to the destination account controller (115). The third authorization request (211) identifies the requested resource (207) and the source identifier (125) received from the mobile device (107). The third authorization request (211) is generated by the reader (109) in response to the authorization response (203) without reading the mobile device (107) again.
The destination account controller (115) routes the authorization request (211), via the centralized router (101), to the source account controller (117), for an authorization response (213) made by the source account controller (117) controlling the source account (121) identified by the source identifier (125).
The centralized router (101) routes the authorization request (211) received from the source account controller (117) back to the reader (109) via the destination account controller (115).
Thus, in
In some embodiments, the reader (109) may present the available resource (205) and receive a user input to accept or reject the transfer of the available resource (205) from the linked account (123) as part of the transfer of resources from the source account (121) identified by the source identifier (125). The requested resources (207) is then computed based on the user input in connection with the available resource (205) identified by the linked account controller (119).
The communication techniques discussed in
For example, in one embodiment, a transaction handler of an electronic payment processing network can be implemented as the centralized router (101). Acquirer processors controlling the merchant accounts can be implemented as the destination account controllers (115) of the destination accounts (113); and the issuer processors controlling the consumer payment accounts can be implemented as the source account controllers (117) of the source accounts (121). Loyalty reward hosts controlling the reward accounts can be implemented as the linked account controller (119) of the linked accounts (123). The transaction terminals of merchants can be implemented as the readers (109) configured to read payment devices, or account identification devices, implemented as the mobile device (107) illustrated in
For example, a system and method can be provided to allow loyalty points redemption at POS terminal using the communication protocols discussed above. The method operates by using POS integration to process point redemption. When a payment transaction is initiated at the POS terminal, the POS terminal visits a portal of a transaction handler to obtain rewards authorization. A rewards broker at transaction handler communicates with the issuer or reward host to obtain authorization of a points redemption deal and causes the POS terminal to prompt the user to accept the deal. Based on the response of the user, the POS terminal generates a further authorization request for a transaction in the payment account for the remaining balance of the transaction. During clearing and settlement, the loyalty broker, the portal, or the POS terminal may push the transaction to the acquirer processor. Thus, a user can be presented with the option to use a just-in-time point redemption deal, communicated via out of band communication channel with the transaction handler, and seamlessly charge the remaining balance to the payment account, as if the authorization for the transaction were performed once from the user point of view.
In one embodiment, the first authorization request (201) for a transaction in the payment account results in a pre-authorization of a point redemption deal that provides a predetermined amount of benefit, which corresponds to the available resource (205) identified in the authorization response (203). The further authorization request (211) for a transaction in the payment account is generated automatically by the POS terminal for a modified transaction amount in the same payment account.
In one embodiment, the first authorization request (201) may be transmitted from the transaction terminal (105) to a transaction handler (143) via an acquirer processor (147) in a way as illustrated in
Alternatively, as illustrated in
In
In
In
In
If the rewards inquiry does not provides an authorization for the redemption, the transaction terminal (105) may transmit an authorization request for the redemption of the rewards requested by the user.
In
Alternatively, the transaction terminal (105) or the transaction handler (103) may amend the settlement request in a similar manner.
In one embodiment, a system and method is configured to: receive an authorization request for a transaction in a payment account; in response to the authorization request, identify a deal to redeem an amount of loyalty benefit applicable to the transaction; provide a pre-authorization of the deal as a response to the authorization request, the pre-authorization causing a POS terminal to prompt a user to provide an input to accept or reject the deal; receive a subsequent authorization request for the transaction, the subsequent authorization identifying a transaction amount in the payment account based on a user response received at the POS terminal; and communicate with an issuer processor of the payment account for an authorization of the transaction amount.
Variations
Some embodiments use more or fewer components than those illustrated in the figures. For example, in some embodiments, the destination account controllers (115), the centralized router (101), and the source account controllers (117) may be operated by the same entity within an intranet. In one embodiment, the destination account controllers (115), the centralized router (101), and the source account controllers (117) may be implemented in the same set of one or more computers.
In some embodiments, the portal (103) is implemented using the same set of one or more computers of the centralized router (101).
Transaction Processing
In
In
In
The account identification device (141) of one embodiment is a plastic card having a magnetic strip storing the account information (142) identifying the consumer account (146) and/or the issuer processor (145). Alternatively, the account identification device (141) is a smartcard having an integrated circuit chip storing at least the account information (142). The account identification device (141) may optionally include a mobile phone having an integrated smartcard.
The account information (142) may be printed or embossed on the account identification device (141). The account information (142) may be printed as a bar code to allow the transaction terminal (144) to read the information via an optical scanner. The account information (142) may be stored in a memory of the account identification device (141) and configured to be read via wireless, contactless communications, such as near field communications via magnetic field coupling, infrared communications, or radio frequency communications. Alternatively, the transaction terminal (144) may require contact with the account identification device (141) to read the account information (142) (e.g., by reading the magnetic strip of a card with a magnetic strip reader).
The transaction terminal (144) is configured to transmit an authorization request message to the acquirer processor (147). The authorization request includes the account information (142), an amount of payment, and information about the merchant (e.g., an indication of the merchant account (148)). The acquirer processor (147) asks the transaction handler (143) to process the authorization request based on the account information (142) received in the transaction terminal (144). The transaction handler (143) routes the authorization request to the issuer processor (145) and may process and respond to the authorization request when the issuer processor (145) is not available. The issuer processor (145) determines whether to authorize the transaction based at least in part on a balance of the consumer account (146).
The transaction handler (143), the issuer processor (145), and the acquirer processor (147) may each include a subsystem to identify the risk in the transaction and may reject the transaction based on the risk assessment.
The account identification device (141) may include security features to prevent unauthorized uses of the consumer account (146), such as a logo to show the authenticity of the account identification device (141), encryption to protect the account information (142), etc.
The transaction terminal (144) of one embodiment is configured to interact with the account identification device (141) to obtain the account information (142) that identifies the consumer account (146) and/or the issuer processor (145). The transaction terminal (144) communicates with the acquirer processor (147) that controls the merchant account (148) of a merchant. The transaction terminal (144) may communicate with the acquirer processor (147) via a data communication connection, such as a telephone connection, an Internet connection, etc. The acquirer processor (147) is to collect payments for deposit into the merchant account (148) on behalf of the merchant.
In one embodiment, the transaction terminal (144) is a POS terminal at a traditional, offline, “brick and mortar” retail store. In another embodiment, the transaction terminal (144) is an online server that receives the account information (142) of the consumer account (146) from the user through a web connection. In one embodiment, the user may provide account information (142) through a telephone call, via verbal communications with a representative of the merchant, and the representative enters the account information (142) into the transaction terminal (144) to initiate the transaction.
In one embodiment, the account information (142) can be entered directly into the transaction terminal (144) to make payments from the consumer account (146) without having to physically present the account identification device (141). When a transaction is initiated without physically presenting the account identification device (141), the transaction is classified as a “card-not-present” (CNP) transaction.
In general, the issuer processor (145) may control more than one consumer account (146), the acquirer processor (147) may control more than one merchant account (148), and the transaction handler (143) is connected between a plurality of issuer processors (e.g., 145) and a plurality of acquirer processors (e.g., 147). An entity (e.g., bank) may operate both an issuer processor (145) and an acquirer processor (147).
In one embodiment, the transaction handler (143), the issuer processor (145), the acquirer processor (147), the transaction terminal (144), the portal (103), and other devices and/or services accessing the portal (103) are connected via communications networks, such as local area networks, cellular telecommunications networks, wireless wide area networks, wireless local area networks, an intranet, and the Internet. Dedicated communication channels may be used between the transaction handler (143) and the issuer processor (145), between the transaction handler (143) and the acquirer processor (147), and/or between the portal (103) and the transaction handler (143).
In
Typically, the transaction handler (143) is implemented using a powerful computer, or cluster of computers functioning as a unit, controlled by instructions stored on a computer-readable medium. The transaction handler (143) is configured to support and deliver authorization services, exception file services, and clearing and settlement services. The transaction handler (143) has a subsystem to process authorization requests and another subsystem to perform clearing and settlement services. The transaction handler (143) is configured to process different types of transactions, such credit card transactions, debit card transactions, prepaid card transactions, and other types of commercial transactions. The transaction handler (143) interconnects the issuer processors (e.g., 145) and the acquirer processor (e.g., 147) to facilitate payment communications.
In
In
The transaction terminal (144) may submit a transaction directly for settlement, without having to separately submit an authorization request.
In one embodiment, the portal (103) provides a user interface to allow the user to organize the transactions in one or more consumer accounts (146) of the user with one or more issuers. The user may organize the transactions using information and/or categories identified in the transaction records, such as merchant category, transaction date, amount, etc. Examples and techniques in one embodiment are provided in U.S. Pat. App. Pub. No. 2007/0055597, and entitled “Method and System for Manipulating Purchase Information,” the disclosure of which is hereby incorporated herein by reference.
Transaction Terminal
In one embodiment, the transaction terminal (144) includes a memory (167) coupled to a processor (151), which controls the operations of a reader (163), an input device (153), an output device (165) and a network interface (161). The memory (167) may store instructions for the processor (151) and/or data, such as an identification that is associated with the merchant account (148).
In one embodiment, the reader (163) includes a magnetic strip reader. In another embodiment, the reader (163) includes a contactless reader, such as a radio frequency identification (RFID) reader, a near field communications (NFC) device configured to read data via magnetic field coupling (in accordance with ISO standard 14443/NFC), a Bluetooth transceiver, a WiFi transceiver, an infrared transceiver, a laser scanner, etc.
In one embodiment, the input device (153) includes key buttons that can be used to enter the account information (142) directly into the transaction terminal (144) without the physical presence of the account identification device (141). The input device (153) can be configured to provide further information to initiate a transaction, such as a personal identification number (PIN), password, zip code, etc., that may be used to access the account identification device (141), or in combination with the account information (142) obtained from the account identification device (141).
In one embodiment, the output device (165) may include a display, a speaker, and/or a printer to present information, such as the result of an authorization request, a receipt for the transaction, an advertisement, etc.
In one embodiment, the network interface (161) is configured to communicate with the acquirer processor (147) via a telephone connection, an Internet connection, or a dedicated data communication channel.
In one embodiment, the instructions stored in the memory (167) are configured at least to cause the transaction terminal (144) to send an authorization request message to the acquirer processor (147) to initiate a transaction. The transaction terminal (144) may or may not send a separate request for the clearing and settling of the transaction. The instructions stored in the memory (167) are also configured to cause the transaction terminal (144) to perform other types of functions discussed in this description.
In one embodiment, a transaction terminal (144) may have fewer components than those illustrated in
In one embodiment, the transaction terminal (144) may have more components than those illustrated in
Account Identification Device
In one embodiment, the account identification device (141) includes the memory (167) coupled to the processor (151), which controls the operations of a communication device (159), the input device (153), an audio device (157) and a display device (155). The memory (167) may store instructions for the processor (151) and/or data, such as the account information (142) associated with the consumer account (146).
In one embodiment, the account information (142) includes an identifier identifying the issuer (and thus the issuer processor (145)) among a plurality of issuers, and an identifier identifying the consumer account (146) among a plurality of consumer accounts (146) controlled by the issuer processor (145). The account information (142) may include an expiration date of the account identification device (141), the name of the consumer holding the consumer account (146), and/or an identifier identifying the account identification device (141) among a plurality of account identification devices (141) associated with the consumer account (146).
In one embodiment, the account information (142) may further include a loyalty program account number, accumulated rewards of the consumer in the loyalty program, an address of the consumer, a balance of the consumer account (146), transit information (e.g., a subway or train pass), access information (e.g., access badges), and/or consumer information (e.g., name, date of birth), etc.
In one embodiment, the memory (167) includes a nonvolatile memory, such as magnetic strip, a memory chip, a flash memory, a Read Only Memory (ROM), etc. to store the account information (142).
In one embodiment, the information stored in the memory (167) of the account identification device (141) may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as the account number and other discretionary data. Track 1 is sometimes used by airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently the most commonly used and is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of Track 1 and banks abide by it. It contains the cardholder's account number, encrypted PIN, and other discretionary data.
In one embodiment, the communication device (159) includes a semiconductor chip to implement a transceiver for communication with the reader (163) and an antenna to provide and/or receive wireless signals.
In one embodiment, the communication device (159) is configured to communicate with the reader (163). The communication device (159) may include a transmitter to transmit the account information (142) via wireless transmissions, such as radio frequency signals, magnetic coupling, or infrared, Bluetooth or WiFi signals, etc.
In one embodiment, the account identification device (141) is in the form of a mobile phone, personal digital assistant (PDA), etc. The input device (153) can be used to provide input to the processor (151) to control the operation of the account identification device (141), and the audio device (157) and the display device (155) may present status information and/or other information, such as advertisements or offers. The account identification device (141) may include further components that are not shown in
In one embodiment, the communication device (159) may access the account information (142) stored on the memory (167) without going through the processor (151).
In one embodiment, the account identification device (141) has fewer components than those illustrated in
For example, in one embodiment, the account identification device (141) is in the form of a debit card, a credit card, a smartcard, or a consumer device that has optional features such as magnetic strips, or smartcards.
An example of an account identification device (141) is a magnetic strip attached to a plastic substrate in the form of a card. The magnetic strip is used as the memory (167) of the account identification device (141) to provide the account information (142). Consumer information, such as account number, expiration date, and consumer name may be printed or embossed on the card. A semiconductor chip implementing the memory (167) and the communication device (159) may also be embedded in the plastic card to provide the account information (142) in one embodiment. In one embodiment, the account identification device (141) has the semiconductor chip but not the magnetic strip.
In one embodiment, the account identification device (141) is integrated with a security device, such as an access card, a radio frequency identification (RFID) tag, a security card, a transponder, etc.
In one embodiment, the account identification device (141) is a handheld and compact device. In one embodiment, the account identification device (141) has a size suitable to be placed in a wallet or pocket of the consumer.
Some examples of an account identification device (141) include a credit card, a debit card, a stored value device, a payment card, a gift card, a smartcard, a smart media card, a payroll card, a health care card, a wrist band, a keychain device, a supermarket discount card, a transponder, and a machine-readable medium containing the account information (142).
Hardware
In one embodiment, a computing apparatus is configured to include some of the components of systems illustrated in various figures, such as the mobile device (107), the reader (109), the destination account controller (115), the centralized router (101), the data storage (105), the portal (103), the source account controller (117), the linked account controller (119), the transaction handler (143), the data warehouse (149), the issuer processor (145), the acquirer processor (147), the transaction terminal (144), the loyalty points bank (181), the settlement bank (183), etc.
In one embodiment, at least some of the components can be implemented as a computer system, such as a data processing system (170) illustrated in
In one embodiment, the transaction handler (143) is a payment processing system, or a payment card processor, such as a card processor for credit cards, debit cards, etc.
In
In one embodiment, the inter-connect (171) interconnects the microprocessor(s) (173) and the memory (167) together and also interconnects them to input/output (I/O) device(s) (175) via I/O controller(s) (177). The I/O devices (175) may include the display device (155) and/or peripheral devices, such as mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices known in the art. In one embodiment, when the data processing system is a server system, some of the I/O devices (175), such as printers, scanners, mice, and/or keyboards, are optional.
In one embodiment, the inter-connect (171) includes one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment the I/O controllers (177) include a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.
In one embodiment, the memory (167) includes one or more of: ROM (Read Only Memory), volatile RAM (Random Access Memory), and non-volatile memory, such as hard drive, flash memory, etc.
Volatile RAM is typically implemented as dynamic RAM (DRAM) that requires power continually in order to refresh or maintain the data in the memory. Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, an optical drive (e.g., a DVD RAM), or other type of memory system that maintains data even after power is removed from the system. The non-volatile memory may also be a random access memory.
The non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system. A non-volatile memory that is remote from the system, such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.
In this description, some functions and operations are described as being performed by or caused by software code to simplify description. However, such expressions are also used to specify that the functions result from the execution of the code/instructions by a processor, such as a microprocessor.
Alternatively, or in combination, the functions and operations as described here can be implemented using special purpose circuitry, with or without software instructions, such as Application-Specific Integrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can be implemented using hardwired circuitry without software instructions or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.
While one embodiment can be implemented in fully functioning computers and computer systems, various embodiments are capable of being distributed as a computing product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
Routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically include one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.
A machine-readable medium can be used to store software and data that, when executed by a data processing system, causes the system to perform various methods. The executable software and data may be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices. Further, the data and instructions can be obtained from centralized servers or peer-to-peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer-to-peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in their entirety prior to the execution of the applications. Alternatively, portions of the data and instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine-readable medium in their entirety at a particular instance of time.
Examples of computer-readable media include but are not limited to recordable and non-recordable type media, such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others. The computer-readable media may store the instructions.
The instructions may also be embodied in digital and analog communication links for electrical, optical, acoustical or other forms of propagated signals, such as carrier waves, infrared signals, digital signals, etc. However, propagated signals, such as carrier waves, infrared signals, digital signals, etc. are not tangible machine-readable medium and are not configured to store instructions.
In general, a machine-readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the techniques. Thus, the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
Other Aspects
The description and drawings are illustrative and are not to be construed as limiting. The present disclosure is illustrative of inventive features to enable a person skilled in the art to make and use the techniques. Various features, as described herein, should be used in compliance with all current and future rules, laws and regulations related to privacy, security, permission, consent, authorization, and others. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment, and, such references mean at least one.
The use of headings herein is merely provided for ease of reference and shall not be interpreted in any way to limit this disclosure or the following claims.
Reference to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, and are not necessarily all referring to separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described that may be exhibited by one embodiment and not by others. Similarly, various requirements are described that may be requirements for one embodiment, but not other embodiments. Unless excluded by explicit description and/or apparent incompatibility, any combination of various features described in this description is also included here. For example, the features described above in connection with “in one embodiment” or “in some embodiments” can be all optionally included in one implementation, except where the dependency of certain features on other features, as apparent from the description, may limit the options of excluding selected features from the implementation, and incompatibility of certain features with other features, as apparent from the description, may limit the options of including selected features together in the implementation.
The disclosures of the above discussed patent documents are hereby incorporated herein by reference.
In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
The present application claims priority to Prov. U.S. Pat. App. Ser. No. 61/952,820, filed Mar. 13, 2014, the entire disclosure of which is hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4941090 | McCarthy | Jul 1990 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5117355 | McCarthy | May 1992 | A |
| 5202826 | McCarthy | Apr 1993 | A |
| 5287268 | McCarthy | Feb 1994 | A |
| 5465206 | Hilt et al. | Nov 1995 | A |
| 5477038 | Levine et al. | Dec 1995 | A |
| 5530232 | Taylor | Jun 1996 | A |
| 5621201 | Langhans et al. | Apr 1997 | A |
| 5689100 | Carrithers et al. | Nov 1997 | A |
| 5774870 | Storey | Jun 1998 | A |
| RE36116 | McCarthy | Feb 1999 | E |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5937391 | Ikeda et al. | Aug 1999 | A |
| 5956694 | Powell | Sep 1999 | A |
| 6032136 | Brake, Jr. et al. | Feb 2000 | A |
| 6055512 | Dean et al. | Apr 2000 | A |
| 6101477 | Hohle et al. | Aug 2000 | A |
| 6129274 | Suzuki | Oct 2000 | A |
| 6138911 | Fredregill et al. | Oct 2000 | A |
| 6243687 | Powell | Jun 2001 | B1 |
| 6247129 | Keathley et al. | Jun 2001 | B1 |
| 6251017 | Leason et al. | Jun 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6334108 | Deaton et al. | Dec 2001 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6341353 | Herman et al. | Jan 2002 | B1 |
| 6408286 | Heiden | Jun 2002 | B1 |
| 6450407 | Freeman et al. | Sep 2002 | B1 |
| 6560581 | Fox et al. | May 2003 | B1 |
| 6571216 | Garg et al. | May 2003 | B1 |
| 6594640 | Postrel | Jul 2003 | B1 |
| 6606745 | Maggio | Aug 2003 | B2 |
| 6663105 | Sullivan et al. | Dec 2003 | B1 |
| 6721743 | Sakakibara | Apr 2004 | B1 |
| 6741968 | Jacoves et al. | May 2004 | B2 |
| 6748365 | Quinlan et al. | Jun 2004 | B1 |
| 6820061 | Postrel | Nov 2004 | B2 |
| 6829586 | Postrel | Dec 2004 | B2 |
| 6842739 | Postrel | Jan 2005 | B2 |
| 6856820 | Kolls | Feb 2005 | B1 |
| 6865547 | Brake, Jr. et al. | Mar 2005 | B1 |
| 6947898 | Postrel | Sep 2005 | B2 |
| 6978250 | Kawan et al. | Dec 2005 | B1 |
| 7054830 | Eggleston et al. | May 2006 | B1 |
| 7072864 | Brake, Jr. et al. | Jul 2006 | B2 |
| 7096190 | Postrel | Aug 2006 | B2 |
| 7134087 | Bushold et al. | Nov 2006 | B2 |
| 7163145 | Cohagan et al. | Jan 2007 | B2 |
| 7263507 | Brake, Jr. et al. | Aug 2007 | B1 |
| 7370811 | Turner et al. | May 2008 | B2 |
| 7376580 | Walker et al. | May 2008 | B1 |
| 7398225 | Voltmer et al. | Jul 2008 | B2 |
| 7424617 | Boyd et al. | Sep 2008 | B2 |
| 7428498 | Voltmer et al. | Sep 2008 | B2 |
| 7606730 | Antonucci | Oct 2009 | B2 |
| 7624041 | Postrel | Nov 2009 | B2 |
| 7665660 | Degliantoni et al. | Feb 2010 | B2 |
| 7680688 | Hessburg et al. | Mar 2010 | B2 |
| 7686218 | Hessburg et al. | Mar 2010 | B2 |
| 7742943 | Postrel | Jun 2010 | B2 |
| 7753264 | Shafer et al. | Jul 2010 | B2 |
| 7765124 | Postrel | Jul 2010 | B2 |
| 7769630 | Postrel | Aug 2010 | B2 |
| 7777053 | Sanganbhatla et al. | Aug 2010 | B2 |
| 7828206 | Hessburg et al. | Nov 2010 | B2 |
| 7853529 | Walker et al. | Dec 2010 | B1 |
| 7868218 | Clark et al. | Jan 2011 | B2 |
| 7870022 | Bous et al. | Jan 2011 | B2 |
| 7894634 | Chung | Feb 2011 | B2 |
| 8010405 | Bortolin et al. | Aug 2011 | B1 |
| 8046256 | Chien et al. | Oct 2011 | B2 |
| 8155999 | de Boer et al. | Apr 2012 | B2 |
| 8180671 | Cohagan et al. | May 2012 | B2 |
| 8265993 | Chien et al. | Sep 2012 | B2 |
| 8285643 | Isaacson et al. | Oct 2012 | B2 |
| 8301593 | Hoffmann et al. | Oct 2012 | B2 |
| 8302030 | Soroca et al. | Oct 2012 | B2 |
| 8313023 | McGhie et al. | Nov 2012 | B1 |
| 8315929 | Allen-Rouman et al. | Nov 2012 | B2 |
| 8332290 | Venturo et al. | Dec 2012 | B1 |
| 8342399 | McGhie et al. | Jan 2013 | B1 |
| 8401967 | Postrel | Mar 2013 | B1 |
| 8478640 | Postrel | Jul 2013 | B2 |
| 8511550 | McGhie et al. | Aug 2013 | B1 |
| 8682791 | Bies et al. | Mar 2014 | B2 |
| 8880431 | Ovick et al. | Nov 2014 | B2 |
| 20010016827 | Fernandez | Aug 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020026348 | Fowler et al. | Feb 2002 | A1 |
| 20020046116 | Hohle et al. | Apr 2002 | A1 |
| 20020062249 | Iannacci | May 2002 | A1 |
| 20020082920 | Austin et al. | Jun 2002 | A1 |
| 20020160761 | Wolfe | Oct 2002 | A1 |
| 20030004808 | Elhaoussine et al. | Jan 2003 | A1 |
| 20030040964 | Lacek | Feb 2003 | A1 |
| 20030158818 | George et al. | Aug 2003 | A1 |
| 20030212626 | Vulkan | Nov 2003 | A1 |
| 20030216967 | Williams | Nov 2003 | A1 |
| 20030225618 | Hessburg et al. | Dec 2003 | A1 |
| 20030236704 | Antonucci | Dec 2003 | A1 |
| 20030236712 | Antonucci et al. | Dec 2003 | A1 |
| 20040049423 | Kawashima et al. | Mar 2004 | A1 |
| 20040083170 | Bam et al. | Apr 2004 | A1 |
| 20040088376 | McCanne et al. | May 2004 | A1 |
| 20040104760 | Ando | Jun 2004 | A1 |
| 20040117250 | Lubow et al. | Jun 2004 | A1 |
| 20040133472 | Leason et al. | Jul 2004 | A1 |
| 20040138949 | Darnton et al. | Jul 2004 | A1 |
| 20040148224 | Gauthier et al. | Jul 2004 | A1 |
| 20040186773 | George et al. | Sep 2004 | A1 |
| 20040203648 | Wong | Oct 2004 | A1 |
| 20040238622 | Freiberg | Dec 2004 | A1 |
| 20040249710 | Smith et al. | Dec 2004 | A1 |
| 20040260608 | Lewis et al. | Dec 2004 | A1 |
| 20050010533 | Cooper | Jan 2005 | A1 |
| 20050021399 | Postrel | Jan 2005 | A1 |
| 20050021401 | Postrel | Jan 2005 | A1 |
| 20050055272 | Ryan et al. | Mar 2005 | A1 |
| 20050060225 | Postrel | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050080727 | Postrel | Apr 2005 | A1 |
| 20050091152 | Suisa | Apr 2005 | A1 |
| 20050114213 | Smith et al. | May 2005 | A1 |
| 20050119938 | Smith et al. | Jun 2005 | A1 |
| 20050149394 | Postrel | Jul 2005 | A1 |
| 20050205666 | Ward et al. | Sep 2005 | A1 |
| 20050240472 | Postrel | Oct 2005 | A1 |
| 20050240478 | Lubow et al. | Oct 2005 | A1 |
| 20060010033 | Thomas | Jan 2006 | A1 |
| 20060020511 | Postrel | Jan 2006 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060059040 | Eldred et al. | Mar 2006 | A1 |
| 20060129456 | Walker et al. | Jun 2006 | A1 |
| 20060136299 | Ruhmkorf | Jun 2006 | A1 |
| 20060184419 | Postrel | Aug 2006 | A1 |
| 20060190337 | Ayers, Jr. et al. | Aug 2006 | A1 |
| 20060206376 | Gibbs et al. | Sep 2006 | A1 |
| 20060208065 | Mendelovich et al. | Sep 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060287943 | Postrel | Dec 2006 | A1 |
| 20070005416 | Jackson et al. | Jan 2007 | A1 |
| 20070011044 | Hansen | Jan 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070043619 | Leason et al. | Feb 2007 | A1 |
| 20070043620 | Leason et al. | Feb 2007 | A1 |
| 20070078719 | Schmitt et al. | Apr 2007 | A1 |
| 20070100691 | Patterson | May 2007 | A1 |
| 20070112629 | Solomon et al. | May 2007 | A1 |
| 20070129955 | Dalmia et al. | Jun 2007 | A1 |
| 20070129998 | Postrel | Jun 2007 | A1 |
| 20070130011 | Postrel | Jun 2007 | A1 |
| 20070143178 | Citrin et al. | Jun 2007 | A1 |
| 20070192784 | Postrel | Aug 2007 | A1 |
| 20070198338 | Heywood | Aug 2007 | A1 |
| 20070214049 | Postrel | Sep 2007 | A1 |
| 20070226059 | Postrel | Sep 2007 | A1 |
| 20070260509 | Hines et al. | Nov 2007 | A1 |
| 20070288313 | Brodson et al. | Dec 2007 | A1 |
| 20080010154 | Tietzen et al. | Jan 2008 | A1 |
| 20080021784 | Hessburg et al. | Jan 2008 | A1 |
| 20080040222 | Gee | Feb 2008 | A1 |
| 20080040270 | Buchheit et al. | Feb 2008 | A1 |
| 20080059303 | Fordyce | Mar 2008 | A1 |
| 20080071640 | Nguyen | Mar 2008 | A1 |
| 20080077499 | Ariff et al. | Mar 2008 | A1 |
| 20080103968 | Bies et al. | May 2008 | A1 |
| 20080120221 | Toneguzzo | May 2008 | A1 |
| 20080133350 | White et al. | Jun 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080147534 | Ephrati et al. | Jun 2008 | A1 |
| 20080154676 | Suk | Jun 2008 | A1 |
| 20080154722 | Galinos | Jun 2008 | A1 |
| 20080162318 | Butler | Jul 2008 | A1 |
| 20080177627 | Cefail | Jul 2008 | A1 |
| 20080201224 | Owens et al. | Aug 2008 | A1 |
| 20080228563 | Zellner et al. | Sep 2008 | A1 |
| 20080228583 | MacDonald et al. | Sep 2008 | A1 |
| 20080249861 | Carotta et al. | Oct 2008 | A1 |
| 20080313034 | Wise | Dec 2008 | A1 |
| 20090006203 | Fordyce, III et al. | Jan 2009 | A1 |
| 20090018909 | Grecia | Jan 2009 | A1 |
| 20090030793 | Fordyce, III | Jan 2009 | A1 |
| 20090048916 | Nuzum et al. | Feb 2009 | A1 |
| 20090076911 | Vo et al. | Mar 2009 | A1 |
| 20090076912 | Rajan et al. | Mar 2009 | A1 |
| 20090106112 | Dalmia et al. | Apr 2009 | A1 |
| 20090106115 | James et al. | Apr 2009 | A1 |
| 20090106300 | Brown | Apr 2009 | A1 |
| 20090112721 | Hammad et al. | Apr 2009 | A1 |
| 20090176580 | Herrmann et al. | Jul 2009 | A1 |
| 20090198572 | Jurgens | Aug 2009 | A1 |
| 20090271262 | Hammad | Oct 2009 | A1 |
| 20090307118 | Baumgartner, IV | Dec 2009 | A1 |
| 20090307130 | Tan | Dec 2009 | A1 |
| 20100010901 | Marshall et al. | Jan 2010 | A1 |
| 20100030688 | Patterson | Feb 2010 | A1 |
| 20100042517 | Paintin et al. | Feb 2010 | A1 |
| 20100051691 | Brooks et al. | Mar 2010 | A1 |
| 20100057551 | Blaisdell | Mar 2010 | A1 |
| 20100057553 | Ameiss et al. | Mar 2010 | A1 |
| 20100075638 | Carlson et al. | Mar 2010 | A1 |
| 20100076820 | Davis | Mar 2010 | A1 |
| 20100125737 | Kang | May 2010 | A1 |
| 20100145855 | Fordyce, III et al. | Jun 2010 | A1 |
| 20100174596 | Gilman et al. | Jul 2010 | A1 |
| 20100211445 | Bodington | Aug 2010 | A1 |
| 20100211469 | Salmon et al. | Aug 2010 | A1 |
| 20100274659 | Antonucci et al. | Oct 2010 | A1 |
| 20100306032 | Jolley | Dec 2010 | A1 |
| 20100312626 | Cervenka | Dec 2010 | A1 |
| 20100312631 | Cervenka | Dec 2010 | A1 |
| 20100312632 | Cervenka | Dec 2010 | A1 |
| 20100312633 | Cervenka | Dec 2010 | A1 |
| 20100312634 | Cervenka | Dec 2010 | A1 |
| 20100312635 | Cervenka | Dec 2010 | A1 |
| 20110022448 | Strock et al. | Jan 2011 | A1 |
| 20110022514 | Lal et al. | Jan 2011 | A1 |
| 20110047019 | Cervenka et al. | Feb 2011 | A1 |
| 20110066483 | Salmon et al. | Mar 2011 | A1 |
| 20110082739 | Pourfallah | Apr 2011 | A1 |
| 20110087530 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110145148 | Hammad | Jun 2011 | A1 |
| 20110161230 | Singh | Jun 2011 | A1 |
| 20110218868 | Young et al. | Sep 2011 | A1 |
| 20110231258 | Winters | Sep 2011 | A1 |
| 20110238483 | Yoo et al. | Sep 2011 | A1 |
| 20110276493 | Graham, III et al. | Nov 2011 | A1 |
| 20110276495 | Varadarajan et al. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110288924 | Thomas et al. | Nov 2011 | A1 |
| 20110295675 | Reodica | Dec 2011 | A1 |
| 20120010940 | Masi | Jan 2012 | A1 |
| 20120035998 | Chien et al. | Feb 2012 | A1 |
| 20120041812 | Postrel | Feb 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120123849 | Armstrong | May 2012 | A1 |
| 20120179531 | Kim | Jul 2012 | A1 |
| 20120191525 | Singh et al. | Jul 2012 | A1 |
| 20120215610 | Amaro et al. | Aug 2012 | A1 |
| 20120215624 | Ramer et al. | Aug 2012 | A1 |
| 20120215638 | Bennett et al. | Aug 2012 | A1 |
| 20120221446 | Grigg et al. | Aug 2012 | A1 |
| 20120226545 | Gebb et al. | Sep 2012 | A1 |
| 20120226604 | Isaacson et al. | Sep 2012 | A1 |
| 20120239417 | Pourfallah et al. | Sep 2012 | A1 |
| 20120239477 | Cueli et al. | Sep 2012 | A1 |
| 20120245987 | Isaacson et al. | Sep 2012 | A1 |
| 20120267432 | Kuttuva | Oct 2012 | A1 |
| 20120271689 | Etheredge et al. | Oct 2012 | A1 |
| 20120271691 | Hammad et al. | Oct 2012 | A1 |
| 20120271697 | Gilman et al. | Oct 2012 | A1 |
| 20120290950 | Rapaport et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120316945 | Wolf et al. | Dec 2012 | A1 |
| 20120323663 | Leach | Dec 2012 | A1 |
| 20130006848 | Kuttuva | Jan 2013 | A1 |
| 20130060679 | Oskolkov et al. | Mar 2013 | A1 |
| 20130124278 | Najm | May 2013 | A1 |
| 20130151323 | Shepard et al. | Jun 2013 | A1 |
| 20130151401 | Scipioni et al. | Jun 2013 | A1 |
| 20130268333 | Ovick et al. | Oct 2013 | A1 |
| 20130282461 | Ovick et al. | Oct 2013 | A1 |
| 20140222533 | Ovick et al. | Aug 2014 | A1 |
| 20150088626 | Salmon et al. | Mar 2015 | A1 |
| 20150088633 | Salmon et al. | Mar 2015 | A1 |
| 20150142655 | Ghosh | May 2015 | A1 |
| 20150199660 | Dolan | Jul 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2003502763 | Jan 2003 | JP |
| 2004303015 | Oct 2004 | JP |
| 20010083521 | Sep 2001 | KR |
| 20010096673 | Nov 2001 | KR |
| 1020020050219 | Jun 2002 | KR |
| 20030080111 | Oct 2003 | KR |
| 1020040016771 | Feb 2004 | KR |
| 20040028110 | Apr 2004 | KR |
| 1020040040253 | May 2004 | KR |
| 1020040077077 | Sep 2004 | KR |
| 1020050061661 | Jun 2005 | KR |
| 20060101241 | Sep 2006 | KR |
| 100717590 | May 2007 | KR |
| 1020070110241 | Nov 2007 | KR |
| 100836484 | Jun 2008 | KR |
| 20080102439 | Nov 2008 | KR |
| PA1013136 | Jun 2004 | MX |
| 0079461 | Dec 2000 | WO |
| 2005022342 | Mar 2005 | WO |
| 2006121541 | Nov 2006 | WO |
| 2008016923 | Feb 2008 | WO |
| 2008102935 | Aug 2008 | WO |
| 2010093893 | Aug 2010 | WO |
| 2010135642 | Nov 2010 | WO |
| 200200475 | Jun 2003 | ZA |
| Entry |
|---|
| International Patent Application PCT/US2010/024057, International Search Report & Written Opinion, Sep. 28, 2010. |
| International Patent Application PCT/US2010/035769, International Search Report and Written Opinion, Jan. 12, 2011. |
| International Patent Application PCT/US2010/037646, International Search Report and Written Opinion, Jan. 18, 2011. |
| International Patent Application PCT/US2010/046360, International Seach Report and Written Opinion, Mar. 30, 2011. |
| International Patent Application PCT/US2012/059607, International Search Report and Written Opinion, Mar. 15, 2013. |
| International Patent Application PCT/US2012/068541, International Search Report and Written Opinion, Mar. 20, 2013. |
| International Patent Application PCT/US2013/023642 International Search Report and Written Opinion, May 30, 2013. |
| International Patent Application PCT/US2013/032307 International Search Report and Written Opinion, Jun. 26, 2013. |
| International Patent Application PCT/US12/68541, International Preliminary Report on Patentability, Jun. 10, 2014. |
| Nenger Monika, Evening the odds: CRM systems are driving sophisticated loyalty programs at Las Vegas Casinos—and not just for the high rollers, Mar. 1, 2002. |
| Number | Date | Country | |
|---|---|---|---|
| 20150262177 A1 | Sep 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61952820 | Mar 2014 | US |
